- Dillo-dev - lists.mailman3.com

Re: [Dillo-dev] Automake and dynamic linking
by Jorge Arellano Cid Jan. 31, 2004

Jan. 31, 2004

Jorgen, Andreas, Riccardo, Matti, Bob (portability issues here): Hi, here is a brief covering the latest portability patches now in CVS. These are not final an certainly need testing, so lets try to get it straight. Issues: libpng, pthreads, proper linking, AF_LOCAL, libc5, PS2 libpng: ------ On Wed, 14 Jan 2004, Jorgen Viksell wrote: > Hi! > > tis 2004-01-06 klockan 16.01 skrev Jorge Arellano Cid: > > [...] > > We can't rely on libpng-config because it would break support > > for older distros (for instance slackware 3.9), and there're > > plenty of dillo users with old distros on laptops. > > Fair enough. Using Debian unstable I tend to forget about those people > stuck with non-evolving distros. > > > The current png detection routine has come a long way to be > > able to detect the library on a wide range of SW/HW combinations. > > Maybe the best approach is to try libpng-config first, and when > > not present, try the older libs. > > I made it do so. Could you please try out the fallback code, using: > PNG_CONFIG=foobar ./configure > And if it still fails could you send me the config.log file. Sorry for taking a long time to answer, I got a lot of troubles installing an old libc5 distro (Slackware 3.6) for testing. These were unrelated to the distro and not worth to detail here! ;) The simple fallback-test passed on my slk current, but the old installation payed off quickly, because it failed on it. For instance: <q> checking for libpng-config... missing checking png.h usability... yes checking png.h presence... yes checking for png.h... yes checking libpng/png.h usability... yes checking libpng/png.h presence... yes checking for libpng/png.h... yes checking for png_check_sig in -lpng... no configure: WARNING: *** No libpng found. Disabling PNG images *** </q> Fixed, added "-lm" and a "&& break" to avoid the second header test when the first is present. The version in CVS works both with the current and libc5 distros. As for the image disabling, although I don't see much use for it, I left to avoid some work at this stage. The one thing I don't like is the #ifdef stuff. Well, if it's not worth it can be removed. pthreads: -------- I added the "pthreads" (with an 's') to the search list as Andreas suggested. Riccardo: please test if this works for you. I made a tarball so you don't need to play with autoconf/automake/autogen. URL: http://www.dillo.org/test/dillo-0.8.0-pre.Jan30.tar.gz Note: there's still some work to do with this one, read below. proper linking: -------------- Now the linked libraries are ok (the problem was that dpis and dpid got all of the libraries used by dillo linked in). ...except for pthread that is till present on dpi, dpis. AF_LOCAL: -------- After studying the history of the socket library development and socket.h for linux, BSD, HURD, etc, it seems that all these are (should be) the same: PF_UNIX : old BSD name for PF_LOCAL PF_LOCAL : POSIX for AF_LOCAL PF_FILE : seldom used POSIX for AF_UNIX AF_LOCAL : somewhat old but the most compatible. AF_UNIX : oldest. Fixed this for the whole tarball. It works on both of my testing environments. Should work for everyone. libc5: ----- Now it compiles cleanly with libc5. Except for a warning on a repeated symbol between libjpeg and autoconf. --innocuous though PS2: --- > [Bob wrote] > - my experience of recent cvs, compiled on the playstion2, (blackrhino > 2.2.21 kernel), apparently shows a disconcerting feature. After a few > minutes of scrolling up and down standard web-sites the whole system > will hang (eg it's unpingable, and doesn't respond to any keyboard > input), and needs a hard reset :-( > > Anyone else currently testing on the ps2 please (and hopefully had > better experiences, or a fix)?? I don't have a PS2, but when testing on libc5, there was a similar problem (crash after scrolling, or crash instants after starting) when _some_ of the libraries used by the X server where compiled reentrant and some others not. In fact I was upgrading slk3.6's with the ones at: http://www.linuxsavvy.com/resources/ and some links pointed to the old ones. Most probably these problems stem from an static errno. Another source can be a non reentrant gethostbyname. If dillo-0.7.3 work right on it, I'm puzzled. That's it. This CVS should work on the same platforms than before and with a few more. Please test and report. Best Jorge.- PS: Those that have had problems with 0.7.3, please test this CVS version, or tarball: URL: http://www.dillo.org/test/dillo-0.8.0-pre.Jan30.tar.gz PS2: Ah there's also a fix to include "dpidc". It fixes "make dist".

3 2

Re: [Dillo-dev] building on AIX, gcc, dillo 0.7.3
by Riccardo Mottola Jan. 31, 2004

Jan. 31, 2004

on 1/28/04 5:58 PM, Andreas Schweitzer at Andreas.Schweitzer(a)hs.uni-hamburg.de wrote: >>> >>> and there I just found : >>> >>> http://aixpdslib.seas.ucla.edu/packages/gtk+.html >> Unfortunately, aix 4.2 is quite out of date (but my original rs/6000 is >> beginning to show its age too). > > I just checked. Back then on that machine I had/have : > > $ lslpp -l | egrep -i gtk > freeware.gtk+.rte 1.2.8.0 COMMITTED Gimp ToolKit GUI Library > freeware.gtk+.rte 1.2.8.0 COMMITTED Gimp ToolKit GUI Library > > So, I took it from one of these sites :-) > > Anyways, my hunch yesterday was right when I suspected a small patch > for AIX. I have a diff for AIX lying around which is attached. > The fix produced a result: in fact build stops this way now: gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/local/include -I/usr/local/includ e/gtk-1.2 -I/usr/local/include/glib-1.2 -I/usr/local/lib/glib/include -g -O2 -D_ REENTRANT -D_THREAD_SAFE -Wall -Waggregate-return -c `test -f 'dpi.c' || echo '. /'`dpi.c dpi.c: In function `Dpi_get_server_uds_name': dpi.c:497: `PF_LOCAL' undeclared (first use in this function) dpi.c:497: (Each undeclared identifier is reported only once dpi.c:497: for each function it appears in.) dpi.c: In function `a_Dpi_bye_dpid': dpi.c:749: `PF_LOCAL' undeclared (first use in this function) gmake[1]: *** [dpi.o] Error 1

2 1

ASK FOR HELP:"view source" and edit data to send.
by FUN TOES Jan. 30, 2004

Jan. 30, 2004

Some websites can't be visited by dillo.So I think of writing a patch to view the raw data(including header) from the server and send the raw data modified manually to the server. It is very easy to edit the data to send by modifying the function Http_send_query().But I do not know how to get the raw http data from the server.What is the function that I need read deeply? And I do not think IO_read()is a good selection.The function send raw data to html parse maybe a good selection.But I am a newbie,and I have difficuty in finding the correct function. Would you like help me find it?Appreciation for your help. -- ___________________________________________________ Check out the latest SMS services @ http://www.operamail.com, which allows you to send SMS through your mailbox. Powered by Outblaze

2 1

building on AIX, gcc, dillo 0.7.3
by Riccardo Jan. 27, 2004

Jan. 27, 2004

Hwllo, I sent a private message, of which a reply was CC to this list AFAIK, about building dillo on my AIX system. The problem are threads. Pth can't be used and so I need the system's native threads. A solution was offered me but another email asked for more information, so I report first this information here before trying blindly. configure reports: checking target system type... rs6000-ibm-aix4.2.1.0 as far the system concerns. The error during configure is: checking whether threads work with -pthread... no. Now we will try some libraries. checking for library containing pthread_create... no configure: WARNING: *** No pthreads found. *** gcc -v yields: Reading specs from /usr/local/lib/gcc-lib/rs6000-ibm-aix4.2.1.0/2.95.3/specs gcc version 2.95.3 20010315 (release) while lslpp -l | egrep -i 'thread|xlc|gcc' bos.rte.libpthreads 4.2.1.0 COMMITTED pthreads Library xlC.cpp 3.1.4.0 COMMITTED C for AIX Preprocessor xlC.rte 3.1.4.0 COMMITTED C Set ++ for AIX Application greets, Ric

3 3

[Dillo-dev]Buggy HTML, the new parser and webmasters
by Andreas Schweitzer Jan. 27, 2004

Jan. 27, 2004

