On Fri, 18 Mar 2005 00:01:33 -0800, Shalabh Chaturvedi
 wrote:
> Mike Orr wrote:
>
> > I was attracted to Quixote because of its minimalist approach, much
> > smaller than other web application servers, yet every "essential" I
> > needed was there:
>
> > But as time goes on I find more essentials I wish Quixote had (things
> > that David doesn't necessarily agree are essential :).  In my mind,
> > Quixote or Quixote+batteries should come with everything one needs to
> > build a straightforward professional app.
>
> What is essential and what is not will vary from person to person.

I agree entirely here. The one major lack I have found in every Python
web framework I have tried is support for building simple CRUD (Create
Report Update Delete) database applications. Something like a form
library, but for table-based (paged) display of database recordsets.
This perceived lack, however, reflects on my requirements rather than
on a real omission in Quixote (or any other framework).

> The real question (not for me to answer) is what does Quixtoe want to be?
> A Zope replacement, an effective object publishing library, or somewhere
> in between?

My understanding has always been that Quixote is at heart an object
publishing system. That's the core, the rest is useful but optional
extras.

I'd also support the idea of some sort of Quixote-extras project,
where people can contribute standalone components which integrate with
Quixote. Of course, the problem is getting contributions, and ensuring
some common standard (of quality, or API, or whatever).

Paul.