Microsoft app store

2023-08-25 Thread J. Landman Gay via use-livecode
Has anyone submitted a Windows app to the Microsoft store? I have a lead 
and if it pans out I'd like to know if there's a resource available here. 
Nothing is set yet but I'm thinking ahead.


--
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: OT - Mac Notarization Problem - Desperation setting in

2023-08-25 Thread Timothy Bleiler via use-livecode
Yes Matthias, I figured you had a good reason so I went back into the account 
and checked every single thing very carefully.  When I saw that my device was 
not trusted I figured THAT had to be fixed!!
Then I just followed your suggestion to redo everything and that’s when I 
learned about how the app-specific password actually works.
I don’t know if I’d have figured it out without your help!!

On Aug 25, 2023, at 5:17 PM, matthias rebbe via use-livecode 
 wrote:

And now you know why wanted to do a remote session to repeat all steps from 
creating app-specific pw to connecting to apples services. ;)
We could have found out sooner. ;) Unfortunately your security office 
prohibited the use of Teamviewer.


___
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: OT - Mac Notarization Problem - Desperation setting in

2023-08-25 Thread matthias rebbe via use-livecode
Congratulations. Good to know that you could resolve it.

And now you know why wanted to do a remote session to repeat all steps from 
creating app-specific pw to connecting to apples services. ;)
We could have found out sooner. ;) Unfortunately your security office 
prohibited the use of Teamviewer. 

Anyway, your are now setup to use Notarytool.

Matthias


> Am 25.08.2023 um 22:34 schrieb Timothy Bleiler via use-livecode 
> :
> 
> I think I’ve solved it.  I’m very grateful to Matthias both for his code 
> signing tool and his personal help with this problem.
> 
> In the end it looks like the trouble was caused by a combination of my 
> limited experience with the process and a lack of helpful feedback from 
> Apple’s online tools at critical points.
> 
> Here’s what happened.
> - I have 2 user accounts on my Mac that use different Apple IDs.
> 
> - Somehow the one I use for the Apple developer account had made my Mac NOT a 
> trusted device for the Apple ID I use for development. I have no idea how 
> this happened.
> You can verify that your device is trusted at appleid.apple.com 
>  for your account under 
> “Devices”.
> 
> - Despite the device not being trusted for the account, the website let me 
> think I’d created an app-specific password. I hadn’t succeed, but my lack of 
> experience prevented me from realizing that the second step of the process is 
> getting the actual password back from Apple and copying it down.  I didn’t 
> get anything, no error message, so in my ignorance I thought the seed string 
> I’d typed in WAS the password. So, I did NOT have an actual app-specific 
> password to use in the NotaryTool commands. This caused all commands 
> dependent on an app-specific password to fail.
> 
> What solved it for me was to go to System Settings, sign out of the Apple 
> account on the mac and sign back in again.
> Then sign back in to appleid.apple.com 
> , verify that my Mac 
> was a trusted device on my developer account and then create a NEW 
> app-specific password.
> This time I saw the second part when they send the actual password. I think 
> you need to copy this down because I don’t see any way to recover it again 
> later.
> 
> Once I had the new app-specific password and my Mac was a trusted device in 
> my developer account, the notaryTool commands worked without errors.
> 
> It all makes me long for the days when we could easily pass around Hypercard 
> stacks for the fun of it!!
> 
> 
___
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: Merging PDF pages

2023-08-25 Thread Eller, Roger via use-livecode
Thank you for this and all the details, Matthias.  I will give it a try.


~Roger


From: use-livecode  on behalf of 
matthias rebbe via use-livecode 
Sent: Friday, August 25, 2023 2:16 PM
To: How to use LiveCode 
Cc: matthias_livecode_150...@m-r-d.de 
Subject: Re: Merging PDF pages


CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.



Just noticed that my steps are missing something.
So here's version 2 of it.

1. download
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.pdflabs.com%2Ftools%2Fpdftk-the-pdf-toolkit%2Fpdftk_server-2.02-mac_osx-10.11-setup.pkg=05%7C01%7Croger.e.eller%40sealedair.com%7Ce1d5200433404eec54d008dba59780d1%7C2691a2514c384643af0b0c0982f197bd%7C0%7C0%7C638285842350859203%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=tEXnKnbF7xT3GjOMoYKIiM%2Fv3JwkS7pzKRM3op80KMI%3D=0

2. to extract the pkg run the following in Terminal
pkgutil --expand   

If the source path to the pkg contains spaces then put quotes around the path.

3. Now open the destination path to which you've extracted the .pkg. There 
should be another pkg pdftk.pkg

4. right click the file pdftk.pkg  and select "show package content"

5. Now you should see a file payload. Right click that file and select "open 
with" and select the archive utility to decompress the file payload.

6. After extraction you'll find a new folder "Payload 2"

7. open that folder. In that folder you will find the Lib and Bin folder. Copy 
those folder to another location.

Now in LC you can use shell shell function to call the pdftk

Example
set the folder to "path to the bin folder"

put shell("./pdftk  file1.pdf file2.pdf file3.pdf cat output mynewfile.pdf")


would create combine the three file..pdf file into a new one called 
mynewfile.pdf

To use pdftk server in your standalone  you just have to include both folders 
in your standalone.


On Windows you first have to run the setup of pdftk server. During the 
installation you can select the folder where pdftk server shall be installed. 
You then can copy the bin folder from that installation folder
and use it with your standalone on any other computer without the need to run 
the setup on that computer.




> Am 25.08.2023 um 17:00 schrieb matthias rebbe via use-livecode 
> :
>
> On which OS are you planning to do this?
>
> On Windows and macOS you could make use of PDFTK server from PDFLabs.com 
> >
>
> On macOS  PDFTK Server normally  has to be installed to use it. But you could 
> follow these steps here to get it working w/o installation.
>
> 1. Do not use the d/l link for pdftk Server from the pdfLabs website. That 
> version will not work on macOS11 and up. Instead download this version of 
> PDFTK Server. Sid Steward created a new version but did not update the d/l 
> link
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.pdflabs.com%2Ftools%2Fpdftk-the-pdf-toolkit%2Fpdftk_server-2.02-mac_osx-10.11-setup.pkg=05%7C01%7Croger.e.eller%40sealedair.com%7Ce1d5200433404eec54d008dba59780d1%7C2691a2514c384643af0b0c0982f197bd%7C0%7C0%7C638285842351015442%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=S5yjsFoOrBWQY%2FKUhQbD6WZxAzuRiBOK6Yrval2H1Q4%3D=0
>
> 2. to extract the pkg run the following in Terminal
> pkgutil --expand   
>
> If the source path to the pkg contains spaces then put quotes around the path.
>
> After extraction you'll find the 2 folders lib and bin and some others .The 2 
> mentioned ones are needed.
>
> Now in LC you can use shell shell function to call the pdftk
>
> Example
> set the folder to "path to the bin folder"
>
> put shell("./pdftk  file1.pdf file2.pdf file3.pdf cat output mynewfile.pdf")
>
>
> would create combine the three file..pdf file into a new one called 
> mynewfile.pdf
>
>
> I wrote this in a hurry, so i might have some error in my explanation. Just 
> ask, if you have problems.
>
> Regards,
>
> Matthias
>
>> Am 25.08.2023 um 15:10 schrieb Eller, Roger via use-livecode 
>> :
>>
>> It's been a while since I've posted a question here.  Is it possible to use 
>> livecode script to merge multiple 1-page PDFs into a multipage PDF without 
>> using Acrobat or other 3rd party 

Re: OT - Mac Notarization Problem - Desperation setting in

2023-08-25 Thread Bob Sneidar via use-livecode
Yes, this is the advantage of an. App specific password. It’s unrecoverable by 
you, and so by anyone else.

Bob S


On Aug 25, 2023, at 1:34 PM, Timothy Bleiler via use-livecode 
 wrote:

This time I saw the second part when they send the actual password. I think you 
need to copy this down because I don’t see any way to recover it again later.

___
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: OT - Mac Notarization Problem - Desperation setting in

2023-08-25 Thread matthias rebbe via use-livecode
If you mean that the the link was shown normal and also in sharp bracktes, then 
that seems to be normal here in the list.
I noticed this also in the past.


> Am 25.08.2023 um 22:41 schrieb Timothy Bleiler via use-livecode 
> :
> 
> It’s just not my day.  The goofy links in my last post are just supposed to 
> be references to the appleID site.  I don’t know how all the rest of that got 
> put in there.
> I’ve got to be more careful with my copy and paste I guess.
> 
> 
> 
>> On Aug 25, 2023, at 4:34 PM, Timothy Bleiler via use-livecode 
>>  wrote:
>> 
>> I think I’ve solved it.  I’m very grateful to Matthias both for his code 
>> signing tool and his personal help with this problem.
>> 
>> In the end it looks like the trouble was caused by a combination of my 
>> limited experience with the process and a lack of helpful feedback from 
>> Apple’s online tools at critical points.
>> 
>> Here’s what happened.
>> - I have 2 user accounts on my Mac that use different Apple IDs.
>> 
>> - Somehow the one I use for the Apple developer account had made my Mac NOT 
>> a trusted device for the Apple ID I use for development. I have no idea how 
>> this happened.
>> You can verify that your device is trusted at 
>> appleid.apple.com for your account under 
>> “Devices”.
>> 
>> - Despite the device not being trusted for the account, the website let me 
>> think I’d created an app-specific password. I hadn’t succeed, but my lack of 
>> experience prevented me from realizing that the second step of the process 
>> is getting the actual password back from Apple and copying it down.  I 
>> didn’t get anything, no error message, so in my ignorance I thought the seed 
>> string I’d typed in WAS the password. So, I did NOT have an actual 
>> app-specific password to use in the NotaryTool commands. This caused all 
>> commands dependent on an app-specific password to fail.
>> 
>> What solved it for me was to go to System Settings, sign out of the Apple 
>> account on the mac and sign back in again.
>> Then sign back in to appleid.apple.com, verify 
>> that my Mac was a trusted device on my developer account and then create a 
>> NEW app-specific password.
>> This time I saw the second part when they send the actual password. I think 
>> you need to copy this down because I don’t see any way to recover it again 
>> later.
>> 
>> Once I had the new app-specific password and my Mac was a trusted device in 
>> my developer account, the notaryTool commands worked without errors.
>> 
>> It all makes me long for the days when we could easily pass around Hypercard 
>> stacks for the fun of it!!
>> 
>> 
>> 
>> On Aug 25, 2023, at 2:38 PM, scott--- via use-livecode 
>>  wrote:
>> 
>> I use Matthias' brilliant “mrSignNotarizeHelperV4.livecode” project 
>> regularly and when I’ve had a problem in the past, ticking the “Debug mode” 
>> checkbox (which places each step of the terminal commands in the message box 
>> when you click the “Start” button) and then manually entering each of these 
>> steps as a command line in Terminal.app, has been helpful in figuring out 
>> exactly what step was failing. And sometimes, why.
>> 
>> --
>> Scott Morrow
>> 
>> Elementary Software
>> (Now with 20% less chalk dust!)
>> web   https://elementarysoftware.com/
>> email sc...@elementarysoftware.com
>> booth1-360-734-4701
>> --
>> 
>> On Aug 25, 2023, at 8:24 AM, Mark Smith via use-livecode 
>>  wrote:
>> 
>> Hi Tim,
>> 
>> Codesigning is (as you probably know) one of the tricker bits of building an 
>> app for distribution (and I’ve certainly had my share of failures and 
>> frustrations along the way). I am following this thread closely so if you 
>> don’t mind sharing, I’d be interested in hearing what the solution is, once 
>> you’ve found it.
>> 
>> Cheers and best of luck,
>> Mark
>> 
>> On 25 Aug 2023, at 3:37 pm, Timothy Bleiler via use-livecode 
>>  wrote:
>> 
>> Thank you Heather,
>> 
>> I’ll take a look.  Matthias Rebbe is also trying to help me find the problem.
>> 
>> Regards,
>> Tim Bleiler
>> 
>> 
>> 
>> On Aug 25, 2023, at 4:13 AM, Heather Laine via use-livecode 
>> mailto:use-livecode@lists.runrev.com>> wrote:
>> 
>> Tim - codesigning is not my expertise but failed password credentials I deal 
>> with frequently :). A possible gotcha is that your password is saved to your 
>> keychain, and then, if you change it, the changed password is overwritten by 
>> the saved password, invisibly since the password is hidden when entered. I 
>> would recommend deleting all saved passwords from your keychain for your 
>> certificates etc, and re-entering them to eliminate this possibility.
>> 
>> Probably not the issue but you never know...
>> 
>> Best Regards,
>> 
>> Heather
>> 
>> Heather Laine
>> Customer Services Manager
>> LiveCode Ltd
>> http://www.livecode.com/ 
>> 
>> 
>> 
>> On 24 Aug 2023, at 

Re: OT - Mac Notarization Problem - Desperation setting in

2023-08-25 Thread Timothy Bleiler via use-livecode
It’s just not my day.  The goofy links in my last post are just supposed to be 
references to the appleID site.  I don’t know how all the rest of that got put 
in there.
I’ve got to be more careful with my copy and paste I guess.



