Why not? It's in the dictionary!
au·to·mag·ic·al·ly
ˌôdəˈmajək(ə)lē/
adverbinformal
adverb: automagically
• (especially in relation to the operation of a computer process)
automatically and in a way that seems ingenious, inexplicable, or magical.
"just type in the name of what you want t
Ehm... some complicated condition might be 5 lines of code.
Bob S
> On Aug 10, 2017, at 18:38 , Mark Wieder via use-livecode
> wrote:
>
>> if some complicated condition then # I’m a makin’ spaghetti
>>— spaghetti
>> end if # I’m a makin' spaghetti
>
> I would actually argue against this
Wait, you're saying that this is a win win, where everybody... WINS???
BAN it! ;-)
Bob S
> On Aug 10, 2017, at 11:55 , J. Landman Gay via use-livecode
> wrote:
>
> Well, you don't actually have to use the tooltip. It wouldn't interfere with
> your current method and would enhance the edito
On 08/11/2017 08:50 AM, Mark Waddingham via use-livecode wrote:
> they aren't likely to happen until someone actually has some 'time'
to do the necessary thinking
Um. Yes. That would be you.
--
Mark Wieder
ahsoftw...@gmail.com
___
use-livecode ma
On Thu, Aug 10, 2017 at 6:24 PM, Monte Goulding via use-livecode <
use-livecode@lists.runrev.com> wrote:
>
> 2. automagical maintenance if the comments exist and you change the
> conditio
>
Oooh, yes; automagical maintenance would be wonderful! (really? my
spellchecker recognizes "automagical" a
On 2017-08-11 17:40, Mark Wieder via use-livecode wrote:
On 08/11/2017 02:51 AM, Mark Waddingham via use-livecode wrote:
Naming loops in a syntactic way certainly sounds like a useful thing
to do:
I should point out here that Robert Cailliau has complained about the
lack of named loops as one
On 08/11/2017 02:51 AM, Mark Waddingham via use-livecode wrote:
Naming loops in a syntactic way certainly sounds like a useful thing to do:
I should point out here that Robert Cailliau has complained about the
lack of named loops as one of the main deficiencies of LiveCode for some
ten years
...@lists.runrev.com] On Behalf
Of Mark Waddingham via use-livecode
Sent: Friday, August 11, 2017 5:51 AM
To: How to use LiveCode
Cc: Mark Waddingham
Subject: Re: Bug 20255 - Simple Loop Labeling
On 2017-08-10 21:33, Dr. Hawkins via use-livecode wrote:
> In fact, what I would *like* is modern Fortran st
On 2017-08-11 14:56, Lagi Pittas via use-livecode wrote:
I thought you didn't agree with USING next repeat as a structured way
of
programming - Reading and understanding before my Brain was in gear.
Sorry - I should have made that more clear - 'next repeat' and 'exit
repeat' are definitely im
HI Mark,
I was probably reading more into this ...
"Certainly 'exit repeat ...' would not be harmful, 'next repeat ...' I'd
have to analyze more deeply"
I thought you didn't agree with USING next repeat as a structured way of
programming - Reading and understanding before my Brain was in gear.
On 2017-08-11 12:51, Lagi Pittas via use-livecode wrote:
Hi Mark,
I Beg to Differ about Next Repeat.
"It's not wat you do it's the way that you do it" comes to mind
Someone who writes spaghetti code can do it very well in any language
but
its much more difficult without the structure brought
Hi Mark,
I Beg to Differ about Next Repeat.
"It's not wat you do it's the way that you do it" comes to mind
Someone who writes spaghetti code can do it very well in any language but
its much more difficult without the structure brought in by the
Algol/Pascal/Modula.
I have not used a Goto Since
On 2017-08-10 21:33, Dr. Hawkins via use-livecode wrote:
In fact, what I would *like* is modern Fortran style labelling or
something
like that, and the ability to the those labels to controls like next
and
exit. This, however, would accomplish so much with so little.
Thinking out loud here a
+100 To Mark for that one
In fact it could copy the complicated condition AND any comment after it -
best of all possible worlds
Lagi
On 11 August 2017 at 02:38, Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On 08/10/2017 06:24 PM, Monte Goulding via use-livecode wrote:
I like and use end if #some complicated condition
On Thu, Aug 10, 2017 at 10:02 PM, Monte Goulding via use-livecode <
use-livecode@lists.runrev.com> wrote:
>
> > On 11 Aug 2017, at 11:54 am, Mark Wieder via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > What would you put as a co
> On 11 Aug 2017, at 11:54 am, Mark Wieder via use-livecode
> wrote:
>
> What would you put as a comment after the 'end if' using your proposed
> approach? The original comment for the 'if' statement or something else?
> Would you force the user to create comments for each 'else if' as well?
On 08/10/2017 06:40 PM, Monte Goulding via use-livecode wrote:
On 11 Aug 2017, at 11:38 am, Mark Wieder via use-livecode
wrote:
I would actually argue against this. For me, the useful part would be
end if # some complicated condition
Otherwise, making the user come up with a comment that b
> On 11 Aug 2017, at 11:38 am, Mark Wieder via use-livecode
> wrote:
>
> I would actually argue against this. For me, the useful part would be
>
> end if # some complicated condition
>
> Otherwise, making the user come up with a comment that basically says "some
> complicated condition" anyw
On 08/10/2017 06:24 PM, Monte Goulding via use-livecode wrote:
So we need:
1. an optional way to add such comments (even users that want them might not
want them unless they are making spaghetti)
2. automagical maintenance if the comments exist and you change the condition
3. work out whether
> On 11 Aug 2017, at 4:55 am, J. Landman Gay via use-livecode
> wrote:
>
> Well, you don't actually have to use the tooltip. It wouldn't interfere with
> your current method and would enhance the editor for those who don't want the
> clutter.
Having thought about this a bit I think the issue
On Thu, Aug 10, 2017 at 1:02 AM, panagiotis merakos via use-livecode <
use-livecode@lists.runrev.com> wrote:
>
> I personally like this idea, and I find it pretty useful. And this does not
> sound too difficult to implement.
>
That was the flash of insight that triggered me: something was *alrea
Well, you don't actually have to use the tooltip. It wouldn't interfere
with your current method and would enhance the editor for those who don't
want the clutter.
Best of both worlds.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://w
If we're taking votes, respectfully count mine as -1 on using tooltips
for this.
Labels within code are most useful when visible. If we need to read the
code carefully enough to figure out where we should aim the mouse, then
aim the mouse, then pause waiting for the tooltip to appear, the ben
I like the tooltip idea. It's less invasive than altering the script
itself, yet still easy to access. Variable values work the same way and I
find that to be a good balance between accessibility and convenience.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Softwa
It can, but as of now we don't have another good way of matching structures
on a permanent basis so that if you, for instance, remove the "if" or
"repeat" on the top, the "end if" or "end repeat" on the bottom goes away,
too, or if you change the condition the label on the end changes.
On Thu, Aug
+1 on the tooltip. I also comment end statements in nested loops or control
structures, but it gets cluttery when trying to read through the script.
Bob S
> On Aug 10, 2017, at 08:28 , Mark Wieder via use-livecode
> wrote:
>
> On 08/10/2017 03:00 AM, Monte Goulding via use-livecode wrote:
>
On 08/10/2017 03:00 AM, Monte Goulding via use-livecode wrote:
I wonder whether a mouse over tooltip would work just as well. Is this
something you want to be able to see _all_ the time or just if you get confused
about where you are?
Hmmm... I think a tooltip could be especially useful for
I do this, in my code, too. I also label my else's (with the opposite of
the condition, of course)
4D's macros have a cool way of making this happen.
for example, to make a labeled if
type the text of the condition
Select the text
Insert the if macro
The condition is replaced with
if condition the
> On 10 Aug 2017, at 6:02 pm, panagiotis merakos via use-livecode
> wrote:
>
> I personally like this idea, and I find it pretty useful. And this does not
> sound too difficult to implement.
>
> But I am not sure if everyone will like it, so if we do it, we should
> probably add a pref to turn
Hi all,
I personally like this idea, and I find it pretty useful. And this does not
sound too difficult to implement.
But I am not sure if everyone will like it, so if we do it, we should
probably add a pref to turn it on/off.
The good news is that Ali has been doing some work on scriptifying th
On 08/09/2017 01:39 PM, Dr. Hawkins via use-livecode wrote:
Eureka!
I don't know why I didn't think of this earlier, but . . .
A simple way to get *some* level of control structure labeling . . .
So when finding the structure typed in the id of
switch -- myLoop
instead of simply adding an
31 matches
Mail list logo