[ANN] IdeaSpring 1.2.1
- Plugin is now commercial (see http://www.yanaware.com/ideaspring)
! All files with the xml type are accepted as config files (not only .xml files)
Bug Fix : init-method, destroy-method, replaced-method and lookup-method completion
! Beans imported by the import tag are now totally handled (was handled only in the browser)
+ Now the plugin verifies that idea-spring-parser.jar is in the lib directory
+ QuickFix : create a new bean from an unknown referenced one
+ Intention : converts full form of value and ref elements to shortcut form
+ Intention : converts shortcut form of value and ref elements to full form if the bean referenced is local
+ Refactoring : move bean
+ Refactoring : rename bean
+ Refactoring : rename alias
+ When you refactor a setter in a class the corresponding property in config files is renamed
+ Gutter Icons for classes injected into others (setters based)
+ Unknown class used in class attribute are now highlighted
+ Notation for inner classes is handled (MyClass$MyInnerClass)
+ Go to declaration for classes and setters
+ Property's name attribute validation
+ Error highlighting for bad bean references in properties
+ Error highlighting for constructors based on number of parameters
+ Error highlighting for bad methods (init-method, factory-method, ...)
+ Error highlighting for classes that are not concrete
+ SmartType completion for properties
+ Works in Demetra
+ Upgraded to SpringFramework 1.2.7
请先登录再写评论。
>>> Plugin is now commercial
Perfect - I won't use it any more :( !
Yes 50$ for such thing quite much...
If only not tech support question I think JB may support in some way plugin writers cause Spring support plugin is good extension(I wasn't used it much but think it is required).
Next commercial plugin will be StrutsAssistant I think.
Interesting how successful commercial extensions (not bridges for existing products but just extensions as products) for IDEA. SixAndRedRiver without doubt but others...
But JB must support plugin writers, may go Atlassian way with Codegeist competition?
Thanks,
Dmitry
Not must, but maybe a good motivation to bring up some cool things to implemented in IDEA, cos JB itself have no enouth time for many cool things available in space :)
>>> Next commercial plugin will be StrutsAssistant I think.
I think so too. What Idea lacks (a lot) is good native support for the most popular frameworks and tools (Struts, Spring, Hibernate, Maven etc.). That's why these plugins are so popular. If JB add such kind of support all of them will be off ... and I think they should, because the Eclipse users also pay for the valuable plugins, but they don't pay for the base, so loosing this battle, JB might start loosing the war.
If they want to have more plugins they MUST
Popular enough to use for free but if it will costs money most users will not buy them and will complaining about lack support of them in IDEA
I already do :)))
I'm not sure it is the right moment to make it commercial: it still is pretty buggy (although at least now it takes into account all the files I give it), and while I would be happy to help a free project with bug reports and so on, I won't spend a second doing quality assurance work for a commercial product that needs beta testing. I just opened my project and browsed through my spring beans, and in 10 seconds I found 2 bugs and a minor issue: this is not what would push me to spend 50€ * developer. Better luck next time (release).
In general, I do agree with all the people complaining or expressing woes about the state of the idea plugin ecosystem or the features found in IDEA. As of today, IDEA needs a profiler, and buying one would double the TCO of the IDE: if jetbrains think that the needs of enterprise developers may be satisfied by a number of 50€ plugins I think they are wrong. Should I buy Hibero + IdeaSpring + the various sixth and red river + future commercial versions of Struts Assistant + Tapidea + ... I would surely have an IDE better covering the technologies which we currently use and need, but at what cost, in terms of:
1) multiple points of support
2) license fee, both from a direct point of view and from an indirect one (provisioning management, etc.)
3) dubious quality if compared with a jetbrains product
I really think Jetbrains should come out with something different: I am not against paying additional fees for particular feature sets, but Jetbrains should endorse the plugins in a more direct way. What about sponsoring the plugin writers instead of leaving them on their own?
+ What about sponsoring the plugin writers instead of leaving them on their own? +
I for one would be happy if the OpenAPI was well documented and there were about 10 additional more complex sample plugins. I would be even more happy, if all questions in OpenAPI-forum would be answered by JB, the same goes for bug reports/OpenAPI feature requests in JIRA.
Let's hope DEMETRA finally reaches the standard plugin writers need to write more powerful plugins - without spending hours using JAD.
Btw, I'm sure someone will come up with another free Spring plugin - at least I hope so..
+1
So what would be a fair price ?
SpringIde is a (free) plugin for Eclipse, so it can't be considered as included in Eclipse.
Hibernator is too provided as a free plugin for Eclipse,
Spindel is provided as a free plugin for Eclipse, .....
So when you say that Eclipse users don't pay for, what you think is, the base you're right but because most popular frameworks are supported by FREE plugins.
It must be avoidable by most Spring users no concrete numbers unfortunately :(
affordable
Which means free ?
You said "50$ for such thing quite much..." so you must have an idea of THE good price haven't you ?
I think if you will set price to 20-30 you will have much more chances. I suggest you to contact companion program and ask what they think about your price. Your plugin looks similiar to Hibero so it may be used as start point.
Please look at the price of the Hibero plugin. http://www.betosoftware.com/hibero/buy.html
My bad may be 30 was price of SRRR plugins during action
It would be good to know how many licenses did they sell. In our case, we didn't buy the plugin mostly because it does not help with HQL, but also because we should buy 5 licenses. Let's put it this way: your plugin's cost is 1/10 of IDEA. I know one can't put it this way, but do you think it provides 1/10 of the value IDEA offers, or did you put 1/10 of the effort Jetbrains put in IDEA in it?
Believe it or not, we have strict budget requirements for development tools, here, and it would be impossible for us to go and ask every 3 weeks "I need 50$*5 for another plugin...". Personally, since I'm sure the product isn't tested enough I think you should at least offer a number of VERY low price licenses so that your first customers will (knowingly) be your beta testers. No more than 20€, though (let's say 19.99): this in my opinion is a much more fair price if compared with the rest of the tool.
You read my mind!!!
Maurice, our point not to reduce you revenue but increase number of copies sold believe me.
And try to ask Hibero authors how many copies they sold.
Thanks,
Dmitry
Dmitry,
It's not all about revenue...
At the beginning, I created this plugin for my own usage and then i decided to make it available to all. But it's a lot of work to maintain and to update a plugin so i need something to motivate me...
When i read messages like "It's commercial now, so perfect i won't use it anymore", it's comfort me in my decision to make it commercial.
Anyway thank you for the advice,
Maurice
Message was edited by:
Maurice Montgénie
Mentioned by you causes and lack of motivation was one of the reason of my PropertiesEditor plugin efforts termination (also as core properties files support) so I understand you. But 50$ price too high even for most SRRR plugins thought ;)
Thanks,
Dmitry
Davide,
This post is much more constructive than your precedent one.
Thank you for your opinion, i'll think about it.
In article <21047556.1144279020463.JavaMail.javamailuser@localhost>,
Maurice Montgénie <intellij@maguyane.net> wrote:
From where I sit, very few plugins are worth money as standalone
products. Plugins that are part of another piece of software tend to be
an easier sell. A product that is part of a profiler, say, lets me
point to the profiler's other benefits in my justification, so even an
IDEA-unsavvy manager can see the benefits.
With a plugin, he has to see the benefits in the IDE. Not impossible,
just a harder sell. That a plugin often costs a tenth what IDEA does
makes it harder. Again, not impossible, but harder.
Consider - I like JProfiler, and that it has IDEA integration adds.
Similarly, I have used Clover for various OS projects, and find the
plugin adds. When next I get a Spring or a Hibernate project, I would
certainly look at IDEASpring and Hibero, but they would have to add
enough to be worth me going to my management and asking for the money.
$10, $15, etc. are amounts I might pay out of my own pocket on a lark,
in hopes that they would help. $50 is getting to where I need to see
visible benefits first.
Scott
--
Scott Ellsworth
scott@alodar.nospam.com
Java and database consulting for the life sciences
Any chance to see support for Spring 2.0 in this plugin any time soon. It just doesn't work if the configuration files use the XML-Schema instead of the old DTD. Or at least autocompletion - the reason I downloaded it for - doesn't work
I will allow configuration files using XML-Schema in the next minor version but you won't have full support of Spring 2.0 in it. You'll have to wait a little bit for it.
Listening to davide and others i've decided to launch a limited time offer (which will last for months) for IdeaSpring.
You can now buy it for 30$ for a single license.
I hope that Davide and others will find that an acceptable price and will go for it.
Nice. I wouldn't expect support for the special aop and tx tags yet. Just the basic bean handling would do for a start.
Hi,
I started using the trial verion of IdeaSpring this week, and it is quite nice. However, I also started using Spring 2 M3. I'd really like to see Spring 2 features supported in a plug-in that I'm paying money for.
Having said that, I did buy Hibero already, and it is very nice. I like to support hard working plug-in authors if the price is reasonable.
I don't really spend a whole lot of time editing Spring and Hibernate files compared to, say, editing Java code. Given IDEA's basic Spring/Hibernate support, I guess it's debateable whether further support is really needed. The errors highlighted by Hibero and IdeaSpring are useful though.
Regards
John Hurst
Wellington, New Zealand
Ok, I started our provisioning process: I don't know if it will ever come to an end because our company policy mandates that we go through an external partner that manages all our software purchases. I should receive an offer from them and as soon as this happens you should receive an order .