On Tue, 31 Oct 2006 06:14:08 +0100, Trace Bond <[EMAIL PROTECTED]> wrote:
*snip*
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
3) An example of a future "Web Application"/"Rich Web Client" might be
illuminating. Allow me to suggest one and you can then tell me whether my
understanding of these concepts has any foundation: my suggestion is a
"WebDraw" program and here is how it could be used:
A grafic artist waiting in an airport lounge decides to work on his
drawings. He/she finds an Internet-connected computer located in the
lounge,
starts its browser and downloads the "WebDraw" program from the "WebDraw"
Internet server. Using a file-download interface (enabled by the proposed
"File upload? API to manipulate files on the client"), he selects a PNG
grafic file from his own file server located back in his hometown. The
file
is downloaded to the airport computer where the "WebDraw" program copies
it
to memory and displays it on-screen. The artist wields the computer's
mouse
to-and-fro and "WebDraw" (using the proposed "DOM Level 3 Events") adds
lines & shapes to the drawing. When his airplane is about to board, he
closes the "WebDraw" program which copies the modified memory to a file
and
uploads it to his hometown file server for safe-keeping.
This kind of functionality can now be accomplished using Java
applets/applications, but it would be great if this capability was part
of
some standard ideal "W3C Web Browser" (and pigs could fly ;-)). Please
tell
me if this "WebDraw" example represents the challenge faced by your
working
group?
-Trace Bond
Actually most of what you have described here is possible today using the
standards defined by the W3C and WHAT-WG. Check out this Opera Widget for
an example.
http://widgets.opera.com/widget/4647
Jon
*snip*
