> Till yestereve we had Play / Training / Openings. Joe User comes along, "Ah, an opening trainer, interesting! Lets try that thing." An there Joe is lost. Not even the ChangeLog said a word about what is required for it and the help page (accessible once you got it up...) only explained the statistics. You might remember, we had some lengthy thread here, while ago, about how to get it working, and before that I think I had some (private?) communication with Pascal, simply cause I thought it is bound to the Reperoire Editor, which is (according to the docs) the way to store your opening repertoire in Scid. But it isn't...
Interesting example. Joe Trainer would never access to your modified help files if he just downloads Win binary, unless the documentation is up to date. And we know that it's almost never the case. If Joe Trainer can compile Scid and install Linux, he certainly only needs to know what are Scid advanced functionalities. We simply don't have the same Joe in mind. The Joe I have in mind will shy away from an application that can't provide a simple About page. It's normal that people asks here for advanced functionalities. What we should do about the questions and the answers ? Build up a better documentation system on-line is easier and faster than rewriting the F1 doc. A FAQ would be nice to complement this mailing list. That does not mean that the F1 doc is to be neglected. What we must insure is to put there information that are vital and permanent. You can't always correct a conceptual bug the same way you can correct a programming bug. (Here's a counter-example, though : the Pause button of the analysis engine is described as "Start/Stop engine(a)" in its contextual menu. That's strange, but simple to fix : only correct the message in the tooltip. I don't know what "(a)" refers to, by the way.) So here is what we can do. You finish off a first check-up or analysis of all Scid's functions. That's unquestionably needed. After I finish up the first pass of the tutorial, I will modify the on-line help pages in a way that will take into account all these functional modifications. I'll try then to find some semantics that will be easily converted into Scid's idiosyncratic HTML. I don't have in mind controverted semantics here : just a way to retrieve tcl's anchors for index entries, say. I can be more precise as to what I have in mind, but I need to get going for now. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
