5 ms·
Kactus: Design version control without changing tools
- Ethcad 9y agoThe website looks exactly the same as that from GitHub Desktop: https://desktop.github.com/ https://desktop.github.com/
- captn3m0 9y agoSaw this earlier today and the screenshots matched. Probably because they are using GitHub Desktop as a base? github/desktop is MIT, so I'd say good idea: https://github.com/desktop/desktop https://github.com/desktop/desktop
- deleted 9y ago[deleted]
- mlinksva 9y agoLooks like the code is at https://github.com/kactus-io/kactus https://github.com/kactus-io/kactus and GitHub Desktop is their upstream.
- mathieudutour 9y agoIndeed, it's forked off desktop/desktop. And some of the work I've done on Kactus has been merged upstream as well, the image comparison for example.
- captn3m0 9y agoThe LICENSE file makes it explicit: https://github.com/kactus-io/kactus/pull/24/commits/0205dc6f3144656fb225d5a45a19c1b84ed3c9ad https://github.com/kactus-io/kactus/pull/24/commits/0205dc6f...
- mlinksva 9y agoThe LICENSE file makes it explicit that Kactus is MIT licensed and copyright holders to at least some of the covered code include those listed. Good, that's what the license file is for when the license is MIT. It doesn't make the upstream relationship explicit though. I imagine explicit would be documenting in README or CONTRIBUTING or something like that (not at all required by the license, just informative for users and contributors).
- deleted 9y ago[deleted]
- krsdcbl 9y ago"Design Version control without changing tools" ... that is, if you're on Mac OS and your tool is sketch.
- mathieudutour 9y agoYes maybe it's pooly phrased. I was trying to convey that, as opposed to pretty much all the other version control tools for designers, Kactus doesn't force you into a workflow. It's more an additional step that comes after, just like when you code, git is a tool that you use after.
- GuiA 9y agoI seem to remember that a reason why Git wasn’t popular with game dev (and why it wouldn’t be with designers, besides usability) is that it handled binary diffs terribly (ie it would store the whole updated file, even if just a few bits had changed). Am I remembering correctly? If so, is that now addressed?
- alkonaut 9y agoAlso it didn’t have native file locking which makes it a no-go for any non-text often changing content. I’m not sure if this has been addressed, or whether some plugin has become the de-facto standard to solve this?
- slrz 9y agoFile locking basically being the antithesis to a distributed version control system, I can't really see how it would fit into Git. How would it work for a system with no central repository? It might make more sense to implement this within the services that emulate a central repository on top of Git.
- alkonaut 9y agoYou lock it in one central repository. There is typically a blessed repository somewhere, at least in every single project I have seen. I know of no one and no project that uses the bare git in a truly distributed sense that isn’t just one central repo with multiple users, or in rare cases a hierarchy of repos such as the Linux kernel. This is also why the github/lab style services are so popular - it’s what people need. But I don’t think that’s a reason to keep this feature away from git itself. I don’t think many want to have to use github just to get this one feature, and as I said, for any repo hosting binary content (common) and using one or more central blessed repos (nearly universal) - it’s very hard to live without.
- davvid 9y agoGitolite has a fine implementation of locking in Git. http://gitolite.com/gitolite/locking/#locking-binary-files http://gitolite.com/gitolite/locking/#locking-binary-files Locking is implemented centrally by gitolite. It would be nice if other services implemented the same mini-protocol.
- Bilters 9y agoI’ve seen multiple version control apps pass by in recent years. However they seem to focus too heavy on one particular tool. For me as a designer I’m really looking for a version control system / app which handles multiple files from multiple software applications. On a regular day I use, Photoshop, Illustrator, Indesign, After Effects, Premiere Pro, and some other smaller tools as a base. If there ever could be a (local— because of the large file sizes in video) versioning system which brings them all together that would mean the world. Preferably in a nice gui application. And I know these apps have failed in the past but I think there might just be a market for it. (Instead of versioning it all in the finder / explorer myself)
- tootie 9y agoZeplin is the current darling. It's real power is in digesting designs into code to make handoff to developers easier.
- TheAceOfHearts 9y agoAFAIK, many of those programs use non-free formats which makes it challenging to implement what you're talking about. Vendor lock-in sucks.
- zoom6628 9y agoFar ago in a space far removed from today in space and time i used svn for versioning everything. Yes it meant storing whole blobs in the folder but it worked for everything - source, documents, pictures. If one doesnt need to have versions of internals of the non-textual items then it is usually good enough. For office docs most of them support edit tracking. The only thing that was an issue was database contents but for those one can store differential logs (most mainline db supported them). Yes its not beautiful but it is useful and it did work reliably. And best of all because of using svn and integrating TortoiseSVN into explorer (was using windows) it meant basically no new tools to learn.