Re: non-blocking http ... will tsnet end up in community?

[Tom Glod via use-livecode]

Hi Alex, thats interesting  thanks for that bit of information.  I'm going
to have to educate myself on this some more, maybe take a moment and write
to kevin to find out from the boss.

Cheers

On Tue, Dec 19, 2017 at 5:49 PM, Alex Tweedly via use-livecode <
use-livecode@lists.runrev.com> wrote:

> I think that, unfortunately, it's not going to be possible.
>
> I am 99% sure that I remember, either in the initial announcement or
> closely related to it, that Kevin mentioned that they (Livecode Ltd) pay a
> per-user (i.e. per-licence) fee to the third party for each tsNet - which
> means they have no way to be able to release it under the Community
> agreements.
>
> Alex.
>
>
>
> On 19/12/2017 20:13, Tom Glod via use-livecode wrote:
>
>> Hi Matthias... thank you for your thoughts.
>>
>> I think my post was less about my own needs for that feature  but in
>> general I'm seeing that Web API's are getting more and more capable and
>> will be more and more used by developers going forward.  So being unable
>> to
>> send more than one asyncronoys request to the same server is highly
>> limiting.
>>
>> So if livecode has any hope that their platform will ever be used for a
>> serious and extensive open source project, this is a deal breaker.
>>
>> As for me, I think I can work around this for my needs.  for now.
>> Like
>> I said, I have no choice in using the community version, so I'm not
>> conflicted as to what to do  just gotta go forward.
>>
>> Thanks for your thoughts and Cheers,
>>
>> Tom
>>
>>
>>
>> On Tue, Dec 19, 2017 at 7:45 AM, Matthias Rebbe via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>>
>> Tom, please excuse for using the wrong name.
>>>
>>> Von meinem iPhone gesendet
>>>
>>> Am 19.12.2017 um 13:13 schrieb Matthias Rebbe via use-livecode <

>>> use-livecode@lists.runrev.com>:
>>>
 Todd,
 i understand your desire to have such a feature in the Community

>>> Edition, but I don´t think this will happen in near future.
>>>
 If i understood correctly then tsNET is a 3rd party product which

>>> Livecode Ltd. has acquired or however this is called. So they have paid
>>> money for that.
>>>
 The tsNet external is really a big win for us and i think it is just

>>> fair that this is only included in the commercial licenses.
>>>
 Why? Because there must be a difference between a free license and a

>>> paid license otherwise everyone would use the free one.
>>>
 And there must be  a feature difference between different Indy and

>>> Business license t for the same reason.
>>>
 Btw. Xojo does it the same.  The more you pay, the more you´ll get. With

>>> one exception, they are not offering a free version.
>>>
 LibURL does and did its job more or less well for years. So at least

>>> there is the possibility to do asnynchronous operations.
>>>
 Although i am a 1-man company and my revenues are less than $500,000 a

>>> year and although i have a lifetime Indy license  i
>>>
 have subscribed for a business license just because of its features and

>>> the possibility to get priority support if ever needed.
>>>
 The indy license btw.allows only 1 seat per organisation. A Seat

>>> (regardless if Indy or Business) are for one named developer and
>>>
 cannot be shared. If you need more seats you have to purchase a business

>>> license with the appropriate number of seats.
>>>
 It seems not all customers are/were aware of these terms in the past.

>>> Otherwise Livecode Ltd. would not have sent out an email in October to
>>> all
>>>
 Indy/Business customers with some information about the license terms

>>> and the requirement to sign a digital license agreement.
>>>
 What i would vote for is to add SFTP (synchronous) feature to the

>>> Community Edition to allow secure FTP transfers.
>>>
 Matthias


 Am 19.12.2017 um 00:50 schrieb Tom Glod via use-livecode <
>
 use-livecode@lists.runrev.com >:
>>>
 Hi Everyone,
>
> I use the Community version for project, and recently I've been working
> with the LibURL Library to get some asynchronous server client
> communication going ...and if you've ever worked with that .. its
>
 clear
>>>
 there is much room for improvement there.
>
> Though I have no choice what version to use, so I can only wait in
> patience, but I think for the long term health of the platform and to
>
 give
>>>
 it the modern robustness it needs, the tsnet library is going to have to
> become part of the community version.  Otherwise it will always lag
>
 behind
>>>
 from being able to use modern internet APIs in combination.
>
> Is this something we would have to crowd fund?
>
> Is there anything legally preventing that from happening?
>
> Thanks for any thoughts
> 

Re: Versions of LC and Xcode

[Sannyasin Brahmanathaswami via use-livecode]

@ Mike and Ralph

Hmmm I jumped the gun… downloaded Xcode 9.0, then woke up this morning to find 
8.1.9 RC1 as a Winter Solstice Candy Box from Scotland  (Nandri/Mahalo!)

8.1.9 RC1 will let us use xCode 9.2 now… 

but saving a specific path to a specific xCode version could be useful…



On 12/19/17, 10:52 AM, "use-livecode on behalf of Mike Kerner via use-livecode" 
 wrote:

Doesn't this sound like a good idea for the "Hacking the IDE series" at LCG?

___
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: At this point, what's the shortest path to an iOS/Android app?

[Sannyasin Brahmanathaswami via use-livecode]

Jacque: You will recall this was HQ's "hack" offered to us in the mix of hacks 
in  our attempts to solve rendering issues on Android (which never did work in 
the end) where the stack being opened had AcceleratedRendering set to true… 
waiting *seemed* to help in some scenarios.

With the fix in 8.1.9 RC1  we should try all these without the wait.  

