Webware for Python

>From: "George Clinton"

>If anyone is interested in exchanging experiences similiar to those id love 
>to hear from you.
>
>GC georgeclinton@...


Well, I'm very new to Webware and I'm developing my first app with it. After 
a few days of researching and reading, I've gotten a basic site framework 
idea set out that I think will be as flexible as humanly possible.

I dedicded to use Apache+Cheetah+Webware+ZODB. I'm following the basic site 
structure set out on the cheetah site for webware apps: 
http://cheetahtemplate.org/docs/users_guide_html_multipage/webware.siteFrameworks.html 
as well as the directory structure (lib, apache, www)

I'm using the inheritance approach with the following layout:

lib/SiteLogic.py -- Python template class containing must have methods as 
well as a database interface.

lib/Site.tmpl -- the "general" site template derived from SiteLogic.py 
containing blocks for all page content.

a hierarchy of templates, divided into sections for the website, abstract 
templates stay in \lib while published templates go in http://www.

MainSite.tmpl (lib)
    Main.tmpl (www)
    Register.tmpl (www)
FooSite.tmpl (lib)
    Foo.tmpl (www)
    FooTopic.tmpl (www)

I've still got to find an easy way to mesh in things like "member only" 
pages but I don't think it will be too tough.

Logic code goes in lib, and it usually for forms:

MainSite.tmpl (lib)
   FormRegister.py (lib)
      Register.tmpl (www)


At first I didn't really like this "mixed" hierarchy concept but it works 
out very well.


my zodb database is loaded in the context's contextInitialize and since it 
is a class-level variable of the site's super abstract class (SiteLogic) 
everybody has access to the db if they want it, and since ZODB is 
thread-safe I don't have to worry about it. Using ZODB transaction support 
also helps out a lot. (And this will be a large app so I plan on switching 
to ZEO eventually). I've just got to figure out a place to put code for 
closing the database.


I'd have to say that the only thing I don't like about this setup is how 
polluted my directories get.
foo.tmpl
foo.py
foo.pyc
foo.py_bak

at least 3 files for every (file).

After this bugger is up and running I'm probably going to hack webware and 
make it auto compile tmpl files and stick the template-servlets into a cache 
var directory, thus removing the need for cheetah compile and all the extra 
files (gonna have to watch performance though).

Just my 2 cents

Jeremy S Lowery

_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE*  
http://join.msn.com/?page=features/junkmail

Re: [Webware-discuss] Webware Application Design Patterns From: Andreas Poisel <a.poisel@ac...> - 2003-02-26 16:00 * Jeremy Lowery <jermnsar@...> [030225 09:20]: > I'd have to say that the only thing I don't like about this setup is how > polluted my directories get. > foo.tmpl > foo.py > foo.pyc > foo.py_bak > > at least 3 files for every (file). I'm using separated "Templates/" and "Servlets/" directories. An A-A-P script (http://www.a-a-p.org/) compiles new or edited templates and moves them from "Templates/" to "Servlets/". BTW: A-A-P is a really great tool for a lot of jobs when creating and maintaining webware applications (compiling templates to servlets, publishing files, running test suites, ...). -- Andi

Re: [Webware-discuss] Webware Application Design Patterns From: Chuck Esterbrook <ChuckEsterbrook@ya...> - 2003-02-26 17:41 On Monday 24 February 2003 11:59 pm, Jeremy Lowery wrote: > After this bugger is up and running I'm probably going to hack > webware and make it auto compile tmpl files and stick the > template-servlets into a cache var directory, thus removing the need > for cheetah compile and all the extra files (gonna have to watch > performance though). I would be interested in using that. WebKit's ServletFactory hook was intended to allow us to add any file type to WebKit that we desire and write any necessary Python code to make it happen. Cheetah's author, Tavis, ran into some technical problems however. If I recall, it was regarding Cheetah inheritance. fyi On Tuesday 25 February 2003 07:01 am, Aaron Held wrote: > For common things such as basic blogs, shopping carts or slashdot > clones, why bother with the advantages of Webware, just drop in a PHP > app. Sure. In fact, the discussion boards for StockAlerts.com were created with a pre-built PHP app, the rest in Webware. But 97% of the time, the applications I build are not blogs, traditional carts or slashdot-wannabes. > All of the the webware apps I have worked on have been very > application specific that are not generally useful other then as > examples. I think with the given PHP and Perl/CGI (think Twiki.org) apps available, there is less incentive to recreate these things in Webware. I'm not saying it wouldn't be useful, but ... On Wednesday 26 February 2003 08:00 am, Andreas Poisel wrote: > BTW: A-A-P is a really great tool for a lot of jobs when creating and > maintaining webware applications (compiling templates to servlets, > publishing files, running test suites, ...). Your experiences and instruction in using AAP with Webware would make an excellent new Wiki page: http://webware.colorstudy.net/twiki/bin/view/Webware nudge nudge -Chuck

Re: [Webware-discuss] Webware Application Design Patterns From: Ian Bicking <ianb@co...> - 2003-02-26 19:37 On Wed, 2003-02-26 at 12:26, Jerome Kerdreux wrote: > > http://webware.colorstudy.net/twiki/bin/view/Webware > > Is this still working ? even a nslookup colorstudy.net return empty That should be webware.colorstudy.com, not .net Ian

Re: [Webware-discuss] Webware Application Design Patterns From: Andreas Poisel <a.poisel@ac...> - 2003-02-27 02:01 * Chuck Esterbrook <ChuckEsterbrook@...> [030226 19:20]: > Your experiences and instruction in using AAP with Webware would make an > excellent new Wiki page: > http://webware.colorstudy.net/twiki/bin/view/Webware I started a Wiki page, but it's far from being excellent ;-) http://webware.colorstudy.com/twiki/bin/view/Webware/UsingAaap -- Andi

1 message has been excluded from this view by a project administrator.