Re: [MiNT] WCOWORK vs WINDOM for components

["Joakim Högberg" <gokmase@gmail.com>]

>Well... if you had have a look at windom, then you saw that windom already
>propose a "frame" API that answers all your needs. With the windom "frame"
>feature, you can develop an application that open a framed window, with QED in
>one frame and HW in the other. The mechanism is already here. The "long road"
>target you plan for xaaes is something that already exist for years thanks to
>windom. Developpers just have to use it !

One thing to keep in mind here! Not everyone is:

a) Coding in C
b) Using Windom

I don't doubt it is a nice feature of Windom, but Windom ain't the only possible route to
take when creating applications.

>In other words, what you tried to introduced in xaaes is a feature that already
>exist for years in windom.

See above.


The WCOWORK implementation will IMO be a very nice and clean implementation.
Developers just have to use it.


/Joakim