Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
E4/SWT Browser Edition
SWT Browser Edition
SWT is a mature and powerful widget technology with a highly portable and functional API. Many Eclipse based products have both a desktop and a web component. In order to run on the web, two code streams are required. SWT Browser Edition can allow code sharing, reduce maintenace and bring Eclipse based applications to the web using native web technologies.
- How can code be shared between the desktop and the web?
- What are the critical browser technologies?
- Flex, Silverlight and Dojo have been identified. What about Qooxdoo and GWT?
- What new API's are needed?
- Modern desktop and browser widget toolkits support effects and animation. These API's (and more?) need to be added to SWT to keep it interesting and modern.
- Which desktop API's don't work in the browser?
- The browser can't wait. That means event loop API's like readAndDispatch() or sleep() can't be implemented. What can we do instead?
- In order to cross compile, a JCL (Java Class Library) is needed. How big is this?
- We currently have a CLDC superset (but not that much more). If we restrict the size of the library, downloads will be smaller and faster. If the library is too small, it won't be useful.
- Is code ported to SWT Browser Edition or rewritten?
- Is there a JFace Browser Edition?