SuperCard 4.83~ Beta

[Collection PhotoGraphex]

Hello Mark, 

I just had the opportunity to install the SuperCard 4.83d3 beta of July 10th, downloaded form your post, on a 2017 iMac Pro running High Sierra.

It all went smoothly and successfully.

I got the 'Un-Quarantine' dialog, the 32-bit warning, and the registration offer.

For the past year, I've been using several copies of the standalone version of my project on a daily basis on different computers. Now, while most people are on holiday, I expect to resume scripting the project and use the latest beta.

Many thanks!

André

[Dan Kelleher]

*** How To Get SuperCard 4.8 Beta ?

Hello All,

I've got the SuperCard 4.7.3 Suite of tools freshly installed and activated and all running well on Mojave installed on a second boot volume ('adjacent to' Catalina) on the Internal SSD of the 2018 MacBook Pro 15" intel. The Link for SuperCard registration of the activation is not working.

Now I want to transition to SuperCard 4.8 (?  4.83d1  ?), but none of the several download links which I've found, within recent conversations here, have worked (did get Joe's SuperEdit .crash report!    ha!).

*** So, how can I get SuperCard 4.8 beta and contribute to forward progress?

Little by. slow,

-Dan

Daniel J Kelleher

Daniel....@umassmed.edu

iPhone (774) 452-1025

5 Berkmans Street

Worcester MA, 01602

[Dan Kelleher]

Hello all,

Disregard my Last message. ---> I found a link that works in Mark's July 10th message.

please don't, "through me out the window" (fenêtre)

I think Stephane Leys would have really enjoyed Mark's entire recent nostalgic walk down memory lane, and perhaps especially --> how a bit of Mark's move rapid movement toward SuperCard way-back-when was based upon avoiding defenestration (fenêtre) at his previous job - if  by daybreak even he wasn't able to fix the flubs of co-"coders".

little by slow,

-Dan

Daniel j Kelleher

Daniel.  Kelleher @umassmed.edu

iPhone (774) 452-1025

5 Berkmans Street

Worcester, MA 01602

[Dan Kelleher]

André,

I Think that the SuperCard 4.83d3 that you downloaded did come from a link that Mark posted on July 10,

 but the link to it that you posted is not the correct link.

Little by slow,

-dan

On Thursday, July 25, 2024 at 10:37:25 PM UTC-4 Collection PhotoGraphex wrote:

[Collection PhotoGraphex]

Hello Dan, 

Le 19-août-2024 à 10:17:25, Dan Kelleher <danieljk...@gmail.com> a écrit :

I Think that the SuperCard 4.83d3 that you downloaded did come from a link that Mark posted on July 10,

 but the link to it that you posted is not the correct link.

As there are several links in this post, here is the actual functional post from Mark:

MARK LUCAS

7 juill. 2024, 12 h 10 min 13 s

à via SuperCard Discussion

OK sorry I have no clue WTF is going on here (yet), but somehow google seems to have totally mangled the contents of the Pouch folder I uploaded (which I downloaded and tested last night before posting the link).

So here's a link to YET ANOTHER zip file I've just uploaded, downloaded, installed, and successfully run here.

If this one doesn't work, I'm clearly going to have to recreate the DMG tools…

SO very sorry for the inconvenience!

-Mark

I've just tested the link at this moment and it is valid.

Regards,

André

-------------------

Google Drive folder for SuperCard 4.83d1.zip

[Dan Kelleher]

Hello André, Thank you!

I've been using SuperCard 4,73.

I just noticed that relative to 4.73, the current version 4.83d3 has lost a LOT of weight;

SuperEdit has lost 31% of its 5.5 MB (4.83d3 has slimed down to 3.8 MB) !

SuperCard has lost 11% of its 8.5 MB (4.83d3 is now 7.6 MB).

That Mark Lucas !

Interesting, eh?

Little by slow,

-Dan 

[MARK LUCAS]

Hi Dan,

LOL! I wish I could attribute that to diet and exercise, but actually it’s due to them being Intel-only debug builds.

Thus the x86 code itself is slightly larger than a release build would be (as it’s unoptimized and contains debug symbols) but there’s no PPC version of it adding bulk.

However if anybody still has the kit set up to test PPC code, I’d be happy to put up a full Universal Binary for that! You have to promise to post screen shots though… ;-)

