It's interesting to watch this idea evolve, and I thought I'd try to sum up our current situation (in Drupal 5) regarding content-related entites and the hooks available for them. This gives a table of all the content-related hooks as I could remember them. I've tried to align horizontally hooks pertaining to a semantically similar operation, and of course columns are used for object types. The table is available here: http://plusvite.net/?245fea66 I've also done a blog post about it and my impressions, to increase remanence on the discussion: http://plusvite.net/?266be461 Frederic G. MARAND fgm / osinet ----- Original Message ----- From: "Chris Johnson" <cxjohnson@gmail.com> To: <development@drupal.org> Sent: Monday, January 22, 2007 9:33 PM Subject: Re: [development] nodify.module idea: 'everything is a node'
Aren't we really talking polymorphism here when we say we want to use the something like the node API "toolkit" on other objects?
If I read and understand correctly, there are 2 major suggestions. One group wants to make more objects be nodes, so that this benefit is gained. Others don't want some other object types to be nodes and have suggested generalizing the node API to obtain the benefits.
Using node-like API functions on other objects sounds like polymorphism to me, which is a "solved problem" so to speak. Any Java or C++ programmers out there who might comment on this? (I only know enough Java and C++ to be dangerous. :-)