New version of bookmarklet, a few improvements. 

My warmup project for today was to write a linkblogging bookmarklet for Scripting2.  

I started to put it together, but when I went to the place where I would write the code, I found it was already there. Huh? 

So I searched the Changes page for "bookmarklet" and found it. Now it's all starting to come back. 

http://scripting.com/stories/2010/06/29/scripting2ChangeNotes.html#p601 

We're back! WIth a new and improved scripting2.root -- with users!  

It's now possible to run your own server. Here's the howto. I added some new sections that help you set up your server after the initial steps, and show you how to add new users. 

Other updates today bring us up to version 0.42. If you're new to scripting2, it pays to review these change notes. There are actual docs in here.  

Today's fixes: 1. New User command in the Scripting2 sub-menu of the Tools menu. 2. The nav links at the top of each page were broken, should work again. 3. There's now a default header image for new sites, I felt the sites looked too stark on Day One.  

This version does not have the Instant Outliner. 

It has been pointed out elsewhere that the current release gets a scripterror about missing callbacks.  

The sub-menu for I/O should be removed. But otherwise, I'm going to leave the code as-is. 

I am also starting to update Scripting2 through the normal updates mechanism. Its period of rock and roll is now behind us. 

Small change -- when you click the Refresh button in the Buddies window, only those buddies whose outlines have changed are refreshed. If none of them have changed, a dialog informs you of that. 

