Re: Encrypting Stack Breaks Field References
On 2020-12-14 06:03, J. Landman Gay via use-livecode wrote: On 12/13/20 6:02 PM, Richard Gaskin via use-livecode wrote: Copying objects is disallowed in an encrypted stack, since of course once an object is copied it could be pasted into an unencrypted stack, and thus expose the source. Except, copying via script using "copy x to y" doesn't involve the clipboard. I think this could be categorized as a bug, the original script should work. Its not the copy that will be failing - but the create. In general you can't do anything to an encrypted stack which might cause a script to move from where its encrypted to somewhere else or vice-versa. (The reason create is disallowed is that you could create a new script via setting props of the template object). 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: Encrypting Stack Breaks Field References
On 12/13/20 6:02 PM, Richard Gaskin via use-livecode wrote: Copying objects is disallowed in an encrypted stack, since of course once an object is copied it could be pasted into an unencrypted stack, and thus expose the source. Except, copying via script using "copy x to y" doesn't involve the clipboard. I think this could be categorized as a bug, the original script should work. -- 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
New MacBook Pro Results
“I sure do miss Scott!” I have been watching videos from different conferences and enjoyed his lectures. So, what happened to Scott? Linda ___ 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: Encrypting Stack Breaks Field References
Hi Ron, About ‘it’ — is that supposed to be the name of the new field or something else? You can always use “last” to refer to a new control, “the last field” is “any object whose number property is equal to the number of objects of that type." ‘It’ might have been changed to something else in the meantime… Peter > On Dec 13, 2020, at 12:15 PM, Ron Noice via use-livecode > wrote: > > My program (built with LC 9.6.1 Indy Windows) contains a large number of > references to fields by variables. For example, instead of refering to [fld > "abc"] I refer to [fld tName] where tName is a variable containing "abc" (no > quotes). > > This has worked perfectly until I *encrypted* the stack (through the > standalone settings). The standalone itself works with no problem; only when > I encrypt it does it fight back. Here's a simplified example of what I'm > doing: > > create group "grpTree" > ... > copy fld "baseBox" to grp "grpTree" > set the name of it to tName > set the visible of fld tName to true > ... > > This gives me a "no such object" error on the "set the visible" line. Through > testing, I've determined that > - tName holds the correct value > - a field named with the value of tName has been correctly created > - but it still seems to be the reference to [fld tName] that is the problem > > This is about building family trees on-the-fly. The largest I've worked with > so far has over 450 boxes (fields) in the tree all with connecting lines and > all based on the ability to use variables to refer to the fields. At the > moment I'm just leaving the stack unencrypted. But inquiring minds would like > to know what the problem is. I know others have used this syntax for naming > and am sure some of them must have encrypted their stacks. Clearly I'm > missing something. > > Thanks for any brilliant suggestions you may have. > > ... Ron > ___ > 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: CentOS Death in 2021
On 12/13/20 4:20 PM, Pi Digital via use-livecode wrote: Thanks all. These insights are useful. Hery’s explanation of their choice to move to Debian provides a good argument. I had just tried Ubuntu 20.04 in a parallels virtual machine and my server app worked ok. I will try a Debian build too. I wonder why LC don’t state support for later Ubuntu, Fedora or Debian builds? Because the team builds the engine on an Ubuntu 16 machine and so doesn't want to say they support anything later. The build process is broken on later versions. I submitted a PR to fix this (it works here) but apparently it doesn't fix things the "right" way, so... And note that we are coming up on the end of Ubuntu 16.04 LTS support on 30 April 2021. -- Mark Wieder ahsoftw...@gmail.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: CentOS Death in 2021
Thanks all. These insights are useful. Hery’s explanation of their choice to move to Debian provides a good argument. I had just tried Ubuntu 20.04 in a parallels virtual machine and my server app worked ok. I will try a Debian build too. I wonder why LC don’t state support for later Ubuntu, Fedora or Debian builds? Sean Cole Pi Digital > On 13 Dec 2020, at 19:27, Heriberto Torrado via use-livecode > wrote: > > Hi Sean, > > I've been using LiveCode on Ubuntu 16.04 and 18.04 for years (Servers and > Desktops) and it worked fine. A years ago we migrated everything to CentOS / > RedHat and Fedora (development machines and servers). However, we are going > to migrate everything to Debian. > Debian is very stable and offers the same user experience on Laptops, > Workstations and Servers. > > Ubuntu is a good system, but after the drift from CentOS with IBM I don't > want to put the heart of our systems in the hands of any big company. > What would happen if tomorrow Ubuntu is acquired by Microsoft and they decide > to charge money for it? That's not the case with Debian: Debian is completely > independent and rock solid. > > I live between Madrid and New York and in both cities there are good > professional companies who offer commercial technical support for Debian, so > you don't need any big and greedy corps getting their hands on your IT > systems. > > Best, > Hery > > > > >> On 12/13/20 12:40 PM, Sean Cole (Pi) via use-livecode wrote: >> Hi all, >> >> I just heard the news that RedHat is going to be dropping support for >> CentOS. With my recent issues with PDF Printing in CentOS, I was already >> looking to perhaps try out CentOS8 or another Dist. but now we have this >> news I'm thinking of going to Ubuntu. >> >> The release notes for LC says it supports Ubuntu 16.04, which is cool. But >> I notice my server host says they have 16.04, 18.04, 20.04 and 20.10. Is >> anyone out there running LC on one of these later builds of Ubuntu? I'd >> like to hear your thoughts. Or maybe I should be looking at Fedora. >> >> All the very best >> >> Sean Cole >> *Pi Digital * >> ___ >> 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
Re: Encrypting Stack Breaks Field References
Ron Noice wrote: ? My program (built with LC 9.6.1 Indy Windows) contains a large number > of references to fields by variables. ... > only when I encrypt it does it fight back. Here's a simplified example > of what I'm doing: > > create group "grpTree" > ... > copy fld "baseBox" to grp "grpTree" ^ that's your issue. Copying objects is disallowed in an encrypted stack, since of course once an object is copied it could be pasted into an unencrypted stack, and thus expose the source. You might consider moving the code from the encrypted stack to an encrypted behavior object, leaving the stack where copying must be done unencrypted. But if these objects are being copied only by script for the purpose of automatically building out a UI, without a need to alter the user's clipboard, you might consider using the clone command instead. -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.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
Encrypting Stack Breaks Field References
My program (built with LC 9.6.1 Indy Windows) contains a large number of references to fields by variables. For example, instead of refering to [fld "abc"] I refer to [fld tName] where tName is a variable containing "abc" (no quotes). This has worked perfectly until I *encrypted* the stack (through the standalone settings). The standalone itself works with no problem; only when I encrypt it does it fight back. Here's a simplified example of what I'm doing: create group "grpTree" ... copy fld "baseBox" to grp "grpTree" set the name of it to tName set the visible of fld tName to true ... This gives me a "no such object" error on the "set the visible" line. Through testing, I've determined that - tName holds the correct value - a field named with the value of tName has been correctly created - but it still seems to be the reference to [fld tName] that is the problem This is about building family trees on-the-fly. The largest I've worked with so far has over 450 boxes (fields) in the tree all with connecting lines and all based on the ability to use variables to refer to the fields. At the moment I'm just leaving the stack unencrypted. But inquiring minds would like to know what the problem is. I know others have used this syntax for naming and am sure some of them must have encrypted their stacks. Clearly I'm missing something. Thanks for any brilliant suggestions you may have. ... Ron ___ 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: CentOS Death in 2021
Hi Sean, I've been using LiveCode on Ubuntu 16.04 and 18.04 for years (Servers and Desktops) and it worked fine. A years ago we migrated everything to CentOS / RedHat and Fedora (development machines and servers). However, we are going to migrate everything to Debian. Debian is very stable and offers the same user experience on Laptops, Workstations and Servers. Ubuntu is a good system, but after the drift from CentOS with IBM I don't want to put the heart of our systems in the hands of any big company. What would happen if tomorrow Ubuntu is acquired by Microsoft and they decide to charge money for it? That's not the case with Debian: Debian is completely independent and rock solid. I live between Madrid and New York and in both cities there are good professional companies who offer commercial technical support for Debian, so you don't need any big and greedy corps getting their hands on your IT systems. Best, Hery On 12/13/20 12:40 PM, Sean Cole (Pi) via use-livecode wrote: Hi all, I just heard the news that RedHat is going to be dropping support for CentOS. With my recent issues with PDF Printing in CentOS, I was already looking to perhaps try out CentOS8 or another Dist. but now we have this news I'm thinking of going to Ubuntu. The release notes for LC says it supports Ubuntu 16.04, which is cool. But I notice my server host says they have 16.04, 18.04, 20.04 and 20.10. Is anyone out there running LC on one of these later builds of Ubuntu? I'd like to hear your thoughts. Or maybe I should be looking at Fedora. All the very best Sean Cole *Pi Digital * ___ 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: CentOS Death in 2021
I personally use Neon, it's based upon Ubuntu and is the development base platform for KDE. I find that it is better integrated between the tools as they are specializing upon one desktop and ensuring everything is properly supported. I have used livecode on it over the past year without issue. So, all the benefits of ubuntu but more stable and better supported, downside is that you are limited to only the one desktop environment or else all the stability issues are gone. best regards Dalton On Sun, 13 Dec 2020 at 13:50, Richmond via use-livecode < use-livecode@lists.runrev.com> wrote: > Well, I am running LC 9.6.1 on Xubuntu (Ubuntu with XFCE) 20.10 without > a backward glance: Rocks! > > Richmond. > > On 13.12.20 19:40, Sean Cole (Pi) via use-livecode wrote: > > Hi all, > > > > I just heard the news that RedHat is going to be dropping support for > > CentOS. With my recent issues with PDF Printing in CentOS, I was already > > looking to perhaps try out CentOS8 or another Dist. but now we have this > > news I'm thinking of going to Ubuntu. > > > > The release notes for LC says it supports Ubuntu 16.04, which is cool. > But > > I notice my server host says they have 16.04, 18.04, 20.04 and 20.10. Is > > anyone out there running LC on one of these later builds of Ubuntu? I'd > > like to hear your thoughts. Or maybe I should be looking at Fedora. > > > > All the very best > > > > Sean Cole > > *Pi Digital * > > ___ > > 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
Re: CentOS Death in 2021
Well, I am running LC 9.6.1 on Xubuntu (Ubuntu with XFCE) 20.10 without a backward glance: Rocks! Richmond. On 13.12.20 19:40, Sean Cole (Pi) via use-livecode wrote: Hi all, I just heard the news that RedHat is going to be dropping support for CentOS. With my recent issues with PDF Printing in CentOS, I was already looking to perhaps try out CentOS8 or another Dist. but now we have this news I'm thinking of going to Ubuntu. The release notes for LC says it supports Ubuntu 16.04, which is cool. But I notice my server host says they have 16.04, 18.04, 20.04 and 20.10. Is anyone out there running LC on one of these later builds of Ubuntu? I'd like to hear your thoughts. Or maybe I should be looking at Fedora. All the very best Sean Cole *Pi Digital * ___ 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
CentOS Death in 2021
Hi all, I just heard the news that RedHat is going to be dropping support for CentOS. With my recent issues with PDF Printing in CentOS, I was already looking to perhaps try out CentOS8 or another Dist. but now we have this news I'm thinking of going to Ubuntu. The release notes for LC says it supports Ubuntu 16.04, which is cool. But I notice my server host says they have 16.04, 18.04, 20.04 and 20.10. Is anyone out there running LC on one of these later builds of Ubuntu? I'd like to hear your thoughts. Or maybe I should be looking at Fedora. All the very best Sean Cole *Pi Digital * ___ 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: Some sad news
Sad indeed. :-( HH's LCB snippets and examples were helpful and inspirational, and in some ways I actually enjoyed reading some of those cantankerous exchanges on bug reports. I wish he'd posted all of his LCB code as some of his more interesting to me LCB work he didn't release the source for. I thought that he had left the LC community out of frustration. I started to add to his LCB snippets thread in the forums and he never commented (he was numbering the examples), now I know why. He will be missed. R.I.P. HH / Hermann Hoch ___ 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: Decrypt problem on Windows
On 12/13/20 1:46 AM, Neville Smythe via use-livecode wrote: [I had just recovered strength from fighting the gratuitously different syntax that Windows uses in its implementation of cURL to hit this problem] I don't have an answer to the decryption problem (sorry), but... I use (and have for some years now) httpie rather than curl. Free, open source, much cleaner syntax, just better all around. When you get tired of fighting with curl or wget, check it out. https://httpie.io/ -- Mark Wieder ahsoftw...@gmail.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
Decrypt problem on Windows
I am getting a difference in the results from decryption of a variable (stored in a stack custom property) between Mac and Windows 10. The script is decrypt using "aes-256-cbc" with password On the Mac this decrypts < myEncryptedStr > to its original value On Windows it gives an empty value, with the result returning “SSL error: Bad encrypt” Could this be a difference in versions between the OpenSSL library built in to OSX 10.15.7 and the LiveCode SSL inclusion for Windows? Or would a different cipher work on both platforms, or perhaps provision of the bit value make it work? Or - surely not - do I have to use different encrypted custom properties for each platform? [I had just recovered strength from fighting the gratuitously different syntax that Windows uses in its implementation of cURL to hit this problem] Neville Smythe ___ 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
