Atte, Welcome back--great ideas. Both of these seem pretty straightforward implementation-wise, so Ill look into getting them in the next version. Kassen, see comments below-- On Jun 7, 2007, at 5:34 AM, Kassen wrote:

On 6/7/07, Atte André Jensen wrote:

...

I have two minor requests for the mini:

1) Make the char position avaliable somewhere,

Agreed! That would be very usefull.

Friendly reminder; there is still a bug that makes the character that's supposedly offensive increment in the error report after re-trying to run the same code which already got a error (for example because you're stuborn, drunk or suspect you hit the wrong hotkey first time'round).

Yeah, I feel like this must be a not too difficult fix.

For bonus points; highlight the offending character when code fails to run.

Sounds like a good idea to me.

...

2) keyboard shortcuts for switching between tabs in the editor.

Would be very usefull indeed. Helpfull note for Mac native developers; in Windows the standard way of doing this is "Ctrl + Tab" to cycle forward and the same plus shift to cycle back

Also; something I thought of myself a while ago. I frequently have the situation where I type things "from the inside towards the outside" with regard to brackets. I might write a inner loop first, then add another around it or write some statement to later place this inside of the brackets of a function-call.

What I think might be a nice time-saver would be highlighting some bit if text,then hitting "[", "(" or "{" and making the mini enclose that bit of text in that kind of bracket.

This might need some thought/debate because it's definately non-standard. My resoning is that the moment when you need this are exactly the moment where you are mentally jugeling a relatively large amount of things and anything that breaks the flow of thought at that point is likely to lead to mistakes.

This is a pretty interesting idea. Although it does seem a little non-standard, I feel like apps like Eclipse have similar functionality. Maybe like Ctrl [ ( or {, in addition to my new favorite keyboard shortcut, Ctrl / which comments out the selected text. spencer

Kas. _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

Hi All, About those keyboard short cuts: Let me suggest something different. Just make the user interface configurable. The keyboard short cuts in particular. Just think about i18n issues. For instance ctrl+/ is not that easy to do on a german keyboard: There, the '/' is above the '7' (unless you use the number block 'divide' key). I was sitting in front of a French keyboard lately, and here again nothing was "where it's supposed to be". With so many different keyboard layouts around, I think it does make little sense to have hard wired keyboard short cuts. Or just think about different user types. Many people are quite "religious" about their particular style of working. Just watch one of those emacs vs vi vs <rest of the world> threads... :-) Cheers, --lu

*grin* Code completion was actually one of the original design goals of miniAudicle, and has been sort of ominously perched on my internal todo list since the beginning. The biggest difficulty with code completion right now is that one essentially needs to parse most or all of the relevant code to make it work. Ive recently realizeed that the way many tools (Xcode, Eclipse) do this is to actually use the full compiler to get some sort of abstract syntax tree and then go from there, instead of more simplistic text processing. spencer On Jun 10, 2007, at 12:43 PM, Leuthold Dominik wrote:

hi all

i'm a bit surprised that "code completion" wasn't mentioned till now. (or is it already in the wishlist?) i'd really like to see something similar like m$ IntelliSense implemented in the mini. (hehe... i like my visual studio:-) i'm often in the situation that i'm not sure how to spell a specific command (uppper/lowercae, or eg. is it keyOn?, or noteOn?) or that i'm not sure about the type of parameters for a function. therefor i always need to look in the documentation wich is really time consuming.

in my personal opinion, a code completion would speed up coding a lot.

jassas /moudi

_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users