On 6-Jul-07, at 16:33 , Andrew Lindesay wrote:
Hello Janine;
The only feature of WOBuilder that I consider important is the one
that helps you to visualize what your component will look like when
it's rendered. WOBuilder always did a lousy job of this, especially
It's interesting; we all have quite different ways of working with
components which probably illustrates different ways of thinking.
I really do like Mike's component editor, but to augment it, I
would also enjoy the visual modeller in WOB. I really do not feel
at all like I need a full render of the page with data or anything
-- what WOB does is perfect for my use. It's really a logical view
for making bindings. I'd love to have the time for such an
undertaking. :-/
You expressed exactly what I was trying to say. Indeed, I believe
that the graphical presentation must not aim at the aesthetics of the
page/component but rather it's structure along with a decent
inspector for the available bindings. The aesthetics of the
presentation should be done through CSS and could be handed off to
other tools like CSSEdit and the like.
In a sense, couldn't it be structured like the eomodeler in eclipse ?
A tree showing the structure and some inspector specific to the
webobject tags being edited ?
_______________________________________________
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]
