Any update on MAC support

[mfkilgore]

Thanks for a great product.

It appears that some of the reported bugs causing you and others problems with OS X support have been resolved. Is that the case from your perspective? Is there any further update on plans to support those of us on the MAC?

FYI - I have downloaded the latest eclipse 3.1 m5a along with the latested designer. I now get Internal Parse Error when attempting to load existing projects. Same error when creating a new SWT project.

The following is in the eclipse log:
!ENTRY com.swtdesigner 4 4 2005-02-25 09:37:48.670
!MESSAGE Designer internal error: null
!STACK 0
Parse failed:
Internal parser error
com.swtdesigner.model.parser.ParserException
at com.swtdesigner.model.parser.JavaInfoParser.parse(JavaInfoParser.java:197)
at com.swtdesigner.gef.DesignerEditor.parseCompilationUnit(DesignerEditor.java:802)
at com.swtdesigner.gef.DesignerEditor.handleActivate(DesignerEditor.java:736)
at com.swtdesigner.gef.DesignerEditor.handleActivate(DesignerEditor.java:704)
at com.swtdesigner.editors.MultiPageEditor.showDesignEditor(MultiPageEditor.java:293)
at com.swtdesigner.editors.MultiPageEditor$2.widgetSelected(MultiPageEditor.java:155)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1237)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1261)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1246)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1094)
at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3141)
at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:1925)
at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:287)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1237)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1261)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1246)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1094)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2903)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2571)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1612)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1578)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:293)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:144)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:102)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:228)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:333)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:150)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:268)
at org.eclipse.core.launcher.Main.basicRun(Main.java:260)
at org.eclipse.core.launcher.Main.run(Main.java:887)
at org.eclipse.core.launcher.Main.main(Main.java:871)

[Eric Clayberg]

It appears that some of the reported bugs causing you and others problems with OS X support have been resolved.

Which ones? I am not aware of any that have been resolved.

Is that the case from your perspective? Is there any further update on plans to support those of us on the MAC?

Are you referring to SWT Designer or Swing Designer? SWT Designer currently works on the Mac; Swing Designer does not. Given the outstanding issues with Swing support in Eclipse for OSX, I would not expect to support the Mac any time soon. For the moment, Eclipse under OSX is a 3rd class citizen in the Eclipse world.

I have downloaded the latest eclipse 3.1 m5a along with the latested designer. I now get Internal Parse Error when attempting to load existing projects. Same error when creating a new SWT project.

Can you send us a test case? It's working just fine on our end. Does your project show any problems in the Problems view? Any other exceptions in your Eclipse ".log" file? Did you delete your Eclipse "configuration" directory after installing Designer?

[mfkilgore]

To recreate I simply created a new project, new main window SWT not Swing. My previous version of eclipse/SWT Designer works fine.

I have noted a number of fixed problems, if you are not aware, they probably do not affect this code base. I was just hopeful


Here is additional stack information:
eclipse.buildId=I20050219-1500
java.version=1.4.2_05
java.vendor=Apple Computer, Inc.
BootLoader constants: OS=macosx, ARCH=ppc, WS=carbon, NL=en_US
Framework arguments: -keyring /Users/mfkilgore/.eclipse_keyring -showlocation
Command-line arguments: -os macosx -ws carbon -arch ppc -keyring /Users/mfkilgore/.eclipse_keyring -consoleLog -showlocation

