Open Source hosting
0 views
Skip to first unread message
Pär Dahlberg
Jul 11, 2009, 11:52:54 PM7/11/09
to widget...@googlegroups.com
I'm considering either Google Code or Kenai for hosting my widgets.
Google, of course, would be nice since I already got an account and their mailing list/forum is good. That's what I've mostly been in contact with as a user.
Kenai on the other hand seems to have nice integration with NetBeans... at least that's what Sun is saying.
Anyone got any suggestions?
/M v h Pär
Welcome to my blog, mostly about programming: http://www.pmdit.se/blog
Google, of course, would be nice since I already got an account and their mailing list/forum is good. That's what I've mostly been in contact with as a user.
Kenai on the other hand seems to have nice integration with NetBeans... at least that's what Sun is saying.
Anyone got any suggestions?
/M v h Pär
Welcome to my blog, mostly about programming: http://www.pmdit.se/blog
krzysztof kula
Jul 12, 2009, 2:29:57 PM7/12/09
to widget...@googlegroups.com
I have didn't try Google, but Kenai is nice, and integration with NetBeans is true. You only need to write login and password in NetBeans. It have subversion, mercurial.... issue tracking systems, forums, wiki and all i one place. Try it and if it suks try google code ;)
Regards,
KrzychuKula
ps. There is also GitHub, CodeProject... ;)
Regards,
KrzychuKula
ps. There is also GitHub, CodeProject... ;)
2009/7/12 Pär Dahlberg <per.da...@gmail.com>
Stephen Chin
Jul 12, 2009, 6:16:47 PM7/12/09
to widget...@googlegroups.com
I have heard good things about Kenai. Google code has been serving us
well, and adding features to keep up with the competition (like new
Mercurial support).
Another option would be to open up the WidgetFX repository for folks to commit their open-source widgets to. It would be less overhead for folks, and if someone really wanted to make improvements to the core WidgetFX codebase that would be great as well.
Cheers,
--Steve
Another option would be to open up the WidgetFX repository for folks to commit their open-source widgets to. It would be less overhead for folks, and if someone really wanted to make improvements to the core WidgetFX codebase that would be great as well.
Cheers,
--Steve
--~--~---------~--~----~------------~-------~--~----~
WidgetFX Developers Group: http://groups.google.com/group/widgetfx-dev?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---
Pär Dahlberg
Jul 12, 2009, 9:19:28 PM7/12/09
to widget...@googlegroups.com
Thanks for the info both of you.
I must say that having open source widgets as part of the WidgetFX repository sounds interesting.
I must say that having open source widgets as part of the WidgetFX repository sounds interesting.
On Mon, Jul 13, 2009 at 00:16, Stephen Chin <st...@widgetfx.org> wrote:
I have heard good things about Kenai. Google code has been serving us well, and adding features to keep up with the competition (like new Mercurial support).
Another option would be to open up the WidgetFX repository for folks to commit their open-source widgets to. It would be less overhead for folks, and if someone really wanted to make improvements to the core WidgetFX codebase that would be great as well.
Cheers,
--Steve
On 7/12/2009 11:29 AM, krzysztof kula wrote:I have didn't try Google, but Kenai is nice, and integration with NetBeans is true. You only need to write login and password in NetBeans. It have subversion, mercurial.... issue tracking systems, forums, wiki and all i one place. Try it and if it suks try google code ;)
Regards,
KrzychuKula
ps. There is also GitHub, CodeProject... ;)
2009/7/12 Pär Dahlberg <per.da...@gmail.com>
I'm considering either Google Code or Kenai for hosting my widgets.
Google, of course, would be nice since I already got an account and their mailing list/forum is good. That's what I've mostly been in contact with as a user.
Kenai on the other hand seems to have nice integration with NetBeans... at least that's what Sun is saying.
Anyone got any suggestions?
/M v h Pär
Welcome to my blog, mostly about programming: http://www.pmdit.se/blog
Stephen Chin
Jul 14, 2009, 3:15:58 PM7/14/09
to widget...@googlegroups.com, widgetf...@googlegroups.com
Consider it done...
Feel free to check in your widget under trunk/widgets (you already have commit access, Pär):
http://code.google.com/p/widgetfx/source/browse/#svn/trunk/widgets
This is also an open invitation for anyone else who wants to open-source your widget and co-host it with the WidgetFX project on Google Code, let me know and I will set you up with committer access.
Cheers,
--Steve
Feel free to check in your widget under trunk/widgets (you already have commit access, Pär):
http://code.google.com/p/widgetfx/source/browse/#svn/trunk/widgets
This is also an open invitation for anyone else who wants to open-source your widget and co-host it with the WidgetFX project on Google Code, let me know and I will set you up with committer access.
Cheers,
--Steve
--~--~---------~--~----~------------~-------~--~----~
WidgetFX Developers Group: http://groups.google.com/group/widgetfx-dev?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---
Pär Dahlberg
Aug 3, 2009, 8:52:27 AM8/3/09
to widget...@googlegroups.com
Great!
I've been planning to break out the ImageEditor in ScreenshotFX to be able to reuse it for a clipboard widget. I guess there is no project dependency in the repository right? So I'll just commit the jar file for ImageEditor as a lib to the widget?
Next... even if it's not a widget, should I commit the ImageEditor project to the repository under the widgets directory?
I've been planning to break out the ImageEditor in ScreenshotFX to be able to reuse it for a clipboard widget. I guess there is no project dependency in the repository right? So I'll just commit the jar file for ImageEditor as a lib to the widget?
Next... even if it's not a widget, should I commit the ImageEditor project to the repository under the widgets directory?
Stephen Chin
Aug 3, 2009, 8:59:29 AM8/3/09
to widget...@googlegroups.com
Pär,
Your ImageEditor component seems like something that might be a better fit for the JFXtras project. I have taken a lot of the other interesting reusable stuff from WidgetFX and pushed it that direction so it gets more community adoption.
If that works for you, join up on the JFXtras mailing lists and drop an introductory e-mail on the dev list. I have already set you up with commit access to the repository:
http://code.google.com/p/jfxtras/
What you should probably do short term is package up a jar for your widgets to include. Once it makes it into a JFXtras build, then that automatically gets included with WidgetFX so you can drop the dependency altogether.
Cheers,
--Steve
Your ImageEditor component seems like something that might be a better fit for the JFXtras project. I have taken a lot of the other interesting reusable stuff from WidgetFX and pushed it that direction so it gets more community adoption.
If that works for you, join up on the JFXtras mailing lists and drop an introductory e-mail on the dev list. I have already set you up with commit access to the repository:
http://code.google.com/p/jfxtras/
What you should probably do short term is package up a jar for your widgets to include. Once it makes it into a JFXtras build, then that automatically gets included with WidgetFX so you can drop the dependency altogether.
Cheers,
--Steve
--~--~---------~--~----~------------~-------~--~----~
WidgetFX Developers Group: http://groups.google.com/group/widgetfx-dev?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---
Pär Dahlberg
Aug 3, 2009, 10:32:09 AM8/3/09
to widget...@googlegroups.com
Sure, that sounds good.
I guess that's a good enough reason for me not to postpone getting into the control+skin stuff as well as the unit tests :)
I guess that's a good enough reason for me not to postpone getting into the control+skin stuff as well as the unit tests :)
Reply all
Reply to author
Forward
0 new messages