Hi all, First : my apologees for a rather large mail ! Now, that the bug counter is in dillo, and with Madis' last post, it's a good coincidence that I just tried to convince webmasters of 3 sites I usually visit to fix their HTML. From 2 I haven't heard a thing (and they are not even THAT huge), but from www.osnews.com I got a reply very fast - and it turned out to be an extremely interesting conversation. I asked her for permission to forward it to the list, and here it goes. I sorted it chronolically, with some comments of mine in between. I omitted my first mail - it was just the HTML warnings of the new parser along with a kind request to fix the page. WARNING, BIG REMINDER : Don't flame her - it's not about this individual site, it's about general practice and the general attitude towards standards ... After all, the e-mail conversation started in privat and she didn't have in mind that a lot of people would read it. And I think she deserves credit for taking her time and lay out her arguments and explaining everything in a very friendly manner. On Sat, Jan 24, 2004 at 06:36:27PM -0800, Eugenia Loli-Queru wrote: > Hello Andreas, > thanks for the heads up. > I looked at the error messages, and I know what is wrong. Please note that > all forms and tables ARE closing in the code, it is just that your parser is > not realizing it. > You see, I start the form inside a table's cell, but I close the form > outside the table. This is not 100% valid code, but it is like that for a > reason. This is causing your parser to spit all these errors (all the errors > below the form error are just a side effect of the first error). > So, the reason I close the form outside that table is because I am trying to > go around bugs on Netscape 4 and IE. As you can see, the cell that holds the > form has a black background color. If I close the form inside that cell, IE > and NS4 create a new paragraph inside that cell, even if my code never asked > for it. And that looks ugly. Up to here, you could argue a lot about how to design a web page, to not wanting to dictate how the page looks and leave it to the browser, to us CSS and whatnot. With enough arguing one could even convince this very author to change (not likely though, see below). BUT : the interesting part comes now : > So, the "trick" that many web developers of my time use a lot (see: > hand-written HTML), is to close the </FORM> outside of tables or places > where it screws up the design. It is a well-known trick, and so your new > parser is going to meet it a number of times in the future. I suggest you The above is frightening .... > fix your parser to understand "non-normal" code like that, and realize that > the form does close as expected. Of course, for us that's not fixing but breaking ;-) .... Here is now my reply (rather long, and you will know the arguments if you follow the lamiling list) : > Hi Eugenia, > > Thanks for the reply and explanation. > First of all : I am not a core developer of that browser - just > a steady user and occasional contributor. > > However, if this mail came from one of the developers or if I told > them to follow your advice, you would either be ignored or flamed ;-) ... > I will try to do neither. So please do keep in mind that my response > is meant as a friendly food for thought or possibly some constructive > criticism. > > Discussions about fixing broken HTML do come up on the mailing list > from time to time. And the consent is to just not do it - for a number > of reasons (I probably will forget some). > - what good are standards if nobody conforms to them, and instead an > own (not very strict !) psuedo-standard develops ? > - It's not a browser's job to guess what the author wanted to have displayed. > - It costs man-power and CPU cycles to detect and fix broken HTML. > We prefer to spend the man-power on developing something useful instead > of broekn HTML-detection code. And we prefer to give the CPU cycles > to the user (BTW, dillo is the snappiest grafic browser I know - maybe Links2) > > All right, but we already detect the problem of your page, you may say :-) .. > and indeed, the *old* parser was closing out of order. In fact, I could > configure dillo to still use the old parser and your page will look great. > BUT : then other pages break :-( - they have buggy HTML, too. And there, > closing tags with the new method is better then with the old method. > So, in chosing which parser to use, the default is the standards complying > method of interpreting HTML (also, the old parser was buggy and not quite > right). Oh - and if we care about the web sites we also tell/told the > authors if these other pages that they have buggy code ! > Now, why then are Mozilla or the other browsers displaying all correctly ? > Probably because they did spend man-power and CPU-cycles to guess what the > author wanted. > I had to smile when you wrote, "Fix your parser to understand non-normal HTML", > because I thought, "That's not fixing it, that's breaking it". > > When I design web pages, I usually make them pass (if possible) > validator.w3.org and if they look ugly in ancient - and buggy ! - browsers, > bad luck ! I realize, my pages are nothing professional like your site, > but still, is it worth to support buggy broswers ? How many visitors > are actually using Netscape 4 ? Probably more than dillo, but the comparison > should be non-buggy vs. buggy browsers. About IE - are all versions > of IE bahving like this ? Then my argument would be, why support MS's > interpretation of standards ? (and outside of HTML you probably will > agrre ;-) ... after all, don't we all know lots of alternatives and fight > for them ?) You as a professional web site probably do have to support > buggy broswers, but the question still may be asked. > > Finally, some links to archived previous discussions : > http://news.gmane.org/group/gmane.comp.web.dillo.devel/thread=1324/force_lo… > (if you don't want to read all of it, read at least Eric Gaudet's posts) > And here is the explanation of the new parser : > http://article.gmane.org/gmane.comp.web.dillo.devel/1434 > > By now, you know that the other problematic site was slashdot ;-) ... > (among others !) which displays ok with the current parser - but also is > buggy HTML - and they know it ! > > And before I forget : Yes, I saw a lot of pages that look quite ugly > with the strict interpretation. And I also only tell the webmasters > of pages for which I care :-) > > And as a really last word : the new parser may indeed have room for > improvement, and some more closing may indeed be possible as a compromise, > BUT, as I said, I'm not a core developer. > > As I said in the beginning, this was meant as food for thought, not flaming. > If you should decide to change HTML after all, that would be fantastic. If > not, hopefully I at least did explain myself well. > > Cheers > Andreas And here is her 2nd answer: > Thank you for the email Andreas, > however, I must say that the code in that form won't change. IE has more > than 70,000 viewers daily on osnews, and Dillo has about 20. So, as you can > understand, being compatible with the broken IE is more important to us, > even if that means that we have to not be validated. In fact, not being > validated, it is a given for big sites, because in order to give a > specific/certain look, you have to do tricks like the one I described to you > in order to render the same on all big browsers. Now you could, of course, go and say "screw this site" .... but the following is at least ineresting food for thought. I don't fully agree, but I can understand the point of view. > Also, please put in mind: my husband is in the browser business. He is a web > browser developer for OpenWave.com among his team. They don't have the > specific problem of out-of-order-tag-closing because they know that many > sites are like that, so they have to go around this problem, OR they won't > be able to sell their browser to anyone. > > This is a market. Even for the free Dillo. Dillo's job is not create the > most "correct" parser in the world, but to render most sites in the world. > If the first was true, then Dillo is nothing but an "Amaya", a test, a proof > of concept. But if the second is true, then Dillo is really a usable by > people browser. > > So, depends what its developers want. If they want a proof of concept, no > problem with me, osnews and most other sites won't work. If they want a > browser that works for most people, they need to sit down and go around > buggy HTML (created by either amateur developers or from developers that > they had to go around bugs). For example, IE even goes around this bug <a/> > and understands that the developer wanted to write </a> instead. Big > browsers do such error checking and go around buggy HTML, because it is the > only way they can be widely used. In my case of course, it was me that I had > to go around their bugs. > > So, it all depends what the Dillo people want. It is not what I, or you, > want, but what their real targets are: proof of concept project or a real > USABLE browser. > > If that was me, it would have being the second. And it ain't my fault that > IE has these bugs that I have to go around, it is my job to make sure my > page renders well for most of my readers. :) > > Rgds, > Eugenia > > --- > Editor in Chief > http://www.OSNews.com When I asked her for permission to forward her mails to the list she added another intersting quote : On Sun, Jan 25, 2004 at 08:53:17PM -0800, Eugenia Loli-Queru wrote: > You can go ahead and quote some of the stuff I said. > BTW, I discussed the matter with my husband (who as I said is in the browser > business) and he told me: > > "Creating an HTML browser and a Web browser are two different things. The > first one just needs to do the job right and parse HTML correctly, the other > one just has to be able to render web pages in any possible mean. These are > two different beasts and targets --unfortunately." > > I am afraid this is the reality of any product though, not just browsers... > Reality market... :( > > Eugenia > Bottom line : it may be possible to convince individual sites to fix their HTML, but what about really big sites that use these ... err ... "workarounds" ? Do they really care how a little browser interprets their HTML ? They care if HTML looks good in IE - reality sucks. It's extremely frustrating. And even more so, when I have to look at garbeled pages ;-) .... The situation may improve over time when more and more sites use CSS and don't have to rely on such dirty formating tricks - but then again, how many bugs has IE there, that authors want/will work around ? And to repeat my reminder : Don't flame her - it's not about this individual site, it's about general practice and the general attitude towards standards ... And again I think she deserves credit for taking her time and lay out her arguments and explaining everything in a very friendly manner. Cheers, Andreas -- **************************** NEW ADDRESS ****************************** Hamburger Sternwarte Universitaet Hamburg Gojenbergsweg 112 Tel. ++49 40 42891 4016 D-21029 Hamburg, Germany Fax. ++49 40 42891 4198

3 2

worried about dillo (cathedral and bazaar)
by linux seaq Jan. 27, 2004

Jan. 27, 2004

