[Compcomm] CompComm Digest, Vol 3, Issue 116

[Jupiter]

Mike i have to say that for you to say this answer is misleading
or just plain wrong,  is ignorant. The fact that i know this user is
using compiz fusion and ccsm, makes my statement true to his
question. Now if you were so interested in getting people informed
as to the capabilities of using your method "gconf", then you wouldn't
be scared to come inform our users of such capabilities. Most
users prefer NOT to use gconf because it sucks. It is not user
friendly at all. Otherwise most people would be using it. You come
to the forum and find an invalid example of the point you are trying
to make and don't even bother to make the correction that YOU
think is right. How friendly of you. Thanks.

P.S. I think if you were to tell the average user to use gconf to get
more capabilities, they would tell you to get lost and, they would
wait for ccsm to have that feature.

Message: 2
> Date: Sat, 23 Jun 2007 01:02:58 +0100
> From: Mike Dransfield <mike at blueroot.co.uk>
> Subject: Re: [Compcomm] Forums
> To: Composite Community List <compcomm at Rock3d.org>
> Message-ID: <467C6332.4030905 at blueroot.co.uk>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Alyssa Hung wrote:
> > Ketil Wendelbo Aanensen wrote:
> >
> >> My point is that developers (too) should maintain support focus on the
> >> official forums. Focusing on 2 makes the know-how less centered and
> >> less user friendly.
> >>
> >
> > I think it's very important for every contributor, including the
> > developers, to be comfortable with the ways they're expected to
> > contribute, but I can definitely see increased developer presence on the
> > forums as a benefit.
> >
> > As I mentioned a few times on oc.o, different people will offer
> > different solutions to the same problems. There's a trend favouring
> > certain kinds of knowledge on each forum (i.e. configuration via
> > gconf-editor versus configuration via ccsm). What if a good solution for
> > you isn't a good solution for someone else? Keeping all the know-how in
> > one place may well result in conflicting and confusing advice. Keeping
> > the know-how in multiple places won't cut down on the conflicting
> > advice, but it won't be as confusing as seeing it all on the same page.
> ;)
>
> The problem comes when the advice is misleading or just
> plain wrong as in this case.
>
> http://forums.opencompositing.org/viewtopic.php?f=46&t=893#p6393
>
> That functionality has been in Compiz for months.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.RiverGorgeSolutions.net/pipermail/compcomm/attachments/20070622/2dce1e75/attachment-0002.htm>