On 02/04/2014 16:20:58, "Graham Cobb" <[email protected]>
wrote:
On 02/04/14 13:16, Patrick Ohly wrote:
FWIW, here's the terminology section from the README. It's meant to
introduce concepts from scratch, i.e. nothing should depend on
anything
not defined yet.
I appreciate the effort that has gone into this: I have read it many
times, and I even had it to hand while writing my earlier reply to
Emile. But I have to say that it has never helped me as much as I would
like :-)
I realise this is my failing, but I have always found it very hard to
understand what is going on with these. I am getting better as I do
more, but I have been using SE for quite a while now and still am lost
with configuration half the time.
I'm relieved it's not just me being dense. I am experiencing the same
difficulties.
I've taken a new tack on things. I've described 4 use-cases that cover a
major part of what syncevolution can be set up to do (and by happy
coincidence, also solve the problem I came to SE for).
I want to work through these use-cases and clarify as I go the concepts
behind the terminology. I started, and stumbled again, mainly for the
points Graham made in his message... there are terms that are doing
double work (such as 'config') and there are concepts to the naive
reader (raises hand) are not easily distinguishable (context/source).
This is why I'd love to work through the use-cases, applying the correct
terminology to the examples; doing so ought to make the other HOWTO's a
lot easier to understand, as the reader could draw parallels from a good
understanding of the concepts, rather than trying to distill the meaning
from HOWTO's. The list of terminology definitions is helpful but not
enough; I'm studying to become a philosopher, I could talk for hours
about the important difference between definition and meaning, but I'll
spare you the boredom :)
Emile
_______________________________________________
SyncEvolution mailing list
[email protected]
https://lists.syncevolution.org/mailman/listinfo/syncevolution
