Either figure out how to integrate effectively with EOModeler/
WOBuilder in Xcode, or rewrite it. I don't personally care about
WOBuilder, but EOModeler is essential and there will be a
workaround ... Windows people ultimately will have to have a rewrite
for things to continue to work properly in the future. It's possible
Cayenne Modeler might be the basis for this work, but I'm not very
happy with the workflow it has at the moment -- coming from EOModeler
it feels kind of clunky. I personally start on an EOModeler
replacement every month or so, but I'm interested to see what the
next version brings, and what level of integration it provides (if any).
Ok... must try Eclipse. I get that part. But you've said yourself
that you expect EOModeler and WOBuilder to eventually be rolled
into one giant Xcode-Borg thing. How do you plan to keep working
with Eclipse once that happens? That is, without so much pain
that the benefits are no longer so compelling?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
