The issue is with the use of both the media declaration and the web fonts. Which media values cause a problem? Looks like all of them (all, screen, print, etc.). Remove the media declaration and your web pages will then show the fonts your designer specified:

@media all { /* Remove this media declaration and start brace */
     @font-face { 
          font-family:"Frutiger";
          src:url("/fonts/frutiger.eot?iefix") format("eot");
     }
     @font-face {
          font-family:"Frutiger";
          src:url("/fonts/frutiger.eot?iefix");
          src:url("/fonts/frutiger.woff") format("woff"),
               url("/fonts/frutiger.ttf") format("truetype"),
               url("/fonts/frutiger.svg#frutiger") format("svg");
     }
} /* Remove this end brace */

If you need to keep your media declaration in your stylesheet, then I suggest that you just move all of your font-face calls to a new stylesheet.

The bad news is that despite all of your hard work, your site won't work on a touchscreen because draggable() doesn't respond to touch events.

Now the good news is that there's an easy fix. After a little searching, I found Touch Punch. The author describes the script as so: "jQuery.ui.touch-punch.js is a small hack that maps touch events to their mouse event analogs." Perfect.

You can view working examples on the author's site or download Touch Punch from Github.

If you care to sponsor me, please contribute here:
http://www.projectbread.org/site/TR/Walk/General?px=2064971&pg=personal&fr_id=1180

1. Every meeting should have a clearly defined mission statement.
   Absolutely correct, every meeting should have a clearly defined set of goals, and they should be clearly stated, both in the invitation and at the start of the meeting itself.
2. Do your homework before the meeting.
   Not only will you look good if you're prepared for the meeting, but you'll be helping everyone else be more productive.
3. Summarize to-dos at the end of the meeting.
   This is as important as stating the goals. Someone should verbally summarize the action items and conclusions from the discussion.

1. No meeting should ever be more than an hour.
   I certainly agree that the shorter a meeting is, the better. But some meetings, especially brainstorming meetings or project reviews, are going to take longer than an hour. There's no reason to set an arbitrary duration that's called "too long".
2. Make it optional.
   I don't see how it's practical to make every attendee optional. People should still feel free to decline an invitation, but sometimes you need to make it clear just who you can't have a meeting without.

"[a wireframe] is a visualization tool for presenting proposed functions, structure and content of a Web page or Web site. A wireframe separates the graphic elements of a Web site from the functional elements in such a way that Web teams can easily explain how users will interact with the Web site."
From Webopedia

Here are the main criteria I used to compare wireframe tools:

• I would prefer an online tool, or at least a desktop tool that offers real-time collaboration instead of file fragmentation. This tool should offer the ability to preview or user-test the wireframe over the web.
• I would love a tool that promotes and supports gradual enhancement of site elements, starting with basic page elements showing relative priority, then adding layout, then adding visual design.
• I would love functional prototyping, where you can configure clickthroughs from one page in the wireframe to another. In-page functional prototyping (such as drop-downs, popups, overlays, AJAX, etc., would be a bonus).
• I really want master templates to support global changes to page elements (ie, when you change the header or footer or even the layout of the template, it affects all pages in the wireframe).
• Export in HTML/CSS is highly preferred since it would save me time, but it's not completely necessary from my perspective.
• I would love the ability for us to add comments and annotations to individual page elements. This will help us evolve each wireframe, and annotations can serve as valuable notes during development to tell webdevs how each page should function.

I looked at the following tools:

• Like the snap-to alignment!
• Drag pages onto page elements to create links
• I like the ease and simplicity, but there doesn't seem to be a header/footer/page wrapper-- no master templates.
• Only exports as PNG/PDF.

• Exports as HTML.
• I don't like the open dialog, but I love the fact they have templates for different devices.
• Flash-based, and so the interface just isn't as fast as others.
• Controls for master templates are very hard to find.

• Requires Flash
• Has page commenting
• I like the presence of the drag-n-drop widget list, but it's ordered alphabetically instead of by functional groups, and the drawings look like a pencil sketch.

• It's a download, but has collaborative access (even SVN, where you can check out individual pages).
• Can upload files to share.axure.com to generate password-protected prototypes, or can generate local prototypes.
• You can export all copy
• You can gather and manage comments
• You can add annotations/page notes
• Export HTML
• Masters make templates for header, footer, etc.
• Disappointing that you have to publish specs to MS Word
• Disappointing that it's not a one-step publish to a web-available prototype.

• Has templates and masters
• Has component/widget palette, but these tend to be richer and more complex than I really want.
• Has page documentation and annotation
• Lets you modify CSS and HTML

