Yes, this works with my example, but the example with the URL containing template information is really just an example, while navigating through the Turbine app, the URL using the JavaScript library could be: - http://HOST/myapp/template/main.vm - http://HOST/myapp/template/main.vm/action/MyAction - http://HOST/myapp/template/main.vm/action/MyAction/id/2 - and so on So I'm afraid this is no viable solution - although I acknowledge its ingeniousity!
Alex -----Ursprüngliche Nachricht----- Von: Michael Kunze [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 05. Dezember 2007 08:46 An: [email protected] Betreff: Re: AW: dynamic image loading: image paths in Javascript conflictwith Turbine's path notation, so how to? Zitat von Alexander Zimmer <[EMAIL PROTECTED]>: > Vick, you are basically right. But ... it's just that I want to set > the path in an *external* JavaScript file which will be linked to > the HTML page. So the JavaScript is no included in the (template) > page => it will only be requested by the browser and thus no dynamic > content will be interpreted. > Alex Hi Alex, your problem has a really simple solution. if http://HOST:8080/myapp/template/images/active.gif is an invalid path make it valid. create a folder named template in your static dir! -- Michael Kunze http://www.smrealms.de --------------------------------------------------------------------- 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]
