Confirmed users
837
edits
Firebug/WeeklyUpdates/2014-04-22: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 24: | Line 24: | ||
** Simon: do some test case + instructions + list of all features | ** Simon: do some test case + instructions + list of all features | ||
** Anything not finished? | ** Anything not finished? | ||
* Issue 7082: OSX style issues in new UI | |||
** Thomas doing great progress | |||
** Honza: give feedback for 1px splitter | |||
== e10s Strategies == | == e10s Strategies == | ||
Round table discussion | Round table discussion | ||
Joe: | |||
* Firebug has better UI aspects | |||
* The best we can do for users is to update native tools with this ideas | |||
* Firebug represents set of extensions (for native tools) | |||
* Doesn't make sense to duplicate features (e.g. having two net panels) | |||
* When you install Firebug you get more advanced features (more buttons, etc.) | |||
Christoph: | |||
* The way how Firebug is extensible is smart | |||
* Firebug did a lot of things right | |||
* The way how templates work is good | |||
* Firebug defined the way how devtools (in different browsers) look today | |||
* Do you want to compete and fade out | |||
* Do you want to do next step and be innovative again? | |||
* Where you want to be in 5 years. | |||
* Firebug can be a platform that integrates web services (tools). Not only Firefox extensions but consuming also web services. | |||
* e10s is key for Firebug survival | |||
* Does FirePHP work with Firebug 2? | |||
* You can get more contributors by offering right API | |||
* You'll attract more contributors if the infrastructure is great and extensible. | |||
=== Sebastian === | === Sebastian === | ||
| Line 42: | Line 69: | ||
# Add more new features on top of the new structure | # Add more new features on top of the new structure | ||
Notes from the meeting: | |||
* Interaction with devtools: new commands for the command line and other little features. | |||
* | * New actor would have to be created, but actors for cookies, index DB has landed already | ||
* | * Existing actors can be monkey patched. | ||
* | * Sebastian estimate for e10s adoption: 1 year (optimistic) - 2 years (pessimistic). | ||
* I (Sebastian) believe there are still users using Firebug because it has better UI | |||
* There is still a lot of users of Firebug Lite | |||
=== Florent === | === Florent === | ||
| Line 71: | Line 98: | ||
We are not shielded from another issue related to Firefox changes (we already have experienced it with JSD1 -> JSD2 and now with e10s, maybe there will be something else afterwards...). That's the reason why relying on the DevTools API and a narrow cooperation with their team look the most viable option. | We are not shielded from another issue related to Firefox changes (we already have experienced it with JSD1 -> JSD2 and now with e10s, maybe there will be something else afterwards...). That's the reason why relying on the DevTools API and a narrow cooperation with their team look the most viable option. | ||
Notes from the meeting: | |||
* We don't have enough time | |||
* We need to define the playground (unique set of features that are not in native tools to avoid) | |||
* Why Firebug should loose users? | |||
* We could integrate existing extensions into Firebug | |||
* If we integrate too much addons users could be confused. | |||
* We should turn Firebug into Web Developer toolbar (too much unrelated features) | |||
* The way how to define new features: | |||
** Target a lot of users | |||
** Make sure features are related | |||
** There are not integrated by devtools | |||
* We can have a group working on dev-tools extensions | |||
=== 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. | |||
=== Honza === | === Honza === | ||
| Line 83: | Line 134: | ||
# Use existing e10s infrastructure from native tools through SDK. | # Use existing e10s infrastructure from native tools through SDK. | ||
# Build unique features on top of the SDK | # Build unique features on top of the SDK | ||
=== Simon === | === Simon === | ||