Announcing Jiffy Firebug Extension

[Bill]

http://looksgoodworkswell.blogspot.com/2008/06/announcing-jiffy-firebug-extension-for.html

[Arlen]

Is there a way to present the timing data collected by jiffy on the
page it is being collected from by calling the Jiffy.getMeasures()
function after all of your marks and measures are called? I want to
print those values on screen as a 'firebug-less' way to see these
results. The firebug plugin is very cool, but there have been a couple
instances where I do not get values for the marks and measures in my
pages and I wanted to be able to work with these values manually if
needed. I have tried navigating the JSON object the getMeasures
function returns but I can not find much documentation on how to get
the data out of it, Any links or tips would be appreciated.

thanks, Arlen

On Jun 20, 10:54 pm, Bill <billwsc...@gmail.com> wrote:
> http://looksgoodworkswell.blogspot.com/2008/06/announcing-jiffy-fireb...

[Devin Ben-Hur]

On Wed, Jul 16, 2008 at 2:41 PM, Arlen <agth...@gmail.com> wrote:

Is there a way to present the timing data collected by jiffy on the
page it is being collected from by calling the Jiffy.getMeasures()
function after all of your marks and measures are called?

Well, the question is, "When's the last measure?"  One could just hook
an event, say on_load, and call getMeasures and dump the data into an
appropriate display.

It may be an interesting extension to allow one to register a callback
function which Jiffy will invoke everytime it records a new measure.
That function could then fully or incrementally update a display with
the new data as appropriate

-Devin

[Arlen]

I think i found where my problem with the firebug plugin was. It
appears that "mark&measures" that take longer than aprox 500ms to
complete do not show up in the initial view, rather you have to hit
the refresh button after the page has loaded to see the data collected
on the longer running measures.

Also I seem to have found an incident where a self closing iframe tag
<iframe .... /> inside the content being measured was causing the
javascript to stop running on the page, but did not display any
errors. On a hunch I changed the iframe tag to the standard format
<iframe ...></iframe> and that appeared to solve the issue, not sure
why the syntax of the content inside of a measure could cause that to
happen but i wanted to share my findings.

P.S. do you have any reference links or notes to show how to navigate
through the JSON object with JavaScript?

thanks, Arlen

[Bill]

In Javascript, if you do the following:

var measures = Jiffy.getMeasures();

then you can access the measures like this:

for(var i=0; i<measures.length; i++) {
var m = measures[i];
alert("Mark: " + m.name + ", Event: " + m.evt + ", Elapsed Time: "
+ m.et + ", Mark Start Time: " + m.rt);
}

As far as iframes, javascript can't go across iframes.

On the delay, that is not easy to solve. I am going to set the delay
as a configuration property for firefox. That way if you have slow
pages loading you can bump it up to a higher number.

--
Bill