[chuck-users] two gui wishes for miniAudicle

Spencer Salazar ssalazar at CS.Princeton.EDU
Sat Jun 9 00:57:47 EDT 2007


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 <atte.jensen at gmail.com> 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 at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users



More information about the chuck-users mailing list