Re: [mylyn-integrators] Problems writing a custom context bridge

[Shawn Minto <sminto@xxxxxxxxx>]

Hi Jan,

You are correct that the entire workspace is provided and we filter it
to show only what is in the context. What are you trying to do and
maybe I would be able to help come up with a work around.

Shawn


--
Shawn Minto
sminto@xxxxxxxxx
----------------------------------------



On Wed, Aug 10, 2011 at 7:29 AM, Jan Mauersberger <mauersberger@xxxxxx> wrote:
> Hi Shawn,
>
> thanks to your description I managed to get my own content provider in
> place. However, the provider is initialized with the workspace root object
> (ContextEditorFormPage line 486:
> commonViewer.setInput(getSite().getPage().getInput()); I do not see how I
> can get access to the context information of the task with that input.
> Therefore I assume that the complete workspace is provided but due to the
> applied interest filter only the objects that are in the context are
> visible, is that assumption correct? In that case my idea is damned to fail
> ;-(
>
> Jan
>
>> Hi Jan,
>>
>> It sounds like you are very far along if items are showing up as
>> invisible.  The context tab of the Task Editor is a common navigator
>> where you will need to contribute a content provider for you elements
>> to show up correctly.  If you look in the plugin.xml of o.e.m.java.ui,
>> you will see the java navigator content provider from JDT added to the
>> context page.  You will need to create a common navigator content
>> provider for your elements (see
>>
>> http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fcnf.htm).
>>  The following is the xml to add the content extension to the context
>> page and the quick context popup:
>>
>> <!-- ==================== Context Editing Common Navigator
>> ==================== -->
>>
>>        <extension
>>                        point="org.eclipse.ui.navigator.viewer">
>>                <viewerContentBinding
>>
>>  viewerId="org.eclipse.mylyn.context.ui.navigator.context">
>>                        <includes>
>>                                <contentExtension
>> pattern="org.eclipse.jdt.java.ui.javaContent" />
>>                        </includes>
>>                </viewerContentBinding>
>>                <viewerContentBinding
>>
>>  viewerId="org.eclipse.mylyn.context.ui.navigator.context.quick">
>>                        <includes>
>>                                <contentExtension
>> pattern="org.eclipse.jdt.java.ui.javaContent" />
>>                        </includes>
>>                </viewerContentBinding>
>>        </extension>
>>
>>
>> Shawn
>>
>>
>> --
>> Shawn Minto
>> sminto@xxxxxxxxx
>> ----------------------------------------
>>
>>
>>
>> On Tue, Jul 12, 2011 at 7:48 AM, Jan Mauersberger<mauersberger@xxxxxx>
>>  wrote:
>>>
>>> Hi,
>>>
>>> short about my problem: I want to store my own type of elements in the
>>> context of a task and I started to write my own structure bridge. I got
>>> it
>>> work to the point that my elements are added to the context and shown as
>>> "Invisible Elements" in the task editor but no further. All attempts to
>>> correctly return the hierarchy of parent elements and to get them visible
>>> in
>>> the view failed. I stumbled over some mylyn base code and also some
>>> example
>>> bridge code that seems to assume that the top of such an element
>>> hierarchy
>>> is always a IResource, but I'm not sure. Anyway, in my context I don't
>>> have
>>> that IResource at the top (or more precisely I don't want to have it
>>> there.
>>>
>>> What do I do wrong with my bridge when I only get the elements added as
>>> invisible? Any chance to see arbitrary element trees in the context tab
>>> on
>>> the task editor?
>>>
>>> Any hint highly appreciated.
>>>
>>> Jan
>>>
>>> --
>>>
>>> jan mauersberger
>>> senior architect / ikv++ technologies ag
>>> dessauer strasse 28/29; 10963 Berlin
>>> e|mauersberger@xxxxxx w|www.ikv.de
>>> p|+49 (30) 3480 7711 f|+49 (30) 3480 780
>>>
>>> _______________________________________________
>>> mylyn-integrators mailing list
>>> mylyn-integrators@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/mylyn-integrators
>>>
>> _______________________________________________
>> mylyn-integrators mailing list
>> mylyn-integrators@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/mylyn-integrators
>>
>
>
> --
> jan mauersberger
> senior architect / ikv++ technologies ag
> dessauer strasse 28/29; 10963 Berlin
> e|mauersberger@xxxxxx w|www.ikv.de
> p|+49 (30) 3480 7711 f|+49 (30) 3480 780
>
> _______________________________________________
> mylyn-integrators mailing list
> mylyn-integrators@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylyn-integrators
>