isa/gnome-shell
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
867cffaf20
gnome-shell/src/st/st-theme-node-private.h

131 lines
3.4 KiB
C
Raw Normal View History

Move rendering into st-theme-node-drawing.c The idea behind this move is that we have a lot more control over rendering if StWidget isn't a big pile of actors, and things are more efficient. https://bugzilla.gnome.org/show_bug.cgi?id=607500
2010-02-08 18:40:25 +00:00
/* -*- mode: C; c-file-style: "gnu"; indent-tabs-mode: nil; -*- */
Fix up copyright and license notices for St * Make sure all source files have a LGPL copyright header, and standardize non-standard variations of the header to a common form. * Check and update all copyright notices. * Remove 'Written By:' lines. They are universally incomplete and typically indicate only who started a particular file. https://bugzilla.gnome.org/show_bug.cgi?id=634550
2010-11-10 22:00:45 +00:00
/*
* st-theme-node-private.h: private structures and functions for StThemeNode
*
* Copyright 2009, 2010 Red Hat, Inc.
St: Implement background-size CSS property Implement the background-size CSS property, specified by the CSS Backgrounds and Borders Module Level 3, including the keywords "contain", "cover", and fixed-size backgrounds. https://bugzilla.gnome.org/show_bug.cgi?id=633462
2011-12-23 17:59:20 +00:00
* Copyright 2011 Quentin "Sardem FF7" Glidic
Fix up copyright and license notices for St * Make sure all source files have a LGPL copyright header, and standardize non-standard variations of the header to a common form. * Check and update all copyright notices. * Remove 'Written By:' lines. They are universally incomplete and typically indicate only who started a particular file. https://bugzilla.gnome.org/show_bug.cgi?id=634550
2010-11-10 22:00:45 +00:00
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU Lesser General Public License as
* published by the Free Software Foundation, either version 2.1 of
* the License, or (at your option) any later version.
*
* This program is distributed in the hope it will be useful, but WITHOUT ANY
* WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
* FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for
* more details.
*
* You should have received a copy of the GNU Lesser General Public License
* along with this program. If not, see <http://www.gnu.org/licenses/>.
*/
Move rendering into st-theme-node-drawing.c The idea behind this move is that we have a lot more control over rendering if StWidget isn't a big pile of actors, and things are more efficient. https://bugzilla.gnome.org/show_bug.cgi?id=607500
2010-02-08 18:40:25 +00:00
#ifndef __ST_THEME_NODE_PRIVATE_H__
#define __ST_THEME_NODE_PRIVATE_H__
#include <gdk/gdk.h>
#include "st-theme-node.h"
St: support css margin property It's implemented similar to the padding property, but instead of taking into account the margin values at drawing time in node-drawing, we set the clutter actor margins in StWidget when the style is computed. In the case that a CSS margin is not specified, we don't to set a value of 0 to the clutter actor margin. In this manner it allows to use Clutter margin values set in the code. However, the margins that are set both in the code and in the CSS on the same side, the result is unpredictable. We avoid to set the clutter actor margin values to 0 if there's no CSS margin values defined, so we still allow clutter actors to use margin set in the code. https://bugzilla.gnome.org/show_bug.cgi?id=728437
2014-11-11 14:04:46 +00:00
#include <libcroco/libcroco.h>
St: Implement background-size CSS property Implement the background-size CSS property, specified by the CSS Backgrounds and Borders Module Level 3, including the keywords "contain", "cover", and fixed-size backgrounds. https://bugzilla.gnome.org/show_bug.cgi?id=633462
2011-12-23 17:59:20 +00:00
#include "st-types.h"
Move rendering into st-theme-node-drawing.c The idea behind this move is that we have a lot more control over rendering if StWidget isn't a big pile of actors, and things are more efficient. https://bugzilla.gnome.org/show_bug.cgi?id=607500
2010-02-08 18:40:25 +00:00
G_BEGIN_DECLS
struct _StThemeNode {
GObject parent;
StThemeContext *context;
StThemeNode *parent_node;
StTheme *theme;
PangoFontDescription *font_desc;
ClutterColor background_color;
/* If gradient is set, then background_color is the gradient start */
StGradientType background_gradient_type;
ClutterColor background_gradient_end;
[StThemeNode] Add basic background-position support Add basic support for background-position, which only supports absolute values. Also don't require an unit to be specified for 0 (because the unit does not really matter here 0 is 0 regardless of the unit). https://bugzilla.gnome.org/show_bug.cgi?id=624375
2010-09-01 16:13:43 +00:00
int background_position_x;
int background_position_y;
st-theme-node: Clean up Replace some faulty indentation, group some booleans to reduce a bit of memory usage https://bugzilla.gnome.org/show_bug.cgi?id=680801
2012-07-28 07:49:14 +00:00
St: Implement background-size CSS property Implement the background-size CSS property, specified by the CSS Backgrounds and Borders Module Level 3, including the keywords "contain", "cover", and fixed-size backgrounds. https://bugzilla.gnome.org/show_bug.cgi?id=633462
2011-12-23 17:59:20 +00:00
StBackgroundSize background_size;
gint background_size_w;
gint background_size_h;
[StThemeNode] Add basic background-position support Add basic support for background-position, which only supports absolute values. Also don't require an unit to be specified for 0 (because the unit does not really matter here 0 is 0 regardless of the unit). https://bugzilla.gnome.org/show_bug.cgi?id=624375
2010-09-01 16:13:43 +00:00
Move rendering into st-theme-node-drawing.c The idea behind this move is that we have a lot more control over rendering if StWidget isn't a big pile of actors, and things are more efficient. https://bugzilla.gnome.org/show_bug.cgi?id=607500
2010-02-08 18:40:25 +00:00
ClutterColor foreground_color;
ClutterColor border_color[4];
[StThemeNode] implement CSS "outline" property Could potentially be used for focus indication https://bugzilla.gnome.org/show_bug.cgi?id=621669
2010-05-26 20:50:24 +00:00
ClutterColor outline_color;
Move rendering into st-theme-node-drawing.c The idea behind this move is that we have a lot more control over rendering if StWidget isn't a big pile of actors, and things are more efficient. https://bugzilla.gnome.org/show_bug.cgi?id=607500
2010-02-08 18:40:25 +00:00
int border_width[4];
int border_radius[4];
[StThemeNode] implement CSS "outline" property Could potentially be used for focus indication https://bugzilla.gnome.org/show_bug.cgi?id=621669
2010-05-26 20:50:24 +00:00
int outline_width;
Move rendering into st-theme-node-drawing.c The idea behind this move is that we have a lot more control over rendering if StWidget isn't a big pile of actors, and things are more efficient. https://bugzilla.gnome.org/show_bug.cgi?id=607500
2010-02-08 18:40:25 +00:00
guint padding[4];
St: support css margin property It's implemented similar to the padding property, but instead of taking into account the margin values at drawing time in node-drawing, we set the clutter actor margins in StWidget when the style is computed. In the case that a CSS margin is not specified, we don't to set a value of 0 to the clutter actor margin. In this manner it allows to use Clutter margin values set in the code. However, the margins that are set both in the code and in the CSS on the same side, the result is unpredictable. We avoid to set the clutter actor margin values to 0 if there's no CSS margin values defined, so we still allow clutter actors to use margin set in the code. https://bugzilla.gnome.org/show_bug.cgi?id=728437
2014-11-11 14:04:46 +00:00
guint margin[4];
Move rendering into st-theme-node-drawing.c The idea behind this move is that we have a lot more control over rendering if StWidget isn't a big pile of actors, and things are more efficient. https://bugzilla.gnome.org/show_bug.cgi?id=607500
2010-02-08 18:40:25 +00:00
int width;
int height;
int min_width;
int min_height;
int max_width;
int max_height;
[StThemeNode] Add transition-duration CSS property Add a CSS property to control style transitions. https://bugzilla.gnome.org/show_bug.cgi?id=619025
2010-05-30 21:06:37 +00:00
int transition_duration;
st: always use GFile internally We're moving the theme infrastructure towards GResource, so as a first step move all the loading to use GFiles instead of URIs or paths. https://bugzilla.gnome.org/show_bug.cgi?id=736936
2014-09-19 00:04:00 +00:00
GFile *background_image;
Move rendering into st-theme-node-drawing.c The idea behind this move is that we have a lot more control over rendering if StWidget isn't a big pile of actors, and things are more efficient. https://bugzilla.gnome.org/show_bug.cgi?id=607500
2010-02-08 18:40:25 +00:00
StBorderImage *border_image;
StThemeNode: Split -st-shadow into three attributes Currently, "-st-shadow" can mean one of three very different things: 1) shadow based on alpha of the background image 2) shadow the "border box" of the node 3) shadow applied to the content of a StIcon It isn't well defined which of the above 3 cases -st-shadow will mean for any given node, however. This commit splits the property into three different properties, "box-shadow", "-st-background-image-shadow", and "icon-shadow" to make it all very explicit. https://bugzilla.gnome.org/show_bug.cgi?id=636976
2011-01-13 23:27:24 +00:00
StShadow *box_shadow;
StShadow *background_image_shadow;
[StThemeNode] Add text-shadow property Reorganize the existing code which parses the -st-shadow property to allow parsing different shadow properties and add support for the text-shadow property. https://bugzilla.gnome.org/show_bug.cgi?id=624384
2010-07-24 14:56:50 +00:00
StShadow *text_shadow;
Add StIconColors object, compute in StThemeNode A new StIconColors object is used to efficiently track the colors we need to colorize a symbolic icon. st_theme_node_compute_icon_colors() is added to compute the StIconColors for a theme node. (Refcounting of StIconColors means that we'll typically share the colors object of the parent node.) https://bugzilla.gnome.org/show_bug.cgi?id=633865
2010-11-01 02:06:48 +00:00
StIconColors *icon_colors;
Move rendering into st-theme-node-drawing.c The idea behind this move is that we have a lot more control over rendering if StWidget isn't a big pile of actors, and things are more efficient. https://bugzilla.gnome.org/show_bug.cgi?id=607500
2010-02-08 18:40:25 +00:00
GType element_type;
char *element_id;
Store CSS classes and pseudo-classes pre-split in the StThemeNode Tokenizing every time we want to evaluate CSS seems a poor plan. Bug: https://bugzilla.gnome.org/show_bug.cgi?id=687465 Reviewed-by: Jasper St. Pierre <jstpierre@mecheye.net>
2012-11-07 18:44:33 +00:00
GStrv element_classes;
GStrv pseudo_classes;
Move rendering into st-theme-node-drawing.c The idea behind this move is that we have a lot more control over rendering if StWidget isn't a big pile of actors, and things are more efficient. https://bugzilla.gnome.org/show_bug.cgi?id=607500
2010-02-08 18:40:25 +00:00
char *inline_style;
CRDeclaration **properties;
int n_properties;
/* We hold onto these separately so we can destroy them on finalize */
CRDeclaration *inline_properties;
st-theme-node: Clean up Replace some faulty indentation, group some booleans to reduce a bit of memory usage https://bugzilla.gnome.org/show_bug.cgi?id=680801
2012-07-28 07:49:14 +00:00
guint background_position_set : 1;
st-theme-node: Add repeating backgrounds Add support for the CSS "background-repeat" property. Currently, this only supports on/off, rather than allowing tiling in each individual dimension. It is supported for both the cogl and cairo rendering paths. https://bugzilla.gnome.org/show_bug.cgi?id=680801
2012-07-28 08:36:20 +00:00
guint background_repeat : 1;
st-theme-node: Clean up Replace some faulty indentation, group some booleans to reduce a bit of memory usage https://bugzilla.gnome.org/show_bug.cgi?id=680801
2012-07-28 07:49:14 +00:00
Move rendering into st-theme-node-drawing.c The idea behind this move is that we have a lot more control over rendering if StWidget isn't a big pile of actors, and things are more efficient. https://bugzilla.gnome.org/show_bug.cgi?id=607500
2010-02-08 18:40:25 +00:00
guint properties_computed : 1;
guint geometry_computed : 1;
guint background_computed : 1;
guint foreground_computed : 1;
guint border_image_computed : 1;
StThemeNode: Split -st-shadow into three attributes Currently, "-st-shadow" can mean one of three very different things: 1) shadow based on alpha of the background image 2) shadow the "border box" of the node 3) shadow applied to the content of a StIcon It isn't well defined which of the above 3 cases -st-shadow will mean for any given node, however. This commit splits the property into three different properties, "box-shadow", "-st-background-image-shadow", and "icon-shadow" to make it all very explicit. https://bugzilla.gnome.org/show_bug.cgi?id=636976
2011-01-13 23:27:24 +00:00
guint box_shadow_computed : 1;
guint background_image_shadow_computed : 1;
[StThemeNode] Add text-shadow property Reorganize the existing code which parses the -st-shadow property to allow parsing different shadow properties and add support for the text-shadow property. https://bugzilla.gnome.org/show_bug.cgi?id=624384
2010-07-24 14:56:50 +00:00
guint text_shadow_computed : 1;
Move rendering into st-theme-node-drawing.c The idea behind this move is that we have a lot more control over rendering if StWidget isn't a big pile of actors, and things are more efficient. https://bugzilla.gnome.org/show_bug.cgi?id=607500
2010-02-08 18:40:25 +00:00
guint link_type : 2;
st: optimize box-shadow rendering Currently the box-shadow is rendering is done like this : The first time we want to render a node that requires a box-shadow, St creates an cogl offscreen surface of the size of the allocation and renders the box into this offscreen buffer using modulation on the alpha channel, this buffer is then blurred according to the CSS parameters. The problem with this method is that every time an StWidget is resized, its box-shadow offscreen buffer has to be resized and therefore rendered and blurred. This patches propose an optimization for this use case by rendering the box-shadow only once but at a size that is independent of the StWidget's size. Then every time we need to paint this box-shadow, we just render this offscreen buffer using a 9-slices. This method only works when the allocation of the widget is bigger than the minimum shadow size on which we can apply a 9-slices, that is given my the radius of the corners. If the allocation is smaller than this minimum size, we then fallback to the fully render/blur the shadow (like before this patch). https://bugzilla.gnome.org/show_bug.cgi?id=689858
2013-07-03 16:01:00 +00:00
guint rendered_once : 1;
st-theme-node: reuse box-shadow materials between paint states when possible
2013-07-04 13:26:08 +00:00
guint cached_textures : 1;
st: optimize box-shadow rendering Currently the box-shadow is rendering is done like this : The first time we want to render a node that requires a box-shadow, St creates an cogl offscreen surface of the size of the allocation and renders the box into this offscreen buffer using modulation on the alpha channel, this buffer is then blurred according to the CSS parameters. The problem with this method is that every time an StWidget is resized, its box-shadow offscreen buffer has to be resized and therefore rendered and blurred. This patches propose an optimization for this use case by rendering the box-shadow only once but at a size that is independent of the StWidget's size. Then every time we need to paint this box-shadow, we just render this offscreen buffer using a 9-slices. This method only works when the allocation of the widget is bigger than the minimum shadow size on which we can apply a 9-slices, that is given my the radius of the corners. If the allocation is smaller than this minimum size, we then fallback to the fully render/blur the shadow (like before this patch). https://bugzilla.gnome.org/show_bug.cgi?id=689858
2013-07-03 16:01:00 +00:00
int box_shadow_min_width;
int box_shadow_min_height;
st-theme-node: Move some allocation-independent textures back to the theme node The background image, background image shadow and border image are allocation-indepedent, so we can keep these in the node. Given that these are are likely cached in the StTextureCache, the slight increase in code complexity may not be worth caching these textures and materials -- we might be better off just computing when we need to paint. https://bugzilla.gnome.org/show_bug.cgi?id=697274
2013-04-05 01:22:34 +00:00
st: Use g_signal_handler_disconnect() to disconnect from StTheme With a high enough amount of actors, there may be enough theme nodes and signal connections on StTheme::custom-stylesheets-changed that g_signal_handlers_disconnect_by*() on dispose becomes expensive, this may become a surprisingly hot spot in StWidget::style-changed. Keep the handler ID around and use g_signal_handler_disconnect() to avoid linear lookups for the matching func/data. https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/524
2019-04-30 12:42:59 +00:00
guint stylesheets_changed_id;
st: Fix a bunch of cogl deprecations
2015-09-26 02:20:22 +00:00
CoglPipeline *border_slices_texture;
st: Rename *material to *pipeline ... since the last commit changed the type from CoglMaterial to CoglPipeline.
2015-10-15 21:42:19 +00:00
CoglPipeline *border_slices_pipeline;
st: Fix a bunch of cogl deprecations
2015-09-26 02:20:22 +00:00
CoglPipeline *background_texture;
st: Rename *material to *pipeline ... since the last commit changed the type from CoglMaterial to CoglPipeline.
2015-10-15 21:42:19 +00:00
CoglPipeline *background_pipeline;
CoglPipeline *background_shadow_pipeline;
st: Fix some more cogl deprecations Replace the remaining cogl_set_source* calls with the explicit pipeline/framebuffer API.
2015-11-12 10:22:52 +00:00
CoglPipeline *color_pipeline;
st-theme-node: reuse box-shadow materials between paint states when possible
2013-07-04 13:26:08 +00:00
StThemeNodePaintState cached_state;
Move rendering into st-theme-node-drawing.c The idea behind this move is that we have a lot more control over rendering if StWidget isn't a big pile of actors, and things are more efficient. https://bugzilla.gnome.org/show_bug.cgi?id=607500
2010-02-08 18:40:25 +00:00
};
void _st_theme_node_ensure_background (StThemeNode *node);
void _st_theme_node_ensure_geometry (StThemeNode *node);
St: support css margin property It's implemented similar to the padding property, but instead of taking into account the margin values at drawing time in node-drawing, we set the clutter actor margins in StWidget when the style is computed. In the case that a CSS margin is not specified, we don't to set a value of 0 to the clutter actor margin. In this manner it allows to use Clutter margin values set in the code. However, the margins that are set both in the code and in the CSS on the same side, the result is unpredictable. We avoid to set the clutter actor margin values to 0 if there's no CSS margin values defined, so we still allow clutter actors to use margin set in the code. https://bugzilla.gnome.org/show_bug.cgi?id=728437
2014-11-11 14:04:46 +00:00
void _st_theme_node_apply_margins (StThemeNode *node,
ClutterActor *actor);
st: Track stylesheet changes on the StThemeContext Instead of every individual StThemeNode. There are essentially two kinds of theme nodes: Those we create for lookups, and those interned by the theme context and used by StWidgets. Listening to the signal on the former is pointless as they are short lived and not meant to be really used for drawing. So it is only essential to track stylesheet changes in those we intern for later use. This change does precisely that, it lets the StThemeContext track the stylesheet changes and let all known theme nodes reset their state for it. The internal array holding all connected handlers for this signal in glib was about the biggest single allocation made in gnome-shell, as interned theme nodes nodes are around the 4 to 5 digit numbers. This essentially makes it disappear. This however means that widgets that are explicitly set a theme through st_widget_set_theme() don't get their theme node implicitly updated. There's little reasons to use that API, so perhaps this is an acceptable tradeoff. https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/779
2019-10-24 12:03:12 +00:00
void _st_theme_node_reset_for_stylesheet_change (StThemeNode *node);
Move rendering into st-theme-node-drawing.c The idea behind this move is that we have a lot more control over rendering if StWidget isn't a big pile of actors, and things are more efficient. https://bugzilla.gnome.org/show_bug.cgi?id=607500
2010-02-08 18:40:25 +00:00
G_END_DECLS
#endif /* __ST_THEME_NODE_PRIVATE_H__ */
Reference in New Issue Copy Permalink