durusmail: quixote-users: Best Practices
Best Practices
2005-07-15
2005-07-15
2005-07-15
Best Practices
David Binger
2005-07-15
On Jul 15, 2005, at 12:06 PM, Orr, Steve wrote:



> I like what I see. But what I need is some more advanced sample code.
> Are there any examples of how to use Javascript with Quixote? I know
> Quixote is meant to be lean and a lot of our "framework" will need to
> stem from our own original engineering efforts. Can someone point
> me to
> some more robust sample code or give me some guidelines in this
> effort?\
>

The dulcinea package includes a lot of example-type code (but no
guidelines).
It includes some widgets that use javascript.
http://www.mems-exchange.org/software/dulcinea/


>
> Here's a specific how-to request:
> We deal with a LOT of tabular database result sets and I'm thinking
> the
> best way to display this is with HTML tables. I've started development
> of a somewhat generic table template object for displaying tabular
> data.
> Now I need to let the user click on the column header to resort the
> data. Most of the time this will require a requerying of the database
>

Dulcinea includes a table class that we use for this purpose.
It supports client-side and server side sorting by column, and
can also generate the table in csv format.
It uses javascript for client side sorting and and a query string
for the server side, but the server-side render could easily be changed.
If you don't want a query string, you could use
ordinary path component to specify the sort column,
or the form-based method you described.




reply