I always wanted to include Intel-only and PPC-only builds in the distro (plus either all the Pouch projects with single-architecture externals, or else a tool to strip the unused code from them) just to minimize the required runtime footprint, but of course Scott wouldn’t hear of it (as usual because HE was the one who’d have to field support calls).

:-(

-Mark

[Drs Mark Schonewille]

I can test SC on a G4 PowerMac running OSX 10.4 and Mac OS 9 (dual booth). I'd do it just for the screenshots, currently I don't have time for serious testing.
I also have a G4 iMac (lamp) running Snow Leopard (IIRC).

Oh, would you perhaps compile for a Mac SE running System 7? 😉

Mark Schonewille
Economy-x-Talk
KvK 50277553
VAT NL002099948B21
https://ecxtalk.nl
https://www.nt2.nu

Programming LiveCode for the Real Beginner
http://www3.economy-x-talk.com/file.php?node=programming-livecode-for-the-real-beginner

Op 19-8-2024 om 18:13 schreef 'MARK LUCAS' via SuperCard Discussion:

[MARK LUCAS]

Hi Mark,

Here's a link to fresh Universal Binary builds of SC, SE, and SCH.

In theory they should launch on both 10.4 and 10.6, though some newer features will of course be absent under Tiger.

Don't forget your safety helmet and lead apron! ;-)

Thanks again,

-Mark

[Collection PhotoGraphex]

Hello Mark, 

Thank you for your dedication for the continuity of SuperCard!

Le 21-août-2024 à 02:17:31, 'MARK LUCAS' via SuperCard Discussion <superca...@googlegroups.com> a écrit :

Hi Mark,

Here's a link to fresh Universal Binary builds of SC, SE, and SCH.

In theory they should launch on both 10.4 and 10.6, though some newer features will of course be absent under Tiger.

Here is my report for the installation of the SC4.83 Test Universal Builds:

After downloading the folder from the link above, I copied the whole folder on the Finder of two Macintoshes for installation into the 'Applications' folder.

• iMac Pro 2017 running MacOS X  High Sierra 10.13.6

The previous SuperCard beta was already installed on this Mac. 

I transferred the 'SuperCard 4.8.app' and the 'SuperEdit 4.8.app' into the 'Applications' folder. 

I copied the 'SuperCard Help.app' into the </Library/Application Support/SuperCard 4.8.2/SC Pouch/SC Help/> folder and replaced the existing one. 

On the first launch of the 'SuperCard 4.8.app' I had the SuperCard 'Authenticate' dialog which successfully un-quarantined the application. 

The 'SuperCard 4.8.app' and the 'SuperEdit 4.8.app' launched successfully thereafter. 

Same thing for the 'SuperEdit 4.8.app'.

In the message box the command 'the expirationdate' returns December 31st 2026.

I will use this mac and this SuperCard beta version for further scripting.

• Mac Mini G4 running MacOS X Tiger 10.4.11

The previous SuperCard version installed on this Mac is 4.7.3. Nowadays I just use the standalone version of the SuperCard projects on those macs that are used as a bridge between the older HyperCard projets and the SuperCard ones. 

I transferred the 'SuperCard 4.8.app' and the 'SuperEdit 4.8.app' into the 'Applications' folder. 

I copied the folder 'SuperCard 4.8.2' that you provided from a previous post into </Library/Application Support/>. I supposed I could have duplicated the existing one and renamed it 'SuperCard 4.8.2'. 

I copied the 'SuperCard Help.app' into the </Library/Application Support/SuperCard 4.8.2/SC Pouch/SC Help/> folder and replaced the existing one. 

The 'SuperCard 4.8.app' and the 'SuperEdit 4.8.app' launched successfully. Same thing for the 'SuperEdit 4.8.app'.

The only remarks, which might not be related to SuperCard is the large icon for the 'SuperCard Help.app' is not showing, just the small one! 

Don't forget your safety helmet and lead apron! ;-)

Didn't need to! ;-)

Regards,

André

[hodger]

Hi Mark,

I'm interested in trying the Beta.  Actually, I was planning to make the purchase but then the site vanished.  I'm still at 4.7.3.

I downloaded and installed, but it seems this beta wants to see an existing v4.8 SCPouch, which of course I don't have.  

#1 - any way I can play with the Beta as a 4.7.3 user?

#2 - I assume you'll alert the list whenever it's possible to purchase an upgrade once more.

Thanks,

Greg

[MARK LUCAS]

Hi Greg,

There should be a copy of the /Library/Application Support/SuperCard 4.8.2/ folder here in that earlier zip file I posted back in mid-July.

Just remember to swap in the updated Help app

Thanks,

-Mark

[Collection PhotoGraphex]

Hello Mark,

Le 22-août-2024 à 06:00:03, hodger <mkt...@track25.studio> a écrit :

I'm interested in trying the Beta.  Actually, I was planning to make the purchase but then the site vanished.  I'm still at 4.7.3.

I am also interested to purchase the next upgrade for SuperCard or for the time being additional licence(s) to encourage the continuation of the development of the software. 

Regards,

André

[Dan Kelleher]

Mark,

As Greg and André said, I too would certainly pay for the upgrade. I would do this via any mechanism you might suggest now, given the present web site status - if that might help. In the past, one time, I bought something in the USA for Ian Bridges and shipped it to him overseas and we used the PayPal mechanism ?

Anywho, keep it simple. Just want you to know we care. Everyone does. 

I will continue using the beta and report any issues. 

I’m happy to have gotten SuperCard back up and running here after missing it for too long. 😀

Little by slow,

-Dan

On Aug 22, 2024, at 11:52 AM, Collection PhotoGraphex <photogr...@gmail.com> wrote:

Hello Mark,

--
You received this message because you are subscribed to the Google Groups "SuperCard Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to supercard-tal...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/supercard-talk/22D6DBFB-3F8D-4BA2-ADBC-FCBD265BEEE2%40gmail.com.

[MARK LUCAS]

On Aug 22, 2024, at 11:52 AM, Collection PhotoGraphex <photogr...@gmail.com> wrote:

I am also interested to purchase the next upgrade for SuperCard or for the time being additional licence(s) to encourage the continuation of the development of the software. 

Hi All,

I certainly appreciate the gestures of support!

Unfortunately as of now I have no way to process payments or issue new licenses (since I haven't been able to obtain Scott's registration database or any other records related to SuperCard, so while I can generate license keys I can't tell whether I'm reissuing already-used ones).

For now at least the goal of this round of testing is just to assemble final working versions of the 32-bit apps and plugins with all the latest fixes and workarounds and stuff Scott wouldn't let me include, remove all the registration sniffing, and come up with a final 'classic' release I can make freely available (however one does that nowadays).

So the most helpful thing interested parties can do is simply to test these builds, and the more obscure the feature the better. What I really need most to promptly and expeditiously complete this step is not money, but BUG REPORTS!

I'm currently going through Standalone Maker (plus the scripts for creating its engine files) cleaning stuff up so I can post an unprotected version of that too, in case anyone's been wondering about what goes on under its hood or felt like trying to shoehorn in relevant portions of the little quick & dirty codesigning project I made for Scott that's been circulating privately since 2016 (but which he refused to ship and forbade me to integrate into SaM, again because he feared it would generate support calls).

More news on that front soon…

-Mark

[hodger]

Thanks a lot Mark, I'll give it a try.  

I think 4.7.3 to 4.8.3 is quite a jump.  Is there a pdf or something that points out the added features?  

Thanks,

Greg

[MARK LUCAS]

Hopefully google will let this attachment through since it doesn't contain any executables:

[MARK LUCAS]

Hi Gang,

Here's an updated version of the wee code signing utility I wrote for Scott (to sign the SuperCard distros) that's been circulating off-label for years because he refused to distribute it through channels. Hopefully google won't block it:

[Collection PhotoGraphex]

Hello Mark, 

Le 23 août 2024 à 15:56, 'MARK LUCAS' via SuperCard Discussion <superca...@googlegroups.com> a écrit :

It's just a vanilla SuperCard droplet wrapper around a couple of simple shell scripts which recursively strip off any shmutz (quarantine xattrs or Finder detritus) that would prevent signing from the bundle(s) you drop onto it, then codesigns the executables inside.

Downloaded the 'Code Signer.sc45’ project into the applications folder on an iMac Pro 2017 running MacOS X High Sierra 10.13.6.

Launched the 'SuperCard 4.83d3 Test Universal Builds’ application successfully.

On launching the 'Code Signer.sc45’ project I am getting the SC caution dialog:

SuperTalk Error Number 19

Expected end of the line but found something else 

In the script editor at line 34, the cursor is flashing at:

alert cution "No valid Apple Developer codesigning identity found! » explain ¬

I’ve corrected the obvious spelling mistake, the new line 34:

alert caution "No valid Apple Developer codesigning identity found!" explain ¬

On re-launching the 'Code Signer.sc45’ project I am getting the SC alert dialog:

No valid Apple Developper code signing identity found!

To codesign applications …

And the alert SC dialog:

No valid signing identity found!

You cannot code sign without a valid certificate.

After which, if I drop a valid standalone in the field under “Drop App(s) Here”, I am get the previous SC alert dialog: 

No valid signing identity found!

You cannot code sign without a valid certificate.

The card field stays empty!

———————

Here are the results for each shell: 

shell(merge("/usr/bin/xattr -dr `com.apple.quarantine` `[[hfsToPosix(thePath)]]`"))

-> EMPTY

shell(merge("/usr/bin/codesign --verbose --sign `[[gDevID ]]` --deep --force `[[hfsToPosix(thePath)]]` 2>&1"))

-> error: The specified item could not be found in the keychain.

shell(merge("/usr/bin/codesign --verify -vvvv `[[hfsToPosix(thePath)]]` 2>&1"))

-> /thePath: No such file or directory

trim(shell(merge("security find-identity -v -p codesigning | grep '`'")))

-> EMPTY

———————

What should I do next?

Regards

André

[MARK LUCAS]

Hi André,

Thanks so much for finding that typo!

If you don't have an Apple developer account (and associated signing certificates) then I'm afraid that's all the testing you can do.

But this does at least establish that the underlying command-line utility is present and functions as expected when no valid certs are installed.

Now we just need somebody who's got a developer account to try it…

<crosses fingers>

-Mark

[Collection PhotoGraphex]

Hello, 

Le 26-août-2024 à 23:11:56, 'MARK LUCAS' via SuperCard Discussion <superca...@googlegroups.com> a écrit :

If you don't have an Apple developer account (and associated signing certificates) then I'm afraid that's all the testing you can do.

Does it mean necessarily an annual paying subscription to obtain the necessary code signing certificate? 

Apple Developer Program - Apple Developer

Would there be additional benefits for the development of SuperCard if I do take this subscription? 

Regards,

André

[MARK LUCAS]

Hi André,

IIRC Apple policy on this has changed several times recently, but FWICT the latest is that unpaid developer accounts are apparently able to create only temporary provisioning profiles (the things that identify you to the signing authority) which remain valid for one week (and then have to be re-created) to use for testing purposes (i.e., NOT for actually distributing apps to the public).

The post I saw about doing this used Xcode to create the profile though. I would expect one can do the same thing under the regular certificate-generating UI on developer.apple.com, but I can’t actually confirm this (since both my accounts *are* paid ones).

Unless you’re trying to distribute SuperCard standalones to other users (or just install them yourself on multiple Macs) I wouldn’t expect a paid account really makes much sense.

However it would definitely be helpful to know whether those temporary provisioning profiles actually work with the Apple security and codesign  command-line tools used by that test project, so if you have an unpaid developer account then trying to create and install a temporary profile and using it to try to codesign a test standalone with the posted project should be illuminating.

Does that make sense?

Thanks,

-Mark

[hodger]

HI Mark,

Excited about your effort to wrap up "classic SC".  I'm still at 4.7.3, and have a useful workflow through High Sierra, with most things ok in Mojave.  (Must build standalones in Sierra or High Sierra). Of course none of this has any code-signing mess involved.  Will your current effort behave similarly to what I'm using now?  Seems the standalones I build currently work fine without code-signing, possibly with the need to "open anyway" 

Thanks,

Greg

[MARK LUCAS]

On Oct 3, 2024, at 2:40 AM, hodger <mkt...@track25.studio> wrote:

Of course none of this has any code-signing mess involved.  Will your current effort behave similarly to what I'm using now?  Seems the standalones I build currently work fine without code-signing, possibly with the need to "open anyway”

Just to be clear, the way Apple security works you aren't hassled about apps (for example SC standalones) that were created on the local machine. Things only turn messy when you take something you built (but didn’t codesign) to another Mac, which is where GateKeeper rears its ugly head.

So don’t assume you’re immune to these issues until you’ve tried taking your standalones to another Mac and running them there.

I expect you’ll find 4.73-based  standalones are just as vulnerable to this foolishness as 4.8’s in GateKeeper-afflicted OS versions. For obvious reasons the mechanism isn’t 'opt-in’… ;-)

-Mark

[Collection PhotoGraphex]

Hello Mark

Le 26-août-2024 à 23:11:56, 'MARK LUCAS' via SuperCard Discussion <superca...@googlegroups.com> a écrit :

If you don't have an Apple developer account (and associated signing certificates) then I'm afraid that's all the testing you can do.

But this does at least establish that the underlying command-line utility is present and functions as expected when no valid certs are installed.

Now we just need somebody who's got a developer account to try it…

Sorry for the delay, I had to take a long detour. Being back, I installed Apple xCode 11.3.1 on a Mac Mini running MacOS High Sierra and xCode 16.0 on another Mac Mini running Sonoma. I have an Apple Developper ID from serval years ago, but I haven't enrolled yet to the paying Apple Developer Program.

From the xCode 11.3.1 on which Mac Mini I have also installed the “SuperCard 4.83d3 Test Universal Builds” folder including 'Code Signer.sc45' downloaded for your August 23rd post, I've made the following tests. Maybe there is a new version of the Code Singer since?

In the preferences of xCode xCode 11.3.1, in the 'Account' tab, I've created an 'Apple Development Certificate' using my 'Apple Development' ID, and then exported it on the Desktop. In the 'Keychain' application, I did a drag and drop in the 'Session' window. 

After launching the Code Signer in SuperCard 4.83d3, I've selected the certificate, without error and then dragged and dropped a recently created SuperCard standalone. Here are the collected logs:

/Users/andre.tremblay/Desktop/SuperPhotox 3.app: replacing existing signature

Warning: unable to build chain to self-signed root for signer "Apple Development: andre.t...@photographex.com (KV6NP7S9WF)"Warning: unable to build chain to self-signed root for signer "Apple Development: andre.t...@photographex.com (KV6NP7S9WF)"

Warning: unable to build chain to self-signed root for signer "Apple Development: andre.t...@photographex.com (KV6NP7S9WF)"

/Users/andre.tremblay/Desktop/SuperPhotox 3.app: signed app bundle with Mach-O universal (i386 ppc) [com.photographex]

/Users/andre.tremblay/Desktop/SuperPhotox 3.app: CSSMERR_TP_NOT_TRUSTED In architecture: i386

After this, in launching the standalone application, I've got a warning from 'Little Snitch':

Warning

The code signature of the process has a formal error. This probably indicates that somebody is trying to pretend a valid code signature, or that the developer used inappropriate, non-standard tools to create the signature. Since the existing rule matches any process, it cannot specify identification characteristics for a particular process. Depending on whether you trust the program in spite of the error, create a specific rule to allow or deny the connection for this program only.

After accepting this warning the standalone application, launched and seems to perform normally.

I suppose the warning from the 'Code Signer.sc45' is caused by the insufficient level of authority of the certificate? 

Not being familiar with the whole procedure, it might be something else?

What can I do next?

Would you suggest I take the Apple Developper enrollment? 

Many thanks for your dedicated support! 

André

============

FYI, trying the load the <https://supercard.us> web page that is redirected to <http://167.99.236.37>, I am getting this popping message in Safari, which seems to be a fraud:

Apple Contact Apple Support (USA head office) Number:+1-855-324-3424

Apple System Security Center 

App: Ads.fiancetrack(2).dll

Threat Detected: Trojan Spyware

Access to this Apple Device has been blocked for security reasons.

Contact Apple (USA head office):+1-855-324-3424

Contact Apple (USA head office) Number: +1-855-324-3424

Contact Apple Toll free Number: +1-855-324-3424

And trying <http://www.solutionsetcetera.com>  redirect to “Macao Gaming Inspection and Coordination Bureau”!