Changes between Version 6 and Version 7 of HackingGtk
- Timestamp:
- Nov 30, 2007, 9:04:18 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
HackingGtk
v6 v7 55 55 * Check function parameters with g_return_if_fail() and g_return_val_if_fail() 56 56 57 * Neveruse the abbreviation "URL" or "url" in any public API headers or documentation. Instead, use "URI" or "uri". This is a strong convention in GLib/GTK+ which deviates from the one used in WebCore and other WebKit ports.57 * Don't use the abbreviation "URL" or "url" in any public API headers or documentation. Instead, use "URI" or "uri". This is a strong convention in GLib/GTK+ which deviates from the one used in WebCore and other WebKit ports. 58 58 * Recommendation: Internally, relevant gchar* variables to be passed to or from the user should also be named "uri" until parsed into a KURL or WebCore data structure, at which point they should be called "url". 59 59 … … 68 68 The strategy here is to develop a GObject-based interpretation of the Objective-C API combined with experience working with GtkTextView, GtkHtml and gtkmozembed. This allows us to benefit from the maturity of a widely-deployed API, but demands extra caution not to adopt any of the baggage or legacy that might be present for backward compatibility only. The Win port is also a useful resource but is less suitable for direct inspiration since it hasn't been deployed as a stable API yet and has a large API footprint that would be difficult to support in the long term. 69 69 70 === WebKit Page===70 === WebKitWebView === 71 71 72 This will likely soon be renamed to WebKitWebView (http://bugs.webkit.org/show_bug.cgi?id=15691) matchingGtkTextView, GtkTreeView etc. on the GTK+ side and WebView in the Mac and Win ports of WebKit.72 Formerly named WebKitPage (http://bugs.webkit.org/show_bug.cgi?id=15691). Name matches GtkTextView, GtkTreeView etc. on the GTK+ side and WebView in the Mac and Win ports of WebKit. 73 73 74 === WebKit Frame ===74 === WebKitWebFrame === 75 75 76 Currently very similar to WebFrame, this is a headless representation of a browser frame, rather than a GtkWidget like WebKitPage.76 Formerly WebKitFrame. Currently very similar to Mac WebFrame, this is a headless representation of a browser frame, rather than a GtkWidget like WebKitWebView. 77 77 78 78 === WebKitNetworkRequest === … … 82 82 === WebKitWebSettings === 83 83 84 The future of WebKitWebSettings is uncertain . We might not want to do settings like this at all.84 The future of WebKitWebSettings is uncertain (http://bugs.webkit.org/show_bug.cgi?id=16219). We might not want to do settings like this at all. 85 85 86 86 == The build bots ==