Another Browser Editing Experiment

  I am starting this post in scripting2's workspace.
  I am keeping it simple, 3 nodes below the summit/title.
  My next modification to this post will be from iJot.
  I just clicked iJotEdit, a bookmarklet in my Safari browser's bookmarks bar, and I am now modifying this post in iJot.
    Adding html links to text in iJot's webOutliner is a lot simpler than in scripting2's outliner.
    I have just added 2 nodes to the post, with 2 level 3 nodes that should be rendered as subtext by scripting2 in the HTML version.
  I'm now saving this version in iJot, my next step is to check the rendered version, then re-open the post in scripting2.
  SUCCESS: The HTML version of this post was perfectly updated by the scripting2 server.
  I clicked the 'edit' button on the page, and I am now back typing this in scripting2's outliner.
  This is indeed very cool.
  One caveat though... I am modifying this post in the OPML Editor's outliner, but in a *different* window than the scripting2 workspace.
  There is still a version of this post in the workspace, but it is the initial version, before any in-browser modification.
    This may become confusing. I suspect that if I add another node to the version of the post kept in the workspace and save it, it will overwrite all my previous modifications.
    We may need a 'Refresh' button in the workspace, or a Refresh Post' right click menu option, to update the selected post in the workspace, just as the 'Save' button saves the selected post.
    Or maybe someone may think of something even simpler.
  In any event, this is my last modification to this post, now back in iJot (I clicked iJotEdit again).
  Dave, I think we nailed it. I am going to focus on step2 of my integration program: creating new scripting2 posts in iJot.
  Anyone interested can repeat my steps. Just remember to start your initial post with scripting2 version 0.29 or higher. You can update your own copy by following these steps.