I would recommend that you separate out you different layers in a slightly different fashion than what you described. In the past, I have had success with the following separation. The model layer is stand-alone python modules (no webware code). The view layer is the HTML templates/CSS that is rendered to the client. The controller is the webware servlets (and primarily the actions on the page--those functions returned in actions() ).
If you would like more info on how I've done this, feel free to ask. --John [EMAIL PROTECTED] wrote: > Hi chris, > Many thanks for your tip > Anyway what im looking for is the best way to use webware on a MVC > environment ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
