last night i wrote the longest post *ever,* and then lost it to a crash. it wasn't really iJournal's fault, per se- AOL disconnected me (not because i was idle- just a host connection failure) while i was writing the post. i didn't realize this, and when i clicked "submit," iJournal gave me a connection failure dialog box and then went down.
my question/suggestion is this: is it possible for iJournal to, upon the user clicking "submit," save the post first into a preset folder (sorta like how browsers cache in the preferences folder) and then send? this way, not only would all posts be saved, but it would prevent the loss of posts when the situation like the one i've described occurs.
overall, iJournal is a really cool, easy-to-use app. thanks.
my question/suggestion is this: is it possible for iJournal to, upon the user clicking "submit," save the post first into a preset folder (sorta like how browsers cache in the preferences folder) and then send? this way, not only would all posts be saved, but it would prevent the loss of posts when the situation like the one i've described occurs.
overall, iJournal is a really cool, easy-to-use app. thanks.
Profile
ijournal- iJournal: Official LiveJournal Client for Mac OS X
- iJournal Home
Comments
I also have it set up to write this file before it does the online post so it always catches the content before a crash in the case of an online problem (the post mechanism also needs to be more robust).
I can give you guys the changes for my implementation once I have some UI for it. I just need an idea of where it would make most sense to put it. I do, afterall, hate bad UI and you guys probably have more of a vision for how this functionality should be accessed.
Tell me, generally, how you want it done and I will do it,
...Nights