- Dillo-dev - lists.mailman3.com

Doubt...

by Sandesh Sethia

Hello everyone, This is my first post on this group. I am a novice programmer who wanted to know that can I use GTKDFB for creating a PNG image of any window (browser especially) delivered to the GTKDFB toolkit through a C++ program ? Please someone do let me know at the earliest..... Thanks Sandesh

June 12, 2006

Re: [Dillo-dev] Why I don't switch from Firefox today

by newman.x＠seznam.cz

> BTW, please send me some latin2 URLs for development tests. > > -- > Cheers > Jorge.- Hi Jorge, http://www.root.cz/ http://www.abclinuxu.cz/ http://www.wp.pl/ should be fine. Michal

May 30, 2006

Re: [Dillo-dev] Why I don't switch from Firefox today

by Jorge Arellano Cid

On Sat, May 27, 2006 at 05:58:03PM +0200, Jan Stary wrote: > Dear Dillo developers, > > I have been using Dillo since about 0.2.x, and would like to > start this email with "Hail Caesar and everything". Thank you! > > I am really looking forward to the day I replace Firefox with > Dillo completely. These are the reasons I won't do it today: > > 1. Internally, Dillo uses GTK1, which, internally, uses LATIN1. > As I am Czech, the last lines of my install process would be > > $ make install > $ strings src/dillo | grep iso8859 > $ sed -e 's/iso8859-1/iso8859-2/g;' < ./src/dillo > ~/bin/dillo > > which happens to work. I suppose that the transition to FLTK > will make me able to vies pages in other charsets too. BTW, please send me some latin2 URLs for development tests. -- Cheers Jorge.-

May 30, 2006

Re: [Dillo-dev] Why I don't switch from Firefox today

by Jorge Arellano Cid

Hi, On Sat, May 27, 2006 at 10:46:56PM +0300, Joonas Saarinen wrote: > One of my wishes would be to have some limit for the cache growing > endlessly. I run Dillo on a old Libretto 100CT (166MHz/32MB) and if surfing > for long periods (especially when viewing large images) the system goes on > knees swapping and eventually Dillo gets killed for hogging all the memory. > :S Of course there's generally a lot of work to do on the browser and this > feature might require significant changes to the code (?)... Not that hard! Just look inside cache.c and add a remove function for images when the cache size surpasses a certain threshold. An algorithm/heuristic that pleases a diverse group of users is much more difficult. You have to care about not removing images that are currently being displayed (e.g. when using multiple Dillo windows, or removing an image that's being displayed in a page that loads lots of images). Al this blurb reduces to a ref count. -- Cheers Jorge.-

May 30, 2006

Re: [Dillo-dev] Why I don't switch from Firefox today

by Jorge Arellano Cid

