An alternative to Markdown in outlines
I missed having expanding outlines, and I want to use the structure in interesting ways in RSS, so I decided to add a small feature to Fargo, that lets us edit outlines as they will be presented, with structure.
This blog post is an example of such an outline. As is the one you're reading right now.
To give it a try, create a headline of type outline with the big + icon in the left margin.
In the Attribute editor (click on the Suitcase icon in the left margin) add an attribute called flMarkdown, with the value false. When you're done the atts should look like this screen shot.
Then add some outline material under the headline. It's important to indent a few times and add structure, or else it'll look exactly like the Markdown-style posts.
When you click the Eye icon to view it, it should have wedges that you can click to expand and collapse the outline structure.
There are a few attributes you can use to control the way outlines are rendered. They're explained below.
Outlines in RSS items
Each item now has an outline element that contains most of the structure and attributes of the outline.
We don't include comments.
We don't include two attributes: isFeedItem (they are all true, because it's in a feed) and isComment (again, all true, because comments are not included).
The outlines are in the new source namespace. What you'll see in the feed is <source:outline>.
In 1.63 we added macro and glossary processing to the RSS feed builder, but the processing was done in the wrong place. The result is that unencoded XML could end up in description and title elements. This is not legal XML. In 1.64 we do it selectively, before encoding, only in title and description elements.
We also evaluate Emoji codes in the feed.
Fix relating to tweets
While I'm waiting for Facebook to approve the new version of Little Card Editor I thought I'd do a little diversion to solve what has been a thorny problem in Fargo that has prevented a lot of interesting things from happening.
The feed has no pagetable
Okay the feature is in. Now let's see how it works.
And one from the Fargo blog outline: cmsPrefs.opml
If the new feature worked, when we look in the RSS file, they should all be evaluated.
One more thing, let's check a pagetable macro: Dave Winer.
Here's what this text looked like in Fargo.
And here's what it looks like in the feed.
There's one major feature in this release, the ability to render tweets.
A tweet is a headline whose type is tweet. They can appear in any kind of page, of any type.
This is the Fargo side of the connection with Happy Friends.
There is a blog post on the Happy Friends site that explains the hookup from that side.
Get the outline from Happy Friends.
Choose Open by URL in the File menu. Enter the outline from step 1.
That gets you an outline with tweets in Fargo.
Copy and paste those into your outlines in Fargo, and render as normal.
The tweets should show up in your pages as they do in mine.
For a more detailed narrative, with an example, see this post on yesterday's Scripting News.
Fixed a problem where the CMS would think it was seeing emojis in the part of the stream template responsible for phone and tablet-size screens.
Thanks to Jason Cobb for spotting the problem.
You should rebuild any pages that rely on the stream template.
Be sure to reload the Fargo app before doing so.
A new release of Fargo today with one small feature, Emojis.
A good friend showed them to me, a few weeks ago on a trip to San Francisco. I was immediately won over. Charmed by them. It's a new fun language.
Colorful and cute and somewhat irreverent.
The best part is that there's a syntax for Emojis in text-based apps like Fargo.
:baseball: gets you the Emoji for
There's a list of all the codes on the Emoji Cheat Sheet.
As you can see this syntax is already supported by lots of famous apps including Campfire and GitHub. Add Fargo to the list.
The new Emoji feature is on by default, you can turn it off with a # attribute:
We're using the Emojify toolkit. It went in real easy. Thank you.
I have commands in the Links menu on Scripting News that turn images on and off.
You may want to add these commands to the menu of your website, so users can have the option to have images on. It's also useful for debugging.
Here's an OPML file with the two commands. Open the file in Fargo, copy the commands and paste them into the menu you want to add them to.
I did an experiment over the weekend, adding a command to Scripting News that turned off background images. I tried it, and immediately wanted to keep them off. The text is much easier to read. And that matters a lot. I wanted to get some experience with images in the background, and I did get that experience. It'll show up again in another context. And you can still have the images now, if you want them. So that's good. Nothing went away, the defaults changed.
Scripting News is the demo.
Add #streamVersion "1" in your cmsPrefs.opml file. You should get the same behavior as before v1.59.
If you want the new version, you shouldn't have to do a thing.
Here's a list of technical changes that were made. If you don't care you can skip this part.
We don't generate the .divStreamTopSpacer element.
Copied fonts into fargo.io/code. Faster loading, not relying on Google servers, avoid possible breakage issue.
Section heads are bold, Ubuntu.
Increase density of foreground text. It's opacity goes from .9 to .98. Also background color changes from white to whitesmoke. Border color goes a little darker to gainsboro.
divStreamDay needs styles for background image
added these styles:
divStreamDayImage goes away
in first version, if there was a backgroundImage att on the day, we'd generate a divStreamDayImage element with the background image as its background.
in the new version, we don't do this. the backgroundImage data is on the day div, and we can add the image at render-time
There's just one very small change in this release, that may fix a problem people are having with dates in noteblog-style blogs. I don't have a set of steps to create the problem on my system, that's why I'm not sure if this is the fix or not, but I did find a problem.
One thing that was clear from reviewing the CMS code, you won't get good results with stream types if you make the calendar entries by hand.
You should use the big gray plus icon at the top of the icon bar at the left of the window to create new blog entries. It automatically sets the attributes up the way the CMS is expecting them.
If you don't use the plus to create blog entries, you may see problems with dates. This may have been responsible for some of the problems we've been seeing.
The last release of Little Outliner was in April 2013. After so much time, it had become dated, in need of a refresh. That's the point of this release, version 1.40.
Here's a brief explanation for newbies.
The Outliner menu above the outline display has been replaced with the menubar we use in Fargo.
In addition to the Outliner menu, there's now a Reorg menu and a Docs menu.
The Arrow Pad from Fargo has been added. The command to activate it is in the Reorg menu.
The clock was removed.
The explanatory text at the bottom of the page was removed, and replaced with a What is this? link that takes you to a full page description of Little Outliner.
The copyright notice was updated.
The previous version of Little Outliner has been archived here.
The last build of Little Outliner before this release was on 4/16/13 at 1:56:03 PM.
Yes, Fargo was on NPR this morning, in a story about a new site called Glass that's edited, and presented, as a Fargo outline.
I've linked to the new site and the NPR report on today's Scripting News.
It's very exciting. Lots of new users today, and I'm hearing from all kinds of old friends who didn't know about Fargo.
The people at Quartz who are doing this site are incredible, innovators, brilliant, and hard-working. We had a lot of fun with this project but I didn't really have to do anything but answer questions, Fargo really works.