StarTeam Components for JBuilder 2007 Visual Editor
One weakness of JBuilder 2007/Eclipse 3.2 is that users cannot modify the Visual Editor (VE) palette dynamically via the UI, like you can with JBuilder 2006. Even though you can add any bean in the Visual Editor via Choose Bean, it’s nice to be able to drag them off a palette.
In JB2007 you have to write a plug-in to get new things to appear on the palette. So as an experiment, as a learning exercise, and as a request from a member of StarTeam Customer Engineer team, I have written a plug-in that adds the StarTeam visual components to the VE palette. I have uploaded it here.
It’s not as complete as it could be. If there’s enough interest, I might try to improve it. Or anybody who is interested can use it as a basis to add their own components of interest to the palette.
Here are a couple of links that I referred to in writing the plug-in:
- Extending the Visual Editor Tutorial: Enabling support for a custom widget
- Extend VE to build a ULC GUI Builder
Share This | Email this page to a friend
Posted by Charles Overbeck on June 8th, 2007 under Eclipse, JBuilder |2 Responses to “StarTeam Components for JBuilder 2007 Visual Editor”
Leave a Comment
Server Response from: dnrh1.codegear.com
November 9th, 2007 at 6:07 am
I’m a JBuilderX user trying to migrate to JBuilder 2007.
So far the migration seems to be OK execpet for the Visual Editor which shows the fields outside the panels, i.e I get a blank panel and after it all the fields on the left side of the pan.
Any recommendation on how to avoid this ?
The problem seems to be only in the Visual Editor because at run time everything is on the right place.
Thanks and regards
J.Brissos
November 9th, 2007 at 11:01 am
Hi Jose,
As far as we can tell, there is a VE bug in this area if the project source is not directly underneath the project directory. When you run our import a .jpx project wizard, it creates links to the source, so the Java source is not under the Eclipse project directory. Please try copying your source directly into your Eclipse project’s directory, and I think that should fix it.
Charles