Home » Newcomers » Newcomers » Wishlist: Selection in eclipse editor
| Wishlist: Selection in eclipse editor [message #246316] |
Tue, 22 January 2008 07:10  |
Eclipse User |
|
|
|
Originally posted by: nick_nansen.hotmail.com
Here are two features that I would appreciate.
1.Earlier start for "select enclosing element"
It would be nice if this also was functional within certain
punctuations too. Selecting long strings would be a lot easier if
quotation marks also were concidered an element. Theoretically it
shouldn't be a problem also stopping at enclosing punctuations, as
there normally is no enclosing punctuations outside elements. So if
starting point is inside a string the first stop should be the
quotation marks. Also brackets like (), [] and {} would be useful
stops in programming.
I have missed this several times when I have copied something and want to
empty the string or bracket to insert new content.
2. Select inner content
This is closely related to the first suggestion. When I select
enclosing elements it is sometimes because i want to change what is
inside this. In HMTL I may select the div id="main_content" because
this nicely defines the entire content I am interested in. Inside there
may be several elements on the same level that doesn't select easily by
this method. Since I do not want to copy/delete the enclosing element
itself, it would be convenient to easily change the selection from
outer-mode to inner-mode.
This is also something I have missed when I want to reuse certain parts of
a bigger code through copy&paste.
I use the select enclosing elements (Alt+Arrow Up) a lot, but these two
possibilities would have made it even better in my perspective.
|
|
| |
| Re: Wishlist: Selection in eclipse editor [message #246368 is a reply to message #246339] |
Tue, 22 January 2008 09:18  |
| Eclipse User |
|
|
|
Originally posted by: nick_nansen.hotmail.com
Ed Merks wrote:
>> ... Selecting long strings would be a lot easier if
>> quotation marks also were concidered an element.
> It's not though. I don't really understand this part of your post.
I see your point, and I concidered not using the term "element" on this,
but it seemed practical though as the function is called "select enclosing
element". Even though it's not an element in the strict definition it's an
element in the wider definition, and it is enclosing something. Most often
a string. Maybe item would be better. I am not native english speaking so
I'm not sure what defines it best.
>> Theoretically it shouldn't be a problem also stopping at enclosing
>> punctuations, as there normally is no enclosing punctuations outside
>> elements. So if starting point is inside a string the first stop
>> should be the quotation marks.
> Are you talking Ctrl-Alt-Up-Arrow? It seems already to do what you
> describe.
Nothing would be better than if I just had missed a detail.
When I use Ctrl-Alt-Up-Arrow it stops at other items than I wish for. If i
have [a href="http//www.aquitelongurl.com/with/a.lot?of=parameters"
onclick="dosomething(cool)"]Link[/a] it would be nice to be able to select
the entire long link for deletion/copying by ctrl-alt-up-arrow. Now it
selects the entire link. Especially if I am just replacing the link after
a copy, this would be useful.
>> Also brackets like (), [] and {} would be useful stops in programming.
> The curly brace thing does work. Does does () but only if it's a
> parenthesized expression (not the condition of an "if" or a the
> arguments of a method call).
The cases I have tried have not worked like that, but maybe I've just
found the cases where it doesn't work. Nevertheless, it would be nice to
be able to configure this feature to stop at all kinds of enclosing items,
even if it is an "if". Even they may be long and complex and useful to
copy/delete.
>> I have missed this several times when I have copied something and want
>> to empty the string or bracket to insert new content.
> Personally I wouldn't like it to select something that's not a
> semantically complete Java construct as opposed to just a fragment of one...
I believe that if such a feature was implemented you wouldn't see much of
it, since it would only be an extra stop when you start inside one of the
enclosing items I'd like to define. Most often they are on the low level,
and the standard elements are on a higher level, which means you'd avoid
them by putting your marker outside "my" items, and if you should happen
to be inside it propably would be just one more up arrow to continue as
before.
It would also be possible to let the user define what should be defined as
an element.
>> 2. Select inner content
>> This is closely related to the first suggestion. When I select
>> enclosing elements it is sometimes because i want to change what is
>> inside this. In HMTL I may select the div id="main_content" because
>> this nicely defines the entire content I am interested in. Inside
>> there may be several elements on the same level that doesn't select
>> easily by this method. Since I do not want to copy/delete the
>> enclosing element itself, it would be convenient to easily change the
>> selection from outer-mode to inner-mode.
> I guess you are saying that Ctrl-Alt-Down-Arrow doesn't do what you
> want? It's really not entirely clear from your description...
Yes, at least it hasn't done so when I have tried. It selects the lower
level at the same node as I started. If i have a table with many rows and
columns a down arrow from table level will select only the td or tr I am
starting from, not all the tds in a row or all the trs inside the table.
This is of course correct as long as I am using up and down to select
levels, but in this case I want to leave the enclosing element (and only
that) when I am selecting.
I may want to copy content to another similar enclosing element, but with
new parameters defined in the element itself. (I.e tables or divs) or
wanting to reuse all of the definitions of the enclosing element but empty
the content in an easy way.
> You'd need to very clearly describe what you want it, it would need to
> fit in with the design intent of the actions, and it would need to be
> something that would be generally useful to most users most of the time....
I believed this was a logical expansion of the existing function since I
only asked for the possibility to define new items as an "element". My
focus was mostly on the term "enclosing", and i believed that enabling
different ways of selecting wrapped content would make things easier for
more people.
I don't think I am the only one handling content enclosed by other items
than the strict definition of an element, or content on the same level
_inside_ an enclosing item.
I will try to answer any uncertainties as quickly as possible. I do also
respect that other people have different needs from me, and that not all
needs can be covered. Still I believe that it is better to post my wishes
so that developers may concider if this is a possible feature to
implement, and maybe useful to more people than me.
|
|
|
| Re: Wishlist: Selection in eclipse editor [message #246388 is a reply to message #246368] |
Tue, 22 January 2008 10:53 |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Nickolas,
I'd assumed you were talking about the Java editor but much of what you
say sounds like it applies for an HTML/XML editor so maybe this is good
feedback to give on the web tools newsgroup (if I understand correctly
the context).
Nickolas wrote:
> Ed Merks wrote:
>
>>> ... Selecting long strings would be a lot easier if quotation marks
>>> also were concidered an element.
>> It's not though. I don't really understand this part of your post.
> I see your point, and I concidered not using the term "element" on
> this, but it seemed practical though as the function is called "select
> enclosing element". Even though it's not an element in the strict
> definition it's an element in the wider definition, and it is
> enclosing something. Most often a string. Maybe item would be better.
> I am not native english speaking so I'm not sure what defines it best.
>
>>> Theoretically it shouldn't be a problem also stopping at enclosing
>>> punctuations, as there normally is no enclosing punctuations outside
>>> elements. So if starting point is inside a string the first stop
>>> should be the quotation marks.
>> Are you talking Ctrl-Alt-Up-Arrow? It seems already to do what you
>> describe.
> Nothing would be better than if I just had missed a detail. When I use
> Ctrl-Alt-Up-Arrow it stops at other items than I wish for. If i have
> [a href="http//www.aquitelongurl.com/with/a.lot?of=parameters"
> onclick="dosomething(cool)"]Link[/a] it would be nice to be able to
> select the entire long link for deletion/copying by ctrl-alt-up-arrow.
> Now it selects the entire link. Especially if I am just replacing the
> link after a copy, this would be useful.
>>> Also brackets like (), [] and {} would be useful stops in programming.
>> The curly brace thing does work. Does does () but only if it's a
>> parenthesized expression (not the condition of an "if" or a the
>> arguments of a method call).
> The cases I have tried have not worked like that, but maybe I've just
> found the cases where it doesn't work. Nevertheless, it would be nice
> to be able to configure this feature to stop at all kinds of enclosing
> items, even if it is an "if". Even they may be long and complex and
> useful to copy/delete.
>
>>> I have missed this several times when I have copied something and
>>> want to empty the string or bracket to insert new content.
>> Personally I wouldn't like it to select something that's not a
>> semantically complete Java construct as opposed to just a fragment of
>> one...
> I believe that if such a feature was implemented you wouldn't see much
> of it, since it would only be an extra stop when you start inside one
> of the enclosing items I'd like to define. Most often they are on the
> low level, and the standard elements are on a higher level, which
> means you'd avoid them by putting your marker outside "my" items, and
> if you should happen to be inside it propably would be just one more
> up arrow to continue as before.
> It would also be possible to let the user define what should be
> defined as an element.
>
>>> 2. Select inner content
>>> This is closely related to the first suggestion. When I select
>>> enclosing elements it is sometimes because i want to change what is
>>> inside this. In HMTL I may select the div id="main_content" because
>>> this nicely defines the entire content I am interested in. Inside
>>> there may be several elements on the same level that doesn't select
>>> easily by this method. Since I do not want to copy/delete the
>>> enclosing element itself, it would be convenient to easily change
>>> the selection from outer-mode to inner-mode.
>> I guess you are saying that Ctrl-Alt-Down-Arrow doesn't do what you
>> want? It's really not entirely clear from your description...
> Yes, at least it hasn't done so when I have tried. It selects the
> lower level at the same node as I started. If i have a table with many
> rows and columns a down arrow from table level will select only the td
> or tr I am starting from, not all the tds in a row or all the trs
> inside the table. This is of course correct as long as I am using up
> and down to select levels, but in this case I want to leave the
> enclosing element (and only that) when I am selecting. I may want to
> copy content to another similar enclosing element, but with new
> parameters defined in the element itself. (I.e tables or divs) or
> wanting to reuse all of the definitions of the enclosing element but
> empty the content in an easy way.
>> You'd need to very clearly describe what you want it, it would need
>> to fit in with the design intent of the actions, and it would need to
>> be something that would be generally useful to most users most of the
>> time....
> I believed this was a logical expansion of the existing function since
> I only asked for the possibility to define new items as an "element".
> My focus was mostly on the term "enclosing", and i believed that
> enabling different ways of selecting wrapped content would make things
> easier for more people. I don't think I am the only one handling
> content enclosed by other items than the strict definition of an
> element, or content on the same level _inside_ an enclosing item.
> I will try to answer any uncertainties as quickly as possible. I do
> also respect that other people have different needs from me, and that
> not all needs can be covered. Still I believe that it is better to
> post my wishes so that developers may concider if this is a possible
> feature to implement, and maybe useful to more people than me.
|
|
|
| Re: Wishlist: Selection in eclipse editor [message #246415 is a reply to message #246388] |
Tue, 22 January 2008 13:45 |
| Eclipse User |
|
|
|
Originally posted by: nick_nansen.hotmail.com
Ed Merks wrote:
> Nickolas,
> I'd assumed you were talking about the Java editor but much of what you
> say sounds like it applies for an HTML/XML editor so maybe this is good
> feedback to give on the web tools newsgroup (if I understand correctly
> the context).
You're right that this has been an issue mainly in html/xml. But it is not
easy to find out where to post this among all these groups, so I thought
newcomer would be the least wrong...
|
|
|
Goto Forum:
Current Time: Mon Jun 09 05:04:55 EDT 2025
Powered by FUDForum. Page generated in 0.07872 seconds |
Home