- Dillo-dev - lists.mailman3.com

[PATCH] bug in menu.c (SOLVED)
by Frank de Lange Oct. 16, 2003

Oct. 16, 2003

Stephan Goetter wrote: >Hi, > >I just got this, after opening a new tab, going to >http://www.foobar123.org/ (yes, it doesn't exist :) >and then trying to close the Tab. > >Program received signal SIGSEGV, Segmentation fault. >Menu_pick_url (widget=0x8158e80, client_data=0x8113f20) at menu.c:112 >112 gtk_object_remove_data(GTK_OBJECT (bw->menu_popup.over_image), "url2"); >(gdb) backtrace full >#0 Menu_pick_url (widget=0x8158e80, client_data=0x8113f20) at menu.c:112 > bw = (struct _BrowserWindow *) 0x8113f20 >#1 0x40142ef6 in gtk_marshal_NONE__NONE () from /usr/lib/libgtk-1.2.so.0 >No symbol table info available. >#2 0x40187e16 in gtk_signal_remove_emission_hook () from /usr/lib/libgtk-1.2.so.0 >No symbol table info available. >#3 0x40186f3b in gtk_signal_handlers_destroy () from /usr/lib/libgtk-1.2.so.0 >No symbol table info available. >#4 0x40184b8e in gtk_signal_emit () from /usr/lib/libgtk-1.2.so.0 >No symbol table info available. >... > >Greets, >Stephan > Found the cause. This error is present in the CVS version of Dillo as well, but there it does not matter much (probably why it was not discovered before). In menu.c:Menu_add(): if (callback != NULL) { gtk_signal_connect(GTK_OBJECT(menuitem), "activate", (GtkSignalFunc) Menu_pick_url, data); ^^^^ "data" should be "bw", as Menu_pick_url() needs a BrowserWindow* as second parameter. In CVS Dillo "data" (which is used as user data for callbacks) happens to be always set to "bw", so this bug did not manifest itself. In the patched version, some callbacks expect a DilloDoc* as parameter though... So Menu_pick_url() is called with a DilloDoc* instead of a BrowserWindow*... The fix is simple: <PATCH> diff -pruN dillo/src/menu.c dillo_patched/src/menu.c --- dillo/src/menu.c 2003-09-25 15:10:24.000000000 +0200 +++ dillo_patched/src/menu.c 2003-10-16 14:56:38.733763968 +0200 @@ -109,7 +109,7 @@ static GtkWidget * } if (callback != NULL) { gtk_signal_connect(GTK_OBJECT(menuitem), "activate", - (GtkSignalFunc) Menu_pick_url, data); + (GtkSignalFunc) Menu_pick_url, bw); gtk_signal_connect(GTK_OBJECT(menuitem), "activate", (GtkSignalFunc) callback, data); } </PATCH> Jorge, can you commit this patchlet to CVS? Cheers//Frank -- WWWWW ________________________ ## o o\ / Frank de Lange \ }# \| / +46-734352015 \ \ `--| _/ <Hacker for Hire> \ `---' \ +31-640037120 / \ frank(a)unternet.org / `------------------------' [ "Omnis enim res, quae dando non deficit, dum habetur et non datur, nondum habetur, quomodo habenda est." ]

2 1

Re: [Dillo-dev] [PATCH] version 1 of keyboard navigation patch
by Frank de Lange Oct. 16, 2003

Oct. 16, 2003

