Re: A question about the compiler to come

2022-03-04 Thread Mark Smith via use-livecode
I also asked about building widgets from LC script. The response was, this 
could be a step along that path. 

Sent from my iPhone

> On Mar 4, 2022, at 2:54 PM, Mike Kerner via use-livecode 
>  wrote:
> 
> It's nice that aCompileIt!/Double-XX replacement is finally coming to
> LiveCode, maybe, but it is pretty expensive, at $499/year.
> The old timers may remember both of those products, from Heizer Software,
> allowed you to compile HyperCard stacks (and build XCMD's and XFCN's).
> We will see how smooth the path will be. I did post $500, but I think it
> will be a rocky transition.
> 
> 
>> On Thu, Mar 3, 2022 at 8:19 PM Tom Glod via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> 
>> I meant to include link to this:
>> https://livecode.com/script-compiler-project-page/
>> 
>>> On Thu, Mar 3, 2022 at 8:13 PM Tom Glod  wrote:
>>> 
>>> Hi Sean, one the page for the compiler project and Kevin talks about the
>>> nature of Livecode being interpreted . currently the script in memory
>>> is just obfuscated, and a sufficiently motivated person or group of
>> people
>>> could eventually find what they want to find.  script passwords are
>> useful
>>> too, but also have their limit.
>>> 
>>> "By compiling scripts fully, standalones become even more secure. We’ve
>>> put a lot of work into making standalones secure at present but there are
>>> still limitations on the existing approach that are fundamental to how an
>>> interpreter like LiveCode operates. Compiled code does not leave any
>> trace
>>> of the original script text."
>>> 
>>> Cheers,
>>> 
>>> Tom
>>> 
>>> On Thu, Mar 3, 2022 at 5:22 PM Sean Cole via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
>>> 
 Tom
 What security imp[lications do you perceive it to overcome?
 
 Sean
 
 On Thu, 3 Mar 2022 at 21:07, Tom Glod via use-livecode <
 use-livecode@lists.runrev.com> wrote:
 
> Pardon my lingo  but this is f#%%ing huge Just last week, I
>> was
> thinking about the nature of livecode and that it comes with some
>> pretty
> profound security implications.
> I'm sSuper happy to see this machine code compiler coming to livecode.
> This is likely to directly influence the amount of sleep I get in this
> upcoming decade of work :)
> Great decision by the team to go ahead with this.
> (y)
> 
> 
> On Thu, Mar 3, 2022 at 3:03 PM Tom Glod  wrote:
> 
>> Interesting.
>> I cannot find  this email from Kevin, can someone please forward it
 to me
>> or direct me to where I can read it?
>> 
>> Thanks,
>> 
>> Tom
>> 
>> On Thu, Mar 3, 2022 at 10:10 AM Rick Harrison via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> 
>>> According to Kevin’s email:
>>> 
>>> Would this script compiler work on all platforms?
>>> All platforms will benefit. Code will run faster and readable
>> scripts
>>> will be removed whatever platform you are targeting.
>>> Rick
>>> 
 On Mar 3, 2022, at 9:33 AM, francois.chaplais via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
 
 Dear all
 
 You probably have received some mail asking for funding
>> concerning
 a
>>> compiler to come.
 
 I would like to know if this compiler can target MacOS/ARM
 processor
> on
>>> the desktop.
 
 Best regards,
 
 François
 ___
 use-livecode mailing list
 use-livecode@lists.runrev.com
 Please visit this url to subscribe, unsubscribe and manage your
>>> subscription preferences:
 http://lists.runrev.com/mailman/listinfo/use-livecode
>>> 
>>> ___
>>> use-livecode mailing list
>>> use-livecode@lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>> 
>> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
 ___
 use-livecode mailing list
 use-livecode@lists.runrev.com
 Please visit this url to subscribe, unsubscribe and manage your
 subscription preferences:
 http://lists.runrev.com/mailman/listinfo/use-livecode
 
