Thursday, October 3, 2013

First LiClipse public release

The first LiClipse public release is now available!

It just came out of Alpha (when it was only available for supporters of the crowdfunding campaign that got the perks to use it before the public release).

Its homepage: has details on where to get it.

So, what do Eclipse users gain from it?

Well, there are 3 major features which I think make it very attractive:

1. Theming: LiClipse extends the features from Eclipse Color Theme to theme the whole IDE and not only the editors, so, dark themes look nice in the IDE.

2. Multiple region edition: The basic concept for this is already available on a number of editors when renaming with Ctrl+2, R, which links multiple regions with the same text for edition, but LiClipse takes this concept to the next level, enabling multiple areas to be selected and edited in various ways.

It's hard to explain it properly, so, I created video showing this feature (and the HTML editor): -- but be warned: after using it for a while, it can be really hard not having it anymore!

3. Support for multiple languages: Out of the box, LiClipse currently supports 10 different languages (CoffeScript, C++, CSS, Django Templates, HTML, JavaScript, Python, RST, SCSS and XML), but it should be easy to add support to new languages (by creating a proper .liclipse file and adding it to plugins\com.brainwy.liclipse.editor\languages, more details at:

Also, it's worth to note that it's HTML editor has gotten special attention so far and IMO it's already among the best editors for HTML (and the Django Templates inherits from it!).



  1. How about x86 Builds not only x86_64

  2. Hi Amin, x86 builds are still not available, so, you have to get Eclipse and install it as a regular plugin (see: for details on the steps to follow in this case).

  3. List of the supported languages on the LoClipse home page says CoffeScript while the language is CoffeeScript - double-'e' (have found the project while looking for coffeescript eclipse support).

  4. Hi Anli,

    Thanks for the heads up. I've fixed it here locally (will be updated on the next LiClipse release).