comments edit

Vallarta So the missus and I are heading over to Puerto Vallarta this Sunday for a short mini-vacation. For me it is a chance to recover from Mix06. It was kind of unfortunate that the two events are so close together, but that was pure coincidence.

We are staying at a nice small bed and breakfast and looking forward to exploring the local area, lounging on the beach, and generally enjoying an itinerary and agenda free few days. I am not bringing a computer so I will be totally disconnected, which will be a nice feeling.

I think.

I do get a bit panicky without my blogs after a few dayshours minutes, but the missus promises me I will be ok.

comments edit

I was involved in a 5 AM breakfast conversation (a little late night snack before we all turned in for the evening) with Clemens Vasters, Steve Maine, and some others at Mix06 in which they explained how streaming content works with WCF (code named Indigo).

They pointed out (as I mentioned in a tongue-in-cheek context in my last post) that with streaming content such as streaming videos, the consumer of the media is really concerned about headers and start tags, because they plan on using the content as it flows over the wire.

In effect, streaming works because WCF promises to send the end tags eventually. Might be hours from now. Might even be years from now. But they will get sent and the message (as everything is a message in WCF) will be well formed and complete.

Clemens then pointed out that even if they never did send the end tags, what would it matter? The consumer of the feed, if he or she is exceedingly anal, could decide to throw an exception then. But at that point, the content has already served its purpose and has been consumed. Remember, we are talking about the streaming content use case.

This struck me with two thoughts. This is a software scenario where the intent is more important than the execution. The fact is that they intend to send the end tags is very important, but whether they actually do or not is of less importance.

Secondly, with streaming content, the valuable deliverable is not a whole message but a partial message. By message I mean the entire content and whatever SOAP envelope it may be wrapped in.

Of course, the key to streaming content producers is to make sure to send any meta-data and commercials at the beginning of the message and not after the streaming part. But you knew that already. ;)

comments edit

UPDATE: Ok, so being away from RSS Bandit has put me out of touch of some of the other discussion on this topic. As Dare writes, Don isn’t the first person to make the Lo-REST distinction.

Sleeping TigerWell it looks like Dimitri beat me to the punch. It also struck me as odd to hear Don Box coin the term Lo-REST. It also struck me to hear it repeated at Mix06 and described as really just POX over HTTP. I had an interesting conversation with Steve Maine (who is one cool cat by the way) about it at Mix06 that got me thinking.

The thing is, REST is an architectural style, and to some degree it is well defined. What is not well defined is exactly how you build real world web services using this style. If you perform a search for the term “xml” within Roy Fielding’s Dissertation (pdf) you will find zero matches. REST does not require nor really have anything to do with XML. However, XML is a viable tool that can be used with a RESTful service.

Now Don is a very smart guy and I have immense respect for his work. I am more likely to second guess myself before I disagree with him. This is why I want to give him the benefit of doubt and try to look at what he was trying to accomplish in this post, though I obviously can’t speak for him so this is mere conjecture. The question I have is whether Don is “prescribing” or “describing”.

It seems to me that rather than try and prescribing a new form of REST, he was merely describing the reality of service oriented implementations that exist in the real world. Fact of the matter is that many companies are unveiling RESTful services that end up being nothing more than attempts to tunnel REST verbs through HTTP GET (Amazon is one example).

The problem is that if this is indeed the case, I can see the usefulness of the term from an academic viewpoint. Lo-REST can usefully describe what services that are labelled as REST, but are really not. Rather, these services are actually POX based services.

Even so, attaching the term REST to a POX service is problematic in two key ways (if not more). First, it dilutes and obscures what REST is, which not only gets the RESTafarians all up in a tizzy, but also can make the conversation around this topic more difficult. Second, it seems to undercut the significance and usefulness of POX by implicitely indicating that POX needs to be attached to the term REST in order to be taken seriously.

Ideally, we should take a step back and realize that significant web services are being written and will continue to be developed using POX. Let’s elevate the respectability of the term POX a bit and retire the term Lo-REST. It is POX, let’s leave it at that and call it what it is.

DISCLAIMER: I am not what you would call a RESTafarian. I think I understand what REST is, but I am on the fence on whether web services SHOULD all be implemented as REST. I tend to take a more pragmatic approach and think that some services will benefit from a REST style approach and others will benefit from using SOAP. What I do care about though is that for the purposes of the grand debate, that we keep our terms clean and as well defined as we can and not dilute what one or the other is.

