Ah, OK. But I see it is open source. So it could always be changed to do whatever is needed.
I doubt that something would be needed, though. The model and view files for the various games in src/games/chessbase would not work on their own; they must also use underlying models and views for piece sets and boards. The only place where it is indicated which piece set or board model must be used for a given game is index.js. And the latter contains the path name of the models and views specific for the games.
But that is assuming that jocly-board uses the source code. Building Jocly does not only create a library in dist/browser, (where for each game all required model and view files are combined, and put into dist/browser/games/chessbase in compressed form), but also in dist/node. I never used the latter (I always test the builds through the browser part), but I suppose this is intended for any off-line application.
Ah, OK. But I see it is open source. So it could always be changed to do whatever is needed.
I doubt that something would be needed, though. The model and view files for the various games in src/games/chessbase would not work on their own; they must also use underlying models and views for piece sets and boards. The only place where it is indicated which piece set or board model must be used for a given game is index.js. And the latter contains the path name of the models and views specific for the games.
But that is assuming that jocly-board uses the source code. Building Jocly does not only create a library in dist/browser, (where for each game all required model and view files are combined, and put into dist/browser/games/chessbase in compressed form), but also in dist/node. I never used the latter (I always test the builds through the browser part), but I suppose this is intended for any off-line application.