2009/8/5 Robert Staudinger robert.staudin...@gmail.com:
On Tue, Aug 4, 2009 at 1:08 AM, Tristan Van Berkomt...@gnome.org 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
On Mon, Aug 3, 2009 at 12:39 AM, Christian Dywanchrist...@lanedo.com wrote:
[...]
I wonder what the API might look like.
gtk_container_get_child_position (GtkContainer* container,
GtkWidget* child,
gint* row,
On Tue, Aug 4, 2009 at 1:08 AM, Tristan Van Berkomt...@gnome.org 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
On Wed, Aug 5, 2009 at 12:09 PM, Robert
Staudingerrobert.staudin...@gmail.com 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
On Wed, Aug 5, 2009 at 12:44 PM, Tristan Van Berkomt...@gnome.org wrote:
On Wed, Aug 5, 2009 at 12:09 PM, Robert
Staudingerrobert.staudin...@gmail.com 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
On Fri, Jul 31, 2009 at 7:28 PM, Tristan Van Berkomt...@gnome.org 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
On Mon, Aug 3, 2009 at 3:34 AM, Robert
Staudingerrobert.staudin...@gmail.com wrote:
On Fri, Jul 31, 2009 at 7:28 PM, Tristan Van Berkomt...@gnome.org wrote:
[...]
[...]
Then, the implemented CSS style for an item group would also cover
GtkBox, allowing
GtkBox to be styled as an itemized
Am Fri, 31 Jul 2009 13:28:02 -0400
schrieb Tristan Van Berkom t...@gnome.org:
On Fri, Jul 31, 2009 at 12:47 PM, Robert
Staudingerrobert.staudin...@gmail.com wrote:
On Fri, Jul 31, 2009 at 6:19 PM, Tristan Van Berkomt...@gnome.org
wrote:
[...]
The idea of theme writers doing
Am Fri, 31 Jul 2009 10:33:41 +0200
schrieb Robert Staudinger robert.staudin...@gmail.com:
On Thu, Jul 30, 2009 at 4:37 PM, Christian
Dywanchrist...@lanedo.com wrote:
[...]
You are probably aware that gtk_container_get_children () does give
yo the positions of children. Assuming that
On Thu, Jul 30, 2009 at 7:06 PM, Tristan Van Berkomt...@gnome.org 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
On Thu, Jul 30, 2009 at 4:37 PM, Christian Dywanchrist...@lanedo.com 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
On Fri, Jul 31, 2009 at 4:15 AM, Robert
Staudingerrobert.staudin...@gmail.com wrote:
On Thu, Jul 30, 2009 at 7:06 PM, Tristan Van Berkomt...@gnome.org 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
On Fri, Jul 31, 2009 at 6:19 PM, Tristan Van Berkomt...@gnome.org 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
On Fri, Jul 31, 2009 at 12:47 PM, Robert
Staudingerrobert.staudin...@gmail.com wrote:
On Fri, Jul 31, 2009 at 6:19 PM, Tristan Van Berkomt...@gnome.org 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
Am Tue, 28 Jul 2009 08:45:26 +0200
schrieb Robert Staudinger robert.staudin...@gmail.com:
On Tue, Jul 28, 2009 at 3:40 AM, Keith Rarickk...@xph.us wrote:
[...]
The margin property in gtk is not implemented like you assume
above. Also does GtkContainer not expose information about child
Am Mon, 27 Jul 2009 18:40:41 -0700
schrieb Keith Rarick k...@xph.us:
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
On Tue, Jul 28, 2009 at 2:45 AM, Robert
Staudingerrobert.staudin...@gmail.com wrote:
On Tue, Jul 28, 2009 at 3:40 AM, Keith Rarickk...@xph.us wrote:
[...]
What you describe addresses the separation of semantic structure from
presentation, but that approach is far more powerful if the
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
2009/7/30 Christian Dywan christ...@lanedo.com:
Am Tue, 28 Jul 2009 08:45:26 +0200
schrieb Robert Staudinger robert.staudin...@gmail.com:
On Tue, Jul 28, 2009 at 3:40 AM, Keith Rarickk...@xph.us wrote:
[...]
The margin property in gtk is not implemented like you assume
above. Also does
On Tue, Jul 28, 2009 at 3:40 AM, Keith Rarickk...@xph.us 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
Hello,
On Sat, Jul 25, 2009 at 2:04 AM, Keith Rarickk...@xph.us 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
On Sun, Jul 26, 2009 at 11:41 PM, Robert
Staudingerrobert.staudin...@gmail.com 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
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
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
24 matches
Mail list logo
