Re: Maybe No Need for a WOBuilder Replacement?
Re: Maybe No Need for a WOBuilder Replacement?
- Subject: Re: Maybe No Need for a WOBuilder Replacement?
- From: Galen Rhodes <email@hidden>
- Date: Tue, 4 Sep 2007 17:14:19 -0400
That's the problem! It IS all about personal preference. No two
people write code the same way. Just as people are individuals in
their preference for color, clothes, music, whatever, people have
preferences for how they write code! A good number of us became very
use to working with WOBuilder and, yes, even got use to it's many
quirks. What's faster for one person may very well be slower for
others simply because we're use to working in a different way. For
some of us who were use to WOBuilder, having to use Eclipse is like
going from JEdit back to using VI. And telling us to try changing
the paradigm even more by switching to inline bindings is cold
comfort. You may as well be telling a lifelong vegetarian to just
shut up and try the veal.
--
Galen Rhodes
email@hidden
On Sep 4, 2007, at 4:42 PM, Mike Schrag wrote:
- the ability to see, in a graphical way, what components are
contained in other components, what they are, and (for simple
things like conditionals), what their main binding is. Using
WOBuilder with a complex component I can see what I need in less
than a second, while it sometimes takes minutes in Eclipse to do
the same thing. Although viewing tables is much easier this way,
that's not the important thing. I don't need to see how the page
will look-- I want to see the component hierarchy in a graphical way.
Just personal preference on this one ... I find the exact
opposite. We don't do almost any table layout, and opening a
complex css-laid-out component in WOBuilder appears to me to be
unintelligible. Component editor in Eclipse shows both an outline
view of your components as well as the collapsible HTML editor with
rollovers that show the span of each tag. But this has been
debated to death, so I'm leaving this at "personal preference."
- the ability to cut or copy a whole group of elements and paste
them somewhere else, bindings and all.
This could definitely be added into component editor ... I can
pretty easily, I think, track the associated wod bindings when you
cut HTML and autocut/copy related wod entries.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40thissmallworld.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden