- Dillo-dev - lists.mailman3.com

[Dillo-dev]dillo.c patch
by Russell J. Wood Nov. 30, 2004

Nov. 30, 2004

Hello all, Attached is a patch for dillo.c that merely ensures all command line arguments are parsed and complete before the GUI environment. Previous to this, the locale and GUI functions where run and then the command line, of which, in my opinion, should be run after the CLI because the CLI has the immediate commands. There is no point firing up the GUI when all one would like to know is the version they are running, right? Again, it's nothing major and doubtfully increases performance in any way. Regards, Russell

2 1

[Dillo-dev]pthreads
by Jorge Arellano Cid Nov. 28, 2004

Nov. 28, 2004

Hi, Is anyone here savvy on using dynamic memory allocation in pthreads? The problem: while hunting a bug that showed after the large parser orthogonalization patch, it was finally found between dillo and the file dpi server; it was a critical race. I recoded the file server to use pthreads and it went away, but... ... the new file server started to increase dramatically its virtual size. The threads are allocating memory and freeing it with the usual g_malloc/g_free pair, but it seems like these blocks remain allocated even after the thread is finished. This may be the same root for the reload memory leak pointed somtime ago, do you remember? The IO engine uses a pthread to make the request. It seems that there's an API to use "thread specific data" or TSD by using pthread_key_create() and akin functions. Does anyone know if this is the only way, or an URL of a good tutorial on how to do this? Note that the file server problem can be solved by using a dpi filter instead of a server, but as pthreads are being used in other parts of Dillo, this becomes very important to know. -- Cheers Jorge.-

5 17

[Dillo-dev]Ugly fonts
by Chris de Vidal Nov. 26, 2004

Nov. 26, 2004

Wonderful, fast program! Especially dig the fullscreen mode and keyboard shortcuts. HTML layout rendering of pages like Google and Amazon and eBay and Slashdot looks great! Unfortunately the fonts don't... Dillo 0.8.3 Debian Sid XFCE 4.0.5-1 XFS 4.3.0.dfsg.1-8 Kernel 2.6.8.1 The fonts on my machine look far worse than those in the screenshots. For example, Slashdot: http://devidal.tv/~chris/ugly_dillo_fonts.png Compared to your screenshot: http://www.dillo.org/screenshots/slashdot1.png And just for reference, Firefox 1.0 RC1 from a Debian Sid source (probably includes gtk2 and xfs): http://devidal.tv/~chris/nice_firefox_fonts.png These fonts are about the only thing preventing my more regular use of Dillo. I built Dillo with just ./configure make make install I tried vw_fontname=lucida which helped some, but it's still uglier than the screenshots. Ideas? Need to know anything else? CD "You will exist forever. You and God are both in the universe to stay either as friends on his terms, or enemies on yours. Which it will be is proven in this life. And this life is a vapor. Two seconds, and we will be gone. Surely God means for our time on earth to count for something significant." -- John Piper in "Life as a Vapor." Read it here: http://www.desiringgod.org/library/onlinebooks_index.html#blv

4 6

Re: [Dillo-dev]pthreads
by Jorge Arellano Cid Nov. 24, 2004

Nov. 24, 2004

On Wed, Nov 24, 2004 at 03:15:15PM +0100, Riccardo Mottola wrote: > Hey Jorge, > > just a quick answer, but I am ina hurry > > > I have solaris, I have gcc. so I can test and compile. I have also > MkLinux which is linux where threads are mapped to mach threads (linux > on mach microkernel). > > > What source code should I run? How do i check for memory leaks (no > valgrind for solaris)... I posted it to the mailing list with instructions. You can find it here: http://lists.auriga.wearlab.de/pipermail/dillo-dev/2004-November/002436.html The mail thread starts at: http://lists.auriga.wearlab.de/pipermail/dillo-dev/2004-November/002429.html BTW, I'm making some tests in dillo using the results explained there, and the results are impressive: For instance: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jcid 3234 2.5 13.9 663804 13116 pts/15 S+ 11:59 0:05 ./dillo jcid 3238 0.0 13.9 663804 13116 pts/15 S+ 11:59 0:00 ./dillo (see the huge virtual size? It's a simple page with lots of tiny images). The same dillo, this time using the explicit detached-attribute pthread creation technique, gives: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jcid 3792 11.8 11.0 14116 10448 pts/15 S+ 12:49 0:07 ./dillo jcid 3793 0.3 11.0 14116 10448 pts/15 S+ 12:49 0:00 ./dillo Same code, same page. Something really weird is going on here! Does anyone know the email of the pthreads library maintainer? -- Cheers Jorge.-

1 0

[Dillo-dev]Parser orthogonalization
by Jorge Arellano Cid Nov. 21, 2004

Nov. 21, 2004

