- Dillo-dev - lists.mailman3.com

.deb files as PPA

by sas＠321.hu

Hello, On Tue, Jul 7, 2009 at 7:24 PM, Jorge Arellano Cid <jcid(a)dillo.org> wrote: > Hi, > > Now that launchpad is back, .deb packages for Debian on squeeze: dillo depends on libxi6 (>= 2:1.2.0); however: Version of libxi6 on system is 2:1.1.4-1. -- SZERV?C Attila http://321.hu/sas SALVI N?ra http://321.hu/zene.html

July 7, 2009

.deb files as PPA

by jcid＠dillo.org

Hi, Now that launchpad is back, .deb packages for Debian and Ubuntu are available from our download page. -- Cheers Jorge.-

July 7, 2009

client-side redirect

by corvid＠lavabit.com

I went to http://home.williampoundstone.net/Keeler/ and it breaks because there's a space before the URL in <meta http-equiv="refresh" content="0;url= Home.html" /> I can't seem to find anything that does a careful job of specifying what's legal here.

July 5, 2009

dillo-2.1.1 released

by kelson＠pobox.com

On Friday 03 July 2009, Jorge Arellano Cid wrote: > Alexander, > > On Fri, Jul 03, 2009 at 10:15:19PM +0200, Alexander Voigt wrote: > > Dear Dillo developers, > > > > could please anyone be so kind and build an Debian/Ubuntu package for > > the new Dillo 2.1.1? > > Our packagers are aware and working on it. Unfortunately > we're a bit behind the announcement. Packages should be ready in > a day or two (I updated the download page saying it so). > > Sorry for the inconvenience. Sorry for the delay -- it's a holiday weekend here. I've posted Fedora 10 i386 and RHEL5 i386 & x86_64, both SSL and non-SSL, at http://www.hyperborea.org/software/dillo/ -- Kelson Vibber www.hyperborea.org and SpeedForce.org

July 5, 2009

dillo 2.1]

by xentalion＠gmail.com

> Does anyone know what the contemporary way is to show the information > in Plans.html? I remember ball.gif being ubiquitous in html in 1995 -- > in stratigraphy it is regarded as a valuable 'index fossil', often found > together with a variety of brightly-colored line.gifs and blink tags -- > but I don't know what to do about it. > For the Plans.html, I'd use a list with each item having a background image from a sprite sheet ala http://www.alistapart.com/articles/sprites/, but that requires background image support in Dillo. In the mean time, maybe change the icons to pngs of check marks and Xs or something. Maybe green Xs for unfinished features and red Xs for pending? When I first saw the new website, I was surprised, but I have to say that I like it. On Wed, Jun 24, 2009 at 5:53 PM, Jorge Arellano Cid <jcid(a)dillo.org> wrote: > On Wed, Jun 24, 2009 at 06:59:00PM +0000, corvid wrote: > > Jorge wrote: > > > On Tue, Jun 23, 2009 at 11:05:07PM +0000, corvid wrote: > > > > Jorge wrote: > > > > > On Mon, Jun 22, 2009 at 11:01:12PM +0300, Tomas Rimkus wrote: > > > > > > > > > > > > Accidentally sent to corvid only. Forwarding to dillo-dev. > > > > > > > > > > > > > > > It seems whoever designed the new website theme has no idea > what > > > > > > > > > READABILITY means... It looks like someone just used some > stupid online > > > > > > > > > color picker, which just picks some similar colors to the > one user > > > > > > > > > chooses. The old website looked MUCH MUCH better. Imho, > it's a > > > > > > > > > regression... > > > > > > > > > > > > > > > > Hm I like the new design, but I agree that readability might > be a problem. > > > > > > > > Let's see what other say. > > > > > > > > > > > > > > I still find visited text to be hard to read, but I know I > should > > > > > > > break down and get a new display... > > > > > > > > > > > > > > > > > > > I wonder if you are the only dillo user with old display... BTW, > I am using > > > > > > pretty new LCD display and still find it hard to read. > > > > > > > > > > OK, we also had readability concerns but we agreed that it was > > > > > enough. OTOH some people bashed the old design as prehistoric! > > > > > > > > > > After all it's a matter of taste. > > > > > Usability is a different thing. Maybe you need higher contrast > > > > > to see clearly (I suffer with white backgrounds). Do you find > > > > > this one better to read [1]? > > > > > > > > > > What do other people think about the new web design? > > > > > Aesthetically and from a readability point of view. > > > > > Please comment. > > > > > > > > > > > > > > > [1] http://www.dillo.org/test/website/dillo2.2.html > > > > > > > > The test page's visited text is easier for me to read than > > > > the home page's visited text. > > > > > > Funny how it's the reverse effect for me! :-) > > > > > > > > > Please test: > > > > > > :visited {color: #403090 !important} > > > > > > and > > > > > > :visited {color: #603060 !important} > > > > > > on http://www.dillo.org/ and FAQ. > > > > > > I prefer the first one because it fits the palette better. > > > > First one is easier. > > Committed. > > -- > Cheers > Jorge.- > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

July 4, 2009

Tango icon theme for Dillo 2.1.1

by xentalion＠gmail.com

Opps, sorry about that. Thank you! On Fri, Jul 3, 2009 at 8:26 PM, corvid <corvid(a)lavabit.com> wrote: > Colin wrote: > > Anyhow, I've updated my Tango icon theme to include the Fullscreen > pixmaps > > along with the new Tools pixmaps. I've also fixed the inactive stop > pixmaps > > to have the internal X, as Jorge suggested quite a while ago. > > Updated :) > > I added some consts to the full_screen ones to make some warnings go away. > > > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

July 4, 2009

Tango icon theme for Dillo 2.1.1

by corvid＠lavabit.com

Colin wrote: > Anyhow, I've updated my Tango icon theme to include the Fullscreen pixmaps > along with the new Tools pixmaps. I've also fixed the inactive stop pixmaps > to have the internal X, as Jorge suggested quite a while ago. Updated :) I added some consts to the full_screen ones to make some warnings go away.

July 4, 2009

Tango icon theme for Dillo 2.1.1

by xentalion＠gmail.com

Skipped content of type multipart/alternative

July 4, 2009

dillo-2.1.1 released

by jcid＠dillo.org

Alexander, On Fri, Jul 03, 2009 at 10:15:19PM +0200, Alexander Voigt wrote: > Dear Dillo developers, > > could please anyone be so kind and build an Debian/Ubuntu package for > the new Dillo 2.1.1? Our packagers are aware and working on it. Unfortunately we're a bit behind the announcement. Packages should be ready in a day or two (I updated the download page saying it so). Sorry for the inconvenience. -- Cheers Jorge.-

July 3, 2009

dillo-2.1.1 released

by Hole.destructor＠gmx.de

