Re: GSoC | Improve the ‘ftinspect’ demo program

[zubin choudhary]

Awesome, thanks!

I did check Veeki's commits I couldn't find a lot.
I guess it would be better if I rollback to his commits and try to implement.
I compiled freetype on my device and I'm still getting used to the codebase.
once I'm a little confident I'll ask you about more stuff maybe.

are there any special requirements before submitting the proposal?


Thank you

On Wed, Mar 11, 2020 at 7:58 PM Werner LEMBERG <address@hidden> wrote:
>
>
> Hallo Zubin,
>
>
> > I'm a Google Summer of Code 2020 aspirant and I am interested in
> > this project.
>
> Great!
>
> > I do have a little experience in C, C++ and Qt framework.
>
> OK.
>
> > I just cloned the freetype-2 demos and wen't through the last years
> > commits.  are there any commits that I should work on?  how should I
> > start contributing to this project?
>
> Have a look at the branch `veeki-gsoc-experimental`, which contains
> the stuff Veeki has added last year; there are also some progress
> reports on the `freetype-devel` mailing lists.
>
> There are many problems with Veeki's contribution, which you can
> certainly detect by yourself.  In particular, most of the stuff that
> is shown in plain windows full of typewriter text should be presented
> with menus, checkboxes, tabs, etc. to simplify navigation, and to get
> a more compact view.
>
> You should also play around with the FreeType demo programs (in
> particular `ftview`, `ftstring`, `ftmulti`, and `ftgrid`) to get a
> feeling of what FreeType does and how it works.
>
> However, it's completely OK if you ignore the veeki branch, starting
> again without any distractions from last year...
>
> If you want to contribute just send patches :-) If you want to write a
> proposal, please read Google's guidelines for that and ask questions
> on this list.
>
>
>     Werner