- This topic has 24 replies, 11 voices, and was last updated 17 years, 7 months ago by
.
-
Posts
-
Okay when is this going to be fixed? Is this at all related to why there’s no Matisse support on OS X? This is frustrating because the OS X Pro software is so hobbled with these limitations.
Correct. If you look at http://www.myeclipseide.com/index.php you will see:
This release continues to integrate the popular Matisse4MyEclipse Swing UI designer directly into MyEclipse, thereby enabling developers to easily build sophisticated graphical user interfaces for their applications. Though Matisse4MyEclipse is now supported on Linux, Mac users will be unable to utilize the Matisse4MyEclipse, MyUML, and MyEclipse Image Editor functions due to the long-standing Eclipse SWT_AWT bug #145890.
Which points to a problem in the SWT implementation for OSX:
aharvey,
You’re correct that without Matisse and UML the Pro version for the Mac definately has some limitations. If you’d like, I’m sure we’d be glad to refund the difference in price between the Pro and Standard versions since you’re not able to use all the features you’d like. If you want to take advantage of that, please send an email to ‘subscriptons at myeclipseide.com’ and they’ll be glad to take care of it.
We continue to work with Eclipse to define the Mac issues and monitor the progress at both Apple and Eclipse to get them addressed.
Is there any status update on this? Does the new JVM stuff from Apple hold any hope? Any new stuff from Eclipse?
Dying for Matisse/UML….
Genuitec? What’s the story? Still working with Apple? Any news from Apple?
Unfortunately, the ball is in both Apple’s and Eclipse platform teams to get this integration working for serious applications like Matisse4MyEclipse. They know about our problems, but they have not addressed the concerns yet.
Scott/Greg,
Apple released an update to their java 5 via the developer preview. Does this fix some of the issues preventing it from running?
http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-15279.htmlAccording to the bug : “If you look at the source code contributed by Apple to fix bug 67384, only embedding AWT within SWT was implemented. The reverse, SWT within AWT, was not.”
I assume that you need SWT to be embeded in AWT? or does it all work if you just embed AWT embeded in SWT?
I had serious problems with WindowsBuilderPro(They primarily embed AWT in SWT from what I can tell), but the latest release seems to fix those issues and I can run it on OSX with no issues. Howver, it does not appear that I can test the UML or Matisse as I assume that it is coded to not show up or allow for use on OSX. Is there some flag or setting to enable it to test?
elee,
You’re correct that Apple release a fix to SWT embedding in AWT, but there remain some threading issues that make its usage problematic in many cases. However, we’re researching those for MyEclipse 5.1.1 to see if we can find some workarounds now that part of the issue is resolved.
Testing on 5.1.0 won’t do you much good since we already know it will not work as currently implemented for the Mac. So, the Mac remains quite different but we’re working now to get resolution on if there are other alternatives there.
Check out https://bugs.eclipse.org/bugs/show_bug.cgi?id=145890
It seems that this problem may be fixed?
If not, can you provide some specific information about what problems remain? Are they documented in the above eclipse bugzilla item or in some different eclipse bugzilla item?
@bentruitt wrote:
Check out https://bugs.eclipse.org/bugs/show_bug.cgi?id=145890
It seems that this problem may be fixed?
If not, can you provide some specific information about what problems remain? Are they documented in the above eclipse bugzilla item or in some different eclipse bugzilla item?
I think you’re missing the comment that says: “download Java 5 update 5 DP 2“. The DP means “Developer Preview”. Until that becomes part of an official release from Apple I don’t think the ME folks can move on it.
@daorriss wrote:
@bentruitt wrote:
Check out https://bugs.eclipse.org/bugs/show_bug.cgi?id=145890
It seems that this problem may be fixed?
If not, can you provide some specific information about what problems remain? Are they documented in the above eclipse bugzilla item or in some different eclipse bugzilla item?
I think you’re missing the comment that says: “download Java 5 update 5 DP 2“. The DP means “Developer Preview”. Until that becomes part of an official release from Apple I don’t think the ME folks can move on it.
On the contrary; I think it’s time for Genuitec to step up to the plate and address this significant limitation since a solution appears to be at hand.
We’re developers. We’re *used* to (in fact, we’d better be damn good at) installing stuff that isn’t in an official release yet. MyEclipse is not a novice-end-user application; it’s a developer tool, and we’re capable of making a decision about whether we want to install a DP, and we’re capable of reading Release Notes that tell us we must do it in order to get XYZ functionality.
Plus, Apple is encouraging developers to download it, so it’s probably more a matter of finding a release package to add this into, vs. it being unstable.
So the fact that a solution is in a DP isn’t an blocking issue for developers, IMHO.
There’s also been recent buglist activity on the previously-referenced Eclipse bug 145890 saying that there is still unfounded FUD about this bug, and that it appears fixed.
This has been a sore spot for a long time. A solution is at hand. It’s time to get the problem solved, Genuitec. (In the meantime, I’m going to switch to ArgoEclipse. Does this mean my future with MyEclipse is limited???)
Genuitec – comments?
@batsonjay wrote:
On the contrary; I think it’s time for Genuitec to step up to the plate and address this significant limitation since a solution appears to be at hand.
Hear Hear! Yes I am well aware that it is a developer preview. I’m the guy on the reference ecilpse bugzilla thread that was able to get ArgoUML working by upgrading to the DP.
However, I should have been more explicit in my previous post – I’d like to know whether the MyEclipse developers have found that this update from Apple does indeed fix the MyEclipse issues. If they feel they have to wait for apple to officially release their corrected software before a new version of MyEclipse can go out, I understand.
That said, a lot of us would be perfectly happy using MyEclipse under the DP if it means getting some long awaited functionality working. Maybe we can get a Beta of the new version of MyEclipse targeted to the corrected JVM from apple?
Again, if the MyEclipse guys find that this fix from apple still does not correct their problems, then I’d really like to know where they documented the problems they’ve encountered so that we can pester Eclipse and Apple further.
Fair enough… if it was up to *me* I probably wouldn’t move with it until Apple made the DP a general release. But considering that apple is notoriously bad at updating their Java tools I supposed users on the Mac platform will have to take what they can get.
bentruitt,
Here is a description of the real problem: https://bugs.eclipse.org/bugs/show_bug.cgi?id=145890#c3
We understand the frustration with this problem. We will try to do what we can on our end. We are in the middle of a big release so time is limited, but maybe we can create a new bugzilla report on eclipse site to talk to this problem more specifically.
We have not had a chance to test the new java 5 update to see if things have been improved. My gut tells me this wont fix our problem, but we can always hope and we will look into it further once we get 5.5M1 shipped. 🙂
Greg,
I’ve added a comment to the bugzilla item you referenced, repeating what you said here.I’m looking forward to the results of your test with the DP2 JVM & native library from comment #24 of that issue.
Thanks for the update. Good luck with your release.
-BenNote that a possibly related eclipse bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=171105
has been resolved. the DP2 JVM fixed it.
-Ben
