Hi Ian,
normally a classpath entry is a classpath entry. WO is different :-).
An entry with a .framework in the path is a WOFramework bundle.
The WOResourceManager is able to load resources from the project if a
PB.project (XCode........) is found on the NSProjectSearchPath.
Changing the PB.project has no effect to the classpath.
The usual way in Eclipse to maintain the classpath is via the
JavaBuildPath pages. It would be great if we were able select the
required projects and WOLips take care about the rest. We had no idea
to do this at the early days of WOLips. That's the reason why you have
to inlcude the project and the product in the Eclipse classpath.
We're working on it.
So what's allready there. :-) Please try the following:
Create a WOApplication and WOFramework with WOLips 1.0.7.40. Open the
'Java Build Path' for the WOApplication and select the WOFramework in
the 'Projects' tab. Add a WOComponent to the WOFramework with a "Hello"
in the body. Create a WOHyperlink in the Main WOComponent to display
the WOComponent from the WOFramework. Refresh both Projects. Launch
the WOApplication within Eclipse. Everything should work as expected.
Terminate the WOApplication. Switch to IncrementalBuilder and launch
the WOApplication again........
WOLips includes the WOFramework from your project automatically in the
classpath. There some rules for it. You have to build your WOFramework
in the project in the default location (project root or dist for ant
and project root or build for incremental), the WOFramework must be
visible for Eclipse (refresh) and the WOFramwork must be referenced by
the WOApplication.
One thing is missing. The Classpath.txt. Your WOFramework is not
included. We're working on it.
Ulrich
Am 03.12.2003 um 01:24 schrieb Ian McDougall:
> This is one for the WOLips developers:
>
> How do I go about using the Incremental Builder with a Framework
> project and
> an Application project?
>
> I understand how the PB.project file is used. The framework name is
> listed
> and at runtime the framework paths are searched for a framework with
> the
> name listed and all resources and .jar files are loaded.
>
> How does the Incremental Builder duplicate this behaviour? Perhaps
> more
> generally, how does WOLips deal with Frameworks at runtime? How
> should we
> build frameworks? Deploy them to NEXT_ROOT/Local/Library/Frameworks
> or keep
> them in the project directory and refence them by path? Or does the
> incremental builder do this for us? Do we need to modify the
> PB.project
> file so WOBuilder will work?
>
> I've been using WOLips for over a year now and this is still one area
> where
> I'm fuzzy. I've been building all frameworks to the
> Local/Library/Frameworks folder and doing a full ant build everytime a
> change is made (very slow). Some apps reference 3 frameworks and a
> full
> rebuild takes a few minutes whenever a single file is changed.
> Incremental
> builder looks promising, but I have no idea how it works!
>
> Thanks.
>
> _ _
> Ian
>
This archive was generated by hypermail 2.0.0 : Wed Dec 03 2003 - 03:38:14 EST