Linked by Thom Holwerda on Mon 20th Feb 2006 12:22 UTC, submitted by Rahul
X11, Window Managers Updated: Fedora was right in the middle of announcing all this properly, so here is the updated item containing the official names. Videos included, as well as the inevitable 'Why not Xgl?'. "AIGLX is a project that aims to enable GL-accelerated effects on a standard desktop. We have a lightly modified X server (that includes a couple of extensions), an updated Mesa package that adds some new protocol support and a version of metacity with a composite manager. The end result is that you can use GL effects on your desktop with very few changes, the ability to turn it on and off at will, and you don't have to replace your X server in the process." This is part of Fedora's Rendering Project, and instructions on how to install all this are available too.
Thread beginning with comment 97598
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Why don't.....
by diegocg on Mon 20th Feb 2006 18:37 UTC in reply to "Why don't....."
Member since:

Or Koffice when OpenOffice is already there?

Because koffice was there before openoffice was opensourced...?

Reply Parent Score: 2

RE[2]: Why don't.....
by MonkeyPie on Mon 20th Feb 2006 18:47 in reply to "RE: Why don't....."
MonkeyPie Member since:

That's really not the point now is it... according to the idea that we don't need more choice, then OpenOffice, which has a code base much older than KOffice, should be the only one that needs furthering and the KOffice devels should just go ahead and contribute to the development. This is the way I feel about the people screaming "Why don't they just work together?"


Reply Parent Score: 1

RE[3]: Why don't.....
by someone on Tue 21st Feb 2006 04:17 in reply to "RE[2]: Why don't....."
someone Member since:

Apparently, you don't seem to be very aware of the situation in OO.o. The code there is almost a decade old and the code base is almost unmaintainable due to its large size.

Even though there are many groups contributing to the auxiliary projects (translations etc.) around OO.o, there are very few outside developers contributing code to OO.o and this is the reason.

KOffice has a much cleaner API, unlike OO.o and is much easier to hack on. OO.o will need to modularize its code base and eliminate even more outdated code before they can get community contributions flowing in.

Reply Parent Score: 1

RE[4]: Why don't.....
by MonkeyPie on Tue 21st Feb 2006 14:25 in reply to "RE[2]: Why don't....."
MonkeyPie Member since:

Don't want to sound to Zen but I think you see my point even if you missed it the first time around. I wasn't saying that KOffice was worse off than My whole point is that without the different projects we would be stuck with one or two things.

If we take the mentality that they should just work together and not have their separate projects, we are worse off.

Maybe I failed to insert enough sarcasm into my original statement.... I am too dry at times.


Reply Parent Score: 1