Friday, January 14, 2011


dear, I found a good company several days ago, and try to buy some goods,
and I received satisfactory item 5 days later.
Introducing to you: , maybe also useful for you.

Tuesday, January 04, 2005

An Ugly Brick with a Spectacular Screen

HP iPAQ hx4700 Review

I handled an HP HX4700 today. Just briefly -- I don't like the case or the touchpad idea, or the price of this thing. But the display is SPECTACULAR!!!

You have no idea how good it looks until you see one in the flesh. This is the best display I've seen -- on anything! Let alone a PDA. This display on a thumbwheel-controlled phone edition would be the ultimate (now, erase from mind and get back to 240X320).

PDA Navigation Brainwave

Under the left thumb there's a press to click thumb wheel with a home
button above it and a back button below.

Clicking the wheel reveals a
base menu arranged down the left hand side of the screen. Hilighting an
item automatically shows a sub-menu and clicking the wheel moves into
that menu.

All apps would be full screen. Apps would be smart enough
to stay in the last menu as required. System wide and user defined menus
would always be available from the root.

Numbers and auto completing
words would also be accessible with the wheel. A touch strip could be
used instead of a wheel. The response must be instant; no special

A hot corner at the top left of the screen would enable pen input. Click
and hold followed by a turn of the wheel would step through the running
apps. Turning without clicking beforehand would scroll through the
current app.

Sunday, October 24, 2004

New log started (Click here to go there...)

Quite often I feel like posting something into the ether that is not
to do with Savi, so I set up another weblog.

It's called Andrew's Random Stuff at

It won't be anything too profound; mainly random thoughts that I might
want to share, or simply archive. Let's face it. This stuff is fun.
I'm finding that right now as far as blogging is concerned, I'm
clicking on and trying everything as far as the feature set goes. In a
few months I'll start fresh with properly designed layouts.

The second time should be a breeze. A.B.R. (Always be Refining) from kaizen...

Monday, October 18, 2004

Some Random Ideas

If it takes more than half a second to react then people will get frustrated and lose interest. The system must be always poised for input. When using the pen, the recogniser should anticipate the input by the type of field and have the appropriate keyboard standing by. Use gestures to launch functions and shortcuts based on short non-existent words to enter long strings of common text. An example would be writing hh to enter http://www. or cm to enter .com.

Grabbing an object and starting to drag then pausing could cause a list of logical targets to pop up next to the object.

Tapping the title of the timeline would pop up all of the object categories. Tapping the name of an object would show a view with only that object. Checking a name would add that object to the default view.

A services area for printing, backing up, burning to optical disc etc with targets that would be dimmed if the actual devices weren't connected to that particular host. The object could still be dropped, but it would be pending.

Printing paper with labels would have two dimensional barcode that would be similtaneously scanned and re-written by the printer. This would keep track of how many labels were used on the sheet.

The desktop device could include the ability to be always running and acting as a gateway for the PDA in wireless mode. Bob could walk around the house and get mail and news and make phonecalls. Those calls could use the landline. He could use that link to control the entertainment system. The entertainment hardware could be shown in the database panel or as part of a row of buttons that could include other attached hardware.

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.

Wednesday, August 25, 2004

Using Savi

Imagine a block the size of a PC card. The block would contain the operating system, all of the applications or enhancements and all of the documents, music, images and other data files. It would also contain a set of smart batteries. Whatever other device the block was connected to would contain the CPU, display, input devices, modem, networking devices, optical drives etc. It would also have firmware to match the operating system to its display type and input method.
Bob uses the Savi system. In the morning he plugs his block into the family desktop system which switches it on. The desktop charges the block's smart batteries while he checks his email and updates his pages. He pulls the block from the desktop, turning the desktop off and inserts it into his combination phone and PDA. The display automatically adapts to the PDA screen size and pen input. Once in his car he slots the PDA into its cradle and the car tops up the battery. The car stereo now adds the music in the block to its playlist. A call comes in and its routed through the stereo as well.
At work Bob plugs the block into his wifi tablet. When Bob checked his mail at home the desktop dialled up, in the car the cellular phone dialled up, now at work the tablet fetches mail from the company server. The block knows where it is by what its plugged into, Bob doesn't have to do anything. Meanwhile back at home Bob's son plugs his block into the desktop. Nothing that Bob did remains on the desktop so there's no way his son can damage Bob's operating system or data.
A phone rings nearby with Bob's personal ring tone; its his boss calling via wifi and bluetooth through the tablet to the phone. In Bob's database panel his boss's name flashes as Bob picks up the phone. By tapping on the name, the timeline shows recent dealings with the boss and the document panel shows recent meeting notes as well as a fresh note for this conversation. During the discussion the boss sends Bob a future meeting button that flashes in his timeline. It doesn't clash with any other appointments so Bob taps it to confirm the meeting. Later that day the boss thinks of some other things to discuss at the meeting so he sends the note to Bob's meeting button. The button flashes slowly to prompt Bob that its been modified.
A reminder sounds in Bob's timeline to organize his vacation; he's too busy right now so he drags the reminder further town the timeline, effectively snoozing it. Later, when it sounds again he decides to delegate by dropping the reminder on his assistant, making the task hers.
This morning the video recorder at home spoke to the desktop and added the most recently recorded shows to Bob's timeline. He tags the shows to watch tonight and selects some more for recording from the schedule, including a training video that shows up in the corporate tab that now appears in his database panel; dragging the video from the corporate tab to the timeline of tonight downloads the video to the block because Bob won't be at work to watch it.

Saturday, August 21, 2004

Web Spaces

