- Dillo-dev - lists.mailman3.com

Future of dillo2

by jcid＠dillo.org

On Mon, May 12, 2008 at 10:30:14PM +0000, corvid wrote: > > On Mon, May 12, 2008 at 09:35:46PM +0000, corvid wrote: > > > > http://www.dillo.org/Plans.html > > > > > > Did you commit/make/whatever it? > > > I thought "What changed?" and looked at a cached version, > > > and didn't see any differences. > > > > Not much here AFAIR the form elements and the rewrite of tables > > have now a green ball (finished). > > > > The bulk of it is adding what "should" be added. :-) > > I see the problem now. > > You didn't update the alt tags :) Yes! Now they're updated, and the extra items added, some sorting made and it looks more like what we have. I believe if we can complete the high priority items and stabilize the code we'd have a release candidate in our hands. If Sebastian completes the floating objects in textblock, that'd be great for the release, because dillo2 would show much better rendering in DIV-based and TABLE-based pages Comments? -- Cheers Jorge.-

May 13, 2008

patch: Re: [Dillo-dev] should zlib be required?

by corvid＠lavabit.com

Joerg wrote: > On Sat, May 10, 2008 at 12:17:37PM +0000, corvid wrote: > > Should zlib be required? > > Given many sites allow compression for HTML pages, it is useful to have > around anyway. I would just make it a requirement. Attached. I'm not sure that the old_libs code is serving any purpose, but, being an autoconf newbie, I left it alone.

May 13, 2008

Future of dillo2

by jcid＠dillo.org

On Mon, May 12, 2008 at 11:40:41PM +0200, Diego . wrote: > 2008/5/12 Jorge Arellano Cid <jcid(a)dillo.org>: > > > On Mon, May 12, 2008 at 03:51:42PM -0400, Jorge Arellano Cid wrote: > > > [...] > > > I'll try to update some pages in the site as soon as I find > > > some time. > > > > Just updated: > > > > http://www.dillo.org/cvs.html > > > > with directions on how to get dillo running. Developers, > > packagers, and experienced user should be pointed here. > > > > Somebody please check the directions work. :-P > > > > I doubt about the "exit" command, but i have not test the directions. "exit" is used as "logout" to get out of root. > and: > > > > http://www.dillo.org/Plans.html > > > > There is a line not updated under the "Current Plans for dillo2" text: > "--updated February 2007" > > It can be confusing. Ooops. Fixed. -- Cheers Jorge.-

May 13, 2008

Future of dillo2

by jcid＠dillo.org

On Mon, May 12, 2008 at 03:51:42PM -0400, Jorge Arellano Cid wrote: > [...] > I'll try to update some pages in the site as soon as I find > some time. Just updated: http://www.dillo.org/cvs.html with directions on how to get dillo running. Developers, packagers, and experienced user should be pointed here. Somebody please check the directions work. :-P and: http://www.dillo.org/Plans.html with what's already done. Note that we have more features than what this page states. Some new features as: * multiple character sets (in both HTTP and META). * HTTP-1.1's chunked transfer support. * optional image loading. * experimental gzip decoder. * Implemented the file input control for forms. * Optimized scrolling. * 64-bit ready out of the box. should be added here. -- Cheers Jorge.-

May 12, 2008

Future of dillo2

by jcid＠dillo.org

On Mon, May 12, 2008 at 06:24:30PM +0100, Jeremy Henty wrote: > On Mon, May 12, 2008 at 12:20:45PM -0400, Jorge Arellano Cid wrote: > > On Mon, May 12, 2008 at 03:52:59PM +0000, corvid wrote: > > > The consequences of not informing the outside world about the progress > > > of dillo in any detail: http://wiki.linuxfromscratch.org/blfs/wiki/dillo2 > > > > Please feel free to write them to get that page back on track before > > somebody believes what was written. ;) > > I have a BLFS Trac account so I can probably do it myself. But what > should I change? At a glance: > > * We *do* support FTP and HTTPS. > * Change "can support cookies" to "supports cookies". Yes, but https is basic. If a page has multiple images, the dialog window may spam the user once per image. That's why https went disabled for normal users, and experienced guys/devs were left the chance to enable it. > * "Dillo always interprets web pages as if they had the ISO-8859-1 > encoding." True? It depends on what dillo they talk about. It looks like a dillo2 page, and in that case, it's FLTK2-based, it has nothing to do with GTK1, glib nor GTK2, just FLTK2. The code is now a mixture of C/C++ instead of pure C, etc... It's important to make a difference between dillo1 (C lang, GTK1/glib, __unmantained__, and dillo2 (active branch). If we talk about dillo2 then the statement: "Dillo always interprets web pages as if they had the ISO-8859-1 encoding." is absolutely false. > > * "useless for reading non-English web pages" Surely not true, though > maybe "useless for reading multibyte-encoded pages" is true. If we talk about dillo2, false again. Dillo2 uses utf-8 by default, and utf-8 is multibyte-encoded. On top of that we have all the work corvid put in the character decoding, so now dillo2 can decode a boat load of charsets into utf-8 using iconv. Non english pages render quite well provided you have the necessary fonts installed. There're a few exceptions as with those that render backwards or have collapsing glyphs. For instance, set: vw_fontname="DejaVu Sans" in ~/.dillo/dillorc2 and go to: http://www.gnu.org/home.fa.html Worth a thounsand words! then go to: http://www.gnu.org/ scroll to the bottom and you'll see plenty of non-english pages, that you can click into. If you go to: http://www.bds-bg.org/ you'll see windows-1251 charset handled properly by dillo. etc. > Anything else? Yes, we should compile and provide this information from our web site. Otherwise it will be extremely hard for a non-developer to get right. A good diff document may be got from reviewing the Changelog alone. Here we have the record of all the work we've put in dillo2; from time to time I find there things forgotten long ago! I'll try to update some pages in the site as soon as I find some time. That's the point: lack of time/manpower. All the help is appreciated. Another very important point to be stated is that the plugins and the dpi daemon need to be installed for most things to work. After the build this is done with: make install-strip. Bottom line: current dillo2 is for developers. After we make a release it will be user ready. HTH. -- Cheers Jorge.-

