Just curious, what's the resource saving of QT_NO_ACTION turned on vs turned off?
--Steve ________________________________________ From: [email protected] [[email protected]] On Behalf Of Hausmann Simon (Nokia-D-Qt/Oslo) Sent: Thursday, April 08, 2010 4:45 AM To: [email protected] Cc: Suzuki Tasuku (Nokia-D-Qt/Tokyo) Subject: [webkit-qt] QtWebKit with reduced feature set for embedded platforms Hi, With Qt for embedded platforms we have the ability to disable various features in Qt to reduce the library size. The features largely evolve around not compiling certain classes, such as QMenu, QColorDialog or QAction, as well as more general features such as QObject properties. The features are controlled using defines, i.e. there's QT_NO_PROPERTIES, QT_NO_CONTEXTMENU, QT_NO_PRINTER. We have a few of these in place the code. Tasuku has been looking into compiling QtWebKit with less features enabled, such as properties and QActions. See https://bugs.webkit.org/show_bug.cgi?id=36529 and https://bugs.webkit.org/show_bug.cgi?id=36526 Adding the feature #ifdefs adds a maintenance burden and clutters the code. On the upside it makes it possible to use QtWebKit in much more restricted environments, with limited functionality though. What do you guys think about this? Do you feel this is a useful thing to have and maintain? Simon _______________________________________________ webkit-qt mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
