Summit2008/Sessions/Proposals/Firebug & Chrome: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(New page: Presented by John J. Barton I propose to give a structured presentation mixing slides, demos, and questions, followed by a brainstorming open discussion on future directions. What is Fir...)
 
(Link slides)
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Presented by John J. Barton
Presented by John J. Barton and Jan Odvarko


I propose to give a structured presentation mixing slides, demos, and questions, followed by a brainstorming open discussion on future directions.
[http://getfirebug.com/workingGroup/2008/FirefoxSummit/FirefoxSummit2008FirebugChromebug.html As presented]


What is Firebug
We propose to give a structured presentation mixing slides, demos, and questions, followed by a brainstorming open discussion on future directions.


    * Overview, Demo
'''What is Firebug'''


A Little History of Firebug
* Overview, Demo


    * Joe Hewitt 1.0 and Open Source
'''A Little History of Firebug'''
    * 1.1 -- eval debugging, Firebug Working Group
    * 1.2 -- scaling/performance
    * 1.3 -- extensions


Architecture
* Joe Hewitt 1.0 and Open Source
* 1.1 -- eval debugging, Firebug Working Group
* 1.2 -- scaling/performance


    * 35kloc javascript
'''Chromebug'''
    * XUL/Component/jsd
    * modules, panels, contexts, events


Limitations and Problems with jsd
* Demo


    * Every callback in a debugger should have the call stack
'''Architecture'''
    * Pre-tab browser architecture problems
    * Script type identifiers
    * Compilation Unit structure
    * Memory and GC info
    * Closures


Competition
* 35kloc javascript
* XUL/Component/jsd
* modules, panels, contexts, events


    * Venkman, Webkit, IE?
'''Extensions'''
* YSlow
* FirePHP
* more from rest from Honza


Chromebug


    * Demo
'''Limitations and Problems with jsd'''


New Directions
* Every callback in a debugger should have the call stack
* Pre-tabbrowser architecture problems
* Script type identifiers
* Compilation Unit structure
* Memory and GC info
* Closures
* Read only Stack/Script


    * Firebug 1.4: socialized debugging, runtime-integrated editing, x-site debugging
'''Competition'''
    * Firebug 2.0: jit support, jit debugging
 
* Venkman, Webkit, IE?
* Input from audience please.
 
'''New Directions'''
 
* Firebug 1.3: extensions, testing
* Firebug 1.4: socialized debugging, runtime-integrated editing, x-site debugging?
* Firebug 2.0: jit support, jit debugging
* Input from audience please.

Latest revision as of 22:40, 8 August 2008

Presented by John J. Barton and Jan Odvarko

As presented

We propose to give a structured presentation mixing slides, demos, and questions, followed by a brainstorming open discussion on future directions.

What is Firebug

  • Overview, Demo

A Little History of Firebug

  • Joe Hewitt 1.0 and Open Source
  • 1.1 -- eval debugging, Firebug Working Group
  • 1.2 -- scaling/performance

Chromebug

  • Demo

Architecture

  • 35kloc javascript
  • XUL/Component/jsd
  • modules, panels, contexts, events

Extensions

  • YSlow
  • FirePHP
  • more from rest from Honza


Limitations and Problems with jsd

  • Every callback in a debugger should have the call stack
  • Pre-tabbrowser architecture problems
  • Script type identifiers
  • Compilation Unit structure
  • Memory and GC info
  • Closures
  • Read only Stack/Script

Competition

  • Venkman, Webkit, IE?
  • Input from audience please.

New Directions

  • Firebug 1.3: extensions, testing
  • Firebug 1.4: socialized debugging, runtime-integrated editing, x-site debugging?
  • Firebug 2.0: jit support, jit debugging
  • Input from audience please.
Retrieved from "https://wiki.mozilla.org/index.php?title=Summit2008/Sessions/Proposals/Firebug_%26_Chrome&oldid=103393"