> Maybe we can extend the Firebug inspector to show the box hierarchy and/or the boxes that the selected box is directly related to.
The inspector already does this when inspecting an element using the
layout tab ... the parent element is highlighted using the image and a
dotted red border. If you would like anything else like this then just
let me know.
> Javascript edit and go
The Firefox extension called Phoenix can do this. It has a simple text
editor but the changes don't appear inside of Firebug.
> Firebug should support multiple simultaneous views of more than one panel
There are improvements planned for the XUL:Panel (https://
wiki.mozilla.org/XUL:Panel_Improvements). One particular section
relates to the multiple simultaneous panel idea:
"A dock button on the titlebar to dock the panel into the main window.
It would appear as, for example, a sidebar. Events would be needed
when a panel switches between these states to update any UI that might
be different. For instance, while a titlebar might appear while
docked, it won't be a native titlebar, although some platforms may be
able to render it as such. In the future, drag and drop of panels to
dock them may be an option. A dockbutton attribute would put a button
on the titlebar to dock and undock the panel. The attribute would have
no effect if a titlebar wasn't present. An API should exist to dock
and undock the panel; this would ideally work even if the button
wasn't present."
I want a simple feature to be able to copy and paste javascript from
the script panel without including the line numbers in the pasted
code.
On Mar 18, 5:26 pm, John J Barton <johnjbar...@johnjbarton.com> wrote:
With a big script in the script panel, try:
1. Ctrl+A to select everything
2. Right-click, select 'Copy Source' from the shortcut menu
3. paste into editor
This way, all output (and line numbers) are pasted too.
FB 1.6X.0a8
FF 3.6.3pre
hth,
d
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
Thanks,
MF
On Mar 19, 5:02 pm, "Honza (Jan Odvarko)" <odva...@gmail.com> wrote:
> You are right, now I also see even the related issue.http://code.google.com/p/fbug/issues/detail?id=2133
Regards
Jörn Zaefferer
On Mar 18, 5:26 pm, John J Barton <johnjbar...@johnjbarton.com> wrote: