not to extent I'd like it to work. I tried it several times and several times switched back to Idea default keyboard. It broke a few times with Idea upgrade, was unavailable for some version in the past for quite a bit of time, so I have to tune up my mind to a totally different way of communicating with the IDE going back to the default, that's very counterproductive. Also, the VIM keyboard is laid out in a way that makes interaction with version control and the debugger painful a bit; if I change the keyboard layout to make it more comfortable then I face another upgrade problem: Idea has not been particularly spectacular in ex/importing my settings to the new version: I lost my keyboard layouts a few times while upgrading, and retuning the keyboard layout again by hand takes too much time and frustration. I could live with it if there was a guarantee that the VIM plugin does not break with the next upgrade, but this would be only possible if it was a part of your QA process which means JetBrains taking over it... Yet another problem is composite keystrokes (such as Shift+Alt) via VNC which I have to use quite often...
1. Mylyn equivalent - a port would be nice. 2. Stability, speed, bugs fixed 3. Multilanguage resource properties editing (this was introduced in 6 where it was very buggy but still very useful and pulled from 7)
Mylin is a big workaround for the mess that's an Eclipse workspace. I believe IDEA already has something that covers most of the good functionality in Mylin without all the complexity: changesets.
Mylin is a big workaround for the mess that's an Eclipse workspace. I believe IDEA already has something that covers most of the good functionality in Mylin without all the complexity: changesets.
I love changesets, but I wish they were more persistent. What I'd like to see is an easy way to convert/add a changeset to a favorites list on commit. That way I can easily keep a record of all of the files that have been touched for each project.
Unfortunately, this is hard to sell. Maybe it would make sense to think about two IDEA development lines, one for stability and bugs fixed (LTS ... long term support) and one for features?
Unfortunately, this is hard to sell. Maybe it would make sense to think about two IDEA development lines, one for stability and bugs fixed (LTS ... long term support) and one for features?
Sure it does make sense. The line for stability and bug fixes is called IDEA 8.1.x, and the line for features is called IDEA 9.
-- Dmitry Jemerov Development Lead JetBrains, Inc. http://www.jetbrains.com/ "Develop with Pleasure!"
Unfortunately, this is hard to sell. Maybe it would make sense to think about two IDEA development lines, one for stability and bugs fixed (LTS ... long term support) and one for features?
Sure it does make sense. The line for stability and bug fixes is called IDEA 8.1.x, and the line for features is called IDEA 9.
-- Dmitry Jemerov Development Lead JetBrains, Inc. http://www.jetbrains.com/ "Develop with Pleasure!"
I think the underlying message here is that people are feeling that not enough bugs are getting addressed. We are certainly appreciative of those that have been fixed in 8.0 and 8.1, and the ones that will be fixed in the 8.1.x line. But there are a lot of open bugs in JIRA, many of which were opened under IDEA 5, 6 or 7, that still exist in 8. That is frustrating since we all love IDEA otherwise. I think that is the sentiment of some of the above posts and some of the other posts in these forums. We understand new features are important to keep IDEA competitive, to not lose market share, and to gain new market share. But so is a stable and bug free product. IDEA has a lot of evangelical users. A powerful marketing and sales force. But it risks losing those valuable users if they end up only liking (or hating) IDEA rather than loving it. And I really think that has already started to happen based on what I have been reading in the forums. Please note that this post isn't meant to be critical of JetBrains and your efforts... just as some input into how a typical IDEA user feels about the conversation at hand.
I think the underlying message here is that people are feeling that not enough bugs are getting addressed. We are certainly appreciative of those that have been fixed in 8.0 and 8.1, and the ones that will be fixed in the 8.1.x line. But there are a lot of open bugs in JIRA, many of which were ope ned under IDEA 5, 6 or 7, that still exist in 8. That is frustrating since we all love IDEA otherwise. I think that is the sentiment of some of the above posts and some of the other posts in these forums. We understand new features are important to keep IDEA competitive, to not lose market share, an d to gain new market share. But so is a stable and bug free product. IDEA has a lot of evangelical users. A powerful marketing and sales force. But it risks losing those valuable users if they end up only liking (or hating) IDEA rather than loving it. And I really think that has already started to h appen based on what I have been reading in the forums. Please note that this post isn't meant to be critical of JetBrains and your efforts... just as some input into how a typical IDEA user feels about the conversation at hand.
I could not have written it better. But this issue comes up each new year and nothing happened in the last years, so why should it be better this one?
>> I think the underlying message here is that people are feeling that >> not enough bugs are getting addressed. We are certainly appreciative >> of those that have been fixed in 8.0 and 8.1, and the ones that will >> be fixed in the 8.1.x line. But there are a lot of open bugs in >> JIRA, many of which were ope ned under IDEA 5, 6 or 7, that still >> exist in 8. That is frustrating since we all love IDEA otherwise. I >> think that is the sentiment of some of the above posts and some of >> the other posts in these forums. We understand new features are >> important to keep IDEA competitive, to not lose market share, an d to >> gain new market share. But so is a stable and bug free product. IDEA >> has a lot of evangelical users. A powerful marketing and sales force. >> But it risks losing those valuable users if they end up only liking >> (or hating) IDEA rather than loving it. And I really think that has >> already started to h appen based on what I have been reading in the >> forums. Please note that this post isn't meant to be critical of >> JetBrains and your efforts... just as some input into how a typical >> IDEA user feels about the conversation at hand. >>
I could not have written it better. But this issue comes up each new year and nothing happened in the last years, so why should it be better this one?
Well, sorry, but what do you expect to have happened? A release of IntelliJ IDEA with zero open bugs in JIRA? This is not going to happen ever, I'm afraid.
We don't see any correlation between this "issue" coming up and the actual quality of each version we release or the amount of post-release bugfixing and improvements that we do.
What is actually helpful us is bringing up specific issues that affect your day-to-day work, either by posting a thread here or by commenting on an issue in JIRA. Doing so significantly increases the chances of the issue getting addressed.
-- Dmitry Jemerov Development Lead JetBrains, Inc. http://www.jetbrains.com/ "Develop with Pleasure!"
Indeed, being bug-free is an illusion for any product except the very-very simple.
I can not resist to put a little weight on the other side of the scales of the above discussion:
My day-to-day experience is that IDEA is extremely stable. I use the EAP release for plain java development and I can hardly remember a real crash. The one I do remember was rather hairy and was solved fairly quick. Ok, I get some popups of stack traces occasionally (80% of the time from plugins) but IDEA seems to magically recover from those all the time. I realy can not remember an occasion where I needed to stop developing because of some bug in IDEA. When I compare the stability and speed of IDEA to that of for example, eh...., eclipse, there can just be one winner: IDEA.
Using IDEA mainly for plain java development and not for the pletora of other languages, might have biased my oppinion.
On topic now:
One enhancement pops up in my mind: When adding custom items to the GUI painter palette it would be nice if my custom setters would be recognized and added to the properties pane of the gui painter.
-Tom
P.S. please don''t stop fixing bugs or boosting speed
My wish? A redesigned UI. The IntelliJ editor is awesome. The rest of the UI is mediocre to bad. It's become weighted down by feature upon feature. Some serious thinking needs to be done about how to structure the functionality so it isn't overwhelming, klunky and hard to deal with. Even the JetBrains blog entries talk about how features are hard to find. The preferences dialog is mammoth. The source control menus are baroque. I lose track of features and then find them again later. So that's my wish.
I liked the 8.x development. 8.1 is very stable and usable (8.0 wasn't for me). If Jetbrains will continue to improve performance and stability then more features are great
I think the features are great and I love all the small things I can do which improve the workflow so much. But on the other hand the small problems like the focus-bug really get on the nerves during development and turn the extraordinary IDE into just an ordinary one. Maybe the 10 most hated / most voted for bugs could be fixed in each major release?
I'm still eagerly waiting for the backport of the focus-bug - this one will improve IntelliJ a lot
In 8.x there are some issues with memory and performance. For example the flex plugin seems to use an extraordinary amount of memory compared to the Java only projects. And it always parses things on project load. And for some reason code completion seems to slow down as soon as the parser cache contains many libs / files, i.e. it's very fast after a cache reset and seems to slow down after a while here. But this is just my observation and it's hard to prove this, I think.
In next eap build you will have focus management fix backported and better Flex editing performance. We are looking for the feedback :)
wallaby.pouch wrote:
I liked the 8.x development. 8.1 is very stable and usable (8.0 wasn't for me). If Jetbrains will continue to improve performance and stability then more features are great
I think the features are great and I love all the small things I can do which improve the workflow so much. But on the other hand the small problems like the focus-bug really get on the nerves during development and turn the extraordinary IDE into just an ordinary one. Maybe the 10 most hated / most voted for bugs could be fixed in each major release?
I'm still eagerly waiting for the backport of the focus-bug - this one will improve IntelliJ a lot
In 8.x there are some issues with memory and performance. For example the flex plugin seems to use an extraordinary amount of memory compared to the Java only projects. And it always parses things on project load. And for some reason code completion seems to slow down as soon as the parser cache contains many libs / files, i.e. it's very fast after a cache reset and seems to slow down after a while here. But this is just my observation and it's hard to prove this, I think.
Hi, thank you for the reply. The support is another thing I like, most of the time important bugs get fixed quickly. I'll test the next eap and will post some feedback.
>Well, sorry, but what do you expect to have happened? A release of IntelliJ >IDEA with zero open bugs in JIRA? This is not going to happen ever, I'm afraid.
I've been mentioning this for years. There are bugs in JIRA that have been around forever. I've listed them in the past. I don't feel like going through JIRA yet again.
What is actually helpful us is bringing up specific issues that affect your day-to-day work, either by posting a thread here or by commenting on an issue in JIRA. Doing so significantly increases the chances of the issue getting addressed.
I always send bug reports using the automatic notification tool (unfortunately, I don't get updates via e-mail about the bug process) or by entering them in JIRA. Every bug I enter affects my day-to-day work, otherwise I would not have taken the time to enter them in JIRA. When I search all my reported bugs, 23 are reported as Unresolved. If you need some help to fix some issues, I'm willing to help. But saying we IDEA users should name our pressing bugs where your issue tracker is full of them (a quick search shows more than 8000!), seems a little bit weired to me.
Of course, no one expects a non-trivial software to be free of bugs. But a little bit more care from Jetbrain's side regarding the issues your users are reporting, would not hurt.
I agree with one of the users here - IDEA 8.1 is pretty stable. My environment is Ubuntu 8.04 (soon upgrading to 9.04), IDEA 8.1 (build 9732), dual core laptop with 2 GB main memory and Java 6. I've only been using IDEA for the past 8 months or so and can't comment on the earlier releases. The speed difference between IDEA 7 and IDEA 8.1 is terrific, but I've also jacked up my heap size and maxperm size since I typically develop with Spring and Hibernate/JPA.
My wishes for IDEA 9
Speed (perhaps you can speed up classloading during startup or do lazy classloading).
Better wizards during project creation with good help
More stable plugins
A GUI designer for XHTML forms (MyEclipse provides this)
Being able to see a diagram of my Spring beans - especially how beans interplay with each other
Keep up the good work guys. I know that everyone is asking for their pet features, but it probably wouldn't hurt to look at some of the older bugs in JIRA and prioritze them.
Even though I've complained a lot recently, I want to say that IDEA is the best Java IDE available today. It has enhanced my working life immeasurably.
You can view a diagram of your spring beans. When viewing a spring config file in the editor, select the dependencies tab at the bottom. This provides a few graphical views (including picking up annotated beans).
I guess I wasn't looking hard enough. Yes - the Spring beans show up graphically when you click the Dependencies tab. I'm not sure how long this feature has been around, but great work, JetBrains and thanks, Charles.
I hope that IDEA 9 would be able to run JUnit tests in parallel, taking full advantage of multiple cores.
Especially when writing code with TDD, you need to run all the tests after every small change, many times per minute, so the speed of the tests is very important. If the unit tests would normally take 15 seconds to run on a single thread, it would be a very big productivity improvement if it would be possible run them in 2 or 1 seconds on a 8 or 16 core machine.
This should work for all normal JUnit 3 and JUnit 4 TestCase classes, as well as other frameworks whose test classes are marked with JUnit's org.junit.runner.RunWith annotation (for example http://www.jdave.org/ which I use).
The system could be implemented for example so, that IDEA takes a list of all test classes and partitions it to for example 4 parts when the CPU has 4 cores. Then it starts JUnit in 4 different threads (or JVMs) and in each of the threads it executes one fourth of all the test classes. (Using one JVM for each thread might make it easier to determine which console output came from which test. It would also protect the tests from some bad code which uses mutable static state.) IDEA should take into consideration that how long it takes to run each of the test classes, and try to partition them to the test runners to that each thread has about an equal amount of work.
Running the tests in parallel should be as simple as ticking a checkbox in the JUnit run configuration. Some optional parameters would be the number of threads to use (defaults to number of CPU cores). Also it might be good to be able to specify tests which are not side-effect-free and need to be run sequentially (they could be specified for example by listing class names or a class name pattern such as "*UnsafeTest").
Should I file a JIRA issue, or is there already one?
I think you should add android support as android is so popular right now.Although there is a plugin for android,it seems not response quickly for some bugs.
hope it will sport built-in VIM support for us old timer VIM addicts (and a kitchen sink is missing too)
Hello Vincent,
We hope to publish the roadmap during the next 2-3 weeks. For the EAP release,
there's not enough interesting new stuff implemented yet. :)
--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"
Hello Michael,
Doesn't the IdeaVIM plugin work for you? We don't have any plans to bundle
it, but I think it works well enough as it is now.
--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"
Thanks!
I hope IDEA9 support different font setting for different language in editor！
Hello Vincent,
We don't have any such plans.
--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"
not to extent I'd like it to work. I tried it several times and several times switched back to Idea default keyboard. It broke a few times with Idea upgrade, was unavailable for some version in the past for quite a bit of time, so I have to tune up my mind to a totally different way of communicating with the IDE going back to the default, that's very counterproductive. Also, the VIM keyboard is laid out in a way that makes interaction with version control and the debugger painful a bit; if I change the keyboard layout to make it more comfortable then I face another upgrade problem: Idea has not been particularly spectacular in ex/importing my settings to the new version: I lost my keyboard layouts a few times while upgrading, and retuning the keyboard layout again by hand takes too much time and frustration. I could live with it if there was a guarantee that the VIM plugin does not break with the next upgrade, but this would be only possible if it was a part of your QA process which means JetBrains taking over it... Yet another problem is composite keystrokes (such as Shift+Alt) via VNC which I have to use quite often...
I have 3 big wishes
1. Mylyn equivalent - a port would be nice.
2. Stability, speed, bugs fixed
3. Multilanguage resource properties editing (this was introduced in 6 where it was very buggy but still very useful and pulled from 7)
Keep up the good work, Jetbrains.....
Mylin is a big workaround for the mess that's an Eclipse workspace. I believe IDEA already has something that covers most of the good functionality in Mylin without all the complexity: changesets.
I love changesets, but I wish they were more persistent. What I'd like to see is an easy way to convert/add a changeset to a favorites list on commit. That way I can easily keep a record of all of the files that have been touched for each project.
@IntelliJ DEV Team
Any plans for JavaFX and JSR 286-Portlets?
Agreeing with Danskal and then some... My big 3 wishes:
1. Stability, speed, bugs fixed
2. Stability, speed, bugs fixed
3. Stability, speed, bugs fixed
And, if you have time:
Stability, speed, bugs fixed
Unfortunately, this is hard to sell. Maybe it would make sense to think
about two IDEA development lines, one for stability and bugs fixed (LTS ...
long term support) and one for features?
Hello Tom,
Sure it does make sense. The line for stability and bug fixes is called IDEA
8.1.x, and the line for features is called IDEA 9.
--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"
Hello Dmitry,
I think the underlying message here is that people are feeling that not enough bugs are getting addressed. We are certainly appreciative of those that have been fixed in 8.0 and 8.1, and the ones that will be fixed in the 8.1.x line. But there are a lot of open bugs in JIRA, many of which were opened under IDEA 5, 6 or 7, that still exist in 8. That is frustrating since we all love IDEA otherwise. I think that is the sentiment of some of the above posts and some of the other posts in these forums. We understand new features are important to keep IDEA competitive, to not lose market share, and to gain new market share. But so is a stable and bug free product. IDEA has a lot of evangelical users. A powerful marketing and sales force. But it risks losing those valuable users if they end up only liking (or hating) IDEA rather than loving it. And I really think that has already started to happen based on what I have been reading in the forums. Please note that this post isn't meant to be critical of JetBrains and your efforts... just as some input into how a typical IDEA user feels about the conversation at hand.
Thanks.
I could not have written it better. But this issue comes up each new year
and nothing happened in the last years, so why should it be better this one?
Tom
Hello Tom,
>> I think the underlying message here is that people are feeling that
>> not enough bugs are getting addressed. We are certainly appreciative
>> of those that have been fixed in 8.0 and 8.1, and the ones that will
>> be fixed in the 8.1.x line. But there are a lot of open bugs in
>> JIRA, many of which were ope ned under IDEA 5, 6 or 7, that still
>> exist in 8. That is frustrating since we all love IDEA otherwise. I
>> think that is the sentiment of some of the above posts and some of
>> the other posts in these forums. We understand new features are
>> important to keep IDEA competitive, to not lose market share, an d to
>> gain new market share. But so is a stable and bug free product. IDEA
>> has a lot of evangelical users. A powerful marketing and sales force.
>> But it risks losing those valuable users if they end up only liking
>> (or hating) IDEA rather than loving it. And I really think that has
>> already started to h appen based on what I have been reading in the
>> forums. Please note that this post isn't meant to be critical of
>> JetBrains and your efforts... just as some input into how a typical
>> IDEA user feels about the conversation at hand.
>>
Well, sorry, but what do you expect to have happened? A release of IntelliJ
IDEA with zero open bugs in JIRA? This is not going to happen ever, I'm afraid.
We don't see any correlation between this "issue" coming up and the actual
quality of each version we release or the amount of post-release bugfixing
and improvements that we do.
What is actually helpful us is bringing up specific issues that affect your
day-to-day work, either by posting a thread here or by commenting on an issue
in JIRA. Doing so significantly increases the chances of the issue getting
addressed.
--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"
Indeed, being bug-free is an illusion for any product except the very-very simple.
I can not resist to put a little weight on the other side of the scales of the above discussion:
My day-to-day experience is that IDEA is extremely stable. I use the EAP release for plain java development and I can hardly remember a real crash. The one I do remember was rather hairy and was solved fairly quick. Ok, I get some popups of stack traces occasionally (80% of the time from plugins) but IDEA seems to magically recover from those all the time. I realy can not remember an occasion where I needed to stop developing because of some bug in IDEA. When I compare the stability and speed of IDEA to that of for example, eh...., eclipse, there can just be one winner: IDEA.
Using IDEA mainly for plain java development and not for the pletora of other languages, might have biased my oppinion.
On topic now:
One enhancement pops up in my mind: When adding custom items to the GUI painter palette it would be nice if my custom setters would be recognized and added to the properties pane of the gui painter.
-Tom
P.S. please don''t stop fixing bugs or boosting speed
My wish? A redesigned UI. The IntelliJ editor is awesome. The rest of the UI is mediocre to bad. It's become weighted down by feature upon feature. Some serious thinking needs to be done about how to structure the functionality so it isn't overwhelming, klunky and hard to deal with. Even the JetBrains blog entries talk about how features are hard to find. The preferences dialog is mammoth. The source control menus are baroque. I lose track of features and then find them again later. So that's my wish.
Simpler. Easier. Organized.
I liked the 8.x development. 8.1 is very stable and usable (8.0 wasn't for me). If Jetbrains will continue to improve performance and stability then more features are great
I think the features are great and I love all the small things I can do which improve the workflow so much. But on the other hand the small problems like the focus-bug really get on the nerves during development and turn the extraordinary IDE into just an ordinary one.
Maybe the 10 most hated / most voted for bugs could be fixed in each major release?
I'm still eagerly waiting for the backport of the focus-bug - this one will improve IntelliJ a lot
In 8.x there are some issues with memory and performance. For example the flex plugin seems to use an extraordinary amount of memory compared to the Java only projects. And it always parses things on project load.
And for some reason code completion seems to slow down as soon as the parser cache contains many libs / files, i.e. it's very fast after a cache reset and seems to slow down after a while here. But this is just my observation and it's hard to prove this, I think.
In next eap build you will have focus management fix backported and
better Flex editing performance. We are looking for the feedback :)
wallaby.pouch wrote:
--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"
Hi,
thank you for the reply. The support is another thing I like, most of the time important bugs get fixed quickly.
I'll test the next eap and will post some feedback.
>Well, sorry, but what do you expect to have happened? A release of IntelliJ
>IDEA with zero open bugs in JIRA? This is not going to happen ever, I'm afraid.
I've been mentioning this for years. There are bugs in JIRA that have been around forever. I've listed them in the past. I don't feel like going through JIRA yet again.
I always send bug reports using the automatic notification tool
(unfortunately, I don't get updates via e-mail about the bug process) or by
entering them in JIRA. Every bug I enter affects my day-to-day work,
otherwise I would not have taken the time to enter them in JIRA. When I
search all my reported bugs, 23 are reported as Unresolved. If you need some
help to fix some issues, I'm willing to help. But saying we IDEA users
should name our pressing bugs where your issue tracker is full of them (a
quick search shows more than 8000!), seems a little bit weired to me.
Of course, no one expects a non-trivial software to be free of bugs. But a
little bit more care from Jetbrain's side regarding the issues your users
are reporting, would not hurt.
--
Best regards,
Thomas Singer
I agree with one of the users here - IDEA 8.1 is pretty stable. My environment is Ubuntu 8.04 (soon upgrading to 9.04), IDEA 8.1 (build 9732), dual core laptop with 2 GB main memory and Java 6. I've only been using IDEA for the past 8 months or so and can't comment on the earlier releases. The speed difference between IDEA 7 and IDEA 8.1 is terrific, but I've also jacked up my heap size and maxperm size since I typically develop with Spring and Hibernate/JPA.
My wishes for IDEA 9
Keep up the good work guys. I know that everyone is asking for their pet features, but it probably wouldn't hurt to look at some of the older bugs in JIRA and prioritze them.
Even though I've complained a lot recently, I want to say that IDEA is the best Java IDE available today. It has enhanced my working life immeasurably.
You can view a diagram of your spring beans. When viewing a spring config file in the editor, select the dependencies tab at the bottom. This provides a few graphical views (including picking up annotated beans).
I guess I wasn't looking hard enough . Yes - the Spring beans show up graphically when you click the Dependencies tab. I'm not sure how long this feature has been around, but great work, JetBrains and thanks, Charles.
I hope that IDEA 9 would be able to run JUnit tests in parallel, taking
full advantage of multiple cores.
Especially when writing code with TDD, you need to run all the tests
after every small change, many times per minute, so the speed of the
tests is very important. If the unit tests would normally take 15
seconds to run on a single thread, it would be a very big productivity
improvement if it would be possible run them in 2 or 1 seconds on a 8 or
16 core machine.
This should work for all normal JUnit 3 and JUnit 4 TestCase classes, as
well as other frameworks whose test classes are marked with JUnit's
org.junit.runner.RunWith annotation (for example http://www.jdave.org/
which I use).
The system could be implemented for example so, that IDEA takes a list
of all test classes and partitions it to for example 4 parts when the
CPU has 4 cores. Then it starts JUnit in 4 different threads (or JVMs)
and in each of the threads it executes one fourth of all the test
classes. (Using one JVM for each thread might make it easier to
determine which console output came from which test. It would also
protect the tests from some bad code which uses mutable static state.)
IDEA should take into consideration that how long it takes to run each
of the test classes, and try to partition them to the test runners to
that each thread has about an equal amount of work.
Running the tests in parallel should be as simple as ticking a checkbox
in the JUnit run configuration. Some optional parameters would be the
number of threads to use (defaults to number of CPU cores). Also it
might be good to be able to specify tests which are not side-effect-free
and need to be run sequentially (they could be specified for example by
listing class names or a class name pattern such as "*UnsafeTest").
Should I file a JIRA issue, or is there already one?
--
Esko Luontola
www.orfjackal.net
I think you should add android support as android is so popular right now.Although there is a plugin for android,it seems not response quickly for some bugs.