Dear Dillo developers, could please anyone be so kind and build an Debian/Ubuntu package for the new Dillo 2.1.1? Many thanks in advance, Alexander On Fri, Jul 03, 2009 at 01:14:01PM -0400, Jorge Arellano Cid wrote: > On Fri, Jul 03, 2009 at 04:10:15PM +0000, corvid wrote: > > The purpose of this release is to prevent a > > maliciously-crafted image from causing an > > overflow. Since this is a matter of security, > > everyone is, naturally enough, encouraged to > > upgrade :) Thanks go to the oCERT folks for > > bringing the matter to our attention. > > > > > > (Jorge will send the freshmeat announcement in > > a little bit, and I will finish updating the > > website in a moment...) > > Announcement made! > Now it waits in freshmeat's queue for revision and publishing. > > -- > Cheers > Jorge.- > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

July 3, 2009

dillo-2.1.1 released

by jcid＠dillo.org

On Fri, Jul 03, 2009 at 04:10:15PM +0000, corvid wrote: > The purpose of this release is to prevent a > maliciously-crafted image from causing an > overflow. Since this is a matter of security, > everyone is, naturally enough, encouraged to > upgrade :) Thanks go to the oCERT folks for > bringing the matter to our attention. > > > (Jorge will send the freshmeat announcement in > a little bit, and I will finish updating the > website in a moment...) Announcement made! Now it waits in freshmeat's queue for revision and publishing. -- Cheers Jorge.-

July 3, 2009

dillo-2.1.1 released

by corvid＠lavabit.com

The purpose of this release is to prevent a maliciously-crafted image from causing an overflow. Since this is a matter of security, everyone is, naturally enough, encouraged to upgrade :) Thanks go to the oCERT folks for bringing the matter to our attention. (Jorge will send the freshmeat announcement in a little bit, and I will finish updating the website in a moment...)

July 3, 2009

dillo 2.1.1

