- Dillo-dev - lists.mailman3.com

[Dillo-dev]about porting dillo to another toolkit

by Eduard Bondarenko

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I think dillo have to be ported to fox toolkit (http://fox-toolkit.org/) it is better than gtk2 and fltk -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with MultiZilla - http://enigmail.mozdev.org iD8DBQFARigvWVzJEsNrxK8RAnfXAKCJIYK8JBEpVmfn+GqhlzRqXVIq6gCfXLrw SuLflp2nwpqq2ctAytMVsuc= =mauP -----END PGP SIGNATURE-----

March 3, 2004

[Dillo-dev]0.80 crash and info

by Riccardo

Hello, I am on OpenBSD 3.4. I run dillo 0.80 and go to "www.knuddel.org" I get the following (repeatable) error: (gdb) run Starting program: /usr/local/bin/dillo dillo_dns_init: Here we go! Disabling cookies. Nav_open_url: Url=>about:splash< Nav_open_url: Url=>http://www.knuddel.org< Dns_server [0]: www.knuddel.org is 0x738d28 Connecting to 64.95.194.245 Gdk-ERROR **: BadMatch (invalid parameter attributes) serial 4490 error_code 8 request_code 72 minor_code 0 typing 'bt' tells me "no stack" and now ? -Ric

March 2, 2004

[Dillo-dev]New to the list -- some patches

by Nelson Rodriguez

Hello everybody, I'm new to the list. I decided to subscribe the list to share some changes I've done to Dillo. I don't know much about programming in GTK, but I know C, so I just modified some functions and took as example existing code. Here are the things I've done so far: - Show a option for "Back" and "Forward" in the pop-up page menu (for history navigation) - Open Links in new window when the link has a target _blank or _new (this include form posts too) - Show in the status bar if a link will open in a new window or same window Who do I sent this patches? I would really love if this gets into the development tree, so I don't have to do it every time a new release comes :P (The web page says that if it's a dillo widget to send it to Sebastian, but otherwise to me. Who is me??? ) The changes I did affected html.c, menu.c, url.c and url.h. Is that part of the "widget"? I plan to improve things in dillo, because I really like it. Right now I'm working in a change to make images fit in the screen (like the IE and Mozilla "zoom" features) when displaying just an image. Ok, bye for now. Please remember to let me know who/how do I send th patches. Nelson

March 2, 2004

Re: [Dillo-dev]Re: Italian docs

by Lupino

Jorge Arellano Cid wrote: > > I've translated the file you sent me, and the file README, both packed in > > doc-it.tar.bz2. Are there other files to translate? > > That's all for now. > > I didn't include the README file in the tarball (we could end > with lots of translations that way). Maybe it'd be good to link > to it from the help page... you're right! or maybe, if more files will be translated in other languages too, we should add a directory for each language, with all docs inside. > Just check the help page now! I've just done it.. It's quite an emotion to see my translation! :) It's the second translation I do (the first has to be published), and it's good to see that I can help the community! Thanks for the opportunity! -- [ Andrea Spadaccini a.k.a. Lupino / Lupin85 - from Catania ] [ MAIL: lupin85(at)email.it - ICQ#: 91528290 - Linux 2.6.3 ] [ Linux Registered User #313388 - Powered by Slackware 9.1 ]

March 1, 2004

[Dillo-dev]Re: Italian docs

by Jorge Arellano Cid

On Sun, 29 Feb 2004, Lupino wrote: > Hi Jorge, do you remember me? Yes i do! ;) Even when I can't answer all the email that I get, usually the names keep inside my head (for instance, as for Ivan, to whom I still owe an answer). > I've translated the file you sent me, and the file README, both packed in > doc-it.tar.bz2. Are there other files to translate? That's all for now. I didn't include the README file in the tarball (we could end with lots of translations that way). Maybe it'd be good to link to it from the help page... > > Do you plan to translate dillo itself in languages different from english? I > would like to help you! I'd like, but that's to be done when we start I18n (more in the developer notes). Just check the help page now! Thanks Jorge.-

March 1, 2004

Re: [Dillo-dev]dillo .filter.dpi mini mini howto

by Diego Sáenz

Sorry. The file seems a mess because the new lines was all moved. I try it again. If this not work i will send it atachement. Diego. #!/bin/sh # characters delimiting the fields for read IFS=" '/" # Read dillo's request read -d'>' tag cmd cmd_value url url_tag1 url_tag2 url_value_e # read put each field in a variable. them looks like: # tag "<dpi" # cmd "cmd=" it can be intersting to test this strings # cmd_value "open_url" for this aplication. Dillo can send "add_bookmark" and # "chat" too.(0.8.0 version) With a case we can respond to every dillo command # url "url=" for this command # url_tag1 "dpi:" for this app ... # url_tag2 "tidy" # url_value_e "http://server.com/path/file.html'" we do not want that final ' # so we delete it url_value=`echo -n "$url_value_e" | tr -d "'"` # get the name of the file name=`basename "$url_value"` # with the follow lines we get the url without the filename without using awk u_tmp1=` echo -n "$url_value" | tr "." "\n" ` u_tmp2=` echo -n "$u_tmp1" | tr "/" "." ` n_tmp=` echo -n "$name" | tr "." "\n" ` b_tmp1=` basename "$u_tmp2" ".$n_tmp" ` b_tmp2=` echo -n "$b_tmp1" | tr "." "/" ` base=` echo -n "$b_tmp2" | tr "\n" "." ` # we change status line with send_status_message PI to Dillo command echo "<dpi cmd='send_status_message' msg='tidy up $url_value. please wait'>" ## we send a wait page with the start_send_page command. We can command dillo ## to "reload_request" and "chat" too. (0.8.0 version) #cat <<EOF #<dpi cmd='start_send_page' url='dpi:/tidy/wait.html'> #Content-type: text/html # #<html> # <head> # <title> Wait a moment TYDY up this MESS </title> # </head> # <body> # <h1> # Tidy up this mess ($url_value) <br> # Please wait a moment # </h1> # </body> #</html> # # #EOF # we download the page url_value to /tmp with wget wget --no-parent -nc -nH --cut-dirs=30 -P /tmp/ $url_value # with this the page works in local like from inet. Tidy move base to the # right html place echo "<base href=$base >" >> /tmp/$name # we send the html header # Don't forget the empty line after the Content-type cat <<EOF <dpi cmd='start_send_page' url='$url_value'> Content-type: text/html EOF # and tidy do the rest tidy /tmp/$name # clean up the tmp files rm /tmp/$name

March 1, 2004

[Dillo-dev]dillo .filter.dpi mini mini howto

by Diego Sáenz

