Daniel,
since I don't have a book detailing how to do this (and the
O'Reilly book on Eclipse I did read said little more than what the
documentation says) the "steps" would be:
- Install Eclipse with plugin development stuff
- Find plugin demo or other editor source
- study example and start new one.
Unfortunately nothing more than this simplistic plan. My first
attempt gave me no syntax highlighting, but I did find out
how to trigger the auto-complete.
The standard demo of a Java Editor helps a bit, and I think
the NSIS editor could be an alternative. I haven't found a real
manual or explanation yet. It'll be a non-trivial exercise in
Java hacking I'm afraid.
To be sure, just a plain editor isn't much of a problem, the default
text editor will do that. It's the sup****t for syntax higlighting
and auto-complete that is the mystery I'm trying to fathom.
Do you have any ideas? Might there be an open sourced Pascal or
Ada plugin somewhere? That would probably be a better start.
Cheers,
Bert
Daniel Benavides wrote:
> If you are intereseted in developing a plugin for eclipse, I think it
> would a very nice idea, specially, for the y know plataforms sup****ted
> with the cm3 distro and why not, pm3.
> What tasks do you plan, and what are the knowledge needed to acomplish
> it?
>
> Daniel Benavides
> Bert Laverman ha escrito:
>
>
>>Y'all,
>>I took a look at Eclipse plugins recently, and I think that, using
>>examples from e.g. the NSIS configuration editor and the demo Java
>>plugin, making a Modula-3 aware editor wouldn't be that hard.
>>Anybody ever tried something like that?
>>
>>I've got an interest in this, as I kind of overdid some scripting
>>tool I made, and ended up with a nice start at an M3 toolkit. I'm
>>trying to see if I can convince legal to take this home, otherwise
>>I'ld have to re-start.
>>
>>It's in Java, but has full access to the JVM. Module identifiers are
>>layered like Java to give packages, but IM****Ts will just as easily
>>im****t a Java runtime package. It's far from complete, but is a big
>>help as scripting language.
>>
>>I guess I wanted scripting, but not Perl or PHP. Can't help myself,
>>just like writing compilers, and my job never needs them. Ah well,
>>that's what you get for working for an employer who wants development
>>risks for tooling to be with vendors of tools.
>>
>>Bert Laverman
>
>
|
