Bug 241002 - Support "Smart Caret Positioning" in fields with IDs and Java identifiers
Summary: Support "Smart Caret Positioning" in fields with IDs and Java identifiers
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: bugday
Depends on:
Blocks:
 
Reported: 2008-07-15 17:42 EDT by Tonny Madsen CLA
Modified: 2019-09-09 02:24 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tonny Madsen CLA 2008-07-15 17:42:29 EDT
The Java editor - and certain dialogs as well - supports "Smart Caret Positioning" when moving forward and backward one word (CTRL Arrow Left and Right as well as CTRL+SHIFT Arrow Left and Right) in Java identifiers.

It would be very nice if PDE could do the same for Java fields.

For ID fields - all other fields???? - it would be nice if '.' (period) was used as a word separator...
Comment 1 Peter Friese CLA 2008-07-16 06:19:29 EDT
Tonny, I took a look at the the PDE manifest editor and found that the following behaviour is already implemented both in the forms editor as well as in the source editor:

1) The dot (.) acts as a word boundary in ID fields
2) The dot (.) acts as a word boundary in class fields as well

I suppose you'd like to (additionally) have camel-cased selection as in the following example:

1) <formatter class="org.eclipse.xtext.ui.service.impl.BuiltInFormatter"
2) Place the caret right after "BuildInFormatter"
3) Press CTRL + SHIFT + Left Arrow
4) "Formatter" is selected

Is this what you are looking for?
Comment 2 Tonny Madsen CLA 2008-07-16 06:52:43 EDT
Hi Peter, I just tried the following

1) Create new plug-in project with the name and ID test.test
2) Add views extension point
2) Add view element


All fields treat '.' (period) as a word character and does not recognize CamelCase - this includes the ID and activator fields on the overview page and the id, class and icon fields on the view element on the Extensions page...

Camel case support would be perfect :-)
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:12:57 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 4 Julian Honnen CLA 2019-09-09 02:24:24 EDT
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.