Hi, i want to express my gratitude with the dillo developers, this is a really nice product, i use it everyday. I use mozilla only for banking, hotmail and flash sites. I'm only a user i'm not a developer, so my point of view is mainly from an user's perspective. Since dillo's win32 fork and previous discussion, it was clear to me that dillo development was, in some way, closed. That odd feeling was confirmed by the "memo" sent by main developers about patches and additions to dillo. Since that mail, all the "foreign" contributors stopped to share their improvements to dillo project.Or it seems to me at this time (PLEASE PROVE ME WRONG) That's really sad 'cause what i'm seeing right now is some kind of slowness on the development of dillo, and somehow is getting behind in needed functionality (frames,https,downloads,images, a lot of stuff out there). - from an user point of view - I recently re-read the cathedral and bazar paper, and thought to my self that dillo was heading in another direction. It seems to me that there's no intention to receive help from others, or get into account other's contributions. I believed that the main force behind a project weren't its main developers but its users and contributors. That mix made projects grow and grow. And dillo rejected that "magical" force. I'm just writing these thoughts, because as i said, i'm worried about dillo. I can't even imagine how painful would be to surf the web without it. Please everyone who loves dillo, do something so this nice project can grow without restrictions. Please don't get me wrong i don't want to start a trial, i just want dillo to evolve and get better everyday, with everyone help. Regards, Andres

3 2

small politically incorrect html parser patch
by Madis Janson Jan. 27, 2004

Jan. 27, 2004

when you want to use dillo for browsing instead of html test tool, then this little patch is useful for many stupid webs, which randomly close or not close font tags whenever happens and whereever happens... diff -pru -x CVS -x configure -x 'aclocal*' -x 'Makefile*' -x config.h.in dillo-tab/src/html.c dillo/src/html.c --- dillo-tab/src/html.c 2004-01-25 04:37:21.000000000 +0200 +++ dillo/src/html.c 2004-01-27 04:27:18.000000000 +0200 @@ -4280,7 +4372,7 @@ static const TagInfo Tags[] = { {"dt", 'O', Html_tag_open_dt, Html_tag_close_par}, {"em", 'R', Html_tag_open_em, Html_tag_close_default}, /* fieldset */ - {"font", 'R', Html_tag_open_font, Html_tag_close_default}, + {"font", 'O', Html_tag_open_font, Html_tag_close_default}, {"form", 'R', Html_tag_open_form, Html_tag_close_form}, {"frame", 'F', Html_tag_open_frame, Html_tag_close_nop}, {"frameset", 'R', Html_tag_open_frameset, Html_tag_close_default}, It makes a bit less likely, that the font tags screw up every other one (like tables and forms)...

1 1

Dillo cookies
by pete Jan. 27, 2004

Jan. 27, 2004

I am getting this error with Dillo 0.8.0: [pete@happy:.dillo, 07:25 PM, Mon Jan 26]> dillo dillo_dns_init: Here we go! The cookies file has a file lock: disabling cookies in this dillo! Nav_open_url: Url=>about:splash< How do I go about 'unlocking' this file? It was working initially with 0.7.3 Thanks, -- Pete http://milneweb.com http://nomorevirus.com

1 0

An odd request, I know...
by Tom Barnes-Lawrence Jan. 26, 2004

Jan. 26, 2004

Hi, Firstly, I'd like to say I've been using Dillo for over 2 years now, and find it fantastic. Well, apart from a few little details (which I'll probably post to the list in a couple of days, when I'm less busy). So anyways, very well done for this piece of software! Now, my strange request: I'm currently writing a bunch of m4 macros to (statically) generate my personal website. Unfortunately, after ages of trying to come up with a decent layout that rendered properly in various browsers, I came up with pretty much nothing. But I kept seeing, every time I started Dillo, the tidy little splash screen... ...So basically, would Jorge (or whoever is responsible for that) mind if I effectively copied the HTML? I wouldn't bother to ask, as I'm just getting my macros to churn out the tags, rather than copying anybody's *content*, but I thought that might be covered by copyright anyway- in which case, I'm being extra cautious before sticking anything up on my site. Thanks in advance, Tom Barnes-Lawrence

4 6

my.yahoo.com
by pete Jan. 26, 2004

Jan. 26, 2004

Hi all, I am now running the CVS version of Dillo. I am seeming to have a lot of lockups with it. Now I know this is common with CVS but is this something that should be mentioned here? Just wondering what is the proper thing to do. Another, I am still trying to access my yahoo with it but still not possible. Am I missing something that I need to do or is this just typical for Yahoo? -- Pete http://milneweb.com http://nomorevirus.com

1 0

Thanks!
by Arjen Meek Jan. 26, 2004

Jan. 26, 2004

Just a quick "thank you" to all Dillo-devs here. It has replaced Firebird as my default browser less than 5 minutes after installing it. Some experiences: - Dillo combines perfectly with the Ion window manager. A browser shouldn't have to perform window manager tasks, and tabbed browsing becomes a rather silly concept when a sensible window manager combines with a sensible browser. - 0.7.3 compiles & runs cleanly on my 60 Mhz HP PA-RISC system (712/60 running Debian Woody-hppa), and actually renders pages faster on that system than Firebird does on my 600 Mhz Athlon. - A suggestion: why not have CTRL+L switch focus to the URL bar when it is visible, instead of popping up a dialog box? Keep up the good work! Arjen

1 0

Mailing list
by Jorge Arellano Cid Jan. 26, 2004

Jan. 26, 2004

Hi Thorben! Is good to see you around. You've surely noticed I recently switched dillo-dev to only accept posts from its members. This is because it was receiving too much SPAM; the kind that's crafted to bypass SPAM filters. I don't know the current filtering layout of our list, but the fact is that now I receive (as the list administrator) a confirmation email for each rejected message (?) coming from a non-member. :( If the list SPAM-filters everything before checking whether it comes from a member, it's a sane default I suppose, but considering that I have near 3 confirmation requests a day (that repeat themselves for each day I leave these duties unattended), I wonder if it's possible to simply discard them. Regards Jorge.-

1 0

Bug meter
by Jorge Arellano Cid Jan. 26, 2004

Jan. 26, 2004

Hi there! I just commited the new (big) patch that adds a "bug meter" to Dillo's UI. From the Changelog: + Added a bug-meter button that shows the count of detected HTML errors (left click shows the errors, right click offers a validation menu). + Removed the "show_html_warnings" option from dillorc. + Cleaned up the code for the progressbar widgets. Most probably this CVS, plus a few improvements to our configure stuff (compiling in old distros, png detection and proper library linking) will be the basis for dillo-0.8.0-rc1. Please test it and enjoy! Cheers Jorge.- PS: I'm for letting "combat mode" rendering and https for 0.8.1 as its been too much time without a release.

3 2

Re: dillo 0.73 not compiling on slackware 3.9 ( libc5 ) (fwd)
by Jorge Arellano Cid Jan. 25, 2004

Jan. 25, 2004

---------- Forwarded message ---------- Date: Sun, 25 Jan 2004 22:20:04 +0200 (EET) From: matti christensen <mchriste(a)welho.com> To: Jorge Arellano Cid <jcid(a)dillo.org> Subject: Re: dillo 0.73 not compiling on slackware 3.9 ( libc5 ) ok - said and done - and Dillo 0.73 rocks as expected ! what i would like to have is instruction of compiling the libraries myself /mc On Fri, 23 Jan 2004, Jorge Arellano Cid wrote: > > Matti, > > > > > ok - now i've recompiled x 3.3.6 with threads library installed - i also > > recompiled glib, gtk+ and dillo 0.73 - but without success - error message > > is different though; > > > > Gdk-ERROR **: Fatal IO error 11 (Try again) on X server :0.0. > > > > so - what would You suggest ?! > > Please try the pre-compiled libs I suggested. > > I will have to intall a libc5 slackware one of these days to > test this and another issues, but currently my time is devoted to > finishing the "bug-meter" feature for the soon to come 0.8.0 > release. > > Cheers > Jorge.- > > PS: Oh, by the way, sometime ago Jorgen asked me to test the > Fallback libpng detection code of a patch. Can you do that, and > get in contact with him for details? > > > > > > > reentrant ???! > > > > On Wed, 14 Jan 2004, Jorge Arellano Cid wrote: > > > > > > > > Hi Matti, > > > > > > On Tue, 13 Jan 2004, matti christensen wrote: > > > > > > > > > > > do You remember short email discussion with me; compiling Dillo 0.73 on > > > > slak 3.9 with resulting binary which did not run ( i sent an email after > > > > this one and adding threads library etc...) > > > > > > Yes I do. > > > > > > > do You think it might be possible to make Dillo run on this laptop ?! > > > > > > Absolutely! > > > > > > I was about to suggest you trying older versions of dillo to > > > find out which one is the last one to compile/run cleanly on > > > slk3.9, but I had a feel that I've seen this before: > > > > > > > Gdk-ERROR **: Fatal IO error 0 (Success) on X server :0.0. > > > > > > And then I remembered that the standard X server packages that > > > come with slk are not reentrant (thread safe), and that some time > > > ago I had to uprade it and some libs of X from a site of a nice > > > german guy that has done it. > > > > > > I don't have the link now, but for instance look at: > > > > > > http://www.linuxsavvy.com/resources/ > > > > > > There you'll find Reentrant XFree86 3.3.3 Libraries. > > > > > > You can try those, or google until finding 3.3.6 reentrant or > > > recompile them reentrant. > > > > > > > > > I Hope this helps > > > > > > Cheers > > > Jorge.- > > > > > > PS: Please let me know hot it goes. > > > > > > > > > > >

1 0

CPU usage
by pete Jan. 25, 2004

Jan. 25, 2004

Greetings, I notice when I have Dillo open for any bit of time, my CPU usage gets about 98%. Any ideas on fixes for this? O/S is FreeBSD 4.9. I notice this happens on my sons machine as well...same O/S. Thanks! -- Pete http://milneweb.com http://nomorevirus.com

3 6

Re: [Dillo-dev] Yahoo
by Kelson Vibber Jan. 23, 2004

Jan. 23, 2004

At 08:19 AM 1/23/2004, you wrote: >I certainly am liking Dillo still but wondering if I am ever going to be >able to use it on my Yahoo? I try to sign in and it tells me 'unsupported >protocol'. It sounds like Yahoo is requiring an SSL connection to log in. There are some people working on adding SSL support, and at least one set of patches to 0.7.3, though I think there are at least two approaches right now. Anyone have more detail? Kelson Vibber www.hyperborea.org

3 2

Yahoo
by Peter Milne Jan. 23, 2004

Jan. 23, 2004

Good Morning All, I certainly am liking Dillo still but wondering if I am ever going to be able to use it on my Yahoo? I try to sign in and it tells me 'unsupported protocol'. How long before we get to use Dillo 80% of the time? I would guess now I am at about 50% usage for a browser. Thanks for the great work! -- ~~~Pete~~~ http://milneweb.com http://nomorevirus.com

1 0

Url box and more history
by Fisco ;) Jan. 22, 2004

Jan. 22, 2004

Hi all, I have recently started running Dillo, and yip its awesome. Anyhoo I want to add my own custom modifications to the browser, 1) Allowing the history list to be displayed in the url-box, as the user types an address. Kinda like how internet explorer used to work before they used drop down lists. What I want to know is where I can take the history list located in history.c and use it in the url-box whenever keypress is done. Any ideas suggestions? Thanks, Dylan Scott Linux Developer OS: Gentoo Linux 1.4 == Download ringtones, logos and picture messages at Ananzi Mobile Fun. http://www.ananzi.co.za/cgi-bin/goto.pl?mobile

1 0

PEN1S Patch - Enla.rge Your C0CK ! ! . . . . . . . cautioning
by Fabio.giovagnini Jan. 22, 2004

Jan. 22, 2004

1 0

PEN1S Patch - Enla.rge Your C0CK ! ! . . . . . . . retrieves
by Aurora-sparc-devel Jan. 21, 2004

Jan. 21, 2004

1 0

Urgent Utilisation Assistance
by Chief. Otumba Adedeji Jan. 21, 2004

Jan. 21, 2004

ADVISORY BOARD, NIGERIA DEPARTMENT OF PETROLEUM RESOURCES (D.P.R) Dear Urgent Utilisation Assistance. I am chief Otumba Adedeji the chairman of Contract advisory board of the Nigeria Department of Petroleum Resources (D.P.R) I am contacting you based on the esteem recommendation from a high ranking officer of the Chambers of Commerce and Industry, This business proposal I wish to intimate you with is of mutual benefit to you and me and its sucess is based on trust, co-operation and a high level of confidentiality. I am seeking your assistance in the utilisation of the sum US$18.5M ( Eighteen Million Five Hundred Thousand U.S.Dollars). This fund came about as a result of a contract awarded and executed here in this Department of Petroleum Resources(D.P.R). the Contract was supposed to be awarded to two Foreign Contractors to the tune of US$60,000,000,(Sixty Million United Dollars) But in the course of the negotiation that involved the then Senate President Late Chief Chuba Okadigbo while on seat, the Contract was awarded to a Malaysian Contractor at the cost of US$41,500,000(Fourty One Million Five Hundred Thousand U.S Dollars) to our benefit unknown to the Malaysian Contractor. I and the Senate President then resolved to transfer the excess of $18.5M into his Foreign Account in Switzerland for our Utilisation upon the completion of the Contract. This contract has been satisfactorily executed and inspected as the malaysian contractor is presently being paid, With the sudden death of the Senate President Chief Chuba Okadigbo I am forced to seek for a foreign Assistance as I am left alone to Utilise this Fund, but for the fact that I as a civil Servant is forbidden from operating a foreign Account here in my Country, I am seeking your assistance to provide me with foreign Account (Existing or Fresh) which this fund will be transfered for our Utilisation.This fund will shared thus: 35% for you the the Account owner (essential Assistance) 5% has been ear-marked for any incidental expenses, 60% is for me the Initiator of this transaction/deal All arrangements are in place to conclude this transaction within next few weeks of commencement. Please furnish me with your telephone/fax numbers and moblile telephone numbers on your reply to this mail on my confidential e-mail :otumbaadedeji@netscape.net. Regards, Chief Otumba Adedeji (jp)

1 0

Don't get busted ! ! . . . . . . . . . idiot
by Tom Jan. 20, 2004

Jan. 20, 2004

1 0

Don't get busted ! ! . . . . . . . . . looseness
by Jaustin Jan. 20, 2004

Jan. 20, 2004

1 0

Compatibility Patch
by Carlos Daniel Ruvalcaba Valenzuela Jan. 15, 2004

Jan. 15, 2004

Hi everyone. This time i have a little patch for urls with white spaces, it converts them to correct characters (%20), it works well, just download the nav.diff.gz from my site and copy it to dillo/src directory: $ gunzip nav.diff.gz $ patch nav.c nav.diff Answare yes to the question that patchs mades to you. My Web: http://earth.prohosting.com/wbuffer Cheers Carlos Daniel Ruvalcaba

6 5

Re: dillo 0.73 not compiling on slackware 3.9 ( libc5 )
by Jorge Arellano Cid Jan. 15, 2004

Jan. 15, 2004

Hi Matti, On Tue, 13 Jan 2004, matti christensen wrote: > > do You remember short email discussion with me; compiling Dillo 0.73 on > slak 3.9 with resulting binary which did not run ( i sent an email after > this one and adding threads library etc...) Yes I do. > do You think it might be possible to make Dillo run on this laptop ?! Absolutely! I was about to suggest you trying older versions of dillo to find out which one is the last one to compile/run cleanly on slk3.9, but I had a feel that I've seen this before: > Gdk-ERROR **: Fatal IO error 0 (Success) on X server :0.0. And then I remembered that the standard X server packages that come with slk are not reentrant (thread safe), and that some time ago I had to uprade it and some libs of X from a site of a nice german guy that has done it. I don't have the link now, but for instance look at: http://www.linuxsavvy.com/resources/ There you'll find Reentrant XFree86 3.3.3 Libraries. You can try those, or google until finding 3.3.6 reentrant or recompile them reentrant. I Hope this helps Cheers Jorge.- PS: Please let me know hot it goes.

2 1

font segfault
by Johann Koenig Jan. 15, 2004

Jan. 15, 2004

Sometimes dillo just segfaults on me, and I'm finally able to reproduce it. The log from the console is: jkoenig@note:~$ dillo dillo_dns_init: Here we go! Enabling cookies as from cookiesrc... Nav_open_url: Url=>about:splash< Nav_open_url: Url=>http://kernel.org< Dns_server [0]: kernel.org is 0x80ef838 Connecting to 204.152.189.116 HTML warning: line 43, unexpected closing tag: </CENTER>. -- expected </a> HTML warning: line 157, <td> or <th> outside <tr> HTML warning: line 406, unexpected closing tag: </BODY>. -- expected </a> Nav_open_url: Url=>http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2 .6.1-mm2/announce.txt< Connecting to 204.152.189.116 ** CRITICAL **: file dw_style.c: line 385 (Dw_style_font_new_internal): assertion `font_attrs->name != NULL' failed. ** ERROR **: Could not find any font. aborting... Aborted I went to kernel.org and tried to view the changelog for 2.6.1-mm2 -- -johann koenig Now Playing: Metallica - ...And Justice for All : ...And Justice For All Today is Boomtime, the 12nd day of Chaos in the YOLD 3170 My public pgp key: http://mental-graffiti.com/pgp/johannkoenig.pgp

3 6

Re: Found a funny glitch
by Maurice McCarthy Jan. 15, 2004

Jan. 15, 2004

Francis Thanks for the reply. I've godulike know. They are a two man band so they might take an interest. Maurice

1 0

Re: Herba.l Products of the year, 2003
by Berryj Jan. 15, 2004

Jan. 15, 2004

1 0

Re: Herba.l Products of the year, 2003
by Roberto.assente Jan. 15, 2004

Jan. 15, 2004

1 0

Re: spam-safe and basic auth
by Jorge Arellano Cid Jan. 7, 2004

Jan. 7, 2004

