Re: Including Pre-existing Assets (was Re: Basic Question)
Re: Including Pre-existing Assets (was Re: Basic Question)
- Subject: Re: Including Pre-existing Assets (was Re: Basic Question)
- From: Paul Lynch <email@hidden>
- Date: Wed, 22 Mar 2006 23:43:26 +0000
On 22 Mar 2006, at 23:23, Jeffrey Pearson wrote:
I learn best running through samples that apply what was said:
Case 1: If I have a static image (ie a company logo) that is shared
across multiple applications, my best bet is to simply refer to an
existing storage location such as a company web site and use the
HTML img tag.
You can do it this way, and it probably is the best approach.
Case 2: If I have a static image (ie an Application Specific Logo),
I can a) store it in a web server location, use an HTML img tag and
refer to it if I want the web server (ie Apache HTTP Server) to
serve it
Yes, you can.
or b) add it to the project in the application server target and
use the WOImage tag if I want the app server (ie Webobjects or
Tomcat) to serve it up (understanding a slight performance penalty
is applied).
No. You can add it to the Web Server target only; its location will
be resolved by the WOResourceManager/WORequestHandler, and served by
the web server.
Case 3: If I have an image that changes dynamically, add images to
the project as in b above and use the WOImage tag.
Web Server target, and use a WOImage with filename binding set to a
key in your component.
Can I use a WOImage tag and refer to a static location(ie http://
www.someserver.com/images/someimage.jpg) and then modify the url(ie
http://www.someserver.com/images/someimage2.jpg) through my code?
Yes, works fine.
WOImage supports bindings of filename, src and data, each of which
can be bound to keys (instance variables or methods) in your components.
Paul
_______________________________________________
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