Rockford Lhotka – Why Silverlight is the future
I was going to argue against Silverlight being the future, but yesterday my reserved copy of “Beginning Silverlight 2:” came in at the library and my copy of “Silverlight 2 in Action” arrived in the mail. So maybe the Colossal Cosmic Anvil of Fate is dropping [...]
Regarding the possible availability of Silverlight on the Linux platforms
if you can’t make your mind up,
we’ll never get started.
and i don’t wanna wind up
being parted, broken-hearted.
so if you really love me,
say yes.
but if you don’t, dear, confess.
and please don’t tell me
perhaps, perhaps, perhaps.
(I’m sure some British Linux fans are getting a chuckle at that [...]
I’m giving up on Silverlight development, at least 1.0 development. It’s pretty obvious that NO ONE is going to ship anything based on Silverlight 1.0. Personally, since Silverlight 1.1 won’t work on Apples PowerPC machines, that means that any Silverlight 1.1 code I write won’t work on my main laptop (G4 iBook).
Why write code [...]
I'm looking at the SilverlightPad example for the 1.1 alpha version of the plugin. Has anyone else noticed that pretty much all XAML code exhibits the arrow anti-pattern?
PLAIN TEXT
XML:
<!---
///////////////////////////////////////////////////////////////////////////////
//
// blocks.xaml
//
//
// 2007 Microsoft Corporation. All Rights Reserved.
//
// This file is licensed as part of the Silverlight 1.0 SDK, for details look
// here: http://go.microsoft.com/fwlink/?LinkID=89144&clcid=0x409
//
///////////////////////////////////////////////////////////////////////////////
-->
<Canvas xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" Height="500" [...]
John Lam has posted a "gathering of facts" about Silverlight and the DLR. His #9 on the list was the one I was most interested in.
"Silverlight V1.1 will only target Intel Mac OS X machines."
That's pretty disappointing to me, but not unexpected. My bet is that this will slow, to a crawl, adoption of [...]
This thread at the Silverlight forums confirms what I found while playing around with Silverlight 1.0 Beta.
If you are using "Namespaces" to segregate your Javascript code in your Silverlight application, you can't use the nested methods as handlers in your XAML page.
PLAIN TEXT
JAVASCRIPT:
player = {
stop : "",
play :""
}
player.stop = function(sender,args) {
[...]
