Slashdot Mirror


Xr Renamed to Cairo

Charles Goodwin writes "Xr, the vector graphics extension for XFree86 that Keith Packard, Carl Worth, and a few others have been hard at work on, has been renamed and is now officially called Cairo. Keith and Carl recently gave a detailed presentation on Cairo (then known as Xr) which should be a useful read for those wishing to understand it a little better. There is already a useful Gtk+ rendering backend that uses Cairo, as well as an SVG test suite. This, along with Gnome2's subtle adoption of SVG and the inception of Xouvert (which now has goals for both the short term and long term, and an initial plan which includes coexisting with XFree86), spells a bright future for the eye candy of an X desktop."

216 comments

  1. Well now, that's just great. by AntiOrganic · · Score: 1, Insightful

    That's all good and well, so when are we getting alpha-blending in X? It's really annoying having "almost" transparent terminals that copy my background.

    1. Re:Well now, that's just great. by Rooktoven · · Score: 4, Insightful

      In some ways almost transparent is easier on the eyes. I know when I have 4 or 5 mac terminals open the overlay can be confusing-- not to mention if (assuming a dark background) a light colored application ends up behind a terminal.

      I know it's nice for the "see what is possible" factor, but pseudo-transparency has it's place. I might even opt for it at times if I had the choice.

      --

      Acquiescence leads to obliteration
    2. Re:Well now, that's just great. by Webmonger · · Score: 1

      Well, Cairo supports translucency. Maybe you'll get your alpha-blending from Cairo?

    3. Re:Well now, that's just great. by Anonymous Coward · · Score: 0

      I've been wating for that for years...... it's soo sad when my mac friend that doesn't know anything about software/hardware upgrades to Mac OSX and gets all sorts of awesome features like that. :(

    4. Re:Well now, that's just great. by bhtooefr · · Score: 0, Offtopic

      Hmm, I didn't think anything before Windows 2000 supports alpha-blending. You are talking about Windows NT 4 (code name Cairo), right?

    5. Re:Well now, that's just great. by Anonymous Coward · · Score: 0

      Maybe after all the more important stuff is taken care of. While you're waiting, I suggest not using the "almost" transparent terminals.

    6. Re:Well now, that's just great. by perlchild · · Score: 1

      I was hoping I wouldn't be the only one to see this coincidence :)

    7. Re:Well now, that's just great. by Jon+Abbott · · Score: 3, Insightful

      I can't remember where I read this quote, but it went something like, "In the publishing industry, tons are spent and much effort is made to ensure that the paper is thick enough so that the reader can't see the words underneath the current page... In the computer industry, it seems that the effort spent is for the opposite effect." :^)

    8. Re:Well now, that's just great. by Squareball · · Score: 3, Funny

      Maybe you'll get your alpha-blending from Cairo?

      Importing alpha-blending from Cairo is WAY to expensive. Just try getting it through customs!

    9. Re:Well now, that's just great. by Anonymous Coward · · Score: 0

      I think you are confusing binary transparancy with alpha blending.

      With X only supporting binary transparency, shaded/brightened/"almost transparent" backgrounds have to be captured and blended in software.

      With proper alpha-blending support, the capture step would be skipped, and the video card would blend the pixels in hardware. Much faster. And that's what we want.

    10. Re:Well now, that's just great. by jo42 · · Score: 1


      Only fag-boy Linux geeks want transparent windows. The rest of us couldn't give a flaming shite.

  2. great by SHEENmaster · · Score: 3, Funny

    but when do we get an ASCII renderer for it?

    --
    You can't judge a book by the way it wears its hair.
  3. Windows NT 4.0 by firehawk2k · · Score: 0

    Wasn't Windows NT codenamed Cairo?

    1. Re:Windows NT 4.0 by pohl · · Score: 1

      At least some version of NT was code-named "Cairo", back in the days when NeXT was working on "Mecca" and IBM had the "Workplace OS" version of OS/2 in the works. I don't think much of the "Cairo" feature-set actually made it to market. It was supposed to have some lovely object-database filesystem or something, wasn't it?

      --

      The "cue the foo posts in 3, 2, 1..." posts will commence with no subsequent foo posts in 3, 2, 1...

    2. Re:Windows NT 4.0 by ultrabot · · Score: 1

      ISTR it was Windows 95.

      --
      Save your wrists today - switch to Dvorak
    3. Re:Windows NT 4.0 by KoolDude · · Score: 3, Interesting


      Actually, it was Windows XP which was code-named Cairo. X and P refer to Greek Letters Chi and Rho. Possibly Xr changed to Cairo using the same logic. Just a guess, though.

      --
      getSexySig(); /* returns sexy signature */
    4. Re:Windows NT 4.0 by Mooset · · Score: 1

      Nope, Windows 95 was Chicago.

    5. Re:Windows NT 4.0 by billatq · · Score: 1

      I think Windows 95's codename was Chicago, not Cairo.

    6. Re:Windows NT 4.0 by BigBadBri · · Score: 1
      Cairo was what was proposed for NT5 - or Win2K as it turned out.

      They never got the OO filesystem to work, though, so NTFS lives on.

      --
      oh brave new world, that has such people in it!
    7. Re:Windows NT 4.0 by Anonymous Coward · · Score: 0

      Cairo was roughly Win 2000, and bits and pieces of it did make it market -- ActiveDirectory, distributed file system, object broker (COM+).

      What didn't make it was that all of this stuff would be tied into some sort of universal "Information Everywhere" framework. Supposedly that's coming in "Longhorn" with a DB-based filesystem.

    8. Re:Windows NT 4.0 by Anonymous Coward · · Score: 0

      I was reading about Cairo when they were still developing windows 95.

      so I guess you're wrong...

    9. Re:Windows NT 4.0 by bhtooefr · · Score: 2, Interesting

      BZZT! It WAS Windows NT 4.0. Here's a FOLDOC entry on NT4:

      Windows NT 4

      A version of Microsoft's Windows NT operating system, originally code named "Cairo". It was supposed to ship in the first half of 1995. Details are scarce, but it is intended to provide an object-oriented version of Windows.

      (1996-07-09)

    10. Re:Windows NT 4.0 by Anonymous Coward · · Score: 0

      > BZZT!
      OK, we got it, you're an ass.

      > It WAS Windows NT 4.0.

      No it wasn't. Cario was killed or backburnered at MS long before NT4 shipped. NT4 had some other code name ("Daytona"?) and shipped with none of the promised Cairo features.

      The propaganda about Cairo was coming heavy and thick in the 93-94 time frame, and it was always described that Cairo was the next version after the next version of NT -- roughly v5.

    11. Re:Windows NT 4.0 by KoolDude · · Score: 1


      The official code-name for Windows XP was Whistler. However, it is safe to say that the name XP is an intended pun referring to the early 90s project Cairo. The actual Cairo project was only hyped and never came to light. Apparently, Windows XP had all the features that were promised in Cairo.

      --
      getSexySig(); /* returns sexy signature */
    12. Re:Windows NT 4.0 by Anonymous Coward · · Score: 0

      In fact Cairo has been postponed a few times (surprise surprise :) and was used as a name of more projects. At first Cairo was a codename for Windows NT 4.0, when WNT4 was released without all the nifty Cairo features Microsoft said Cairo would be the next release and continued to postpone it until year 2000 or so.

      One could say Cairo was the development branch of Windows based on NT kernel and Windows 95 interface. From this branch, WNT and W2K were released.

    13. Re:Windows NT 4.0 by tuba_dude · · Score: 1
      ...ActiveDirectory, distributed file system, object broker (COM+).

      Sorry, is it just me, or did I read that as "object breaker"?

      --
      "The government of the United States is not, in any sense, founded on the Christian religion."
    14. Re:Windows NT 4.0 by John+Allsup · · Score: 1

      This was BEFORE WNT4 was unveiled to the public, and before the later press releases that NT4 was not, in fact, going to be the Cairo OS that they'd been touting over the previous months. Then people were talking about NT5 being Cairo, but alas, that also wansn't to be. In the end, Cairo fell by the wayside and we've got what M$ are currently putting out.

      --
      John_Chalisque
    15. Re:Windows NT 4.0 by bhtooefr · · Score: 1

      No, it wasn't Daytona. From a Windows Server 2003 history on Paul Thurrott's SuperSite for Windows, here's some info on Daytona:

      The next release, Windows NT 3.5, was code-named Daytona, and shipped in September 1994. "Daytona was a very rewarding project," Thompson said. "We focused on size and performance issues, and on "finishing" many of the first-release features of 3.1. Daytona also had significant functional improvements and enhancements." The original themes for Daytona were size, performance, compression, and Netware compatibility. Two of those goals were emblematic of the time: DoubleSpace-style compression was a hot topic in the early 1990's because disk space was at such a premium, and Netware was the dominant network operating system of the day. "We eventually dropped compression," Thompson said, "but the Netware port was strategic. Novell was ambivalent about the NT desktop ? they didn't know if they wanted to build a client. We offered our assistance, but they kept messing around and ... well. We did our own. And it just blew them away. Ours was the better Netware client, and customers used ours for years, even after they finally did one. That client enabled the NT desktop, because Netware was the prevalent server in the market. We wouldn't have been able to sell NT desktops otherwise."

      Daytona also benefited from new compiler technology which enabled Microsoft to compress the code size and enable realistic NT desktops on lower-end systems than the original version. "The results were measurable," Thompson said.

      Windows NT 3.51 was dubbed the Power PC release, because it was designed around the Power PC version of NT, which was originally supposed to ship in version 3.5. But IBM constantly delayed the Power PC chips, necessitating a separate NT release. "NT 3.51 was a very unrewarding release," Thompson said, contrasting it with Daytona. "After Daytona was completed, we basically sat around for 9 months fixing bugs while we waited for IBM to finish the Power PC hardware. But because of this, NT 3.51 was a solid release, and our customers loved it." NT 3.51 eventually shipped in May 1995.

    16. Re:Windows NT 4.0 by AgTiger · · Score: 1

      See the following link. Cairo is listed as "Originally Windows NT 4.0, later a designation of technologies, which were planned partly for NT 4 and/or NT 5. Cancelled.

      Bink.nu: Microsoft Codenames

  4. eye candy? by Anonymous Coward · · Score: 0, Insightful

    If I wanted eye candy, I'd buy a Mac...

    Just give me a good, solid system to do my stuff on!

    1. Re:eye candy? by log2.0 · · Score: 2, Interesting

      I have always thought vectors were the way to go. The mac implementation is really good (I used mac os X for the first time yesterday). Although having a nicer looking desktop (as long as its optimized) is a good thing. Of course, at first, you wouldnt expect it to go very fast but it should get faster and stable in good time.

      --
      Can your karma go above being Excellent?
    2. Re:eye candy? by oc255 · · Score: 2, Interesting

      One of the parts in the article mentions a user-specified error tolerance to control quality vs performance. I'd be curious to see how this performs in the real world.

      There's already a gnome theme by the name of scalable gorilla that uses vector graphics. It runs a little slow on slow CPUs, but it looks fantastic and it's easily configurable. With a bitmap icon, I have to recreate the graphics file, with the Scalable Gorilla theme, I change text in a XML file. Another thing to keep in mind is the size of the hi-res bitmaps that would be required to compete with the computer synthesized perfection of vector graphics.

      Isn't this a disk space vs CPU tradeoff? I have to store a bitmap where I have to compute a vector? I'm all for using my untapped CPU cycles instead of disk storage.

    3. Re:eye candy? by fireboy1919 · · Score: 2, Interesting

      The lack of vector graphics was on of the major arguments citing why X11 doesn't work very well over low-bandwidth links.

      Is having X over low bandwidth eye candy?

      --
      Mod me down and I will become more powerful than you can possibly imagine!
    4. Re:eye candy? by diamondc · · Score: 1

      Mac OS X definetly uses pixels, instead of vectors for the icons.

      --
      "I keep looking in the want-ads under 'revolutionary' but there don't seem to be any listings.. "
    5. Re:eye candy? by fault0 · · Score: 1

      > The lack of vector graphics was on of the major arguments citing why X11 doesn't work very well over low-bandwidth links.

      Have you ever heard of NX? It's not vector based yet beats the shit out of vector based protocols.

    6. Re:eye candy? by Anonymous Coward · · Score: 0

      Normal folks act to maximize beauty ... beauty is truth, it's a basic food-group like air & water. Only twinkee_munching, Jolt_swilling byteboyz with one thumb up their azzwhole and a lust for repulsive, ugly recursiion confuse beauty with candy.

    7. Re:eye candy? by fireboy1919 · · Score: 1

      I have. I used it back when it was called mlview-dxpc. Trouble with that is that you have to recompile X11 on the server and the client just to use it, and that's not very useful when you aren't an administrator of the server (so that you can reinstall X11).

      Of course, if you control both sides, it's nice.

      It needs to be standardized to be useful. But anyway, it'll work even better with vector-based additions.

      --
      Mod me down and I will become more powerful than you can possibly imagine!
    8. Re:eye candy? by Anonymous Coward · · Score: 0

      "Trouble with that is that you have to recompile X11"

      You don't have to. NX stays on top of X11 and it only works with the X11 network protocol. You don't need a special X server and don't need to recompile the X clients. Proxy sits between the clients and the X server and is transparent to both of them.

      The nx-X11 source tree is only used to compile the agents. Agents are special X clients that can leverage the NX protocol extensions. As with mlview-dxpc, you only need nxproxy to compress the X protocol.

    9. Re:eye candy? by usotsuki · · Score: 1

      "Beauty is truth, truth beauty; that is all
      Ye know on earth, and all ye need to know."

      qp?

      -uso.

      --
      Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
    10. Re:eye candy? by TRACK-YOUR-POSITION · · Score: 2, Insightful

      Steve Jobs doesn't want you to theme your Aqua eye candy--which kinda defeats the purpose, IMHO. Not to mention that Mac OS X doesn't let you exploit the most important benefit of vector graphics--resolution independence.

    11. Re:eye candy? by fireboy1919 · · Score: 1

      Don't you need it to build the xnest server they've got?

      It's not really that awesome without that.

      --
      Mod me down and I will become more powerful than you can possibly imagine!
    12. Re:eye candy? by Anonymous Coward · · Score: 0

      Yes, but from the point of view of the remote server running the desktop it's just a X client.

  5. Cairo? Bill Gates will be contacting them. by Anonymous Coward · · Score: 4, Funny

    This is the code name for Windows NT. This is a blantant and illegal DMCA violation, and a dilution and sullying of Windows NT's good name. They will be served.

    1. Re:Cairo? Bill Gates will be contacting them. by meckardt · · Score: 1

      I doubt it. Isn't NT about to be End-of-Lifed soon anyway?

    2. Re:Cairo? Bill Gates will be contacting them. by samael · · Score: 2, Informative

      NT 4.0 was EOL-ed back in June. 2000 is, however, NT5 and XP is NT5.1 (I think).

      Cairo was never the codename for NT anyway, it was the codename for the Object Oriented File System microsoft was working on that was going to go into Win2k.

    3. Re:Cairo? Bill Gates will be contacting them. by SquadBoy · · Score: 1

      Cairo was Win 98 I think.

      --

      Cypherpunks: Civil Liberty Through Complex Mathematics. Those who live by the sword die by the arrow.
    4. Re:Cairo? Bill Gates will be contacting them. by samael · · Score: 1

      The Register disagrees

    5. Re:Cairo? Bill Gates will be contacting them. by dvdeug · · Score: 1

      This is the code name for Windows NT.

      Then we'll have to rename it to Butthead Astronomer, then.

    6. Re:Cairo? Bill Gates will be contacting them. by JarekC · · Score: 1
      Cairo was never the codename for NT anyway, it was the codename for the Object Oriented File System microsoft was working on that was going to go into Win2k.

      You are both right. Cairo was the codename of Windows NT 4.0, back in the days of WinNT 3.n (codenamed Daytona). However, it was later reused as the codename for a unified distributed filesystem.

    7. Re:Cairo? Bill Gates will be contacting them. by squiggleslash · · Score: 1

      Oh, it's perfectly understandable: this is merely following the current Linux Desktop development team of copying something Microsoft has done...

      --
      You are not alone. This is not normal. None of this is normal.
    8. Re:Cairo? Bill Gates will be contacting them. by axxackall · · Score: 1

      By the way, what's happened to that file system?

      --

      Less is more !
    9. Re:Cairo? Bill Gates will be contacting them. by scrytch · · Score: 1

      > This is the code name for Windows NT

      You're thinking of Windows 95. NT's code name was, get ready for it, NT. It never escaped its codename except for adding a "Windows" in front of it when they added the Win32 layer.

      --
      I've finally had it: until slashdot gets article moderation, I am not coming back.
    10. Re:Cairo? Bill Gates will be contacting them. by barzok · · Score: 1

      No Win95 was Chicago. Cairo was supposed to be NT4, then it devolved into a loose collection of technologies for future MS OSes, some of which have seen the light of the day, a couple which have not.

    11. Re:Cairo? Bill Gates will be contacting them. by Jah-Wren+Ryel · · Score: 1

      It sounds like Cairo has morphed into this "WinFS" thingee which is not an FS but rather a OO database layer on top of NTFS or some other filesystem.

      --
      When information is power, privacy is freedom.
    12. Re:Cairo? Bill Gates will be contacting them. by Anonymous Coward · · Score: 0

      And, of course, The Register is never wrong.

  6. Re:Who the hell cares? by AntiOrganic · · Score: 1

    They are. It's slated for inclusion in 2.4, if I recall correctly.

  7. KDE3? by SHEENmaster · · Score: 4, Informative

    QT3 has translucent menu items and such. I haven't checked to see if they cheat by reading from the screen, or if they have implimented an alpha layer.

    The big issue with an alpha layer is that someone has to have the authority to impliment such a change in the X11 protocol, it can't be done as an extension. Anyone who uses the fucked up protocol won't be able to display their app on a different X server. This breaks compatibility with thin clients.

    What I want is complete revamping of the X protocol with backward compatibility maintained (permanently), such that new apps can take advantage of new server-side widgets without breaking compatibility. Wouldn't it be sweet if GTK+ apps could run as well over a 256kb/s line as XAW apps do?

    --
    You can't judge a book by the way it wears its hair.
    1. Re:KDE3? by Anonymous Coward · · Score: 0

      They do cheat.

    2. Re:KDE3? by Anonymous Coward · · Score: 0

      are you implying that XAW widgets are server side?

    3. Re:KDE3? by rmull · · Score: 1

      Yes, they cheat.

      --
      See you, space cowboy...
    4. Re:KDE3? by IamTheRealMike · · Score: 4, Informative

      They do cheat, yes. There is no need to break backwards compatability, in fact the protocol already has what's needed, it's mostly a matter of XFree engineering and getting it effecient enough to not kill performance. If you want GTK apps to run sweet over a modem even, look into NX compression. Again, no need to break X.

    5. Re:KDE3? by bhtooefr · · Score: 1

      They do a bad job of cheating. Ever try transparency in Konsole? It's not showing you what's directly behind your Konsole, it's showing you your desktop background.

    6. Re:KDE3? by andrewl6097 · · Score: 2, Interesting

      Actually the protocol wouldn't have to be changed much at all. I've investigated this - the alpha value can be passed in the word-alignment byte. If you load up transluxent and throw real alpha values into your XImage, then it will be real alpha. It's just that regular XFree86 ignores the word alignment byte, and transluxent just passes it on to OpenGL so it actually works fine. Unfortunately transluxent isn't very stable.

    7. Re:KDE3? by Breakfast+Pants · · Score: 1

      How about KDE's translucent menus?

      --

      --

      WHO ATE MY BREAKFAST PANTS?
    8. Re:KDE3? by Daniel+Phillips · · Score: 1

      They do cheat, yes. There is no need to break backwards compatability, in fact the protocol already has what's needed, it's mostly a matter of XFree engineering and getting it effecient enough to not kill performance.

      It will be pitifully slow without major changes to the rendering model. Window buffers are one approach, but there's a better way to do it: retained mode graphics where each window buffers a list of graphics primitives that are re-rendered on window expose or any visibility event, such as lying underneath a translucent window that changed. The primitives can be sorted into, e.g., a quadtree, to make partial exposes of complex windows efficient. This can be done with minimal impact on applications.

      There are big advantages to this approach:

      - Memory efficient

      - Relatively processor-efficient, especially if accelerated with a 3D render card

      - Subpixel rendering - buffered window bitmaps don't support that

      - Easily extended to use standard 3D visibility and culling algorithms

      - Double buffering is an easy extension

      --
      Have you got your LWN subscription yet?
  8. This might even turn out better than expected by justsomebody · · Score: 5, Informative

    According to publications they are going to contact as many organisations and support as many standards as possible. That's something that XFree never did.

    They even plan to contact Freedesktop.org.

    --
    Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
    1. Re:This might even turn out better than expected by justsomebody · · Score: 0, Offtopic

      heh, there's even a funny post in xsvg archives

      [xsvg] Viagra and Diet Pills prescribed online! US doctors and pharmacies! Overnight Shipping imikwclffggizyh

      looks like, the mailing list is on a mailing list:)

      --
      Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
    2. Re:This might even turn out better than expected by 21mhz · · Score: 1

      They even plan to contact Freedesktop.org

      Bagh, Freedesktop.org came to existence because the XFree team was unwilling to develop any new standards in the first place.
      Now, roughly the same people who participate in the Freedesktop efforts are taking over the flag of free X server development as well. For me, it's definitely a turn to the better.

      --
      My exception safety is -fno-exceptions.
  9. This is OLD OLD news by HanzoSan · · Score: 1



    Why are we posting this when this happened like a month ago?

    Anyway where can I donate money to Cairo development?I mean I dont have A PHD in software engineering and cannot help with the actual development, so how about accepting donations people?

    --
    If you use Linux, please help development of Autopac
    1. Re:This is OLD OLD news by Anonymous Coward · · Score: 0

      Why not just send them some of that gold you've been hoarding from when you used to do your trolls with a Transgaming subscriber link in your sig?

    2. Re:This is OLD OLD news by Anonymous Coward · · Score: 0

      Because there's finally a break in SCO news to post a non-SCO article.

    3. Re:This is OLD OLD news by Anonymous Coward · · Score: 0
      Why are we posting this

      I don't know, why did you post it?

      You speak in the plural quite often. Who are you talking about?
    4. Re:This is OLD OLD news by Anonymous Coward · · Score: 0
      I dont have A PHD in software engineering

      Good, then there's still hope that you may one day be able to practice actual programming.

    5. Re:This is OLD OLD news by Anonymous Coward · · Score: 0
      Dean for President! geeks4dean.com [geeks4dean.com] Think Economy, Stupid!

      Will you PLEASE PLEASE get Howard's camp to STOP FUCKING SPAMMING ME.

  10. This is good. by Anonymous Coward · · Score: 0

    Gnomes SVG support is good, it allows me to run gnome on a 1920x1440 display, unlike kde, which seems to go flaky after 1280x1025.

    1. Re:This is good. by Anonymous Coward · · Score: 0

      Hmm.. kde runs fine on 1600x1200 here (well, actually 3200x2400 if you count xinerama..)

      But yeah, svg icon support might be cool in kde. Only GNOME has it so far, I guess (no, OSX does NOT have any vector icon support, they go from vectors->to prerendered pixmaps like KDE)

  11. Re:Dumb name of the month by Mooncaller · · Score: 0, Redundant

    Whys it dumb? Chi = X, Rho = r. Together they are pronounced Cairo.

  12. You have no need to upgrade. by HanzoSan · · Score: 3, Interesting



    Cairo is not for you! someone like you should use the old version of Xfree86 because you dont like cutting edge, you dont like polish, you dont need eye candy.

    But please do not hold the rest of us back because you dont want progress.There's the commandline and original Xfree86 for people like you, we also need to attract desktop users, and this requires eyecandy.

    They will not switch from Windows if Windows is better.

    --
    If you use Linux, please help development of Autopac
    1. Re:You have no need to upgrade. by Anonymous Coward · · Score: 0

      Another troll from the master of..stupid trolls.

    2. Re:You have no need to upgrade. by tuba_dude · · Score: 1
      They will not switch from Windows if Windows is better.

      Replace 'is' with 'looks'. Everyone will be happier.

      --
      "The government of the United States is not, in any sense, founded on the Christian religion."
    3. Re:You have no need to upgrade. by bockman · · Score: 1
      we also need to attract desktop users, and this requires eyecandy..

      No, to attract desktop users you need:

      • Applications
      • More applications
      • A user-friendly interface, i.e. a constistent computer-supported methaphor that allow them to learn how to do the things they have to do without loosing time with meaningless (for them) details.

      Eye-candy is for geeks and for people which use the computer as 'status-symbol'. Maybe still a worthing target, but different from the 'average desktop user'.

      --
      Ciao

      ----

      FB

  13. We can do better than the mac implementation. by HanzoSan · · Score: 1



    We can, should and MUST do better than MacOSX. We must also do better than Microsoft. If we are to compete with these rich billion dollar companies, Linux must simply be better. A person should be able to SEE that Linux is better and not just a clone.

    How about some innovation?

    --
    If you use Linux, please help development of Autopac
    1. Re:We can do better than the mac implementation. by fireboy1919 · · Score: 1

      How about "exactly the same except that it doesn't cost anything."

      It sounds better to me, anyway.

      But, anyway, it will probably be better simply because it'll be a thin client, and the others aren't.

      --
      Mod me down and I will become more powerful than you can possibly imagine!
    2. Re:We can do better than the mac implementation. by HanzoSan · · Score: 1



      Desktop users dont want that. Thats what a company wants. Companies buy what is cheapest and most thin,

      Desktop users buy whatever looks best.

      --
      If you use Linux, please help development of Autopac
    3. Re:We can do better than the mac implementation. by fireboy1919 · · Score: 1

      Well...I want that. It lets me use my stuff anywhere without carrying around my computer.

      I imagine other people might if they saw it as a possibility. It's not at the moment. Most people didn't think about having PDAs before they were actually useful for something.

      I am a desktop user. Hence, there is at least one desktop user who prefers "with thin client" to "without thin client" because I see the potential.

      --
      Mod me down and I will become more powerful than you can possibly imagine!
    4. Re:We can do better than the mac implementation. by HanzoSan · · Score: 1



      I know what you mean and I do the remote thing every once in a while, but I showed it to people and every one I showed it to couldnt find a use for it. They have been using windows for so long that when I showed it to them they were like "how could I ever use this?"

      People just dont use computers like we do, they use it casually.

      --
      If you use Linux, please help development of Autopac
  14. sub-pixel aliasing? by Anonymous Coward · · Score: 1, Interesting

    Does anybody know if sub-pixel anti-aliasing is planned for this -- or any other vector drawing APIs? Smooth anti-aliased lines look nice, but they look bad in comparison when they're next to sub-pixel anti-aliased text on an LCD screen.

    1. Re:sub-pixel aliasing? by BattleCat · · Score: 0

      Sub-pixel AA for text is already in freetype2 and Xft2, although not on par with MS ClearType. I've played with it for some time trying to improve the results, but nobody was interested enough to listen :-)

    2. Re:sub-pixel aliasing? by Anonymous Coward · · Score: 0

      Yes, but that is only for text. I'm talking about the other things drawn on the screen, and it could even be done to regular bitmapped images.

  15. WTF? by Anonymous Coward · · Score: 0

    I thought KDE3 didn't cheat despite the 5 people below that disagree. Sure, konsole copies the background image, but when you turn on menu translucency w/ the Keramik theme, it's a real Xrender based transparency (as in you'll see whatever's underneath it - videos, windows, kcalc, whatever). Who are these people yelling cheat? I thought that would be considered legit.

    1. Re:WTF? by uhmmmm · · Score: 2, Informative

      because, IIRC, it grabs what's on the screen before the menu pops up, and uses that. if the window, video, etc displayed under the menu changes while the menu is still shown, the menu isn't updated.

    2. Re:WTF? by Carlos+Laviola · · Score: 1

      Incorrect. I just tried that with a konsole running irssi in the background and, sure enough, it scrolled by on the transparency when someone said something.

  16. Not eye candy!!! by G3ckoG33k · · Score: 4, Interesting

    "right future for the eye candy of an X desktop"

    This is essentially untrue. Accepting vector graphics as the default in computers may alter our perception of what is eye candy completely. As far as I'm concerned the Fresco/Berlin project was the right way already several years ago. Today, the hardware has caught up and there is nothing to be lost in user space with vector graphics everywhere.

    In fact, we have no idea what kind of possibilities may open up here. If we're unlucky, yes, it might be a can of worms... ;)

    1. Re:Not eye candy!!! by jsebrech · · Score: 1

      At least we'll finally be able to put those IBM 200 dpi screens to good use.

    2. Re:Not eye candy!!! by penguin7of9 · · Score: 5, Informative

      As far as I'm concerned the Fresco/Berlin project was the right way already several years ago. Today, the hardware has caught up and there is nothing to be lost in user space with vector graphics everywhere.

      X11 doesn't support "vector graphics" any more or less than it used to. What has changed is that X11 now has an imaging model similar to PostScript (subpixel addressing, antialiasing, etc.) in addition to its older bitblit model (pixel-accurate, using boolean operations for drawing).

      (Subpixel addressing also allows you to do zoomable or "resolution independent" graphics, while the bitblit model is resolution dependent. However, the term "resolution independent" is somewhat of a misnomer--even if your imaging model supports arbitrary zooming, you can't just zoom user interfaces up and down and expect them to be usable.)

      When people talk about "vector graphics" in the context of window systems, that usually means the use of display lists: you give the server a list of "objects" to display (lines, triangles, rectangles, etc.), and the server takes care of displaying them when needed. But they might mean something else as well.

      Display lists in X11 are still handled the way it has always been handled: by client-side libraries. Eventually, there may be a server-side extension for handling display lists and perhaps even the ability to transfer display lists and structured graphics in the form of SVG data. That would give you Quartz-like redrawing and rescaling, although while that looks nice it has few real advantages.

      Now, what about Berlin vs. X11? First of all, one big thing in Berlin is the incorporation of GUI components into the server. That is an anathema to X11 designers. Also, while resolution-independent graphics is nice (the same thing X11 now supports with Cairo), it is a poor choice as the only graphics model: well-designed application for low-resolution and/or low-depth screens (e.g., a 160x160 Palm) must be able to draw with pixel-accurate drawing operations and precisely predictable results on every bit on the screen.

      I don't think Berlin "got it right". Berlin concentrated on the obvious, convenient, clean, high-level stuff. Berlin would give you slick-looking OS X-like desktops if it ever caught on, but the Berlin designers have neglected the other imaging models that are really important to real window systems, and they have put way too much policy into the server.

      Fortunately, the way X11 is evolving, we won't have to make a choice: you can have all the slick antialiased, structured graphics you like, and yet still have pixel-accurate drawing in a bounded memory X11 implementation. The only difference will be that X11 still won't enforce policy on the server side, and that's a good thing as far as I am concerned. But the market will decide that issue.

      In fact, we have no idea what kind of possibilities may open up here. If we're unlucky, yes, it might be a can of worms... ;)

      There is no "can of worms". We have had window systems with antialiased drawing, structured graphics, and all that at least since the 1980s; maybe you remember NeXT and NeWS. The feature is nice, but it doesn't radically change what people do with GUIs.

    3. Re:Not eye candy!!! by Deusy · · Score: 1

      Perhaps a tad pedantic, but X11 is the protocol and hasn't evolved. XFree is, what I think, you are referring to.

      Replace all the X11 references with XFree86 and the parent was a very informative post!

      --

      Free Gamer - Free games list and commentary

    4. Re:Not eye candy!!! by Overly+Critical+Guy · · Score: 1

      The feature is nice, but it doesn't radically change what people do with GUIs.

      Then why does everyone else have it but Linux?

      --
      "Sufferin' succotash."
    5. Re:Not eye candy!!! by obi · · Score: 1

      Cool to see someone who doesn't have misconceptions about fresco. However, can you elaborate a bit on why you think putting as much policy as possible in the server is a bad thing?

      - it offers possibilities to take advantage of and adapt to the available hardware. (server knows if the screen is only a 4" PDA screen, or a 30" 3D display - the application shouldn't have to know these things)
      - it should be the user (where the server is) who decides on policy, not the application
      - it's bandwith friendly if you're only transferring high-level info to/from the servers.
      - you don't get different apps using different policies on the same server.

      etc.

      Anything I'm missing?

    6. Re:Not eye candy!!! by penguin7of9 · · Score: 1

      Perhaps a tad pedantic, but X11 is the protocol and hasn't evolved. XFree is, what I think, you are referring to.

      I view the Render extension as part of the X11 protocol family now, and Cairo as a portable client-library for it. So, in that sense, I do view this as a part of X11 now, not just some XFree86-specific hack. I believe some commercial vendors of X11 server implementations have already been tracking Render. I would hope that HP, Sun, and IBM will start supporting Render quickly.

    7. Re:Not eye candy!!! by penguin7of9 · · Score: 1

      Neither Windows nor MacOS got support for anything close to the PostScript imaging model until fairly recently, and very few applications take advantage of it.

      And did the Windows or MacOS GUIs get significant functional changes as a result? Not really: it's still the same old menus, the same old dialog boxes, the same old title bars, etc. They just look a little prettier, and transparency and fading give people some slight additional visual cues. Nice, but not exactly a revolution.

    8. Re:Not eye candy!!! by penguin7of9 · · Score: 2, Insightful

      it offers possibilities to take advantage of and adapt to the available hardware. (server knows if the screen is only a 4" PDA screen, or a 30" 3D display - the application shouldn't have to know these things)

      But the application has to know--scaling applications down to a PDA screen requires some hard choices to be made in terms of what is displayed. Merely scaling down the display won't help, and the server simply doesn't know enough about the application to do it automatically

      - it's bandwith friendly if you're only transferring high-level info to/from the servers.

      That is far from clear. Think of a grid bound to a large database table--does transferring all that data make sense? I don't think so. Not even on demand. In fact, even X11 may be too high-level in terms of bandwidth: VNC actually is often better in terms of bandwidth (but it is too low-level to be useful as a replacement for X11).

      - you don't get different apps using different policies on the same server.

      You get that on Windows and OS X. And Berlin were to catch on, people would port FLTK, Swing, wxWindows, and all those other toolkits to it as well.

      The X11/toolkit/UI layering is completely standard and analogous to GDI/MFC/Explorer and Quartz/Cocoa/Aqua. The only difference is that X11 is well-designed and mature enough that there are, in fact, multiple commonly used toolkits and that those toolkits can even somewhat interoperate. That's a good thing.

    9. Re:Not eye candy!!! by Ed+Avis · · Score: 1

      I don't understand why on Slashdot, the main application of any display improvement is automatically assumed to be the latest skin for GTK or kewl Enlightenment theme. Eye candy is about the least important thing in a desktop.

      --
      -- Ed Avis ed@membled.com
  17. This news predates Slashdot by bhtooefr · · Score: 1

    Wasn't Cairo released in 1996 or something? BTW, I don't think MS wants your money for Cairo anymore. They'd rather have your money for at least Windows 2000, if not XP or Server 2003.

  18. So, when does this turn in to a practical product? by Vexalith · · Score: 3, Interesting

    I like the sound of Xr/Cairo, seems pretty cool. But how long is it going to take for this to turn in to something I can actually use? I guess the eventual goal is to have GTK and QT running on top of Cairo (maybe with extensions to do explicitly vector things?), but this strikes me as something that's not going to happen fast. Maybe I'm just being impatient.

  19. Technology, not XP by Anonymous Coward · · Score: 1, Informative

    Cairo was well before Windows XP.

    Microsoft's Cairo was a project of the 90s which started off as an operating system but became a set of technologies. Some of Cairo went into NT 4.0, more into Windows 2000, while some parts like an Object Oriented were never finished. Longhorn (XP's successor) had it's plan of a distributed file system downgraded down to a service running on NTFS.

    The three main portions of the technology were: Expanded Directory Services, Object-Based File System, and Expanded integration with DNS.

  20. That sample rasterized penguin looks contented! ;) by f1ipf10p · · Score: 2, Interesting

    Stuffed on the finest of herring no doubt!

    Great news on the arrival of rasterized graphics output for Xfree86. That should allow for some superb gaming, visual modeling, and graphic apps for Linux.

    XrStroke is sure to be a popular command...
    maybe that explains the contented look... randy penguin!

    If you are lost with these references, you might enjoy "Why a penguin?" and "linux" together as a google search.

    --
    ~8^]
  21. But by Anonymous Coward · · Score: 0

    Will they port twm to it?

  22. Re:That sample rasterized penguin looks contented! by Vexalith · · Score: 1
    That should allow for some superb gaming
    Not if it isn't hardware accelerated. Until then OpenGL will still be the way to go.
  23. Finally, buffering. by TheRaven64 · · Score: 4, Insightful
    From the short term goals:

    Provide an option to force backingstore on all windows.
    This is the one I've been waiting for for a while. When RAM was $500 for 64K it made sense not to buffer windows, but now it is insane not to, forcing redraws which drain CPU and networt bandwidth (on remote displays).
    --
    I am TheRaven on Soylent News
    1. Re:Finally, buffering. by Anonymous Coward · · Score: 1, Informative

      Doesn't just turning Option "backingstore" in XF86Config force all windows to use it? That's been my experience.

    2. Re:Finally, buffering. by listen · · Score: 2, Interesting

      Of course, once we have backing store it is a small step to provide (unaccelerated) translucent windows.

      The *really* important thing to do after that is to provide an extension to use the backing store of each window as a pixmap, and as a OpenGL texture.

      This will allow a window manager to do nice tricks.
      * On a window move, unmap the window, get its backing store as a GL texture, and do all the flippy rolly effects that have got everybody salivating over longhorn and OSX.
      * Expose like effects. See if those patents (or the will to sue) hold up ;-)

      It could also allow desktop pagers to get an accurate picture of whats on the screen, and maybe provide a slightly improved performance for remote desktops like NX and x0rfb. Not as good as a drawing command redirect, as I said here.

      For some really nice currently available eyecandy, see 3ddesktop . This should make clear that its not neccessary to shove too much into the server to get nice things done.

  24. Re:Then you want Windows Millennium. by arkane1234 · · Score: 1

    I think you missed the "good" and "solid" part of that sentence.

    --
    -- This space for lease, low setup fee, inquire within!
  25. Here is what I think the Linux GUI needs. by HanzoSan · · Score: 4, Interesting



    I think the whole friggin GUI should be vectors. The Icons should be vectors, and these vectors should be manipulated in realtime via the video card/hardware.

    Forget software rendering, we need hardware rendered GUI, using SVG for the interface and icons.

    We also need to somehow maybe via OpenGL or some technique, to get the special effects of the video card applied to the GUI.

    Then someone can write KDE4 or whatever, and the eyecandy/special effects should be plugins, a person should be able to code an effect via a scripting or programming language, someone should be able to download say, the motion blur or sparkle plugin, and then I click it and suddenly my menus motion blur or sparkle with fairy dust when I move them.

    You could break the effects up into groups.

    Scaling effects
    Trails for cursor
    Trails for menu
    Icon effects/animations

    etc, and when this is done, then people can write themes easily etc and we can innovate.

    The key should be a system that allows a newbie who isnt a coding genius to actually manipulate a video card either via scripting, or some high level interface.

    What I want is complete revamping of the X protocol with backward compatibility maintained (permanently), such that new apps can take advantage of new server-side widgets without breaking compatibility. Wouldn't it be sweet if GTK+ apps could run as well over a 256kb/s line as XAW apps do?

    I dont care so much about backward compatibility and I dont think most desktop users do. Servers sure as hell wont be running this. But if back compatbility is so important that can be handled to.

    QT3 has translucent menu items and such. I haven't checked to see if they cheat by reading from the screen, or if they have implimented an alpha layer.


    Fake translucency is not what people want, we want alpha channeling. This will only happen when the whole interface changes from pixel based to SVG based and then an OpenGL backend to access the video cards.

    I think Evas has the right idea here, now its just time to have X catch up to it.

    --
    If you use Linux, please help development of Autopac
    1. Re:Here is what I think the Linux GUI needs. by sketerpot · · Score: 1
      I agree completely. Screw the current practice of using X as a glorified framebuffer, I want my vector based GUI!

      Years ago, I had a vector based GUI. Now, however, that old NeXTSTEP box is just too old and obsolete. It was nice, though, having the whole GUI use PostScript. Now, I don't really care if you want to use PostScript, SVG, or whatever. It would be nice if both were supported somehow, but this should be in some layer of abstraction. Make the basic protocol elegant and extensible---you'll be living with it for quite a while.

    2. Re:Here is what I think the Linux GUI needs. by Anonymous Coward · · Score: 0

      now its just time to have X catch up to it.

      So... that'll be 10-15 years then?

    3. Re:Here is what I think the Linux GUI needs. by tuba_dude · · Score: 1

      Nice ideas. The only problem is X. From what I've seen, they're more worried about stability and backwards compatibility than new features. That's why I'm looking forward to xouvert. People can stick with standard XF86 for older systems, servers and terminal clients, while desktop users can have their eye candy. Compatability might eventually become an issue, but hey, it's open source. Somebody will find a way to fix it.

      --
      "The government of the United States is not, in any sense, founded on the Christian religion."
    4. Re:Here is what I think the Linux GUI needs. by Overly+Critical+Guy · · Score: 1

      This is exactly what needs to happen. In a few years, Microsoft is going to release a hardware accelerated desktop with full transparency and graphic effects. It would be nice if Linux would beat it to the punch within the next year.

      --
      "Sufferin' succotash."
    5. Re:Here is what I think the Linux GUI needs. by Feztaa · · Score: 1

      Wow, that sounds great! When can we expect to see your 0.1 alpha release?

  26. Cairo, hmm, that has been a Windows codename by marcovje · · Score: 1

    ... for one of the w9x window's versions.

    Bad, bad :-)

    1. Re:Cairo, hmm, that has been a Windows codename by Beetjebrak · · Score: 1

      Not Win9x, rather Win2K/NT5. Win95 was called Chicago (the beta had a 'welcome to Chicago' bootsplash), with WinXP/Longhorn they started moving from cities to mountains. XP was called Whistler, Longhorn (if I'm nog mistaken) is Blackcomb.

      --
      Learn from the mistakes of others. There isn't enough time to make them all yourself.
    2. Re:Cairo, hmm, that has been a Windows codename by Anonymous Coward · · Score: 0

      with WinXP/Longhorn they started moving [to names of] mountains

      How oddly fitting...

    3. Re:Cairo, hmm, that has been a Windows codename by marcovje · · Score: 1

      Win98 was Memphis IIRC.

  27. Its not done right, but its a start by HanzoSan · · Score: 1



    Gorilla is a start. I think however there should be no more bitmap / pixel based interfaces. This is 2003 and Linux should just go 100 percent SVG. People who want to use pixels can use their 486.

    Linux needs to prepare to take on Windows on the Desktop, this is going to require that Linux is cutting edge.

    Isn't this a disk space vs CPU tradeoff?

    Most people have more free CPU power than diskspace. Most people have 2ghz cpus, and super powered Gforce video cards which just dont get used at all except for a few tasks. Dont you think its time our software catches up to the hardware?

    The worse that can happen is make more people buy video cards and upgraes which will give us jobs again.

    --
    If you use Linux, please help development of Autopac
    1. Re:Its not done right, but its a start by aardvarkjoe · · Score: 2, Insightful

      This is 2003 and Linux should just go 100 percent SVG.

      Linux should have nothing to do with either bitmaps or SVG. You mean that XFree86 should be 100% SVG. (Which I think is a stupid idea, by the way. Breaking backwards compatibility for the sake of "market domination" is something that Microsoft would do, not engineers who actually care about the technical side of things.)

      --

      How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
    2. Re:Its not done right, but its a start by Anonymous Coward · · Score: 0
      Most people have 2ghz cpus, and super powered Gforce video cards

      I call BS.

    3. Re:Its not done right, but its a start by HanzoSan · · Score: 1



      If you want backward compatibility why not use the old version? People like you would tell KDE not to upgrade to QT4 because it breaks backward compatiblity.

      Ok Fossil, have fun running AfterStep, Fluxbox or any of the others on the old version of Xfree. Let those who want to progress have progress, stop holding the Linux community back with your nonsense!

      is something that Microsoft would do, not engineers who actually care about the technical side of things.

      Why is backward compatibility so important to engineers who create Xfree86 when they only use Linux to create Xfree86?

      --
      If you use Linux, please help development of Autopac
    4. Re:Its not done right, but its a start by aardvarkjoe · · Score: 2, Interesting
      Since when is removing support for something "progress?" You could make the exactly same arguments for Linus to remove support for IPV4, PCI support, IDE support, and a bunch of other stuff from the kernel. That, of course, would be stupid beyond belief. You can support SVG for new apps while retaining support for hundreds of applications that already exist. I'm not going to hold anyone or anything back, but I'm not going to go along with those who make technical decisions based on ignorance.

      Why is backward compatibility so important to engineers who create Xfree86 when they only use Linux to create Xfree86?

      What is this supposed to mean? Are you under the impression that XFree86 only runs on Linux? If so, here's a quote for those of you who live in the "Linux is the only thing there is" box:

      The XFree86 Project, Inc is the organisation which produces XFree86(TM), a freely redistributable open-source implementation of the X Window System. XFree86 runs primarily on UNIX(R) and UNIX-like operating systems such as Linux, all of the BSD variants, Sun Solaris x86, Mac OS X (via Darwin), as well as other platforms like OS/2 and Cygwin.

      That's directly from the XFree86 home page. Apperently, the engineers who create XFree86 do care about compatibility.
      --

      How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
    5. Re:Its not done right, but its a start by be-fan · · Score: 1

      You can support SVG for new apps while retaining support for hundreds of applications that already exist.
      >>>>>>>>>
      Careful, that's the same logic that got us the current anti-aliasing fiasco! To this day, I can't use most non-Qt or GTK+ apps because non-AA text is almost unreadable on my LCD.

      --
      A deep unwavering belief is a sure sign you're missing something...
    6. Re:Its not done right, but its a start by aardvarkjoe · · Score: 1

      I see what you mean, but the appropriate solution to that is to update the applications incrementally, not rip out any support for the older applications (as the OP suggested.)

      --

      How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
    7. Re:Its not done right, but its a start by HanzoSan · · Score: 1



      I care about Linux, not Xfree. Perhaps its time that Xfree gets a (Linux)fork.

      Xfree is like Mozilla, because of all these people trying to make it compatible with every OS and make it run the oldest software, it cannot compete with anything released in the last 5 years.

      --
      If you use Linux, please help development of Autopac
    8. Re:Its not done right, but its a start by aardvarkjoe · · Score: 1

      You still keep harping on the whole Linux thing. Get it through your thick skull: This has nothing to do with Linux. The GUI runs on the user level, not the kernel level. As I said, your technical arguments are based on ignorance.

      If you want to ignore the benefits of collaberation and portability, buy yourself a copy of Windows. That's what you really want.

      --

      How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
    9. Re:Its not done right, but its a start by be-fan · · Score: 1

      The problem is that the transition is so painful and unnecessary, and is really bad from a consistency point of view.

      Consider this: what if the XFree guys had just decided to add AA automagically to the X text functions? Some apps that used X in an unusual way would break and need to be fixed. On the other hand, the way it is now, some apps are still broken (they don't do AA text) but there is far less of an impetus to fix them (they still kinda work). Plus, on top of all that, we had to deal with that transition period, which lasted well over a year.

      --
      A deep unwavering belief is a sure sign you're missing something...
    10. Re:Its not done right, but its a start by aardvarkjoe · · Score: 1

      what if the XFree guys had just decided to add AA automagically to the X text functions?

      Unfortunately, the "just" is no small thing. The text rendering in X was not designed for that (unfortunately, but it's about twenty years too late now), and making it work would be somewhere between "horrible kludge" and "impossible." (I don't know exactly where it would fall; I've never looked at the XFree code and haven't done a whole lot of X programming.) Nothing they do can change the fact that old apps aren't going to magically antialias their text.

      New versions of XFree support antialiased text via extensions; it's now just up to people to use them. I fail to see why it would be better to completely break all old apps than support them and encourage the use of the new font systems when possible.

      --

      How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
    11. Re:Its not done right, but its a start by HanzoSan · · Score: 1

      "The GUI runs on the user level, not the kernel level. As I said, your technical arguments are based on ignorance."

      Don't you think I know the difference between the Linux kernel and the Linux OS? If the best arguement you can come up with is to redefine the definition of Linux, I suppose you conceed and I officially win.


      If you want to ignore the benefits of collaberation and portability, buy yourself a copy of Windows. That's what you really want.


      I dont use Linux for portability, I could care less if it runs on every piece of software every designed if it runs slowly. Mozilla does this too, its portable, and because of that its slow as hell.

      Java is portable, and because of this its slow as hell. Portable code is never better than native code, and I dont own every piece of hardware on planet earth, I only care about how the software I run happens to perform on the hardware I use. You compability fools should run your java based OS, there are many of them for you.

      By the way I'd sooner run OSX before running Microsoft, Microsoft thinks like you, trying to make everything compatible with the older versions of Windows, therefore they have a messed up API, and tons of bugs. Compatibility slows progress, its a fact, perhaps if Windows dropped trying to be compatible they'd have a secure unix based operating system by now.

      --
      If you use Linux, please help development of Autopac
    12. Re:Its not done right, but its a start by aardvarkjoe · · Score: 1

      Don't you think I know the difference between the Linux kernel and the Linux OS? If the best arguement you can come up with is to redefine the definition of Linux, I suppose you conceed and I officially win.

      You're being an idiot. This has nothing to do with Linux -- the OS or the kernel. This has to do with XFree. I would continue, but it's obvious from your juvenile "I win, you lose" retort that you have no interest in debate, and that you'd rather stick your thumbs in your ears and say, "nyah, nyah, can't hear you."

      --

      How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
    13. Re:Its not done right, but its a start by Wolfrider · · Score: 1

      (BS Answers) Hello? Hello?? Who's there? Is this a prank call?!

      --
      .
      == WolfriderV6 == I'm willing to admit that *I just might* be wrong... Are you??
  28. We didn't choose the name by Anonymous Coward · · Score: 0

    We were going to call it 'Trek' or 'Cannondale', but then some IBM dude who knows waaaaay more about choosing names than we do told us to call it 'Cairo'.

  29. Re:That sample rasterized penguin looks contented! by f1ipf10p · · Score: 1

    Probably true enough that OpenGL is the way for a while.

    Now that there is a set of instructions, perhaps they will be widely adopted and drive some sort of hardware accelerated video card with Cairo support. Not very easy for me to predict. Probably not likely.

    Still glad to see Xr / Cairo... And that penguin is very happy.

    btw-I love OpenGL, and think of it as legos for my monitor. I am very glad developers and video card manufacturers have done what they have with OpenGL. I dual boot my Radeon 9700 equipped PC - XP for games or 2.4.20-8 for most everthing else for that very reason.

    --
    ~8^]
  30. Mozilla SVG? by Anonymous Coward · · Score: 0

    So when will this library be used to add SVG to Mozilla on linux?

  31. Re:That sample rasterized penguin looks contented! by Vexalith · · Score: 1

    Unfortunately the problem with this will be getting hardware manufacturers to produce suitable drivers. Getting them to produce linux drivers for OpenGL was bad enough, and is still a mess (thanks, nVidia!). If designed well enough, perhaps Cairo itself can sit on top of GLX, but we'll see...

  32. Cairo == Windows XP by Anonymous Coward · · Score: 0

    Actually, Cairo is Windows XP.

    The XP is a greek pun that the MS engineers thought up. X is actually the greek letter Chi and P is the greek letter Ro, so Windows XP == Windows Chi-Ro (Sound it out).

    1. Re:Cairo == Windows XP by Anonymous Coward · · Score: 0

      Greek letters... greek letters... hmmm, greek letters... where have I seen greek letters recently?

      Hmmm... Aha! I knew they were behind everything!

  33. yesterday. by pb · · Score: 1

    Just load it up in XGGI, like so, silly!

    --
    pb Reply or e-mail; don't vaguely moderate.
  34. That spam is actually on topic by Anonymous Coward · · Score: 1, Funny

    > heh, there's even a funny post in xsvg archives
    >
    > [xsvg] Viagra and Diet Pills prescribed online!

    This is actually on topic for XSVG. Viagra is supposed to help men "scale" up while "Diet Pills" are for people to "scale down".

  35. Themes? by Anonymous Coward · · Score: 0

    Has anyone here tried any of those three themes they list? (cairo-simple, cairo-industrial, and cairo-nuvola.) I'm curious to see what they look like, but (like a typical unfriendly project page) they don't have any screenshots of what they've created.

    1. Re:Themes? by Anonymous Coward · · Score: 0

      Anyone? Anyone? Bueller?

  36. Re:Who the hell cares? by Anonymous Coward · · Score: 0

    It was slated for inclusion for gtk 1.2, then gtk 2.0, then 2.2, now 2.4? Try gtk 5.6.

  37. Who names these things? by IntelliTubbie · · Score: 4, Interesting

    Whatever happened to descriptive naming? Who would instinctively associate "Cairo" with "vector graphics for XFree86"? Why not name it something sensible, like "XVector" (if that's not already taken)?

    In all seriousness, I think that poor name choices hurt the adoption of free software. Think about "Photoshop" vs. "The GIMP," or "Internet Explorer" vs. "Mozilla." Rather than something simple, descriptive, and catchy, we usually opt for indecipherable codenames, stupid recursive acronyms, or lame in-jokes that few people but the developers themselves will get.

    Poor naming limits the spread of the software meme to those who are already in the know, especially when the names are designed to enforce an only-the-anointed-get-it, us-vs-them mentality.

    Cheers,
    IT

    --

    Power corrupts. PowerPoint corrupts absolutely.

    1. Re:Who names these things? by mauddib~ · · Score: 1

      Oh wait, we should call everything by its function then: Ford and Porsche must then be called eg. "NormalCar" and "FastCar". Is that what you intended?

      --
      This is a replacement signature.
    2. Re:Who names these things? by Anonymous Coward · · Score: 1

      So how descriptive are commercial product names like Excel, PowerPoint, Outlook, Dreamweaver, Premiere, Maya, Avid, and millions of others? It hasn't stopped their adoption.

    3. Re:Who names these things? by mattdm · · Score: 1

      Who would instinctively associate "Cairo" with "vector graphics for XFree86"? Why not name it something sensible, like "XVector" (if that's not already taken)?

      Well, exactly -- it's a cross-platform library not necessarily tied to X at all. That's why the name was changed *away* from "Xr".

    4. Re:Who names these things? by bitMonster · · Score: 2, Interesting

      X r -> Chi Rho -> Cairo

      Names are all about first impressions, anyway.

    5. Re:Who names these things? by damiam · · Score: 2, Insightful

      Jaguar, XP, Outlook, KaZaA, QuickTime, Quartz, DirectX, etc., there are a million proprietary apps or technologies with nondescriptive names. Besides, no end user should ever have to hear about Cairo, they should just see good-looking graphics.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    6. Re:Who names these things? by Anonymous Coward · · Score: 0
      Why not name it something sensible, like "XVector" (if that's not already taken)?

      I have no comment on Cairo's suitability as a name, but "XVector" is horrible. It sounds like a comic book character.

    7. Re:Who names these things? by BalloonMan · · Score: 1

      Actually, "Chi Rho" would be written as "X P", *not* "X r".

      In old illustrated religious manuscripts, e.g. The Book of Kells, you will see pages with elaborate decorations around this particular pair of letters. Why? Because Chi Rho was an abbreviation for (the first two letters of) the word, "Christ".

      When I read that they had changed the name, I thought it was the start of just another religious debate.

    8. Re:Who names these things? by tirenours · · Score: 0

      Yeah, but there are plenty of descriptive names, like xcalc / gcalc, proftpd, wuimapd, links, etc.

    9. Re:Who names these things? by fireboy1919 · · Score: 3, Informative

      That depends largely on your perspective.

      "P" is the closest thing we have to the greek letter rho, which phonetically is "R." The "P" sound is taken by the greek letter pi.

      Since Xr is written by people who speak English, not ancient Greek, it is likely that they're taking the letters from the modern alphabet, not the greek one. Therefore using the letters "Chi Rho" make sense when doing the translation into greek - since such translation is almost always done phonetically.

      --
      Mod me down and I will become more powerful than you can possibly imagine!
    10. Re:Who names these things? by nathanh · · Score: 3, Insightful
      In all seriousness, I think that poor name choices hurt the adoption of free software. Think about "Photoshop" vs. "The GIMP," or "Internet Explorer" vs. "Mozilla." Rather than something simple, descriptive, and catchy, we usually opt for indecipherable codenames, stupid recursive acronyms, or lame in-jokes that few people but the developers themselves will get.

      Oh? So Excel just says "spreadsheet" to you? How about Quark Express? Or Oracle? Or Solaris? These names are only "obvious" because you have heard them before. There is nothing descriptive about them.

    11. Re:Who names these things? by TRACK-YOUR-POSITION · · Score: 1

      Holy freaking crap! Did you just hold up "Internet Explorer" as an example of a GOOD product name? GASP!

    12. Re:Who names these things? by Anonymous Coward · · Score: 0

      Excel... cell, as in spreadsheet, but better.

    13. Re:Who names these things? by zsau · · Score: 1

      And Dreamweaver is particularly transparent? How about Windows (until you know what one is)? Excel? If you have a problem with 'The GIMP', call it 'The GNU Image Manipulation Program'. That's much more descriptive than 'Photoshop'.
      Do you buy photos from Photoshop? --That's what it sounds like to me. /. mods, please stop modding these posts up. They aren't interesting and insightful: they're repeats.

      --
      Look out!
    14. Re:Who names these things? by burns210 · · Score: 1

      maybe we should name it rename Xfree86 to windows, since X puts 'windows' on the screen. And when you hear window, don't you just automaticly think 'a rectangle on a computer monitor' rather than, say, a peice of transparent glass in a wall?

      Generic names like word, office, windows... so unimaginative...

    15. Re:Who names these things? by G-funk · · Score: 1

      There's nothing descriptive about the name Oracle for database software? Do you know what the world oracle means?

      --
      Send lawyers, guns, and money!
    16. Re:Who names these things? by FooBarWidget · · Score: 1

      So? The "ouvert" in "Xouvert" means "open" in French. So it roughly translate to "Open X". But that didn't stop all the ignorant Slashdotters who don't know French from complaining about the name either.

    17. Re:Who names these things? by nathanh · · Score: 1
      There's nothing descriptive about the name Oracle for database software? Do you know what the world oracle means?

      Yes, I know my Greek history just fine, as does everybody else who did 8th grade high school. How's things, Josh? Haven't seen you in ages.

    18. Re:Who names these things? by Anonymous Coward · · Score: 0

      This is because anything French is inherently bad.

    19. Re:Who names these things? by G-funk · · Score: 1

      Not too bad dude, just trying to find a job. Yourself? Going up to see ben and nik this week.

      --
      Send lawyers, guns, and money!
    20. Re:Who names these things? by ddilling · · Score: 1

      Wait, you mean Quark Express ISN'T a high-end scientific computing package for physics modeling???

      --
      Mahnamahna!
    21. Re:Who names these things? by ndogg · · Score: 1

      No, I think it has something to do with miniature trains or nanotech delivery or something like that.

      --
      // file: mice.h
      #include "frickin_lasers.h"
  38. Everything is coming together by smallpaul · · Score: 3, Interesting

    Over the next few years, desktop graphical environments will move increasingly towards vector graphics and away from bitmaps. The Mac is already there. Windows and Linux are both in the development stage (Longhorn and Cairo respectively) and it will be interesting to see who gets there first. Desktops will finally scale properly to different sized monitors and there will be no excuse for apps that do not scale properly.

    Once every operating system supports vectors natively, SVG will become a no-brainer. Why would we use vectors for everything on the desktop and then dumb it down to bitmaps for transmission over comparitively thin network pipes to devices of arbitrary size and shape? It would make no sense whatsoever. So SVG will replace a huge number of the GIFs and PNGs on the Web, to say nothing of Flash files.

    A wonderful side effect of this will be that people will finally be able to have richly rendered text on the Web without resorting to binary formats like GIF and Flash. Imagine being able to cut and paste text even when it is embedded in highly stylized corporate graphics (as is becoming more and more common!).

    There are really so many follow-on effects that we could have a long thread discussing them. Congratulations to the Cairo and X teams for taking a few more steps down the path!

    1. Re:Everything is coming together by inri · · Score: 1

      The Mac is not already there with vector graphics. The sexy scalable icons are raster graphics which are rescaled, not vector graphics.

      Yes, with Quartz/Display Postscript you have a vector drawing model, but you need APIs so it's actually usable.

      AFAIK, GNOME was the first desktop to have a vector theme for it -- on this, Free Software is ahead of the Mac.

    2. Re:Everything is coming together by smallpaul · · Score: 1

      Clearly nobody has the full package yet. But if you presume that Quartz/Display PDF are in the same category of component as Cairo then it is clear that the Mac is shipping with it today and it is still future development for standard Linux distros (setting aside OpenStep). But I'm not an advocate of any of the environments so I really don't care who is first as long as everyone keeps moving in the vector direction. I would like to see OSS and the Mac move ahead of Microsoft because I don't want the Microsoft APIs and vector file formats to become defacto standards just by virtue of being first. If Cairo/DPDF/SVG are widely deployed by the time LongHorn arives then Microsoft will feel some pressure to at least promise support for open standards in some timeframe.

  39. Since this thing seems to be x independent by Anonymous Coward · · Score: 0

    That leaves only one question... will there be a port of the athena widgets, there are so many apps relying of that that the port simply cannot be ignored.

    And also this thing needs network transparency just in case X is not under it dragging it down speedwise, people cannot live without network transparency even if they don't need it!!!

  40. Re:Dumb name of the month by Anonymous Coward · · Score: 0

    Why was it named Xr in the first place?

  41. Re:Go Without by Anonymous Coward · · Score: 0

    >
    Calling it eye candy? Sorry - I'll go without. Linux desktops are drab
    and unprofessional looking. They only appeal to the ultra cheap mfs
    who think they're entitled to something for nothing. I hate people
    like that. They don't do our world any good at all.
    >
    >
    You're right. It's "professional" MF's like you who are responsible for the spread of email viruses and other crap. Before assholes like *YOU* appeared on the scene, people spoke the truth when they said it was *IMPOSSIBLE* to contract a virus via email.

    Great job, *ASSHOLE*

  42. Uh oh by Anonymous Coward · · Score: 1, Interesting
    "Cairo" as a product-in-development label has a untasteful history of missed deadlines, deadends, failed architectural implementations and organizational embarassment.

    But...who knows. Maybe this Cairo won't be a wasted excursion in the desert...

  43. things slowly moving on, but still it's a monolith by maxmo74 · · Score: 1

    ...to be moved. The Xouvert project team, instead of being a "hot head" and planning to just develop something terribly different, fast, slow and maybe also very unstable or even NOT planning at all, decided that the first step has to be taken on april 2004. Gee... when I saw the very first page of Xouvert I was excited about this fork. Just a little later I found out that it's not a fork but a "development branch" therefore no question about license change (would't have been great to have it GPL finally?), that the development speed is surely nothing like I am used to (KDE, linux, mozilla...) and that the final result would be nothing more and nothing less than the same XFree we are using since a long ago. Yes, there have been improvements, surely many in the last two years, but I think many were/are waiting for something "different", even if unstable at the beginning (I had KDE crashing 10 times aday until january). A question: why is it so difficult to create a REAL fork from XFree? Making it GPL also would maybe make more developers decide to contribute. XFree could not get the changes and improvements back? Is it that bad when such a new software would be used by everyone instead of XFree? If it doesn't work out they might switch to X11/MIT license back and recontribute the (little) changes back to XFree.

  44. Watch out for the WTO! by Kakurenbo+Shogun · · Score: 1

    Better be careful--unless this stuff is getting developed in Egypt, the WTO might sue to force them to change the name.

    --
    Convert RSS to HTML - integrate webfeeds into your website
    1. Re:Watch out for the WTO! by KingRamsis · · Score: 1

      :-) ok I'm egyptian and all your sources are belong to us.

  45. Chigamma? by allanc · · Score: 0, Redundant

    The greek letters that look like XP, Chi and Rho, would be pronounced Cairo.

    But this was Xr. So shouldn't it be pronounced Chigamma?

    --AC

  46. X r == "Cairo" by musselm · · Score: 5, Informative

    Pronounce the Greek letters.

    X == Chi

    r == Rho

    Okay

    1. Re:X r == "Cairo" by sitruc37diesel · · Score: 1

      actually, the greek letter 'rho' looks like a p

    2. Re:X r == "Cairo" by DarlFromSCO · · Score: 0

      Also, sorry to bother the English speaking, but X is no pronounced Kai, but khe.

      --
      IP law confuses me. I am persuaded slashdot readers who read this sig now legally owe me 699$
    3. Re:X r == "Cairo" by scrytch · · Score: 1

      Yeah, and a capital rho looks like a P.

      XP

      Goody.

      --
      I've finally had it: until slashdot gets article moderation, I am not coming back.
  47. Not really a rename, is it? by fishbowl · · Score: 0, Redundant

    XR (or XP) can be read as "Chi Rho" ...

    --
    -fb Everything not expressly forbidden is now mandatory.
    1. Re:Not really a rename, is it? by Fnkmaster · · Score: 3, Funny
      Very interesting, I never thought of that. And IANAPOS (I am not a professor of symbology), but "chi rho" was the classical symbolic representation of the name of Christ (written in the Greek as "XP" of course, and often rendered with the P superimposed on top of and through the middle of the X). In Greek, of course, chi and rho form the first two letters of "Christos", or Christ.


      Makes you wonder what that "XP" in Windows XP and Athlong XP really stands for. A plot by the religious right to infiltrate Microsoft? Hmmm...

    2. Re:Not really a rename, is it? by arcus · · Score: 1

      Nah, it's all the Dungeons and Dragons weenies in Microsoft.

  48. Re:things slowly moving on, but still it's a monol by big-magic · · Score: 1

    Switching to GPL would solve nothing. The problem is not people hoarding code, but lack of good developers. That has nothing to do with which license it uses. It is more important that the various X11 forks use the same license so that they can freely share code (in both directions).

  49. Re:Dumb name of the month by KingRamsis · · Score: 1

    care to enlight us about whats wrong with the name "cairo" ?


    disclaimr: I'm biased.

  50. Re:things slowly moving on, but still it's a monol by Deusy · · Score: 1

    You read too much into too little.

    If you bothered to read the mailing lists, or even the three links to roadmap/goals in the article, you'd recognise that it's not that simple.

    Yes, Xouvert intends to be a development branch of XFree. No, Xouvert does not intend to be shackled by a slow adoption of new features in XFree. If XFree fails to move with the times, Xouvert will be a drop-in replacement for (and indeed coexist with) XFree.

    In fact, the goal/roadmap links suggest massive architectural changes in the code base. But that's mean of me to point that out - I mean how would you know that since you didn't bother to read it. ;)

    This way, new features get developed and there is a option for the future. I suspect that, supposing XFree do not align themselves with Xouvert as it evolves, this project will indeed become a full fork.

    --

    Free Gamer - Free games list and commentary

  51. no, servers won't be running it by SHEENmaster · · Score: 1

    but my workstation might. I'd need to still be able to tunnel X from my server to display GUI apps locally.

    --
    You can't judge a book by the way it wears its hair.
  52. What DOES (Windows) XP stand for? by The+Monster · · Score: 1
    In Greek, of course, chi and rho form the first two letters of "Christos", or Christ. Makes you wonder what that "XP" in Windows XP . . . really stands for.
    Well, I'm not a bible college professor (But my brother is, and my sister-in-law is Academic Dean) but I can read the Bible just fine. Since XP is the symbol for 'Christ' . . .
    Matthew 24:24 [KJV]: For there shall arise false Christs, and false prophets, and shall shew great signs and wonders; insomuch that, if it were possible, they shall deceive the very elect.
    There you have it. Windows XP is { an | the } Antichrist.
    --

    [100% ISO 646 Compliant]
    SVM, ERGO MONSTRO.

  53. Congratulations on re-inventing GDI by Anonymous Coward · · Score: 0

    Only 13 years after Windows 3.0

    Linux on the desktop? (* snort *)

  54. When Bill Gates Said... by Radical+Rad · · Score: 1

    "We're on the road to Cairo" he was right but his timing was just a little off.

  55. Re:So, when does this turn in to a practical produ by Jah-Wren+Ryel · · Score: 1

    I like the sound of Xr/Cairo, seems pretty cool.

    Zer-kai-roh. Sounds like an anime title to me.

    --
    When information is power, privacy is freedom.
  56. All I know is I want.. by mattr · · Score: 2, Interesting
    That awesome icon resizing wheel widget you get in SGI desktops. I've wanted one for years and years, didn't get one with BeOS, and now finally I'm gonna get one!! Hooray!!

    For anyone who has not used an SGI machine before, windows often have one or two widgets (if two then one would be oriented on the horizontal axis, the other on the vertical) which resemble long, thin, ridged wheels. When you click and drage so as to rotate the wheel showing in a file manager window the file icons will all resize automatically in realtime and smoothly, since it is all drawn in vectors. To me this would make a graphic desktop in linux a lot more useable.

    That, and the way you can use a mouse and three buttons in OpenInventor windows to navigate/manipulate in three dimensions are a couple of the best things about SGI user interfaces to my mind.

    A picture of an IRIX desktop with an icon resizing wheel is here

  57. Windows 95 by vrt3 · · Score: 1
    As other posts indicate, it's not important whether a name is or is not descriptive.

    But wasn't Cairo the codename for Windows 95 during its development?

    --
    This sig under construction. Please check back later.
    1. Re:Windows 95 by Anonymous Coward · · Score: 0

      Windows 95 was codenamed Chicago

    2. Re:Windows 95 by turpie · · Score: 1

      That was my first thought.
      Cairo was the code name for the planned object oriented rewrite of Windows, which ended up as NT5.

      I not sure if we should have too much hope in the new X guys plans to refit X, when they can't even come up with reasonable names for their projects. :)

  58. Re:Who the hell cares? by AntiOrganic · · Score: 1

    You can always use this one in the meantime.