Hi all,
On or about September 2006 I was asked by Aleksey (PC) and Alex if I could head up
the win32 and gdi32 part of the rewrite. The discussion had taken place on irc. It
was important that the rewrite would have one developer working alone (preferred
method) or be the leading developer working with a small group of developers (no
more than three). The rewrite was needed so that this section of ReactOS would be
compatible with the new kernel and the very thing we are trying to do. Be
compatible. This included interfaces, structures and the data that was contained in
those structures. Just not only that, also dropping in the place of drivers and
dlls, the real thing and still be compatible. Yes! Running with ReactOS.
I do not recall any requirement for me to write a technical manual or any kind of
web wiki. Even a How-To-Black-Box an OS interrupt calling hooky thingy with kmtest
driver callback winpooch as an application interface. ReactOS developers should have
a healthy tool box.
This point on, the discussion is over. I have a job to do. I would like help and not
debate everything I do. Some of you, need to, really think about, the future of this
project. How can I help with this and how can I help make this work for
compatibility with the very thing we are working toward. If you are thinking about
something new and different other than something innovative, compatible and helpful?
Maybe this project is not for you. Aros, FreeMint, Linux, Syllable, Visopsys, X,
etc, these projects might be what you are looking for.
If it breaks compatibility with interfaces and data stored in structures? I will
reject it and post an email why it was rejected. Wine is not enough, okay?
Thanks,
James
Show replies by date