Home » Language IDEs » Java Development Tools (JDT) » JDT Project Tree Structure Question
| JDT Project Tree Structure Question [message #159843] |
Fri, 21 May 2004 12:15  |
Eclipse User |
|
|
|
Originally posted by: dkumar.oc.com
Hello,
I am trying to build several plugins into Eclipse that will develop an end
result that has nothing to do with Java (the plugins themselves are
written in Java though). I noticed that in Eclipse, for the Java editor
(JDT) using the Package Explorer, the project tree contains Java class
nodes that the user can expand in the tree. The user can then see all of
the methods/fields/etc. contained in the Java class. The tree is
dynamically built as the user types in the Java editor. However, the
nodes in the tree do not appear to be files or folders, yet they are
expandable.
Does anyone know how I might develop a similar project tree in Eclipse?
The public API only allows for projects, folders, files, and workspaces in
the tree. I know the Java nodes in the tree are closely tied to the JDT,
it appears it was specifically built for the JDT with the use of the AST
internally. Is there a way to build a project tree that contains
expandable nodes (like the JDT Java class nodes), but that does not depend
on the JDT? Thanks for any help.
-David
|
|
|
| Re: JDT Project Tree Structure Question [message #160259 is a reply to message #159843] |
Mon, 24 May 2004 06:19  |
| Eclipse User |
|
|
|
Originally posted by: daniel.megert.gmx.net
David wrote:
>Hello,
>I am trying to build several plugins into Eclipse that will develop an end
>result that has nothing to do with Java (the plugins themselves are
>written in Java though). I noticed that in Eclipse, for the Java editor
>(JDT) using the Package Explorer, the project tree contains Java class
>nodes that the user can expand in the tree. The user can then see all of
>the methods/fields/etc. contained in the Java class. The tree is
>dynamically built as the user types in the Java editor. However, the
>nodes in the tree do not appear to be files or folders, yet they are
>expandable.
>
>Does anyone know how I might develop a similar project tree in Eclipse?
>The public API only allows for projects, folders, files, and workspaces in
>the tree.
>
That's true for the Core Resources API but the Package Explorer reflects
the Java Model.
> I know the Java nodes in the tree are closely tied to the JDT,
>it appears it was specifically built for the JDT with the use of the AST
>internally. Is there a way to build a project tree that contains
>expandable nodes (like the JDT Java class nodes), but that does not depend
>on the JDT? Thanks for any help.
>
>
Sure, you simply need to define the model and then show its nodes in a
tree viewer.
Dani
>-David
>
>
>
|
|
|
| Re: JDT Project Tree Structure Question [message #160374 is a reply to message #160259] |
Mon, 24 May 2004 10:17 |
| Eclipse User |
|
|
|
Originally posted by: dkumar.oc.com
I understand I can use a tree viewer to show any kind of data I want. And
depending on the model I use for the tree viewer, I can make the tree
nodes in the viewer expandable or not.
But is there a way to use the Package Explorer tree without building my
own tree viewer? Can I somehow change the Package Explorer tree to show
tree nodes that are expandable file nodes - just like the .java files in
the tree but that are not dependent on the JDT? Can this be done, or am I
just stuck with projects, folders, files, and workspaces in the Package
Explorer tree? Thanks for ANY help!
-David
Daniel Megert wrote:
> David wrote:
> >Hello,
> >I am trying to build several plugins into Eclipse that will develop an end
> >result that has nothing to do with Java (the plugins themselves are
> >written in Java though). I noticed that in Eclipse, for the Java editor
> >(JDT) using the Package Explorer, the project tree contains Java class
> >nodes that the user can expand in the tree. The user can then see all of
> >the methods/fields/etc. contained in the Java class. The tree is
> >dynamically built as the user types in the Java editor. However, the
> >nodes in the tree do not appear to be files or folders, yet they are
> >expandable.
> >
> >Does anyone know how I might develop a similar project tree in Eclipse?
> >The public API only allows for projects, folders, files, and workspaces in
> >the tree.
> >
> That's true for the Core Resources API but the Package Explorer reflects
> the Java Model.
> > I know the Java nodes in the tree are closely tied to the JDT,
> >it appears it was specifically built for the JDT with the use of the AST
> >internally. Is there a way to build a project tree that contains
> >expandable nodes (like the JDT Java class nodes), but that does not depend
> >on the JDT? Thanks for any help.
> >
> >
> Sure, you simply need to define the model and then show its nodes in a
> tree viewer.
> Dani
> >-David
> >
> >
> >
|
|
|
| Re: JDT Project Tree Structure Question [message #167203 is a reply to message #160374] |
Mon, 05 July 2004 05:28 |
| Eclipse User |
|
|
|
Originally posted by: daniel.megert.gmx.net
David wrote:
>I understand I can use a tree viewer to show any kind of data I want. And
>depending on the model I use for the tree viewer, I can make the tree
>nodes in the viewer expandable or not.
>
>But is there a way to use the Package Explorer tree without building my
>own tree viewer? Can I somehow change the Package Explorer tree to show
>tree nodes that are expandable file nodes - just like the .java files in
>the tree but that are not dependent on the JDT? Can this be done, or am I
>just stuck with projects, folders, files, and workspaces in the Package
>Explorer tree?
>
Neither the Navigator nor the Package Explorer can currently be
extended. You have to write your own view with your own label and
content providers.
Dani
> Thanks for ANY help!
>-David
>
>
>
>Daniel Megert wrote:
>
>
>
>>David wrote:
>>
>>
>
>
>
>>>Hello,
>>>I am trying to build several plugins into Eclipse that will develop an end
>>>result that has nothing to do with Java (the plugins themselves are
>>>written in Java though). I noticed that in Eclipse, for the Java editor
>>>(JDT) using the Package Explorer, the project tree contains Java class
>>>nodes that the user can expand in the tree. The user can then see all of
>>>the methods/fields/etc. contained in the Java class. The tree is
>>>dynamically built as the user types in the Java editor. However, the
>>>nodes in the tree do not appear to be files or folders, yet they are
>>>expandable.
>>>
>>>Does anyone know how I might develop a similar project tree in Eclipse?
>>>The public API only allows for projects, folders, files, and workspaces in
>>>the tree.
>>>
>>>
>>>
>>That's true for the Core Resources API but the Package Explorer reflects
>>the Java Model.
>>
>>
>
>
>
>>> I know the Java nodes in the tree are closely tied to the JDT,
>>>it appears it was specifically built for the JDT with the use of the AST
>>>internally. Is there a way to build a project tree that contains
>>>expandable nodes (like the JDT Java class nodes), but that does not depend
>>>on the JDT? Thanks for any help.
>>>
>>>
>>>
>>>
>>Sure, you simply need to define the model and then show its nodes in a
>>tree viewer.
>>
>>
>
>
>
>>Dani
>>
>>
>
>
>
>>>-David
>>>
>>>
>>>
>>>
>>>
>
>
>
>
|
|
|
Goto Forum:
Current Time: Fri Jul 25 22:04:25 EDT 2025
Powered by FUDForum. Page generated in 0.04960 seconds |
Home