Hi Philippe, thanks a lot for replying.<div>A couple of cuestions about your suggestion. If I understood right, you say:</div><div><br></div><div><b>First</b></div><div>Use #resourseUrl: in your #updateRoot: like:</div><div>
<br></div><div>anHtmlRoot stylesheet resourceUrl: 'css/style.css'</div><div><br></div><div>This sounds very good because you can change the resource base url either in a subclass of WASystemConfiguration or directly on the configuration of the website.</div>
<div>I have just tried this approach just now, and if the "Resource Base Url" entry field is not empty in the configuration it produces a walkback (MNU #addToPath:) in method:</div><div><br></div><div>WARenderContext>>absoluteUrlForResource:</div>
<div>right in the last line. Because the url that was written on the configuration is basically a ByteString (which does not implement #addToPath:)</div><div><br></div><div>I guess this must be a bug in Seaside 3.0</div>
<div><br></div><div><br></div><div><br></div><div><b>Second</b></div><div>In development, serve files statically from the file system with Komanche, instead of WAFileLibrary I guess.</div><div>Do you have a code snippet to make Kom serve files from a certain path without disrupting Seaside?</div>
<div><br></div><div><br></div><div>Cheers</div><div><br></div><div>r</div><div><br></div><div><br><br><div class="gmail_quote">On Mon, Oct 5, 2009 at 8:54 PM, Philippe Marschall <span dir="ltr"><<a href="mailto:philippe.marschall@gmail.com">philippe.marschall@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">2009/10/1, Ramiro Diaz Trepat <<a href="mailto:ramiro@diaztrepat.name">ramiro@diaztrepat.name</a>>:<br>
<div class="im">> This is an easy one I guess. Indeed it may be solved in a number of ways, I<br>
> just wanted to ask what is the standard way.I guess this is a standard set<br>
> up issue to solve with WASystemConfiguration subclasses for anyone<br>
> developing with Seaside.<br>
><br>
> If I have resources on a server, in a simple structure like:<br>
><br>
> /css<br>
> /img<br>
> /js<br>
><br>
> but for development I just use komanche and WAFileLibrary, which holds all<br>
> resources in a single "virtual" path:<br>
><br>
> /file/LibraryName/resources<br>
><br>
><br>
> Then, in my root component I would like to have something like<br>
><br>
><br>
> RootComponent>>updateRoot: anHtmlRoot<br>
> super updateRoot: anHtmlRoot.<br>
><br>
> "in case i am in dev"<br>
> anHtmlRoot stylesheet url: MyFileLibrary / #styleCss<br>
<br>
</div>That's an uncool pattern. I know the tests use it everywhere but you<br>
shouldn't use it. It's better to implement #selectorsToInclude in<br>
MyFileLibrary and answer #(styleCss). The best way is probably to use<br>
#resourceUrl: 'css/style.css'<br>
<div class="im"><br>
> Should I try to get which subclass of WASystemConfiguration is installed and<br>
> build the relative path inside #updateRoot: ?<br>
> Or is there a different way to sort this out?<br>
<br>
</div>There are multiple ways you can go. If you use Comanche I'd use<br>
#resourceUrl: and a Comanche config to serve the files from disk.<br>
<br>
Cheers<br>
Philippe<br>
_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
</blockquote></div><br></div>