> How are the nice boxes with the little green 'scriptaculous' header
> displayed? - seems like magic to me. These boxes are coming from a static CSS file: <http://scriptaculous.seasidehosting.st/resources/style.css>. This is a slightly adapted version of the style-sheet that is used at the official script.aculo.us site <http>//script.aculo.us>. They are using these nice boxes as well ;-) Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Hi Frank,
Check out my blog on this topic: Screen shot: http://www.brokentomb.com/images/browser15.gif Blog entry: http://www.brokentomb.com/blog/index.html#28july Your confusion is that you expect the CSS to be in a "style" method. The CSS sheet for this is stored in a server in Bern, Switzerland, and then linked. The fellow who just answered your post runs that server. He just gave you the link to the hidden style sheet. To prove that the style sheet comes from outside Scriptaculous on your computer, try this. Trash your version of Seaside. Download another. Disconnect your computer from the Internet. Open Scriptaculous. It will look awful, because it cannot fire the link it needs to get the CSS style sheet in Bern. Reconnect to the Internet, and try again. Quite a change. Chris Cunnington Toronto _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
> To prove that the style sheet comes from outside Scriptaculous on your
> computer, try this. Trash your version of Seaside. Download another. > Disconnect your computer from the Internet. Open Scriptaculous. It will look > awful, because it cannot fire the link it needs to get the CSS style sheet > in Bern. Reconnect to the Internet, and try again. Quite a change. The whole story is the following: When I started to work on that functional testing suite I directly referenced the style-sheet from the official script.aculo.us site. You can still see this in early version on the SqueakSource repository. Later on I simply swapped that reference to a copy on the seasidehosting.st server and removed some things that were irrelevant. The point is now -- again the same problem as already several times discussed here -- that there are also external image files that I cannot reference from the style-sheet if I don't have a static web-server somewhere. Using the extension of Philippe would enable me to do that using a WAStyleLibrary, though as long as this is not well tested (I don't blame anyone, this is mainly my own fault) and not part of the official distribution it simply won't change. Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
2006/8/11, Lukas Renggli <[hidden email]>:
> > To prove that the style sheet comes from outside Scriptaculous on your > > computer, try this. Trash your version of Seaside. Download another. > > Disconnect your computer from the Internet. Open Scriptaculous. It will look > > awful, because it cannot fire the link it needs to get the CSS style sheet > > in Bern. Reconnect to the Internet, and try again. Quite a change. > > The whole story is the following: > > When I started to work on that functional testing suite I directly > referenced the style-sheet from the official script.aculo.us site. You > can still see this in early version on the SqueakSource repository. > Later on I simply swapped that reference to a copy on the > seasidehosting.st server and removed some things that were irrelevant. > The point is now -- again the same problem as already several times > discussed here -- that there are also external image files that I > cannot reference from the style-sheet if I don't have a static > web-server somewhere. Using the extension of Philippe would enable me > to do that using a WAStyleLibrary, though as long as this is not well > tested (I don't blame anyone, this is mainly my own fault) and not > part of the official distribution it simply won't change. Well it actually has tests, but I know what you want to say. So what are we going to do about it? Because if we do nothing about it everything will stay the same. A special Pier that uses WAFileLibrary and if it works move it in? Philippe _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Lukas Renggli
Is there a way for instances of WAComponent to discover what is the
current document root? _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
2006/8/13, Kurt Thams <[hidden email]>:
> Is there a way for instances of WAComponent to discover what is the > current document root? override #updateRoot: to get the current root. Do any modifications (set title, include css or js, ...) there and don't forget the super send. Philippe _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Free forum by Nabble | Edit this page |