Svensters blog

Tuesday, December 29, 2009

It's a toss up

It's a toss up, originally uploaded by sprevrha.

Cookie or lego train?

Sunday, December 13, 2009

Huge newspaper glider

Huge newspaper glider, originally uploaded by sprevrha.

In case you didn't know it: the Americans have the biggest of everything and it friggin flies the moon man!
350 ppm now!

Friday, December 04, 2009

Anton' school fund raiser

Anton' school fund raiser, originally uploaded by sprevrha.

You can't see it but the penny box is magic - the coins simply disappear!

Saturday, November 28, 2009

Bust!

Bust!, originally uploaded by sprevrha.

And boom! He exploded back out of it!

Tuesday, November 24, 2009

Tim Heuer's Silverlight 4 collection

http://timheuer.com/blog/archive/2009/11/22/pdc-silverlight-resources-link-dump-learn-silverlight.aspx

Just watched the new MEF shipping with Silverlight 4. kind of confusing, I'd better read up on or watch a different video: http://development-guides.silverbaylabs.org/Video/Silverlight-MEF#videolocation_0 talks about "Separation of Concerns": http://en.wikipedia.org/wiki/Separation_of_concerns . The big idea behind MEF seems to be that one can instantiate objects - from the extremely simple such as a string to very complicated such as a database access object - by referencing an object external to the code, say in a different Silverlight App, instead of explicit instantiation by "new". MEF ties the instantiation and the external object together by a string token: The exporting module uses a [Export("MyObject")] decoration above the instantiation, the importing module a matching [Import("MyObject")]. When the import is triggered, the instantiation pointed to by the "Export" happens. This allows the concrete implementation of the needed type to be separate and outside of the core code, and therefore easily extensible and changeable. How does MEF find the right package? The magic seems to be in the PackageCatalog class.