Glyn Kennington wrote: > I like most of it. But after a very short time, I've found some things > >that I think need improving. So, in order of decreasing importance: > >1) I've found a bug that will cause dillo to crash: > > Go to a page whose first link is in an alt-tagged image. (The one I've > been using for this bugreport is www.guardian.co.uk .) > > Press the key for `link DOWN'. This will make the image link the > current link (status bar reads "http://www.guardian.co.uk/0,6961,,00.html") > > Go to another page. This can be by clicking Home, Back etc, typing in > another URL, or activating a link on the current page. > > Once dillo is about to start rendering the new page, it dies with a > segfault. gdb tells me that it's at the end of Dw_image_destroy(): > g_free (image->alt_text); > >This crash still occurs if I move to the next link (outside the image) >before going to a different page. > > I have not been able to reproduce this yet, will try again and fix anything I find... But, as stated, it does not happen here... Could have something to do with your next remark? [ LIST: has anyone else seen this? ] >2) Patching problems. I know the email said `use cvs 14/10/2003', but >the patch filename includes the string 20031015, so I attempted to patch >against my just-updated checkout. This normally wouldn't be a problem >over the course of only a day, but today there was some change to the >arguments of a_Commands_set_selection which broke the patch. If you >could include on your webpage the exact date and time of the CVS >checkout, near the link to the patch, it would probably prevent this >sort of confusion from happening again. > > Hmmm... tricky. I'll add a GMT date/time to the CVS version to be used. The date-string on the patch is autogenerated by my patch scripts, it just tells the date I made a release. It is not necessarily related to the CVS date the patch is based on. Sometimes I make incremental changes to a patch without updating CVS. >3) The TODO mentions more bindings. Do you intend to make Back > bindable? > > I intend to make everything bindable. That is, everything which can be bound. That is 'the GTK+ way' of doing things... Cheers//Frank -- WWWWW ________________________ ## o o\ / Frank de Lange \ }# \| / +46-734352015 \ \ `--| _/ <Hacker for Hire> \ `---' \ +31-640037120 / \ frank(a)unternet.org / `------------------------' [ "Omnis enim res, quae dando non deficit, dum habetur et non datur, nondum habetur, quomodo habenda est." ]

3 2

Re: [Dillo-dev] [PATCH] version 11 of tab/frame patch, added keyboard navigation
by Frank de Lange Oct. 16, 2003

Oct. 16, 2003

Stephan Goetter wrote: >Hi, > >I just got this, after opening a new tab, going to >http://www.foobar123.org/ (yes, it doesn't exist :) >and then trying to close the Tab. > >Program received signal SIGSEGV, Segmentation fault. >Menu_pick_url (widget=0x8158e80, client_data=0x8113f20) at menu.c:112 >112 gtk_object_remove_data(GTK_OBJECT (bw->menu_popup.over_image), "url2"); >(gdb) backtrace full >#0 Menu_pick_url (widget=0x8158e80, client_data=0x8113f20) at menu.c:112 > bw = (struct _BrowserWindow *) 0x8113f20 >#1 0x40142ef6 in gtk_marshal_NONE__NONE () from /usr/lib/libgtk-1.2.so.0 >No symbol table info available. >#2 0x40187e16 in gtk_signal_remove_emission_hook () from /usr/lib/libgtk-1.2.so.0 >No symbol table info available. >#3 0x40186f3b in gtk_signal_handlers_destroy () from /usr/lib/libgtk-1.2.so.0 >No symbol table info available. >#4 0x40184b8e in gtk_signal_emit () from /usr/lib/libgtk-1.2.so.0 >No symbol table info available. >... > >Greets, >Stephan > > Hmmm, this did not happen here, but that was caused by me using a proxy (privoxy) which produces a nice 'not found' page... Will look in to it asap... Cheers//Frank -- WWWWW ________________________ ## o o\ / Frank de Lange \ }# \| / +46-734352015 \ \ `--| _/ <Hacker for Hire> \ `---' \ +31-640037120 / \ frank(a)unternet.org / `------------------------' [ "Omnis enim res, quae dando non deficit, dum habetur et non datur, nondum habetur, quomodo habenda est." ]

1 0

[PATCH] version 11 of tab/frame patch, added keyboard navigation
by Frank de Lange Oct. 16, 2003

Oct. 16, 2003

