Proposal for a Google Web Machine (GWM) that would integrate the whole Google web environment and unify the programming and construction of web presentation of Google products like Blogger, Page Creator, Sites, App Engine, adsense, Apps, etc
1. Shareable libraries/widgets based on Blogger Template programming. 2. Common widget structure. 3. Establish Google namespace to facilitate private, group or global sharing. 4. Google Web Machine to facilitate component API for Scripting 5. Concept of Google Web Pages 6. Compartmentalised for Apps, Web, Mobile & Streaming. 7. GWT to accomodate the proposed concept. 1. XML programming in the style of Blogger Templates. Blogger template programming is currently very tedious. Single file programming should be retained for non-advance users. Blogger templates should be allowed to be broken up into multiple files for advanced users: - The variables section - The css section - The widget section - The includeable section - The main page By breaking them up into files, a programmer would no longer need to recode standard widgets, includeables and css that are often repeated. The variable section is actually a virtual section because the variables change according to the font and colour configuration wizards of Blogger, Pages or Page Creator. Google should also foster intra-Google commerce by allowing independent programmer-entities to make a living off construction of components by establishing a Google commercial eco-system. Where exists a component authentication protocol either for metering, regular licensing, one-time purchase or adsense embedding. Of course, Google should receive a percentage of such commerce. The commercial eco-system would certainly not preclude the ever enthusiastic open-source component sharing that would dominate such a shared component framework. 2. The widget concepts on user start page (igoogle), Blogger and Sites should be the same. A widget or component should be useable anywhere within its compartment role. 3. A namespace convention would help differentiate the scope of a component. Shared library components may be private to the user, group or submitted to Google for global use. Google should allow users who prefer to group together and share code among themselves only. 4. A user may prefer to use scriptable means rather than to construct components. Therefore a component API would be available for scripting. Google should establish a Google Web Machine (GWM) that would restrict, authenticate and facilitate scripting to ensure components are well-behaved. Google should provide an initial access to the GWM through Python. Google should expose the specification of the GWM so that enthusiastic open-sourcerers may contribute to creating scripting interface for Java, C#, Perl, etc. Once compiled, there would be no difference between components built by script and those built using XML. Complex components would probably be built using both XML and scripting and that would lead us to the concept of Google Web Pages. 5. A Google Web Page concept would not be dissimilar to JSP's. HTML and XML would be the basis of the page. Components would be callable by XML. 6. The GWM would help Google maintain compartmentalisation between Apps, Blogger, Picasa, Sites, Mobile and streaming. Most components or widgets should be useable across every Google product, but some products components with requires specialised roles. Therefore, the GWM would naturally not successfully compile a component with a specialised Calendar role directly into a Picasa page, vice versa - except by having a Picasa page embed a Calendar component, vice versa. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
