Slashdot Mirror
GUADEC Reports
Havoc Pennington writes: "Some reports from the GNOME Users and Developers Conference are coming in; see one on the O'Reilly site and in the weekly GNOME Development Summary." Sounds like some good stuff was accomplished -- a GNOME Steering Committee, work towards 2.0, and setting up a non-profit among other things.
GNOME is building strongly on Bonobo -as you might have seen from Chuck's description of the trip- all new apps use it: Gnumeric, Evolution, Nautilus and various apps are being rewritten with it: the panel and the control center.
Bonobo and CORBA are pretty nice. I invite you to read over the white paper we have (either at developer.gnome.org, or at www.helixcode.com) that describe Bonobo.
Best wishes
Miguel.
... is here.
One, fvwm is a window manager, gnome is something else. Are you sure you are current, for example, Red Hat 6.1 seems badly out of date, my Krud Feb 2000 (Red Hat 6.1 with curent versions of everything www.tummy.com/krud/ $55 for a cd a month for a year) system is MUCH better.
Yeah, they need a really stable benchmark release to get out there, but I think they are closer than you think.
I'm not sure what you mean by feature poor, give us some examples.
Plato seems wrong to me today
More costly, but so much simpler to implement and to interface, and so much independent of the medium. The main problem with complex systems like Corba and such, is that most developpers (esp. the code drones in closed source software companies) don't read the specs, RFC, etc. They copy and paste some code, or look at the file, et voila. That works. Some times. Take for example SMTP. It's simple. It's been here for ages. Yet there's a significant portion of the MUA and MTA which don't respect it fully. XML, on the other, being human readable and having some built-in checks, will make interoparability easier.
Isn't KDE moving towards XMLRPC?
As far as stability, I'm a bit confused. Have you tried the latest October Gnome builds? I have found them to be extraordinarily stable. The builds that shipped with RH 6.0 were pretty poor, and the ones that shipped with 6.1 were a drastic improvement but still left something to be desired in terms of stability. October Gnome, however, is very solid.
The latest 1.1.X (Helix, etc...) include many more features, but still need to be hammered on a bit more...that's why they're labeled "BETA." I expect that the April Gnome release will come a long way towards smashing these stability bugs.
----
Celebrate the finer things in life
The latest, stable release of GNOME, the October release, is very stable. I haven't had it crash on me once. I've been using GNOME since the 0.33 days, when it used to crash every couple days, if not every day...
----------
In a real emergency, we would have all fled in terror, and you would not have been notified.
No, Qt 2.x is not backwardly compatible to 1.x. But they have managed to achieve a level of backwards compatibility that is still very good. All of the 2.x releases will work together. The 2.1 beta is out and it works just fine with 2.0. No recompiles necessary.
Compare this to the Windows world where every program comes with yet another copy of the MFC, VB or DX runtimes because the compatibility gets lost from month to month.
A Government Is a Body of People, Usually Notably Ungoverned
In other news, Miguel and I [Havoc] presented the new development roadmap; the steering committee will be fleshing out some of the details and monitoring progress[.]
Actually, if this project really demands a committee (and how else would they get the various companies to cooperate?...), this is the way to do it -- have the design declared by one or two people, and have the committee apportion the gritty-details work and make sure it goes according to schedule. We all know about how the camel is said to be a horse designed by committee, and I'd hate to see what a committee could come up with in trying to be the next MS killer. Something tells me it would look too much like USB[2] -- too much for its original purpose, and like the camel, quite cranky.
"If one is really a superior person, the fact is likely to leak out without too much assistance" -- John Andrew Holmes
Slightly off-topic...but someone mentioned porting GNOME to palmtop PDA devices. They proposed calling it Palm GNOME.
:-)
Think about how that would look.
-JD
TurboLinux also comes with GNOME now.
yeah a private exclusive list with more than 400 people on it
I suppose my point is that all the developers, translators, and documenters (anyone doing work in CVS) are on the list. So it only excludes people who aren't doing any work. And of course that's the point of the list. (Seen the signal-to-noise ratio of the public lists lately? Point made.)
If you think the Linux kernel developers or any other large project's developers make all decisions on a public list, you're just mistaken.
However most discussions of a technical nature (such as new gnome-libs features) are encouraged to be held on gnome-devel-list.
The article mentions the book GTK+ in 21 Days. Don't bother, that book isn't very good. (like most of those 21 Days books). You want a good book on GTK+ snag a copy of GTK+/Gnome Application Development by Havoc Pennington. Much better. Sharkey
www.badassmofo.com
I think Gnome will be the "standard" desktop as the big distributors supports it, and the licensing issue with KDE(OT).
I use Gnome myself(and sometimes KDE) but i do not want KDE to stop developing, choices is always good.
Hopefully the new version of the two will support each other better.
Keep up the good work Gnome and KDE developers!
Second, KDE2 do have CORBA support, only it is activated only when needed and deactivated then. This means they need a daemon to lurk for CORBA call. This maybe better if you stick with KDE-based apps, but if you use true CORBA applications often, it will slow down your PC.
Also, don't forget the DCOP is particuliar to KDE, as it needs both Qt and X, whereas CORBA is a standard. You have CORBA application on Unices, Windows, BeOS, MacOS, etc. You can't port DCOP to windows because you won't have X even if you have Qt. And you can't port DCOP to Qt/Embedded for the same reason. And you can't port DCOP to GNOME because you don't have Qt. I'm a KDE-fan, but I'm not sure in the long run it was the best thing to do.
Third, CORBA is an advance in desktop computing. CORBA on unices was pioneered by GNOME, and you say that CORBA-lack was pioneered by KDE. Nonsense.
You've well deserved your troll rating.
sigmentation fault
For some more informal reports, have a look through some diary entries at Advogato, including mine.
LILO boot: linux init=/usr/bin/emacs