- Dillo-dev - lists.mailman3.com

[Dillo-dev]forcing dillo to not cache pages
by Brian Hechinger Aug. 1, 2004

Aug. 1, 2004

i'm writing a web based application for my friend using dillo as the primary interface client. dillo is being too hyperactive with the page caching that it uses, and i have to hit reload every time i go back to a page that has had data in the database change. how do i get dillo to not cache those pages and force it to request them everytime so i can always get current data? thanks!! -brian -- "The cats tend to administer themselves, and contrary to the expected facts, the house and everything in it was installed for their benefit." -- Nic Clews

2 1

[Dillo-dev][patch] dillo-cvs fails to detect OpenSSL on FreeBSD
by Thomas-Martin Seck July 31, 2004

July 31, 2004

Hi all, I am the current maintainer of the dillo FreeBSD port. While looking at the current CVS version, I noticed that it fails to detect OpenSSL on FreeBSD (which has OpenSSL 0.9.7d in the base system) because the test program does not link to libcrypto, which causes the linking of the test program to fail with "unresolved symbols". The following patch "works for me", i.e. dillo compiles and the https filter does not error out directly (well, it failed anyway with "The remote certificate cannot be trusted" when I tried accessing <https://www.iks-jena.de> but I guess that is to be expected right now?). Anyway, keep up the good work! Index: configure.in =================================================================== RCS file: /sfhome/cvs/dillo/dillo/configure.in,v retrieving revision 1.76 diff -u -u -r1.76 configure.in --- configure.in 16 Jul 2004 22:57:19 -0000 1.76 +++ configure.in 31 Jul 2004 20:16:28 -0000 @@ -229,7 +229,7 @@ if test "x$ssl_ok" = "xyes"; then old_libs="$LIBS" - AC_CHECK_LIB(ssl, SSL_library_init, ssl_ok=yes, ssl_ok=no) + AC_CHECK_LIB(ssl, SSL_library_init, ssl_ok=yes, ssl_ok=no, -lcrypto) LIBS="$old_libs" fi

1 0

[Dillo-dev]RE: MGDillo-porting Dillo to MiniGUI,are you interesting?
by david feldman July 27, 2004

July 27, 2004

Hello, Since I began using dillo (about a month or so), this is the second time I've seen the topic of a light(er) weight toolkit (the former was fltk, I believe.) I have been considering if it is possible to port either (miniGUI or fltk) or something similar to windows CE; there is a problem in the world of windows CE where the browser microsoft supplied (Pocket IE 3 for CE 2.11 and Pocket IE 4 for CE 3.0) is essentially obsolete (the problem is so severe on CE 2.11 that those machines aren't really robust enough even to access commercial hotspot websites that depend on some degree of competent web client.) There isn't as far as I know a browser under current development targeted at the Windows CE world (that is, something really independent of Pocket IE.) When I first saw Dillo it occured to me that a "Dillo for widows CE" would be nice, but as I looked at GTK+ it seemed alot of work. So, I'm wondering if anyone here in dillo-land has any interest in attacking a port to CE, perhaps through one of these lighter-weight GUI libraries? Tnx much for your time, Dave wb0gaz(a)hotmail.com >From: dillo-dev-request(a)lists.auriga.wearlab.de >Reply-To: dillo-dev(a)lists.auriga.wearlab.de >To: dillo-dev(a)lists.auriga.wearlab.de >Subject: Dillo-dev digest, Vol 1 #480 - 2 msgs >Date: Tue, 27 Jul 2004 06:28:01 +0200 > >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. short absence... (Jorge Arellano Cid) > 2. MGDillo-porting Dillo to MiniGUI,are you interesting? (suowei) > >--__--__-- > >Message: 1 >Date: Mon, 26 Jul 2004 13:15:55 -0400 >From: Jorge Arellano Cid <jcid(a)dillo.org> >To: Dillo mailing list <dillo-dev(a)lists.auriga.wearlab.de> >Subject: [Dillo-dev]short absence... > >Hi there, > > I'm leaving town for a few days. I'll be back on Thursday. > > Cheers > Jorge.- > > >--__--__-- > >Message: 2 >Date: Tue, 27 Jul 2004 09:20:31 +0800 >From: suowei <suowei(a)minigui.net> >To: dillo-dev(a)lists.auriga.wearlab.de >Subject: [Dillo-dev]MGDillo-porting Dillo to MiniGUI,are you interesting? > >Hi,everyone > I am a developer from Beijing Frynman Software of >China(http://www.minigui.com),My boss leaded the >MiniGUI which is lighted GUI library of linux as an open source project >some years ago(http://www.minigui.org). > Now,we want to startup an open source project--MGDillo,its target is >to port the Dillo from GTK+ to MiniGUI, >so,maybe we perhaps need the Dillo developers' help,on the same time,I >hope you can visit the MGDillo's website >:http://www.minigui.net. > If you are interested in this project,you can attend the maillist: >http://lists.minigui.net/cgi-bin/mailman/listinfo/minigui-dillo >welcome everyone~~~ > > suowei > >--------------------------------- >Suo Wei >Beijing Feynman Software Technology Co., Ltd. >A Embedded Linux Tech. & Dev. Tools Provider. > >Mailbox: suowei(a)minigui.net >Website: http://www.minigui.com >Tel: (8610)-82570025 Fax: (8610)-82570026 > > > > >--__--__-- > >_______________________________________________ >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 _________________________________________________________________ FREE pop-up blocking with the new MSN Toolbar get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/