It all started when I completely rebuilt my Eclipse environment, using the latest version, Indigo, so that I could install the wonderful PhoneGap plugin. I installed the latest version of all of my plugins, including Subclipse, and I also installed the latest CollabNet subversion binaries. Subclipse's wikipage for JavaHL says that if you install these binaries says that you shouldn't have to do any further configuration to get Subclipse to work, but in my case that turned out to be wildly optimistic, to say the least. Each time I tried to use a Subclipse feature, I was presented with the dialog that I gather all too many people are familiar with: "Unable to load default SVN client". A search across the Googles for this sentence gave me a lot of results, almost all of which referred to confirming the path variables in your .profile file or your eclipse.ini file. I edited, I confirmed, I failed. Again and again. I even tried to install SVNKit, but their subversion client doesn't support the svn client version of 1.7.x that Subclipse was looking for. Aargh.

The binaries that Collabnet installs have version numbers of "1.0" in their filenames, so you really can't tell what version they are. Instead you have to run "svn-javahl --version" to get that information. And what do you know, I had version 1.6.x.

So the final solution?

1. Install MacPorts if you don't have it already.
2. Use MacPorts to install the JavaHL bindings (you'll get the latest version by default):
   sudo port install subversion-javahlbindings

But I ran into errors while trying to updated the Android plugins; quite a few of the errors in the update log referred to messages such as "No repository found containing org.eclipse.mxunit/osgi..." Most of the messages referred to that osgi library, somehow. I thought that somehow I had some majorly screwed up libraries on my hands.

After searching, it turned out the problem and solution were relatively simple: update URLs should have trailing slashes at the end. Refer to this blog post for the specific solution. If anyone else runs into update issues because you're inspired by Ray's work, I hope this solution is helpful to you.

"ClassroomWindow addresses an absolutely critical missing element in education -- understanding what works, and for which kids. Sounds obvious, but it doesn't exist (yet). Our mission is to provide transparency into the effectiveness of educational texts, tools, and resources. It is Yelp + Consumer Reports for education products and services, combining crowd-sourced input from teachers and others on the front-lines of education with expert opinion and student data."

ClassroomWindow is preparing for a private beta later this year. If you or others you know (teachers in particular) would like to have their voices heard on which products work and which don't, please sign up for the beta at www.classroomwindow.com, check them out on Facebook, and follow them on Twitter.

For those of you who, like me, want to refer to Marc's slides to set up your own CI system, you can find his presentation files here:
http://wiki.mxunit.org/display/default/CFObjective+2011+--+Continuous+Integration

"Perhaps you have some unit tests. Maybe even an ANT build file that runs your tests. And maybe even a build file that packages or deploys your application. But how do you orchestrate those separate pieces into a symphony of automation? Continuous Integration, of course.

Imagine: you have tests. A Teammate commits code to source control. Minutes later, you and your teammate get an email indicating that tests are now failing.

Imagine: you commit code. Minutes later, all tests run. All tests pass. Zip files are built and are ready for deployment. Or code was automatically pushed to any accessible environment. All without your intervention."

In this session, Marc will demonstrate how to use the open source Jenkins Continuous Integration server, together with ANT and MXUnit, to create a top-notch automated test and build system for your ColdFusion applications.

The meeting will be at 6:00pm at the Sun Life offices in Wellesley. You can RSVP at http://bostoncfug-oct2011.eventbrite.com. Drinks at Dunn-Gaherin's afterward!

Via .net magazine

@variables { elementcolor: black; }
#selector1 { color: var(elementcolor); }
#selector2 { color: var(elementcolor); }
#selector3 { color: var(elementcolor); }

I can't believe there are people who say that CSS variables aren't needed or wouldn't be useful. These folks tend to have two arguments:

• Variables make CSS too complex, and more like a programming language.
  I disagree with this one heartily. Variables would only make CSS more like a programming language if the developer felt like using them. If someone didn't want to use variables, the wouldn't need to touch them. And, what's wrong with letting a language evolve? HTML certainly has, and it's gotten more like a programming language since it came into widespread use.
• You don't need variables if you use your selectors correctly.
  This is a better argument. It's the idea that you'd have a bunch of selectors all in one comma-delimited list with one declaration after it-- color, for example, or font-family. But that kind of arrangement seems almost as contrived and complex as the use of variables. Variables, at least, let you organize your declarations where you want them, instead of forcing you to separate them in a predetermined manner.

At Ping Identity, our company has been growing non-stop for the last two years, and the scale and number of web projects has grown along with our headcount. So, we need a third web developer to join our team. Bring your current skills, and we'd be happy to teach you new ones as well. Benefits are great, the work environment is fun (though you're able to work from home two to three days a week if you like), and the bonus structure is mighty fine.

If you're interested, please send your resume directly to me so that I can personally promote it to HR. For specifics, please check out our job posting for the web developer position:
https://www.pingidentity.com/about-us/career-detail.cfm?customel_datapageid_1441=53112

img:not([width]):not([height]) {
  border: 2px solid red !important;
}