DevTools/2011-05/19

Meeting Details

• Thursday May 19, 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
  • 1.8 beta is coming
  • will keep compatibility with existing extensions as much as possible
  • mark obsolete APIs display a warning in the console panel whenever a deprecated API is used
  • debated about including some extensions with Firebug
    • a better solution seems to be to use the "Swarm" feature started by John to load a bundle of connections
    • might include EventBug extension at least
  • Tested SeaMonkey compatibility
    • Only a couple of minor problems
  • Firebug modules are now loaded into an iframe rather than browser global scope
    • not perfect yet, but close
  • the modules work is nearly done, but the reorganization needs to be finished
  • More progress on remoting/Browser Tools Interface
• Debugger
  • remote protocol is limping along with thread-like actors
  • not tied into the UI yet
  • also working just on globals now
  • next step is getting it working with tabs
  • currently can stop at debugger statement and resume in global space
  • Mihai asked if you can set breakpoints at arbitrary points on a line
    • dcamp says "eventually"
• Web Console update
  • Console repositioning (top request!)
  • Autocompletion popup
  • video demo of the two new features
  • yay Firefox 6
  • Panos has 3 patches that are racing against time to try to land by Monday
• Scratchpad update
  • Working to get a few fixes before Tuesday
  • l10n feedback on menu items, so renaming some menu items
  • robcee is holding off on making a Scratchpad video until the menu items stabilize
• Highlighter update
  • Highlighter draws a darker background now
  • Tried adding shadows, outlines and such but found that performance was bad.
  • added a close button to the Highlighter
• Command Line update
  • Demo up
  • Working on patches
• Style Doctor:
  • Quick demo video (14Mb WebM)
  • Pages used in the video: demo and test
• Style Inspector
  • Applied changes from Mihai's review
  • Merged a couple of bugs into the main patch
  • Next step to integrate with the Highlighter
  • CSS logic part hasn't been reviewed by a peer at all, but some of the code has been reviewed a few months ago by dolske.
• Style Editor
  • Stylesheets tab
  • Editor tab
  • Cedric working on tests
  • Will likely post an add-on for people to play with
  • ultimately will end up in patch form
  • dcamp suggested we move Style Editor up in the list because of Cedric's timezones
  • Cedric's small incremental parser now has lots of tests and works pretty solidly (3 failing tests)
  • the parser allows the editor to know the context of what you're editing all the time
  • the DOM stylesheets get refreshed in parts, rather than entirely
  • the parser also allows making transitions for changes
• View source
  • working on feature pages/wireframes
  • dev-apps-firefox thread to start
• HTML Tree Editing
  • has been experimenting with the way you edit
  • the existing editing experience in other tools isn't always great
    • font changes
    • can't see original text
  • trying out having a separate editing box
    • clearly an editing interface
    • doesn't obscure the original code
  • also figuring out whether it makes sense to edit attributes independently
  • possibly making a delete button
  • maybe have tab key jump between values
  • robcee had a contenteditable patch that might be relevant, but that one replaced the entire fragment

Roundtable

• Kyle asked about how we generally do DOM manipulation work
  • Most people just do straight DOM manipulation
  • there is IQ, which is our stripped down jQuery
  • msucan says you could use IQ if you want, because there's nothing panorama specific
  • we may need to file a bug to get IQ pulled out into a resource we can load
• dcamp: should debugger be a web console-esque panel at the bottom or separate window?
  • most people seemed in favor of attached
• dcamp: if there are repos where people can put these bits of work in progress, it would be nice to know that
  • jwalker: for Joe's bits the URLs are in the feature pages
• when is final merge from devtools to m-c
  • robcee might make that tomorrow
  • Monday is a holiday in Canada
  • Rob is trying to get some Scratchpad things
• jwalker suggested that if we knew where all of these repos were, we could have automatic builds that identify where conflicts are
  • dcamp suggested having a repo where we dump everything in progress together and be able to play with it
• robcee: wouldn't it be cool if there was a web-based l10n thing that showed you which files referred to which strings?
• QA will update the Scratchpad wiki page with some basic use cases
  • they would like us to verify whether those cases are good