- Dillo-dev - lists.mailman3.com

CSS speed
by Johannes.Hofmann＠gmx.de Jan. 15, 2009

Jan. 15, 2009

Hi, pages with complex CSS feel a bit slow with the current css-prototype and gprof shows a huge number of CssSelector::match() calls. Attached is a patch that tries to improve that by: * putting CssSelectors into hashtables so that we only need to match against a small subset of CssSelectors. * avoiding repeated matches of CssSimpleSelectors against the same part of the doctree. Please test and report if there is a real world speedup. Cheers, Johannes

2 4

Dillo 2 in Tiny Core Linux
by xentalion＠gmail.com Jan. 15, 2009

Jan. 15, 2009

Hello, Just wanted to let you that I've built a package of Dillo 2 for Tiny Core Linux. http://www.tinycorelinux.com/ It is now in the repositories for Tiny Core. :D Dillo 2 doesn't use any OpenGL does it? I compiled FLTK 2 without OpenGL support, and I didn't know if that would be a problem. Thanks, Colin

2 1

patch: focus URL opened from command line
by corvid＠lavabit.com Jan. 14, 2009

Jan. 14, 2009

I see there's a new entry in the bug tracker reporting that after opening multiple URLs from the command line, shift-right and shift-left do not work immediately. What do you think of something like the attached patch? The downside is that it wastes cycles when you click on a link, but I was reluctant to let dillo.cc know about this UI stuff.

1 0

CSS freeze
by jcid＠dillo.org Jan. 13, 2009

Jan. 13, 2009

Hi, Current and former CSS protos freeze on this page: http://www.instantfundas.com/2007/12/5-opera-tricks-you-did-not-know-about.… -- Cheers Jorge.-

2 3

IMG ratio
by jcid＠dillo.org Jan. 11, 2009

Jan. 11, 2009

Hi Johannes, Now that I have the image process mostly in my head, I'd like to hook correct image ratio scaling when only one of width/height is given. I see scaling done with the styleengine in a_Html_add_new_image but 'props' goes away when popping the tag. How do I handle this? Do I have to preserve props in the stack until I have the final data, or is there another way? Please explain. -- Cheers Jorge.-

3 18

Blimey, when was this fixed? Selections are fast!
by onepoint＠starurchin.org Jan. 11, 2009

Jan. 11, 2009

I used to complain that drawing the text selection was desperately slow when I dragged the mouse across the contents of a table with two columns and very many rows. Today I suddenly realised that this hadn't bothered me for a while, so I checked the problem page and indeed the selection now draws itself as fast I can drag the mouse. Big thanks to whoever fixed this performance bug! Regards, Jeremy Henty

1 0

RE: Dillo in Debian
by devidfil＠gmail.com Jan. 9, 2009

Jan. 9, 2009

Hi, I'm the current dillo Debian maintainer. I know, dillo 2.0 isn't in Debian right now but it isn't caused by me, fltk2 package is missing in Debian so I can't upload the 2.0 version right now. However I've done the fltk2 package for Debian and if all is ok it will uploaded (and accepted) in Debian as soon as possible (but it won't be in Lenny). If you will switch dillo to fltk1.3 then the problem will be the same because actually Debian doesn't have the 1.3 version of fltk (only 1.1) so I will need to work on a new package for fltk1.3 and this will require time (there is no a good documentation about how to work on a static lib package). So please continue to use fltk2. I'm sorry for the delay. Devid Antonio Filoni

1 0

one more crash
by Johannes.Hofmann＠gmx.de Jan. 9, 2009

Jan. 9, 2009

