![]() ![]() This way, if an actor is added in the future it will automatically work with Thunderbird too. I will also refactor the toolkit DebuggerServer's addBrowserActors() to something like addCommonActors() which contains all actors that are supposed to work regardless of the app and then just call that from our init code. Then I can just call these methods from either the builtin overlay or the extension's bootstrap.js. The idea is to take the code currently in dbg-messenger-overlay.js and package it into a module. I'm going to use this milestone for completing the extension packaging work. > Milestone 5: September 10th - September 23rd It will be possible to use scratchpad remotely, likely without any extra Thunderbird work, when bug 895180 is fixed. > * Check if Inspector is ready for remote support yet bug 805526, not ready yet, but dcamp is working on it. Yes, gcli is remoteable, but it contains _a lot_ of Firefox specific code and dependencies. > - Alternatively, consider adding the gcli to Thunderbird itself. > * Find out if the gcli actor makes sense for Thunderbird and is remoteable The alternative would be a general mechanism that allows tracking any network connections, this goes down pretty deep into gecko. I haven't confirmed this with anyone, but it looks to me like this needs to be done on a per-channel basis, implementing nsITraceableChannel on the mock imap channel, somehow ignoring the cached entries and using the observer service to notify when imap requests are being made. This could be pretty tricky and might exceed the scope of a GSoC project. > * Investigate the possibility to add imap connections to the network monitorįiled bug 897564. > Milestone 4 (bonus): August 2nd - September 9th Ok, let me tell you a little about the post-midterm milestones: It would be nice to be able to have it work with those kinds of apps too. Since there is still some time before the next milestone is scheduled, I will take the time to figure out how to best proceed w.r.t Seamonkey and xulrunner. I will monitor bug 883342 and possibly find a solution for this, but aside from that I feel Milestone 1 is completed. I've also fixed two very trivial bugs in the devtools code. > * Add a "tab" actor per displayed email to be able to access content I've filed bug 883342 for this, it also fails for Firefox. If you close the window and open it again, the breakpoint is not triggered again. If you open the window, set the breakpoint, then its triggered as expected. > * Make chrome debugger work for the main windowįixed by bug 881235 > * Refactor chrome debugger and browser actorĪs mentioned, fixed by the devtools team in bug 870081 > * Make sure it also works for secondary windows > * Initialize the debugger server correctly, allow remote connections > * Add UI to Thunderbird to start the remote debugger (Tools menu) Milestone 5: September 10th - September 23rd * Check if Inspector is ready for remote support yet Alternatively, consider adding the gcli to Thunderbird itself. * Find out if the gcli actor makes sense for Thunderbird and is remoteable * Investigate the possibility to add imap connections to the network monitor Milestone 4 (bonus): August 2nd - September 9th * Make sure the profiler works for content code (if needed?) * Hook up the style editor to Thunderbird via StyleEditorActor * Hook up the web console to Thunderbird's console via WebConsoleActor * Make WebConsoleActor/StyleEditorActor code in toolkit independent of window * Add a "tab" actor per displayed email to be able to access content documents * Make sure it also works for secondary windows * Make chrome debugger work for the main window (this was my plan, but is now fixed by bug 870081) * Refactor chrome debugger and browser actor * Initialize the debugger server correctly, allow remote connections ![]() * Add UI to Thunderbird to start the remote debugger (Tools menu) I believe I will be able to achieve some of these milestones earlier. The dates are oriented at the GSoC dates and rather optimistic. The devtools team really deserves something shiny for their architecture and thanks to the existence of b2g their code is written to work with more than one application. ![]() I have spent the last days reading all the toolkit devtools code to find out what possibilities we have and what needs to be done. So, here is my first update and a firm plan on how I would like to go about things. ![]()
0 Comments
Leave a Reply. |