Right, and I would agree that desklets are a nifty way to share sandboxed code. My point was more a caution against trying to undo Silverlight/Moonlight's reduction. It's one thing to add additional controls, quite another to start messing with the networking support. The security implications could be tragic ;) It may interest you to know that folks have already created Silverlight gadgets for Vista's sidebar including, IIRC, gadgets that are remotely hosted.
________________________________ From: [email protected] on behalf of Miha Valencic Sent: Fri 12/26/2008 12:48 PM To: Discussion of IronPython Subject: Re: [IronPython] DLR, OS X/Linux & other languages [I hope this is not too off-topic...] What is wrong? Nothing I guess -- if you have full WPF at the other end. Probably WPF (or WCF in my example) is not the right example -- due to dependencies further down the road. Reduced set or not, you will end up with extensions/additions to base class library. You have extensions/additions with SL as well -- be it custom UI controls or some other backend libraries that make your life easier. (it is the same with desktop development). So you end up bringing those libraries along with your apps. Now the point of my ... writing/thinking is not how to bring in additional DLLs but how far are we from having the Silverilght programming model (with DLR + CoreCLR + XAML) with the whole extensibility model as a [lightweight] desktop programming model as well? So that, regardless of my platform of choice (Linux, OS X, Windows XP/Vista/7?), I can develop apps in the language of choice (be it a dynamic beast or a statically typed beast or something in between :)), and have it run on multiple platforms -- and on the web. Basically, we would need an environment to run Silverlight applications on the desktop as a "first class applications" with access to the full .NET/Mono/xy API where applicable. Something like desklets apparently deliver[1]. It seems pretty awesome to me that I would be able to choose the language and have a great tooling support (UI controls, BCL subset..., VisualStudio) and that I could develop for the web and for the desktop using the same technology and paradigms. Miha [1]: http://www.davidarno.org/2008/04/21/mono-team-to-microsoft-build-moonlight-desklet-support-into-silverlight/ 2008/12/26 Keith J. Farmer <[email protected]> What's wrong with targetting a full WPF host (assuming that Mono's WPF support is sufficient at the time)? Either stick to the reduced set or not. Don't try to turn the one into the other :)
_______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
