OpenSource license 关注
Hi JetBrains
See this link for the OS version of IDEA:
http://www.jetbrains.com/idea/opensource/
Would you consider us plugin developers that have our plugin as open source project also?
We do have the www.intellij.org as our homesite (wiki) and the community is in these fourms and in the wiki.
Most times I develop the plugin using the EAP license but I can't keep my plugin bugfree/updated during the 'non EAP' periods.
/Claus
请先登录再写评论。
Hi Claus,
It is very good question. I have same question in my mind and want to
know the answer from JetBrain folks.
-Rambabu.
"Claus Ibsen" <cib_rejse@yahoo.dk> wrote in message
news:630473.1107962409233.JavaMail.itn@is.intellij.net...
>
>
source project also?
>
is in these fourms and in the wiki.
>
plugin bugfree/updated during the 'non EAP' periods.
>
:) Bad idea then everyone will write plugins for IDEA and nobody will pay for it if you want you may develop plugins for Eclipse it works as you described.
TIA,
Dmitry
Why is that a bad idea?
Isn't the point that IDEA will get more momentum if there were more (quality) plugins for their excellent editor?
And letting all the creative and talented developers sitting at big corporates and doing dummy code all day not being able to unfold their creativity writing plugins for their beloved IDE is just "bad idea" for my point of view.
What if Dave Gfiffin couldn't write his excellent IG plugin? If it wasn't free I bet nobody would pay for it. And it wouldn't have got such massive positive feedback.
Now its included in the core.
/Claus
Cause of "then everyone will write plugins for IDEA and nobody will pay for it" how to distinct plugin authors and license hunters?
TIA,
Dmitry
If you give it for free for Open Source Projects, then it only makes sense to give it free for IDEA Plugin Authors.
IDEA Plugins are also a Project in their own rights, and if its Open Source.. why not?
Ok if we measure "established, vital and active community" then it may be possible, but make it for ALL plugins doesn't make sense.
It's like the chicken and the egg.
1) People will know more about IDEA if it is used more.
2) It is used more if there are good and quality plugins.
Making plugins for IDEA must sure be in the interest of JetBrains.
Why not support the plugin writers that surely is more succesful than JetBrains could have imagined to start with. Writing plugins for IDEA is quite painful. The open API is porly documented, alot cant be done yet, the UI components cant be resued / hard to reuse etc. etc.
So what you are saying is that we should give up and write plugins for Eclipse? Since there is books about it, it was designed from start to be reused, support plugins etc. etc.
The only plugins that I know of that people pay for is "MyEclipse". So if there are less OS plugin writers for IDEA there would then be more attractive for companies to produce plugins for IDEA that people should pay for?
I double anyone would pay for some of the small nifty plugins for IDEA that exists now:
- reg.exp
- toString
- The dissasembler one, cant remember its name
- property editor
The only candiate to pay IMHO will be large plugins such as SQL browser, UML viewer, WebService Tester/Tool, Hibernate.
IDEA currently could have been more attractive if there were plugins for popular frameworks:
- Tapestry
- Spring
- Hibernate
- Struts
And the OS community could help if it was more easier to write plugins.
Hello Claus,
CI> What if Dave Gfiffin couldn't write his excellent IG plugin? If it
CI> wasn't free I bet nobody would pay for it. And it wouldn't have got
CI> such massive positive feedback.
Dave,
Now you "The Simple Monster Gfiffin" :)))
Thanks!
--
Alexey Efimov, Java Developer
Tops BI
http://www.topsbi.ru