• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Reusable components
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Reusable components


  • Subject: Re: Reusable components
  • From: Jean-François Veillette <email@hidden>
  • Date: Sat, 23 Oct 2004 08:06:22 -0400

I agree with Chuck, nothing good will come out of embedding your images, etc inside a framework or app.

I disagree on this. From my stading point, it simplify deployement trouble if the project is self contained and all you have to do is buid/run, and not care about out of project resources.
I'm in a situation where :
- we have a graphic departement,
- we build multiple sites, for multiple clients, using virtual hosts directives on few (not as multiple) apache web server.
- we use different server (webserver, app server) for test, staging, production deployement)
- a framework can be shared across multiple deployment sites (maybe on the same wo server, or maybe the same apache webserver, but maybe a different virtual host)
- projects are mostly one man job, frameworks are shared across developer
- different developer can work on a different project at different time.
- we have wrap our mind around the fact that projects are entirely self contained, doesn't need external build/deployement procedure over the usual buid/run.


If you go with hard-coded url, you will need a different buid/deployment procedure than the bare minimum that we use. I haven't really tried, but it seem that I would need extra procedure over the simple split-install procedure we do right now. Maybe it can be added to the xcode build scripts (new build phase), so it won't be extra work ?

Give both a try, keep the one that fit your development / deployment situation best.
I guess the question could be : Do you want woresouremanager to manage resources, or do you want the developers to manage resources ?


Another benefit of not doing that is your web server does the image serving not your WO app. Helps scalability tremendously!!

Well, yes and no.
Yes because : the url has to be build by the wo application (woresourcemanager), thus it has an impact on the wo app (but minime, woresourcemanager cache all of this, I think).
No because : once deployed the woimage are served by the web server and not the wo application.


To make this work you can't use DirectConnect (I think, maybe there is a way). This is also, IMHO, a good thing as you develop as you deploy.

but you can use :
http://localhost/cgi-bin/WebObjects/MyApp.woa/-9999/...
(where 9999 is the port number of your app) that kind of give you an in between of direct connect and full webserver deployment.


- jfv


On 10/22/04 2:57 PM, "Chuck Hill" <email@hidden> wrote:

Many will argue with me.  Let them rant, I say.  :-P

Do not include these shared resources in your project. Keep them in the web server's doc root where you, your app, and (here is the important part!) the graphics guys can all access them. When they update the images, there is no need for you to update your project. They can design new pages without getting the images from your project, nothing gets out of synch.

Then in your image tags, use relative URLs that start with '/', e.g.
<img src="/images/navigation/navbar.gif">

To make this work you can't use DirectConnect (I think, maybe there is a way). This is also, IMHO, a good thing as you develop as you deploy.


Anyway, that is my two cents on the subject.

Chuck


On Oct 21, 2004, at 6:41 PM, Darich Runyan/OMNI INFOSEC LTD HQ wrote:

All,

Just recently finished up my first production WO web app. I took the
easy
route and focused only on the logic, didn't mess with any of that
stinking
graphics stuff. ;^) Now that the app has completed testing and is
deployed
the client wants me to work with the graphics design group to pretty
it up.
The layout that the graphics guys have come up with have a lot of
sections
that are juicy for reusable components so I started to look into how to
create one today. I created a new framework and build the reusable
component within the framework. I also included all of the images
that the
component needed within the framework. I then added this new
framework to
my test application and it worked fine except it did not show the
image that
I was looking for, it output the following error within the HTML
output:


<img
src="/cgi-bin/WebObjects/Authors.woa/wr?
wodata=ERROR_NOT_FOUND_framework_*nu
ll*_filename_navbar.gif">

Do I need to capture the resource somehow in order to display it?

Thanks,
Darich


_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: village.net

This email sent to email@hidden




_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden


This email sent to email@hidden


_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: Reusable components
      • From: John Gilmore-Baldwin <email@hidden>
References: 
 >Re: Reusable components (From: Dov Rosenberg <email@hidden>)

  • Prev by Date: Re: Hashtable to WOString?
  • Next by Date: Re: [NEWBIE] Need some help getting started with a local dev environment
  • Previous by thread: Re: Reusable components
  • Next by thread: Re: Reusable components
  • Index(es):
    • Date
    • Thread