> On Aug 25, 2023, at 4:34 PM, Timothy Bleiler via use-livecode 
>  wrote:
>
> I think I’ve solved it.  I’m very grateful to Matthias both for his code 
> signing tool and his personal help with this problem.
>
> In the end it looks like the trouble was caused by a combination of my 
> limited experience with the process and a lack of helpful feedback from 
> Apple’s online tools at critical points.
>
> Here’s what happened.
> - I have 2 user accounts on my Mac that use different Apple IDs.
>
> - Somehow the one I use for the Apple developer account had made my Mac NOT a 
> trusted device for the Apple ID I use for development. I have no idea how 
> this happened.
> You can verify that your device is trusted at 
> appleid.apple.com for your account under “Devices”.
>
> - Despite the device not being trusted for the account, the website let me 
> think I’d created an app-specific password. I hadn’t succeed, but my lack of 
> experience prevented me from realizing that the second step of the process is 
> getting the actual password back from Apple and copying it down.  I didn’t 
> get anything, no error message, so in my ignorance I thought the seed string 
> I’d typed in WAS the password. So, I did NOT have an actual app-specific 
> password to use in the NotaryTool commands. This caused all commands 
> dependent on an app-specific password to fail.
>
> What solved it for me was to go to System Settings, sign out of the Apple 
> account on the mac and sign back in again.
> Then sign back in to appleid.apple.com, verify 
> that my Mac was a trusted device on my developer account and then create a 
> NEW app-specific password.
> This time I saw the second part when they send the actual password. I think 
> you need to copy this down because I don’t see any way to recover it again 
> later.
>
> Once I had the new app-specific password and my Mac was a trusted device in 
> my developer account, the notaryTool commands worked without errors.
>
> It all makes me long for the days when we could easily pass around Hypercard 
> stacks for the fun of it!!
>
>
>
> On Aug 25, 2023, at 2:38 PM, scott--- via use-livecode 
>  wrote:
>
> I use Matthias' brilliant “mrSignNotarizeHelperV4.livecode” project regularly 
> and when I’ve had a problem in the past, ticking the “Debug mode” checkbox 
> (which places each step of the terminal commands in the message box when you 
> click the “Start” button) and then manually entering each of these steps as a 
> command line in Terminal.app, has been helpful in figuring out exactly what 
> step was failing. And sometimes, why.
>
> --
> Scott Morrow
>
> Elementary Software
> (Now with 20% less chalk dust!)
> web   https://elementarysoftware.com/
> email sc...@elementarysoftware.com
> booth1-360-734-4701
> --
>
> On Aug 25, 2023, at 8:24 AM, Mark Smith via use-livecode 
>  wrote:
>
> Hi Tim,
>
> Codesigning is (as you probably know) one of the tricker bits of building an 
> app for distribution (and I’ve certainly had my share of failures and 
> frustrations along the way). I am following this thread closely so if you 
> don’t mind sharing, I’d be interested in hearing what the solution is, once 
> you’ve found it.
>
> Cheers and best of luck,
> Mark
>
> On 25 Aug 2023, at 3:37 pm, Timothy Bleiler via use-livecode 
>  wrote:
>
> Thank you Heather,
>
> I’ll take a look.  Matthias Rebbe is also trying to help me find the problem.
>
> Regards,
> Tim Bleiler
>
>
>
> On Aug 25, 2023, at 4:13 AM, Heather Laine via use-livecode 
> mailto:use-livecode@lists.runrev.com>> wrote:
>
> Tim - codesigning is not my expertise but failed password credentials I deal 
> with frequently :). A possible gotcha is that your password is saved to your 
> keychain, and then, if you change it, the changed password is overwritten by 
> the saved password, invisibly since the password is hidden when entered. I 
> would recommend deleting all saved passwords from your keychain for your 
> certificates etc, and re-entering them to eliminate this possibility.
>
> Probably not the issue but you never know...
>
> Best Regards,
>
> Heather
>
> Heather Laine
> Customer Services Manager
> LiveCode Ltd
> http://www.livecode.com/ 
>
>
>
> On 24 Aug 2023, at 18:02, Timothy Bleiler via use-livecode 
>  wrote:
>
> Hi all,
>
> I believe the problem I’m having is either on Apple’s end or something with 
> my local configuration but Apple has not been very helpful and I’m running 
> out of ideas, so I’m turning to the wealth of experience on this list in 
> desperation.
>
> I’ve been using the lessons from  Matthias Rebbe and V4 of his handy 
> 

Re: OT - Mac Notarization Problem - Desperation setting in

2023-08-25 Thread Timothy Bleiler via use-livecode
I think I’ve solved it.  I’m very grateful to Matthias both for his code 
signing tool and his personal help with this problem.

In the end it looks like the trouble was caused by a combination of my limited 
experience with the process and a lack of helpful feedback from Apple’s online 
tools at critical points.

Here’s what happened.
- I have 2 user accounts on my Mac that use different Apple IDs.

- Somehow the one I use for the Apple developer account had made my Mac NOT a 
trusted device for the Apple ID I use for development. I have no idea how this 
happened.
You can verify that your device is trusted at 
appleid.apple.com for your account under “Devices”.

- Despite the device not being trusted for the account, the website let me 
think I’d created an app-specific password. I hadn’t succeed, but my lack of 
experience prevented me from realizing that the second step of the process is 
getting the actual password back from Apple and copying it down.  I didn’t get 
anything, no error message, so in my ignorance I thought the seed string I’d 
typed in WAS the password. So, I did NOT have an actual app-specific password 
to use in the NotaryTool commands. This caused all commands dependent on an 
app-specific password to fail.

What solved it for me was to go to System Settings, sign out of the Apple 
account on the mac and sign back in again.
Then sign back in to appleid.apple.com, verify that 
my Mac was a trusted device on my developer account and then create a NEW 
app-specific password.
This time I saw the second part when they send the actual password. I think you 
need to copy this down because I don’t see any way to recover it again later.

Once I had the new app-specific password and my Mac was a trusted device in my 
developer account, the notaryTool commands worked without errors.

It all makes me long for the days when we could easily pass around Hypercard 
stacks for the fun of it!!



On Aug 25, 2023, at 2:38 PM, scott--- via use-livecode 
 wrote:

I use Matthias' brilliant “mrSignNotarizeHelperV4.livecode” project regularly 
and when I’ve had a problem in the past, ticking the “Debug mode” checkbox 
(which places each step of the terminal commands in the message box when you 
click the “Start” button) and then manually entering each of these steps as a 
command line in Terminal.app, has been helpful in figuring out exactly what 
step was failing. And sometimes, why.

--
Scott Morrow

Elementary Software
(Now with 20% less chalk dust!)
web   
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Felementarysoftware.com%2F=05%7C01%7Cbleiler%40buffalo.edu%7Ccc7afb2eab1b4bcb60b608dba59aa569%7C96464a8af8ed40b199e25f6b50a20250%7C0%7C0%7C638285855863548154%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=%2Fk0TjFvUmYt2BZ9CqydNyA9ZZx34rwuZC3FiprBPQ4s%3D=0
email sc...@elementarysoftware.com
booth1-360-734-4701
--

