builtins.webApp

Last update: Thu, Sep 1, 2011 at 6:08 PM.

builtins.webApp

Now that the new OPML interface is out, it's time to factor it, so that the same techniques can be used by the websites of the Tools, without replicating code.
Let's start a new builtin table, webApp. There is webBrowser and webServer. This layer adds menus, prefs, etc.
1. I factored the rendering code from builtins.opmlEditor into builtins.webApp, and made the modifications to the template for the opmleEditor website.
2. Then I started work on River2. Changed its menu routine to use webapp.viewmenu. I was able to access almost all parts of my local River2 website, and the styles mostly work. There are a few colors that are wrong. I have an idea what the problem is.
3. Now I'm going to check in these changes on my test server, one that's really running River2. Once I get it working there, I'll release the modifications to builtins.opmlEditor, the first release of builtins.webApp, and a new version of River2.
- builtins.webapp
- river2Suite.viewMenu
- river2Website.["#template"]
- opmlEditor.data.outlines.catalogIntro
- opmlEditor.viewCatalog
- opmlEditor.viewMenu
- opmlEditor.website.["#template"]
- opmlEditor.website.styles
4. Time to call it a day. Very productive even though not a lot of hours at the keyboard.