Progress on Favorites Browser

It is still far from being anywhere close to being ready for "prime time," but I am moving forward. There are no user interaction features as of yet, hence me posting static HTML and not a nice web interface for you to use. The originating username is still hard coded. I have somewhat solved the problem where a person does not have enough favorites to complete a row. I have a quick hack to prevent two rows in a row from having the same owner, although this is a cheap hack. I need to make sure there are no duplicate rows in the whole square. I can do this by either grabbing another batch of favorites for the same owner or skipping an owner after they have gotten a row. I would like to add some visual styling to show which photos are which as I always run into problems explaining the concept to people.

Every decision I make revolves around keeping the number of API calls to a bare minimum. I also want to keep the size of the calls as small as possible. I try to only ask for the number of favorites that I actually need to make a square instead of the default 50. XML is verbose and the less the API has to send back the better. Of course, that means more logic and data structure fu on my end and boy, is my perl rusty!