The bug wasn't fixed earlier because: 1) it's like it is the only open bug report, you know... this is just one bug, which happens only with advanced usage, 2) the bug was default-assigned to someone who left the project since, so the people who could actually fix the bug (e.g. me) didn't see it.
Typical slashdot: the article distorts the truth in order to get reactions.
It was pretty clear during that presentation that the goal was to make it possible to still run X applications -- using a rootless X server -- and that this would also allow X-over-the-network use cases. X11 is not going away, the idea is to use Wayland -and- X.
OpenDocument Alliance is not the OASIS Technical Committee. It has no say whatsoever on the contents of the OpenDocument specification, it is merely "big companies getting together to promote OpenDocument".
Re:I know you're kidding, but....
on
Undelete In Linux
·
· Score: 3, Informative
> Easy to use Windows filesharing is clicking on a button that > says share files and seeing that folder show up in Network > Neighborhood. Like one can do in Konqueror-3.1 (and in Mandrake-9.0's Konqueror) ?
1) IMHO it's the responsibility of a journalist to check for facts before "forwarding" a story. The lack of doing so is how so many wrong stories appear everywhere. It's just too easy: as soon as one person says nonsense somewhere, all "news" sites pick it up... That's not journalism, that's "spreading rumours".
It's especially frustrating for those who "know the truth", to see that we don't even have time to get the initial website corrected, all the other news sites make news out of it immediately.
2) The article on theRegister does not say "KDE is adopting mono" like the/. headline said. It felt like this was being said behind the lines, the the headline on/. is really amplifying this wrong 'fact'.
Ah, so the interview was done over the phone and you had no way to check the printed version before it went online? That's very bad IMHO, they should check with the person interviewed first. That's how misunderstandings happen - such as this one.
The article was already very misleading IMHO, the slashdot headline even more so. I think many more statements should have been corrected in that article...
Well, thanks for the work on the language bindings, keep it up. David Faure.
The Qt-C# / KDE-C# developer might be proud of his language bindings (undoubtly it's cool that those exist), but that's no reason to spread such wrong rumours. (I'm not accusing him, it could very well be the journalist from TheRegister who's making most of this up).
There is NO decision from the KDE project to do ANYTHING with C#,.NET or Mono at this point.
Apply this patch to the KDE 3 sources (current CVS, or 3.0-final when it's out). It's a tiny bit late for inclusion in 3.0, given the size of the patch (which mainly moves code around though). Feel free to test and report problems to me:)
Re:KParts won't dominate
on
Coding with KParts
·
· Score: 3, Interesting
The goal of KParts is certainly not to dominate, but to do the job well in KDE. Without KParts there would be no embedding in Konqueror nor KOffice (etc.), no GUI merging etc. There's nothing in KParts that attempts to dominate the world - nor even other component models. Why would there be ?
KParts itself won't dominate. However, if KDE ever dominates, then KParts will by association dominate too;)
> What about Unicode support? GNOME 2, based on the new GTK+ will supposedly support Unicode all over the place. Is this true with KDE 3/Qt 3 also?
Definitely. Already KDE2/Qt2 uses Unicode everywhere internally.
KDE3/Qt3 do this even more, removing the need for applications to worry about font charsets, and offering support for bi-directional editing of text.
Try it out !
Javascript is the ONE thing that will have really improved between KDE 2.2 and KDE 3.0, if I had to name only one.
Please try KDE 3.0 beta1, retest those Javascript sites, and I can assure you that you'll be surprised.
It's not all bugfree yet, but it's much much better than what was there before. I see those JS popupmenus in many websites, where they wouldn't appear before.
I haven't completely cleaned up the KJS buglist yet - that takes time, even just testing - but we're almost there now;)
See also the other posts on how to prevent one crash from taking down all your browser windows.
Tabbed browsing: that will come right after 3.0, stay tuned;)
Open the "Letter" template, and then do "File / Create Template" from document, and overwrite the
"Plain Text" template.
That's the template that is used when starting kword with the "empty document" radiobutton.
You'll find Mandrake packages on ftp.kde.org and mirrors, with the other packages.
Re:Good grief!
on
KDE 2.2.2
·
· Score: 2, Informative
Simply skipping the "guessing the image format" code of QImage::QImage(), passing the name of the image format, since we know it from the icon's filename extension.
Nothing spectacular, sorry.
The rest of the fixes are much more important IMHO, dunno why everyone's picking on that one.
Re:Icons load 5% faster
on
KDE 2.2.2
·
· Score: 2, Interesting
Can't get excited ? Don't, that wasn't the purpose. I agree that the announcement here was a bit exxagerating about that change. But have a look at the icon loading code, and try to make it faster than that, then we'll talk.
How come everyone seems to think that developers make thing slow _on purpose_ ? When we find a way to make things faster, we do, even if the result is only a 5% difference. Small steps, but they accumulate. Would you prefer that we don't fix the things we find ?
David,
actually happy about his icon loading fix....
and disappointed everytime he reads Slashdot, by this habit of criticizing really _everything_.
PS: note that the announcement could have said "icon-loading speedup" and nothing else. You could at least appreciate that someone took the time to measure the actual speedup even if the result isn't huge.
No, there was a bug in the HTML of the official announcement (PHP footer missing), and Netscape choked on the resulting HTML, but Konqueror parsed it alright. Another good point for Konqueror, if you ask me;)
Anyway, the official announcement is fixed now, it shows up in Netscape too.
Pricing ?? Qt is free - just try it.
You can develop free software with it, for free.
Of course if you want to develop closed-source
commercial software it's another story, but if you want to "try this out" then just go ahead and download it.
"GNOME/Mozilla will take place. Because their architecture is far better." You just read that somewhere and repeat it even though you have no idea what you're talking about, right ? KDE's architecture is much better, but of course it takes looking into both to know that.
Slashdot Mirror
Typical slashdot over-reaction ;)
The bug wasn't fixed earlier because:
1) it's like it is the only open bug report, you know... this is just one bug, which happens only with advanced usage,
2) the bug was default-assigned to someone who left the project since, so the people who could actually fix the bug (e.g. me) didn't see it.
It took me a full day of very intense and complex debugging to fix this.
Typical slashdot: the article distorts the truth in order to get reactions.
It was pretty clear during that presentation that the goal was to make it possible to still run X applications -- using a rootless X server -- and that this would also allow X-over-the-network use cases.
X11 is not going away, the idea is to use Wayland -and- X.
OpenDocument Alliance is not the OASIS Technical Committee. It has no say whatsoever on the contents of the OpenDocument specification, it is merely "big companies getting together to promote OpenDocument".
KHTML is LGPL indeed.
> Easy to use Windows filesharing is clicking on a button that
> says share files and seeing that folder show up in Network
> Neighborhood.
Like one can do in Konqueror-3.1 (and in Mandrake-9.0's Konqueror) ?
Yes, that box can get a checkmark now.
David.
1) IMHO it's the responsibility of a journalist to check for facts before "forwarding" a story. The lack of doing so is how so many wrong stories appear everywhere. It's just too easy: as soon as one person says nonsense somewhere, all "news" sites pick it up... That's not journalism, that's "spreading rumours".
/. headline said. It felt like this was being said behind the lines, the the headline on /. is really amplifying this wrong 'fact'.
It's especially frustrating for those who "know the truth", to see that we don't even have time to get the initial website corrected, all the other news sites make news out of it immediately.
2) The article on theRegister does not say "KDE is adopting mono" like the
Ah, so the interview was done over the phone and you had no way to check the printed version before it went online? That's very bad IMHO, they should check with the person interviewed first. That's how misunderstandings happen - such as this one.
The article was already very misleading IMHO, the slashdot headline even more so. I think many more statements should have been corrected in that article...
Well, thanks for the work on the language bindings, keep it up.
David Faure.
> KDE and Gnome have conspired together to merge their underlying implementations
Don't worry, they haven't.
Don't believe everything you read.
When, oh when will journalists *check* for facts first?
What a load of mis-information....
.NET or Mono at this point.
The Qt-C# / KDE-C# developer might be proud of his language bindings (undoubtly it's cool that those exist), but that's no reason to spread such wrong rumours. (I'm not accusing him, it could very well be the journalist from TheRegister who's making most of this up).
There is NO decision from the KDE project to do ANYTHING with C#,
It's amazing how much bullshit people can invent.
David, KDE/KOffice developer.
> AFAIK in KDE 2.2 you cannot simply drag and drop to the "floppy device" icon in the desktop.
;)
:)
Just implemented this yesterday... quite a concidence
konq_operations.diff
Apply this patch to the KDE 3 sources (current CVS, or 3.0-final
when it's out). It's a tiny bit late for inclusion in 3.0, given the size of the patch (which mainly moves code around though).
Feel free to test and report problems to me
The goal of KParts is certainly not to dominate, but to do the job well in KDE. Without KParts there would be no embedding in Konqueror nor KOffice (etc.), no GUI merging etc.
;)
There's nothing in KParts that attempts to dominate the world - nor even other component models. Why would there be ?
KParts itself won't dominate. However, if KDE ever dominates, then KParts will by association dominate too
David (co-designer of KParts).
> What about Unicode support? GNOME 2, based on the new GTK+ will supposedly support Unicode all over the place. Is this true with KDE 3/Qt 3 also?
Definitely. Already KDE2/Qt2 uses Unicode everywhere internally.
KDE3/Qt3 do this even more, removing the need for applications to worry about font charsets, and offering support for bi-directional editing of text.
Try it out !
Javascript is the ONE thing that will have really improved between KDE 2.2 and KDE 3.0, if I had to name only one. ;)
;)
Please try KDE 3.0 beta1, retest those Javascript sites, and I can assure you that you'll be surprised.
It's not all bugfree yet, but it's much much better than what was there before. I see those JS popupmenus in many websites, where they wouldn't appear before.
I haven't completely cleaned up the KJS buglist yet - that takes time, even just testing - but we're almost there now
See also the other posts on how to prevent one crash from taking down all your browser windows.
Tabbed browsing: that will come right after 3.0, stay tuned
See also the option in Konqueror's configure dialog, which offers several choices for this behaviour.
Open the "Letter" template, and then do "File / Create Template" from document, and overwrite the
"Plain Text" template.
That's the template that is used when starting kword with the "empty document" radiobutton.
Sounds like the QClipboard bugs (still partly unsolved) - try killing klipper.
You'll find Mandrake packages on ftp.kde.org and mirrors, with the other packages.
Simply skipping the "guessing the image format" code of QImage::QImage(), passing the name of the image format, since we know it from the icon's filename extension.
Nothing spectacular, sorry.
The rest of the fixes are much more important IMHO, dunno why everyone's picking on that one.
Can't get excited ? Don't, that wasn't the purpose. I agree that the announcement here was a bit exxagerating about that change. But have a look at the icon loading code, and try to make it faster than that, then we'll talk.
How come everyone seems to think that developers make thing slow _on purpose_ ? When we find a way to make things faster, we do, even if the result is only a 5% difference. Small steps, but they accumulate. Would you prefer that we don't fix the things we find ?
David,
actually happy about his icon loading fix....
and disappointed everytime he reads Slashdot, by this habit of criticizing really _everything_.
PS: note that the announcement could have said "icon-loading speedup" and nothing else. You could at least appreciate that someone took the time to measure the actual speedup even if the result isn't huge.
No, there was a bug in the HTML of the official announcement (PHP footer missing), and Netscape choked on the resulting HTML, but Konqueror parsed it alright. Another good point for Konqueror, if you ask me ;)
Anyway, the official announcement is fixed now, it shows up in Netscape too.
Of course if you want to develop closed-source commercial software it's another story, but if you want to "try this out" then just go ahead and download it.
No, the point is that http://ftp.kde.org automatically redirects to a mirror, most often sourceforge... which hasn't updated yet :(
:)
Be patient (I didn't think it would take so much time to get there
Not much. See details here.
"GNOME/Mozilla will take place. Because their architecture is far better."
You just read that somewhere and repeat it even though you have no idea what you're talking about, right ?
KDE's architecture is much better, but of course it takes looking into both to know that.