Bug 397791 - import namespace proposal
Summary: import namespace proposal
Status: NEW
Alias: None
Product: Xtend
Classification: Tools
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X
: P3 enhancement with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-09 14:08 EST by Eugen B CLA
Modified: 2013-08-26 03:42 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eugen B CLA 2013-01-09 14:08:02 EST 
If I want to manually import some Types/Namespaces like:

"import my.new.namespace." << Press CTRL+SPACE to hope that it Lists all possible sub namespaces, but nothing happens
Comment 1 Eugen B CLA 2013-01-16 15:13:32 EST 
Update:

If I do the same with "import my.new.namespace" (without a point after namespace), a suggestion-list pops up, and if I then write "." + a char of my desired Type, I can select it, and my "import" is complete.

But this doesn't work for namespaces.
Comment 2 Jan Koehnlein CLA 2013-01-22 17:26:39 EST 
Our new import infrastructure almost deprecates namespace imports, but code assist works fine for simple type names in imports, e.g.

import File << CTRL.SPACE

works nicely. Maybe we should add '.*' if the prefix is 'import static '. But given our dense agenda, I am not to sure whether code completion for namespaces should be scheduled for Kepler.