!ENTRY com.swtdesigner 4 4 2005-02-25 19:34:52.912
!MESSAGE Designer internal error: Can't start the AWT because Java was started on the first thread. Make sure StartOnFirstThread is not specified in your application's Info.plist or on the command line
!STACK 0
java.lang.InternalError: Can't start the AWT because Java was started on the first thread. Make sure StartOnFirstThread is not specified in your application's Info.plist or on the command line
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1586)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1503)
at java.lang.Runtime.loadLibrary0(Runtime.java:788)
at java.lang.System.loadLibrary(System.java:834)
at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50)
at java.security.AccessController.doPrivileged(Native Method)
at sun.awt.NativeLibLoader.loadLibraries(NativeLibLoader.java:38)
at sun.awt.DebugHelper.<clinit>(DebugHelper.java:29)
at java.awt.Component.<clinit>(Component.java:506)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at com.swtdesigner.model.JavaInfoFactory.create(JavaInfoFactory.java:409)
at com.swtdesigner.model.JavaInfoFactory.create(JavaInfoFactory.java:88)
at com.swtdesigner.model.parser.JavaInfoParser$ParserVisitor.endVisit(JavaInfoParser.java:1278)
at org.eclipse.jdt.core.dom.ClassInstanceCreation.accept0(ClassInstanceCreation.java:337)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2450)
at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2497)
at org.eclipse.jdt.core.dom.VariableDeclarationFragment.accept0(VariableDeclarationFragment.java:224)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2450)
at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2520)
at org.eclipse.jdt.core.dom.VariableDeclarationStatement.accept0(VariableDeclarationStatement.java:273)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2450)
at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2520)
at org.eclipse.jdt.core.dom.Block.accept0(Block.java:135)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2450)
at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2497)
at org.eclipse.jdt.core.dom.TryStatement.accept0(TryStatement.java:194)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2450)
at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2520)
at org.eclipse.jdt.core.dom.Block.accept0(Block.java:135)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2450)
at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2497)
at org.eclipse.jdt.core.dom.MethodDeclaration.accept0(MethodDeclaration.java:503)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2450)
at com.swtdesigner.model.parser.JavaInfoParser$ParserVisitor.visit(JavaInfoParser.java:2531)
at org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:469)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2450)
at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2520)
at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:291)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2450)
at com.swtdesigner.model.parser.JavaInfoParser.parse(JavaInfoParser.java:191)
at com.swtdesigner.gef.DesignerEditor.parseCompilationUnit(DesignerEditor.java:802)
at com.swtdesigner.gef.DesignerEditor.handleActivate(DesignerEditor.java:736)
at com.swtdesigner.gef.DesignerEditor.handleActivate(DesignerEditor.java:704)
at com.swtdesigner.editors.MultiPageEditor.showDesignEditor(MultiPageEditor.java:293)
at com.swtdesigner.editors.MultiPageEditor$2.widgetSelected(MultiPageEditor.java:155)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1237)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1261)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1246)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1094)
at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3141)
at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:1925)
at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:287)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1237)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1261)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1246)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1094)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2903)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2571)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1612)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1578)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:293)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:144)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:102)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:228)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:333)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:150)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:268)
at org.eclipse.core.launcher.Main.basicRun(Main.java:260)
at org.eclipse.core.launcher.Main.run(Main.java:887)
at org.eclipse.core.launcher.Main.main(Main.java:871)

[Eric Clayberg]

To recreate I simply created a new project, new main window SWT not Swing. My previous version of eclipse/SWT Designer works fine.

Is this on Windows or the Mac? If the latter, you may be running into the same problem that prevents Swing Designer from working under OSX.

Our recent addition of SWT_AWT support could have tripped over the existing Eclipse OSX issue that affects Swing Designer.

You might try turning off the SWT_AWT palette option on the Designer > SWT preference page.

[mfkilgore]

Eric,

This problem is on my mac running os x 10.3.8. And only occurs in the latest release of Designer.

I tried your suggesting of turnning off the SWT_AWT palette that had no affect on this problem.

[Eric Clayberg]

This problem is on my mac running os x 10.3.8. And only occurs in the latest release of Designer. I tried your suggesting of turnning off the SWT_AWT palette that had no affect on this problem.

I was afraid of that. It is likely due to various SWT_AWT init code that is now in place. I have attempted to isolate that code with a series of "isMac" checks and have uploaded a new v3.0.1 build. I am at EclipseCon this next week and won't be able to actually check it myself on a Mac until I get back.

BTW, none of this would be necessary if the Eclipse SWT team would fix their OSX problems. Until OSX becomes more than a 3rd class citizen in the Eclipse world, our support will remain at a "best efforts" level (e.g., officially unsupported, but we will try to address any bug reports).

[Ken Lee]

Could you please describe what is supported, and what is not ?

If you develop an app on Windows, will it run on Mac ? If not, which features ?

Alternately, if someone installs your product on a current OSX machine, then which features will work, and which will not ? Or will it not install ?

Just looking for a concise overview. Thanks !

[Eric Clayberg]

Could you please describe what is supported, and what is not ? If you develop an app on Windows, will it run on Mac ? If not, which features ? Alternately, if someone installs your product on a current OSX machine, then which features will work, and which will not ? Or will it not install ?

