## Bugs Fixed
- The gallery gradually populates with pictures to avoid lag.
- Added manual re-connect buttons to recover if lagging breask the connection between the main program and the background tasker program.
- Widened the tasker to make debug messages easier to read.
## Bugs Fixed
- Keyboard search was not working right.
- Program would not quit if fav_pictures.json is missing.
- Was not reading any .URL file that was dragged in with a picture.
That said... what it currently does is oddly specific. It copies pictures and videos into a folder and creates thumbnails for them, then it adds their filenames to a JSON file, and then runs a CMD script when you close the program. What you put in there is up to you but only programmers know how to use that stuff... I should probably figure out a simple way to spit out an HTML file that other people can just directly use on their websites.
I decided to keep the Netscape throbber as a busy indicator because it was fun. The retro computer style became kind of a running theme.
To check for lag I added a Netscape throbber animation in the corner of both programs. Fun fact: This was the original purpose of browser animations. They helped you figure out if your Windows 98 computer had silently crashed and frozen up in the middle of loading a web page for 10 minutes on dial-up internet. If it was animating that meant the computer was still working.
[ffprobe.exe](https://ffmpeg.org/ffprobe.html)
: This program measures the width and height of pictures and videos. It can also read other information. It's part of the ffmpeg project.
[pngquant.exe](http://pngquant.org/)
: This program compresses PNG files into 256 colors with a full alpha channel. They're sometimes just as small as JPG files. Amazingly good for losslessly compressing pixel art. Created by [Greg Roelofs](http://www.gregroelofs.com/), [Jef Poskanzer](http://www.acme.com/jef/), [Kornel Lesiński](https://kornel.ski/about).
It's kind of ironic because this program relies on a bunch of DOS command-line programs that other people made to convert files and read metadata. But those are programs written by programmers for other programmers. Normal people need buttons to click on or these things will go to waste. So... what are these magical programs?
[convert.exe](https://legacy.imagemagick.org/script/download.php)
: This program converts pictures into other file formats. It comes with ImageMagick. Created by [Cristy, Dirk Lemstra, and Fred Weinhaus](https://github.com/sponsors/ImageMagick?o=esb).
[exiftool.exe](https://exiftool.org/)
: This program reads and writes metadata information embedded inside of files, such as the author name, website, keywords, and copyright info. Created by Phil Harvey.
[ffmpeg.exe](https://ffmpeg.org/)
: This program creates and converts video files. Created by a [whole bunch of people](https://ffmpeg.org/consulting.html).
🧪 **Experiment 5:** A settings editor. Nobody on Earth ever wants to edit a program's settings by hand using a text file. Nobody wants to waste time looking up what all my little words mean or how to get all the commas and quotation marks exactly right. And my pride won't let me settle for that. The original Macintosh proved that it is possible for all settings to be 100% graphical. Every program made after 1984 should always do this. There's no excuse. We figured it out. The problem is solved. I don't care how much work it takes because it's objectively the correct thing to do. It took me about 2 days to add a settings editor to my program at the very end, which isn't that long.
... aaaaaand then after building all these things, I discovered that Flash *already* has a built-in system for handling pop-up windows. Heck it even has an "Alert" window that does almost exactly the same thing as the one I created. So I adjusted my code to use Flash's official system and it was... still a little janky. But it works either way.
🧪 **Experiment 4:** I also needed pop-up dialog windows to ask questions such as whether to replace a picture. I also needed a way to display the settings editor on top of everything in a way that blocks people from clicking buttons underneath. You take it for granted but something has to *cause* that to happen. One way to do this in Flash is to overlap everything with a giant transparent MovieClip with an onPress() reaction that eats mouse clicks. But my gallery manually detects mouse-clicks directly from the Mouse system, so I also programmed it to react to windows and drop-down menus being opened and closed so that it can deactivate itself. The question pop-up needed to display a message, an icon, Yes and No buttons, a way to report which button was clicked, and have a close button for cancelling *(in case the user isn't sure what to choose)*
So I need to create temporary placeholder thumbnails. Ideally each with a progress bar showing that picture's progress. And also figure out how to send status updates to those thumbnails as tasks get completed. There's nothing more annoying than telling a program to do something and then seeing absolutely nothing happen. You need feedback or it feels like the program is broken. Besides, I enjoyed the puzzle of figuring out how to append promises to an existing array of promises and continue waiting for that entire list of asynchronous tasks to finish, so that I can drop additional pictures into the program while it's in the middle of processing other pictures. A good program doesn't force you to wait until it's done.
🧪 **Experiment 3:** Processing multiple files at the same time. I don't just mean dragging in multiple pictures at once. Each one takes awhile to generate the thumbnail file, check the compression to figure out the ideal file format, read EXIF metadata, cross-reference the artist folder to get the website URL for known artists, etc...
🧪 **Experiment 2:** A resizable window. A folder in Windows can be resized. This is convenient. Can a Flash program somehow adjust itself when you resize it? Yes it turns it can, but... it's weird. It doesn't expand to the right and down like you would expect. Instead Flash moves your animation so that it's *centered* inside the window when you resize it. This turns out to be very annoying, because now your animation or program won't fill the window. Instead you will have all this blank space in the upper left because Flash moved everything away from that corner. This can be fixed with a bit to math to manually figure out where the new center of the window is, how big the window is, and where to move your stuff to reach the top-left corner again. But it was annoying.
But then I remembered an obscure Flash feature called "Local Connection" which allows Flash animations to directly talk to each other. And if I make 2 connections, I can have two-way communication between the programs. So sending a task can later send back a result for that task. But this demands that the first program remain mostly lag-free or messages might be dropped. Which is actually fine, because that was already one of my main goals. The second hidden program can lag as much as it wants as long as it can reliably receive a to-do list from the main graphical program whenever it asks for it. Besides a "local connection" will tolerate some lag up to about a second. And I could just request the to-do list again if the connection lags out and emits an error.
🧪 **Experiment 1:** The old program could only add one file at a time, and it lagged like crazy until it finished chewing on it. Not really a problem but it makes the experience of using it feel super janky. The solution? 2 programs! One to provide a smooth stutter-free user experience with graphical menus, and a second hidden program that does all the real work. I had never attempted something like this before. My original plan for this was to tell the second program what to do by saving little to-do files into a folder. These would be tiny text files that simply had the command and relevant information. Glorified function-calls. The second program would check the folder periodically, load files and do tasks at its own pace. That way this "task queue" could exist and be reliably accessible no matter how busy or laggy any programs were, because they would not be directly relying on each other.
Now any rational person would stop me right there and tell me to only create an easy solution to the actual problem and nothing more. Well too late! I'm actually writing this a whole month later and I already completed this fully armed and operational battle-station!
Because I wasn't just making this to solve a problem. And it wasn't purely for the sake of pride either. I had ideas for new experiments I wanted to try. And that's what truly motivated me.
Making something that resembles Windows turns out to be way more ambitious than you might assume. A folder is more than just a rectangle with pictures in it. It might look boring as hell but Windows is way more polished than you think. You can right-click and do things to the pictures. You can change the sorting order. There's a menu at the top to show new people all of the options that are possible. I'm making this program for the sake of convenience so I am going to add *every* convenience I can possibly think of. I don't need them. I just want them.
The original program was just a linear sequence of steps. I would need to start over to make anything more ambitious. But what should this new program look like? Ideally an image gallery editor would look like, well, an image gallery. And then I realized the answer was already staring me in the face. Windows! An image gallery is really just a folder full of pictures anyway. So the most intuitive experience is to just drag and drop pictures into a "folder" and have it mostly act the same way you expect Windows to act, but with the extra thumbnail-generation and list-making stuff happening automatically in the background.
Making these minor changes manually from time to time is no big deal. They're quick and simple. But it would be *nice* if my convenient program could make that stuff convenient too. Besides I just couldn't escape the nagging guilt that any program that requires you to text files by hand is, by definition, an incomplete program and a crappy experience for anybody who isn't the original programmer. I knew could do better, and my pride wasn't going to leave me alone until I did.
Well the thing is... that was the *only* thing it did. Sure I could drag and drop a picture onto that program and it would automagically add pictures to the website... one... at... a... time. But I was often running into situations where I wanted to modify pictures that were already added. Sometimes the program would make wrong guesses about which file format I wanted the pictures to be. **(For the love of god NEVER compress pixel-art with JPEG!!)**
I built an easy and convenient editor for my website's "favorite pictures" gallery. Actually I over-engineered the hell out of this thing. I was just having way too much fun! It supports pictures, videos, and animated GIF's.
In hindsight I should have been keeping a running log while I was making this, because I ended up spending a full month on this thing. That wasn't the plan, but time flies when you're having fun!
But what *was* the plan anyway? After all I had already finished making another program earlier that did the same thing. Easily adding pictures to the gallery. Why did I need another one?
