So you want to have a tool that operates with Show Comments false in
the HTML panel?
One solution is another HTML side panel, one that listens for event
>
> I would like to find the way to selectively show the meta-info for any
> given html-node. I mean something triggered by a contextual menu, or a
> mouseover, or anything that could just show what the developer is
> interested in.
onObjectBoxSelected(objectBox)
onObjectBoxUnselected(objectBox)
From the object box you can get the element and find comments around
it by some rule you create, parse the comment and display it in the
side panel.
Any of the current side panels are synced to the selection so you can
>
> We can eventually change the way DRYML embeds its meta-info by
> changing the comments for some custom tag attribute or anything else
> that might simplify that task to Firebug, although a sort of meta-
> commenting could be extendable to any other context (not just DRYML).
>
> Is there any canonical/suggested way to do that? What would you
> recommend? Is there any extension that could give me any hint about
> how to implement it?
use the same solution; I think they may use panel events instead of
the one I mentioned above.
As for the structure of the extension, they are all pretty similar,
and Honza has some great tutorial info
http://www.softwareishard.com/blog/firebug-tutorial/extending-firebug-hello-world-part-i/
SCRIPT TYPE="APPLICATION/VND.ACME-HTML-TEMPLATE" RUNAT=SERVER
SCRIPT TYPE="APPLICATION/VND.ACME-HTML-TEMPLATE" RUNAT=SERVER
Use SCRIPT instead of COMMENT. TYPE is registered for your application’s microsyntax, or application/xml, but then you should provide a reference to the XSD. RUNAT tells the browser that this script is interpreted on server; skip this if your server strips RUNAT scripts automatically, but then you need to make sure that your TYPE is not recognized by the target browser as an executable script. Note that TYPE="TEXT/XML" will load your script into MSXML3 in Microsoft Internet Explorer which is probably not what you want because MSXML3 is badly broken.
Chris