These are chat archives for pixijs/pixi.js

13th
Apr 2015
Mathias Latournerie
@JiDW
Apr 13 2015 14:06
Hey, I'm wondering what's the best way to maintain a heavily modded version of PIXI ? At first, we only made small overrides in a specific file but it's becoming way too big to continue like this. I'm a beginner with github but can I make some kind of "fork" and still be able to merge commits from the official repo to my fork ? If not, how would you do it ? Thanks !
Chad Engler
@englercj
Apr 13 2015 14:09
Well the easiest way is to not diverge, the cases where that is necessary are slim and often are solved more cleanly a different way. If you must fork, I recommend reading the github docs, they will help if you are new to git: https://help.github.com/articles/fork-a-repo/
Mathias Latournerie
@JiDW
Apr 13 2015 14:16
Mostly it is features that are not yet implemented and that we do not have time (on business hours at least) to propose in a "out of context" way to make is usable by everybody. Like a texture cache for text, bitmapfonts from frames, cocoonjs tweaks, etc.
I don't know if I "must" fork, I will read your link to see if it is a possible solution to still apply "official" fixes to our version
Thanks !
Chad Engler
@englercj
Apr 13 2015 14:17
That's fine, I'm just trying to warn you that often forking and maintaining that fork is more expensive that just sending back changes as PRs (or in v3 writting them as standalone plugins).
Mathias Latournerie
@JiDW
Apr 13 2015 14:18
We could make standalone plugins !! That's a very good idea
Hmm well, maybe... I have mods inside the ressourceloader too for bitmaps... but others are mainly inside PIXI.Text and PIXI.extras.BitmapText
so i guess I could maintain a forked plugin
I will look how to do a pixi plugins. thanks for the idea, way better than a full fork