An important take-away from Daryl's comments is that EOModeler,
Xcode, WOBuilder, etc aren't going anywhere soon. The road map is in
place that Eclipse/Entity Modeler/etc will eventually replace them
for WO development, but you can use them for a while to come. WO
doesn't have a history of changing quickly .... a blessing and a
curse.
ms
I like the "etc" in the "Eclipse/EntityModeler/etc" bundle!
I must admit that I am not able to write html directly in
WOComponentEditor... And I can no longer stand WOBuilder crashing on
me all the time.
I don't know how many people use WebObjects these days, but many of
them might be willing to pay for a "Eclipse/EntityModeler/
WOBuilderReplacement" bundle.
Mike, given that you have been so successful with EntityModeler, you
have done half of the work!
May be this is a stupid idea, but I am sure that a good, integrated
WO development environment would appeal to many of us, and that we
would pay 100 € each year or two (upgrades) for it without problem
(I say 100$ because many commercial eclipse plugins are about that
price, but it could be less, or more).
You would have no competitors on this product, given that Apple tools
are deprecated... And it would be good for WebObjects in the long run.
I realize that EntityModeler has not been created as a commercial
product in the first place, and that a WOBuilder replacement might be
more difficult to develop, but, Mike, did you ever think of creating
a commercial bundle of WO tools?
JPM
_______________________________________________
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]