On Aug 25, 2023, at 8:24 AM, Mark Smith via use-livecode 
 wrote:

Hi Tim,

Codesigning is (as you probably know) one of the tricker bits of building an 
app for distribution (and I’ve certainly had my share of failures and 
frustrations along the way). I am following this thread closely so if you don’t 
mind sharing, I’d be interested in hearing what the solution is, once you’ve 
found it.

Cheers and best of luck,
Mark

On 25 Aug 2023, at 3:37 pm, Timothy Bleiler via use-livecode 
 wrote:

Thank you Heather,

I’ll take a look.  Matthias Rebbe is also trying to help me find the problem.

Regards,
Tim Bleiler



On Aug 25, 2023, at 4:13 AM, Heather Laine via use-livecode 
mailto:use-livecode@lists.runrev.com>> wrote:

Tim - codesigning is not my expertise but failed password credentials I deal 
with frequently :). A possible gotcha is that your password is saved to your 
keychain, and then, if you change it, the changed password is overwritten by 
the saved password, invisibly since the password is hidden when entered. I 
would recommend deleting all saved passwords from your keychain for your 
certificates etc, and re-entering them to eliminate this possibility.

Probably not the issue but you never know...

Best Regards,

Heather

Heather Laine
Customer Services Manager
LiveCode Ltd
https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.livecode.com%2F=05%7C01%7Cbleiler%40buffalo.edu%7Ccc7afb2eab1b4bcb60b608dba59aa569%7C96464a8af8ed40b199e25f6b50a20250%7C0%7C0%7C638285855863548154%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=Eaw78gb3oD9j4XuzyHu%2FdyRRerM%2FT0GunR2oGocDSzM%3D=0
 

Re: OT - Mac Notarization Problem - Desperation setting in

2023-08-25 Thread scott--- via use-livecode
I use Matthias' brilliant “mrSignNotarizeHelperV4.livecode” project regularly 
and when I’ve had a problem in the past, ticking the “Debug mode” checkbox 
(which places each step of the terminal commands in the message box when you 
click the “Start” button) and then manually entering each of these steps as a 
command line in Terminal.app, has been helpful in figuring out exactly what 
step was failing. And sometimes, why.

--
Scott Morrow

Elementary Software
(Now with 20% less chalk dust!)
web   https://elementarysoftware.com/
email sc...@elementarysoftware.com
booth1-360-734-4701
--

> On Aug 25, 2023, at 8:24 AM, Mark Smith via use-livecode 
>  wrote:
> 
> Hi Tim,
> 
> Codesigning is (as you probably know) one of the tricker bits of building an 
> app for distribution (and I’ve certainly had my share of failures and 
> frustrations along the way). I am following this thread closely so if you 
> don’t mind sharing, I’d be interested in hearing what the solution is, once 
> you’ve found it. 
> 
> Cheers and best of luck,
> Mark
> 
>> On 25 Aug 2023, at 3:37 pm, Timothy Bleiler via use-livecode 
>>  wrote:
>> 
>> Thank you Heather,
>> 
>> I’ll take a look.  Matthias Rebbe is also trying to help me find the problem.
>> 
>> Regards,
>> Tim Bleiler
>> 
>> 
>> 
>>> On Aug 25, 2023, at 4:13 AM, Heather Laine via use-livecode 
>>> mailto:use-livecode@lists.runrev.com>> 
>>> wrote:
>>> 
>>> Tim - codesigning is not my expertise but failed password credentials I 
>>> deal with frequently :). A possible gotcha is that your password is saved 
>>> to your keychain, and then, if you change it, the changed password is 
>>> overwritten by the saved password, invisibly since the password is hidden 
>>> when entered. I would recommend deleting all saved passwords from your 
>>> keychain for your certificates etc, and re-entering them to eliminate this 
>>> possibility.
>>> 
>>> Probably not the issue but you never know...
>>> 
>>> Best Regards,
>>> 
>>> Heather
>>> 
>>> Heather Laine
>>> Customer Services Manager
>>> LiveCode Ltd
>>> http://www.livecode.com/ 
>>> 
>>> 
>>> 
 On 24 Aug 2023, at 18:02, Timothy Bleiler via use-livecode 
  wrote:
 
 Hi all,
 
 I believe the problem I’m having is either on Apple’s end or something 
 with my local configuration but Apple has not been very helpful and I’m 
 running out of ideas, so I’m turning to the wealth of experience on this 
 list in desperation.
 
 I’ve been using the lessons from  Matthias Rebbe and V4 of his handy 
 mrSignNotarizeHelper stack.
 Code signing seems to work fine but when I get to the Notarization step I 
 always get an
 "Error: HTTP status code: 401. Invalid credentials. Username or password 
 is incorrect.
 
 I’m on an M1 Mac with OS 13.4.1, Xcode 14.3.1 is installed, Livecode 9.6.9.
 
 So far, this is what I’ve tried with the same result
 
 1) Verified developer account in good status with Apple
 2) Multiple checks of my credentials (Apple ID, team ID, app-specific 
 password) on Apple's developer and ID sites,
 3) Multiple checks of my credentials in the parameters I’m using
 4) Setting up a new app specific password on my account
 5) Trying with a different Livecode application
 6 Trying everything manually in Terminal. (What is apparent is any 
 subcommands of NotaryTool (e.g. submit, store-credentials) using my 
 credentials fail with the same error.
 
 7) Repeat everything on a brand new user account on my Mac
 8) Sought help through devprogr...@apple.com
 
 
 I’ve done codesigning and notarization many times before with the same 
 developer account with no issues.
 What’s new here for me is using NotaryTool and the app-specific password.
 
 I realize this is a long shot but I’m stuck, so it would be great if 
 anyone has any suggestions for solving this problem (even some detail I 
 may have missed in the steps I’ve already taken)
 
 Thanks,
 
 Tim Bleiler, Ph.D.
 Instructional Designer, HSIT
 University at Buffalo
 







___
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: Merging PDF pages

2023-08-25 Thread matthias rebbe via use-livecode
Just noticed that my steps are missing something.
So here's version 2 of it.

1. download
https://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/pdftk_server-2.02-mac_osx-10.11-setup.pkg

2. to extract the pkg run the following in Terminal
pkgutil --expand   

If the source path to the pkg contains spaces then put quotes around the path.

3. Now open the destination path to which you've extracted the .pkg. There 
should be another pkg pdftk.pkg

4. right click the file pdftk.pkg  and select "show package content"

5. Now you should see a file payload. Right click that file and select "open 
with" and select the archive utility to decompress the file payload.

6. After extraction you'll find a new folder "Payload 2"

7. open that folder. In that folder you will find the Lib and Bin folder. Copy 
those folder to another location.

Now in LC you can use shell shell function to call the pdftk

Example
set the folder to "path to the bin folder"

