Re: I'm back

2020-06-27 Thread Behdad Esfahbod
Hi David, I've been meaning to reply to your request but the list of things I wanted to communicate kept growing exponentially and so I have not been able to say. But here, from a technical perspective this is my biggest issue, which you can also see as a roadmap:

Re: Logging Library-GSOC

2020-06-27 Thread Werner LEMBERG
> I have updated the progress report for this week @ here > > It contains a brief description of all the useful APIs provided by > dlg Thanks, looks promising. If you are going to import the

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

2020-06-27 Thread Werner LEMBERG
> One more thing. I think the OpenGL demo is not good for everyone to > test, so I will working on a demo similar to 'ftview' in my spare > time. Great! Werner

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

2020-06-27 Thread Anuj Verma
One more thing. I think the OpenGL demo is not good for everyone to test, so I will working on a demo similar to 'ftview' in my spare time. On Sat, Jun 27, 2020, 8:21 PM Anuj Verma wrote: > > >> A) Checking all grid points:15.43 seconds (~154ms per glyph average) > >> B) Bounding Box check:

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

2020-06-27 Thread Anuj Verma
>> A) Checking all grid points:15.43 seconds (~154ms per glyph average) >> B) Bounding Box check: 0.898 seconds (~8.98ms per glyph average) >> C) Subdivision method : 0.665 seconds (~6.65ms per glyph average) > > [for subdivision I equally divided the curve into 16 parts] > This is a tie

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

2020-06-27 Thread Alexei Podtelezhnikov
H Anuj, On Fri, Jun 26, 2020 at 8:16 AM Anuj Verma wrote: > A) Checking all grid points:15.43 seconds (~154ms per glyph average) > B) Bounding Box check: 0.898 seconds (~8.98ms per glyph average) > C) Subdivision method : 0.665 seconds (~6.65ms per glyph average) > > [for subdivision I

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

2020-06-27 Thread Anuj Verma
> I assume spread means maximum distance. Yes. > We use a spread of 4, so 8 would be plenty. We use 4 mainly to keep the glyph sizes under control, > because a larger spread means a larger pad of texels around each glyph to make use of that information. So I guess 8 is enough for now. And btw

Re: Logging Library-GSOC

2020-06-27 Thread Priyesh kumar
Hi, I have updated the progress report for this week @ here It contains a brief description of all the useful APIs provided by dlg Please look at the report... Thanks, Priyesh On Thu, Jun 25, 2020