[chandler-users] User guide

[Fritz Meissner]

Seconded. I suppose that up till now Chandler has been too much of a moving
target to document, but it really is needed now. I find that much of what
exists tells me that a feature exists, but not how to use it - I'm thinking
of the "Basic Concepts" section in Getting Started, or the Vision and Tour
on the home page. Each of them has contributed something to the picture, but
I still find myself at sea frequently.

For instance, something I am currently struggling with is
publish/subscribe/sync - what exactly each of these concepts (which seem to
be interrelated) means. Especially when I get warnings like "Synchronising
does not update subscriptions", or something like that.

The standard template I see for user manuals on my Ubuntu system looks like
a relatively painless and systematic way of approaching this. It leads one
to go systematically through  the application describing each menu item or
screen feature so that in the end you have a manual without having to do a
lot of thinking about how to organise it. Possibly this could be started by
putting the section headings into the wiki and then letting us users fill in
the info as we have time, with the team checking and correcting details.

Fritz

2008/8/20 Mike Finley <finley1 at gmail.com>

> I really like the ideas behind Chandler. The only problem I have is the
> learning curve. I've had to spend a few hours trying to figure out how to
> use it. This is a huge barrier to integration into my schedule. Is there an
> easier way to learn how to use Chandler other than trial and error?
>
> Thanks,
> Mike
>
> _______________________________________________
> chandler-users mailing list
> chandler-users at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/chandler-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/chandler-users/attachments/20080820/9482e78d/attachment.htm