Monday, September 20, 2004

Object Standardisation

There would be a standardisation of object properties. If Dick Jones Electronics wanted Bob and others to use their services they would build an object and place it on their website where it could be dragged and dropped into Bob's database.
As well as the usual contact details, such features as "I am a vendor," "I deliver" and "I use Savi cash transfers" could be enabled. The Dick Jones online catalogue would use standardised product objects. Because they use common retail product specification fields and image spaces Bob will be able to show competing products in tabular form to help him compare features and comparison shop.
Corporate, Retail or Public Savi hardware would have a guest slot where Bob could plug in his block to retrieve product brochures, catalogues, local maps and contact details. All of these objects would strictly comply with standards or be rejected by the block. Multiple addresses in the Dick Jones object would tie in with Bob's "I am here, what's nearby" feature.

Saturday, September 18, 2004

jkOnTheRun: A typical day with the Sony U-70

jkOnTheRun: A typical day with the Sony U-70

A great weblog from a guy who uses his gadgets...

04 Website

04 Website
This my other website. When you're there, click on "Home" to get the framed version...

Savi Budgeting

Using Mac's addon, Bob decides to budget for an overseas vacation a year from now. First he clicks on his bank account in the database panel. In the properties panel he sees his current balance in bar graph form. He slices $200 from the bar and drops it on a new account. Then he chooses to repeat this process every week. Next time he connects the bank will open the new account and start transferring the money.
He drops the account on the timeline and, using the properties panel, he creates a new viewing filter. The filter makes a wedge in the timeline, starting $200 thick and expanding into the future. A year into the future Bob creates a new object; it's the vacation and in its property sheet he enters its cost. This places another wedge within the wedge. At any point between now and a year from now he can see how much is put aside for the vacation and how much is in surplus.
He decides he wants a new camera between now and then; dropping the camera object in the vacation wedge shrinks the surplus wedge -- if the vacation date is locked then the camera will snap to when it will be affordable. If he drags the camera towards the future then the surplus wedge will re-appear; if he drags towards today then the vacation object will either contract in value or move away, further into the future.
Adding money to the account could fatten the wedge, causing the camera to slide closer to today. A bar could be extended from the camera towards today, creating a lead time in which comparison shopping could start; the camera could be linked to the contact details of a dealer to request brochures at that time as well.
With enough surplus, Bob decides to buy the camera. He drops the camera on the supplier and the money is transferred from his new account to the supplier who delivers the camera. The shiny new camera now appears in his regular timeline at the projected delivery date; clicking on the camera displays is shipping progress in the properties panel. When it arrives Bob can choose to leave it in the timeline with a warranty bar extending onto the future.
It's getting close to vacation time now so Bob selects points on the vacation's lead time bar and assigns vacation related tasks; the vacation object now doubles as a financed project...

Savi Mapping

A streetmap enhancement could fetch addresses from the contacts database and place them on the streets in a refined database view. When plugged into the cellphone the Savi would refine the view to the suburb surrounding the nearest cell site. A "Next Time I'm" database linked to contacts could generate a list of errands when in a particular area. The map could generate the most efficient route to tackling them.
A call from a contact could show their position on the map; tapping your position would produce directions from here to there. Tapping your position when in other cities or countries would switch you to different dialling prefixes, timezones, currencies, service providers, rail schedules etc.
The firmware of any Savi device that you plug your block into would tell the block where the device is located, to help in updating your location. Public Savi kiosks would present you with calling rates when you attempt to connect to online services.

Thursday, September 16, 2004

Navigating Savi

On the PDA or tablet there would be an eight way centred joystick under Bob's left thumb. Pressing the joystick would step the focus through the four permanent panels. Pressing and holding would step the focused panel through normal, larger and full screen. Nudging the joystick left or right would tab through items or options in the panel and nudging up or down would either scroll through the view of a panel or change the value of tabbed options.
On the desktop the screen edges could be activated to replicate the joystick; slamming the pointer against any edge would simulate nudging the joystick and a mouse button under the thumb would simulate pressing the joystick.
Screen corners could be used for quick jumping. An open document could be slammed top left for later reading; an item or clip could be slammed top right to the temporary stash; contacts could be slammed bottom left to add to the speed dialling list; bottom right could be a screensaver or hardware status display.

