pgeorges schrieb: Hi!
> It is also important to consider Pocket PC, as some people > already managed to connect a DGT board with a PPC > (CEboard, Pocket GrandMaster). Hm, though I do not use such a thing and admit that I really don't like the runtime... I do not forget it. Why should I? It would be interesting wether dgtnix would not compile on WinCE as well as it does on Windows already. ;) After that the engine-approach is pure POSIX, (dgtdv2 itself does not conatin _any_ hardware dependent part, that is all done within dgtnix, which is a lib like libhid that Ben uses) no need to worry on that side. To connect it to scid would involve the same procedure as you do for all other engines. At least the use of C(++) for the input engine does not hinder porability. If there is any hindrence there it would be the use of stdio which would require conversion as you do for other engines. But as I do not have any CE, nor will I get any CE, so I can not program for CE. (Admitting that I've also no interest in coding _for_ it, otherwise I'd probably have a device ;) All I can assure is that dgtdrv2 itself will most likely compile out of the box. If there is any problem it would be dgtnix and it would be there to fix. Maybe Pierre did try it already? Same point for the Mac btw. dgtdrv2 runs smoothly just dgtnix has a problem with serial com on the apple and I was not able to fix it myself. :( If I could I would do it ASAP, but as with CE I do not own an Apple either. > More over a new version of DGT board will include > Bluetooth, making it even easier to connect to a PDA. I do not see the point here. IMHO: give me a BT-enabled DGT and it will just run with dgtnix and consequently with dgtdrv2. BT is not at all an issue here. It's just another "cable" and it's still just serial communication as it is with usb. Neither dgtnix nor dgtdrv2 makes any difference between USB and serial. In fact I use a serial board connected via USB to my PC by means of some USB2serial converter, and I think for quite some time about using some Serial2BT and use BT. I just did not yet get a proper adaptor at a suitable price. Ideally it would just connect to the serial port at the dgt, contain a 9V battery and sit just outside the board. I believe the cabeling there wouldn't be rocke science. So to say: the connection of the board to the PC is quite some layers below the software written. The "cabeling" is something like layer 0, the driver (dgtdrv2) lives on layer 6 or 7 (depending on your view of the end user level). That is like Bens tcl-code that lives someweher up there. The libhid is still "high enough" to work over a bt cabeling as well I'd guess. So why should I have to care about the kernel part? To handle the BT/USB/serial is the reason why I use an OS. It wouldn't even come to my mind to implment this in scid ;) -- Kind regards, Alexander Wagner Universitaetsbibliothek Ilmenau Langewiesener Str. 37 98693 Ilmenau Tel.: 03677/69-4521 , Fax.: 03677/69-4617 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
