DevTools/2011-06/02: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎Notices: added Scratchpad+Orion video demo link)
No edit summary
 
Line 9: Line 9:


* Firebug update
* Firebug update
** Firebug 1.7.2 released yesterday (several fixes, compatible with Fx5)
** Firebug 1.8 beta will be released tomorrow
** Firebug 1.8 works with Firefox 6 (maxVersion is set to 7 currently)
** Firebug 1.8 net panel displays the IP addresses and ports for remote end of request
* Style Editor
* Style Editor
** Incremental parser is a complex issue
*** Cedric has been reading research papers on parsers to figure out what's going wrong
*** Most of the papers are ancient
* Script Debugger
* Script Debugger
** Stack frame display likely to be finished today
* Web Console update
* Web Console update
** console.time, console.timeEnd and console.clear are all in various stages of review/superreview
** console.dir is progressing
** Fix for Scratchpad links for console.logs from the Scratchpad
** Workaround for document.body autocompletion problem
* Highlighter update
* Highlighter update
** some review going on for the main Highlighter patch
** iframes not highlighting properly
** some new mockups with suggestions coming up
* Command Line update
* Command Line update
** dcamp and jwalker put together a video showing the [https://people.mozilla.com/~jwalker/demos/gcli-debug-resume.webm command line controlling the debugger]
** dcamp and jwalker put together a video showing the [https://people.mozilla.com/~jwalker/demos/gcli-debug-resume.webm command line controlling the debugger]
** bunch of bugfixes have gone in
** needs a toggle switch (how much do we share between JS and Command Line)
* Style Doctor
* Style Doctor
** no update this week
* Style Inspector
* Style Inspector
* View source
** Going to try to land it without Highlighter integration
** Just need to deal with some RTL issues
** Going to add multiple style panels
* Code Editor
** A patch to integrate Orion editor
** Another patch to plug it into the Scratchpad
** Orion team really responsive to our patches
* View Source
** No updates
* HTML Tree Editing
* HTML Tree Editing
** Making the editor work against the DOM directly
*** Dropping the complicated regexes for attribute parsing to rely on the HTML parser (putting attributes on a dummy element and then reading the attributes off of that)
*** Communicating change events to DOM elements
** Next step is to plug the code directly into the HTML panel in Firefox
** In parallel, opinions accumulated on the UX
*** more feedback welcome
* Scratchpad
* Scratchpad
** Orion editor video demo [http://www.robodesign.ro/coding/screen-casts/mozilla-scratchpad-orion-bug-636727.ogv]
** Orion editor video demo [http://www.robodesign.ro/coding/screen-casts/mozilla-scratchpad-orion-bug-636727.ogv]


== Roundtable ==
== Roundtable ==
* QA
** Need use cases review (the ones on the Feature Page)
** New test cases for Scratchpad
** Rob's video link is forthcoming
* Command Line toggle
** started with a very simple integration... took JSTerm and made GCLITerm
** Patch doesn't rot easily because it's a clean separation
** The downside is that we end up with two sets of components (one for JS, one for GCLI)
** Question: do we just have one completion element?
*** One problem is that the JSTerm allows input to be separated over multiple lines
*** Mihai thinks we should use the same elements, but only allow multiline in JSTerm
*** dcamp: Don't want to change people's workflow, especially on a 6 week basis
*** Solution then is that JS mode allows multiple lines, Command Line mode just allows a single line
** It sounds like a more invasive patch is likely the better way to go
* Multiple Style Inspectors
** For the moment, going to punt on allowing multiple inspectors
** the current Web Console integration is not really the main entry point (that's the Highlighter)
** the Web Console should close auxiliary windows (object inspectors and network inspectors) when you leave the tab, in the same way the old Inspector did

Latest revision as of 15:44, 2 June 2011

Meeting Details

  • Thursday Jun 2, 2010 - 8:00am Pacific, 11:00am Eastern, 15:00 UTC
  • 650-903-0800 or 650-215-1282 x92 Conf# 9364
  • 1-800-707-2533 (pin 369) Conf# 9364 (US)
  • #devtools on irc.mozilla.org for backchannel

Notices

  • Firebug update
    • Firebug 1.7.2 released yesterday (several fixes, compatible with Fx5)
    • Firebug 1.8 beta will be released tomorrow
    • Firebug 1.8 works with Firefox 6 (maxVersion is set to 7 currently)
    • Firebug 1.8 net panel displays the IP addresses and ports for remote end of request
  • Style Editor
    • Incremental parser is a complex issue
      • Cedric has been reading research papers on parsers to figure out what's going wrong
      • Most of the papers are ancient
  • Script Debugger
    • Stack frame display likely to be finished today
  • Web Console update
    • console.time, console.timeEnd and console.clear are all in various stages of review/superreview
    • console.dir is progressing
    • Fix for Scratchpad links for console.logs from the Scratchpad
    • Workaround for document.body autocompletion problem
  • Highlighter update
    • some review going on for the main Highlighter patch
    • iframes not highlighting properly
    • some new mockups with suggestions coming up
  • Command Line update
    • dcamp and jwalker put together a video showing the command line controlling the debugger
    • bunch of bugfixes have gone in
    • needs a toggle switch (how much do we share between JS and Command Line)
  • Style Doctor
    • no update this week
  • Style Inspector
    • Going to try to land it without Highlighter integration
    • Just need to deal with some RTL issues
    • Going to add multiple style panels
  • Code Editor
    • A patch to integrate Orion editor
    • Another patch to plug it into the Scratchpad
    • Orion team really responsive to our patches
  • View Source
    • No updates
  • HTML Tree Editing
    • Making the editor work against the DOM directly
      • Dropping the complicated regexes for attribute parsing to rely on the HTML parser (putting attributes on a dummy element and then reading the attributes off of that)
      • Communicating change events to DOM elements
    • Next step is to plug the code directly into the HTML panel in Firefox
    • In parallel, opinions accumulated on the UX
      • more feedback welcome
  • Scratchpad
    • Orion editor video demo [1]

Roundtable

  • QA
    • Need use cases review (the ones on the Feature Page)
    • New test cases for Scratchpad
    • Rob's video link is forthcoming
  • Command Line toggle
    • started with a very simple integration... took JSTerm and made GCLITerm
    • Patch doesn't rot easily because it's a clean separation
    • The downside is that we end up with two sets of components (one for JS, one for GCLI)
    • Question: do we just have one completion element?
      • One problem is that the JSTerm allows input to be separated over multiple lines
      • Mihai thinks we should use the same elements, but only allow multiline in JSTerm
      • dcamp: Don't want to change people's workflow, especially on a 6 week basis
      • Solution then is that JS mode allows multiple lines, Command Line mode just allows a single line
    • It sounds like a more invasive patch is likely the better way to go
  • Multiple Style Inspectors
    • For the moment, going to punt on allowing multiple inspectors
    • the current Web Console integration is not really the main entry point (that's the Highlighter)
    • the Web Console should close auxiliary windows (object inspectors and network inspectors) when you leave the tab, in the same way the old Inspector did