Every Savi user would have their own web space. They would drop text and items on their local version to have the remote version updated automatically. Navigation and other dynamic elements would be updated automatically at the same time. Most of the visual design elements shown on the web page will have been fetched, not from the remote site, but from the local effects library within the Savi operating system even when browsing other Savi user's websites.
If a page contained a piece of data that was often updated, like a "What's New" list or the latest stock price, that piece of data could be dragged as a package to any of your own pages. Whenever you are online it will be updated with the latest version of the data.
For sites with a lot of pages of text, read the first page while the rest of the site is being downloaded as a zip
Instead of sending files attached to messages, users would be encouraged to send a button linked to the remote file and the recipient could then have the option to open or ignore the remote file.
The management of your own site would be totally seamless. You would look at your site in exactly the same way you would browse anyone else's, but you would be able to directly edit and add to yours. Any document that you create locally would use basically the same web-biased technology, so at any future time you could choose to "Publish" and it would be added to your website.
From webpage to timeline
A webpage could mention an upcoming date and show it as a distinctive looking button. Dropping that button on the timeline would schedule a new event with all of the details filled in. The timeline can be told to fetch other events from the same publisher. The view of the timeline can be refined to show only those events. Some examples:
· Tide charts
· TV schedules
· Bus and train times
· Club meetings
Events could be linked back to the publisher for ordering tickets.

Friday, August 20, 2004

The Savi interface

The Savi interface is dominated by four panels that are always present. These are, clockwise from top right:
The document panel
This is the primary panel and it normally dominates the screen real estate. Images, articles, messages and movies etc. are always displayed here.
The properties panel
If any item is clickable then the resulting information or options will be displayed here.
The timeline panel
Every action taken by the user is time stamped and recorded on the timeline. The timeline is the primary means of refering to things done or things looked at. The timeline also looks forwards at meetings and reminders.
The database panel
Every item can be categorized and listed in the database panel. Broad categories could include contacts, collections, document types etc.
An in depth look at each panel:
The document panel
At its top is a horizontal bar displaying the document date, the type, the author and the title. If the panel was displaying a web page then the author would be the website and the title would be the title normally seen in a browser. Click and hold on one of the fields to show a list of recents followed by an alphabetical list for jumping to other documents. Click and release a field to change its value. In the case of a web page, changing its title causes the page to be permanently saved.
While you are looking at the web page an email message arrives from Peter. Peter's name flashes in the database panel. At the same time "Message from Peter" appears in the timeline. Clicking Peter's name causes the message to display in the document panel at the foot of the continuous roll. As well as text, the message contains a link and an image. The message can be scrolled while his signature remains fixed in a separate sub panel at the bottom.
The link appears as a button, hiding the address; it can be clicked to open the link, or dragged to the database or timeline. When held over the database, various logical categories and destinations will cascade and when held over the timeline, a view of the near future will expand for it to be dropped for scheduling. The button could be dropped on a name or group, initiating a message that contains the button. It could be dropped on the local version of your website which will update the online version.
If the image where dropped on your website you would have the option of using that image, or linking to Peter's original. If you chose to then "focus" on the message from Peter then the database would show all items linked to him, the timeline would show all dealings with him and the properties would show all of his details. If the Savi where connected while you were looking at Peter's details: Clicking his address would show a map and his location with the option of directions from here to there. Clicking a phone number would call him and record it in the timeline; a fresh note page would appear in the document panel. The properties panel would also contain a checklist of things to mention to Peter. His instant messaging address would show if he was currently online. Naturally, if you clicked it a chat would initiate in the document panel

Wednesday, August 18, 2004

Alternative OS

As it's the twentieth anniversary of the Mac I've found myself over the last few days reading articles about the original development of the Mac, Star, and Lisa; how they came up with and honed the various interface elements. It's all stuff that we're now familiar with and consider ubiquitous, such as scroll bars, windows, icons etc. The current state of the interface art seems to work quite well, but I do think there are alternatives -- major alternatives really, when it comes to the very idea of launching applications to perform tasks.
Years ago I was one of the first to get my hands on an Apple Newton, and I've had every hardware version since then. The Newton was a computer -- in that you could download software into it, and it was very flexible in how you used it -- but because it was a handheld they took the opportunity to start again from scratch with regard to the interface and what metaphors it would use.
Instead of using a desktop as the back bone of the OS, they chose a notepad, or rather, an endless roll of note paper.
You didn't create new notes, or save them or name them. You simply drew a line across the screen and wrote something new below it. The OS then turned the line into a separator and date stamped it, using the first few words of the note as a title to be used when viewed in the overview mode. Third party developers wrote enhancements for the OS that made the notepad incredibly powerful, and easy to navigate.
When going back to an earlier note, the first thought wasn't "what did I name it," or, "where did I file it", but rather, "when did I write it?" This reference to a timeline seemed such an obvious and natural method of searching that I began thinking about how it could be used in a fullsized setting -- for everything. Not just notes created or edited, but having every activity recorded on the timeline. If the timeline projected into the future as well it could also serve as a scheduler.
I imagine something vertical that could be zoomed or filtered to reduce clutter. With the resolutions available on today's screens it could be a permanent fixture of the OS. If the timeline was a column that was positioned at the lower-left of the screen then above it could be the data column. The first use for the data column would be as a list of contacts. Other categories could include websites, inventories and collections, any sort of quick reference lists. That leaves the rest of the screen which would be primarily made up of the content screen.
The lower portion of the content screen could double as a context, or properties screen. If an active item is clicked but not activated then relevant information would appear in this lower right screen.