I completely disagree. I also assumed there was not yet a preview function implemented. I looked to the bottom for "things I can do related to this post", not for "things that will affect this post". The link with the rest of the functions, and it should look the same. Additionally, this is done in many other systems, so many users already have the habit of looking there (with the rest of the functions) for a preview.
I think the excuse for not placing it there is due to hyperanalysis. On May 24, 1:49 am, David <[email protected]> wrote: > I agree with Arthus. > > The buttons perform actions, while links navigate you elsewhere. > We're > using the right controls. > > My issue was a matter of discoverability. Arthus's recommendation > below would have led to an improved user experience for me. > > --David > > On May 22, Arthus Erea <[email protected]> wrote: > > > Saving a post is an action taken upon a post. We already have a button > > to do said action. > > > Previewing is something you can do with a post, but it does not affect > > the post at all. The buttons at the bottom are for updating a post; > > previewing is just "getting" a post. > > > I think having the save prompter makes sense, and would be happy to > > implement it in the current link. > > > In fact, that's probably the best solution: > > 1) Keep the current link position, but always have it there. > > 2) If clicked for an unsaved post, prompt to save first. > > > In that situation, I don't see any need for FAT and recommend against > > using it. > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-users -~----------~----~----~----~------~----~------~--~---
