Since the WL-Plugin was again mentioned several times, let me take the opportunity to say a few words.
The WL-Plugin is the Mathematica Plugin for IntelliJ IDEA and you can find the first announcement on stackexchange here, the initial post in the community here, a detailed description of new features here and the source-code here. As already pointed out the WL-Plugin does indeed support all of the syntax additions that were introduced with the release of Mathematica version 10.0. Prominent examples are the Association
brackets <|
|>
or for instance RightComposition
operator /*
.
If you are new to the WL-Plugin or even if you have used it for a while, I strongly encourage you to read the article How to use IDEA effectively with Mathematica code that I published some weeks ago. I know that all the features of IDEA can be a bit overwhelming at first, especially for users that just want to start right away, but the IDE is so powerful that you should invest a small amount of time to get to know the most important things.
Last night I added autocompletion and the documentation-lookup for all new built-in functions in version 10. Furthermore, I added the new file-extensions *.wl
and *.wlt
so that they are recognised by the WL-Plugin. Together with some minor bug-fixes this will be released in the next week and everyone should get the update-notice automatically through IDEA.
Furthermore, let me respond to this
I hope that the debugger will be implemented soon
I know that there are 4 major things missing in the WL-Plugin: Debugging, Profiling, Documentation-Building and Unit-Testing. What you have to understand is that e.g. the Documentation-Building functionality is part of the WB and not openly accessible through Mathematica. I cannot just use what the WB provides and publish it in an open-source project. A few users might have noticed that the documentation files that come with the WL-Plugin have a different license. I am very grateful that WRI allowed me to use this information but as well as everything that comes with WB, this is property of WRI and I cannot simply copy it into the plugin by re-engineering.
Debugging and Profiling are probably a bit different because this functionality is available in Mathematica too and what I would have to do is to implement a working interface for it: Setting breakpoints in IDEA, controlling execution, etc.. One big hindrance here is that I rarely (in other words never) use these features myself and Im not very much experienced with it. Therefore, it would need some time so that I can look at these things.
Unit-Testing is now, in version 10, available in Mathematica too, where in former times it was hidden in WB as secret package and was loaded on demand. Now, it is theoretically easily possible to support this in the WL-Plugin.
I'm willing to pay for help to the programmer in order to speed development!
Currently, the limiting factor is time. Im doing this completely in my free-time and the WL-Plugin is only one of my hobbies. What is interesting and important to me is: how large is the user-base of the WL-Plugin? As you can surely imagine, it makes a difference whether your software is used by 3 or by 300 people, especially when you have to decide what you do with your time.
So what you as users can do is
- Subscribe to the mailing list so that I (and only I) can see how many active users we have. Additionally, I have a way to keep you informed.
- Report bugs or make feature requests in the issue tracker. Look for instance at this issue. I doesnt always has to be a strict bug-report. Here I see how people are using the plugin an what they want.
- Tell your friends and colleagues about the WL-Plugin! Just spread it to all people you think could be interested.
- Make sure that I know about things the happen around the plugin. For instance, I only saw this question because someone else pointed me to it.
If you need to get in touch with, now you know who this programmer is. It is this guy in the Wolfram Community and this guy at stack exchange.