// Add your reply above here
==================================================
Aaron Fuleki updated this ticket at October 19th, 2010 @ 08:37 PM
Well, regardless of how & when the version numbers are incremented, this is the behavior I see on both 1.10 and 2.0:
1. Create a story, put in some content, and check it in. This becomes v1.
2. Check out the same story, make some edits, and save. Let's call this the current working copy.
3. Click the "diff" link from the story profile page. This loads the diff page.
4. By default, the diff page diffs the current working copy against itself, which isn't particularly useful (can't see the "original" v1).
5. Also frustrating is the fact that v2 doesn't exist yet (since I haven't checked the story in), and bricolage seems to treat the current working copy as v1, making it impossible to actually compare any changes I've made to a story since checking it out, because v1 isn't really v1, it's my working copy.
It seems that, when an asset is checked out, the current working copy supersedes the previous version, since they can't both use the same revision number. There needs to be some way to differentiate between the two. You can see a new record appear in the instance table when an asset is checked out, so this should be possible.
I personally think it makes the most sense to increment asset versions at checkout time, and just discard them if they are reverted or cancelled. If that's not feasible, then some other name/number should be reserved for the working copy, so diffs and other actions can refer to them directly.
What does anybody else think? It's really annoying that I have to check something in to see a diff, as that often creates bogus revisions, or forces me to just use a separate text editor entirely.
--------------------------------------------------------------------------------
Assigned: theory
State: new
Milestone: 2.0.1
View this ticket online: http://bricolage.lighthouseapp.com/projects/29601/tickets/197-bricolage-fails-to-set-the-default-diff-version-to-last-vs-current-on-the-story-profile-page
Stop being notified of this ticket's changes: http://bricolage.lighthouseapp.com/projects/29601/tickets/197-bricolage-fails-to-set-the-default-diff-version-to-last-vs-current-on-the-story-profile-page/watch
Update your Profile: http://bricolage.lighthouseapp.com/profile
Support: support@lighthouseapp.com or http://help.lighthouseapp.com
==================================================
Aaron Fuleki updated this ticket at October 19th, 2010 @ 08:37 PM
Well, regardless of how & when the version numbers are incremented, this is the behavior I see on both 1.10 and 2.0:
1. Create a story, put in some content, and check it in. This becomes v1.
2. Check out the same story, make some edits, and save. Let's call this the current working copy.
3. Click the "diff" link from the story profile page. This loads the diff page.
4. By default, the diff page diffs the current working copy against itself, which isn't particularly useful (can't see the "original" v1).
5. Also frustrating is the fact that v2 doesn't exist yet (since I haven't checked the story in), and bricolage seems to treat the current working copy as v1, making it impossible to actually compare any changes I've made to a story since checking it out, because v1 isn't really v1, it's my working copy.
It seems that, when an asset is checked out, the current working copy supersedes the previous version, since they can't both use the same revision number. There needs to be some way to differentiate between the two. You can see a new record appear in the instance table when an asset is checked out, so this should be possible.
I personally think it makes the most sense to increment asset versions at checkout time, and just discard them if they are reverted or cancelled. If that's not feasible, then some other name/number should be reserved for the working copy, so diffs and other actions can refer to them directly.
What does anybody else think? It's really annoying that I have to check something in to see a diff, as that often creates bogus revisions, or forces me to just use a separate text editor entirely.
--------------------------------------------------------------------------------
Assigned: theory
State: new
Milestone: 2.0.1
View this ticket online: http://bricolage.lighthouseapp.com/projects/29601/tickets/197-bricolage-fails-to-set-the-default-diff-version-to-last-vs-current-on-the-story-profile-page
Stop being notified of this ticket's changes: http://bricolage.lighthouseapp.com/projects/29601/tickets/197-bricolage-fails-to-set-the-default-diff-version-to-last-vs-current-on-the-story-profile-page/watch
Update your Profile: http://bricolage.lighthouseapp.com/profile
Support: support@lighthouseapp.com or http://help.lighthouseapp.com