Slashdot Mirror


User: Roberto

Roberto's activity in the archive.

Stories
0
Comments
391
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 391

  1. Re:Waiting for Konquerer to fix File-menu spelling on KDE 3.2 Release Candidate 1 Debuts · · Score: 1

    Oh, right. So there's a file somewhere I can open that contains http://slashdot.org?

    Unless you are using something like FUSE, there isn't.

  2. Re:OpeneXchange Server on Novell Not Pushing Ximian Onto SuSE · · Score: 1

    If theres one thing worse than selling something that competes against your product, its giving away something that competes with your product ;-)

  3. Re:OpeneXchange Server on Novell Not Pushing Ximian Onto SuSE · · Score: 1

    Novell owns, sells, and basically earns a large chunk of its bread from GroupWise.

    Why would they opensource something that will instantly become competition for their own product???

  4. Re:Why no QT? on Novell Not Pushing Ximian Onto SuSE · · Score: 1

    My mistake. I hadnt read the previous post correctly.

  5. Re:I've said it before on Novell Not Pushing Ximian Onto SuSE · · Score: 1

    So, consider it retroactively fulfilled then! ;-)

  6. Re:I hope they do it right... on Novell Not Pushing Ximian Onto SuSE · · Score: 1

    Let me see if I understand what you say:

    The ones who write most of the software should do what the guys who make most of the money (and keep it) say, and then everyone is a winner?

    How exactly are the developers winning anything there?

  7. Re:Why no QT? on Novell Not Pushing Ximian Onto SuSE · · Score: 1

    Go to google. Type buy "photoshop album".

    You get things like this:

    http://www.amazon.co.uk/exec/obidos/ASIN/B0000D8 D1 V/202-7841639-7774221

    It seems to cost 39 UKP

  8. Re:I've said it before on Novell Not Pushing Ximian Onto SuSE · · Score: 1

    It makes more sense to see Ximian drop Red Hat, Debian, etc. support from Ximian setup tools and Red Carpet.

    After all, those services only cost money for Novell and only make money for their competition.

    That makes no sense.

  9. Re:Things will change, just not right now. on Novell Not Pushing Ximian Onto SuSE · · Score: 1

    In fact, logically, what the original article said is:

    a) Novell will not make Ximian the default interface (notice, not "will not do it soon", just will not do it)

    b) KDE will stay the default interface in the medium term

    The only logical inference possible from this is:

    a) KDE may stay as the default interface in the medium or long term

    b) KDE may not sat as the default interface in the medium or long term

    c) Ximian will not be the default interface in the medium or long term

    d) Something else may be the default interface in the medium or long term.

    Of course I know thats not what the guy meant, but its what he said ;-)

  10. Re:So does this mean... on GNOME/KDE Integration Gets A Few Boosts · · Score: 1

    a) I want to rip a track.
    b) I click on the nice "audio cd" icon
    c) I drag it
    d) Its ripped

    Sounds like ideal UI to me.

  11. Re:The fuse_kio stuff... on GNOME/KDE Integration Gets A Few Boosts · · Score: 1

    Use the fuse_kio gateway mode. Its explained in the page.

  12. Re:So does this mean... on GNOME/KDE Integration Gets A Few Boosts · · Score: 1

    You are saying that because something is easy, it causes people to do it, thus producing obviously useful stuff like audiocd: and kamera:, and thats bad?

    No, thats good. It may be bad in some twisted world where you dont want to rip your CDs and see your pictures, though.

  13. Re:Finally GNOME can get a nice file dialog! on GNOME/KDE Integration Gets A Few Boosts · · Score: 1

    Lets see if I got this right: you want the slashdot readers to explain to you why you dont like KDE?

    I have no answer to that question, but I am guessing its because you lack introspection.

  14. Re:TrollTech is setting us up just like SCO on GNOME/KDE Integration Gets A Few Boosts · · Score: 1

    If its not a great deal, dont do it.

  15. Re:Anyone else notice the "direction" of integrati on GNOME/KDE Integration Gets A Few Boosts · · Score: 1

    Well, you could say kdevelop - anjuta, except you would have to say kdevelop is beter ;-)

    BTW: kwrite is not a word processor.

  16. Re:License? on GNOME/KDE Integration Gets A Few Boosts · · Score: 1

    If its not distribute, just use Qt under the GPL.

  17. Re:The fuse_kio stuff... on GNOME/KDE Integration Gets A Few Boosts · · Score: 1

    Uh... fuse_kio is integrated with the fs.

    You just mount it and use it.

  18. Re:Just a style on Unifying GTK & QT Theme Engines · · Score: 1

    Darling, come back when you learn to read, too!

    As I said, I *asked* where it was used, and *other people* who are GNOME users came back with a rather poor list.

    A poor list that you, beyond saying bonobo components are used all over the place, have done nothing to extend.

    If your point was really to correct my "FUD", you could do it by just posting a nice list.

    However, you seem to find entertainment on insulting people on threads noone else reads, while hiding behind the veil of your anonymous coward features.

    That is, in my humble opinion, sign of some strange inclinations. Perhaps you are of a too masturbatory nature. Maybe you lack fiber in your diet.

  19. Re:Just a style on Unifying GTK & QT Theme Engines · · Score: 1

    Dear, when I said "their users" I didn't mean me, I meant the OTHER guys, the ones that use GNOME, that said it was used in evolution and that there were "a few" apps that worked as components.

    And just a small question. You actually bother checking this page every day to answer me? At least I get email notification!

    You must have serious issues to act like you do. I suggest you seek professional help.

  20. Re:Just a style on Unifying GTK & QT Theme Engines · · Score: 1

    I mean, they mention very little usage. Now you say its used all over the place. Whatever.

    If you are right and its a widely used technology, then they are not doing enough to educate their own users.

    The rest of your message is too stupid to answer to.

  21. Re:Just a style on Unifying GTK & QT Theme Engines · · Score: 1

    Well, apparently, the GNOME users in this forum can only mention Evolution as a container and Abiword and Gnumeric as components.

    Doesn't look like much. If there is more, they should publicize it. It's part of developing a platform.

    You act as if saying "hey, we have components and we use them all over the place" is bad. It isn't. It's good.

    If GNOME has components and uses them all over the place, GNOME should emphasize it, and spread the gospel.

    As for thwe rest, dude, I won't bother dropping to your level. I had read that in a place I usually trust to have decent GNOME information (sorry, can't say the source). I was wrong? Good for GNOME, then.

  22. Re:Just a style on Unifying GTK & QT Theme Engines · · Score: 1

    Well, KDE seems to use the components a lot more. Perhaps thats why they speak about it more.

    It is hard to brag about something that is not happening.

    Besides, I just asked about it being dropped because I had heard something about it. No biggie.

  23. Re:Just a style on Unifying GTK & QT Theme Engines · · Score: 1

    They are intertesting as long as they are accepted as what they are. But not too good to generalize from them.

  24. Re:Just a style on Unifying GTK & QT Theme Engines · · Score: 1

    Well, I wrote the RSS agg. because I wanted it, and trust me, having the browser in it is better.

    It was even one of the most requested features for NNW, the most popular app of its kind on OSX.

    Your opinion of the gratuitousness is really not too interesting because you (as myself) are probably so many standard deviations outside of the normal use cases.

  25. Re:Just a style on Unifying GTK & QT Theme Engines · · Score: 1

    You seem to be confused.

    That sort of component is not what those libraries "reused by GNOME and KDE" are.

    Although it is possible to write a component model based on shared libraries (like, say, KParts ;-), GNOMEs component model is based on CORBA, and it seems to be really losing emphasis nowadays.

    It is strange because there was a lot of GNOME flamage about how KDEs approach was so inferior and antiquated (CORBA is the future, remember? it will always be ;-), yet KDEs component framework
    is the successful one, go figure!