Mike Austin's Blog

Sunday, December 30, 2007

No 3D for Nokia N810

"Although the N800/N810 are built around an OMAP2420 they don't use the PowerVR on the chip. The reason is that it only comes with 5Mbits of VRAM which is nowhere near enough for the 800x480x16 resolution. So Nokia had to use an external LCD controller (Epson Blizzard or Hailstorm I think), which is the reason for the not so great video performance (bandwidth to/from the CPU is slow).

The OMAP3430 will support resolutions up to 1024x768x24, so next year's tablet (the one after the N810) is likely to finally have hardware-accelerated 3D and possibly a higher-res screen as well (why else would they spend time making hildon resolution-independent earlier this year?)" - link

I'm looking for a small, touch screen tablet device to try some 3D multitouch coding. I guess the only ones are the expensive Sony UX and related?

Interfaces: beyond sliders

I came across an interesting power management UI in the Sony UX pc: a multi-dimensional selector. I think it really helps visualize the settings between battery life, performance, etc.

Trigger happy

"No matter how boring, impossible or just plain whacky the idea, it is a valuable contribution. Either it triggers a reaction from other participants in the opposite direction, or it invites to meander for a minute along that train of thought (‘imagine there really is no menu bar…’). Both are a step in the right direction."

The Making of: GIMP UI brainstorm

Imagine there is no spoon :)

Monday, December 24, 2007

Classic WTF: What Is Truth?

What-Is-Truth?

Tuesday, December 18, 2007

TODO



http://www.goesping.org/archives/2007/12/08/todo/

Friday, December 14, 2007

Fun with XSLT

I played around with XSLT a while ago (it's been around a long time), and recently started looking at it again. It's nifty how declarative it is, for example you can set the attribute of a div whether it is an even or odd numbered child (only snippets for brevity):
<friends>
<friend name="Bob"/>
<friend name="Ray"/>
<friend name="Joe"/>
</friends>

<xsl:template match="friend[position() mod 2 = 1]">
<xsl:copy>
<xsl:attribute name="class">odd</xsl:attribute>
</xsl:copy>
</xsl:template>

<div class="odd">Bob</div>
<div>Ray</div>
<div class="odd">Joe</div>
It's like aspect oriented programming, where you can define rules that apply to any parts of the document.