On Sat, 29 Sep 2007, Ken Mays wrote: > P.S. I was going to fully update KDE 3.5.7 over at Blastwave, but with > KDE 4.0 only two months away it seemed we should move everything to KDE > 4.0 support.
That's exactly what we were saying here a few months ago. Stefan has got KDE to agree to take changes for Solaris/OpenSolaris, but those changes will only be taken upstream if they go into 4, so there is really no sense in wasting time on 3.x.x, since even if that stuff does get done, the changes won't be taken upstream. I see this as a key point Ken, since we really don't want to be in a situation where we need to keep layering changes on top of what KDE distributes. Personally, I don't see any point in using gcc, if we would end up with ABI incompatibilities, which it seems we would. Although I know there's work to be done to get Studio working with the 4.x codebase, but in the end it seems it will be worth it. Interesting to note that the Indiana project stated that KDE is not of concern to them, and they will focus on GNOME. I really see it to all of OpenSolaris' advantage to have as many desktops as possible. That and I do use KDE as my desktop...:-/ Last weekend I was looking at libraw1394 which is needed for much of the multimedia stuff, mpeg4ip and some other video components. Those are really the cool features of KDE 4, IMO, and when we see cool screen shots, those are some of the really snazzy eye candy... I'm not sure if you were following the discussion on BOOST and getting Studio to compile it, but in the past week I saw a message from a RougeWave guy mentioning they had a fix to compile boost...I wasn't clear if that is the same stuff in Studio or what, and if so, that would be good if we could expect to have Studio support without using the Apache code. The Apache code seems like it would work, Stefan had the BOOST stuff compiled and tested with another piece of code, as I recall. Maybe Stefan will comment when he sees this thread. -- Alan DuBoff - Solaris x86 IHV/OEM Group
