I wish to support the sentiment of this email and
make some observations:
1 many people think visually and
WOBuilder enables them to express themselves quickly to frame their work -
either for prototyping, demonstrations or otherwise. Furthermore, for
an old person like me, the visual cues are a replacement for poor memory!
Whether a WO replacement is devised in the form of a Dreamweaver adjunct or
smart tags or something else, it is essential that a WOBuilder replacement is
planned.
2 one of the powers of WO is the
range of tooling, that applies at all enterprise levels. This range lets
people work in their own way - we are not all the same (but we are all
supporters of WO) and some are less gifted than others.
3 many on this mailgroup are
clearly very bright, very supportive of others and very generous
in contributing their time and efforts for the rest of us - we all know who
they are! Thank you all, this is another power of WebObjects, Apple
gave the start, the passion comes from the group, long may it
continue!
For the record, I moved to WebObjects 5 some 4
years ago after directing two large J2EE projects and feeling the pain they
cause. I think WebObjects can benefit from an environment that better
supports Java, as long as it continues to add the immense value inherent in its
pedigree.
Clive
----- Original Message -----
Sent: Sunday, August 13, 2006 4:08
AM
Subject: WOBuilder Value
I've been working on WebObjects for about two years and apprenticed
closely with developers who had been on board since the Objective-C
days. The problem with losing the tools is that it takes WebObjects one
step down and therefore closer to competing technologies. I've always
felt that the clear, graphical way WOBuilder helps me quickly design my
application interface has given it a big boost in my mindshare. If I am
going to be editing HTML code then I am going to look at JSP2.0 and SpringMVC
and like technologies to see what it has to offer that WebObjects
doesn't. I still think WO is the gold standard for developing Web
applications but they've slid back towards the pack a little bit this week and
that pack keeps improving. Right now we have the most dedicated and
talents members of the WO community throwing out everything from fabulous
suggestions to irate diatribes. But who is going to take the lead
here? We all have jobs to do, I work at a University and I would love to
be able to throw the resources of the school behind an open source WOB but we
are already several FTEs short and I can't imagine finding the time and
resources to even help out.
These are the things that concern me and I assume much of the developer
community. The direction of this technology seems to be swinging between
unpredictable and doomed. I'm going to be an optimist and say that the
unpredictable will turn into positive growth and that the people in this
community won't let such a truly fantastic technology die. But I will
feel a lot better when I see the road map that Apple has refused to provide
come from somewhere else.
Jeremy
For WebObjects to move forward without WOBuilder, we need a
visually-
oriented tool that does the three things I described above. I am sure
that some people don't need it, but many people do. To say that only
newbies and klutzes use WOBuilder is an insult to many experienced
developers, and I believe it shows a focus on the narrow coding
issues rather than the overall
productivity.
_______________________________________________
Do not post admin
requests to the list. They will be ignored.
Webobjects-dev mailing
list
(email@hidden)
Help/Unsubscribe/Update your
email sent to email@hidden