| Tree-Widget in RAP [message #515393] |
Thu, 18 February 2010 11:24  |
Eclipse User |
|
|
|
I know you RAP guys have a lot to do and what you've done so far is really
impressive but anyhow I'd like to point out *gently* that the current
support for the Tree widget is ... hmm ... let's say rather poor:
For example:
- no tooltips
- SWT.FULL_SELECTION not working
- setLinesVisible() not working, though there is already a patch available
in Bug 232406 (but is somehow not considered)
- and not to forget about all those open bugs and enhancement requests
regarding this widget.
Do you think it is possible to revise it in "near" future?
The way the works right now, it is hardly usable...
Thanks,
Niels
|
|
|
| Re: Tree-Widget in RAP [message #515444 is a reply to message #515393] |
Thu, 18 February 2010 13:55  |
| Eclipse User |
|
|
|
Niels,
I fully understand that you are unsatisfied with the current state of
the Tree widget. Though "hardly usable" depends on the use case. In
other cases than yours, it serves quite well. Anyway, I don't want to argue.
Apart from tooltips, the limitations are rooted in the client-side Tree
widget that comes from the qx library. The qx-Tree just wasn't made with
requirements in mind as they arise in the RAP/RCP environment it is
placed. We already pushed the Tree as far as we can get with reasonable
effort.
To get around these bugs it is required to re-implement the widget from
scratch (as done with the Table widget). And that isn't realistic for
the near future.
Regards,
--
Rüdiger Herrmann
http://eclipsesource.com
On 18.02.2010 17:24, Niels Lippke wrote:
> I know you RAP guys have a lot to do and what you've done so far is
> really impressive but anyhow I'd like to point out *gently* that the
> current support for the Tree widget is ... hmm ... let's say rather poor:
>
> For example:
> - no tooltips
> - SWT.FULL_SELECTION not working
> - setLinesVisible() not working, though there is already a patch
> available in Bug 232406 (but is somehow not considered)
> - and not to forget about all those open bugs and enhancement requests
> regarding this widget.
>
> Do you think it is possible to revise it in "near" future?
>
> The way the works right now, it is hardly usable...
>
> Thanks,
> Niels
|
|
|
| Re: Tree-Widget in RAP [message #515518 is a reply to message #515444] |
Thu, 18 February 2010 22:08 |
| Eclipse User |
|
|
|
"Rüdiger Herrmann" <rherrmann@eclipsesource.com> schrieb im Newsbeitrag
news:hlk2fq$rs3$1@build.eclipse.org...
> Niels,
>
> I fully understand that you are unsatisfied with the current state of the
> Tree widget. Though "hardly usable" depends on the use case. In other
> cases than yours, it serves quite well. Anyway, I don't want to argue.
You're right. In my case - showing two columns, make one editable - its
current state is not reasonable for
a user to work on it. If you have only one column it might be sufficient.
> Apart from tooltips, the limitations are rooted in the client-side Tree
> widget that comes from the qx library. The qx-Tree just wasn't made with
> requirements in mind as they arise in the RAP/RCP environment it is
> placed. We already pushed the Tree as far as we can get with reasonable
> effort.
> To get around these bugs it is required to re-implement the widget from
> scratch (as done with the Table widget). And that isn't realistic for the
> near future.
This is at least good to know. I should use a table instead.
Thanks,
Niels
>
> Regards,
>
> --
> Rüdiger Herrmann
> http://eclipsesource.com
>
> On 18.02.2010 17:24, Niels Lippke wrote:
>> I know you RAP guys have a lot to do and what you've done so far is
>> really impressive but anyhow I'd like to point out *gently* that the
>> current support for the Tree widget is ... hmm ... let's say rather poor:
>>
>> For example:
>> - no tooltips
>> - SWT.FULL_SELECTION not working
>> - setLinesVisible() not working, though there is already a patch
>> available in Bug 232406 (but is somehow not considered)
>> - and not to forget about all those open bugs and enhancement requests
>> regarding this widget.
>>
>> Do you think it is possible to revise it in "near" future?
>>
>> The way the works right now, it is hardly usable...
>>
>> Thanks,
>> Niels
|
|
|
Powered by
FUDForum. Page generated in 0.09333 seconds
Home