Believe me, it took a little bit longer than just a coffee break. ;)

-
Matthias Rebbe
Life Is Too Short For Boring Code
> Am 31.03.2021 um 23:30 schrieb scott--- via use-livecode 
> <[email protected]>:
> 
> Matthias, when I didn’t see you at the Zoom “coffee break” during Panos' 
> Livecode Advanced course (on just this topic) I assumed that it was because 
> you were using that time to create such a tool.  :- )
> 
> —
> Scott
> 
>> On Mar 31, 2021, at 9:48 AM, matthias rebbe via use-livecode 
>> <[email protected]> wrote:
>> 
>> Thanks Bob for the "reminder" about Devolution and its custom1 buttons.
>> 
>> 
>> I needed it to load a plugin right after i've built a standalone. Yesterdays 
>> discussion "New idea for Standalones" led me there.
>> I want to automatically sign and notarize a MacOS standalone without any 
>> additional user interaction right away after it was built.
>> 
>> For this i am using the standaloneSaved message. In this handler i am 
>> calling/opening my NotarizeHelper stack, give all needed information to the 
>> stack (just the path to the app bundle and the desired action) and start the 
>> notarization process.  So no need anymore to do this manually after the 
>> standalone build process. ;)
>> 
>> This works now w/o a problem. I am now enhancing the script to code sign 
>> also Windows standalones under macOS using osslsigncode. I have alreay an 
>> help app for this, but i would prefer to get it done also right after the 
>> standalone building process.
>> 
>> So if i get/have this working, I can build standalones and code sign / 
>> notarize them with only one click.
>> 
>> Regards,
>> 
>> 
>> -
>> Matthias Rebbe
>> Life Is Too Short For Boring Code
>> 
>>> Am 31.03.2021 um 02:25 schrieb Bob Sneidar via use-livecode 
>>> <[email protected]>:
>>> 
>>> Which is what you have to do to add a plugin to Devolution. Someone turned 
>>> me on to this:
>>> 
>>> eg. I have in the Custom 1 script:
>>> 
>>> on mouseUp
>>> -- Your custom code goes here:
>>> put revenvironmentuserpluginspath() & "/" into tPluginsPath
>>> put tPluginsPath & "Navigator.rev" into tFilePath
>>> go stack tFilePath
>>> go stack (the defaultStack)
>>> end mouseUp
>>> 
>>> 
>>> On Mar 29, 2021, at 4:40 PM, Mark Wieder via use-livecode 
>>> <[email protected]<mailto:[email protected]>> wrote:
>>> 
>>> On 3/29/21 4:06 PM, matthias rebbe via use-livecode wrote:
>>> Dear all,
>>> is there a way to get the path to the 'My Livecode' or the 'Plugins' folder?
>>> Searched now for more than 40 minutes and did not find anything about it?
>>> Is there maybe a hidden variable / property available for this?
>>> 
>>> Not well documented, but...
>>> 
>>> put revEnvironmentUserPluginsPath()
>>> 
>>> --
>>> Mark Wieder
>>> [email protected]<mailto:[email protected]>
>>> 
>>> _______________________________________________
>>> use-livecode mailing list
>>> [email protected]
>>> Please visit this url to subscribe, unsubscribe and manage your 
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> 
>> 
>> _______________________________________________
>> use-livecode mailing list
>> [email protected]
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> 
> _______________________________________________
> use-livecode mailing list
> [email protected]
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to