An updated screendump script that'll generate nicer html, work faster, and look nicer in the browser.
Aliases
screendump logname - saves your buffer with the current log name. Warning, a huge buffer might take a while - do it in a safe place.
If you're on Mudlet2.0-rc6+, then you can just import the .mpackage, otherwise import the two xmls.
Updated screendump +mpackage
Updated screendump +mpackage
- Attachments
-
- screendump.mpackage
- (1.9 KiB) Downloaded 874 times
-
- screendump-buffer.xml
- (3.12 KiB) Downloaded 915 times
-
- screendump-alias.xml
- (574 Bytes) Downloaded 793 times
Re: Updated screendump +mpackage
This is an update to the script and it adds background colors. Replace your script with the one below:
If you've got a min, options to select what to save (instead of the whole buffer) would be desired additions.
Re: Updated screendump +mpackage
When I've tried to do this (make the screendump function log between certain lines), for some reason, the output I get is ... very very screwy. The colours are all wrong and off. The changes I made where the following :Vadi wrote: If you've got a min, options to select what to save (instead of the whole buffer) would be desired additions.
With only those changes made, the log file I get looks like this. Have you run into this issue as well?
Re: Updated screendump +mpackage
Nope, didn't try doing it - but there seems to be a bug in how it does </span>s, so that could be it
Re: Updated screendump +mpackage
Yes, using those changes there appears to be a bug in the for loop of going over the line/index of characters. I cannot see how just changing the line start number of getLines() introduces this behaviour though... it is baffling.
Re: Updated screendump +mpackage
Nah it's therr all along, just the browsers were managing to deal with it
Re: Updated screendump +mpackage
Would you be able to take a look and try to fix that particular bug?Vadi wrote:Nah it's therr all along, just the browsers were managing to deal with it
Re: Updated screendump +mpackage
Fair enough, I've fixed it and it validates as HTML now. I also added generation time and log size optimizations.
There is a slight optimization bug in the sense that it makes stuff like this:
Which should be optimized out. Further optimizations would be generating classes as necessary for new color combos and reusing them (currently, timestamp colors are optimized very well using this).
Still though, a usability improvement that allows the user to select where to dump from, not just the whole buffer, would be a very welcome addition.
There is a slight optimization bug in the sense that it makes stuff like this:
Code: Select all
<span style="color:rgb(73,149,0);">m</span>
<span style="color:rgb(73,149,0);background:rgb(0,0,0);">apper</span>
Still though, a usability improvement that allows the user to select where to dump from, not just the whole buffer, would be a very welcome addition.
Re: Updated screendump +mpackage
I will work on this addition, as it is something I would an will make quite a lot of use of.Vadi wrote:
Still though, a usability improvement that allows the user to select where to dump from, not just the whole buffer, would be a very welcome addition.
Thank you.
Re: Updated screendump +mpackage
Same HTML color writing error as the first time, when I attempt to give the function getLines() a start line.
http://pastehtml.com/view/b9suhcwo1.html
http://pastehtml.com/view/b9suhcwo1.html