| Welcome [message #146] |
Thu, 17 April 2003 15:08  |
Eclipse User |
|
|
|
Originally posted by: john_wiegand.oti.com
Welcome to the Platform newsgroup.
This is the place for technical discussions about how to
develop Eclipse plug-ins. This forum is open to all - please
join in! If you have questions, comments, advice, please post
them here. However, if you want to report a bug or request
a feature, please use bugzilla http://dev.eclipse.org/bugs/
Look for additional eclipse.platform.* newsgroups for more
specific discussions, such as the SWT newsgroup.
---The Eclipse Platform Team
|
|
|
| Details on developing "core" eclipse plugins? [message #174 is a reply to message #146] |
Thu, 17 April 2003 18:01  |
| Eclipse User |
|
|
|
Originally posted by: kduffey.marketron.com
Hi there all,
Glad to see a forum for this line of discussion!
I happen to be working on adding XMLPull parsing by replacing the
eclipse.core.runtime.PluginParser class with my own. There are a few issues
that I have.
First, I read the PDE stuff and there isn't anything on working on core
classes. I am going to assume that this is usually left up to the core
eclipse team and therefore the majority of plugin developers are outside the
scope of core plugins. In particular since the piece of code I am working on
seems to be detrimental to eclipse working (that is parsing the fragment.xml
and plugin.xml files), I am not quite sure how to properly "test and debug"
my code. I have even put System.out.println() calls in the original
PluginParser.java code and when I run the debug Eclipse (or runtime Eclipse)
where from what I have read a second Eclipse IDE should appear with my work
loaded, I am not seeing any output in the console at all. More so, I seem to
see the Eclipse splash get stuck, it just sort of sits there. What I do see
is a ton of output regarding the plugin names, one for each plugin I am
guessing. I see fragment.xml and plugin.xml for each plugin showing up. I
even tried setting a breakpoint in the parsePlugin() method to see if it
gets to that point. In debug, it doesn't ever stop there, so I am a bit
clueless as to what is going on. Perhaps some help from core eclipse
developers, better if the one who worked on the PluginParser class, could
enlighten me as to how to properly modify/add code to the PluginParser class
and see it tested? Am i missing the compiling stage? I am guessing that the
incremental compiler is already compiling because I see the red squigly
lines if i type something wrong, and they go away when I fix it and it
saves.
I did check out the org.eclipse.core.runtime as a project, which one
developer here told me to do, from the HEAD branch of Equinox (my original
work is being tested with Equinox and possibly put into Eclipse 2.2).
The other issue is the way parsing is done currently. I see a TON of nodes
below <extension .. > and <extension point > nodes but I see no specific
string values for these nodes, such as <page .. > <context .. > and many
others. I am unclear as to how these apparent random nodes are parsed and
used by the plugin. One developer had mentioned there are the "main" nodes,
then the rest are considered like key/value pairs and stored in that manner
in the PluginModel (I am guessing). So, the sticky issue here is without
knowing the node names, how are they parsed? Is there a set rule that every
node that isn't part of nodes like <Runtime>, <library>, <requires>,
<extension-point> and so forth that those always have a number of key/value
pairs below them and they are stored in a specific manner? Also, looking at
the code I see the use of a stack, and I am not quite clear on why it is
used. Is it required, or is it just the way the class is parsing the xml
nodes?
So, if anyone wants to look at the PluginParser class, maybe help me out a
bit, I would appreciate it.
Thanks.
|
|
|
| Re: Welcome [message #234 is a reply to message #146] |
Fri, 18 April 2003 14:57 |
| Eclipse User |
|
|
|
Originally posted by: knut_radloff.oti.com
"John Wiegand" <john_wiegand@oti.com> wrote in message news:b7mfes$b0f$1@rogue.oti.com...
> Welcome to the Platform newsgroup.
>
> This is the place for technical discussions about how to
> develop Eclipse plug-ins. This forum is open to all - please
What is the appropriate forum to ask general Eclipse user questions, i.e., those not specific to JDT?
Now that the eclipse.tools newsgroup is being retired there doesn't seem to be a place to ask questions like the "Custom Filters in
Navigator view" one.
I think the eclipse.tools newsgroup should still be active and used for anything not JDT, SWT or plugin development related.
Knut
|
|
|
|
| Re: Details on developing "core" eclipse plugins? [message #2812 is a reply to message #174] |
Tue, 22 April 2003 15:33 |
| Eclipse User |
|
|
|
Originally posted by: chaves.nospam.inf.ufsc.br
Kevin wrote:
> First, I read the PDE stuff and there isn't anything on working on core
> classes.
> (...)
> I am not quite sure how to properly "test and debug"
> my code.
The PDE rules for self-hosting should work as usual even when the plug-in
in question is the core.runtime plug-in.
I think you should try developing a simple custom plug-in first to become
more familiar with self-hosting (running/debugging/testing with JUnit) in
Eclipse. Once you feel confident with the environment, it will be much
easier to do what you want.
I would suggest as well to break your different questions in different
posts, so it is more likely for people to understand your problems and
give you answers.
Regards,
Rafael
|
|
|
|
Powered by
FUDForum. Page generated in 0.03567 seconds
] 
Search
Help
Register
Login
Home
