With the glossary, the new feature in 0.43, you can define little bits of text that plug into documents you edit with Little Facebook Editor.
Choose Glossary from the File menu.
A dialog appears. Enter something like what I've entered in this screen shot.
I've defined a value called name, which has the value DAVE. And values called status and location. I can then refer to them in documents by including them in angle-braces and percent signs, like this: <%name%>.
Here's a screen shot of a post I created this way.
And here's what shows up in Facebook.
The glossary is also a feature in Fargo and basically every CMS I've made going back to the early CMSes in Frontier in the mid-90s. It's an incredibly useful feature. It saves me from having to enter URLs of pages I point to frequently, and makes it easy to change the URLs in the content, if they should change. Note that because Facebook does not at this time support linking in posts, you won't be able to use it that way, yet.
With the v0.42 release, Little Facebook Editor can cross-post to both WordPress and Facebook simultaneously, and when a post changes, both sites are updated.
As with previous versions, this is a demo app, not meant for production use by large numbers of people. The new WordPress functionality requires a server, and that means it can get overloaded.
Because there's a server involved, your WordPress credentials flow through the server, but we do not retain a copy of them. I'd much prefer if this could work without a server at all.
Use the app as before to post to Facebook.
If you want to post to WordPress, choose Settings from the system menu at the right edge of the menubar. The first and only panel in the Settings dialog is where you set your WordPress prefs.
Most of it is self-explanatory, the one potentially tricky part is the URL of your WordPress blog. This must be the address of the home page of the site. The server will look at the source of the page to discover the address of the XML-RPC endpoint for updating the blog. Best way to get this URL is to go to the home page, and copy the URL from the browser's address bar.
Click the New button to start a new post. Enter some text, and click Save. You should see a status message saying that it posted to Facebook and then to WordPress. After it's done if it works, next to the Go button there will be a WordPress icon. If you click it, it will take you to the post on the WordPress site.
Facebook posts (at this time) don't have titles, but WordPress posts do.
When sending to WordPress, we take the first line of the post and call it the title.
Make a change, click the Update button.
The changes should go to both Facebook and WordPress.
If you have questions please post a comment below. Remember this is a demo app, so feature suggestions probably aren't on-topic. I just want to help get the WordPress community working on this and provide an example for others.
Little Facebook Editor is good enough now to get its own blog.
And with this new release, it's now possible to maintain a library of Facebook posts. It's really starting to feel like a blogging app.
There's a menubar.
The buttons at the bottom of the text are still there, but the same functionality is in the File menu. At some point the buttons may go. Or they might turn into icons on the left edge of the text area. We'll see.
The Docs menu will point to blog posts about this app. It's where you should look for information about the latest updates. The Info icon points to the latest howto (for now, this page).
The History menu is the reason there's a menu bar. When you create a new post, by clicking the New button or choosing the command in the File menu, a new item is added at the top of the History menu. Later, when you choose that item, the text of the post appears in the editing area, and any changes you save will go to that post on Facebook. This gives you the ability to edit a library of posts on FB.
There's room for 35 items in the menu. At present there's no way to manage the contents of the menu. So be sparing in creating posts. When the more than 35 appear, the oldest item will fall off the bottom of the menu. So things will still work, though this may not be the desired effect.
When you save or update, a status message appears, providing confirmation that something happened.
There's now a status menu at the right edge of the menu bar, which gives you a place to sign onto Facebook or sign off. There's a settings command in the menu, but there are no actual settings for the app, yet.
All information is stored locally, and not shared between instances of the app on different machines. At this time we don't have a way to store information in the cloud associated with Facebook logins (I have that functionality for Twitter, but it took quite some time to develop). It would be great if I didn't have to do this for Facebook, if they could offer a small amount of per-user-per-app storage for app info.
As usual if you have questions or comments please post them below.