| [TCS] registering PDL extensions [message #21352] |
Wed, 13 August 2008 06:51  |
Eclipse User |
|
|
|
I have a TCS project for a PDL with the extension ext. In the
workspace with my TCS project, ext is registered in someway
so that files with the extension ext are edited in the TGE
editor and an outline view of the file is available; great.
I'm now trying to support processing of my PDL with a couple
of plugins that I've written. Using these I have a builder that
process an ext file when it is saved. However, when testing the
plugin in a runtime workspace, I've noticed that files with the
ext extension are not associated with the TGE editor and no
outline view of the file is available.
What do I need to do to get an automatic association of the
ext extension with the TGE editor in a runtime workspace?
thanks
Andy.
--
-- ------------------------------------------------------------ -------------
Dr Andy Carpenter
School of Computer Science,
University of Manchester, Manchester M13 9PL, UK
Email: Andy.Carpenter@manchester.ac.uk
Tel: +44 161 275 6168
Fax: +44 161 275 6280
|
|
|
| Re: [TCS] registering PDL extensions [message #21410 is a reply to message #21352] |
Thu, 14 August 2008 04:47  |
| Eclipse User |
|
|
|
I've discovered that the answer is the org.eclipse.gmt.tcs.metadata
plugin. This scans projects in the current workspace to see if they
are tcs language projects, it also provides the
org.eclipse.gmt.tcs.metadata.language extension point that a
plugin can used to register a tcs language. Registered languages
are associated with the TGE editor and an outline view of a file
is displayed.
It turns out that the latest version of the tcs builder can build a
plugin jar that includes a plugin.xml, that registers the language with
the extension point, and the resources needed to use the language.
I was working with an old tcs language project that did not include
the build property required to do this.
For registering a language in a runtime workspace I found that
using the tcs builder generated plugin did not produce a
convenient workflow. It was easier to convert my tcs language
project to a plugin project, make it dependent on
org.eclipse.gmt.tcs.metadata and manually configure the use
of the extension point.
Andy.
"Andy Carpenter" <Andy.Carpenter@manchester.ac.uk> wrote in message
news:g7uenb$pkq$1@build.eclipse.org...
>I have a TCS project for a PDL with the extension ext. In the
> workspace with my TCS project, ext is registered in someway
> so that files with the extension ext are edited in the TGE
> editor and an outline view of the file is available; great.
>
> I'm now trying to support processing of my PDL with a couple
> of plugins that I've written. Using these I have a builder that
> process an ext file when it is saved. However, when testing the
> plugin in a runtime workspace, I've noticed that files with the
> ext extension are not associated with the TGE editor and no
> outline view of the file is available.
>
> What do I need to do to get an automatic association of the
> ext extension with the TGE editor in a runtime workspace?
>
> thanks
> Andy.
>
>
> --
> -- ------------------------------------------------------------ -------------
> Dr Andy Carpenter
> School of Computer Science,
> University of Manchester, Manchester M13 9PL, UK
> Email: Andy.Carpenter@manchester.ac.uk
> Tel: +44 161 275 6168
> Fax: +44 161 275 6280
>
|
|
|
| Re: [TCS] registering PDL extensions [message #21871 is a reply to message #21410] |
Tue, 14 October 2008 10:44 |
| Eclipse User |
|
|
|
Hi Andy,
I am glad to see that you found the answer.
Thanks for reporting this here, and do not hesitate to contribute such
information directly on the wiki :-).
Thanks,
Frédéric
Andy Carpenter a écrit :
> I've discovered that the answer is the org.eclipse.gmt.tcs.metadata
> plugin. This scans projects in the current workspace to see if they
> are tcs language projects, it also provides the
> org.eclipse.gmt.tcs.metadata.language extension point that a
> plugin can used to register a tcs language. Registered languages
> are associated with the TGE editor and an outline view of a file
> is displayed.
>
> It turns out that the latest version of the tcs builder can build a
> plugin jar that includes a plugin.xml, that registers the language with
> the extension point, and the resources needed to use the language.
> I was working with an old tcs language project that did not include
> the build property required to do this.
>
> For registering a language in a runtime workspace I found that
> using the tcs builder generated plugin did not produce a
> convenient workflow. It was easier to convert my tcs language
> project to a plugin project, make it dependent on
> org.eclipse.gmt.tcs.metadata and manually configure the use
> of the extension point.
>
> Andy.
>
> "Andy Carpenter" <Andy.Carpenter@manchester.ac.uk> wrote in message
> news:g7uenb$pkq$1@build.eclipse.org...
>> I have a TCS project for a PDL with the extension ext. In the
>> workspace with my TCS project, ext is registered in someway
>> so that files with the extension ext are edited in the TGE
>> editor and an outline view of the file is available; great.
>>
>> I'm now trying to support processing of my PDL with a couple
>> of plugins that I've written. Using these I have a builder that
>> process an ext file when it is saved. However, when testing the
>> plugin in a runtime workspace, I've noticed that files with the
>> ext extension are not associated with the TGE editor and no
>> outline view of the file is available.
>>
>> What do I need to do to get an automatic association of the
>> ext extension with the TGE editor in a runtime workspace?
>>
>> thanks
>> Andy.
>>
>>
>> --
>> -- ------------------------------------------------------------ -------------
>> Dr Andy Carpenter
>> School of Computer Science,
>> University of Manchester, Manchester M13 9PL, UK
>> Email: Andy.Carpenter@manchester.ac.uk
>> Tel: +44 161 275 6168
>> Fax: +44 161 275 6280
>>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.04979 seconds
Home