The realtime updating code behind the Instant Outliner was rebuilt so that it runs in the main part of the OPML Editor, not in scripting2.root. This is because the code seems so useful that I'll want to use it in many other places. The time to refactor it is when it's fresh and there are a small number of users. So this may cause a disruption, if so, I apologize in advance. (But there's a chance it will "just work.") 

You have to install version 0.35 to be able to see other people's updates. To do so, just choose the Reinstall scripting2.root command from the Scripting2 sub-menu of the Tools menu. Open your instant outline and create a new entry and save. If all goes well you should see your name update in the Buddies window, and so should the rest of us. 

As usual, report any problems on the Scripting2 mail list. 

Added Refresh button to I/O buddy window. When you click it, we connect to the server and get the latest copies of the outlines from all members of the workgroup. Each buddy's name boldens. When you collapse/expand their name you'll see their latest stuff. This is how you get updated when you come back after being offline. 

Eventually this will be integrated into the opening of the buddy window, so you won't have to click the button, but the button will probably stay in the user interface. 

Scripting2 now has an instant outlining capability. This means that members of a workgroup, the people who use the same server to host their blogs, can privately share notes about their work with the other members of the workgroup. 

1. Update your copy of Scripting2. Choose Reinstall scripting2.root from the Scripting2 sub-menu of the Tools menu and click OK to confirm that you want to replace Scripting2. (I had previously said this wasn't a legit way to update, that was a misunderstanding -- it is.) 

2. Choose Open My Outline from the Instant Outliner sub-menu of the Scripting2 menu. 

3. Click on the New Entry button, type something and click Save. The rest of us will see your name appear in our Buddies window, and your name will be bold. When we 2click your name we'll see your updated outline. Naturally, the same goes for you if you open your Buddies window.  

You may not see anything happen for a while. It depends on who's at work. I will put a Refresh button in soon that allows you to instantly see all the outlines for everyone in the workgroup. 

New button in Edit window -- Delete 

First cut at a link-blogging bookmarklet, below. 

When the user sets the name of his or her blog or the time zone etc on the Prefs page, rebuild the blog. 

You can now enter time zones that are greater than zero. The allowed range is -23 to 23. 

When saving a blog post in its own window, we now preserve the window size and location. 

Removed the Blogroll button in the Workspace window. 

When the OPML of each story is saved, we include the server XML-RPC address and the username as attributes on the summit headline. You can see these atts in the OPML for this page. Thanks to Marc Barrot for this excellent suggestion. 

Adding blog posts to the Bookmarks menu was broken by a change made to eliminate duplicate text attributes on summits. Fixed.  

RSS feeds now take their title, link and description from the blog prefs if they haven't been set independently (right now there's no UI to set them). 

For the generator of RSS feeds, use the version of Scripting2, not the version of the OPML Editor (which almost never changes, and isn't very relevant). 

In the last version, when I "improved" the first-time user experience, but I actually made it worse.  

When saving a post, if the table of contents needs rebuilding, rebuild it. (Technically, it needs rebuilding if your post is in a new month, if the TOC doesn't have an entry for that month.) 

Welcoming two new users, Carla Cassilli and Russ Lipton. 

Improved the first-time user experience, esp when I'm not physically present to help. When the workspace is created, we set a flag that says it's new. The first time it's opened, make a quick call to the server to set up a Hello World post, and insert that headline in with all the proper attributes, and create a first subordinate headline, and put it in text mode.  

Somewhere along the line the ability to change the title of a post by editing the headline was broken. Fixed it. To change the title, just edit the top headline and click the Save button. 

After much wrestling with CSS and with much help from scripting.com readers, we now have N-level hierarchy working in the story editor. You can read about it here and here. The hero is Daniel Kurejwowski, who laid it out in step-by-step instructions even I could follow.  

To get it to work on your system, however, you're going to have to make changes to your stylesheet.  

If you haven't made changes to your stylesheet, follow these instructions carefully: 

If you have made changes to your stylesheet. 

The Install script now opens the Workspace and opens your browser to the Getting Started section of the Scripting2 home page. 

Made a change in the OPML we generate. The first attribute of <?xml> must be version. Marc Barrot's outliner would fail on reading our OPML, so I hacked the output of op.outlineToXml to conform. Here's an example. 

Major shakeup on the server, but shouldn't have any impact on users.  

Fixed the problem with Blogroll window opening without buttons the first time you open it. To get the fix, in addition to updating Scripting2 to v0.22, you must also update opml.root. The command that does this is in the File menu. 

Lots of little UI tweaks, you'll stumble across them as you use the software. 

The big change in this release is that you get to manage your own Disqus comments, or decide if you want them or not. 

There's a new pair of prefs that turn comments on (they default to off) and allow you to tell us what your Disqus "shortname" is. Screen shot. 

After you set the prefs, you have to save a post to have them take effect on your blog. 

The advantage of having each of us with our own Disqus setup is that you can get the emails for your comments and I can get mine, etc. You can also determine your moderation prefs on Disqus. It's an excellent product, I've been using it for years.  

Various cleanups in the OPML generated that's attached to blog posts. Set the title of the OPML we generate and the dateCreated. Also it generates, for some unknown reason, a second text attribute on the summit headline. We get rid of it using string processing. Working around a bug somewhere. 

For example, here's the OPML generated for this post. 

In this version we make it so that the Edit button only displays in pages you can edit. To do this I have to hack the storyTemplate for all of you guys. Hope you don't mind.  

It will only work on stories created with v0.19 or greater. Older stories you'll have to be careful about editing (but you shouldn't have to worry about saving them). 

The update to v0.18 is mandatory. Previous versions will not be able to create new posts on the server because there was a protocol change.  

Protocol change. When the user clicks New Post in workspace, we send a message to the server with the title of the post and it returns a token that it stashes in a table. 

The first time the post is saved, if the token is present, it goes through as before.  

However if the token is not present, the save fails with an error message. Something like "Can't save the post because we don't recognize this format."  

Hopefully no one will see the message, but if they do, it will generate bug reports and hopefully will be reproducible -- since the error will happen closer in time to when the action that caused it occurred.  

I'm hoping no one sees it. "> 

1. Choose Tool Catalog from the Misc menu. 

2. Click on the Install link next to Scripting2. 

3. Click OK to all confirmation prompts. 

You can now save a post by pressing Cmd-S or Control-S or choosing File/Save with its edit window or the workspace in front. 

We now log RSS builds. 

1. From your graphics program, save a copy of the image into the images folder. By default this folder is a sub-folder of the Scripting2 folder in your OPML app folder. 

2. After a few seconds a clipboard window appears in the OPML Editor with the HTML text for the image.  

3. Select-all and paste it into your blog post. It will appear right-justified. If you want it to be inline, delete the align="right" attribute from the <img>. 

Big feature in this release -- lots of new settings on the Preferences page. To get there, choose Preferences from the Scripting2 sub-menu of the Tools menu. A web page opens. You can change the name of your weblog, edit your name, email address, timezone, the name of your timezone and your weblog's tagline or description.  

Added logging when you create a new post or edit an existing post. There is a log readout page. This is a community feature, the first one. "> 

New command in the Scripting2 sub-menu of the Tools menu allows you to set the header graphic. 

To begin, in a graphics editor, create the image. It must be either a GIF or JPEG. 

In the OPML Editor, choose the Choose header graphic command from the Scripting2 sub-menu of the Tools menu. 

A dialog appears asking you to locate the file.  

Once you click the Open button, the file is uploaded to the server and your home page is automatically rebuilt. 

To see what the new header graphic looks like refresh the home page of your weblog. 

To test the command, I've changed the header graphic on scripting.com. 

The big feature in this version is support for an images folder. 

The folder is created by default as a sub-folder of the Scripting2 sub-folder of the OPML folder (the one that contains the OPML application). You can change the location of the folder through the Preferences page. 

To upload a picture, drop a copy of it into the images folder. With ten seconds it will be read and uploaded to the server and the HTML text of an <img> will appear in a window. You can then paste this into a blog post. 

At this point there is no limit to the size or number of images you can upload, however there will probably be a limit at some point in the future. 

A copy of the image file is also placed in the backup folder on your local hard drive. It's also configurable from the Preferences page. 

The image of the soccer ball to the right was uploaded with this facility. "> 

Note: I installed 0.14 on the edit.scripting2.com server.  

There's now a rudimentary browser-based Preferences page.  

You can access it through a command in the Scripting2 sub-menu of the Tools menu. 

It's also accessible through the Preferences command in the Misc menu. 

You can now map a domain to a blog post. Here's how you do it. 

1. Through your registrar, create a new CNAME record and point it at mapper.scripting2.com. 

2. View the blog post that you want to map the CNAME to in your browser and click on its Edit button to open its source code in the OPML Editor. 

3. In the OPML Editor, right-click on its title headline. Choose Map Domain from the pop-up menu. 

4. Enter the CNAME created in step 1. 

5. Save the post. The mapping doesn't take place until you do the save. 

6. You should now be able to enter the name in your browser and it should display the post. 

I used this feature to map changes.scripting2.com to this post. 

New option in right-click menu allows sub-text to be initially visible instead of hidden. This document, the change notes page, uses that feature. The role sub-text plays in this document is different from a typical blog post. Not sure whether this text should appear in the RSS feed. I'm assuming it will largely be used for posts that are not part of the weblog's chronology. 

Standalone edit windows qualify as editing windows. You can now create bookmarks in these windows. The right-click menu works in these windows. 

The extra commands in the right-click menu now only appear if the cursor is pointing at the title of a blog post. 

Added a command to the Tools sub-menu that upgrades scripting2.root to the latest version without me having to send a copy via email to each of the testers. 

scripting2.root now has a version number. We're starting with version 0.11. You can see the version number by jumping to (Cmd-J on the Mac) scripting2Info.version.  

You can now bookmark a blog post to edit it later. To do so, place the cursor somewhere inside the post and choose Add Bookmark from the Bookmarks menu. A confirmation dialog appears. Click OK. Now when you want to edit the document just choose it from the menu. Particularly useful for "standalone" posts that don't appear in the blog's chronology. 

When creating a new post, we create a blank line under the title headline. The attributes of that line weren't being set. Now we call the opInsertCallback set the attributes. 

Wrote a doc explaining how to turn on the Bookmarks menu in the OPML Editor. 

Paragraph permalinks run off serial number. 

Getting ready for 1 or 2 non-Dave users. (Prepare for this by starting a second blog.) 

Edit This Page buttons. 

Right-click menu in editor. 

Paragraph-level permalinks as a pref. 

Added a mini XML icon under the blogroll linking to the OPML. 

When opening the blogroll, stylesheet or a template locally, if we already have the outline locally we don't get it from the server. If it's already open in a window we just bring it to the front. 

Added discovery link for blogroll in both templates. Add discovery link for story source OPML to story pages. 

Added day of week to byline text and the "last updated" text on the home page. 

The day level Next/Prev links were all fucked. The AddPost routine was initializing the links whether or not the post was new. Now it only does it if they are new. Wrote a utility to fix all the links in case we ever need it again.  

We save the templates to the site, and include a comment (automatically generated) in the HTML that says where they are. This way you get a View Source capability for all Scripting2 blogs, automatically. It is on by default but there is a pref as well.  

Click on a permalink on a story page, now you go to the beginning of the paragraph, instead of the end. There was confusion between the two uses of the same ID. 

The blogroll is saved to the website as an OPML file. 

scripting2.com placeholder site is up. 

New Tweet button in the Editor window. 

When you change the title of a story the URL stays the same.  

When you create a new story the previous story is rebuilt because its Next link changed. 

The first time you update in a day, all the other pages in the month are now rebuilt because their calendars have a new day. 

On the home page, the most recent day's stories are expanded, all other stories are collapsed. 

There's now a UI for editing the stylesheet. It synchs immediately when you save it. 

When you save the blogroll the Home page is rebuilt. 

The blogroll is now editable. 

Third-level text is implemented (it was #9 on the original to-do list). 

Display bugs in expand/collapse on home page were fixed (#13 on the original list). 

Finish documenting the API. 

Bookmarklet for linkblogging. 

Referencing pages with custom domains can be more efficient. 

Why are windows losing their size and position values? 

Connection between link-blogging and Twitter. 

Display the version number someone in the UI. 

Inclusion. 

Easy UI for attaching a podcast to a post. 

Build a first version of the AMI for the server. 

An RSS feed for the community. 

Editing the glossary. 

Previewing a post before publishing (a Publish button, possibly replaces the Build RSS button). 

As an outline leaves the OPML Editor, change the type attribute of non-standard types to be namespaced, to conform to the OPML 2.0 spec.  

Template library. 

The CMS should be fully time-zone-aware.