Midterm is over, I passed 🙂 . So much for seeking attention, let’s get back to the updates.
There was no report last week and this week also, as I was fine tuning many things to be ready for mid-term and an AMO push bound this week. I will mention the changes from the previous meeting, the overall progress of the project and the future plans (tentative) in this post.
Changes from the last report:
- The zoomed out view is complete, and the default view when you start the timeline.
- The timeline will only squeeze when any new events are available.
- The detailed view is complete and it will show all the details related to the event.
- It only works when the Timeline is not in overview mode (just move the time ruler or select a time range #4) and when you hover the event.
- You can pin the detail box by clicking once the box is visible (click again to unpin it)
- You can select any time range and zoom into that. Just click and drag a time range on the canvas. It’s very simple, give it a try.
- Some performance gains by combining the 3
- Nothing is hard-coded into the timeline.jsm anymore. The producers themselves register the things to be displayed in the detailed box, and there are more than 5 types available (namely date, string, enum, url, object, etc.). I will soon start writing wiki for all these things.
- Many issues related to producers pane were fixed as the pane is not collapsed anymore. It just slides away from view.
- The play button is gone. Maybe the remaining two text button will also become images (maybe).
Now the overall progress in a little medium-sized nut shell:
- The timeline records three types of events:
- Network calls: Any kind of GET or POST calls.
- DOM Events: Events like click, mouseup etc. for the page, the timeline is active.
- Garbage collection and Cycle collection: Incase of Incremental GC, the slices are also visible.
- More producers can be added to record more type of events as everything is modular (just like GCLI commands).
- The UI for displaying these events is also in good shape and close to being perfect. (I know any UI will never be actually perfect).
- The interactions between the UI and the producers is async and handled using custom events for now. Soon RDP will be the way.
- Code cleanup and performance optimizations.
- Linking Style Editor, Scratchpad, Script Debugger and Inspector with the Timeline.
- Using Remote Debugging protocol to transfer event data and any other message.
- Proper documentation so that others can also add some producers, or may some UI components too.
- May be some more kind of producers, most probably recording timers.
As always, try out the add-on using this xpi file, until the add-on is hosted on AMO.