Home » Archived » Visual Editor (VE) » Eclipse Forms UI - is it supported?
| |
| Re: Eclipse Forms UI - is it supported? [message #94768 is a reply to message #94665] |
Wed, 22 June 2005 19:22   |
Eclipse User |
|
|
|
Hi Alex,
> I was wondering if I just missed it or it is just not supported.
> Is it planned to be supported? If yes when?
We hope to get this as a 1.1 item. It's progress is being tracked in
bugzilla https://bugs.eclipse.org/bugs/show_bug.cgi?id=64039.
Current thoughts are that we'd have a new palette category called
"Eclipse Forms" that had entries of "Composite", "Button", "Hyperlink",
etc... You could drop these onto any SWT composite to get code
generated like
getFormToolkit.createButton(aComposite, null , SWT.PUSH);
If there is not an existing FormToolkit instance then we will create one
for you that will appear as a non visual part on the GUI and tree. If
there is an existing form toolkit (i.e. you are dropping the 2nd or
subsequent control) then it will re-use the existing form toolkit
instance. The FormToolkit instance can be selected on the GUI or tree
viewer and have its properties changed (like background for example)
One design point we can't get our head around, so maybe you can help, is
how much we surface the FormToolkit instance versus hide it. For
example, are there times when you would want to have multiple
FormToolkit instances in the same class and want to somehow select which
one you were using, so when you dropped a Control you could maybe say
whether you wanted to use one of the existing form toolkits or create a
new one. The approach we have right now is a simple one where it just
creates one instance for you if required and re-uses it on subsequent
drops. If you were a programmer who wanted multiple toolkits to get
some kind of cascading style sheet with different colors and themes per
composite (for example) then you could change the code by hand and the
VE would re-parse it OK, but we run the risk of over complicating things
if we put too much into the palette drop experience.
TableWrapLayout, ColumnLayout and ILayoutExtension are also other things
that look like they might be tricky to implement right without
overwhelming the user. Do you have any experience with these and/or
ideas as to how you'd like to see a VE edit experience with these classes ?
Any design thoughts or other feedback on how you'd like to see Eclipse
forms integrated would be super as now is the perfect time for us to
discuss these.
Best regards,
Joe Winchester
|
|
|
| Re: Eclipse Forms UI - is it supported? [message #94782 is a reply to message #94681] |
Wed, 22 June 2005 23:37 |
| Eclipse User |
|
|
|
"Rui Figueira" <rui.figueira@gmail.com> wrote in message
news:a69e41c01fe9cefb3fd848941cb6e698$1@www.eclipse.org...
> In the Version 1.1 Plan document
> ( http://dev.eclipse.org/viewcvs/indextools.cgi/%7Echeckout%7E /vep-home/WebContent/docs/current-plan/vep-plan-1.1.html),
> it's a deferred item, but it's a feature I miss, mostly for editors...
If you miss Eclipse Forms support, you can get it now in SWT Designer...
http://www.instantiations.com/windowbuilderpro/docs/wizards/ wizard_forms_formpage.html
http://www.instantiations.com/windowbuilderpro/docs/palettes /palettes.html#EclipseForms
SWT Designer fully supports Eclipse Forms for use in views, editors and
general composites. All of the Eclipse Forms components are supported as are
the special Eclipse Forms layout managers (ColumnLayout and
TableWrapLayout). Designer also supports all of the common RCP & JFace UI
types such as ViewParts, EditorParts, PreferencePages, WizardPages, etc.
Note that Swing Designer is a commercial tool with a $199 list price (lower
cost NC and academic licenses are available). A free, feature-limited
edition is also available as is a time-limited eval version of the entire
product (for Eclipse 2.1, 3.0 or 3.1 RC3).
-Eric Clayberg
Sr. Vice President of Product Development
Instantiations, Inc.
http://www.instantiations.com
http://www.windowbuilderpro.com/
Author: "Eclipse: Building Commercial Quality Plug-ins"
http://www.awprofessional.com/title/0321228472
|
|
|
| Re: Eclipse Forms UI - is it supported? [message #94794 is a reply to message #94782] |
Thu, 23 June 2005 09:43 |
| Eclipse User |
|
|
|
Just bought it!
Excellent product and so many imporvements! I checked it out about a year
ago and found it quite flaky, but now it feels stable.
thanks.
"Eric Clayberg" <clayberg@instantiations.com> wrote in message
news:d9daqp$3ke$1@news.eclipse.org...
> "Rui Figueira" <rui.figueira@gmail.com> wrote in message
> news:a69e41c01fe9cefb3fd848941cb6e698$1@www.eclipse.org...
>> In the Version 1.1 Plan document
>> ( http://dev.eclipse.org/viewcvs/indextools.cgi/%7Echeckout%7E /vep-home/WebContent/docs/current-plan/vep-plan-1.1.html),
>> it's a deferred item, but it's a feature I miss, mostly for editors...
>
> If you miss Eclipse Forms support, you can get it now in SWT Designer...
>
>
> http://www.instantiations.com/windowbuilderpro/docs/wizards/ wizard_forms_formpage.html
>
> http://www.instantiations.com/windowbuilderpro/docs/palettes /palettes.html#EclipseForms
>
> SWT Designer fully supports Eclipse Forms for use in views, editors and
> general composites. All of the Eclipse Forms components are supported as
> are the special Eclipse Forms layout managers (ColumnLayout and
> TableWrapLayout). Designer also supports all of the common RCP & JFace UI
> types such as ViewParts, EditorParts, PreferencePages, WizardPages, etc.
>
> Note that Swing Designer is a commercial tool with a $199 list price
> (lower cost NC and academic licenses are available). A free,
> feature-limited edition is also available as is a time-limited eval
> version of the entire product (for Eclipse 2.1, 3.0 or 3.1 RC3).
>
> -Eric Clayberg
> Sr. Vice President of Product Development
> Instantiations, Inc.
> http://www.instantiations.com
> http://www.windowbuilderpro.com/
>
> Author: "Eclipse: Building Commercial Quality Plug-ins"
> http://www.awprofessional.com/title/0321228472
>
|
|
| |
| Re: Eclipse Forms UI - is it supported? [message #608057 is a reply to message #94665] |
Wed, 22 June 2005 19:22 |
| Eclipse User |
|
|
|
Hi Alex,
> I was wondering if I just missed it or it is just not supported.
> Is it planned to be supported? If yes when?
We hope to get this as a 1.1 item. It's progress is being tracked in
bugzilla https://bugs.eclipse.org/bugs/show_bug.cgi?id=64039
Current thoughts are that we'd have a new palette category called
"Eclipse Forms" that had entries of "Composite", "Button", "Hyperlink",
etc... You could drop these onto any SWT composite to get code
generated like
getFormToolkit.createButton(aComposite, null , SWT.PUSH);
If there is not an existing FormToolkit instance then we will create one
for you that will appear as a non visual part on the GUI and tree. If
there is an existing form toolkit (i.e. you are dropping the 2nd or
subsequent control) then it will re-use the existing form toolkit
instance. The FormToolkit instance can be selected on the GUI or tree
viewer and have its properties changed (like background for example)
One design point we can't get our head around, so maybe you can help, is
how much we surface the FormToolkit instance versus hide it. For
example, are there times when you would want to have multiple
FormToolkit instances in the same class and want to somehow select which
one you were using, so when you dropped a Control you could maybe say
whether you wanted to use one of the existing form toolkits or create a
new one. The approach we have right now is a simple one where it just
creates one instance for you if required and re-uses it on subsequent
drops. If you were a programmer who wanted multiple toolkits to get
some kind of cascading style sheet with different colors and themes per
composite (for example) then you could change the code by hand and the
VE would re-parse it OK, but we run the risk of over complicating things
if we put too much into the palette drop experience.
TableWrapLayout, ColumnLayout and ILayoutExtension are also other things
that look like they might be tricky to implement right without
overwhelming the user. Do you have any experience with these and/or
ideas as to how you'd like to see a VE edit experience with these classes ?
Any design thoughts or other feedback on how you'd like to see Eclipse
forms integrated would be super as now is the perfect time for us to
discuss these.
Best regards,
Joe Winchester
|
|
|
| Re: Eclipse Forms UI - is it supported? [message #608058 is a reply to message #94681] |
Wed, 22 June 2005 23:37 |
| Eclipse User |
|
|
|
"Rui Figueira" <rui.figueira@gmail.com> wrote in message
news:a69e41c01fe9cefb3fd848941cb6e698$1@www.eclipse.org...
> In the Version 1.1 Plan document
> ( http://dev.eclipse.org/viewcvs/indextools.cgi/%7Echeckout%7E /vep-home/WebContent/docs/current-plan/vep-plan-1.1.html),
> it's a deferred item, but it's a feature I miss, mostly for editors...
If you miss Eclipse Forms support, you can get it now in SWT Designer...
http://www.instantiations.com/windowbuilderpro/docs/wizards/ wizard_forms_formpage.html
http://www.instantiations.com/windowbuilderpro/docs/palettes /palettes.html#EclipseForms
SWT Designer fully supports Eclipse Forms for use in views, editors and
general composites. All of the Eclipse Forms components are supported as are
the special Eclipse Forms layout managers (ColumnLayout and
TableWrapLayout). Designer also supports all of the common RCP & JFace UI
types such as ViewParts, EditorParts, PreferencePages, WizardPages, etc.
Note that Swing Designer is a commercial tool with a $199 list price (lower
cost NC and academic licenses are available). A free, feature-limited
edition is also available as is a time-limited eval version of the entire
product (for Eclipse 2.1, 3.0 or 3.1 RC3).
-Eric Clayberg
Sr. Vice President of Product Development
Instantiations, Inc.
http://www.instantiations.com
http://www.windowbuilderpro.com/
Author: "Eclipse: Building Commercial Quality Plug-ins"
http://www.awprofessional.com/title/0321228472
|
|
|
| Re: Eclipse Forms UI - is it supported? [message #608060 is a reply to message #94782] |
Thu, 23 June 2005 09:43 |
| Eclipse User |
|
|
|
Just bought it!
Excellent product and so many imporvements! I checked it out about a year
ago and found it quite flaky, but now it feels stable.
thanks.
"Eric Clayberg" <clayberg@instantiations.com> wrote in message
news:d9daqp$3ke$1@news.eclipse.org...
> "Rui Figueira" <rui.figueira@gmail.com> wrote in message
> news:a69e41c01fe9cefb3fd848941cb6e698$1@www.eclipse.org...
>> In the Version 1.1 Plan document
>> ( http://dev.eclipse.org/viewcvs/indextools.cgi/%7Echeckout%7E /vep-home/WebContent/docs/current-plan/vep-plan-1.1.html),
>> it's a deferred item, but it's a feature I miss, mostly for editors...
>
> If you miss Eclipse Forms support, you can get it now in SWT Designer...
>
>
> http://www.instantiations.com/windowbuilderpro/docs/wizards/ wizard_forms_formpage.html
>
> http://www.instantiations.com/windowbuilderpro/docs/palettes /palettes.html#EclipseForms
>
> SWT Designer fully supports Eclipse Forms for use in views, editors and
> general composites. All of the Eclipse Forms components are supported as
> are the special Eclipse Forms layout managers (ColumnLayout and
> TableWrapLayout). Designer also supports all of the common RCP & JFace UI
> types such as ViewParts, EditorParts, PreferencePages, WizardPages, etc.
>
> Note that Swing Designer is a commercial tool with a $199 list price
> (lower cost NC and academic licenses are available). A free,
> feature-limited edition is also available as is a time-limited eval
> version of the entire product (for Eclipse 2.1, 3.0 or 3.1 RC3).
>
> -Eric Clayberg
> Sr. Vice President of Product Development
> Instantiations, Inc.
> http://www.instantiations.com
> http://www.windowbuilderpro.com/
>
> Author: "Eclipse: Building Commercial Quality Plug-ins"
> http://www.awprofessional.com/title/0321228472
>
|
|
|
Goto Forum:
Current Time: Tue Jun 24 16:37:22 EDT 2025
Powered by FUDForum. Page generated in 0.06738 seconds |
Home