So I’ve now uploaded the code as a normal webpage. You can view it in a window sized like a phone screen [Pops up new window]. Once this window opens, you should be able to resize it in order to see how the page will look at different screen/browser sizes. Or you could view it in your current browser window (if you’d like to download the HTML, you should be able to right-click the link to get an option from your browser to save the target).

This isn’t what I wanted. I really just wanted a very simple page that had a login form and our Usage Policy (not a link to it, the actual policy on the page). If it was on a tablet or a PC, I wanted them to use the screen real-estate to show them both side by side. If it was on a phone, they should be stacked to avoid zooming. I couldn’t find anything that did quite what I wanted, so I wrote my own. Just in case there’s somebody else looking, I decided to post it here.

First, a screenshot of how it looks on an iPhone 6:

And an iPad:

There are actually two more “modes” not pictured here. They are both only applicable to being displayed on a computer.

There is one mode that is in between phone and tablet size. The only time it should be used is if somebody opens a very small browser window. It condenses the login form to take less horizontal space, but still keeps the policy text to the right of the page.

The second mode is for a very large web browser windows (more than 1,200 pixels). This mode simply keeps the max width at 1,200 pixels and displays nothing to the right of that boundary.

The magic in all of this are the @media CSS queries. These media queries are a function of CSS3 and are not supported on older browsers such as IE 8 (the most recent version available on Windows XP). Because of this, I put most of the style (colors, borders, etc) outside of the media queries and then shifted items around using the media queries. The page may not respond exactly as it’s supposed to in older browsers (for example, the items don’t stack properly when the width drops below 480 pixels in IE8), but the page should still be functional.

The code is available after the break. You are welcome to take this code and modify it for your needs.

UPDATE 11-Feb-2016: Instead of embedding the code in this post, I now have a Live Demo page setup.

Back in 2010 as Microsoft was putting the finishing touches on Office 2010, the Microsoft Exchange team mentioned that it was going to possible to show pictures in Outlook 2010. They also talked about how these pictures could be loaded directly into Active Directory and Outlook would be able to pull them from the directory. It didn’t take me long to make the required schema change on our network at work and load a few pictures in for testing. Once I updated our system to support Windows 2008 domain controllers, the display of pictures in the beta version of Outlook started working perfectly.

Even before I got the picture display to work in Outlook, I started wondering if it would be possible to make Windows 7 automatically load those pictures for its User Tile (I actually even asked the question on the blog post by the MS Exchange Team). It seemed that this wasn’t possible. Supposedly the fact that this was desired was passed on to the Windows team, but even after Windows 7 SP1 came out there didn’t seem to be any official support for this feature. And as far as I can tell, none is forthcoming.

The other day, I happened across a post by a guy named Joco where he detailed an undocumented API in Windows 7 that sets the User Tile. He also included some sample C# code that you can execute with command line arguments for the username and the picture location. However, I want to load the pictures directly from AD and I’ve done most of my “programming” in Visual Basic, not C#. So, I took his sample code, translated the API declaration to VB and added some code to retrieve the picture from Active Directory.

The Executable File

For simplicity, I’m providing an executable file already compiled against .Net 3.5 (which comes with Windows 7). This executable is signed by a CA Cert code signing certificate. If you do not have their root certificates installed, Windows will tell you that it’s an invalid signature.

• setUserTile.exe

To use this file, it can be simply be run by the user. You can launch this automatically as part of a login script (which is how I use it). The logic script application I use also allows me to hide any output so the DOS box never gets seen by our users.

Note: The icon used in this executable is licensed under the CC Attribution-Noncommercial-Share Alike 3.0 license. I’m open to using a different icon if I can find one a little more representative of what the program is doing.

Source code and some basic directions for using it can be found after the break.

The VB.net Code

This code was written using the free Visual Basic 2010 Express. Once you have that installed, you can create a new Console Application named “setUserTile”.

From the “Project” menu, select “Add Reference…”

And add a reference to both “System.DirectoryServices” and “System.DirectoryServices.AccountManagement”.

NOTE: You may also wish to change the version of .Net for this application to 3.5, which is the version that ships with Windows 7. If you leave it at 4.0 (the default for VB.Net 2010) the application will only be able to run on systems that have installed v4.0 of the .Net framework.

