John J Barton wrote:
Some ideas on future features:
http://blog.getfirebug.com/2010/03/18/firebug-dreams/
jjb
Some really thought-provoking ideas in there; look forward to having
them all implemented RSN. 8^) Here's a few thoughts:
Automatic or Query-based Logging: Now we have to edit our Javascript
to add console.log() statements. Some times we just want to know:
what code runs when I do this? A simple way to summarize the
execution path would be automatically inserted console.log() calls on
every function call or every call matching a pattern and so on.
I'm wondering if Aspect Oriented Programming concepts would be useful
here. For example, look at
http://www.ibm.com/developerworks/java/library/j-aopwork15/
As an ExtJS user, I heartily approve. It'd be really cool to be able to
have a view on the HTML showing ExtJS objects with ExtJS properties.
Firebug should support multiple simultaneous views of more than one
panel and have better integration support with editors and Web
servers.
You might get some good ideas from wxWidgets' AUI library:
http://wiki.wxwidgets.org/WxAUI. (I think there are some demo apps,
either from wxWidgets or wxPython.)
--
Don Dwiggins
Advanced Publishing Technology
--
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.