Its interesting how the mind perceives even 200 milliseconds as "sluggish"

On 12/18/17, 8:30 PM, "use-livecode on behalf of J. Landman Gay via 
use-livecode"  wrote:

>c) once you accept the above, they you are good to go with
>
>on preopenstack
>wait 200 milliseconds with messages
>set the fullscreenmode of this stack to "showAll"
>end preopenstack

Just for the record, I've never needed the wait command. There's something 
about Swami's fairly complex setup that requires it but for a more 
straightforward implementation it doesn't seem necessary.

I do like fullscreenmode though. It really does cut down on development 
time.

___
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: Analyzing Crashes on iOS Apps

[Sannyasin Brahmanathaswami via use-livecode]

For several early builds I was including iPad in SA settings but iPad users 
couldn't open because I did not include a splash screen to exact rect/spec. (SA 
builder did not object either…) 

 I note the devices in some the of the crash report show "iPad 4th Generation 
Model" 

I wonder if the app opened and then "died"  right away and this registered a 
crash… even though the user saw nothing… this has been fixed… odd thing is: app 
analytics shows Crashes: 90… but I only see a few reports, not 90… 

Mike wrote:

I think you can also get crash reports if someone quits the app under
certain conditions.

___
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: non-blocking http ... will tsnet end up in community?

[Alex Tweedly via use-livecode]

I think that, unfortunately, it's not going to be possible.

I am 99% sure that I remember, either in the initial announcement or 
closely related to it, that Kevin mentioned that they (Livecode Ltd) pay 
a per-user (i.e. per-licence) fee to the third party for each tsNet - 
which means they have no way to be able to release it under the 
Community agreements.


Alex.


On 19/12/2017 20:13, Tom Glod via use-livecode wrote:

Hi Matthias... thank you for your thoughts.

I think my post was less about my own needs for that feature  but in
general I'm seeing that Web API's are getting more and more capable and
will be more and more used by developers going forward.  So being unable to
send more than one asyncronoys request to the same server is highly
limiting.

So if livecode has any hope that their platform will ever be used for a
serious and extensive open source project, this is a deal breaker.

As for me, I think I can work around this for my needs.  for now.  Like
I said, I have no choice in using the community version, so I'm not
conflicted as to what to do  just gotta go forward.

Thanks for your thoughts and Cheers,

Tom



On Tue, Dec 19, 2017 at 7:45 AM, Matthias Rebbe via use-livecode <
use-livecode@lists.runrev.com> wrote:


Tom, please excuse for using the wrong name.

Von meinem iPhone gesendet


Am 19.12.2017 um 13:13 schrieb Matthias Rebbe via use-livecode <

use-livecode@lists.runrev.com>:

Todd,
i understand your desire to have such a feature in the Community

Edition, but I don´t think this will happen in near future.

If i understood correctly then tsNET is a 3rd party product which

Livecode Ltd. has acquired or however this is called. So they have paid
money for that.

The tsNet external is really a big win for us and i think it is just

fair that this is only included in the commercial licenses.

Why? Because there must be a difference between a free license and a

paid license otherwise everyone would use the free one.

And there must be  a feature difference between different Indy and

Business license t for the same reason.

Btw. Xojo does it the same.  The more you pay, the more you´ll get. With

one exception, they are not offering a free version.

LibURL does and did its job more or less well for years. So at least

there is the possibility to do asnynchronous operations.

Although i am a 1-man company and my revenues are less than $500,000 a

year and although i have a lifetime Indy license  i

have subscribed for a business license just because of its features and

the possibility to get priority support if ever needed.

The indy license btw.allows only 1 seat per organisation. A Seat

(regardless if Indy or Business) are for one named developer and

cannot be shared. If you need more seats you have to purchase a business

license with the appropriate number of seats.

It seems not all customers are/were aware of these terms in the past.

Otherwise Livecode Ltd. would not have sent out an email in October to all

Indy/Business customers with some information about the license terms

and the requirement to sign a digital license agreement.

What i would vote for is to add SFTP (synchronous) feature to the

Community Edition to allow secure FTP transfers.

Matthias



Am 19.12.2017 um 00:50 schrieb Tom Glod via use-livecode <

use-livecode@lists.runrev.com >:

Hi Everyone,

I use the Community version for project, and recently I've been working
with the LibURL Library to get some asynchronous server client
communication going ...and if you've ever worked with that .. its

clear

there is much room for improvement there.

Though I have no choice what version to use, so I can only wait in
patience, but I think for the long term health of the platform and to

give

it the modern robustness it needs, the tsnet library is going to have to
become part of the community version.  Otherwise it will always lag

behind

from being able to use modern internet APIs in combination.

Is this something we would have to crowd fund?

Is there anything legally preventing that from happening?

Thanks for any thoughts
___
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

Matthias Rebbe
Tel +49 5741 31
‌https://matthiasrebbe.eu ‌
___
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:

Re: Versions of LC and Xcode

[Mike Kerner via use-livecode]

Doesn't this sound like a good idea for the "Hacking the IDE series" at LCG?

On Tue, Dec 19, 2017 at 12:03 PM, Ralph DiMola via use-livecode <
use-livecode@lists.runrev.com> wrote:

> BR,
>
> I've been a little under the weather so I can't test. I always rename/move
> the most recent version of Xcode to another folder and download the most
> recent one to the application folder and open it at least once. If you need
> an older version then temporarily rename and move a more recent version to
> another folder then download the older version and open it once in the
> applications folder using the name xcode.app. Then rename/move the older
> version and move the most recent back to applications folder and name it
> Xcode.app.
>
>
> This does not fix the building problem with the hardcoded build path and
> the shared prefs in a LC version series. As I said the only way out of this
> rigmarole is:
>
> 1) Have unique prefs for each LC version. These unique prefs might only
> include the mobile prefs and let the other prefs be shared in a series
>
> 2) A way of indicating the Xcode version to use the build tools from.
>
> Things just move too quick not to do these 2 fixes. We have 2 or 3 active
> LC branches being released along with OSX/iOS/Xcode versions out the
> ying-yang not to do these 2 fixes. Have either of these 2 been added to the
> QCC DB? If this could all be done in LCS I would work on it. I can't see a
> downside. This would encourage me to do more testing with DPs and RCs. I
> can't remember a contiguous 30 day period in the last 18 months that my iOS
> prefs were stable.
>
> Ralph DiMola
> IT Director
> Evergreen Information Services
> rdim...@evergreeninfo.net
>
> -Original Message-
> From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On
> Behalf Of Sannyasin Brahmanathaswami via use-livecode
> Sent: Monday, December 18, 2017 10:51 PM
> To: How to use LiveCode
> Cc: Sannyasin Brahmanathaswami
> Subject: Re: Versions of LC and Xcode
>
> Hmmm I seem to have gotten myself into the same fix as Ben.
>
> " Now that I have updated to LC 9.0 DP-10 and LC
> 8.1.8 stable, nothing can build (except 8.1.6 stable - which unfortunately
> doesn't like the widgets in my stack!)."
>
> I'm on High Sierra 10.13.6, Xcode 9.1 and LC is telling me I don't have
> the required SDK
>
> @Ralph: I should start saving the old XCodes as you describe.
>
> so what now? Can we build for iOS on 9 dp 10 and if so, how?
>
> I’ll go and re-download the previous Xcode 9 from the developer portal…
> see it that helps.
>
> BR
>
>
>
>
>
> On 12/6/17, 11:36 AM, "use-livecode on behalf of Ralph DiMola via
> use-livecode"  use-livecode@lists.runrev.com> wrote:
>
> #1 below==>The shared prefs is a problem. I see the same thing.
> Different prefs for each version would solve this. When a new version is
> started for the first time the prefs from the last version in the series(if
> any) should be copied to the new version prefs file. But the rub is... if
> you change some other prefs and go to another version the you lose the
> change.
> #2 below==>True... I always keep the Xcode version to build from in
> the applications folder and name it xcode.app. I put the other versions
> into another folder. When I upgrade Xcode I move the most recent version
> into my "OtherXcodeVersions" folder and rename it with the version number.
> I then download and install the new version into the applications folder.
> Of course I have to go into the LC prefs and fix the Xcode versions. The
> hardwired path to /Applications/Xcode.app should come from the prefs. Radio
> buttons in the Xcode prefs to indicate==> "Build using tools in this
> version would solve this.
> #3 below==> I agree the docs need to be updated matrix whenever a new
> Xcode/Mac/LC version is released. Even if LC does not support a particular
> combination it should be documented.
>
> Ralph DiMola
> IT Director
> Evergreen Information Services
> rdim...@evergreeninfo.net
>
>
> -Original Message-
> From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On
> Behalf Of Ben Rubinstein via use-livecode
> Sent: Wednesday, December 06, 2017 4:16 PM
> To: Use LiveCode
> Cc: Ben Rubinstein
> Subject: Versions of LC and Xcode
>
> This continues to be a major source of friction.
>
> Once again all my versions of LiveCode seem to have been reset so that
> they can't find a version of Xcode they like. (At any time I am probably
> switching between (or have simultaneously open) four version of LC: LC
> 6.7.11; the latest stable version of 8; the latest 8 RC or sometimes DP;
> the latest DP of 9. Admittedly I'm not building iOS apps from 6.7.11.)
>
> I think that there are two main problems:
>
> 1) Because preferences are shared between versions of LiveCode. I
> believe it is the case than when switching between versions of LiveCode, if
> the 

Re: Analyzing Crashes on iOS Apps

[Mike Kerner via use-livecode]

I think you can also get crash reports if someone quits the app under
certain conditions.

On Tue, Dec 19, 2017 at 3:19 PM, Sannyasin Brahmanathaswami via
use-livecode  wrote:

