INSERT INTO sites(host) VALUES('twotoasts.de') 1045: Access denied for user 'www-data'@'localhost' (using password: NO) twotoasts.de Estimated Worth $370,714 - MYIP.NET Website Information
Welcome to MyIP.net!
 Set MYIP as homepage      

  
           

Web Page Information

Title:
Meta Description:
Meta Keywords:
sponsored links:
Links:
Images:
Age:
sponsored links:

Traffic and Estimation

Traffic:
Estimation:

Website Ranks

Alexa Rank:
Google Page Rank:
Sogou Rank:
Baidu Cache:

Search Engine Indexed

Search EngineIndexedLinks
 Google:
 Bing:
 Yahoo!:
 Baidu:
 Sogou:
 Youdao:
 Soso:

Server Data

Web Server:
IP address:    
Location:

Registry information

Registrant:
Email:
ICANN Registrar:
Created:
Updated:
Expires:
Status:
Name Server:
Whois Server:

Alexa Rank and trends

Traffic: Today One Week Avg. Three Mon. Avg.
Rank:
PV:
Unique IP:

More ranks in the world

Users from these countries/regions

Where people go on this site

Alexa Charts

Alexa Reach and Rank

Whois data

Who is twotoasts.de at de.whois-servers.net

% Copyright (c) 2010 by DENIC

% Version: 2.0

%

% Restricted rights.

%

% Terms and Conditions of Use

%

% The data in this record is provided by DENIC for informational purposes only.

% DENIC does not guarantee its accuracy and cannot, under any circumstances,

% be held liable in case the stored information would prove to be wrong,

% incomplete or not accurate in any sense.

%

% All the domain data that is visible in the whois service is protected by law.

% It is not permitted to use it for any purpose other than technical or

% administrative requirements associated with the operation of the Internet.

% It is explicitly forbidden to extract, copy and/or use or re-utilise in any

% form and by any means (electronically or not) the whole or a quantitatively

% or qualitatively substantial part of the contents of the whois database

% without prior and explicit written permission by DENIC.

% It is prohibited, in particular, to use it for transmission of unsolicited

% and/or commercial and/or advertising by phone, fax, e-mail or for any similar

% purposes.

%

% By maintaining the connection you assure that you have a legitimate interest

% in the data and that you will only use it for the stated purposes. You are

% aware that DENIC maintains the right to initiate legal proceedings against

% you in the event of any breach of this assurance and to bar you from using

% its whois service.

%

% The DENIC whois service on port 43 never discloses any information concerning

% the domain holder/administrative contact. Information concerning the domain

% holder/administrative contact can be obtained through use of our web-based

% whois service available at the DENIC website:

% http://www.denic.de/en/domains/whois-service/web-whois.html

%



Domain:
twotoasts.de

Nserver: ns1.hans.hosteurope.de

Nserver: ns2.hans.hosteurope.de

Status: connect

Changed: 2013-05-27T00:17:05+02:00



[Tech-C]

Type: PERSON

Name: HostEurope GmbH

Address: Welserstrasse 14

PostalCode: 51149

City: Koeln

CountryCode: DE

Phone: +49.1805467838

Fax: +49.1805663233

Email: info

Changed: 2013-02-18T12:04:12+01:00



[Zone-C]

Type: PERSON

Name: HostEurope GmbH

Address: Welserstrasse 14

PostalCode: 51149

City: Koeln

CountryCode: DE

Phone: +49.1805467838

Fax: +49.1805663233

Email: info

Changed: 2013-02-18T12:04:12+01:00

Front Page Thumbnail

sponsored links:

Front Page Loading Time

Keyword Hits (Biger,better)

Other TLDs of twotoasts

TLDs Created Expires Registered
.com
.net
.org
.cn
.com.cn
.asia
.mobi

Similar Websites

More...
Alexa鏍囬

Search Engine Spider Emulation