Hi Jan, On Sat, May 27, 2006 at 05:58:03PM +0200, Jan Stary wrote: > Dear Dillo developers, > > I have been using Dillo since about 0.2.x, and would like to > start this email with "Hail Caesar and everything". Thank you! Thanks for the recognition. > > I am really looking forward to the day I replace Firefox with > Dillo completely. These are the reasons I won't do it today: > > 1. Internally, Dillo uses GTK1, which, internally, uses LATIN1. > As I am Czech, the last lines of my install process would be > > $ make install > $ strings src/dillo | grep iso8859 > $ sed -e 's/iso8859-1/iso8859-2/g;' < ./src/dillo > ~/bin/dillo > > which happens to work. ... and also breaks iso8859-1 support. > I suppose that the transition to FLTK > will make me able to vies pages in other charsets too. Yes. This is the main point. > > This problem is adressed in > http://teki.jpn.ph/pc/software/index-e.shtml#dillo-i18n > (Are you guys considering any of the patches included in that?) No. I've explained several times that this patches break some internal things in Dillo (as entities, forms, other charsets etc). In the meanwhile I consider this patches a good thing to have in an unofficial branch because the benefits from being able to read your own language sometimes are bigger than broken things with others. The real solution is to have Dillo use utf-8 internally and to convert other encodings to it. This is what we have with dillo FLTK2 (and something that GTK1 doesn't provide. BTW, this is also one of the main reasons for GTK2 existence). Bottom line: we do care about other languages and we're working towards a universal solution for it. > 2. Lack of CSS support. I am aware of > http://www.dillo.org/download/dillo-0.8.0-css-3.tar.gz (which, BTW, > needs to have a few syntax errors fixed before it compiles, see PS). > However, it doesn't do much - looking at http://www.dillo.org won't > even let me click on the links. We've done a lot in this respect. All the internal structures for Dw are designed with CSS in mind. The problem is we don't have the funds to have the main developer of Dw working full time on this. --It's frustrating. > 3. Dillo does not have tabbed browsing. I know it's just a convenience, > not really related to fast rendering and stuff, but this convenience > is just so ... you know, convenient :-) This is also patched into > http://teki.jpn.ph/pc/software/index-e.shtml#dillo-i18n > > After these issues are resolved, you have a converted Firefox user > (not that I would use anything else but Dillo for e.g. reading > documentation). Quite simple to add! I've focused my time on making the FLTK2 prototype work though. > OTOH, don't waste your time on frames and javascript, everybody > knows it's evil. GREAT! I really wish this line of thought was predominant! (although it wouldn't be that hard to implement). -- Cheers Jorge.-

May 30, 2006

Re: [Dillo-dev] Why I don't switch from Firefox today

by Joonas Saarinen

One of my wishes would be to have some limit for the cache growing endlessly. I run Dillo on a old Libretto 100CT (166MHz/32MB) and if surfing for long periods (especially when viewing large images) the system goes on knees swapping and eventually Dillo gets killed for hogging all the memory. :S Of course there's generally a lot of work to do on the browser and this feature might require significant changes to the code (?)...

May 27, 2006

Why I don't switch from Firefox today

by Jan Stary

Dear Dillo developers, I have been using Dillo since about 0.2.x, and would like to start this email with "Hail Caesar and everything". Thank you! I am really looking forward to the day I replace Firefox with Dillo completely. These are the reasons I won't do it today: 1. Internally, Dillo uses GTK1, which, internally, uses LATIN1. As I am Czech, the last lines of my install process would be $ make install $ strings src/dillo | grep iso8859 $ sed -e 's/iso8859-1/iso8859-2/g;' < ./src/dillo > ~/bin/dillo which happens to work. I suppose that the transition to FLTK will make me able to vies pages in other charsets too. This problem is adressed in http://teki.jpn.ph/pc/software/index-e.shtml#dillo-i18n (Are you guys considering any of the patches included in that?) 2. Lack of CSS support. I am aware of http://www.dillo.org/download/dillo-0.8.0-css-3.tar.gz (which, BTW, needs to have a few syntax errors fixed before it compiles, see PS). However, it doesn't do much - looking at http://www.dillo.org won't even let me click on the links. 3. Dillo does not have tabbed browsing. I know it's just a convenience, not really related to fast rendering and stuff, but this convenience is just so ... you know, convenient :-) This is also patched into http://teki.jpn.ph/pc/software/index-e.shtml#dillo-i18n After these issues are resolved, you have a converted Firefox user (not that I would use anything else but Dillo for e.g. reading documentation). OTOH, don't waste your time on frames and javascript, everybody knows it's evil. Sincerely Jan PS: Compiling http://www.dillo.org/download/dillo-0.8.0-css-3.tar.gz on FreeBSD 6.0-RELEASE-p7 with gcc (GCC) 3.4.4 [FreeBSD] 20050518 stops with the following errors: In file included from doctree.c:40: css.h:267:8: warning: extra tokens at end of #endif directive doctree.c: In function `Doctree_construct': doctree.c:746: error: label at end of compound statement doctree.c: In function `Doctree_draw_text': doctree.c:806: error: label at end of compound statement The src/css.h ends with #endif __CSS_H__ which I just commented properly, and the empty labels case DW_STYLE_DISPLAY_LAST: /* compiler happiness */ } and case DOCTREE_ELEMENT: /* compiler happiness */ } in src/doctree.c can obviously be deleted. Then it compiles smoothly.

May 27, 2006

Re: [Dillo-dev] Oriental(?) overlay

by Francis Daly

On Sun, May 14, 2006 at 03:53:56PM -0400, Beartooth wrote: Hi there, > Lately I've been finding many sites covered, or all but covered, with what > may be either very dense pictographs, or a version of the stuff printed on > the backs or carbons of checks to keep part of the data from being legible > on the copies. > > rpm -q says I'm running dillo-0.8.5-2.fc5 ; on this machine the opening > screen doesn't show the version when I open it from another app (It's my > default browser.), but when I open it from its icon, it calls itself > 0.8.5-i18n-misc. Does that mean I have two conflicting versions installed?? Not necessarily. The Fedora Core packaged version dillo-0.8.5-2.fc5 is (I believe) the dillo 0.8.5 version plus a patch they choose to apply. If you go to the url "about:splash" it should show you information on what you have, The patch they apply is one that makes significant changes to the dillo internals, and is not one that the dillo-dev list chooses to support. Either the author, or the FC5 guys who apply the patch, are probably better people to talk to for help. > cron does yum update nightly, and I do it manually from time to time. > > Anyway, what is wrong, and how do I fix it? The description of the problem doesn't match anything I recall seeing (except perhaps possibly when I used the "nil" font family, which defaulted to "rather small", which could count as "dense pictographs"). If you can reproduce it (possibly with a pointer to a screenshot somewhere) using the plain dillo code, people here may be able to offer more help. Alternatively, the about:splash page probably gives more details about the patch author. The plain dillo code can be found at http://www.dillo.org/download.html, with a link to an FC5 rpm at http://www.hyperborea.org/software/dillo/ Good luck, f -- Francis Daly francis(a)daoine.org

May 14, 2006

Oriental(?) overlay

by Beartooth

Lately I've been finding many sites covered, or all but covered, with what may be either very dense pictographs, or a version of the stuff printed on the backs or carbons of checks to keep part of the data from being legible on the copies. rpm -q says I'm running dillo-0.8.5-2.fc5 ; on this machine the opening screen doesn't show the version when I open it from another app (It's my default browser.), but when I open it from its icon, it calls itself 0.8.5-i18n-misc. Does that mean I have two conflicting versions installed?? cron does yum update nightly, and I do it manually from time to time. Anyway, what is wrong, and how do I fix it? -- Beartooth Staffwright, Neo-Redneck Linux Convert FC5; Pine 4.64, Pan 0.14.2.91; Privoxy 3.0.3; CXO 5.0.1 Dillo 0.8.5, Opera 8.54, Firefox 1.5, Epiphany 2.14 Remember I have little idea what I am talking about.

May 14, 2006

Re: Dillo Hungarian translation.

by Jorge Arellano Cid

On Tue, May 09, 2006 at 08:06:37PM +0200, Balazs Melikant wrote: > Hi, Hi Balazs. > > Dillo became one of my favorite applications on my SUSE Linux systems It's Good you like it! > and would have some spare time to prepare a Hungarian translation for > it. I would start it asap, but only if there would be interest from > your side. Yes there is. As you may know, we're working in finishing the port to FLTK2. FLTK2 will allow us to use utf8 characters, and thus i18n and friends will be much easier. The other important point is autoconf stuff to be able to disable all this (embedded devices require apps. to be as lean as possible). While we finish the current prototype tree (not yet publicly available), you may start investigating about i18n: what would it require, how to enable/disable it with autoconf etc, and report me back (I did this research some years ago). The new source tree is very different to the old one (with significative parts in C++ and a new UI module), so there's no point in trying to work on dillo-0.8.6 with a view to port to the new tree. Some research on this topic, and an optional framework for enabling/disabling different translations would be a good contribution you may work on while we finish our prototype. > It would also help me, if you would briefly let me know, > how and where to start... As above. You should also subscribe to dillo-dev and have a this topic discussion there. You may get some help and good advice there. BTW, I'm CC'ing this answer to dillo-dev. -- Cheers Jorge.-

May 11, 2006