This is a tricky problem that we recently figured out.
The key is to not flatten the resources when creating your framework or
application. To do this you will need to set up your build.xml and
PB.project files to handle the subdirectory.
For example, in our build.xml, we have a section that looks like this:
build.xml
---------
...
<woapplication name= ...>
...
<resources dir=".">
<include name="resources/"/>
...
</resources>
...
this will create the app file tree appname.woa/Contents/Resources/resources
which is your un-flattened subdirectory
next, you will need to manually describe each item in the resources folder
in WOAPP_RESOURCES. For example:
PB.project
----------
...
WOAPP_RESOURCES =
(
Properties,
resources/foo.css,
resources/bar.xml,
...
which allows the resources to be located at runtime.
hope this helps!
> -----Original Message-----
> From: Frédéric Dreier [mailto:frederic.dreie..ptime.ch]
> Sent: Monday, August 18, 2003 7:12 AM
> To: Woproject
> Subject: resources
>
>
> Hi,
>
> I have a question about resources : I used to put them in a 'resources'
> folder in a hierarchical structure (subfolders for each
> components). Now, it
> seems that WOLisp copy them in a flat fashion; giving warnings
> since I have
> several 'stylesheet.css' files in resources.
>
> Have anybody some advices about this issue? Some input about a
> best practice
> ?
>
> Thanks,
>
>
> Frédéric
>
>
This archive was generated by hypermail 2.0.0 : Mon Aug 18 2003 - 11:38:03 EDT