Ubuntu QA:
BlogBrainstormPackage status
Log in
Ubuntu QA
The Ubuntu community has contributed 22823 ideas, 138726 comments, 2639112 votes
Idea sandbox Idea sandbox
Popular ideas Popular ideas
Ideas in development Ideas in development
Implemented ideas Implemented ideas
Idea #15345: Gecko as KPart or Firefox in Qt

Written by Dinth the 6 Nov 08 at 23:32. Related project: Konqueror. Status: New
Rationale
It would be nice to have Gecko Qt port as KPart in KDE.

Currently, for webdevelopers either GNOME nor KDE doesn't provide complete set of tools for website development (HTML, CSS(!!), JS, PHP, etc) - GNOME is lacking something like Quanta in Gtk, etc, and KDE is lacking only native Firefox support to test and debug/make css corrections with Firebug.

I think the best way to resolve this would be Gecko as KPart (if it would be possible to run Firebug on Konqueror then), so developer could test css/layout of website on three different rendering engines with one app.

2
votes
up equal down
Solution #1: Auto-generated solution of idea #15345
Written by Dinth the 6 Nov 08 at 23:32.
Ubuntu Brainstorm was updated in January 2009. Since the idea #15345 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!

Propose your solution

Attachments
No attachments.


Duplicates


Comments
dino wrote on the 7 Nov 08 at 11:03
whats wrong with webkit?

Dinth wrote on the 7 Nov 08 at 15:42
Because all my clients for CSS layout/CMS implementations want to have their projects optimized mainly for Gecko, secondly for Internet Explorer 6/7 (i handle this with Wine), and sometimes Opera. Any of my heretofore clients even by himself was checking look of webpage that i've made on Safari - so for what i would optimize my projects for WebKit?

Dinth wrote on the 7 Nov 08 at 15:55
Sorry for double comment but i should add also some kind of conclusion to my last post.

Page owners doesn't bother about how their sites look in WebKit - for them only important is if webpages work in FF/IE, so CSS/layout "cutters" (how would be PSD cutting in english? :) ) and PHP coders also don't bother. It's only luck if most of the pages work good in Safari, so how anyone can call Webkit as good, universal and properly rendering engine when its working depends on luck ? ;)


Post your comment