- Dillo-dev - lists.mailman3.com

Re: [Dillo-dev] Dillo FLTK2 alpha release for developers

by Alan Carvalho de Assis

Hi Jorge, 2007/9/30, <>: > Hi there, > > This is an alpha release of the next generation of the Dillo > web browser. The code underwent a major rewrite: significant > parts of the codebase were ported to C++, and the rendering > engine now uses the FLTK2 library instead of GTK1. > > Please read the README inside dillo's tarball. > You do my day with this news. Congratulations!!! > Developers willing to join the project and contribute are > highly encouraged. Sebastian did an excellent work documenting > the new dillo widget engine (just run doxygen inside DW tree). > > This is a good milestone in the project's history, we hope to > be able to continue working on it. This is one step ahead, and we > need other developers help. > The linux embedded community now have a real embedded web browser to use. > Please note that this code is under GPL3! > :-D > BTW, if you want to know what antialiased utf-8 is, just go to: > > http://www.gnu.org/home.fa.html > > after compiling dillo-fltk. > > > Here are the instructions on how to get it working: > > --------------- > Get these files > --------------- > > wget http://www.dillo.org/dillo2/fltk-2.0.x-r5917.tar.bz2 > wget http://www.dillo.org/dillo2/dw-testbed-0.0.43j.tar.bz2 > wget http://www.dillo.org/dillo2/dillo-f15f.tar.bz2 > > ----- > FLTK2 > ----- > > tar jxvf fltk-2.0.x-r5917.tar.bz2 > cd fltk-2.0.x-r5917 > make // Should compile cleanly if you have the > // necessary development packages... > cd test; ./demo // You can play with it too! > cd .. > su > make install // Install FLTK2 libraries > exit > cd .. > > ---------- > dw-0.0.43j > ---------- > > tar jxvf dw-testbed-0.0.43j.tar.bz2 > cd dw-testbed-0.0.43j > ./configure > make > cd test // You can test it from here > cd ../.. > doxygen // Excellent documentation in html > cd html; dillo index.html // (start browsing docs here) > cd ../.. > ln -s dw-testbed-0.0.43j dw-testbed // Don't forget this link > > ---------- > dillo f15j > ---------- > > tar jxvf dillo-f15f.tar.bz2 > cd dillo-f15 > ./configure > make > su > make install // Needed for dpis > exit > cd src > ./dillo-fltk // This is is it! > cd .. > > -------- > dillorc2 > -------- > > There's a "dillorc2" file inside the tarball's top directory: > cp dillorc2 ~/.dillo/ > that will let you use the new and old dillo without trouble. > Long life to Dillo! > > > -- > Cheers > Jorge.- > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev > Alan

Oct. 1, 2007

Re: [Dillo-dev] Dillo FLTK2 alpha release for developers

by Mark South

Hi again Jorge, --- Jorge wrote: > On Mon, Oct 01, 2007 at 09:37:22AM +0100, Mark South wrote: > > It is encouraging to see the first release in a > > veeeeery loooong time. > > Yes, it's a loooong story. Sometime when you feel like it, you can tell us all. > > Under Debian Lenny, the fltk and dw packages build fine. > dillo > > configures OK, but make fails with masses of errors spat out > from > > https.c - mostly "expected ')' before '*' token" errors. Is > > there possibly a typo that may have crept into the server > copy? > > Not in the server. > > $ md5sum dillo-f15f.tar.bz2 > $ cbc03fd64ae538fc887a54de5116fa4b dillo-f15f.tar.bz2 > > Please verify that your tree is not corrupted. The md5sum is good (and the bzip archive would not unpack correctly if it were not). The choke point is in https.c, just after the #define ENABLE_SSL > BTW, I'm using Debian etch (also tested on Slackware, Fedora > and Ubuntu). My Etch box is doing something else right now :-) -- Mark South marksouth.tumblr.com ___________________________________________________________ Want ideas for reducing your carbon footprint? Visit Yahoo! For Good http://uk.promotions.yahoo.com/forgood/environment.html

Oct. 1, 2007

Re: [Dillo-dev] Dillo FLTK2 alpha release for developers

by Brian Hechinger

