|
| Re: Moving legacy SWT classes to VE [message #110726 is a reply to message #110711] |
Wed, 09 November 2005 15:10   |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
It is not exactly a science for what is understood. :-) We've been
slowly expanding what is understood.
Basically if you are subclassing Composite it expects an initialize()
method, and inside that initialize method is where you set the
properties of the Composite, and add children controls to the composite.
There are two things you can do, first is just try the legacy class and
see if they work, and second using the New Visual Class wizard create a
few class and see what we generate.
Thomas Mauch wrote:
> Hello
>
> I have legacy SWT classes developped without VE. What exactly are the
> prerequisites that these classes can be handled by VE? Is there any
> document which describes how the structure of the classes / fields must
> look?
>
> I noticed as well that there are sometimes comments like
> @jve:decl-index=0:visual-constraint="" which are obviously used to
> communicate with VE. Where are they described?
>
> Thomas
--
Thanks,
Rich Kulp
|
|
|
| Re: Moving legacy SWT classes to VE [message #113086 is a reply to message #110726] |
Tue, 13 December 2005 21:15 |
| Eclipse User |
|
|
|
Originally posted by: rozhang.cisco.com
Rich,
I believe what Thomas asked is the procedure of using Visual Editor to
edit SWT/Swing sub-classes that are created by tools other than VE. It'd
be helpful for people to have greater use of the VE.
Thanks,
Rolly
|
|
|
|
| Re: Moving legacy SWT classes to VE [message #611309 is a reply to message #110711] |
Wed, 09 November 2005 15:10 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
It is not exactly a science for what is understood. :-) We've been
slowly expanding what is understood.
Basically if you are subclassing Composite it expects an initialize()
method, and inside that initialize method is where you set the
properties of the Composite, and add children controls to the composite.
There are two things you can do, first is just try the legacy class and
see if they work, and second using the New Visual Class wizard create a
few class and see what we generate.
Thomas Mauch wrote:
> Hello
>
> I have legacy SWT classes developped without VE. What exactly are the
> prerequisites that these classes can be handled by VE? Is there any
> document which describes how the structure of the classes / fields must
> look?
>
> I noticed as well that there are sometimes comments like
> @jve:decl-index=0:visual-constraint="" which are obviously used to
> communicate with VE. Where are they described?
>
> Thomas
--
Thanks,
Rich Kulp
|
|
|
| Re: Moving legacy SWT classes to VE [message #611537 is a reply to message #110726] |
Tue, 13 December 2005 21:15 |
| Eclipse User |
|
|
|
Originally posted by: rozhang.cisco.com
Rich,
I believe what Thomas asked is the procedure of using Visual Editor to
edit SWT/Swing sub-classes that are created by tools other than VE. It'd
be helpful for people to have greater use of the VE.
Thanks,
Rolly
|
|
|
|
Powered by
FUDForum. Page generated in 0.03602 seconds
] 
Search
Help
Register
Login
Home