comments edit

My Wife! The comedienne. Honey, still don’t quit your day job.

Exhibit One: My post on Mix06 in which I mentioned…

Maybe, if things are going well, I might have a date with destiny at the Let It Ride tables.

Her comment…

destiny called. she now works at the crazy horse. ; )

Exhibit Two: My recent and slightly rambling post on Lo-REST in which I talk about REST and POX over HTTP. Near the end I state…

Lets elevate the respectability of the term POX a bit and retire the term Lo-REST. It is POX, let’s leave it at that and call it what it is.

And her comment in response…

yes. Lets elevate the respectability of the term POX.

Finally, my wife is taking an interest in the work that I do. I am sure she’ll now enjoy a long and intellectually stimulating dinnertime conversation as I explain to her how streaming content works with IndigoWCF. As long as the start tags are all correct, you can consume the streaming content relying on the intent that the end tags will arrive some day in the future. And if they don’t arrive, will you care as you have already consumed the content? With streaming content, the valuable deliverable is not a whole message but a partial message. Discuss amongst yourselves.

comments edit

It is unfortunate that I haven’t been able to blog much about the Mix06 conference so far, as there is so much worth writing about. Unfortunately I have acquired a bad cold on top of a splitting headache that will not go away. Such is the price one pays when partying with the hard charging Microsofties (particularly with such Indigo team members such as Steve Maine and Clemens Vasters).

When I get a chance, I will write more, but I wanted to drop a note in here about Microformats. With Bill Gates on stage saying that “We Need Microformats”, there is a pretty good chance that Microformats are here to stay.

I attended a Birds of a Feather (BOF) session on Structured Blogging and Microformats with Tantek Çelik and Marc Canter

I asked a question on whether or not there is an autodiscovery story for Microformats. Consider how an aggregator finds an RSS feed for a site. In general, the aggregator scrapes the HTML looking for a several common indicators of an RSS feed. Ideally the web page adds a <link /> tag using the RSS autodiscovery format.

But I am not aware of any such mechanism for discovering my Microformat contacts. Let’s say that I do not want to have all my contacts on my home page. How would an aggregator find my contacts short of spidering my whole site. Tantek’s answer was that they are essentially working on it and there is nothing set yet.

One problem he pointed out is that sites may end up hosting a large number of microformats. Adding an autodiscovery link in the HEAD section of a page for each format supported could get unwieldy. One idea I had would be to work on a “Table of Contents” microformat (I am sure someone else will have a better name) that would serve as an index for where my site hosts certain microformats of interest.

This would be an optional format. For example, for a site that uses very few microformats. The site can make do with autodiscovery links within the HEAD section of the home page. But if the site uses an exceedingly large number of formats, it could have a single autodiscovery link to the page that contains the Table of Contents Microformat. Aggregators would then know where to find specific microformatted information.


comments edit

Luciano Spiguel just posted a partial translation of my post entitled Does Mort Know We’re Talking Smack About Him Behind His Back in Spanish. I’m actually quite honored that someone saw that as being worth a translation.

As a reminder, my content is published under a Creative Commons license Attribution license. What that means is that you may feel free to republish and translate my content as long as you attribute me properly. I do appreciate that people tend to ask me before they do so. It is a nice consideration, but not absolutely necessary.

comments edit

Anyon Braid Illustation Scientific American has a fascinating article this month on Computing with Quantum Knots. In particular, it focuses on using topological properties of a two-dimensionaly confined particles called anyons. Needless to say, the only thing they’ve managed to tie in a knot so far is my brain. But the research is very promising.

I never studied topology in college, though I did try and audit a topology class in Hungary. After a couple classes I decided it was over my head and focused on Number Theory, which is more my thing. Reading this article is spurring a newfound interest.

In essense, one of the difficulties with Quantum computing is that it relies on the superposition states of individual atoms. These states are exceedingly fragile, which make building a real Quantum computer difficult. The benefit of using topological properties is that they are more resistant to change.

The classic example of a topological property is to think of a string in a closed loop. You can twist the and deform the loop all you want, but it retains the same basic topological property of being a loop. You cannot twist or deform it so that it becomes a closed loop with a knot tied in it. You would have to cut it, tie the knot, and then rejoin it, thus changing its topology.

What caught my attention in the article were the number of researches mentioned who are now at Microsoft. The article mentions Michael H. Freedman, Zhenghan Wang, and Alexei Y. Kitaev, all of whom have made advances in the concept of using quantum knots for computation.

