Re: what we need to make apps use gtk instead of libgnome/ui

I wonder why there is still no GnomeDruid replacement is it because it
will depends on GtkCanvas? 

And I wonder if dbus could be used to have href, help (if a fd.o help
spec is introduced) and printing support into gtk. Dbus can give us the
necessary desktop independence for this kind of stuff.

On Wed, 2005-02-23 at 21:23 +1030, Alex Murray wrote:
>On Wed, 2005-02-23 at 11:37 +0100, Kristof Vansant wrote:
>> I think one of the important things missing at the moment, is good
>> documentation for developers how they can switch from gnome widgets to
>> gtk widgets. A lot of gnome stuff is deprecated but still used in a
>> of projects.
>I agree -> perhaps in the Gnome API it could say (eg):
>GnomeAboutDialog is deprecated and should not be used in newly written
>code -> superseded by GtkAboutDialog
>this way at least there is some guidance as to what to use instead..
>> Guides that should be possible to write but I can't find:
>> GnomeFileEntry -> ?
>> GnomeAppBar -> GtkStatusbar + GtkProgressBar
>> GnomeEntry -> GtkEntry + ? (to save the history)
>> GnomeCanvas -> GtkCanvas (gtk 2.8)
>> esd -> gstreamer
>Has gstreamer been confirmed as the plan for sound in Gnome in the
>> gnome_config_* -> ?
>> widgets and functions missing in gtk at the moment, so can't be
>> replaced:
>> GnomeDruid
>> GnomeHREF
>> GnomeDateEdit ?
>> gnome_help_*
>> gnome_url_*
>> session support
>> I hope someone would write those guide so we can start replacing code.
>> Or set up a wiki and when the documentation is done include it into
>> gtk api guide.
>> _______________________________________________
>> gnome-devel-list mailing list
>> gnome-devel-list gnome org
>gnome-devel-list mailing list
>gnome-devel-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]