Continuing the discussion from Integrating Open Web Apps with the rest of the application:
I've been thinking more about how we're going to have build common application functionality with Open Web Apps, and how they'll work alongside apps in the Reference Application.
One idea: we move the reference application's CSS style guide out of the UI Commons module and into a new "UI Commons Open Web App" we create for this purpose. (We'll need to switch the standardEmrPage decorator in the App UI module to refer to this, and add a way to package OWAs in the reference application.)
We should also put some common reference application things like page decoration and global navigation in the same UI Commons OWA. (I guess we start doing these in AngularJS, and think about how to generalize across technologies as a separate piece of work.) While doing this, we should also refactor so that it takes the minimum number of modules running to build an OWA that's consistent with the refapp UI.
For example currently the refapp gets session details from a REST service in the App UI module (which itself requires the uiframework, appframework, uicommons, and webservices.rest modules). We could move this REST service up one level to the appframework module, but we might actually want to move it all the way up to the webservices.rest module. (@burke, @pascal, and others, how do we feel about moving more application logic into our core REST web services? E.g. having a sessionLocation set in an HTTP session attribute, and the logic for deciding which provider account is active. A refactoring of the stuff here.)
Also, on the thread I forked from, I mentioned that we'll need a way to let OWA zip files add apps and extensions to the App Framework. That's still true, and we should go ahead and ticket this.
Any thoughts? (I wrote a bit of code for this on my last flight, so I will share that soon.)