put shell("./pdftk  file1.pdf file2.pdf file3.pdf cat output mynewfile.pdf")


would create combine the three file..pdf file into a new one called 
mynewfile.pdf

To use pdftk server in your standalone  you just have to include both folders 
in your standalone.


On Windows you first have to run the setup of pdftk server. During the 
installation you can select the folder where pdftk server shall be installed. 
You then can copy the bin folder from that installation folder
and use it with your standalone on any other computer without the need to run 
the setup on that computer.




> Am 25.08.2023 um 17:00 schrieb matthias rebbe via use-livecode 
> :
> 
> On which OS are you planning to do this?
> 
> On Windows and macOS you could make use of PDFTK server from PDFLabs.com 
> 
> 
> On macOS  PDFTK Server normally  has to be installed to use it. But you could 
> follow these steps here to get it working w/o installation.
> 
> 1. Do not use the d/l link for pdftk Server from the pdfLabs website. That 
> version will not work on macOS11 and up. Instead download this version of 
> PDFTK Server. Sid Steward created a new version but did not update the d/l 
> link
> https://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/pdftk_server-2.02-mac_osx-10.11-setup.pkg
> 
> 2. to extract the pkg run the following in Terminal
> pkgutil --expand   
> 
> If the source path to the pkg contains spaces then put quotes around the path.
> 
> After extraction you'll find the 2 folders lib and bin and some others .The 2 
> mentioned ones are needed. 
> 
> Now in LC you can use shell shell function to call the pdftk
> 
> Example
> set the folder to "path to the bin folder"
> 
> put shell("./pdftk  file1.pdf file2.pdf file3.pdf cat output mynewfile.pdf")
> 
> 
> would create combine the three file..pdf file into a new one called 
> mynewfile.pdf
> 
> 
> I wrote this in a hurry, so i might have some error in my explanation. Just 
> ask, if you have problems.
> 
> Regards,
> 
> Matthias
> 
>> Am 25.08.2023 um 15:10 schrieb Eller, Roger via use-livecode 
>> :
>> 
>> It's been a while since I've posted a question here.  Is it possible to use 
>> livecode script to merge multiple 1-page PDFs into a multipage PDF without 
>> using Acrobat or other 3rd party software?
>> 
>> Thanks.
>> 
>> ~Roger
>> 
>> 
>> ___
>> 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: OT - Mac Notarization Problem - Desperation setting in

2023-08-25 Thread Mark Smith via use-livecode
Hi Tim,

Codesigning is (as you probably know) one of the tricker bits of building an 
app for distribution (and I’ve certainly had my share of failures and 
frustrations along the way). I am following this thread closely so if you don’t 
mind sharing, I’d be interested in hearing what the solution is, once you’ve 
found it. 

Cheers and best of luck,
Mark

> On 25 Aug 2023, at 3:37 pm, Timothy Bleiler via use-livecode 
>  wrote:
> 
> Thank you Heather,
> 
> I’ll take a look.  Matthias Rebbe is also trying to help me find the problem.
> 
> Regards,
> Tim Bleiler
> 
> 
> 
>> On Aug 25, 2023, at 4:13 AM, Heather Laine via use-livecode 
>> mailto:use-livecode@lists.runrev.com>> wrote:
>> 
>> Tim - codesigning is not my expertise but failed password credentials I deal 
>> with frequently :). A possible gotcha is that your password is saved to your 
>> keychain, and then, if you change it, the changed password is overwritten by 
>> the saved password, invisibly since the password is hidden when entered. I 
>> would recommend deleting all saved passwords from your keychain for your 
>> certificates etc, and re-entering them to eliminate this possibility.
>> 
>> Probably not the issue but you never know...
>> 
>> Best Regards,
>> 
>> Heather
>> 
>> Heather Laine
>> Customer Services Manager
>> LiveCode Ltd
>> http://www.livecode.com/ 
>> 
>> 
>> 
>>> On 24 Aug 2023, at 18:02, Timothy Bleiler via use-livecode 
>>>  wrote:
>>> 
>>> Hi all,
>>> 
>>> I believe the problem I’m having is either on Apple’s end or something with 
>>> my local configuration but Apple has not been very helpful and I’m running 
>>> out of ideas, so I’m turning to the wealth of experience on this list in 
>>> desperation.
>>> 
>>> I’ve been using the lessons from  Matthias Rebbe and V4 of his handy 
>>> mrSignNotarizeHelper stack.
>>> Code signing seems to work fine but when I get to the Notarization step I 
>>> always get an
>>> "Error: HTTP status code: 401. Invalid credentials. Username or password is 
>>> incorrect.
>>> 
>>> I’m on an M1 Mac with OS 13.4.1, Xcode 14.3.1 is installed, Livecode 9.6.9.
>>> 
>>> So far, this is what I’ve tried with the same result
>>> 
>>> 1) Verified developer account in good status with Apple
>>> 2) Multiple checks of my credentials (Apple ID, team ID, app-specific 
>>> password) on Apple's developer and ID sites,
>>> 3) Multiple checks of my credentials in the parameters I’m using
>>> 4) Setting up a new app specific password on my account
>>> 5) Trying with a different Livecode application
>>> 6 Trying everything manually in Terminal. (What is apparent is any 
>>> subcommands of NotaryTool (e.g. submit, store-credentials) using my 
>>> credentials fail with the same error.
>>> 
>>> 7) Repeat everything on a brand new user account on my Mac
>>> 8) Sought help through devprogr...@apple.com
>>> 
>>> 
>>> I’ve done codesigning and notarization many times before with the same 
>>> developer account with no issues.
>>> What’s new here for me is using NotaryTool and the app-specific password.
>>> 
>>> I realize this is a long shot but I’m stuck, so it would be great if anyone 
>>> has any suggestions for solving this problem (even some detail I may have 
>>> missed in the steps I’ve already taken)
>>> 
>>> Thanks,
>>> 
>>> Tim Bleiler, Ph.D.
>>> Instructional Designer, HSIT
>>> University at Buffalo
>>> 
>>> ___
>>> 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


Re: Merging PDF pages

2023-08-25 Thread matthias rebbe via use-livecode
On which OS are you planning to do this?

On Windows and macOS you could make use of PDFTK server from PDFLabs.com 


On macOS  PDFTK Server normally  has to be installed to use it. But you could 
follow these steps here to get it working w/o installation.

1. Do not use the d/l link for pdftk Server from the pdfLabs website. That 
version will not work on macOS11 and up. Instead download this version of PDFTK 
Server. Sid Steward created a new version but did not update the d/l link
https://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/pdftk_server-2.02-mac_osx-10.11-setup.pkg

2. to extract the pkg run the following in Terminal
pkgutil --expand   

If the source path to the pkg contains spaces then put quotes around the path.

After extraction you'll find the 2 folders lib and bin and some others .The 2 
mentioned ones are needed. 