> One app report 90 crashes in iTunes connect among users who have opted in.
>
> How can we analyze these to make improvements?
>
> in xCode we can set our account preferences  then go
>
> Window -- Organizer -- Crashes
>
> and xCode will fetch data for the app you have up … if click on the iOS
> app for your app on the left, then you get info listings on the right.  but
> these give me nothing I can make any use of … long list under e.g:
>
> "Thread 8"
>
> 0 SivaSiva 0x34000
> 1 SivaSiva 0x34000
>
> clicking on the small arrow take you to a window to "Open crash longs in:
>
> but
>
> No recent Projects
>
> since we don't build our standalones in xCode, we have not project, so no
> way to view any of these crash logs.
>
> 1 crash total for iPad 4th Generation model
>
> So I am not seeing there the total of 90 is coming from in the analytics.
>
> IN any case, is there some way we can make these reports more useful in
> terms of
>
> a) sending to LC HQ
> b) figuring out what is going on that we should change in our LC scripting
> (though a case could be made that if it is not crashing or breaking in the
> IDE, then it Is not something we can fix in our LC code…
>
> ?? Any LC develop got all this figured out?
>
> BR
>
>
>
>
>
> ___
> 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 little diving.
And God said, "This is good."
___
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

Analyzing Crashes on iOS Apps

[Sannyasin Brahmanathaswami via use-livecode]

One app report 90 crashes in iTunes connect among users who have opted in.

How can we analyze these to make improvements?

in xCode we can set our account preferences  then go

Window -- Organizer -- Crashes

and xCode will fetch data for the app you have up … if click on the iOS app for 
your app on the left, then you get info listings on the right.  but these give 
me nothing I can make any use of … long list under e.g:

"Thread 8"

0 SivaSiva 0x34000
1 SivaSiva 0x34000

clicking on the small arrow take you to a window to "Open crash longs in:

but

No recent Projects

since we don't build our standalones in xCode, we have not project, so no way 
to view any of these crash logs.

1 crash total for iPad 4th Generation model

So I am not seeing there the total of 90 is coming from in the analytics.

IN any case, is there some way we can make these reports more useful in terms of

a) sending to LC HQ
b) figuring out what is going on that we should change in our LC scripting 
(though a case could be made that if it is not crashing or breaking in the IDE, 
then it Is not something we can fix in our LC code…

?? Any LC develop got all this figured out?

BR





___
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: non-blocking http ... will tsnet end up in community?

[Tom Glod via use-livecode]

Hi Matthias... thank you for your thoughts.

I think my post was less about my own needs for that feature  but in
general I'm seeing that Web API's are getting more and more capable and
will be more and more used by developers going forward.  So being unable to
send more than one asyncronoys request to the same server is highly
limiting.

So if livecode has any hope that their platform will ever be used for a
serious and extensive open source project, this is a deal breaker.

As for me, I think I can work around this for my needs.  for now.  Like
I said, I have no choice in using the community version, so I'm not
conflicted as to what to do  just gotta go forward.

Thanks for your thoughts and Cheers,

Tom



On Tue, Dec 19, 2017 at 7:45 AM, Matthias Rebbe via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Tom, please excuse for using the wrong name.
>
> Von meinem iPhone gesendet
>
> > Am 19.12.2017 um 13:13 schrieb Matthias Rebbe via use-livecode <
> use-livecode@lists.runrev.com>:
> >
> > Todd,
> > i understand your desire to have such a feature in the Community
> Edition, but I don´t think this will happen in near future.
> >
> > If i understood correctly then tsNET is a 3rd party product which
> Livecode Ltd. has acquired or however this is called. So they have paid
> money for that.
> >
> > The tsNet external is really a big win for us and i think it is just
> fair that this is only included in the commercial licenses.
> >
> > Why? Because there must be a difference between a free license and a
> paid license otherwise everyone would use the free one.
> > And there must be  a feature difference between different Indy and
> Business license t for the same reason.
> > Btw. Xojo does it the same.  The more you pay, the more you´ll get. With
> one exception, they are not offering a free version.
> >
> > LibURL does and did its job more or less well for years. So at least
> there is the possibility to do asnynchronous operations.
> >
> > Although i am a 1-man company and my revenues are less than $500,000 a
> year and although i have a lifetime Indy license  i
> > have subscribed for a business license just because of its features and
> the possibility to get priority support if ever needed.
> >
> > The indy license btw.allows only 1 seat per organisation. A Seat
> (regardless if Indy or Business) are for one named developer and
> > cannot be shared. If you need more seats you have to purchase a business
> license with the appropriate number of seats.
> > It seems not all customers are/were aware of these terms in the past.
> Otherwise Livecode Ltd. would not have sent out an email in October to all
> > Indy/Business customers with some information about the license terms
> and the requirement to sign a digital license agreement.
> >
> > What i would vote for is to add SFTP (synchronous) feature to the
> Community Edition to allow secure FTP transfers.
> >
> > Matthias
> >
> >
> >> Am 19.12.2017 um 00:50 schrieb Tom Glod via use-livecode <
> use-livecode@lists.runrev.com >:
> >>
> >> Hi Everyone,
> >>
> >> I use the Community version for project, and recently I've been working
> >> with the LibURL Library to get some asynchronous server client
> >> communication going ...and if you've ever worked with that .. its
> clear
> >> there is much room for improvement there.
> >>
> >> Though I have no choice what version to use, so I can only wait in
> >> patience, but I think for the long term health of the platform and to
> give
> >> it the modern robustness it needs, the tsnet library is going to have to
> >> become part of the community version.  Otherwise it will always lag
> behind
> >> from being able to use modern internet APIs in combination.
> >>
> >> Is this something we would have to crowd fund?
> >>
> >> Is there anything legally preventing that from happening?
> >>
> >> Thanks for any thoughts
> >> ___
> >> 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
> >
> > Matthias Rebbe
> > Tel +49 5741 31
> > ‌https://matthiasrebbe.eu ‌
> > ___
> > 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

Re: [ANN] Release 8.1.9 RC-1

[Sannyasin Brahmanathaswami via use-livecode]

Jai Ganesha!  

Yay! The SivaSiva app can now "go live" -- we have been keeping it under wraps 
until Android was working. So this is *huge* for us.

Thank you so much! Have a great Christmas… 

BR

Panos:  Various crashes related to the acceleratedRendering property are now 
fixed

___
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: Interprocess Communication (IPC) under OSX

[Mark Waddingham via use-livecode]

On 2017-12-19 19:43, Mark Waddingham via use-livecode wrote:

On 2017-12-18 20:01, Paul Dupuis via use-livecode wrote:
In principle, the same code should work equally great under OSX, but 
it
does not. And yes, if (and when) I have time, i will track down the 
bugs

and report them, but at the moment I was hoping for a quick fix where
someone else already on the list may have identified the OSX
idiosyncrasies and had sample code that worked around them :-)


