New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Redesign options page #47
Comments
See comments on iOrder for notes on how this was implemented there. |
Also see the new comment on iOrder for information of how it was finally implemented. |
Seems to be working fine. Currently I'm not planning on redesigning the options page but perhaps in the future if Chrome adds some kind of new framework and/or L&F for this. Therefore this only includes the simplification of i18n within the options page and all other areas of the extension along with some other minor tweaks. |
There's currently a cosmetic issue with facebox and the templates guide where the close button is outside of the boundaries. I thought I previously fixed this but it seems that fix now breaks the close button when the guide is displayed. It's something to do with the display type but I think the following workaround will fix this; facebox = $ '#facebox > .popup > .content'
$(document).bind 'reveal.facebox', ->
margin = if facebox.find('> .template').length then '0' else ''
facebox.css 'margin-right', margin |
Now works fine. |
Now looking at Twitter's bootstrap framework for redesigning the page. |
Completely redesigned the options page and I'm extremely happy with the results. I'm now considering this closed but expect there may be minor changes to this page still before full release that relate to outstanding issues. |
As the title suggests... The new look should coexist with the style and layout of Chrome's internal option pages (chrome://settings). Help sections being triggered by "Learn more" links and tabs controlled by the left navigation. No search box should exist.
Resources could possibly be looked up the same way as the internal option pages (e.g. chrome://resources/css/button.css). I'm only guessing this but it would be really useful if it could.
Finally, it might be useful if a better framework could be in use for i18n replacement. Chrome's internal pages use the attribute
i18n-content
to contain the name of the message to be looked up used to replace the element's content. However, consideration should be given to how attributes and messages with arguments should be handled, but this a good start.All screenshots showing the options page should be updated afterwards.
The text was updated successfully, but these errors were encountered: