Re: [Freetype-devel] Re: GSOC - Distance Fields

2020-06-20 Thread Werner LEMBERG
>>> Also I'm surprised that you haven't put the code get_min_distance >>> code for each edge type into a function. Would you prefer that I >>> comment re these on github? >> >> I don't think that will be necessary. I will fix that while adding >> in FreeType. That repository is just for testing

Re: [Freetype-devel] Re: GSOC - Distance Fields

2020-06-20 Thread Werner LEMBERG
> Systems without an FPU are vastly less common than they were 20 > years ago. They still exist, and is a defendable position to want > FreeType to continue to work on those systems, [...] Honestly, I think this an issue even today – just think of the Internet of Things stuff, which demands

RE: Logging Library-GSOC

2020-06-20 Thread armin
Hi Priesh, >> In previous mails, Armin suggested to move some of the FreeType's >> logging functionality to the external logger but according to my >> analysis, none of the external logging libraries that I have >> explored exactly matches the logging architecture of FreeType >> (i.e. logging

Re: [Freetype-devel] Re: GSOC - Distance Fields

2020-06-20 Thread Anuj Verma
Hello Alexei, First thing, here is the result of all the curves after using square distances: A) Line Segment: ~0.10 microseconds B) Conic Curves: ~0.75 microseconds C) Cubic Curves: ~0.71 microseconds For comparison, the previous result with `FT_Vector_Length': A) Line Segment: ~0.32

Re: [Freetype-devel] Re: GSOC - Distance Fields

2020-06-20 Thread Alexei Podtelezhnikov
On Sat, Jun 20, 2020 at 7:38 AM Anuj Verma wrote: > Secondly, I did try subdividing the conic curves, for start I simply divided > them into equal parts and used that to generate SDF. I saw that it require > at least 32 divisions to produce a decent SDF, which in itself is quite slower > than

Re: Logging Library-GSOC

2020-06-20 Thread Behdad Esfahbod
On Sat, Jun 13, 2020 at 10:59 PM Werner LEMBERG wrote: > > > I find it a *very* bad idea to have code in FreeType that would > > write to a file. Specially bad if that can be controlled by an > > env-var. > > Interesting. Please explain. Do you fear security issues? > > > I still think what's

Re: Logging Library-GSOC

2020-06-20 Thread Behdad Esfahbod
On Sat, Jun 13, 2020 at 10:59 PM Werner LEMBERG wrote: > > > I find it a *very* bad idea to have code in FreeType that would > > write to a file. Specially bad if that can be controlled by an > > env-var. > > Interesting. Please explain. Do you fear security issues? > Sorry, forgot to reply

Re: [Freetype-devel] Re: GSOC - Distance Fields

2020-06-20 Thread Behdad Esfahbod
Werner! On Wed, Jun 17, 2020 at 12:23 AM Werner LEMBERG wrote: > > Also, why doesn't FreeType use floats? Is it just because of > > platform which doesn't have floating point type? > > Yes. The original intention of FreeType was to provide support for > embedded devices, which usually are

Re: [Freetype-devel] Re: GSOC - Distance Fields

2020-06-20 Thread Behdad Esfahbod
Hi Anuj, On Tue, Jun 16, 2020 at 9:43 PM Anuj Verma wrote: > Hello Behdad, > > > First, let me congratulate you. This is a very thorough and impressive > piece of work for such a short time period. > > Thank you for that. Viktor's paper did help me a lot while writing the > code. I guess you

Re: [Freetype-devel] Re: GSOC - Distance Fields

2020-06-20 Thread Behdad Esfahbod
On Wed, Jun 17, 2020 at 7:22 PM Alexei Podtelezhnikov wrote: > Hi Anuj, > > Please let me finish my thoughts below... > > >> Each curved segment has a large number of neighboring grid points. > >> each of which has a unique nearest projection on the curve. The curve > >> is naturally sampled by

Re: [Freetype-devel] Re: GSOC - Distance Fields

2020-06-20 Thread Behdad Esfahbod
On Tue, Jun 16, 2020 at 9:54 PM Anuj Verma wrote: > > > Also I'm surprised that you haven't put the code get_min_distance code > for each edge type into a function. > > Would you prefer that I comment re these on github? > > I don't think that will be necessary. I will fix that while adding in >