I keep hearing the phrase's "once I converted my projects" and "once
I got use to Eclipse/WOLips." That's a really big problem for a lot
of us who REALLY DON'T HAVE THE TIME!
We don't have the month or more to figure out and acclimate ourselves
to Eclipse/WOLips and painstakingly convert all of our projects and
frameworks (which I'm still fighting with). Combine this with the
fact that now I'll be editing my HTML and WOD files by hand and we're
talking a serious loss of productivity. (and time... and money...)
On Jan 21, 2007, at 9:43 PM, Lachlan Deck wrote:
Deprecated == dying (aren't we all). But deprecated != dead. i.e.,
you can still use it happily today ... and even tomorrow. So if you
really like it and find that it suits your needs 'at this time'
then continue to use it.
Yea, well, I remember being forced to upgrade from 5.1 to 5.2 just so
I could install OS X 10.3 (because of an incompatibility between
WOBuilder 5.1 and OS X 10.3 you couldn't use the delete key). This
also meant upgrading all of my projects and deployment servers (a
VERY time consuming task). So we know how this story goes.
Chances are, we can stick with WOBuilder and EOModeler as long as we
don't want to upgrade to Leopard and/or xCode 3. In fact I wouldn't
be surprised if xcode 2 won't work on Leopard so that if you want to
upgrade to Leopard that you'll have to kiss WOBuilder and EOModeler
goodbye.
Then, Lachlan Deck wrote:
Earlier on 22/01/2007, Georg Tuparev replied:
I too have mixed feelings about WOBuilder. With all its bugs, it
is still faster to bind a WOString to
Session.observatory.controlRoom.telescope.positioningInstruments.curr
entPointingModel.declination using WOBuilder then type it.... And
it is less error prone...
WOLips/Eclipse offers auto-completion + Compile-time checking of
keypaths (as mentioned above). So the charge of being more error-
prone is actually not the case at all. It is actually far less
error-prone because the IDE continually shows you up-to-date
information on the validity of not only your java files but the
components and model-files as well.
While I agree that compile time checking of keypaths is nice it does
not equate to faster development. The purpose of WYSIWYG is to
eliminate typing as much as possible. And as I said before, even
though WOBuilder had MANY faults we are still heading backwards.
And while WOLips development is proceeding (I hope) it may be quite a
while before we get the drag-n-drop abilities back (if ever). My
biggest fear is that WOLips will reach that magical, OpenSource
prone, "good enough" stage and then development with become stagnate
as the developers lose interest in it.
Also, even though many people might not use a feature of EOModeler or
WOBuilder, many other people still do and they are desperate to find
an alternative before Apple does kill it off.
--
Galen Rhodes
[EMAIL PROTECTED]
"There is no worse tyranny than to force a man to pay for what he
does not want merely because you think it would be good for him."
-- Robert Heinlein --
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to archive@mail-archive.com
