April 2014 - Dillo-dev - lists.mailman3.com

Dillo and Irix
by diegel＠work.de 25 Sep '14

25 Sep '14

Hello, I just started another attempt to port dillo to Irix. With gcc 4.7 it compiles without any serious warnings. It starts and about:splash shows up correctly, But if you want to use it something goes wrong: ftp works without problems. files show up if the path is very short (less than 32 bytes). If you browse directories and you want to change from /tmp to /tmp/x for example. I changes to /x http doesn't work at all. If you go to a non existing url. For example: http://test.yy you get the following console output, but nothing happens in the dollo window: Nav_open_url: new url='http:test.yy' a_Capi_ccc : OpStart [2B] Info=10262fa8 Flags=0 a_Dpi_ccc : OpStart [2B] Info=10262da0 Flags=0 a_IO_ccc : OpStart [2B] Info=10262e90 Flags=0 a_Capi_ccc : OpStart [1B] Info=10262eb8 Flags=0 a_Http_ccc : OpStart [1B] Info=10262f80 Flags=0 a_IO_ccc : OpStart [1B] Info=10262e40 Flags=0 Http_must_use_proxy: http:test.yy NO DNS error: HOST_NOT_FOUND Dns_server [0]: is (nil) a_IO_ccc : OpAbort [1B] Info=10262e40 Flags=0 a_Capi_ccc : OpAbort [1F] Info=10262eb8 Flags=0 a_Capi_ccc : OpAbort [2B] Info=10262fa8 Flags=0 a_Dpi_ccc : OpAbort [2B] Info=10262da0 Flags=0 a_IO_ccc : OpAbort [2B] Info=10262e90 Flags=0 If you are opening an existing url like dillo.org it puts out: Nav_open_url: new url='http://www.dillo.org/' a_Capi_ccc : OpStart [2B] Info=10262fd0 Flags=0 a_Dpi_ccc : OpStart [2B] Info=10262f08 Flags=0 a_IO_ccc : OpStart [2B] Info=10262e68 Flags=0 a_Capi_ccc : OpStart [1B] Info=10262ee0 Flags=0 a_Http_ccc : OpStart [1B] Info=10262e90 Flags=0 a_IO_ccc : OpStart [1B] Info=10262f30 Flags=0 Http_must_use_proxy: http://www.dillo.org/ NO Dns_server [0]: www.dillo.org is 85.214.105.140 Connecting to 85.214.105.140 a_IO_ccc : OpSend [1B] Info=10262f30 Flags=0 a_Capi_ccc : OpSend [1F] Info=10262ee0 Flags=0 a_Capi_ccc : OpSend [2B] Info=10262fd0 Flags=0 a_Dpi_ccc : OpSend [2B] Info=10262f08 Flags=0 a_IO_ccc : OpSend [2B] Info=10262e68 Flags=0 http, referer='Referer: http://www.dillo.org/ ' Query: {GE} a_IO_ccc : OpSend [1B] Info=10262f30 Flags=0 and after some seconds: a_IO_ccc : OpEnd [2F] Info=10262e68 Flags=0 a_Dpi_ccc : OpEnd [2F] Info=10262f08 Flags=0 a_Capi_ccc : OpEnd [2F] Info=10262fd0 Flags=0 a_Capi_ccc : OpEnd [1B] Info=10262ee0 Flags=0 a_Http_ccc : OpEnd [1B] Info=10262e90 Flags=0 a_IO_ccc : OpEnd [1B] Info=10262f30 Flags=0 but nothing happens in the dillo window. I would be very happy to get any hint what is going wrong here. Thanks you, Jan

5 21

HTTP persistent connections / keep-alive
by eocene＠gmx.com 12 Jul '14

12 Jul '14

I have been experimenting with persistent connections for http, and wanted to see what your thoughts were. This has been working well enough for me: http://flpsed.org/hgweb/eocene_persistent_connections/ Why? To be a good internet citizen, tcp slow-start, etc. Johannes gave it a try and said it performed well. Initially I let FDs stick around even if I didn't immediately have new queries for them. When the server closed it, I'd get EPIPE on the write side and... I think it was ECONNRESET on the read side, send the OpEnd around ccc, and that worked all right and wasn't too messy. But then I wanted to handle the case where a FD sits idle and we try to reuse it and it fails. Sending the notifications around and getting everything back in a state where we could try again with a new connection was looking like it would be very messy. So I trimmed it all down so that, when we have our full reply, we reuse the FD if we already have something queued that can use it, and if not we just close the connection.

1 1

[jcid@dillo.org: Commit 3626. Redraw problems]
by jcid＠dillo.org 04 May '14

