MSU CSE Capstone update 1/23
Today is the beginning of the third week of the in-content preferences project.
Last week the team landed their first patch and began working on fixing their second bug. Work has begun on moving the tabs pane to an in-content page, and the team has started to play with browser-chrome-tests, mixing XHTML and XUL, and putting together a project plan.
The basic plan of the the architecture is to place all the panes within one document and show/hide the panes when navigating the preferences. We can use pushState/popState to allow for forward/backward navigation, as well as perform in-content searches by showing/hiding the relevant sections.
The organization of the preferences will remain the same as it is today in Firefox. Any work on reorganizing the current preferences will be handled in a later phase that is not part of this project.
As a side note, I will be out of town for the next two Mondays but I will try to post updates when possible.
So I assume that the extensions inside the preferences aren’t part of this project ?
I’m also wondering if there’re any new mockups, because those made by Stephen Horlander are a bit old.
I’m not sure what you mean by “extensions inside the preferences”. Can you elaborate?
Unfortunately, there are no new mockups. The style of the pages will roughly follow that of the mockups you mentioned, about:permissions, and about:addons.
From https://wiki.mozilla.org/In-content_preferences :
“Integrate the parts of Firefox that should be in Preferences (such as the Add-ons Manager)”
The mockups also describe this : http://www.stephenhorlander.com/images/blog-posts/incontent-ui/win7-preferences-base.jpg
Thanks for the clarification.
I think that part of the project will be left out of the initial phase due to time constraints. If anything, there may be a link to the current implementation of the Add-Ons Manager.
Thanks for the quick answer. It’s always nice getting answered and even more when answered quickly.
No problem