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...)
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.
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
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
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.
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)
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)...
