[#IDEABKL-2878] Provide 'complete class' variation that only suggests project classes

IDEA: Backlog

Provide 'complete class' variation that only suggests project classes

Created: 25 Mar 05 16:39 Updated: 05 Aug 08 21:29

Component/s:

Editor. Code Completion

Affects Version/s:

None

Fix Version/s:

None

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

Build:

3,265

Description

« Hide

When using complete->class name, I always know if I'm looking for a project class or a class from a library (classpath).

It would be nice to have this level of distinction when using class completion:
1) Complete Class Name, using all candidates (the current implementation)
2) Complete Class Name, using project classes as filter (the requested addition)

Provide such an action, leaving it to the user to select a keyboard mapping (seems like all obvious candidate mappings are in use already)

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Maxim Shafirov - 29 Mar 05 00:44

I think having separate actions there is really bad idea. This way it won't be possible to switch quickly from one to another. We'll think of some different means of filtering though.

[ Permlink | « Hide ]

Taras Tielkes - 01 Jun 05 23:50

This is really starting to hurt, now that I'm completely hooked on the new CamelHump classname completion.

The problem is that in a project referencing 20 or more libraries and also the huge amount of JDK 1.5 internal sun.* classes, for most CamelHump codes (DMDS->DriverManagerDataSource), my project classes are outnumbered by library and JDK classes.