JS Dev Tools about blitz HOT 1 CLOSED

Wontfix… in this repo.

First things first. In hindsight, I’d rather have the CSS framework and the CSS template decoupled – that was a poor decision on my part – so I would consider adding an extra “debug tools” layer more bloat.

Then, ROI is blurry to say the least. Those dev tools would be a glorified console you would inline in your EPUBs, with predefined methods. But we’d obviously have to create one for reflowable text, and another one for fixed-layout. So that’s quite a significant amount of work.

That inline console helped me debug some EPUBs tremendously, but that’s just me. Unfortunately, I’m not sure people are comfortable enough with using JavaScript in ebook production. Command-line can already be a huge showstopper, and developers of tooling have to pretty much build GUIs to be useful to the most people possible. Not complaining about this, mind you, just can’t help thinking we’d have to build a tool automating the creation of a debug version from the original EPUB file. So, it should be its own repository to not bloat this one anyway.

Finally, I’d be OK putting some work into the init of such a dedicated repository, but I’m definitely not willing to do all the work.

Please make your voice heard if you consider it would be useful and would want to help. I’ll then reconsider. For the time being though, there’s simply no visible incentive to share/polish the debug tools I’ve been using.

from blitz.