I'm not joking, that's a verbatim quote: (at 0:51) https://t.co/5F6JwTTqXU

Day 271 / #365DaysOfCode 8.2.23 #buildinpublic | Formlogic Today I continued to deconstruct my form builder page in order to simplify and isolate my template loading issue. #100DaysOfCode

Day 279 / #365DaysOfCode 8.16.23 #buildinpublic | Formlogic Continuing work on the iframe zoom buttons. #100DaysOfCode

Day 270 / #365DaysOfCode 7.31.23 #buildinpublic | Formlogic Today I began to deconstruct my form builder page in order to simplify and isolate my template loading issue. I made a copy of the page & routes for so I could leave the original in place. #100DaysOfCode

Day 269 / #365DaysOfCode 7.29.23 #buildinpublic | Formlogic Ever since I modified the form builder to load files dynamically rather than the static test, I have been in error hell. I am going to adjust my approach, make a simple copy of the page & rebuild fresh #100DaysOfCode

Day 276 / #365DaysOfCode 8.8.23 #buildinpublic | Formlogic Post 2 Solved the debugging issue w/ my second carousel menu, which is responsible for loading user projects into the editor. This took several days to complete w/my work schedule. Keep on grinding!⚙️🔨 #100DaysOfCode

Day 285 / #365DaysOfCode 8.24.23 #buildinpublic | Formlogic Fixed the menu loading arrows, moved on to reconstructing the code editing window #100DaysOfCode

Day 272 / #365DaysOfCode 8.3.23 #buildinpublic | Formlogic Still deconstructing my form builder to isolate my template loading issue. #100DaysOfCode

Day 277 / #365DaysOfCode 8.9.23 #buildinpublic | Formlogic Began reconstructing the form editor & tools. Started with the zoom buttons, hopefully I can finish these on my lunch break. #100DaysOfCode

Day 278 / #365DaysOfCode 8.15.23 #buildinpublic | Formlogic Continuing the reconstructing the form editor & tools. The previous function for iframe zoom buttons no longer works and needs to be updated. #100DaysOfCode

Day 282 / #365DaysOfCode 8.21.23 #buildinpublic | Formlogic Repairing zoom capacity for my templates by isolating the issue. The problem was the use of "body::before {}" CSS that I had previously used to flip my background image. #100DaysOfCode

Day 283 / #365DaysOfCode 8.22.23 #buildinpublic | Formlogic Triggering puppeteer screenshots of saved or freshly loaded html projects so we can see them in the menu. Task Complete! That was a pretty efficient prompt lol🤣 #100DaysOfCode

Day 284 / #365DaysOfCode 8.23.23 #buildinpublic | Formlogic Working on the "my Projects" carousel menu arrows that load the next 6 images/links/screenshots into the carousel. The carousel is cool but, I will probably pivot to a grid/list menu as the default. #100DaysOfCode

@matthewachang @jack_watson_hfw At Formlogic we could keep the machines running 24/7 doing high-mix aerospace parts, but onboarding new SKUs, inspection, and compliance paperwork were powered by humans and middle managers. That’s what AI can streamline

Day 276 / #365DaysOfCode 8.8.23 #buildinpublic | Formlogic Continuing the debugging for my second carousel menu, which is responsible for loading user projects into the editor. #100DaysOfCode

Day 280 / #365DaysOfCode 8.17.23 #buildinpublic | Formlogic Still working on the iframe zoom buttons. I will probably return to this after making the content editable and see if that changes how the zoom feature functions. #100DaysOfCode

Day 281 / #365DaysOfCode 8.18.23 #buildinpublic | Formlogic iframe zoom buttons are restored. I was going to return to this after making the content editable, but I had a realization that the issue was in my example html files not the zoom function itself. #100DaysOfCode

Day 283 / #365DaysOfCode 8.22.23 #buildinpublic | Formlogic I cont. tweaking the iframe zoom feature. I think it's time to move on to the next task, which is triggering puppeteer screenshots of saved or freshly loaded html projects so we can see them in the menu. #100DaysOfCode

Day 273 / #365DaysOfCode 8.4.23 #buildinpublic | Formlogic I have isolated the problem w/ loading templates into the iframe where i do my editing, well there are a few problems. Solution: separate out what I can from within the page route into endpoints... #100DaysOfCode