|Page Inspector Tilt (3D View)|
|Release target||Firefox 11|
|Product manager||Kevin Dangoor|
|Directly Responsible Individual||Kevin Dangoor|
|Lead engineer||Victor Porof|
|QA lead||Trif Andrei - Alin|
|Product marketing lead||`|
Stage 1: Definition
1. Feature overview
Tilt was a Google Summer of Code 2011 project that resulted in an add-on showing a 3D view of an HTML document. It was initially an experiment to see how such a view could be used, and the student working on the project (Victor Porof) came up with many ideas for enhancements on the basic idea.
It is likely that we wouldn't want to provide all of the functionality that exists in the add-on as a built-in feature. However, the basic 3D view has proven to be useful and unique.
Tilt is available on AMO.
2. Users & use cases
- Finding nesting problems
In the Hacker News discussion, at least one commenter noted that Tilt provided a visualization that will help solving nesting problems more quickly than the other solutions.
- Learning about HTML structure
Developer tools such as "view source" have always been used to help people learn about web technology. The 3D view highlights the structure of a page better than a flat view.
Stage 2: Design
5. Functional specification
The plan is to take the 3D visualization from Tilt and incorporate it as an optional view in the Page Inspector.
As with the normal Page Inspector view the user can select elements in the 3D view and have that selection propagate to tools like the Style Inspector.
Keyboard navigation will work as it does currently in Tilt. The on-screen navigational components from the Tilt add-on will be the only auxiliary UI brought forward from the add-on. The navigation controls will be helpful for users to learn how to navigate the 3D view.
Switching Into and Out of 3D Mode
There will be a "3D" button in the Inspector Toolbar that toggles 3D mode. There should also be a command line command for doing so.
If the user's computer is not capable of GL, then the 3D button will not be displayed at all in the toolbar.
6. User experience design
Stage 3: Planning
7. Implementation plan
Quality Assurance review
Stage 4: Development
Stage 5: Release
10. Landing criteria
|Theme / Goal||`|
Team status notes