#85 Minor Edits

[Derek Lakin]

# Minor Edits: Allow users --perhaps only
authenticated ones or those at certain IP addresses--
to mark certain editions as "minor edit" so that
changes do not appear in RecentChanges and clog up the
system with spelling, formatting, grammar, and other
trivial changes. -- KorbyParnell

(Transcribed from
http://www.flexwiki.com/default.aspx/FlexWiki/FeatureRequests.html\)

I'd like to add to this too. I think that adding two
extra bits of date information to a topic would be
helpful too: LastMajorEdit and LastMinorEdit. This
could then be used to determine which version history
was displayed. Perhaps default to major edits with an
option to show minor edits (i.e. showing all changes).
The Created date would obviously remain as it is and
LastModified date would always be the date of the last
change, whether major or minor.

[Derek Lakin]

Logged In: YES
user_id=1130840

Areas of impact:
ContentBase class would need to be modified to add this
extra information when editing topics.
TopicInfo WikiTalk class would need extending to expose the
new dates.
WikiEdit.aspx would need to be enhanced visually to put a
'Minor Edit' flag up on the page would no doubt need some
codebehind changes to update the necessary dates.
Versions.aspx would need to be updated to handle the 'Show
minor edits' option, both in terms of presenting the user
with the option and handling the processing.

[Craig Andera]

Logged In: YES
user_id=879696

This might be a breaking change against the web service as
well, without careful thought. And possibly even with it.

[Nobody/Anonymous]

Logged In: NO

I like the major/minor idea and defaulting to major.
Also, JustinCollum had the idea of auto-distinguishing
between major and minor, here:
http://www.flexwiki.com/default.aspx/FlexWiki/FAQEditingAn
dFormatting.html
Basically, anything with more than X characters changed is a
major edit. Perhaps, in addition, a new newline followed by
any new characters would automatically be major.

[Nobody/Anonymous]

Logged In: NO

I like the major/minor idea and defaulting to major.
Also, JustinCollum had the idea of auto-distinguishing
between major and minor, here:
http://www.flexwiki.com/default.aspx/FlexWiki/FAQEditingAn
dFormatting.html
Basically, anything with more than X characters changed is a
major edit. Perhaps, in addition, a new newline followed by
any new characters would automatically be major.
BradWhite

[BWhite]

Logged In: YES
user_id=1035940

I like the idea of Major/Minor edits, with Major being the
default view.
Also, JustinCollum suggested here
http://www.flexwiki.com/default.aspx/FlexWiki/FAQEditingAn
dFormatting.html, the idea of auto-discerning whether it is a
major or minor edit. If it is more than X characters, then it is
major. Personally, I think that should be X *consecutive*
characters. I would also add, if it includes a newline with
characters before or after, then it is major.
The question is, when does this happen. You still want a
checkbox so the user can choose the appropriate setting.
Being a web page, it would be a pain for it to monitor the
editing in real time and update the checkbox. But you could
have the checkbox, and then do the appropriate hueristics,
and if the results don't match, ask the user to verify that it is
marked correctly. Most likely, they forgot to check/uncheck
the box.
BradWhite

[Derek Lakin]

Logged In: YES
user_id=1130840
Originator: YES

Due to the complexities of the implementation compared to the perceived benefits, this feature will not be implemented at this stage.