Alexander Wagner a écrit : > > All those inputs are handled by separate procedures > > (present in different files). In each of these procedures > > it is necessary to send the new board position to a > > currently analysing engine. It certainly would be nice to > > gather all these in one place. I have started to do it in > > Pocket PC code as I wrote it so it is easier for me here. > > To me it looks as if you are coding scid pocket entirely > diffrent then the real thing. Isn't it possible to have it > on a common code basis? Hi,
It is very hard to do so. All C/C++ code is common (through #defines), but Tcl mixes model data and user interface stuff. So the code is always, even slightly, different. Even when scidpocket runs on Linux, I have to check on which OS I am in order to have all Tcl code work. > Right now the code to handle Citrine's board is about 150 > > lines of Tcl code, which is simple to port and maintain. > > I can only speak of the dgt, but give that one a factor of > 10 for the hardware specific part within dgtnix + the same > for dgtdrv to get the logic to just speak about the concept > of a move. Most of this is convert 0xSomething from > /dev/ttyUSB0 to "move e2e4". (The dgts hardware works on a > much lower level than your Citrine seems to work. Sad, but > true) > I am not sure it is so sad. Working at a lower level sometimes eases things, because you have access to more info. Citrine is very poor in that field. > > and just one side of the problem. I implemented > > engine/engine tournament on Pocket PC > > Why again only for CE? > Simply because the code is slightly different between the two, and there are functions I prefer to have on Pocket PC, and others on PC. To backport stuff is painful, needs debugging for features I don't need. But the PPC code is available to anybody if there are gaps to fill. > > The user enters "play mode" or "opening training mode" > > explicitely. This is for me how he says if he wants to be > > in analysis mode or not. > > But then I need to know that from some point in scid. The > minimum is some accessible flag. Tell me how I can read it > and I'll use it. IMHO the better way would be to call some > sc_getmode and it is returned, but I've no principle problem > with globals. For example, the flag is ::fics::playing (set to 1 when the user plays on FICS), and ::novag::connected when the Citrine is connected. Pascal ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
