Hi Clark,
Thank you for a reasoned response in what has become a rather feisty
thread!
On Jul 5, 2007, at 9:57 PM, Clark Mueller wrote:
I was one of those who raised his hand - but honestly, I no longer
feel the same way, so it's even fewer than those few. Having
digested some of this discussion going on for the past several
days, I've arrived at the conclusion that, as many people have
indicated, the current WOComponent editor helps me be more
productive than I ever was with WOBuilder. The pros for me that
make WOBuilder irrelevant are things such as:
* Autocompletion is fantastic. This is already a deeply ingrained
part of my regular WOLips development workflow (I've only even been
using WOLips for about nine months), so it extends easily for me to
the WOD editor. Once I have a good grasp of the layout of the data
I am modeling in a component, it's much faster than digging through
the list of bindings in WOBuilder to figure out what I want to
connect.
* The latest, absolutely kick-ass round of refactoring features
have made it so much easier to deal with my old, WOBuilder-built
components that I might have ordinarily been tempted to open
WOBuilder for. In a single click, I can convert all the ugly
WOBuilder generated names to something much more meaningful, and
the end result is that I don't have to go spelunking in my own code
to figure out what's going on. I haven't opened WOBuilder at all
since this surfaced, and even before then, it was an infrequent event.
* Since I've been using WOLips, my component code ends up looking
MUCH cleaner, simply because I have to look at and edit it all the
time. That also makes me come off better to the people who actually
like to admire others' HTML. Almost the only thing that is a bit of
a headache for me is building tabular data views and whipping up
the initial layout of forms. I often mock up the code for these
with Dreamweaver and copy/paste, so I wouldn't mind seeing some
alternative function in WOLips to accelerate that common task, but
that's certainly not something I can't live without, either.
That strikes me as an excellent suggestion! I do most forms with
divs now, but it is still the same painful process getting the
scaffolding laid out. Something to kickstart this might be quite
useful and may not take too long to make. Think on how this might
work and file a suggestion here: http://issues.objectstyle.org/jira/
secure/Dashboard.jspa
In the meantime, have a look at AjaxGrid in Wonder's Ajax framework.
It is driven from a plist file (for which I may write a nice editor
one of these days) and makes tabular data views quick and easy to
create.
Chuck
* The WOD editor doesn't exhibit all of the bugs that WOBuilder does.
So at the end of the day, would I pay "real money" for a graphical
tool that does all this, except with eye candy? Possibly - I'd even
go as far as to say "probably". But it also definitely doesn't fit
into the category of a must-have.
Clark
On 5 Jul 07, at 6:30 AM, Mike Schrag wrote:
I asked at WWDC who would pay "real money" (granted, an
unspecified amount) for a WOBuilder and VERY few hands went up in
a pretty large room of WO developers.
_______________________________________________
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/chill%
40global-village.net
This email sent to [EMAIL PROTECTED]
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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 [EMAIL PROTECTED]