The article mentions that these researchers are part of Microsoft’s Project Q. It’ll be interesting to see if Microsoft makes a splash in Quantum computing as it moves forward.

comments edit

Clover My former neighbors who are now in Iraq helping the reconstruction efforts write about their St. Patrick’s day celebration in the IZ, aka “The Compound”.

Chris and Susan used to live a few doors down and my dog Twiggy was a huge fan of their dog Nelson. In fact, Nelson still comes by every now and then to visit, which turns Twiggy into a little excited doggy groupie.

My neighbors are working with USAID and the Army Corps of Engineers, hopefully helping to make some small good come out of a terrible situation.

Susan finishes the post with a funny St. Paddy’s day joke.

Chris and Susan, good luck and here’s a joke right back atcha.

comments edit

Lazy Coder Scott snickers when he reads blog entries decrying the existence of “Mort”. As he points out, we are all Morts to some degree or another.

I snicker when I read these posts because they dont get it. The entire POINT of writing code is to abstract away the difficulty that is inherent in using computers.

Which is true. The history of software development has been all about heaping one layer of abstraction on top of another.

However, I don’t see many blog entries decrying the existence of Mort. What I see are blog entries from “Not-So-Mort” upset about what happens to their programming tools and languages when tool and language providers accomodate Mort. Perhaps we see these tools as being made for the “Not-So-Mort” set, when the reality appears that these tools are being built for Mort. Perhaps the “Not-So-Mort” set would like separate tools.

Consider this, all abstractions are leaky. However, when an abstraction is well implemented, it hardly matters for the majority of the population. I believe I drive just as well in an automatic transmission car as I would in a manual transmission car, though my car has reduced the leak in the abstraction a bit via its sequential shift so I can switch to a manual-like mode, but that’s beside the point.

But many times, an abstraction is created in haste and causes problems for those of us who need finer grained control. A classic example is WebForms designer in Visual Studio.NET 1.1. I’m fine with the webforms designer. It is a great productivity tool and makes it quick and easy for Mort to build web pages using RAD techniques.

But now, take a Not-So-Mort who wants to use something like Microformats for example, which requires clean markup. He marks up his pages just right, but the pages get all FUBAR because the designer decides to rewrite his code. That’s problematic.

The problem here is we’ve exchanged long-term productivity gains (the maintenance cycle) in exchange for short-term gains in initial productivity.

Because these abstractions are leaky and poorly implemented, they convolute the implementation details they are meant to hide and make long term maintenance that much more difficult.

Whereas well implemented abstractions tend to promote good code. I’ve read several people state that a developer would have a difficult time writing more optimized Assembler than a good C++ compiler generates in this day and age, especially on a grand scale. It can still be done, but the fact that it is so close shows that C++ is a great abstraction on top of Assembly.

I’ve written about Mort too, but I am not hating on Mort. As Scott says, we are all to some degree a Mort. However one characteristic of a Mort as I have seen commonly defined is that Mort does not care to constantly learn. Mort isn’t striving to improve.

I do still think we should expect more from Mort. Understand that though the tools we have at our disposal make computing easier every day, computing at its core is a complex problem. Be sure to gain some small understanding of what these tools are doing for you and a general idea of what happens under the hood.

Back to my car analogy, I couldn’t take a wrench and fix my timing belt for the life of me. But I do have a general idea of what an automatic transmission is doing and what limitations it causes on my driving (I can’t seem to redline!). I would never ask Mort to understand assembly, but do take the time to understand some general principles.

comments edit

Well maybe not all of you. For example, I know Jayson isn’t going. Sucker. (Oooh, I just had to rub it in, didn’t I?). ;)

For you others that are going, I know there a few people I hope to meet because you promised to buy me a beer, or did I promise to buy you one? Here are the lists of people I plan to see:

Buying Me Beer

I’m Buying

No Exchange of Beer, Just Saying Hello

Normally, when I go to a conference like this, packing is a last minute afterthought. But this time, I will plan one specific article of clothing for the first day of the conference. I’ll wear a retina scarring bright orange Aloha shirt so that those of you who owe me a beer can easily spot me. If I owe you a beer, I will be wearing green and I have blonde hair. Ignore the rest of this post.

Orange Shirt\ Figure 1: Eye burning shirt at BurningMan

