Sunday Nov 09, 2008
Scala for NetBeans Screenshot#15: Twilight Color Theme
>>>Updated Nov 11:
Emacs Standard color theme already be there.
======
I'm beginning to write some real thing based on Liftweb. The more code I wrote, the more bugs of Scala plugin were fixed.
Not only bugs are being fixed, I also created a Twilight color theme for this plugin. And an Emacs color theme is also on the road.
When NetBeans 6.5 is official released, I'll put a new Scala plugin too.
Click on the picture to enlarge it
Posted at 10:28PM Nov 09, 2008 by dcaoyuan in NetBeans | Comments[9]
Thank you! I have a preference for dark color themes. Thank you for all of your netbeans + scala work.
Posted by Bryan on November 10, 2008 at 12:16 AM PST #
It looks great, but I would like to know when will you release it.
Thanks for your great work with scala plugin.
Posted by Jesus on November 10, 2008 at 12:55 PM PST #
I've just read that you'll be releasing a new plugin when Netbeans 6.5 is officially out.
Sorry for my english, and thanks.
Posted by Jesus on November 10, 2008 at 12:59 PM PST #
I discovered a bug in syntax coloring:
Settings for "mod-global" are not saved or loaded properly (changes are lost on Netbeans restart).
Posted by boris_kolar on November 11, 2008 at 10:47 AM PST #
Good work on the plugin. Just noticed on the netbeans/scala wiki that mixing java & scala projects is to come once 2.7.2 is released. Now the 2.7.2final has been released, any chance this can be added? Would make things a bit easier for me:-)
Thanks!
Posted by Graham on November 16, 2008 at 12:15 PM PST #
Graham,
No for current version. Mix java/scala for ant building is not so hard, but to support mixed project in IDE, for example, code-completion between them is another story.
I'm going to rewrite Scala plugin in Scala itself gradually. So, no innovation will happen recently.
Posted by Caoyuan on November 18, 2008 at 05:47 PM PST #
Hi Caoyuan,
Thanks for your reply. I've since moved to having my Java GUI code in one project, the main project, while keeping the Scala code in a separate project. Would this be easier to implement, or does it present the same problems?
Cheers
g
Posted by Graham on November 18, 2008 at 10:26 PM PST #
Graham,
Separating Java, Scala projects to different project is the best way in my opinion. NetBeans with Scala plugin can handle these dependencies via project's "library" setting. The building process can handle this situation automatically, except sometimes, the code-completion across these projects' may not reflect the source changes immediately, you may need to re-start Netbeans (This will be fixed in the future)
Posted by Caoyuan on November 19, 2008 at 08:14 AM PST #
I'm seen more problems than that.
Create a Scala class library project and create a class called TestClass in package 'xxx' with a simple method to output some text.
Create a Java application project. In the view class, try to import xxx.TestClass and build - an error will be reported. Also, if you try to add the library jar directly (as a jar rather than as a project), you can't view the contents of the jar, even although they look fine when viewed with javap.
Netbeans doesn't seem to be able to handle the scala-built class. Is this my problem (I'm relatively inexperienced with Scala although have used Java for years) or a problem with Scala/Netbeans/the plugin?
Thanks!
Posted by Graham on November 19, 2008 at 07:11 PM PST #