Picasa Replacement Project - Update 2 - Initial Working Parser

It's taken a few more days than originally planned, but I've just reached a first concrete milestone:

The rudimentary parser for Picasa.ini settings file is now able to fully parse the settings file for the test folder I chose from my collection!   (Albeit, this was one of the newer ones that I haven't applied as heavy edits on as some of those in the full collection... but it's still a starting point!)

There's lots more to do still to make it actually useful, including:
* 1) Set up a Git repo for this project, so it can be used by others  

EDIT:   The code can be found here            https://github.com/Aligorith/picasa_lib_utils 

* 2) Need to unpack how a handful of other filters I've sometimes used on other photos have their parameters done too

* 3) Figure out what the pixel-level operations some of these were actually doing (i.e. most critical is the "finetune2" filter though that is the hardest; but even something like the "tilt" filter will need translating into a concrete rotation angle)

Late night musings on Pixar's relative "downfall" in recent years...

What follows are a bunch of late night ramblings + musings about things I can't help wondering after seeing seeing a YT rabbithole analysing the relative downfall of Pixar in the last few years...

 

(Disclaimer:  As some of the topics here are apparently contentious, I will be moderating any comments on this post heavily as I see fit... you have been warned) 

Picasa Replacement Project - Day 1 Status Report

Following Monday's incident, I have decided to urgently bring forward + accelerate my plans to start developing a replacement solution to my Picasa-based Photo Management workflow. As this incident had highlighted, I do somewhat urgently need to find a reliable automated solution to migrate my almost 2 decade library of non-destructive edits over to a future-proof solution I fully control!

As a result, I made a bunch of promising progress on my Picasa Reverse Engineering project last night - i.e. the first night of a new journey!

Fixing Picasa3 suddenly freezing on Windows10 (July 2025)

This evening, Picasa suddenly started freezing on Windows 10 here.  (Yes, it has been officially discontinued for years now... but for my workflow, it is still much better than many of the alternatives I've tried, and so, until I manage to get my own self-built alternative up and running, I'm continuing to use it...)

After a whole bunch of sleuthing (including deleting my old DB and rebuilding it, in case of some database corruption there), it turns out that the culprit was Windows Defender!

TLDR:  To fix this, add an exclusion for the following setting (i.e. "Block Untrusted Fonts") for Picasa3.exe 

EDIT:  Posted too soon!  While doing that gets things moving a little at least, a few seconds later, after letting you scroll, it will again lock up, while it now starts another batch of CPU activity.  Doh!   (Trying again with disabling a whole lot more to see what sticks...)

EDIT 2: Tried a bunch more stuff, but annoyingly each "fix" only seems to last about 5 seconds before Windows Defender catches on and locks down even harder!

Things that didn't go down well:

* Going through disabling *every* checkbox in that infernal program-settings-override dialog.  Doing that just makes it worse it seems!

