MythicDungeonTools VS turbo

Mapping changes: * Neltharion's Lair mapping updated (see https://github.com/Nnoggie/MythicDungeonTools/issues/465). Bugfixes: * [\#1739](https://github.com/Wotuu/keystone.guru/issues/1739) When new affixes are added, a hard-reload is no longer required to fetch the latest affixes image. If you didn't do this you'd see the wrong images for the affixes until you did.

This question arose when I tried cloning an addon's github repo in hopes of contributing to it. But I quickly realized it won't run as-is because the libraries aren't part of the repo. Next I tried downloading those libraries and putting them in my AddOns folder, but I still see UI errors because the addon's xml file is attempting to load those libraries from a relative path. If it helps, the particular addon I was attempting this with is https://github.com/Nnoggie/MythicDungeonTools/tree/master/libs Strangely, this addon's repo does include a copy of LibDeflate, but not any of the other libraries it's trying to include from load_libs.xml. So clearly I'm missing something about how addon devs handle dependencies during the actual development.

If you find any wrongly placed npcs or bugs you can report them on GitHub or in Discord.

You can find a full list of changes here.

this release is with data https://github.com/Nnoggie/MythicDungeonTools/releases/tag/v3.3.4 If you still want to user this over ManbabyDungeonTools, which are superior by name.

I also recommend checking out the docs for Stimulus and Turbo to familiarise yourself with all their features and the APIs used in this series.

https://github.com/hotwired/turbo

Turbo 8 remove typescript without using JSDOC

Experiment using Turbo to drive front-end behavior: "Turbo 7.2.0 (currently in beta) allows you to define your own Stream actions which can be any JS code you want. By combining a custom Stream action or two with web components, you can essentially drive reactive frontend behavior from the backend stupidly easily. Loooove it! 😍 […] For a turnkey example, you could check out https://github.com/hopsoft/turbo_ready " —Jared White on The Spicy Web Discord

This handles disconnection (as could be done by any destructive change to the DOM, like navigating with Turbo or htmx, I'm not even talking about using the element in a JavaScript-heavy web app) but not reconnection though, and we've exited early from the connectedCallback to avoid initializing the element twice, so this change actually broke our component in these situations where it's moved around, or stashed and then reinserted. To fix that, we need to always call addSparkles in connectedCallback, so move all the rest into an if, that's actually as simple as that… except that when the user prefers reduced motion, sparkles are never removed, so they keep piling in each time the element is connected again. One way to handle that, without introducing our housekeeping of individual timers, is to just remove all sparkles on disconnection. Either that or conditionally add them in connectedCallback if either we're initializing the element (including attaching the shadow DOM) or the user doesn't prefer reduced motion. The difference between both approaches is in whether we want the small animation when the sparkles appear (and appearing at new random locations). I went with the latter.

If you think you have seen enough Rails magic, you are mistaken my friend. Rails have a new trick up its sleeve: Hotwire. And with the magical Turbo tool that comes with it, you can create modern, interactive web applications with minimal, or sometimes no JavaScript at all, providing users with an incredibly smooth experience.

There is also Turbo and the frameworks who adopt them, Ruby on Rails, PHP Symphony and possibly others that solves the same issue in the same manner as HTMX. And the choice for HTMX is only a personal taste in this, but you should definitely learn about this, this is as cool as HTMX!

Most controversially, the Turbo framework dropped TypeScript support altogether after assessing that strong typing was the culprit behind poor developer experience.

Turbo[0] has been solving this for years. Quite the contrary, front-end frameworks have started to think "sending JSON is good, but actually sending HTML could be great!".

DHH's presentation[1] during Rails World 2023 is quite interesting in that regard, I recommend you give it a go (start around minute 16). I am actually very excited with his vision of the web.

[0] https://turbo.hotwired.dev/