James Harris - 2016-10-11

The news now is that a new Java version is coming up next year, where I will need to at least change Class Viewer from being a JApplet, which seems easy enough. Am thinking about other things as well where dawns on me, have downloads packaged always for NEW users, but app is over 12 years old now, so should I also be doing things to allow an upgrade? But not sure how, so looking to research.

But then for existing users next Class Viewer could have an upgrade option allowing you to just click a few things and get latest downloaded, with old replaced. As way I see it that's what the upgrade code would do, like just delete your old ClassViewer.jar and replace with new one? That's easy to do, but wondering.... Oh, and for ClassViewerConfig.xml could try to get fancier and only update changed areas. Those are the two main files so conceivably could be trivial, and kind of fun with the XML file to update them on the fly for users, but is there a need?

Am not interested in giving full edit capability for ClassViewerConfig.xml as seems like work for not much gain. Editing in a text editor is easy, and as Class Viewer is an app for developers I think is informative and a way to push XML as a cool format. So I don't want to hide it behind an interface which allows uers to not even see it. So some thoughts which seem good here. Talking things out helps me, even if don't get feedback. But also option FOR feedback IS here, and any thoughts or comments on these things would be very much appreciated.