> it does not help me much because it���s case sensitive.
add to your startup settings
NECPreferences caseSensitive: false
(or��Settings > Code Completion > Case Sensitive)
> just ignore middle word suggestions.
so Dict would match "Identity<Dict>ionary", but not "interdiction"? That sounds good.
> I think that there are many limitations because you are editing a text and not ast. Would be nice to have a placeholders like in xCode that allow you to enter parameters one by one after you���ve autocompleted multi-parameter message.��
The highlighter currently uses AST even as I type (if I am not mistaken), so it should be available there, but it surely requires investigation.
I'm not familiar with xCode/Objective-C, but the syntax seem that they wrap methods in brackets [] so you always knows the context of the parameter, no?
>��I see a lots of potential��doing precise code completion in the debugger/inspector/workspace based on��the runtime information available.
Yes, this is a good idea (although iterating on the result of the method can leave you blind again...).
>��Once I started digging into NECCompletion (or something like this) but its��inner behavior wasn't that trivial to me.
>��Yes, and we need to change it to use the AST instead of Shout��� that could simplify it a lot.
Which makes me wonder whether it would make sense to start something small from scratch instead of trying to force AST into the current one.
But we'll see...
Peter