-> >Maybe we should organise a plug in architecture for commonly used
-> >website components like this would be helpful.  Anybody thought of
-> >this?
->
-> Every web framework has dreamed of this sooner than later... I would
-> certainly love to see a quixotic component spec, and if there'd be such
-> a thing I'd be happy to program against (for ;) it.

Perhaps I'm being overly skeptical here -- I hate servlet-style
bureaucracy ;) -- but the reason I love Quixote so much is that
it already provides the perfect "component spec" for my needs:
the Quixote package publication spec is both lightweight and quite
general.  Why do we need add'l specs?

For example, for one project I wrote a ReST/Wiki page object that sits
in a library.  It handles editing and display of individual Wiki pages.
With a little bit of work to separate out the persistence mechanism from
the display mechanism & maybe provide some template drawing functions,
it could be a generally re-usable object for use as a namespace in
pretty much any Quixote framework -- and all the work that needs to
be done is my side, not Quixote's side.

--titus