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 : Wed Sep 28 2005 - 11:35:21 EDT