Arora

After several Qt 4.6 features it is time to add a feature that everyone can enjoy. This weekend we merged in a new simple start page that Arora will use as the default home page starting in 0.8.0. A big thanks goes to Fernando Lemos who created it. ... [More] The page is integrated with the search box using QtWebKit's Javascript bridge. This means that whatever you have currently selected in the search box will be used in the start page, i.e. Google is not hardcoded.Please report any usability/design related suggestions. [Less]

After several Qt 4.6 features it is time to add a feature that everyone can enjoy. This weekend we merged in a new simple start page that Arora will use as the default home page starting in 0.8.0. A big thanks goes to Fernando Lemos who created it. ... [More] The page is integrated with the search box using QtWebKit's Javascript bridge. This means that whatever you have currently selected in the search box will be used in the start page, i.e. Google is not hardcoded.Please report any usability/design related suggestions. [Less]

One missing feature that QtWebKit has had (and Arora) has been the ability to set the text encoding. This feature ended up being relatively simple path to QtWebKit and has been added to QWebSettings. This API will be part of Qt 4.6 and for those running Arora against QtWebkit trunk or Qt-git you will now see a simple text-encoding menu.

One missing feature that QtWebKit has had (and Arora) has been the ability to set the text encoding. This feature ended up being relatively simple path to QtWebKit and has been added to QWebSettings. This API will be part of Qt 4.6 and for those running Arora against QtWebkit trunk or Qt-git you will now see a simple text-encoding menu.

One missing feature that QtWebKit has had (and Arora) has been the ability to set the text encoding. This feature ended up being relatively simple path to QtWebKit and has been added to QWebSettings. This API will be part of Qt 4.6 and for those running Arora against QtWebkit trunk or Qt-git you will now see a simple text-encoding menu.

One missing feature that QtWebKit has had (and Arora) has been the ability to set the text encoding. This feature ended up being relatively simple path to QtWebKit and has been added to QWebSettings. This API will be part of Qt 4.6 and for those running Arora against QtWebkit trunk or Qt-git you will now see a simple text-encoding menu.

Over on planetkde.org (and on some KDE mailing lists) there is a bunch of discussion about web browsers and KDE. A common theme was that rather then talking about KHTML v.s. Webkit it you should just get out there and code. In that spirit I ... [More] finished off my AccessKey branch and merged it in tonight. When you press the ctrl key little semi transparent boxes will appear all over the screen highlighting links. If you type the letter in the box that link will be followed. Using this it is much easier to browse without a mouse, not to mention faster. This was a feature that I really enjoyed using in Konqueror and missed.Unfortunately it uses the new QtWebKit dom API so it is only enabled if you are using the Qt master git branch or linking to QtWebKit Trunk. [Less]

Over on planetkde.org (and on some KDE mailing lists) there is a bunch of discussion about web browsers and KDE. A common theme was that rather then talking about KHTML v.s. Webkit it you should just get out there and code. In that spirit I ... [More] finished off my AccessKey branch and merged it in tonight. When you press the ctrl key little semi transparent boxes will appear all over the screen highlighting links. If you type the letter in the box that link will be followed. Using this it is much easier to browse without a mouse, not to mention faster. This was a feature that I really enjoyed using in Konqueror and missed.Unfortunately it uses the new QtWebKit dom API (which will be in Qt 4.6) so it is only enabled if you are using the Qt master git branch or linking to QtWebKit Trunk. [Less]

Over on planetkde.org (and on some KDE mailing lists) there is a bunch of discussion about web browsers and KDE. A common theme was that rather then talking about KHTML v.s. Webkit it you should just get out there and code. In that spirit I ... [More] finished off my AccessKey branch and merged it in tonight. When you press the ctrl key little semi transparent boxes will appear all over the screen highlighting links. If you type the letter in the box that link will be followed. Using this it is much easier to browse without a mouse, not to mention faster. This was a feature that I really enjoyed using in Konqueror and missed.Unfortunately it uses the new QtWebKit dom API (which will be in Qt 4.6) so it is only enabled if you are using the Qt master git branch or linking to QtWebKit Trunk. [Less]

Over on planetkde.org (and on some KDE mailing lists) there is a bunch of discussion about web browsers and KDE. A common theme was that rather then talking about KHTML v.s. Webkit it you should just get out there and code. In that spirit I ... [More] finished off my AccessKey branch and merged it in tonight. When you press the ctrl key little semi transparent boxes will appear all over the screen highlighting links. If you type the letter in the box that link will be followed. Using this it is much easier to browse without a mouse, not to mention faster. This was a feature that I really enjoyed using in Konqueror and missed.Unfortunately it uses the new QtWebKit dom API (which will be in Qt 4.6) so it is only enabled if you are using the Qt master git branch or linking to QtWebKit Trunk. [Less]