Re: Write doc from users viewpoint, please.

Am Tue, 29 Dec 2009 13:48:22 +0900 (JST)
schrieb Teika Kazura <teika lavabit com>:

> Hi. It's doc issue. Look at the next hunk in news.texi:
> ------------------------------------------------------------------------ 
> -This is part of window rules, but it cannot be **set by**
> configurator -yet.
> +This is part of window rules, but it cannot be **exposed in** the
> configurator yet.
> ------------------------------------------------------------------------
> The viewpoint is changed. The former is from users', but the latter
> from developers. When you write a doc for users, please take user's
> view.

Well, set and exposed don't mean the same, `set by' would suggest, that
*we* don't allow/want it to be in SawfishConfig, whilst `exposed in'
makes clear that's currently technically not possible, furthermore I
don't expect `expose' to be a techie-word, therefore I'm sure everyone
understood it.

> Yes, texts should be useful to developers too. For example, use of a
> headline helps, so the short description is for users, and you can
> skip the longer contents if not interested in.

> One more from the Wiki news:
>  Bug fix: Prevent window crashing (at least that part sawfish is fault
>  of, bugs in video drivers **of course** still may cause that)
> For those who haven't read the patch, i.e., 99% of the news readers,
> it's not "of course" at all. For them, it does not matter if it's
> of course or by luck. The goal of the news is to tell the fact,
> in this case what's done.

I just wanted to say, that it's not just sawfish causing the issue.
Say, we said we fixed the issue, but it happened again, the user now
knows, that it's not sawfishs fault. But perhaps that `of course' is a
bit too much, isn't it?


> Regards,
> Teika (Teika kazura)

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]