Skip to main content

Using move to clean up SwingLabs

10 replies [Last post]
kschaefe
Offline
Joined: 2006-06-08

We may decide to not migrate some projects to the new Kenai-based, java.net.  What projects are people using currently?

This is by no means a declaration that projects will not be moved, but more of a poll to gain an undestanding about which projects may be dead weight and we could afford not to move.

Karl

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
limo42
Offline
Joined: 2005-07-04

Please count this as a vote for swingx, swinghelper, and timingframework.
thanks,
-chris

kleopatra
Offline
Joined: 2003-06-11

okay, just looked at the list of sub-projects - we are not even owners of most of them ... don't know if we can request the move then?
Those I care about are: swingx, swinglabs-demos, jdnc-incubator, swingx-ws and databinding (both occasionally discussed here), jxlayer (stand-in for core 7 functionality).
Everything else could be left to their respective owners (or community leaders like Jeff :-). That or simply move all.
CU
Jeanette

kleopatra
Offline
Joined: 2003-06-11

overwhelming response <g>
Maybe we should do the other way round: same as on the site level migration, leave behind every project that doesn't opt-in ... Partly kidding as there is "old stuff" that's usable (like TimingFramework, f.i.) but unmaintained. We could opt for simply move all, least work for us.
Cheers, Jeanette

osbald
Offline
Joined: 2003-06-13

osbald
Offline
Joined: 2003-06-13

> overwhelming response <g>
Wasn't aware of the thread, seems the new java.net feeds are a bit wonky, last topic I can see from google reader is "How to display a txt db data in swing?" . Also note the new feed only includes new topics not new posts like the old one did, bit of a pain if anyone comments on an old topic. (wonky in that theyre very slow, seem to be too slow for google reader at any rate, just tested in the browser and it was only missing latest post, which was an old thread, doh!).
If the option is "if its not included - its deleted" I'd prefer to err on the side of caution and want to keep the code for several projects I've used. BeansBindings, AppFramework, SwingWorker & Swing-Layout I've used and are all still part of Netbeans so should be kept. Also used Wizard, JXLayer TimingFramework & transitions. Not sure what should be done over missing contributors / owners though. It'd still be important for some of my older projects to be able to checkout a 1.5 compatible version of SwingX, hopefully VCS history is being preserved?
Splitting Swing-WS up makes sense to me, rubbish name for a map view anyway. Did briefly wonder if the web client bit could be replaced by the newer Java based JavaFX 2.0 API, but then remembered we still cant ship JavaFX jars with our code so worth still worth keeping. PdfViewer & Flying Saucer might be worth keeping too, just off the top of my head. Shame they dont have a list of whats been request already and what are the most popular projects (downloads), honestly dont know where half the majority of libs Ive used are hosted.
Incubator is a bit of a nightmare, might want to tarball the lot & follow the same principal of asking people to migrate their bits to SwingX 1.6? much of the incubator uses all manner of SwingX versions, some really ancient ones.. I noticed this as IntelliJ IDEA unlike Eclipse is very fussy about code being at least compilable before it'll let you run anything. Hence the occational nagging.
Ugh, not liking this comment WYSIWYG widget much, is there a way to turn it off? (using source view still dosent allow browser spellchecking).

kschaefe
Offline
Joined: 2006-06-08

I was thinking we move the minimum necessary. Who uses Actions? Or Wizards? Or the original SAF? Etc.
Wd definitely need to move SwingLabs, SwingX, incubator (which should probably be reparented), and demos.
I'm torn on SwingX-WS; may be better to kill and move the only interesting piece (maps) into SwingX. Would only consider doing so (really), if we had volunteer support to handle the component.
Karl

niranaam
Offline
Joined: 2010-11-15

I think ALL SwingX projects should be moved. Even they're not maintained anymore, many developers use or used them.
There should be the possibility to access the sources/binaries/docs in the future.
"Who uses Actions? Or Wizards? Or the original SAF?"
Me! I used that stuff.
Marcus

kleopatra
Offline
Joined: 2003-06-11

we are listening :-) On the other hand - there's not sooo much we can actually _do_ about it: we (the currently most active committers and admins of SwingLabs related stuff) only have owner status for the core projects. So we're trying to push it up the line to get Alex (as master-owner of SwingLabs) and/or Jeff (as once/current? community leader) to push all of SwingLabs - at least that's my intention ;-)
Thanks for your input
Jeanette

kleopatra
Offline
Joined: 2003-06-11

I'm torn a bit - even is unused, it should be available somewhere. What's the procedure for unmoved projects? Are they archived somehow? Reparenting the incubator is a good-thing (does kenai infrastructure support subprojects?)
CU
Jeanette

kschaefe
Offline
Joined: 2006-06-08

Supposedly, there will be a tarball maintained of the data. Kind of tempted to say we provide the tarballs as downloads in SwingLabs as a way of maintaining archived projects.
Jeff asked Alex what should and should not be kept; I'm just pushing the question out to the community, which seems to be silent on the matter.
Karl