- Dillo-dev - lists.mailman3.com

[Dillo-dev]about DilloHtmlParseMode
by Calvin Yu Dec. 10, 2004

Dec. 10, 2004

hello all: Can you tell me the difference among these dillo html parse mode? DILLO_HTML_PARSE_MODE_INIT,DILLO_HTML_PARSE_MODE_STASH,DILLO_HTML_PARSE_MODE_STASH_AND_BODY,DILLO_HTML_PARSE_MODE_VERBATIM,DILLO_HTML_PARSE_MODE_BODY,DILLO_HTML_PARSE_MODE_PRE What do these parse mode mean? Especially, what is stash mode? Thank you very much!

2 1

[Dillo-dev][Offtopic] Dillo in mobile research
by Livio Soares Dec. 10, 2004

Dec. 10, 2004

Hi all, Just as a miscellaneous little bit of curious information: while taking a Mobile Computing course during my first semester here at the University of Toronto, I've learned of the citation of Dillo in a few mobile computing papers: [1] Ghosts in the Machine: Interfaces for Better Power Management http://notrump.eecs.umich.edu/group/papers/mobisys04.pdf Work from University of Michigan, presented in Mobisys'2004 (a very good conference in the mobile area). Won the best paper award. Dillo is used to measure energy savings in the proposed system. [2] Transport Protocol Optimization For Energy Efficient Wireless Embedded Systems http://www.ee.princeton.edu/~anand/pub_links/date03_tcp.pdf Work from Princeton, presented in Design, Automation and Test in Europe Conference and Exhibition (DATE 03) Dillo, again, is used in the evaluation section for energy-savings measurements. [3] Chameleon: Application Controlled Power Management with Performance Isolation http://lass.cs.umass.edu/~lass/papers/pdf/TR04-26.pdf Just a technical report from University of Massachusetts Amherst Also used in evaluation section. Again for energy savings/power-management. The papers themselves have nothing directly to do with Dillo, but it was still nice to see it being mentioned and used in the mobile-research community. My (wild) guess is that the mobile people probably know about Dillo because of its inclusion in the 'Familiar' distribution. Cheers, Livio

1 0

[Dillo-dev]Ugly fonts -- fixed
by Chris de Vidal Dec. 3, 2004

Dec. 3, 2004

I honestly don't know what worked. This morning I commented out vw_fontname and reloaded Dillo and it worked! Apparently at some point in time I fixed the problem but because vw_fontname was set I didn't know when it was fixed. Now the default font looks great, like the screenshots. Compared to anti-aliased fonts of course it looks edgier and for some reason the screenshot's fonts look slightly less edgy, but it's far better than when I first started using it. Thanks to everyone! 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

1 0

[Dillo-dev]Ugly fonts
by Chris de Vidal Dec. 3, 2004

Dec. 3, 2004

This must be related to the GTK 1.x engine that's used with XFCE 4. I say that because the font in the type location box (Ctrl+L) has the same ugliness that Dillo renders websites with, and this font is the same as used by the menus at the top of Multi-Gnome-Terminal. But on GTK 2.x programs I get a nice anti-aliased font for the menus. J-Pilot, a GTK app, was recently converted from 1.x to 2.x. Before the upgrade fonts were terrible; now they're smooth. KDE must use a slightly different configuration for GTK 1.x apps; on the wife's computer, both Dillo and Multi-Gnome-Terminal use nice fonts for the menus, location box (Dillo, Ctrl+L), and when Dillo renders HTML. I have the same versions of GTK 1.x and 2.x on both machines. XFCE 4 is GTK 2.x-based. Do I *have* to install a heavy window manager to use a light web browser? Not fair :( Livio Baldini Soares wrote: > Chris, regarding your Debian box, make sure you have correctly > configured your '/etc/fonts/local.conf' configuration file. > Specifically, I have found that most Debian default installations > disable bitmapped fonts, due to the use of anti-aliased or truetype > fonts used in most applications and/or window managers. Uncomment the > lines around: <dir>/usr/X11R6/lib/X11/fonts</dir> > > After you do that, run: > > $ defoma-reconfigure > and > $ fc-cache -f No gold. > Another issue is that fonts with "odd" sizes are butt-ugly. In this > respect, try adding 0.1 to your "font_factor" variable in your dillorc > file (if it's 1.0 set it to 1.1, if it's 1.1 set it to 1.2, for > example). It usually makes very little difference in the final font > size, but makes it a _big_ difference in scalability. No difference. Thanks for the attempt. higuita wrote: > try > > "-misc-fixed-*-*-*--*-*-*-*-*-*-iso8859-1" Same. > probably kde installed truetype fonts... > try to do the xfontsel in that computer and compare > then I don't think you mean xfontsel because that just lets me see what fonts look like, it doesn't show which my X server is using. Jorge Arellano Cid said: > This is a problem with your machine's installed > fonts, not with Dillo. Never doubted that for a second, especially when exactly the same Dillo binary and config file worked at home. Just writing this list because I don't know where else to look. > I'm not a Debian user, but most probably you left out > a set of "legacy" fonts that Dillo requires. Wish that were true... I've installed every font package the other machine has. > Maybe the fastest solution is to check the font-specific .debs > of your wife's cpmputer against yours, once this is done update > the font cache, restart X and retry. I compared font packages on both machines and ensured both had the same packages installed. Some were missing, so I installed them, updated the font cache, restarted X. No joy. xlsfonts shows exactly the same fonts on both machines. X on both machines are now using strictly xfs for fonts. I think I'll just give up using Dillo for now... it hurts the eyes too much.

2 2

[Dillo-dev]Dillo doesn't work!! :(
by Andrea Spadaccini Dec. 1, 2004

Dec. 1, 2004

Hi everyone, i compiled and installed Dillo 0.83, but it doesn't open anything! Here there are the error messages I get: [andrea@iridiumII andrea]$ dillo dillorc:98: unexpected string constant "force_visited_color", expected symbol dillo_dns_init: Here we go! Disabling cookies. Nav_open_url: Url=>about:splash< Nav_open_url: Url=>dpi:/bm/< dpi_socket_dir.c:61: tst_dir: access : No such file or directory - /tmp/andrea-0c137u/ debug_msg - init_sockdir: The socket directory /tmp/andrea-0c137u does not exist or is not a directory dpid.c:500: init_all_dpi_sockets: bind : Address already in use/tmp/andrea-3vbac6/bookmarks.dpi dpid started Capi_dpi_conn_timeout:: try 1 main.c:153: get_command: dpid tag is NULL : main.c:326: main: get_command failed : ** ERROR **: file main.c: line 351 (main): assertion failed: (numsocks >= 0) aborting... waitpid: No child processes IO_write_chunk: Pipe rotta It seems like it cannot access the dir /tmp/andrea-0c137u, but it should be able to do it: [andrea@iridiumII andrea]$ ll /tmp/ totale 4 drwx------ 2 andrea users 4096 2004-11-30 00:59 andrea-3vbac6/ srwxr-xr-x 1 andrea users 0 2004-11-30 00:59 sylpheed-1000= srwxr-xr-x 1 andrea users 0 2004-11-29 22:20 xmms_andrea.0= srwxr-xr-x 1 giorgia users 0 2004-11-03 16:57 xmms_giorgia.0= srwxr-xr-x 1 luther users 0 2004-11-27 11:50 xmms_luther.0= [andrea@iridiumII andrea]$ cd /tmp/andrea-3vbac6/ [andrea@iridiumII andrea-3vbac6]$ ls bookmarks.dpi= dpid.srs= ftp.filter.dpi= https.filter.dpi= downloads.dpi= file.dpi= hello.filter.dpi= I get the same problems if I'm root too, so it shouldn't be a permissions problem... I've tried installing dpis in my home directory, but it doesn't work.. Can you help me, please? Thanks! :) -- [ 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 ]

3 3

[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