We are on the final day of our week of code crunching.
Kasper has during the last couple of days rewritten the object storage a couple of times, but have now decided on a (so far) final design.
The goal for today (and hence the final goal of the week) is to get the object system properly integrated with the client. Currently the objects rendered on the screen is represented in a client side mock-up of the system – this will hopefully change soon.
On the client side a few kinks in the window handling has been worked out and we have implemented the first governor. A simple governor which annotates a page with timestamps as seen below.
The final design of the governor interface and how they are connected to the object system has yet to be done. However we are pretty certain that there will be a range of different types of governors.
The governor implemented for timestamps are one of the simplest types of governors. When it is enabled it just reacts to changes on a given object or objects. However if one is to implement a governor to support e.g. alignment of graphical objects, the instrument on the client will have to be able to communicate with the governor to get e.g. suggested positions. Furthermore a governor for a board-game as discussed in the CHI paper, will need to be able to validate whether a given modification of an object is valid. This could be the position of a piece on a game board.
February 1, 2009 at 8:09 pm
Hey!
Looks great so far, but when is there gonna be a PC version ?
Remember that PC is the most awesome computer ever designed and it would be foolish to ignore it. yes
(thumbs up!)