From: Kustaa N. <Kus...@pl...> - 2011-07-17 19:09:06
|
On 7/17/11 19:41, "Travis" <tra...@co...> wrote: > >Not to put more words in peoples mouths but it seems you are both saying >the same thing. ;) > >I think figuring what these API potos will need to look like and the >flow as-to how they will be called is the hard part. After this is >figured, Writing the actual windows source code is probably not a big >deal. > >Are you not both essentially saying this? I don't think they are saying the same thing. Not wanting to put words to anyones mouth, I think Peter is saying that it is (more) difficult to figure out the design than to code it, but that it can and should be done without coding. Pete is saying that without the code we will not realize certain mistakes in the design until we code it, and there fore we should code in parallel with the design. I have to say I agree with Pete. RERO. When you have code there is no ambiguity about what the direction is and what is being done/discussed. So RERO is a great way to enhance communication, unlike endless mailing list threads. Also great way to find out fatal flaws. Pete gave a telling example of callbacks for 3.0. Is going to be callbacks or not? I don't know, who knows? If we had code we knew that it is going to be callbacks (or not) and we could then discuss this and revert that design decision (or not). Pete also gave an other telling example about the horizontal line issue in an other project. Exactly what *will* happen when you don't code and share early. br Kusti |