Web Desktop (webtop)ΒΆ

date:Feb 12, 2009 @ 14:52

First of all I thought about implementing a Web Desktop client application.

A web desktop or webtop is a desktop environment embedded in a web browser or similar client application. A webtop integrates web applications, web services, client-server applications, application servers, and applications on the local client into a desktop environment using the desktop metaphor. Web desktops provide an environment similar to that of Windows, Mac, or a graphical user interface on Unix and Linux systems. It is a virtual desktop running in a web browser. In a webtop the applications, data, files, configuration, settings, and access privileges reside remotely over the network. Much of the computing takes place remotely. The browser is primarily used for display and input purposes.

One thing that could be quite neat is creating a specific SolidWorks Webtop specifically for the Mini9 (or other UMDs).

Whether it should run in the available web-browser or as a stand-alone client application remains to be determined, however running from within a web-browser eliminates the need for different versions for different devices.

2 samples of browser based Wee Desktops are Eyeos and the DHTML desktop.

EyeOS

The self-styled Cloud Computing Operating System. The idea of eyeOS is to create a free, open source product easy to install on a web server so you will have your own cloud system under your control. You can also participate in a great community of users and developers, able to create your own apps.

More details about eyeOS are available from the related web-site at

http://eyeos.org/

DHTML Desktop

Based on Dynamic HTML (DHTML) and Javascript, the DHTML Desktop is another example of a Web Desktop.

_images/2009-02-12_1429.png

Conclusion

The approach used by DHTML desktop is a little more restrictive (proprietary) than with EyeOS (OpenSource) but both lend themselves as good demonstrations of the technological concept.

Both these samples have been available for a long time and in some respects, WebTop concepts generally, have fallen out of fashion.

The approach, however, is a zero install application. All data and applications are stored remotely and you NEED a web connection in order for it to work. The idea can be extended for SW and possibly incorporate some of the technology available with Google Gears for on-line/offline working and data synchronisation.

Another item which may have some value is with the possible collaborative nature of the WebTop where multiple users could be accessing shared data through the remote file-system.