Just look for the guy who looks like a cross between Kim Jong Il and Samuel Schmid. You can probably find me at the Craps or the Blackjack tables. Maybe, if things are going well, I might have a date with destiny at the Let It Ride tables. Assuming she still works there.

And of course, if time permits, I will be at some of the sessions.

[Listening to: Walk Like an Egyptian - The Bangles - Greatest Hits (3:24)]

comments edit

Fire I have had it up to here (imagine my hand on my head) and I am ready to fire the damn QA department for my blog. Unfortunately I am the QA department, so things will be a little awkward around here till I find a replacement willing to take zero pay with no benefits.

I read this recent post on The Joy of Code that describes how to defer the execution of a javascript that is slowing down the rendering of your site.

So I go ahead and try it out, test in Firefox, and deploy to my hosting provider. The next day, I notice that hits to my site are way down. Strange. Everybody must be taking a break from blogs.

It wasn’t till today that a kind soul sent me an email saying my blog acts funny in IE.

Funny? I’ll say. Visitors using IE would get a scripting error and then see my Flickr Badge. Only my Flickr badge.

I have gotten so comfortable with Firefox that I completely forgot to test in IE, which the majority of web users are still using. It is fun to be on the bleeding edge, but never forget your audience. In the meanwhile, I am going to try and patch things up with my QA person because there are no resumes coming in.

UPDATE: As far as I can tell, the reason IE broke and not FireFox is that IE seems to actually honor the “defer” attribute while Firefox ignored it. This was not a bug in IE, but a bug in my head in applying the defer to scripts that should not have defer applied. And the Joy of Code article warned me too.

comments edit

So a little while ago I mentioned a new site named On10. I didn’t know what it was at the time, but I was assured by Erik and Adam that it would be cool.

And then it was released and I have to admit, I was not blown away. In truth, I was a bit confused. It looked to me like Channel 9, but highlighting the use of Microsoft technology outside of Microsoft.

But this channel 9 video sheds some light on the site and I am impressed. Not so much with what the site is itself, that may take time to grow on me, but what is going on under the hood.

Some interesting points:

  • First of all, their site validates as XHTML Transitional. Good job guys, as the Mix06 site did not validate.
  • Judicious use of AJAX to provide a rich experience.
  • The site works fine with a rich experience in Safari, IE, and Firefox.
  • You can add comments next to a video while the video continues playing.
  • Hackable URLs. Ex…
  • Trackbacks are treated as first class comments. So they are free with their traffic. I hope their spam filter is strong.
  • XBox Live integration via you can select your XBox Live avatar as your On10 avatar.

All in all, On10 is an “enthusiast” site that looks to participate in and give back to the community.

comments edit

Several people have complimented the live comment preview used in my skin. Try leaving a comment and notice the preview mode underneath. It now even supports a few HTML tags. Unfortunately I haven’t updated the comment page to tell you which tags are supported. Doh!

I did not write the original script. It was borrowed from the Asual Theme for blojsom and used in our Piyo skin.

However as I like to do, I spent a little bit of time trying to improve the script and turn it into a Markup Based Javascript Effect Library.

Now, by simply referencing this script, you can add live comment preview to any blog in three easy steps.

  1. Reference the script.
  2. Add the CSS class livepreview to a TextArea
  3. Add the CSS class livepreview to a div

The textarea is of course the form input into which the user enters a comment. In ASP.NET it would be a TextBox control with the TextMode property set to MultiLine like so:

<asp:TextBox id=”tbComment” runat=”server”\  Rows=”10” Columns=”40” width=”100%” Height=”193px”\ TextMode=”MultiLine” class=”livepreview”></asp:TextBox>

The <div> is the tag used to display the preview. There is a good reason to choose a div as opposed to allowing a <p> which I will talk about later. In my blog, that div already had a CSS class applied so I simply added the livepreview class like so:

<div class="commentText livepreview"></div>

And that’s it!

Well not exactly. I fibbed just slightly. There is actually a fourth step for the discriminating blog author. If you crack open the script, you’ll notice the following section on top:

var subtextAllowedHtmlTags = new Array(7);
subtextAllowedHtmlTags[0] = 'a';
subtextAllowedHtmlTags[1] = 'b';
subtextAllowedHtmlTags[2] = 'strong';
subtextAllowedHtmlTags[3] = 'blockquote';
subtextAllowedHtmlTags[4] = 'i';
subtextAllowedHtmlTags[5] = 'em';
subtextAllowedHtmlTags[6] = 'u';

