Re: [opensource-dev] Enhanced Script Editor Request

2010-10-21 Thread Argent Stonecutter
On 2010-10-20, at 18:07, Ricky wrote: > lol... That comment reminds me of this (tongue-in-cheek,) graphic > representing the learning curves for a variety of common editors: > http://blogs.msdn.com/b/steverowe/archive/2004/11/17/code-editor-learning-curves.aspx Pet peeve time: I understand the co

Re: [opensource-dev] Enhanced Script Editor Request

2010-10-21 Thread Argent Stonecutter
On 2010-10-20, at 13:20, malachi wrote: > For you windows developers who are using Visual Studio, When you type a > function name and get to the ( point of the function it pops a tip up > telling you what is needed to complete this function. The SL editor already has this: you just hover the m

Re: [opensource-dev] Enhanced Script Editor Request

2010-10-20 Thread Glen Canaday
I do sometimes wonder what happened to i, ii, iii, iv, and v, though. Must be like that "Leonard Part 6" movie Bill Cosby did in the early 80's. --GC On Wed, 2010-10-20 at 19:45 -0500, Dave Booth wrote: > On 10/20/2010 18:40, Ponzu wrote: > > Alas, so many generations of coder who learned vi from

Re: [opensource-dev] Enhanced Script Editor Request

2010-10-20 Thread Glen Canaday
On Wed, 2010-10-20 at 19:40 -0400, Ponzu wrote: > Alas, so many generations of coder who learned vi from someone who > already didn't know vi. > > > You will note that Google's new keyboard commands are vi commands. > There is a reason for this. > Google... has keyboard commands? :wq , :i, :q

Re: [opensource-dev] Enhanced Script Editor Request

2010-10-20 Thread Dave Booth
On 10/20/2010 18:40, Ponzu wrote: > Alas, so many generations of coder who learned vi from someone who > already didn't know vi. > > You will note that Google's new keyboard commands are vi commands. > There is a reason for this. > same reason that most chat apps commands are IRC commands :) /m

Re: [opensource-dev] Enhanced Script Editor Request

2010-10-20 Thread Ponzu
Alas, so many generations of coder who learned vi from someone who already didn't know vi. You will note that Google's new keyboard commands are vi commands. There is a reason for this. On Wed, Oct 20, 2010 at 7:23 PM, Altair Sythos wrote: > On Wed, 20 Oct 2010 16:07:31 -0700 > Ricky wrote: >

Re: [opensource-dev] Enhanced Script Editor Request

2010-10-20 Thread malachi
I didn't mean add something that would allow editing in an external program. It is bad enough on older machines to run SL alone. and opening multiple programs is not enough. Perhaps tool tips are a bit out of the way i agree with others that the tooltip can sometimes be annoying. but instea

Re: [opensource-dev] Enhanced Script Editor Request

2010-10-20 Thread Sythos
On Wed, 20 Oct 2010 16:07:31 -0700 Ricky wrote: > lol... That comment reminds me of this (tongue-in-cheek,) graphic > representing the learning curves for a variety of common editors: > http://blogs.msdn.com/b/steverowe/archive/2004/11/17/code-editor-learning-curves.aspx damn awaked my wife laug

Re: [opensource-dev] Enhanced Script Editor Request

2010-10-20 Thread Ricky
lol... That comment reminds me of this (tongue-in-cheek,) graphic representing the learning curves for a variety of common editors: http://blogs.msdn.com/b/steverowe/archive/2004/11/17/code-editor-learning-curves.aspx vi indeed... I'm a pico guy myself, but I'll stoop to using Programmer's Notepa

Re: [opensource-dev] Enhanced Script Editor Request

2010-10-20 Thread Brandon Husbands
I will submit my external editor patch to snow storm On Oct 20, 2010 5:39 PM, "Ponzu" wrote: Make the script editor use vi. On Wed, Oct 20, 2010 at 6:19 PM, Ricky wrote: > > It used to stay up until cli... ___ Policies and (un)subscribe informati

Re: [opensource-dev] Enhanced Script Editor Request

2010-10-20 Thread Ponzu
Make the script editor use vi. On Wed, Oct 20, 2010 at 6:19 PM, Ricky wrote: > It used to stay up until clicked on or until certain characters were > typed... Got in the the way at times, but was quite useful. > > > On Wed, Oct 20, 2010 at 3:08 PM, SuezanneC Baskerville > wrote: > > I'd be ple

Re: [opensource-dev] Enhanced Script Editor Request

2010-10-20 Thread Ricky
It used to stay up until clicked on or until certain characters were typed... Got in the the way at times, but was quite useful. On Wed, Oct 20, 2010 at 3:08 PM, SuezanneC Baskerville wrote: > I'd be pleased if the popup tip remained visible somewhere. My short term > memory is bad, if there are

Re: [opensource-dev] Enhanced Script Editor Request

2010-10-20 Thread Frans
I have the same problem as Suezanne. When I use the popup is usually for something longwinded and frequently have to make the popup appear several times. If the popup would appear automatically and I could hit tab,space or enter to have it auto complete that would be perfect. Frans On Thu, Oct 21

Re: [opensource-dev] Enhanced Script Editor Request

2010-10-20 Thread SuezanneC Baskerville
I'd be pleased if the popup tip remained visible somewhere. My short term memory is bad, if there are many parameters I have to make the popup appear more than once. On Wed, Oct 20, 2010 at 3:53 PM, Ricky wrote: > I think the idea here is to have the popup capable of doing > auto-completion. Th

Re: [opensource-dev] Enhanced Script Editor Request

2010-10-20 Thread Ricky
I think the idea here is to have the popup capable of doing auto-completion. This would save a load of time, as well as make it easier to script, IMHO. An alternative would be to expand the usefulness of the code insert dropdown by having it add the parens and properties for events and functions

Re: [opensource-dev] Enhanced Script Editor Request

2010-10-20 Thread Dave Booth
On 10/20/2010 13:20, malachi wrote: > Of all the developers who are working on the client someone has to be > smart enough to implement this. > > For you windows developers who are using Visual Studio, When you type a > function name and get to the ( point of the function it pops a tip up > telling