MECCA PRODUCTS

MODULAR ENTERPRISE COLLABORATIVE CONTENT ARCHITECTURE (MECCA)
Mecca Framework, for Simple Users; Stupid Developers

Users cry out for not only friendliness but simplicity.
Developers, well, 80% of them are stupid.
Ok, since you are one of us in that respect, take this analogical question:

Which car will u prefer:

1. Ferrari that is super fast but once it breaks down, so do u!
2. Porsche that is not that fast and easier on the pocket, but when it breaks down, so do u!
3. Volkswagen that u don't care if it breaks down, because u can fix it. And it gets u there and still keep the frills!

SIMPLE; for the user as we have…

1. Incorporate high level UI to configure features and personalize content in a easy to use web-interface.
2. Separate individual modules that are pluggable into the Mecca Framework in few easy steps.
3. Written detailed user manuals for using our portal and ERP solutions.
4. Ported in the SourceForge repository for easy access and download of our software.
5. Created a bubbling worldwide community to support newbies.

STUPID; for the developer as we have…

1. Lightning fast to setup
2. Implemented a wrapper to keep you away from the complexity of JSR168 modular portlet technology.
3. Incorporated the easiest templating engine from Apache which is Velocity.
4. Written detailed how-to tutorials on understanding our framework.
5. Embedded SQL-Renderer API for reused.

THE MECCA FRAMEWORK

Mecca framework allows developers to create application that is pluggable into the portal. Basically, web based development is separated into three layers - the data layer, the model layer, and the view layer. The framework make use of this layer by using the Velocity templating engine to separate between model and view layers, while the data layer is handled by the framework’s database API.

To point out why it is easy for developers, lets list down what developers need not do:

1. Security and user authentication - while developing the application, developer don’t have to worry about security and authentication.
    
2. Access control level to module being developed - usually developers have a question - who will be allowed to access this piece of codes? Using the framework, developers don’t have to ask this question, just proceed with his work.
    
3. Database connectivity - use the API
    
4. SQL statements - don’t write the full SQL statement but use the API instead, by only passing field names and values
    
5. Look and feel - color and fonts to be used in the view page is handled by the portal CSS (cascading style sheet), which is the task for web designer.

Modularity allows module to be developed separately, and plugged in to the portal when needed. Module can be run separately or several modules can be grouped together by creating a module’s wrapper object.