1 0

[Dillo-dev]About the HTML Form
by 索炜 July 27, 2004

July 27, 2004

Hi,there I am reading the Dillo's source code,I want to read the HTML Form part,but I can not find which file is include the form function,who can tell me? thank you:) --------------------------------- Suo Wei Beijing Feynman Software Technology Co., Ltd. A Embedded Linux Tech. & Dev. Tools Provider. Mailbox: suowei(a)minigui.net Website: http://www.minigui.com Tel: (8610)-82570025 Fax: (8610)-82570026

1 0

[Dillo-dev]MGDillo-porting Dillo to MiniGUI,are you interesting?
by suowei July 27, 2004

July 27, 2004

Hi,everyone I am a developer from Beijing Frynman Software of China(http://www.minigui.com),My boss leaded the MiniGUI which is lighted GUI library of linux as an open source project some years ago(http://www.minigui.org). Now,we want to startup an open source project--MGDillo,its target is to port the Dillo from GTK+ to MiniGUI, so,maybe we perhaps need the Dillo developers' help,on the same time,I hope you can visit the MGDillo's website :http://www.minigui.net. If you are interested in this project,you can attend the maillist: http://lists.minigui.net/cgi-bin/mailman/listinfo/minigui-dillo welcome everyone~~~ suowei --------------------------------- Suo Wei Beijing Feynman Software Technology Co., Ltd. A Embedded Linux Tech. & Dev. Tools Provider. Mailbox: suowei(a)minigui.net Website: http://www.minigui.com Tel: (8610)-82570025 Fax: (8610)-82570026

1 0

[Dillo-dev]short absence...
by Jorge Arellano Cid July 26, 2004

July 26, 2004

Hi there, I'm leaving town for a few days. I'll be back on Thursday. Cheers Jorge.-

1 0

[Dillo-dev]Re: any documents about html parser?
by Calvin Yu July 26, 2004

July 26, 2004

yes, I'm going to make dillo able to render chinese. Furthermore, I wish I can add support for JavaScript for dillo. So I must analyse the code of html parser. Am I right? By the way, what do you think of porting GUI to gtk+-directfb? Then we don't need X Windows any longer. I'm a newbie in browser. Please tell me whether what I think is right or not. Thank you very much!

1 0

[Dillo-dev]HTTPS Cleanup
by Garrett Kajmowicz July 24, 2004

July 24, 2004

I have gone through and modified the https.c file to use (what I believe are) your preferred coding standards, with one exception. I *cannot* stand unbraced if statements (or any other statements), and thus I braced them in two locations. I also don't care for use of the tertiary operator, but you wrote the function it is used in, so I don't plan on touching it. I would also like your opinion on how to "clean up" the function save_certificate_home() It has three exit points, and dropping it to fewer would be somewhat of a challenge to do cleanly. There are a few loctions where I believe you broke a statement which would ift on one line, specifically snprintf statements. I might have dont this (though I can't think of why). If this is the case, could you let me know your reasoning behind this? I'd like to learn from this if possible... - Garrett Kajmowicz

2 3

[Dillo-dev]Your attention please: we have a webmaster!
by Jorge Arellano Cid July 23, 2004

July 23, 2004

Hi there, Yes it's true, now we have a dedicated webmaster. Jörgen Viksell (or Jorgen if the umlaut doesn't display) has accepted these duties, so now you'll see our old site starts to renew. For instance now we have a FAQ link (a work in progress). Please contact him for site-related suggestions/fixes/etc. He's in charge now. Cheers Jorge.- PS: Jörgen: please don't forget the webmaster link. (you can use an image or the same mangling as in the bugtrack for the email address). PS2: Garret: I added your suggestion to the NC_Design.

1 0

Re: [Dillo-dev]HTTPS certificate support
by Garrett Kajmowicz July 23, 2004

July 23, 2004

> Producing code quick is not the goal. The point is to produce > well designed code that works OK, and that's easy to > read/review/follow and thus to maintain. I'm spending a lot of time on this because I've been working on a project for several months to revamp some PCs with 32MB of RAM to be sent to the homes of deaf people. I'm running a uClibc based distribution, but I need a good web browser which works. Thus I want to get this done as soon as possible. > The problem I found (and probably your classmates) is that > reviewing rushed-code takes more time than necessary, and once > understood, it changes. In my case is a bit worst because I took > the extra time to polish it, only to find it back with my work > wasted. I crank out a lot of code because I think quickly and clearly, and have no life. If I could comit often enough, I could gurantee you about 4 hours/day solid development for the next month and a half. More if I dropped another pet programming project and some metal work I am doing. I am usually the person doing the code reviews. I'm also the person who tends to put the most documentation into my code to make the most redably readable. > Let me suggest you a second stage after your code is working. > Stop, and take the same amount of time polishing it. Think of the > design, long functions, multiple exit points, global variables, > data structures, future additions, variable names, memory > management, comments, etc. > > Once you finish this second stage, testing for robustness will > be much easier (third stage). Once you've done it, your > classmates will love your code. Most of my classmates can't program *snort*. Then again, neither can the comp sci professors..... > Just an example, multiple exit points make code more complex to > grasp because you have to understand the flow of execution of > each one of the exits, before having confidence of not breaking > it with some changes. I would disagree with that point. With single exit point functions, you have to carry a variable (extra stack allocation) through the application and all code. Thus you can either have large numbers of nested statements (which is very effective and reasonably clean, but excedes line length) or you have your finalized variable being carried through the rest of the application with nothing else to do. With the multi-exit point strategy, you can exit the application as soon as you are done done whatever it is that you need to do. This way you aren't hanging around in the code any more. I have found that tends to make for better code than single-exit writing. > > Another big problem comes with finalization code (freeing > memory, leaving variables in a stable state, return codes, side > effects...). > > Take for instance yes_ssl_support(). Look at the many exit > points and its finalization code, and compare with a single exit > code version. > > It took a lot of time. > > Please follow my advice. Since this is the preffered coding standard (I suggest adding it to the coding standards on the web) I will follow it as you wish. I will follow any coding standards to the letter, and will take suggestions as I see fit. I will modify everything that I have writen to conform to your preferences, and resubmit. I'm tempted to blow away all of my work and start over sust so I can have a sync'd tree to make sane diffs against. *sigh* - Garrett

1 0