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)

PhotoTool Project Updates Ep 1 - Initial Steps Towards Scripts to Ease + Automate Import + Backup of Media Data

For the past few weeks, I've been having a blast hacking away at a pair of scripts for automating some steps of my current photo management workflow that have thus-far been very labour-intensive to perform:  Namely, importing/backing up photos and videos from my camera (R5)'s memory card, and doing the same with my phone (Android).

Trip Down Memory Lane + Resurrecting An Old Project

I know it's technically a "work night", but I just went through my drawer trying to dig out my ancient mockups for a project I've recently revived.

I had originally built it as a thing for Dad to use for outreach activities - Back in the day (i.e. back in 2009, from the comments in the source code I've been porting between machines), I'd managed to get the core engine running, but ultimately ran out of time (+ also, a suitable distribution tech stack back in the day), so had ultimately abandoned that project.

Anyway, recently I've been resurrecting it as a motivating toy app to play with Haxe + HaxeUI. 

 

* This seemed like the perfect project for learning this stack + playing around with it. It was a relatively simple + straightforward little piece of tech that is small enough to be easily implementable / portable (i.e. within constraints of what I can safely manage energy-wise + time-wise on top of long days of fulltime 9-5 weekday job commitments). 

* It was also an almost perfect case for this tech stack (i.e. the HTML5 deployment option is particularly attractive for someone who has never been able to get CSS layouts + Javascript coding to really sit well with my worldview).

 

In other words, this was the PERFECT type of small toy project to tinker around with during the evenings now, as I try to re-establish a small pipeline for me to get a bunch of small fun projects done for myself, where I have full + complete control over every aspect. No questions asked. No input from third parties accepted or needed. 100% owned by me, and for the sole purpose of me having a creative outlet to do fun stuff for myself.