Hi, and since we're discussing of commas and slashes, why does Turbine require that to be a comma?
and why does the url in the browser than look contain a "%2C" instead of a slash? http://localhost:8080/homeworkmessenger/app/template/members%2CMembers.vm I'm having troubles protecting this url in web.xml because of that.. Thanks Rudi -----Ursprungliche Nachricht----- Von: Jeffery Painter [mailto:[EMAIL PROTECTED] Gesendet: Friday, June 03, 2005 1:53 PM An: Turbine Users List Betreff: Re: Structure On Fri, 3 Jun 2005, madhuranjan kumar sinha wrote: > Hi Levi, > Since you do want to go for the two solutions which you have > mentioned. Third i can suggest is create different folder under screen > folder and append the folder heirarchy path to a call to said page. This can > be feasible bse any how you have change the calls from some hard coded value > present in HTML code to something like $link.setPage... > Ex. if a vm file is in 'test' folder under screen folder then you can call > this page by following code > $link.setPage("test/Test.vm") actually the "proper" turbine way to do this is to use a comma instead $link.setPage("test,Test.vm") > > Hi everebody! > > I must include a large number of fix html s in my turbine framework base > application. The problem is that the html are structured on directories > because they are categorized. How can I include all these html-s > (transformed in vm) in my application in such a way that some kind of > structuredness to be maintained. > 1 One solution is to put all screens in a single directory, but this will be > very hard to maintain - it is not structured > 2 Other solution is to put them in separate directorie. In every directory > to create the structure: layouts, navigations, screens directories and to > include in Turbine resources to velocity resource path the path to my > directory. In this way the turbine resource property will be very long > defined. > > Does anybody know a better solution. Thanks a lot! > Do you absolutely need to use velocity for these pages? It sounds like you said they will be static. If that is true, you could move them out of templates/ into a folder under resources like resources/static/ and then use the $content tool to build the links to those static pages. I may have misunderstood you though, in which case just ignore this suggestion :) <a href="$content.getURI("resources/static/top_level/somePage.html")">some page</a> -- Thank you, Jeffery Painter 2431 Reunion Meadows Lane Apex, NC 27539 voice: 919.321.0378 - -- [EMAIL PROTECTED] http://jeff.kiasoft.com PGP FP: 9CE8 83A2 33FA 32B1 0AB1 4E62 E4CB E4DA 5913 EFBC -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/qEQE5Mvk2lkT77wRAnMJAJ9vJ6qOkg/mvqqIpz7troCEQJ8bFACglu/U YNXabx7DZOV2Hd9LwSTmGpY= =dWiu -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