Hello. The DPIP is here, but it seems that developers(external ones) do not make a big use of it. I have made a litle PI to learn how to use DPIs that can help others. This filter dpi uses tidy to see a bad writen page. If i have write this dpi is only because it was more easy to write in shell script than a download dpi with progres indicator, thah was my other option. I agree that tidy is a big thing but in the server side. First of all a filter.dpi is a executable file that reads dillo comands from stdin an ouputs commands and html to stdout. It can be write in any language that can do this. It is possible to do it in shell programing. This file must be in a directory in /usr/local/lib/dillo/ for a local compiled dillo. When you enter a url dpi:/name/otherthings a file /usr/local/lib/dillo/name/name.filter.dpi is executed and a command <dpi cmd='open_url' url='dpi:/name/otherthings'> is send to it. Then the PI can send commands or html page that dillo show. I have try to send more than a page, with and without the reload command, and use another comands but for the moment this do not work for dpi filters. If you add a filter dpi with dpid running do not forget to restart it or reload DPIs using dpidc. To install this PI create a tidy directory in the dillo DPIs directory and copy it named tidy.filter.dpi You can use it to see some bad writen pages with a url like dpi:/tidy/http://page_that_you_can_view_with The PI do not add index.htm automaticaly so put it in the url. I hope that this help somebody to write some better PIs. Diego. ------------------------ #!/bin/sh # characters delimiting the fields for read IFS=" '/" # Read dillo's request read -d'>' tag cmd cmd_value url url_tag1 url_tag2 url_value_e # read put each field in a variable. them looks like: # tag "<dpi" # cmd "cmd=" it can be intersting to test this strings # cmd_value "open_url" for this aplication. Dillo can send "add_bookmark" and # "chat" too.(0.8.0 version) With a case we can respond to every dillo command# url "url=" for this command # url_tag1 "dpi:" for this app ... # url_tag2 "tidy" # url_value_e "http://server.com/path/file.html'" we do not want that final ' # so we delete it url_value=`echo -n "$url_value_e" | tr -d "'"` # get the name of the file name=`basename "$url_value"` # with the follow lines we get the url without the filename without using awk u_tmp1=` echo -n "$url_value" | tr "." "\n" ` u_tmp2=` echo -n "$u_tmp1" | tr "/" "." ` n_tmp=` echo -n "$name" | tr "." "\n" ` b_tmp1=` basename "$u_tmp2" ".$n_tmp" ` b_tmp2=` echo -n "$b_tmp1" | tr "." "/" ` base=` echo -n "$b_tmp2" | tr "\n" "." ` # we change status line with send_status_message PI to Dillo command echo "<dpi cmd='send_status_message' msg='tidy up $url_value. please wait'>" ## we send a wait page with the start_send_page command. We can command dillo## to "reload_request" and "chat" too. (0.8.0 version) #cat <<EOF #<dpi cmd='start_send_page' url='dpi:/tidy/wait.html'> #Content-type: text/html # #<html> # <head> # <title> Wait a moment TYDY up this MESS </title> # </head> # <body> # <h1> # Tidy up this mess ($url_value) <br> # Please wait a moment # </h1> # </body> #</html> # # #EOF # we download the page url_value to /tmp with wget wget --no-parent -nc -nH --cut-dirs=30 -P /tmp/ $url_value # with this the page works in local like from inet. Tidy move base to the# right html place echo "<base href=$base >" >> /tmp/$name # we send the html header # Don't forget the empty line after the Content-type cat <<EOF <dpi cmd='start_send_page' url='$url_value'> Content-type: text/html EOF # and tidy do the rest tidy /tmp/$name # clean up the tmp files rm /tmp/$name ---------------------------------------------

March 1, 2004

[Dillo-dev]CSS pre-release 2

by Sebastian Geerken

Hi! A second CSS pre-release is available, at <http://www.dillo.org/download/dillo-0.8.0-css-2.tar.gz>. It now deals with external stylesheets (thanks to Jörgen), and adds the forgotten HTML entities. Sebastain

Feb. 29, 2004

[Dillo-dev]RE: Error png in make of Dillo - Help

by Eduard Bondarenko

dillo-dev-request(a)lists.auriga.wearlab.de wrote: >Send Dillo-dev mailing list submissions to > dillo-dev(a)lists.auriga.wearlab.de > >To subscribe or unsubscribe via the World Wide Web, visit > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >or, via email, send a message with subject or body 'help' to > dillo-dev-request(a)lists.auriga.wearlab.de > >You can reach the person managing the list at > dillo-dev-admin(a)lists.auriga.wearlab.de > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of Dillo-dev digest..." > > >Today's Topics: > > 1. Error png in make of Dillo - Help (=?iso-8859-1?q?Pablo?=) > >--__--__-- > >Message: 1 >Date: Wed, 25 Feb 2004 17:53:23 -0600 (CST) >From: =?iso-8859-1?q?Pablo?= <pabloruiz(a)yahoo.com> >To: dillo-dev(a)lists.auriga.wearlab.de >Subject: [Dillo-dev]Error png in make of Dillo - Help > >I wish use Dillo but I got an error, I apprecite if somebody can help >me. > >make >make all-recursive >make[1]: Cambiando a directorio `/home/pr114793/Downloads/dillo-0.8.0' >Making all in doc >make[2]: Cambiando a directorio >`/home/pr114793/Downloads/dillo-0.8.0/doc' >make[2]: No se hace nada para `all'. >make[2]: Saliendo directorio `/home/pr114793/Downloads/dillo-0.8.0/doc' >Making all in src >make[2]: Cambiando a directorio >`/home/pr114793/Downloads/dillo-0.8.0/src' >Making all in IO >make[3]: Cambiando a directorio >`/home/pr114793/Downloads/dillo-0.8.0/src/IO' >make[3]: No se hace nada para `all'. >make[3]: Saliendo directorio >`/home/pr114793/Downloads/dillo-0.8.0/src/IO' >make[3]: Cambiando a directorio >`/home/pr114793/Downloads/dillo-0.8.0/src' >gcc -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 >-I/usr/lib/glib/include -I/usr/X11R6/include -g -O2 >-D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter >-Waggregate-return -L/usr/local/lib -o dillo chain.o commands.o >cache.o capi.o dw.o dw_aligned_page.o dw_bullet.o dw_button.o >dw_container.o dw_embed_gtk.o dw_ext_iterator.o dw_gtk_scrolled_frame.o >dw_gtk_scrolled_window.o dw_gtk_statuslabel.o dw_gtk_viewport.o >dw_hruler.o dw_image.o dw_list_item.o dw_marshal.o dw_page.o dw_style.o >dw_table.o dw_table_cell.o dw_tooltip.o dw_widget.o findtext.o >selection.o web.o progressbar.o dillo.o bookmark.o dicache.o dns.o >gif.o jpeg.o png.o html.o image.o misc.o interface.o history.o nav.o >plain.o menu.o prefs.o colors.o bitvec.o klist.o strbuf.o url.o >cookies.o IO/libDio.a -ljpeg -L/usr/lib -Wl,-rpath,/usr/lib -L/usr/lib >-L/usr/X11R6/lib -lgtk -lgdk -rdynamic -lgmodule -lglib -ldl -lXi >-lXext -lX11 -lm -lz -lpthread >png.o: En la funciуn `Png_error_handling': >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:116: referencia a >`png_get_error_ptr' sin definir >png.o: En la funciуn `Png_datainfo_callback': >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:136: referencia a >`png_get_progressive_ptr' sin definir >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:139: referencia a >`png_get_IHDR' sin definir >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:153: referencia a >`png_get_valid' sin definir >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:167: referencia a >`png_get_gAMA' sin definir >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:182: referencia a >`png_read_update_info' sin definir >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:184: referencia a >`png_get_IHDR' sin definir >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:187: referencia a >`png_get_rowbytes' sin definir >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:188: referencia a >`png_get_channels' sin definir >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:178: referencia a >`png_set_interlace_handling' sin definir >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:173: referencia a >`png_set_gray_to_rgb' sin definir >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:168: referencia a >`png_set_gamma' sin definir >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:161: referencia a >`png_set_strip_16' sin definir >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:157: referencia a >`png_set_expand' sin definir >png.o: En la funciуn `Png_datarow_callback': >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:221: referencia a >`png_get_progressive_ptr' sin definir >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:223: referencia a >`png_progressive_combine_row' sin definir >png.o: En la funciуn `Png_dataend_callback': >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:282: referencia a >`png_get_progressive_ptr' sin definir >png.o: En la funciуn `Png_callback': >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:381: referencia a >`png_process_data' sin definir >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:350: referencia a >`png_check_sig' sin definir >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:356: referencia a >`png_create_read_struct' sin definir >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:362: referencia a >`png_create_info_struct' sin definir >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:367: referencia a >`png_set_progressive_read_fn' sin definir >/home/pr114793/Downloads/dillo-0.8.0/src/png.c:325: referencia a >`png_destroy_read_struct' sin definir >collect2: ld returned 1 exit status >make[3]: *** [dillo] Error 1 >make[3]: Saliendo directorio `/home/pr114793/Downloads/dillo-0.8.0/src' >make[2]: *** [all-recursive] Error 1 >make[2]: Saliendo directorio `/home/pr114793/Downloads/dillo-0.8.0/src' >make[1]: *** [all-recursive] Error 1 >make[1]: Saliendo directorio `/home/pr114793/Downloads/dillo-0.8.0' >make: *** [all] Error 2 > > >_________________________________________________________ >Do You Yahoo!? >Informaciуn de Estados Unidos y Amйrica Latina, en Yahoo! Noticias. >Visнtanos en http://noticias.espanol.yahoo.com > > > >--__--__-- > >_______________________________________________ >Dillo-dev mailing list >Dillo-dev(a)lists.auriga.wearlab.de >http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev > > >End of Dillo-dev Digest > > > > make sure that you have install libpng. also i don't see -lpng in gcc command, you can edit Makefile if you sure you have libpng installed

