Home » Eclipse Projects » Eclipse Platform » Extending Java plug-ins to new language?
| Extending Java plug-ins to new language? [message #178163] |
Sun, 11 January 2004 01:37  |
Eclipse User |
|
|
|
Originally posted by: ronm.p-cube.com
Hello Guys.
We're looking to implement plug-ins to support a new network language that
we created. We would like to have a complete IDE for this language -
editors, views (heirarchy, call-heirarchy, etc) etc.
Because the language is similiar (somewhat) to java, we thought it might
be easier to take the existing java classes that do all that, and just
tweak them to our language. Is that possible? how can I access that code?
Thanks in advance,
Ron Mertens
P-Cube LTD.
|
|
| |
| Re: Extending Java plug-ins to new language? [message #178536 is a reply to message #178414] |
Mon, 12 January 2004 08:05  |
| Eclipse User |
|
|
|
Originally posted by: ronm.p-cube.com
Hello Tom.
Thanks for your reply. The thing is, we do not want to create new editors
(and views, more specifically) from scratch. It seems like a hard work for
nothing. Can I also get code for the java views? (call heirarchy, outline,
etc.) and build on those classes and just
tweak them to work on our new language?
How can I access the entire eclipse code?
Ron Mertens
P-Cube LTD.
On Mon, 12 Jan 2004 08:56:38 +0100, Tom Eicher <eclipse@tom.eicher.name>
wrote:
> have a look at the java editor example available from the eclipse
> download page.
>
> -tom
>
> Ron Mertens wrote:
>> Hello Guys.
>>
>> We're looking to implement plug-ins to support a new network language
>> that we created. We would like to have a complete IDE for this language
>> - editors, views (heirarchy, call-heirarchy, etc) etc.
>>
>> Because the language is similiar (somewhat) to java, we thought it
>> might be easier to take the existing java classes that do all that, and
>> just tweak them to our language. Is that possible? how can I access
>> that code?
>>
>> Thanks in advance,
>>
>> Ron Mertens
>> P-Cube LTD.
>
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
|
|
|
| Re: Extending Java plug-ins to new language? [message #178558 is a reply to message #178536] |
Mon, 12 January 2004 09:15 |
| Eclipse User |
|
|
|
Ron Mertens wrote:
> Hello Tom.
>
> Thanks for your reply. The thing is, we do not want to create new
> editors (and views, more specifically) from scratch. It seems like a
> hard work for nothing. Can I also get code for the java views? (call
> heirarchy, outline, etc.) and build on those classes and just
> tweak them to work on our new language?
>
> How can I access the entire eclipse code?
Check it out from CVS or download the full source build available from
the download page. The java editor is in the org.eclipse.jdt.ui plugin,
but it requires many other plugins, including jdt.core,
ui.workbench.texteditor, platform.core etc... it's a lot of code to just
tweak...
HTH, tom
|
|
| |
| Re: Extending Java plug-ins to new language? [message #179044 is a reply to message #178558] |
Tue, 13 January 2004 03:54 |
| Eclipse User |
|
|
|
Originally posted by: ronm.p-cube.com
Hello Tom,
Thanks fo ryour reply. Hmmm... So would you recommend writing the editors
and views from "scratch" rather than tweaking
the java code?
Our problem is that we fear we will have to do a lot of work for nothing -
like building heirarchy trees, GUI, stuff like that. Can these be somehow
reused? After all, languages are pretty much the same, we only change
syntax (ours is pretty much like java in many cases) and add our special
features (and remove features not supported by our language...).
Thanks,
Ron Mertens
P-Cube LTD.
>> Thanks for your reply. The thing is, we do not want to create new
>> editors (and views, more specifically) from scratch. It seems like a
>> hard work for nothing. Can I also get code for the java views? (call
>> heirarchy, outline, etc.) and build on those classes and just
>> tweak them to work on our new language?
>>
>> How can I access the entire eclipse code?
>
> Check it out from CVS or download the full source build available from
> the download page. The java editor is in the org.eclipse.jdt.ui plugin,
> but it requires many other plugins, including jdt.core,
> ui.workbench.texteditor, platform.core etc... it's a lot of code to just
> tweak...
>
> HTH, tom
>
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
|
|
|
| Re: Extending Java plug-ins to new language? [message #179067 is a reply to message #179044] |
Tue, 13 January 2004 04:35 |
| Eclipse User |
|
|
|
Ron, I don't recommend writing everything from scratch. I just think
that if you don't have too much experience with eclipse, its plug-in
system and all, you might be better off to start with the "java editor
example", which is a lot simpler than the full-blown java editor. It
uses the same mechanisms though, so that doing so does not mean you
cannot copy and adapt code from the java editor once you get your
project rolling.
But of course, all of this depends on your resources etc...
HTH, Tom
Ron Mertens wrote:
> Thanks for your reply. Hmmm... So would you recommend writing the
> editors and views from "scratch" rather than tweaking
> the java code?
>
> Our problem is that we fear we will have to do a lot of work for nothing
> - like building heirarchy trees, GUI, stuff like that. Can these be
> somehow reused? After all, languages are pretty much the same, we only
> change syntax (ours is pretty much like java in many cases) and add our
> special features (and remove features not supported by our language...).
|
|
|
| Re: Extending Java plug-ins to new language? [message #179106 is a reply to message #179067] |
Tue, 13 January 2004 07:56 |
| Eclipse User |
|
|
|
Originally posted by: ronm.p-cube.com
Hello Tom.
Thanks again. We intend to really turn Eclipse into our development
environment, so basically I assume I will quickly have to become
an Eclipse plug-in writer ;-)
But maybe you have a good suggestion. I guess the best would be to begin
with the Java editor example, tweak it so it supports our language. Than
at least I can have a plug-in with syntax colouring and simple stuff. Next
stage will be to take the real Java editor & Views plug-ins and start
working on these. Is this reasonable?
Cheers,
Ron Mertens.
P-Cube LTD.
On Tue, 13 Jan 2004 10:35:43 +0100, Tom Eicher <eclipse@tom.eicher.name>
wrote:
> Ron, I don't recommend writing everything from scratch. I just think
> that if you don't have too much experience with eclipse, its plug-in
> system and all, you might be better off to start with the "java editor
> example", which is a lot simpler than the full-blown java editor. It
> uses the same mechanisms though, so that doing so does not mean you
> cannot copy and adapt code from the java editor once you get your
> project rolling.
>
> But of course, all of this depends on your resources etc..
>
> HTH, Tom
>
> Ron Mertens wrote:
>> Thanks for your reply. Hmmm... So would you recommend writing the
>> editors and views from "scratch" rather than tweaking
>> the java code?
>>
>> Our problem is that we fear we will have to do a lot of work for
>> nothing - like building heirarchy trees, GUI, stuff like that. Can
>> these be somehow reused? After all, languages are pretty much the same,
>> we only change syntax (ours is pretty much like java in many cases) and
>> add our special features (and remove features not supported by our
>> language...).
>
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
|
|
| | |
Goto Forum:
Current Time: Mon May 12 16:56:01 EDT 2025
Powered by FUDForum. Page generated in 0.04193 seconds |
Home