Date:  22 Jan 2019 23:19:40 Hong Kong Time

Re: Intent to unship unmaintained panels: Canvas Debugger, WebAudio Editor, 

Shader Editor


Hello again.

Thank you to everyone who responded to our survey and got in touch with us. I would like to provide an update on what the plan is for the coming year regarding the three panels in question: the Web Audio Editor, Shader Editor, and Canvas Debugger.

We will be introducing a deprecation message in Firefox 68. This message will point folks to alternatives to the panels, as well as a Firefox build that still has the panels available. 

As of Firefox 69, the panels will be completely removed.

There is a group of people interested in migrating the Web Audio Editor to a Web Extension, and we will be helping them do that.

Unlike the Web Audio Editor, there are some good alternatives for the Shader Editor and the Canvas Debugger, but if this is not enough there will still be a version of Firefox that can be built or downloaded with these panels still intact. We will post the removal patch (which you can revert on your own build) as well in case you want to explore the code. If there is similar interest in migrating the other panels, we can also help any teams do that as well.

On Tuesday, November 20, 2018 at 9:46:58 AM UTC+1, Patrick Brosset wrote:
> The DevTools team working at Mozilla is too thinly stretched to continue
> maintaining this panel or migrate it to a WebExtension (which isn't trivial
> because of the need to have access to an event that tells us when audio
> nodes are being garbage collected, which is precisely what makes this tool
> useful for Michel).
> The awesome community of volunteers who work on DevTools in their free time
> hasn't really been interested in working on this (aging) tool either.
> So, yes, porting it to an extension, and moving it somewhere else would
> make a lot of sense, but we need someone willing to pick this up.
> I'm sure that with our combined experiences we would be able to give that
> person (or group of people) a lot of support in the form of discussions,
> ideas, reviews, maybe code changes.
> On Tue, Nov 20, 2018 at 9:40 AM Isaac Besora  wrote:
> >
> > Would it be possible to publish the WebAudio Editor code to some open
> > repository and port (and mantain) it as a separate extension?
> >
> > El dilluns, 19 novembre de 2018 15:33:13 UTC+1, va
> > escriure:
> > > Hi, I regularly use the WebAudio Editor to debug my WebAUdio graphs. So
> > far, even, if not maintained, it's still the only debugger for WebAudio
> > applications that takes into account the garbage collector. I just can't
> > imagine working without this tool or an equivalent in other browsers (and
> > while the Chrome WebAudio inspector extension is pretty good, it does not
> > help for debugging Audio Node allocation as it does not linked to the
> > garbage collector).
> > >
> > > You can check the tools we develop at
> > or read our papers published in
> > multiple international conferences. We are also developing other tools such
> > as a WebAudio plugin ecosystem that includes plugins + hosts (see our WAC
> > 2018 paper), for the moment these tools do not run on FF (waiting for
> > AudioWorklet support), but we always tried to make all our apps runnable on
> > as many browsers as possible.
> > >
> > > I talked at TPAC 2018 with some WebAudio developers about finding
> > resources to maintain and develop the WebAudio FF editor, and the announce
> > of its possible discarding can push us to REALLY try to find resources now.
> > Please don't let this tool die, I can't imagine developing our WebAudio
> > Apps without it now... Get in touch with us so that we can help...
> > >
> > > Michel Buffa
> > > University Côte d'Azur
> > > France
> >
> > _______________________________________________
> > dev-developer-tools mailing list
> >
> >
> >