GNOME 3 Delayed Until September 2010
supersloshy writes "Contrary to popular opinion, GNOME 3 will not be released in March next year. It has been delayed until September 2010, six months later. According to the news message, this is because 'our community wants GNOME 3.0 to be fully working for users and why we believe September is more appropriate.' GNOME 3's main goal is to re-define the ways people interact with the desktop, mainly through a new UI design (currently called 'GNOME Shell'), while GNOME 2.30, set for release in March, will have a focus on being stable. An early visual tour of GNOME 3 has been posted at Digitizor."
80% percent of the tour looks like stuff in the current gnome. I mean we already have a NetworkManager and you already get a calendar when you click on the clock.
Virtual desktops get more recognition. The UI is more modal and Mac like. So what if their default configuration has just the one panel? Thats how I configure it anyway.
http://michaelsmith.id.au
Try GNOME Do.
The "Docky" frontend is a fantastic dock experience as well.
You're looking for Katapult. And you know what - that was probably the first (or one of the first) apps of such kind.
Linux needs this
Most Linux desktop environments have this. The default in Gnome is to use to pop up a run dialogue, that will autocomplete recently used apps. I configured the same thing in openbox, with lxpanel.
Except that it isn't. According the GnomeShell page on Gnome Live, "Much of the code of the shell is written in Javascript and Clutter and GNOME platform libraries via GObject Introspection and JavaScript bindings for GNOME."
GObject Introspection is actually quite cool IMO, it makes it much easier to create bindings from dynamic languages libraries that use GObject, like the GNOME platform, GStreamer, etc.
Can you please explain why? I wrote a plugin for Gnome-Do last summer and found the code refreshingly simple and easy to grok. I'm a hard core C/Perl/Java coder, and I really like some of the features of C#, such as the in-line properties for accessors/mutators. The dbus hooks into Mono are first-class citizens, and MUCH easier to use than their C counterparts. Apart from the "omg a Microsoft engineer designed it" knee-jerk reaction, what is the complaint with Mono?
The wheel is turning, but the hamster is dead.