Categories:
Wednesday, 4 February 2004
Improving Konqueror the Browser
Arendjr
|
As I downloaded KDE 3.2 RC1 some while ago and KDE 3.2.0 today, I started using Konqueror as my primary browser as it has improved immense since 3.1. Now I want to share some ideas for improving Konqueror the Browser.
Read More
Monday, 2 February 2004
fd.o redux
Aseigo
|
Holy f***ing CHRIST people! I haven't read the blogs for a while due to being simultaneously busy beyond belief and rather uninterested in anything further than 3 feet from my own naval, but I decided to take a gander at what's been up here of late and ... it's crazyness! People are spouting off about fd.o when they obviously don't know the first thing about it. Let me cluebat some of you back onto this side of the International Stupid Line (which runs straight through Elbonia and the Far Side universe, IIRC).
Read More
Monday, 2 February 2004
sleep
Aseigo
|
so i've gotten a couple hours sleep now and i'm calmer. thanks to work for waking me up; i just love fixing code over the phone. i still haven't finished the stupid "Everything that's new or changed in 3.2" page thanks to my 3.2 install being minorly screwed right now. i'll probably hijak my system at work to finish it off. anyways. i reread my last blog and boy was i in a pissy, albeit mildly humourous, mood. "cluebat you back to this side of the International Stupid Line".. hehe.. i'm such an ass. back to sleep.
Read More
Friday, 30 January 2004
fd.o disast^Wdiscussion
Daniels
|
The "nods in agreement" comment at the bottom of this post is required reading. For all of you. Go Eike.
Thursday, 29 January 2004
The freedesktop.org discussion in three simple points
Tjansen
|
I think the whole discussion can be simplified with three points that hopefully everyone can agree to:
In the next 12-24 months the only way to get a somewhat competitive desktop is to pile up code from all sources, including kde and gnome, and try to integrate them somehow If you think about the architecture of a desktop in 5-10 years, this mixture of pure C code, Gnome/Glib C code, KDE C++ code, Python, Bash scripts, maybe Mono C# code etc, all with different API conventions and wrapped by various wrapping mechanisms, all that sounds like a horrible nightmare that no one really wants Whether you like freedesktop.org or not depends on whether you want to have a usable desktop soon (thus today's desktop has a high priority for you and the future a low priority), or whether your goal is to have the best desktop at some point in the future (future: high priority, today: low priority) Make your choice.
Thursday, 29 January 2004
We need to embrace freedesktop.org
What's up with freedesktop.org? Daniel says KDE people don't care about it, Ian says we have to abandon it. I say let's embrace it and make it what it's meant to be, a common building block for all desktops, KDE, GNOME and whatever else.
Read More
Thursday, 29 January 2004
We should carefully examine specifications and code on freedesktop.org
freedesktop.org is a website. Really! It contains code and documentation. We could use some of that for KDE, if it suits us. But KDE is a volunteer effort, and we don't have to read any particular website, nor use any particular code, nor implement any particular specifications.
Read More
Wednesday, 28 January 2004
*sigh*
Daniels
|
I have only one thing to say. kde-core-devel mail: one reply - from myself, one 'good work' on IRC, one 'I don't care, go away' (hi coolo) on IRC. desktop-devel-list (GNOME) mail: seventeen replies, all up, and many 'rock on's on IRC from GNOME hackers.
That is all.
Read More
Wednesday, 28 January 2004
Making a start on XPath
Rich
|
I've started taking another look at how to best add support for XPath to KHTML. I've got a bunch of code I'm busy reexamining that lets you define an AST for XPath. It needs cleaning up but I think it is a decent first cut.
Read More
Wednesday, 28 January 2004
we need to abandon freedesktop.org
Geiseri
|
In the beginning it was a neat idea. They wanted a common set of standards for interop on the desktop... Then somehow it all went wrong, somehow implementations started to pollute these standards. This has caused quite a quandary, now somehow we have these standards that are bound to technology, some of which we could argue is pretty poor technology. IMHO this is reason to abandon efforts to follow these standards until they become standards once again, instead of implementations.
Read More