Not having a Board component currently generates a bunch of "error board not found" console log messages when interacting with other components or simply clicking stuff around.

This is because at some point the data-boardname attribute of the Board component is used to get the board name. But all of this can be avoided if there is some internal _CURRENT_BOARD_NAME privately. This would not only solve the issue but be a bit more performant since it would not transverse the DOM tree with jQuery to get the board name (but just a bit, since after all, it is matching an element by ID which should not be slow at all).

Historically, each component had their own data-boardname attribute, then as a major rewrite it was changed to only check for it in the Board component, but it actually makes more sense to go one step ahead and make everything internally. The more we don't rely on the DOM, the better.

Depending if the move is a click-to-move or piece dragging we should animate or not the last move(s).

Currently if you drop the piece, a piece animation sometimes is played instead of simply leaving the position as it is.

After a white move with comment the black move should start with three-dots.

Current format:
1. e4 {some comment} e5 2. Nf3 Nc6 3. Bc4

Change to:
1. e4 {some comment} 1...e5 2. Nf3 Nc6 3. Bc4

Just like ajax333221/isepic-chess#38 for board.pgnExport() but for IcUi PGN viewer.

Allow to drag and drop pieces with the mouse.

Enabled by default, but the feature can be disabled.

Consider having the current "click=select-move-from click=move-to" work alongside the new drag and drop when the user clicks a piece but immediately drops it without having dragged a bit.

Sometimes when the window is zoomed in and you start dragging a piece, scrollbars will appear (horizontal and vertical).

Also when the console is open, the dragged piece will go a bit further and create scrollbars. Some research need to be done in the differences of using document, document.body and window.

Hello,

Some games (problems for young players for example) require boards which are smaller than 8x8.

Do you think you could add the ability to create smaller boards than 8x8?

For example, it could be nice to initialize the board with FEN string like: 3k2/1Qnp2/2r3/3N2/6/K5 w - - 1 1

Thanks in advance for your answer and have a nice day.

Create some variety of themes that can be applied like: IcUi.setTheme("wood") this is tentative and it should probably not be done this way (maybe should be a board property to be consistent with the "isUnlabeled" board property).

It should be only just 1 class that gets added to the board and have everything from the theme cascading down to each element.

It should only trigger when the mouse enters some part (like the board area or move list).

Only when the cursor is above the board and the moves are being scrolled, the event should be stopped.

I don't know why a e.preventDefault(); or return false; didn't work. More investigation is needed.

Some way to enter a setup mode allowing to place pieces (probably dragged and dropped from somewhere, or click to toggle between all pieces) and then exiting the setup mode triggers a position validation and only allows to exit the setup/edit mode when the fen is legal.

With some component to help in clearing/emptying the board and to specify en passant square, castling rights, half/full move clocks, etc.

When the window is resized it works fine, however when the window change in size as resulting of something in the page loading, the drag and drop becomes a broken.

The piece would jump and follow the cursor with some vertical empty space difference, also the dragging limits get calculated incorrectly.

Ignoring the wrong position of the piece, dropping the piece (as if it were correctly following the cursor) sends the correct move though. But still, this is super broken and high priority bug to fix.

The recent removal of UI-only board properties in isepic-chess.js v6.0.0 (board.isUnlabeled for that matter) makes it impossible to show/hide board labels without manually modifying the source-code of isepic-chess-ui.js (var _HIDE_LABELS=false;).

A new API method should be added to bring back this possibility, preferably not per-board but to all boards rendered.

... unless you drag and drop on the same square, then keep it selected (to be able to perform a click-to-move)

Note: should unselect on wrong puzzle moves too.

Most likely done via Right clicking (once for red square highlight toggle and click+drag for arrow drawing).

Left clicking a square should clear all arrows and red squares.

Config. to have this disabled.

Maybe there should also be a way to describe these arrows in a PGN comment or NAG so they get drawn as the replayer reads the move.

It would be good to have these implemented, to intercept some actions and do this before, during and after them.

What happens in lichess is:

• You have a selected piece without having mouse pressed (either you selected via clicking it, or dragging and dropping on the same square)
• You can immediately start dragging it elsewhere
• If you drop it again on the square it now unselects it.

Currently we are doing -> if you have a selected piece (while not having anything pressed) -> as soon as you click it, it unselects it and doesn't let you start dragging it.

Are isepic-chess and its UI compatible as Nuxt modules? Has anyone tried this yet?

Few things were a bit rushed:

• The rook is not animated on drag and drop castling (it works with the "click from > click to").
• Center the piece only after the dragging starts to remove the jumpy feeling when using "click from > click to" instead of drag and drop.
• Some code cleanup.

Currently the only need for _playMoveCaller() to exist is to wrap the calls and do something different when in puzzle mode _CFG.puzzleMode.

But the problem is, sending via the console a board.playMove() move while in puzzle mode will not work.

We should replace the x2 calls on _playMoveCaller() with the native board.playMove() calls. But with the above changes we still need to manually pass _CFG.puzzleMode into some new p option "isPuzzle" or something.

Another alternative is to make something similar to _WIN.IcUi.refreshUi.apply(that, [animation_type, play_sounds]);.

Still unclear which is the best approach, but ideally, the flag of "is puzzle mode?" should live in IcUi, and the logic on how to play puzzle moves should live on Ic.

When a pawn reaches the last rank, that square and the next 3 squares towards the center of the board should turn into: Q R B N (sorted in the most promoted piece to least promoted pieces).

Pressing ESC or clicking outside should revert the move. And also there should be an option for not allowing to cancel. Maybe some API function to select them so people only using the console don't get stuck in there.

When you select (or unselect) a square in Chrome mobile browser, the whole board will flash blue for a fraction of a second.

Maybe the CSS property user-select: none; might fix the issue.

Maybe allow to navigate within the played moves in progress but not the solution moves.

Allow the ABCD... 1234... labels to appear inside instead of outside the board.

It should be compliant with the existing _CFG.boardLabels to actually show them or not.

It is currently not possible to display more than one board at a time (even though we can have multiple virtual boards) because the limitation of not being allowed to have multiple DOM elements sharing the same id.

It would be good not to force the components to have those very specific mandatory id-attributes and rewrite them in a way that we can work with multiple boards visually and no just internally.

The way the auto binding of components work makes this change very hard to implement, a big rewrite needs to take place for this to work.

It would be great to have this feature:

When you are dragging: you will see the square you are hovering, some kind of highlight or ghost piece.

When you are click-to-move and have selected a piece: when you hover a square you see some kind of highlight or ghost piece.

Default will be turned off

• Only overwrite known existing options (keys).
• Some safety checks and sanitization for the input (values).
• Accept object, array or read N arguments to be able to change more than a single option per call.

Done in v4.6.1:

• Return value (did the value change to a new value?).
• Only refresh UI if config changed.