On Wed, 7 Jan 2004, Francis Daly wrote: > On Fri, Dec 19, 2003 at 05:45:50PM +0000, Francis Daly wrote: > > On Fri, Dec 12, 2003 at 06:32:54PM -0300, Jorge Arellano Cid wrote: > > > [...] > > > On to another topic, have you had a look at the basic > > > authentication patch by Madis and Tor? > > I've spent a few evenings on this now, and have through the mzz auth > patch, and tried implementing something similar myself. I don't see how > mzz avoids the "redirect loop" problem which it seems to generate. I got > the full mzz-wtab.diff file which applies cleanly to the 0.7.3 code, and > it compiled and ran okay, but failed to even ask for authentication when > I tried it against a 401 page. And it gave the "redirect loop" warning. > > So "doesn't work for me" is the best I can report about it for now, > unfortunately. I'm moving this thread to dillo-dev, just in case Madis or somebody else is interested in helping the development of this feature. > I believe that a 401-handler could be broadly analogous to the 30x > handler, Cache_redirect(). Within Cache_parse_header(), I set a new > value CA_Unauthorized for entry->Flags for a 401 response; and then > within Cache_process_queue(), if that value is set, call the new > Cache_reload_auth() just after where Cache_redirect() is called. Interesting idea. > For adding the Authorization: header, I just edit Http_query to > include an appropriate header if URL_RealmAccess is set (it's not used > elsewhere, and looks like it was intended for 401 usage); and within > Cache_reload_auth(), I set URL_RealmAccess and URL_E2EReload and call > a_Nav_push(). It seems to work fine for authentication pages with no > images, and for authentication pages with images which don't require > authentication. But images that *do* require authentication cause > breakage. Yes, a_Nav_push is for root urls (WEB_RootUrl). > The difficulty is in how to handle non-WEB_RootUrl requests -- I > was following Cache_redirect() for inspiration, and it appears that > Cache_redirect() just ignores them, and I don't see a clean way to > manage them. > > Why are sub entity redirections ignored? Is it because of > security/privacy concerns, or because it was difficult to do them > right? Because the only sub-entity type that dillo handles is image, and near 99% of image redirections is advertising, so given the state of the web, it's a feature! What could be done: my first thought is to check whether an URL (root or not) requires authentication (a flag). If it requires it and we have the auth cached, load it, if not, ignore. > If the former, then whatever the original plan was (using > a_Cache_open_url() or similar) would be worth learning. If the latter, > then unfortunately, in order to handle authentication it's going to have > to be addressed some time :-( Unfortunately I have little time to devote to this design, as I'm given priority to pushing the next release, that is, stabilizing the dpi framework (hopefully done), making the HTML warnings go into a window (not stdout), and adding an HTML error counter together with a "combat mode" parsing feature (a way to try to render pages full of errors in a simplistic but viewable way). Ah, and also giving a check to Keyb-nav-4 if it comes my way... > As I see it, the ideal situation would be that when Cache_parse_header() > finds the 401, it would be useful to check whether we have suitable > authentication credentials, and if so, initiate a new http request which > will feed into (and replace) the same "entry". Doing that directly, > though, probably cuts across too many layers of abstraction. Funny, quite the same I described above! No not that many layers. As you noticed, it can be viewed as a redirection (that asks for credentials on root pages.). It should be possible to implement it this way without breaking the current model. > (I did all my testing on the 0.7.3 codebase; I've just had a look at > CVS and it doesn't appear significantly different.) > > I'm quite happy to keep working on getting authentication working > (Basic, initially, but with the possibility of adding Digest or > anything else in the future) -- if you have any known-dead-ends from > implementing Cache_redirect, or ideas of "safe" ways to intercept the > cache handling, I'd appreciate hearing them. Try to prototype the idea above. It should work. Sorry for not being of more help by now. Cheers Jorge.-

1 0

Re: dillo configuration on AIX
by Jorge Arellano Cid Jan. 7, 2004

Jan. 7, 2004

On Wed, 7 Jan 2004, Riccardo wrote: > Hello, Hi! > I have a question whichmight be a short configuration question. I'm > trying to build dillo 0.7.3 on AIX 4.2.1 using gcc. I already installed > and tested gtk and pth. Pth is different from pthread (POSIX threads). > > when configuring dillo it says it can't find pthreads. In fact it tries > -pthread. I'm sure that AIX has native threads, Yes, but our configure doesn't detect them yet. Although this should not be hard to do: Get the detected target system type string from the configure script. That is, near the third line of output, it says something like: checking target system type... i586-pc-linux-gnu Then add that option to "configure.in" inside the case statement for pthreads. Something like: [...] case $target in *-*-linux*|*-*-solaris*) AC_CHECK_LIB(pthread, pthread_create) ;; + *-*-aix*) + AC_CHECK_LIB(pthreads, pthread_create) + ;; [...] Then follow the directives at: http://home.t-online.de/home/Andreas.Steinmetz/unix/pthreads.html That is basically adding a call to pthread_init() somewhere in main() in dillo.c. Run autoreconf or autogen.sh, configure, make, tweak and send some feedback! :-) > but in any case -lpth > should be used to use libpth. I'm not an expert with AIX development, > I'm using version 4.2.1. > Can dillo be linked against lpth? other projects usually have a > configure option top select the threading model. Against Pth, no. Cheers Jorge.-

2 1

MINISTRY OF MINES AND NATURAL RESOURCES,SIERRA-LEONE
by BRIGEDIER EVANS GIWA Jan. 7, 2004

Jan. 7, 2004

Dear sir, I PRESUME THIS LETTER WILL NOT BE A SURPRISE TO YOU. I am Brigedier Evans Giwa, a soldier by profession, formerly a director with the ministry of Mines and Natural Resources in SIERRA-LEONE before the out - break of the civil war in Sierra-Leone. When I was the director with that ministry, I acted as a link between foreign buyers of Diamonds and the Sierra-Leonian government, but ae a result of the civil war, I diverted the sum of US$36.5 million meant for Sierra-Leone government to a security company in Europe. All I need from you.: (1)Coming up with a viable business that we can invest this fund in. (2)To act as the beneficiary of the said money, as I cannot act in this capacity as I`m still directly or indirect involved in the peace negotiations going on in my country now. (3)To clear the money with the security company in Europe and lodge the money into an account we shall both run. After acknowledging this letter,and indicating your interest and willingness in my proposals, we shall arrange for a meeting in Europe to discuss your areas of interest and investment. As a christain, I will like to invest 20%of the money to help the less priviledged in the society.You willget 25% of the total money for your assistance and 5% will be set aside to offset whatever expenses incurred during the duratation of this transaction. Do kindly contact me through the below email address for further discussion and forsecurity reasons,this business remains confidential. Your Sincerly Brigedier. Evans Giwa giwa(a)consultant.com or egiwa(a)lycos.com

1 0

Improved stability patch for dpi framework!
by Jorge Arellano Cid Jan. 5, 2004

Jan. 5, 2004

Hi Ferdi, (et all) After spending the last weeks hunting for some bugs in the dpi framework deeply, I've succeeded to track them down, and finally, to fix them! From time to time there were multiple dpid instances, this was due to a race condition while waiting for dpid to be "online"; if the process took around a second, dillo could end launching multiple instances of the daemon (I left a commented sleep in the dpid code that served to reliably reproduce it). Another nasty bug was that sometimes dillo crash-locked when requesting a dpi service, for instance: launch dillo -> ask for bm -> kill dpid -> ask for bm -> crash ...this was because of FD inheritance! The bm dpi survived, and kept its parent's FD open, so the connect-test succeeded but there was no server to answer. This couple was really hard to track. As a by-product, lsof showed a FD leak in dpi.c (one per dpi request) and another for dillorc. All of these bugs are fixed in CVS. The good news is that this is a big step towards 0.8.0 release because the stabilization of the dpi-framework is a necessity. There is still at least one pending thing to polish, but it is not a big problem to live with it in 0.8.0 because it causes little harm. This is: if dpid crashes (or is killed), the dpi servers will survive, but the new dpid will launch new processes for them (the old ones will last until their bore-time is reached). No crash, no locks. My first idea was to make a connection-test to dpi servers from dpid at start time, but unfortunately, the parent-child relationship would be lost for the second dpid, so we have to find another way to tell dpid that a dpi-server has finished. The "srs" may be used, although it may be a bit tricky to do when the dpi server has crashed; anyway, the connection test from dpid can detect the crash and bypass the old server with a new one. Cheers Jorge.-

1 0

Re: dillo 0.73 not compiling on slackware 3.9 ( libc5 )
by Jorge Arellano Cid Jan. 4, 2004

Jan. 4, 2004

On Sat, 3 Jan 2004, matti christensen wrote: > Hello ! Hi! > > In Your README You asked to email comments on compiling Dillo on libc5, > and here's some of mine. Good, the first in a long time. > - slackware 3.9 is the last one with libc5 ( glibc 2.0.7pre6 ) and ( gcc > 2.7.23 ) No problem, I use slackware, and have deployed dillo on it in much earlier versions. > - kernel is the latest of 2.0 -series ( 2.0.39 ) which i have compiled > according to attached config and dmesg > > - i also compiled following in for Dillo ;o) > > --- XFree 3.3.6 > --- glib 1.2.9 > --- gtk+ 1.2.9 > --- jpeg-6b > --- libpng 1.2.5 > --- libtiff 3.5.7 > --- zlib 1.1.4 > > - when i try to make Dillo after making the changes to dns.c as You kindly > adviced, compiling stops to src/IO/mime.c saying "mime.c:34: parse error > before `static'" OK. It seems to be the G_GNUC_UNUSED directive. Remove lines 31 to 40 in mime.c. It should stop complaining about mime.c. If this is true, as I do expect, do the same with html.c and IO/Url.c. Please report me how it goes to fix it in current CVS. Cheers Jorge.-

