Re: Thoughts on GTK+ and CSS

2009/8/5 Robert Staudinger : > On Tue, Aug 4, 2009 at 1:08 AM, Tristan Van Berkom wrote: > > [...] > >> I think half of that complexity is certainly needed, and the other >> half can be reliably introspected. >> >> For instance: >>  a.) I think its necessary for a customized composite widget author

Re: Thoughts on GTK+ and CSS

On Wed, Aug 5, 2009 at 12:44 PM, Tristan Van Berkom wrote: > On Wed, Aug 5, 2009 at 12:09 PM, Robert > Staudinger wrote: > [...] >> It seems we are looking at the issues from a different angle. > > Yes, which is why I am still here :) > Sorry to sound plaintive, I dont want to transmit the wrong m

Re: Thoughts on GTK+ and CSS

On Wed, Aug 5, 2009 at 12:09 PM, Robert Staudinger wrote: [...] > It seems we are looking at the issues from a different angle. Yes, which is why I am still here :) > I think all gtk should do is expose a DOM that the future CSS > subsystem can match against. Then there could be a gnome-hig.css t

Re: Thoughts on GTK+ and CSS

On Tue, Aug 4, 2009 at 1:08 AM, Tristan Van Berkom wrote: [...] > I think half of that complexity is certainly needed, and the other > half can be reliably introspected. > > For instance: >  a.) I think its necessary for a customized composite widget author >       to be able to mark a vbox as an

Re: Thoughts on GTK+ and CSS

On Mon, Aug 3, 2009 at 12:39 AM, Christian Dywan wrote: [...] > I wonder what the API might look like. > > gtk_container_get_child_position (GtkContainer* container, >                                  GtkWidget*    child, >                                  gint*         row, >                    

Re: Thoughts on GTK+ and CSS

On Mon, Aug 3, 2009 at 3:34 AM, Robert Staudinger wrote: > On Fri, Jul 31, 2009 at 7:28 PM, Tristan Van Berkom wrote: > > [...] [...] >> >> Then, the implemented CSS style for an item group would also cover >> GtkBox, allowing >> GtkBox to be styled as an itemized group, but not be one by nature, >

Re: Thoughts on GTK+ and CSS

On Fri, Jul 31, 2009 at 7:28 PM, Tristan Van Berkom wrote: [...] > Ofcourse, great example - the way I would suggest implementing this is >   a.) we recognize the need to show itemized groups >   b.) we define GTK_STOCK_STYLE_ITEM_GROUP >   c.) we allow some customized containers define themselve

Re: Thoughts on GTK+ and CSS

Am Fri, 31 Jul 2009 10:33:41 +0200 schrieb Robert Staudinger : > On Thu, Jul 30, 2009 at 4:37 PM, Christian > Dywan wrote: > > [...] > > > You are probably aware that gtk_container_get_children () does give > > yo the positions of children. Assuming that the lack of guarantees > > about order of

Re: Thoughts on GTK+ and CSS

Am Fri, 31 Jul 2009 13:28:02 -0400 schrieb Tristan Van Berkom : > On Fri, Jul 31, 2009 at 12:47 PM, Robert > Staudinger wrote: > > On Fri, Jul 31, 2009 at 6:19 PM, Tristan Van Berkom > > wrote: > > > > [...] > > > >> The idea of theme writers doing something to the first or last item > >> of a Gtk

Re: Thoughts on GTK+ and CSS

On Fri, Jul 31, 2009 at 12:47 PM, Robert Staudinger wrote: > On Fri, Jul 31, 2009 at 6:19 PM, Tristan Van Berkom wrote: > > [...] > >> The idea of theme writers doing something to the first or last item >> of a GtkBox simply based on it being a GtkBox; is a scary idea to me, >> while I do recognize

Re: Thoughts on GTK+ and CSS

On Fri, Jul 31, 2009 at 6:19 PM, Tristan Van Berkom wrote: [...] > The idea of theme writers doing something to the first or last item > of a GtkBox simply based on it being a GtkBox; is a scary idea to me, > while I do recognize the value of exposing the positional data of GtkBox > to the theme

Re: Thoughts on GTK+ and CSS

