[ Re-CCed to quixote-users because I'd appreciate input ;) ]

-> > We use both -- I prefer Quixote for Web applications, and Webware for
-> > Web sites;
->
-> What, in your view, is the difference between "Web applications" and
-> "Web sites"?
->
-> As you may have guessed from my posting to the PyWX list earlier today,
-> I haven't yet made up my mind on which framework to use.

I separate the two based on how complex the application logic is and how
complex the user interface needs to be.  So, for example, my bioinformatics
Web interface (Cartwheel) runs on Quixote, because it has a very simple
user interface but does some fairly tricky things deep inside, and I want
to be able to have the infrastructure fairly represented on the Web.  Quixote
is excellent for this; read AMK's "manifesto" on the subject,

        http://www.amk.ca/python/writing/mx-architecture/

to see what convinced me.

On the other hand, Web designers find Quixote difficult to deal with, so
my Quixote-based sites -- currently the aforementioned Cartwheel and
another site, Collar, that is a conference paper submission system --
tend to have fairly simple user interfaces.  So, for the Sea Urchin Genome
Project (http://sugp.caltech.edu/), which I view as a wrapper around a
read-only database, and our local Web people view as a user interface
issue, we're going to be doing future development in Webware: it's easy
for people to understand the basic WebKit model, and no complex understanding
of Python is required.

So I put Web sites with complex logic (which tend to have simple UIs when
I write them) under the "Web application" rubric, and I put Web sites
with complex UIs (which tend to have simple logic) under the "Web site"
rubric.

This is pretty Titus-centric though.

--titus