sorry to disappoint, that wasn't me. the GP is correct, though, in identifying most of the negative feedback for Gnome 3 as the result of hypocritical hipsters - so it's understandable that you might be confused.
you don't know me, son, so let me explain this to you once: If I ever bitchslap you, you'll be using an AC post. I'll be using my account. and I'll still bitchslap you so hard, your mom will feel it (just like she did last night).
the burden of proof befalls on you, my dear; and you have no proof that the name was chosen intentionally. but obviously this is the internet, where random muppets like you can make up stuff and ask others to prove it false. guess what, I can also say that your mom was pleasuring me the other night.
Also, the way you speak to people online needs to change -unless you really are 14 years old. You wouldn't make your ditch comment to me in person (without my hand print on your cheek as a thank you) so don't do it online either.
don't be so sure about that: the argument cuts both ways - and if your first thought was a slap on the cheek then I'm pretty sure I'd find you seething and looking at my feet while whimpering about my harsh words. now get lost, nerd.
it actually turns out that the KDE system settings shell is *always* shown (regardless if your using Gnome, XFCE, LXDE or whatever), and the maintainer did not accept the "OnlyShowIn" tag fix: https://git.reviewboard.kde.org/r/102038/ - the Gnome system setting shell correctly sets the "OnlyShowIn" tag, so that it is only shown under Gnome (or Unity). and yet Gnome gets bashed because the gnome-control-center maintainer decided to give a more descriptive name for something that, unlike in Gnome 2.x, will appear as a launcher. the power of the FLOSS community: eating their children since 1991.
a) I didn't sign the code of conduct; b) the code of conduct applies to gnome resources and conversations with humans, as opposed to muppets like yourself; c) Olav is a gnome sysadmin; d) I can probably find a big enough bucket full of cocks for you to choke on as well, my dear AC.
it was not intentional.
turns out that there are not many ways to give a generic and yet descriptive name for the user-facing shell for settings that involve the system.
the binary name, and everything else, has a different name. it's just the user-facing name that it's the same - and it only collides if you install and use both KDE and Gnome at the same time.
so, if I provide you a ditch big enough, will you be so kind and go die in it? thanks.
the commit was made in December last year; it's in EoG 3.0. I doubt it was backported to the 2.x series, and I'm pretty sure it won't be backported to version 2.23.0, which was the first release in the 2.23 development cycle - which happened 2 and a half years ago.
Is that the "open source way"? Or are you not fixing a bug that scores of users have taken the trouble to report over three years out of laziness, or is it some kind of nerd pride? What must we go, oh master?
nobody pays anybody to work full time on the whole of GNOME; it's a volunteer effort, through and through. this is also true of a lot of other open source projects.
if no developer is working on your pet bug you have two choices: a) learn the ropes and fix it yourself or b) convince a developer (with money, if necessary) that your pet bug is important and that he or she should work on it for you.
otherwise you have misunderstood how open source works, and you don't get to complain.
I'd feel more amenable to the GNOME developers plight if they'd give some attention to some of the three-plus year old bugs that don't seem to get any attention. Some of the bugs aren't serious, but they're so simple and yet so annoying you'd figure someone would have fixed them years ago.
and I'd feel more amenable about closing "simple" bugs if you provided patches for them instead of moaning and bitching about them on/.
if you provided a patch and didn't stick around to actually have it committed then you're not doing open source development right either, by the way.
Clutter is an open source project that has been around since 2005, and "marketing morons" have nothing to do with its name. and since it's an API to create applications, toolkits and desktop environment, then you won't have Clutter on your desktop, but your desktop will use Clutter internally.
What I am curious about is the processors in some of the PocketPC handhelds like the Axim are pretty powerful. Why didn't they go for similar hardware specs in the first place with the 770? With those, they might have been able to get embedded Qt instead of Gtk.
and that (choosing qt over gtk+), pray tell, what would have accomplished? I'm not aware of benchmarks showing incredibly blazing speeds of qt over gtk+ on the embedded platform.
by the way: don't try the "gtk+ is slow because of cairo": the 770 uses a cairo-less version of gtk+.
post hoc ergo propter hoc - before that therefore because of that. sorry, but this seldom is the truth.
also what is more likely: that microsoft wanted to crush a still pre-release quality product or that novell shifted money (a resource not overabundant for them, these days) and developers from a perceivedly failing project (which is replicating what already exists in various forms)?
GNOME did invert some years ago the order of the buttons on right-to-left languages, following the example of the Apple UI, and uses verbs instead of the infamous YNC combo; so, no: "linux" does not do like windows.
and just to be overly zealous: windows vista added message boxes with verbs+descriptions, so neither does newer releases of windows do like the old times (finally).
And this would be cheaper than rockets that send satellites into orbit now?
as the elevator would stay exactly where it is and as the elevator robot would be reused, it is obviously cheaper on the long run. right now, sending a kg worth of stuff in space costs ~1000 USD; a space elevator would bring down the cost to 10 USD/kg.
and I won't even mention the secondary gains obtaining when developing a space elevator, in terms of technology and manufacturing breakthroughs.
A 100 meter test
the 100 meters test followed a 1.6 km test, so it's more like 59.999 more miles to go.
folding support is planned for the 2.15/2.16 release cycle; Gedit code base was refactored during this cycle and the developers' attention was reserved to fixing bugs, improving performances and revamping the plugin system. support for folding is in an unstable branch, ATM.
also, since the editor widget used by Gedit is placed into a shared library (gtksourceview) a bunch of other projects will have folding support as soon as it gets included.
Okay, d.g.o is still a pain to use and still has some old stuff, but the API reference should qualify as "good documentation". GNOME core libraries are basically all documented - except libgnomeprint/libgnomeprintui, which have large gaps - and if you don't find enough documentation, Just. File. A. Bug..
The interesting bit is that, thanks to the Maemo project, Nokia is gving back to the community some of the changes made to the GTK libraries - namely, the stylus mode and other issues that emerged during development of the Hildon platform library.
Yes, as Mandriva pays attention to both KDE and Gnome. Thus, Gnome applications don't look extremely alien in KDE. And KDE apps do not look just from another planet in KDE.
Thus making Mandrake/Mandriva a "desktop-wars neutral" distribution, and not a KDE-centric one, as far as I can see.
Perl works great, although it is not the fastest language around. But then, Perl+GTK integration looks nice and works well.
I certainly hope so, since I've helped creating those bindings.;-)
Are you aware, yes, that all the software tools used by Mandrake before, and by Mandriva now, are written in Perl using the fine Gtk2 Perl bindings for the GTK library?
Slashdot Mirror
this.
oh, if I had mod points.
kudos, dude.
sorry to disappoint, that wasn't me. the GP is correct, though, in identifying most of the negative feedback for Gnome 3 as the result of hypocritical hipsters - so it's understandable that you might be confused.
you don't know me, son, so let me explain this to you once: If I ever bitchslap you, you'll be using an AC post. I'll be using my account. and I'll still bitchslap you so hard, your mom will feel it (just like she did last night).
Liar.
the burden of proof befalls on you, my dear; and you have no proof that the name was chosen intentionally. but obviously this is the internet, where random muppets like you can make up stuff and ask others to prove it false. guess what, I can also say that your mom was pleasuring me the other night.
Also, the way you speak to people online needs to change -unless you really are 14 years old. You wouldn't make your ditch comment to me in person (without my hand print on your cheek as a thank you) so don't do it online either.
don't be so sure about that: the argument cuts both ways - and if your first thought was a slap on the cheek then I'm pretty sure I'd find you seething and looking at my feet while whimpering about my harsh words. now get lost, nerd.
it actually turns out that the KDE system settings shell is *always* shown (regardless if your using Gnome, XFCE, LXDE or whatever), and the maintainer did not accept the "OnlyShowIn" tag fix: https://git.reviewboard.kde.org/r/102038/ - the Gnome system setting shell correctly sets the "OnlyShowIn" tag, so that it is only shown under Gnome (or Unity). and yet Gnome gets bashed because the gnome-control-center maintainer decided to give a more descriptive name for something that, unlike in Gnome 2.x, will appear as a launcher. the power of the FLOSS community: eating their children since 1991.
a) I didn't sign the code of conduct; b) the code of conduct applies to gnome resources and conversations with humans, as opposed to muppets like yourself; c) Olav is a gnome sysadmin; d) I can probably find a big enough bucket full of cocks for you to choke on as well, my dear AC.
it was not intentional. turns out that there are not many ways to give a generic and yet descriptive name for the user-facing shell for settings that involve the system. the binary name, and everything else, has a different name. it's just the user-facing name that it's the same - and it only collides if you install and use both KDE and Gnome at the same time. so, if I provide you a ditch big enough, will you be so kind and go die in it? thanks.
the commit was made in December last year; it's in EoG 3.0. I doubt it was backported to the 2.x series, and I'm pretty sure it won't be backported to version 2.23.0, which was the first release in the 2.23 development cycle - which happened 2 and a half years ago.
the code contributed is still present in the current version of EoG, major version bump notwithstanding.
Is that the "open source way"? Or are you not fixing a bug that scores of users have taken the trouble to report over three years out of laziness, or is it some kind of nerd pride? What must we go, oh master?
nobody pays anybody to work full time on the whole of GNOME; it's a volunteer effort, through and through. this is also true of a lot of other open source projects.
if no developer is working on your pet bug you have two choices: a) learn the ropes and fix it yourself or b) convince a developer (with money, if necessary) that your pet bug is important and that he or she should work on it for you.
otherwise you have misunderstood how open source works, and you don't get to complain.
I'd feel more amenable to the GNOME developers plight if they'd give some attention to some of the three-plus year old bugs that don't seem to get any attention. Some of the bugs aren't serious, but they're so simple and yet so annoying you'd figure someone would have fixed them years ago.
and I'd feel more amenable about closing "simple" bugs if you provided patches for them instead of moaning and bitching about them on /.
if you provided a patch and didn't stick around to actually have it committed then you're not doing open source development right either, by the way.
Clutter is an open source project that has been around since 2005, and "marketing morons" have nothing to do with its name. and since it's an API to create applications, toolkits and desktop environment, then you won't have Clutter on your desktop, but your desktop will use Clutter internally.
oooh, it was a pun on the name! now, I get it.
They're revamping their whole product line with names like this.
New speech synthesis software: Mutter
actually, the fork of the Metacity window manager using Clutter to handle the scenegraph is called Mutter
a video? like, I don't know, this one? :-)
the Moblin 2.0 UI for netbooks is probably the best showcase of what Clutter can do.
that's "Perl for Hopeless Programmers".
and that (choosing qt over gtk+), pray tell, what would have accomplished? I'm not aware of benchmarks showing incredibly blazing speeds of qt over gtk+ on the embedded platform.
by the way: don't try the "gtk+ is slow because of cairo": the 770 uses a cairo-less version of gtk+.
post hoc ergo propter hoc - before that therefore because of that. sorry, but this seldom is the truth. also what is more likely: that microsoft wanted to crush a still pre-release quality product or that novell shifted money (a resource not overabundant for them, these days) and developers from a perceivedly failing project (which is replicating what already exists in various forms)?
GNOME did invert some years ago the order of the buttons on right-to-left languages, following the example of the Apple UI, and uses verbs instead of the infamous YNC combo; so, no: "linux" does not do like windows.
and just to be overly zealous: windows vista added message boxes with verbs+descriptions, so neither does newer releases of windows do like the old times (finally).
hookers and beer!
in fact, forget the beer! ah, screw the whole thing!
And this would be cheaper than rockets that send satellites into orbit now?
as the elevator would stay exactly where it is and as the elevator robot would be reused, it is obviously cheaper on the long run. right now, sending a kg worth of stuff in space costs ~1000 USD; a space elevator would bring down the cost to 10 USD/kg.
and I won't even mention the secondary gains obtaining when developing a space elevator, in terms of technology and manufacturing breakthroughs.
A 100 meter test
the 100 meters test followed a 1.6 km test, so it's more like 59.999 more miles to go.
folding support is planned for the 2.15/2.16 release cycle; Gedit code base was refactored during this cycle and the developers' attention was reserved to fixing bugs, improving performances and revamping the plugin system. support for folding is in an unstable branch, ATM.
also, since the editor widget used by Gedit is placed into a shared library (gtksourceview) a bunch of other projects will have folding support as soon as it gets included.
Since it's Italian, it's capice.
It's capisce, third person (singular) of the verb capire (to understand) with the imperative form in a question (capisce, lei? == do you understand?).
It's pronounced in english as ka-pee-sh, but in italian the final e is not muted, so it's pronounced like ka-pee-sh-e.
Okay, d.g.o is still a pain to use and still has some old stuff, but the API reference should qualify as "good documentation". GNOME core libraries are basically all documented - except libgnomeprint/libgnomeprintui, which have large gaps - and if you don't find enough documentation, Just. File. A. Bug..
The interesting bit is that, thanks to the Maemo project, Nokia is gving back to the community some of the changes made to the GTK libraries - namely, the stylus mode and other issues that emerged during development of the Hildon platform library.
Yes, as Mandriva pays attention to both KDE and Gnome. Thus, Gnome applications don't look extremely alien in KDE. And KDE apps do not look just from another planet in KDE.
Thus making Mandrake/Mandriva a "desktop-wars neutral" distribution, and not a KDE-centric one, as far as I can see.
Perl works great, although it is not the fastest language around. But then, Perl+GTK integration looks nice and works well.
I certainly hope so, since I've helped creating those bindings. ;-)
Are you aware, yes, that all the software tools used by Mandrake before, and by Mandriva now, are written in Perl using the fine Gtk2 Perl bindings for the GTK library?