On Jun 15, 9:15 am, gozala <[email protected]> wrote: > Hi folks, > > I have tweeted today that: > > > Thinking that forking webkit #webinspector and porting it 2 a #Firefox > > extension is a very good idea. I just can't > > use #firebug any more!! > > I immediately got some replies probably it sounded to offensive to > firebug and it really was not my intention. I actually preferred > Firebug a lot before I started with a webkit related project last > year. After actively using it for a year I indeed find many things > very annoying in firebug most of them are UX related btw. I think are > some things that web-inspector does better job then firebug and I will > be a good citizen and will fill a bug reports for them. > > Here is the list: > > - In webkit command line presents on every tab and it's very > convenient specially in scenarios where you are inspecting some code. > Let's say you are on break-point and want to evaluate some js code to > digg into some objects in webkit you just type it while in Firebug you > have to switch to console tab type it (if you still remember what > exactly if not switch back) then go back. At least in my case that's > most of the time is scenario
I've heard this one and I've seen it in the Web kit videos http://code.google.com/p/fbug/issues/detail?id=768 > - Multiline js evaluation in webinspector is such a seamless > experience if you paste something your cmd is just grows a bit bigger > and enter still evals your code. While in firebug pasting multiline > snippet will make cmdline fold to the left and enter won't eval it > anymore which forces you to switch to differnt mode. I don't know about a bug report for that. > - in webinspector you dumped object can be inspect in place by > unfolding them, while Firebug will switch you to a different tab again > without cmdline forceing you to switch working mode That one is probably easy, but I'm not sure everyone would agree. One thing I'd like to understand about the UX here: if the cmdline results are on top of your panel, why is is better than switching panels? Is the keyboard bind better? Or what? > - source URL's for evaled code works very rarely (with the same code > sometimes it does sometimes it's not), for me and bunch of people I > know, maybe it's just us... If we had test cases we could fix it. All the cases for eval that I have work. Do all of these cases work in Web inspector? > - Things like code highlighting (I know about firerainbow which blocks > my firefox whenever you open a sourse with a lot of lines), code > completion are extremely useful! We need better support from Firefox for syntax highlighting. Code completion works in the Firebug command line. There is http://code.google.com/p/fbug/issues/detail?id=2676 about improving the UI. > > I don't know if there was any UX involved in designing webinspector > UI, but overall I think user experience is much better. Actually I can I think some people are very focused on the command line, and for them a tool like web inspector, which is strong on the command line, is a great fit. I don't use the command line much so I don't know about its issues. > see a lot of value in merging those two projects since more people > will be improving things better the tooling will get, besides most of > it is js. Actually the opposite is happening, with Firefox's new inspector and console projects. jjb -- 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.