Hi there, A few days ago I finished the: [1] Orthogonalize the parser (leaks, XML, CSS) task from the list. I didn't commit it inmediately because of the pthreads issue we're still workint in (it showed as a parser bug when in fact it was elsewhere). Now the large parser patch is commited (a 70KB beast!). From the ChangeLog: <q> * Orthogonalized the generic parser: - Fixes memory leaks and widget state when recovering from bad HTML. - Improves error detection and validation (needed by XHTML). - Makes DOC tree generation possible (needed by CSS). - Cleaner design of handling routines for bad HTML. - Orthodox treatment of double optional elements (HTML, HEAD, BODY). - Lots of minor code cleanups. </q> That's the summary. Now tags are always pushed into the stack when they're found and the respective closing functions are always called when finishing them, no matter if this is triggered by an explicit tag, optional close, or bad-HTML cleanup. This is very important because of the above explained reasons. The routines for handling HTML cleanup (optional, magic and bad HTML) were mostly isolated into three functions: Html_test_section() Html_stack_cleanup_at_open() Html_tag_cleanup_at_close() (fairly commented in the source). In brief: the good news of all of this patch is that it makes much easier to understand, improve and maintain the parser (eventually to chop, merge or reuse too), fixes memory handling, widget creation state, validation, and is also good for future CSS, XHTML. For instance, look at the new <P> and </P> tag treatment at: http://www-106.ibm.com/developerworks/eserver/articles/framework.html Now, I'm back to pthreads, ah, and I have more cleanups already done waiting for commit, some patches pending, the usual stuff! -- Cheers Jorge.-

1 0

[Dillo-dev]Dillo and multimedia keys
by Andrea Spadaccini Nov. 20, 2004

Nov. 20, 2004

Hi everyone, does Dillo support "strange" keys that are configured with Xmodmap? I'd like to hit the "back" button (XF86Back) and go back one page, and so on... If Dillo doesn't support this, you could give me suggestions on how to implement it. I know a little C, and maybe I could be able to help you. Thanks in advance -- [ Andrea Spadaccini a.k.a. Lupino / Lupin85 - from Catania ] [ MAIL: lupin85(at)email.it - ICQ: 91528290 - Linux 2.4.22 ] [ Linux Registered User #313388 - Powered by Slackware 9.1 ] -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Email.it Phone Card: chiami in tutto il mondo a tariffe imbattibili da tutti i telefoni fissi e cellulari! Clicca e scopri come Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=2686&d=20-11

1 0

[Dillo-dev]dns error with static dillo
by Roberto A. Foglietta Nov. 16, 2004

Nov. 16, 2004

Hi, please try to reproduce this bug: I've compiled dillo with -static in linking but 0.8.2 --> 0.8.4rc1 show the same problem: dns error! [roberto@wsraf src]$ ./dillo Gdk-WARNING **: locale not supported by C library GLib-WARNING **: getpwuid_r(): failed due to: No such user 1309. Gtk-WARNING **: libc.so.6: cannot handle TLS data Gtk-WARNING **: libc.so.6: cannot handle TLS data Gtk-WARNING **: libc.so.6: cannot handle TLS data Gtk-WARNING **: libc.so.6: cannot handle TLS data Gtk-WARNING **: libc.so.6: cannot handle TLS data Gtk-WARNING **: libc.so.6: cannot handle TLS data Gtk-WARNING **: libc.so.6: cannot handle TLS data Gtk-WARNING **: libc.so.6: cannot handle TLS data dillo_dns_init: Here we go! Disabling cookies. Nav_open_url: Url=>about:splash< Nav_open_url: Url=>http://www.lugge.net< Dns_server [0]: www.lugge.net is (nil) Dillo: normal exit! -- Roberto A. Foglietta Analista Programmatore GNU/Linux SAD Trasporto Locale S.p.a. Corso Italia 13/N 39100 BOLZANO (I) Tel. +39/0471-450.261 Fax +39/0471-450.253

2 1

[Dillo-dev]refresh tag patch for 0.8.4 (and fix)
by Roberto A. Foglietta Nov. 16, 2004

Nov. 16, 2004

Hi, previous patch was little buggy, I hope this is better and it's against the last version I know. I hope you will interested in apply it. :-) Cheers, -- Roberto A. Foglietta Analista Programmatore GNU/Linux SAD Trasporto Locale S.p.a. Corso Italia 13/N 39100 BOLZANO (I) Tel. +39/0471-450.261 Fax +39/0471-450.253

1 0

[Dillo-dev]https by lynx -source
by Hanspeter Roth Nov. 15, 2004

Nov. 15, 2004

Hello, I don't know where to post feature requests. So I try here. Could one do a preliminary implementation of HTTPS (SSL) via piping to `lynx -source %s'? -Hanspeter

1 0

[Dillo-dev]Toolkit & dillo
by Lars Segerlund Nov. 15, 2004

Nov. 15, 2004

There has been a lot of talk about toolkits and dillo, and I had a small idea. What about using lesstif ( Motif ) for dillo ? It's fairly small ( you can bring only the widgets you need ) and if done with some care a statically linked dillo would not be bloated. I can have a look at it, but I would like the general opinion first, ( I would even give Xt a shot :-) that way it would be FAST & SMALL ). regards, Lars Segerlund.

4 7