Ramiro Diaz Trepat
ramiro at diaztrepat.name
Mon Oct 5 22:38:17 UTC 2009
Hi Philippe, thanks a lot for replying.A couple of cuestions about your
suggestion. If I understood right, you say:
Use #resourseUrl: in your #updateRoot: like:
anHtmlRoot stylesheet resourceUrl: 'css/style.css'
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
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:
right in the last line. Because the url that was written on the
configuration is basically a ByteString (which does not implement
I guess this must be a bug in Seaside 3.0
In development, serve files statically from the file system with Komanche,
instead of WAFileLibrary I guess.
Do you have a code snippet to make Kom serve files from a certain path
without disrupting Seaside?
On Mon, Oct 5, 2009 at 8:54 PM, Philippe Marschall <
philippe.marschall at gmail.com> wrote:
> 2009/10/1, Ramiro Diaz Trepat <ramiro at diaztrepat.name>:
> > 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.I guess this is a standard
> > up issue to solve with WASystemConfiguration subclasses for anyone
> > developing with Seaside.
> > If I have resources on a server, in a simple structure like:
> > /css
> > /img
> > /js
> > but for development I just use komanche and WAFileLibrary, which holds
> > resources in a single "virtual" path:
> > /file/LibraryName/resources
> > Then, in my root component I would like to have something like
> > RootComponent>>updateRoot: anHtmlRoot
> > super updateRoot: anHtmlRoot.
> > "in case i am in dev"
> > anHtmlRoot stylesheet url: MyFileLibrary / #styleCss
> That's an uncool pattern. I know the tests use it everywhere but you
> shouldn't use it. It's better to implement #selectorsToInclude in
> MyFileLibrary and answer #(styleCss). The best way is probably to use
> #resourceUrl: 'css/style.css'
> > Should I try to get which subclass of WASystemConfiguration is installed
> > build the relative path inside #updateRoot: ?
> > Or is there a different way to sort this out?
> There are multiple ways you can go. If you use Comanche I'd use
> #resourceUrl: and a Comanche config to serve the files from disk.
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside