Home

News: MyEclipse Brings Tools to NetBeans, Visual Studio Users

  1. MyEclipse has announced immediate availability of the popular SNAPs tools to Sun's NetBeans and Microsoft's Visual Studio developers via "Use-Anywhere" connectors. Users of NetBeans and Visual Studio are now able to utilize the MyEclipse Visual HTML Designer, XML Editor, Database Explorer and Image Editor SNAPs directly in their own environment. Additional SNAPs will be made available using other MyEclipse features by integrating open source technologies and through partner extensions. The SNAPs are part of the expanding Fusion Technology suite of tools that allows developers to accomplish focused tasks without the weight of an entire IDE. They can also be used with other development tools thereby freeing users from the vendor lock-in that is commonly associated with development environments. Many developers utilize multiple platforms for different tasks, and the availability of these crossover tools should improve productivity by avoiding back-and-forth behavior. The MyEclipse "Use-Anywhere" connectors for NetBeans and Visual Studio are available immediately. Both require the All-in-One installation of MyEclipse 5.5M1 Enterprise Workbench, which can be downloaded here. The following URLs provide additional details about the MyEclipse "Use-Anywhere" connectors, and provide installation and/or tutorial links:Do you see this improving your workflow? Will having the lightweight SNAPs available make you more likely to explore these types of lock-in free tools if you are a NetBeans or Visual Studio user?
  2. I'm probably misreading this post in the hope of finding something that I (and a lot of other people) have been waiting for a long time. Is this a port of the MyEclipse Plugins, or do they use some sort of facade to make Eclipse plugins work in NetBeans / Visual Studio. If it's the latter (and I appreciate that it is not a trivial technical challenge) then I believe that MyEclipse has begun something crucial : a cross platform plugin environment. I don't care which is 'better' (Eclipse ,NetBeans or Visual Studio), but I do care that whichever one I choose has the widest range of possible functionality. Again, it might be me misreading this announcement, but that would be really big news. Paul , Technology in Plain English
  3. Paul; What is happening here is likely closer to your second statement than the former. We are in the process of expanding our Fusion Technology suite that allows developers to break the barriers between previously fractioned development environments. With the creation of our NetBeans and Visual Studio "Use-Anywhere" Connectors, we have been able to bring - at this point anyway - specifically MyEclipse SNAPs tools (SNAPs are not a plugin, but rather a tool suite we have developed) to this user population. However, the SNAPs tool suite will be expanding rapidly, delivering tools to users of other environments like NetBeans and Visual Studio. And this is just an initial phase of the development of these types of tools. I think you'll be more excited as time goes by as far as barrier-breaking goes. :-) Stay tuned to both TSS and our website for announcements.

    Thanks for your interest! I would also invite you to visit our forums to let us know what features or tools you would like to see next. Feel free to suggest things (like your statements above) that you previously thought were not possible. They just might be... :-)

    Our goal, as you allude to, is not to fall in love with an IDE religion or lock users into a specific platform/vendor, but give users the widest possible choice in their tooling. Many developers use multiple environments because they have their favorite tools in each. Wouldn't it be nice if you didn't have to choose all the time?
    -Jens
  4. I can see MyEclipse wanting to expand their market, it must not be fun waiting for the Eclipse group to come out with high level frameworks you can build to while still providing leading features (viz Myeclipse components that are not cross platform, such as the UML tool, image editor, etc). However, as a current Myeclipse subscriber, I would rather have fewer, better choices, than simply more choice. Again, I suppose it is more attractive for Myeclipse to build a bigger market than make an existing product work well with one IDE's directions, cross platform - as well as competing as a "closed" product in a primarily open source space. So, when's the name change? SNAP to it! :)
  5. Maybe a bit offtopic, but is the Matisse port in MyEclipse compatible with the original NetBeans Matisse? What I mean is, would there be any problems if some developers on a team use MyEclipse and some use NetBeans (5.5 or 6.0), and these people edit one another's forms?
  6. Either way, it is good for users. J2EE tools
  7. Is this a port of the MyEclipse Plugins, or do they use some sort of facade to make Eclipse plugins work in NetBeans / Visual Studio.
    From the Flash demo is looks like neither of those things is happening. These Snap applications are mostly 'just' standalone applications. Most IDEs have an option to edit a workspace file using an external editor. What seems to be happening with this integration is that these other IDEs simply see the MyEclipse Snap applications as just another external editor. This by itself is nothing really new. You can if you wish edit text files in Eclipse using gedit, jot, nedit, or whatever app you choose. Upon opening a file, the editor does not integrate in the UI of the IDE but simply opens in a new window. Perhaps MyEclipse is doing a little more than just that (like perhaps providing a small plug-in that does a refresh in the target IDE upon saving in the external editor), but from what I've seen this is basically all there is to it. At this moment atleast ;) Of course, letting editors that were originally designed as an Eclipse plug-in run as a standalone app is quite an accomplishment. The other way around though has been done at least a couple of times already (standalone app that also functions as a eclipse plugin).
  8. Deintegration is Right...[ Go to top ]

    This really looks like the wrong direction. I can't see this being useful for Visual Studio, and I really don't see the limited integration being useful for Netbeans. Just keep making the Eclipse ones better, or start up a new line for Netbeans. Trying to do both with this "SNAP" concept is just clumsy.