A bit OT, but for general interest check out http://openatrium.com/ It is a "groupware"-type application written on top of Drupal. I have never used Drupal but if I was to start I would first look at how they did it.
Of-course you wanted to know about going the other way... from Drupal to Cake or other framework. Drupal looks like (30sec peek at the code for a custom module) a half-finished app. Not in the sense that anything is missing but that you start with haft the app done. The downside is that you have to live with the modules and hooks to make your code talk to Drupal. You have less freedom. Cake and most other frameworks act in the background as the invisible foundation on which you build your application. Drupal has tons of GUIs and preset features and application design that help you or hinder you depending on what you want to do. If you feel limited then consider another framework but know that there might be a lot that Drupal does that you will now have to build yourself. Example: Cake has authentication. = a core component doing only just that authenticating. Drupal has authentication with groups, registration management, login panel.... = a complete module Cake has an ACL component that can add advanced premissions to the authentication component.... but you still build all the GUIs, decide what and how to authenticate/authorize. On Aug 9, 9:02 pm, Robert P <shiftyrobs...@gmail.com> wrote: > Drupal is a highly extensible CMS with a fairly powerful API, and the > progress from Zengine made it easy to theme as well > > Jake (for Joomla) and Drake (for Drupal) are plugins that allow a Cake > application to be called from certain URIs within the CMS, but this > has a much greater overhead and there are major stumbling blocks > trying to integrate the seperate systems. On the other hand if the > application was moved from Drupal to CakePHP then all the basic > functionality would have to be planned and developed, since Cake is > not a CMS. > > Since Drupal 5 the module API has been fairly robust, and if there is > an application already running on Drupal there would have to be a good > reason to move away from it. > > On Aug 10, 1:50 am, Parris <presid...@parrisstudios.com> wrote: > > > > > As i understand it... drupal isn't so much of a framework and more of > > a cms. Of course it probably does have an api. I have worked with > > drupal once. I got frustrated and moved on. It is really hard to > > create a theme in it, if you ask me. > > > Cake is a framework much like ruby on rails. > > > If you don't want to create a full on cms in cake, you may want to > > check out jake for joomla. I am sure there is something similar for > > drupal also. > > > On Aug 9, 9:14 am, Josh <joshs.silver...@gmail.com> wrote: > > > > Does anyone have CakePHP experience and Drupal custom module > > > experience? > > > > If so, what is your opinion of the Drupal API for writing custom > > > modules? > > > > I have a friend that is about to do a re-design for his Drupal app and > > > is considering changing frameworks. They would have to design 3-4 > > > custom modules. Any thoughts? > > > > Thanks. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
