- Dillo-dev - lists.mailman3.com

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

July 1, 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