1 0

Best wishes for year 2004
by Jorge Arellano Cid Dec. 31, 2003

Dec. 31, 2003

Hi There, It's early in the morning here in Chile, and I know that in Europe the clock is around 4 to 6 hours ahead, hopefully still in time to send my greetings and best wishes to all the people scattered around the world that participate of dillo-dev. Somewhere inside this december the Dillo project completed four years of existence and continued development. Please excuse me for not displaying a birthday cake picture at the home page; I didn't have the time, but the will to share and celebrate the event still remains! I spent the last months of this year making the arrangements to be able to keep working on dillo the 2004, and hopefully more... It seems that these efforts will flourish and let me work through this new year with renewed energies and hope: let 2004 be a great year for the Dillo project! Cheers & Best wishes to all! Jorge.-

1 0

VRML support in Dillo
by Rich3800＠aol.com Dec. 30, 2003

Dec. 30, 2003

Does Dillo support display of VRML images?

2 1

WINNING NOTIFICATION/FINAL NOTICE
by MR. TOM VANAD Dec. 27, 2003

Dec. 27, 2003

RABOAS INTERNATIONAL LOTTERY NTERNATIONAL PROMOTION/PRIZE AWARD DEPT. HOLLAND REFF: OGS/7316786098/03 BATCH: 14/055/IPD /NL WINNING NOTIFICATION/FINAL NOTICE We are pleased to inform you of the result of the RABOAS Lottery International programs held on the 27st of Decbmer 2003. Your e-mail address attached to ticket number 4411465886-629 with serial number 3772-99 drew lucky numbers 7-14-17-23-31-44 which consequently won in the 2nd category, you have therefore been approved for a lump sum pay out of US$100,000.(One Hundred Thousand Dollars)CONGRATULATIONS!!! Due to mix up of some numbers and names, we ask that you keep your winning information confidential untill your claims has been processed and your money remitted into your accaunt. This is part of our security protocol to avoid double claiming and unwarranted abuse of this program by some participants All participants were selected through a computer ballot system drawn from over 100,000 company and 50,000,000 individual email addresses and names from all over the world. This promotional program take place every three years. We hope with part of your winning you will take part in our end of year 50 million Dollars international lottery. To file for your claim,please contact our fiduciary agent MR.DALE MELLOR, E.U.INTERNATIONAL B.V E.mail:dalemell@netscape.net TEL:31 641 684 576 Remember, all winning must be claimed not later than 11 th of January 2004. After this date all unclaimed funds will be included in the next take Please note in order to avoid unnecessary delays and complications please remember to quote your reference number and batch numbers in all correspondence. Furthermore,should there be any change of address do inform our agent as soon as possible.Congratulations once more! from our members of staff and thank you for being part of our promotional program. Note: Anybody under the age of 18 is automatically disqualified. Sincerely yours, MR. TOM VANAD (Winning Co-ordinator)

1 0

Re: spam-safe and basic auth
by Jorge Arellano Cid Dec. 26, 2003

Dec. 26, 2003

Hi Francis, > [...] > > I was just looking for the spam-safe image blocking patch and > > couldn't find it. Would you mind resending it to me? > > No problem at all. It's included below, updated for current CVS (the > earlier version applied cleanly with a 126-line offset). > > The same caveats as before apply -- there is no "right" answer, so the > choice between omitting the image entirely, faking a submit button, > including a default image, or something else, is pretty arbitrary. > > Faking a submit button is what I went for here, taking inspiration > from http://www.htmlhelp.com/reference/html40/forms/input.html#image > and http://ppewww.ph.gla.ac.uk/~flavell/alt/type-image.html > > If you prefer a different option, I'm sure you're well capable of > coding it ;-) I took the text-submit-button approach (it will also serve for when browsing in "text mode" with Dillo). It took me some time to review it (looks simple but it's not!), I also had to fix a bug... Cheers Jorge.- PS: further testing is welcome! ;)

1 0

Cache expire header...
by Tom Lisjac Dec. 24, 2003

Dec. 24, 2003

