hpi-swa-lab / nemo Goto Github PK

E.g.: startsWith is prioritized higher than fuzzy matching

The additional information can be used to display the source code where the chain information was found etc.

vs.

In the last example, the token at the current cursor position is #excessCode, not #keyword like in the first example.

Method suggestions now contain super class methods as well which, logically, are not included in the methodDict of the specific class
In those cases we receive a "Key not found" error

remove chain elements like ) or [ or ;

If the list contains "confirmPassword:" and you type "password", the entry is filtered due to case sensitivity.

Patterns

• permutations of arguments (morph red color -> morph color red)
• source includes (bounds -> size)
• isLiteral (morph size 10)
• check camel-case parts (instead of lowercase'ing everything... storeData .. matches red)
• look through all superclasses, too
• look through all inst vars for methods containing a substring (TextMorph height)
• rank by Method-Category (down-rank for private and extension methods etc.)

Examples

• FileSystem openFile: -> FileDirectory ...
• File readAllLines -> FileDirectory ...
• morph color: #red -> morph color: Color red
• m := Morph new. m color red -> morph color: Color red
• Smalltalk allClasses -> SystemNavigation allClasses
• TextMorph height -> get line height of all lines in a TextMorph
• aString lastIndex: -> aString lastIndexOf:
• morph requestFocus -> ActiveHand newKeyboadFocus: morph
• aCollection unique -> aCollection asSet

Side-effecting code is assumed when an AST contains:

• MessageNodes
• AssigmentNodes with a variable that is not temporary
• PragmaNodes

If a suggestion entry has a display value which is too long, it is simply clipped by the Morph.
Add something like a tooltip when hovering an entry or another possibility to view the hole entry.

Observed: No caret shown behind the self in the picture below, after having used the FancyUserInput stuff.

Expected: The caret to be placed there as usual - have a look at how the caret is placed in the actual FancyUI input.

Something like

morph on: aSelector do: aBlock
morph emit: #clicked

Think about implementing this in Paragraph to make it available for all components

Implementation Concept:

• KeyboardEvents are mapped to text commands (pattern)
• text commands can be grouped (e.g. a-z insertions are grouped together to simplify un-/redoing)

morph color red -> ctrl+f -> morph color: Color red
morph size 20@20 -> ctrl+f -> morph bounds: ... / morph extent: ...

• BPSuggestionEntry must be extended to distinct between value (what is pasted) and displayValue (what is shown in the list of suggestions)
• types must be tracked using the BPCOPObserver and written to the BPVariableTypeBook
• types must be guessed using BPVariableTypeBook if information is available there
• types must be guessed from the variable name

Observed: The caret is placed before the word that was selected from FancyUI.

Expected: it should be placed behind the word. Maybe the word should be selected as well (?)

Observed: The current menu morph has a type-to-select-an-entry logic, but instead of really filtering the result list, it just grayes-out the items that dont match.

Expected: It should reduce its list of results.

If you press Enter on an empty list -> exception

• Stop chain construction on closing parenthesis which have not been opened in the current chain (i.e. count number of opening/closing parenthesis)
• remove/advance incomplete selectors (validate via literal frame of method)
• handle huge methods like AbstractSound>>bachFugueVoice1On:

Use a block "onRightArrow: []" like "onSelect: []" to define the action outside of SuggestionMorph.

Reproduction:

• Open list of suggestions
• select any entry larger than index=1
• filter so that less that index items are displayed

Result:

• no selection is visible anymore
• pressing enter in this situation causes "out of bounds" exception

• process method additions
• process method deletions
• invalidate list (idle, timestamp, image closed ...)

BPWorkspace like BPBrowser?

hook into Morph>>keyboardFocusChange:

But do not close, if "owner" (Editor) is new focus owner.

As a foundation to track things like variable types
Base this on a unified Observer interface since we have more observation components coming (e.g. Markov list scanning etc.)

• cache hashes
• improve inclusion filtering

We had that already. Reintroduce it!