January 16, 2012 at 3:29 am #322360
(Note that these comments apply only to releases of MyEclipse prior to the 2013 release)
The MyEclipse visual designers are fully available only on Windows 32 bit platforms. If these are not available on your system (for example Linux systems, or 64 bit systems), you might want to consider using the Web Page Editor (which will have to be selected, using the “Other” menu item, the first time a file is edited), which has many similar features. The rest of this note refers to the MyEclipse visual designers on systems other than Windows 32 bit.
Due to technical constraints, the 64-bit version of MyEclipse on Windows and the Cocoa installations of MyEclipse on the Mac will not include Visual Designers. This feature will be re-introduced in future releases. Windows users can always choose to provision a 32-bit version of MyEclipse, even on 64-bit systems and Mac users can choose to provision a Carbon version of MyEclipse, even on Cocoa systems, to retain access to all features. However, see below for further information on the Mac.
In addition, the visual designers are not enabled by default on Linux systems. See below for more information.
Going forward we are looking for alternative solutions as Mozilla has ended support for embedded XULRunner, which is what we use in our Visual Designers.
The MyEclipse Visual Designers on Mac have exhibited stability problems on some systems. Until this matter is resolved the WYSIWYG design mode has been restricted to a source-only mode of operation. You can re-enable the WYSIYWG design mode for experimental use by including the command line (or ini file) flag: -Dmac.experimental=true
This flag is applicable only to Carbon installations of MyEclipse (see above).
The Visual HTML Designer on Linux has exhibited stability problems on some systems. Until this matter is resolved the WYSIWYG design mode has been restricted to a source-only mode of operation. You can re-enable the WYSIYWG design mode for experimental use by including the command line (or ini file) flag: -Dlinux.experimental=true.
This problem is to do with the fact that we have never been able to achieve a good level of stability with XULRunner on Linux due to technical reasons with the XULRunner builds and constantly changing Linux distributions with corresponding conflicts.
There is a lot of trial an error in getting the visual designers to work on Lunux systems. If the visual designer doesn’t work, after setting the experimental flag, you may get it working by installing release 1.9.2 (or a release prior to 2.0) of XULRunner and pointing MOZILLA_FIVE_HOME (an environment variable) at it before starting MyEclipse. This isn’t guaranteed to work, especially on 64 bit platforms (if you can find a 64 bit build for your system). Note that some limited success has also been seen by setting the following flag:
-Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/XULRunner-220.127.116.11Where the path depends on the installed location of XULRunner. Again, this isn’t guaranteed to work.
Notes on the experimental flag
The flag mentioned above (either -Dmac.experimental=true or -Dlinux.experimental=true), if specified in the MyEclipse ini file (see this FAQ for the location of the ini file), should be specified after the -vmargs line. The best place is at the end of the file, for a default ini file structure.
In the final analysis, experimental features are just that, experimental. As such, they are not fully supported features of MyEclipse. Because of the instabilities mentioned above, there is no guaranteed way to get them to work in all non-32 bit Windows systems, particularly Linux. We apologise for the inconvenience this causes and we will provide a stable implementation of the visual designers in a future release on all supported platforms.
- This topic was modified 3 years, 2 months ago by support-tony.