In Fargo 1.68 there's a new <includeRiver%> macro. It takes one parameter, the http address of a River.js file.
I included my personal river on today's Scripting News home page, with hilarious results. Not saying this is particularly useful, but it's really nice when two big pieces of technology "just work", in this case, they worked the first time I tried it. Hala.
On Twitter, Frank Meeuwsen asks a good question about Fargo.
"Would it be possible to update a Fargo Outline from within Dropbox? So add/update directly in a folder instead of the editor?"
I answered, yes no problem with that. OPML is a text-based format. Just edit the text in whatever you want, and save it to the folder.
The best way to learn about OPML is to create something in Fargo, save it, and then drag the file onto a plain text editor and see what it generated. Fargo doesn't care how the text gets there. So you just have to produce what it's expecting. I tried to design the elements so if you think about it, you'll figure out what it's doing. And I'm happy to answer any questions people have, to the extent that I can.
What's interesting is that Frank is an Evernote business consultant, and Evernote is a service that Fargo and our other products should hook up to. Imagine Radio3 able to post to Evernote alongside Facebook, Twitter, WordPress and RSS. That's the philosophy of these products. Let's make users' data flow smoothly. There's a lot of untapped potential here.
We had an outage starting at approximately 2AM Eastern this morning that just cleared, at 1PM.
There was a problem with the Dropbox API. It was saying every call Fargo was an error.
I posted a status report on the outage almost immediately before it cleared.
Glad to have Fargo back!
No version number change for this fix.
Fargo would fail on startup if you left the cursor on the first line in the outline.
Fargo now remembers the bar cursor location when it saves an outline. It automatically restores the cursor when the outline is reopened.
There's a new <head> element in the OPML that Fargo produces, <lastCursor>.
Its value is a number, the number of times you have to move the cursor flatdown from the summit, after the previously expanded elements are expanded.
Thankfully, the Font Awesome updates go pretty easily these days.
You can use the new icons with the icon macro.
Example: <%icon ("bomb")%> produces a icon (obviously).
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 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.