Posts Tagged ‘userinterface’

Visualizing Inline Links

Thursday, August 2nd, 2007

Joen of Noscope has just suggested, what I’ve been trying to tell people for nearly a year. With the advent of pages commonly referred to as “Web 2.0” sites, the styling of inline or AJAX links became an issue. Usually links have to be indicated to the user, since clicking them slowly loads a whole different page and the user is unable to interact with the current page. The common indicator we use for links is the hand cursor.

Normal Link

AJAX or JavaScript links, however, immediately change a part of the page you’re looking at, without reloading the whole page and without disturbing the user experience. The user can still interact with the page. For example on Pageflakes - the personalized start page I’m using - you can find both types of links: normal ones that take you to another page and AJAX links that allow you to edit settings or reload embedded RSS feeds. The cursor for both types of links is the same, a hand. For the Web-savvy, this might not pose much of a problem, we intuitively know most of the time what type of link we deal with but for other users, this can be increasingly difficult to discern.

Inline Link

The solution Joen proposes, and what I have previously used in these cases, is simply not changing the cursor at all. In reality, it’s not a link, it’s more of a pushbutton that looks different, so why not use the same cursor we use for buttons?

The implementation is rather easy as it only requires a simple cursor: default; rule. To allow for fallback (if the user has no JavaScript, the AJAX link becomes a normal link), I just embedd the stylesheet with JavaScript so I get a hand cursor for people without JavaScript, where the link actually reloads the page and a default cursor (pointer) for people where the link only affects the current page.

Adding a stylesheet via Javascript is rather easy too:

<script type="text/javascript">
<!--//--><![CDATA[//><!--
 	if( document.getElementById && document.createElementNS && document.getElementsByTagName ) {
		var javacss = document.createElementNS( "http://www.w3.org/1999/xhtml", "link" );
		if( javacss ) {
			javacss.setAttribute( "rel", "stylesheet" );
			javacss.setAttribute( "type", "text/css" );
			javacss.setAttribute( "href", "/_css/java.css" );
			javacss.setAttribute( "media", "all" );
			document.getElementsByTagName( "head" )[0].appendChild( javacss );
		}
	} else {	
		document.write( '<link rel="stylesheet" href="/_css/java.css" type="text/css" media="all" />' );
	}

//--><!]]>
</script>

So, what do you think?

Apple’s Unobscured Touchscreen

Wednesday, May 16th, 2007

Rain Noe wrote an article on Apple’s new Touchscreen patent:

Touchscreens have one single but, as of yet, unadressed design flaw: your finger on the screen is obscuring the very elements you’re interacting with. This has several implications for the user interface, for example buttons need to be quite large so you can still see them.

Never fear though, the clever designers from Cupertino have come up with a solution for this particular dilemma. It’s still only a patent and I would be very surprised if this ever made it into a real product but it’s nevertheless a cool and unique idea.

Basically it’s an iPod or (i)Phone with a screen covering the whole front of the device. A transparent control layout on the screen allows interaction. The difference is, you’re not touching the screen, you touch the back, the opposite side of the controls. A cursor is shown to give you visual feedback on the position of your fingers and if you press harder, the device registers it as a click.

Apple’s Unobscured Touchscreen

Since your fingers end up on the back of the iPod anyway, simply by virtue of holding the thing, it sounds like a pretty good idea. The whole thing, especially the cursor and “press harder to click” function might take a bit of getting used to but I’m sure Apple’s designers and engineers could come up with something.