Meitar, I've used drupal quite a bit in the past, and I don't think there is really anything that it does as far as content management that cannot be done with CakePHP. If you were to use EAV (expandable) and table inheritance you can easily build a data structure much like drupal. With an api interface that works like node_load() and node_api_*
If you are interested in data structures like these check out http://bakery.cakephp.org/articles/view/polymorphic-behavior as well. It solves the issue of resolving table inheritance. -Mark On Sep 24, 3:36 am, "Mr. Meitar Moscovitz" <[EMAIL PROTECTED]> wrote: > I realize I'm coming to the party a little late, but I just wanted to > take the opportunity to ask…. > > On Sep 23, 2008, at 11:37 PM, mark_story wrote: > > > As for an already built solution to EAV in cake take a look at > > >http://debuggable.com/posts/unlimited-model-fields-expandable-behavio... > > > Seems to fit the bill pretty closely, and you retain a fair bit of > > 'magic' > > > -Mark > > This "EAV" model sounds very much like an "object database."[0] Does > this assertion make sense or am I missing something fundamental to EAV > that makes it different from an object database? > > It seems like each of these basically define an abstraction for a > "kind of" datum. This is also, interestingly, how Drupal's core works. > Drupal has a notion of something called a "node" (a "content type" in > user-facing docs)[1] and each node can be of a number of "node types". > These types are not technically subclasses in code, but they act as > though they are via its node API[2]. Also interestingly, this is > exactly the kind of architecture that Zope makes use of, and upon > which Plone is built. > > After working with systems like Drupal and Plone, I'm finding that > they are great at solving problems that CakePHP is not necessarily the > ideal for, and that CakePHP is great at solving that are nightmares to > deal with in systems like Drupal and Plone. > > Specifically, when you have a problem domain like content management > (as opposed to application development), it makes sense to specify > something like an EAV-style object hierarchy for your content. This is > a lot like how filesystems work, if you think about it, and so the > hierarchy and its natural inheritance are great solutions for making > good CMSes. > > However, this model is really difficult to work with when what you're > trying to do is build an application whose components really do need > to be tightly associated with one another for functional reasons. What > I'm finding is that many sites these days want a CMS for their > content, but they want some kind of functionality that a framework > like CakePHP is better for. Thus, I think hybrid solutions will become > par for the course *if* bridges and so forth to CMSes can be built > within frameworks. A great example of this is Radiant[3], which is > built on Ruby on Rails but provides a CMS-like platform on top of it. > > Also more generically, Mark, et. al., thanks for posting these links. > I'm finding them a fun and education read. > > Anyway, these are just some half-baked thoughts. Thought maybe someone > would find them interesting, or enlighten me as to their own > experience. It's relevant to me right now because I'm just beginning > to work with CakePHP on a more regular basis (after having spent a few > weekends dabbling for fun), and I'm loving it, yet finding myself > loathe to ditch my favorite already built CMS platforms for many > things…. I'm still playing around with cake and thus trying to figure > out kind of site it excels at. > > My 2¢. Sorry for being rambly. > > Cheers, > -- > -Meitar Moscovitz > Personal:http://maymay.net > Professional:http://MeitarMoscovitz.com > > EXTERNAL REFERENCES: > > [0]http://en.wikipedia.org/wiki/Object_database > [1]http://drupal.org/node/21947 > [2]http://api.drupal.org/api/file/developer/examples/nodeapi_example.module > [3]http://radiantcms.org/ --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
