This control.html was a demo file that came with the Jocly source distribution, and it is included in the tree you installed ( /play/jocly/temp/examples/browser/control.html ). It seems operational there. I might have made a copy of it in another directory on my own website. By appending an argument ?game=... it is possible to change the initially-selected game. (But there is a link on the page that can be used to switch to any other game.) I suppose you can see the required game names for the games I implemented on my Jocly starting page.
It seems the other games you have on CVP use another method for embedding Jocly than just linking to control.html with a game-selecting argument; they have their own html page, invoking Jocly through some embedded script, but having a CVP header and some other info, plus some ads added. I am not familiar with this method of embedding. It might be an older one; I remember having seen an obsolete Jocly tutorial, which discussed a very simple method of embedding that was dependent on the jocly.com server. This could be that method, except that it seems to link to a local version of the Jocly library ( /play/jocly/jquery.jocly.min.js ) which the described method would fetch from jocly.com.
I suppose you could also create game-specific pages derived from control.html, by adding the CVP- and game-specific elements to it, deleting the game-switch link from it, and then linking to it with the argument that selects the game it describes. My turn-based server page http://hgm.nubati.net/jocly/jocly-master/remote.html is a similarly adapted version of control.html.
The Jocly version as it now builds from the GitHub sources seems much less monolithic than the jquery.jocly.min.js file; the latter seems to contain everything, while the version I build keeps the Jocly library distributed over a huge tree, and loads the required components on demand. E.g. there all games are in separate files jocly/dist/browser/games, which again has a subdirectory 'chessbase' that contains all chess variants. Where each variant then has 3 .js files (config, model and view), two .html files (description and rules) and a .png thumbnail image, and the config.js then indicates what other components are needed for more basic support (e.g. what type of board view, the general chess model). All the graphics for chess pieces is in a subfolder chessbase/res.
This control.html was a demo file that came with the Jocly source distribution, and it is included in the tree you installed ( /play/jocly/temp/examples/browser/control.html ). It seems operational there. I might have made a copy of it in another directory on my own website. By appending an argument ?game=... it is possible to change the initially-selected game. (But there is a link on the page that can be used to switch to any other game.) I suppose you can see the required game names for the games I implemented on my Jocly starting page.
It seems the other games you have on CVP use another method for embedding Jocly than just linking to control.html with a game-selecting argument; they have their own html page, invoking Jocly through some embedded script, but having a CVP header and some other info, plus some ads added. I am not familiar with this method of embedding. It might be an older one; I remember having seen an obsolete Jocly tutorial, which discussed a very simple method of embedding that was dependent on the jocly.com server. This could be that method, except that it seems to link to a local version of the Jocly library ( /play/jocly/jquery.jocly.min.js ) which the described method would fetch from jocly.com.
I suppose you could also create game-specific pages derived from control.html, by adding the CVP- and game-specific elements to it, deleting the game-switch link from it, and then linking to it with the argument that selects the game it describes. My turn-based server page http://hgm.nubati.net/jocly/jocly-master/remote.html is a similarly adapted version of control.html.
The Jocly version as it now builds from the GitHub sources seems much less monolithic than the jquery.jocly.min.js file; the latter seems to contain everything, while the version I build keeps the Jocly library distributed over a huge tree, and loads the required components on demand. E.g. there all games are in separate files jocly/dist/browser/games, which again has a subdirectory 'chessbase' that contains all chess variants. Where each variant then has 3 .js files (config, model and view), two .html files (description and rules) and a .png thumbnail image, and the config.js then indicates what other components are needed for more basic support (e.g. what type of board view, the general chess model). All the graphics for chess pieces is in a subfolder chessbase/res.