Re: WO Component Editor Issue

From: Mike Schrag (mschra..dimension.com)
Date: Thu Sep 29 2005 - 09:42:13 EDT

  • Next message: Sébastien Sahuc: "Re: WO Component Editor Issue"

    The WindowSelectionService believes the active part is the Java
    Editor (CompilationUnitEditor) ... So the selection service is not be
    added to the appropriate editor.

    On Sep 29, 2005, at 8:43 AM, Mike Schrag wrote:

    > I think this was a red herring, because I can't now get it to
    > reproduce ... However, one thing I am noticing is that WOD Editor
    > goes through all the same processes as Component Editor/WOD Editor
    > EXCEPT when it gets to the point of delivering the selection event,
    > in Component Editor there are 5 listeners .. in WOD Editor there
    > are TWELVE listeners. The last two are the most interesting --
    > WindowSelectionService and PageSelectionService. These don't exist
    > on Component Editor.
    >
    > On Sep 28, 2005, at 11:39 PM, Mike Schrag wrote:
    >
    >> This find/replace code is a tangled mess to trace through ... What
    >> I know so far (is not much), but if I have a word "Test" at the
    >> beginning of a WOD file and search for it in WOD Editor
    >> standalone, the startOffset of the search is 0. When I search for
    >> the word in WOD Editor as part of Component Editor, the start
    >> offset is 4, placing it AFTER the match. The start offset comes
    >> from the current selection on Styled Text, but I have yet to
    >> figure out who's SETTING it to 4 or if that is even the actual
    >> cause of the failure, but it is a notable difference between the
    >> two scenarios.
    >>
    >> On Sep 28, 2005, at 12:28 PM, Ulrich Köster wrote:
    >>
    >>> Moin Mike,
    >>>
    >>> do you have the time investigate the issue and provide a patch?
    >>>
    >>> I'll take a look at it also.
    >>>
    >>> Ulrich
    >>>
    >>> Am 28.09.2005 um 17:49 schrieb Sébastien Sahuc:
    >>>
    >>>> I've asked to address the find/search bug in eclipse for 3.1.1,
    >>>> here is what it's been replied. Could we have some people in the
    >>>> list vote for this ? All you have to do is go to: https://
    >>>> bugs.eclipse.org/bugs/show_bug.cgi?id=108774 then click the
    >>>> 'vote' link.
    >>>>
    >>>> Sebastien
    >>>>
    >>>> ------ Additional Comment #1 From Sebastien Sahuc 2005-09-28
    >>>> 11:29 [reply] -------
    >>>> This is a showstopper for any MPE plugin such as WOLips. Could
    >>>> we address that for 3.1.1 ?
    >>>>
    >>>> ------- Additional Comment #2 From Paul Webster 2005-09-28 11:39
    >>>> [reply] -------
    >>>> 3.1.1 has had RC2, I don't think we are submitting any more code.
    >>>>
    >>>> PW
    >>>>
    >>>> ------- Additional Comment #3 From Michael Van Meekeren
    >>>> 2005-09-28 11:42 [reply] -------
    >>>> I suppose if a patch were to appear today or tomorrow we could
    >>>> consider but at
    >>>> this point it is not on the plan. Does anyone have time to
    >>>> investigate?
    >>>>
    >>>>
    >>>>
    >>>> On Sep 28, 2005, at 8:35 AM, Sébastien Sahuc wrote:
    >>>>
    >>>>> Thanks Mike,
    >>>>>
    >>>>> Comments very well appreciated. Will keep an eye on the eclipse
    >>>>> bug.
    >>>>>
    >>>>> Sebastien
    >>>>>
    >>>>> On Sep 27, 2005, at 4:55 PM, Mike Schrag wrote:
    >>>>>
    >>>>>> Search not working is a show stopper in anyone's opinion,
    >>>>>> which is why you'll notice that there is no WOLips 2.0 final
    >>>>>> release. You're running off of a nightly build from the head
    >>>>>> of the CVS tree on top of an unreleased version of your IDE --
    >>>>>> not everything is going to work yet. The example you give of
    >>>>>> a successful search is in a single editor, not a multi-part
    >>>>>> editor (MPE), which is what is used for WO Component editor.
    >>>>>> I'm not saying there's not a workaround that could be done up
    >>>>>> at the WOLips level, but as far as I've been able to tell from
    >>>>>> tracing through Eclipse's text search/selection code, it's a
    >>>>>> failure in "their stuff".
    >>>>>>
    >>>>>> In the meantime, you should be able to disassociate WO/Java/
    >>>>>> HTML/etc from using WO Component Editor and attach them
    >>>>>> individually to their standalone counterparts. That is, you
    >>>>>> can associate WOD files with WOD Editor directly, which will
    >>>>>> allow you to search to your hearts delight.
    >>>>>>
    >>>>>> ms
    >>>>>>
    >>>>>> On Sep 27, 2005, at 6:41 PM, Sébastien Sahuc wrote:
    >>>>>>
    >>>>>>>> 2) This is an Eclipse 3.1.1 bug
    >>>>>>>
    >>>>>>> --> Can't search inside WOD And HTML is a show stopper IMHO.
    >>>>>>> And I'm curious to hear why you think it's an Eclipse 3.1.1
    >>>>>>> bug. Indeed when I open of the .wod with the text editor , or
    >>>>>>> the .html with the HTML editor, the search works just fine.
    >>>>>>> It's ONLY when using the WO editor that the search fails.
    >>>>>>> Again, this is a REAL problem and from what I see it looks
    >>>>>>> like limited to WOLips plugin. Is there any bug open
    >>>>>>> elsewhere on that subject (both woproject and eclipse ) ?
    >>>>>>>
    >>>>>>> Thanks,
    >>>>>>>
    >>>>>>> Sebastien
    >>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>>> 3) There error is actually that it's either missing or
    >>>>>>>> doesn't extend WOElement ... It's possible the parser's not
    >>>>>>>> able to FIND the class for some reason. Can you send me
    >>>>>>>> what the hierarchy for that class looks like and if there's
    >>>>>>>> anything kind of weird about the location of the source file
    >>>>>>>> that is referenced relative to the wod (i.e. in a framework,
    >>>>>>>> in a weird folder, etc?)
    >>>>>>>>
    >>>>>>>> ms
    >>>>>>>>
    >>>>>>>> On Sep 20, 2005, at 11:07 AM, Dov Rosenberg wrote:
    >>>>>>>>
    >>>>>>>>> I just updated to build 2.0.0.53 and came across a couple
    >>>>>>>>> of weird errors:
    >>>>>>>>>
    >>>>>>>>> Every other time I recompile and rebuild my project – the
    >>>>>>>>> WOD parser errors either show up or disappear.
    >>>>>>>>> Can’t search inside the WOD or HTML
    >>>>>>>>> Some components in my project cause the WOD Parser to flag
    >>>>>>>>> errors indicating that a referenced component does not
    >>>>>>>>> extend WOElement. All of our components extend WOComponent
    >>>>>>>>> or some descendent thereof
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>> --
    >>>>>>>>> Dov Rosenberg
    >>>>>>>>> Conviveon/Inquira
    >>>>>>>>> Knowledge Management Experts
    >>>>>>>>> http://www.conviveon.com
    >>>>>>>>> http://www.inquira.com
    >>>>>>>>>
    >>>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>>
    >>
    >



    This archive was generated by hypermail 2.0.0 : Thu Sep 29 2005 - 09:42:24 EDT