• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: WOBuilder Replacement
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WOBuilder Replacement


  • Subject: Re: WOBuilder Replacement
  • From: Janine Sisk <email@hidden>
  • Date: Fri, 6 Jul 2007 11:26:23 -0700

On Jul 6, 2007, at 9:26 AM, Chuck Hill wrote:

Two: when new developers start poking at WO the complaint I hear is "The docs are unclear and incomplete", not "What?!!? No WYWISYG HTML editor?". It is a nice to have feature, not a critical one, in attracting new developers. The critical thing seems to be in having good tutorials and clear beginner docs. I certainly see progress being made this year in those areas.

WOBuilder is really one name for several different features. There's the WYSIWYG editor, the drag-n-drop bindings, the ability to edit the source, and probably more I'm forgetting now.


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 without real data, but some things were just easier to see, like whether your form really enclosed all the things it was supposed to. I happen to think that this one piece is something that some people will find useful regardless of how experienced they are; some people are just better at visualizing from words than others.

Personally this is the only piece I think we need. I have no idea if this could be built as a plug-in to Eclipse or some other existing package (maybe Coda, like someone else said) or if it would have to be a standalone app. It wouldn't even have to be an editor; a viewer where you could preview what your WOLips-produced component would look like would satisfy me. The icing on the cake would be if it would allow entry of dummy data for display purposes, but that would probably require reinventing too much of WO to be practical.

Maybe I'm the only one who feels this way, but I do think this approach would be simpler than making a full WOBuilder clone. It would be interesting to find out which WOBuilder features people actually want; maybe Pascal's survey can capture that.

janine

_______________________________________________
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


  • Follow-Ups:
    • Re: WOBuilder Replacement
      • From: Kieran Kelleher <email@hidden>
References: 
 >Re: WOBuilder Replacement (From: Jeremy Rosenberg <email@hidden>)
 >Re: WOBuilder Replacement (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: Unable to create page 'IIxrY0tStknjYQDhjDa6s0'
  • Next by Date: Re: WOBuilder Replacement
  • Previous by thread: Re: WOBuilder Replacement
  • Next by thread: Re: WOBuilder Replacement
  • Index(es):
    • Date
    • Thread