durusmail: quixote-users: Quixote Application Skeleton? Best Practices?
debugging quixote applications
2004-09-20
2004-09-20
Re: debugging quixote applications
2004-09-21
2004-09-21
Quixote Application Skeleton? Best Practices?
Newbie Question - Quixote w/ Medusa - pythonpath issue?
2004-09-21
2004-09-21
Quixote Application Skeleton? Best Practices?
Graham Fawcett
2004-09-21
rtjohan@syspres.com wrote:

> Hi,
>
> How widely used is the "Quixote Application Skeleton" at
> http://www.rexx.com/~dkuhlman/quixote_skeleton.html? Is this
> considered to represent best practices for Quixote?

I'm sure that, at the very least, Dave Kuhlmann would agree it
represents best practices. ;-)

I haven't studied the code; just the Web documentation. The directory
layout is logical and clean, and separates model from UI; it comes with
a set of starter scripts; it uses classes for "object publishing" which
is a good technique to learn; it appears to use the cutting-edge form2
package which is a source of frequent discussion on this list.
Altogether, this gets at least a B+, code unseen. ;-)

> Is it possibly overly complex / convoluted or is it worth studying to
> do things correctly the 1st time?

I might skip the stuff about writing widgets, unless you're extremely
interested in the form/form2 packages. You can choose to do forms the
old-fashioned way:

    def edit [html] (request):
        '
' '' ... or using the existing forms packages; or you can roll your own. Since you're in studying-mode, you might consider the latter: build your own set of widget functions (it's not hard to do), just for the sake of learning, and move on to form/form2 when you're comfortable with Quixote's mechanics. Best, -- Graham
reply