04 May '14

Hi, FYI. -- Cheers Jorge.-

3 19

More problem pages
by onepoint＠starurchin.org 02 May '14

02 May '14

I updated and rebuilt a few minutes ago and though thecode is shaking out nicely there are still some problems. Layout thrashes: http://www.nature.com/nature/journal/v508/n7496_supp/full/508S66a.html CPU thrashes for a long time but eventually calms down: http://www.sciencebasedmedicine.org/microwaves-and-nutrition/ Regards, Jeremy Henty

3 4

Gamma error in picture scaling
by sgeerken＠dillo.org 30 Apr '14

30 Apr '14

Hi all! Visit <http://www.4p8.com/eric.brasseur/gamma.html> (you remember?) and search for "dillo". Sebastian

2 1

H1's inside A's
by dennisn＠dennisn.linuxd.org 30 Apr '14

30 Apr '14

I know technically the H1 heading tags aren't allowed between A../A, and Dillo rightfully complains about this: "a" is not allowed to contain "h1". -- closing "a" But it seems like an innocent tiny mistake. Can't dillo linkify anyways, in addition to throwing this error? Currently the link-information is lost and only accessibly if I manually view the source and copy-paste it. Other browsers (i.e. webkitgtk based ones) do this, which is quite useful.

4 4

New/fixed Toolbar icons
by pankso＠slitaz.org 26 Apr '14

26 Apr '14

Hi all, Please find attached the screenshot of SliTaz Toolbar icons and her are the new pixmaps.slitaz.h + fixed pixmaps.tango.h: http://hg.slitaz.org/wok/file/tip/dillo/stuff/pixmaps.slitaz.h http://hg.slitaz.org/wok/file/tip/dillo/stuff/pixmaps.tango.h Dillo is the default web browser on SliTaz ARM and SliTaz Raspberry Pi distribution so I wanted a realy fine desktop integration with modern look and feel :-) By the way, congrats for all the work done on Dillo! Best regards, - Christophe Lincoln

3 3

Nanolinux distro with Dillo
by mailbox＠georgpotthast.de 25 Apr '14

25 Apr '14

I just want to mention that I made a small (14 MB footprint) Linux distro called "Nanolinux" which includes Dillo as the browser plus many FLTK apps: https://sourceforge.net/projects/nanolinux/ Georg

2 1

[jcid@dillo.org: Re: [jcid@dillo.org: Commit 3626. Redraw problems]]
by jcid＠dillo.org 24 Apr '14

24 Apr '14

FYI, -- Cheers Jorge.-

1 0

[jcid@dillo.org: Commit 3626. Redraw problems]
by johannes.hofmann＠gmx.de 24 Apr '14

24 Apr '14

That was me. Sorry I didn't follow this. Can you point me to the problem? The idea with redrawY is that when loading long pages we don't keep redrawing the currently visible (top) part of the page while adding text on the bottom. Obviously this only works as long as the newly incoming HTML doesn't affect the layout of the already drawn (top) part of the page. Cheers, Johannes Am 24.04.2014 14:44 schrieb Sebastian Geerken <sgeerken at dillo.org>: On Wed, Apr 23, 2014, Sebastian Geerken wrote: > Hi Jorge, > >?? Today I saw commit 3626, and checked whether the pages I see to > > produce redraw storms and CPU hogs were gone, and...? no?? :-P > > > >?? I got one of them and worked reducing it to try to produce a good > > test case, that's the attachment. If you open it with embedded CSS > > disabled, it's OK, then enable it and voila: redraw storm and CPU > > hog. > > > >?? I hope this helps the cause. Please let me know whether you can > > work on it, or give me some clues to try to start digging further. > > Yes, I can reproduce the problem. Thanks for the test. > > This change (revision 3626) was for the opposite problem: in some > cases, there is no redraw. It seems that I'll have to care about the > TODO of the commit message soon: "Cleanup and document lastWordDrawn > and redrawY!". > > I'll work on this soon, after an issue I'll hope to finish today. I'm now working on this, and have already found out that this is not a redrawing problem: the only change in 3626 is that the CPU load is shifted from dillo to Xorg. (It seems that more redrawing is done, but this is rather a symptom of another problem, probably with resizing.) I noted this several times, so please observe CPU load (e. g.? with top(1)): if it stays high, even if dillo is responsive this is a problem you should send to the list. Sebastian PS: Cleaning up lastWordDrawn/redrawY is still an issue, but with lower priority.? Who did actually implement this? _______________________________________________ Dillo-dev mailing list Dillo-dev at dillo.org http://lists.dillo.org/cgi-bin/mailman/listinfo/dillo-dev

1 0