Christian Gmeiner [mailto:[EMAIL PROTECTED] wrote:
> Okay i think this project can be done by one student, because we can use the
> SDK for our work. We can take all API prototypes and build our own SDK based
> on the original SDK.
> We are only not allowed to share the original source files, bu
Hi all.
Okay i think this project can be done by one student, because we can use the
SDK for our work. We can take all API prototypes and build our own SDK based
on the original SDK.
We are only not allowed to share the original source files, but we are allowed
to make them by our own by lookin
Hi Tom,
On Tuesday 25 Apr 2006 19:05, Tom Spear wrote:
> On 4/25/06, Paul Millar <[EMAIL PROTECTED]> wrote:
> > Yes, this looks to be amenable to a clean-room implementation. [...]
>
> I don't see any reason why that couldn't work. We could combine that test
> suite with users that use various pr
On 4/25/06, Paul Millar <[EMAIL PROTECTED]> wrote:
> Hi Tom,
>
> Yes, this looks to be amenable to a clean-room implementation.
>
> This could involve two students: one activity would be to write a document
> describing the API and write a suite of functional tests that "define"
> correct behaviour
Paul Millar wrote:
Hi Tom,
On Tuesday 25 Apr 2006 19:05, Tom Spear wrote:
On 4/25/06, Paul Millar <[EMAIL PROTECTED]> wrote:
Yes, this looks to be amenable to a clean-room implementation. [...]
I don't see any reason why that couldn't work. We could combine that test
suite wit
On 4/25/06, Tom Spear <[EMAIL PROTECTED]> wrote:
>
> If I am reading what you said above, you basically want to for example, take
> fruity loops, figure out what it does when you do various things (by tracing
> that app's execution), then using that trace, write our own code to produce
> an _identi
On 4/25/06, Paul Millar <[EMAIL PROTECTED]> wrote:
Hi Tom,Yes, this looks to be amenable to a clean-room implementation.This could involve two students: one activity would be to write a documentdescribing the API and write a suite of functional tests that "define"
correct behaviour of the API; the
Hi Tom,
Yes, this looks to be amenable to a clean-room implementation.
This could involve two students: one activity would be to write a document
describing the API and write a suite of functional tests that "define"
correct behaviour of the API; the other activity would be to use the document
Willie Sippel wrote:
Am Dienstag, 18. April 2006 11:56 schrieb Christian Gmeiner:
What is ASIO?
ASIO is a driver interface for pro-audio apps developed by Steinberg. It's
somewhat similar to our beloved Jack sound server, but not as advanced.
I thought about implementing ASIO for wine so we
Am Dienstag, 18. April 2006 11:56 schrieb Christian Gmeiner:
> What is ASIO?
>
> ASIO is a driver interface for pro-audio apps developed by Steinberg. It's
> somewhat similar to our beloved Jack sound server, but not as advanced.
>
> I thought about implementing ASIO for wine so we are one step nea
10 matches
Mail list logo