austinenglish at gmail.com
Fri May 29 10:14:47 CDT 2009
On Fri, May 29, 2009 at 10:10 AM, chris ahrendt <celticht32 at yahoo.com> wrote:
> Question on this debate:
> Has AJ documented anywhere what the architectural issues are so they can
> be addressed?
> I have not seen this in the thread and was just wondering.
> If we have them documented then its a relatively easy task to address
> each of them.
> Yes it may be a hack but you would be surprised at how much of Windows
> is a hack internally.
> Do we even have an architectural document or guidelines to reference?
If you read the entire thread, you'll see that the DIB design is not a
puzzle that can be carved out and dropped in. The DIB engine must be
designed from scratch. Designing the DIB architecture is half of the
work itself, since that involves planning a lot of the code/testing,
He pointed out a few things he didn't like about Massimo's design, but
not a full 'here's the spec, do this exactly'.
For more details, read the full thread and past discussions.
More information about the wine-devel