comment on

Brethern and Sistern (excuse the homo sap bias):

For the too-many-th time, I discovered after posting that I'd omitted a critical point, markup or something else that left me dissatisfied with the node and then turned myself into a serial updater by adding an error for every correction.

Therefore, seizing the bull by the bs ^H^H^H ... er, horns, may we discuss a possible change to the update capability; namely, an optional "preview before updating" configuration, which might be added to the option for direct posting without previewing which exists for Monks of certain orders?

Alternately, we might add a second, "preview" button to the existing "update" button and redirect the action that way.

And, actually I'm very curious about why this hasn't surfaced recently. It may be this has engendered little interest previously or that it's a fundamentally 'bad idea' or that it's in the 'too hard' box (but, without suggesting I'm sure I could do the job, I don't see why that would be the case).

What say you?

In reply to Preview for "Update" by ww

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


P is for Practical
	PerlMonks