81–85 of 85 posts
I see this as a case of applying a successful model from one field to another without consideration around whether this is actually a problem in the first place.
Earlier quoted context omitted.
Man, this space is filling up so fast. We're working on a similar product, we're funded and a little further along (shameless plug: http://www.revisu.com ). When we started working on this, there was no one in this space. Now there are a ton of offerings! I think you hit the nail on the head with regard to what designers need from version control. We bill ourselves as Dribbble + Github for creative teams exactly for…
I agree with joemoon, and I also advise you to annouce what are the OS supported. So I didn't register.
One problem is that your average designer will not know what versioning is, never mind have an opinion as to whether it'd be useful or not. I see this as a case of applying a successful model from one field to another without consideration around whether this is actually a problem in the first place.
Earlier quoted context omitted.
I agree with joemoon, and I also advise you to annouce what are the OS supported. So I didn't register.
It's a web app. Pretty OS agnostic.
Some notes:
When playing around with the |X|Y| functionality
BUG - Dragging the slider on a compare window beyond the container and releasing the mouse causes the window to follow your mouse around. Your drag and drop "sorting" functionality seems to kick in.
BUG 2 - Adding multiple versions to the compare frame works well, however it was initially hard to tell how to remove a given frame. Some ability from the frame would be nice, but that wasn't the bug. When you add multiple versions to compare you see them highlighted below. Then when you go to another view (i.e. the single revision view) and back to the |X|Y| compare view the frames you were last comparing are still there, however they are no longer highlighted.
Again, this looks great, just keep going! :)