Hi All! I've written a small, Dillo friendly wiki/cms system in php that I'm hoping to release in a few weeks. During testing (today's cvs), I found that Dillo's cache wasn't expiring the dynamic pages. Here's the header I was initially using to disable client caching: header("Expires: Sun, 22 Mar 1998 20:00:00 GMT"); header("Last-Modified: " . gmdate("D, d M Y H:i:s") . " GMT"); header("Pragma: no-cache"); header("Cache-Control: post-check=0, pre-check=0"); With this header, Dillo's stdout messages reported "bad clocks"... so I tried sending the same date for Expires and Last-Modified. Dillo's stdout came back with: "Forcing min expire 60 on >the url< instead 0". What does that mean? I really need the content of certain pages to expire immediately when viewed. Any suggestions for the correct header parameters would be greatly appreciated. Thanks! -Tom

2 2

Is something wrong with the cvs repository?
by Matthias Pfeifer Dec. 19, 2003

Dec. 19, 2003

I think the cvs version is currently not working. i do cd src cvs -z3 -d:pserver:anonymous@auriga.wearlab.de:/sfhome/cvs/dillo login cvs -z3 -d:pserver:anonymous@auriga.wearlab.de:/sfhome/cvs/dillo co dillo cd dillo automake -a autoconf (without outputs) and then ./configure gives ./configure: line 650: syntax error near unexpected toke `AM_INIT_AUTOMAKE(dillo,' ./configure: line 650: `AM_INIT_AUTOMAKE(dillo,0.8.0-pre)' - Matthias Pfeifer, Aachen/Germany

1 0

ChessBrain: World Record!
by The ChessBrain Network Dec. 19, 2003

Dec. 19, 2003

The ChessBrain Network T o be removed from our mailing list, send an email to support(a)chessbrain.net

1 0

sending referer
by Jan Stary Dec. 19, 2003

Dec. 19, 2003

Hello, why does Dillo not send the referer header? Without it, I cannot use the http://validator.w3.org/check/referer link, as appearing on the bottom of my pages. This is the only problem which keeps mozilla on my machine. Thank you Jan

3 2

[PATCH] Version 15 of tab/frame/kbnav/etc patch, now with keywords and more...
by Frank de Lange Dec. 19, 2003

Dec. 19, 2003

Hi'all, The next version (15) of my tab/frame/keyboard navigation patch is ready (see bottom of this message for download instructions). This release incorporates a number of bug fixes to keyboard navigation, in response to feedback on the list. It also fixes several other bugs (see non-exhaustive list further down). And, last but not least, there are several new features: keywords, use of location bar for search, local document handling on location bar, user configurable '_blank' target, repeated search, many more configurable key bindings, etc... /* ATTENTION */ This is the first release *without the conditional compile options* for tabs and frames. Tabs, frames and keyboard navigation are standard now, and there is no provision to compile Dillo without support for these features. This is a BIG patch, with many changes. Please test it, and tell me (through the list) about any problems. New features ------------ - keywords Keywords can be used to access sites and locations with short commands in the location bar (and elsewhere). They are defined in the dillorc as a space-separated list of keyword:url pairs: keywords = "<keyword>:<url> <keyword>:<url> ..." %s is in url is replaced by (escaped) location bar contents Example: (in dillorc) keywords="s:http://www.google.com/search?q=%s" "s dillo patch" in the location bar will execute a search on google for the words 'dillo patch'. There is one default keyword, "search". This corresponds to the search_url preference. The web search feature has been changed to use the new code. Keywords currently work in the location bar, in the "open url" window and *from the command line*. This way you can search the web from the command line: dillo "search whatever you want to search for" (enter) [ programming info ] To add keyword processing to a url, you need to make an explicit call to a_Url_string_process_keywords(gchar *str). I explicitly did NOT add the keyword processing code to the default url code path, so keywords can not be initiated through external links. Better safe than sorry... - local file handling in the location bar: type a valid absolute path in the location bar and it will be transformed into a valid file: url. [ programming info ] To add local path processing to a url, you need to make an explicit call to a_Url_string_process_local(gchar *str, gboolean relative) Set relative to TRUE to include relative path processing (from the current directory) to the code path. - location bar search using keywords and/or with popup_dialogs=NO. If you have popup_dialogs=NO in dillorc, pressing the search button on the toolbar or using the search key combination (ALT-s) will search the web for whatever you typed in the location bar (if you have entered search terms) or focus the location bar with the search keyword set. In the latter case just add search terms and press enter to search. - location bar contents are selected when it is focused, deselected when the content area is focused. - the contents of the findtext and websearch entries are selected when they are re-opened. Type a new search term to replace the old term. Use the cursor keys to deselect the contents when you want to add to the existing search term. - the splash screen no longer lives in the binary (as suggested by Indan Zupancic). It is installed by the makefile and should be distributed with dillo. The default location is in the 'sharedstate' directory (default /usr/share/dillo/dillo.html). There is a preference for those who want to change this: splash = NO | <url> This takes any url. Set it to NO to suppress the splash screen alltogether (you will still be able to get to the splash screen by visiting about:splash). The default value is defined in prefs.h: #define DILLO_SPLASH "file:/usr/share/dillo/dillo.html" - There is a new preference for control of the "_blank" tag and handling of new windows in general (as suggested by Andreas Schweitzer): target_blank = SELF | TAB | [WINDOW] Set this to "self" to disable the "_blank" target (no more new windows popping up all around). The other two settings are self-explanatory I guess... This also works for documents opened using the middle mouse button, and documents opened on the command line. For the latter the "self" setting is ignored (it defaults to new windows in that case). - Repeated search by pressing CTRL-g at any time. Unhiglight search by pressing Escape. If search resulted in a highlighted link, this will be unhighlighted as well (to follow that link, press Enter instead of Escape). - many more configurable key bindings. To avoid overloading the scrolled_frame with content-related signals I added a general 'content_command' signal, which gets passed one parameter of type DilloCommand (defined in commands.h). To adjust a keybinding for a command, set a key for the signal 'content_command' for the widget named 'dillo-content' (or for the class GtkDwScrolledFrame). As an example the following binding sets the 'F3' key for the 'repeat find' command (like it does in Mozilla): key_bindings = "binding 'mozilla-keys' { bind 'F3' { 'content_command' (9) } ... (add more bindings if needed) ... } widget '*dillo-content' binding 'mozilla-keys'" There are currently 30 available commands: DILLO_COMMAND_NAVIGATE_BACK, /* 0 */ DILLO_COMMAND_NAVIGATE_FORWARD, /* 1 */ DILLO_COMMAND_NAVIGATE_RELOAD, /* 2 */ DILLO_COMMAND_NAVIGATE_STOP, /* 3 */ DILLO_COMMAND_NAVIGATE_HOME, /* 4 */ DILLO_COMMAND_DUPLICATE_WINDOW, /* 5 */ DILLO_COMMAND_DUPLICATE_TAB, /* 6 */ DILLO_COMMAND_FINDTEXT, /* 7 */ DILLO_COMMAND_FINDTEXT_INCREMENTAL, /* 8 */ DILLO_COMMAND_FINDTEXT_REPEAT_LAST_SEARCH, /* 9 */ DILLO_COMMAND_FINDTEXT_UNHIGHLIGHT, /* 10 */ DILLO_COMMAND_SAVE, /* 11 */ DILLO_COMMAND_SAVE_LINK, /* 12 */ DILLO_COMMAND_BOOKMARK, /* 13 */ DILLO_COMMAND_NEW_WINDOW, /* 14 */ DILLO_COMMAND_NEW_TAB, /* 15 */ DILLO_COMMAND_OPEN_FILE, /* 16 */ DILLO_COMMAND_OPEN_URL, /* 17 */ DILLO_COMMAND_OPEN_LINK, /* 18 */ DILLO_COMMAND_OPEN_LINK_NEW_WINDOW, /* 19 */ DILLO_COMMAND_OPEN_LINK_NEW_TAB, /* 20 */ DILLO_COMMAND_CLOSE_WINDOW, /* 21 */ DILLO_COMMAND_CLOSE_TAB, /* 22 */ DILLO_COMMAND_EXIT, /* 23 */ DILLO_COMMAND_TAB_PREVIOUS, /* 24 */ DILLO_COMMAND_TAB_NEXT, /* 25 */ DILLO_COMMAND_VIEW_SOURCE, /* 26 */ DILLO_COMMAND_VIEW_BOOKMARKS, /* 27 */ DILLO_COMMAND_FOCUS_LOCATION, /* 28 */ DILLO_COMMAND_WEBSEARCH, /* 29 */ DILLO_COMMAND_TOGGLE_FULLWINDOW /* 30 */ DILLO_COMMAND_FOCUS_ACTIVATE, /* 31 */ DILLO_COMMAND_FOCUS_ACTIVATE_NEW_WINDOW, /* 32 */ DILLO_COMMAND_FOCUS_ACTIVATE_NEW_TAB, /* 33 */ DILLO_COMMAND_FOCUS_POPUP, /* 34 */ DILLO_COMMAND_FOCUS_HIDE, /* 35 */ DILLO_COMMAND_FOCUS_MOVE_UP, /* 36 */ DILLO_COMMAND_FOCUS_MOVE_DOWN, /* 37 */ DILLO_COMMAND_FOCUS_MOVE_LEFT, /* 38 */ DILLO_COMMAND_FOCUS_MOVE_RIGHT, /* 39 */ DILLO_COMMAND_FOCUS_MOVE_TAB_BACK, /* 40 */ DILLO_COMMAND_FOCUS_MOVE_TAB_FORWARD, /* 41 */ DILLO_COMMAND_SCROLL_UP, /* 42 */ DILLO_COMMAND_SCROLL_DOWN, /* 43 */ DILLO_COMMAND_SCROLL_LEFT, /* 44 */ DILLO_COMMAND_SCROLL_RIGHT, /* 45 */ DILLO_COMMAND_SCROLL_PAGE_UP, /* 46 */ DILLO_COMMAND_SCROLL_PAGE_DOWN, /* 47 */ DILLO_COMMAND_SCROLL_PAGE_LEFT, /* 48 */ DILLO_COMMAND_SCROLL_PAGE_RIGHT, /* 49 */ DILLO_COMMAND_SCROLL_EDGE_TOP, /* 50 */ DILLO_COMMAND_SCROLL_EDGE_BOTTOM, /* 51 */ DILLO_COMMAND_SCROLL_EDGE_LEFT, /* 52 */ DILLO_COMMAND_SCROLL_EDGE_RIGHT /* 53 */ If you'd like to see any other commands, tell me or the list! [programming info] To add a new command, simply add the name to the DilloCommand enum, add a handler to a_Commands_handler() and, optionally, add a default key binding to a_Commands_init(). The commands.[ch] files are in a bit of a state of flux, as many commands are currently present in two forms: one with a *dd interface, the other (older) with a *bw interface. Where appropriate the older (*bw) versions can and will be removed - the View Source window can now be closed by pressing Escape. View source is (over)due for an overhaul by the way. I might implement the view-source protocol in one of the next patches. - Tab movement is now cyclic, thanks to a patch by Stephan Goetter - the Frame context menu now has navigation controls (as suggested by Stephan Goetter), so it is possible to go back in the frame history. The main history is not yet synchronised with frame actions. [LIST: Is this necessary? Should the 'back' button and menu remember actions inside nested frames or should it do what it does now, remember actions in the top-level document?] - Keyboard navigation can be used to popup context menus, as suggested by Melvin Hadasht. The default binding for context menu is Alt-Enter (and Alt-KP_Enter). The related DILLO_COMMAND is DILLO_COMMAND_FOCUS_POPUP. Fixed bugs ---------- keyboard navigation - all known segfaults - most 'weird navigation order' problems - related issue (now fixed in CVS): a_Findtext_search returned FALSE (instead of FINDTEXT_NOT_FOUND) when a search was performed on an empty page. Since this function is supposed to return a FindtextResult enum value (and the first value in that enum is FINDTEXT_SUCCESS) this made the focus code try to focus a link in an empty page leading to a segfault in the scrolled_window. document abstraction - a problem with tab/page duplication which had the potential to cause segfaults is fixed - selection copy did not work because I forgot to set the owner for the selection in tab mode. This is fixed. REMOVED PREFERENCES =================== These preferences have been removed from the patch. Update your dillorc if you used them. Complain to me (on the list) if you want them back. * tab_instead_of_window: merged into the new target_blank pref * focus_location_on_new: did anyone use the NO setting? * tab_bar_homogeneous: did anyone use the NO setting? * compress_vowels: can be changed during compile if needed, COMPRESS_VOWELS in src/misc.h CHANGED KEY COMBINATIONS ======================== * Internet search: ALT-s (was CTRL-g, CVS CTRL-s) * Repeat search CTRL-g (was nothing, CVS nothing) * View source: ALT-u (was CTRL-u, CVS nothing) * Open URL: CTRL-l (was SHIFT-CTRL-l, CVS CTRL-l) * focus location bar: CTRL-u (was CTRL-l, CVS CTRL-u) If you want the old keys back, add a binding for the related command (see above) If something doesn't work they way it should (or the way you *think* it should), I want to know! For more info on keyboard navigation, see the doc/Keyboard_Navigation.txt document (after applying the patch, naturally...). More information on tabs can be found in doc/Browser_Tabs.txt, for frames see doc/Browser_Frames.txt. The mailing list archives are also a good place to look for answers to questions relating to this patch. REMOVED COMPILE OPTIONS ======================= * --disable-tabs Tabs are a fixed part of the code now * --enable-xhtml-dtd Full frameset support is a fixed part of the code now TODO ==== - add x scrolling capability to Dillo (change anchors, URL_POS, scrolling functions, iterators, etc...). This is needed for better keyboard navigation on wide pages. Tabs, Frames and browser bloat ============================== version: 0.8.0-pre patch: dillo-20031121-tabs.patch.gz unpatched: 297172 bytes patched: 333364 bytes (gcc 3.2.2, binutils 2.13.90.0.18, CFLAGS "-Os") Download instructions ===================== The patch is made against 20031119@15:09 CVS. Do not forget to run ./autogen.sh after applying the patch. You can find the patch on the usual (ad-happy, use an ad-blocking proxy or sane browser) site: http://www.geocities.com/ikbenfrank/ More specifically: Dillo 0.8.0-pre (CVS) ===================== http://www.geocities.com/ikbenfrank/dillo-20031121-tabs.patch.gz size: 116678 bytes (gzipped, as downloaded) 529298 bytes (uncompressed) md5sum: 846a6be5100809cd95553e2cae595f3b (gzipped, as downloaded) 7a94882aa87a8787d959105231fcfacf (uncompressed) As always, check the site for the most recent version Cheers//Frank -- WWWWW ________________________ ## o o\ / Frank de Lange \ }# \| / +46-734352015 \ \ `--| _/ <Hacker for Hire> \ `---' \ +31-640037120 / \ frank(a)unternet.org / `------------------------' [ "Omnis enim res, quae dando non deficit, dum habetur et non datur, nondum habetur, quomodo habenda est." ]

3 4

Automake and dynamic linking
by Jorge Arellano Cid Dec. 18, 2003

Dec. 18, 2003

Hi guys, I just noticed that out automake process ends linking all the libraries required by dillo to dpid and every dpi! For instance: $ldd dpid libpthread.so.0 => /lib/libpthread.so.0 (0x4001f000) libpng.so.3 => /usr/lib/libpng.so.3 (0x40071000) libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x4009b000) libz.so.1 => /usr/lib/libz.so.1 (0x400b8000) libgtk-1.2.so.0 => /usr/lib/libgtk-1.2.so.0 (0x400c5000) libgdk-1.2.so.0 => /usr/lib/libgdk-1.2.so.0 (0x401e3000) libgmodule-1.2.so.0 => /usr/lib/libgmodule-1.2.so.0 (0x40214000) libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0 (0x40218000) libdl.so.2 => /lib/libdl.so.2 (0x40239000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x4023c000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x4024a000) libm.so.6 => /lib/libm.so.6 (0x40311000) libc.so.6 => /lib/libc.so.6 (0x40334000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) Wow! And the kernel reports: VmSize: 4684 kB VmLck: 0 kB VmRSS: 1160 kB VmData: 304 kB VmStk: 16 kB VmExe: 24 kB VmLib: 4208 kB This means that resident dpis (servers) can end wasting virtual memory after dillo exits by retaining unused libs in VmLib. If someone here can make a patch for this problem, it'd be a great time saver. Please? :-) Cheers Jorge.-

2 2

wanted: CPU overhead source.
by Jorge Arellano Cid Dec. 17, 2003

Dec. 17, 2003

Hi, I just noticed that utilities.html (from ImageMagick manual), takes near three times more time to render with CVS than with 0.7.3. That page is 230KB and has no images. It takes 3 seconds to render with 0.7.3 vs 9 seconds of CVS (on a slow machine). The same is true for the new and old parser. Can somebody please profile it to find the overhead source? (./configure --enable-gprof). TIA Jorge.-

3 7

Re: [Dillo-dev] Re: BUG#494
by Trent Jarvi Dec. 15, 2003

Dec. 15, 2003

> > > Hi, > > Some *BSD don't provide a reentrant gethostbyname: > > <q source='manpage of a BSD'> > BUGS > These functions use static data storage; if the data is needed for future > use, it should be copied before any subsequent calls overwrite it. Only > the Internet address format is currently understood. > </q> > > The only one I know that doesn't work is openBSD >= 3.3. > (produces random lookups) > > Does anyone know the situation better? > It is for disabling threaded dns lookups at configure time. > > Would gethostbyname_r() solve this? -- Trent Jarvi taj(a)www.linux.org.uk

2 1

*BSD and gethostbyname
by Jorge Arellano Cid Dec. 13, 2003

Dec. 13, 2003

Hi, Some *BSD don't provide a reentrant gethostbyname: <q source='manpage of a BSD'> BUGS These functions use static data storage; if the data is needed for future use, it should be copied before any subsequent calls overwrite it. Only the Internet address format is currently understood. </q> The only one I know that doesn't work is openBSD >= 3.3. (produces random lookups) Does anyone know the situation better? It is for disabling threaded dns lookups at configure time. Cheers Jorge.- PS: That's it. A thread follows with other minutiae... ---------- Forwarded message ---------- Date: Sat, 13 Dec 2003 14:26:58 +0100 (MET) From: Anders Gavare <md1gavan(a)mdstud.chalmers.se> To: Jorge Arellano Cid <jcid(a)dillo.org> Subject: Re: [Dillo-dev] Re: BUG#494 On Sat, 13 Dec 2003, Jorge Arellano Cid wrote: > On Sat, 13 Dec 2003, Anders Gavare wrote: > > How typical: now I found this already mentioned in dillo's README file. > > Sorry to have bothered you. :-) Still, this is something that should > > be detected and taken care of by the configure script... > > Thanks for the info. > > Can you send me a patch for configure.in? Unfortunately I don't think I'm familiar enough with neither Dillo nor the configure system to add such a functionality. It took several days for me to track down the widget bug (#494), and several hours of testing to figure out this gethostbyname() bug. > Or at least the contents of the detected $target variable on > your machine (an extra line with "echo $target" after > AC_CANONICAL_SYSTEM will tell). sparc64-unknown-openbsd3.3 The same problem should exist in other BSDs as well, but I've not actually seen the symptoms. The manpages of FreeBSD 4.5 and NetBSD-current (after 1.6.1) have the following in their gethostbyname(3) manpages: BUGS These functions use static data storage; if the data is needed for future use, it should be copied before any subsequent calls overwrite it. Only the Internet address format is currently understood. Imho, if Dillo aims for platform independance, which is one of the things I like best about Dillo, this feature (multithreaded DNS lookups) would be better off disabled _unless_ the underlying platform explicitly allows it. Not the other way around. That's my opinion, anyway. Anders

1 0

BUG#494
by Jorge Arellano Cid Dec. 13, 2003

Dec. 13, 2003

Hi, Some time ago I read this bug and now the CVS has a bunch of fixed for signed/unsigned conflicts that may cause trouble on 64bit machines. Please test our CVS and tell me if the bug persists. You can send me the screenshot (not to dillo-dev please) Cheers Jorge.-

2 4

statically linked dillo
by Jorge Arellano Cid Dec. 12, 2003

Dec. 12, 2003

Hi, ---------- Forwarded message ---------- Date: Thu, 11 Dec 2003 23:30:05 +0000 From: Victor M. <voremo(a)safe-mail.net> To: jcid(a)softhome.net Subject: dillo Can dillo be compiled into a static, self-contained executable to run under X? (.i.e. that it can be pressed on and run from a publication CD, with no need for GTK libraries on the target computer...?) Victor --------------------------------------- Does anyone here know/done it? Cheers Jorge.-

2 1

[PATCH] I18N
by Kiyo Dec. 12, 2003

Dec. 12, 2003

Hi. I made an I18N patch for Dillo. This is simple I18N. Japanese, Chinese, Korean, Greek, etc. Only LOCALE character are displayed. Not support "complicated languages". (such as Arabic) Internal code is mainly processing by UTF-8. UTF-8 wrapper of a part of APIs of GTK+1 is included. This wrapper will be unnecessary if Dillo ports to FLTK2 or GTK+2. But, I think that others will be probably needed. A part of this patch referred to Mr. Robert Thomson's Japanese patch. It is better to also gettextize. But, it has not applied to this patch. http://teki.jpn.ph/pc/software/dillo-cvs2003121203-i18n.diff.bz2 md5sum: 5a1e0428d0e049a081dd4721d48b1de2 and... For Core team, may not be desirable... This is large patch for Dillo-0.7.3 . I18N(UTF-8 support and gettext) Xft antialiasing(multibyte support) Setting Tool(gtk+) frame&tab(ver.10 with I18N fix) gzip compression transmission SearchBox UserAgent changer Referer meta-refresh SSL BASIC authorization Fix page scroll Character entity references(Probably almost is supported. but it's dependent on LOCALE.) and some various changes. Various persons' patches are unified and an original improvement is added. http://teki.jpn.ph/pc/software/dillo-0.7.3-i18n-misc-20031208.diff.bz2 md5sum: 0d3bdf88a3e61a4659e708ac4a971c1f #I'm hoping that both user and developer can become happy :-) --- Kiyo<kiyo(a)teki.jpn.ph> http://teki.jpn.ph/

1 0