- This topic has 56 replies, 25 voices, and was last updated 18 years, 5 months ago by
.
-
Posts
-
From that I take they did not really succeed, so far. 🙂
Actually, it’s doing OK for what it is; a bunch of projects trying to ship at the same time. The problem with it is that some people think it’s some sort of super-IDE, and it’s not. Just the same projects with synchronized delivery schedules which is really quite helpful, inspiteof the confusion it causes from time to time.
In the Matisse4MyEclipse realease for 4.1.1, it was mentioned Matisse would become available for Linux in 5.0M1, but I notice the M1 version is still Windows-only.
So, what is the new target for Matisse on Linux? M2?
We worked really hard on getting it into M1. The problem is that we saw problems in the Linux implementation of the SWT_AWT bridge on Linux that weren’t there on Windows. It looks like a threading issue somewhere in the bridge implementation that we’re aggravating, but we didn’t have time to get it resolved for M1. We’ll keep at it and hopefully have something for M2; we haven’t given up. 🙂
now that apple has released a patch to resolve the mac swt bug (https://bugs.eclipse.org/bugs/show_bug.cgi?id=67384 – see last entry in the messages), will support for matisse, etc make its way into the final 5. 0 release for macs?
Yes! Now that M1 is out the door we’re going to be all over seeing how the Mac fix addresses the problems we saw with UML, Matisse, and the image editor. Hopefully (fingers crossed) they’ll all be “Mac-worthy” by M2. 🙂
Just went out internally this morning… basically all the features that weren’t in M1 due to the porting work. I can’t comment specifically on it yet because official evaluating isn’t completed yet, but should be done soon.
Is ME build on top of a ‘stock’ WTP or have changes been made to the WTP in support of the ME integration?
We are fixing some bugs in WTP that adversely affect WTP or MyEclipse functionality. Going forward, we anticipate that this will typically be the case to some degree since we have much faster shipping cycles than the platform projects and we must remain highly responsive to fix any usage issues. However, the APIs for the Eclipse projects we ship are, and will remain, fully compatible with those at eclipse.org. Going forward we’ll continue to fix bugs in the projects we include and submit the fixes back to the foundation. But, due to the lag time in the delivery cycles, we choose to ship the latest released versions of those projects plus all local fixes that haven’t made their way into the Eclpse update cycle yet.
@support-rkalla wrote:
Just went out internally this morning… basically all the features that weren’t in M1 due to the porting work. I can’t comment specifically on it yet because official evaluating isn’t completed yet, but should be done soon.
Are you able to update the road map yet?
thanks
Nothing has been officially handed down to me yet but that’s just because everyone is heads down trying to get all our targetted items for M2 done so we can decide what is going to get cut and what will make it.
Speaking of Callisto, I am assuming you are going to do a release of ME5.0 just after the final release of E3.2/Callisto?
I think it is very important that for the parts of Callisto you bundle, you make sure it is the final versions, and that you also test to some degree the other components of Callisto (for me especially TPTP) and communicate which of the Callisto components are compatible with ME5 (hopefully all of them!)
Given that the goal of Callisto is compatibility between the disparate projects, it would be disasterous if ME prevented the installation of the whole stack.Cheers,
Jon
Jon,
We plan on having a release with the final components we ship within 1 week of the Callisto release (6/30). MyEclipse will be fully compatible. No worries.
For an update on the 5.0M2 timeline, now that Eclipse 3.2 has shipped, please see this thread:
http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-13153.html
