[Radiant] Page Parts as Model (behavior) Attributes, Inheritance

[Daniel Sheppard]

> Imagine for a moment adding a pluralized page called "Recipes" of
fictitious behavior "Model."
> The Model behavior can optionally change the layout of parts to appear
as sequential fields
> Each part may have additional functionality, eg: rails-style
validations

This is somewhat what I'm trying to do here:
http://soxbox.no-ip.org/radiant/ - though I was going down the path that
the model of the page itself was changable, rather than the individual
parts. Which makes sense for introducing new interfaces for pages that
aren't really 'parted' - things like redirection pages and such. I've
got most of how to implement it in my head, and a some movements towards
it in my svn repository, but my employer just put me into a new project
that's taking up a lot of my thinking time at the moment, so I'm
struggling to weigh up the decisions of some of the key interface
problems.

Placing different behaviours and models onto page parts is a really
interesting idea. Having a page made up of many structured parts, with
the ability to inherit those parts, is definitely something that I'll be
thinking about... though I'm struggling to think of the use-cases at the
moment that aren't covered by being able to change the model of the
page... maybe as an avenue for introducing multiple behaviors into a
page (a recipe model behavior combined with a comments behavior without
having the create a CommentableRecipe behavior). 

Dan.