Sorry, but I'm seeing one more crash with current css-prototype. I think it has to do with abdae95b1c9e. I get it often - but not always e.g. on www.spiegel.de. Somehow layout is not set properly in the Image widget. Below is the stack. Cheers, Johannes Program terminated with signal 11, Segmentation fault. #0 0x08073f8e in dw::core::Layout::createImgbuf (this=0x3, type=dw::core::Imgbuf::RGB, width=140, height=80) at ../dw/layout.hh:241 241 return platform->createImgbuf (type, width, height); (gdb) bt #0 0x08073f8e in dw::core::Layout::createImgbuf (this=0x3, type=dw::core::Imgbuf::RGB, width=140, height=80) at ../dw/layout.hh:241 #1 0x0805f016 in a_Dicache_set_parms (url=0x28fa2a00, version=1, Image=0x2952d040, width=140, height=80, type=DILLO_IMG_TYPE_RGB) at dicache.c:268 #2 0x08072f2e in Jpeg_write (jpeg=0x28f85000, Buf=0x28f97000, BufSize=8000) at jpeg.c:299 #3 0x08072df4 in Jpeg_callback (Op=0, Client=0x297b4e20) at jpeg.c:246 #4 0x0805f407 in a_Dicache_callback (Op=0, Client=0x297b4e20) at dicache.c:396 #5 0x0805de7a in Cache_process_queue (entry=0x2952d080) at cache.c:1134 #6 0x0805d624 in a_Cache_process_dbuf (Op=0, buf=0x2955d000 "Z121\034\002\n", buf_size=7930, Url=0x2952d200) at cache.c:856 #7 0x08060af9 in a_Capi_ccc (Op=2, Branch=2, Dir=1, Info=0x294d6b40, Data1=0x286bb5b0, Data2=0x80fb16c) at capi.c:596 #8 0x08059f38 in a_Chain_fcb (Op=2, Info=0x294d6740, Data1=0x286bb5b0, Data2=0x80fb16c) at chain.c:112 #9 0x080794d2 in Dpi_parse_token (conn=0x2952d240) at dpi.c:219 #10 0x080797b2 in Dpi_process_dbuf (Op=0, Data1=0x286bbca0, conn=0x2952d240) at dpi.c:278 #11 0x0807a545 in a_Dpi_ccc (Op=2, Branch=2, Dir=1, Info=0x294d6740, Data1=0x286bbca0, Data2=0x0) at dpi.c:668 #12 0x08059f38 in a_Chain_fcb (Op=2, Info=0x294d6fa0, Data1=0x286bbca0, Data2=0x0) at chain.c:112 #13 0x0807b197 in a_IO_ccc (Op=2, Branch=2, Dir=1, Info=0x294d6fa0, Data1=0x294d6560, Data2=0x0) at IO.c:414 #14 0x0807abdd in IO_read (io=0x294d6560) at IO.c:201 #15 0x0807acf7 in IO_callback (io=0x294d6560) at IO.c:266 #16 0x0807ad80 in IO_fd_read_cb (fd=64, data=0x8e) at IO.c:287 #17 0x080c8c99 in fltk::wait () #18 0x080c8e49 in fltk::run () #19 0x0804f19c in main (argc=1, argv=Cannot access memory at address 0x3c ) at dillo.cc:334 (gdb)

2 5

Dillo in Debian
by jcid＠dillo.org Jan. 8, 2009

Jan. 8, 2009

Hi Wookey, A post in dillo-dev made me aware of this thread: http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=510348 Thanks for your comment ;-) Some technical facts (all available from dillo.org) * dillo-0.8.x is unmaintained * dillo-2.x is the official stable branch * dillo-2.x uses FLTK2 not GTK2 as stated in the thread IMHO it'd be good to have dillo-0.8.x in Lenny, at least until dillo-2.x makes its way into Debian. We've been working on this branch for more than a year and it's way better than the former (details in the website). I'm aware of the problem distros have with including statically linked packages, and it looks like dillo-2.x will be left out of them until this issue is solved. Unfortunately FLTK-2.0 is stalled and an official release of it is nowhere near in the future. OTOH, an active set of developers is pushing FLTK-1.3.x very fast. This branch provides more or less the same FLTK-2.0 does. It's being actively developed, is less buggy and more stable, and will most probably be released soon (I'm yet to ask the team about dates). At some point in time we'll be migrating to FLTK-1.3.x (it has almost the same API), and hopefully then it'll be easier to include dillo in Debian. If you make progress with the certificate patch, please let us know. We're fully devoted to CSS now, and have no SSL expert in the team :( -- On a personal level, I'd love to have Dillo used in Debian as a help browser. This is, since a long time ago I've noticed applications come with almost no help (F1 button in the old days) and help drives you to an "About" window. But OTOH they have very good HTML docs (usually in usr/share/), that could provide for accurate context-sensitive help pages. The problem is they don't hook a web browser to the help button because a bloated app. that takes a long time to start, only to crawl the computer afterwards, is the last thing a developer hopes as her end user experience. There's the possibility of having a simple API to remote control the browser so the same instance is used. Dillo is fast, lean, and low on library dependencies. Any doubts, just don't hesitate to ask. -- Cheers Jorge.-

2 1

dillo about to be dropped from debian
by r00t＠constancy.org Jan. 8, 2009

Jan. 8, 2009

FYI: http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=510348 it seems that dillo is about to be dropped from debian, because * ssl lacks proper certificate verification * it still uses gtk1.2 (personally, the first never bothered me, and i consider the second a _feature_) Greetings, Thorben Thuermer

1 0