May 12, 2008

Dillo freeze

by Johannes.Hofmann＠gmx.de

On Mon, May 05, 2008 at 05:41:32PM -0400, Jorge Arellano Cid wrote: > Hi there, > > Dillo freezes on this page: > > http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.24.6.tar.bz2.sign > > Dillo bug or FLTK2? Other than I initially thought it is a Dillo bug. The IOwatch for reading is not removed properly. As a result the select call in the fltk event loop keeps failing with EBADF. Attached is a fix for the problem, but I'm not sure whether it is correct. Jorge, can you please have a look at it? Cheers, Johannes

May 12, 2008

Future of dillo2

by onepoint＠starurchin.org

On Mon, May 12, 2008 at 08:08:38PM +0200, Andreas Kemnade wrote: > Hmm, can you really fully test dillo in its build directory? You > won't have the dpi stuff and loose functionality. Perhaps that > should be noted too. Good catch! We don't want BLFS telling users to run Dillo in ways we don't support. Personally I don't understand the author's fear of installing alpha software. Does Dillo's "make install" do anything other than install a few executables and config files? If not then what's the problem with installing it? Also, the instructions should specify " ./configure --prefix=/usr " as the BLFS convention is to install everything in /usr rather than /usr/local . Jeremy Henty

May 12, 2008

Future of dillo2

by akemnade＠informatik.uni-bremen.de

Hi, On Mon, 12 May 2008 18:24:30 +0100 Jeremy Henty <onepoint(a)starurchin.org> wrote: > On Mon, May 12, 2008 at 12:20:45PM -0400, Jorge Arellano Cid wrote: > > On Mon, May 12, 2008 at 03:52:59PM +0000, corvid wrote: > > > The consequences of not informing the outside world about the progress > > > of dillo in any detail: http://wiki.linuxfromscratch.org/blfs/wiki/dillo2 > > > > Please feel free to write them to get that page back on track before > > somebody believes what was written. ;) > > I have a BLFS Trac account so I can probably do it myself. But what > should I change? At a glance: > > * We *do* support FTP and HTTPS. > * Change "can support cookies" to "supports cookies". > > * "Dillo always interprets web pages as if they had the ISO-8859-1 > encoding." True? > > * "useless for reading non-English web pages" Surely not true, though > maybe "useless for reading multibyte-encoded pages" is true. > > Anything else? > Hmm, can you really fully test dillo in its build directory? You won't have the dpi stuff and loose functionality. Perhaps that should be noted too. Greetings Andreas Kemnade

May 12, 2008

Future of dillo2

by onepoint＠starurchin.org

On Mon, May 12, 2008 at 12:20:45PM -0400, Jorge Arellano Cid wrote: > On Mon, May 12, 2008 at 03:52:59PM +0000, corvid wrote: > > The consequences of not informing the outside world about the progress > > of dillo in any detail: http://wiki.linuxfromscratch.org/blfs/wiki/dillo2 > > Please feel free to write them to get that page back on track before > somebody believes what was written. ;) I have a BLFS Trac account so I can probably do it myself. But what should I change? At a glance: * We *do* support FTP and HTTPS. * Change "can support cookies" to "supports cookies". * "Dillo always interprets web pages as if they had the ISO-8859-1 encoding." True? * "useless for reading non-English web pages" Surely not true, though maybe "useless for reading multibyte-encoded pages" is true. Anything else? Regards, Jeremy Henty

May 12, 2008

Future of dillo2

by corvid＠lavabit.com

Jorge wrote: > On Mon, May 12, 2008 at 03:52:59PM +0000, corvid wrote: > > The consequences of not informing the outside world about the progress > > of dillo in any detail: http://wiki.linuxfromscratch.org/blfs/wiki/dillo2 > > Quite funny! :-) > > Got to have courage to write such nonsense! It just shows what impression dillo gives a person who is focused on other things and giving the README a skim. > Please feel free to write them to get that page back on track > before somebody believes what was written. ;) I will. > BTW, if you want to update the website, please do. I don't have access yet.

May 12, 2008