4 ms·

> JsLayout I went looking for Inbox's template engine and came across: https://code.google.com/p/google-jstemplate/wiki/HowToUseJsTemplate https://code.google

by stephen 12y ago

> JsLayout I went looking for Inbox's template engine and came across: https://code.google.com/p/google-jstemplate/wiki/HowToUseJsTemplate https://code.google.com/p/google-jstemplate/wiki/HowToUseJsT... The "jstcache" attribute looks the same. Although, looking at the code.google.com project's source, it doesn't look like any code/non-wiki changes since ~2008. So maybe a forgotten attempt at open sourcing the/precursor-to JsLayout? POA sounds interesting; hopefully it'll have a great unit testing story too?

cromwellian 12y ago
Yeah, that looks like an early version of it, I'll ask why we aren't developing it in the open anymore (it may have been because of rapid changes need by Inbox) The central idea of Page Oriented Architecture is to return to the Web 1.0 era of "A URL for everything", where the application consists of a bunch of pages, and if desired, any page can be rendered server-side. However, what really happens beside the scenes is GWT processes all the pages for the whole site, synthesizes an application, which each page between a GWT "splitpoint". So you have your cake and eat it too. An application that is developed a 'page at a time' with crawlable, indexable, server-side URLs for everything, while at the same time, you get a monolithically compiled, globally optimized, Single-Page-Application out of it. There's an old set of slides here: https://docs.google.com/presentation/d/1JobclkctBvciYZ8CzHIoibykY18_aRraAMk_iVH1tkw/edit#slide=id.g121d24137_042 https://docs.google.com/presentation/d/1JobclkctBvciYZ8CzHIo... However, that's since been super-ceded by a system I'm working on that makes everything look like Polymer, only it's monolithically compiled and optimized, and using ReactJS style virtual DOM-diffing. I want to combine this with DeltaJS techniques and ServiceWorker to produce offline-by-default high performance mobile web apps out of the box.

by stephen 12y ago

cromwellian 12y ago

Yeah, that looks like an early version of it, I'll ask why we aren't developing it in the open anymore (it may have been because of rapid changes need by Inbox) The central idea of Page Oriented Architecture is to return to the Web 1.0 era of "A URL for everything", where the application consists of a bunch of pages, and if desired, any page can be rendered server-side. However, what really happens beside the scenes is GWT processes all the pages for the whole site, synthesizes an application, which each page between a GWT "splitpoint". So you have your cake and eat it too. An application that is developed a 'page at a time' with crawlable, indexable, server-side URLs for everything, while at the same time, you get a monolithically compiled, globally optimized, Single-Page-Application out of it. There's an old set of slides here: https://docs.google.com/presentation/d/1JobclkctBvciYZ8CzHIoibykY18_aRraAMk_iVH1tkw/edit#slide=id.g121d24137_042 https://docs.google.com/presentation/d/1JobclkctBvciYZ8CzHIo... However, that's since been super-ceded by a system I'm working on that makes everything look like Polymer, only it's monolithically compiled and optimized, and using ReactJS style virtual DOM-diffing. I want to combine this with DeltaJS techniques and ServiceWorker to produce offline-by-default high performance mobile web apps out of the box.