Comments by fhou

Thanks

I have merged our change in wikipedia-fairy-sprites.png (hawk and terror) and fairy-set-view.js (+ res/fairy/terror/) If you can, you should retrieve at least that from : https://github.com/fhoudebert/jocly/tree/trial

The idea of the steward seems relevant. Would this be the same behavior as the soldier used in some variants?

Would this include the Steward Chess promotion rules?

Interesting!

I'll try to compile it and use it out of curiosity when the time comes.

I've published the changes on github
As I've modified the hawk sprites in the meantime, I think you'll need to get the latest version of
wikipedia-fairy-sprites.png

I've seen jocly/tube, so I'll have to study that in depth.

How do you see the next step? Is it possible to pull down the refactoring of the documentation (html of rules, images ...) to get index.js files closer? or Shall we do it on a brand new branch?

fr-terror : you are right, I had a conflict on that file, I thought I resolved it correctly, but I didn‘t. I pushed a new version.

Your evolutions for PiecesFromFEN are interesting, I will certainly use the setValues functions if possible.

I managed to compile Tube but I am not yet able to make the most out of it. Of course we can replace the diffuse maps if we have improved ones.

Concerning the visuals, I made it from screen capture from joclyboard, that may be why the chessboard square render badly.

Your idea to use SVG would be a great improvement for Jocly but I'm not sure how feasible it is. I assume you already have an idea of how to do it.

I confirm that the order of PiecesFromFEN work as expected. I have tested and modified grand chess but not commited it yet.

I also confirm that the default in wild-mirza-600x600-2d.jpg comes from windows resizing in joclyboard. The visual is modified. but of course the problem remains.

I saw that you'd managed to pull the refactoring of the doc to your branch. That's a good news. Let me know if there's any point in my continuing to refactor the docs of chessbase/decimal and chessbase/shogi directories, or if there are more disadvantages than advantages because of the risk of conflicts.

Yes I will try to help to fill res/rules/fairy, I don‘t know yet how I'm going to get the 3d images consistent with the rest though.

for tube unfortunately I am not yet able to be useful so far.

I pushed a first draft. I can easily improve some image if necessary

yes probably best in base-view.js

I will check that in the evening

for the terror : zip initial version and zip tested on my env

Jocly v0.9.13 is the version they published after the recent pull requests. Joclyboard, which was broken, was recently repaired and now includes this version.

We are working on the next version 0.9.14 ? Joclyboard 0.9.14 will carry it.

Now (with gulp 4 et nodejs 18) we can work on any machine even a windows desktop as long as nodejs 18 is installed.

I use joclyboard to test (I copy fresly compile dist directory in joclyboard/app/node_modules/jocly) : thmbs, visuals, the 3 html files ...

You can access the documentation via the rules, credits, about button (test from this morning).

This is what they will use for each variant before accepting the next pull request. I also believe that the html and images will be used in the next mobile application.

I don't know if it's still time to talk about that. I have a new candidate for the 2d hawk sprite: a Falco peregrinus.

@Jean-Louis : Do you like it better than the aquila. Would a rounder eye be better?
@HG : At least if it was selected. It would be better to modify the sprites file on your side. It's up to you to decide to keep it or not.

if you install the expected version of node on another computer  while waiting to solve the problem :

https://nodejs.org/download/release/v18.19.0/

then you could clone http://hgm.nubati.net/git/jocly.git

then npm install

I haven't had time to test it, but all the changes have been uploaded to github.

The only info I got is from https://github.com/aclap-dev/joclyboard

Note that there is a hidden(collapsed) menu at the bottom of the page when you play to control parameters.

I haven't gone into the details yet. But I'd like a few clarifications to make sure I understand.

Does this mean that when it's finished, I won't need to implement cbMoveMidZ in the views for standard variants built from a FEN string? Or is it broader than that, e.g. all variants that use fairy-move-model?

By the way, if you think it is usefull, I can make a documentation on how to use joclyboard for dev from scratch in the latest version.

Concerning the hawk/falcon visual, I asked Jérôme for help because I couldn't manage to make a decent one on my own. Here are his suggestions. what do you think?

They are ready to use, personnally I prefer the one with round eyes.

If usefull for minjiku or any other of your shogi variant, I Can send you the fortress / tiger piece which have beautifull visuals in 3d.

That's a nice present for Jocly.

This means we can test it simply by commenting cbMoveMidZ in a view like bigorra-view.js, which contains almost all the pieces.

right?

It might be a bit early to test, but I thought it might help to get some initial feedback.

Jean-Louis helped us to check the moves on bigorra without custom cbMoveMidZ in the view:

Snake: When the Snake does a non jumping "Knight" move (2,1) to its right, and only in this case, it starts by the diagonal step prior to the vertical one, which is wrong.

Rhino: sometimes, it starts also by the diagonal step when making a non jumping Knight move. But not always, it depends on the square it starts! (For example Black Rhino on j11 to go on k9 or k13)

Camel: it's sliding, not jumping Sorceress,

Canon: sliding for capturing instead of leaping (Archer is correct)

Marshall: does the opposite: slide as N and leap as R

By the way, I posted the hawk sprites may be a bit too early. It is better to retrieve wikipedia-fairy-sprites.png to avoid a clash on the binary file before the next pull command.