RE: Cascading Style Sheets with WO
RE: Cascading Style Sheets with WO
- Subject: RE: Cascading Style Sheets with WO
- From: Jonathan Rochkind <email@hidden>
- Date: Wed, 19 Feb 2003 11:40:05 -0600
At 07:16 AM 2/19/2003 -0500, Reid Bundonis wrote:
Reply to: RE: Cascading Style Sheets with WO
Don't store the file as part of the project.
I disagree. I think storing it as part of a project is generally better for
organization and maintanace sake. But you are right that you don't have to,
it's up to you.
If you do then everytime you
make a change you need to rebuild and install the app.
Not true. You _could_ rebuild and re-install the app every time you made a
change. But you could also just drop the new file into place on the web
server manually if you don't want to do an entire rebuild/reinstall.
Instead, if you are
working on OS X, store the file somewhere in web root.
Under normal WO deployment, it will be installed in a particular place
under the web root for you, if you include it as a Web Server Resource.
Then you don't need to install it by hand (and remember where it is) every
time you do an install---it'll just get put there for you. That's one of
the benefits of including it as a Web Server Resource. Under ordinary
'development' builds/executions, Web Server Resources are not served from
the web server document root, but under normal deployment they are. There
may be some way to rig things so they are installed/served from the web
server document root even in development, but I haven't really tried.
Also, use this same strategy for common, non active images. Let Apache do the
work of serving the graphics instead of putting all of the work on WO.
Reference images with the same path strategy, /images/name_of_image.gif.
Again: under a normal WO deployment scenaior, Web Server Resources ARE
served by Apache (or your other web server). Web Server Resources are
installed to [web server
root]/WebObjects/AppOrFrameworkName/resourceAsExample.gif . They are
served by the web server.
You can do things the way Reid describes if you want to. I used to do that
myself; I forget exactly why I thought it was superior, maybe I was just
frustrated becuase I couldn't get the Web Server Resources to work for some
reason. But I later decided this approach had been a mistake, and didn't
give me any advantage, and it was a lot more convenient to put the things
in Web Server Resources. But it's up to you.
--Jonathan
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.