Firebug/WeeklyUpdates/2014-04-15: Difference between revisions

Jump to navigation Jump to search
(Fixed section title)
Line 46: Line 46:
* https://groups.google.com/forum/#!topic/firebug-working-group/wcCOqyk_kkk
* https://groups.google.com/forum/#!topic/firebug-working-group/wcCOqyk_kkk
** Everyone: join the discussion
** Everyone: join the discussion
Strategy suggestions:
=== Sebastian ===
Overall strategy:
* Keep Firebug a separate tool but interact with the DevTools
* Rebuild it based on RDP to make it e10s ready
* Use (reworked) APIs of the DevTools as far as possible
* Implement unique but important features to make it outstanding of the other tools
Steps how to reach that goal:
# Implement a fallback for the case we're not ready when e10s is obligatory (i.e. turn off e10s for Firebug or run it in the client process)
# Create some general functionality to access the page remotely (I guess that's what Honza calls the SDK)
# Locate each point where Firebug accesses the page directly
# Rework the located points, so that they access the page through RDP and e10s messages, first general things like TabWatcher than panel by panel, using DevTools APIs where applicable; while doing that already add some new features
# Add more new features on top of the new structure
=== Djalil ===
Overall strategy:
* Make firebug an advenced debuger (rest client, perf analytics, js game debuger, ...)
* Keep it as simple as now (keep same design)
* Keep existing panel (dont know if it's possible)
Steps how to reach that goal:
# Integrate devtools, i dont think we have choise, it's not only about e10s but also about all the new things (sourcemap, webgl/ canvas debuging, ...) i know that it's a difficulte decision, for me firebug was a revolutionary tools and now it's time for a new revolution.
=== Simon ===
TODO
=== Florent ===
TODO
=== Jakob ===
TODO
=== Steven ===
TODO
=== Others? ===
TODO
Confirmed users
837

edits

Navigation menu