Regarding what to do, I hope to have the automated tests for all kits converted before PyCon so we can rely on them to not break things. It would be nice to have a build before then too so we are freer to change things.
Some ideas I have are:
• Documentation as Eric Radman suggests.
• Some example websites to be included in the distribution. I'm thinking one very simple website to get started with, and another fully featured website with masteads, navigation, forms, user authentication, and maybe DB support with MiddleKit
• Clean up the build process. Instead of building the documentation and so forth in place, how about put things in a build/ directory like disutils does.
• Split WebKit into two parts, a WSGI container, and WSGIKit.
• Reorganize working app folders. I'm thinking about a folder layout like this:
myWebApp/
htdocs/
lib/
run.py
Run.py sets up your python path, and launches the app server. The app server notices that there are no configuration files so it creates a directory for it's files and writes in default config files:
myWebApp/
htdocs/
lib/
run.py
webwareconfig/
webwaredata/
Cache/
Session/
Logs/
The advantages would be: (1) Easy to clean out temporary webware data, it's all in one folder. (2) You can distribute applications and examples with just a few files. In the simplest case, run.py and htdocs/index.py.
On Jan 31, 2005, at 11:21 PM, Tracy Ruggles wrote:
I'll be there. Not sure yet how many days early, but at least the last 2 days of the sprint period, maybe all 4. Any specific work anyone is interested in?_________________________________________
--Tracy
Winston Wolff wrote:
winston wolff - (646) 827-2242 - http://www.stratolab.com - learning by creating