On Mon, Oct 01, 2007 at 09:18:54AM -0400, dillo-dev-bounces(a)dillo.org wrote: > > Please verify that your tree is not corrupted. > BTW, I'm using Debian etch (also tested on Slackware, Fedora and Ubuntu). I left the laptop at home today, but I gave this a quick go last night, and fltk didn't configure properly on Ubuntu claiming that it couldn't find X11. Any thoughts as to why that may be? It couldn't find X11/Intrinsic.h (which I didn't actually look for yet). Is there a package I need to install that I don't have? -brian -- "Perl can be fast and elegant as much as J2EE can be fast and elegant. In the hands of a skilled artisan, it can and does happen; it's just that most of the shit out there is built by people who'd be better suited to making sure that my burger is cooked thoroughly." -- Jonathan Patschke

Oct. 1, 2007

Re: [Dillo-dev] Dillo FLTK2 alpha release for developers

by None

On Mon, Oct 01, 2007 at 09:37:22AM +0100, Mark South wrote: > Hi Jorge, > > Congratulations. Thanks! > It is encouraging to see the first release in a > veeeeery loooong time. Yes, it's a loooong story. > Under Debian Lenny, the fltk and dw packages build fine. dillo > configures OK, but make fails with masses of errors spat out from > https.c - mostly "expected ')' before '*' token" errors. Is > there possibly a typo that may have crept into the server copy? Not in the server. $ md5sum dillo-f15f.tar.bz2 $ cbc03fd64ae538fc887a54de5116fa4b dillo-f15f.tar.bz2 Please verify that your tree is not corrupted. BTW, I'm using Debian etch (also tested on Slackware, Fedora and Ubuntu). -- Cheers Jorge.-

Oct. 1, 2007

Re: [Dillo-dev] Dillo FLTK2 alpha release for developers

by Mark South

Hi Jorge, Congratulations. It is encouraging to see the first release in a veeeeery loooong time. Under Debian Lenny, the fltk and dw packages build fine. dillo configures OK, but make fails with masses of errors spat out from https.c - mostly "expected ')' before '*' token" errors. Is there possibly a typo that may have crept into the server copy? Best wishes, Mark --- wrote: > Hi there, > > This is an alpha release of the next generation of the > Dillo > web browser. The code underwent a major rewrite: > significant > parts of the codebase were ported to C++, and the > rendering > engine now uses the FLTK2 library instead of GTK1. > > Please read the README inside dillo's tarball. > > Developers willing to join the project and contribute > are > highly encouraged. Sebastian did an excellent work > documenting > the new dillo widget engine (just run doxygen inside DW tree). > > This is a good milestone in the project's history, we hope > to > be able to continue working on it. This is one step ahead, and > we > need other developers help. > > Please note that this code is under GPL3! > > BTW, if you want to know what antialiased utf-8 is, just go > to: > > http://www.gnu.org/home.fa.html > > after compiling dillo-fltk. > > > Here are the instructions on how to get it working: > > --------------- > Get these files > --------------- > > wget http://www.dillo.org/dillo2/fltk-2.0.x-r5917.tar.bz2 > wget http://www.dillo.org/dillo2/dw-testbed-0.0.43j.tar.bz2 > wget http://www.dillo.org/dillo2/dillo-f15f.tar.bz2 > > ----- > FLTK2 > ----- > > tar jxvf fltk-2.0.x-r5917.tar.bz2 > cd fltk-2.0.x-r5917 > make // Should compile cleanly if > you have the > // necessary development > packages... > cd test; ./demo // You can play with it too! > cd .. > su > make install // Install FLTK2 libraries > exit > cd .. > > ---------- > dw-0.0.43j > ---------- > > tar jxvf dw-testbed-0.0.43j.tar.bz2 > cd dw-testbed-0.0.43j > ./configure > make > cd test // You can test it from here > cd ../.. > doxygen // Excellent documentation > in html > cd html; dillo index.html // (start browsing docs > here) > cd ../.. > ln -s dw-testbed-0.0.43j dw-testbed // Don't forget this > link > > ---------- > dillo f15j > ---------- > > tar jxvf dillo-f15f.tar.bz2 > cd dillo-f15 > ./configure > make > su > make install // Needed for dpis > exit > cd src > ./dillo-fltk // This is is it! > cd .. > > -------- > dillorc2 > -------- > > There's a "dillorc2" file inside the tarball's top directory: > cp dillorc2 ~/.dillo/ > that will let you use the new and old dillo without trouble. > > > > -- > Cheers > Jorge.- > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev > ___________________________________________________________ Want ideas for reducing your carbon footprint? Visit Yahoo! For Good http://uk.promotions.yahoo.com/forgood/environment.html

Oct. 1, 2007

Dillo FLTK2 alpha release for developers

by None