Hmmm - I have quite a long memory but it doesn't quite stretch as far
back as 4.6.4 these days so I can' say what might have changed on the
process related commands in versions since then.

I do know that there *were* significant bugs in process communication
on OS X for quite some time after I started working at LiveCode (well,
RunRev back then) - which gradually got fixed. I'm pretty sure that
the most recent versions (certainly since 6.x) should be working
correctly (- but I can't really say much about versions before then.

So I suspect the issues might be to do with the 4.6.4 side - rather
than the version on the other side (presumably 6.7.11?).


Of course, looking through the release notes for 4.6.4 I found this:



Slave process improvements (4.5)

A number of issues with the open process command and the engine itself 
have, up until now,
conspired to make it difficult (if not impossible!) to either run a 
slave process, or use the engine as

slave on all platforms.

These issues have been resolved in this version, thus making it 
straightforward to run another

process and poll for input and output over stdin/stdout.
The typical form for this is along the following lines (this example 
assumes the process being

executed outputs whole lines):

command startSlave pProcess
  open process pProcess for text update
  send “monitorSlave pProcess” to me in 50 millisecs
end startSlave

command monitorSlave pProcess
  repeat forever
# Loop until there are no more lines to read.
read from process pProcess for 1 line in 0 millisecs
if the result is empty then
  # The slave has sent us something, so process it and loop for
  # (potentially) more data.
else if the result is “timeout” then
  # There is nothing waiting for us, so exit repeat
  exit repeat
else if the result is “eof” then
  # The slave has terminated, so do any final processing and finish
  # monitoring.
  close process pProcess
  exit monitorSlave
else
  # Some error has occurred!
  exit monitorSlave
end if
  end repeat
  send “monitorSlave pProcess” to me in 50 millisecs
end monitorSlave



So, it would seem that the issues I refer to above were fixed in 4.5... 
So either other bugs have crept in, or there is a cross-platform 
difference lurking somewhere between mac/windows...


Warmest Regards,

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
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: Interprocess Communication (IPC) under OSX

[Mark Waddingham via use-livecode]

On 2017-12-18 20:01, Paul Dupuis via use-livecode wrote:

In principle, the same code should work equally great under OSX, but it
does not. And yes, if (and when) I have time, i will track down the 
bugs

and report them, but at the moment I was hoping for a quick fix where
someone else already on the list may have identified the OSX
idiosyncrasies and had sample code that worked around them :-)


Hmmm - I have quite a long memory but it doesn't quite stretch as far 
back as 4.6.4 these days so I can' say what might have changed on the 
process related commands in versions since then.


I do know that there *were* significant bugs in process communication on 
OS X for quite some time after I started working at LiveCode (well, 
RunRev back then) - which gradually got fixed. I'm pretty sure that the 
most recent versions (certainly since 6.x) should be working correctly 
(- but I can't really say much about versions before then.


So I suspect the issues might be to do with the 4.6.4 side - rather than 
the version on the other side (presumably 6.7.11?).


In terms of the changes to field indicies - 6.x still uses the same 
unicode flag for style runs in the field that 4.6.4 uses - the data 
inside the engine is the same, but the char indicies are not.


I'm pretty sure it would be possible to write a handler which takes the 
styledText array of a field in 6.7.11 and a list of old indicies, 
returning a list of new char indicies... Would that help?


Warmest Regards,

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
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: Xmas LC-elf activity

[Mark Waddingham via use-livecode]

On 2017-12-18 03:56, James At The Hale via use-livecode wrote:

And so, I wonder, looking over the github milestones

Will the long standing and non critical issue still open against
8.13rc-1 and 8.20dp-3 be bumped to the next respective versions to
allow these babies to be released?

Will the tireless worker elves at Kris Kringle’s Edinburgh office be
able to wrap up the outstanding 9 dp-11 issues before the Xmas break?

Will our stockings be stuffed with three new downloads or will they
remain empty?


The elves have been working quite tirelessly the last couple of weeks 
(even more so the last few days - judging by the UK times of commits / 
PRs on GitHub and internal messages on slack by those who don't live in 
an antipodean timezone)!


The first early christmas present (8.1.9-rc-1) has already been 
delivered, and assuming that no unexpected headwinds affect the course 
of Santa's sleigh there are more expected before the upcoming festive 
break :)


Warmest Regards,

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
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: Versions of LC and Xcode

[Ralph DiMola via use-livecode]

BR,

I've been a little under the weather so I can't test. I always rename/move the 
most recent version of Xcode to another folder and download the most recent one 
to the application folder and open it at least once. If you need an older 
version then temporarily rename and move a more recent version to another 
folder then download the older version and open it once in the applications 
folder using the name xcode.app. Then rename/move the older version and move 
the most recent back to applications folder and name it Xcode.app.


This does not fix the building problem with the hardcoded build path and the 
shared prefs in a LC version series. As I said the only way out of this 
rigmarole is:

1) Have unique prefs for each LC version. These unique prefs might only include 
the mobile prefs and let the other prefs be shared in a series

2) A way of indicating the Xcode version to use the build tools from.

Things just move too quick not to do these 2 fixes. We have 2 or 3 active LC 
branches being released along with OSX/iOS/Xcode versions out the ying-yang not 
to do these 2 fixes. Have either of these 2 been added to the QCC DB? If this 
could all be done in LCS I would work on it. I can't see a downside. This would 
encourage me to do more testing with DPs and RCs. I can't remember a contiguous 
30 day period in the last 18 months that my iOS prefs were stable.

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net

