1. WEE Subroutine Arguments and Completions
- Posted by dcuny Feb 02, 2015
- 1403 views
I'm not sure what WEE can be expected to do at this point (WEE changelog, perhaps? 
), but a couple things I noticed:
Routine arguments don't pop up for built-in routines like length() or sin(). This seems an odd omission.
There's no feedback on routine arguments when the routine wasn't found. I'm sort of on the fence about this - I can't tell if WEE is broken or doesn't implement some functionality, or if the routine simply hasn't been defined yet. I'm not sure a popup with "No matches found" would be helpful or not.
Completions aren't in sorted order. Alpha sorting would make it easier to use.
I love the auto-include. Love it, love it, love it! 
The colon (:) symbol seems to confuse completions. For example:
include "filter.e" as filter function foo(integer x, integer y) end function
If I then type the code:
filter:
WEE helpfully proposes foo as an option. I've got no clue why it does that, since foo() isn't in the namespace filter.
I'm really looking forward to WEE supporting completions with namespaces!
Adding information to the display on the autocomplete would be nice. In Eclipse, the format is:
TYPE_ICON ROUTINE_NAME( ARG_1, ARG_2 ... ) : RETURN_TYPE - CLASS_NAME
Where CLASS_NAME is in light grey, so it doesn't overwhelm the list. I don't know if you have color control on the Scintilla list.
- David
2. Re: WEE Subroutine Arguments and Completions
- Posted by PeteE Feb 02, 2015
- 1406 views
Routine arguments don't pop up for built-in routines like length() or sin(). This seems an odd omission.
If it doesn't exist in the include files, WEE doesn't know about it. I suppose I can hardcode a list of builtins with arguments into the parser... I'll put it on the todo list.
There's no feedback on routine arguments when the routine wasn't found. I'm sort of on the fence about this - I can't tell if WEE is broken or doesn't implement some functionality, or if the routine simply hasn't been defined yet. I'm not sure a popup with "No matches found" would be helpful or not.
Completions aren't in sorted order. Alpha sorting would make it easier to use.
I debated sorting the list, and went with having the items in declaration order. Since you think sorted would be easier, I'll change it.
I love the auto-include. Love it, love it, love it!
Me too. This is absolutely the most fun I've had programming in over a decade.
The colon (:) symbol seems to confuse completions. For example:
WEE helpfully proposes foo as an option. I've got no clue why it does that, since foo() isn't in the namespace filter.
I'm really looking forward to WEE supporting completions with namespaces!
The parser is currently still broken in regards to namespaces. I spend hours yesterday hacking on it, and it still doesn't work right. The whole namespace/global/public/export/"public include" rules and permutations are really complicated. I miss just having "include" and "global".
Adding information to the display on the autocomplete would be nice. In Eclipse, the format is:
TYPE_ICON ROUTINE_NAME( ARG_1, ARG_2 ... ) : RETURN_TYPE - CLASS_NAME
Where CLASS_NAME is in light grey, so it doesn't overwhelm the list. I don't know if you have color control on the Scintilla list.
Well, it does support icons, so I could do icons with a letter for the type of the symbol, like (f)unction (p)rocedure (t)ype (c)onstant (i)nteger (s)equence, (o)bject, (e)num. But with the arguments I feel the list might be too wide. I will give it a shot.
3. Re: WEE Subroutine Arguments and Completions
- Posted by dcuny Feb 02, 2015
- 1407 views
I should note that icons aren't high on my wish list... I just thought I'd mention them.
But... they would be cool!
- David
4. Re: WEE Subroutine Arguments and Completions
- Posted by mattlewis (admin) Feb 03, 2015
- 1373 views
If it doesn't exist in the include files, WEE doesn't know about it. I suppose I can hardcode a list of builtins with arguments into the parser... I'll put it on the todo list.
In wxide, I pull stuff from euphoria/keywords.e. The downside is that there is no parameter information for that.
Matt
5. Re: WEE Subroutine Arguments and Completions
- Posted by PeteE Feb 03, 2015
- 1375 views
I added the builtins and their parameters to the calltips. Autocompletion lists are now sorted. Namespace autocomplete is a little better, but 'include as' is still not working.
6. Re: WEE Subroutine Arguments and Completions
- Posted by dcuny Feb 03, 2015
- 1356 views
It looks good!
- David
7. Re: WEE Subroutine Arguments and Completions
- Posted by dcuny Feb 04, 2015
- 1318 views
I should have mentioned this before - I noticed you changed autocomplete of for from:
for .. .= to do end for
to:
for ... do end for
That works a lot better, thanks!
- David
8. Re: WEE Subroutine Arguments and Completions
- Posted by PeteE Feb 04, 2015
- 1299 views
Yes, I too was annoyed by having to move the cursor between "for = to do". Euphoric suggested using tab to move between each field, and I may have enter do the same thing like it allows you to jump over the "do" to the next line. I can also make it so that the " = to " is overtypeable, meaning if you just type out for the for statement normally, you end up with the same result. In case you haven't noticed, when you type '[' it inserts the closing ']' automatically, but you can still type the ']' and it overwrite the inserted one.