If you develop an app on Windows, it will run on the Mac (as long as you aren't mixing SWT and Swing in the same UI). SWT Designer v3.0.0 should work on the Mac. Although it is officially unsupported, we do accept bug reports on it. The latest SWT Designer v3.0.1 build has not been tested on the Mac, and may or may not work. In my experience, Eclipse on the Mac is extremely fragile and just looking at it the wrong way is enough to lock it up. Swing Designer definitely will not run on the Mac due to all of the known, critical issues with Swing support in Eclipse for the Mac (none of which have been resolved at this time).

See the Designer FAQ for more details.

[evan]

i'm pleased to report that i got SWT Designer to work on my Mac. I haven't tested it rigorously, but I got past the initial parse error and could design stuff. (I didn't try running my design).

This is tested with Eclipse 3.1 with the May 6 SWT Designer build.

Steps to reproduce:

1) Install Tiger (OSX 10.4).
2) Install the 1.5 JRE (http://www.apple.com/support/downloads/ ... ease1.html)
3) I put eclipse in /Applications, find yours appropriately. Edit /Applications/eclipse/Eclipse.app/Contents/Info.plist.
4) Add
<string>-vm</string>
<string>/System/Library/Frameworks/JavaVM.framework/Versions/1.5/Home/bin/java</string>
right after
<key>Eclipse</key>
<array>
5) Add
<string>-Djava.awt.headless=true</string>
after <string>-vmargs</string>


This info was derived from here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=67384#c40
http://groups-beta.google.com/group/ecl ... 4493a0ff26


Now I can use SWT Designer in Windows/Linux at the office and on on my trusty PowerBook at home and on the road! =)

-Evan

[Eric Clayberg]

Now I can use SWT Designer in Windows/Linux at the office and on on my trusty PowerBook at home and on the road!

Thanks for the info. It was very helpful.

Now if only Apple and/or the Eclipse.org folks would fix the Swing interoperability problems, we will be in great shape.

[mfkilgore]

Thank you very much!

Followed the instructions above and now have the latest SWT, latest Eclipse, Java 1.5, and OS X 10.4 all happily working. I will be doing some more testing over the next few days

I agree the addition of Swing support will complete the picture. Are there specific bug reports on this? Maybe there is hope that it will be fixed before 3.1 final...

[Eric Clayberg]

Followed the instructions above and now have the latest SWT, latest Eclipse, Java 1.5, and OS X 10.4 all happily working.

That is good news (Thanks Evan!). I have added this information to the Designer FAQ.

I agree the addition of Swing support will complete the picture. Are there specific bug reports on this? Maybe there is hope that it will be fixed before 3.1 final.

Unfortunately, that is very unlikely. Here are some of the relevant bug reports:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=67384
https://bugs.eclipse.org/bugs/show_bug.cgi?id=53790
https://bugs.eclipse.org/bugs/show_bug.cgi?id=54791
https://bugs.eclipse.org/bugs/show_bug.cgi?id=50540
https://bugs.eclipse.org/bugs/show_bug.cgi?id=41234

[evan]

Things have changed slightly for Eclipse 3.1 M7:

1) Install Tiger (OSX 10.4).
2) Install JRE 1.5 (http://www.apple.com/support/downloads/ ... ease1.html)
3) The rest assumes you installed Eclipse 3.1 M7 at /Applications/eclipse
4) To /Applications/eclipse/Eclipse.app/Contents/MacOS/eclipse.ini, append the line
-Djava.awt.headless=true
5) To /Applications/eclipse/Eclipse.app/Contents/Info.plist, add the lines
<string>-vm</string>
<string>/System/Library/Frameworks/JavaVM.framework/Versions/1.5/Home/bin/java</string>
right after
<key>Eclipse</key>
<array>

This has been verified to work. However I had an initial problem where I thought things were still broken (window parser error). However, the problem was that 3.1 M7 changed the name of the platform-specific SWT jar. Updating the build path fixed the problem and everything works fine.

-Evan

[Eric Clayberg]

Things have changed slightly for Eclipse 3.1 M7

Thanks Evan! I have updated the Desigenr FAQ with this revised info.

[ethomson]

I didn't have much luck with SWT Designer under the 1.5 VM. (Clicking the design tab locked up Eclipse.) Here's my current setup, which seems to be working so far:

Eclipse 3.1.1 (M20050929-0840)
Java 1.4.2 (1.4.2-54 build from OS 10.4.4)

I did require the -Djava.awt.headless=true in my eclipse.ini.