AshTeriyaki Posted October 19, 2015 Share Posted October 19, 2015 I'd love a save incremental / save version button, when clicked it'd just save a new version of the file in place with _0001 etc appended to the filename. Super easy, lovely little feature. Bruce bonus time - add a user definable suffix option to preferences so users can choose version themes or timestamps etc. A_B_C, architectureshooting and ronnyb 3 Quote Link to comment Share on other sites More sharing options...
Staff Andy Somerfield Posted October 19, 2015 Staff Share Posted October 19, 2015 Hmm.. interesting.. ;) Andy Quote Link to comment Share on other sites More sharing options...
Staff Andy Somerfield Posted October 19, 2015 Staff Share Posted October 19, 2015 Arg.. we'd still have to show a "Save As" dialog - pre-populated with "Something_0002.afphoto" etc.. (damned sandbox!). Not sure if it would be much use like that :S Andy. Quote Link to comment Share on other sites More sharing options...
ronnyb Posted October 19, 2015 Share Posted October 19, 2015 What about making it part of the Autosave functionality, like a secondary checkbox in the prefs labeled something like, Incremental Autosave, which adds a user defined suffix and a user defined time amount before save? Arg.. we'd still have to show a "Save As" dialog - pre-populated with "Something_0002.afphoto" etc.. (damned sandbox!). Not sure if it would be much use like that :S Andy. Petar Petrenko 1 Quote 2021 16” Macbook Pro w/ M1 Max 10c cpu /24c gpu, 32 GB RAM, 1TB SSD, Sonoma 14.4.1 2018 11" iPad Pro w/ A12X cpu/gpu, 256 GB, iPadOS 17 Link to comment Share on other sites More sharing options...
paolo.limoncelli Posted October 19, 2015 Share Posted October 19, 2015 But... What about something like a proto-symple-stupid version control implementation? Something like a sidecar History file push to a GIT/SVN repo that can be pulled down... Just saying... Ok... Need to eat something... I'm going crazy. :ph34r: Quote The white dog, making tools for artists, illustrators and doodlers Link to comment Share on other sites More sharing options...
koyanloshe Posted March 15, 2016 Share Posted March 15, 2016 It would be great if we could have version control specially with the UX feature that is being designed. There is a lot of back and forth that always happens in that case. paolo.limoncelli 1 Quote Link to comment Share on other sites More sharing options...
Teo_ Posted March 17, 2016 Share Posted March 17, 2016 I’d like to see a version control with a good granularity in future. I tried to track a 100MB .afdesign for an user interface in a git repository and an after some commits and two branches the result was this: Quote Link to comment Share on other sites More sharing options...
ALx Posted March 17, 2016 Share Posted March 17, 2016 Forgive me my ignorance but how would it be different/better from OS X built in file versioning? Dominique 1 Quote —ALx Link to comment Share on other sites More sharing options...
Teo_ Posted March 17, 2016 Share Posted March 17, 2016 Forgive me my ignorance but how would it be different/better from OS X built in file versioning? The OS X built in versioning (used for example by Pixelmator) has a granularity of documents, so you can restore a full document version an replace the actual. Imagine the possibilities of a granularity of artboards, styles, objects, layers, etc.: you should commit an revert only some parts of a document an keep the rest of the document unchanged. A quite simple implementation of this method for visual design can be found in Justinmind. I mean quite simple because it use a "locks" that could confuse somebody not used to versioning systems. Quote Link to comment Share on other sites More sharing options...
JimGoshorn Posted March 17, 2016 Share Posted March 17, 2016 If you decide to use OSX's built in versioning, PLEASE allow us to delete versions. Apple stopped doing that so the file that holds versions just keeps getting bigger and bigger. The only way I have found around it is to rename the file in the Finder that I am going to modify, open it, duplicate the open document (cmd-shift-s) and then work on the duplicate and save that. The other suggestion would be to allow us to specify how many versions back we want to keep and the software would automatically delete older versions beyond that point. Quote Link to comment Share on other sites More sharing options...
AshTeriyaki Posted April 5, 2016 Author Share Posted April 5, 2016 Coming back to this, git LFS is around nowadays, a git based solution would be epic! No branches, just simple committing. That'd be aces. Just thinking out loud though Quote Link to comment Share on other sites More sharing options...
Staff Ben Posted April 5, 2016 Staff Share Posted April 5, 2016 The OS X built in versioning (used for example by Pixelmator) has a granularity of documents, so you can restore a full document version an replace the actual. Imagine the possibilities of a granularity of artboards, styles, objects, layers, etc.: you should commit an revert only some parts of a document an keep the rest of the document unchanged. A quite simple implementation of this method for visual design can be found in Justinmind. I mean quite simple because it use a "locks" that could confuse somebody not used to versioning systems. There are so many reasons why we won't be doing sub-document version granularity. We have structured our files to try to minimise binary differences between saves. Our saves only apply atomic changes to the end of the file, and a saved and compacted file should be storing the sub-elements of the document in consistent order, so that binary differences are limited to simple insert/remove/replace rather than reordered blocks of binary data that will result in large diffs being generated. This should help with the size of trickle updates for iCloud and DropBox... in theory. Quote SerifLabs team - Affinity Developer Software engineer - Photographer - Guitarist - Philosopher iMac 27" Retina 5K (Late 2015), 4.0GHz i7, AMD Radeon R9 M395 MacBook (Early 2015), 1.3GHz Core M, Intel HD 5300 iPad Pro 10.5", 256GB Link to comment Share on other sites More sharing options...
Petar Petrenko Posted April 6, 2016 Share Posted April 6, 2016 And also, a purge. When the design is finished, to delete all previous version and leave only the latest one? Quote All the latest releases of Designer, Photo and Publisher (retail and beta) on MacOS and Windows. 15” Dell Inspiron 7559 i7 ● Windows 10 x64 Pro ● Intel Core i7-6700HQ (3.50 GHz, 6M) ● 16 GB Dual Channel DDR3L 1600 MHz (8GBx2) ● NVIDIA GeForce GTX 960M 4 GB GDDR5 ● 500 GB SSD + 1 TB HDD ● UHD (3840 x 2160) Truelife LED - Backlit Touch Display 32” LG 32UN650-W display ● 3840 x 2160 UHD, IPS, HDR10 ● Color Gamut: DCI-P3 95%, Color Calibrated ● 2 x HDMI, 1 x DisplayPort 13.3” MacBook Pro (2017) ● Ventura 13.6 ● Intel Core i7 (3.50 GHz Dual Core) ● 16 GB 2133 MHz LPDDR3 ● Intel Iris Plus Graphics 650 1536 MB ● 500 GB SSD ● Retina Display (3360 x 2100) Link to comment Share on other sites More sharing options...
Staff Ben Posted April 6, 2016 Staff Share Posted April 6, 2016 And also, a purge. When the design is finished, to delete all previous version and leave only the latest one? You can just use Save-As for that purpose. Quote SerifLabs team - Affinity Developer Software engineer - Photographer - Guitarist - Philosopher iMac 27" Retina 5K (Late 2015), 4.0GHz i7, AMD Radeon R9 M395 MacBook (Early 2015), 1.3GHz Core M, Intel HD 5300 iPad Pro 10.5", 256GB Link to comment Share on other sites More sharing options...
Petar Petrenko Posted April 6, 2016 Share Posted April 6, 2016 Yes, but Save-As does not delete previous versions. VAX/VMS systems had this options. Files were automatically named like (*.txt;1 *.txt;2... *.txt;3) whenever you pres Ctrl-S and when you activated Purge, all previous versions were deleted and the newest version was renamed to (*.txt). * = file name P.S. But. this tool should be part of the OS. Quote All the latest releases of Designer, Photo and Publisher (retail and beta) on MacOS and Windows. 15” Dell Inspiron 7559 i7 ● Windows 10 x64 Pro ● Intel Core i7-6700HQ (3.50 GHz, 6M) ● 16 GB Dual Channel DDR3L 1600 MHz (8GBx2) ● NVIDIA GeForce GTX 960M 4 GB GDDR5 ● 500 GB SSD + 1 TB HDD ● UHD (3840 x 2160) Truelife LED - Backlit Touch Display 32” LG 32UN650-W display ● 3840 x 2160 UHD, IPS, HDR10 ● Color Gamut: DCI-P3 95%, Color Calibrated ● 2 x HDMI, 1 x DisplayPort 13.3” MacBook Pro (2017) ● Ventura 13.6 ● Intel Core i7 (3.50 GHz Dual Core) ● 16 GB 2133 MHz LPDDR3 ● Intel Iris Plus Graphics 650 1536 MB ● 500 GB SSD ● Retina Display (3360 x 2100) Link to comment Share on other sites More sharing options...
Dominique Posted June 24, 2016 Share Posted June 24, 2016 You should implement the macOS's built in versioning. First this feature is ready to use (I am wrong?) and second this bring consistency within the platform. Today I lost my work because 1/ I am used to work with built-in feature on many apps and 2/ I thought AD have this feature implemented as many others. Quote ☰ dominiquevial.fr deviant Art Link to comment Share on other sites More sharing options...
Staff Ben Posted June 28, 2016 Staff Share Posted June 28, 2016 The MacOS versioning you are referring to is based on the ObjectiveC libraries, a lot of which is "hidden" from the developer. It is also not a cross platform solution. We have written a fully cross platform format, that is optimised for cloud updates for multiple systems (not just iCloud). We do allow for iCloud support, and if you save your files to an iCloud folder they will be synchronised. We do not, however, employ the mechanism used by apps like Pages that do live continuous saving of the file - this mechanism is fine for small scale files, but would have had significant problems for our document model. We use the standard method of saving that requires you to perform the save. For this reason, we also have a background backup facility which should offer some level of protection against file losses. Also, the feature you refer you is only used by apps that are exclusively on the App store. Adobe, for example, won't be offering this feature either. And, why did you lose your work? Affinity would have told you that you needed to save your work before you close the document or the application. Teo_ 1 Quote SerifLabs team - Affinity Developer Software engineer - Photographer - Guitarist - Philosopher iMac 27" Retina 5K (Late 2015), 4.0GHz i7, AMD Radeon R9 M395 MacBook (Early 2015), 1.3GHz Core M, Intel HD 5300 iPad Pro 10.5", 256GB Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.