#1066: Sizer vertical alignment differences
-------------------------+--------------------------------------------------
Reporter: paul | Owner: somebody
Type: discussion | Status: new
Priority: minor | Milestone: 0.8.3
Component: ui | Version: 0.8.1
Resolution: | Keywords:
-------------------------+--------------------------------------------------
Comment (by add):
Many things are transparently clear for a dev but unclear for an end user.
This is why I think it is a different community which should take care of
the docs than which develops the code. Of course the app maintainer has to
check for vandalism correctness and his cool hidden feature missing for
releases, but the docs can be generally worked out by end users who would
like to contribute and start to use docs to learn cool stuff about their
apps in the first place. Both annotations and contributions will only
clutter the interface by default as a design pattern rather than trying to
put it all together. That way you can never create offline or print docs
of high quality without again having the devs or current admins maintain
the comments and annotations. Hopefully a small Wiki quality team will
evolve (i am against ops or admins) to review and summarize the
contributions. I hope this gives us more users as contributors than having
the docs focused on the devs. Cheers, duns [http://www.about-china.net.cn
/wrought-iron/cat_4.html china tour] [http://www.about-china.net.cn
/wrought-iron/cat_3.html Apparel] [http://www.about-china.net.cn/wrought-
iron/cat_5.html shoes] [http://www.about-china.net.cn/wrought-
iron/cat_12.html bags] [http://www.about-china.net.cn/wrought-
iron/cat_6.html Kitchen] [http://www.about-china.net.cn/wrought-
iron/cat_7.html Food and Wine] [http://www.about-china.net.cn/wrought-
iron/cat_8.html Furniture)] [http://www.about-china.net.cn/wrought-
iron/cat_9.html Flowers and Gifts] [http://www.about-china.net.cn/wrought-
iron/cat_10.html Wall Art] [http://www.about-china.net.cn/wrought-
iron/cat_11.html Computer Components] I still prefer a wiki like approach
since the php (or mysql) docs are very cluttered when you have to take
their comments in account. On the other hand they are professionally
maintained imho, since they are *much* better than KDE documentation. KDE
is by far larger and has so many different apps, which need screenshots
and end user not dev/api docs, that more help is needed as long as the
devs prefer to code than to write nice docs. And it is their choice to
some degree imo. Technically interested but non-dev end users, which are
plenty out there, are the users of and the best contributers to the docs,
since they know what to write about. And they are certainly more than devs
--
Ticket URL: <http://trac.dabodev.com/ticket/1066#comment:7>
Dabo Trac <http://trac.dabodev.com>
Trac Page for Dabo
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
