Home » Archived » Visual Editor (VE) » Feature Requests
| Feature Requests [message #2488] |
Thu, 20 November 2003 11:09  |
Eclipse User |
|
|
|
First of all, congratulations to the whole team for this much needed (and
awaited) editor.
I used the WSAD 5 JVE on a few occasions and I must say that this new
version is a real improvement (both in performance and usability).
Still, there are IMHO some key features missing ... such as the inability to
rename a widget without saving the class and doing some refactoring (which
leads to resynchronization between visual and source, not to mention a
couple of compilations).
Ok it works fine but it takes a loooooong time, especially when you do
*real* developement with more than 3 widgets ;-)
I think this is a key feature because it makes the code much more
maintainable when your widget is called jButtonSave instead of jButton5.
Another interesting feature would be to be able to customize the palette so
we could add a new category with specific widgets (e.g. 3rd party
java-beans, or custom components) ... which would probably lead to the need
for a bean-info editor so one could design his own beans ;-)
Ok, I think it's pretty obvious that I'm a former VAJ user ... still I think
this is worth it.
I'm pretty much aware, that it's possible to do the same thing with the
editor as it is, but my point is that it's both difficult and slow to do and
these features would really prove themselves useful if implemented.
|
|
| |
| Re: Feature Requests [message #2611 is a reply to message #2488] |
Thu, 20 November 2003 18:27  |
| Eclipse User |
|
|
|
Sébastien Alonzo wrote:
> I used the WSAD 5 JVE on a few occasions and I must say that this new
> version is a real improvement (both in performance and usability).
> Still, there are IMHO some key features missing ... such as the inability to
> rename a widget without saving the class and doing some refactoring (which
> leads to resynchronization between visual and source, not to mention a
> couple of compilations).
> Ok it works fine but it takes a loooooong time, especially when you do
> *real* developement with more than 3 widgets ;-)
> I think this is a key feature because it makes the code much more
> maintainable when your widget is called jButtonSave instead of jButton5.
Yes, it is. But there is a trick. Don't use the bean palette. Try to click
the "Choose Bean" button. A dialog appears to choose the bean (previously
selected beans appears in a combo!) with an entry field at bottom to
write the bean name. You can write "jButtonSave" and no refactoring is
needed.
I suggest when I choose a bean from the palette, a little dialog appears
to enter the bean name.
> Another interesting feature would be to be able to customize the palette so
> we could add a new category with specific widgets (e.g. 3rd party
> java-beans, or custom components) ... which would probably lead to the need
> for a bean-info editor so one could design his own beans ;-)
> Ok, I think it's pretty obvious that I'm a former VAJ user ... still I think
> this is worth it.
Yes, and other features from VAJ where desirables IMHO. For example:
- Promote bean feature (yes, I can promote a get method changing
your scope from private to public, but what happens with the
event promotion?)
- Possibility of connections (yes, why eliminate the possibility
to use visual programming optionally?)
- A bean editor
- etc.
> I'm pretty much aware, that it's possible to do the same thing with the
> editor as it is, but my point is that it's both difficult and slow to do and
> these features would really prove themselves useful if implemented.
Now the project is open source and a big user community can opine. I think
this is the beginning...
Francesc
|
|
| |
| Re: Feature Requests [message #3773 is a reply to message #2488] |
Fri, 21 November 2003 08:52 |
| Eclipse User |
|
|
|
Originally posted by: mendelgili.netscape.net
Sébastien Alonzo wrote:
> First of all, congratulations to the whole team for this much needed (and
> awaited) editor.
>
> I used the WSAD 5 JVE on a few occasions and I must say that this new
> version is a real improvement (both in performance and usability).
> Still, there are IMHO some key features missing ... such as the inability to
> rename a widget without saving the class and doing some refactoring (which
> leads to resynchronization between visual and source, not to mention a
> couple of compilations).
> Ok it works fine but it takes a loooooong time, especially when you do
> *real* developement with more than 3 widgets ;-)
>
Yep. There is a saying, get it working, get it working right, then get
it fast. We are in this latest phase. The 3 high priority items for
the next release effort are:
V3 port
SWT extension
Performance
> I think this is a key feature because it makes the code much more
> maintainable when your widget is called jButtonSave instead of jButton5.
>
Once a bean is dropped and code is generated, the rename uses the
refactoring path which requires a save.
I agree, a naming option is key. Our thinking is to provide an
optional *small* dialog on the drop to give one a chance to name the
bean up front.
> Another interesting feature would be to be able to customize the palette so
> we could add a new category with specific widgets (e.g. 3rd party
> java-beans, or custom components)
A plugin can extend the palette today. The following is a bit stale but
will start you up:
http://www-106.ibm.com/developerworks/websphere/library/tech articles/0302_winchester/winchester.html
There is much work to be done in the palette area: User extension,
loading/remembering a set of drawers (e.g., SWT, Swing, Customed),
enabling GEF support for customization etc.
.... which would probably lead to the need
> for a bean-info editor so one could design his own beans ;-)
> Ok, I think it's pretty obvious that I'm a former VAJ user ... still I think
> this is worth it.
>
We will welcome contributions for a bean-info editor; in the short run,
we have to focus on getting the three items above.
> I'm pretty much aware, that it's possible to do the same thing with the
> editor as it is, but my point is that it's both difficult and slow to do and
> these features would really prove themselves useful if implemented.
>
>
|
|
|
| Re: Feature Requests [message #5024 is a reply to message #3767] |
Tue, 25 November 2003 03:19 |
| Eclipse User |
|
|
|
Ok guys,
This solution works fine with small adaptations :
1) The required plugins need to be changed from "com.ibm.etools.jbcf" to
"org.eclipse.jem.beaninfo" and "org.eclipse.ve.java.core"
and extensions points need to be changed from
"com.ibm.etools.jbcf.registrations" to
"org.eclipse.ve.java.core.registrations" and from
"com.ibm.etools.beaninfo.registrations" to
"org.eclipse.jem.beaninfo.registrations".
2) The XMI file namespaces are just slightly different : xmlns:palette needs
to be changed from "palettecde.xmi" to
"http:///org/eclipse/ve/internal/cde/palette.ecore" and xlmns:utility needs
to be changed from "utilitycde.xmi" to
"http:///org/eclipse/ve/internal/cde/utility.ecore".
Actually there is a sample palette available in the VE examples, so it's
pretty easy to build your own.
Thanks for the tip.
"Chemi" <jmordax@terra.es> wrote in message news:bpksdf$ldu$1@eclipse.org...
> S
|
|
|
| Re: Feature Requests [message #567632 is a reply to message #2488] |
Thu, 20 November 2003 11:58 |
| Eclipse User |
|
|
|
Congrats to IBM/Eclipse, this project opens new opportunities for developers
and the Eclipse platform!
What I see as a major feature to VEP is data binding capabilities, that will
definitely appeal more users.
This could go with the custom Bean API or some other standard approach.
Anyway I'm confident that this project will have the same success as the
whole Eclipse story and good things will come out, maybe the next JSF/WEB
visual editor could come from this project...
"S
|
|
|
| Re: Feature Requests [message #567691 is a reply to message #2488] |
Thu, 20 November 2003 18:27 |
| Eclipse User |
|
|
|
Sébastien Alonzo wrote:
> I used the WSAD 5 JVE on a few occasions and I must say that this new
> version is a real improvement (both in performance and usability).
> Still, there are IMHO some key features missing ... such as the inability to
> rename a widget without saving the class and doing some refactoring (which
> leads to resynchronization between visual and source, not to mention a
> couple of compilations).
> Ok it works fine but it takes a loooooong time, especially when you do
> *real* developement with more than 3 widgets ;-)
> I think this is a key feature because it makes the code much more
> maintainable when your widget is called jButtonSave instead of jButton5.
Yes, it is. But there is a trick. Don't use the bean palette. Try to click
the "Choose Bean" button. A dialog appears to choose the bean (previously
selected beans appears in a combo!) with an entry field at bottom to
write the bean name. You can write "jButtonSave" and no refactoring is
needed.
I suggest when I choose a bean from the palette, a little dialog appears
to enter the bean name.
> Another interesting feature would be to be able to customize the palette so
> we could add a new category with specific widgets (e.g. 3rd party
> java-beans, or custom components) ... which would probably lead to the need
> for a bean-info editor so one could design his own beans ;-)
> Ok, I think it's pretty obvious that I'm a former VAJ user ... still I think
> this is worth it.
Yes, and other features from VAJ where desirables IMHO. For example:
- Promote bean feature (yes, I can promote a get method changing
your scope from private to public, but what happens with the
event promotion?)
- Possibility of connections (yes, why eliminate the possibility
to use visual programming optionally?)
- A bean editor
- etc.
> I'm pretty much aware, that it's possible to do the same thing with the
> editor as it is, but my point is that it's both difficult and slow to do and
> these features would really prove themselves useful if implemented.
Now the project is open source and a big user community can opine. I think
this is the beginning...
Francesc
|
|
| |
| Re: Feature Requests [message #567910 is a reply to message #2488] |
Fri, 21 November 2003 08:52 |
| Eclipse User |
|
|
|
Sébastien Alonzo wrote:
> First of all, congratulations to the whole team for this much needed (and
> awaited) editor.
>
> I used the WSAD 5 JVE on a few occasions and I must say that this new
> version is a real improvement (both in performance and usability).
> Still, there are IMHO some key features missing ... such as the inability to
> rename a widget without saving the class and doing some refactoring (which
> leads to resynchronization between visual and source, not to mention a
> couple of compilations).
> Ok it works fine but it takes a loooooong time, especially when you do
> *real* developement with more than 3 widgets ;-)
>
Yep. There is a saying, get it working, get it working right, then get
it fast. We are in this latest phase. The 3 high priority items for
the next release effort are:
V3 port
SWT extension
Performance
> I think this is a key feature because it makes the code much more
> maintainable when your widget is called jButtonSave instead of jButton5.
>
Once a bean is dropped and code is generated, the rename uses the
refactoring path which requires a save.
I agree, a naming option is key. Our thinking is to provide an
optional *small* dialog on the drop to give one a chance to name the
bean up front.
> Another interesting feature would be to be able to customize the palette so
> we could add a new category with specific widgets (e.g. 3rd party
> java-beans, or custom components)
A plugin can extend the palette today. The following is a bit stale but
will start you up:
http://www-106.ibm.com/developerworks/websphere/library/tech articles/0302_winchester/winchester.html
There is much work to be done in the palette area: User extension,
loading/remembering a set of drawers (e.g., SWT, Swing, Customed),
enabling GEF support for customization etc.
.... which would probably lead to the need
> for a bean-info editor so one could design his own beans ;-)
> Ok, I think it's pretty obvious that I'm a former VAJ user ... still I think
> this is worth it.
>
We will welcome contributions for a bean-info editor; in the short run,
we have to focus on getting the three items above.
> I'm pretty much aware, that it's possible to do the same thing with the
> editor as it is, but my point is that it's both difficult and slow to do and
> these features would really prove themselves useful if implemented.
>
>
|
|
|
| Re: Feature Requests [message #569013 is a reply to message #3767] |
Tue, 25 November 2003 03:19 |
| Eclipse User |
|
|
|
Ok guys,
This solution works fine with small adaptations :
1) The required plugins need to be changed from "com.ibm.etools.jbcf" to
"org.eclipse.jem.beaninfo" and "org.eclipse.ve.java.core"
and extensions points need to be changed from
"com.ibm.etools.jbcf.registrations" to
"org.eclipse.ve.java.core.registrations" and from
"com.ibm.etools.beaninfo.registrations" to
"org.eclipse.jem.beaninfo.registrations".
2) The XMI file namespaces are just slightly different : xmlns:palette needs
to be changed from "palettecde.xmi" to
"http:///org/eclipse/ve/internal/cde/palette.ecore" and xlmns:utility needs
to be changed from "utilitycde.xmi" to
"http:///org/eclipse/ve/internal/cde/utility.ecore".
Actually there is a sample palette available in the VE examples, so it's
pretty easy to build your own.
Thanks for the tip.
"Chemi" <jmordax@terra.es> wrote in message news:bpksdf$ldu$1@eclipse.org...
> S
|
|
|
Goto Forum:
Current Time: Thu Oct 30 23:44:44 EDT 2025
Powered by FUDForum. Page generated in 0.34708 seconds |
Home