Saturday, September 11, 2004

Savi Target Points

The timeline includes a clock. When you click and drag the clock it becomes a countdown timer. The more you drag down the longer the time - the further to the right, the greater the sensitivity of the timer setting scale. Releasing starts the timer and produces a bar from the Now terminator on the timeline, into the future. As Now passes the end point an alarm sounds and the end point is now dragged by Now to become a count up timer. Clicking the bar causes the clock to show the bar's current value. Later, the bar can be dropped in the database panel to produce a preset timer for later use.
All objects that have values that can be varied have target points on them. Clicking and dragging an object may move the actual object, but clicking and dragging an object's target point pops up magnified scales of values that can be changed. Any movement left or right would switch scales and any movement up or down would scroll through the available values.
Expanding on that -- registered value types within documents could have their own target points; the phrase, "A temperature of 180° Celsius" could be clicked to show a scale centred on that value and its Fahrenheit equivalent.

Savi Scheduling

Bob has scheduled a meeting for Friday at noon, lasting for one hour. He decides to change the date and time. If he clicks on the meeting and drags up or down the duration of the meeting changes. If he drags to the right then a new sub-scale appears under the meeting showing several hours either side of the meeting.
Further to the right a sub-scale shows the whole day, followed by the week, month and year. At any stage he can slide through a scale and then left to zero in on a new start date and time. Releasing the meeting over a day causes it to change into an all day event; dragging the all day event down makes it a multi-day event. Details about whether to repeat the meeting or whether to be reminded before-hand are handled by the properties panel. The document panel is used for the agenda and other meeting notes. Other contacts or groups dropped on the meeting or its notes will be invited.
Bob's moving the meeting will cause the other contact's to move as well, and to cause them to flash, prompting confirmation of attendance. Bob's copy will stop flashing when everyone has agreed to the new time. The planned meeting is now a discussion group that will expire when the meeting starts. Any of the invitees can add to the meeting notes and edit any documents attached to it.
Selected meeting notes could be dragged onto the timeline to make a separate meeting; with all items resolved in time, the actual meeting could be dispensed with!
Projects or tasks could be handled in a similar way. A task would be dropped on the expected completion date and dragged up to extend a timeline ending in a start date. Extending to the right of the task is a percentage completed bar. Its length is determined by how many items remain open in the task's document panel. If, over time, the task crosses the current date and time on the time line then the task is either carried along with Today or develops a new timeline extending from when it should have been completed to now. Dropping contacts onto appropriate sections of the task's timeline turns the task into a project.
Any uncompleted object can be handled in the same way - an unfinished ebook, an incomplete document, a website to be revisited. Any of these objects can be dropped into the future to behave just like tasks.

Friday, September 10, 2004

Enhancing Savi

Lisa is a software developer. She decides to write an image editing program for the Savi operating system. She downloads the software developer kit and reads the manuals where she is told the following:
Programs are never stand alone. They can only be enhancements to the existing four panel interface.
There are no traditional menus or toolbars; items are first selected and then the properties panel reflects the current state of the item. Lisa's program would add the capability to adjust various properties of the selection. When writing the elements of her program, Lisa would list the performance requirements for each function. If the block was in the PDA which has less performance than the desktop, certain properties of the image selection may not be visible for editing.
Mac is a software developer as well. He wants to write a budgeting application. He would be required to create a new type of stationery for use in the document panel to represent deposit and withdrawal slips and the results or projections would show up in the database and timeline panels. His program could enhance the selection properties of any number or currency displayed, no matter what type of stationery it was sourced from.
Wherever possible, applications would pull data from that already in storage. So Mac's budgeting program would show banking details from Bob's existing bank account info, and get foreign currency rates from Bob's bank. There would only ever be one master object physically located in the block for each file or piece of information. All instances of each object would be pointers to the original so that if the original is changed then all instances would reflect the change; if Bob changed banks then that would be reflected everywhere.
If Bob decided to buy Mac and Lisa's programs then they would be purchased using Bob's bank via his block and downloaded to his block; he would not be able to transfer them to another block. If Bob sent some output from a purchased program to someone who didn't have the program required to view it then the recipient would be prompted to purchase the program using a form in the Properties panel, already including the recipient's banking details; a portion of the proceeds would be forwarded to Bob as a commission.