PyKDE
It seems to work well, even if it doesn't expose ALL the KDE 3.1 API, and it should be useful as a stopgap until the authors release the real thing.
You can see a screenshot of it here
It seems to work well, even if it doesn't expose ALL the KDE 3.1 API, and it should be useful as a stopgap until the authors release the real thing.
You can see a screenshot of it here
Not only can you now reach this humble weblog through ggl:lateral+opinion (if you are using KDE, of course), but a look at my referrers show that the follwing google searches have gotten the searcher here:
d-bus havoc (reasonable, I wrote about it) kde vs gnome (reasonable, the words are here)
kfte
Ok, I wrote kfte. But I never mentioned it here. I wonder how that worked?
Well, just because I want to use KHTML in KRsN, I got the latest PyKDE. It says it is for KDE up to 3.0.3 ...
Well, with very minimal hacking (deleting two lines in KFontDialog's sip file) and a couple of shoves at the build.py, it seems to be compiling allright on KDE 3.1.
Oh, sure, it won't expose the new pieces of API in KDE 3.1, but who cares? It will work. I suppose I will post it somewhere as soon as it does.
After some network hiccups (48 hour long hiccups, too), I have Internet at home again.
Man, am I pissed at the dumbasses who run velocom.com.ar :-P
SCO is becoming Intergraph.
For those who don't know it, Intergraph was once a workstation maker.Last year they had 10M in business income. And 385M in lawsuit income.
Basically the company sits in a few patents, does nothing, and milks everyone else (not that it's illegal to do so).
And why I say SCO is becoming intergraph?
Let's look at the possible income sources for SCO, shall we?
SCO OpenServer and UnixWARE: pretty much just upgrading old servers. That is not going to pay for R&D for new versions, and then this dries up, because no new version == no upgrades == no income. Unless of course, this gets subsidies from somewhere else.
Caldera Linux == If this suit killed something, this is what got whacked
Licensing of IP, either friendly or forceful a.k.a the Intergraph path
There is no d!
And about c)... who is going to license the UNIX stuff from SCO anymore? This suit means if you do it, you can NEVER AGAIN develop a unix system or a linux system, or SCO will sue your ass. To do that to get a technology that is not too much better than FreeBSD... it makes no sense. Specially considering there will be no R&D on it anymore (see a).
The only ones with UNIX licenses wil be those who got them from AT&T, and they don't pay a dime to SCO. BTW: this basically means Sun, since HP-UX and IRIX and the rest is on their death bed anyway (and AIX... well, just think about it ;-).
So c), the only visible income source for SCO becomes "We will sue people, and live on what we get out of settlements".
Because SCO can't even do a GOOD Intergraph and actually win the lawsuits. Not this one, and not against IBM, at least, and they don't have a good patent portfolio!
Tu put it another way, SCO will become a bully that will try to look impressive and steal milk money from smaller companies. That is, they will, if IBM lets them.
If IBM caves in and settles, SCO will look impressive enough for this to work. Which is why I hope IBM beats the crap out of them, just to make SCO have to work to earn an honest buck.