slayeroffice - web experiments gone horribly awry

05.08.2005 - MODI v2.0

Its probably too early to release, but I'd like to get some feedback and some extra eyes on the newest version of the Mouseover DOM Inspector.

Version 2.0 sports an entirely new code-base and UI along with a load of new features, including multiple operational modes, ~20 keyboard commands (more coming, probably) that do everything from remove objects from the DOM to add labels to them, and my personal favorite - an optional external preference file that you can host yourself to define how you want the favelet to run.

These and everything it did in version 1.x, including in-place editing and Aaron's additions. I've put a help file together that details all of the new functionality and has a link for the favelet. If you'd like to try it out, please keep in mind that its not quite finished yet, so please make an effort to send me a note or leave a comment with any problems you encounter (particularly with MSIE6) or suggestions you have for additional feature sets.

So far so good in Firefox 1.0.3!
Posted by Jon on May 9, 2005 @ 12:36 am
Error message from JavaScript console in Opera 8:

http://slayeroffice.com/tools/modi/v2.0/modi_help.html

Inline script thread

Error:

name: TypeError

message: Statement on line 43: Could not convert undefined or null to object

Backtrace:

Line 43 of linked script http://slayeroffice.com/tools/modi/v2.0/modi_v2.0.js

var isAppXML = document.contentType.indexOf("application/xhtml") > - 1;
Posted by Oswald on May 9, 2005 @ 3:11 am


@Jon - thanks!

@Oswald - thanks, its fixed. Clear your cache if need be.
Posted by Steve on May 9, 2005 @ 4:12 am


**bows in humility**

Amazing upgrade Steve... these are all just awesome.

Only thing I've noticed (and not sure anything can be done) is that when you turn the border on, and then off, the border attributes (-moz-outline-color, etc) are still there. Not critical by any means, just an observation.

Other then that, all the new features are very nice and can't wait to start using them regularly. Will make sure to report back anything else I bump into. Great job!!
Posted by Aaron on May 9, 2005 @ 4:41 pm


Woops... finally started looking in your code and see you have that as a todo. Or at least I think that is what you were saying.
Posted by Aaron on May 9, 2005 @ 4:47 pm
Thanks Aaron, appreciate the comments. You're right, the -moz-outline stuff is on my list. Definately let me know of anything else you come across.
Posted by Steve on May 9, 2005 @ 5:05 pm
Hi Aaron,

Is there a way to force your parenting structure to show something like the following?

html > body > div#mContainer > div#content > form.news > textarea.txtArea

A good example would be the View Style Info feature on the Web Developer extension for Firefox This would help designers to find the exact CSS child element.

Cheers and keep up the great work.

Marcelo
Posted by Marcelo Paiva on November 11, 2005 @ 4:34 am


Sorry, I meant Steve
Posted by Marcelo Paiva on November 12, 2005 @ 2:02 am

Comments have been closed for this post.