Title:Twotoasts | About WebKit, browsers and mail clients. And green cats.
Description:olor: #444444 !important; }
Keywords:
Body:
Twotoasts | About WebKit, browsers and mail clients. And green cats.
Twotoasts
About WebKit, browsers and mail clients. And green cats.
Menu
Skip to content
HomeAboutCatfishMidori
Preparing for Chemnitz 19 March 2016
Freshly printed Midori stickers just arrived, in November the last ones of the old batch were being given out to visitors of the OpenRheinRuhr. So I ordered new ones at FlyerAlarm, a print company based in W眉rzburg, Austria. This time around I went for circular ones and slightler smaller than they used to be. This size also fits better on phones and tablets for those who like to decorate theirs with stickers. You might also notice that the colors are better and the graphic comes out better #8211; fixes to the SVG will be finding their way into the repository soon.
With the new stickers I #8217;m well-prepared for Chemnitz Linux Days this march, in a little more than a fortnight. There will be a Midori booth there. Be sure to add the weekend of March 19 and 20 to your calendars!
This entry was posted in Midori on March 3, 2016 by kalikiana.
Heads or tails
As things go we diverged a bit from the original plan of making a big compatibility break with this release. Instead much of the original branch has been broken off into pieces that made their way into trunk. We did however bump WebKit2, libSoup and Zeitgeist dependencies. The most visible change is support for CSD, client side decorations, also called header bars after the API in GTK+3.10 (enabled via GTK_CSD=1). With no further adue here goes Midori 0.5.11 with a whole lot of nice things and a ton of bug fixes! Peek at the change log if you want more details.
So download Midori v0.5.11 now (1.2 MB)
The source tarball is up. Windows is going to follow suit shortly, and others are still being refreshed, so be patient if the option of your choice isn #8217;t there just yet.
You are welcome to join #midori on irc.freenode.net and party for the release!
This entry was posted in Midori, Uncategorized on August 30, 2015 by kalikiana.
A leap of leopards (or: 0.5.10)
Whilst work on the compatibility breaking branch is coming along nicely it seemed sensible to do another bug fix release. Thus Midori 0.5.10.
So download Midori v0.5.10 now (1.2 MB)
The source tarball is up. Windows is going to follow suit shortly, and others are still being refreshed, so be patient if the option of your choice isn #8217;t there just yet.
You are welcome to join #midori on irc.freenode.net or Slack and party for the release!
This entry was posted in Midori on April 20, 2015 by kalikiana.
WebKitGTK+ 2.8.0
We are excited and proud of announcing WebKitGTK+ 2.8.0, your favorite web rendering engine, now faster, even more stable and with a bunch of new features and improvements.
Gestures
Touch support is one the most important features missing since WebKitGTK+ 2.0.0. Thanks to the GTK+ gestures API, it #8217;s now more pleasant to use a WebKitWebView in a touch screen. For now only the basic gestures are implemented: pan (for scrolling by dragging from any point of the WebView), tap (handling clicks with the finger) and zoom (for zooming in/out with two fingers). We plan to add more touch enhancements like kinetic scrolling, overshot feedback animation, text selections, long press, etc. in future versions.
HTML5 Notifications
Notifications are transparently supported by WebKitGTK+ now, using libnotify by default. The default implementation can be overridden by applications to use their own notifications system, or simply to disable notifications.
WebView background color
There #8217;s new API now to set the base background color of a WebKitWebView. The given color is used to fill the web view before the actual contents are rendered. This will not have any visible effect if the web page contents set a background color, of course. If the web view parent window has a RGBA visual, we can even have聽transparent colors.
A new聽WebKitSnapshotOptions flag has also been added to be able to take web view snapshots over a transparent surface, instead of filling the surface with the default background color (opaque white).
User script messages
The communication between the UI process and the Web Extensions is something that we have always left to the users, so that everybody can use their own IPC mechanism. Epiphany and most of the apps聽use D-Bus for this, and it works perfectly. However, D-Bus is often too much for simple cases where there are only a few 聽messages sent from the Web Extension to the UI process. User script messages make these cases a lot easier to implement and can be used from JavaScript code or using the GObject DOM bindings.
Let #8217;s see how it聽works with a very simple example:
In the UI process,聽we register a script message handler using the WebKitUserContentManager and connect to the #8220;script-message-received-signal #8221; for the given handler:
webkit_user_content_manager_register_script_message_handler (user_content,
"foo");
g_signal_connect (user_content, "script-message-received::foo",
G_CALLBACK (foo_message_received_cb), NULL);
Script messages are received in the UI process as a WebKitJavascriptResult:
static void
foo_message_received_cb (WebKitUserContentManager *manager,
WebKitJavascriptResult *message,
gpointer user_data)
{
char *message_str;
message_str = get_js_result_as_string (message);
g_print ("Script message received for handler foo: %s\n", message_str);
g_free (message_str);
}
Sending a message from the web process to the UI process using JavaScript is very easy:
window.webkit.messageHandlers.foo.postMessage("bar");
That will send the message #8220;bar #8221; to the registered foo script message handler. It #8217;s not limited to strings, we can pass any JavaScript value to postMessage() that can be serialized. There #8217;s also a convenient API to send script messages in the GObject DOM bindings API:
webkit_dom_dom_window_webkit_message_handlers_post_message (dom_window,
"foo", "bar");
Who is playing audio?
WebKitWebView has now a boolean read-only property is-playing-adio that is set to TRUE when the web view is playing audio (even if it #8217;s a video) and to FALSE when the audio is stopped. Browsers can use this to provide聽visual feedback about which tab is playing audio, Epiphany already does that
HTML5 color input
Color input element is now supported by default, so instead of rendering a text field to manually input the color 聽as hexadecimal color code, WebKit now renders a color button that when clicked shows a GTK color chooser dialog. As usual, the public API allows to override the default implementation, to use your own color chooser. MiniBrowser uses a popover, for example.
APNG
APNG (Animated PNG) is a PNG extension that allows to create animated PNGs, similar to GIF but much better, supporting 24 bit images and transparencies. Since 2.8 WebKitGTK+ can render APNG files. You can check how it works with the mozilla demos.
SSL
The聽POODLE vulnerability fix introduced compatibility problems with some websites when establishing the SSL connection. Those problems were actually server side issues, that were incorrectly banning SSL 3.0聽record packet versions, but that could be worked around in WebKitGTK+.
WebKitGTK+ already provided a WebKitWebView signal to notify about TLS errors when loading, but only for the connection of the main resource in the main frame. However, it #8217;s still possible that subresources fail due to TLS errors, when using a connection different to the main resource one. WebKitGTK+ 2.8 gained WebKitWebResource::failed-with-tls-errors signal to be notified when a subresource load failed because of invalid certificate.
Ciphersuites based on RC4 are now disallowed聽when performing TLS negotiation, because聽it is no longer considered secure.
Performance: bmalloc and concurrent JIT
bmalloc is a new memory allocator added to WebKit聽to replace TCMalloc. Apple had already used it in the Mac and iOS ports for some time with very good results, but it needed some tweaks to work on Linux. WebKitGTK+ 2.8 now also uses bmalloc which drastically improved the overall performance.
Concurrent JIT was not enabled in GTK (and EFL) port for no apparent reason. Enabling it had also an amazing impact in the performance.
Both performance improvements were very noticeable in the performance bot:
The first jump on 11th Feb corresponds to the bmalloc switch, while the other jump on 25th Feb is when concurrent JIT was enabled.
Plans for 2.10
WebKitGTK+ 2.8 is an awesome release, but the plans for 2.10 are quite promising.
More security: mixed content for most of the resources types will be blocked by default. New API will be provided for managing mixed content.
Sandboxing: seccomp filters will be used in the different secondary processes.
More performance: FTL will be enabled in JavaScriptCore by default.
Even more performance: this time in the graphics side, by using the threaded compositor.
Blocking plugins API: new API to provide full control over the plugins load process, allowing to block/unblock plugins individually.
Implementation of the Database process: to bring back IndexedDB support.
Editing API: full editing API to allow using a WebView in editable mode with all editing capabilities.
This entry was posted in WebKit and tagged epiphany, Free Software, GNOME, gtk+, Igalia on March 23, 2015 by carlos garcia campos.
Ballet (or: 0.5.9)
Seven months of sweat and tears鈥 oh well, not quite so dramatic. In any event Midori 0.5.9 is out!
We #8217;re already scheming鈥 I mean planning for the next cycle. We want to go WebKit2 and GTK+3 only now and do away with the fourfold compatibility setup. Anyone who finds this thrilling is more than welcome to join in; the fun is going to start soon.
So download Midori v0.5.9 now (1.2 MB)
The source tarball and Windows download are up, while others are still being refreshed, so be patient if the option of your choice isn #8217;t there just yet.
You are welcome to join #midori on irc.freenode.net or Slack and party for the release!
This entry was posted in Midori on November 11, 2014 by kalikiana.
Midori booth at OpenRheinRuhr 2014
At OpenRheinRuhr 2014 we had a Midori booth again. Almost didn #8217;t happen due to the strike of Deutsche Bahn which caused many people to miss the event. Fortunately my humble self made it.
In addition to stickers, this time around we even had edible gummi paws!
Amongst the most posed questions was process isolation, something WebKit2 provides, and which will be available to everyone soon once our plan to move fully towards GTK+3, WebKit2 and Vala is put in motion. The other one was why Midori crashed so often #8211; which is due to the at least 4 primary build configurations currently available. I #8217;m very much looking forward to seeing this go away at some point in the future.
Pretty happy with the results personally, was able to get a decent number of people curious to try out Midori and in one instance even install it on site.
This entry was posted in Midori on November 10, 2014 by kalikiana.
Xubuntu 14.10 鈥淯topic Unicorn鈥
After six months of development, the latest version of Xubuntu has been released! Xubuntu 14.10 #8220;Utopic Unicorn #8221; features the latest in Xfce development and is the first step towards the next Long Term Support release in 2016.
Here #8217;s 10 new things to look for in the latest release.聽 For a more comprehensive list of changes and a list of download links, please see the official release announcement and release notes.
Appearance Updates
The login screen received a minor visual refresh and greater customization options.
LightDM GTK+ Greeter with the latest Greybird theme.
The new wallpaper for this release adds a splash of pink to the Xfce mouse.
The new default wallpaper for Xubuntu 14.10 #8220;Utopic Unicorn #8221;
To celebrate the 14.10 codename #8220;Utopic Unicorn #8221;, pink highlights have been added.聽 These highlights can be reverted or easily changed to another color with the installed #8220;Theme Configuration #8221; utility.
Using #8220;Theme Configuration #8221;, you can easily change Xubuntu #8217;s colors to match your mood.
Xfce Updates
Xfce Power Manager 1.4 sports several improvements over previous releases. Brightness controls have been extended to better support backlit keyboards and new laptop displays. The updated panel plugin shows device charge status, adds display brightness controls, and fixes #8220;Presentation Mode #8221; #8212; letting you disable automatic screensavers.
Xfce Power Manager replaces the Power Indicator for Xubuntu 14.10
With the latest Xfce Display Settings, managing multiple monitors is no longer a hassle. Just drag and rearrange the displays to your liking.
The new drag-and-drop display settings greatly improves multihead support.
With the updated Xfce window manager, the Alt-Tab switcher has been updated with a refreshed appearance and the ability to select windows with your mouse or by touch.
Even minor features like the Alt-Tab switcher have been improved.
With the latest Whisker Menu and changes to the default configuration, applications in the Settings Manager are now searchable.
Quickly find and launch any application with the Whisker Menu.
Application Updates
With Catfish 1.2, previewing files has been greatly simplified. Easily switch between details and preview mode. When the search index becomes outdated, Catfish will also notify you to update.
Catfish makes searching for images easier with the latest release.
Parole 0.7 introduces a new Clutter-based backend and finally supports video playback in Virtualbox. The media controls are now contained in a slide-over overlay (with a configurable timeout).
Parole #8217;s interface is further refined with each new release.
Light Locker Settings has been improved, further integrating with Xfce Power Manager to handle screensaver settings.
Light Locker Settings can now integrate with other screensaver managers.
That #8217;s it for this release, now to get ready for 15.04 #8220;Vivid Vervet #8221;!
This entry was posted in Catfish and tagged 14.10, Light Locker, Linux, Open Source, Parole, Xfce, Xubuntu on October 24, 2014 by Sean.
Kitten looking to be adopted
The following unfortunately comes up regularly these days:
This Midori looks interesting, maybe I should try it out.
Aha, there #8217;s a Debian package for it.
sudo apt-get install midori
midori (0.4.3+dfsg-0.1)
Meh, pretty crashy, I better ask some devs for help.
Ah, so 0.5.8 is the latest.
So why isn #8217;t this packaged!?
The answer is simple, Midori needs a Debian package maintainer! Thousands of Debian and Ubuntu users are facing the above situation, including lots of Raspberry Pi users. A single person stepping up to it can literally change the world at this point. Now if fame isn #8217;t motivation enough, there may be a t-shirt to get.
This entry was posted in Midori on September 2, 2014 by kalikiana.
GTK+ 3 Plugins in WebKitGTK+ and Evince Browser Plugin
GTK+ 3 plugins in WebKitGTK+
The WebKit2 GTK+ API has always been GTK+ 3 only, but WebKitGTK+ still had a hard dependency on GTK+ 2 because of the plugin process. Some popular browser plugins like flash or Java use GTK+ 2 unconditionally (and it seems they are not going to be ported to GTK+ 3, at least not in the short term). These plugins stopped working in Epiphany when it switched to GTK+ 3 and started to work again when Epiphany moved to WebKit2.
To support GTK+ 2 plugins we had to build the plugin process with GTK+ 2, but also some parts of WebCore and WebKit2 (the ones depending on GTK+ and used by the plugin process) were built twice. As a result we had a WebKitPluginProcess binary of ~40MB, that was always used for all the plugins. This kind of made sense, since there were no plugins using GTK+ 3, and the GTK+ 2 dependency was harmless for plugins not using GTK+ at all. However, we realized we were making a rule for the exception, since most of the plugins don #8217;t even use GTK+, and there weren #8217;t plugins using GTK+ 3 because they were not supported by any browser (kind of chicken-egg problem).
Since WebKitGTK+ 2.5.1 we have two binaries for the plugin process: WebKitPluginProcess2 which is exactly the same 40MB binary using GTK+ 2 that we have always had, but that now is only used to load plugins using GTK+ 2; and WebKitPluginProcess, a 7,4K binary that is now used by default for everything except loading plugins that use GTK+ 2. And since it links to GTK+ 3, it might load plugins using GTK+ 3 as well. Another side effect is that now we can make GTK+ 2 optional, WebKitPluginProcess2 wouldn #8217;t be built and only plugins using GTK+ 2 wouldn #8217;t be supported.
Evince Browser Plugin
For a long time, we have maintained that PDF documents shouldn #8217;t be opened inside the browser, but downloaded and then opened by the default document viewer. But then the GNOME design team came up with new mockups for Epiphany were everything was integrated in the browser, including PDF documents. It #8217;s something all the major browsers do nowadays, using different approaches though (Custom PDF plugin inside the web engine, JavaScript libraries, etc.).
At the WebKitGTK+ hackfest in 2012 we started to think about how to implement the integrated document reading in Epiphany based on the design mockups. We quickly discarded the idea of implementing it as a NPAPI plugin, because that would mean we had to use a very old evince version using GTK+ 2. We can #8217;t implement it inside WebKit using libevince because it #8217;s a GPL library, so the first approach was to implement it inside Epiphany using libevince. I wrote a first patch, it was mostly a proof of concept hack, that added a new view widget based on EvView to be used instead of a WebView when a document supported by evince was requested. This approach has a lot of limitations, since it only works when the main resource is a document, but not for documents embedded in a HTML page or an iframe, and a lot of integration problems that makes it quite difficult to maintain inside Epiphany. All of these issues would be solved by implementing it as a NPAPI plugin and it wouldn #8217;t require any change in Epiphany. Now that WebKitGTK+ supports GTK+ 3 plugins, there #8217;s no reason not to do so.
Thanks to a project in Igalia I #8217;ve been able to work on it, and today I #8217;ve landed an initial implementation of the browser plugin to Evince git master. It #8217;s only a first implementation (written in C++ 11) with the basic features (page navigation, view modes, zoom and printing), and a very simple UI that needs to be updated to match the mockups. It can be disabled at compile time like all other frontends inside Evince (thumbnailer, previewer, nautilus properties page).
Another advantage of being a NPAPI plugin is that it #8217;s scriptable so that you can control the viewer using JavaScript.
And you can pass initial parameters (like current page, zoom level, view mode, etc.) from the HTML tag.
lt;object data="test.pdf" type="application/pdf" width="600" height="300"
currentPage="2" zoomMode="fit-page" continuous="false" gt;
The pdf could not be rendered.
lt;/object gt;
You can even hide the default toolbar and build your own one using HTML and JavaScript.
This entry was posted in WebKit and tagged epiphany, evince, Free Software, GNOME, Igalia, pdf on August 6, 2014 by carlos garcia campos.
WebKitGTK+ 2.5.1: Good bye WebKit1
WebKitGTK+ 2.5.1 is the first version of this release cycle. It comes very late mainly due to the regressions introduced by the switch to CMake and the problems we found after removing WebKit1 from the tree. It also includes some new features that I #8217;ll talk about in other posts, probably when 2.6.0 is released. In this post I #8217;ll only focus on the breaks introduced in this release, in order to help everybody to adapt their applications to the API changes if needed.
Wait, but why breaking the API?
Since the release of WebKitGTK+ 2.0 the WebKit1 API has been considered deprecated and in maintenance mode. The new WebKit2 API is quite complete and stable now, so the plan for WebKitGTK+ 2.6 was removing WebKit1, leaving it alive, but still in maintenance mode, in the 2.4 branch. After removing the code from trunk we realized that newer versions of WebKitGTK+ that are WebKit2 only should be parallel installable with older versions of WebKitGTK+ that also include WebKit1. After some discussions trying to find the best solution, we reached the conclusion that we had to bump the binary version. But then I thought, since we were going to force everybody to recompile, why not take advantage to introduce some small (but necessary) API changes that in most of the cases will not affect the the users anyway? And then I started to review the API and proposing some changes. I also wanted to make sure all API changes were introduced in the first unstable release, so that users only have to adapt their applications once, and that #8217;s the main reason why the release has taken so long.
Binary version bump
The new binary version is 4.0, so to use this new release you need to update your build system to look for webkit2gtk-4.0 pkg-config file.
GObject DOM Bindings
The GObject DOM bindings API situation was actually the main reason for breaking the API. The problem was that the code for the DOM bindings is generated automatically from the IDL files. This means that every time a new IDL file was added to the build system, we ended up exposing a new class in our public API without even noticing. Same happened when a API incompatible change was introduced in an IDL file, for example to update it to the current standard. We added a script to our build bots to warn us when that happened, and then we had to manually deprecate the existing API and add exceptions to the code generator. This was a lot of work just to keep backwards compatibility of an API nobody was using. Most of the people actually use a 5-10% of the DOM bindings API.
Since WebKitGTK+ 2.5.1 the GObject DOM bindings API is split into stable and unstable parts. The stable part contains the most commonly used API that it #8217;s unlikely to change. We will keep maintaining backwards compatibility of this part of the API. The rest of the API is considered unstable and might change at any time, you can still use it but at your own risk. We thought this solution was better than just removing the unstable API. There are two kind of unstable APIs:
Classes that are considered unstable: the entire class is considered unstable. The header is not included in the main webkitdom.h header, so to use them you have to include the header file explicitly.
Unstable symbols of stable classes: a method or constant in a stable class that is considered unstable. In this case the header file is included by the main webkitfom.h header, but it doesn #8217;t contain any unstable symbols, they are included in a new header WebKitDOMClassNameUnstable.h that also needs to be included explicitly.
In both cases you need to define聽WEBKIT_DOM_USE_UNSTABLE_API before including the headers
#define WEBKIT_DOM_USE_UNSTABLE_API
#include lt;webkitdom/WebKitDOMHTMLMediaElement.h gt;
#include lt;webkitdom/WebKitDOMElementUnstable.h gt;
WebKit2 GTK+ API
The API changes in the WebKit2 GTK+ API could have been avoided, by deprecating symbols and adding new ones, but since we were going to break the API anyway, and the affected symbols are not that commonly used we thought it was worth it.
WebKitWebView::create: the signal now receives a聽WebKitNavigationAction parameter containing information about the navigation action that triggered the event. So now you can know the type of event (if it was a link clicked, a form submitted, etc.), the mouse button and keyboard modifiers, the URI request or even if it was a user gesture. This information is very useful to implement a popup blocker, for example.
/* before */
static WebKitWebView *
web_view_created_cb (WebKitWebView *web_view,
gpointer user_data)
/* after */
static WebKitWebView *
web_view_created_cb (WebKitWebView *web_view,
WebKitNavigationAction *navigation_action,
gpointer user_data)
WebKitWebViewGroup has been removed. This class was only introduced to add the user stylesheets API, since most of the people actually use the default web view group. The grouping of pages inside WebKit2 is something that will be eventually removed, in favor of users doing the groups they need. The user stylesheets API has been moved to a new class WebKitUserContentManager that will also be extended to support user scripts. The settings can still be handled directly with the WebKitWebView API, so that if you want a group of web views to share the same settings you can simply call webkit_web_view_set_settings() for all the web views passing the same WebKitSettings object.
/* before */
WebKitWebViewGroup *group = webkit_web_view_get_group (web_view);
webkit_web_view_group_add_user_style_sheet (group,
buffer,
NULL, /* base URI */
NULL, /* whitelist */
NULL, /* blacklist */
WEBKIT_INJECTED_CONTENT_FRAMES_ALL);
/* after */
WebKitUserContentManager *user_content;
WebKitUserStyleSheet *style_sheet;
style_sheet = webkit_user_style_sheet_new (buffer,
WEBKIT_USER_CONTENT_INJECT_ALL_FRAMES,
WEBKIT_USER_STYLE_LEVEL_USER,
NULL, /* whitelist */
NULL /* blacklist */);
user_content = webkit_web_view_get_user_content_manager (web_view);
webkit_user_content_manager_add_style_sheet (user_content, style_sheet);
webkit_user_style_sheet_unref (style_sheet);
WebKitCertificateInfo has been removed. This was supposed to be a convenient way of handling TLS certificates, but when trying to use it in a real case, it ended up being unconvenient. The聽WebKitWebView::load-failed-with-tls-errors聽signal now receives a GTlsCertificate and TlsCertificateFlags, and聽webkit_web_context_allow_tls_certificate_for_host() receives a GTlsCertificate.
/* before */
static gboolean
load_failed_with_tls_errors_cb (WebKitWebView *web_view,
WebKitCertificateInfo *info,
const gchar *host,
gpointer user_data)
{
WebKitWebContext *context = webkit_web_view_get_context (web_view);
GTlsCertificate *certificate = webkit_certificate_info_get_tls_certificate (info);
GTlsCertificateFlags errors = webkit_certificate_info_get_tls_errors (info);
if (add_exception_for_error (host, errors))
webkit_web_context_allow_tls_certificate_for_host (context, info, host);
}
/* after */
static gboolean
load_failed_with_tls_errors_cb (WebKitWebView *web_view,
GTlsCertificate *certificate,
GTlsCertificateFlags errors,
const gchar *host,
gpointer user_data)
{
WebKitWebContext *context = webkit_web_view_get_context (web_view);
if (add_exception_for_error (host, errors))
webkit_web_context_allow_tls_certificate_for_host (context, certificate, host);
}
View mode API: The view source mode was removed from WebCore, and the API was already marked as deprecated. Since it #8217;s very unlikely we add more view modes, we just removed the API. There #8217;s no replacement for this, but it could be easily implemented either using a external window with a GtkSourceView or embedded into a WebKitWebView by using a custom URI scheme and a JavaScript library for syntax highlighting.
CMake
Since version 2.5.1 WebKitGTK+ uses CMake instead autotools as its build system. The equivalent to configure, make and make install now would be something like this:
$ cd webkitgtk-2.5.1
$ cmake -DCMAKE_INSTALL_PREFIX= -DCMAKE_INSTALL_LIBDIR=lib -DPORT=GTK \
-DCMAKE_BUILD_TYPE=Release .
$ make
(enjoy the summer in the meantime)
# make install
Help!
Sure, we are available as usual in the #webkitgtk+ IRC channel at FreeNode and our mailing list webkit-gtk@lists.webkit.org.
This entry was posted in WebKit and tagged Free Software, GNOME, Igalia on August 1, 2014 by carlos garcia campos.
Post navigation
larr; Older posts
Search for:
Recent Posts
Preparing for Chemnitz 19 March 2016
Heads or tails
A leap of leopards (or: 0.5.10)
WebKitGTK+ 2.8.0
Ballet (or: 0.5.9)
Recent Commentsmzsade on MidoriSpencer on Midori賲毓乇賮蹖 氐丿 亘乇賳丕賲賴 乇丕蹖诏丕賳 亘乇丕蹖 诏賳賵/賱蹖賳賵讴爻 | 爻賱丕賲 丿賳蹖丕 | 乇爻丕賳賴 鬲禺氐氐蹖 賳乇賲鈥屫з佖藏ж辟囏й 丌夭丕丿 / 賲鬲賳鈥屫ㄘж on CatfishBetaBrowserTest 14: Firefox 41 Chrome 45 Midori 0.5.10 Opera 31 SeaMonkey 2.38 | osS) (Side blog on A leap of leopards (or: 0.5.10)Elementary OS, une jolie distribution et facile pour tous, tout simplement ! | My Tiny Tools on MidoriArchives
March 2016
August 2015
April 2015
March 2015
November 2014
October 2014
September 2014
August 2014
July 2014
April 2014
March 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
May 2013
April 2013
March 2013
February 2013
December 2012
September 2012
August 2012
June 2012
May 2012
April 2012
March 2012
December 2011
November 2011
October 2011
August 2011
July 2011
May 2011
March 2011
February 2011
January 2011
October 2010
September 2010
August 2010
May 2010
March 2010
February 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
October 2008
September 2008
August 2008
July 2008
Categories
Catfish
Midori
Postler
Ubuntu
Uncategorized
WebKit
Meta
Log in
Entries RSS
Comments RSS
WordPress.org
Proudly powered by WordPress

Updated Time

Updating   
Friend links: ProxyFire    More...
Site Map 1 2 3 4 5 6 7 8 9 10 20 30 40 50 60 70 80 90 100 110 120 130 140 150 160 170 180 190 200 250 300 350 400 450 500 550 600 610 620 630 640 650 660 670 680 690 700 710 720 730 740 750
TOS | Contact us
© 2009 MyIP.cn Dev by MYIP Elapsed:49.881ms