In message <[EMAIL PROTECTED]>
Adam Blokus <[EMAIL PROTECTED]> wrote:
> [...]
> As you can see - the plans for the first three weeks are quite determined,
> but
> the time of the latter two is flexible and open for your ideas and
> propositions - let me know if any of you has any requests :)
That's looks like a sane plan. I'm fine with it.
I'm not sure if there is much room for throwing in another item which was
mentioned in the original project proposal, i.e. think how your code is
going to be tested. Of course initially manually creating PDF files and
verify in a PDF reader but I'm wondering how we can ensure that your code
(and things like your looosing code) remain behaving in the future, i.e.
detecting potentional regressions.
IMHO a more systematic and (semi)automatic testsuite would actually be an
area where NetSurf could improve on and benefit hugely when doing bugfixes
and refactoring code.
You see this reasonably possible to take this up ?
Thanks for sharing your plan Adam,
John.
--
John Tytgat
[EMAIL PROTECTED]
