Dirk,
I think you have focused in on what the real requirement is here: don't
create a new version if the change is minor. Previously in this thread we
have assumed either that the user should know when not to create a new
version, or that the amount of time that passed between creating changes
fully agreed !
2009/4/8 Janne Jalkanen janne.jalka...@iki.fi
let's then keep the discussions there, another option might be to have
one
save button, but with an additional dont make new version check-box,
whose
setting is kept in the cookie ?
I fear that that is a bit too confusing
Good points.
It seems to me we have two major audiences: geeky and non-geeky.
The geeky would probably understand versioning and appreciate the desire to
reduce intermediate versions. They would probably not be put off by an extra
button or checkbox.
The non-geeky would prefer the click here to
Was SingleVersionForSavesBySameUserWithinHour ever implemented?
Thanks,
Lou
~~
LOG-NET, Inc.
The Logistics Network Management System
~~
230 Half Mile Road
Third Floor
Red Bank, NJ 07701
PH: 732-758-6800
FAX: 732-747-7497
nope, is there a JIRA issue for this ?
2009/4/7 louis.mast...@log-net.com
Was SingleVersionForSavesBySameUserWithinHour ever implemented?
Thanks,
Lou
~~
LOG-NET, Inc.
The Logistics Network Management System
~~
230 Half
I only see this page:
http://www.jspwiki.org/wiki/IdeaSingleVersionForSavesBySameUserWithinHour
Harry Metske harry.met...@gmail.com wrote on 04/07/2009 12:05:15 PM:
nope, is there a JIRA issue for this ?
2009/4/7 louis.mast...@log-net.com
Was SingleVersionForSavesBySameUserWithinHour
I found that page also.
Before I found JSPWiki I was looking at several other options. One (maybe
TWiki? I forget) had what I see as a better solution than those proposed on
the referenced JSPWiki page; instead of setting a timeout, etc, you have two
save buttons. One creates a new version, and
I also prefer this option (2 buttons).
Janne,Andrew,Dirk: this looks a good improvement to me, how does this fit in
JCR ? (same semantics ?)
Any caveats ?
Do we need a JIRA issue here ?
Harry
2009/4/7 Bob Paige bobpa...@gmail.com
I found that page also.
Before I found JSPWiki I was looking
Can we make this configurable via properties? I have a site that I need
to maintain versioning so I would not allow the second button there.
Thanks,
Lou
Harry Metske harry.met...@gmail.com wrote on 04/07/2009 12:31:03 PM:
I also prefer this option (2 buttons).
Janne,Andrew,Dirk: this
Having spent the last few years teaching TWiki to people, I can surely
say that the two buttons are bloody confusing to most people.
Must vote strong -1 on that idea.
Implementing it would mean removing the previous version and then
adding a new one. Not impossible with JCR either.
I used to have a kind of 'hacked' JSPWiki version as described in
http://www.jspwiki.org/wiki/VersionOverwrite.
It allowed the user to overwrite the same version in very specific conditions :
1) The user must be logged in. (authenticated)
Anonymous or asserted users can not overwrite
11 matches
Mail list logo