>>> 
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> 
> 
> 
> -- 
> On the first day, G

Re: Speed up a slow loop

2022-03-04 Thread Bob Sneidar via use-livecode
Well… the idea was, if storing and working with the data as arrays was crucial, 
then I have a method for creating sqLite databases, memory or otherwise, from 
arrays and then back again. I don’t know if mobile devices can use memory 
databases, or perhaps the data is too much for mobile device limits, so I am 
sailing murky waters there. But once the overhead of iterating through the 
array once is spent, recursive querying of a memory or even a file database is 
much more efficient.  

Sent from my iPhone

> On Mar 4, 2022, at 15:16, Neville Smythe via use-livecode 
>  wrote:
> 
> Bob’s suggestion of storing the word list in an sqlite database would keep 
> the list on disk and not in memory
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Speed up a slow loop

2022-03-04 Thread J. Landman Gay via use-livecode

On 3/4/22 2:33 PM, Neville Smythe via use-livecode wrote:

Jacque, are you trying to keep the whole of SOWPODS in memory the whole time? 
That’s a 2.5MB file. It sounds to me like you are getting virtual memory 
thrashing.


I'm thinking the same thing, it's the only explanation. I stopped using SOWPODS and things got 
a bit faster after I substituted a file half that size.


I'm sure you and Bob are right about using a database, but I'm not a database person and I 
wouldn't know where to start. If anyone wants to help, you can have a free copy of my 
already-free game...


Probably we shouldn't cluter the list with that, but there's email.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Speed up a slow loop

2022-03-04 Thread Neville Smythe via use-livecode
Bob’s suggestion of storing the word list in an sqlite database would keep the 
list on disk and not in memory, so avoiding VM swapping which is  I think  the 
basic problem, and also use a much faster search engine than LC to do the 
checking for the existence of user candidates. A more elegant solution than 
breaking up the wordlist into hundreds of small files. 

It is possible because we know the structure of the data in this case that lots 
of small files, with a couple of other tricks to reduce file size, and then 
using an LC search, could be faster (because the OS file system is even more 
efficient than sqlite) but I’d be surprised if the db approach didn’t solve 
your problem.


Neville
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Speed up a slow loop

2022-03-04 Thread Neville Smythe via use-livecode
Jacque, are you trying to keep the whole of SOWPODS in memory the whole time? 
That’s a 2.5MB file. It sounds to me like you are getting virtual memory 
thrashing.

If so, try breaking up the wordlist into 26 files for example - or even more by 
length as well as initial letter - kept as resources (rather than in fields)  
and only reading in the file required to check  a word as needed (and emptying 
the variable loaded from file asap). My guess is a linear search on a small 
file is going to be faster than array indexing magic if memory swapping starts 
to occur.

Neville
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: A question about the compiler to come

2022-03-04 Thread Mike Kerner via use-livecode
It's nice that aCompileIt!/Double-XX replacement is finally coming to
LiveCode, maybe, but it is pretty expensive, at $499/year.
The old timers may remember both of those products, from Heizer Software,
allowed you to compile HyperCard stacks (and build XCMD's and XFCN's).
We will see how smooth the path will be. I did post $500, but I think it
will be a rocky transition.


On Thu, Mar 3, 2022 at 8:19 PM Tom Glod via use-livecode <
use-livecode@lists.runrev.com> wrote:

> I meant to include link to this:
> https://livecode.com/script-compiler-project-page/
>
> On Thu, Mar 3, 2022 at 8:13 PM Tom Glod  wrote:
>
> > Hi Sean, one the page for the compiler project and Kevin talks about the
> > nature of Livecode being interpreted . currently the script in memory
> > is just obfuscated, and a sufficiently motivated person or group of
> people
> > could eventually find what they want to find.  script passwords are
> useful
> > too, but also have their limit.
> >
> > "By compiling scripts fully, standalones become even more secure. We’ve
> > put a lot of work into making standalones secure at present but there are
> > still limitations on the existing approach that are fundamental to how an
> > interpreter like LiveCode operates. Compiled code does not leave any
> trace
> > of the original script text."
> >
> > Cheers,
> >
> > Tom
> >
> > On Thu, Mar 3, 2022 at 5:22 PM Sean Cole via use-livecode <
> > use-livecode@lists.runrev.com> wrote:
> >
> >> Tom
> >> What security imp[lications do you perceive it to overcome?
> >>
> >> Sean
> >>
> >> On Thu, 3 Mar 2022 at 21:07, Tom Glod via use-livecode <
> >> use-livecode@lists.runrev.com> wrote:
> >>
> >> > Pardon my lingo  but this is f#%%ing huge Just last week, I
> was
> >> > thinking about the nature of livecode and that it comes with some
> pretty
> >> > profound security implications.
> >> > I'm sSuper happy to see this machine code compiler coming to livecode.
> >> > This is likely to directly influence the amount of sleep I get in this
> >> > upcoming decade of work :)
> >> > Great decision by the team to go ahead with this.
> >> > (y)
> >> >
> >> >
> >> > On Thu, Mar 3, 2022 at 3:03 PM Tom Glod  wrote:
> >> >
> >> > > Interesting.
> >> > > I cannot find  this email from Kevin, can someone please forward it
> >> to me
> >> > > or direct me to where I can read it?
> >> > >
> >> > > Thanks,
> >> > >
> >> > > Tom
> >> > >
> >> > > On Thu, Mar 3, 2022 at 10:10 AM Rick Harrison via use-livecode <
> >> > > use-livecode@lists.runrev.com> wrote:
> >> > >
> >> > >> According to Kevin’s email:
> >> > >>
> >> > >> Would this script compiler work on all platforms?
> >> > >> All platforms will benefit. Code will run faster and readable
> scripts
> >> > >> will be removed whatever platform you are targeting.
> >> > >> Rick
> >> > >>
> >> > >> > On Mar 3, 2022, at 9:33 AM, francois.chaplais via use-livecode <
> >> > >> use-livecode@lists.runrev.com> wrote:
> >> > >> >
> >> > >> > Dear all
> >> > >> >
> >> > >> > You probably have received some mail asking for funding
> concerning
> >> a
> >> > >> compiler to come.
> >> > >> >
> >> > >> > I would like to know if this compiler can target MacOS/ARM
> >> processor
> >> > on
> >> > >> the desktop.
> >> > >> >
> >> > >> > Best regards,
> >> > >> >
> >> > >> > François
> >> > >> > ___
> >> > >> > use-livecode mailing list
> >> > >> > use-livecode@lists.runrev.com
> >> > >> > Please visit this url to subscribe, unsubscribe and manage your
> >> > >> subscription preferences:
> >> > >> > http://lists.runrev.com/mailman/listinfo/use-livecode
> >> > >>
> >> > >> ___
> >> > >> use-livecode mailing list
> >> > >> use-livecode@lists.runrev.com
> >> > >> Please visit this url to subscribe, unsubscribe and manage your
> >> > >> subscription preferences:
> >> > >> http://lists.runrev.com/mailman/listinfo/use-livecode
> >> > >>
> >> > >
> >> > ___
> >> > use-livecode mailing list
> >> > use-livecode@lists.runrev.com
> >> > Please visit this url to subscribe, unsubscribe and manage your
> >> > subscription preferences:
> >> > http://lists.runrev.com/mailman/listinfo/use-livecode
> >> >
> >> ___
> >> use-livecode mailing list
> >> use-livecode@lists.runrev.com
> >> Please visit this url to subscribe, unsubscribe and manage your
> >> subscription preferences:
> >> http://lists.runrev.com/mailman/listinfo/use-livecode
> >>
> >
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>


-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a littl