Now in LC you can use shell shell function to call the pdftk

Example
set the folder to "path to the bin folder"

put shell("./pdftk  file1.pdf file2.pdf file3.pdf cat output mynewfile.pdf")


would create combine the three file..pdf file into a new one called 
mynewfile.pdf


I wrote this in a hurry, so i might have some error in my explanation. Just 
ask, if you have problems.

Regards,

Matthias

> Am 25.08.2023 um 15:10 schrieb Eller, Roger via use-livecode 
> :
> 
> It's been a while since I've posted a question here.  Is it possible to use 
> livecode script to merge multiple 1-page PDFs into a multipage PDF without 
> using Acrobat or other 3rd party software?
> 
> Thanks.
> 
> ~Roger
> 
> 
> ___
> 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: Merging PDF pages

2023-08-25 Thread panagiotis m via use-livecode
Hello all,

There is a built-in utility on MacOS for merging PDFs. You can call it from
"shell", as Paul suggested.

This seems to work - tested on MacOS Mojave. It merges "test1.pdf" and
"test2.pdf" into "merged.pdf" on Desktop.
Just check that the path of tApp actually exists in modern MacOS as well.

on mouseUp pButtonNumber
   local tShell, tApp
   put quote & "/System/Library/Automator/Combine PDF
Pages.action/Contents/Resources/join.py" & quote \
 into tApp
   put tApp && "-o ~/Desktop/merged.pdf ~/Desktop/test1.pdf
~/Desktop/test2.pdf" \
 into tShell
   get shell(tShell)
end mouseUp

Cheers,
Panos
--

On Fri, 25 Aug 2023 at 17:23, Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:

> The short answer is NO. There is nothing built into Livecode to take a
> set fo existing PDF files and append them to create a readable PDF that
> is them all stitched together. Neither the XPDF external nor the PDF
> widget will do this.
>
> You best option is to use some 3rd party command line utility that will
> merge PDF files that works on the platform or platforms your want to do
> this on and use the Livecode shell() function to call that command line
> utility.
>
> If this is going to be a distributed standalone, you can actually read
> the utility as a binary file and compress it as a staved property in
> your application, that can uncompress and install it on any target
> computer.
>
> We do this with the popular free open-source video tool ffmpeg for macOS
> and WIndows. Our app install it if needed on the target computer from a
> compressed copy bundled into our app and we use SHELL() to call it to do
> several video operations that can't be done in Livecode.
>
> Paul Dupuis
> Researchware
>
>
>
> On 8/25/2023 9:10 AM, Eller, Roger via use-livecode wrote:
> > It's been a while since I've posted a question here.  Is it possible to
> use livecode script to merge multiple 1-page PDFs into a multipage PDF
> without using Acrobat or other 3rd party software?
> >
> > Thanks.
> >
> > ~Roger
> >
> >
> > ___
> > 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: OT - Mac Notarization Problem - Desperation setting in

2023-08-25 Thread matthias rebbe via use-livecode
The Keychain.app does not have any influence on passwords entered in the 
command line.
Passwords entered in terminal will not be replaced by Keychain.app.

> Am 25.08.2023 um 16:37 schrieb Timothy Bleiler via use-livecode 
> :
> 
> Thank you Heather,
> 
> I’ll take a look.  Matthias Rebbe is also trying to help me find the problem.
> 
> Regards,
> Tim Bleiler
> 
> 
> 
>> On Aug 25, 2023, at 4:13 AM, Heather Laine via use-livecode 
>> mailto:use-livecode@lists.runrev.com>> wrote:
>> 
>> Tim - codesigning is not my expertise but failed password credentials I deal 
>> with frequently :). A possible gotcha is that your password is saved to your 
>> keychain, and then, if you change it, the changed password is overwritten by 
>> the saved password, invisibly since the password is hidden when entered. I 
>> would recommend deleting all saved passwords from your keychain for your 
>> certificates etc, and re-entering them to eliminate this possibility.
>> 
>> Probably not the issue but you never know...
>> 
>> Best Regards,
>> 
>> Heather
>> 
>> Heather Laine
>> Customer Services Manager
>> LiveCode Ltd
>> http://www.livecode.com/
>> 
>> 
>> 
>>> On 24 Aug 2023, at 18:02, Timothy Bleiler via use-livecode 
>>>  wrote:
>>> 
>>> Hi all,
>>> 
>>> I believe the problem I’m having is either on Apple’s end or something with 
>>> my local configuration but Apple has not been very helpful and I’m running 
>>> out of ideas, so I’m turning to the wealth of experience on this list in 
>>> desperation.
>>> 
>>> I’ve been using the lessons from  Matthias Rebbe and V4 of his handy 
>>> mrSignNotarizeHelper stack.
>>> Code signing seems to work fine but when I get to the Notarization step I 
>>> always get an
>>> "Error: HTTP status code: 401. Invalid credentials. Username or password is 
>>> incorrect.
>>> 
>>> I’m on an M1 Mac with OS 13.4.1, Xcode 14.3.1 is installed, Livecode 9.6.9.
>>> 
>>> So far, this is what I’ve tried with the same result
>>> 
>>> 1) Verified developer account in good status with Apple
>>> 2) Multiple checks of my credentials (Apple ID, team ID, app-specific 
>>> password) on Apple's developer and ID sites,
>>> 3) Multiple checks of my credentials in the parameters I’m using
>>> 4) Setting up a new app specific password on my account
>>> 5) Trying with a different Livecode application
>>> 6 Trying everything manually in Terminal. (What is apparent is any 
>>> subcommands of NotaryTool (e.g. submit, store-credentials) using my 
>>> credentials fail with the same error.
>>> 
>>> 7) Repeat everything on a brand new user account on my Mac
>>> 8) Sought help through devprogr...@apple.com
>>> 
>>> 
>>> I’ve done codesigning and notarization many times before with the same 
>>> developer account with no issues.
>>> What’s new here for me is using NotaryTool and the app-specific password.
>>> 
>>> I realize this is a long shot but I’m stuck, so it would be great if anyone 
>>> has any suggestions for solving this problem (even some detail I may have 
>>> missed in the steps I’ve already taken)
>>> 
>>> Thanks,
>>> 
>>> Tim Bleiler, Ph.D.
>>> Instructional Designer, HSIT
>>> University at Buffalo
>>> 
>>> ___
>>> 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


Re: OT - Mac Notarization Problem - Desperation setting in

2023-08-25 Thread Timothy Bleiler via use-livecode
Thank you Heather,

I’ll take a look.  Matthias Rebbe is also trying to help me find the problem.

Regards,
Tim Bleiler



