|
|
Featured White Papers
- Why choose an Open Source BPM?
- 10 FAQs on Business Process Management
- Best Practices for Getting Started with BPM
- Free Your Devs From The Pain Of Java Redeploys
- Increase Velocity 40% by Using JRebel
- What Developers Want: The End of Application Redeploys
- Developer Productivity Report: Java Tools, Tech, Devs, and Data
- Coding with JRebel: Java Forever Changed
- Utilizing Fast Testing to Transform Java Development
- 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
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.