Click here to Skip to main content
15,890,506 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
I want to porting a dekstop application (written in java, and run for windows) to the web (run in browser), but i dont know what are the step.

What I have tried:

I have seen the source code, and i just read about porting OS to OS but it seems not too specific to port from desktop to web. Thankyou
Posted
Updated 6-Apr-18 23:45pm

Basically, don't.
The problem is not that they are different environment - they are - or languages - they are - but that a browser based web app is a completely different paradigm. It's server / client based, using two different languages (javascript, HTML, and CSS for the client; VB , C#, or PHP for the server). And what happens where isn't as simple as you might think: where in a desktop app a button click is easy to process, with a web app you have options: handle it locally in the client via Javascript, handle it it remotely via the server language by posting the page back to the server, or add more complexity via AJAX to reduce the amount you post back. To add to that, you don't even have a single place to store your data: cookies (client), session (server, but volatile), database (server, non-volatile).

So "porting an app" from desktop to web isn't trivial: if the code is incredibly well written so there are clear distinctions between DL, BL, and PL then it can be easier - but even then you still have the language problem which means it won't be a "drop in" port.

Instead, use the existing app as a guide, and design a specification for the web based system using that - then start again from scratch to write the new version. If you don't, you will end up with a unmaintainable mess to support for several years...
 
Share this answer
 
To add to solution 1: If the application requires access to local resources, like disk, ports etc. then creating a web application might face some challenges, depending on the architecture.

Also one thing to consider is, do you need to support both versions? If you do, I'd suggest trying to separate the layers so that as much of the codebase is the same in both applications. In future when the app needs to be maintained, it's much more easier if you have common ground for both versions instead if you need to mainain both versions separately.
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900