In the next version of Subtext, that snippet is actually generated within an ASP.NET page (specifically DTP.aspx) as it is a list of HTML tags allowed by the blog engine. Since this is configured on the server, I needed some easy way to pass that information to the javascript. I chose to dynamically render javascript. I could have used an AJAX approach, but why bother at this point?

You can edit that array to specify your own tags. Note the preview only currently renders tags that contain something between a start and end tag. So for example, <b></b> won’t show up, but <b>Text</b> will.

For example if you add hr to your list of allowed tags, <hr /> won’t get rendered properly in the live comment preview. It will get rendered properly when it is actually posted as a comment. This may change in a future release.

Now it is up to you to apply some CSS styling to actually make the preview look good.

comments edit

This is a follow up tip to my post on Implementing CSS Based Printing.

One technique that served me well on a project recently was to implement a very simple print.css for the print stylesheet. In fact, it looks like this:

    display: none;

Make sure you declare the stylesheet properly:

<link rel=”stylesheet” type=”text/css” href=”print.css” media=”print” />

And now simply add the css class noprint to any elements in your HTML you do not want printed as in the simple example below.

<div id="main">
   <div id="header" class="noprint"></div>
   <div id="sidebar" class="cool noprint"></div>
   <div id="content"></div>
   <div id="footer" class="noprint"></div>

This is useful especially when retrofitting a complicated html page to use CSS based printing.

comments edit

Artificial Teeth In my last post, I mentioned that even in high pressure situations, I would take my time and follow certain practices I believe lead to better code, even if it meant taking longer to complete the code.

I took this approach because I felt secure enough in my career that I was not likely to get fired outright. Or at the very least I wouldn’t mind a bit of severance to fund a short vacation. I was confident that my overall time spent on the code, when taking into consideration time to find and fix bugs, was less than others who rushed through the code and spent the majority of their time debugging it.

However, there is another key fact I realized that kept me from rushing headlong into code oblivion. Many deadlines are totally and completely artificial, and I was tired of that bullshit.

“Tell me how you really feel Phil.”

Linus Oh don’t get me started.

An artificial deadline is nothing more than a comfort blanket to satiate a stakeholder’s need to feel in control over a process he or she refuses to understand. See the image on the left, that’s the stakeholder in charge of your project.

Most executives have a pretty solid understanding of corporate accounting. Yes, they trust the CFO to handle the specifics, but they understand the basic principles. This makes sense of course. A CEO who runs a company really ought to understand how the money is flowing in and out of the company.

Unfortunately, this same principle seems to apply less to software development. If a company undertakes a software development project, arguably one of the more expensive engagements a company can take on, it would make sense for the executive in charge to obtain a basic understanding of how real software development occurs.

Barring that, at the very least, trust your CTO or lead tech person, whomever that may be.

When given a deadline, I like to probe a bit and see if I can ascertain whether it is a hard deadline, or completely bogus. Bogus deadlines hurt morale, unless your team just plain decides not to care about them. My advice to anyone in charge of a software project is that the right way to gain control over a software project is to take the time to understand the software development process or completely cede control to your head tech person and trust them.

As for the developers and other tech people, we are not without culpability. As a commenter pointed out in my last post, we need to be ready to communicate the business case for why we want to institute certain practices. We have to speak up and speak clearly, or there is no chance for improvement.

UPDATE: James Avery points out the necessity of deadlines lest developers gold plate like they are decorating the sistine chapel.

And I agree. Deadlines are important. This is the comment I left in his blog.

Well I do believe in deadlines. However, deadlines should be set based on realistic deadlines in which the developers give input and feedback. A deadline should really be an agreement between developers and management.

“Artificial” deadlines are those that are not informed by realistic estimates, but by wishful thinking.

comments edit

Plug and Play It never ceases to amaze me how short sighted management at many companies can be with software developers. Jeremy Miller mentions a discussion he had at the Austion Code Camp in which several developers were really unhappy with their work situations for very legitimate reasons.

I am reading a book called Beyond Software Architecture and just finished a short section on Design Debt. I’ve read and written on this topic before, but I focused on the cost to change code that is in debt. Luke Hohmann takes it further, noting that by not paying off that debt, a developer’s attention to quality is deadened. If the management does’t care and won’t allot the necessary time, what can we do? Not only that, allowing the code to remain and incur more design debt chips away at developer morale.

