- Dillo-dev - lists.mailman3.com

The sound of silence
by Joonas Saarinen Nov. 29, 2006

Nov. 29, 2006

Hello, It has been almost two months of silence on this list and I thought to ask how are you doing? :) Anything new about the "Campaign to help Dillo survive"? Etc.

2 1

Re: [Fwd: Dillo article precisions]
by Jorge Arellano Cid Oct. 4, 2006

Oct. 4, 2006

Hi Henry, On Tue, Oct 03, 2006 at 02:30:33PM -0700, Henry Kingman wrote: > Hi Jorge, > > I tried to update our article with some of the details you sent. > > Thanks, and good luck with the Dillo project! I hope you find funding. Thanks for the corrections. One important precision: the dillo project needs at least two core developers working on it fulltime. Not only me. If there's only one person working full time on it, it's not enough to keep the pace of evolving technologies. That's what I meant when writing: > > The situation is this: there're two core developers. We need at > >least to be both working on Dillo full time (ideally three devs.) > >otherwise the project would lag behind the moving target that > >Internet browsing is. I find this paragraph misleading: "Alternatively, Cid says he will release the FLTK2 port if he finds enough funding to be able to continue working fulltime on the port himeself. He said, "Given the current situation, the best option seems to be to remain closed until funding happens." and it's not true. Please make the correction. -- Cheers Jorge.- > > -Henry > > cc: Rick, executive editor > > -- > Henry Kingman, senior editor > LinuxDevices.com > Ziff Davis Internet > 775 625-4547 > > > > > > > >-------- Original Message -------- > >Subject: Dillo article precisions > >Date: Tue, 3 Oct 2006 09:40:28 -0400 > >From: Jorge Arellano Cid <jcid(a)dillo.org> > >To: Rick Lehrbaum <rick(a)linuxdevices.com> > >CC: Dillo mailing list <dillo-dev(a)lists.auriga.wearlab.de> > > > >Hi Rick, > > > > It's being a long time since my last article at linuxdevices, > >receive my greetings from Chile! > > > > With regard to the new article: > > > > http://linuxdevices.com/news/NS4370323584.html > > > > It caught me by surprise. There was a thread in dillo-dev and > >some users suggested that campaign. I was commenting on gross > >factual mistakes in the wiki when it was announced that an > >article was live at linuxdevices. > > > > It's good to see our users' interest in keeping the project > >alive, so I'll comment the article here so you can correct and > >improve the article: > > > > > >>A project to create an ultra-lightweight web browser for use in > >>embedded devices and other resource-constrained hardware has > >>issued a plea for financial help. The Dillo Project says it needs > >>to find a corporate sponsor in order to add anti-aliased text, > >>CSS, Javascript, and internationalization/localization support. > > > > We've almost finished the port to FLTK2, and it already has > >anti-aliased text. (Dillo doesn't compile with FLTK1) > > > > FLTK2 uses UTF8 and provides antialiasing so it solves the > >problem of using GTK1 (this was one of the reasons for GTK1 to go > >GTK2). > > > > UTF8 also makes it easy to add i18n and l10n without breaking > >things inside the browser. > > > > I point this technical details because unofficial patches have > >been developed for antialiasing, i18n and l10n for GTK1. This is > >a good workaround but not a long term solution. > > > > > >> > >>(Click for larger screenshot of Dillo) > > > > Here you'll find a screenshot of dillo-fltk2: > > > > http://www.dillo.org/test/ph2.png > > > > (it shows antialiasing) > > > > > >> > >>Dillo is a very lightweight (about 350 KB) browser supporting a > >>subset of HTML, CGI, SSL, and cookies. > > > > And plugins. > > + Images (GIF, PNG and JPEG) > > > >> Dillo is not really > >>practical for browsing the modern Internet, due to missing > >>support for frames, CSS, Javascript, and other commonly used > >>standards and protocols. It also lacks support for anti-aliased > >>text, something even Linux desktop users have long taken for > >>granted, and appears to have only rudimentary HTML error handling > >>capabilities. > > > > The HTML error handling has improved a lot (the bug meter can > >atest that), but yes, error handling is not as advanced as with > >Firefox. > > > > Anyway, sometimes there're pages with a few hundred mistakes > >handled gracefully. ;-) > > > > > >>Nonetheless, Dillo is extremely fast and lightweight, using less > >>memory in some cases than popular text-based browsers such as > >>lynx. And, since it supports CGI, it could be useful as a > >>framework for simple device interfaces based on Web standards, > >>such as survey kiosks and other closed, "walled garden" > >>applications. > > > > BTW, the new Dillo with a statically linked FLTK2 is about > >820 Kilobytes. > > > >> > >>Additionally, Dillo is popular with web developers due to > >>excellent HTML error reporting. > > > > :-) > > > > > >> > >>Dillo is expected to gain support for anti-aliased text after its > >>development team completes a port to FLTK (fast light toolkit, > >>aka "fulltick"). > > > > [Already there, see above] > > > >> However, founder Jorge Arellano Cid appears > >>adamant that funding be located prior to release of his > >>nearly-complete FLTK port, according to a "save Dillo" campaign > >>page hosted here. > > > > True. > > > > The situation is this: there're two core developers. We need at > >least to be both working on Dillo full time (ideally three devs.) > >otherwise the project would lag behind the moving target that > >Internet browsing is. > > > > Sebastian (the other core developer) is employed fulltime in > >Germany so he has almost no time to Develop. I don't have funds > >to keep on working fulltime too, so if there're no funds the > >project will loose the main developers and their knowledge. > > > > With regard to releasing. That's what I've done for 6+ years > >with GTK1 and no funding happened ;-). > > > > If there were more interested developers in working with Dillo > >(lets say 6 serious and qualified people) I would consider > >releasing because the project could advance in that case. > > > > Believe it or not I asked in dillo-dev, and there was only one > >answer from a dev that could put 4 hours/week and that had no > >FLTK2 knowledge nor on Dillo internals. > > > > Given the current situation, the best option seems to remain > >closed until funding happens. > > > > > >> > >>Other ongoing Dillo development efforts reportedly include CSS > >>support (said to be "70 percent complete") and JavaScript > >>support, as well as additional internationalization (I18n) and > >>localization (l10n) features. > > > > I reported 70% on CSS. This is on the FLTK2 branch, not from > >external efforts. > > > > The interesting part is that we paved the way for all these in > >the newest branch, so now it's much easier to develop them over > >the new code base than with the old branch. > > > > A rough timeline estimation would be near 2 years to have the > >whole set: antialiasing, CSS, I18n, l10n, Frames, Tabs, SSL and > >good Javascript. > > > > We could make a release in 6 months and thenceforth go on > >incrementally adding features in any desired order (probably this > >would be up to the sponsors' needs). > > > > > >>Additional details about Dillo can be found on Dillo's official > >>funding presentations page. For additional background, be sure to > >>read Cid's 2002 introduction to the browser, here. > >> > >>The Dillo project previously sought funding in February of 2004, > >>and was successful in obtaining a one-time grant through the > >>Linux Fund. > > > > > > Thanks a lot for your time and commitment. > > > > > > > -- > Henry Kingman, senior editor > LinuxDevices.com > Ziff Davis Internet > 775 625-4547 >

2 2

Dillo article precisions
by Jorge Arellano Cid Oct. 3, 2006

Oct. 3, 2006

Hi Rick, It's being a long time since my last article at linuxdevices, receive my greetings from Chile! With regard to the new article: http://linuxdevices.com/news/NS4370323584.html It caught me by surprise. There was a thread in dillo-dev and some users suggested that campaign. I was commenting on gross factual mistakes in the wiki when it was announced that an article was live at linuxdevices. It's good to see our users' interest in keeping the project alive, so I'll comment the article here so you can correct and improve the article: > A project to create an ultra-lightweight web browser for use in > embedded devices and other resource-constrained hardware has > issued a plea for financial help. The Dillo Project says it needs > to find a corporate sponsor in order to add anti-aliased text, > CSS, Javascript, and internationalization/localization support. We've almost finished the port to FLTK2, and it already has anti-aliased text. (Dillo doesn't compile with FLTK1) FLTK2 uses UTF8 and provides antialiasing so it solves the problem of using GTK1 (this was one of the reasons for GTK1 to go GTK2). UTF8 also makes it easy to add i18n and l10n without breaking things inside the browser. I point this technical details because unofficial patches have been developed for antialiasing, i18n and l10n for GTK1. This is a good workaround but not a long term solution. > > (Click for larger screenshot of Dillo) Here you'll find a screenshot of dillo-fltk2: http://www.dillo.org/test/ph2.png (it shows antialiasing) > > Dillo is a very lightweight (about 350 KB) browser supporting a > subset of HTML, CGI, SSL, and cookies. And plugins. + Images (GIF, PNG and JPEG) > Dillo is not really > practical for browsing the modern Internet, due to missing > support for frames, CSS, Javascript, and other commonly used > standards and protocols. It also lacks support for anti-aliased > text, something even Linux desktop users have long taken for > granted, and appears to have only rudimentary HTML error handling > capabilities. The HTML error handling has improved a lot (the bug meter can atest that), but yes, error handling is not as advanced as with Firefox. Anyway, sometimes there're pages with a few hundred mistakes handled gracefully. ;-) > Nonetheless, Dillo is extremely fast and lightweight, using less > memory in some cases than popular text-based browsers such as > lynx. And, since it supports CGI, it could be useful as a > framework for simple device interfaces based on Web standards, > such as survey kiosks and other closed, "walled garden" > applications. BTW, the new Dillo with a statically linked FLTK2 is about 820 Kilobytes. > > Additionally, Dillo is popular with web developers due to > excellent HTML error reporting. :-) > > Dillo is expected to gain support for anti-aliased text after its > development team completes a port to FLTK (fast light toolkit, > aka "fulltick"). [Already there, see above] > However, founder Jorge Arellano Cid appears > adamant that funding be located prior to release of his > nearly-complete FLTK port, according to a "save Dillo" campaign > page hosted here. True. The situation is this: there're two core developers. We need at least to be both working on Dillo full time (ideally three devs.) otherwise the project would lag behind the moving target that Internet browsing is. Sebastian (the other core developer) is employed fulltime in Germany so he has almost no time to Develop. I don't have funds to keep on working fulltime too, so if there're no funds the project will loose the main developers and their knowledge. With regard to releasing. That's what I've done for 6+ years with GTK1 and no funding happened ;-). If there were more interested developers in working with Dillo (lets say 6 serious and qualified people) I would consider releasing because the project could advance in that case. Believe it or not I asked in dillo-dev, and there was only one answer from a dev that could put 4 hours/week and that had no FLTK2 knowledge nor on Dillo internals. Given the current situation, the best option seems to remain closed until funding happens. > > Other ongoing Dillo development efforts reportedly include CSS > support (said to be "70 percent complete") and JavaScript > support, as well as additional internationalization (I18n) and > localization (l10n) features. I reported 70% on CSS. This is on the FLTK2 branch, not from external efforts. The interesting part is that we paved the way for all these in the newest branch, so now it's much easier to develop them over the new code base than with the old branch. A rough timeline estimation would be near 2 years to have the whole set: antialiasing, CSS, I18n, l10n, Frames, Tabs, SSL and good Javascript. We could make a release in 6 months and thenceforth go on incrementally adding features in any desired order (probably this would be up to the sponsors' needs). > Additional details about Dillo can be found on Dillo's official > funding presentations page. For additional background, be sure to > read Cid's 2002 introduction to the browser, here. > > The Dillo project previously sought funding in February of 2004, > and was successful in obtaining a one-time grant through the > Linux Fund. Thanks a lot for your time and commitment. -- Cheers Jorge.-

2 1

Campaign to help Dillo survive
by Alan Carvalho de Assis Oct. 3, 2006

Oct. 3, 2006

Hi all, I am writing a document to convince some company to help Dillo project. I think it is an idea we need fight for. I invite everybody to help to improve this document, when we get a powerful document we will send it for some friends at Nokia, Motorola and others. The early version can found here: http://fornix.sourceforge.net/wiki/index.php/Campaign_to_help_Dillo_survive Be free do edit this wiki. Thank you, -- ------------------------------------------------------------ | Alan Carvalho de Assis | ------------------------------------------------------------ -- Não importa o que os outros irão pensar, A cura para a infelicidade é a felicidade

4 11

[jcid@dillo.org: Re: [Dillo-dev] Campaign to help Dillo survive]
by Jorge Arellano Cid Oct. 2, 2006

Oct. 2, 2006

-- Cheers Jorge.-

1 0

Re: [Dillo-dev] Dillo FLTK CVS
by Alan Carvalho de Assis Oct. 2, 2006

Oct. 2, 2006

Hi Michal, On 9/29/06, Michal Nowak <xnowak01(a)stud.fit.vutbr.cz> wrote: > Hi Alan, > > well I am not sure how you could do it i(=desktop@floppy) but I think > Dillo will be quite large with staticaly linked with fltk2. > Do you know how large is it? > May I ask you, how many space have you got on the floppy? Or you mean > "the floppy" (1.4 MiB)? It would be great proof of concept... Well, I am formatting it at 1.74 MB, and I will use compressed fs (squashfs). I think it will get ~ 3MB. Kernel: ~ 600KB (I am using kernel-tiny patch) Kdrive: ~ 600KB (I am using uClibc) Dillo-fltk: < 1.8 MB > The troubles with funds... it's quite longstanding problem. Dillo neads > fulltime dev or two. There are companies which has Dillo build in their > products and sold them, well, that's OK, but thay give nothing back... > just sitting and waiting for Jorge. Comunity of Dillo is rather small, > people from developed countrie have fast computers -> lack of hunger for > such think Dillo is. Probably nobody will pay for releasing "another > browser", coz hey have ff, opera, konq etc. Dillo will be the best option for cheap linux cell phones. Then when these cell phone companies realise it is a best option it will invest. To do it we need emphasize Dillo qualities: the faster browser ever, the smallest footprint, etc. It is just "blow one's own horn" :) > But you can help Dillo with submitting code, if ou want to :). Doing a small linux distro I will help to demonstre as powerful dillo is. And it will demonstre too the small dillo footprint. > CU, > Michal > Cheers, Alan

2 1

Dillo FLTK CVS
by Alan Carvalho de Assis Sept. 29, 2006

Sept. 29, 2006

Hi people, I am new in this list and I have a silly question. I want to compile dillo with no GTK libs. I already compiled kdrive and fltk with uClibc, now I just need to compile dillo. My problem is where to find the dillo fltk tree, I download the default CVS tree (dillo module), but it is not fully fltk, just the download.cc use fltk. I search at mail list and google, but don't find anything. Where can I download the dillo fltk source code? I know it is in development, but it is not problem. Thank you, -- ------------------------------------------------------------ | Alan Carvalho de Assis | ------------------------------------------------------------ -- Não importa o que os outros irão pensar, A cura para a infelicidade é a felicidade

2 4

Opening new URL in same instance and -s option
by Rainer M Krug Sept. 21, 2006

Sept. 21, 2006

Hi I have two questions first: I would like to be able to have only one instance of dillo open and when I try to open a new url (from outside dillo), that this url is opened in the old instance. Is this possible, and if yes, how? second: I have seen emails concerning running dillo in server mode (dillo -s server). I tried it, but dillo didn't know -s. Is this feature imp[lemented, and if yes, how can I access it? Thanks a lot for a brilliant lightning fast browser, Rainer -- Rainer M. Krug, Dipl. Phys. (Germany), MSc Conservation Biology (UCT) Department of Conservation Ecology and Entomology University of Stellenbosch Matieland 7602 South Africa Tel: +27 - (0)72 808 2975 (w) Fax: +27 - (0)21 808 3304 Cell: +27 - (0)83 9479 042 email: RKrug(a)sun.ac.za Rainer(a)krugs.de

1 0

[abc@ai1.anchorage.mtaonline.net: frames/fltk]
by Jorge Arellano Cid Sept. 14, 2006

Sept. 14, 2006

-- Cheers Jorge.-

1 0

Serious Memory Allocation Strategy Problem in Cache_parse_header()
by R.L. Horn Sept. 8, 2006

Sept. 8, 2006

I'm currently in the process of modifying dillo for use in browsing an http media server (yeah, I know it's httpd abuse, but it's only for a local network and I was running Apache anyhow). At present, this basically involves sending a modified downloads plugin an "execute" command and the MIME type when AbortEntry is true in Cache_process_queue() (the plugin then executes an agent which deals with the URL entirely independent of dillo). (Actually, this is functionality that would be nice in the main branch, albeit with its own plugin and user-selectivity. If there's interest, please let me know.) So far, so good -- it seems to work passably well and it only took a couple of hours. Easy peasey. Unfortunately, the first time I click on a 700M video stream, things go horribly wrong. Seems that Cache_parse_header() attempts to allocate memory for the entire content *before* the header has been checked for viewability (since the dispatcher isn't called until Cache_process_queue()). As it happens, this has been reported as bug 726. The upshot of all this is that when you click on a link, there had better be room for the whole thing in heap even though the content may never be read. Otherwise, glib just gives up and dumps core via g_malloc(). I think I can get around this by doing a Content-Type check in Cache_parse_header(). I'd be happy to provide a patch provided I can come up with a reasonably elegant solution. Any advice would be appreciated.

2 3