On 31/07/2022 11:18, Alan B wrote:
> Andy Hewitt <thewildrover@icloud.com> wrote:
>> Andy Hewitt <thewildrover@icloud.com> wrote:
>>
>>> However, I would prefer it if it were possible to change it on an app by
>>> app basis (although I know you can for some if they include the option).
>>>
>>> I find it is preferable to have the dark mode for some things (Photos is
>>> one, although that does use a dark background when editing, but the
>>> switch from light to dark suddenly is not great), but not others (like
>>> Maps, that's just unusable in dark mode).
>>
>> Well I never! Shortcuts to the rescue. I never even considered the
>> possibility that it could even be done that way.
>>
>> I’ve set up a Shortcuts ‘Automation’ routine that sets dark mode when I
>> open Photos, and then reverts to light mode when it quits. Perfect - and of
>> course you could do that for any app you need to.
>
> That seems like a very useful shortcut! Knowing a bit about AppleScript
> helps I guess?

You build shortcuts using drag and drop from a palette of commands drawn
from all installed apps. There are commands to run scripts of various
types too, but you might not need them.

Personally I find Shortcuts as annoying as Applescript, though for
different reasons. Shortcuts only seems to let you do what the other app
developers thought of, and nothing else. Applescript's syntax is just
painful for anyone who has ever done programming and I'm not convinced
it is useful for anyone who hasn't.

--
Chris

Chris Ridd <chrisridd@mac.com> wrote:
> On 31/07/2022 11:18, Alan B wrote:
>> Andy Hewitt <thewildrover@icloud.com> wrote:
>>> Andy Hewitt <thewildrover@icloud.com> wrote:
>>>
>>>> However, I would prefer it if it were possible to change it on an app by
>>>> app basis (although I know you can for some if they include the option).
>>>>
>>>> I find it is preferable to have the dark mode for some things (Photos is
>>>> one, although that does use a dark background when editing, but the
>>>> switch from light to dark suddenly is not great), but not others (like
>>>> Maps, that's just unusable in dark mode).
>>>
>>> Well I never! Shortcuts to the rescue. I never even considered the
>>> possibility that it could even be done that way.
>>>
>>> I’ve set up a Shortcuts ‘Automation’ routine that sets dark mode when I
>>> open Photos, and then reverts to light mode when it quits. Perfect - and of
>>> course you could do that for any app you need to.
>>
>> That seems like a very useful shortcut! Knowing a bit about AppleScript
>> helps I guess?
>
> You build shortcuts using drag and drop from a palette of commands drawn
> from all installed apps. There are commands to run scripts of various
> types too, but you might not need them.
>
> Personally I find Shortcuts as annoying as Applescript, though for
> different reasons. Shortcuts only seems to let you do what the other app
> developers thought of, and nothing else. Applescript's syntax is just
> painful for anyone who has ever done programming and I'm not convinced
> it is useful for anyone who hasn't.

I have ‘played’ with AS over the years but never became really anyway near
expert with it. A year or so ago I wrote a couple of scripts with the
intention of using them in shortcuts but never bothered in the end. I agree
AS’s syntax is not for the faint hearted! I prefer shell scripts - not that
I’m expert in those too!

--
Cheers, Alan

In article <tc5rf4$aipb$1@dont-email.me>, Chris Ridd
<chrisridd@mac.com> wrote:

> Personally I find Shortcuts as annoying as Applescript, though for
> different reasons. Shortcuts only seems to let you do what the other app
> developers thought of, and nothing else.

applescript is limited to what is exposed in the dictionary. only four
events are required. the rest is up to the developer. some apps are
very thorough. most are not.

> Applescript's syntax is just
> painful for anyone who has ever done programming and I'm not convinced
> it is useful for anyone who hasn't.

it is.

On 31/07/2022 11:18, Alan B wrote:
> Andy Hewitt <thewildrover@icloud.com> wrote:
>> Andy Hewitt <thewildrover@icloud.com> wrote:
>>
>>> However, I would prefer it if it were possible to change it on an app by
>>> app basis (although I know you can for some if they include the option).
>>>
>>> I find it is preferable to have the dark mode for some things (Photos is
>>> one, although that does use a dark background when editing, but the
>>> switch from light to dark suddenly is not great), but not others (like
>>> Maps, that's just unusable in dark mode).
>>
>> Well I never! Shortcuts to the rescue. I never even considered the
>> possibility that it could even be done that way.
>>
>> I’ve set up a Shortcuts ‘Automation’ routine that sets dark mode when I
>> open Photos, and then reverts to light mode when it quits. Perfect - and of
>> course you could do that for any app you need to.
>
> That seems like a very useful shortcut! Knowing a bit about AppleScript
> helps I guess?

Not at all, it was all simple drag/drop, select from menus kind of stuff.

--
Andy H

On 31/07/2022 13:10, Chris Ridd wrote:

> Personally I find Shortcuts as annoying as Applescript, though for
> different reasons. Shortcuts only seems to let you do what the other app
> developers thought of, and nothing else. Applescript's syntax is just
> painful for anyone who has ever done programming and I'm not convinced
> it is useful for anyone who hasn't.

Perhaps, but in this case, the desired result was achieved easily, and
exactly as needed. I'm not really bothered what it was that got me
there, to be honest.

Applescript has often got me things done that I wouldn't have done
otherwise (haven't done any programming stuff since I had an Atari 8-bit
in the 80's). I quite often use other's scripts and modify them to suit
my needs (like Old Toad's Photos scripts, which I use to create various
batch Titles in Photos).

--
Andy H

On 31 Jul 2022 at 16:34:59 BST, "Andy Hewitt" <thewildrover@icloud.com> wrote:

> On 31/07/2022 11:18, Alan B wrote:
>> Andy Hewitt <thewildrover@icloud.com> wrote:
>>> Andy Hewitt <thewildrover@icloud.com> wrote:
>>>
>>>> However, I would prefer it if it were possible to change it on an app by
>>>> app basis (although I know you can for some if they include the option).
>>>>
>>>> I find it is preferable to have the dark mode for some things (Photos is
>>>> one, although that does use a dark background when editing, but the
>>>> switch from light to dark suddenly is not great), but not others (like
>>>> Maps, that's just unusable in dark mode).
>>>
>>> Well I never! Shortcuts to the rescue. I never even considered the
>>> possibility that it could even be done that way.
>>>
>>> I’ve set up a Shortcuts ‘Automation’ routine that sets dark mode when I
>>> open Photos, and then reverts to light mode when it quits. Perfect - and of
>>> course you could do that for any app you need to.
>>
>> That seems like a very useful shortcut! Knowing a bit about AppleScript
>> helps I guess?
>
> Not at all, it was all simple drag/drop, select from menus kind of stuff.

Yes you're correct - I wasn't thinking outside the box, so to speak. I've
accomplished something similar now with 4 essentially d&d actions. Much easier
than messing with AppleScript.

--
Cheers, Alan

I'm in the same boat: I haven't upgraded from Mojave because I like iPhoto and don't use an iPhone so I dont like Photos. Also, I use Fusion so I dont want to update to APFS.

But my MBP may have just died and Ihave been told that an insurance company is going to pay for a new computer

So I will be doing a full system restore of Mojave onto a 2022 MBP!

Stop laughing everyone: Let's see how that goes!!

On 21/08/2022 16:00, DManzaluni wrote:
> I'm in the same boat: I haven't upgraded from Mojave because I like iPhoto and don't use an iPhone so I dont like Photos. Also, I use Fusion so I dont want to update to APFS.
>
> But my MBP may have just died and Ihave been told that an insurance company is going to pay for a new computer
>
> So I will be doing a full system restore of Mojave onto a 2022 MBP!
>
> Stop laughing everyone: Let's see how that goes!!
>
If it's a 2022 then it probably won't go at all.

What would prevent a full system restore? It wouldn't give me a "different model" error message for restoration of an EARLIER OS, would it?

On 21/08/2022 16:15, DManzaluni wrote:
> What would prevent a full system restore? It wouldn't give me a "different model" error message for restoration of an EARLIER OS, would it?
>
AFAIK the 2022 (5th generation) needs Monterey or later.

> > What would prevent a full system restore? It wouldn't give me a "different model" error message for restoration of an EARLIER OS, would it?
> >
> AFAIK the 2022 (5th generation) needs Monterey or later.

I can't imagine many people have tried it but sounds like a severe case of "Uh-Oh1" I'll have to find out if Fusion works with APFS yet and if there is any alternative to iPhoto. Or if they have yet upgraded Photos so that it has the functionality of iPhoto or if Photos is still quite as klunky as it was when I first tried it?

In point of fact,Lots of Apple reps to whom I have spoken say that users have very often stayed with Mojave for my reasons.

In article <0ca6bf63-679a-4540-8220-bebd12d2b5b2n@googlegroups.com>,
DManzaluni <dmanzaluni@gmail.com> wrote:

>
> I can't imagine many people have tried it but sounds like a severe case of
> "Uh-Oh1" I'll have to find out if Fusion works with APFS yet

it does

> and if there is
> any alternative to iPhoto.

photos, which is a much better app. there are also third party options,
such as lightroom.

> > and if there is
> > any alternative to iPhoto.
> photos, which is a much better app. there are also third party options,
> such as lightroom.

E.G. When I tried Photos, I found it very difficult to search amongst tens of thousands of pics. In iPhoto, you hover above an event to see all the pics in it. I couldnt do this search in Photos.

DManzaluni <dmanzaluni@gmail.com> wrote:
> What would prevent a full system restore? It wouldn't give me a
> "different model" error message for restoration of an EARLIER OS, would
> it?

Mojave runs on Intel Macs, a 2022 Mac is likely to be Apple Silicon.
*Everything* is different.

In general Macs won't work with any OS older than the one they were first
shipped with.

You might be able to copy the Photos app and try to run it on Monterey under
Rosetta, but I'm not sure how much it depends on other stuff in the OS.

The other option is to run the old OS in a virtual machine, for those apps
you can't run natively.

Theo

Thanks for that Theo. It hadnt occurred to me that it would make any difference with an OLDER version.
But I can see that you are right.

It also hadnt occurred tome to run a MacOS in a VM on a mac.

If I can get Fusion to work, it doesnt sound so daunting!

On 21/08/2022 22:50, Theo wrote:
> DManzaluni <dmanzaluni@gmail.com> wrote:
>> What would prevent a full system restore? It wouldn't give me a
>> "different model" error message for restoration of an EARLIER OS, would
>> it?
>
> Mojave runs on Intel Macs, a 2022 Mac is likely to be Apple Silicon.
> *Everything* is different.
>
> In general Macs won't work with any OS older than the one they were first
> shipped with.
>
> You might be able to copy the Photos app and try to run it on Monterey under
> Rosetta, but I'm not sure how much it depends on other stuff in the OS.
>
You can't. The icon shows the "No Entry" sign.

> The other option is to run the old OS in a virtual machine, for those apps
> you can't run natively.
>
> Theo
>

On 22/08/2022 06:50, David Kennedy wrote:
> On 21/08/2022 22:50, Theo wrote:
>> DManzaluni <dmanzaluni@gmail.com> wrote:
>>> What would prevent a full system restore?  It wouldn't give me a
>>> "different model" error message for restoration of an EARLIER OS, would
>>> it?
>>
>> Mojave runs on Intel Macs, a 2022 Mac is likely to be Apple Silicon.
>> *Everything* is different.
>>
>> In general Macs won't work with any OS older than the one they were first
>> shipped with.
>>
>> You might be able to copy the Photos app and try to run it on Monterey under
>> Rosetta, but I'm not sure how much it depends on other stuff in the OS.
>>
> You can't. The icon shows the "No Entry" sign.
>
>> The other option is to run the old OS in a virtual machine, for those apps

Sorry, I miss parsed that as "under Monterey"

Theo <theom+news@chiark.greenend.org.uk> wrote:
> DManzaluni <dmanzaluni@gmail.com> wrote:
>> What would prevent a full system restore? It wouldn't give me a
>> "different model" error message for restoration of an EARLIER OS, would
>> it?
>
> Mojave runs on Intel Macs, a 2022 Mac is likely to be Apple Silicon.
> *Everything* is different.
>
> In general Macs won't work with any OS older than the one they were first
> shipped with.
>
> You might be able to copy the Photos app and try to run it on Monterey under
> Rosetta, but I'm not sure how much it depends on other stuff in the OS.
>
> The other option is to run the old OS in a virtual machine, for those apps
> you can't run natively.

From what I’ve read, it might be possible to run Mojave as a VM using UTM
on a Silicon Mac but clearly it would run - probably unacceptably - slow as
it will be using Intel processor emulation.

--
Cheers, Alan

David Kennedy <davidkennedygm@gmail.com> wrote:
> On 22/08/2022 06:50, David Kennedy wrote:
> > On 21/08/2022 22:50, Theo wrote:
> >> You might be able to copy the Photos app and try to run it on Monterey
> >> under Rosetta, but I'm not sure how much it depends on other stuff in
> >> the OS.
> >>
> > You can't. The icon shows the "No Entry" sign.
> >
> >> The other option is to run the old OS in a virtual machine, for those
> >> apps
>
> Sorry, I miss parsed that as "under Monterey"

I wonder if iPhoto (what I meant instead of Photos) is a 32 bit Intel app?
Which might explain the lack of operation under Monterey, even on Intel
Macs? Apparently 'no entry' is also caused by incorrect permissions.

You should be able to run it in a Mojave VM anyway. I've been running x86
Linux VMs under UTM on M1 and it's 'ok'. Performance is not good when
you need to do lots of compute, but when you just want to do light things
it's usable.

Theo

DManzaluni <dmanzaluni@gmail.com> wrote:
> Thanks for that Theo. It hadnt occurred to me that it would make any
> difference with an OLDER version. But I can see that you are right.
>
> It also hadnt occurred tome to run a MacOS in a VM on a mac.
>
> If I can get Fusion to work, it doesnt sound so daunting!

Why do you want a Fusion drive, on a machine with an internal SSD? I don't
think any Apple Silicon Macs have HDD.

I'm not sure you can install MacOS on HFS+ any more, but I can't see why you
would want to.

Possibly if you were booting from an external HDD performance might suffer
on APFS, but I really wouldn't recommend that. An external HDD for data
using HFS+ is fine.

(I assume your comments about avoiding APFS and using Fusion refer to the
'Fusion drive' concept, not VMWare Fusion virtual machines)

Theo

> (I assume your comments about avoiding APFS and using Fusion refer to the
> 'Fusion drive' concept, not VMWare Fusion virtual machines)
>
> Theo

Actually no! I meant VMWare Fusion Not sure what fusion drive is but I suppose I'll now need to see how VMWare runs under an M1 chip, if that's what I am getting.

DManzaluni <dmanzaluni@gmail.com> wrote:
>
>> (I assume your comments about avoiding APFS and using Fusion refer to the
>> 'Fusion drive' concept, not VMWare Fusion virtual machines)
>>
>> Theo
>
>
> Actually no! I meant VMWare Fusion Not sure what fusion drive is but I
> suppose I'll now need to see how VMWare runs under an M1 chip, if that's
> what I am getting.

It’s still a work in progress. You would be better off with UTM (QEMU+) or
if you want to spend some money Parallels runs very well on M1 Macs.

--
Cheers, Alan