[Fontforge-devel] FontForge's next 3 months

[Dave C. <da...@la...>]

On 22 December 2012 13:02, Matijs van Zuijlen <ma...@ma...> wrote:
> On 21/12/12 11:11, Dave Crossland wrote:
>> On 21 December 2012 09:14, Matijs van Zuijlen <ma...@ma...> wrote:
>>> The library contains calls to the likes of ff_progress_start_indicator, i.e., it
>>> depends on a _global_ struct ui_interface to be present and filled with sensible
>>> values. This means the library very much dictates the kind of UI that is written
>>> on top of it.
>>
>> Okay. How much work do you think it is for a full time competent C
>> developer to refactor the whole library?
>>
>> 1 week, 1 month, 6 months, 12 months?
>
> It's probably hard to make someone work on only this task full-time; there's a
> lot more restructuring that could happen at the same time.
>
> That said, given the above four options, I would guess about a month. In that
> time, it should be possible to remove all use of ui_interface and similar
> structures as global variables, and pass them to the functions that need them.
>
> (On the other hand, C is not my main programming language, so I might be way off).

Okay cool. If its just a month, that seems like a reasonable goal for 2013.

I think what I want to contribute to FontForge over the next 3 months is,

1. automated daily builds of installation packages, so up-to-date FF
is easy to install on all platforms

2. launch the new website

3. include a crash reporter so that whenever segfaults occur, the user
is asked to send the information needed to fix that crash to us, so we
can make FF much more reliable