Great! Awesome! Perfect! It is a day for celebration. Thanks to tonikitoo, Roberto Oliveira and Tomaz Noleto we were awarded! Our first Firefox add-on is the "Best Updated Add-on for Firefox 3.5"!
"Smart Find enhances the default “Find” feature of Firefox by matching words phonetically. So if you don’t know how to spell “Schwarzenegger”, you won’t have to."
Ensure you are using Firefox and install Smart Find.
Updated in Nov 26th.
WebKit is not just a great platform for Web Browsers development. It allows one to 'easily' port it to a given environment such as Gtk+, Qt, EFL, etc. At least easier than Mozilla does. So, as I told in my first post, I've started collaborating on the Qt port, fixing bugs and adding features and removing deprecated stuff. The best part of working on WebKit-Qt is that it is time to time merged in the Qt code itself.
An interesting feature I had the pleasure to add in WebKit-Qt is a Web page frame property that sets whether the content of this frame should be cropped by the *view area. In other words, when it is set to 'true' WebKit-Qt automatically adds scrollbars in the view area and render only the content that fits in it. Update: the property was removed in Qt 4.6 because there is another (not so simple) way of doing the same thing.
So, why does that deserve a blog post? Because the possibilities it adds to the WebKit-Qt usage and because it also gave me my first NOT WebKit commit in the Qt tree. Ok! It is a WebKit example... It is named framecapture and can be found here.
The framecapture does not have a Graphical User Interface (can work in batch mode) and loads a given Web page using WebKit as backend, rendering it internally. In other words, WebKit does not need to show a Web page to render it. When the page is finally loaded, it is split in frames and each frame content is captured and saved in PNG files. Without the property above added the PNG files would contain only the viewable part of the frame content.
Suppose this is the Web page we want to capture in frames. It has a top frameset containing two frames: one with a fake logo (in blue) and another one with a fake header (in green). It also contains a fake main frame (in red).
The Web page will be split in the 3 images below, which are then saved in PNG files. All of it is done with a simple command: 'framecapture http://blablabla...'
Image 1: the logo frame.
Image 3: the main frame.Update: thanks Kenneth Christiansen (who sent me an email) and tonikitoo (who commented here) that framecapture and this post were deprecated.
As I wrote in my first post I have started working on the WebKit world! I spent few months making it work with Evas/Ecore/EFL as back-end. Just to clarify, I was not alone on that! Actually, I was not even the main developer on it as I was a little bit busy with INdT internal projects and my Master degree activities, which I will post about later.
There are more details about the WebKit-EFL port in the WebKit trac here. It was released in June 2009 as tonikitoo pointed out in his blog and a new release is about to be announced. Unfortunately I could not contribute in this next release, but as far as I could see in #webkit-efl on irc.freenode.net there was a big refactoring on the rendering code. That refactoring was done mainly by Enlightenment developers, which shows that there is already some interest on it.
WebKit-EFL promises to be very useful in low profile devices, as it inherits the Enlightenment characteristics such as lower memory/CPU consuming with great visual effects and performance and aggregates to it the WebKit browser functionalities.
The first browser client using the release 0.1 is Eve. Francisco Alecrim shows how to build and run Eve in a Nokia N810 device using Mamona here. It also runs in SHR, a OpenMoko distribution that contains some basic EFL applications.
More is about to come as Barbieri mentioned in the Enlightenment Devel email list: "ProFUSION is working on it on behalf of another company that shall remain unnamed. If/When they release their product we may see the source code, as WebKit-EFL license requires."
Something I'm planning to do on it would be a memory/CPU comparison test between ELauncher, QtLauncher and GtkLauncher, all of them basic WebKit based browsers.
Lots to do in a short time but I'm back. I have spent the last two weeks catching up all the things I missed when I was in FISL. I went there to help mainly in the Mozilla booth (as they financed my air fare, hotel and lunch) and in the INdT's (as they let me go to FISL and stay 1 week away of my tasks).
That was my third time attending to FISL: the first one in 2007 I went as a simple watcher. The second one, last year, I went as a speaker talking about porting Firefox add-ons to MicroB (the Maemo browser). This year as I told before, I went as expositor.
I don't know if I will go in 2010, actually I just went this year due to the Mozilla "sponsorship". The event itself does not call my attention anymore, it is cheaper to see the mosts interesting talking in videos.
More pictures of the Mozilla both in FISL 2009 here.
Posts
All Comments
