lukasmonk
commented
1 year ago Thank you very much for your suggestions.
Questions
How to contribute a new theme?
* This is a club tournament inspired theme. I called it tournament. * I saw **UserData** directory and found out that, theme file is encrypted in **themes.pkd** file. While, in **Resources** directory, the themes are in **.lktheme3** and they are also encrypted.
They are saved with a standard library, pickle.
themes.pkd and
### Theme Preview Issues
* while working with this settings, I found some issues/bugs. * The window is not fully shown. (see the bottom, it is hidden and there is no way we can resize the window. DPI problem?) 
I have to work on it. In windows there is no problem, maybe removing windows inheritance will be enough.
Suggestions
This are the UX, DX suggestions
* Change project slug/name to **lucaschess** . Why? The reason is the current name suggest the explicit version in it **(R2).** Instead of specifying the version in project name, it is advisable to specify the version name in release binaries.
Perhaps in LucasChess 3
* Change the project structure to a standard. * The current project structure is mess IMO. * I found the code in **bin** directory. Which is not expected. The **bin** directory is for binaries, not for code. * Split the code in **src** directory and used libraries to **lib** directory.
It mimics the distribution, I don't really like the rules in my work :). At the moment, I don't want any help on programming, so it's not a big problem.
* Remove some **ALPHA/BETA, OLD** engines.
Not so easy and I like old engines.
* I saw some of the engines are in their early development phase and some of are not being maintained/has no activities since years. So, it is advisable to remove it from bundle and create a way for users to **plug-n-play**. So, if they wish, they can use them. This'll remove the clutter, reduce the bundle/binary size and headache of maintaining that engines. * Update the **requirements**. * I saw, many requirements are out-of-date. Such as **python-chess** etc. * Add highlight of **from-to-move**/**last-move** and **possible moves** just like, lichess or chess[.]com 
Perhaps in future
* Allow users to draw **possible-moves** arrows just like, lichess[.]com, chess[.]com or chessbase. 
Right button when activated in Options/Configuration/Board F1/F10 to enter in directory mode.
HarshilPatel007
Hi all,
First of all, many many thanks for this awesome piece of software. My hunt of best chess client/tool for the linux is ended here.
Version : R2.04 Wayland OS : Arch
Questions
How to contribute a new theme?
Theme Preview
Issues
while working with this settings, I found some issues/bugs.
The window is not fully shown. (see the bottom, it is hidden and there is no way we can resize the window. DPI problem?)
Suggestions
This are the UX, DX suggestions
Change project slug/name to lucaschess . Why? The reason is the current name suggest the explicit version in it (R2). Instead of specifying the version in project name, it is advisable to specify the version name in release binaries.
Change the project structure to a standard.
Remove some ALPHA/BETA, OLD engines.
Update the requirements.
Add highlight of from-to-move/last-move and possible moves just like, lichess or chess[.]com
Allow users to draw possible-moves arrows just like, lichess[.]com, chess[.]com or chessbase.