First time here?

You are looking at the most recent posts. You may also want to check out older archives. Please leave a comment, ask a question and consider subscribing to the latest posts via RSS or email. Thank you for visiting!

i saw over in the township of adam kinney that someone came up with a version of the sIFR concept.

for those who don't know, (scalable inman flash replacement) in simplest forms is a method for using css to annotate elements of text that you might want replaced with higher-quality/different/pick-your-word-of-choice typography.  it provided a method on sites to essentially say "hey if javascript is enabled and flash is installed, replace this plain text header with some whiz-bang custom font to make the user say ooooooooohhhh yea" or something like that.

filipe fortes, who apparently used to work on the wpf team himself, wrote a silverlight version of that methodology as a test of sorts i guess...turns out it looks pretty good.  he calls it sistr and is implemented by including one javascript file and a css class name.  looks like it is implemented using the downloader object in silverlight as well so it provides an "as needed" approach.

why should you care?  well, that's up to you.  but one thing sIFR solved (or attempts to) is those questions on accessibility with rich content.  since the text you are replacing is still there, it should present a more accessible site in the event you needed that (i.e., text readers, etc.).  of course ymmv on your particular implementation.

Sistr: Rich accessible typography in Silverlight

pretty cool.  the sample indicates that hyperlinks work, but i didn't see it working in the sample...maybe a slight bug, but great start nonetheless.


The opinions/content expressed on this blog are provided "ASIS" with no warranties and are my own personal opinions/content (unless otherwise noted) and do not represent my employer's view in any way.