Module setUserTile
    ' Undocumented API learned from http://joco.name/2010/12/06/i-discovered-the-new-windows-user-tile-api/
    <system .Runtime.InteropServices.DllImport("shell32.dll", EntryPoint:="#262", CharSet:=Runtime.InteropServices.CharSet.Unicode, PreserveSig:=False)> _
    Private Sub SetUserTile(ByVal strUserName As String, ByVal intWhatever As Integer, ByVal strPicPath As String)
        ' This is just to fool WordPress which thinks it's being helpful </system>
    End Sub
 
    Sub Main()
        Dim strUser As String
        Dim currentADUser As System.DirectoryServices.AccountManagement.UserPrincipal
        Dim de As System.DirectoryServices.DirectoryEntry
        Dim b() As Byte
        Dim strTempFile As String
        Dim stream As System.IO.FileStream
 
        Try
 
            ' The WindowsIdenty object can retrieve the current username (with domain), but not the AD Object
            ' The "AccountManagement" object can retrieve the current user, but not the thumbnailPhoto
            ' The "DirectoryEntry" object can retrieve the thumbnailPhoto, but not the current user
            ' So we use all three objects...
            '     The WindowsIdentity object to pass the full domain\username string to our API
            '     And the "AccountManagement" object to tell the "DirectoryEntry" object which user to get the photo for
            strUser = System.Security.Principal.WindowsIdentity.GetCurrent().Name
            currentADUser = System.DirectoryServices.AccountManagement.UserPrincipal.Current
            de = New System.DirectoryServices.DirectoryEntry("LDAP://" + currentADUser.DistinguishedName)
 
            b = de.Properties("thumbnailPhoto").Value
            If b IsNot Nothing Then
                ' We've got a picture... save it to %TEMP% ...
                strTempFile = System.IO.Path.GetTempFileName
                stream = New System.IO.FileStream(strTempFile, System.IO.FileMode.Create)
                stream.Write(b, 0, b.Length)
                stream.Close()
                ' ... call our API ...
                SetUserTile(strUser, 0, strTempFile)
                ' ... and delete the temporary file.
                System.IO.File.Delete(strTempFile)
            End If
        Catch ex As Exception
            ' Fail silently
        End Try
    End Sub
End Module

setUserTile in VB.Net by Jacob Steenhagen is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
Based on a work at joco.name.

• Things I liked about the BlackBerry that I’m missing now
  • Sleeper Magnet
  • Voice Command
  • Battery Life
  • Facebook Application
  • Different Alerts for Different Events
  • CacheBerry
• Things I like better about the Pre
  • Polished OS
  • Read status syncs
  • Usable touch screen
  • Synergy calendar
  • Chat like text messaging
  • Touchstone
• Summary

Things I liked about the BlackBerry that I’m missing now

Any time you switch to a new phone, especially if you change platforms, there’s things you miss about the old one.

Sleeper Magnet

I mentioned how nice this feature was in the post I made when I first got the BlackBerry and I never changed my mind about that. It was so nice to have the phone automatically switch to vibrate mode whenever it was in the holster. If it was in the holster, I wasn’t as likely to hear it ring but I was much more likely to feel it vibrate. It just kinda made sense. It was also nice walking into a movie theater or Church on Sunday and not having to worry about putting my phone on silent. If it was in the holster, I was good to go. Not a world changer by any stretch, but a nice convenience factor, for sure.

Voice Command

When I did my last review, I mentioned that the voice command on Windows Mobile was better than the BlackBerry. When I first got my Windows Mobile phone, it came with a pretty pathetic voice dialing application. It was the old school kind where you had to record voice tags for each contact. Even that was better than the voice command on the Pre… it doesn’t have one at all. We can hope that voice command is something they’ll add in a future OS update.

Battery Life

I kind of took a step backward on this one… but when I went to the BlackBerry I had taken two steps forward. So all told, I’m still a step ahead of my 6700. I can normally make it through a full day of normal use on the Pre’s battery. But on my BlackBerry, I could get almost two days of normal use. They sell two different extended life batteries. One that’s the same size as the stock battery [link to outdated product removed], so it doesn’t add any extra thickness to the phone while giving a slight power boost, and one that doubles the battery life [link to outdated product removed] but adds about 4mm of thickness to the phone and requires a new back (comes with the battery). I’m currently still using the stock battery, but we’ll see what happens as the phone ages.

