Description: A simple KDE web browser based on KParts. Designed to be fast, efficient, clean, and extensible.Last changelog:
0.5: * bugfixes * optimization * tags support * Tab reordering (middle click) and double-clicking opens a new tab * DOCUMENTATION! * Configuration dialog 0.4: I'd rather not try to account for them all, but: * Major code refactoring. * Individual tab history instead of browser-wide history. * Progress bar * Right-click context menu * Customizable home page (currently hidden config option) * Plugins now use KServiceTrader, instead of a hidden configuration option that points straight at the script. This allows plugin authors to specify metadata, and makes system administration easier.
0.3: * Basic Solid support (if the connection isn't connected, Eureka will wait). * Optimization * More bugfixing * 'Close Tab' button is now only shown when there is more than one tab opened * plugin support: use --install to install a plugin
0.2: * Bugfixes, including fixing a memory leak * Some code cleanup * The beginnings of Kross-based plugins * Now warns before exiting if multiple tabs are opened * Added keyboard shortcuts for 'New Tab' and 'Close Tab'
I really like it, almost everything essential
is there, however, I've come across a
few "quirks", dunno if all of them are
related to your code or if its related
to kparts...
I'm unable to login at opendesktop, just
shows the login dialog over again.
When clicking the "preview" screenshot
at opendesktop it crashes.
When only typed a word in locationbar
like "opendesktop" (usually searches
google on a lot of browsers when done
this), it crashes.
Also, I'd like to know whether middleclick
to open in new tab (or close tab) will
be available in the future?
And lastly, is there a google search bar
planned?
Sry for over 9000 questions, is just
I've tried most the browsers here
and this one caught my attention the
most :) I realize it's early in development
and this is very promising :)
Voted up.
//Robert
Looks great but Eureka and Foxkit looks to share the same goals (web browser, KDE integration, Kross support...)
Any chance to join your efforts ? :)
Simple suggestion of course, and thanks your for your work !
I'm not sure. I'd like to, but Foxkit and Eureka differ in one simple way: Eureka uses KParts to display pages (can use KHTML or WebKit), while Foxkit directly uses QWebKit. Otherwise, I would've just contributed to Foxkit ;).
Personally, yes, I would like to somehow unify efforts (extension compatibility, for example, is on my to-do list).
I did. The foxkit developer already said "At this point I'm still not sure if I'll end up using KParts or not, I still have to weigh the pros and cons of using them.". I've seen them both, and QWebKit provides features that KParts don't (for example, QWebView provides built-in support for back and forward navigation). Adding KPart support would probably make Foxkit's codebase more complex, especially if they want to continue to make use of QWebKit's extra features.
Ratings & Comments
6 Comments
I really like it, almost everything essential is there, however, I've come across a few "quirks", dunno if all of them are related to your code or if its related to kparts... I'm unable to login at opendesktop, just shows the login dialog over again. When clicking the "preview" screenshot at opendesktop it crashes. When only typed a word in locationbar like "opendesktop" (usually searches google on a lot of browsers when done this), it crashes. Also, I'd like to know whether middleclick to open in new tab (or close tab) will be available in the future? And lastly, is there a google search bar planned? Sry for over 9000 questions, is just I've tried most the browsers here and this one caught my attention the most :) I realize it's early in development and this is very promising :) Voted up. //Robert
Looks great but Eureka and Foxkit looks to share the same goals (web browser, KDE integration, Kross support...) Any chance to join your efforts ? :) Simple suggestion of course, and thanks your for your work !
I'm not sure. I'd like to, but Foxkit and Eureka differ in one simple way: Eureka uses KParts to display pages (can use KHTML or WebKit), while Foxkit directly uses QWebKit. Otherwise, I would've just contributed to Foxkit ;). Personally, yes, I would like to somehow unify efforts (extension compatibility, for example, is on my to-do list).
maybe Foxkit's author is just waiting that the webkit kpart is really finished ? You should investigate this ;-)
I did. The foxkit developer already said "At this point I'm still not sure if I'll end up using KParts or not, I still have to weigh the pros and cons of using them.". I've seen them both, and QWebKit provides features that KParts don't (for example, QWebView provides built-in support for back and forward navigation). Adding KPart support would probably make Foxkit's codebase more complex, especially if they want to continue to make use of QWebKit's extra features.
OK, thanks for the explanation and good hack then. Cheers