-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of 
Sannyasin Brahmanathaswami via use-livecode
Sent: Monday, December 18, 2017 10:51 PM
To: How to use LiveCode
Cc: Sannyasin Brahmanathaswami
Subject: Re: Versions of LC and Xcode

Hmmm I seem to have gotten myself into the same fix as Ben.

" Now that I have updated to LC 9.0 DP-10 and LC
8.1.8 stable, nothing can build (except 8.1.6 stable - which unfortunately 
doesn't like the widgets in my stack!)."

I'm on High Sierra 10.13.6, Xcode 9.1 and LC is telling me I don't have the 
required SDK

@Ralph: I should start saving the old XCodes as you describe.

so what now? Can we build for iOS on 9 dp 10 and if so, how?

I’ll go and re-download the previous Xcode 9 from the developer portal… see it 
that helps.

BR

 

 

On 12/6/17, 11:36 AM, "use-livecode on behalf of Ralph DiMola via use-livecode" 
 wrote:

#1 below==>The shared prefs is a problem. I see the same thing. Different 
prefs for each version would solve this. When a new version is started for the 
first time the prefs from the last version in the series(if any) should be 
copied to the new version prefs file. But the rub is... if you change some 
other prefs and go to another version the you lose the change.
#2 below==>True... I always keep the Xcode version to build from in the 
applications folder and name it xcode.app. I put the other versions into 
another folder. When I upgrade Xcode I move the most recent version into my 
"OtherXcodeVersions" folder and rename it with the version number. I then 
download and install the new version into the applications folder. Of course I 
have to go into the LC prefs and fix the Xcode versions. The hardwired path to 
/Applications/Xcode.app should come from the prefs. Radio buttons in the Xcode 
prefs to indicate==> "Build using tools in this version would solve this.
#3 below==> I agree the docs need to be updated matrix whenever a new 
Xcode/Mac/LC version is released. Even if LC does not support a particular 
combination it should be documented.

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net


-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf 
Of Ben Rubinstein via use-livecode
Sent: Wednesday, December 06, 2017 4:16 PM
To: Use LiveCode
Cc: Ben Rubinstein
Subject: Versions of LC and Xcode

This continues to be a major source of friction.

Once again all my versions of LiveCode seem to have been reset so that they 
can't find a version of Xcode they like. (At any time I am probably switching 
between (or have simultaneously open) four version of LC: LC 6.7.11; the latest 
stable version of 8; the latest 8 RC or sometimes DP; the latest DP of 9. 
Admittedly I'm not building iOS apps from 6.7.11.)

I think that there are two main problems:

1) Because preferences are shared between versions of LiveCode. I believe 
it is the case than when switching between versions of LiveCode, if the mobile 
support preferences are opened in a version of LC which doesn't play nice with 
the selected version of Xcode, that path is deleted; so that next time the 
version of LC which was previously happy is opened, the path to Xcode is gone. 
The behaviour may be a little more subtle than this, but I believe 

Re: [ANN] Release 8.1.9 RC-1

[Dave Kilroy via use-livecode]

Excellent Excellent Excellent

Dave




Mike Kerner via use-livecode <
> Excellent.
> 
> On Tue, Dec 19, 2017 at 8:54 AM, panagiotis merakos via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> > Well, short answer is "quite soon, before Christmas" :)
> >
> > On Tue, Dec 19, 2017 at 1:48 PM, Mike Kerner via use-livecode <
> > use-livecode@lists.runrev.com> wrote:
> >
> > > Any word on the next release of 9?
> > >
> > > On Tue, Dec 19, 2017 at 7:33 AM, panagiotis merakos via use-livecode <
> > > use-livecode@lists.runrev.com> wrote:
> > >
> > > > Dear list members,
> > > >
> > > > We are pleased to announce the release of LiveCode 8.1.9 RC-1.
> > > >
> > > > Getting the Release
> > > > ===
> > > > You can get the release at https://downloads.livecode.com/livecode/ 
> > > >  or
> > > via
> > > > the automatic updater.
> > > >
> > > >
> > > > Release Contents
> > > > 
> > > >
> > > > LiveCode 8.1.9 RC-1 contains more than 20 bugfixes and improvements,
> > > > including:
> > > >
> > > > - Various crashes related to the acceleratedRendering property are now
> > > > fixed
> > > > - Support for building with Xcode 9.2 (and using the latest iOS 11.2
> > SDK)
> > > > has been added, as well as the ability to set splash images and icon
> > for
> > > > iPhone X.
> > > > - New versions of mergExt* and tsNet externals are included,
> > addressing a
> > > > couple of bugs.
> > > >
> > > >
> > > > Notes:
> > > >
> > > > - Xcode 9.2 requires MacOS 10.12.6 or higher
> > > >
> > > >
> > > > The full release notes are available from:
> > > > http://downloads.livecode.com/livecode/8_1_9/LiveCodeNotes- 
> > > > 
> > > 8_1_9_rc_1.pdf
> > > >
> > > >
> > > > Feedback
> > > > 
> > > > Please report any bugs encountered on our BugZilla at
> > > > http://quality.livecode.com/ 
> > > >
> > > >
> > > > Have fun!
> > > > The LiveCode Team
> > > > --
> > > > ___
> > > > 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 little diving.
> > > And God said, "This is good."
> > > ___
> > > 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 little diving.
> And God said, "This is good."
> ___
> 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

Re: [ANN] Release 8.1.9 RC-1

[Mike Kerner via use-livecode]

Excellent.

