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.


Post a Comment

<< Home