--
You received this message because you are subscribed to the Google Groups "Firebug" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebug+u...@googlegroups.com.
To post to this group, send email to fir...@googlegroups.com.
Visit this group at http://groups.google.com/group/firebug.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/6277c77a-934a-4fd0-8fcf-833b0dc0fd5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I'd love to give 3.0 a try, but cannot, at the moment, or indeed for a few months. Firebug is mission-critical to my current app's development process and that process is on a deadline. I can't take the risk that I would be forced into an inferior tool-set (and the Mozilla-provided "tools" are that, in my experience) which would slow down or cripple my dev process. In fact, I've currently disabled ALL updating of Firefox, so as to avoid exactly that situation. :(
The only option I can explore, for the near-future is PaleMoon (https://www.palemoon.org/), with an older version of Firebug, as a concurrent installation, which is why I am in favor of getting Firebug's latest 2.0 version compatible with that fork (but understand why that is unfortunately probably not going to happen). :)
I suggest, when you have time again you should try the built-in devtools again and file bugs for the things that are annoying for you. The devtools team obviously wants to close the gaps between Firebug and their tools. See bug 991806. Also, I have to say that I like the devtools. Their UI and features are in some parts not as good as Firebug, though therefore they offer much more features. And I am saying that as a former Firebug contributor.
If Pale Moon gets updated to be based...
Just to give everyone an idea of what I mean by "intense client-side"
development, here is a WIP image of my current project, "The Role
Table." It's a Virtual Tabletop for Pen and Paper Role-Playing Games. It
allowspeople around the globe to get together and play any RPG (Think
D&D) as if they were all sitting around the same kitchen table. It
allows folks to directly implement the rules for any RPG system, through
an easy-to-read XML format (created by hand or by a supplied desktop
app). It makes extensive use of Ajax, JSON and CSS. (warning large image, click to enlarge)
All windows are moveable with positions remembered and support dragging and dropping, configurable context menus, and more. The app also implements a plugin architecture, allowing users to further extend ts functionality. All communication from browser done with a messaging server app, written to run under Windows/MacOS/Linux and using JSON and XML as its formats. Future features to include a "3D" dice roller, built-in voice/video chat and more.
So, you can see, a "toy" debugger just isn't going to cut it, for me, LOL. Firebug does a fantastic job for me, though.
Whoops, forgot to add:
It currently targets (using CSS) a variety of browser platforms and screen sizes. Currently tested on: iPhone (5.6), iPad, Android and the 3 major desktop browsers.
--
You received this message because you are subscribed to the Google Groups "Firebug" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebug+u...@googlegroups.com.
To post to this group, send email to fir...@googlegroups.com.
Visit this group at http://groups.google.com/group/firebug.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/4cd1dca0-5c76-4b59-9a36-781ecacbd223%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/9121b711-aaa4-40e3-836d-498753efe07f%40googlegroups.com.
For my small 2 cents here -- I am completely agree with @William Nerini. I think the folks at Firefox do not a clue about how important the dev community is to their product and I think they seem to be pursuing things that, as UI front-end developer, I have never seen "real" people require.
Whereas, it does not seem all that hard -- in the context of a company with their capabilities -- to exactly re-create Firebug, and then improve it.
On Friday, August 28, 2015 at 8:03:20 AM UTC-4, William Nerini wrote:I suggest, when you have time again you should try the built-in devtools again and file bugs for the things that are annoying for you. The devtools team obviously wants to close the gaps between Firebug and their tools. See bug 991806. Also, I have to say that I like the devtools. Their UI and features are in some parts not as good as Firebug, though therefore they offer much more features. And I am saying that as a former Firebug contributor.Sadly, most of my problems with the built-in tools are lack of features. And that's not a bug-fix away.
Especially problematic, for me, is the poorly implemented variable watch system
and lack of a real "DOM Panel".
Also the "debugger" is a mess, in general,
but especially when it comes to script navigation
I had come up with a list, last year which had about a dozen features and dozens of bugfixes/changes that would be required to their tools, to bring them up to Firebug's level, for me, so I see any attempts there, on my part, as, essentially, an effort doomed to get no traction.
The problem lies in that I'm doing extremely intense client-side development and Firefox's tools seem to be fundamentally geared towards the developer who needs to work on the occasional small scripting problem.
Firebug has, for me, been a godsend. I couldn't have developed half the tools I have for my apps without its power and flexibility.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/c7864384-e7e7-4583-83a9-d4c81d8d7ed5%40googlegroups.com.
I had come up with a list, last year which had about a dozen features and dozens of bugfixes/changes that would be required to their tools, to bring them up to Firebug's level, for me, so I see any attempts there, on my part, as, essentially, an effort doomed to get no traction.
Could you point me at that list?