in reply to Adding writeup hints to compose pages

I don't post often enough to remember the ins and outs of all the various codes and how they're used. When I do need one of those codes, it's a hunt and peck search operation opening new tabs to find them. I'm all for including these in the help text ++. For that matter even the What shortcuts can I use for linking to other information? link here would be most helpful.

On the same topic, I really dislike that I lose the original post when I go to preview. I'd like to be able to see the original post AND my preview comment together so I get the full sense of my words in context. At the very least there should be a way to switch back from preview to original post.
  • Comment on Re: Adding writeup hints to compose pages

Replies are listed 'Best First'.
Re^2: Adding writeup hints to compose pages
by ww (Archbishop) on Feb 27, 2008 at 18:51 UTC

    Whether you're posting a new SOPW or responding to one, there's a short list of a fair number of specific codes and a set of links directly to most of the others immediately below the text-input box. The preview window offers the same (you are previewing, aren't you?).

    Noted, however, that there is not a *direct* link to What shortcuts can I use for linking to other information?, so that may be worth having devs and the sitedoc clan consider.

    On the proverbial third hand, however, you can avoid the "hunt and peck" that annoys you by adding links to whatever you'd like to your free nodelet (see Free Nodelet Settings.

    And as to your plaint "that I lose the original post when I go to preview"...

    1. You could open the comment form in a new tab or window, thus preserving direct access to the target of your remarks
      or
    2. you could make use of the fact that the preview page provides links to the node to which you're responding and to the whole thread, either of which is easily accessible by opening one or the other in a new tab or new browser window.

    The latter option is an enhancement added fairly recently and incurs fairly low overhead, for you and the server, whereas including the node or entire thread each time someone clicks "preview" could represent a significant cost in responsiveness.