I have had a look at the code and I find it very hard to follow. They appear to be using a slightly different SD library, a different display and using a rotary encoder to do the menu selections. I guess the modern equivalent of the rotary encoder would be the touchy circle on the front of the i-pods or the rotary wheel on the MS style mice. I like that idea, but it is hard to understand, I think I need a deep course in the basics of C++ before I can untangle some/most(?) of the code.
I suspect my problem lies either in the way that particular SD card library is written, where it assumes any output will be going to the serial interface and nothing else, or that the data returned from a directory interrogation concerning any file files found in it, comes back in some array format I have no idea about. I don't particularly want to write some convoluted bit of code to untangle bad programming that someone else has created, or because I don't understand it, I would rather fix it properly as a lot of other ideas are going to depend on this section I would like it clean and mean code, no spaghetti code.
I would like to write a screen formatter that followed some standard, and for my size screen I reckon the old standard of Teletext would do (without the double height characters to begin with) but something like that. They still use that format with the Totaliser betting in Australia. Go into any pub with on line betting and you will screens and screens of teletext. It puts a smile on an old hands face I can tell you.
Teletext would give standardised high lighting and low-res graphics. Who knows I (er we!) could come up with the First Arduino Totaliser screen 
Ahem, I will go back to that program again and see what I can glean, I am getting way off track here.
Rob