81–90 of 142 posts
What will Microsoft do for 3D on the web, then? They've said the won't implement WebGL and Silverlight 5 + XNA was supposedly their solution.
Earlier quoted context omitted.
Oh, so everybody should just do HTML no matter what, from now on, for ever and ever, amen? Nobody should ever invent a competing technology because HTML is good enough for you? Is that it?
> Nobody should ever invent a competing technology As long as this technology is easy and free for everyone to implement in compatible ways, yes, you can.
Good riddance! I spent the last 5 months at a gig working on a massive Silverlight 4 application. I've been a web guy forever, but I took this job thinking it would be good to learn how the other half lives. After experiencing the pain and drudgery of working with Silverlight, I couldn't be happier that it's going away. The most maddening part of working on a Silverlight app was that things that are dead simple with…
Interesting... I as a Silverlight dev now learning JS/HTML/CSS would say the complete opposite. I find it very difficult to create similar layout functionality like DockPanel and friends. Any tips?
As far as tips - vertical stack panels are just a series of unfloated divs (or other block element). Horizontal stack panels are a series of floated divs.
Vertical positioning with HTML/CSS can be tricky, especially in older browsers. line-height and padding/margin are you friends :)
Earlier quoted context omitted.
I don't see anything particularly remarkable there. http://www.trirand.com/blog/jqgrid/jqgrid.html
Is pagination of the data (as shown in those examples) mandatory? It seems kind of annoying to have to limit the amount of data actually in the browser at one time, especially if it's done for "performance" reasons.
Earlier quoted context omitted.
> Nobody should ever invent a competing technology As long as this technology is easy and free for everyone to implement in compatible ways, yes, you can.
"You can" implies that you have some sort of say in the matter. Why should everyone have to implement technologies that are "easy and free" just because you say so?
Good riddance! I spent the last 5 months at a gig working on a massive Silverlight 4 application. I've been a web guy forever, but I took this job thinking it would be good to learn how the other half lives. After experiencing the pain and drudgery of working with Silverlight, I couldn't be happier that it's going away. The most maddening part of working on a Silverlight app was that things that are dead simple with…
I see your gripe with the REPL loop and binding but . . . Would you be willing to share what was easy with HTML/CSS/JS that was tons of work with SL and what gymnastics you had to go through? I'm genuinely curious.
Further, text wrapping and layout were my biggest pain points in SL. I wasn't used to having fixed dimensions on everything. That really bugged me.
Finally, I didn't like the visual state manager at all. There's not really an analogous equivalent in JS/HTML, but for a "rich" internet platform it certainly didn't seem like the way to go to me. I have to run now, but I'll try and think up some more of my pain points and edit as appropriate.
Earlier quoted context omitted.
Incorrect. Silverlight runs out of browser.
Oh... You mean using Silverlight for intranet applications without a browser... That's an interesting idea. Allow me not to take part on it.
Earlier quoted context omitted.
Interesting... I as a Silverlight dev now learning JS/HTML/CSS would say the complete opposite. I find it very difficult to create similar layout functionality like DockPanel and friends. Any tips?
You know it's interesting that you're seeing lots of pain going the other way. I realized part of my issue with Silverlight was just how different it was from what I was used to. I don't like things I don't understand :) That being said, I did like the Stack Panel and the Dock Panel. I liked them because they worked more closely to the way HTML layout works. It was the Grid that I despised. The markup was tough to fo…
I found this a couple of weeks ago, and it seems like it might be useful: http://www.w3.org/TR/2009/WD-css3-flexbox-20090723/ Demo: http://www.html5rocks.com/en/tutorials/flexbox/quick/ I wanted to post this for anyone who stumbles across this info via search.
People who relied on the Silverlight plugin certainly cannot continue to develop it, either.
Long-run, there's more security in relying on software created by a sufficiently large and capable community of enthusiasts. Such software will never die if it's good enough to be useful - sunk costs, NIH, and all that.
The "strategic direction" of a community won't change except by consensus. People will enter and leave. By the time the community withers and dies, nobody cares any more.
Earlier quoted context omitted.
I see your gripe with the REPL loop and binding but . . . Would you be willing to share what was easy with HTML/CSS/JS that was tons of work with SL and what gymnastics you had to go through? I'm genuinely curious.
For one thing, with Prism, binding events to view model methods was a giant pain, specifically if you wanted to pass event args. I know I ended up having to write a number of attached properties to handle different event binding scenarios. With jQuery it's a cinch to handle user interaction. (I guess my major gripe in this case is with Prism, which is perhaps separate from SL). Further, text wrapping and layout were…
We can ignore your Prism complaints because that was simply your choice of MVVM frameworks as you mentioned. MVVMLight supports passing event arguments to View Models quite easily.
You didn't mention what you didn't like about the VSM, but even there, you didn't have to use it.
Lastly, layout...of all things, is done absolutley right in Silverlight compared to the non-intuitive HTML way.