Ok. Here's my little lesson.
I've got the following subdir layout.
/
/bin # compiled classes from eclipse.
/src
/src/Components # .wo's and their classes
/src/Java # Application classes
/src/Test # Junit test cases
/src/Resources # Models, properties files, blah.
/src/Images # You get the idea.
/release # destdir - where the .woa goes.
/PB.project
/Makefile*
/.classpath
/.project
/.cvsignore
Ok. Now here's the cool thing. The WOB needs PB.project to exist in
the ../ of a given .wo. So if my components are all in /src/Components,
then it needs a PB.project in /src/Components. However it doesn't need
the whole thing. It only needs the following:
{FILESTABLE = {CLASSES = (Test.java, Main.java); }; PROJECTVERSION = "";
}
To exist within the /src/Components. It's all standard NeXT .plist
format, and CLASSES is the only plist that actually needs to be cared
about. So if we could specify a WOProjects and a WOLips variable
${components.dir} or something, and re-build a reduced PB.project within
it when classes were added or removed from that folder, we could make it
so that you could have a cleaner project structure and still use WOB and
(I believe) EOM.
The other possibility is to write a plugin to EOM and WOB to have them
try to find PB.project in a parent folder if it's possible.
Now this may be pretty specific to my intended use, which is to
eliminate the PB but still get full value from WOB and EOM. However, if
someone can figure out a way of making such an alternate structure work
in PB, that would be cool. Perhaps a new project type in PB could be
build to support such a structure.
Regards,
Christian.
P.S. The Components folder could be listed in a "Properties for
<project>" panel sub-view. -cg.
> -----Original Message-----
> From: Ulrich Köster [mailto:ul..ac.com]
> Sent: Tuesday, October 01, 2002 12:16 PM
> To: Christian Edward Gruber
> Cc: woproject-de..bjectstyle.org
> Subject: Re: Problems with wolips.
>
>
> ProjectBuilderWO updates the makefiles whenever you add or remove a
> file in ProjectBuilderWO.
> Try this in ProjectBuilderWO remove Main.api from the
> resources and add
> it again. You should now be able to build with ProjectBuilderWO.
>
> The biggest problem is that ProjectBuilderWO put new java classes in
> the main directory. Just make sure they are under Projectname.src and
> you are golden.
>
> WOLips 0.8.8 or higher?
>
> Am Dienstag, 01.10.02, um 17:52 Uhr (Europe/Berlin) schrieb Christian
> Edward Gruber:
>
> > Well, one problem solved. If I use ${basedir} as the source folder,
> > I'm
> > good with WOB using the .java files.
> >
> Where did you set this?
>
> > I could also put all my .wo components into a subdir for
> that purpose
> > and use the build.xml file to make it work.
> >
> > It seems to me then that I can use EOM/WOB with eclipse without
> > incident, or I can use PB, but not both effectively as a
> primary dev
> > tool. (Though with some makefile hacking, one could build from PB,
> > just not use conveniently with the UI for editing as you would in an
> > old-style environment.)
> >
> > Is the above true? Or am I further missing things.
> >
> > Regards,
> > Christian.
> >
> >> -----Original Message-----
> >> From: Christian Edward Gruber [mailto:cgrube..srafil.net]
> >> Sent: Tuesday, October 01, 2002 11:44 AM
> >> To: 'Ulrich Köster'; woproject-de..bjectstyle.org
> >> Subject: Problems with wolips.
> >>
> >>
> >> Hmm. I'm having problems with making WoLips work with eclipse and
> >> with PB/WOB.
> >>
> >> It seems to work fine, but it puts my .java classes into
> >> ${basedir}/src. Now I like that, but I can't figure out
> how to make
> >> PB and WOB work in that context. WOB can edit the .wo components,
> >> but can't use the source. And PB doesn't recognize the
> .java files
> >> and fails to put them in the Classes project view.
> >>
> >> Am I destined to choose WOLips OR PB, or am I missing something?
> >>
> >> Regards,
> >> Christian.
> >>
> >>
> >
>
>
This archive was generated by hypermail 2.0.0 : Tue Oct 01 2002 - 14:00:57 EDT