What are we doing?

[JamesM]

What is this EDI?

Extensible device interface. It's a driver specification that Crazed123 (Eli Gottleib) came up with to try and help interoperability for device drivers between hobby OS's.

I've hosted the specification he made over at my website, here.

I don't think anyone else supports it yet, but I'm hoping to set a (good) trend

[Dex]

I voted for Team (5+ people) as DexOS is a team effort, i am just responsible for the kernel.
I know a OS is never finished, but now DexOS is very usable, so must of my work from now no, will be making program to run on my OS.

[AJ]

I don't think anyone else supports it [EDI] yet, but I'm hoping to set a (good) trend

I'm going to be supporting it with my kernel too. Unfortunately, that bit is such a long way in the future, I don't consider myself part of that trend yet

Cheers,
Adam

[JackScott]

As soon as anybody writes a half-decent EDI implementation, I'm going to start pumping out open-source EDI drivers. That'll help everybody at once!

[JamesM]

As soon as anybody writes a half-decent EDI implementation, I'm going to start pumping out open-source EDI drivers. That'll help everybody at once!

I'm intending to, very soon. It'll be with the release of pedigree 0.1.

OOI, I was planning to extend EDI slightly to give access to a standardised range of containers, e.g. resizeable vectors, hashtables etc, to avoid code repetition. What do you think of that?

[JackScott]

Well, the idea is that it is extendable...

I think it's a great idea. I'd be careful not to include the whole standard library in there though, that would just cause too much bloat.