Skip to content
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

Theme72 #10

Merged
merged 3 commits into from Sep 18, 2013
Merged

Theme72 #10

merged 3 commits into from Sep 18, 2013

Conversation

manuq
Copy link
Contributor

@manuq manuq commented Sep 12, 2013

No description provided.

Manuel Quiñones added 3 commits September 12, 2013 13:50
- We had 'indicator-size' harcoded to 26px.  Now is a proper number
  for sugar-72 theme.

- Provide new SVG files for the checkbox states, for sugar-72 .  Those
  were optimized with SVGO https://github.com/svg/svgo

- Reorder the assets in directories 'assets/100' and 'assets/72'.  The
  Makefile takes care of copying the correct SVG files to the build
  directory.

Fixes #4092 .
- Variable scale_trough_margin was harcoded for both themes.  Now is a
  proper number for sugar-72 theme.

- Provide new SVG files for the slider assets, for sugar-72 .
- Provide new SVG files for the radiobutton states, for sugar-72 .
@manuq
Copy link
Contributor Author

manuq commented Sep 12, 2013

Ideally we would just add 'viewBox' attribute in these SVGs in order to make them fit the available space: http://www.w3.org/Graphics/SVG/IG/resources/svgprimer.html#SVG_web

But the gtk theme engine does not consider that attribute. I submitted a bug:
https://bugzilla.gnome.org/show_bug.cgi?id=707934

So the current option is what these patches do, provide different SVGs for the 72% theme.

@dnarvaez
Copy link
Contributor

Looks good

@manuq manuq merged commit e893099 into sugarlabs:master Sep 18, 2013
@manuq manuq deleted the theme72 branch September 18, 2013 17:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants