• 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: Maybe No Need for a WOBuilder Replacement?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Maybe No Need for a WOBuilder Replacement?


  • Subject: Re: Maybe No Need for a WOBuilder Replacement?
  • From: Thomas <email@hidden>
  • Date: Fri, 7 Sep 2007 19:11:32 +1000

On 05/09/2007, at 6:42, Mike Schrag wrote:

- the ability to see, in a graphical way, what components are contained in other components, what they are, and (for simple things like conditionals), what their main binding is. Using WOBuilder with a complex component I can see what I need in less than a second, while it sometimes takes minutes in Eclipse to do the same thing. Although viewing tables is much easier this way, that's not the important thing. I don't need to see how the page will look-- I want to see the component hierarchy in a graphical way.
Just personal preference on this one ... I find the exact opposite. We don't do almost any table layout, and opening a complex css-laid-out component in WOBuilder appears to me to be unintelligible. Component editor in Eclipse shows both an outline view of your components as well as the collapsible HTML editor with rollovers that show the span of each tag. But this has been debated to death, so I'm leaving this at "personal preference."

Perhaps something is broken in my WOLips setup. But the outline view of my component never shows any rollovers. The only connection I can find is that when I click on the outline, it takes me to that component in the HTML pane. But that's the wrong way for me.


A typical task is that a customer has asked for another input field, and I know that it's somewhere near the text "Product Title:" in the component. So in WOBuilder I just search on that text, and I'm immediately shown a page full of 2D widgets representing the components near there, and I can instantly identify the text fields, conditionals, repetitions and so on, and if I like I can just click on a <div> surrounding a similar input field, its label, conditionals, styles etc, and paste a copy nearby, then chenge the bindings and text to suit the new attribute.

In the WOLips Component Editor, I can twiddle on the outline view forever without finding the location I want. And it doesn't show the important contextual "Product Title:" clue. And since I can't (or don't know how to) get from the HTML pane to a specific place in the outline editor, I'm stuck.

Am I missing something stupidly simple?


- the ability to cut or copy a whole group of elements and paste them somewhere else, bindings and all.
This could definitely be added into component editor ... I can pretty easily, I think, track the associated wod bindings when you cut HTML and autocut/copy related wod entries.

That would be fantastic-- if you could copy/paste as well as cut/ paste and it looked after renaming the objects in the case of a copy. Oh-- and it didn't lose the quoted values like WOBuilder does.


_______________________________________________
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: Maybe No Need for a WOBuilder Replacement?
      • From: Mike Schrag <email@hidden>
References: 
 >Maybe No Need for a WOBuilder Replacement? (From: Andrew Lindesay <email@hidden>)
 >Re: Maybe No Need for a WOBuilder Replacement? (From: Galen Rhodes <email@hidden>)
 >Re: Maybe No Need for a WOBuilder Replacement? (From: Thomas <email@hidden>)
 >Re: Maybe No Need for a WOBuilder Replacement? (From: Mike Schrag <email@hidden>)

  • Prev by Date: Re: Ajax File Uploader / WOLongResponse File Uploader
  • Next by Date: Re: Maybe No Need for a WOBuilder Replacement?
  • Previous by thread: Re: Maybe No Need for a WOBuilder Replacement?
  • Next by thread: Re: Maybe No Need for a WOBuilder Replacement?
  • Index(es):
    • Date
    • Thread