With the differences in browsers and the ready availability of
multiple browsers along with a plethora of tools for analyzing and
inspecting html, page structure, javascript, css, dom, etc., etc.
(especially the tools in FireFox such as the awesome FireBug), having
visual rendering in yet another tool might be quite redundant,
especially since we have hot code replace and a refresh button on the
browser. The browser is in another window in the OS ..... does it
matter that that "rendering window" is not a part of the IDE we are
using? The majority of the internet users are split 3 ways now ....
FireFox, IE6 and IE7. So develop in one of these (I prefer FireFox
due to its abundance of developer plugins) and test in the other 2
undesirable browsers (in 2 Parallels instances if you have a Mac). If
you can arrange two monitors on your dev machine, or a big monitor on
your dev laptop, just put FireFox on the small screen and Eclipse on
the big one and workflow is very efficient.
Besides graphical HTML editors really produce garbage, so you will
produce better stuff with tools that make working with the raw html
and wod efficient that some visual editor that hides the details that
you really need to see to figure out how the thing is working.
So all in all, the only really cool thing in WOBuilder that I liked,
IMHO, was the drag-connect binding feature. But I don;t miss it now
that I have autocomplete, etc in WOLips.
On Jul 6, 2007, at 2:26 PM, Janine Sisk wrote:
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.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
