It was only a few months later I think that I heard about QuickSilver the perpetual beta quicklauncher. I don’t remember why I switched but I switched from Launchbar to Quicksilver. It was probably the nice bezel look I could get on Quicksilver that made me switch. I was still in heaven and able to fly around my computer without taking my hands off the keyboard. Maybe I wasn’t flying since I type so slowly, but it was faster then mousing around. Then a few months ago Boone Gorges wrote a post about how he was using Quicksilver and I realized I had been missing so much. I tried to follow some of Boone’s tips but encountered little success. To top it off Quicksilver started crashing and just generally acting sluggish since upgrading to 10.6.

So today I happened to read a tweet that mentioned a new quicklauncher, Alfred. The name is not as sexy as Quicksilver, but I downloaded it anyway. Initially it didn’t work. I wrote the nice folks at Alfred and they hooked me up with a version that would run on my old non 64 bit laptop (someone should really get me a new one). Let me say I love the design of their site and so far Alfred feels a lot faster than Quicksilver. I’m not sure Alfred can do all the crazy things Boone has Quicksilver doing, that is why I’m hoping he downloaded it and can try to push it. For now I’ll try Alfred and keep my hands on the keyboard. Yahooooo!

Tungle makes it super simple to allow people to schedule meetings with me. In the first four weeks of class, I’ve already had half of my class use the link I give them in our course site to setup a meeting. So far it has been a joy to use and I can’t think of anything I’d need to change. I’ve enjoyed it so much that I recommended it to the other members of the Instructional Technology department. And they must be doing something right because my boss has started using it. I’m not sure how you’d find it via Google as a search for “web based scheduling” and “web based appointments” didn’t turn up Tungle in the first page of results. Hopefully people reading this spread the word.

I must say it has been relatively painless to convert Voices from just a plain WordPress Multi-blog setup to a BuddyPress powered community site. My first step was to convert my existing Multi-blog setup on DreamHost to use BuddyPress and mark it as the development environment. Once that was done in late October I began looking at my options for a theme to use as the main site theme. This was before the changes in theme structure for BuddyPress. At first I tried to code something myself, but given that I wanted it to be ready for this semester and that I have other duties, it was clear I couldn’t take the time. I looked at some of the free options like Bruce, but could not get them to really work consistently and be stable. In the end I settled on BP Corporate by incsub. It is a nice clean theme, which is what I really wanted since the content of an academic community should be the focus.

Once I had picked a theme I started playing with where to put the widgets and how to make sure the site had a dynamic feel. I ended up using the plugins Ahjira Recent Site-wide Articles, Auto Group Join (with some modifications to make it work), BP Groupblog, BP Events, and Recent Global Comments Widget. The homepage also uses some of the built-in BuddyPresss widgets like Groups, Site wide activity, Who’s Online Avatars, Members and Recently active member avatars. Eventually I’d like to add a Featured Post widget, but the ones available currently do not seem to work. I think the overall effect has been very good. The site feels dynamic and people can see what community members are writing about.

I would say it has definitely been worth it. Even though the main use is for class blogs at the moment, we are getting a number of users joining because they want to be a part of the community. This is something that was not happening before BuddyPress allowed us to easily create the community features. The feature with the biggest impact though has been BuddyPress groups with the Auto Group Join plugin. This has made creating class blogs super easy and faculty have really loved it. There are still some things to tweak, but overall I’m happy with how it is going.

I also had a chance to meet Jim Groom, Andrea and Ron Rennick, Andy Peatling, Matt Mullenweg, and many others. Jim and I had a chance to talk over some yummy pizza and some drinks. Our views on WPMU, the direction of personal publishing, and education in general seem to be very close. We talked a little about the idea of setting up a multi-school WPMU, possibly with the help of a grant. Our thinking is that this might cut down maintenance and would give us an opportunity to connect students and faculty at the participating institutions in a way that cannot be done currently. This is kind of sketchy, but I really want to explore this some more with Jim.

I also had a thought while attending all of these presentations. I saw so many people with their laptops open and typing away. I’d say about 90% of some of the audiences had their laptops open. Of those 90% it seemed that about 10% were taking notes/tweeting notes. The rest seemed to be checking e-mail, surfing, etc. This struck me as a little odd. I took my laptop but all my notes were written on paper. I also thought it was interesting that Jason Alley of Lafayette was taking paper notes as well. I just wondered what people were getting out of surfing while sitting in a session. I think this is the fear that some of our faculty have when we mention laptop programs.

• Server: ldap.wooster.edu
• Port: 389
• Search Base: o=wooster this will make all people affiliated with Wooster searchable (Student, Staff, Faculty, Alumni)
• Scope: Subtree
• Authentication: Simple
• User Name: cn=yourusername,ou=yournovellcontext,ou=yourrole,o=wooster (e. g., cn=jbreitenbuch,ou=math_cs,ou=faculty,o=wooster)
• Password: yournovellpassword

