Home » Archived » Visual Editor (VE) » Suggestion: Prompt for control name at creation time
| Suggestion: Prompt for control name at creation time [message #79169] |
Sat, 05 February 2005 11:22  |
 Howard Treisman
Messages: 6
Registered: July 2009 |
Junior Member |
|
|
Hi
VE is a great tool - thank you to all who contribute.
One suggestion that would make life quicker and easier:
When you create a new visual component, VE gives it a default name eg
JButton, JButton1, JButton2, etc. I always immediately right click on the
compoent and use the "Rename Field" menu option. This uses Eclipse
refactoring to modify the name of the field, which works fine. However, it
is generally VERY slow, and also causes the focus to be lost.
My suggestion:
Have a preference that allows you to specify that VE will prompt for a
component name before it is actually created. This will dramatically speed
up coding time.
I also think this is a good practise to impose on myself, and others in my
company - having our code littered with components called JButton1,
JButton2, etc, for anything other than a hack/prototype, is bad programming
practise.
Many thanks,
Howard
|
|
|
| Re: Suggestion: Prompt for control name at creation time [message #79257 is a reply to message #79169] |
Mon, 07 February 2005 17:32  |
Joe Winchester
Messages: 496
Registered: July 2009 |
Senior Member |
|
|
Hi Howard,
> One suggestion that would make life quicker and easier:
> When you create a new visual component, VE gives it a default name eg
> JButton, JButton1, JButton2, etc. I always immediately right click on the
> compoent and use the "Rename Field" menu option. This uses Eclipse
> refactoring to modify the name of the field, which works fine. However, it
> is generally VERY slow, and also causes the focus to be lost.
If you use the property sheet there is a property called "fieldName".
Using this should use the local rename which is the same as the Ctrl+1
and "Rename field" option which doesn't use refactoring. The "rename
field" option you're using should look at the field and check to see
whether or not the faster Ctrl+1 option can be used, and only do the
full refactoring option if required (i.e. the field or its accessor
isn't protected so there might be the possibilitiy of someone else using
it). I believe we might have a problem with this however from your
description so please open a bugzilla problem for us to look into what's
going on. The refactoring is slower because it requires a save of the
file which then causes the entire VE to re-open so it's a big trigger to
pull.
> My suggestion:
> Have a preference that allows you to specify that VE will prompt for a
> component name before it is actually created. This will dramatically speed
> up coding time.
We toyed with this idea and actually designed a GUI that would appear
with the field name, together with an extension API so this could be
specific for each component (on certain controls there are other
settings that you always specify like a button's label or panel's layout
manager)). We haven't implemented this yet, so please open a bugzilla
feature requrest for us with your ideas.
Best regards,
Joe
|
|
|
| Re: Suggestion: Prompt for control name at creation time [message #79620 is a reply to message #79257] |
Wed, 09 February 2005 10:06 |
Howard Treisman
Messages: 6
Registered: July 2009 |
Junior Member |
|
|
Hi Joe
Thanks for the response.
I know about the the "local rename" option via the fieldName property, which
is much faster, as you indicate. However, this has the disadvantage that it
doesn't update the geneated javadoc, which means that your javadoc and code
get out of synch.
I will log my suggestion via bugzilla (as soon as I find out where it is and
how to use it - still a bit of a newbie up here). Also apologise for posting
enhancement requests on the newgroup - I'm guessing that those should go
straight into bugzilla.
Thanks,
Howard
"Joe Winchester" <winchest@uk.ibm.com> wrote in message
news:cu7n54$khg$1@www.eclipse.org...
> Hi Howard,
>
> > One suggestion that would make life quicker and easier:
> > When you create a new visual component, VE gives it a default name eg
> > JButton, JButton1, JButton2, etc. I always immediately right click on
the
> > compoent and use the "Rename Field" menu option. This uses Eclipse
> > refactoring to modify the name of the field, which works fine. However,
it
> > is generally VERY slow, and also causes the focus to be lost.
>
> If you use the property sheet there is a property called "fieldName".
> Using this should use the local rename which is the same as the Ctrl+1
> and "Rename field" option which doesn't use refactoring. The "rename
> field" option you're using should look at the field and check to see
> whether or not the faster Ctrl+1 option can be used, and only do the
> full refactoring option if required (i.e. the field or its accessor
> isn't protected so there might be the possibilitiy of someone else using
> it). I believe we might have a problem with this however from your
> description so please open a bugzilla problem for us to look into what's
> going on. The refactoring is slower because it requires a save of the
> file which then causes the entire VE to re-open so it's a big trigger to
> pull.
>
> > My suggestion:
> > Have a preference that allows you to specify that VE will prompt for a
> > component name before it is actually created. This will dramatically
speed
> > up coding time.
>
> We toyed with this idea and actually designed a GUI that would appear
> with the field name, together with an extension API so this could be
> specific for each component (on certain controls there are other
> settings that you always specify like a button's label or panel's layout
> manager)). We haven't implemented this yet, so please open a bugzilla
> feature requrest for us with your ideas.
>
> Best regards,
>
> Joe
|
|
| |
| Re: Suggestion: Prompt for control name at creation time [message #605027 is a reply to message #79169] |
Mon, 07 February 2005 17:32 |
Joe Winchester
Messages: 496
Registered: July 2009 |
Senior Member |
|
|
Hi Howard,
> One suggestion that would make life quicker and easier:
> When you create a new visual component, VE gives it a default name eg
> JButton, JButton1, JButton2, etc. I always immediately right click on the
> compoent and use the "Rename Field" menu option. This uses Eclipse
> refactoring to modify the name of the field, which works fine. However, it
> is generally VERY slow, and also causes the focus to be lost.
If you use the property sheet there is a property called "fieldName".
Using this should use the local rename which is the same as the Ctrl+1
and "Rename field" option which doesn't use refactoring. The "rename
field" option you're using should look at the field and check to see
whether or not the faster Ctrl+1 option can be used, and only do the
full refactoring option if required (i.e. the field or its accessor
isn't protected so there might be the possibilitiy of someone else using
it). I believe we might have a problem with this however from your
description so please open a bugzilla problem for us to look into what's
going on. The refactoring is slower because it requires a save of the
file which then causes the entire VE to re-open so it's a big trigger to
pull.
> My suggestion:
> Have a preference that allows you to specify that VE will prompt for a
> component name before it is actually created. This will dramatically speed
> up coding time.
We toyed with this idea and actually designed a GUI that would appear
with the field name, together with an extension API so this could be
specific for each component (on certain controls there are other
settings that you always specify like a button's label or panel's layout
manager)). We haven't implemented this yet, so please open a bugzilla
feature requrest for us with your ideas.
Best regards,
Joe
|
|
|
| Re: Suggestion: Prompt for control name at creation time [message #605131 is a reply to message #79257] |
Wed, 09 February 2005 10:06 |
Howard Treisman
Messages: 6
Registered: July 2009 |
Junior Member |
|
|
Hi Joe
Thanks for the response.
I know about the the "local rename" option via the fieldName property, which
is much faster, as you indicate. However, this has the disadvantage that it
doesn't update the geneated javadoc, which means that your javadoc and code
get out of synch.
I will log my suggestion via bugzilla (as soon as I find out where it is and
how to use it - still a bit of a newbie up here). Also apologise for posting
enhancement requests on the newgroup - I'm guessing that those should go
straight into bugzilla.
Thanks,
Howard
"Joe Winchester" <winchest@uk.ibm.com> wrote in message
news:cu7n54$khg$1@www.eclipse.org...
> Hi Howard,
>
> > One suggestion that would make life quicker and easier:
> > When you create a new visual component, VE gives it a default name eg
> > JButton, JButton1, JButton2, etc. I always immediately right click on
the
> > compoent and use the "Rename Field" menu option. This uses Eclipse
> > refactoring to modify the name of the field, which works fine. However,
it
> > is generally VERY slow, and also causes the focus to be lost.
>
> If you use the property sheet there is a property called "fieldName".
> Using this should use the local rename which is the same as the Ctrl+1
> and "Rename field" option which doesn't use refactoring. The "rename
> field" option you're using should look at the field and check to see
> whether or not the faster Ctrl+1 option can be used, and only do the
> full refactoring option if required (i.e. the field or its accessor
> isn't protected so there might be the possibilitiy of someone else using
> it). I believe we might have a problem with this however from your
> description so please open a bugzilla problem for us to look into what's
> going on. The refactoring is slower because it requires a save of the
> file which then causes the entire VE to re-open so it's a big trigger to
> pull.
>
> > My suggestion:
> > Have a preference that allows you to specify that VE will prompt for a
> > component name before it is actually created. This will dramatically
speed
> > up coding time.
>
> We toyed with this idea and actually designed a GUI that would appear
> with the field name, together with an extension API so this could be
> specific for each component (on certain controls there are other
> settings that you always specify like a button's label or panel's layout
> manager)). We haven't implemented this yet, so please open a bugzilla
> feature requrest for us with your ideas.
>
> Best regards,
>
> Joe
|
|
| |
Goto Forum:
Current Time: Fri Apr 26 12:58:59 GMT 2024
Powered by FUDForum. Page generated in 0.03288 seconds |
] 
Search
Help
Register
Login
Home
