On Aug 18, 2004, at 3:12 PM, Graham Fawcett wrote:
> Mario Ruggier wrote:
>> On Aug 18, 2004, at 12:17 AM, Simon Cusack wrote:
>>
>>> 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.
>
> I'd join in too.
>
> I'd love to see something that was component-oriented enough so that I
> could, for example, decide whether to use a relational database, or
> ZODB, or just a bunch of text files to handle persistence. Something
> that works "out of the box" with only Quixote as a requirement (or at
> least only depended on third-party Python packages, but not on other
> installed software) would be tremendously helpful.
>
> -- Graham

I was actually thinking more about the other end... the front-end that
is. Components that can be easily plugged into a site, and that can be
both page-level, and sub-page-level (boxes on a page...), or a mixture
of both... e.g. forums, tracker, news, subscriptions/newsletters, ...
another cms-building framework! This of course means a common auth
interface, common handling of privileges and roles, and so on... do not
think that that is what the scope of quixote is, or will ever be...
but, having such a component web framework defined and implemented in
the quixote philosophy of explicitness and simplicity would certainly
save a _lot_ of trouble... while probably making this world a
significantly better place ;-!

mario