How do you effectively work with multiple people in a team?

[TobiasW]

@yaustar

Versioning was added this year (yay!). https://blog.playcanvas.com/version-control-in-playcanvas/ and https://developer.playcanvas.com/en/user-manual/version-control/

That should hopefully help with your first two issues as it allows merging of scenes too.

Oh my, that is wonderful. I’d obviously have to try it to be sure, but from what I see regarding branching, this is nearly exactly what I’d want! Of course people can still accidentally change things on the main branch, but at least it seems that there is a safe workflow now. That’s huge!

I make a ticket about that page you have linked as that shouldn’t be there anymore.

Thank you very much! It didn’t help that it was the first page in the google results for “playcanvas source control”.

@yaustar

I’m afraid I can’t help you much here as I came from game dev into using PlayCanvas. There is an API available for ORG that allows pushing/updating of scripts. I don’t know the exact workflow but I think some developers have been using it to work outside the web browser. Perhaps you could use as a post build step after the standard JS build tools? https://developer.playcanvas.com/en/user-manual/api/asset-update

Thanks for the link! I thought this might need some time to figure out, but now I’ve played around with TEMPLATE: ES6 | Version Control | NPM | PlayCanvas - #71 by redka in the meantime, and it seems to do the job!

There was some trouble on the way, but solvable:

• I had to add import “babel-polyfill” because the other way described there didn’t work for me.
• Both methods for " Local serving your development build" described here don’t work anymore. (Probably due to pc.Asset.prototype.getFileUrl not being used anymore? It never got called after being replaced by the loading screen solution or excerpt.js.)
  Luckily using Redirector as described here worked well. I don’t like that it means that I always have to have a local server running, but I guess I can change the pattern so I that it only activates when I add some parameter to the URL.
• playcanvas-delay was broken for some reason, but easily replaced with const delay = (ms) => new Promise(resolve => setTimeout(resolve, ms)) (found here).

And now it seems that I’ve got a buildchain with Babel, Webpack, automatic uploads and local serving (using code running on localhost without having to upload it) working! I’d still need to update the components (the template is over 2 years old) and clean it up a little, but this is promising.