Hi there, This is an alpha release of the next generation of the Dillo web browser. The code underwent a major rewrite: significant parts of the codebase were ported to C++, and the rendering engine now uses the FLTK2 library instead of GTK1. Please read the README inside dillo's tarball. Developers willing to join the project and contribute are highly encouraged. Sebastian did an excellent work documenting the new dillo widget engine (just run doxygen inside DW tree). This is a good milestone in the project's history, we hope to be able to continue working on it. This is one step ahead, and we need other developers help. Please note that this code is under GPL3! BTW, if you want to know what antialiased utf-8 is, just go to: http://www.gnu.org/home.fa.html after compiling dillo-fltk. Here are the instructions on how to get it working: --------------- Get these files --------------- wget http://www.dillo.org/dillo2/fltk-2.0.x-r5917.tar.bz2 wget http://www.dillo.org/dillo2/dw-testbed-0.0.43j.tar.bz2 wget http://www.dillo.org/dillo2/dillo-f15f.tar.bz2 ----- FLTK2 ----- tar jxvf fltk-2.0.x-r5917.tar.bz2 cd fltk-2.0.x-r5917 make // Should compile cleanly if you have the // necessary development packages... cd test; ./demo // You can play with it too! cd .. su make install // Install FLTK2 libraries exit cd .. ---------- dw-0.0.43j ---------- tar jxvf dw-testbed-0.0.43j.tar.bz2 cd dw-testbed-0.0.43j ./configure make cd test // You can test it from here cd ../.. doxygen // Excellent documentation in html cd html; dillo index.html // (start browsing docs here) cd ../.. ln -s dw-testbed-0.0.43j dw-testbed // Don't forget this link ---------- dillo f15j ---------- tar jxvf dillo-f15f.tar.bz2 cd dillo-f15 ./configure make su make install // Needed for dpis exit cd src ./dillo-fltk // This is is it! cd .. -------- dillorc2 -------- There's a "dillorc2" file inside the tarball's top directory: cp dillorc2 ~/.dillo/ that will let you use the new and old dillo without trouble. -- Cheers Jorge.-

Oct. 1, 2007

Re: [Dillo-dev] new unfinished code

by None

Hi Diego, On Sat, Sep 29, 2007 at 08:20:21PM +0200, Diego . wrote: > This start to seem like spam. Sorry. No need to apologize. This is quite on topic and a contribution to the project. The fact of having no active developers for some time is a separate issue (as I presume not much answers had come on the patch). > I have upload to my page unfinished code for a prefs dpi and my first > screenshot :). The patch do not change dillo code, but need dillo code to > compile. (dpi lib). > > The page is: > http://personales.ya.com/darkspirit/ > > > If i get time i will try to post some docs about mime code for > dillo(unfinished, unpublished, break, etc) and questions about internals of > dillo. I my experience it is best if you have some code that works cleanly and needs to be extended, rather than a big cloud that needs more work. -- Cheers Jorge.-

Sept. 30, 2007

new unfinished code

by Diego .

This start to seem like spam. Sorry. I have upload to my page unfinished code for a prefs dpi and my first screenshot :). The patch do not change dillo code, but need dillo code to compile. (dpi lib). The page is: http://personales.ya.com/darkspirit/ If i get time i will try to post some docs about mime code for dillo(unfinished, unpublished, break, etc) and questions about internals of dillo. Diego.

Sept. 29, 2007

Re: dillo

by Jorge Arellano Cid

