Hi Team Hubski
I love the new save draft functionality, but I discovered a bit of a bugski related to it. If I create a draft post, then eventually post it, it seems to be posted according to the date of the first draft version, rather than as a new post.
I was working on a draft of something for a few days. When I posted it last night, I couldn't even find it on my own feed without scrolling down several pages. When I post this, I expect to find it at the top of my feed and the feed of others who go in looking for new posts.
Edit: I know things don't necessarily show up chronologically, but there is something of the chronological in mk's magic mix.
Do you think my analysis is correct? thenewgreen
I have also noticed this. It hadn't risen up to my level of giving a crap yet, but Lil's right.
FWIW, quotes in drafts also reflect the "post" CSS, not the "draft" CSS.
Also, the mechanism by which drafts are interacted with is kind of crap. Draft "yes" and Draft "no" make a lot less sense than "do not post" and "post". Saying "no" when you want something to actually appear is weird.
That actually resulted from an odd bit of code left over from Paul Graham whereby the name shown is the variable itself, i.e. 'draft', so it made the most sense to follow it by yes/no. It sounds ludicrous, but there was no simple way to give the toggle a different name without undoing a gordian knot of code. It's really a piece of work. Last week, I did just that, and that's why the settings page has been updated to have actual descriptions on the toggles. I'll do the same to the edit page in short order.
I saw a horrible solution to a similar problem in a Common Lisp codebase that shall remain nameless. They defined a read macro to look up a token in a hash table and use that as the object read, so a symbol could be given the name |Save draft?|, then entered in the hash table with the key "draft", and the string "$draft" would be read as the symbol |Save draft?|. It was probably the grossest thing I've ever seen in a CL codebase, but it did solve the problem of having to present friendly strings to people who were not lisp programmers familiar with the project with minimal changes.
I have no idea whether Arc has read macros, and it's probably a bad idea to do that if it does, but it has been done.
Hi mk
While you're addressing draft some time in the future, I'm wondering if you could put "reply" on the intuitive right corner, and save draft on the non-intuitive left corner.
I keep finding myself clicking "save draft" when I mean to hit reply.
CALL TO OTHER DRAFTEES, or perhaps drafters: anyone else doing that??? kleinbl00 am_Unition
I will vote in favor of lil's motion, I do feel like the "reply" button should be rightmost.
Maybe mk is a lefty?