W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2007

[whatwg] [Whatwg] Wish

From: Devi Web Development <devi.webmaster@gmail.com>
Date: Sun, 12 Aug 2007 02:42:32 -0500
Message-ID: <3bceeb2d0708120042t4f6d6f35w4e5fc7cb2c536d5b@mail.gmail.com>
First of all, I see no reason additional HTML tags would be helpful or
necessary for what you are describing.

Second, Javascript needs to be provided with more abilities for larger local
storage beyond cookies. Luckily, there has been work on this by the
WHATWG<http://www.whatwg.org/specs/web-apps/current-work/#storage>and
even early implementation
by Mozilla <http://developer.mozilla.org/en/docs/DOM:Storage>.

Third, you venture into a new area which I have not yet seen a formal
proposal or specification for: ability for Javascript to access, save, and
generally manipulate files. This is a logical step, the browser is becoming
almost as an operating system on top of your operating system. The web
applications often have nicer interfaces thanks to the ease of XHTML, CSS,
and Javascript. Some web applications are trying to replace desktop
applications altogether. Under careful security parameters, the same XHTML,
CSS, and Javascript pages ought to be able to perform the same kinds of
tasks as any computer application.

There are several ways of doing this. WeBMartians
<webmartians at verizon.net>pointed
out that LiveScript originally had abilities permitted only to local files.
This is the easy way, it would simply let files on your computer do what
files on your computer could always do. For web applications such as Bert is
describing, they could also whitelisted. This should probably only happen
after the user receives a one-time, scary warning message of the dangers to
their computer. That sort of whitelist is probably the best way. Frankly, I
don't really know, but I am convinced that Javascript is the Next Big
Language <http://steve-yegge.blogspot.com/2007/02/next-big-language.html>(well,
at least a language which will continue to grow and prosper) and
should have specifications in place to work with files, even if the security
issues are not yet fully worked out.

------------------------------------------
Daniel Brumbaugh Keeney
Devi.Webmaster at gMail.com
Devi Web Development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20070812/7879eafa/attachment.htm>
Received on Sunday, 12 August 2007 00:42:32 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:36 UTC