On Tue, Dec 19, 2017 at 8:54 AM, panagiotis merakos via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Well, short answer is "quite soon, before Christmas" :)
>
> On Tue, Dec 19, 2017 at 1:48 PM, Mike Kerner via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> > Any word on the next release of 9?
> >
> > On Tue, Dec 19, 2017 at 7:33 AM, panagiotis merakos via use-livecode <
> > use-livecode@lists.runrev.com> wrote:
> >
> > > Dear list members,
> > >
> > > We are pleased to announce the release of LiveCode 8.1.9 RC-1.
> > >
> > > Getting the Release
> > > ===
> > > You can get the release at https://downloads.livecode.com/livecode/ or
> > via
> > > the automatic updater.
> > >
> > >
> > > Release Contents
> > > 
> > >
> > > LiveCode 8.1.9 RC-1 contains more than 20 bugfixes and improvements,
> > > including:
> > >
> > > - Various crashes related to the acceleratedRendering property are now
> > > fixed
> > > - Support for building with Xcode 9.2 (and using the latest iOS 11.2
> SDK)
> > > has been added, as well as the ability to set splash images and icon
> for
> > > iPhone X.
> > > - New versions of mergExt* and tsNet externals are included,
> addressing a
> > > couple of bugs.
> > >
> > >
> > > Notes:
> > >
> > > - Xcode 9.2 requires MacOS 10.12.6 or higher
> > >
> > >
> > > The full release notes are available from:
> > > http://downloads.livecode.com/livecode/8_1_9/LiveCodeNotes-
> > 8_1_9_rc_1.pdf
> > >
> > >
> > > Feedback
> > > 
> > > Please report any bugs encountered on our BugZilla at
> > > http://quality.livecode.com/
> > >
> > >
> > > Have fun!
> > > The LiveCode Team
> > > --
> > > ___
> > > 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 little diving.
> > And God said, "This is good."
> > ___
> > 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 little diving.
And God said, "This is good."
___
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: [ANN] Release 8.1.9 RC-1

[panagiotis merakos via use-livecode]

Well, short answer is "quite soon, before Christmas" :)

On Tue, Dec 19, 2017 at 1:48 PM, Mike Kerner via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Any word on the next release of 9?
>
> On Tue, Dec 19, 2017 at 7:33 AM, panagiotis merakos via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> > Dear list members,
> >
> > We are pleased to announce the release of LiveCode 8.1.9 RC-1.
> >
> > Getting the Release
> > ===
> > You can get the release at https://downloads.livecode.com/livecode/ or
> via
> > the automatic updater.
> >
> >
> > Release Contents
> > 
> >
> > LiveCode 8.1.9 RC-1 contains more than 20 bugfixes and improvements,
> > including:
> >
> > - Various crashes related to the acceleratedRendering property are now
> > fixed
> > - Support for building with Xcode 9.2 (and using the latest iOS 11.2 SDK)
> > has been added, as well as the ability to set splash images and icon for
> > iPhone X.
> > - New versions of mergExt* and tsNet externals are included, addressing a
> > couple of bugs.
> >
> >
> > Notes:
> >
> > - Xcode 9.2 requires MacOS 10.12.6 or higher
> >
> >
> > The full release notes are available from:
> > http://downloads.livecode.com/livecode/8_1_9/LiveCodeNotes-
> 8_1_9_rc_1.pdf
> >
> >
> > Feedback
> > 
> > Please report any bugs encountered on our BugZilla at
> > http://quality.livecode.com/
> >
> >
> > Have fun!
> > The LiveCode Team
> > --
> > ___
> > 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 little diving.
> And God said, "This is good."
> ___
> 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

Re: [ANN] Release 8.1.9 RC-1

[Mike Kerner via use-livecode]

Any word on the next release of 9?

On Tue, Dec 19, 2017 at 7:33 AM, panagiotis merakos via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Dear list members,
>
> We are pleased to announce the release of LiveCode 8.1.9 RC-1.
>
> Getting the Release
> ===
> You can get the release at https://downloads.livecode.com/livecode/ or via
> the automatic updater.
>
>
> Release Contents
> 
>
> LiveCode 8.1.9 RC-1 contains more than 20 bugfixes and improvements,
> including:
>
> - Various crashes related to the acceleratedRendering property are now
> fixed
> - Support for building with Xcode 9.2 (and using the latest iOS 11.2 SDK)
> has been added, as well as the ability to set splash images and icon for
> iPhone X.
> - New versions of mergExt* and tsNet externals are included, addressing a
> couple of bugs.
>
>
> Notes:
>
> - Xcode 9.2 requires MacOS 10.12.6 or higher
>
>
> The full release notes are available from:
> http://downloads.livecode.com/livecode/8_1_9/LiveCodeNotes-8_1_9_rc_1.pdf
>
>
> Feedback
> 
> Please report any bugs encountered on our BugZilla at
> http://quality.livecode.com/
>
>
> Have fun!
> The LiveCode Team
> --
> ___
> 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 little diving.
And God said, "This is good."
___
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: non-blocking http ... will tsnet end up in community?

[Matthias Rebbe via use-livecode]

Tom, please excuse for using the wrong name.

Von meinem iPhone gesendet

