Apr 092009

Lots and lots of things have been going on around me lately, but that’s best left for other posts if I ever get around to do them. ๐Ÿ˜‰

A few months ago, I’ve sat down with quite some help by others and collected the input and feedback around Gtk+ 3.0. The outcome of that was a first Gtk+ 3 Roadmap draft that was sent around to the core team.

After some recent poking, the draft has now been posted on the Gtk+ development list, here is the Gtk+ 3 Roadmap Draft Announcement.

I’d like to thank everyone who participated in the fruitful discussions leading to this and particularly Stormy and Dave Neary for their suggestions on the post-draft process.

Cody Russell has kindly volunteered to wikify the roadmap, so future alterations will be easy. I much appreciate his initiative, especially because I can’t foresee to have much time around the roadmap personally in the near future.

The roadmap draft is best discussed on the mailing list and provided online here: Gtk+ 3 Roadmap Draft

This roadmap is also a call for participation to all developers and contributors.

If you have an interest in Gtk+ 3, this is the time to participate in constructive discussions around the roadmap or sign up for one of the many development tasks.

I sincerely hope this is helpful for everyone.

Es ist nicht deine Schuld daรŸ die Welt ist wie sie ist.Es wรคr’ nur deine Schuld wenn sie so bleibt.
— Die ร„rzte

Tweet about this on TwitterShare on Google+Share on LinkedInShare on FacebookFlattr the authorBuffer this pageShare on RedditDigg thisShare on VKShare on YummlyPin on PinterestShare on StumbleUponShare on TumblrPrint this pageEmail this to someone

[suffusion-the-author display='description']

  4 Responses to “09.04.2009 Gtk+ 3 Roadmap Participation”

  1. Too bad that a canvas widget didn’t make it into the “Wishlist items for 3.x” section. Any thoughts/news on http://live.gnome.org/ProjectRidley/CanvasOverview ?

  2. H,

    I read through the list and it looked as if rapicorn & clutter are *the* tools for the GTK canvas.
    Nothing like GTKCanvas *canvas = gtk_create_canvas(window, WITH_GL, background, DEFAULT_PEN); though ๐Ÿ™

  3. Beyond the api breakage (largely from house-cleaning and better separation of API and implementation) what is GTK+ 3.0 meant to be? What is the vision of GTK+ the toolkit and the goals of this phase?

    I see a list of features, but it doesn’t communicate the problem it solves, the goal it contributes towards, nor the inter-relationships of the changes.

    Perhaps this isn’t the document to communicate the larger vision, but that vision should at least be summarized, cross referenced, and the document aligned in part with that so people can understand the importance of each contribution (and which contributions, although important, are not core features but rather supporting libraries)

  4. Hi Tim.

    The ideas/plans posted in the Gtk 3.0 Roadmap sound good and relevant in overall. Some of them will really help Gtk to provide stuff other toolkits are doing/working on and thus keep gtk relevant in the future.

    However, what I’m really missing from the roadmap is clear support for the different platforms where Gtk is being used.

    Currently gtk is quite big library. And most of that is very desktop oriented. There’s nothing bad in that, as such, but it means that gtk is not able to be mobile oriented at the same time.

    To solve this, I’d like to see the “point-zero / API break” release to be taken one step further: to divide Gtk into (sub-)packages, which applications can use in opt-in basis. Here’s a layman’s suggestion to the division:

    gtk-core — all non-widget stuff that is needed for widgets to work. Additionally, the bare essentials of the most generic widgets: Label, slider, entry, textarea, button, ?? (yes, I’m seriously thinking of not even having GtkTreeview and IconView here, because they have evolved to be SO complex right now).

    gtk-desktop — all stuff that is not in core, including the rest of the widgets

    gtk-mobile — (new) only widgets relevant to mobile people? Maybe towards some kind of set similar to what hildon is in maemo 5?


    The idea in the division (obviously) would be that you could include e.g. gtk-core while not having to deal with the whole package of gtk-desktop. Or even create your own widget library (a bit similar idea what hildon is doing) and only use gtk as the foundation for those widgets.

    I think this kind of approach (if it makes technically any sense) would help speeding up the experimentation and enhancement of gtk towards multiple platforms, while not forcing gtk to throw out or replace any of the stuff it currently has (and of which much remains to be useful for e.g. desktop platform).

 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>