Will MIL ever be documented?

I see in this article:

http://www.simplegeek.com/PermaLink....6-0c5e7beae66b

"MILCORE.DLL is the unmanaged composition engine that Avalon uses for
rendering. It is a layer above Direct3D, giving us basic 2D, 3D,
Animation, and Composition services (probably a few others i'm
forgetting to mention also). The composition engine is unmanaged
primarily for interop/performance reasons. The composition engine spends
most of it's time talking to Direct3D. In addition, there are multiple
customers of the composition engine, including some that can't take a
managed code dependency right now. "

The key interesting line for me is the last one. It prompts the
question:

Will MIL ever be documented so that us plebs who can't take a managed
code dependency can still take advantage of the retained-mode
composition engine underlying WPF?

Or is this reserved for MS applications only?

-- Barry

--
http://barrkel.blogspot.com/

The part of the MIL that has unmanaged exposure is the imaging
functionality.

-Pablo

"Barry Kelly" <barry.j.kelly@gmail.com> wrote in message
newsf69a2tc0nc2kkc2tt9el01qgni73423h6@4ax.com...
>I see in this article:
>
> http://www.simplegeek.com/PermaLink....6-0c5e7beae66b
>
> "MILCORE.DLL is the unmanaged composition engine that Avalon uses for
> rendering. It is a layer above Direct3D, giving us basic 2D, 3D,
> Animation, and Composition services (probably a few others i'm
> forgetting to mention also). The composition engine is unmanaged
> primarily for interop/performance reasons. The composition engine spends
> most of it's time talking to Direct3D. In addition, there are multiple
> customers of the composition engine, including some that can't take a
> managed code dependency right now. "
>
> The key interesting line for me is the last one. It prompts the
> question:
>
> Will MIL ever be documented so that us plebs who can't take a managed
> code dependency can still take advantage of the retained-mode
> composition engine underlying WPF?
>
> Or is this reserved for MS applications only?
>
> -- Barry
>
> --
> http://barrkel.blogspot.com/

Hmm, I wonder why not milcore documentation available.

Is it just another Microsoft attempt to push managed code? I don't know how
to tell this politely, but there are still developers who hate all that slow
managed thing...
Unless of course Microsoft think that only their employees can use lower
level APIs and the rest of us are only able to ...play "safely" !

Sakis

I very much doubt this is the case. More likely, they are focusing on a
single external api (the managed one) right now (for v1), and once they have
that out in the wild they will clean up the unmanaged api and support that
externally as well.

Its easy to forget that they dont have unlimited resources to and its not
always possible to support everyones favorate feature.

I'm glad they didn't make yet another unmanaged api with a flimsy managed
wrapper. WPF is built to utilize the great features of managed code and I
think this is a good thing.


"Sakis Papademetriou" wrote:

> Hmm, I wonder why not milcore documentation available.
>
> Is it just another Microsoft attempt to push managed code? I don't know how
> to tell this politely, but there are still developers who hate all that slow
> managed thing...
> Unless of course Microsoft think that only their employees can use lower
> level APIs and the rest of us are only able to ...play "safely" !
>
> Sakis