> Am 19.12.2017 um 13:13 schrieb Matthias Rebbe via use-livecode 
> :
> 
> Todd,
> i understand your desire to have such a feature in the Community Edition, but 
> I don´t think this will happen in near future.
> 
> If i understood correctly then tsNET is a 3rd party product which Livecode 
> Ltd. has acquired or however this is called. So they have paid money for that.
> 
> The tsNet external is really a big win for us and i think it is just fair 
> that this is only included in the commercial licenses.
> 
> Why? Because there must be a difference between a free license and a paid 
> license otherwise everyone would use the free one.
> And there must be  a feature difference between different Indy and Business 
> license t for the same reason. 
> Btw. Xojo does it the same.  The more you pay, the more you´ll get. With one 
> exception, they are not offering a free version.
> 
> LibURL does and did its job more or less well for years. So at least there is 
> the possibility to do asnynchronous operations.
> 
> Although i am a 1-man company and my revenues are less than $500,000 a year 
> and although i have a lifetime Indy license  i 
> have subscribed for a business license just because of its features and the 
> possibility to get priority support if ever needed.
> 
> The indy license btw.allows only 1 seat per organisation. A Seat (regardless 
> if Indy or Business) are for one named developer and 
> cannot be shared. If you need more seats you have to purchase a business 
> license with the appropriate number of seats.
> It seems not all customers are/were aware of these terms in the past. 
> Otherwise Livecode Ltd. would not have sent out an email in October to all 
> Indy/Business customers with some information about the license terms and the 
> requirement to sign a digital license agreement.
> 
> What i would vote for is to add SFTP (synchronous) feature to the Community 
> Edition to allow secure FTP transfers. 
> 
> Matthias
> 
> 
>> Am 19.12.2017 um 00:50 schrieb Tom Glod via use-livecode 
>> >:
>> 
>> Hi Everyone,
>> 
>> I use the Community version for project, and recently I've been working
>> with the LibURL Library to get some asynchronous server client
>> communication going ...and if you've ever worked with that .. its clear
>> there is much room for improvement there.
>> 
>> Though I have no choice what version to use, so I can only wait in
>> patience, but I think for the long term health of the platform and to give
>> it the modern robustness it needs, the tsnet library is going to have to
>> become part of the community version.  Otherwise it will always lag behind
>> from being able to use modern internet APIs in combination.
>> 
>> Is this something we would have to crowd fund?
>> 
>> Is there anything legally preventing that from happening?
>> 
>> Thanks for any thoughts
>> ___
>> 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
> 
> Matthias Rebbe
> Tel +49 5741 31
> ‌https://matthiasrebbe.eu ‌
> ___
> 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

[ANN] Release 8.1.9 RC-1

[panagiotis merakos via use-livecode]

Dear list members,

We are pleased to announce the release of LiveCode 8.1.9 RC-1.

Getting the Release
===
You can get the release at https://downloads.livecode.com/livecode/ or via
the automatic updater.


Release Contents


LiveCode 8.1.9 RC-1 contains more than 20 bugfixes and improvements,
including:

- Various crashes related to the acceleratedRendering property are now fixed
- Support for building with Xcode 9.2 (and using the latest iOS 11.2 SDK)
has been added, as well as the ability to set splash images and icon for
iPhone X.
- New versions of mergExt* and tsNet externals are included, addressing a
couple of bugs.


Notes:

- Xcode 9.2 requires MacOS 10.12.6 or higher


The full release notes are available from:
http://downloads.livecode.com/livecode/8_1_9/LiveCodeNotes-8_1_9_rc_1.pdf


Feedback

Please report any bugs encountered on our BugZilla at
http://quality.livecode.com/


Have fun!
The LiveCode Team
--
___
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: non-blocking http ... will tsnet end up in community?

[Matthias Rebbe via use-livecode]

Todd,
 i understand your desire to have such a feature in the Community Edition, but 
I don´t think this will happen in near future.

If i understood correctly then tsNET is a 3rd party product which Livecode Ltd. 
has acquired or however this is called. So they have paid money for that.

The tsNet external is really a big win for us and i think it is just fair that 
this is only included in the commercial licenses.

Why? Because there must be a difference between a free license and a paid 
license otherwise everyone would use the free one.
And there must be  a feature difference between different Indy and Business 
license t for the same reason. 
Btw. Xojo does it the same.  The more you pay, the more you´ll get. With one 
exception, they are not offering a free version.

LibURL does and did its job more or less well for years. So at least there is 
the possibility to do asnynchronous operations.

Although i am a 1-man company and my revenues are less than $500,000 a year and 
although i have a lifetime Indy license  i 
have subscribed for a business license just because of its features and the 
possibility to get priority support if ever needed.

The indy license btw.allows only 1 seat per organisation. A Seat (regardless if 
Indy or Business) are for one named developer and 
cannot be shared. If you need more seats you have to purchase a business 
license with the appropriate number of seats.
It seems not all customers are/were aware of these terms in the past. Otherwise 
Livecode Ltd. would not have sent out an email in October to all 
Indy/Business customers with some information about the license terms and the 
requirement to sign a digital license agreement.

What i would vote for is to add SFTP (synchronous) feature to the Community 
Edition to allow secure FTP transfers. 

Matthias


> Am 19.12.2017 um 00:50 schrieb Tom Glod via use-livecode 
> >:
> 
> Hi Everyone,
> 
> I use the Community version for project, and recently I've been working
> with the LibURL Library to get some asynchronous server client
> communication going ...and if you've ever worked with that .. its clear
> there is much room for improvement there.
> 
> Though I have no choice what version to use, so I can only wait in
> patience, but I think for the long term health of the platform and to give
> it the modern robustness it needs, the tsnet library is going to have to
> become part of the community version.  Otherwise it will always lag behind
> from being able to use modern internet APIs in combination.
> 
> Is this something we would have to crowd fund?
> 
> Is there anything legally preventing that from happening?
> 
> Thanks for any thoughts
> ___
> 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

Matthias Rebbe
Tel +49 5741 31
‌https://matthiasrebbe.eu ‌
___
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