WordPress database error: [INSERT, UPDATE command denied to user '51213-2'@'10.10.20.100' for table 'wp_options']
INSERT INTO `wp_options` (`option_name`, `option_value`, `autoload`) VALUES ('_transient_doing_cron', '1716085463.7020521163940429687500', 'yes') ON DUPLICATE KEY UPDATE `option_name` = VALUES(`option_name`), `option_value` = VALUES(`option_value`), `autoload` = VALUES(`autoload`)


Warning: Cannot modify header information - headers already sent by (output started at /home/lexiqued/www/WordPress/wp-includes/wp-db.php:1502) in /home/lexiqued/www/WordPress/wp-includes/rest-api/class-wp-rest-server.php on line 1372

Warning: Cannot modify header information - headers already sent by (output started at /home/lexiqued/www/WordPress/wp-includes/wp-db.php:1502) in /home/lexiqued/www/WordPress/wp-includes/rest-api/class-wp-rest-server.php on line 1372

Warning: Cannot modify header information - headers already sent by (output started at /home/lexiqued/www/WordPress/wp-includes/wp-db.php:1502) in /home/lexiqued/www/WordPress/wp-includes/rest-api/class-wp-rest-server.php on line 1372

Warning: Cannot modify header information - headers already sent by (output started at /home/lexiqued/www/WordPress/wp-includes/wp-db.php:1502) in /home/lexiqued/www/WordPress/wp-includes/rest-api/class-wp-rest-server.php on line 1372

Warning: Cannot modify header information - headers already sent by (output started at /home/lexiqued/www/WordPress/wp-includes/wp-db.php:1502) in /home/lexiqued/www/WordPress/wp-includes/rest-api/class-wp-rest-server.php on line 1372

Warning: Cannot modify header information - headers already sent by (output started at /home/lexiqued/www/WordPress/wp-includes/wp-db.php:1502) in /home/lexiqued/www/WordPress/wp-includes/rest-api/class-wp-rest-server.php on line 1372

Warning: Cannot modify header information - headers already sent by (output started at /home/lexiqued/www/WordPress/wp-includes/wp-db.php:1502) in /home/lexiqued/www/WordPress/wp-includes/rest-api/class-wp-rest-server.php on line 1372

Warning: Cannot modify header information - headers already sent by (output started at /home/lexiqued/www/WordPress/wp-includes/wp-db.php:1502) in /home/lexiqued/www/WordPress/wp-includes/rest-api/class-wp-rest-server.php on line 1372
{"id":1460,"date":"2013-06-30T17:53:33","date_gmt":"2013-06-30T15:53:33","guid":{"rendered":"http:\/\/www.jonathanantoine.com\/?p=1460"},"modified":"2013-07-01T11:18:38","modified_gmt":"2013-07-01T09:18:38","slug":"windows-8-1-xaml-new-theme-management-in-your-windows-store-apps","status":"publish","type":"post","link":"http:\/\/www.jonathanantoine.com\/2013\/06\/30\/windows-8-1-xaml-new-theme-management-in-your-windows-store-apps\/","title":{"rendered":"Windows 8.1 #XAML new theme management in your Windows Store Apps"},"content":{"rendered":"

Did you remember Windows 8 ? The theme of your app was set once at the launch and you could\u2019nt change it dyamically or set once by control. This was really annoying in some case like Settings Flyout where you often wanted to set the opposite one of your app. <\/strong><\/p>\n

This was good old times and these issues are gone in Windows 8.1 : youpi !<\/strong><\/p>\n

Let\u2019s digg a little more \"Smile\"<\/p>\n

<\/p>\n

The theme can be updated at runtime<\/h3>\n

Windows 8 theme resources are provided using StaticResource and so can\u2019t be updated at runtime. The resources are loaded once at the app startup and even if you update it, the controls won\u2019t update themselves because the StaticResource provide the value once and only once : when parsed.<\/p>\n

Now comes a new markup extension named ThemeResource.<\/strong> You can use it like the StaticResource object but this special resource will update the targeted control if the Theme of the control is updated<\/strong>. You can see it as the DynamicResource in WPF but only for some \u201ctheme\u201d resource and triggered only by a theme change.<\/p>\n

Of course, all the template of the frameworks are now using this new feature and you are free (must \"Smile\") use it in your own controls. You can actually use it anywhere in your XAML :
\n[xml]
\n<Border RequestedTheme="Light"
\n Background="{ThemeResource ApplicationPageBackgroundThemeBrush}">
\n<\/Border>
\n[\/xml]\n<\/p>\n

The theme can now be set by control<\/h3>\n

In Windows 8 you had to set the RequestedTheme property at launch (in the constructor of you app for example) and it could be set only once. <\/p>\n

Now this is a property of the FrameworkElement class which is the base class for any control.<\/strong> The value will be inherited by all its children (this is actually done because it overrides values in the resource dictionary which will be available to the children of the control).<\/p>\n

In this sample I override the theme twice in the same visual tree : <\/p>\n

[xml]
\n<StackPanel RequestedTheme="Light"
\n Background="{ThemeResource ApplicationPageBackgroundThemeBrush}">
\n <TextBlock Text="Hello World !" \/>
\n <Border RequestedTheme="Dark"
\n Background="{ThemeResource ApplicationPageBackgroundThemeBrush}">
\n <TextBlock Text="Another theme" \/>
\n <\/Border>
\n<\/StackPanel>
\n[\/xml]
\nIt then produce this view :
\n\"Screenshot<\/p>\n

 <\/p>\n

Be aware that this is a \u201clow priority\u201d setting<\/strong> and that all the styles, directly set attributes\/properties, triggers, animations and even implicit styles are winning over it.<\/p>\n

 <\/p>\n

Questions ?<\/h3>\n