Re: Autocompletion for GtkEntry
- From: Kristian Rietveld <kris gtk org>
- To: Havoc Pennington <hp redhat com>
- Cc: Ricardo Fernández Pascual <ric users sourceforge net>, GTK Development list <gtk-devel-list gnome org>
- Subject: Re: Autocompletion for GtkEntry
- Date: 12 Oct 2002 22:03:13 +0200
On Sat, 2002-10-12 at 21:04, Havoc Pennington wrote:
>
> Havoc Pennington <hp redhat com> writes:
> > Kristian Rietveld <kris gtk org> writes:
> > > So this is just how I feel about it, I know that I don't have any real
> > > arguments. But I would love to know how others think about this.
> > >
> >
> > I think it'd be useful to better define what you mean by complex and
> > simple:
> >
> > - what are the use cases we have in mind (file selector, Galeon,
> > nautilus ?)
Those and usage in a simple text combo.
> > - which use cases are supported by the complex version
> > - which are supported by the simple version
> >
> > In short, what are we giving up in the simple version, and is it
> > important.
> >
>
> Another way to sort this out might be:
>
> - what are the minimal hooks needed for GtkEntry to make it possible
> for nautilus/galeon to use its native autocompletion in the
> location bar?
>
> i.e. is the EggCompletionFunc enough of a hook?
That would be interesting to know.
>
> Naively I'd say you need to be able to:
>
> - tell GtkEntry the currently-active completion
>
> - tell GtkEntry the list of possible completions to show in the
> dropdown
>
> - if you want the "show titles" feature, a way to pass that in
>
> That's all the core API it seems like we need. Most of the work is in
> implementing the UI part (the dropdown, etc.)
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]