Why would I want a web browser inside a web browser?
a calendar client
There are plenty of online calendars. I'm not familiar with calendar clients, but what's the advantage of setting up a calendar protocol server rather than using an online calendar or installing similar software?
Web apps cannot talk imap or to ical whatever, they need to be able to talk to another non web platform that can do these things, usually via requests to a web server.
I am currently writing a web browser in JavaScript for boot2gecko, there is a need
"writing a browser" is a little bit of an exaggeration, since it's just all the chrome being implemented, and HTML rendering is handled by gecko. But, it's still a browser being implemented in js. It's pretty sweet.
I'm working on a tcpsocket API for js for the same project. It's being used to implement an imap client in js. It's all part of the boot 2 gecko project. It's quite fun!
Sounds good. Any chance you can encourage Mozilla to share UDP, TCP, POSIX with those outside of boot2gecko? i.e. someone else who wants to build something like boot2gecko but outside of Mozilla?
B2G is 100% open-source and developed in the open. They even take pull requests and have open meetings. They are going to be taking their work to standards bodies and hopefully a lot of it gets picked up.
maybe you don't want a web browser inside a browser, but think about something like mozilla's boot-to-gecko project. the browser engine is a given, and the browser UI is actually just a web app.
similarly, an online calendar is a calendar client. It interacts with some server somewhere. Same idea with mail - Gmail is an IMAP client.
