Re: Community Wish List
Re: Community Wish List
- Subject: Re: Community Wish List
- From: "Jerry W. Walker" <email@hidden>
- Date: Wed, 6 Sep 2006 19:02:08 -0400
On Sep 6, 2006, at 6:41 PM, Thomas wrote:
I'd be happy to contribute the fee previously discussed, and
contribute my time for design discussions and testing of the
WOBuilder replacement.
But we do NOT need a WYSIWYG WOBuilder replacement.
We need an editor that, like WOBuilder, displays the organisation
of the component, not the way it will be rendered in a browser.
It's fine by me if someone wants to go down the path of developing
a separate tool that previews what a component looks like in a
browser, CSS and all, but in my opinion that is a waste of time
because the rendered result would be so heavily dependent on the
data and functionality of the WO application. The only real way to
preview a component is to run the WO app and look at it in a browser.
Agreed.
I never really understood the hype surrounding WOBuilder's Preview
view and have only used it a few times with disappointing results.
The WOBuilder replacement should, however, have a Source and Layout
view and allow the same (or better) ease of switching back and forth
between the two views with selections of components from either view
carrying into the other view. In a complicated HTML hierarchy, I've
found this capability among the most helpful of services that
WOBuilder offers.
I also think WOBuilder's object browser is valuable. The ability to
see the keys of the WOComponent Java class file (and the Session and
Application class files) and be able to visually link them to the
subcomponent and element bindings is great both as a teaching tool
and as a page composition tool.
Although a WO development plugin for a commercial Web editor would
be nice, I too don't want to buy and learn DreamWeaver. I use Golive.
However, we could focus on a much lower target in addition to the
WOBuilder replacement: plugins for both DreamWeaver and Golive
(or .wo -> HTML -> .wo conversion tools) that allow web designers
to edit a WO component without destroying the WO tags. I believe
the WO developer tasks and the WYSIWYG appearance tasks are
completely separate activities, often done by different people, and
with entirely different requirements.
+1
--
__ Jerry W. Walker,
WebObjects Developer/Instructor for High Performance Industrial
Strength Internet Enabled Systems
email@hidden
203 278-4085 office
_______________________________________________
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