Maybe you meant this bug?
https://bugs.eclipse.org/bugs/show_bug.cgi?id=151644
As you can see its been decided against.
It would be really great if JFace could provide a widget wrapper/proxy
mechanism. I think having each widget developer create their own
viewer is kinda redundant redundant. They would also almost certainly
lag behind design and feature changes in the main JFace viewers. Does
any of your existing patches contain this kind of wrapper feature?
I do have plans to create a Nebula project
with a JFace dependency (how bout NebFace?). Besides just viewers
there could be other things like contribution managers too.
-Chris
Tom Schindl <listom@xxxxxxxxxxxxxxx> Sent by: nebula-dev-bounces@xxxxxxxxxxx
08/04/2006 10:30 AM
Please respond to
Nebula Dev <nebula-dev@xxxxxxxxxxx>
To
Nebula Dev <nebula-dev@xxxxxxxxxxx>
cc
Subject
Re: [nebula-dev] Viewers
Tom Schindl schrieb:
> Just my 2¢.
>
> At the moment there's great effort at JFace-side to make Viewers more
> platform compatible and extensible.
>
Sorry meant not platform but widget-set
> See
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=149193
>
> and maybe more important for you nebula:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=151377
If this does go through I already providing this at JFace level using
wrappers which widget-implementators (e.g. nebula) have to provide.
>
> A nebula-viewer-project although is in my idea a good thing to have
> because it could provide more specialized Viewers ontop of JFace.
>
> I think the same concept of than SWT vs. JFace could be done for nebula
> Nebula vs NeFace (NebulaJFace).
>
> Tom
>
> Ian Bull schrieb:
>> I agree with this this, I think having viewers for some of these
widgets
>> will really help with adoption.
>>
>> Do you think the existing content provider interfaces will work
or will
>> you need a more specialized ICTableTreeStructuredContenetProvider?
>>
>> Cheers,
>> ian
>>
>> Roland Tepp wrote:
>>> Although I admit I don't quite know anything about the internal
>>> structure of Nebula project the first thing popping to my
mind is to
>>> have two well separated CVS/eclipse projects - one for widget(s)
and
>>> another for viewer code.
>>>
>>> Jeremy Dowdall kirjutas mulle midagi seesugust:
>>>> I will be uploading the CTableTree this weekend but am
not sure what to
>>>> do with its viewer since, as mentioned on this list, Nebula
is not to
>>>> have dependencies beyond SWT. I have no problem
with keeping the viewer
>>>> on my Sourceforge site and linking to it from CTableTree's
Nebula page
>>>> (it's great advertising, how could I mind?!) but there
should probably
>>>> be a more defined solution in the works - as also mentioned,
people will
>>>> want viewers.
>>>>
>>>> Thoughts / comments?
>>>> _______________________________________________
>>>> nebula-dev mailing list
>>>> nebula-dev@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>>>> _______________________________________________
>>>> nebula-dev mailing list
>>>> nebula-dev@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>>>>
>>
>> _______________________________________________
>> nebula-dev mailing list
>> nebula-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>
>
> _______________________________________________
> nebula-dev mailing list
> nebula-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nebula-dev