JDunk
4.2K posts
@4JDunk
Club-74 - owner of all 74 Otherside resources! 🌌 “Any sufficiently advanced technology is indistinguishable from magic."
My dear front-end developers (and anyone who’s interested in the future of interfaces): I have crawled through depths of hell to bring you, for the foreseeable years, one of the more important foundational pieces of UI engineering (if not in implementation then certainly at least in concept): Fast, accurate and comprehensive userland text measurement algorithm in pure TypeScript, usable for laying out entire web pages without CSS, bypassing DOM measurements and reflow
🚨EVERY CHAMPION NEEDS A STEED🚨 All Flingers have been updated for the days events! Our Champion @agentbye has been gifted a special Pirate-King Flinger to help him on his Trial. Stay tuned, this will be one for the ages! FlingIt! <3
Proof of MML! ➡️All the Worlds a Stage! Some light reading for you with some things to keep in mind. "Make it work now, make it good later." ☕️ Late Tuesday night I was looking back at some of my favorite games and BETHESDA Elder Scrolls Series truly stands out to me. You could interact with every item. I can't tell you how much time I spent in Oblivion at Arcane University just picking up books to learn spells or others just for reading. Par for the course if you wanted to find and learn the best spells as a mage. I woke up Wednesday and attacked the AI on how to accomplish this in MML editor. We fiddled with MML trained it on the docs but couldn't get anything to load... until we did. Two days and 36 plays later.... they're ready to deploy for virtual worlds. 💥 A few things we discovered in making this work: 💥The text looks somewhat unreadable, but keep in mind this is a compressed video and the MML Editor is showing us 1/8th of the screen. You will be able to read this in your virtual world. 💥AI helped to design the spines for the books like some off-shoot publisher giving it a new style. Blood Red for tragedies, Grass Green for Comedies, Royal Blue for Tragedies. Time Written shows the progression of grid fill in. IDK seems cool! 💥MML is limited to one type of font, so if you want to stylize your text you'll need to resort to an image converter and bake the pages into textures individually. 💥In order for pages to load, Claude AI built a text parser which converts .txt files to images. It also takes direction on Font, Page Numbers, where to place the title / act / scene, highlights character names, etc. I simply shared the .txt and it did the rest. 💥You can use an invisible cube over the book spine to act as the trigger for opening it. When the player clicks this it fetches all pages and loads the book UI. 💥In the book design for Shakespeare we loaded 5 Acts each since all of his works were in 5 Acts and built in logic which highlights the ACT you're currently on not only on the page but in the book UI. 💥Claude AI also loaded the code into a manifest which broke down each book by scene / act etc. which linked to the act or page turning in the book UI. You click on Act III, it navigates to the page with ACT III content. You flip the last page in ACT III, it moves to ACT IV. 💥You can load an unbelievable amount of content into one of these books. I loaded each of Shakespeare's plays as individual books. It felt like a good starting challenge because there were so many but also they are all in public domain. There are few that remain to be completed outside the cannon. For now, 36 of William Shakespeare's plays including all tragedies, comedies, and histories are complete. [{ "ROMEO & JULIET" }] is published to the explore page and will be refined over time. Yeah - "its a book that opens" but it's also loading this stuff in real time. Its loading the ENTIRE work, but not in {mFrame} which can take down a world. It makes the world feel much richer. This is the first of many steps. Next step a book tome that summons goblinz? lolllz
When I built menugen ~1 year ago, I observed that the hardest part by far was not the code itself, it was the plethora of services you have to assemble like IKEA furniture to make it real, the DevOps: services, payments, auth, database, security, domain names, etc... I am really looking forward to a day where I could simply tell my agent: "build menugen" (referencing the post) and it would just work. The whole thing up to the deployed web page. The agent would have to browse a number of services, read the docs, get all the api keys, make everything work, debug it in dev, and deploy to prod. This is the actually hard part, not the code itself. Or rather, the better way to think about it is that the entire DevOps lifecycle has to become code, in addition to the necessary sensors/actuators of the CLIs/APIs with agent-native ergonomics. And there should be no need to visit web pages, click buttons, or anything like that for the human. It's easy to state, it's now just barely technically possible and expected to work maybe, but it definitely requires from-scratch re-design, work and thought. Very exciting direction!
He can smell your fear... He’s got a scent for vengeance... HE NOSE SOMETHING!
