Re: [freetype2] Remove #include FT_XXX_H includes from library sources

2020-06-04 Thread David Turner
Le ven. 5 juin 2020 à 00:00, Werner LEMBERG a écrit : > > This is the first time ever that I got a git bundle to handle, and I'm > stuck. I don't know how to apply it to the git repository. Trying > > git pull freetype2-remove-macro-includes.bundle > > results in > > fatal: Couldn't find re

Re: [freetype2] Remove #include FT_XXX_H includes from library sources

2020-06-04 Thread Werner LEMBERG
Hello David, > This bundle contains patches to replace all #include FT_XXX_H > statements from the library into the corresponding #include > include. Thanks! If I understand you correctly, the idea is to 'normalize' FreeType so that it looks similar to other libraries, not alienating users wi

Re: GSOC - Distance Fields

2020-06-04 Thread Werner LEMBERG
Dear all, please stay constructive and civilized. No need for personal attacks – in the end we all want the same. I'm glad that there are experts on the list who want to share their experience, and who are willing to help Anuj so that he succeeds. I believe that it is a big help to have diffe

Re: GSOC - Distance Fields

2020-06-04 Thread Alexei Podtelezhnikov
Well. It is your arrogance against my ignorance. Why haven't you thought about contributing your wonderful DF ideas before? Or, is it again like HarfBuzz autoshaper that has to be separate and you have to control it? On Thu, Jun 4, 2020 at 2:32 PM Behdad Esfahbod wrote: > > For more context: I'm

Re: GSOC - Distance Fields

2020-06-04 Thread Behdad Esfahbod
For more context: I'm not going to stay silent to your abuse anymore. You have no idea what distance-fields are used for, never used one, never generated one, and you are blocking real constructive discussion from people who actually know that shit. On Thu, Jun 4, 2020 at 11:31 AM Behdad Esfahbod

Re: GSOC - Distance Fields

2020-06-04 Thread Behdad Esfahbod
That's BS Alexei. Eff off. On Thu, Jun 4, 2020 at 10:28 AM Alexei Podtelezhnikov wrote: > Jim, Behdad, > > Please hold your horses. This is Anuj's GSoC project for this summer. > It is not nice to take it over until September. For now, please let > him explore the field. Feel free to discuss yo

Re: GSOC - Distance Fields

2020-06-04 Thread Jim Van Verth
Apologies, it was not my intent to bikeshed. As I said before, I'm looking forward to seeing his results. Either way, happy to offer my experiences off-thread if desired. On Thu, Jun 4, 2020 at 1:28 PM Alexei Podtelezhnikov wrote: > Jim, Behdad, > > Please hold your horses. This is Anuj's GSoC p

Re: GSOC - Distance Fields

2020-06-04 Thread Alexei Podtelezhnikov
Jim, Behdad, Please hold your horses. This is Anuj's GSoC project for this summer. It is not nice to take it over until September. For now, please let him explore the field. Feel free to discuss your own implementation in a separate thread or at least povide some explanation instead of abrupt "8.8

Re: GSOC - Distance Fields

2020-06-04 Thread Behdad Esfahbod
Thanks Jim. A 2.14 representation when 1 unit = 1em is sufficient. If we are talking pixels then 10.6 or better 8.8 makes more sense. And I agree that the pixel values are more useful to clients than em values. On Thu, Jun 4, 2020 at 8:35 AM Jim Van Verth wrote: > Behdad, > > Thanks for the p

Re: GSOC - Distance Fields

2020-06-04 Thread Jim Van Verth
Behdad, Thanks for the pointer to cu2qu, I'll take a look at it. I assume you're suggesting we use that in place of GrPathUtils::convertCubicToQuads. I believe in our case we chop at inflections to avoid artifacts from our resolution independent curve rendering. As far as scale for our SDFs, 1 un

Re: Edge effect (Depressed) on a Pixmap buffer using freetype lib

2020-06-04 Thread Alexei Podtelezhnikov
On Thu, Jun 4, 2020 at 8:28 AM Aurovind Sagar wrote: > We are using FreeType. Sorry, the intention was not to report any bug. We are > looking for suggestions. We are not from graphics background, hence please > excuse if we have asked any obvious questions. Guys, you need to learn about alpha

Re: Edge effect (Depressed) on a Pixmap buffer using freetype lib

2020-06-04 Thread Aurovind Sagar
Hi Alexei, We are using FreeType. Sorry, the intention was not to report any bug. We are looking for suggestions. We are not from graphics background, hence please excuse if we have asked any obvious questions. As Niyas mentioned, everytime we write new stuff onto the pixmap it would overwrite th

Re: Edge effect (Depressed) on a Pixmap buffer using freetype lib

2020-06-04 Thread Alexei Podtelezhnikov
> Now here the problem what we are facing is when we load the glyph we get the > data in a bounding box. The glyph which is loaded is a greyscale and it is > with bounding-box. So when we draw the edges and font as per the above logic, > the bounding boxes of the edges and the font gets overlapp