Jun 30, 2011, 6:38:09 PM6/30/11
Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message as abuse
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
This is a very good question,
I think the increased test coverage, documentation, API review and better debugging can only help developers working on Shell.
The distributed development approach will be great for implementing modules for Shell which wouldn't be useful for most (desktop app) projects which use Chromeless.
The improvements for Web Content Embedding are absolutely essential (for Shell bugs currently scheduled for the next release). Things seemed to have slowed down a little recently with commits to Chromeless but maybe there are things we can do to help with these blocker bugs?
I don't think the size optimisations are really essential but depending on how it's implemented, an application update feature could be used to update Shell itself.
The ability to use a "shared runtime" could be very important if we want to use a packaged version of XULRunner and create a package for Shell.
As for better communications about Chromeless, what's good for Chromeless is good for Shell!