*Just a quick update on the inkscape open symbols set!*
- Added Octicons https://octicons.github.com/, the github icon font ( https://octicons.github.com/) - Added Humble UI https://github.com/Xaviju/inkscape-open-symbols/wiki/Humble-UI, a simple UX wireframing library that I created myself ( https://github.com/Xaviju/inkscape-open-symbols/wiki/Humble-UI) - Probably soon: Ubuntu Suru http://www.typhoonpc.com/linux/suru-icon-theme-package-lands-in-ubuntu-14-04 Icons ( http://www.typhoonpc.com/linux/suru-icon-theme-package-lands-in-ubuntu-14-04) I'm waiting for a PR
https://github.com/Xaviju/inkscape-open-symbols
Brynn asked
For now, the main question is this. Why do you go through all the steps with the SVG/XML code and stuff, rather than use the on-canvas tools?
You are right, is perfectly fine to use the UI. To me is a little bit more
complicated and slower, but it is fine. Since I am more a front-end developer than a designer, it looks faster to me to manage SVG code than multiple windows, forms and clicks :) But also, in my tests, I found out that the final generated code from the UI (and this might be my fault) its not as perfect as I would like it to use it directly (just copying and pasting it) in my web development workflow, so I need to clean it up a bit. I just wanted to remove this step. That's why the posts says "and make your front-end developer love you". This feature is just awesome.
Thanks again, your feedback is very appreciated.
2015-02-26 14:07 GMT+01:00 Xaviju Julián <xaviju@...155...>:
Hi!
I just send you this email to let you know that I created a symbol set for inkscape with the *Google Material Design Icons* (at the moment only this set) that you may find useful for design and development.
https://github.com/Xaviju/inkscape-open-symbols
I also encourage you to collaborate as indicated in the readme to make it even better and make designers and front-end developers happier. Lets open source and share our own icon libraries as well.
Hope you enjoy it. :)
Xaviju