On 12/07/2008, at 3:07 PM, Mike Schrag wrote:
>> just recently updating to more recent eo generation - and was just
>> thinking
>> a) within Eclipse does the config really need to be told about
>> related models? e.g., Entity Modeler picks this up automatically.
> No (well, no for the typical case) and you don't have to anymore ...
> There's a checkbox to just use the same process that is used for
> default model loading.
Ah, okay. I was wondering what it did.
>> b) is it possible for destination/subclass destination paths to
>> default to that defined for the project (if blank)
> It defaults to your source folder automatically when you create the
> eogen file. As most people don't ever change that location, you
> should never have to touch this.
Okay. Seemed to default to WebServerResources for me upon creation.
But I was more thinking of it dynamically being tied to the source
folder (however that's defined at the time). But these are only
passing observations...
>> Then perhaps Templates, Options and Defines could be promoted(?)
> I suppose? They're all equally untouched for me. I use
> WonderEntity.java and _WonderEntity.java in my top level prefs, so I
> don't set anything in eogen.
Sure. Thanks.
with regards,
--Lachlan Deck
This archive was generated by hypermail 2.0.0 : Sat Jul 12 2008 - 01:34:30 EDT