jEdit plugin best practise - jedit

Which plugin could be example of the best jEdit plugin? In terms of the code, the use of tests.
I've made Markdown plugin and want to update it. This plugin has no any tests and uses a singleton. Which plugin can I use as example?

I don't think there is an example of the "best" jEdit plugin.
It always depends on what you try to implement how to do it.

Related

Is there a way to create my own ideavim plugin?

I would like to use with my emulated vim in jetbrain's IDE, some plugins that can be used with the original vim.
But as far as I know, only a small handful of plugins are compatible with ideaVim.
So I wonder how these plugins have been made, and if it is possible to make my own.
I can't find any documentation about such a thing on the internet.
Does somebody know?

How should I set up a web project using Kotlin on the back-end and in the browser?

If I wanted to build a website which used Kotlin both on the back-end, and in the browser - how would I set this up? Is there a Maven archetype or a Gradle template that captures best-practices for something like this?
The easiest way is to keep the modules separate, and I guess conceptually you'd probably want to do that also. While IntelliJ IDEA for instance doesn't natively support the ability to output to JS and JVM with Kotlin, in principle with Gradle/Maven you could. Here are instructions on targeting JVM and JavaScript for Gradle http://kotlinlang.org/docs/reference/using-gradle.html

Is there an easy way to use intellij for liferay theme development?

I recently switched from eclipse and netbeans to intellij, but I have also liferay stuff to do and intelliJ seems to lack a decent liferay integration.
Does someone know how to use intelliJ for that, with as much of intelliJs comfort as possible :-/
As the themes are no simple java project the import stuff doesn't seem to recognize it properly...
You could look into the maven integration for Liferay (depending on the version of Liferay you're using - the more recent the version, the better the maven integration) and just import a pure maven project. The layout of this differs a bit from the usual ant-based SDK.
But of course you can also use the pure Ant buildfiles you find in the plugins sdk. As there's typically no java in a theme, it doesn't make a lot of differences.
Not wanting to start IDE wars here, but you also might consider Liferay IDE (or Developer Studio, it's EE-Version) for theme-related development. As there's no Java development done in themes, the conflict of changing tools should be handleable. I wouldn't want to work in both IDEs for Java development again (been there, done that), but for themes I can imagine just going the easy route - it's mainly CSS that you edit.

Is there a good Rhino Javascript compiler available as Maven plug-in?

Commons JCI project doesn't seem to be maintained since a long time. Are there other options?
Maven does allow you to use Ant tasks using the AntRun plugin. So you could use the Mozilla compiler through an Ant task, such as this one. Not pretty, but I bet it will work.

favourite IDE for griffon development

I am experimenting with Groovy Griffon development and I am wondering what IDE to use.
I am trying to use NetBeans 6.5, and I found this post
https://blogs.oracle.com/geertjan/entry/notes_on_converting_netbeans_grails
essentially it describes forking the NetBeans trunk and hacking the Grails support; I was hoping for something more lightweight.
Are there any simple tools to create eclipse, netbeans or pom.xml's from Griffin Apps?
Or is it best to use a simple text editor?
There is a NetBeans Griffon plugin already available at http://plugins.netbeans.org/PluginPortal/faces/PluginDetailPage.jsp?pluginid=18664
Griffon apps have some rudimentry hooks already for IDE integration.
First, a .classpath and .project file are generated that mark the expected source and test directories for Eclipse. Both IntelliJ and NetBeans have importers for these eclipse files (and they work, I use them regularly).
Second, Griffon 0.1.1 adds more targets to the parallel build.xml so that more of the common scripts can be used as though they were ant tasks (run-app, compile, debug-app, etc.)
Third, there is some better IDE support in the works form some of the IDE vendors. As mentioned in the article you linked because Griffon is grails derived it is fairly easy to re-purpose existing Grails support. IntelliJ has the only specific tracked feature request I am aware of.
IntelliJ Idea has very good Griffon support.
This question usually comes with a next question:
How to debug Griffon?
Just in case someone still requires a helping hand trying to figure out how to debug Griffon in Eclipse/STS I've written a simple step by step guide to get it done:
http://ivo43.blogspot.com/2012/02/debugging-griffon-in-eclipsests.html
Hope it helps someone someday, :D
PD: I've tried Netbeans and even though it looks great am still with STS, call me a maniac!