On Oct 18, 11:53 pm, Sam <[email protected]> wrote:
> - Sandboxed but not limited to the confines of a web page (OS APIs,
> granted by the user)
> .... All that is need after this, are some APIs that allow for the
> application to take
> advantage of the power of the OS (files, data storage, cross
> application messaging, etc.).
I totally agree with you Sam. This is what Adobe missed out on and
they still don't get it!
Most users don't really want to download something that's going to
hurt our PC and developers at the same time would like API features
to be made available for special purposes.
The idea of allowing the user to select the type of functionality for
the app is the way to go. If I can download a music player app that I
can grant access to a folder for playing music that that would make
things much better than having to worry about what's going on inside
the app and if it's doing more than what it should be doing.
With the web we have this Sandboxing so we don't have to worry too
much when we visit a website that the security of the browsers (even
thought there are times when things do go right).
Here how I see it working
Chrome Engine
----------------------------
1. Chrome Window- UI Renderer
2. Special Access Manger - Use can control what special features and
capabilities the app will have
3. Offline Web App or Online Url - Application source files or url
So does anyone from Google likes the idea?
--~--~---------~--~----~------------~-------~--~----~
Chromium Discussion mailing list: [email protected]
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-discuss
-~----------~----~----~----~------~----~------~--~---
