[Compcomm] A possible forum merge proposal
Stephen Moore
delfick755 at gmail.com
Thu Apr 26 18:33:37 EDT 2007
there is a reason the beryl people get angry that they lose features
i think i've said it before
IT'S A COMMUNICATION ISSUE!!!!!!
if you tell them at the beginning that there is going to be no functionality
loss, then go away and do this without reporting back to the community, the
community will start to want something, and so they start using new code
(which as is said, not ready yet) and so they're gonna see that some
functionality they had before isn't there anymore
if some of the people involved in coding this stuff were to post updates, in
say a blog or something (doesn't have to be anything too large, it could
even help them in trying to get their mind around what has been done, what
needs to be done and general status of things)
then the community will know the status of things, why things are missing,
why things don't work, when they'll get functionality back...
it also doesn't help when no-one explains to the average user (in an
announcement type thing they will not miss) why the merge won't be a two
second thing, and that they'll just have to use beryl/compiz for a while
until the "merge" is complete
and can somone PLEASE come up with a better word than merge if it's gonna
cause so much anger, it's stupid now
when we say merge (well for me atleast anyways) i refer to the joinage of
two projects into one.......it doesn't matter what that means in code, all
that matters is that two becomes one.......
On 4/27/07, Danny Baumann <dannybaumann at web.de> wrote:
>
> Hi,
>
> > >> Again, just the big parts
> > >>
> > >
> > > Again, should I list every tiny bit?
> > >
> >
> > Yes please. Thats what we are looking for, I thought that list already
> > exists?
>
> OK, so here you are:
>
> - Focus Steation Prevention (present in Compiz)
> - beryl logger
> - more core actions (implemented in extram plugin)
> - saturation, brightness (present in bs plugin)
> - "focus on close" mode (last window/window under pointer) (TODO)
> - edge triggering delay (TODO)
> - minimized window thumbnails (will get a better replacement)
> - Copy mode (only temporarily needed until NVidia fixes their drivers)
> - system check & XGL/AIGLX/NVIDIA autodetection (helper script in the
> works)
> - plugin loader autosorting (supposed to be done in the settings
> manager, implemented in libbs)
> - all global core variables are either extern'd or in CompDisplay (patch
> done)
> - multiperspective stuff (needed for wall) (discussion pending)
> - settings in core (supedceded by libbs & bset)
> - BTF/FTB drawing (discussion pending)
> - requests system (use handleCompizEvent instead)
> - focusDefaultWindow and warpPointer work screen-wise (done)
> (Why? -- racarr)
> - beryl desktop manager stuff (not sure about this stuff)
> - IPCS (its usage has been replaced)
> - paint modifier locking (not sure if that is really needed)
> - setClipPlanes is wrappable (not needed due to different core changes)
> - RGBAimageToTexture (implemented differently as imageDataToBuffer)
> - keyboard grab optional in pushScreenGrab (not really needed as soon
> there will be IR)
> - screenGrabExist (implemented in plugins)
> - windowSetUrgentHint/ClearUrgentHint (replaced by changeWindowState)
> - saving of restore geometry to X atom (not sure if that is really
> needed)
> - resize preview (TODO)
> - don't update position of grabbed windows on ConfigureNotify (to avoid
> jump on restacking of a window grabbed for movement) (TODO - try if that
> also happens with Compiz)
> - fullscreenWindow (now in extrawn)
> - texturing fixes for multiscreen (done)
> - minimum window width/height constraining (done)
> - legacy maximized app fixes (needed for wine, but break OOo)
>
> I hope you are now happier than before.
>
> Regards,
>
> Danny
>
> _______________________________________________
> CompComm mailing list
> CompComm at Rock3d.org
> http://www.ubaight.com/mailman/listinfo/compcomm
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.RiverGorgeSolutions.net/pipermail/compcomm/attachments/20070427/13212289/attachment-0002.htm>
More information about the CompComm
mailing list