RE: Cascading Style Sheets with WO
RE: Cascading Style Sheets with WO
- Subject: RE: Cascading Style Sheets with WO
- From: Reid Bundonis <email@hidden>
- Date: 19 Feb 03 12:57:44 -0500
Reply to: RE: Cascading Style Sheets with WO
Jonathan,
Valid points all. I prefer to work this way as most of the applications that
I've worked on to this point are a mix of WebObjects and static HTML pages.
By using my approach, I can keep the "static" html objects external to the
project and available to other developers on my team. This includes the css,
external javascript file(s), and non-active images. In my environment there
is one WO developer (me) and a handful of HTML developers. If I needed to
incorporate the image and css changes into a project every time a developer
decided to change the text color of a link, I would have no time for anything
else. Essentially, that is my reason. For projects that are all WO, I see
the value of storing everything inside the project. But for the mixed
projects that I do, storing html elements (images, css, etc) in Apache root in
a structure that web developers are familiar with is a lot easier than trying
to get them to place items in the WO project web resources directory,
especially when dealing with virtual hosts and multiple WebObjects folders.
Also, since I am lazy, I also can leave the default permissions on the
WebObjects folder, restricting access by lesser developers on my team.
Anyway, thanks for the feedback. While my practices seem to make sense to me,
I often wonder if my perceived sanity is madness to others.
R-
Jonathan Rochkind wrote:
>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
>
>
>
>
>
>RFC822 header
>-----------------------------------
>
> RECEIVED: from SF_Database by POP_Mailbox_-1166463993 ; 19 FEB 03 12:41:43
UT
> Received: from RELAY.IT.NORTHWESTERN.EDU by mail.imc-nj.com
> with SMTP (QuickMail Pro Server for MacOS 1.1.2); 19-Feb-2003 >12:41:35
-0500
> Received: (from mailnull@localhost)
> by relay.it.northwestern.edu (8.12.3/8.12.3) id h1JHfZSD015525;
> Wed, 19 Feb 2003 11:41:35 -0600 (CST)
> Received: from collab-b8gzju.northwestern.edu (nil.it.northwestern.edu
>[129.105.237.36]) by relay.it.northwestern.edu via smap (V2.0)
> id xma014849; Wed, 19 Feb 03 11:41:22 -0600
> Message-Id: <email@hidden>
> X-Sender: email@hidden
> X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
> Date: Wed, 19 Feb 2003 11:40:05 -0600
> To: Reid Bundonis <email@hidden>, Bambi Nice
<email@hidden>,
> "webobjects-dev" <email@hidden>
> From: Jonathan Rochkind <email@hidden>
> Subject: RE: Cascading Style Sheets with WO
> In-Reply-To: <email@hidden>
> Mime-Version: 1.0
> Content-Type: text/plain; charset="us-ascii"; format=flowed
_______________________________________________
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.