My screencast

Error

This video doesn’t exist

LocalStorage – impressions, future plans, ideas, roadplan,

Hello world.

Well, this is the last of my updates on this blog, I guess. Let me start by saying this has been a really nice experience. I feel like I’ve learned quite a bit, and has done nothing but to strengthen my resolve to become an active part of the WordPress community.

IMHO, the plug-in turned out really nice. But software is never done, and I’m determined to work on it even further.

First thing, like @wojtekskutnik, I’ll post a call on wp-hackers to help with further testing and feedback.

1.0 will be the version after some further “real-world” testing is done.

Subsequent versions will have the following improvements:

• multiple versions backed up for each post (right now the plug-in saves the latest autosave and the latest “final” version). On request, the user will be able to see each one.
• a meta-box which will hold a button to manually “Save to localStorage”, the previous versions, and a button to delete any (or all) the versions.
• leveraging Application Cache to keep an editor in browser cache. On connection down, clicking on “Add post” will bring up this minimal editor.
• Integration with core, hopefully for 3.4.

Thanks a lot to my mentors, and I hope the community will find my work useful. Have a nice end-of-summer, everyone 🙂

This is just a short post to explain…

This is just a short post to explain theme and plugin developers how to use my plugin (LocalStorage Plugin), which, btw, made it’s way into the official wp plugin repo – feedback and impressions always welcome. 🙂

Thanks to the awesomeness of amplify.js, it’s easy to have something akin to WP PHP hooks in JavaScript – beyond events and callbacks.

You see, the core of the amplify library offers two methods –  publish and subscribe, which are equivalent to do_action and add_action.For more info, check out amplify.js documentation

The cool thing about it is that you can send parameters, and they’re sent by reference, so it works both as actions and as filters.

In the hooks I’ve added so far, you can modify the post_data which will be saved, or submitted, before the actions take place

a.publish('aboutToSave', action, post_data);

The “plugin” example I’ve chosen to implement backs up the post format and modifies the value when showing the backup (on request).

amplify.subscribe("aboutToSave", function (action, post_data) {
	post_data.post_format = $('input.post-format:checked').val();
});
amplify.subscribe("showBackup", function (action, post_data) {
	$("input.post-format").filter("[value=" + post_data.post_format + "]").prop("checked", true);
});

And this is basically it! I’ll add some more examples later, but this is what it’s mostly about.

This week I’ve added localization options to the plugin. Also fixed a few bugs,and will add the plugin to the main plug-ins repo later today.

The following days I’ll add plugability and write a few short tutorials on how to add custom functionality to my plug-in. (Should be useful for plug-in/theme developers).

Also, final code clean-up will follow, to make it pretty for the final evaluations. =)

Added security checking these days. (nonces, etc)

This week I’ll focus on localization settings, adding plugability to my plugin (via apmpify’s pub/sub system) and a few bug fixes.

I know I’m late again, sorry.

Good thing is, I took care of some bugs, and now things work correctly when it comes to scheduling a post for later, or when you want to make a post private.

I also took care of whitespace issues, making my code more readable.

Right now I’m adding nonces (which I’ll have in by monday’s update, which will take place as scheduled).

Hello all,

Terribly sorry for the late update. This has been a truly hectic week, for which I’ll make up in the weekend.
I’ve been talking to @suscov and he’s given me a few ideas and pointers. Priorities: security, documentation and white space issues in the code 🙂

Last week I’ve added support for notifying a user when he has an unsynced post which is waiting to be published, and patched a few bugs. This week is one of self-assessment, reordering and bug hunting and fixing. Some new trac tickets will be open. Some old ones will be closed, etc. Top priority is hardening security, at the moment.

Terribly sorry for the slightly delayed update.

I’ve got a (crude) notification system going for when you have backed-up posts which are to be published/updated. Tomorrow I’ll tag the first version (0.1) of the plug-in, after I’ve quashed a few bugs and made a few improvements, mostly to the notification/ui.

Last week was pretty good.

The plugin now has a component that loads on all admin pages and checks if you have backed up pages and syncs if it needs to.

It also checks when an autosave request fails in the post editor, and also sends a dummy request when you press the “Publish” button.

(this part was also posted here but I might as well copy-paste it, as this blog gets a lot more visitors)

@mitchoyoshitaka believes that when the server is not reachable, the “Publish/Update” buttons should be greyed out. I think a notification that the post will be submitted later suffices, and greying out the buttons detters the user from clicking, and (part of) what I’m trying to do is to make it ok to push that button even when offline.

We’d both love some more input from more UX-savvy people.

This week I’ll work on some user notifications and some bugs to bring it to a really usable version before midterm 🙂