Fanyun, I am learning, so I hope you don't mind if we discuss this a little further :-) >In turbine, you can call your screen in serveral ways >1. file://local:8080/servlet/Turbine/screen/Test >this will call the test.java class, and use test.getLayout(Rundata data) function to determin the layout. But notice, here the layout is not the *.wm file. It is the layout class name. You have to write another layout class for it. > Excellent point! I did not notice that "getLayout" returned the name of the class. So, when using the "WebMacroSite" classes is it more convenient to specify the template in the URL. Then the template will determine the screen and the layout. I understand that WebMacroSite makes it convenient to convert a site of largely static content to Turbine. But if I am starting new, should my URLs request templates (*.wm) or screens (and let the screen decide the template to return, ala MVC)? I realize that the screen can always "short circuit" the template to be returned. It seems like, if I use WebMacroSite*, the logic of my application is driven by templates, is this limiting? Sorry, if I am making this to complicated!:-) Brian ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/> Problems?: [EMAIL PROTECTED]
