I liked the idea for the genius type completion, I only don't think that tab is a good key because it would conflict with live templates.
 
   []'s,
 
   Rodrigo.
-----Original Message-----
From: Jon Steelman [mailto:[EMAIL PROTECTED]]
Sent: quinta-feira, 4 de abril de 2002 15:00
To: [EMAIL PROTECTED]
Subject: Re: [Eap-list] a few 614 issues

Valentin Kipiatkov wrote:
But -- this was requested often -- wouldn't it make sense, if the
SmartCompletion falls back to BasicCompletion if there are no smart
suggestions?

This might make understanding of SmartType completion harder for novice
users, I think.
So then how about adding "GeniusType" completion? ;-)
...and keeping the current SmartType and Basic completion? It's an approach I suggested yesterday that gives a new combination completion. Here it is again--

This "GeniusType" combination completion would be in addition to the current Basic & SmartType but build off them. I would consider mapping it to the Tab key. Here's one way it could work to deal with your original objection and satisfy my goal:
* 1st tab pressed-- invoke SmartType if anything matches type else invoke Basic on 1st tab
* 2nd tab pressed-- invoke Basic (if SmartType was successfully invoked on 1st tab)
Valentin Kipiatkov
JetBrains, Inc / IntelliJ Software
http://www.intellij.com
"Develop with pleasure!"

----- Original Message -----
From: "Thomas Singer" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 02, 2002 8:08 PM
Subject: Re: [Eap-list] a few 614 issues
At 19:14 02.04.02 +0400, you wrote:
Code completion--
* For autocomplete, I assume there is no way to combine SmartType with
Basic in one keymap, but I think such a combined code completion
technique would be helpful. Ideally, SmartType would take effect if
possible but if it cannot then Basic completion would be in effect.
This is actually not that straightforward. For example in the following
code:

String s = a<code completion here>

you can either get

String s = aStringVar;
with SmartType code completion, or

String s = aNonStringVar.getSomeString();

by using normal completion. So the choice is up to you.
But -- this was requested often -- wouldn't it make sense, if the
SmartCompletion falls back to BasicCompletion if there are no smart
suggestions?

Tom

Reply via email to