I could try to add some tolerance so the viewport does not move until the highlight is out of say the middle third of the window. 1.4 has stuff to reduce the flicker so I've already forgotten about it ;-) (You could try the 1.4 alpha to see if that bit is better).
And thanks for the positive feedback, let me know if you have additional problems. jjb On Nov 3, 12:08 pm, blaimue <[EMAIL PROTECTED]> wrote: > I was comparing FF2/FB1.05 with FF3/FB1.2.1 and also FF2/FB1.2.1. And > for the record, > > 1.3 is much faster! It steps as fast as 1.05 did, and most notably it > loads the file MUCH faster. Thanks =) > > I notice that in 1.3 the file is scrolled as I step to keep the > current line in the middle of the window. Is there a setting to change > this behavior? It's hard to follow because I get a lot of flicker as > the file moves. > > Thanks, > Chris > > PS - Sorry if this is a double-post, I thought I replied but it wasn't > showing up in the thread so I'm resubmitting. > > On Nov 3, 11:39 am, John J Barton <[EMAIL PROTECTED]> wrote: > > > I don't know which old version you were using, but I guess 1.05. > > > I'm surprised that you did not have a problem before. Any chance you > > are comparing > > Firebug 1.05 + Firefox 2.0 > > to > > Firebug 1.2.1 + Firefox 3.0? > > > I've found two problems in the performance of the Script panel for > > large JS source files. > > > First, building the Script panel involves about 10 DOM elements per > > line of source. Once we get to 40kloc we are talking lots of memory > > and time to build the view. In addition, Firefox 3 has some additional > > problem with nodes that have a lot of identical kinds of elements. > > That is the only reason I can imagine that could explain how it could > > be ok in 1.05+FF2 and not good in 1.2.1+FF3. > > > Second, the Script panel wants to should you which lines are > > executable. When I started looking at some of the very large JS files > > I found out that the FF API for isLineExecutable() is impressively > > expensive. Its not practical for more than about 100 lines. So when > > we get to 40kloc, its not good. 1.05 did not show executable line > > markers, 1.2.1 does. > > > Firebug 1.3 solves both of these problems by building the DOM for only > > the visible lines and only calling isLineExecutable() on those lines. > > Please try it and let us know. > > >http://getfirebug.com/releases > > > jjb > > > On Nov 3, 11:07 am, blaimue <[EMAIL PROTECTED]> wrote: > > > > Maybe it's just me... but in terms of stepping through code I saw a > > > dramatic speed drop between 1.2 and the older version I had before. > > > My JS files are tens of thousands of lines long, if not hundreds of > > > thousands, but I never had a problem in the old version. Sometimes it > > > would take a long time for firebug to load the file and find the right > > > line, but when I got there I could step line by line relatively > > > quickly. In the new version it takes ~5s per line, which is a > > > dealbreaker for me. Just wondering if anyone else saw a similar drop > > > in performance in the new version and if there are any plans to > > > address this problem. > > > > Thanks, > > > Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
