Regarding communication with chess engines: these engines are typically written as console applications. Establishing reliable communication with them has not been an easy task, and performance issues are noteable, especially because of synchronization issues. Also, data transfer between CIE/CIR and the engine is considerably slower because these engines are built in such way to provide output on the screen and to receive input from the keyboard. We'll see what we can do to improve all of this.
Chessboard size cannot be changed currently, but I see why this is an issue. It will find its place on our to-do list :).
CIE supports splitting publications into smaller pieces and this is one feature which caused some minor issues, one of which you described. Namely, CIE cannot know where the game might be, as you might have "shredded" the original publication into smaller pieces. However, we have implemented an automatic search among native CI publications, if they are found. For example, if a game contains a reference to game 5/88, CIE will first try to find any CI package which contains Informant 88, and automatically select this publication as the one which should be searched, whereas if no native CI publications containing CI 88 have been found, CIE will search among any installed publication that are searchable. I agree with you that this was more comfortable in CIR, but some features in CIE implied some lacks.
We are taking all the suggestions and reported issues into account and are trying to make things as easy as possible, which was the primary goal while we were developing Expert. As development continues, we are improving it more and more, although it sometimes seems too slow for some customers.
With regards,
Aljosa Obuljen
|