Selon Alexander Wagner <[EMAIL PROTECTED]>: > > Even when scidpocket runs on Linux, I have to check on > > which OS I am in order to have all Tcl code work. > > Just for my understanding: you mean you run sicd on a pocket > PC (some ARM machine), but this ARM runs on Linux, not on > WinCE? Just asking out of curiosity. I did not follow the > Pocket PC stuff at all as it is entirely out of my interests > as long as it requires CE. (I had very bad experiences with > that stuff, and I'm myself using PalmOS for years).
When compiling scidpocket for Pocket PC I use a cross compiler (arm-gcc) to generate ARM code. When compiling for Linux (mainly for debugging), I simply use gcc for x86. > >> 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. > > I do not see the latter. IMHO the functionality should be in > both versions. Otherwise its two different programs. It is like Pocket Word and MS Word : 2 different programs that are able to share files. I agree most functionalities should be in both versions, but I have limited time for this, and I put high priority on features that pleases me the most (for the moment Citrine support). But anybody can work on this (features synchronization between the two versions) : this is not hard work as all difficult part is common (the C/C++ back office). > >> 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. > > Is there somewhere some comprehensive list of the flags? You > did all this coding you know them of course. No, there is no doc, but the code and some "grep" always did the trick for me. > But to come back to the design part: what about a > centralised procedure to send move to from whatever input? > Are you working on the port of your CE code for that? Would > ease up things a lot I think and give cleaner code. Yes, I am trying to centralize things on Pocket PC as I wrote the code from scratch myself. Scid was iteratively coded, hence some complexities. >E.g. in > your example, I strongly hope that ::novag::connected is not > checked at any other place then within the novag code as > otherwise one would have to add checking of quite some > flags. This will get a bit unmaintainable. > Of course ::novag::connected is read from other places, but only written in Novag handling code. I don't think it will be possible to have a single flag : the behavior is different when playing FICS, a board is connected etc., and you will not trigger the same actions. 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
