• 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: Thomas <email@hidden>
  • Date: Sat, 7 Jul 2007 18:50:28 +1000

To expand on what Janine said, I am a visual person, not a textual person. The three things that I use all the time in WOBuilder are:

- [most important] the ability to visualise how the components in the page are organised (NOT how it will be rendered), eg are all form elements in the form.

- ability to visually navigate the business logic. Typing auto- completion doesn't help me (although WOBuilder does that) because in my system with thousands of classes, I could never remember what the methods are called, not even the first letter.

- ability to drag a business method/action from the above onto a component binding.

I will greatly miss WOBuilder when it is gone, unless there is something that does these three things. And yes, I am willing to pay up to US$500 for such a tool. However, it doesn't need to be a standalone application. I love CSSEdit, and it would be cool to have WO support built in, but they have almost nothing in common (I don't care what the page will look like, I just run the application to see that).

At the moment I use Golive for some display-oriented editing-- you can set up the HTML database to recognise tags like <wo:if condition="$whatever"> and you can see the structure of the page, expanding and collapsing blocks. You can even have predefined attributes (eg every wo:if has a condition) but there is no business browser or binding dropper. So a Golive plugin would work for me. I haven't found a way to do this in Dreamweaver.

On 07/07/2007, at 4:26, 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. 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.

_______________________________________________ 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: Mike Schrag <email@hidden>
References: 
 >Re: WOBuilder Replacement (From: Andrew Lindesay <email@hidden>)
 >Re: WOBuilder Replacement (From: Louis Demers <email@hidden>)

  • Prev by Date: Re: WOLips Survey
  • Next by Date: Re: WOBuilder Replacement
  • Previous by thread: Re: WOBuilder Replacement - Another idea
  • Next by thread: Re: WOBuilder Replacement
  • Index(es):
    • Date
    • Thread