RE: [dash-dev] Documentation for built-in DOMs?

[Ingo Muschenetz <ingo@xxxxxxxxxx>]

Hi All,

I realize now that the JavaDocs had not been published for Eclipse Monkey. I'll make sure that gets taken care of.

However, I'm pretty sure a DOM hasn't been written to wrap the compare functionality. One of the tricks I would use is to find the specific piece of functionality I wanted by searching through the Eclipse source, and then extracting that out into a small DOM I could use. I did this for things like "Open Type" based on a class name by looking through the JDT sources.

Much of the UI components of Eclipse aren't readily set up for programmatic/scripting access. Perhaps that is something we can hope to address as part of 3.4?

Thanks,
Ingo

-----Original Message-----
From: dash-dev-bounces@xxxxxxxxxxx [mailto:dash-dev-bounces@xxxxxxxxxxx] On Behalf Of Dickens, Thomas P
Sent: Monday, November 05, 2007 10:45 AM
To: Tools for Committer Community
Subject: RE: [dash-dev] Documentation for built-in DOMs?


The Eclipse scripting capability promises to be very powerful.
I've been trying to write a script, but the lack of documentation is a
problem!

I have a script that successfully locates two files I've
specified in a pop-up dialog. It took hours of trial-and-error
and looking at the few code samples available to get the first
part of the script running successfully. Here is the code after I have
located the two target files.

        files = resources.filesMatching( "reg exp from dialog..." );
        if( files.length == 2 ) {
           f0 = files[0].getEclipseObject() ;
           f1 = files[1].getEclipseObject() ;
         // compare with each other code goes here
      }

I now want to invoke the Eclipse "Compare with each other" right-click
menu option on these two files.

Any ideas or help on how to do this???

The DOM my script uses is:
 * DOM:
http://download.eclipse.org/technology/dash/update/org.eclipse.eclipsemo
nkey.lang.javascript

Thanks for any help you can provide.


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Tom Dickens -- Boeing Associate Technical Fellow --
thomas.p.dickens@xxxxxxxxxx



> -----Original Message-----
> From: Steve Corwin [mailto:scorwin@xxxxxxxxxxxxx]
> Sent: Monday, November 05, 2007 9:25 AM
> To: Tools for Committer Community
> Subject: Re: [dash-dev] Documentation for built-in DOMs?
>
> Which is what I'm doing now to, but it would be significantly
> easier to
> get started if there were some docs readily available.
>
> Versions:
> Eclipse: 3.3.0, Build id: I20070625-1500
> Buckminster Core: 0.2.0.r3483, the other pieces are all
> 0.2.0.r something
> All on Ubuntu 7.0.4 Feisty Fawn
>
> -Steve
>
>
> Bjorn Freeman-Benson wrote:
> > On the documentation issue: well, no, not really - we were
> just using
> > the source so far. You're right that we should at least
> extract Javadoc
> > from it to create documentation.
> >
> > On the Buckminster issue: what version of Eclipse and what
> version of
> > Buckminster are you using?
> >
> > Steve Corwin wrote:
> >> Is there documentation for the DOMs that ship with Eclipse
> Monkey?  I
> >> suspect that everything I want to do could be done with
> basic access
> >> to the active editor component, if I only knew what
> functions to call.
> >>
> >> I did try to look at the source, but I'm having trouble
> resolving it.
> >> Buckminster gives the following error, and disables the
> Finish button:
> >>
> >> Use of deprecated attribute <provider componentType> Use attribute
> >> 'componentTypes' instead :
> >> http://www.eclipse.org/dash/monkey/monkey.rmap, line 9.
> >> ERROR   [0001] : No component type with id eclipse.feature
> has been
> >> registered with extension-point
> >> org.eclipse.buckminster.core.componentTypes
> >>
> >> Thanks,
> >> Steve
> >> _______________________________________________
> >> dash-dev mailing list
> >> dash-dev@xxxxxxxxxxx
> >> https://dev.eclipse.org/mailman/listinfo/dash-dev
> >
> > --
> >
> > [end of message]
> >
> _______________________________________________
> dash-dev mailing list
> dash-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dash-dev
>
_______________________________________________
dash-dev mailing list
dash-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dash-dev