- Dillo-dev - lists.mailman3.com

patches

by Phillip Warner

Hi, I'm typically a lurker, but I thought I would release a few modifications I made to dillo. My patch also includes someone's (I can't recall whose) patch that adds external downloading and opening in external browsers. I thought someone may be interested. Here are the modifications I made: <alt>-w closes the window (instead of <ctrl>-q) <alt>-b in viewport opens a new window with the bookmarks <alt>-u view source <ctrl>-r in viewport reloads the current page (bookmark button loads bookmarks in current viewport <ctrl>-h loads homepage vi-style scroll (h = left, j = down, k = up, l = right) <esc> button stops loading the current page (this has no effect on images--they still load if page is fully loaded) The patchfile can be found at: http://www.xmission.com/~locutus/various-locutus.patch and the modifications above can be seen at: http://www.xmission.com/~locutus/index.html#dillo If you find this useful, enjoy! Boa, --Phil

Feb. 19, 2003

dillo-0.7.0 release

by Daniel Pfurtscheller

Works great on my system: Slackware Current (9.0 Beta) and gcc version 3.2.1. Keep up the good work! pfu -- "Contrariwise," continued Tweedledee, "if it was so, it might be, and if it were so, it would be; but as it isn't, it ain't. That's logic!" -- Lewis Carroll

Feb. 18, 2003

dillo 0.7

by Richard A Downing

Best yet. Compiled and rinning fine with LinuxFromScratch V4 using gcc3.2.2 and glibc3.2.1. Jorge, Many thanks! -- Cheers, Richard Richard A Downing FBCS

Feb. 18, 2003

Re: [Dillo-dev] bug tracking engine

by Joe Crayne

On Sun, Feb 16, 2003 at 10:45:49PM +0100, Sebastian Geerken wrote: > > I've been thinking about it (and hacking on dw_page.c) and > > have a partial implementation. It involved adding a pointer > > line->last_float_line which points to the last line that has > > a floater hanging down in the margin of the current line. > > Dw_page_draw_line() traces that pointer and draws that line > > too (and hence also its last_float_line and so on). > > Dw_page_draw_line (which is called by Dw_page_draw, the > implementation of DwWidget::draw) just does the actual drawing > (putting the pixels on the screen), and since you cannot > predict that it is called for all lines (normally it will be > called for those lines seen in the viewport), it should not > change the state of a DwPage. It doesn't. Dw_page_draw_line() traces the pointer and causes possibly other lines to be drawn other than the one it is called for. > - Floats may exceed the allocation of the DwPage, so they may not be > a child widget, instead, an interaction between two DwPage's is > necessary. When does a float exceed the allocation of the DwPage? Is there a new DwPage for new paragarphs? > - Since a float may be defined at a point, where there is > already a float at the respective side, you do not only need > one pointer, but rather a list or a tree, depending on how the > second float is positioned (below or left/right, both is > allowed by the CSS2 spec, but from what I've thought about it, > I believe that the second variant is simpler to implement). How about this: Floats are drawn in sequence just as other words on the line. Nothing special, except that now, line->ascent and line->descent doesnt count floats. Consequently, if the portion of the screen being refreshed doesn't yeild the DwPageLine where the float occurs, then that float wont get properly refreshed. The pointer points to the lowest (highest index) line containing a float that hangs down low enough that it may need to be refreshed also. (Note that if there's another float, then it will be either on the same line or refered back to by the pointer for the float line so that all the floats in the margin get refreshed.) Thanks.

Feb. 18, 2003

I don't really get this...

by slymer＠slymer.org

============================================================ if [ -d /home/silviu/etc ]; then \ /usr/bin/install -c -m 644 -b ./dillorc /home/silviu/etc/; \ elif [ -d /etc/ ]; then \ /usr/bin/install -c -m 644 -b ./dillorc /etc/; \ fi /usr/bin/install: cannot create regular file `/etc/dillorc': Permission denied ============================================================ Here's why I don't really get this part. If dillo is compiled like this: ./configure --prefix=$HOME make && make install-strip upon installation, the install script will try to see it $HOME/etc dir exists. Why this ? Dillo may look in /etc/dillorc if there was no .dillo/dillorc file in $HOME, but since $HOME/.dillo/ exists it is only logical that the script should try to install the rc file in $HOME/.dillo and not $HOME/etc Therefore I suggest that the script should look for $HOME/.dillo not $HOME/etc and it would not be a bad ideea if the dir is missing for the install script to create it... Just my 2 euro cents :} -- Registered Linux user #298569 First law of debate: Never argue with a fool. People might not know the difference.

Feb. 17, 2003

Re: [Dillo-dev] dillo-0.7.0 release

by Ralph Slooten

Hi there, Sorry if this is an obvious problem, but I cannot compile the new dillo. I keep getting: /home/axllent/dillo/src/jpeg.c:131: undefined reference to `jpeg_destroy_decompress' jpeg.o: In function `Jpeg_new': /home/axllent/dillo/src/jpeg.c:211: undefined reference to `jpeg_std_error' /home/axllent/dillo/src/jpeg.c:214: undefined reference to `jpeg_CreateDecompress'/home/axllent/dillo/src/jpeg.c:222: undefined reference to `jpeg_resync_to_restart' jpeg.o: In function `Jpeg_write': /home/axllent/dillo/src/jpeg.c:322: undefined reference to `jpeg_destroy_decompress'/home/axllent/dillo/src/jpeg.c:316: undefined reference to `jpeg_destroy_decompress'/home/axllent/dillo/src/jpeg.c:304: undefined reference to `jpeg_read_scanlines'/home/axllent/dillo/src/jpeg.c:294: undefined reference to `jpeg_start_decompress'/home/axllent/dillo/src/jpeg.c:274: undefined reference to `jpeg_read_header' collect2: ld returned 1 exit status make[3]: *** [dillo] Error 1 make[3]: Leaving directory `/home/axllent/dillo/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/axllent/dillo/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/axllent/dillo' make: *** [all-recursive-am] Error 2 I'm presuming this has something to do with the jpeg libs, and I have: [axllent@ws dillo]$ rpm -qa | grep jpeg libjpeg62-6b-25mdk libjpeg62-devel-6b-25mdk I'm using the standard Mandrake 9.0 release, and previous cvs/releases of dillo have worked great. Any ideas? Greetings Ralph -- http://tuxpower.f2g.net/ http://axljab.homelinux.org:8080/ "Linux is not The Answer. Yes is the answer. Linux is The Question"

Feb. 17, 2003

Re: [Dillo-dev] dillo-0.7.0 release

by John Bradford

> Hi there! > > As I'm in a big hurry now, I just made the release with the > feedback I got so far. It should work ok. > > Well, what else can I say, it's a big milestone! > > Go get it, and enjoy! It's working fine here! John.

Feb. 17, 2003

dillo-0.7.0 release

by Jorge Arellano Cid

Hi there! As I'm in a big hurry now, I just made the release with the feedback I got so far. It should work ok. Well, what else can I say, it's a big milestone! Go get it, and enjoy! Cheers Jorge.-

Feb. 17, 2003

Re: [Dillo-dev] dillo won't start the bm server

by slymer＠slymer.org

On Sun, 16 Feb 2003 11:43:28 +0200 slymer(a)slymer.org wrote: > > I dunno what's going on, but, dillo won't start the > bookmark > server. > > Compiled with: > > ./configure --prefix=$HOME > make > make install-strip > Ugh, cancel on this, dillo just started it, my bad :/ -- Registered Linux user #298569 Gravity brings me down.

Feb. 16, 2003

dillo won't start the bm server

by slymer＠slymer.org

I dunno what's going on, but, dillo won't start the bookmark server. Compiled with: ./configure --prefix=$HOME make make install-strip -- Registered Linux user #298569 Gravity brings me down.

Feb. 16, 2003