Timeline for Desktop to Web - How to deal with user-interactive workflows
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 23, 2014 at 9:25 | history | bounty awarded | OlivierH | ||
| Jul 15, 2014 at 9:52 | comment | added | OlivierH | We could in the future make this work of modernization, but for now I try to find a way to be able to port those workflows as is in a web application. @BasileStarynkevitch comment on my question could be a solution : using websockets in, as you said, a client-centric application. But, new point, we have to use Java ecosystem to develop the whole application. Does anyone know a framework or design pattern to "emulate" a desktop-application on web, like Basile's Wt seems to do ? | |
| Jul 15, 2014 at 9:49 | comment | added | OlivierH | First of all, thanks for this detailed answer, you have well understood my issue. To detail a bit more, this application were actively maintained during its 30 years of existence, and was several times "rewritten". The last version uses Borland VCL and is pretty "modern" in its presentation. As I said, rethinking all workflows to adapt them to a server/client architecture would be a really huge job, except if we can find a way to automate the conversion process (ie apply exact rules on all workflows to make them web-comptatible) | |
| Jul 11, 2014 at 16:54 | history | answered | maple_shaft♦ | CC BY-SA 3.0 |