Feb. 28, 2004

Re: [Dillo-dev]Error png in make of Dillo - Help

by Lupino

Pablo wrote: > I wish use Dillo but I got an error, I apprecite if somebody can help > me. [snip] maybe you need to install libpng and headers.. -- [ Andrea Spadaccini a.k.a. Lupino / Lupin85 - from Catania ] [ MAIL: lupin85(at)email.it - ICQ#: 91528290 - Linux 2.6.3 ] [ Linux Registered User #313388 - Powered by Slackware 9.1 ]

Feb. 28, 2004

[Dillo-dev]CVS

by Pete

Can someone fill me in a little on the CVS process. I just installed from the CVS server. Now say for example I want to update every week...or whenver there is progress made. How do I do this? I am pretty sure I dont do what I just did to install it. FreeBSD btw. Thanks -- Pete http://milneweb.com http://nomorevirus.com

Feb. 26, 2004

[Dillo-dev]Error png in make of Dillo - Help

by Pablo

I wish use Dillo but I got an error, I apprecite if somebody can help me. make make all-recursive make[1]: Cambiando a directorio `/home/pr114793/Downloads/dillo-0.8.0' Making all in doc make[2]: Cambiando a directorio `/home/pr114793/Downloads/dillo-0.8.0/doc' make[2]: No se hace nada para `all'. make[2]: Saliendo directorio `/home/pr114793/Downloads/dillo-0.8.0/doc' Making all in src make[2]: Cambiando a directorio `/home/pr114793/Downloads/dillo-0.8.0/src' Making all in IO make[3]: Cambiando a directorio `/home/pr114793/Downloads/dillo-0.8.0/src/IO' make[3]: No se hace nada para `all'. make[3]: Saliendo directorio `/home/pr114793/Downloads/dillo-0.8.0/src/IO' make[3]: Cambiando a directorio `/home/pr114793/Downloads/dillo-0.8.0/src' gcc -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -Waggregate-return -L/usr/local/lib -o dillo chain.o commands.o cache.o capi.o dw.o dw_aligned_page.o dw_bullet.o dw_button.o dw_container.o dw_embed_gtk.o dw_ext_iterator.o dw_gtk_scrolled_frame.o dw_gtk_scrolled_window.o dw_gtk_statuslabel.o dw_gtk_viewport.o dw_hruler.o dw_image.o dw_list_item.o dw_marshal.o dw_page.o dw_style.o dw_table.o dw_table_cell.o dw_tooltip.o dw_widget.o findtext.o selection.o web.o progressbar.o dillo.o bookmark.o dicache.o dns.o gif.o jpeg.o png.o html.o image.o misc.o interface.o history.o nav.o plain.o menu.o prefs.o colors.o bitvec.o klist.o strbuf.o url.o cookies.o IO/libDio.a -ljpeg -L/usr/lib -Wl,-rpath,/usr/lib -L/usr/lib -L/usr/X11R6/lib -lgtk -lgdk -rdynamic -lgmodule -lglib -ldl -lXi -lXext -lX11 -lm -lz -lpthread png.o: En la función `Png_error_handling': /home/pr114793/Downloads/dillo-0.8.0/src/png.c:116: referencia a `png_get_error_ptr' sin definir png.o: En la función `Png_datainfo_callback': /home/pr114793/Downloads/dillo-0.8.0/src/png.c:136: referencia a `png_get_progressive_ptr' sin definir /home/pr114793/Downloads/dillo-0.8.0/src/png.c:139: referencia a `png_get_IHDR' sin definir /home/pr114793/Downloads/dillo-0.8.0/src/png.c:153: referencia a `png_get_valid' sin definir /home/pr114793/Downloads/dillo-0.8.0/src/png.c:167: referencia a `png_get_gAMA' sin definir /home/pr114793/Downloads/dillo-0.8.0/src/png.c:182: referencia a `png_read_update_info' sin definir /home/pr114793/Downloads/dillo-0.8.0/src/png.c:184: referencia a `png_get_IHDR' sin definir /home/pr114793/Downloads/dillo-0.8.0/src/png.c:187: referencia a `png_get_rowbytes' sin definir /home/pr114793/Downloads/dillo-0.8.0/src/png.c:188: referencia a `png_get_channels' sin definir /home/pr114793/Downloads/dillo-0.8.0/src/png.c:178: referencia a `png_set_interlace_handling' sin definir /home/pr114793/Downloads/dillo-0.8.0/src/png.c:173: referencia a `png_set_gray_to_rgb' sin definir /home/pr114793/Downloads/dillo-0.8.0/src/png.c:168: referencia a `png_set_gamma' sin definir /home/pr114793/Downloads/dillo-0.8.0/src/png.c:161: referencia a `png_set_strip_16' sin definir /home/pr114793/Downloads/dillo-0.8.0/src/png.c:157: referencia a `png_set_expand' sin definir png.o: En la función `Png_datarow_callback': /home/pr114793/Downloads/dillo-0.8.0/src/png.c:221: referencia a `png_get_progressive_ptr' sin definir /home/pr114793/Downloads/dillo-0.8.0/src/png.c:223: referencia a `png_progressive_combine_row' sin definir png.o: En la función `Png_dataend_callback': /home/pr114793/Downloads/dillo-0.8.0/src/png.c:282: referencia a `png_get_progressive_ptr' sin definir png.o: En la función `Png_callback': /home/pr114793/Downloads/dillo-0.8.0/src/png.c:381: referencia a `png_process_data' sin definir /home/pr114793/Downloads/dillo-0.8.0/src/png.c:350: referencia a `png_check_sig' sin definir /home/pr114793/Downloads/dillo-0.8.0/src/png.c:356: referencia a `png_create_read_struct' sin definir /home/pr114793/Downloads/dillo-0.8.0/src/png.c:362: referencia a `png_create_info_struct' sin definir /home/pr114793/Downloads/dillo-0.8.0/src/png.c:367: referencia a `png_set_progressive_read_fn' sin definir /home/pr114793/Downloads/dillo-0.8.0/src/png.c:325: referencia a `png_destroy_read_struct' sin definir collect2: ld returned 1 exit status make[3]: *** [dillo] Error 1 make[3]: Saliendo directorio `/home/pr114793/Downloads/dillo-0.8.0/src' make[2]: *** [all-recursive] Error 1 make[2]: Saliendo directorio `/home/pr114793/Downloads/dillo-0.8.0/src' make[1]: *** [all-recursive] Error 1 make[1]: Saliendo directorio `/home/pr114793/Downloads/dillo-0.8.0' make: *** [all] Error 2 _________________________________________________________ Do You Yahoo!? Información de Estados Unidos y América Latina, en Yahoo! Noticias. Visítanos en http://noticias.espanol.yahoo.com

Feb. 25, 2004

Re: [Dillo-dev]Re: Upcoming review.

by Jorge Arellano Cid

On Tue, 24 Feb 2004, Gavin Henry wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I was thinking about the timing of entering url to complete rendered page. > > How about a perl or bash script that simply checks the time a cache item was > first entered into the cache dir until the last one. And that should be the > full rendering time? This varies from browser to browser, and finding a custom way for each one is what I'd do. For instance: to visually check the images once the html page has arrived is one way (just select a page with closely placed images to avoid much scrolling). > > I checked out ~/.dillo/ to look for a cache dir. Is it this setting > use_dicache=NO to YES?? No (explained in the former email). Dillo doesn't cache to disk, but it will tell you when a page is done (look at the top meters). Note that when a page includes images inside iframe these will not be loaded, but you can check that in advance and wait for the image counter to reach a certain number. As I wrote above, the page completion check depends on the browser. Cheers Jorge.-

Feb. 25, 2004

Re: [Dillo-dev]Re: Upcoming review.

by Jorge Arellano Cid

On Tue, 24 Feb 2004, Gavin Henry wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > - ---------- Original Message ----------- > From: Jorge Arellano Cid <jcid(a)dillo.org> > To: Gavin Henry <ghenry(a)fedoranews.org> > Cc: Dillo mailing list <dillo-dev(a)auriga.wearlab.de> > Sent: Tue, 24 Feb 2004 13:22:38 -0300 (CLST) > Subject: Re: Upcoming review. > > > [list: this was originally a personal answer to Gavin, but as it > > has general interest information I'm CC to dillo-dev. > > It's about a browser comparison article. ] > > > > [...] > > There're some interesting tests to be done. Which one you > > choose depends on the time you have, and on what you want to test > > for. > > > > For instance, IMHO, the common "web experience" has four > > important factors: > > So far I have tested the browsers on slashdot, and bbc.co.uk > and a few others. > > They all seem to wait until some pictures arrive until rendering anything. I > haven't time these yet. Dillo, displays text immediately, but has some > difficulty with CSS. For instance fedoranews.org looks bad :-) Dillo doesn't have support for CSS yet. The closest we've got is a prototype. More info at: http://article.gmane.org/gmane.comp.web.dillo.devel/1827 > > Are you familiar with http://wwww.udcast.com/ whcih runs freebsd and has > customised apache etc. > > I thought maybe you have done something like this. As my day job > www.invsat.com we had a demo from them and they explained the priciple of > http precaching. > > Instead of requesting 4 images then waiting, it requests all images at once, > as this then reduces the latency across a satellite link. > > Is this how your browser works? (*I haven't look at any code as of yet ;-) ) Yes, dillo does that and more. There's a paper explaining dillo's internals. You can find it at the bottom of the links section. It's large though. > > * Network wait time > > > > * Rendering wait time > > > > * Time to start seeing content > > - streamed rendering > > > > * Site usability > > These will be what I base the benchmarks on. Good! > > > > These are key factors; for instance the same site may be > > unusable depending on whether you're on a dialup or broad band. > > The same is true for rendering time (influenced by CPU power and > > available memory); you may end going to some site only when > > you're sitting at a powerful workstation. > > I don't have access to dial-up, but I have a celeron 400 and a athlon xp 2000 > to test on. The dialup test is really a must. Got to see to believe. There are slow-connection emulators. Sometime ago someone suggested one in this mailing list. Does anyone remember? > [...] > > > > * Rendering wait time > > > > Very simple, load a semi complex page (like slashdot with > > comments --a 500KB one), or a large one (as the mysql manual -- I > > have one which is more than two Megabytes long). > > > > Press back, the forward. (you can have some coffee :) > > Slashdot works perfect. What do you define as a compliant site? A site that follows the W3C standards. > All done in CSS? no java script or flash? xhtml or html? Oops, meant for > usability section. You can find these answers here: http://www.dillo.org/funding/technical.html#fea In brief: CSS, java script, flash: NO xhtml, html: YES (note: xhtml works when served as "text/html" because the standard requires a validation we don't have for xhtml). > [...] > > > > Simple usability experience can be explained to less technical > > people: > > > > For instance, take dillo, and dig for something using google. > > You'll find that the time you use to make different queries and > > to check for alternative links until you find what you look for > > is better than with almost anything you've used before. > > Noticed that. Great! > > Thanks Jorge, I really appreciate your time and expertise. > > I think these will > be used as the basis for browser benchmarks, stealling the > reasoning you gave for the introductions :-) Great! "The eyes can't see what the mind doesn't comprehend". The average user (and some Ph.Ds in this country ;) don't know about those concepts. Explaining them simply and briefly will certainly contribute to understanding the test data. Note that getting accurate hard numbers for each one of the listed points is close to impossible, it depends a lot on how the browser was built, and instrumentating the source code for each one is out of reach. For instance for testing rendering time (in any browser), you have to separate it from networking time. Having the page already in memory helps, but you don't know how much of the rendering is cached. Dillo can cache decompressed images (use_dicache=YES). This will make back and forward extremely fast with pages that contain images because dillo will have them already buffered as RGB. With firebird, you can quickly switch from one tab to another (the rendering is clearly cached), but doing the same with back and forward yields different results! Now, with browsers that cache to disk, HD access time can count... The tests I suggested take this into account and can provide "meningful" numbers, but not strictly accurate ones. > > I will give you a preview of it as it starts to resemble > something readable. Thxs. Cheers Jorge.-

Feb. 25, 2004

Re: [Dillo-dev]Re: Upcoming review.

by Gavin Henry

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I was thinking about the timing of entering url to complete rendered page. How about a perl or bash script that simply checks the time a cache item was first entered into the cache dir until the last one. And that should be the full rendering time? I checked out ~/.dillo/ to look for a cache dir. Is it this setting use_dicache=NO to YES?? Sorry, I should RTFM. - -- Kind Regards, Gavin Henry. Director. Open Source. Open Solutions. http://www.suretecsystems.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAO9zbeWseh9tzvqgRAuM9AJwIEayFmaLw0+7Tp1xuXFWmUhXivACgkdbG avlygLLvJbcVY7VaB3bfUcg= =ocI4 -----END PGP SIGNATURE-----

Feb. 24, 2004

[Dillo-dev]Re: Upcoming review.

by Gavin Henry

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - ---------- Original Message ----------- From: Jorge Arellano Cid <jcid(a)dillo.org> To: Gavin Henry <ghenry(a)fedoranews.org> Cc: Dillo mailing list <dillo-dev(a)auriga.wearlab.de> Sent: Tue, 24 Feb 2004 13:22:38 -0300 (CLST) Subject: Re: Upcoming review. > [list: this was originally a personal answer to Gavin, but as it > has general interest information I'm CC to dillo-dev. > It's about a browser comparison article. ] > > Gavin, > > > [...] > > Thanks, I saw a few of these. I will check out the wording etc. Mine might > > not be so in depth, more of a general features thing. But there will be > > figures ie load times etc. which I am sure yours will win. > > :) > > > Know of any monster sites, that would be a good benchmark for the browsers. I > > have ADSL, so banwidth shouldn't be an issue. > > There're some interesting tests to be done. Which one you > choose depends on the time you have, and on what you want to test > for. > > For instance, IMHO, the common "web experience" has four > important factors: So far I have tested the browsers on slashdot, and bbc.co.uk and a few others. They all seem to wait until some pictures arrive until rendering anything. I haven't time these yet. Dillo, displays text immediately, but has some difficulty with CSS. For instance fedoranews.org looks bad :-) Are you familiar with http://wwww.udcast.com/ whcih runs freebsd and has customised apache etc. I thought maybe you have done something like this. As my day job www.invsat.com we had a demo from them and they explained the priciple of http precaching. Instead of requesting 4 images then waiting, it requests all images at once, as this then reduces the latency across a satellite link. Is this how your browser works? (*I haven't look at any code as of yet ;-) ) > > * Network wait time > > * Rendering wait time > > * Time to start seeing content > - streamed rendering > > * Site usability These will be what I base the benchmarks on. > > These are key factors; for instance the same site may be > unusable depending on whether you're on a dialup or broad band. > The same is true for rendering time (influenced by CPU power and > available memory); you may end going to some site only when > you're sitting at a powerful workstation. I don't have access to dial-up, but I have a celeron 400 and a athlon xp 2000 to test on. > > The time to start seeing content is also important. If it takes > too long, it may exceed the user's patience (there're studies > about this). For instance, if a browser needs the whole table > to start rendering, some table-based sites will be exceedingly > annoying to visit (unless your band-width can mitigate this). Dillo is very fast on this. > > The site usability is another key factor. For instance if it's > designed for a certain browser, it may be impossible to use with > another. Alot seem broken. I will properly read the review site you posted so I can see what result they found. > Now, getting back to the test suggestions you asked, these > points can be isolated. > > * Network wait time: > > Get to a site with multiple images, ideally with some coming > from other sites. I'm sure you will find a better example for > an english speaking audience, but this link illustrates the idea: > > http://www.lun.com/_portada/contenido.asp Alot of pics n this one ;) > > * Rendering wait time > > Very simple, load a semi complex page (like slashdot with > comments --a 500KB one), or a large one (as the mysql manual -- I > have one which is more than two Megabytes long). > > Press back, the forward. (you can have some coffee :) Slashdot works perfect. What do you define as a compliant site? All done in CSS? no java script or flash? xhtml or html? Oops, meant for usability section. > > * Time to start seeing content > - streamed rendering > > Get to a table-based semi complex page (300Kb-600Kb) and > measure the time between asking for the URL and when you can > start reading. > > * Site usability > > Well, this depends on whether the page respects standards, how > broken the site implementation is, the browser's support for > the technologies involved, user preferences (javascript may be > disabled, same for cookies, a JVM may not be present, same for > flash, etc). Got it. > > -- > > Now that's for having some numbers to show inside a table for > people with above the average knowledge about browsers :-) > > (very interesting, but not massive). Nope, but very interesting. I will need a quick hand on the stop watch :-) > > Simple usability experience can be explained to less technical > people: > > For instance, take dillo, and dig for something using google. > You'll find that the time you use to make different queries and > to check for alternative links until you find what you look for > is better than with almost anything you've used before. Noticed that. > > The same is true for browsing local documentation (all of those > html files under the /usr/doc or /usr/share/doc directories). > This happens because the combined rendering speed and low > download time (a filesystem) let you move very quickly, back and > forward, make text searches inside the pages, go to another link, > saving you lots of time. Agreed. > > Going with dillo to any web site is different, if it respects > standards (ans so renders OK) its great, but if not, you'll have > to resort to a bigger browser. Agreed. :-( > > The other important points to consider is to test with > different band widths and CPU power. You'll barely notice how > fast dillo is on a 2.2 Ghz machine, and if you only test on broad > band you'll never know that it's possible to have a good browsing > experience with a simple dialup. > > That's it. > > Cheers > Jorge.- - ------- End of Original Message ------- Thanks Jorge, I really appreciate your time and expertise. I think these will be used as the basis for browser benchmarks, stealling the reasoning you gave for the introductions :-) I will give you a preview of it as it starts to resemble something readable. Thanks again. P.S> I posted this to the list from my company account too. - -- Kind Regards, Gavin Henry. Director. Open Source. Open Solutions. http://www.suretecsystems.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAO9X0eWseh9tzvqgRAr/uAJ9piEKRTm8E6Ndqi71Oaecg4kcL9gCfYdma x2S++i7TSEVnL4W8Fmu6J9k= =cwPk -----END PGP SIGNATURE-----

Feb. 24, 2004

Re: [Dillo-dev]CVS password

by Jeremy Henty

On Tue, Feb 24, 2004 at 01:19:18PM -0800, Kelson Vibber wrote: > At 01:00 PM 2/24/2004, Jeremy Henty wrote: > >I just tried to download from CVS as per the instructions on your CVS > >page and I'm getting kicked out. I have tried guessing passwords (my > >email, "guest", "anonymous") but nothing works. > > Just hit enter. D'oh! I tried that too but after nothing happened I assumed something was still wrong. I forgot that login and checkout are separate operations. <FX: slaps self> It's coming down the wire right now. Thanks, Jeremy

Feb. 24, 2004

Re: [Dillo-dev]CVS password

by Kelson Vibber

At 01:00 PM 2/24/2004, Jeremy Henty wrote: >I just tried to download from CVS as per the instructions on your CVS >page and I'm getting kicked out. I have tried guessing passwords (my >email, "guest", "anonymous") but nothing works. What am I doing >wrong? (I am running CVS 1.11.11 on Linux 2.4.25 .) Just hit enter. Kelson Vibber www.hyperborea.org

Feb. 24, 2004

[Dillo-dev]CVS password

by Jeremy Henty

Hello people, I just tried to download from CVS as per the instructions on your CVS page and I'm getting kicked out. I have tried guessing passwords (my email, "guest", "anonymous") but nothing works. What am I doing wrong? (I am running CVS 1.11.11 on Linux 2.4.25 .) $ cvs -z3 -d:pserver:anonymous@auriga.wearlab.de:/sfhome/cvs/dillo login Logging in to :pserver:anonymous@auriga.wearlab.de:2401/sfhome/cvs/dillo CVS password: cvs login: authorization failed: server auriga.wearlab.de rejected access to /sfhome/cvs/dillo for user anonymous Cheers, Jeremy

Feb. 24, 2004

[Dillo-dev]Re: Upcoming review.

by Jorge Arellano Cid

[list: this was originally a personal answer to Gavin, but as it has general interest information I'm CC to dillo-dev. It's about a browser comparison article. ] Gavin, > [...] > Thanks, I saw a few of these. I will check out the wording etc. Mine might > not be so in depth, more of a general features thing. But there will be > figures ie load times etc. which I am sure yours will win. :) > Know of any monster sites, that would be a good benchmark for the browsers. I > have ADSL, so banwidth shouldn't be an issue. There're some interesting tests to be done. Which one you choose depends on the time you have, and on what you want to test for. For instance, IMHO, the common "web experience" has four important factors: * Network wait time * Rendering wait time * Time to start seeing content - streamed rendering * Site usability These are key factors; for instance the same site may be unusable depending on whether you're on a dialup or broad band. The same is true for rendering time (influenced by CPU power and available memory); you may end going to some site only when you're sitting at a powerful workstation. The time to start seeing content is also important. If it takes too long, it may exceed the user's patience (there're studies about this). For instance, if a browser needs the whole table to start rendering, some table-based sites will be exceedingly annoying to visit (unless your band-width can mitigate this). The site usability is another key factor. For instance if it's designed for a certain browser, it may be impossible to use with another. Now, getting back to the test suggestions you asked, these points can be isolated. * Network wait time: Get to a site with multiple images, ideally with some coming from other sites. I'm sure you will find a better example for an english speaking audience, but this link illustrates the idea: http://www.lun.com/_portada/contenido.asp * Rendering wait time Very simple, load a semi complex page (like slashdot with comments --a 500KB one), or a large one (as the mysql manual -- I have one which is more than two Megabytes long). Press back, the forward. (you can have some coffee :) * Time to start seeing content - streamed rendering Get to a table-based semi complex page (300Kb-600Kb) and measure the time between asking for the URL and when you can start reading. * Site usability Well, this depends on whether the page respects standards, how broken the site implementation is, the browser's support for the technologies involved, user preferences (javascript may be disabled, same for cookies, a JVM may not be present, same for flash, etc). -- Now that's for having some numbers to show inside a table for people with above the average knowledge about browsers :-) (very interesting, but not massive). Simple usability experience can be explained to less technical people: For instance, take dillo, and dig for something using google. You'll find that the time you use to make different queries and to check for alternative links until you find what you look for is better than with almost anything you've used before. The same is true for browsing local documentation (all of those html files under the /usr/doc or /usr/share/doc directories). This happens because the combined rendering speed and low download time (a filesystem) let you move very quickly, back and forward, make text searches inside the pages, go to another link, saving you lots of time. Going with dillo to any web site is different, if it respects standards (ans so renders OK) its great, but if not, you'll have to resort to a bigger browser. The other important points to consider is to test with different band widths and CPU power. You'll barely notice how fast dillo is on a 2.2 Ghz machine, and if you only test on broad band you'll never know that it's possible to have a good browsing experience with a simple dialup. That's it. Cheers Jorge.-

Feb. 24, 2004

Re: [Dillo-dev]Frame support in CVS

by Kelson Vibber

On Saturday 21 February 2004 5:19 am, Andreas Kemnade wrote: > I have tried to update Frank's patch. It is not well tested or cleaned > up yet but I simply need to take a deep breath. Thanks! I tried to do that a week or so ago, but didn't get far enough for it to be useful. The patch you posted works so far here (minus obvious things like the incomplete splash page). I've posted some test RPMs in the usual spot, if anyone's interested. > The patch has one big problem. It is too big. Not that it bloats dillo, > but it is hard to review such a big patch. Perhaps it can be split up > and then be committed piece by piece. Has anyone ideas how to split it? > Perhaps in the DilloDoc/BrowserWindow separation, the kbnav thing and > frame support? Agreed. My suggestion would be to pare it down to just what's needed for frames and tabs. Rip out the kbnav changes, the splash screen changes, and everything else. Once that's done, maybe separate the pieces further just to make the pieces easier to review. Maybe three chunks: the doc/window split, frames support, and tabs support. > So what's the way to get frames into cvs? I suspect that the smaller and easier-to-review the patch is, the better chance it'll have of getting accepted. (But I'm just an interested end-user and packager, not a core developer, so what do I know?) > I would not like to see Frank's effort lost. Neither would I! -- Kelson Vibber www.hyperborea.org

Feb. 23, 2004

Re: [Dillo-dev]Italian help translation

by Lupino

Jorge Arellano Cid wrote: > > Hi, list! > > I'm a new user of Dillo, and I found it GREAT! It's handy at > > home, my PII-400 likes it; at the university is EVEN BETTER (we > > have PI-133, so you can imagine how sluggish is netscape..). > > Yes I can! > > Thanks for the encouraging. > > Would you mind telling us more about the lab with PI-133 you're > deploying dillo at? It's a lab in which they install Windows in good computers, and Linux is installed only in OLD machines, namely all PI-133. So Linux is used only by a few people, including me (it's entertaining to round up a good and fast system with a PI-133, especially when you don't have root privileges ;) So I use wmaker/dillo, I have a 20MB home, but I use /tmp to compile my programs, and it works because I ./configure --prefix=/home/../me all the programs/libs. Thanks for your interest and your efforts. :) > > I'm writing to ask if I can translate Dillo help in Italian: is > > there someone else that is translating in italian? If there > > isn't, which files should I translate, and where should I send them? > > Get: > > http://www.dillo.org/dillo-help.html.in > > and send me the translated version. I'm going to download it! I'll send it translated as soon as I have time to do it (in this period I have exams...). -- [ Andrea Spadaccini a.k.a. Lupino / Lupin85 - from Catania ] [ MAIL: lupin85(at)email.it - ICQ#: 91528290 - Linux 2.6.3 ] [ Linux Registered User #313388 - Powered by Slackware 9.1 ]

Feb. 22, 2004

Re: [Dillo-dev]0.8.0 issue

by Jorge Arellano Cid

On Sat, 14 Feb 2004, Johannes Hofmann wrote: > Some more info on the BSD dpid problem: > Actually, there is no need for any changes in the dillo sources. The problem > comes from dpid beeing linked with the "-pthread" flag, which has strange > consequences on the inherited file descriptors. If "-pthread" is used, one > cannot close the inherited file descriptors anymore (one gets EBADF). > I don't know, if this is a bug or a feature of the BSD thread implementation. > > To avoid the problem, one can simple link dpid manually without the > "-pthread" flag and everything works fine, at least for me. Very interesting. AFAIU gcc has a way to set its behaviour with respect to the -pthread flag; that way it can be properly set for each OS. Now, in my experience BSD developers are very competent with regard to technical issues, so if it was done on purpose there may be good reasons behind. If that's the case (and not a misconfigured gcc), we can add a check in our configure.in. Cheers Jorge.-

Feb. 22, 2004

Re: [Dillo-dev]Italian help translation

by Jorge Arellano Cid

On Thu, 12 Feb 2004, Andrea Spadaccini wrote: > Hi, list! > I'm a new user of Dillo, and I found it GREAT! It's handy at > home, my PII-400 likes it; at the university is EVEN BETTER (we > have PI-133, so you can imagine how sluggish is netscape..). Yes I can! Thanks for the encouraging. Would you mind telling us more about the lab with PI-133 you're deploying dillo at? > > I'm writing to ask if I can translate Dillo help in Italian: is > there someone else that is translating in italian? If there > isn't, which files should I translate, and where should I send them? Get: http://www.dillo.org/dillo-help.html.in and send me the translated version. > Thanks for you great work! :-) Cheers Jorge.-

Feb. 22, 2004

Re: [Dillo-dev]progress on AIX?

by Jorge Arellano Cid

On Sat, 14 Feb 2004, Riccardo wrote: > Hello, > > I posted the buildlog I got on AIX... did someone had a look at it to > see if there are some warnings or errors that could explain the > brokeness of dillo on aix? Of course the right way to fix the socklen_t issue is to have: TYPE_SOCKLEN_T in configure.in, or to define it like this: AC_DEFUN([TYPE_SOCKLEN_T], [AC_CACHE_CHECK([for socklen_t], ac_cv_type_socklen_t, [ AC_TRY_COMPILE( [#include <sys/types.h> #include <sys/socket.h>], [socklen_t len = 42; return 0;], ac_cv_type_socklen_t=yes, ac_cv_type_socklen_t=no) ]) if test $ac_cv_type_socklen_t != yes; then AC_DEFINE(socklen_t, int) fi ]) I just want to know it it solves the problem before changing the configure script. Cheers Jorge.-

Feb. 22, 2004

Re: [Dillo-dev]progress on AIX?

by Jorge Arellano Cid

On Sat, 14 Feb 2004, Riccardo wrote: > Hello, > > I posted the buildlog I got on AIX... did someone had a look at it to > see if there are some warnings or errors that could explain the > brokeness of dillo on aix? Yes I did. The only thing capable of producing an illegal instruction I can think of by reading the gcc compile log is: <q> main.c:298: warning: passing arg 3 of `naccept' from incompatible pointer type bookmarks.c:1824: warning: passing arg 3 of `naccept' from incompatible pointer type downloads.c:176: warning: passing arg 3 of `naccept' from incompatible pointer type </q> The third argument of accept() is of socklen_t * type. If the size of the pointed-to value is smaller than the actual type, memory corruption can happen. If AIX doesn't provide socklen_t, dillo blithely defines it as: <q> IO/http.c: #define socklen_t guint32 ../dpi/downloads.c: #define socklen_t guint32 ../dpid/dpi.h: #define socklen_t guint32 </q> Please try changing these to int. This is: #define socklen_t int The other warnings worth of considering at this point are: <q> ld: 0711-224 WARNING: Duplicate symbol: .strcmp ld: 0711-224 WARNING: Duplicate symbol: strcmp ld: 0711-224 WARNING: Duplicate symbol: .pow ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more information. </q> Hope this helps Jorge.-

Feb. 22, 2004

[Dillo-dev]Resuming...

by Jorge Arellano Cid

Hi there, I'm back from my week off! It was very nice with plenty of good times in the southern part of Chile. A bit short but reassuring! In fact it was a few days ago that I started moving the large stack of emails and pending issues... Those still waiting for an answer, please be patient, just keep sending periodic remainders to the mailing list just in case I get lost in the email pile. ;) (email is kind of an entropic activity: the more you write, the more you receive). One of the already answered was a request from LinuxDevices. Now you can check their coverage of 0.8.0 release here: http://linuxdevices.com/news/NS6109819427.html Greetings to everyone Jorge.-

Feb. 22, 2004

Re: [Dillo-dev]GTK error

by Sebastian Geerken

On Sat, Feb 14, Riccardo wrote: > dillo 0.8.0 (well, the last pre series I think...) dies from time to > time with this error: > Gdk-ERROR **: BadMatch (invalid parameter attributes) > serial 6737 error_code 8 request_code 72 minor_code 0 > > this is on solaris, gtk 1.2.10 I'm not sure whether I will be able to help you at all, but for this kind of error, the following is helpful for others. If you are able to reproduce it (or it happens often enough so that the chance is there), try the following: 1. Start gdb with dillo, and run it with "--g-fatal-warnings". 2. When this error occurs, dillo will immediately abort, and you are back in gdb. 3. Type "bt" in gdb. If you are a bit familiar with the internals of dillo, try to find the relevant level on the stack (usually the top-most function of dillo itself), and print the values of the variables of which you think that they might help. Sebastian

Feb. 22, 2004

[Dillo-dev]CSS pre-release

by Sebastian Geerken

Hi! For those interested in the work on CSS, there is a pre-release at <http://www.dillo.org/download/dillo-0.8.0-css-1.tar.gz>. Don't expect too much, it is rather incomplete, even the splash screen cannot be displayed :-) (because of a syntax error in it). It is based on dillo 0.8.0, although much of the functionality in the latter is missing. See the file README for further informations. Sebastian

Feb. 22, 2004

Re: [Dillo-dev]Frame support in CVS

by Andreas Kemnade

On Thu, 05 Feb 2004 14:05:06 -0800 Kelson Vibber <kelson(a)pobox.com> wrote: > At 07:39 PM 2/3/2004, Jacky Lam wrote: > > I am new to dillo and I want to use dillo with frame support. I try > > dillo in CVS and find it only show some link pages for each frames > > respectively. Is it the current status? How about Frank patches? > > I don't know. I tried applying the latest version of Frank's patch > (version 16, from November 24), but ended up with about 30 reject files, so > it's clearly *way* out of sync. Unfortunately, Frank hasn't posted here > since early December. > > Does anyone else know what's going on with this? Even if frames aren't > being merged in yet, it would be nice to have a patch that's in sync with > the new release. > I have tried to update Frank's patch. It is not well tested or cleaned up yet but I simply need to take a deep breath. http://users.auriga.wearlab.de/~andi/dillo/dillo-frames.diff.gz Tested with yesterday's cvs. At least it seems to work at me. There are some issues with scrolling where I have disabled some pieces of code and marked them with a #warning. I think whoever maintains this patch in the future should be noticed about changes in the dillo source which might affect the patch. The patch has one big problem. It is too big. Not that it bloats dillo, but it is hard to review such a big patch. Perhaps it can be split up and then be committed piece by piece. Has anyone ideas how to split it? Perhaps in the DilloDoc/BrowserWindow separation, the kbnav thing and frame support? So what's the way to get frames into cvs? I would not like to see Frank's efford lost. Greetings Andreas Kemnade

Feb. 22, 2004

[Dillo-dev]dillo execution error

by Nagaraja

Hi All, Has any one in the list got dillo working on Strong-Arm (SA1110), I am getting the error when I run dillo-0.7.3. my board is strong-ARM(SA1110) with 128 Mb RAM . currently I am using toolchain build with gcc-332,glibc-232 and binutils-214 to cross compile the dillo. I build the toolchain with msoft-float enabled in gcc and glibc by applying the patches downloaded from http://www.kegel.com/crosstool/ When I searched for the error I found them in the xc/lib/X11/XErrorDB file ,actually I compiled Xserver(X421src-1.tgz X421src-2.tgz, X421src-3.tgz) as usual i.e make World , make and make install since I could't find a way to enable msoft-float option in Xserver cross.def file. Has any one here got an idea what is going wrong here, is it toolchain problem or Xserver cross-compilation problem. same package(dillo-0.7.3) works fine with my previous toolchain used gcc-323,glibc-232 and binutils-21321 with same Xserver. The error is ....... Gdk-WARNING **: locale not supported by Xlib, locale set to C Gdk-WARNING **: can not set locale modifiers dillo_dns_init: Here we go! Disabling cookies. Nav_open_url: Url=>about:splash< Gdk-ERROR **: BadAlloc (insufficient resources for operation) serial 527 error_code 11 request_code 45 minor_code 0 Gdk-ERROR **: BadFont (invalid Font parameter) serial 528 error_code 7 request_code 47 minor_code 0 Thank you all in advance Regards Nagaraja

Feb. 20, 2004

[Dillo-dev]About proxy authorization && password storing

by Ivan Daniluk

Hi, all! I use proxy server, that requires basic authorization. So, I wrote patch for dillo 0.8.0 that enables this feature. It's available on: http://dem2mpg.by.ru/dillo-0.8.0-proxy-auth.patch.gz Main question I would ask is about password storing. This patch just implements new dillorc option - "http_proxyauth", which is the string like "user:password". But, I guess, it's not correspond to dillo security policy, is it? Maybe, we should open popup dialogue and ask user for login/password? Regards! -- Ivan Daniluk, software developer, Ukrainian Computer Labs, Kiev, Ukraine mailto:Ivan.Daniluk@ucl.com.ua

Feb. 17, 2004

Re: [Dillo-dev]rendering 0.7.3 vs. 0.8

by Madis Janson

On Sun, 15 Feb 2004, John wrote: > Hi, > I was presently surprised to see slashdot readable again. Oddly enough, some other websites are not rendering properly anymore. > > Here is an example: > http://damnsmalllinux.org/0.7.3_vs_0.8.png > dillo treats buggy html now differently... .dillo/dillorc:use_old_parser=YES should give old behavior. but i have a patch to eat the cake and have it also... ;) this gives a bit more forgiving html error threatment (for old parser mode), that seams to work fine in most cases: diff -pru dillo-0.8.0/src/html.c dillo08-mzz/src/html.c --- dillo-0.8.0/src/html.c 2004-02-07 01:10:45.000000000 +0200 +++ dillo08-mzz/src/html.c 2004-02-10 01:19:10.000000000 +0200 @@ -1169,7 +1176,8 @@ static void Html_tag_cond_cleanup(DilloH while (stack_idx && (cmp = strcmp(Html_tags_get_name(html->CurrTagIdx), html->stack[stack_idx].tag)) && - (old_mode || + ((old_mode && + !Html_match_tag(html->stack[stack_idx].tag, "table>", 6)) || Html_tags_get_endtag(html->stack[stack_idx].tag_idx) == 'O')){ --stack_idx; } (this is part of http://zone.ee/myzz/dillo/0.8.0/dillo-0.8.0-mzz.html)

Feb. 16, 2004

Re: [Dillo-dev]rendering 0.7.3 vs. 0.8

by Andreas Schweitzer

Hi, On Sun, Feb 15, 2004 at 09:16:48PM -0800, John wrote: > I was presently surprised to see slashdot readable again. > Oddly enough, some other websites are not rendering properly anymore. A very quick answer can be found here :-) : http://article.gmane.org/gmane.comp.web.dillo.devel/1434/ Cheers, Andreas -- **************************** NEW ADDRESS ****************************** Hamburger Sternwarte Universitaet Hamburg Gojenbergsweg 112 Tel. ++49 40 42891 4016 D-21029 Hamburg, Germany Fax. ++49 40 42891 4198

Feb. 16, 2004

[Dillo-dev]rendering 0.7.3 vs. 0.8

by John

Hi, I was presently surprised to see slashdot readable again. Oddly enough, some other websites are not rendering properly anymore. Here is an example: http://damnsmalllinux.org/0.7.3_vs_0.8.png The Dillo on top is 0.8 while the one on the bottom is 0.7.3. Regards, John

Feb. 16, 2004

[Dillo-dev]dillo question

by Donald McKnight

Anyone know where to get a compiled arm binary for yopy 3700? Donald ----- Original Message ----- From: "Globe Trotter" <itsme_410(a)yahoo.com> To: <dillo-dev(a)lists.auriga.wearlab.de> Sent: Saturday, February 14, 2004 9:06 PM Subject: [Dillo-dev]dillo question > Hi, > > New to dillo, and like it! But can not get www.washingtonpost.com to display. > Any ways around it? > > I a using Fedora Core 1 and version dillo 0.80. > > The idea of having non-bloated software is so wonderful and something I so > deeply believe in!! Thanks for working on it!!! > > Best wishes! > > > __________________________________ > Do you Yahoo!? > Yahoo! Finance: Get your refund fast by filing online. > http://taxes.yahoo.com/filing.html > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)lists.auriga.wearlab.de > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

Feb. 15, 2004

[Dillo-dev]dillo question

by Globe Trotter

Hi, New to dillo, and like it! But can not get www.washingtonpost.com to display. Any ways around it? I a using Fedora Core 1 and version dillo 0.80. The idea of having non-bloated software is so wonderful and something I so deeply believe in!! Thanks for working on it!!! Best wishes! __________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html

Feb. 15, 2004

Re: [Dillo-dev]0.8.0 issue

by Johannes Hofmann

Some more info on the BSD dpid problem: Actually, there is no need for any changes in the dillo sources. The problem comes from dpid beeing linked with the "-pthread" flag, which has strange consequences on the inherited file descriptors. If "-pthread" is used, one cannot close the inherited file descriptors anymore (one gets EBADF). I don't know, if this is a bug or a feature of the BSD thread implementation. To avoid the problem, one can simple link dpid manually without the "-pthread" flag and everything works fine, at least for me. Johannes

Feb. 14, 2004

[Dillo-dev]progress on AIX?

by Riccardo

Hello, I posted the buildlog I got on AIX... did someone had a look at it to see if there are some warnings or errors that could explain the brokeness of dillo on aix? -Ric

Feb. 14, 2004

[Dillo-dev]GTK error

by Riccardo

Hello, dillo 0.8.0 (well, the last pre series I think...) dies from time to time with this error: Gdk-ERROR **: BadMatch (invalid parameter attributes) serial 6737 error_code 8 request_code 72 minor_code 0 this is on solaris, gtk 1.2.10 -Ric

Feb. 14, 2004

[Dillo-dev]Thanks!!

by Scorpio Rising

Hey Devs, Just a note to say that Dillo 0.8 configured, compiled and installed flawlessly. Good work! Thanks, -- Gregg

Feb. 13, 2004

Re: [Dillo-dev]0.8.0 issue

by Pete

On Thu, Feb 12, 2004 at 05:33:30PM +0100, Andreas Schweitzer wrote: > There were issues with starting the dipd and/or bookmakrk plugin. > Maybe there still is a race-condition. > > What you see when you start dillo a second time is that > the dpi-system is already up and running. > > How fast is your machine ? And how busy is it ? > > Cheers > Andreas > Andreas, It is a Dual 400 with 512 RAM and not busy at all. Thanks, -- Pete http://milneweb.com http://nomorevirus.com

Feb. 12, 2004

Re: [Dillo-dev]about java script support

by Kelson Vibber

At 01:02 AM 2/12/2004, Thierry Zhong wrote: >Does dillo support java script now? No, it does not. >Or is there any work on this feature? I'm not sure (I'm a user, not a developer), but I think the plans are to avoid JavaScript due to privacy and security implications. I'm basing this on the Project Objectives page: http://www.dillo.org/funding/objectives.html Kelson Vibber www.hyperborea.org

Feb. 12, 2004

Re: [Dillo-dev]0.8.0 issue

by Andreas Schweitzer

Hi, > When I open Dillo up, if I try to open my bookmarks I get a hard lockup and have to 'xkill' dillo. > Anytime I try bookmarks after that, things work just fine. It is only the initial time when I open Dillo that I > have this issue. Anyone else have this issue? Yes - sounds very familar. BUT : lately it works here (for both FreeBSD 4.8-STABLE and 5.1-STABLE). There were issues with starting the dipd and/or bookmakrk plugin. Maybe there still is a race-condition. What you see when you start dillo a second time is that the dpi-system is already up and running. How fast is your machine ? And how busy is it ? Cheers Andreas -- **************************** NEW ADDRESS ****************************** Hamburger Sternwarte Universitaet Hamburg Gojenbergsweg 112 Tel. ++49 40 42891 4016 D-21029 Hamburg, Germany Fax. ++49 40 42891 4198

Feb. 12, 2004

[Dillo-dev]0.8.0 issue

by Pete

Greetings all, I certainly hate to complain after all the good work has been done in this new version of Dillo. I wont complain, I will ask a question: When I open Dillo up, if I try to open my bookmarks I get a hard lockup and have to 'xkill' dillo. Anytime I try bookmarks after that, things work just fine. It is only the initial time when I open Dillo that I have this issue. Anyone else have this issue? Running Free BSD 5.1-RC Thanks for the good work! -- Pete http://milneweb.com http://nomorevirus.com

Feb. 12, 2004

[Dillo-dev]Italian help translation

by Andrea Spadaccini

Hi, list! I'm a new user of Dillo, and I found it GREAT! It's handy at home, my PII-400 likes it; at the university is EVEN BETTER (we have PI-133, so you can imagine how sluggish is netscape..). I'm writing to ask if I can translate Dillo help in Italian: is there someone else that is translating in italian? If there isn't, which files should I translate, and where should I send them? Thanks for you great work! -- Andrea Spadaccini -- a.k.a. Lupino / Lupin85 - Catania - -:* Powered by Slackware Linux 9.1 *:-

Feb. 12, 2004

[Dillo-dev]about java script support

by Thierry Zhong

Hi,all Does dillo support java script now? Or is there any work on this feature? Thanks and Best Regards! Thierry

Feb. 12, 2004

[Dillo-dev]dillo-0.8.0 release

by Jorge Arellano Cid

Hi, Finally it's done. dillo-0.8.0 was released today! (Already submitted to freshmeat and expecting for display). Enjoy Jorge.-

Feb. 9, 2004

Re: [Dillo-dev]dillo-0.8.0-rc1.tar.bz2

by Kelson Vibber

On Sunday 08 February 2004 5:32 am, Jorge Arellano Cid wrote: > Kelson, Phil: I'd wish I could have given you more time for > making the packages, but I'm leaving the city tomorrow for a week > off! :-) RPMs are ready and uploaded. The new index page is ready. All I need to do is swap the two HTML files. -- Kelson Vibber www.hyperborea.org

Feb. 9, 2004

[Dillo-dev]dillo 0.8.0-rc1 on aix

by Riccardo

Hello, 0.8.0-rc1 still segfaults with an illegal instruction on AIX, I have done howewer a clean build from the tarball and logged the build process, maybe some of the warnings could be significative. Since it is quite small I just attach it here. -Ric

Feb. 8, 2004