Updating the engine on a work in progress isn't a smooth process #22
Comments
The The documentation will be updated and I'll add the updating guide as well as the new features, gulp is mainly for the engine development but I'll add documentation of that as well. |
After some thoughts, making it through git may not be exactly the best solution, neither through gulp, although they are good solutions, that leaves out many people, specially non-programmers, there probably is a need of a Builder, an application that allows you to create a new VN, handling the download of the files and everything, as well as the update of that VN, pretty much the way the Ren'py launcher works. |
A builder seems like an entire project on it's own. I've never used Renpy to know how it works, but if this builder you're talking about lets non-programmers essentially drag and drop a VN (select and manipulate character, action, scenes and fill in speech all from a GUI) frame by frame, that's definitely going to be a fairly long running project. |
Yeah, the problem would be the time to work on that. The issue with making the update smooth by git is that only people who use git would benefit from it, I wish it could be something more general. |
Ok so, after A LOT of time, I think this finally won't be an issue any more :) Given the current architecture being developed in the v2.0 branch, Monogatari now acts more as a library providing ways to expand it without having to modify its core engine. To update a game, one would simply need to change these files: https://github.com/Monogatari/Monogatari/tree/v2.0/dist/engine And that's it :D |
I suggest adding a
.gitattributes
with some merge driver lines so thatscript.js index.html main.css main.js options.js
are excluded from merge, and maybe adding a "how to" in the readme/docs on updating the engine.
And perhaps a bit about gulp and the addons you're using too.
The text was updated successfully, but these errors were encountered: