On Jun 20, 2011, at 10:46 AM, Catherine Seppanen wrote:
>
> Yep, I work at Cicada Consulting Group in Raleigh. We're a fairly small shop
> as I am the entire WebObjects development team. :) If anyone on the list
> remembers Mark McCraw, I took over from him a few years ago (has it been that
> l
On Jun 19, 2011, at 12:06 PM, Ramsey Gurley wrote:
> It uses WOContext _urlForResourceNamed which calls WOResourceManager
> urlForResourceNamed(). If you are using Wonder, ERXResourceManager is used
> which provides a fix for using paths relative to your resource. (Wonder
> makes a '?' into
It uses WOContext _urlForResourceNamed which calls WOResourceManager
urlForResourceNamed(). If you are using Wonder, ERXResourceManager is used
which provides a fix for using paths relative to your resource. (Wonder makes
a '?' into a '/' I believe).
So if the script and the image are in th
You can also just put resources into the webserver doc root and using plain img
tags and absolute paths if you like.
On Jun 18, 2011, at 3:37 PM, Catherine Seppanen wrote:
> Executive summary:
>
> How does a WOImage element like this:
>
>
>
> get translated to this HTML:
>
> src="/WebObje
