- Dillo-dev - lists.mailman3.com

dillo-2.2-rc1
by corvid＠lavabit.com Feb. 9, 2010

Feb. 9, 2010

As you may have already noticed, we're at RC1 for the next release. Johannes has built a tarball: http://www.dillo.org/download/dillo-2.2-rc1.tar.bz2 SHA1: 146216a1541b20a3e042c62c0db8ee42f173ed01 Please test!

4 12

How to use the tab or other keyboard keys to set foucs on web page links?
by sdliyong＠gmail.com Feb. 7, 2010

Feb. 7, 2010

Hello All, I am using the Dillo on an embedded device for web browsing. Since this device does not support mouse or touchscreen, I have to use the keyboard(or some buttons). I found I cannot set the focus on these links using tab keys( Dillo 2.2-rc1). If there any key configuration settings to set the tab key? If not, I want to modify the source code to add this function, is there any example or related patches for reference? Thanks a lot! Yong

2 1

.hgignore needs updating?
by furaisanjin＠gmail.com Jan. 28, 2010

Jan. 28, 2010

Hi all. This is a minor issue but after building dillo, hg status shows this. ? test/cookies I guess .hgignore needs updating. Regards, furaisanjin

3 9

dpidc
by corvid＠lavabit.com Jan. 26, 2010

Jan. 26, 2010

- Why does install-dpi-local put dpidc in ~/.dillo, anyway? Wouldn't that be unusual for it to be in anyone's path? - Do you think it would be silly to make a little manpage for dpidc? - I'm contemplating making dpidc's exit values distinguish between the cases of: 1) Bad usage. Wrong number of args. 2) I can't find the stuff to communicate with dpid (either because this the first use of dillo, or the dpi system has been changed). 3) Connection refused. I think dpid just isn't running right now. 4) Something is breaking while communicating with dpid.

4 8

display: inline
by tim.nieradzik＠gmx.de Jan. 25, 2010

Jan. 25, 2010

I am currently working on adding CSS support for "display: inline" tags. They are commonly used for navigation menus. As these menus are nothing more than simple unordered lists (<ul>), the items are printed one below the other which wastes lots of space. The patch I came up with does only partially implement support for these tags: The items are correctly displayed within one line but I cannot figure out why there is so much empty space after each item. Perhaps somebody with a better understanding of the dw-code than me might have a look into the issue. If I am correct, the dw/textblock.cc is responsible for calculating the widths. Textblock::wordWrap() looks pretty promising as there is a variable (hasListitemValue) determining whether it is a list item and calculates values for lastLine->leftOffset and words->getRef(0)->effSpace depending on this state. --Tim

6 27

Re: even more cookies SECURITY
by jcid＠dillo.org Jan. 24, 2010

Jan. 24, 2010

Hi, I want to start this 2010 year thanking all the people that have contributed to make Dillo what it is. It's been 10 years and a long way lays behind. Lots of people have shared their time/work/advice/help/money/. After all, what we have now is the addition of all those efforts. Thanks to you all!!! On Mon, Jan 04, 2010 at 11:38:03PM +0000, corvid wrote: > Do we currently have anything that needs to be > fixed/implemented before a release would be sensible? Not that I remember. The only problem I recall was the error message you reported with cookies and later seemed to be working somehow. Besides, AFAIS the repo is stable enough to start rolling the release process. BTW, the cookie story is frustrating. Generally speaking: vested interests strive to kill commodity technologies to introduce their own and henceforward profit monopoly-like. This happens everywhere in the area we deal with e.g. HTTP, HTML, SGML, XML, scripting, flash, java, video streams, audio, cookies, AJAX, etc. Remember that not even the big players were able (nor willing) to implement the SPECS they co-designed. Dillo's game so far had been to support a subset with emphasis on efficiency and privacy. The game is never solved, the point is to decide well where to prune (see bottom line). Speaking of technology: Ten years ago it was images and tables, the FTP, then CGI, then cookies (the stateless HTTP, now with state), then frames (which faded 5 years later), then SGML (which was replaced by XML), then XML (which never succeeded over HTML tag soup). Then CSS (which is necessary these days. Despite IE never gave much for it). Somewhere in the middle there was java (and java beans), but it died. Then Flash, then AJAX, then silverlight, the cloud... IMHO, beyond the hyped technologies "du jour", Dillo is relevant as long as it's able to serve as an efficient information gathering tool, with emphasis on privacy. -- Cheers Jorge.-

3 8

experimental patch: gnutls for the https dpi
by corvid＠lavabit.com Jan. 21, 2010

Jan. 21, 2010

A few hours ago, I started to wonder how much trouble it would be to make https.c understand gnutls instead of openssl. The answer is: If you borrow liberally from the public domain code in the gnutls manual, then not very much! So here's a toy for anyone who would like one: http://www.dillo.org/test/gnutls.0.patch Now we'll _have_ to have a release soon, because we're accumulating so many things to play with after release...

3 5

dillo2.x on Fedora 12
by itsme_410＠yahoo.com Jan. 19, 2010

Jan. 19, 2010

Hi, Any likelihood of getting some Fedora 12 dillo2 RPMS? Thanks for the great work!! Best, T

3 5

Cookies performance
by Johannes.Hofmann＠gmx.de Jan. 19, 2010

Jan. 19, 2010

Hi, I noticed that since the recent DPI update pages which use cookies load slower (e.g. fltk.org) Do others also see that? It could also be OS specific. Cheers, Johannes

3 25

some code for better cookie rejection
by corvid＠lavabit.com Jan. 16, 2010

Jan. 16, 2010

Yesterday I made a rough draft of some code to allow the use of the http://publicsuffix.org/list/ to determine which domains dillo shouldn't allow cookies to be set for: http://www.dillo.org/test/public_suffix.diff I just put it there for safekeeping for now, as I have no plans to clean it up and get it into dillo until after the next release, but it occurred to me that I should at least mention it's there for anyone who uses cookies and lives somewhere where the domain situation is complicated (e.g., Japan). A user would have to add a line to cookiesrc like public_suffix_file /path/to/list/file

1 0