Hi, On Sat, Sep 15, 2007 at 05:36:25AM -0700, j murphy wrote: > Jorge: > I hope that you and your collaborators are > well, and that your plans for releasing the new dillo > are still on track. Yes, still on track. > Despite the work being done on > other lightweight browsers like hv3 and Twibright > Labs' Links, I still prefer to use dillo, :-) > and I need > it for use on some of my older, slower machines that > have less memory, and are too slow with Firefox or > Opera. I'm writing to share with you a few problems > that I have noticed with dillo 0.8.6: I'll answer them below, but please just notice that the main problem we face now is lack of time from the main developers; we know about bugs, and have development plans, but we have no time or funds to quit our jobs and devote 100% to Dillo. > > 1)I often use a browser with tor ( https://tor.eff.org > ) and privoxy ( http://www.privoxy.org )for secure > browsing, and I was using dillo in this way, until I > noticed (through some of the useful diagnostics at > https://torcheck.xenobite.eu ) that dillo doesn't > route https traffic through my web proxy correctly -- > instead it seems to establish a direct connection, > bypassing the proxy, despite the http_proxy setting in > my dillorc file. Normal http traffic seems to be > handled correctly. Does the user need to set a > separate proxy for https traffic? Or does the proxy > handling in dillo have a bug? Dillo's https support is basic. It uses wget for this. You can set a proxy for wget and it should work. > 2)Also, I've had some trouble with dillo's > https.filter.dpi, which often sends an error message > stating that it can't verify a certificate repeatedly, > and sometimes launches multiple instances of itself > when attempting to connect to the same website > securely. This can occasionally lead to crashes in > which https.filter.dpi.core is dumped, and > occasionally brings down the browser as well. I > realize that this information is somewhat vague, but > if you'd like me to send a coredump next time it > occurs, I'll do so. Sad fact: it's a known bug. No need to send the core. The problem is that currently there's no cache for asking for a certificate, so a page with multiple https resources (e.g. images) asks several times for the same certificate flooding the communication socket. > > 3)The fltk downloader has one irritating glitch: when > attempting to save a file, if the user to change the > directory into which the file will be saved, the file > name is cleared, requiring the user to type it in > again, which wastes a lot of time. Yes! This one has bitten me too. This is the default behaviuor of that FLTK dialog. If I find some time and a simple way to change that, I'll fix it. > > 4)When dillo is closed, many of the dpis that were > spawned during a dillo session remain as zombie > processes, when they ought to be terminated along with > the parent dillo process. I realize that file > downloads may have to be handled carefully, and may > sometimes be required to remain open until completion, > even after the parent dillo is closed, but it seems to > me that no useful purpose is served by having the > other dpis remain after dillo is closed. dpidc stop That command tells them to quit. If they remain, that's a bug. > > 5)With the latest snapshots of fltk2 on my machine, > the downloader doesn't refresh itself properly when > multiple files are being downloaded. For instance, a > user starts one download, and the downloader gui is > spawned with a progress tracking entry in the > downloader gui for that particular download. Then the > user starts another download, but the progress > tracking entry for this second download, and for > subsequent downloads, is not displayed properly: it's > somehow underneath the first entry, and partially > obscured by it, so that control of the download or > tracking of it's progress isn't possible. Yes I noticed this too. This simple problems hopefully will be tackled by an interested developer when the code is released (before the end of September. Cross your fingers.). > I hope that this information will help you to improve > your new version of dillo, if these problems have not > already been addressed. If I can help, please let me > know. (Of course I'm a scientist, and not really a > developer, so don't expect miracles.) Yes, your bug report is concise and self explaining. Thanks for it. I wish I had the resources to work hands on in it now. -- Cheers Jorge.-

Sept. 17, 2007

Re: [Dillo-dev] 0.6% of people uses Dillo (poll said)

by Diego .

I sorry the delay in the reply. I was out a week for vacation (1000Km from my home). 2007/8/29, <>: > > Hi Diego, > > On Sat, Aug 25, 2007 at 03:28:55AM +0200, Diego . wrote: > > DesktopLinux.com has published the results of its anual (desktop)linux > poll. > > The interesting thing is in the 3rd question: Which web browsers do you > > frequently use on your Linux desktop(s)? > > > > > http://www.desktoplinux.com/cgi-bin/survey/survey.cgi?view=archive&id=08132… > > > > The interesting thing is that a frozen project have enough users to win > over > > 3 fully developed browsers :) (optimistic without cure) > > Yoou made more than my day with that! I rejoice for you. > Are there news about dillo development? > > Yes there're. > > It is soothing to see your optimism and hopes for Dillo. > Sometimes we think with Sebastian that releasing the code may not > make a difference after all because we currently have no time to > devote, and if people don't develop themselves, there the code > will remain. I think that a change will happend, but to un-freeze a proyect need a lot of work. I hoppe that other people will help with it. First is to communicate the un-freeze then a delay will happend until people known and other for the people to make changes(patchs). I remember that a question was made in the list about a GTK2 dillo version so it can be included in the (graphical) debian installer (as a d-i plugin i think) to read the docs. Surely a static linked FLTK version can be very attractive to d-i people. Don't read us wrong, the decision to open the code is already > made, and BTW, Sebastian did an sterling job of documenting the > internals of Dw, so once it's out there, studying time starts, > and development should follow naturally. > > I wish you or somebody else in this list could take care of > patch reviewing, web site updating and that kind of tasks. > Anyone? I want to take care of patch reviewing with the condition that other person review my patchs. Please give me some orientation or guidelines. Some details remain, and I hope before September ends, the > fltk2 version of Dillo to be online. That is a very good news! -- > Cheers > Jorge.- Diego.

Sept. 2, 2007