On Fri, 18 Mar 2005 10:20:53 -0800, Mike Orr  wrote:
> Paul Moore wrote:
>
> >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).
>
> I have some code which, combined with Form, will do a
> search/results/details view.  I have to run for a plane so I can't
> post it now, but it will be in the next Superdemo next month.
[...]
> Is something like this what you're looking for?

It certainly sounds similar. I'll look out for it in the next Superdemo.

The interesting (to me) bit of this sort of thing is how to make it
into a "drop in" component. I have a concept of web application design
that works almost like Visual basic did - drop a data-bound grid here,
a couple of buttons there, customise the grid by setting paging=True
and rows_per_page=20, etc. Add a data source for the grid, and you
have a full webpage with working links all set up. And the layout is
nice and fluid, like Tk's packer produces. All without me having to
write any HTML or CSS. Oh, yes, and I'd like to be able to drop the
result into the "content" region of my site page template, which was
designed in a similar way (breadcrumbs here, link panel there, etc).

For my taste, too much web application design seems to be
hand-crafting snippets of HTML, and fighting CSS and browser
limitations. That seems to me the sort of thing that should be solved
once, and packaged up.

Sorry, I just went off into wild speculation there. Back down to earth now...

Paul.