Well, first of all Scala plugin is a joint JetBrains-"Scala-raving community" effort, so since some of us are doing the plugin work in our free time, it is very difficult to set the timeframes and expect releases in the fixed date. Having said that, the current work concentrates on working out the decompiler and repeating scalac when inferring types. Also since the development is in scala itself we are figuring out the IDE features that we miss in the process. You are most welcome to evaluate the plugin and feed us back with the features you find valuable and worth having.
Well, first of all Scala plugin is a joint JetBrains-"Scala-raving community" effort, so since some of us are doing the plugin work in our free time, it is very difficult to set the timeframes and expect releases in the fixed date. Having said that, the current work concentrates on working out the decompiler and repeating scalac when inferring types. Also since the development is in scala itself we are figuring out the IDE features that we miss in the process. You are most welcome to evaluate the plugin and feed us back with the features you find valuable and worth having.
Eugene.
Eugene, thanks for the answer. But I'm still in doubt :) A year ago the only thing has prevented me from buying a license (project files encoding hierachy subsystem absence), and now with 8.0 the problem has gone (great!). But during this period I have switched to Scala and already have a ~400KB of Scala code. It is difficult to switch without some kind of assurance (can not "play only" with the plugin at current state). And I don't say about rich features set (you have mentioned "features" twice :)), rather about stability (let those things we have to work).
Probably my case isn't unique, is it?
Is there a chance Scala support will be included in official IDEA development stream?
Hello anli, Unfortunately I cannot comment on scala plugin inclusion into IntelliJ IDEA development stream, since I'm not working for JetBrains now. However your remark on the minimal IDE support you want is really interesting. What do you mean by this minimum?
I keep getting confused by the JB icon next to your name in the forum. But you're no longer a JetBrains employee, right?
Anyway, I was wondering if the community effort status of the Scala plug-in means that it is open-source? How many people are currently working on it?
(And before you ask for help, I'm afraid I've yet to write more than a few lines of Scala and even they were just variations on examples from the Programming in Scala book and that furthermore I've never written or seen a line of IDEA plug-in code...)
Hello Randall, No, I'm not JetBrains employee anymore and the icon I suppose is just a leftover. The plugin is indeed opensource and AFAIK JetBrains really welcomes external contributions, though I should warn anyone that Scala is not even nearly as easy for writing the compiler as Java.
Hello anli, Unfortunately I cannot comment on scala plugin inclusion into IntelliJ IDEA development stream, since I'm not working for JetBrains now. However your remark on the minimal IDE support you want is really interesting. What do you mean by this minimum?
Eugene,
Heh, your question is rather difficult to answer :) Generally speaking, I mean - deferring a big part of refactoring patterns, all kinds of code autogeneration, autoimporting and other 'second level' sugars (and even "too smart" formatting), and - concentrating to already-existing bugs fixing.
You see, it is rather difficult to list a minimal set of features, especially when they all are in hand already.
Exact plugin development team described at . Now, our plans is to create scala plugin page with describing all known features (with them known bugs) and some kind of roadmap. Also I concentrating my attention to stabilization current features. But we will listen all recomendations for new features (applicable to scala, different to java).
Now, our plans is to create scala plugin page with describing all known features (with them known bugs) and some kind of roadmap. Also I concentrating my attention to stabilization current features. But we will listen all recomendations for new features (applicable to scala, different to java).
Thanks! Hope this page will be announced in Scala (EAP) forum.
Well, first of all Scala plugin is a joint JetBrains-"Scala-raving community" effort, so since some of us are doing the plugin work in our free time, it is very difficult to set the timeframes and expect releases in the fixed date. Having said that, the current work concentrates on working out the decompiler and repeating scalac when inferring types. Also since the development is in scala itself we are figuring out the IDE features that we miss in the process. You are most welcome to evaluate the plugin and feed us back with the features you find valuable and worth having.
Eugene.
Eugene, thanks for the answer. But I'm still in doubt :) A year ago the only thing has prevented me from buying a license (project files encoding hierachy subsystem absence), and now with 8.0 the problem has gone (great!). But during this period I have switched to Scala and already have a ~400KB of Scala code. It is difficult to switch without some kind of assurance (can not "play only" with the plugin at current state). And I don't say about rich features set (you have mentioned "features" twice :)), rather about stability (let those things we have to work).
Probably my case isn't unique, is it?
Is there a chance Scala support will be included in official IDEA development stream?
Hello anli,
Unfortunately I cannot comment on scala plugin inclusion into IntelliJ IDEA development stream, since I'm not working for JetBrains now. However your remark on the minimal IDE support you want is really interesting. What do you mean by this minimum?
Hello, Eugene,
I keep getting confused by the JB icon next to your name in the forum. But you're no longer a JetBrains employee, right?
Anyway, I was wondering if the community effort status of the Scala plug-in means that it is open-source? How many people are currently working on it?
(And before you ask for help, I'm afraid I've yet to write more than a few lines of Scala and even they were just variations on examples from the Programming in Scala book and that furthermore I've never written or seen a line of IDEA plug-in code...)
Randall Schulz
Hello Randall,
No, I'm not JetBrains employee anymore and the icon I suppose is just a leftover. The plugin is indeed opensource and AFAIK JetBrains really welcomes external contributions, though I should warn anyone that Scala is not even nearly as easy for writing the compiler as Java.
Eugene.
Eugene,
Heh, your question is rather difficult to answer :) Generally speaking, I mean
- deferring a big part of refactoring patterns, all kinds of code autogeneration, autoimporting and other 'second level' sugars (and even "too smart" formatting), and
- concentrating to already-existing bugs fixing.
You see, it is rather difficult to list a minimal set of features, especially when they all are in hand already.
Exact plugin development team described at .
Now, our plans is to create scala plugin page with describing all known features (with them known bugs) and some kind of roadmap. Also I concentrating my attention to stabilization current features. But we will listen all recomendations for new features (applicable to scala, different to java).
>...
Thanks! Hope this page will be announced in Scala (EAP) forum.
Of course it will be announced.