Hi'all, The next version (11) of my tab patch is ready (see bottom of this message for download instructions). The big new features are keyboard navigation and configurable key bindings (currently only for keyboard navigation and scrolling, more will be added later). See below for more information on these features. Keyboard navigation is also available in a separate patch, for those who do not want to apply the tab/frame patch. Watch the mailing list and/or see the patch website (http://www.geocities.com/ikbenfrank/) for more information. New features: - keyboard navigation! - configurable key bindings (for keyboard navigation and scrolling) Fixed bugs - solved the 'missing frames' problem for German (and other?) users. Stephan Goetter pointed me in the right direction (the German locale uses the "," as a decimal separator). Some behavioural changes with regard to stock (CVS) Dillo: - Shift-Ctrl-L (instead of Ctrl-L) for "open URL" dialog - Ctrl-L for "focus location bar" - Ctrl-S for "Save page As..." - Ctrl-U for "view source" while in a document, "clear entry" everywhere else (in stock Dillo this key is bound to "focus location bar" while in a document) - Ctrl-B for "Bookmark this page" - Alt-H for "Home" - "/" starts incremental search instead of normal search. For normal (non-incremental) search use Ctrl-F Support for the 0.7.3 branch has been dropped as of this version of this patch. Sorry, folks, but that is the price you pay for progress... Currently, both tab and frame support can be turned off completely, producing a smaller binary. I might (on request of other Dillo developers) remove the conditional compilation, thereby making tab and frame support a permanent feature of Dillo. If you want to keep the conditional compilation feature, speak out on the mailing list! Keyboard navigation can currently NOT be turned off, let me know if this is needed. Frameset (and iframe) support is enabled by default, it can be disabled using the configure option --enable-xhtml-dtd=strict. You can also use --enable-xhtml-dtd=transitional, which will give you iframe but no frameset support. The default option, --enable-xhtml-dtd=frameset, gives both iframe and frameset support. As usual, tab support can be disabled using --disable-tabs. What does not work yet: - the full_screen_off_button is not shown in frame documents. Use double-click instead to toggle the full screen setting... - the frameborder attribute works, but dw_gtk_scrolled_frame always draws a (focus) shadow around itself - even with the border size is set to 0. This can be solved in several ways - adding a 'borderless' attribute to dw_gtk_scrolled_frame, using a special borderless GTK theme for the widget, etc. In GTK2 this is all much easier (just set the widget's style's xthickness/ythickness to 0), but we're not there yet... - borderless frames can not be resized, even though Dillo always shows a thin border (see above). Who cares about resizing borderless frames? Mozilla does it, but I don't think this is an issue. Agree? - iframes always have a border (see above) Keyboard Navigation =================== You can use the keyboard to navigate links and controls in Dillo. In the default configuration, the following keys are used: Alt-Up: link UP Alt-Down: link DOWN Alt-Left: link LEFT Alt-Right: link RIGHT Enter: follow link or activate GTK+ widget Escape: unhighlight link In a non-frames version of Dillo the following keys are also used: Tab: NEXT link Shift-Tab: PREVIOUS link these keys are not bound by default in a frames-capable version of Dillo because they are used to navigate between frames. You are free to bind them (or any other key combination) to these functions though (see Keyboard bindings) Sometimes the result of link UP and link DOWN seems a bit unpredictable. This can happen when the next UP or DOWN link is currently not visible (below the bottom or above the top of the window). The screen coordinates for words are only known when they are in the visible area of the viewport, so off-screen links are accessed sequentially instead. Search and keyboard navigation ------------------------------ Keyboard navigation works with the Search feature: if search hits a link, it will be focused. Press <Enter> in the viewport to follow the link, <Esc> to unhighlight it. When using the status bar for search (an optional feature in the tabbed version of Dillo), press <Esc> to close the search entry followed by <Enter> to follow the link. A second <Esc> will unhighlight the focused link. Pressing <Enter> in the search entry (popup or status bar) repeats the search. History ------- The focus location is saved when navigating to another document in the same window or tab. This makes it possible to go back in history and continue to the next link on the page. Form fields ----------- The same keys used for link navigation work for form field navigation. Do note however that form fields, being embedded GTK+ widgets, can have their own bindings for some functions. As an example, the space bar is bound to the activate function in radio buttons. Keyboard bindings ================= It is possible to change the keyboard bindings used for keyboard navigation, either through editing the dillorc or by adding a section to any of the current GTK+ rc-files. The syntax is the same, the only difference is the addition of the preference keyword "key_bindings" in the dillorc and the fact that the bindings have to be enclosed in double quotes. An example of the configuration syntax can be found in the dillorc and on the mailing list. Tabs, Frames, Keyboard navigation and browser bloat =================================================== version: 0.8.0-pre patch: dillo-20031015-tabs.patch.gz unpatched: 294132 bytes patched, no tabs, no frames: 308404 bytes patched, with tabs, no frames: 315220 bytes patched, no tabs, with frames: 324852 bytes patched, with tabs, with frames: 333108 bytes (gcc 3.2.2, binutils 2.13.90.0.18, CFLAGS "-Os") The increase in size is due to the addition of keyboard navigation. If you want to be able to compile Dillo without this feature (it takes about 10 KB) let me know through the mailing list. Download instructions ===================== The patch is made against 20031014 CVS. Do not forget to run ./autogen.sh after applying the patch. You can find the patch on the usual (ad-happy, use an ad-blocking proxy or sane browser) site: http://www.geocities.com/ikbenfrank/ More specifically: Dillo 0.8.0-pre (CVS) ===================== http://www.geocities.com/ikbenfrank/dillo-20031015-tabs.patch.gz size: 85716 bytes (gzipped, as downloaded) 371416 bytes (uncompressed) md5sum: 358041a00feeef1706b81d24a985613a (gzipped, as downloaded) bf61b1bdb212c69c30ee1fa6fa74f729 (uncompressed) As always, check the site for the most recent version Cheers//Frank -- WWWWW ________________________ ## o o\ / Frank de Lange \ }# \| / +46-734352015 \ \ `--| _/ <Hacker for Hire> \ `---' \ +31-640037120 / \ frank(a)unternet.org / `------------------------' [ "Omnis enim res, quae dando non deficit, dum habetur et non datur, nondum habetur, quomodo habenda est." ]

4 5

RE: [Dillo-dev] FLTK
by Eric Gaudet Oct. 16, 2003

Oct. 16, 2003

> Hi Eric! > Hi Sebastian, > Only some remarks about my experiences. I'm only using Gtk 2.0 and > Pango 1.0, I'll update to see if it makes a difference. > > Startup time is a bit difficult to measure, since the disk cache state > etc. may influence this. What I found out: > ... As I said before, in my tests I always started with a dry run to make sure the libraries and files were loaded or buffered in RAM. The time differences between the first run and subsequent runs was very small in avarage, but could vary a lot. Also, as I said, startup time is slightly longer but still acceptable. If this was the only drawback with gtk2, I would be fine with it. > I've found no difference in drawing time, but this has only played a > bit time in dillo1 (at least for text). I've not configured anything > for Pango, and from what I see on the screen, anti-aliasing (which may > take much time) is turned off. > How do I turn off anti-aliasing? I'd like to try it again if you think this may speed-up redraws. > What *does* take far more time is the initial rendering, while > rewrapping is exactly as fast as before. This (and also that Pango is > only used for drawing, and determing the size of fonts and words) lets > me assume that Dw_page_shape_glyphs is not very efficient. I've tried > to track down this with gprof, but somehow the profile does not give > me much clues. Perhaps it is worth to optimize this code. (The > comparison is a bit unfair because of the different grades of > matureness :-) > I did't try rewrapping (changing the window's size), only scrolling down and up by one full page. I can try to rewrap and scroll line by line if you want. What is the purpose of Dw_page_shape_glyphs? Best, EG

2 1

Development
by Carlos Daniel Ruvalcaba Valenzuela Oct. 15, 2003

Oct. 15, 2003

Hi everyone It sems i lost a lot of the development cycle, now even plugins are implemented! Anyways, here is my wasted effort with dillo-0.7.3: * Fixed dpi.c capi.c, to handle launching multiple dpis via url, example dpi:/bm/ will launch bookmarks plaugs, dpi:/cfg/ will launch the configuration plugin. * Worked on dpilib a bunch of code to initialize comunications from a dpi to dillo, it works pretty well, also handles tag params, and url passed vars. * ddm_srv.c Dillo Download Manager, a download plugin using wget, will be able to download multiple files and show their progress in dpi:/ddm/downloads * cfg_srv.c Configuration, It can tweak a bunch of options for Dillo and DDM. Way back about a month i worked on a plugin daemon too. But with current changes i maded the daemon is not necesary, also dillo can load plugins if necesary. Any comments?, anyone wants the patches? Anyway, cheers. Carlos Daniel Ruvalcaba Valenzuela --------------------------------- Do You Yahoo!? Yahoo! Net: La mejor conexión a internet y 25MB extra a tu correo por $100 al mes.

2 1

Selection leak
by Jorge Arellano Cid Oct. 15, 2003

Oct. 15, 2003

Hi there! Finally the selection riddle is clear: there were some GTK+ warnings very seldomly appearing sometimes, but not in 0.7.3. In 0.7.3 one of the popups was being set as the permanent owner for all the selections, and it was initialized at browser window creation time. As 0.7.3 leaked the popups (not destroying them with the window) the widget remained valid all the time! In CVS the popup leak is fixed, so the selection owner can be destroyed with its window, and thus the warnings. I fixed it like I originally suggested: > Perhaps it'd be better to add a widget parameter to > a_Commands_set_selection: > > void a_Commands_set_selection(GtkWidget *widget, gchar *str) > > So we can set the owner properly. AFAIU the owner gets the > "clear selection" event on the handler it set. For instance, when > the user selects text from the location bar, the "clear > selection" callback is called. This can help to set a custom > handler for when the selected text comes from the rendered area. > This new handler can toggle the selection highlighting off, and > then call a_Commands_clear_selection_callback() to finish the > work. Sebastian: I used "GTK_BIN(bw->docwin)->child" as the selection owner for the rendered area. Is there a better candidate? Commited! Cheers Jorge.-

1 0

Re: [Dillo-dev] Development
by Scorpio Rising Oct. 15, 2003

Oct. 15, 2003

Behold, Carlos Daniel Ruvalcaba Valenzuela scribed in runic symbols on a tube chassis: > * ddm_srv.c Dillo Download Manager, a download plugin using wget, will be able to download multiple files and show their progress in dpi:/ddm/downloads Oy! Could I use this one :-)

1 0

[PATCH] version 1 of keyboard navigation patch
by Frank de Lange Oct. 15, 2003

Oct. 15, 2003

Hi'all, The first version (1) of my keyboard navigation patch is ready. See the end of this message for download instructions. Do note that the tab/frame patch already contains this functionality, so there is no need (and no way) to apply this patch on top of that or the other way around. The patch adds Keyboard navigation with configurable key bindings to (the CVS version of) Dillo. Please test it and let me know what you (don't) like. Even though keyboard navigation does not make much sense with devices without keyboards (pda's, etc), there is no configure option to disable it. Let me know if there is a need for such an option (it is easily implementable). Personally I think there is... For keyboard navigation to work Dillo has to track the position of individual words in a document, which increases memory overhead with 4 bytes per word. However, there seems to be some animosity against the added complexity of conditionally compiled code (enclosed in #ifdef ... #endif). More information on keyboard navigation can be found in the document "Keyboard_Navigation.txt" in the doc/ directory which I'll just reproduce it here: Keyboard Navigation =================== You can use the keyboard to navigate links and controls in Dillo. In the default configuration, the following keys are used: Alt-Up: link UP Alt-Down: link DOWN Alt-Left: link LEFT Alt-Right: link RIGHT Enter: follow link or activate GTK+ widget Escape: unhighlight link In a non-frames version of Dillo the following keys are also used: Tab: NEXT link Shift-Tab: PREVIOUS link these keys are not bound by default in a frames-capable version of Dillo because they are used to navigate between frames. You are free to bind them (or any other key combination) to these functions though (see Keyboard bindings) Sometimes the result of link UP and link DOWN seems a bit unpredictable. This can happen when the next UP or DOWN link is currently not visible (below the bottom or above the top of the window). The screen coordinates for words are only known when they are in the visible area of the viewport, so off-screen links are accessed sequentially instead. Search and keyboard navigation ------------------------------ Keyboard navigation works with the Search feature: if search hits a link, it will be focused. Press <Enter> in the viewport to follow the link, <Esc> to unhighlight it. When using the status bar for search (an optional feature in the tabbed version of Dillo), press <Esc> to close the search entry followed by <Enter> to follow the link. A second <Esc> will unhighlight the focused link. Pressing <Enter> in the search entry (popup or status bar) repeats the search. History ------- The focus location is saved when navigating to another document in the same window or tab. This makes it possible to go back in history and continue to the next link on the page. Form fields ----------- The same keys used for link navigation work for form field navigation. Do note however that form fields, being embedded GTK+ widgets, can have their own bindings for some functions. As an example, the space bar is bound to the activate function in radio buttons. Keyboard bindings ================= It is possible to change the keyboard bindings used for keyboard navigation, either through editing the dillorc or by adding a section to any of the current GTK+ rc-files. The syntax is the same, the only difference is the addition of the preference keyword "key_bindings" in the dillorc and the fact that the bindings have to be enclosed in double quotes. As an example, this configuration (in gtkrc) uses the numerical keypad for link navigation: binding "keypad-keys" { bind "KP_Add" { "focus_move" (0) } bind "KP_Subtract" { "focus_move" (1) } bind "KP_8" { "focus_move" (2) } bind "KP_2" { "focus_move" (3) } bind "KP_4" { "focus_move" (4) } bind "KP_6" { "focus_move" (5) } bind "KP_Enter" { "focus_activate" () } } class "GtkDwScrolledFrame" binding "keypad-keys" You can also use 'widget "*dillo-content" instead of 'class "GtkDwScrolledFrame" if you prefer to use widget names: widget "*dillo-content" binding "keypad-keys" This one (in dillorc, note the enclosing double quotes, the use of single quotes and the preference name 'key_bindings') makes Dillo behave like the vi editor when it comes to link navigation: key_bindings = "binding 'vi-keys' { bind 'k' { 'focus_move' (2) } bind 'j' { 'focus_move' (3) } bind 'h' { 'focus_move' (4) } bind 'l' { 'focus_move' (5) } } class 'GtkDwScrolledFrame' binding 'vi-keys'" The numerical values after "focus_move" are actually GTK enumeration values, but the current implementation does not support this. It would of course look much better to be able to write "focus_move" (GTK_DIR_DOWN) instead of "focus_move" (3)... It is also possible to bind a sequence of actions to a single keypress by adding more actions after the first. Bugz^Hs ======= - Image links without alt text do not work with keyboard navigation. - Image links with alt text work, but Dillo is currently not able to scroll to them. This can lead to 'hidden' focused links, use the scroll keys or scroll bars to bring them in to view. This problem is shared with the Search feature. It is caused by a deficiency in the widget iterator function which is used for scrolling. - The sometimes unpredictable behaviour of link UP/DOWN can be classified as a bug. Or not. It is probably hard to solve this. The root cause is the use of incremental display in dw_page, which is in itself a good feature. To good to mess it up with some hack to get each and every link in the right place before using keyboard navigation. TODO ==== Well, apart from fixing those bugs... Maybe merge focus with search, they have quite a lot in common. This would save some code and memory. It would also mess up the current design, so maybe this is not such a good idea. Add more GTK+ bindings, replacing current key_press event handling. ... Download instructions ===================== There is currently only one version of the patch, made against 20031014 CVS. Sorry, no 0.7.3 support (yet...). As always, have a look at the patch website (http://www.geocities.com/ikbenfrank/) for the latest version of the patch. This patch does NOT apply on top of the tab/frame patch, and the tab/frame patch does not apply on top of this one! The tab/frame patch already contains this functionality, so it is not needed. Also, there is some overlap in the patched files, so I'd have to create a special version of this patch for this purpose. http://www.geocities.com/ikbenfrank/dillo-200310142300-kbnav.patch.gz size: 14336 bytes (gzipped, as downloaded) 62481 bytes (uncompressed) md5sum: 06c21168960cc5de12437ab4abff6d45 (gzipped, as downloaded) a1317f63190ad0df9501bbb257f8c137 (uncompressed) Cheers//Frank -- WWWWW ________________________ ## o o\ / Frank de Lange \ }# \| / +46-734352015 \ \ `--| _/ <Hacker for Hire> \ `---' \ +31-640037120 / \ frank(a)unternet.org / `------------------------' [ "Omnis enim res, quae dando non deficit, dum habetur et non datur, nondum habetur, quomodo habenda est." ] -- WWWWW ________________________ ## o o\ / Frank de Lange \ }# \| / \ \ `--| _/ <Hacker for Hire> \ `---' \ +46-734352015 / \ frank(a)unternet.org / `------------------------' [ "Omnis enim res, quae dando non deficit, dum habetur et non datur, nondum habetur, quomodo habenda est." ]

1 0

RE: [Dillo-dev] FLTK
by Eric Gaudet Oct. 14, 2003

Oct. 14, 2003

> Please back your opinions with links, docs, facts or with > whatever helps better to understand the point. Maybe a single > email can show there's no way to do it, or maybe not! > Two applications I used to run regularly when they were on gtk1.2 were ported to gtk2.0: pan and edonkey2000-gtk. I'm not using them anymore, because their rendering became painfully slow: scrolling the lists down takes several seconds to refresh on my 300MMX laptop. After doing some research, is seems that Pango is the culprit: rendering unicode needs some advanced graphic operation also slows down any text rendering. As I yet have to see a fast application using it, I would recommend NOT going with gtk2.0 for Dillo. Best, Eric

2 1