Log in

No account? Create an account
Not Hart to Implement - LiveJournal Client Discussions — LiveJournal [entries|archive|friends|userinfo]
LiveJournal Client Discussions

[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

Not Hart to Implement [Mar. 3rd, 2003|08:20 am]
LiveJournal Client Discussions


[mood |thoughtfulthoughtful]
[music |Fire Emblem from Super Smash Brothers: Melee]

I've been thinking about something today.
And I really should have thought of it earlier.

This is basically a feature suggestion to EVERY LJ Client Developer out there.

Shouldn't we really implement a simple 'save before posting' feature?
I mean, how many times have you guys read about "Damn LJ ate my post/angst/rant, blah blah blah."
No offense to anyone who says that...I know how annoying it is too.

Seriously. Can't almost everybody just dump the contents of a post (all contents, subject, body, security, mood, current music, etc.) to a file temporarily?
You can either dump out the file if the server returned a post success, or store it and just overwrite it when the user makes another post.

Oh, keep in mind, that you should have a 'recover last post' button or menu CLEARLY VISIBLE on the client.
That way, they know the feature exists. Don't hide it or say 'go open this file etc. etc., in the documentation'.

(Note: If anyone has implemented this, then you rawk :D. I'm Microsoft's whore, so I only have messed with Visions, Sema, and Loch...I just got the .NET framework, so I'll start messing with the .NET client as well.
And yes, I understand, non-HD clients can't quite achieve this. But, for those who can, keep this in mind.)

(Deleted comment)
From: stenz
2003-12-23 09:42 pm (UTC)
How about an auto-save? You tell it a directory in the preferences where it should auto-save out what you have written so far - perhaps named after the date or with some user editable naming system?

I just had my Xjournal crash out on me after writing a rather long journal entry. I suppose I "should" have saved out on my own, but I usually do that upon exiting the program instead of as I'm typing.

That way, it auto-saves out, and then when you post, it gets rid of the auto-save file. Then if it starts up and sees that there is a file in there, it can assume that something happened last time you were using the app and it can ask if you want to continue in the file that you were last working on?

Or maybe I need to learn to write much shorter journal entries.
(Reply) (Parent) (Thread)
[User Picture]From: jerronimo
2003-03-03 09:06 am (UTC)
mine saves all of the posts in a 'queue' which you can re-flush out later, in case the server is down or slow. it will also retry to post the event a few times.

there are no 'buttons' on mine, since it's all text-based. there are no graphics. ;)
(Reply) (Thread)
From: evan
2003-03-03 09:18 am (UTC)
I suspect LJ eating your post is actually your web browser failing to post. Any good client should not delete what you have typed unless the request to post succeeded.

Crashing is a different problem, and the only one that really needs to save to disk.
logjam autosaves drafts, and deletes it if you quit. If it crashes (which it doesn't do very often anymore) the draft will still be there and it'll find it the next time it starts.

A hacky version for Windows is available here but I don't recommend it.
(Reply) (Thread)
[User Picture]From: xb95
2003-03-03 11:04 am (UTC)
If you do it wrong you have people who complain of their "private data" being put where anybody can read it. Yeah, it is a fairly trivial thing to add, but it has to be done right or the dissenters won't like it. :)

I've been playing this for LochJournal for ages. Just haven't gotten around to it.
(Reply) (Thread)
[User Picture]From: fflewddur
2003-03-03 11:11 am (UTC)
Drivel autosaves posts and deletes the autosave after posting is complete. If it detects a non-empty autosave file on startup, it loads it automatically. It also includes "Save Draft/Open Draft" buttons in the File menu. :)
(Reply) (Thread)
From: ex_kanis722
2003-03-03 02:54 pm (UTC)
logjam allows you to save entries (even autosaves them). which is a useful thing, because i always have problems with that program spouting out sig11's (especially the older versions).
(Reply) (Thread)
[User Picture]From: sapphirecat
2003-03-03 05:42 pm (UTC)

Depends on the client design, really.

It's on my wishlist for SCLJ 3 (current status: vaporware), but there's no good way to do it in 2.x because of the way the data structure is held in RAM. (Data::Dumper might work with minimal effort, but would be somewhat brittle.)

So yeah... only well-designed clients can do cool stuff like that.
(Reply) (Thread)
[User Picture]From: anam_uk
2003-03-05 06:08 am (UTC)
Well I've just fixed up my ruby client to do this, but only if you get as far as posting, I really ought to get of my backside and do some kind of drafting/versioning thing, maybe at the weekend :>
(Reply) (Thread)
[User Picture]From: tainted_emotion
2003-03-06 12:52 pm (UTC)
I'm currently using Win32-MFC, are there any other clients I can use for Win that will allow me to recover last post/Prevent a post from being purged?
(Reply) (Thread)
[User Picture]From: vxjasonxv
2003-03-06 12:54 pm (UTC)


Win32 actually doesn't purge the post if it fails...but it doesn't save it, so if you close the program, it goes bye bye as well.
I can't tell you about .NET Sema or LochJournal though.
(Reply) (Parent) (Thread)