1.0 Status
1.0 is right around the corner, but a few things need to happen first. First off, IBM has responded to the long standing bug that would cause some progressive JPEGs to consume gobs and gobs of ram. This seems to have been fixed in the 3.2 SWT release but saving these images is still not supported. I’m in an ongoing discussion with someone at IBM to remedy this situation. The image saving problem only occurs if you re-size images before upload, and I have a workaround in place for this. I expect to have a resolution in the next week or so. If I end up using the SWT 3.2 API, you users will be in for a treat. All the image loading/resizing code is now native which results in a remarkable 4x speedup when dropping images into jUploadr. Woot!
Some users have already suggested ideas for the 1.1 release. So far, the only thing that’s certainly going to be in there is upload bandwidth throttling, but I’d love to hear where you think the user experience could be improved. I’ve had a suggestion to include a file browser, but personally, I think that jUploadr should stick to what it’s good at.
Any thoughts?
April 14th, 2006 at 1:28 am
I have more than one flickr account and am using your excellent jUploadr from a linux fedora 5 box. Is it possible to switch from an account to another. I didn’t manage to find how to do it.
Thanks
April 14th, 2006 at 7:59 am
Actually, there is no easy way to do this. You will have to go through authorization again each time you want to switch accounts. To reset your preferences, start jUploadr with the –reset-preferences option, and then re-authorize.
This seems like a useful feature, and two people have asked for it before, so I’ll probably include it in the 1.1 release. Go to the project site and add it as a feature request.