starbeam.one

.@StarbeamOne Daily Status* Current Story: v2 Data Migration: Product Display Notes: Work started on the Product Display story for Data Migration yesterday. I made a good deal of progress after spending some time with analysis to figure out the best path forward. We have five file types: image, video, text, book, and audio. Both images and videos already work exactly as desired. Which is convenient, as they are also the most popular file types. 😀 Audio does not have a visual file, and we prompt for a cover instead. That will also stay intact, but I need to review the experience and workflow. However, the text and book file types were generating "sample" files that should really be our preview files, and that is what I ended up doing yesterday. It actually wasn't all that involved, and I was able to route the behavior to the appropriate process with little effort. I was able to greatly simplify the interface, too, which was riddled with complicated code. All of that is gone now, and everything is much simpler. We still have some issues presenting a dialog to the user when adding "non-visual" elements, and I hope to address this today. #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `An epic feature shot deep of space, prominently featuring bold, bright, colorful, glowing, contrasting neon colors --ar 16:9`

.@StarbeamOne Daily Status* Current Story: v2 Data Migration - Product Display Notes: Alright, after a week of unexpected effort on quality assurance, I finally cracked open the New Publishing Wizard to resume work on implementing a good solution for Product Display -- only to be punched in the face by even more bugs. 😅 These were not terrible, but they were tricky, and ended up taking most of the day, unfortunately. I did a big refactor on how the wizard stores (and cascades) state to its children elements a few months ago, and that's what we're running into here. Despite the wrinkles, everything is working really well now. Our display refreshes are minor and expected now. In v1, our views/displays refresh terribly due to a few really bad bugs, mostly stemming from my misunderstanding of how Blazor rendering works. In v2, that's all been smoothed over, and our components refresh once or twice per action. So, that was good to at least see and verify. Now that those issues have been addressed, I can resume work on the Product Display and incorporate it. This is sort of an involved story, and I can see it taking the next week easily. It will impact how files are saved and categorized, particularly for file types that do not have a visual representation (e.g., audio). One foot in front of the other here... #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `An external shot of a futuristic space station in another universe made of shiny bright neon glowing metal, prominently featuring bright glowing contrasting neon colors, epic lighting, there may be a Dyson sphere nearby --ar 9:16`