* Switching "Compatability Mode" to "Windows 8" - This worked for about 5 seconds (i.e. longer than when just doing "open + scroll" tests, but still it locked right up!

Ultimately, after an hour of testing this crap, I'm going have to call it a night on this here, and have ended up filing a bugreport with MS about this... hopefully they do resolve it!  Gah!

(PS:  The project to again try to migrate my personal workstation to Linux ahead of October just got another massive boost again tonight!)

A Piece of Old Christchurch History - First "Jade Garden" Location

Many people know this old building as the old "Canterbury Public Library" building

For me, this was and always will be: "The Original Home of 'Jade Garden' - Dim Sum Chinese Restaurant"  (although apparently, they may have been in one other location before this one IIRC)

 

I was inspired to write this little oral history down for posterity when stumbling across the photo below earlier today (complete with the caption that showed below it). It was one of the first times I'd come across a decent photo of the place, so thought it was a good chance to write this down. 

Canterbury Public Library 19 December 1981. Exterior of the former Canterbury Public Library building on the corner of Cambridge Terrace and Hereford Street. Christchurch Star archive photo

(NOTE: Once again, am reposting this long-form post from my Mastodon for archiving - though this probably means the AI's will now ingest this too... sigh)

WhioDoc Updates - Version 1.1 just released

I've just released a minor update to WhioDoc to add some clarity + tweaks around the formatting of range-specifiers, and guidance on how "complex type specifiers" should be documented (i.e. "there is no established standard here yet, as you're probably doing something wrong if you need it")

 

Links to WhioDoc Repo:

* The Repo:  https://github.com/Aligorith/whiodoc

* Today's Updates:   

    https://github.com/Aligorith/whiodoc/commit/66aba8762073eabd948872e149323f17584a2b87

 

Key Points:

* Changed the delimiter for "type vs range" parts of the range-specifiers to use "::" instead of "-" 

   This has been changed after I realised on my current project that the "-" is really not too visible in my text editor (where I usually have "show all whitespace" enabled now - long story for another day), and a more heavy-weight symbol was needed.

  i.e. The recommended format is now something like:

         (Num :: 0.1 <= v < 0.9)

 

In other news:

The lack of news / updates here recently is because I'm currently hard at work on a bunch of projects, with a view towards getting some of them in a shippable state. And with that, I need to get back to actually building stuff, and less time talking about building it!  Over and out!

Blast from the Past: Cathay Pacific 747 Cardboard Model Plane / Glider

When doing some long overdue cleaning of one of our bookshelves yesterday, I ran into the following fun little guy:

IIRC, it's a Cathay Pacific 747 cardboard plane model from a Meadow Fresh milk-carton promotion here in NZ. It would have been from the mid-late 90's (as it uses the "brush tick" tail).

(At least that's what I think it's from! I could be wrong, with it potentially having come from an in-flight activities pack for kids instead, since I do have a few of those... somewhere...)

 

Thoughts on Windows 11's "Recall" Feature

Seeing one of the latest threads this morning about Win11's Recall feature, I'm not surprised that it does what it does TBH

Some of these points overlap with comments I made earlier when news of this feature first broke. I can't easily find those now, but if/when I do, I may amend this post with those notes as well, as they better cover a bunch of other insights I don't think I've captured here as well.

 

EDIT:  Cool, according to this Ars article, they do seem to have put in place most of the reasonable safeguards I'd expect / recommend them to have.

PureQML Followup - Initial Code Audit Notes

Following on my previous post, I did some more poking around the PureQML code as an initial stage towards vetting whether it is a suitable and/or trustworthy codebase to build any projects with.

Here are some observations I've made regarding things I'd want to fork + hack the codebase to do before I did anything more serious with it. I thought I'd post these here in case I lost the file I kept these notes in when I came back to try to work on this later (and also for anyone else considering using this)

DISCLAIMER:  I still don't know all that much about this project, so some of these may be able to be fully disabled + fixed in ways that I haven't found yet.

 

EDIT 2025/04/25:

* Have forked the pureqml/qmlcore repo with these changes to

    https://github.com/Aligorith/pureqml_qmlcore/tree/PureQML-Clean

* Added "Issue 5" below

 

On Approaching Composition Line-By-Line (i.e. Per Voice) vs Vertically (i.e. Chord Progressions)

Just saw a very interesting video looking at music theory / analysis at a different way than "chord chord chord chord chord" (to paraphrase the video) 😜

Instead, this video argues that we should be focussing more on the horizontal movements of the parts (i.e. "voice leading"), which thus helps draw your attention towards the flow / journey of the piece more...

Link: "Inside the Score - Most musicians learn harmony wrong"

https://www.youtube.com/watch?v=SJYj57TUKj

 

MediaSlurper Updates - Ep2 - Introducing a basic GUI + Cute Mascot

Time for another (hopefully) quick + brief writeup following another busy but relatively successful weekend of hacking away on this project. In short: I managed to tick off the biggest todo I had planned for the weekend (along with a few other smaller tasks), and with a few additional bonus points for good measure.

Introducing, the initial MVP UI for "MediaSlurper"

1) MediaSlurper  MVP GUI

Perhaps the biggest achievement this weekend was managing to put together an initial functioning UI for the media-backup scripts I've been working on for the past few weeks (see screenshot above).

Functionally, it's still very very crude (i.e. those buttons just call the existing scripts, but then they just execute in that existing terminal window backing this GUI (instead of in a dedicated GUI-wrapped window, OR via nicer GUI-driven UI's). But, most importantly, it serves the original goal of implementing this GUI in the first place (i.e. allowing me to launch these tools in ~2 clicks from the Start Menu, without needing to keep open a dedicated terminal window with 2 tabs - one for each script - open so that I can run them on the near daily / every-other-day basis that I end up needing these)

PureQml's Python-based QML Compiler - A tempting starting point for Kea's UI-Definition Compiler...

I know I already have too many open / unfinished projects (and a bunch more un-started yet)...

BUT, I was "doing the rounds" again after work today on HTML/CSS alternatives to doing web-deployable apps, and ended up looking at the QML situation again...

(Unfortunately, while I'll try to finish current project using HaxeUI, I'm running into too many weird update bugs + other hard-to-overcome limitations that I'm currently inclined to go back to looking for another solution for the next test project / whatever will be used to implement Parus)

 

TLDR:  Am again getting itchy hands to jump back into building my "Kea" language compiler in Python (possibly either hacking OR deriving significant inspiration from "PureQml"'s Python-based "QML-subset -> HTMl5 / Javascript" compiler), but focussing first on the QML-like UI-definition syntax   (before adapting the wider language later, and for non-web backends for those other parts)...