[Slogger] saving doctored DOM

Derek Robinson nnvsnu at yahoo.com
Sat Sep 3 13:43:38 EDT 2005


I'd like to be able to edit a web page with the very nice slayeroffice
MODI (MouseOver DOM Inspector) bookmarklet, invoked as a browser script
through a context menu button. Which I can indeed do and it works fine
except that when a page is logged, it's the original page that's saved and
not the page I've painstakingly redesigned. Is there a convenient way to
substitute the dynamic DOM (i.e. doc.documentElement.innerHTML) for the
static DOM of the downloaded page? All kinds of useful page-mods (think,
Greasemonkey) could be effected once this was in place.

I'd so like to get this working for me. My delight could be exceeded only
if I were shown how to make HTTP requests to multiple nonsame-domain URLs,
if this is possible. I suspect that it is, given the gnarly JavaScript in
the Slogger jarfile and the interfaces to Furl, Spurl, del.icio.us, et al.
but it'd be nice to know where to focus my attention without a degree from
XUL school. Basically I'm thinking that any page-mod I'd otherwise do with
Greasemonkey should be doable in Slogger -- e.g. under the Automation tab,
where one can apply a user script to be run at every page load. No need to
wait for a Greasemonkey release that doesn't lock up the extension manager
or cause worse mischief. If need be, I guess I could perform a system call
via slogger_systemExec() to a shell script that'd save the doctored DOM to
the Slogger data folder and update the log but that's absurdly roundabout,
there must be an easier way to patch into Slogger's innards.

Any tips / hints / guidance gratefully received!

Thanks, D.




__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


More information about the Slogger mailing list