What I’d like to do is find a way to limit the search base to just students, faculty, and staff, but entering ou=staff,ou=student,ou=faculty,o=wooster didn’t seem to work. This is probably because you can only go down one branch of the tree at a time. Doing something like ou=student,o=wooster does work and will only search LDAP for students. So creating an LDAP entry for each search base (ou=student,o=wooster; ou=staff,o=wooster; and ou=faculty,o=wooster) should allow one to search for everyone but alumni. If anyone happens to try this and has trouble just leave a comment.

While playing with @font-face I’ve also looked at some other CSS 3 commands to try out on the site. Currently I’m making use of the rgba command and border-radius command to style block quotes. I did try the -moz-column-count: 2; -webkit-column-count: 2; commands to make post content two-column, but it doesn’t work so well with video. I’m thinking what one would do is make the post content two-column and then have a postfooter that spanned the entire div. So a post would have a containing div with a content div (with column styling) and footer div inside it. You could then use a plugin or custom fields to place the video in the footer. More experimentation is required. I encourage everyone to start to experimenting with CSS 3 and see what it can do.

If you’re not aware there is a new feature in CSS3 called @font-face. This feature is intended to address one of the major issues of publishing on the Web: not all readers have the fonts you used in the design! For graphic artists, publishers and typography nuts (such as myself) this has been a real issue. We develop a fantastic layout and design with fonts that make the entire piece or site look gorgeous, only to see it on a friends computer displayed in Arial, Georgia, or Trebuchet. @font-face and the Typekit service are here pull us out of this Dark Age of Web typography.

So how does it all work? You can see Web fonts with @font-face for a more detailed explanation, but the gist is that you host your fonts on the Web and then access them as you would any other Web file. It sounds great and if you take a .otf file and put it in a Web accessible directory then you’ll be able to use it with @font-face. Sounds great doesn’t it? So why do we need Typekit? Well, fonts are software. I know it sounds crazy but in terms of the licensing of their use they are treated like software. This means that you are allowed to have a copy on your computer and to use it to produce documents, but you cannot freely distribute it. This is exactly what you would be doing if you put that .otf file in a public Web directory.

Typekit has developed a solution which a number of font foundries seem to think is a good solution. Typekit’s solution is to host the fonts on their servers and require you to use some javascript to be able to access the fonts in your sites. They have arranged their offerings into 4 packages: Trial, Personal, Portfolio, and Corporate. Prices range from free to $49.99/month. A free account will entitle you to 5GB of bandwidth per month, two fonts from the 62 in the Trial Library to be used on one website, and you will have to display the Typekit badge (as you see in the bottom right of the site). Other plans increase the bandwidth, number of fonts you can use, number of fonts to choose from, and allow you to opt out of displaying the badge.

Once you join you’re asked to provide a website where you would like to use the service. Once you supply a URI and advance, you’ll be presented with some javascript to copy and put in the head of the pages using the fonts. After pasting the code into your webpages you can return to the Tyepekit site and select the fonts you would like to use. You can do so by browsing the appropriate library for your plan and then clicking the ADD button next to the font. Doing so will try to open a Popup window (Firefox complained and I had to allow an exception). At this point you will find directions on how to use the fonts on your site and you’ll be able to disable weights and styles that will not be used in your design so that the payload of the javascript is as small as possible. When you are finished here just click on the Publish button to make the fonts available to your site.

Overall I was very pleased with the way the service operated and the fonts that were available. I didn’t see any Adobe or Linotype designs in the Trial Library, but there were plenty of good fonts. Hopefully Typekit can get the traction necessary to attract larger foundries to use the service. I so want to use my beloved Helvetica and Myriad Pro. For now I’ll go with Liberation Sans for headings and such and M +1c Garogier Liberation Sans for the body text. If you are browsing in the most recent versions of Internet Explorer, Firefox, Opera or Safari then you should be seeing the site with my Typekit fonts. I’d encourage everyone that has a blog or website to check them out.

This week’s webinar series was all about SEO and inbound marketing. The event was organized by Hubspot and featured a series of well-respected authorities on SEO and marketing. A lot of attention was payed to increasing your rank in Google, extending the reach of your content, and making the proper use of social media in marketing yourself. It was very interesting stuff to listen to as I completed my various daily quests. Many of the things they mentioned I knew, but there were several things I took away that I think will prove useful in the coming months as I work on the Voices site. Who knows I may have even passed their exam so I will be certified in inbound marketing.

Also in the so far, so good category is NMC 2009. I didn’t really know what to expect, but I have been really happy with the sessions I have attended. Kathy Sierra’s talk this morning was excellent and I’ll probably have a separate post about it in the near future. The Google Earth session gave me some great ideas for Katie and Peter’s World History Museum project, the Screencasting session had a few cool tricks, and the session by the CSUMB faculty was great. Can’t wait to see what tomorrow brings.