January 2013 - Dillo-dev - lists.mailman3.com

line wrap for Japanese

by furaisanjin＠gmail.com

Hello all. It seems that change set de05508cbbbd causes the line wrap problem for Japanese. Certain lines become very long and I don't see appropriate line wrap in the middle. Regards, furaisanjin

Jan. 21, 2013

[patch] Scrollbar thickness from dillorc

by podarcis＠lavabit.com

> Just curious whether you've experimented with incorporating > Fl::scrollbar_size() into this. > My initial idea was indeed to just set Fl::scrollbar_size() from the prefences and use it from the rest of the code. But then I decided against, because of several reasons: - there is code in FltkViewport that (though unused) tries to make different vertical/horizontal scrollbar widths possible. - the current code seems not to use any of the FLTK scrollbar_size() methods, not even Fl_Scrollbar::scrollbar_size(), so I thought this is intentional. - anyway I wanted the change to be small and close to the existing implementation. > Aside: A few years ago, there was a little bit of discussion now and > then about improving the UI for touch, but unfortunately it would all > die down without us getting much further than "Hmm, that's an > interesting idea..." > Yes, of course, if you want to make the rest of the UI also fit for touchscreen then there's much to do. All those tiny buttons are unsuitable. I mostly intend to use dillo in fullscreen mode, where all controls are hidden, so scrollbars are nearly the only problem. Cheers, podarcis _______________________________________________ > Dillo-dev mailing list > Dillo-dev at dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

Jan. 20, 2013

[patch] Scrollbar thickness from dillorc

by corvid＠lavabit.com

podarcis wrote: > Scrollbars currently have the hardcoded thickness 15. This can be too > small to operate dillo on large screens or with fingers on a touch > screen. > > The supplied patch does the following: > > - Adds the prefence "scrollbar_tickness" to dillorc. > > - Reads the value into the prefences > (Note: added a type UINT32 to prefsparse.cc) > > - Sets this value to the FltkViewport with the new > method FltkViewport::setScrollbarThickness(). > > Note: I deliberately did no check for value 0, which can therefore be > used to make the scrollbars invisible. Scrolling can then still be > achieved with the cursor keys. This could be called a feature. Just curious whether you've experimented with incorporating Fl::scrollbar_size() into this. Aside: A few years ago, there was a little bit of discussion now and then about improving the UI for touch, but unfortunately it would all die down without us getting much further than "Hmm, that's an interesting idea..."

Jan. 20, 2013

[patch] Scrollbar thickness from dillorc

by podarcis＠lavabit.com

Scrollbars currently have the hardcoded thickness 15. This can be too small to operate dillo on large screens or with fingers on a touch screen. The supplied patch does the following: - Adds the prefence "scrollbar_tickness" to dillorc. - Reads the value into the prefences (Note: added a type UINT32 to prefsparse.cc) - Sets this value to the FltkViewport with the new method FltkViewport::setScrollbarThickness(). Note: I deliberately did no check for value 0, which can therefore be used to make the scrollbars invisible. Scrolling can then still be achieved with the cursor keys. This could be called a feature. Cheers, podarcis

Jan. 20, 2013

drawing highlighting

by corvid＠lavabit.com

For highlighting in a single word:

Jan. 19, 2013

[patch] disable SSLv2 support

by Johannes.Hofmann＠gmx.de

On Fri, Jan 18, 2013 at 01:57:49AM +0400, p37sitdu at lavabit.com wrote: > http://www.inventati.org/noname/dillo/https-no-SSLv2.patch > > I have found HTTPS server that Dillo was unable to connect to. > > After defining SILENT to 0 in https.c I found that SSL_connect > failed. Adding ERR_print_errors_fp(stderr) showed error > "SSL23_GET_SERVER_HELLO:unknown protocol". > > Disabling SSLv2 support fixed the problem for me. And SSLv2 is > insecure so it must be disabled anyway. committed! Thanks, Johannes

Jan. 18, 2013

[patch] dWrite

by p37sitdu＠lavabit.com

http://www.inventati.org/noname/dillo/dwrite.patch Removed Dpi_blocking_write from src/IO/dpi.c and moved similar code to dlib. Also fixes ckd_write in dpid/dpid_common.c: it handled EINTR, but did not handle situation when number of bytes written is less then requested. Now it uses dWrite.

Jan. 18, 2013

[patch] disable SSLv2 support

by p37sitdu＠lavabit.com

http://www.inventati.org/noname/dillo/https-no-SSLv2.patch I have found HTTPS server that Dillo was unable to connect to. After defining SILENT to 0 in https.c I found that SSL_connect failed. Adding ERR_print_errors_fp(stderr) showed error "SSL23_GET_SERVER_HELLO:unknown protocol". Disabling SSLv2 support fixed the problem for me. And SSLv2 is insecure so it must be disabled anyway.

Jan. 17, 2013

chain.c cleanup

by p37sitdu＠lavabit.com

http://www.inventati.org/noname/dillo/chain-cleanup.patch 1. Replaced dNew with dMalloc and dNew0 with dMalloc0. This way it is possible to use (sizeof *var) instead of repeating variable type. By the way, when 'count' is constant, dMalloc is easier to use, and when count is not constant, integer overflow can happen in dNew during multiplication. It looks like there are no such errors, but I think check should be added or, better, dCalloc can be introduced so libc checks for such cases. 2. Replaced #defines with enums and made them uppercase so it is easier to distinguish them from variables. This style is already used in most modules. IO should be fixed too, probably. 3. Moved duplicate code from a_Chain_fcb and a_Chain_bcb to Chain_cb. Anonymous structures for connections (forward or backward) are introduced in ChainLink structure for this purpose. 4. Removed unused a_Chain_unlink function. Chain links are just dFreed instead. Anyway, there is no function to connect existing links back, so disconnected link can only be dFreed. 5. Replaced AtoB_branch and BtoA_branch parameters of a_Chain_link_new with single Branch parameter. They were always equal anyway, and using different branch identifiers for one connection makes no sense, as branch ID is used to distinguish between Answer and Query chains. Branch parameter can be eliminated completely by separating existing CCC callbacks into answer and query callbacks. Currently instead of two functions we have one with if (Branch == 1) { ... } else { ... }

Jan. 17, 2013

CustChoice

by corvid＠lavabit.com

I was looking into why the search dialog would no longer let me tab to the search engine list and press down arrow to switch between them... It seems that, once Jorge added a CustChoice in fltkui.cc, the dialog code started to use _that_ one and not its own. (I would've expected something to complain about there being two CustChoice::handle()s in that case...) Would it be considered incorrect in any way if fltkui.cc's CustChoice and CustInput2 were put inside dw::fltk::ui?

Jan. 16, 2013