Hi,
2008/4/2, Benoit St-Pierre <[EMAIL PROTECTED]>:
>
> Pascal, Alexander, Michael & alii,
>
> We could agree that there are those important questions to settle
> before embarking upon a FAQ :
>
> What format ? ~~ We shall one day use UTF-8. If it's something Scid
> could easily do, we'd rather start now. As for myself, working with
> vim/cream at the job (PC) or textmate (home) does not pose any
> difficulty. If that's not what we do, we would be at some tr or sed
> scripts away from it anyway. (As an aside, I wonder if it would only
> be for help files, or all the code.)
UTF 8 is certainly the best choice, and TCL should handle this perfectly.
Where to put that ? ~~ The FAQ could in faq, I mean in fact, very well
> be a subset of the help files. (Imagine a first topic named **Scid
> for Dummies**.) That could entail some rewriting of the whole help
> files, which would be a nice idea. I may be interested in that job at
> one day, maybe next year, say. But the FAQ I was thinking about could
> reside only a page on Pascal's site, or Scid's, or whatever, and still
> be of value. In fact, the whole idea came from two events that came
> up on the same day : editing the Wikipedia page for Scid and having
> the simple question about renaming, and more to the point, the two
> very valuable answers. Maintaining both web pages and help files may
> hinder development, but can also improve reactivity.
The help files in Scid does not display screenshots, they only contain
text. One good choice seems to use HTML files put anywhere, for example on
my site, and/or a menu could be added under the help one, that launches the
default browser with the relevant URL (or the HTML stull could be packaged
with Scid, so people could browse it without internet connection).
Where to start ? ~~ The first thing would be of course to build some
> preliminary sketch. For this, I will skim the mailing list archives,
> while reflecting about my usual use of Scid. I am glad to have a
> reason to indulge in reading back the whole archive. The main
> objective would be to decide upon the first few things to know. That
> should give an idea about how all the topics will fall and the depth
> of treatment.
Why not use http://scid.sourceforge.net/tutorial/index.html as a starting
point ? My point is that I think more documentation is a good thing but I'd
like information to be available from the least possible places. So if
someone has a question, he won't have to search first in help files, in
tutorial then in FAQ, etc... I think ideally the documentation should be
concentrated somewhere.
Look for example at http://prolinux.free.fr/scid/scid_newfeatures.html : not
only is it outdated, but it is yet another place to find answers, and
certainly not the best thing to do.
So I guess that sums what needs to be said in this mailing list.
> Maybe that would be better if I only report here about results from
> now on. I am asking the question, in fact : is it usual to keep the
> discussions between project members open to the readers of the mailing
> list ?
This mailing list is not overcrowded, and discussing some matters in a
public way may be helpful.
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/scid-users
