Today I am learning how to do a SPA (Single Page Application). So I can recreate the Comic Details editor page, which I previously did with old school frames aka HTML4 and HTML 3 tech. HTML5 has phased frames out so we have to use other methods to make this work. This will require a bit of thinking, javascript which I really hate, but I will manage. I want to keep this as simple as possible so I can work on updating this website. I do not like using stupid amounts of javascript code to do simple tasks. We shall see how far I get with this. At least according to the MS documentation I am seeing, they support a few options out of the box (1) Vue, (2) React, (3) Angular, (4) Blazor. Vue, React, Angular need proxies for the a static component. Blazor my current understanding compiles stuff into the necessary javascript, bypassing the need for a proxie layer for javascript stuff. But the downside to Balzor it keeps a connection open to the webserver. This is not a deal killer as I do not expect anyone but myself to be doing any editing of the website. But what bugs me is all the new html5 stuff is so complicated and requires soo much javascript for simple stuff, and moved away from the normal every man HTML versions 1 to 4 was designed for its no longer funny. I still might to a 1.0 alpha without Blazor and just break up the comic edit page into smaller chunks, just to keep things moving smoothly, and not get too slogged down in the rebuild at this stage.
I will still have records of all the comic books I own, but this website will move into just being a general comic Informational website. I am thinking of the pro/cons of redoing all the images I have of the comic books. I still have the originals so it will just take time if I am going to reupload them for each comic. Or I can just reuse the originals I uploaded almost 10 years ago. Either way I have to restruture the image folder so its not dumped into one folder anymore. It resulted in a folder with 3 images per cover uploaded times how many images I uploaded. This many files in a folder made browsing this folder slow especially in newer MS Operating systems whcih tried to thumbnail all the images. I might not put file name extention's on them to prevent the thumbnail issue. I am thinking of putting each size in a sub folder. So I am thinking of a structure of "APP_Data\{Title ID}\{Size}\{Image ID}", with this strucuture I should be able to figure out what the images are for which Title easy enough. I don't want to create too many sub folders to kill the OS with mixing DB stuff with folders. This should make backing up the images easier as well.
Thats all for today.