| |
Glasnost
Account closed
Registered: Aug 2011
Posts: 26 |
Demo cooperation
Just a short question regarding demo creation involving a large group of people.
What kind of tools do you guys use for communication/discussion, screenshots, uploads etc.. ?
And what experiences do you have with it?
Best regards /Glasnost. |
|
... 20 posts hidden. Click here to view all posts....
|
| |
Hein
Registered: Apr 2004
Posts: 946 |
Maybe what Oswald is trying to say is that he hates productivity and efficiency in his spare time. Dig! |
| |
Digger
Registered: Mar 2005
Posts: 427 |
What Brush said :) GIT doesn't have to be hard when you use a tool like SourceTree (free from Atlassian).
The benefit of using HipChat (or Slack) with GIT is that you can get a notification in the room every time there's a push to the repo. Then we can download and launch .prg files on mobile with Mr SID's C64 Scene.app too :) So I can fap on the toilet when Brush pushes his codepr0n stuff.
iPhone only though. |
| |
Bitbreaker
Registered: Oct 2002
Posts: 504 |
Further advantages:
- easy synchronisation of stuff being made at home or work
- backup, be it of working versions but also if you loose your local data. So no more whining about a died HD with all your work on it.
- because it is 2016 and it is one of the many things that made cross-compiling a success
- easy revert to older versions, if you fucked something up, so introduced bugs can be found easily, especially when watching the diffs and if you happened to commit small changes and picked the changes by issue.
- as soon as a second person joins in, so easy way of sharing, no need to even give notice to others, just have your regular update, pull, fetch
- not using version control invalidates your scene licence |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1408 |
Git's essential for even the tiniest solo project. At a bare minimum it shows me what I changed when I fucked the code "optimising."
Admittedly name_043 etc can give much the same power, but rapidly floods your directory structure. (Or, in the old days, quickly filled a floppy side :-/ ) |
| |
Axis/Oxyron
Account closed
Registered: Apr 2007
Posts: 91 |
Further advantage:
- Adding comments to your commits helps to remind what you have done and you easily find the place where you fucked everything up 2 month ago. |
| |
enthusi
Registered: May 2004
Posts: 677 |
I use bitbucket for some time now.
I second bitbreaker on the biggest advantages: backups and for some projects I work on up to 4 different systems. Also I remeber where I left even after n years ;-)
While 01enthusi.asm, 02enthusi.asm... has it's benefits, usually the tools to generate data/content change along with the main source. So I would need to rename dozens of files with every major step. No, no. |
| |
Oswald
Registered: Apr 2002
Posts: 5086 |
Quote: Maybe what Oswald is trying to say is that he hates productivity and efficiency in his spare time. Dig!
 |
| |
Glasnost
Account closed
Registered: Aug 2011
Posts: 26 |
BB quote: "- not using version control invalidates your scene licence"
Whoops, where do i hand in my license? :) |
| |
Magic
Registered: Sep 2012
Posts: 44 |
there is a nice app called Slack out there..
perfect for it..
https://slack.com/is |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1408 |
Quoting enthusi... usually the tools to generate data/content change along with the main source. So I would need to rename dozens of files with every major step. No, no.
So much this^ Trying to keep the data generator(s!) in sync with the render routine with numbered source files would be hell. Version numbers are for sets of files, not individual files. I vaguely recall a stage of duplicating my source folder with every major change, but that was a long time ago now. |
| Previous - 1 | 2 | 3 - Next |
