Re: why the Component Editor is so un-helpful...

From: Ray Kiddy (ra..anymede.org)
Date: Mon Dec 14 2009 - 17:39:37 EST

  • Next message: David Avendasora: "Re: why the Component Editor is so un-helpful..."

    On Dec 14, 2009, at 2:21 PM, Tim Worman wrote:

    > Also, if you manage to get your perspective messed up somehow (very
    > easily done), it is possible to reset the perspective under the
    > Window menu. That might have corrected your problem too since it
    > seems to go back to defaults when you do that?
    >
    > Tim Worman
    > UCLA GSE&IS
    >
    >

    Nope. I have reset the perspective many times, including just today.
    That does not do it.

    - ray

    >
    > On Dec 14, 2009, at 1:32 PM, Ray Kiddy wrote:
    >
    >>
    >> On Dec 14, 2009, at 1:27 PM, Mike Schrag wrote:
    >>
    >>> incidentally, wolips saves the split view positions (or maybe the
    >>> weights?), so that if you're using mostly inline bindings, you can
    >>> just collapse it down and it stays collapsed. the "this wod file
    >>> is not empty" is to provide some indication that you have
    >>> collapsed your view, but there is actually information to see
    >>> inside the wod. the default in wolips is to NOT be closed, though,
    >>> so you had have closed it at some point to get to that point.
    >>>
    >>> ms
    >>
    >> OMG! I cannot believe that has been there the entire time.....
    >>
    >> I am really going to have to file a bug with eclipse about the non-
    >> obviousness of that UI element.
    >>
    >> I guess that, at times, the only way to figure out what eclipse can
    >> do in some of these views is more your cursor over every pixel in
    >> the view and see if the cursor changes. I bet that does not cover
    >> it all, though....
    >>
    >> Well, thanks anyway.
    >>
    >> - ray
    >>
    >>
    >>>
    >>> On Dec 14, 2009, at 4:21 PM, Mike Schrag wrote:
    >>>
    >>>> I have no idea why you have the huge white space between the
    >>>> breadcrumb and the sash ... as far as the lack of any ui denoting
    >>>> that you can resize that thing, thank eclipse's Sash
    >>>> implementation, which doesn't draw any handles. Maclipse,
    >>>> however, does:
    >>>>
    >>>> <PastedGraphic-3.png>
    >>>>
    >>>> notice the couple lines there in the horizontal gray bar below
    >>>> the breadcrumb.
    >>>>
    >>>> when you scale it small enough, rather than show a degenerate
    >>>> case of the scrollbar, it collapses away:
    >>>>
    >>>> <PastedGraphic-2.png>
    >>>>
    >>>> why SWT chose not to draw any grab handle on their Sash
    >>>> component, I don't know.
    >>>>
    >>>> ms
    >>>>
    >>>> On Dec 14, 2009, at 4:14 PM, Ray Kiddy wrote:
    >>>>
    >>>>>
    >>>>> Hey -
    >>>>>
    >>>>> I figured out something about why I prefer modern syntax for wo
    >>>>> components and why the Component Editor in WOLips is so un-
    >>>>> helpful when I am editing old-style components. I have never,
    >>>>> ever, ever seen the wod contents in the same pane as the html
    >>>>> when I edit a wo.
    >>>>>
    >>>>> How is this happening? I would not be surprised, knowing me, if
    >>>>> I set some flag a long, long time ago that disabled or broke
    >>>>> something. I just cannot figure out what it is.
    >>>>>
    >>>>> So, for example, if I open the ERNeutralLook framework project
    >>>>> in eclipse and open the ERNeutralLook.wo component, I see its
    >>>>> html in the top part of the resulting pane. In the bar in the
    >>>>> middle of that pane, I get flattened DOM structure of the
    >>>>> selected element in the html. And below that brown bar I see
    >>>>> nothing. Well, in very faint letters, basically white letters in
    >>>>> a white background, I see "wod file is not empty." But I do not
    >>>>> see its contents. See the pic below. Why not?
    >>>>>
    >>>>> I actually did not realize that I was supposed to see anything
    >>>>> under there until, on a whim, I watched Pascal's podcast on the
    >>>>> component editor. I mean, I thought I knew how to use the
    >>>>> editor. Who knew.
    >>>>>
    >>>>> Well, there is actually one time I see something in the bottom
    >>>>> part. If I click on one of the WO Element icons that appear in
    >>>>> the toolbar when one is editing a wo, then I see the wod
    >>>>> contents for that element in that lower half of the pane. But I
    >>>>> have never actually used those icons either. Typing "<wo:str ..
    >>>>> " is just not that difficult.
    >>>>>
    >>>>> So, how have I broken this? If I could double-click on a wo
    >>>>> component and actually see the wod contents, I might actually
    >>>>> not have to click on the wod in the 'Related' tab, get the
    >>>>> content menu and open the wod file in the text editor. That
    >>>>> would be so wonderful. Anyone have suggestions as to how I can
    >>>>> make this work?
    >>>>>
    >>>>> thanx - ray
    >>>>>
    >>>>> So, where are the wod contents in this view?
    >>>>>
    >>>>> <badWOComponentPane.png>
    >>>>
    >>>
    >>>
    >>>
    >>
    >
    >



    This archive was generated by hypermail 2.0.0 : Mon Dec 14 2009 - 17:40:21 EST