This is an easy one I guess. Indeed it may be solved in a number of ways, I just wanted to ask what is the standard way.<div>I guess this is a standard set up issue to solve with WASystemConfiguration subclasses for anyone developing with Seaside.</div>
<div><br></div><div>If I have resources on a server, in a simple structure like:</div><div><br></div><div>/css</div><div>/img</div><div>/js</div><div><br></div><div>but for development I just use komanche and WAFileLibrary, which holds all resources in a single "virtual" path:</div>
<div><br></div><div>/file/LibraryName/resources</div><div><br></div><div><br></div><div>Then, in my root component I would like to have something like</div><div><br></div><div><br></div><div><div>RootComponent>>updateRoot: anHtmlRoot</div>
<div> super updateRoot: anHtmlRoot.</div><div><br></div><div> "in case i am in dev"</div><div> anHtmlRoot stylesheet url: MyFileLibrary / #styleCss</div><div><br></div><div> "in case i am in prod another path"</div>
<div><br></div><div><br></div><div><br></div><div>Should I try to get which subclass of WASystemConfiguration is installed and build the relative path inside #updateRoot: ?</div><div>Or is there a different way to sort this out?</div>
</div>