As Jeremy points out, there are two solutions, try and be a leader, institute good practices, and convince management to allocate the time, or move on to greener pastures.

And you know what?

Management doesn’t care. Many of them see developers as plug-and-play. We’ll just get another one. Ignoring the cost to recruit and hire a new developer, they’d rather just plug in a new developer than make difficult systemic changes. Changes that would ultimately lead to the benefit of the bottom line, but does not do so immediately in a manner they can show off to their shareholders, bosses, whomever.

So what is the solution? Unfortunately I do not have much more to offer than what Jeremy points out. Personally, I make all efforts to refuse to compromise on certain practices in the first place. I am not always successful, but I have worked in high pressure situations where I simply refused to lower my attention to quality and still took the time to write unit tests and spend time refactoring. My successor at one job even IM’d me out of the blue to congratulate me on the quality of code I wrote in such a chaotic situation. That felt pretty good.

And the funny thing is, it did take a bit longer to reach code complete, but I do not think the overall time to release was extended. “Code Complete” usually meant to now find and fix all the major bugs introduced from rushing it in the first place.

comments edit

I don’t know about you, but when I find something wordy but really worth reading on the web, I print it out. Sure, I could try reading it on my tablet, but do you really want to deal with your tablet while reading in the…er… “office” if you know what I mean? *wink wink* *nudge nudge*

Unfortunately, the experience of printing many blog posts typically includes an ink draining header graphic, an unecessary space wasting sidebar or two, and the main fixed-width content being truncated off to one side.

If you click through to an individual blog post from my blog using a browser, you will notice that I now have a Print button. Go ahead and click it. It should bring up the following dialog.

Print Dialog

Getting that dialog to display is quite simple. Here is the HTML.

<a href="javascript:window.print();">Print</a>

However if you actually follow through and print a page, you can see that the result only includes the contents of the post and does not include my top navigation nor the sidebar. To test it out without actually printing, try turning on print preview for your printer if your printer driver software supports it.

The other thing you’ll notice is that the printed view displays the urls for links alongside the link (if you are using a CSS2 conformant browser such as Firefox). The image below is a screenshot from my poor quality print preview.

Print Preview

So the obvious conceit here is that I expect to someday write something worth printing. In the meanwhile, I have the print icon there to give people the impression that my content is worth printing.

And setting this up is quite simple using media specific CSS. My blog has a separate css stylesheet for printing. The changes the stylesheet makes to the layout include changing from a fixed-width layout to a 100% width layout as well as setting the display of certain elements to none. Note that this print specific stylesheet works whether a reader clicks on the print icon or uses the browser’s print button.

My inspiration for setting this up was this article in A List Apart by Eric Meyer. His article provides several tips for better web printing.

Setting This Up For Subtext

For those of you with a Subtext blog, how can you set this up for yourself? Glad you asked.

One enhancement we made to the skinning engine over .TEXT is that we added more options to the Skins.config file located in the Admin directory.

A skin can now specify one or more script and css files. For script files, you may specify the language, though javascript is the default. For css files, you can specify the media type.

Here is a snippet from my Skins.config file. Haacked is my personally customized skin not included with Subtext.

<SkinTemplate SkinID="Haacked" Skin="Haacked">
        <Script Src="scripts/ExternalLinks.js" />
        <Script Src="scripts/LiveCommentPreview.js" />
        <Script Src="scripts/tableEffects.js" />
        <Style href="IEPatches.css" />
        <Style href="print.css" media="print" />

As with .TEXT, the skinning engine just assumes that there is a style.css in the root of your skin’s directory, so it does not need to be specified here. However, now you may simply add additional css files for your skin to reference. In the snippet above, you can see I have a separate file for IE CSS hacks as well as a separate css file for printing.

The declaration for print.css includes a value of “print” for media. Other allowed values include, all, aural, braille, embossed, handheld, print, projection, screen, tty, tv, though for everyday use, most developers will stick to print and screen.

After setting a reference to your print.css file in the Skins.config file, simply add a print.css file to your skins root and you are on your way to better printing.

comments edit

Kent Sharkey comments on the necessity of marketing and advertising in general in response to Microsoft’s recent viral marketing efforts.

Blah Blah Blah

What grabbed my attention was the new word he coined (or if he didn’t coin it, he brought it to my attention and that is good enough).


I just have to add it to my vocabulary. I’ve tried to coin terms in the past such as blogtegrity that I hoped would catch on, but I realize now that I’m just stooping to linguistic whorosity.