Eclipse Community Forums: Visual Editor (VE) » VE design of RCP Wizard pages (ve 3.1M2)

Help

Home

Home » Archived » Visual Editor (VE) » VE design of RCP Wizard pages (ve 3.1M2)

Show: Today's Messages :: Show Polls :: Message Navigator

VE design of RCP Wizard pages (ve 3.1M2) [message #94027]

Wed, 15 June 2005 09:10

Eclipse User

Originally posted by: frugal.purplewombat.co.uk

I am currently creating a series of wizards for my RCP application as such
each of these wizards has pages derived from WizardPage.

However as WizardPage creates all of it's controls in "void
createControl(Composite parent)" the VE does not recognise it as a class
that it can edit.

I can create a Composite class for each of my wizard pages and then add it
as the only child of the WizardPage composite but then I have to create
accessors and delegates for all of the entities in the Composite class.

Does anyone have a better way of being able to design the contents of a
WizardPage without needing to use an extra class?

regards,
Frugal

Report message to a moderator

Re: VE design of RCP Wizard pages (ve 3.1M2) [message #94043 is a reply to message #94027]

Wed, 15 June 2005 10:12

Joe Winchester

Messages: 496
Registered: July 2009

Senior Member

Hi Frugal,

> However as WizardPage creates all of it's controls in "void
> createControl(Composite parent)" the VE does not recognise it as a class
> that it can edit.

We need to support WizardPages and Dialogs where you subclass rather
than create a custom composite which is what you have to do now. I have
opened a bugzilla https://bugs.eclipse.org/bugs/show_bug.cgi?id=100145
so please add yourself as a cc member and you can track its progress.

In our last 2 drivers we added support for ViewPart and EditorPart which
form the backbone of an RCP app and these use the coding pattern where
there is a createComposite(Composite parent) method so the plumbing is
all there - we just need to make it work for more classes and also do
this in a generic way so that people who have their own pattern they
want to use can enable the VE to recognize it without having to write a
lot of fancy plugin code. There are also things like Dialog to support
which is interesting because you have several methods to generate into -
one for the dialog area and another for the button bar.

Best regards,

Joe

Report message to a moderator