Re: Building multiple backends on on same system

[Benjamin Otte <otte gnome org>]

While we're talking about getting rid of stuff, I'd like to get rid of
> gdk_utf8_to_string_target
> gdk_string_to_compound_text_for_display
> gdk_utf8_to_compound_text_for_display
> gdk_free_text_list
> gdk_free_compound_text

But I lack enough clue about selections to do that. Is there anyone
with enough clue that could find an API that can do this?
The biggest problem I have with these APIs is that either they should
be used (in which case we need to make sure people actually use them
when they have to by introducing GdkCompoundText etc types) or they
should not be used and the gdk selection code should take care of
them. But the current situation is that even people who worked on the
DND code have no idea what it's for. (I asked in #gtk+ and nobody had
any clue.)

Benjamin


On Fri, Dec 10, 2010 at 6:22 PM, Matthias Clasen
<matthias clasen gmail com> wrote:
> I have mostly taken care of GdkDragContext, GdkVisual and GdkDevice now.
> Some of the remaining pieces look more like candidates for dropping/cleanup
> instead of virtualization though:
>
>> gdk_spawn_command_line_on_screen
>> gdk_spawn_on_screen
>> gdk_spawn_on_screen_with_pipes
>
> Looking over the backends, only X11 has anything that is not a 100%
> direct mapping to g_spawn apis, and even that is only setting DISPLAY
> to a value returned by
> gdk_screen_make_display_name(). We could just make this backend-specific.
>
> I think the same goes for the various apis related to foreign windows:
> It would seem much more natural to me to move those to be
> backend-specific.
>