One thing I forgot to mention: using _sub-projects_ instead of
sub-directories is also much more likely to work without hassles. A
sub-project is a WOLips thing, not an Eclipse thing and is taken from
the days of ProjectBuilder. You might prefer to use sub-projects to
organize your larger projects.
On Nov 8, 2004, at 4:28 PM, Chuck Hill wrote:
> Hi Guido,
>
> You have to think about project organization differently under
> Eclipse. Rather than using "grouping so I don't have to look at it",
> Eclipse uses "filter this out so I don't have to look at it". :-)
>
> There are two areas to look at in this. Both are accessed via the
> drop down black arrow in the upper right of the Navigator and Package
> explorer panes.
>
> One is the Working Set. This controls which projects are visible in
> these panes. Even if a project is not visible, it will still be part
> of the build. You can have as many Working Sets as you need and
> switch between them for a view appropriate to the task at hand.
>
> The other thing to look at is Filters. This allows you to show or
> hide specific files. Don't want to see the API files? Swish. They
> are gone. Don't want to be distracted by property files and plist
> files? Flick them away.
>
> Between the two of these you can setup a fairly focused perspective.
>
> As for the prototypes, I'dd guess that either the Folder is getting
> replicated into the build product, or something in the PB.project file
> was not updated properly.
>
> Chuck
>
>
> On Nov 8, 2004, at 1:50 PM, Guido Neitzer wrote:
>
>> Chuck Hill wrote:
>>
>>> Where are the prototypes? I'm not clear: the model is in a framework
>>> which is in a subdirectory of the application?
>>
>> I have a few projects in Eclipse (all in the starting phase - I'm not
>> yet
>> sure whether I will use Eclipse).
>>
>> One is a framework only with the EOPrototypes, another a framework
>> with a
>> lot of convenience stuff, and then some related things: project one
>> (not
>> only an Eclipse project, its a company wide project), which will be
>> in the
>> end 4 or 5 applications and a few frameworks, and project two (also
>> not
>> only an Eclipse project) with the same amount of Eclipse projects.
>>
>> Currently I'm not sure how to organize all that. I miss the "groups"
>> from
>> Xcode, where I can arrange stuff logically without drawbacks with
>> EOModeler or WOBuilder.
>>
>> Currently the projects are organized in this way:
>>
>> Eclipse-Workspace
>> EOPrototypes
>> ConvenienceFramework
>> EOFrameworkProjOne
>> AppOneProjOne
>> AppTwoProOne
>> ...
>>
>> And so on. I'm trying to get some things out of my way so I'm
>> packaging
>> java classes, try to move components, try to move EOModels.
>>
>> The prototypes model is in the root of the EOPrototypesFramework, the
>> other models are in the root folders of other projects. When I move
>> them
>> to a folder, the prototypes in EOModeler are gone, but the application
>> works (as long as I have seen it - I'm at home now, the whole stuff
>> is on
>> my Mac in the office).
>>
>> All this stuff seems pretty complicated to me in Eclipse. I'm
>> absolutely
>> not happy with it. On the other side I love Eclipse for its
>> performance
>> with Java code (code completion, hints, ...).
>>
>> cug
>>
>>
> --
> Practical WebObjects - a book for intermediate WebObjects developers
> who want to increase their overall knowledge of WebObjects, or those
> who are trying to solve specific application development problems.
> http://www.global-village.net/products/practical_webobjects
>
>
>
>
-- Practical WebObjects - a book for intermediate WebObjects developers who want to increase their overall knowledge of WebObjects, or those who are trying to solve specific application development problems. http://www.global-village.net/products/practical_webobjects
This archive was generated by hypermail 2.0.0 : Mon Nov 08 2004 - 19:32:49 EST