[Syncevolution-issues] [Bug 56263] Can't synchronise CardDAV with Basic Auth
https://bugs.freedesktop.org/show_bug.cgi?id=56263
--- Comment #9 from Patrick Ohly <patrick.ohly(a)gmx.de> ---
(In reply to comment #4)
(In reply to comment #3)
> In other words, add a setup wizard mode to the command line. That's doable,
> but also quite a bit of work.
>
Hm. Maybe not exactly a wizard with steps and all. But in the case of CalDAV
or CardDAV, it should be possible to check the remote contents for being
either calendar, todolist or addressbook data, I think.
The command line as it stands today manipulates and uses configs. Any kind of
code which helps creating configs for specific use cases is a separate layer,
which today doesn't exist in the command line.
I'm unsure how to move forward though. Add that layer for the creation of
configs? All other operations then would still expose the user to the details.
Or add some high-level config which then gets translated into the actual mode
of operation underneath?
> Did the terminology section help? It should have. If not, I need
to reword
> it.
>
Hm. I don't know. It's just so much text. Every time I read it, I feel it's
totally clear. But shortly after that, when trying to interact with
SyncEvolution, that feeling is gone and total confusion and frustration
kicks in. Many things seem to be implicit and it's not immediately clear
what the things are, that I give a name, i.e. "target-config@radicale",
"calendar1", "radicale".
Would a command line syntax that doesn't use positional arguments be better? On
the one hand, the current syntax allows very short commands ("syncevolution
radicale calendar").
On the other hand, combined with the lack of constraints for config names,
detecting user errors is hard: "syncevolution --foo bar" uses "--foo"
as config
name, which is not what the user wanted.
The alternative would be "syncevolution --config radicale --source calendar"
where "--source" may be repeated multiple times.
And if anything goes wrong, the sanest thing to do
seems to be to mv ~/.config/syncevolution out of the way, because I find it
not discoverable which part failed due to which configuration (and how to
change it then). That also adds to the frustration.
Understandable. I try to remedy that by listing individual steps in the HOWTOs
(like using the target side in isolation), but it's hard to discover that.
Anyway, maybe a picture would help. For various use cases. For me, I
would
probably appreciate a picture with PC, a "cloud", several databases and the
relevant terms attached to them.
Okay. So, who draws one? ;-/
--
You are receiving this mail because:
You are on the CC list for the bug.
Attachments:
- attachment.html (text/html — 3.7 KB)