- Dillo-dev - lists.mailman3.com

Re: [Dillo-dev] [marco@hep.uchicago.edu: Re: Dillo not compiling]
by Livio Soares Feb. 8, 2007

Feb. 8, 2007

Hi Marco, Marco Mambelli writes: > Hi Livio, > Thank you, I added glib-devel and gtk+-devel > > autogen and configure are fine now. Nice. > In compilation there are some warning (signedness mainly) and errors in > downloads.cc compilation: > if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include > -I/usr/include/glib-1.2 -I/usr/lib/glib/include -g -O2 -MT downloads.o -MD > -MP -MF ".deps/downloads.Tpo" -c -o downloads.o downloads.cc; \ > then mv -f ".deps/downloads.Tpo" ".deps/downloads.Po"; else rm -f > ".deps/downloads.Tpo"; exit 1; fi > downloads.cc:34:22: error: fltk/run.h: No such file or directory > downloads.cc:35:25: error: fltk/Window.h: No such file or directory > downloads.cc:36:25: error: fltk/Widget.h: No such file or directory > downloads.cc:37:25: error: fltk/damage.h: No such file or directory > ... and many other errors depending probably on the missing files > (undefined variables, scope problems, ...) > > I installed fltk and fltk-devel libraries but this did not solved the > problem. Unfortunately, this isn't very well documented, but you actually need FLTK 2, to allow the download DPI to work. If I remember correctly (Jorge can correct me if I'm wrong), compiling the download DPI is optional (--disable-dlgui, I think, was the configure option). So, you can either forget about the download DPI, find RPMs for FLTK2 (both library and -devel), or build/install FLTK2 yourself. Now, don't you just _love_ recursive build dependences ;P Good luck, Livio

2 1

[marco@hep.uchicago.edu: Re: Dillo not compiling]
by Jorge Arellano Cid Feb. 6, 2007

Feb. 6, 2007

-- Cheers Jorge.-

2 1

[grigory@cisnet.ru: an article about dillo]
by Jorge Arellano Cid Jan. 25, 2007

Jan. 25, 2007

-- Cheers Jorge.-

1 1

Re: Your Web Pages
by Jorge Arellano Cid Jan. 11, 2007

Jan. 11, 2007

Hi John, First of all, thanks for checking the project. Hero go some answers... On Wed, Jan 10, 2007 at 09:58:37PM -0800, John Gutierrez wrote: > Jorge, > > Will you site be updated anytime soon. Some of your pages have a date of > July 24, 2003 (funding.html). I check your site from time to time, but > rarely see new information. > > Plans.html has not had an update since August 2006. I would imagine that the > bullet colors would have changed by now. > > The ChangeLog.html shows a date of Apr 26, 2006 (no new version since then?) > > The FAQ.html still references version 8.4. and talks about FLTK port as of > 2005! > > Fosdem 2005 and LSM 2005 are OLD events - anything current? > > The Achievements (A_gols.html was last modified October 2,2006 - anything > new? The Dillo project is currently frozen. I'm expecting the vacation season in Germany to end to communicate with Sebastian and update the site with an official statement of the current situation. (I've tried to reach him since late 2006 so I assume he's on holidays). The latter time was spent trying to rise funds for continuing the development with at least two people working full time on it. Funding didn't happen so I had to take a job, and as Sebastian had a job, the situation now is we're both on a spare time basis that in practice has been close to nil. OTOH, the port to FLTK2 has gone very good with no surprises and a very good transition. The problem is lack of manpower because of lack of funds. The project is frozen because it is impossible to develop a web browser (very complex task), keeping pace with the evolving technologies, by working on a spare time basis. The web site will be updated after I have a virtual meeting to discuss the points with Sebastian, or in mid February, whatever comes first. -- Cheers Jorge.-

1 0

Re: [Dillo-dev] dillo chat in Logroño/La Rioja/Spain
by Diego . Dec. 5, 2006

Dec. 5, 2006

Ok, but with FALSE (DwPage owns a button that owns the image) the button fail to draw the alt text when can not load the image and do not use width and height atributes of the html tag. Using your patch and seting the parameter to TRUE it use width, height and alt, but do not redraw alt text. Without your patch dillo segfaults if that parameter is true. Diego. 2006/12/2, Jorge Arellano Cid <jcid(a)dillo.org>: > > Hi Diego, > > On Fri, Dec 01, 2006 at 02:23:01AM +0100, Diego . wrote: > > Very thanks for the fast patch and the advices. > > One question ¿In Html_input_image why is the function Html_add_new_image > > called with the FALSE parameter? > > Quick answer: > > Because the image is embedded inside a button that's already > inside the DwPage. > > In other words: there's no need to add the image to the DwPage > because the button "owns" the image (think of an object), thus > only the button object needs to be added. > > -- > Cheers > Jorge.- >

2 1

dillo chat in Logroño/La Rioja/Spain
by Diego . Nov. 29, 2006

Nov. 29, 2006

Hello. I am Diego Sáenz. I use this mail address now (I had mail problems and lost some mails, but i have read them in the list archive). I am associate of AULIR (Asociacion de Usuarios de GNU/Linux de La Rioja) a spanish LUG and will give a chat about how to wrote dillo plug-ins. I will explain a few the dillo internals too. There are not very much programers in AULIR(one of them program anjelica.sourceforge.net) but i will try to wake interest about dillo. Any advice for the chat? I will try to show a preferences plug in as example. Is the bug #695 solved somewhere? i think i will need to use it for a feature of the plug in. Diego. ps: i hoppe that this do not seem spam* *

2 1

Re: invalid (?) relative url resolve issue +patch
by Jorge Arellano Cid Nov. 29, 2006

Nov. 29, 2006

Hi, On Wed, Nov 29, 2006 at 12:47:39AM +0100, Schilter Roland wrote: > Hello, > first of all, thanks for dillo :) ;) > I think I found a bug or at least, a misbehaviour that is handled in famous browsers differently. > I looked through the code and finally figured out where to change code to get the expected behaviour. > (Took some time though :p ) > > I need to mention that I didn't read the RFC2396 about URIs and I have the feeling that the implementation > in dillo may be according to specifications but nevertheless, i couldn't browse several sites... :) > > The problem is, if a `href' attribute of html-tag `a' starts only with a query (`?test') > then the path of the baseurl is only taken until the last slash: > > <a href="?test">test</a> while the baseurl being `www.example.com/example' > > this link will resolve to www.example.com/?test although I expected it to go to www.example.com/example?test Give a look to RFC-2396 C.1 Normal examples: base = http://a/b/c/d;p?q#f relative = ?y resolved => http://a/b/c/?y Dillo passes all those tests, including the abnormal section. Ah and we also test for these extra tests: http://www.ics.uci.edu/~fielding/url/test2.html http://www.ics.uci.edu/~fielding/url/test3.html http://www.ics.uci.edu/~fielding/url/test4.html http://www.ics.uci.edu/~fielding/url/test5.html HTH. -- Cheers Jorge.-

1 0

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