I’ve been working on a Python program today that monitors which application I’m using. For now it’s writing the data with a timestamp to a text file. But of course I want to share this data on numuseum. I’m now researching the use of sockets. As only just discovered that Flash can also work with sockets… That’s very interesting for me, I should be able to push life data to a Flash film. Wow!
I’ve finally started building. I’ve made an inventory of all the properties
and methods a list of items should have and now I’m building the background.
I’m very new to Object Orientated Programming in Flash. So I’m building and
learning at the same time.
In the pic you see the main background of (in this case) the Input item
list, the background for the more button and the unformatted title. All with
the right size and position. From this I can move on and add more and more
features now that I’m beginning to understand how writing a class works.
I’ve just finished my design for all the items views: links, input, sketches, webart, haiku, pictures and projects. It’s consistent enough but not boring. I think it’s quite serene :)
One thing I’ve already found out is that I can load auto generated thumbnails from my delicious link straight into flash, it’s so cute to see the tiny webpages.
After weeks of struggling I’ve had a breakthrough in the numuseum archive interface. The archive will consist of three parts:
- The items or subjects
- The timeline
- The tags
The interface for part 1 is now almost finished. It’s been pretty hard to get a consistancy for all the different types of media. I’m still working on that but the main access is now ready.
I finally managed to get all the stuff about the back-end workings of the archive part of numuseum from my head into a diagram. It’s a great relief to see all the subjects in their different visualisations attached to the correct tools and APIs. I’ve got so much room in my head now that I’ve got new ideas for an interface metaphor. To be continued…
First rough sketch of the numuseum archive.
The interactive circular timeline will show all media items by day. There will also be a tag cloud and I think downloading everything from the internet at every move will be very non-fluid. I looked for and discovered a cool app in the Flickr app garden: phpFlickrSynch, “a PHP application that reads the metadata of your photos stored on Flickr, stores them in a local MySQL database, and gives you an API to let you play with those metadata.” Exactly what I need! After some wrestling with keys, tokens and secrets I managed to install and download the first metadata. Today I made an example app which chooses a set of pictures based on the actual date the picture was taken (this is actually stored in the EXIF data) and shows the title and thumbnail of every photo.
I’ve worked on the new numuseum interface today, these are the first
sketches. I want to combine the different subjects (e.g. webart,
photographs, etc.) in a scrollable circular interface that functions as a
timeline. The black lines indicate the years (like annual rings in a tree)
and the coloured lines are the subjects. The red line would indicate a
cursor with which to navigate the years and their different products.
Chronology, subject and tags will become the main interface for navigating
the numuseum content. For inspiration – and because I’m a map freak – I
bought this lovely book: Cartographies of Time: A History of the Timeline
I’ve been working on my collection of business cards. Each have a very distict design to stress the different characters of the projects. All have a nice glossy front and a back with a tag cloud and a background image as a teaser. I love tag clouds and I’ve discovered some nice online tools to make them: http://tagcrowd.com/ is my favourite as it lets you create a cloud from any text.
I’ve been looking for an aproriate wrapper. I think I’ll use anti-static grip bags so I can make a nice package. This is very convient as the series will never be completed and I can keep adding new cards to the package. The next card will probably be for this blog :)