Cool! thanks Monte!
On Wed, Jun 21, 2017 at 5:48 PM, Mark Talluto via use-livecode <
use-livecode@lists.runrev.com> wrote:
> > On Jun 21, 2017, at 4:40 PM, Monte Goulding via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > Hi Guys
> >
> > I have done _some_ work on an autocomplete
> On Jun 21, 2017, at 4:40 PM, Monte Goulding via use-livecode
> wrote:
>
> Hi Guys
>
> I have done _some_ work on an autocomplete framework which could also be used
> for a snippet library. It is something we have on the radar to complete and
> integrate into the script editor but I’m not su
> On 22 Jun 2017, at 3:20 am, Mike Bonner via use-livecode
> wrote:
>
> Perhaps a different direction here? I think it would be helpful to me as a
> perpetual newbie to have the option to insert common scripts on demand.
> Maybe a context sensitive dropdown with a mouseup framework for buttons
You're right, not a good solution for newcomers.
However, I think there's a (perhaps minority) class of newcomers - more
or less, those who come as experienced developers in another language /
IDE - for whom a good setup would include ST + linter + just enough of
Levure to provide the externa
I am using ST and Levure, now, and I have the linter working, and am a
cheerleader for the setup. However, that is not a good solution for
beginners, IMHO.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, un
Why not just use Sublime Text editor, with Levure to allow you to use an
external editor?
(or plug in to that system to allow other external editors to be used)
Other than the fact that I can't get the 'linter' to work (and I know
that'll just be me doing something stupid and wrong :-), it se
I like the idea of going even another step further, and having macros that
we can use. An example from another tool I use adds the ability to add
structures (e.g. if-then-else, repeat, etc.), and even being able to hilite
text and have the macro do something with the text, for example
someContaine
Mike Bonner wrote:
> Perhaps a different direction here? I think it would be helpful to me
> as a perpetual newbie to have the option to insert common scripts on
> demand.
> Maybe a context sensitive dropdown with a mouseup framework for
> buttons, for fields, textchanged, keyup, keydown.
Hyper
What about Mike Doub’s MasterLibrary?
I just tried it in latest LC, and it fails because there is a function named a
reserved word. But, it seems like a valuable resource that might be used as a
starting point?
Best,
Bill
William Prothero, PhD
Professor Emeritus
University of California, Santa B
Making scripted elements is a great thing for scripters to do. And the
one thing we all have in common here is that we're all scripters.
There should be no need to make LC Ltd's C++ experts set aside work on
the engine to build these instead.
What prevents any of us from delivering those?
-
Perhaps a different direction here? I think it would be helpful to me as a
perpetual newbie to have the option to insert common scripts on demand.
Maybe a context sensitive dropdown with a mouseup framework for buttons,
for fields, textchanged, keyup, keydown. Maybe backed by a personal
snippet l
Going back to the original issue of "not applying the empty mouseup
handler", wouldn't a frontscript running on a plugin on the IDE be enough
to remove those scripts by interfeering with the IDE Editor at runtime?
(PS: I have a thing for dangerous scripts...)
On Wed, Jun 21, 2017 at 12:03 PM, Sann
Kevin,
Thanks for jumping in, very inspiring work you have all been doing recently.
One has to wonder if anyone sleeps in Edinborough!
I've been having a running conversation with Richard on how to make small
solutions available to the whole community, in the spirit of "this would make
adopti
ct/infinite-livecode-native-field-object/
>
>--Andrew Bell
>
>> Message: 6
>> Date: Mon, 19 Jun 2017 16:57:30 -0400
>> From: Mike Kerner
>> To: How to use LiveCode
>> Subject: Re: Preference for Keeping Saved Empty Button Scripts Empty
>> Message-ID:
>
Which is exactly why this is a better idea. Kickstarter releases the funds
when the funding goal is achieved, not when the product is finished. This
idea is the reverse.
1. We set up the account
2. We fund the account
3. We administer the account
4. We decide which projects we want to fund at wha
bject that I contributed for a year ago was available.
https://livecode.com/project/infinite-livecode-native-field-object/
--Andrew Bell
Message: 6
Date: Mon, 19 Jun 2017 16:57:30 -0400
From: Mike Kerner
To: How to use LiveCode
Subject: Re: Preference for Keeping Saved Empty Button Scripts
r
To: How to use LiveCode
Subject: Re: Preference for Keeping Saved Empty Button Scripts Empty
Message-ID:
Content-Type: text/plain; charset="UTF-8"
and another case where we should have a little crowd fund setup.
On Mon, Jun 19, 2017 at 4:00 PM, Bob Sneidar via use-livecode
A work in progress
http://quality.livecode.com/show_bug.cgi?id=19905
On 6/19/17, 2:35 PM, "use-livecode on behalf of Sannyasin Brahmanathaswami via
use-livecode" wrote:
ha… that's a simple hack… I might use
___
use-livecode maili
ha… that's a simple hack… I might use
#
instead… though these all start showing up in PB as have in a 1 line script..
which I guess is server explanatory.
panos wrote me back today say he thinks the default behavior is good for
newbies. which it probably is.
Theoretically the IDE *could* us
and another case where we should have a little crowd fund setup.
On Mon, Jun 19, 2017 at 4:00 PM, Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:
> +1
>
> > On Jun 19, 2017, at 12:49 , J. Landman Gay via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > Right, bu
+1
> On Jun 19, 2017, at 12:49 , J. Landman Gay via use-livecode
> wrote:
>
> Right, but every time you open the script and then close it again, it keeps
> asking if you want to save the default. It gets irritating.
>
> I sometimes just replace the default entry with a single space and save i
On 6/19/17 12:58 PM, Paul Hibbert via use-livecode wrote:
On Jun 19, 2017, at 8:19 AM, Sannyasin Brahmanathaswami via
use-livecode wrote:
so, does it make sense to request a feature enhancement to add a
preference to*not* insert any handler in buttons/widgets, whose
scripts are empty if inadve
and a visual indicator that an object has a script might be nice, too. A
certain tool that some of your colleagues use does that with a filled-in
top-left corner triangle. You can look in the project browser to see which
objects have scripts assined, but that is certainly not ideal. You could
al
On Jun 19, 2017, at 8:19 AM, Sannyasin Brahmanathaswami via use-livecode
wrote:
>
> so, does it make sense to request a feature enhancement to add a preference
> to *not* insert any handler in buttons/widgets, whose scripts are empty if
> inadvertently opened? there would need to be a way to
I wrote support "complaining" that after I clear the
on mouseup
end mouseUp
that is inserted in button scripts by default, apply, close, save. Then later
if one inadvertently opens the script of that button, the script is reinserted.
Panos replied this is the default behavior….gave me a hack t
25 matches
Mail list logo
