> Any plans to include a set of WO libraries with the stand-alone
> version?
Not at the moment ... You have to point Entity Modeler to your WO
classes on your own (I wrote about this somewhere). This whole
embedding-of-WO-framework is a great heated debate on the WOLips side,
let alone for Entity Modeler standalone.
> Also I think it is missing a button to trigger Java file generation.
... soooorrt of. Entity Modeler doesn't do Java generation,
EOGenerator does. So there is no button to generate Java because
that's not EM's job in the new world. Now in WOLips, this happens
automagically for you -- WOLips watches for changes in your model and
automatically runs eogenerator. Outside of WOLips, you're sort of on
your own here. I haven't really thought about embedding
VelocityEOGenerator into Entity Modeler (veleogen didn't exist when
entity modeler was created), but that might be a possibility -- this
is generally a little tricky, because outside of a full Eclipse/WOLips
you're missing all kinds of metadata (like ... where is your
project ... where is your source folder ... etc) that often makes
using more of WOLips hard.
> I assume the stand-alone version is for those not using eclipse.
> What do they use in place of WOBuilder?
I can only assume they beat together rocks and pound on dirt. I can't
even imagine.
ms
This archive was generated by hypermail 2.0.0 : Fri Jan 18 2008 - 12:16:43 EST