On Fri, Jul 31, 2009 at 4:15 AM, Robert Staudinger wrote: > On Thu, Jul 30, 2009 at 7:06 PM, Tristan Van Berkom wrote: > > [...] > >> An example of the backwardness we have in place, is that, >> IMO its simply wrong to assume the role of a GtkToolbar in a >> given application, the toolbar already n

Re: Thoughts on GTK+ and CSS

On Thu, Jul 30, 2009 at 4:37 PM, Christian Dywan wrote: [...] > You are probably aware that gtk_container_get_children () does give yo > the positions of children. Assuming that the lack of guarantees about > order of widgets in a container is the actual problem, maybe this can be > reconsidered.

Re: Thoughts on GTK+ and CSS

On Thu, Jul 30, 2009 at 7:06 PM, Tristan Van Berkom wrote: [...] > An example of the backwardness we have in place, is that, > IMO its simply wrong to assume the role of a GtkToolbar in a > given application, the toolbar already needs properties to override > theme settings in cases where its not

Re: Thoughts on GTK+ and CSS

2009/7/30 Christian Dywan : > Am Tue, 28 Jul 2009 08:45:26 +0200 > schrieb Robert Staudinger : > >> On Tue, Jul 28, 2009 at 3:40 AM, Keith Rarick wrote: >> >> [...] >> >> The "margin" property in gtk is not implemented like you assume >> >> above. Also does GtkContainer not expose information about

Re: Thoughts on GTK+ and CSS

Hi, I think its really exciting that you guys are working on this, so I stole the time this morning to share in the fun... I just want to throw out some ideas that Im sure are not new, but I was surprised werent really addressed yet in this thread. Im really not versed in what can/cant should

Re: Thoughts on GTK+ and CSS

On Tue, Jul 28, 2009 at 2:45 AM, Robert Staudinger wrote: > On Tue, Jul 28, 2009 at 3:40 AM, Keith Rarick wrote: > > [...] > >> What you describe addresses the separation of semantic structure from >> presentation, but that approach is far more powerful if the semantic >> information is sufficientl

Re: Thoughts on GTK+ and CSS

Am Mon, 27 Jul 2009 18:40:41 -0700 schrieb Keith Rarick : > > The "margin" property in gtk is not implemented like you assume > > above. Also does GtkContainer not expose information about child > > widget positions like you suggest using ":first-child" and friends. > > Work on those limitations wo

Re: Thoughts on GTK+ and CSS

Am Tue, 28 Jul 2009 08:45:26 +0200 schrieb Robert Staudinger : > On Tue, Jul 28, 2009 at 3:40 AM, Keith Rarick wrote: > > [...] > >> The "margin" property in gtk is not implemented like you assume > >> above. Also does GtkContainer not expose information about child > >> widget positions like you

Re: Thoughts on GTK+ and CSS

On Tue, Jul 28, 2009 at 3:40 AM, Keith Rarick wrote: [...] > What you describe addresses the separation of semantic structure from > presentation, but that approach is far more powerful if the semantic > information is sufficiently rich and sufficiently general. Currently, > writing a gtk theme f

Re: Thoughts on GTK+ and CSS

On Sun, Jul 26, 2009 at 11:41 PM, Robert Staudinger wrote: > The limitation regarding pseudo elements is not that we aren't aware > of their existence, but that libcroco doesn't support them at this > point. Gotcha. I wonder if libcroco would accept a patch implementing that. I'll ask on libcroco-

Re: Thoughts on GTK+ and CSS

Hello, On Sat, Jul 25, 2009 at 2:04 AM, Keith Rarick wrote: > I saw some discussion a while back [1] about using CSS for gtk themes > in the future. Now I have some ideas about that. My apologies if this > isn't the right time or place. > > ## Pseudo-element Selectors > > Last I heard, the best wa

Re: Thoughts on GTK+ and CSS

You can see progress of the Gtk css engine on a few places : http://blogs.gnome.org/theming/ and of course in git repository : http://git.gnome.org/cgit/gtk-css-engine/ it seems that you can contact Robert Staudinger if you want to help him on this matter. But is work seems already fairly advan

Thoughts on GTK+ and CSS

I saw some discussion a while back [1] about using CSS for gtk themes in the future. Now I have some ideas about that. My apologies if this isn't the right time or place. ## Pseudo-element Selectors Last I heard, the best way to represent pieces of complex widgets in CSS is still being discussed.