Facebook Application

I mentioned when I got the BlackBerry how nice it was to have a Facebook Application and how much better it was than m.facebook.com. Well, now I’m back to a phone that doesn’t have one and I miss it. Sure, there’s touch.facebook.com, which the phone comes with a bookmark for (actually, it comes with a bookmark for x.facebook.com, but that redirects automatically to touch.facebook.com now days… same page, different URL), but it’s not the same thing as having an actual Facebook app. The Facebook app loads faster (it can use cached information). I also miss the ability to tag a photo as I upload it. The Pre does have some nice Facebook integration… for example, my phone contacts are automatically linked to my Facebook friends (if it gets the auto part wrong, I can manually correct it). This means that their Facebook photo can show up on my caller ID. It also means that if they’ve put their phone number on their Facebook profile it’s automatically in my phone book. The downside is, it grabs all my Facebook friends… including those who I just became “friends” with in order to gain something in a Facebook app or people I knew in High School but don’t talk to anymore. It still nice to have some idea what those old acquaintances are up to these days, but I don’t know that I need them in my phonebook. Photo uploading is also possible right from the photos application, but you can’t tag friends from the Pre.

Different Alerts for Different Events

I really miss this one. I could tell by the sound my phone made before if I had a text message, a work email, a personal email, an AKO (Army Knowledge Online… don’t have this account anymore) email, a Facebook message, or something else. On the Pre, not only is it not possible to set sounds for each of these events individually, but you can’t even change the default sound. My wife also has a Pre so if we’re both together, it can be difficult to know which one of us just got alerted… nevermind what the alert means. I’ve briefly tried the homebrew solutions to that problem, but didn’t really like them… though I do appreciate that they were at least an option. I’d imagine this is something coming in future OS updates.

CacheBerry

When we started Geocaching a while back, one of the first things I did was look for a way to go paperless. What I came across was CacheBerry. It was a nice little program that let me load GPX files into it filled with cache information which I could then use in the field to look at recent logs, hints, etc. I was also able to use it to keep track of what caches we found to make logging easier when we got home. Over the year or so I used it, a lot of new features got added. Unfortunately, there really isn’t anything similar for the Pre. So while it may just be an application that was available for the BlackBerry, it qualifies as something I miss about my old phone.

Things I like better about the Pre

Obviously I knew most, if not all, of the above things when I picked the Pre over an updated BlackBerry, so I must have had a reason…

Polished OS

There are those who would say that eye candy doesn’t matter. In fact, I used to be phone of them. I thought of all that animation (menus, windows transitions, task switching, etc) as nothing more than wasted CPU cycles. But as I use operating systems that have those things built into them I realize that they can be useful… as long as the animation is fast enough and stays out of the way of usability (nothing worse that not being able to do what you need because you’re waiting for an animation to complete). As I was watching videos of both the Palm Pre and the Android based HTC Hero one thing I noticed was that the Pre had a lot more polish to it. And, of course, both of those had more polish than my BlackBerry Pearl… and the Tour didn’t seem to be terribly much better in that department. The Pre and the Hero seemed to have similar, though not identical, capabilities. But the Pre had a physical keyboard and that’s still pretty important to me. I’ve used the virtual keyboard on an iPod Touch and it was possible to type on it, but I still prefer to pushing actual buttons. While the webOS software is still lacking a few features, I think it has a ton of potential. I’m definitely looking forward to the next few OS updates… especially if they get the GPU in the Pre working to it’s full potential!

Read status syncs

This was something that always annoyed me on my BlackBerry. I’d read a message on the phone and when I got back to the computer it’d normally be marked as read. But if I read it on the computer, the phone would never realize it. Even if I deleted it on the computer. The Pre, being that it uses Exchange Active Sync and IMAP to interface directly with the mailbox (whereas the BlackBerry goes through either a BES or BIS connection), is pretty always in sync. Sometimes it has to run the “sync process” first, but once it does the read and deleted status of each message is the same in both places.

Usable touch screen

