- Dillo-dev - lists.mailman3.com

[Dillo-dev]Re: Italian docs
by Jorge Arellano Cid March 1, 2004

March 1, 2004

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.-

2 1

[Dillo-dev]dillo .filter.dpi mini mini howto
by Diego Sáenz March 1, 2004

March 1, 2004

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 ---------------------------------------------

1 1

[Dillo-dev]CSS pre-release 2
by Sebastian Geerken Feb. 29, 2004

Feb. 29, 2004

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

1 0

[Dillo-dev]RE: Error png in make of Dillo - Help
by Eduard Bondarenko Feb. 28, 2004

Feb. 28, 2004

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

1 0

[Dillo-dev]Error png in make of Dillo - Help
by Pablo Feb. 28, 2004

Feb. 28, 2004

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

2 1

[Dillo-dev]CVS
by Pete Feb. 26, 2004

Feb. 26, 2004

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

1 0

[Dillo-dev]Re: Upcoming review.
by Gavin Henry Feb. 25, 2004

Feb. 25, 2004

-----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-----

2 3

[Dillo-dev]CVS password
by Jeremy Henty Feb. 24, 2004

Feb. 24, 2004

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

2 2

[Dillo-dev]Re: Upcoming review.
by Jorge Arellano Cid Feb. 24, 2004

Feb. 24, 2004

[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.-

1 0

Re: [Dillo-dev]Frame support in CVS
by Kelson Vibber Feb. 23, 2004

Feb. 23, 2004

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

1 0