> 1. Hope cakephp is suitable for building this kind of application ? > Here we are going to use the latest version of cakephp (RC2). We will > migrate to the stable version once it is released.How difficult it > will be ?
I would consider this largely a non-issue. The cakephp team is generally very good about not breaking code compatibility from the previous version. Especially considering that you will be using a release candidate version, the risk of anything major changing is very small. > 2.In our product, there will be different modules and we want to > customize the modules as much as possible. For example, like in > oscommerce the admin should be able to add and remove the modules (ex: > paypal module from payment section, fedex module from shipping section > etc). And these modules should be independent (but these can use some > common code). How can be implemented this feature ? If I were doing something like this, I'd likely code these modules as elements (app/views/elements). These are self-contained blocks of code that accept parameters from a view. It's easy to pre-render them, or pop them right into a layout. > 3.How can I switch to different template layouts (as like in joomla) ? > In cake, we are placing the image files, css etc in separate folders, > so how can I create a template layout easily without placing the files > in separate folders ? In your app/views/layouts directory, you can build as many templates as you'd like. To call a specific layout, in your controller, you'd just set $this->layout to the name of the layout file. You can reference different image and css files in the layouts. > 4.There will be different user groups and users will be in multiple > groups. And the admin should be do assign some permissions to those > groups.(For example like in Joomla the articles can be assigned to > some user groups with add / edit / publish etc permissions). Is there > a similar functionality in cake ? And which will be good to track the > user sessions (files or database) ? CakePHP offers a fully generic ACL implementation, or several built-in ACL structures. These only provide the ability to check for CRUD (create, read, update, delete) on a request object - it's up to you to write code to send and respond to the checks. > 5. Hope cake 1.2 supports internationalization by default. How can I > implement this to different modules and templates ? For example if the > admin change the language, the whole site should be changed to that > language. Cake is fully internationalized out of the box. > 6. Where can I write common code ? For example, two controllers are > using the same code for saving the records into the database (here all > fields are same only table name is different). Can I use requestAction > for this by writing the code in one controller and calling it from > another controller ? Or should I use components for this ? It depends on the nature of the code. Common code for views would exist as a Helper, common code for controllers would exist as a Component. Also Cake is fully object-oriented so if you wanted to extend a base class, you could do that too. As for code samples and examples, the Bakery (http:// bakery.cakephp.org) is your best bet. Tons of helpful tutorials and information there. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
