|
|
Recommended: Sing it, brah! 5 fabulous songs for developers
JW's Top 5
Featured White Papers
- Measuring Risk to Improve Java Software Quality
- Do You Really Get Classloaders?
- Pragmatic Continuous Delivery with Jenkins, Nexus, and LiveRebel
- Your Next Java Web App: Less XML, No Long Restarts, Fewer Hassles
- Coding with JRebel, Java Forever Changed
- 2012 Developer Productivity Report: Java Tools, Tech, Devs, and Data
Sponsored Links
-
Graph databases are 1000x faster than relational.
Learn More!
-
Career opportunities at Harman- Careers That'll Rock Your Socks Off.
Learn More!
-
Developer-friendly Java PDF libraries by Qoppa Software
Live Demos
-
Stop blaming your app! Diagnose Java performance issues.
Free tool >
-
UrbanCode: Go From Continuous Integration to
Continuous DeliveryLearn More!
Migrate legacy swing to web
Submitted by pendell on Wed, 01/20/2010 - 21:15.
I'm looking at a legacy swing GUI system with around a hundred windows and dialogs. User wants to view it on the web through a browser.
Possible approaches I have thought of:
1) Use a commercial swing-like framework that is web-enabled.
2) Manually convert every Frame to an applet.
3) Tell the user to start over with a new system designed to be web-enabled from the ground up. J2EE compliance at the same time would be a bonus.
Thoughts? Have I missed something easy and obvious?
Respectfully,
Brian P.
About Us | Advertise | Contact Us | Terms of Service/Privacy | AdChoices
Copyright, 2006-2013 Infoworld, Inc. All rights reserved.