The BlackBerry doesn’t have a touch screen at all, so any touch screen is going to be more usable than it had. Where I’m comparing “usable” here is actually two phones ago when I had the PPC-6700. That phone had a touch screen, but it wasn’t nearly as usable as the capacitive touch screen driven by webOS. One reason was that the 6700 used a resistive touch screen (the mainly being how much “touch” was required). Another reason is that the Pre is multitouch. I can handle being touched two different places at the same time and even react to it appropriately (such as pinch zooming). And lastly, webOS is built for being used with a finger whereas Windows Mobile was built for being used with a stylus. Switching between the screen and the keyboard on Windows Mobile was always a huge pain… even ignoring the fact that they keyboard was only in landscape mode so pulling it out meant rotating the phone.

Synergy Calendar

I tried for so long to get my work calendar, my personal Google calendar, and my Facebook calendar all onto the BlackBerry with only limited success. In the end, I was able to get the Google Calendar to sync using Google Sync. The problem with that was that I have a lot of calendars on my Google Calendar account and Google Sync could only lump them all onto one device calendar. It wanted to put all those events onto the device default calendar, which was my work calendar. So things would become a mess pretty quick with my personal items ending up on my work calendar. I really wanted to keep those two separate and I managed to find a setting on the BlackBerry that would cause Google Sync to put all its items on a different calendar (changed the device default calendar). I could only choose one remote calendar that all created events would go to, which wasn’t ideal, but it worked. I have a personal calendar and my wife and I have a shared calendar. Whenever I wanted to put something on the shared calendar and we were out and about I’d create it on the phone, it’d get synced to my personal calendar, then I’d have to remember to go online and move it to the shared calendar.

One the Pre, things are so much nicer. I added my Google Calendar account to the Calendar application (actually, it added it automatically when I added my gmail account to the mail app). I was then given the option for which calendars I wanted to view on my device. When I create an event, I can choose any calendar I have write access to (work, personal, shared w/my wife) and the event gets synced up to that calendar. If I want to display another calendar on my device (like the Detroit Lion’s schedule), I simple add it to my Google calendar and it’ll be available on my phone’s calendar. This multi-calendar display was possible with the combined calendar thing that Google Sync did, but on the Pre they can all be different colors.

Chat like text messaging

As I mentioned back when I did my other review, back when i was on Windows Mobile I started using threaded (chat-like) text messaging. I accomplished this by finding a third party program that replaced the default Windows Mobile text messaging program. That program was written by Palm when they started putting Windows Mobile on their handsets instead of PalmOS. That chat feature was a great selling point for their phones and they didn’t want to abandon it when they went to Windows Mobile (we’ll leave my other thoughts about Palm going to WM out of this). So I’m not at all surprised that the Pre has chat-like text messaging.

What is pleasantly surprising is that they didn’t stop there. They also added chat-like instant messaging. Well, instant messaging is pretty much the definition of chat, but what they did is integrate text messaging (SMS) and instant messaging (Google IM and AOL in the initial release). You can add your contact’s Google IM or AIM screen name to their contact information (it might be able to pull that down from Facebook, I’m not really sure) and then switch seamlessly between SMS and IM. OK, so there is a seam, but that’s just a small divider line so you known when the communication method changed.

Touchstone

The touchstone is one really slick piece of hardware. It enables you to charge the phone without plugging any cables into it. Simply set the phone on it and it starts charging. When it’s done, pick it up. If the phone rings while it’s setting on the touchstone and you pick it up, the call will be answered. If you’re in the middle of a call and you set the phone down on the touchstone, it will transfer it to speaker phone. Those are really nice software features of the phone; but, to be honest, they aren’t as useful as the aforementioned sleeper magnet in the BlackBerry.

If you get the Touchstone kit [link to outdated product removed], it comes with a new back for the phone and the touchstone itself. This new back is required for using the touchstone as it provides the phone part of the connection. That said, even without the touchstone requirement, the new back is nice because it’s a matte finish rather than a glossy one (which the standard cover has). The glossy finish is a real fingerprint magnet whereas the matte finish doesn’t really have that problem.

Summary

So here we are, more than 2,000 words later. I’d imagine I’ll be posting more about the Palm Pre and webOS in the future. Overall I like the phone. There are some shortcomings, but almost every one of them is software related. And the software is constantly improving. There’s actually a new update expected “soon.” When the Palm Pixie launch (this Sunday) it will have webOS 1.3.1 available for it. It’s expected that 1.3.1 will become available for the Pre soon after that.

Similar to when I got the Blackberry, I’ll do a pros and cons post soon. Also similar to when I got the BlackBerry, this post was made from my phone.