> On Aug 25, 2023, at 4:13 AM, Heather Laine via use-livecode 
>  wrote:
>
> Tim - codesigning is not my expertise but failed password credentials I deal 
> with frequently :). A possible gotcha is that your password is saved to your 
> keychain, and then, if you change it, the changed password is overwritten by 
> the saved password, invisibly since the password is hidden when entered. I 
> would recommend deleting all saved passwords from your keychain for your 
> certificates etc, and re-entering them to eliminate this possibility.
>
> Probably not the issue but you never know...
>
> Best Regards,
>
> Heather
>
> Heather Laine
> Customer Services Manager
> LiveCode Ltd
> http://www.livecode.com/
>
>
>
>> On 24 Aug 2023, at 18:02, Timothy Bleiler via use-livecode 
>>  wrote:
>>
>> Hi all,
>>
>> I believe the problem I’m having is either on Apple’s end or something with 
>> my local configuration but Apple has not been very helpful and I’m running 
>> out of ideas, so I’m turning to the wealth of experience on this list in 
>> desperation.
>>
>> I’ve been using the lessons from  Matthias Rebbe and V4 of his handy 
>> mrSignNotarizeHelper stack.
>> Code signing seems to work fine but when I get to the Notarization step I 
>> always get an
>> "Error: HTTP status code: 401. Invalid credentials. Username or password is 
>> incorrect.
>>
>> I’m on an M1 Mac with OS 13.4.1, Xcode 14.3.1 is installed, Livecode 9.6.9.
>>
>> So far, this is what I’ve tried with the same result
>>
>> 1) Verified developer account in good status with Apple
>> 2) Multiple checks of my credentials (Apple ID, team ID, app-specific 
>> password) on Apple's developer and ID sites,
>> 3) Multiple checks of my credentials in the parameters I’m using
>> 4) Setting up a new app specific password on my account
>> 5) Trying with a different Livecode application
>> 6 Trying everything manually in Terminal. (What is apparent is any 
>> subcommands of NotaryTool (e.g. submit, store-credentials) using my 
>> credentials fail with the same error.
>>
>> 7) Repeat everything on a brand new user account on my Mac
>> 8) Sought help through devprogr...@apple.com
>>
>>
>> I’ve done codesigning and notarization many times before with the same 
>> developer account with no issues.
>> What’s new here for me is using NotaryTool and the app-specific password.
>>
>> I realize this is a long shot but I’m stuck, so it would be great if anyone 
>> has any suggestions for solving this problem (even some detail I may have 
>> missed in the steps I’ve already taken)
>>
>> Thanks,
>>
>> Tim Bleiler, Ph.D.
>> Instructional Designer, HSIT
>> University at Buffalo
>>
>> ___
>> 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: Merging PDF pages

2023-08-25 Thread Paul Dupuis via use-livecode
The short answer is NO. There is nothing built into Livecode to take a 
set fo existing PDF files and append them to create a readable PDF that 
is them all stitched together. Neither the XPDF external nor the PDF 
widget will do this.


You best option is to use some 3rd party command line utility that will 
merge PDF files that works on the platform or platforms your want to do 
this on and use the Livecode shell() function to call that command line 
utility.


If this is going to be a distributed standalone, you can actually read 
the utility as a binary file and compress it as a staved property in 
your application, that can uncompress and install it on any target computer.


We do this with the popular free open-source video tool ffmpeg for macOS 
and WIndows. Our app install it if needed on the target computer from a 
compressed copy bundled into our app and we use SHELL() to call it to do 
several video operations that can't be done in Livecode.


Paul Dupuis
Researchware



On 8/25/2023 9:10 AM, Eller, Roger via use-livecode wrote:

It's been a while since I've posted a question here.  Is it possible to use 
livecode script to merge multiple 1-page PDFs into a multipage PDF without 
using Acrobat or other 3rd party software?

Thanks.

~Roger


___
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: Merging PDF pages

2023-08-25 Thread Craig Newman via use-livecode
Richmond.

Did I mention this was a bit clunky?

Craig

> On Aug 25, 2023, at 9:39 AM, Craig Newman via use-livecode 
>  wrote:
> 
> Hmmm.
> 
> Rereading, did you want to be able to collect existing pdf documents, read 
> them, and then output a single new PDF?   If so, I guess you can import those 
> documents as images on successive cards, and do what I posted earlier.
> 
> Seems clunky, but then you are asking LC to do something clunky.
> 
> Craig
> 
>> On Aug 25, 2023, at 9:33 AM, Craig Newman via use-livecode 
>>  wrote:
>> 
>> Hi.
>> 
>> Sure. Try this in a button on card 1 of a new stack with, say, three cards:
>> 
>> on mouseUp
>> 
>> get the desktop folder
>> 
>> open printing to pdf it & "/" & “yourNamehere" & ".pdf"
>> 
>> repeat with x = 1 to 3
>> 
>> print card x
>> 
>> end repeat
>> 
>> close printing
>> 
>> end mouseUp
>> 
>> 
>> 
>> And I wonder if the new pdf widget has that built in.
>> 
>> 
>> 
>> Craig
>> 
>> 
>>> On Aug 25, 2023, at 9:10 AM, Eller, Roger via use-livecode 
>>>  wrote:
>>> 
>>> It's been a while since I've posted a question here.  Is it possible to use 
>>> livecode script to merge multiple 1-page PDFs into a multipage PDF without 
>>> using Acrobat or other 3rd party software?
>>> 
>>> Thanks.
>>> 
>>> ~Roger
>>> 
>>> 
>>> ___
>>> 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


Re: Merging PDF pages

2023-08-25 Thread Richmond Mathewson via use-livecode
Humph . . . importing documents at images and then knitting them 
together . . . be aware that you will lose one the most valuable things 
about a PDF document: the embedded text layer.


Richmond.

On 25.08.23 16:39, Craig Newman via use-livecode wrote:

Hmmm.

Rereading, did you want to be able to collect existing pdf documents, read 
them, and then output a single new PDF?   If so, I guess you can import those 
documents as images on successive cards, and do what I posted earlier.

Seems clunky, but then you are asking LC to do something clunky.

Craig


On Aug 25, 2023, at 9:33 AM, Craig Newman via use-livecode 
 wrote:

Hi.

Sure. Try this in a button on card 1 of a new stack with, say, three cards:

on mouseUp

get the desktop folder

open printing to pdf it & "/" & “yourNamehere" & ".pdf"

repeat with x = 1 to 3

print card x

end repeat

close printing

end mouseUp



And I wonder if the new pdf widget has that built in.



Craig



On Aug 25, 2023, at 9:10 AM, Eller, Roger via use-livecode 
 wrote:

It's been a while since I've posted a question here.  Is it possible to use 
livecode script to merge multiple 1-page PDFs into a multipage PDF without 
using Acrobat or other 3rd party software?

Thanks.

~Roger


___
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


Re: Merging PDF pages

2023-08-25 Thread Craig Newman via use-livecode
Hmmm.

Rereading, did you want to be able to collect existing pdf documents, read 
them, and then output a single new PDF?   If so, I guess you can import those 
documents as images on successive cards, and do what I posted earlier.

Seems clunky, but then you are asking LC to do something clunky.

Craig

> On Aug 25, 2023, at 9:33 AM, Craig Newman via use-livecode 
>  wrote:
> 
> Hi.
> 
> Sure. Try this in a button on card 1 of a new stack with, say, three cards:
> 
> on mouseUp
> 
> get the desktop folder
> 
> open printing to pdf it & "/" & “yourNamehere" & ".pdf"
> 
> repeat with x = 1 to 3
> 
> print card x
> 
> end repeat
> 
> close printing
> 
> end mouseUp
> 
> 
> 
> And I wonder if the new pdf widget has that built in.
> 
> 
> 
> Craig
> 
> 
>> On Aug 25, 2023, at 9:10 AM, Eller, Roger via use-livecode 
>>  wrote:
>> 
>> It's been a while since I've posted a question here.  Is it possible to use 
>> livecode script to merge multiple 1-page PDFs into a multipage PDF without 
>> using Acrobat or other 3rd party software?
>> 
>> Thanks.
>> 
>> ~Roger
>> 
>> 
>> ___
>> 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: Merging PDF pages

2023-08-25 Thread Craig Newman via use-livecode
Hi.

Sure. Try this in a button on card 1 of a new stack with, say, three cards:

on mouseUp

get the desktop folder

open printing to pdf it & "/" & “yourNamehere" & ".pdf"

repeat with x = 1 to 3

print card x

end repeat

close printing

end mouseUp



And I wonder if the new pdf widget has that built in.



Craig


> On Aug 25, 2023, at 9:10 AM, Eller, Roger via use-livecode 
>  wrote:
> 
> It's been a while since I've posted a question here.  Is it possible to use 
> livecode script to merge multiple 1-page PDFs into a multipage PDF without 
> using Acrobat or other 3rd party software?
> 
> Thanks.
> 
> ~Roger
> 
> 
> ___
> 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


Merging PDF pages

2023-08-25 Thread Eller, Roger via use-livecode
It's been a while since I've posted a question here.  Is it possible to use 
livecode script to merge multiple 1-page PDFs into a multipage PDF without 
using Acrobat or other 3rd party software?

Thanks.

~Roger


___
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: Polygrid sorting

2023-08-25 Thread Paul Dupuis via use-livecode

Thank you Panos!

I must be going blind not to have seen the example when I clicked on the 
Dictionary entry for the message!


On 8/25/2023 5:16 AM, panagiotis m via use-livecode wrote:

Hello Paul,

See the example in the dictionary for the "headerClick" message:

local sDirection

on headerClick pColumnNumber
 local tText

 put the text of me into tText
 put not sDirection[pColumnNumber] into sDirection[pColumnNumber]

 set the itemDel to tab

 # Sort data by this column.
 if sDirection[pColumnNumber] then
 sort lines of tText ascending by item pColumnNumber of each
 else
 sort lines of tText descending by item pColumnNumber of each
 end if

 set the text of me to tText
end headerClick

Kind regards,
Panos

--

On Fri, 25 Aug 2023 at 02:57, Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:


The Polygrid, unlike the Datagrid, has no built in column sorting. You
have to roll your own.

Before I write my own, has anyone written a column sort (i.e click on a
column header to sort by it) for a Poly grid they'd care to share?




___
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: Polygrid sorting

2023-08-25 Thread panagiotis m via use-livecode
Hello Paul,

See the example in the dictionary for the "headerClick" message:

local sDirection

on headerClick pColumnNumber
local tText

put the text of me into tText
put not sDirection[pColumnNumber] into sDirection[pColumnNumber]

set the itemDel to tab

# Sort data by this column.
if sDirection[pColumnNumber] then
sort lines of tText ascending by item pColumnNumber of each
else
sort lines of tText descending by item pColumnNumber of each
end if

set the text of me to tText
end headerClick

Kind regards,
Panos

--

On Fri, 25 Aug 2023 at 02:57, Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:

> The Polygrid, unlike the Datagrid, has no built in column sorting. You
> have to roll your own.
>
> Before I write my own, has anyone written a column sort (i.e click on a
> column header to sort by it) for a Poly grid they'd care to share?
>
>
>
>
> ___
> 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: OT - Mac Notarization Problem - Desperation setting in

2023-08-25 Thread Heather Laine via use-livecode
Tim - codesigning is not my expertise but failed password credentials I deal 
with frequently :). A possible gotcha is that your password is saved to your 
keychain, and then, if you change it, the changed password is overwritten by 
the saved password, invisibly since the password is hidden when entered. I 
would recommend deleting all saved passwords from your keychain for your 
certificates etc, and re-entering them to eliminate this possibility.

Probably not the issue but you never know...

Best Regards,

Heather

Heather Laine
Customer Services Manager
LiveCode Ltd
www.livecode.com



> On 24 Aug 2023, at 18:02, Timothy Bleiler via use-livecode 
>  wrote:
> 
> Hi all,
> 
> I believe the problem I’m having is either on Apple’s end or something with 
> my local configuration but Apple has not been very helpful and I’m running 
> out of ideas, so I’m turning to the wealth of experience on this list in 
> desperation.
> 
> I’ve been using the lessons from  Matthias Rebbe and V4 of his handy 
> mrSignNotarizeHelper stack.
> Code signing seems to work fine but when I get to the Notarization step I 
> always get an
> "Error: HTTP status code: 401. Invalid credentials. Username or password is 
> incorrect.
> 
> I’m on an M1 Mac with OS 13.4.1, Xcode 14.3.1 is installed, Livecode 9.6.9.
> 
> So far, this is what I’ve tried with the same result
> 
> 1) Verified developer account in good status with Apple
> 2) Multiple checks of my credentials (Apple ID, team ID, app-specific 
> password) on Apple's developer and ID sites,
> 3) Multiple checks of my credentials in the parameters I’m using
> 4) Setting up a new app specific password on my account
> 5) Trying with a different Livecode application
> 6 Trying everything manually in Terminal. (What is apparent is any 
> subcommands of NotaryTool (e.g. submit, store-credentials) using my 
> credentials fail with the same error.
> 
> 7) Repeat everything on a brand new user account on my Mac
> 8) Sought help through devprogr...@apple.com
> 
> 
> I’ve done codesigning and notarization many times before with the same 
> developer account with no issues.
> What’s new here for me is using NotaryTool and the app-specific password.
> 
> I realize this is a long shot but I’m stuck, so it would be great if anyone 
> has any suggestions for solving this problem (even some detail I may have 
> missed in the steps I’ve already taken)
> 
> Thanks,
> 
> Tim Bleiler, Ph.D.
> Instructional Designer, HSIT
> University at Buffalo
> 
> ___
> 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