--> Saturday, September 13, 2003, 2:41:06 PM, [EMAIL PROTECTED] wrote: > I'm getting confused and I'm hoping maybe someone can clarify this for > me. Here's what I'd ideally like to achieve in terms of code organization:
> app_work_dir/lib/myapp > root of python package hierarchy for myapp >[snippity do dah] > Any advice? I find contexts and /WK fairly annoying myself. I do not use them in any way wittingly. I create sites with normal URL's, no crazy rewriting, etc. I put my servlets and other modules in app_work_dir/lib. I then use PSP to create pages in app_work_dir/site, which is the root of the website. I never execute /WK or .py servlets directly. I always execute .psp. However, all my PSP pages are subclasses of defined servlets... <%@ page extends="DocContentsPage" %> <%@ page method="writeStaticContent" %> I don't think I will ever execute raw servlets via URL, as it is most common to subclass well defined servlet modules, and this is much easier with PSP. However, I sometimes write some psp pages which are only one or two lines : <%@ page extends="DocSourcePage" %> <%@ page method="writeStaticContent" %> I suppose I could take that 2nd line out per my implementation. With this specific convention I put these two (or one) lines into a file named like sourcefile.c.psp and visit that URL to see my documentation system's page for a listing of the sourcefile.c code I use as an example in the docs. I've written a very nice documentation system using this design. I looked at all sorts of documentation systems but nothing did everything I wanted. -Kai ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
