Firebug/WeeklyUpdates/2014-07-08

From MozillaWiki
< Firebug‎ | WeeklyUpdates
Revision as of 18:32, 8 July 2014 by Honza (talk | contribs) (Created page with "Jan Odvarko, Joe Walker, Florent Fayolle, Sebastian Zartner, Farshid Beheshti, Steven Roussey, Simon Lindholm == Vacations == == Firebug 2 == * https://code.google.com/p/fb...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Jan Odvarko, Joe Walker, Florent Fayolle, Sebastian Zartner, Farshid Beheshti, Steven Roussey, Simon Lindholm

Vacations

Firebug 2

  • https://code.google.com/p/fbug/issues/detail?id=7560 (Improve performance of switching between JavaScript sources)
    • Probably related to syntax highlighting; many complaints => high priority
    • Introduce a new option in the Firebug menu "Turn off Color Highlighting"
    • Switch off syntax color everywhere
    • Try huge JS file to see the perf problem
    • But first: we should try appending the stylesheet asynchronously
    • Farshid: take a look at that
    • Farshid: ask :bgrins in #devtools IRC (Brian Grinstead, CM guru)
    • (Honza can introduce you if you want :)



Firebug 3

  • Theming
    • Let focus on one "Firebug" theme and do it right
    • We can safe reasonable amount of time by not maintaining three different themes.
    • But, it may be a competitive advantage for Firebug
  • Use chrome.manifest file
    • For skin dirs
    • For locale dirs
    • Honza: take a look
  • Default arg values
    • Yes, please!
  • Localization API (Farshid)
    • No blocker apart from accessing the locale dir
  • Let's use "theme" label for all new issues related to issues related to theming stuff
  • Simplify error tracing API #17
    • Options for short API:
    • TraceError.sysout()
    • TraceError.syserr()
    • TraceError.log()
    • Florent: make a decision

Demo for London work week (milestone "london" - we want this milestone in the github.com issue list), focus on (can we have meta bugs?):

  1. Firebug theme
  2. Support for jQuery
  3. Server side logging