Improvements for 1.4.8

[juanpc2018]

#1. BigSur does Not allow to "Downgrade" to Catalina... in fact it takes a million years to "upgrade" from Catalina to BigSur. Older versions of OSX allowed to Up & Down grade very easy, Exept El Capitan, needs a Clean install.

1.4.7 does Not work with [Install to This Machine] Option. 1.4.8 should detect what OSX im running and give a Warning / Forbiden Logo "Apple does Not allow to Downgrade BigSur" you need a clean install, make a backup of your files. in the [Install to This Machine] Icon.

i havent tested Monterey or Ventura, but i guess its the same, because the Hybrid Kernel.

[Install to HDD or USB] works Ok. Clean Install to other HDD/SSD if formatted as APFS GPT.

but.... #2. installed Catalina to a USB3.0 hdd with a Supported Machine, and did Not installed the Patch...?

it should ask the user, give the option. Because i dont need to have the Unsupported machine infront of me. i could install in other machine a MacMini, and move the HDD to the Unsupported machine later.

"If the Mountain does Not go to Mahoma, Mahoma goes to the Mountain." MacPro5,1 2010 are very heavy... its better to move the HDD. LOL.™

i dont have a Metal compatible GPU available at this moment, for x or y reason.. i need a new gpu, or i havent done the Neklas GPU PSU cable mod

instead of waiting, i could install Catalina on a Supported Mac, and move the HDD later when i can get a Metal comaptible GPU or PSU mod for the other mac.

IF installer does Not give the option to install patch on supported machine, i have to install again. at this moment is better to have a "master" ssd/hhd to clone and change UUID, instead of clean install, like Vinyl 12" stampers. https://bombich.com/kb/ccc4/ccc-found-multiple-volumes-same-universally-unique-identifier https://developer.apple.com/documentation/corefoundation/cfuuid-rci

The idea is to move the HDD to different machines without problem.

[clsource]

Hello, normally such use case can be fullfilled using a webapp made with React, Vue, Svelte or similar that connects with the Wordpress Rest API. Then upload it to a server you control and finally using that url for embed it on a Jasonette web container.

A popular option too is using the services at bubble.io and create an app with that 👍 (and then embed it with Jasonelle). But any website would do.

https://github.com/jasonelle/jasonelle/wiki

{
    "$jason": {
        "body": {
            "background": {
                "type": "html",
                "url": "https://www.google.com",
                "style": {
                    "background": "#ffffff",
                    "progress" : "rgba(0,0,0,0)"
                },
                "action": {
                    "type": "$default"
                }
            }
        }
    }
}

[niszlo]

Ok i managed this pointing to a PWA i cloned & mostly recoded.

Sole problem left now : to publish the resulting signed APK, Play Store requires API 29 as target and idk how ...

Also got a warning that "com.jasonette" already exists, shall i rename subfolders and therefore dependancies pathes everywhere needed, to be able to publish ?

Thanks for suggestions to finalize this.

PS : i'm now installing SKD 10.0 + changing pathes to see if that solves Play Store warnings ...

[clsource]

You can also check the Android setup guide :)

https://jasonelle-archive.github.io/docs/legacy/android/