support a new language, first questions

Hello ben,

Actually the JavaScript plugin already supports the ECMAscript syntax. You
don't need to write a new plugin for that.

The source code of the JavaScript plugin can be found in the plugin development
package. For historical reasons it's not stored in the Subversion repository.

I'm interested in supporting a new language for intellij. The syntax
of the target language is very similar to the syntax of ActionScript,
that is supported in the ECMAScript plugin. This is the reason because
I believe it could be feasable.
While the sources of latest language extensions (ruby, groovy) are
accessible, the sources of the JS plugin are not downloadable. Is that
correct? Is there a reason behind this?

Going through the language tutorial
http://www.jetbrains.com/idea/plugins/developing_custom_language_plugi
ns.html

I noticed, that this docs refer to intellij V. 5 and so do the example
sources. Is there a posibility to have some documentation that is more
actual?

regards
ben

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"

hi dmitry
thanks for your quick response.

can be found in the plugin development package

hmm... could you help me with an url? i can't find the "core module" on the plugin page, just some add-ons:

http://plugins.intellij.net/category/?category_id=50

regards
ben

Hello ben,

>> can be found in the plugin development package
>>

hmm... could you help me with an url? i can't find the "core module"
on the plugin page, just some add-ons:

http://www.jetbrains.com/idea/download/index.html#kit

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"

hi
thanks :)
Nice sdk - lots of materials! Before I dive in - just a small question. The target language has other file extensions (hx) and there a few minor differences in the syntax compared to actionscript. For ex:
- as: package my.pack{...
- hx: package my.pack;

is it still a better strategy to extend the existing js plugin than to build a new one (on the basis of the existing js plugin of course)?

regards
ben