2008/9/5 Alexander Wagner <[EMAIL PROTECTED]>
>
> Are they maintained at the moment at all? I admit that I
> only took care about the online help. <confused> Pascal,
> what's the state here?
>
Unmaintained. I never write documentation.
> > So what exactly _is_ Scid ? What are its main features ?
> > This is not just marketing stuff. This is important for
> > the tutorial, the main page, the fast intro, the Wikipedia
> > entry, etc.
>
> Ahm, what about a nice entry page that links to a completed
> tutorial, where the latter starts with some real world
> examples "what I always wanted to do and never dared to
> ask". ;)
>
> I could imagine a hand full of pages to be sufficient.
> Entry containing also recent news, (recent) Screenshots,
> Tutorial, Download.
>
Yes, that's enough.
I want simple things, no fancy framework for any purpose, no XML. People
want a decent manual and a tutorial. That's all. Only the information
(content) is important, provided that it is not too hard to maintain, and I
know no format that is so hard to maintain. So even an ASCII file
(README.txt) is good enough. I prefer a finished tutorial up to date in Txt
form than tons of ideas and blahblah about the way to manage this data. See
our previous discussion about a "centriscid" base : what came out ? nothing,
nichts, rien.
[...]
> > The time-frame I set myself included the tutorial, btw.
> > Scid's website is at most ten pages deep : no terrifying
> > depth there. It's not that deep that I should not work on
> > the HTML templates first.
>
> I mean, do it as you prefer. But, keep in mind (IMHO a very
> important point) that in some years you may not have the
> time to continue it, therefore it must be in a state that
> another one could take over, so keep it simple from a
> technical point of view. Keep the information that needs
> updates to a minimum, IF these information is not generated
> from the online help or other docs that gets updated
> _anyway_ in the development process.
>
> And another IMHO very important point: don't open to much
> construction sites with unfinished parts. I'd suggest to
> change small parts and finish them, then take the next part
> and finish that one. And so on.
>
Right. Scid's site is "good enough". The only parts requiring (urgent !)
updates are help and tutorial. I will not change Scid's site until those
issues are addressed, because only those parts really need some work.
> > The actual HTML template does need repairs. We don't
> > create tables to insert navigation anymore.
>
> Well, no objection against barrier free pages, but
> concerning the Scid page and documentation(!!!), the tables
> for the menues are really the least of the problems... ;)
>
I agree again :-)
>
> I still feel that documentation/web wise the most important
> thing to do would be to go over all current help pages
> (refering to the online help) and check them for
> correctness, validity and agreement with the current
> version, plus _add_ all things that are not yet documented
> at all and extend those parts that are documented only
> rudimentary.
>
> I think the priority should be to get a decent tutorial for
> new users and to get the docs right. Then one could think of
> design issues like removing table-based menues. Actually,
> one of the ideas to use something like a wiki is, that one
> does not take care about such things in these frameworks at
> all. The design is really a second order problem.
>
> Just my personal thoughts.
No, no : *my* personal thoughts also ;-)
Pascal
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/scid-users
