mdx4ever> from what i have seen of silverlight, its not diffucult. the problem i see with it is that not a single media format supported by it is patent-unencumbered most of silverlights functionality is similar to stuff i have been working on - and if i can do it, i'm sure novell can too =-= m4rc05 is now known as m4rc05|cod i can already tell you what the problem areas will be because i already had them |<-- nags has left irc.gnome.org (Ping timeout: 600 seconds) Yes, the media is the problem So we will likely have to use Fluendo And you will likely have to buy the codec on your own mdx, would love to hear about them =-= nags_ is now known as nags My question right now is how much is running in unmanaged code, and how much managed WPF at least had a model where the managed side built an execution list, and passed it to unmanaged So all the rendering and updates were handled there And we need to sort out the threading model/application model |<-- Urriellu has left irc.gnome.org (Remote closed the connection) |<-- slomo has left irc.gnome.org (Ex-Chat) -->| javamaniac (gerardo@200.84.165.64) has joined #mono -->| shana_ (~shana_@62.169.103.226.rev.optimus.pt) has joined #mono -->| uFo-Z (~ufoz@p57B2DBEA.dip.t-dialin.net) has joined #mono the only thing that really needs to be native is the video/audio codec stuff. you can write that managed but performance sucks: for my media layer i opted to not use fluendo/gstreamer because it made cross platform too diffuclut... the silverlight stuff doesnt need all of gstreamer so your better off passing pointers to libvorbis, etc and pinvoke this gives you portability: your primary convern since you guys license mono, make it as friendly as possible for embedders the less native they have to write, the happier they will be so you really want to work backwards on this one, start managed then go native where necesarry