On 02/09/2009 02:04 PM, Milosz Derezynski wrote:
Hmm the feedback was just generally, if there are any comments on the plan or whether something should be added, or if someone else is already working on something that i've proposed. But it seems the contract is now almost finalized so this point is moot. I also think now Mr. Dexter was more speaking about peer review of the code (which of course will happen naturally, I think best would be working in an SVN branch?).
No one is currently working on the items mentioned that they've announced (at least not that I recall seeing). As for peer review of code, I'm sure it will not be an issue. With regard to best place to work on it, if you are looking for peer review or testing throughout the process it would be good to do in a branch until it is functionally equivalent to (or better than) what's in trunk. Basically the key is not losing any functionality in trunk... so if you could even work on it there and perhaps have a config option to compile it with your stuff instead (thus not breaking normal functionality), I don't think anyone would have any issues with that option either.
I'm going to write very generic code, it's just the way I write stuff these days. Not absurdly abstract APIs but generic enough so that e.g. the dropdown can be used independently of whatever provides the actual font previews, and so on (have an enumerator/adaptor interface that bridges a specific library for providing the fonts, with the list widget). With this I hope that the dropdown could be maybe reused in the future for other projects that don't use libnrtype, and so on.
Sounds good. :)
Cheers, Josh