Re: Re : Suggestion for improved LiveCode scripting notation

ROQUEFORT!!! On Oct 5, 2012, at 12:44 PM, Francis Nugent Dixon wrote: > No two minds think alike (Thank the man up there !) ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your sub

Re: Re : Suggestion for improved LiveCode scripting notation

CHEESE! On Oct 5, 2012, at 12:44 PM, Francis Nugent Dixon wrote: > 2 - Are you going to come back to your scripts >next year, and mutter "Who wrote this shit ?) ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to s

Re: Re : Suggestion for improved LiveCode scripting notation

How about next week :-)!!! I don't think anyone is trying to impose any standards, just gathering ideas on how people tackle the issue. Pete lcSQL Software On Fri, Oct 5, 2012 at 12:44 PM, Francis Nugent Dixon wrote: > 2 - Are you going to come back to your scripts >

Re : Suggestion for improved LiveCode scripting notation

Hi from Beautiful Brittany, I think we have been round this subject several times. 1 - As anybody going to look at your scripts ? (chances are already vastly reduced !) 2 - Are you going to come back to your scripts next year, and mutter "Who wrote this shit ?) 3 - As a principle, do you

Re: SUggestion for improved LiveCode scripting notation

Thanks Jacque, didn't know about the right click options. Pete lcSQL Software On Fri, Oct 5, 2012 at 10:24 AM, J. Landman Gay wrote: > Right-click the handler name in the script, choose "Go to definition" in > the contextual menu. _

Re: SUggestion for improved LiveCode scripting notation

That's a great idea! I've used comments to divide up handlers of different types but that, of course, doesn't show up in the list of scripts. Pete lcSQL Software On Fri, Oct 5, 2012 at 10:32 AM, Charles E Buchwald wrote: > I don't use GLX2 so I can't do grouping like tha

Re: SUggestion for improved LiveCode scripting notation

In this case that makes no difference. If the function is being defined, its yours, since functions are not events/messages. On Fri, Oct 5, 2012 at 12:27 PM, Peter Haworth wrote: > Yes, I do that too but unfortunately there's no alternative to "function". > Pete > lcSQL Software

Re: SUggestion for improved LiveCode scripting notation

Yes, I do that too but unfortunately there's no alternative to "function". Pete lcSQL Software On Fri, Oct 5, 2012 at 9:50 AM, Mike Bonner wrote: > While not the same thing as you are talking about, when I write scripts I > use the "on" form for lc commands and handlers

Re: SUggestion for improved LiveCode scripting notation

Am 05.10.2012 um 19:32 schrieb Charles E Buchwald : >> On Oct 5, 2012, at 9:50 AM, Mike Bonner wrote: >> >>> While not the same thing as you are talking about, when I write scripts I >>> use the "on" form for lc commands and handlers and any that are created >>> soley by me I use the "command" f

Re: SUggestion for improved LiveCode scripting notation

> On Oct 5, 2012, at 9:50 AM, Mike Bonner wrote: > >> While not the same thing as you are talking about, when I write scripts I >> use the "on" form for lc commands and handlers and any that are created >> soley by me I use the "command" form. This way it only takes a glance to >> know which are

Re: SUggestion for improved LiveCode scripting notation

On 10/5/12 11:47 AM, Peter Haworth wrote: This is something I've thought about too. Even for my own use, coming back to code I haven't looked at for some time, it's sometimes hard to remember where a handler is located. Right-click the handler name in the script, choose "Go to definition" in

Re: SUggestion for improved LiveCode scripting notation

I group them. I use GLX2, which has a feature that allows you to create categories of commands and functions by entering --> and some text in the script of an object. Everything that comes after that and before the next declaration gets grouped into it's own "folder" in the left pane. I believe

Re: SUggestion for improved LiveCode scripting notation

While not the same thing as you are talking about, when I write scripts I use the "on" form for lc commands and handlers and any that are created soley by me I use the "command" form. This way it only takes a glance to know which are mine and which are built in. On Fri, Oct 5, 2012 at 10:47 AM, P

Re: SUggestion for improved LiveCode scripting notation

This is something I've thought about too. Even for my own use, coming back to code I haven't looked at for some time, it's sometimes hard to remember where a handler is located. As part of the docs for my code, I have a script that goes through all the scripts in a stack file, lists every handler

SUggestion for improved LiveCode scripting notation

Reading someone's LiveCode scripting has been improved by adding the prefix "t" (for temporary) to the notation for a local variable and "g" for a global variable. With the increase in the number of scripting words, it also has helped to use the prefixes "mobile", "iphone", "android", and "