Re: a new combo box

2014-12-28 Thread Kristian Rietveld
On 27 Dec 2014, at 18:05, Sébastien Wilmet swil...@gnome.org wrote: On Sun, Dec 28, 2014 at 12:50:24AM +0900, Tristan Van Berkom wrote: In any case, I think this misses the point I was trying to make, I think someone had to raise the obvious question: is it justified to bring in a whole

Re: a new combo box

2014-12-28 Thread Matthias Clasen
On Sun, Dec 28, 2014 at 1:27 AM, Alberto Ruiz ar...@gnome.org wrote: My main concern with the design is that users can't make a difference between a normal button and this widget (usually related to an action, perhaps with the exception of iconized menus like the ones we're using in headerbars

Re: a new combo box

2014-12-28 Thread Morten Welinder
This is the third (fourth) incarnation of a combo box and there is still opposition to keeping the API stable? That's just crazy. Matthias' awesomeness aside, why would this be the last time? Seriously, a change in a widget like this means 20+ hours[*] of extra work for me as an application

Re: a new combo box

2014-12-28 Thread Emmanuele Bassi
On 28 December 2014 at 16:32, Morten Welinder mort...@gnome.org wrote: This is the third (fourth) incarnation of a combo box and there is still opposition to keeping the API stable? That's just crazy. on the contrary: with a new class you'd be sure that the GtkComboBox widget API is finally

Re: a new combo box

2014-12-28 Thread Jasper St. Pierre
So let me ask a very basic question here, since I feel it's at the heart of the dumb internet argument we're having. What is this design trying to solve? What problems with the old ComboBox are we trying to fix? What use cases is it designed for? Is it the usability problems? Are we adding the

Re: a new combo box

2014-12-28 Thread Morten Welinder
on the contrary: with a new class you'd be sure that the GtkComboBox widget API is finally stable — as in no changes, except for bug fixes — which is apparently what you want. There are three types of widgets in the gtk+ world: (1) active and non-deprecated, (2) deprecated, and (3) deprecated

Re: a new combo box

2014-12-28 Thread Emmanuele Bassi
hi; On 28 December 2014 at 17:23, Morten Welinder mort...@gnome.org wrote: on the contrary: with a new class you'd be sure that the GtkComboBox widget API is finally stable — as in no changes, except for bug fixes — which is apparently what you want. There are three types of widgets in the

Re: a new combo box

2014-12-28 Thread Matthias Clasen
I am a bit disappointed by the turn this discussion has taken - I was hoping people would try the code I pointed to and let me know what they think and point out problems (thanks to Tim for doing just that). Instead, I get arguments about how much my time is worth compared to Mortens, complaints

Re: a new combo box

2014-12-28 Thread Emmanuele Bassi
hi Matthias; On 27 December 2014 at 13:02, Matthias Clasen matthias.cla...@gmail.com wrote: over Christmas, I had some for a little side project, a new combo box. It is based on these mockups:

Re: a new combo box

2014-12-28 Thread Cosimo Cecchi
On Mon, Dec 29, 2014 at 1:53 AM, Matthias Clasen matthias.cla...@gmail.com wrote: I am a bit disappointed by the turn this discussion has taken - I was hoping people would try the code I pointed to and let me know what they think and point out problems (thanks to Tim for doing just that).

Re: a new combo box

2014-12-28 Thread Cosimo Cecchi
On Mon, Dec 29, 2014 at 1:09 AM, Jasper St. Pierre jstpie...@mecheye.net wrote: Cosimo talks about GtkPopover and GtkMenu, but those just sort of have me stunned. Why should I use one instead of the other? I doubt application authors choose which widget to use by reading type names in API