Yesterday, I was at BarcampGhent. The first one, ever. Since the concept of Barcamp is that participation (in whatever way) is key, I gave a presentation on my n00b findings on Silverlight, the DLR and Ruby.
You can check out my presentation here, although it’s not telling the whole story without me doing the talking:
Suppose you have a MasterPage with two ContentPlaceHolders, and you need to reference a control from one ContentPlaceHolder in a control in the other ContentPlaceHolder. You can’t use the normal control id, since ASP.Net will complain that it can’t find the control living in the other ContentPlaceHolder.
The solution is very simple: just prefix the referenced control id with the id of the ContentPlaceHolder it’s living in, seperated by a $ sign. Like this:
SomeContentPlaceholder$SomeReferencedControl
And now ASP.Net will happily find the control and continue it’s business as planned. It even works for UpdatePanels across different ContentPlaceHolders.
For example, you have a form in a left ContentPlaceHolder, but you want to display the validators in another ContentPlaceHolders. Here’s how to do that:
First one, wp-fancyzoom, is one that I had developed a while ago. It’s basically a simple wrapper around Cabel Sasser’s FancyZoom, which enables fancy zooming effects on links to images on your blog. Great for displaying larger versions of thumbnails, for example.
Second one, wp-deredactie-embed-fix, is a simple filter plugin that fixes the embedding code of deredactie.be videoclips. Most of the time, these work okay but fail when an editor puts quotes in the description or title of the clip. This plugin fixes that.
More info (and a download links) at the plugin pages.
Looks like they caved in. Oh well, my previous points still stand: it’ll all depend on how good IE8 implements its standards mode. If that implementation is good, all will be fine. If it’s bad, the opt-in approach would have been better. And I’m still not sure that all the developers yelling “Thank you!” now will be so happy in a few years. We’ll see.
But hey, since they (MS) seem confident about this, I assume IE8 will rock.
And you know what would be awesome: support Firefox extensions in IE. Without the memory leaks. I know, that won’t happen, but I’d dump Firefox for it, I think.