[Sugar-devel] GSoC 2020 Work Product Submission - Hosting Offer
GSoC has given Work Product Submission Guidelines; https://developers.google.com/open-source/gsoc/help/work-product As an option, students working on Sugar Labs projects may also contribute to our GSoC repository as follows; 1. fork our repository; https://github.com/sugarlabs/GSoC 2. create a folder 2020 here; https://github.com/sugarlabs/GSoC/tree/master/archives 3. create a folder for yourself; 4. create files with your work product, 5. link to the files from the idea list; https://github.com/sugarlabs/GSoC/blob/master/Ideas-2020.md 6. commit the changes and make a pull request, or push direct to the repository if you have permission. -- James Cameron http://quozl.netrek.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Handling of SVG in Sugar/Sugarizer
Thanks Lionel, I agree with the change. For your interest, Sugar loads SVG and changes the colours in sugar3.graphics.icon _SVGLoader; https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/src/sugar3/graphics/icon.py#L116 In your study you say; "The SVG file should be updated manually" ... in some cases sugariconify can be used to update the file automatically. https://github.com/sugarlabs/sugariconify On Thu, Aug 20, 2020 at 10:55:13PM +0200, Lionel Laské wrote: > > Hi all, > > From the beginning, the handling of SVG files in Sugar rely on Entity fields > in > the header of files. Something like: > > "[1]http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd; [ > > > ]> > > This mechanism is described on [1]. Sugarizer rely on the same mechanism to > colorize icons. > > Because this "hack" has some drawbacks - specifically on performance - I think > to change it in a future version of Sugarizer to use native SVG/CSS features > instead. I've done a detailed study here [2] to explain how it could work. > > Of course it will generate compatibility issues but it would be nice to see if > the same thing could be done in Python too. I'm not a Python/Gtk specialist > but > will be happy to help on it. > > Regards. > > Lionel. > > [1] [2]https://wiki.sugarlabs.org/go/Development_Team/Almanac/Making_Icons > [2] [3]https://github.com/llaske/svgstudy > > References: > > [1] http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd > [2] https://wiki.sugarlabs.org/go/Development_Team/Almanac/Making_Icons > [3] https://github.com/llaske/svgstudy > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- James Cameron http://quozl.netrek.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Handling of SVG in Sugar/Sugarizer
Very interesting. I hadn't known that svg had css support these days. Would make sense to take advantage. On Thu, Aug 20, 2020, 4:55 PM Lionel Laské wrote: > > Hi all, > > From the beginning, the handling of SVG files in Sugar rely on Entity > fields in the header of files. Something like: > > "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd; [ > > > ]> > > This mechanism is described on [1]. Sugarizer rely on the same mechanism > to colorize icons. > > Because this "hack" has some drawbacks - specifically on performance - I > think to change it in a future version of Sugarizer to use native SVG/CSS > features instead. I've done a detailed study here [2] to explain how it > could work. > > Of course it will generate compatibility issues but it would be nice to > see if the same thing could be done in Python too. I'm not a Python/Gtk > specialist but will be happy to help on it. > > Regards. > > Lionel. > > > [1] https://wiki.sugarlabs.org/go/Development_Team/Almanac/Making_Icons > [2] https://github.com/llaske/svgstudy > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Handling of SVG in Sugar/Sugarizer
Hi all, >From the beginning, the handling of SVG files in Sugar rely on Entity fields in the header of files. Something like: http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd; [ ]> This mechanism is described on [1]. Sugarizer rely on the same mechanism to colorize icons. Because this "hack" has some drawbacks - specifically on performance - I think to change it in a future version of Sugarizer to use native SVG/CSS features instead. I've done a detailed study here [2] to explain how it could work. Of course it will generate compatibility issues but it would be nice to see if the same thing could be done in Python too. I'm not a Python/Gtk specialist but will be happy to help on it. Regards. Lionel. [1] https://wiki.sugarlabs.org/go/Development_Team/Almanac/Making_Icons [2] https://github.com/llaske/svgstudy ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