by 4winter＠informatik.uni-hamburg.de

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Justus Winter wrote: > The current tip [0] compiles and runs fine on solaris [1] with gcc 3.4.3 > (gcc 4.4.0 dies compiling dillo, haven't looked deeply into that one, > could be the local setup...). Uh, I forgot that the linking failed. I had to add - -l{X11,Xrender,fontconfig,iconv}. I blame the first three missing libs on fltk2-config not including them, I am not too sure about iconv though I tend to blame that on the local setup. Could anyone with access to a vanilla solaris setup test that? Justus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpN/r8ACgkQoPmwNWhsaZa/TwCeLiHf4PWshQH0OMnmBDo+wf5I 8XcAoJg0+HW3HYymtwAg5WMpx1/sRD5E =0xPN -----END PGP SIGNATURE-----

July 3, 2009

dillo 2.1.1

by 4winter＠informatik.uni-hamburg.de

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey corvid :) corvid wrote: > Considering how I ripped out a bunch of extraneous system > includes right after the 2.1 release, it would be a comfort > to know that the code in the repository still compiles > for everyone. The current tip [0] compiles and runs fine on solaris [1] with gcc 3.4.3 (gcc 4.4.0 dies compiling dillo, haven't looked deeply into that one, could be the local setup...). Fltk2 still doesn't build ootb on solaris (same issue I reported a year ago [3], workaround still works...) and they introduced bashisms into their build system and fltk2-config script that makes suns sh throw up (not really motivated to file a bug though)... (btw, given the fact that you are porting dillo to fltk1.3 I wanted to give 1.3 a spin, but the download for the latest snapshot 404s and their download-php-magic makes my eyes bleed (what's wrong with plain directory lists?)... are you sure that fltk is the right choice?) Justus 0: changeset: 1208:7ea0944187ad tag: tip user: corvid <corvid(a)lavabit.com> date: Thu Jul 02 14:39:11 2009 +0000 summary: Added tag release-2_1_1 for changeset 65ee806d5172 1: $ uname -a SunOS rzdspc6 5.10 Generic_138888-01 sun4u sparc SUNW,Sun-Fire-V445 Solaris 2: $ g++ --version g++ (GCC) 3.4.3 (csl-sol210-3_4-branch+sol_rpath) 3: http://fltk.org/str.php?L1890 > > > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpN+R8ACgkQoPmwNWhsaZbsswCgitF9VpbG8KMStg7D1Uvh2JsS EYoAniHLM6MzuI1OK+2ROoDwH8P09pVG =fSfB -----END PGP SIGNATURE-----

July 3, 2009

dillo 2.1.1

by newman.x＠gmail.com

On Thu, Jul 2, 2009 at 6:51 PM, Johannes Hofmann<Johannes.Hofmann(a)gmx.de> wrote: > On Thu, Jul 02, 2009 at 03:57:50PM +0000, corvid wrote: >> I wrote: >> > We're planning a bugfix release because it turns out that >> > the PNG image size fix added right before the 2.1 release >> > was incorrect. >> > >> > The nominal release date is Friday, but of course we'll see... >> > >> > Considering how I ripped out a bunch of extraneous system >> > includes right after the 2.1 release, it would be a comfort >> > to know that the code in the repository still compiles >> > for everyone. >> >> http://www.dillo.org/download/ now contains >> dillo-2.1.1.tar.bz2 and dillo-2.1.1.tar.bz2.asc > > Even though there is not much time until the official release > announcement tomorrow, it would be nice if some packages for > dillo-2.1.1 could be made available until then. > Thanks to all our packagers btw. :-) F-11 packages ready @ http://mnowak.fedorapeople.org/dillo2/static/ > > Cheers, > Johannes Michal > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

July 3, 2009

dillo 2.1.1

by Johannes.Hofmann＠gmx.de

On Thu, Jul 02, 2009 at 03:57:50PM +0000, corvid wrote: > I wrote: > > We're planning a bugfix release because it turns out that > > the PNG image size fix added right before the 2.1 release > > was incorrect. > > > > The nominal release date is Friday, but of course we'll see... > > > > Considering how I ripped out a bunch of extraneous system > > includes right after the 2.1 release, it would be a comfort > > to know that the code in the repository still compiles > > for everyone. > > http://www.dillo.org/download/ now contains > dillo-2.1.1.tar.bz2 and dillo-2.1.1.tar.bz2.asc Even though there is not much time until the official release announcement tomorrow, it would be nice if some packages for dillo-2.1.1 could be made available until then. Thanks to all our packagers btw. :-) Cheers, Johannes

July 2, 2009

dillo 2.1.1

by corvid＠lavabit.com

I wrote: > We're planning a bugfix release because it turns out that > the PNG image size fix added right before the 2.1 release > was incorrect. > > The nominal release date is Friday, but of course we'll see... > > Considering how I ripped out a bunch of extraneous system > includes right after the 2.1 release, it would be a comfort > to know that the code in the repository still compiles > for everyone. http://www.dillo.org/download/ now contains dillo-2.1.1.tar.bz2 and dillo-2.1.1.tar.bz2.asc

July 2, 2009

Re: Feels good to be free. Close-tab button.

by corvid＠lavabit.com

Jorge wrote: > On Wed, Jul 01, 2009 at 03:02:45PM +0000, corvid wrote: > > Jorge wrote: > > > 2.- http://planet.postgresql.org/ Unrendered HTML. > > > Simple one to start with. > > > > Isn't that one because it says > > <meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8" /> > > and we don't have a > > Mime_add_minor_type("text/xhtml", a_Html_text); > > because we never quite decided what we wanted to do about xhtml and validation? > > Could be, I just checked the HTTP server sent the correct type. > If this is the case, then the task is to create a notification > area widget that hides/unhides just like the findbar, but below > the control panel. It would serve for the Meta refresh warning > (instead of the current HTML injection) and for XHTML that has > bugs detected. > > In the above mentioned case (XHTML served as HTML). Whatever > the reasons (broken as from [1], understandable as from [2]), it > would be good to render it, provided we have the warning-widget > just in case it doesn't validate. ;) For that matter, http://www.iana.org/assignments/media-types/ doesn't show text/xhtml as a registered media type. (The usual application/xhtml+xml is registered) PS I wonder how the CSS people got it into their heads to reuse the term "media type" for something completely different.

July 2, 2009

Re: Feels good to be free. Close-tab button.

by jcid＠dillo.org

On Thu, Jul 02, 2009 at 08:42:27AM -0400, Jorge Arellano Cid wrote: > In the above mentioned case (XHTML served as HTML). Whatever > the reasons (broken as from [1], understandable as from [2]), it > would be good to render it, provided we have the warning-widget > just in case it doesn't validate. ;) The URLs: [1] http://www.hixie.ch/advocacy/xhtml [2] http://www.goer.org/Journal/2003/04/the_xhtml_100.html -- Cheers Jorge.-

July 2, 2009

Re: Feels good to be free. Close-tab button.

by jcid＠dillo.org

On Wed, Jul 01, 2009 at 03:02:45PM +0000, corvid wrote: > Jorge wrote: > > 2.- http://planet.postgresql.org/ Unrendered HTML. > > Simple one to start with. > > Isn't that one because it says > <meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8" /> > and we don't have a > Mime_add_minor_type("text/xhtml", a_Html_text); > because we never quite decided what we wanted to do about xhtml and validation? Could be, I just checked the HTTP server sent the correct type. If this is the case, then the task is to create a notification area widget that hides/unhides just like the findbar, but below the control panel. It would serve for the Meta refresh warning (instead of the current HTML injection) and for XHTML that has bugs detected. In the above mentioned case (XHTML served as HTML). Whatever the reasons (broken as from [1], understandable as from [2]), it would be good to render it, provided we have the warning-widget just in case it doesn't validate. ;) -- Cheers Jorge.-

July 2, 2009

dillo 2.1.1

by onepoint＠starurchin.org

On Thu, Jul 02, 2009 at 02:50:12AM +0000, corvid wrote: > Considering how I ripped out a bunch of extraneous system includes > right after the 2.1 release, it would be a comfort to know that the > code in the repository still compiles for everyone. No problems here. $ hg tip changeset: 1207:65ee806d5172 tag: tip user: corvid <corvid(a)lavabit.com> date: Wed Jul 01 18:27:07 2009 +0000 summary: update for 2.1.1 Jeremy Henty

July 2, 2009

dillo 2.1.1

by corvid＠lavabit.com

We're planning a bugfix release because it turns out that the PNG image size fix added right before the 2.1 release was incorrect. The nominal release date is Friday, but of course we'll see... Considering how I ripped out a bunch of extraneous system includes right after the 2.1 release, it would be a comfort to know that the code in the repository still compiles for everyone.

July 2, 2009

Re: Feels good to be free. Close-tab button.

by jorl17.8＠gmail.com

Crap, forgot to attach the patch, my bad sorry. Jo?o > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

July 2, 2009

Re: Feels good to be free. Close-tab button.

by jorl17.8＠gmail.com

Qua, 2009-07-01 ?s 17:53 +0200, Johannes Hofmann escreveu: > On Wed, Jul 01, 2009 at 08:51:08AM -0400, Jorge Arellano Cid wrote: > > Hi Ricardo, > > > > On Wed, Jul 01, 2009 at 12:36:27AM +0100, Jo?o Ricardo Louren?o wrote: > > > Ter, 2009-06-30 ?s 22:43 +0100, Jo?o Ricardo Louren?o escreveu: > > > > Well, I promised I would report to you when I got more free time. > > > > Guess what, I'm on vacation! Getting free time from my own personal > > > > projects finally lets me take a closer look at Dillo. I am sorry for > > > > being away for such a long time, though. > > > > > > > > I would like to contribute to one area that I have contributed > > > > previously -- the close-tab button. It isn't critical, I know, but, > > > > for now, it's the best I can do. The idea now is to finally have a > > > > button in each tab. > > > > > > > > It is tough, but I am getting somewhere. The 'initial' drawing part is > > > > done, but I have had to make some small changes to some virtual > > > > functions, and also changing non-virtual functions and finding a way > > > > to 'enable' them in the code. > > > > > > > > It's pretty hackish right now, but I have managed to print the button > > > > and am now starting to handle all the events and different button > > > > states (clicked, over, etcetera). > > > > > > > > I'll keep you updated! > > > > > > > > Jo?o > > > > > > Answering myself, I've got the system working! There are still many more > > > code-cleanups to do and add a couple of documentation features here and > > > there.... It isn't 'pretty', but someone with more skills in the > > > 'design' area can do better than me, I've got the system (which is > > > pretty dumb and slow, IMO). > > > > > > There are, however, three issues I have: > > > > > > 1. I still haven't sorted things with the pager to have tabs behave > > > 'correctly', but that should be _too_ hard, just quite some research. > > > > > > 2. When I destroy a tab, their order gets 'mixed up', but only > > > sometimes. > > > > > > 3. For some reason, clicking on some tabs isn't working (not the > > > buttons, but the tabs). > > > > > > I'll go into them and I think that 3 and 2 are related. I just decided > > > to inform all of you how progress was going. > > > > It's good to see you around again! > > Welcome back. > > > > > WRT tabs. If you succeed in a short time span, great. > > If it takes more effort, I'd prefer you to work on another area. > > The fact is most probably we'll have to port dillo2 to FLTK-1.3 > > at some point this year, and our fine tunning/hacking/workarounds > > for FLTK2 will be lost, and we'll have to start again... > > The progress on FLTK-1.3 really looks promising. However I would not > hold my breath waiting for a FLTK-1.3 release. > I would just keep working on whatever is needed or wanted and judge > about a switch to FLTK-1.3 once there is an official release. > > Cheers, > Johannes > Well, the problems I referred to in the previous post are still an issue, but I thought I should share the code so that someone with more experience can solve it. This doesn't mean I'm not trying to solve it! -- I sure am. Problems: 1. Once the tabs start shrinking, it all goes wacko. which_tab() starts returning incorrect values, which makes the detection go wrong. Maybe it is related to extra_spacing? 2. BTN_DISTANCE_FROM_EDGE_X is doing the opposite, but that's intentional 3. the toolTip is currently disabled (read: not working), but that's easy to fix. 4. Removing a tab other than the selected can cause troubles. Previously I had fixed this by removing() it first and then using a_UIcmd_close_bw(). But it sometimes caused valgrind errors which I couldn't debug. 5. Many tabs open is painful. Check it for yourself. 6. Redrawing the entire thing is painful. Clipping is needed. So, if there weren't any valgrind errors (which seemed random) and if there wasn't any shrinking process, this would be nearly 'perfect'. ---- I think that the optimal tab system would be something like what is used in firefox, with arrows both on the left side and on the right side (when needed). This is logically something harder to do...but an additional challenge (a full rewrite of the tab system, which, fortunately, isn't that 'used' along the system). It would probably also be more user-friendly. But that's my opinion, and there are more important things. I would, however, be available for that task. In fact, I think that, eventually, dillo will need to reformulate its tab system. !! This patch is in no-way finished, complete, fully usable, recommended, or in full agreement with the formatting rules for dillo. !! Thanks, Jo?o > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

July 2, 2009

Re: Feels good to be free. Close-tab button.

by jorl17.8＠gmail.com

Qua, 2009-07-01 ?s 17:53 +0200, Johannes Hofmann escreveu: > On Wed, Jul 01, 2009 at 08:51:08AM -0400, Jorge Arellano Cid wrote: > > Hi Ricardo, > > > > On Wed, Jul 01, 2009 at 12:36:27AM +0100, Jo?o Ricardo Louren?o wrote: > > > Ter, 2009-06-30 ?s 22:43 +0100, Jo?o Ricardo Louren?o escreveu: > > > > Well, I promised I would report to you when I got more free time. > > > > Guess what, I'm on vacation! Getting free time from my own personal > > > > projects finally lets me take a closer look at Dillo. I am sorry for > > > > being away for such a long time, though. > > > > > > > > I would like to contribute to one area that I have contributed > > > > previously -- the close-tab button. It isn't critical, I know, but, > > > > for now, it's the best I can do. The idea now is to finally have a > > > > button in each tab. > > > > > > > > It is tough, but I am getting somewhere. The 'initial' drawing part is > > > > done, but I have had to make some small changes to some virtual > > > > functions, and also changing non-virtual functions and finding a way > > > > to 'enable' them in the code. > > > > > > > > It's pretty hackish right now, but I have managed to print the button > > > > and am now starting to handle all the events and different button > > > > states (clicked, over, etcetera). > > > > > > > > I'll keep you updated! > > > > > > > > Jo?o > > > > > > Answering myself, I've got the system working! There are still many more > > > code-cleanups to do and add a couple of documentation features here and > > > there.... It isn't 'pretty', but someone with more skills in the > > > 'design' area can do better than me, I've got the system (which is > > > pretty dumb and slow, IMO). > > > > > > There are, however, three issues I have: > > > > > > 1. I still haven't sorted things with the pager to have tabs behave > > > 'correctly', but that should be _too_ hard, just quite some research. > > > > > > 2. When I destroy a tab, their order gets 'mixed up', but only > > > sometimes. > > > > > > 3. For some reason, clicking on some tabs isn't working (not the > > > buttons, but the tabs). > > > > > > I'll go into them and I think that 3 and 2 are related. I just decided > > > to inform all of you how progress was going. > > > > It's good to see you around again! > > Welcome back. > > > > > WRT tabs. If you succeed in a short time span, great. > > If it takes more effort, I'd prefer you to work on another area. > > The fact is most probably we'll have to port dillo2 to FLTK-1.3 > > at some point this year, and our fine tunning/hacking/workarounds > > for FLTK2 will be lost, and we'll have to start again... > > The progress on FLTK-1.3 really looks promising. However I would not > hold my breath waiting for a FLTK-1.3 release. > I would just keep working on whatever is needed or wanted and judge > about a switch to FLTK-1.3 once there is an official release. > > Cheers, > Johannes > Well, it shouldn't take much longer. There are only two problems left: 1. With many tabs (running under valgrind's memcheck), whenver we need to 'redraw' the button, we're redrawing the entire TabGroup, which shows flickering. Meaning that on older computers that will be shown, and we can't have that. So I'm guessing that, to fix it, we're going to need cliping. 2. I still have some issues with detecting if the cursor was on top of a button or not, but I'm trying to decode the hardcoded fltk source to see if I can understand it properly and use it. > I would just keep working on whatever is needed or wanted and judge > about a switch to FLTK-1.3 once there is an official release. That seems rather reasonable to me, but one must realize that the more we wait, the more we depend on current code and the harder it will be to make the switch. And there's always the distro problem... Jo?o > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

July 1, 2009

Re: Feels good to be free. Close-tab button.

by Johannes.Hofmann＠gmx.de

On Wed, Jul 01, 2009 at 08:51:08AM -0400, Jorge Arellano Cid wrote: > Hi Ricardo, > > On Wed, Jul 01, 2009 at 12:36:27AM +0100, Jo?o Ricardo Louren?o wrote: > > Ter, 2009-06-30 ?s 22:43 +0100, Jo?o Ricardo Louren?o escreveu: > > > Well, I promised I would report to you when I got more free time. > > > Guess what, I'm on vacation! Getting free time from my own personal > > > projects finally lets me take a closer look at Dillo. I am sorry for > > > being away for such a long time, though. > > > > > > I would like to contribute to one area that I have contributed > > > previously -- the close-tab button. It isn't critical, I know, but, > > > for now, it's the best I can do. The idea now is to finally have a > > > button in each tab. > > > > > > It is tough, but I am getting somewhere. The 'initial' drawing part is > > > done, but I have had to make some small changes to some virtual > > > functions, and also changing non-virtual functions and finding a way > > > to 'enable' them in the code. > > > > > > It's pretty hackish right now, but I have managed to print the button > > > and am now starting to handle all the events and different button > > > states (clicked, over, etcetera). > > > > > > I'll keep you updated! > > > > > > Jo?o > > > > Answering myself, I've got the system working! There are still many more > > code-cleanups to do and add a couple of documentation features here and > > there.... It isn't 'pretty', but someone with more skills in the > > 'design' area can do better than me, I've got the system (which is > > pretty dumb and slow, IMO). > > > > There are, however, three issues I have: > > > > 1. I still haven't sorted things with the pager to have tabs behave > > 'correctly', but that should be _too_ hard, just quite some research. > > > > 2. When I destroy a tab, their order gets 'mixed up', but only > > sometimes. > > > > 3. For some reason, clicking on some tabs isn't working (not the > > buttons, but the tabs). > > > > I'll go into them and I think that 3 and 2 are related. I just decided > > to inform all of you how progress was going. > > It's good to see you around again! Welcome back. > > WRT tabs. If you succeed in a short time span, great. > If it takes more effort, I'd prefer you to work on another area. > The fact is most probably we'll have to port dillo2 to FLTK-1.3 > at some point this year, and our fine tunning/hacking/workarounds > for FLTK2 will be lost, and we'll have to start again... The progress on FLTK-1.3 really looks promising. However I would not hold my breath waiting for a FLTK-1.3 release. I would just keep working on whatever is needed or wanted and judge about a switch to FLTK-1.3 once there is an official release. Cheers, Johannes

July 1, 2009

Re: Feels good to be free. Close-tab button.

by corvid＠lavabit.com

Jorge wrote: > 2.- http://planet.postgresql.org/ Unrendered HTML. > Simple one to start with. Isn't that one because it says <meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8" /> and we don't have a Mime_add_minor_type("text/xhtml", a_Html_text); because we never quite decided what we wanted to do about xhtml and validation?

July 1, 2009

Re: Feels good to be free. Close-tab button.

by jcid＠dillo.org

Hi Ricardo, On Wed, Jul 01, 2009 at 12:36:27AM +0100, Jo?o Ricardo Louren?o wrote: > Ter, 2009-06-30 ?s 22:43 +0100, Jo?o Ricardo Louren?o escreveu: > > Well, I promised I would report to you when I got more free time. > > Guess what, I'm on vacation! Getting free time from my own personal > > projects finally lets me take a closer look at Dillo. I am sorry for > > being away for such a long time, though. > > > > I would like to contribute to one area that I have contributed > > previously -- the close-tab button. It isn't critical, I know, but, > > for now, it's the best I can do. The idea now is to finally have a > > button in each tab. > > > > It is tough, but I am getting somewhere. The 'initial' drawing part is > > done, but I have had to make some small changes to some virtual > > functions, and also changing non-virtual functions and finding a way > > to 'enable' them in the code. > > > > It's pretty hackish right now, but I have managed to print the button > > and am now starting to handle all the events and different button > > states (clicked, over, etcetera). > > > > I'll keep you updated! > > > > Jo?o > > Answering myself, I've got the system working! There are still many more > code-cleanups to do and add a couple of documentation features here and > there.... It isn't 'pretty', but someone with more skills in the > 'design' area can do better than me, I've got the system (which is > pretty dumb and slow, IMO). > > There are, however, three issues I have: > > 1. I still haven't sorted things with the pager to have tabs behave > 'correctly', but that should be _too_ hard, just quite some research. > > 2. When I destroy a tab, their order gets 'mixed up', but only > sometimes. > > 3. For some reason, clicking on some tabs isn't working (not the > buttons, but the tabs). > > I'll go into them and I think that 3 and 2 are related. I just decided > to inform all of you how progress was going. It's good to see you around again! WRT tabs. If you succeed in a short time span, great. If it takes more effort, I'd prefer you to work on another area. The fact is most probably we'll have to port dillo2 to FLTK-1.3 at some point this year, and our fine tunning/hacking/workarounds for FLTK2 will be lost, and we'll have to start again... e.g. 1.- Jump to #anchor doesn't work correctly. Find out what is wrong in the current mechanism, fix it. (Related: there's a need to add a timeout-remove function and use it for cancel operations in the rest of the code). 2.- http://planet.postgresql.org/ Unrendered HTML. Simple one to start with. -- Cheers Jorge.-

July 1, 2009

Re: Feels good to be free. Close-tab button.

by jorl17.8＠gmail.com

Ter, 2009-06-30 ?s 22:43 +0100, Jo?o Ricardo Louren?o escreveu: > Well, I promised I would report to you when I got more free time. > Guess what, I'm on vacation! Getting free time from my own personal > projects finally lets me take a closer look at Dillo. I am sorry for > being away for such a long time, though. > > I would like to contribute to one area that I have contributed > previously -- the close-tab button. It isn't critical, I know, but, > for now, it's the best I can do. The idea now is to finally have a > button in each tab. > > It is tough, but I am getting somewhere. The 'initial' drawing part is > done, but I have had to make some small changes to some virtual > functions, and also changing non-virtual functions and finding a way > to 'enable' them in the code. > > It's pretty hackish right now, but I have managed to print the button > and am now starting to handle all the events and different button > states (clicked, over, etcetera). > > I'll keep you updated! > > Jo?o Answering myself, I've got the system working! There are still many more code-cleanups to do and add a couple of documentation features here and there.... It isn't 'pretty', but someone with more skills in the 'design' area can do better than me, I've got the system (which is pretty dumb and slow, IMO). There are, however, three issues I have: 1. I still haven't sorted things with the pager to have tabs behave 'correctly', but that should be _too_ hard, just quite some research. 2. When I destroy a tab, their order gets 'mixed up', but only sometimes. 3. For some reason, clicking on some tabs isn't working (not the buttons, but the tabs). I'll go into them and I think that 3 and 2 are related. I just decided to inform all of you how progress was going. Jo?o

July 1, 2009

Feels good to be free. Close-tab button.

by jorl17.8＠gmail.com

Well, I promised I would report to you when I got more free time. Guess what, I'm on vacation! Getting free time from my own personal projects finally lets me take a closer look at Dillo. I am sorry for being away for such a long time, though. I would like to contribute to one area that I have contributed previously -- the close-tab button. It isn't critical, I know, but, for now, it's the best I can do. The idea now is to finally have a button in each tab. It is tough, but I am getting somewhere. The 'initial' drawing part is done, but I have had to make some small changes to some virtual functions, and also changing non-virtual functions and finding a way to 'enable' them in the code. It's pretty hackish right now, but I have managed to print the button and am now starting to handle all the events and different button states (clicked, over, etcetera). I'll keep you updated! Jo?o

June 30, 2009

[PATCH] warning: ignoring return value of ???int chdir(const char*)???

by jcid＠dillo.org

On Thu, Jun 25, 2009 at 07:20:27PM +0000, corvid wrote: > Michal wrote: > > cookies.c: > > + rc = fgets(line, LINE_MAXLEN, stream); > > + if (!rc) { > > + MSG("Cookies: Error while reading rule from cookiesrc\n"); > > + /* (Partially) corrupted file? Skip this unreadable line */ > > + continue; > > + } > > > > The idea was to read all the lines with rules and skip those > > unreadable, so we have the rules before and after the unreadable > > part. But - can something like this happen? And will it in reality > > perform like I expect in the code? > > > > Another quirk I found is that I always receive one this line > > at Dillo start: > > > > Cookies: Error while reading rule from cookiesrc > > > > I guess there's some problem with EOF handling. > > I think I would just loop while the return from fgets() > 0 > and then give an error if ferror(stream) is nonzero. Committed with modifications. Please check it. -- Cheers Jorge.-

June 27, 2009

[PATCH] warning: ignoring return value of ???int chdir(const char*)???

by corvid＠lavabit.com

Michal wrote: > cookies.c: > + rc = fgets(line, LINE_MAXLEN, stream); > + if (!rc) { > + MSG("Cookies: Error while reading rule from cookiesrc\n"); > + /* (Partially) corrupted file? Skip this unreadable line */ > + continue; > + } > > The idea was to read all the lines with rules and skip those > unreadable, so we have the rules before and after the unreadable > part. But - can something like this happen? And will it in reality > perform like I expect in the code? > > Another quirk I found is that I always receive one this line > at Dillo start: > > Cookies: Error while reading rule from cookiesrc > > I guess there's some problem with EOF handling. I think I would just loop while the return from fgets() > 0 and then give an error if ferror(stream) is nonzero.

June 25, 2009

[PATCH] warning: ignoring return value of ???int chdir(const char*)???

by newman.x＠gmail.com

On Wed, Jun 24, 2009 at 12:20:11PM -0400, Jorge Arellano Cid wrote: > On Wed, Jun 24, 2009 at 11:03:26AM +0200, Michal Nowak wrote: > > gcc-4.4.0-4.i586 > > > > HG tip: > > > > newman src $ make | grep -i warning > > [...] > > paths.cc: In static member function ???static void Paths::init()???: > > paths.cc:38: warning: ignoring return value of ???int chdir(const char*)???, declared with attribute warn_unused_result > > > > With the patch dillo-guard-chdir.patch no warning. But this > > patch alone won't have any effect, all MSG(...) from > > Paths::init() won't write anything to output due to > > prefs.show_msg not being set to TRUE at that moment. Patch > > dillo-use-MSG-asap.patch moves a_Prefs_init() > > before Paths::init() is called. Hope it's not breaking > > anything. > > > > Tested > > - setting non-existing directory instead of /tmp > > - Dillo won't crash on start, basic browsing works > > Committed. > > > There're also: > > cookies.c:90: warning: ignoring return value of 'write', > cookies.c:249: warning: ignoring return value of 'fgets', > dpid.c:754: warning: ignoring return value of 'write' > bookmarks.c:696: warning: ignoring return value of 'system' > bookmarks.c:698: warning: ignoring return value of 'system' > cookies.c:188: warning: ignoring return value of 'write' > cookies.c:276: warning: ignoring return value of 'fgets' > cookies.c:341: warning: ignoring return value of 'fgets' > cookies.c:428: warning: ignoring return value of 'ftruncate' > cookies.c:1234: warning: ignoring return value of 'fgets' > datauri.c:283: warning: ignoring return value of 'chdir' > ftp.c:280: warning: ignoring return value of 'chdir' > > Can you please make a patch for those too? Attaching the patch. But few comments first. cookies.c: + rc = fgets(line, LINE_MAXLEN, stream); + if (!rc) { + MSG("Cookies: Error while reading rule from cookiesrc\n"); + /* (Partially) corrupted file? Skip this unreadable line */ + continue; + } The idea was to read all the lines with rules and skip those unreadable, so we have the rules before and after the unreadable part. But - can something like this happen? And will it in reality perform like I expect in the code? Another quirk I found is that I always receive one this line at Dillo start: Cookies: Error while reading rule from cookiesrc I guess there's some problem with EOF handling. > > -- > Cheers > Jorge.- > Michal > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev -- Regards, Michal Nowak

June 25, 2009

[marcio.ccamargo@gmail.com: Thank u!]

by jcid＠dillo.org

Hi, :) -- Cheers Jorge.-

June 25, 2009

dillo 2.1]

by jcid＠dillo.org

On Wed, Jun 24, 2009 at 06:59:00PM +0000, corvid wrote: > Jorge wrote: > > On Tue, Jun 23, 2009 at 11:05:07PM +0000, corvid wrote: > > > Jorge wrote: > > > > On Mon, Jun 22, 2009 at 11:01:12PM +0300, Tomas Rimkus wrote: > > > > > > > > > > Accidentally sent to corvid only. Forwarding to dillo-dev. > > > > > > > > > > > > > It seems whoever designed the new website theme has no idea what > > > > > > > > READABILITY means... It looks like someone just used some stupid online > > > > > > > > color picker, which just picks some similar colors to the one user > > > > > > > > chooses. The old website looked MUCH MUCH better. Imho, it's a > > > > > > > > regression... > > > > > > > > > > > > > > Hm I like the new design, but I agree that readability might be a problem. > > > > > > > Let's see what other say. > > > > > > > > > > > > I still find visited text to be hard to read, but I know I should > > > > > > break down and get a new display... > > > > > > > > > > > > > > > > I wonder if you are the only dillo user with old display... BTW, I am using > > > > > pretty new LCD display and still find it hard to read. > > > > > > > > OK, we also had readability concerns but we agreed that it was > > > > enough. OTOH some people bashed the old design as prehistoric! > > > > > > > > After all it's a matter of taste. > > > > Usability is a different thing. Maybe you need higher contrast > > > > to see clearly (I suffer with white backgrounds). Do you find > > > > this one better to read [1]? > > > > > > > > What do other people think about the new web design? > > > > Aesthetically and from a readability point of view. > > > > Please comment. > > > > > > > > > > > > [1] http://www.dillo.org/test/website/dillo2.2.html > > > > > > The test page's visited text is easier for me to read than > > > the home page's visited text. > > > > Funny how it's the reverse effect for me! :-) > > > > > > Please test: > > > > :visited {color: #403090 !important} > > > > and > > > > :visited {color: #603060 !important} > > > > on http://www.dillo.org/ and FAQ. > > > > I prefer the first one because it fits the palette better. > > First one is easier. Committed. -- Cheers Jorge.-

June 25, 2009

patch: save bookmark segfault when dpis not found

by corvid＠lavabit.com

Jorge wrote: > On Wed, Jun 24, 2009 at 02:50:17PM +0000, corvid wrote: > > A new one seen in the bugtracker... > > > > a_Bookmarks_chat_add() sets URL to NULL, so it needs to be handled. > > > > Anyway, the reason this is interesting is that I had always figured > > the URL_*() macros were protecting against a NULL URL, when really > > they protect against NULL fields in URLs. > > Right. > > Please commit (with changelog entry) and update the > bug track entry as "done". The entry is also partly about the fact that the dpis aren't working with their deb package. Perhaps something is broken in it with sysconfdir changing.

June 24, 2009

dillo 2.1]

by jcid＠dillo.org

On Wed, Jun 24, 2009 at 06:59:00PM +0000, corvid wrote: > Jorge wrote: > > On Tue, Jun 23, 2009 at 11:05:07PM +0000, corvid wrote: > > > Jorge wrote: > > > > On Mon, Jun 22, 2009 at 11:01:12PM +0300, Tomas Rimkus wrote: > > > > > > > > > > Accidentally sent to corvid only. Forwarding to dillo-dev. > > > > > > > > > > > > > It seems whoever designed the new website theme has no idea what > > > > > > > > READABILITY means... It looks like someone just used some stupid online > > > > > > > > color picker, which just picks some similar colors to the one user > > > > > > > > chooses. The old website looked MUCH MUCH better. Imho, it's a > > > > > > > > regression... > > > > > > > > > > > > > > Hm I like the new design, but I agree that readability might be a problem. > > > > > > > Let's see what other say. > > > > > > > > > > > > I still find visited text to be hard to read, but I know I should > > > > > > break down and get a new display... > > > > > > > > > > > > > > > > I wonder if you are the only dillo user with old display... BTW, I am using > > > > > pretty new LCD display and still find it hard to read. > > > > > > > > OK, we also had readability concerns but we agreed that it was > > > > enough. OTOH some people bashed the old design as prehistoric! > > > > > > > > After all it's a matter of taste. > > > > Usability is a different thing. Maybe you need higher contrast > > > > to see clearly (I suffer with white backgrounds). Do you find > > > > this one better to read [1]? > > > > > > > > What do other people think about the new web design? > > > > Aesthetically and from a readability point of view. > > > > Please comment. > > > > > > > > > > > > [1] http://www.dillo.org/test/website/dillo2.2.html > > > > > > The test page's visited text is easier for me to read than > > > the home page's visited text. > > > > Funny how it's the reverse effect for me! :-) > > > > > > Please test: > > > > :visited {color: #403090 !important} > > > > and > > > > :visited {color: #603060 !important} > > > > on http://www.dillo.org/ and FAQ. > > > > I prefer the first one because it fits the palette better. > > First one is easier. Is it good enough for you? -- Cheers Jorge.-

June 24, 2009

dillo 2.1]

by corvid＠lavabit.com

Jorge wrote: > On Tue, Jun 23, 2009 at 11:05:07PM +0000, corvid wrote: > > Jorge wrote: > > > On Mon, Jun 22, 2009 at 11:01:12PM +0300, Tomas Rimkus wrote: > > > > > > > > Accidentally sent to corvid only. Forwarding to dillo-dev. > > > > > > > > > > > It seems whoever designed the new website theme has no idea what > > > > > > > READABILITY means... It looks like someone just used some stupid online > > > > > > > color picker, which just picks some similar colors to the one user > > > > > > > chooses. The old website looked MUCH MUCH better. Imho, it's a > > > > > > > regression... > > > > > > > > > > > > Hm I like the new design, but I agree that readability might be a problem. > > > > > > Let's see what other say. > > > > > > > > > > I still find visited text to be hard to read, but I know I should > > > > > break down and get a new display... > > > > > > > > > > > > > I wonder if you are the only dillo user with old display... BTW, I am using > > > > pretty new LCD display and still find it hard to read. > > > > > > OK, we also had readability concerns but we agreed that it was > > > enough. OTOH some people bashed the old design as prehistoric! > > > > > > After all it's a matter of taste. > > > Usability is a different thing. Maybe you need higher contrast > > > to see clearly (I suffer with white backgrounds). Do you find > > > this one better to read [1]? > > > > > > What do other people think about the new web design? > > > Aesthetically and from a readability point of view. > > > Please comment. > > > > > > > > > [1] http://www.dillo.org/test/website/dillo2.2.html > > > > The test page's visited text is easier for me to read than > > the home page's visited text. > > Funny how it's the reverse effect for me! :-) > > > Please test: > > :visited {color: #403090 !important} > > and > > :visited {color: #603060 !important} > > on http://www.dillo.org/ and FAQ. > > I prefer the first one because it fits the palette better. First one is easier.

June 24, 2009

dillo 2.1]

by jcid＠dillo.org

On Tue, Jun 23, 2009 at 11:05:07PM +0000, corvid wrote: > Jorge wrote: > > On Mon, Jun 22, 2009 at 11:01:12PM +0300, Tomas Rimkus wrote: > > > > > > Accidentally sent to corvid only. Forwarding to dillo-dev. > > > > > > > > > It seems whoever designed the new website theme has no idea what > > > > > > READABILITY means... It looks like someone just used some stupid online > > > > > > color picker, which just picks some similar colors to the one user > > > > > > chooses. The old website looked MUCH MUCH better. Imho, it's a > > > > > > regression... > > > > > > > > > > Hm I like the new design, but I agree that readability might be a problem. > > > > > Let's see what other say. > > > > > > > > I still find visited text to be hard to read, but I know I should > > > > break down and get a new display... > > > > > > > > > > I wonder if you are the only dillo user with old display... BTW, I am using > > > pretty new LCD display and still find it hard to read. > > > > OK, we also had readability concerns but we agreed that it was > > enough. OTOH some people bashed the old design as prehistoric! > > > > After all it's a matter of taste. > > Usability is a different thing. Maybe you need higher contrast > > to see clearly (I suffer with white backgrounds). Do you find > > this one better to read [1]? > > > > What do other people think about the new web design? > > Aesthetically and from a readability point of view. > > Please comment. > > > > > > [1] http://www.dillo.org/test/website/dillo2.2.html > > The test page's visited text is easier for me to read than > the home page's visited text. Funny how it's the reverse effect for me! :-) Please test: :visited {color: #403090 !important} and :visited {color: #603060 !important} on http://www.dillo.org/ and FAQ. I prefer the first one because it fits the palette better. -- Cheers Jorge.-

June 24, 2009

patch: viewport keybindings

by jcid＠dillo.org

On Wed, Jun 24, 2009 at 05:13:51AM +0000, corvid wrote: > Here is an idea for viewport keybindings. > > It just builds a SimpleVector once and lets all of the viewports point to it, > which I think goes against the dillo/dw boundary rules, but we'll see how > the general idea goes over... > Well, that's one way to do it... I'm more inclined to have an scrolling keys enum in fltkviewport.hh, and to export another scrollTo() function that receives them as parameter. Then we can catch the shortcut in UI::handle(), and map between KEYS_* and the enum in a function like a_UIcmd_set_scroll_xy(). That avoids stepping over the dillo/dw boundaries. -- Cheers Jorge.-

June 24, 2009

[PATCH] warning: ignoring return value of ???int chdir(const char*)???

by jcid＠dillo.org

On Wed, Jun 24, 2009 at 11:03:26AM +0200, Michal Nowak wrote: > gcc-4.4.0-4.i586 > > HG tip: > > newman src $ make | grep -i warning > [...] > paths.cc: In static member function ???static void Paths::init()???: > paths.cc:38: warning: ignoring return value of ???int chdir(const char*)???, declared with attribute warn_unused_result > > With the patch dillo-guard-chdir.patch no warning. But this > patch alone won't have any effect, all MSG(...) from > Paths::init() won't write anything to output due to > prefs.show_msg not being set to TRUE at that moment. Patch > dillo-use-MSG-asap.patch moves a_Prefs_init() > before Paths::init() is called. Hope it's not breaking > anything. > > Tested > - setting non-existing directory instead of /tmp > - Dillo won't crash on start, basic browsing works Committed. There're also: cookies.c:90: warning: ignoring return value of 'write', cookies.c:249: warning: ignoring return value of 'fgets', dpid.c:754: warning: ignoring return value of 'write' bookmarks.c:696: warning: ignoring return value of 'system' bookmarks.c:698: warning: ignoring return value of 'system' cookies.c:188: warning: ignoring return value of 'write' cookies.c:276: warning: ignoring return value of 'fgets' cookies.c:341: warning: ignoring return value of 'fgets' cookies.c:428: warning: ignoring return value of 'ftruncate' cookies.c:1234: warning: ignoring return value of 'fgets' datauri.c:283: warning: ignoring return value of 'chdir' ftp.c:280: warning: ignoring return value of 'chdir' Can you please make a patch for those too? -- Cheers Jorge.-

June 24, 2009

patch: a binding for stop

by jcid＠dillo.org

On Wed, Jun 24, 2009 at 12:20:54AM +0000, corvid wrote: > How about if we just don't give it any default binding: Committed. -- Cheers Jorge.-

June 24, 2009

patch: save bookmark segfault when dpis not found

by jcid＠dillo.org

On Wed, Jun 24, 2009 at 02:50:17PM +0000, corvid wrote: > A new one seen in the bugtracker... > > a_Bookmarks_chat_add() sets URL to NULL, so it needs to be handled. > > Anyway, the reason this is interesting is that I had always figured > the URL_*() macros were protecting against a NULL URL, when really > they protect against NULL fields in URLs. Right. Please commit (with changelog entry) and update the bug track entry as "done". -- Cheers Jorge.-

June 24, 2009

patch: save bookmark segfault when dpis not found

by corvid＠lavabit.com

A new one seen in the bugtracker... a_Bookmarks_chat_add() sets URL to NULL, so it needs to be handled. Anyway, the reason this is interesting is that I had always figured the URL_*() macros were protecting against a NULL URL, when really they protect against NULL fields in URLs.

June 24, 2009

dillo 2.1

by sandshrew＠gmail.com

On Wed, 24 Jun 2009 14:24:41 +0200 Johannes Hofmann <Johannes.Hofmann(a)gmx.de> wrote: > hg tip now has support for color definitions of the form > rgb(255,255,255). > > Please give it a try. > Thanks. It seems to work ok. I have also tried the patch which makes text wrapping work in textareas ( http://lists.auriga.wearlab.de/pipermail/dillo-dev/2009-April/006267.html ). The text does wrap but it doesn't automatically scroll down. Maybe the patch could be committed with some adjustments? -- Brain: an apparatus with which we think we think. - A. Bierce

June 24, 2009

dillo 2.1

by Johannes.Hofmann＠gmx.de

On Mon, Jun 22, 2009 at 05:12:07PM +0300, Tomas R wrote: > Been testing dillo 2.1 for some time and would like to share my > experience. > > It's really great to see some basic css support (appearance of most if > not all websites has improved alot), properly resized images, > redirection and basic authentication working now :) > > Anyway, even dillo improved alot recently there still seems to be some > issues. Here are some I've noticed after testing this release for few > days: > Rendering > 1) ubuntu.lt > Not sure if it's dillo fault or website's malformed stylesheet, but > with default dillo settings some of the lithuanian characters are not > displayed. This can be fixed by just adding "* {font-family: > serif !important}" to the style.css. Here is a pic with some of the > places where letters are missing marked in red: > http://img4.imageshack.us/img4/2227/ubuntult.png > 2) gmail > It's nice that login works now, but with default dillo settings the > size of most of the text is 1px. This can be partially fixed by adding > font_min_size to dillorc, but it's obviously a dillo bug as this > doesn't happen with links-hacked. > 3) google > What's with the textarea in the top left corner of the page? And just > for information: signing out doesn't work because it requires basic > javascript support (works with links-hacked). > 4) Black on black, white on white... > http://www.nma-fallout.com/forum/viewtopic.php?t=42776&start=2660&sid=a5712… > For some reason black font color is used here and we get black text on > black background in some posts (doesn't happen with links-hacked). > http://www.acetoneteam.org/ > Background color is not set here and if we have "body > {background-color: white}" rule in our style.css file, we get white > text on white background. hg tip now has support for color definitions of the form rgb(255,255,255). Please give it a try. Cheers, Johannes

June 24, 2009

[PATCH] warning: ignoring return value of ‘int chdir(const char*)’

by newman.x＠gmail.com

gcc-4.4.0-4.i586 HG tip: newman src $ make | grep -i warning [...] paths.cc: In static member function ?static void Paths::init()?: paths.cc:38: warning: ignoring return value of ?int chdir(const char*)?, declared with attribute warn_unused_result With the patch dillo-guard-chdir.patch no warning. But this patch alone won't have any effect, all MSG(...) from Paths::init() won't write anything to output due to prefs.show_msg not being set to TRUE at that moment. Patch dillo-use-MSG-asap.patch moves a_Prefs_init() before Paths::init() is called. Hope it's not breaking anything. Tested - setting non-existing directory instead of /tmp - Dillo won't crash on start, basic browsing works -- Regards, Michal Nowak

June 24, 2009

patch: viewport keybindings

by corvid＠lavabit.com

Here is an idea for viewport keybindings. It just builds a SimpleVector once and lets all of the viewports point to it, which I think goes against the dillo/dw boundary rules, but we'll see how the general idea goes over...

June 24, 2009

patch: a binding for stop

by corvid＠lavabit.com

How about if we just don't give it any default binding:

June 24, 2009

dillo 2.1]

by corvid＠lavabit.com

Jorge wrote: > On Mon, Jun 22, 2009 at 11:01:12PM +0300, Tomas Rimkus wrote: > > > > Accidentally sent to corvid only. Forwarding to dillo-dev. > > > > > > > It seems whoever designed the new website theme has no idea what > > > > > READABILITY means... It looks like someone just used some stupid online > > > > > color picker, which just picks some similar colors to the one user > > > > > chooses. The old website looked MUCH MUCH better. Imho, it's a > > > > > regression... > > > > > > > > Hm I like the new design, but I agree that readability might be a problem. > > > > Let's see what other say. > > > > > > I still find visited text to be hard to read, but I know I should > > > break down and get a new display... > > > > > > > I wonder if you are the only dillo user with old display... BTW, I am using > > pretty new LCD display and still find it hard to read. > > OK, we also had readability concerns but we agreed that it was > enough. OTOH some people bashed the old design as prehistoric! > > After all it's a matter of taste. > Usability is a different thing. Maybe you need higher contrast > to see clearly (I suffer with white backgrounds). Do you find > this one better to read [1]? > > What do other people think about the new web design? > Aesthetically and from a readability point of view. > Please comment. > > > [1] http://www.dillo.org/test/website/dillo2.2.html The test page's visited text is easier for me to read than the home page's visited text. Does anyone know what the contemporary way is to show the information in Plans.html? I remember ball.gif being ubiquitous in html in 1995 -- in stratigraphy it is regarded as a valuable 'index fossil', often found together with a variety of brightly-colored line.gifs and blink tags -- but I don't know what to do about it.

June 24, 2009