June 2009 - Dillo-dev - lists.mailman3.com

memory use

by jcid＠dillo.org

On Sat, Jun 13, 2009 at 01:14:51AM +0000, corvid wrote: > Interesting that Firefox has a greater VSZ without images. > I don't think I noticed that earlier. Oh, I didn't notice too. Is this result reproducible in your computer? -- Cheers Jorge.-

June 13, 2009

memory use

by jcid＠dillo.org

Hi, After a long time, a memory usage page was added! There's a link from the first bullet point of dillo.org, and another form the 9years page. -- Cheers Jorge.-

June 13, 2009

[patch] change font size on the fly

by Johannes.Hofmann＠gmx.de

On Fri, Jun 12, 2009 at 12:47:10PM -0400, Jorge Arellano Cid wrote: > On Thu, Jun 11, 2009 at 03:32:35PM +0000, corvid wrote: > > Johannes wrote: > > > attached patch allows to change the font size form the tools menu. > > > I find this quite handy sometimes. What do you think? > > As is, it's handy for developers, although it may be confusing > for users. Sometimes it works, sometimes it doesn't. When it doesn't > it looks as if nothing happened, but when going to another page, > the font factor surprises with a change. > > e.g. http://www.linuxpackages.net > > (click larger fonts a few times, then go back). That happens when websites specify fixed font sizes (e.g. 12pt). In that case font_factor does not change it. It only changes font sizes like "small", "medium" ... and font sizes relatively defined to the base font. Here is a related discussion: http://css-discuss.incutio.com/?page=ForceFontSize > > > > No objections here. > > (although I've been content since increasing font_min_size a bit) > > As is now, I'd go for a plain explanation of font_min_size and > font_factor in the FAQ. Ok. > > I'd prefer to polish the patch until is behaves "as expected" > in all cases, but that may involve keeping a per page font_factor. > It may take some time... Hm, let's check what other browsers do. Cheers, Johannes

June 12, 2009

[patch] change font size on the fly

by jcid＠dillo.org

On Thu, Jun 11, 2009 at 03:32:35PM +0000, corvid wrote: > Johannes wrote: > > attached patch allows to change the font size form the tools menu. > > I find this quite handy sometimes. What do you think? As is, it's handy for developers, although it may be confusing for users. Sometimes it works, sometimes it doesn't. When it doesn't it looks as if nothing happened, but when going to another page, the font factor surprises with a change. e.g. http://www.linuxpackages.net (click larger fonts a few times, then go back). > No objections here. > (although I've been content since increasing font_min_size a bit) As is now, I'd go for a plain explanation of font_min_size and font_factor in the FAQ. I'd prefer to polish the patch until is behaves "as expected" in all cases, but that may involve keeping a per page font_factor. It may take some time... -- Cheers Jorge.-

June 12, 2009

[patch] change font size on the fly

by corvid＠lavabit.com

Johannes wrote: > attached patch allows to change the font size form the tools menu. > I find this quite handy sometimes. What do you think? No objections here. (although I've been content since increasing font_min_size a bit)

June 11, 2009

[patch] change font size on the fly

by Johannes.Hofmann＠gmx.de

Hi, attached patch allows to change the font size form the tools menu. I find this quite handy sometimes. What do you think? Cheers, Johannes

June 11, 2009

[PATCH] fix dillorc path

by jcid＠dillo.org

On Sun, Jun 07, 2009 at 06:43:25PM +0200, Johannes Hofmann wrote: > On Sun, Jun 07, 2009 at 12:34:31PM -0400, Jorge Arellano Cid wrote: > > On Sun, Jun 07, 2009 at 02:08:22AM +0000, corvid wrote: > > > Jorge wrote: > > > > On Thu, Jun 04, 2009 at 06:26:40PM +0000, corvid wrote: > > > > > Paul wrote: > > > > > > When opening dillo from the CLI I noticed the following message: > > > > > > > > > > > > paths: Cannot open file '/home/user/.dillo/dillorc' > > > > > > paths: Cannot open file '/etc/dillo/dillorc' > > > > > > paths: Using internal defaults... > > > > > > > > > > > > Checked my system and saw that dillorc had been installed > > > > > > in /usr/etc/dillorc > > > > > > > > > > > > Checking config.log showed sysconfdir='${prefix}/etc', so no > > > > > > surprises there. But Paths::getPrefsFP() in src/paths.cc uses > > > > > > PATHS_RC_SYS, which is "/etc/dillo/", so my patch uses DILLORC_SYS, > > > > > > as specified in src/Makefile.am, instead. Now all is fine! > > > > > > > > > > In addition, perhaps we should make sysconfdir have '/dillo' at the end. > > > > > If I look in an etc dir and see dillorc, I'd know what it's for, > > > > > but I wouldn't know what uses keysrc. > > > > > > > > Yes, a '/dillo' suffix looks OK. > > > > Please merge both ideas and commit. > > > > > > I defined a DILLO_SYSCONF instead of DILLORC_SYS > > > so that a system keysrc will work someday. > > > Please test. > > > > dillorc and dpidrc got into "/usr/local/etc". > > (I was expecting them in "/usr/local/etc/dillo"). > > Works fine for me. Did you call ./autogen.sh before configuring/ > compiling? Sorry, my mistake. I run autoreconf before the "hg up". It works fine now. -- Cheers Jorge.-

June 7, 2009

keyboard shortcuts non-functioning under KDE 3.5.10

by corvid＠lavabit.com

Rogutes wrote: > Johannes Hofmann (2009-06-04 16:58): > > On Thu, Jun 04, 2009 at 06:22:34AM +0100, Paul wrote: > > > Hi, > > > > > > I've got recent code from mercurial, June 1st. > > > No keyboard shortcuts are working for me using KDE 3.5.10. > > > > > > I was speaking to Johannes Hofmann about this problem, he asked me > > > what my locale was (it's en-GB.UTF-8) and also asked me to report > > > the problem here. > > > > Thanks for reporting. > > > > > > > > Do you need more information from me? > > > > Is anyone else seeing this? dillo shortcuts don't seem to work at > > all for Paul. Shortcuts in test/editor from fltk2 seem to work > > though. > > I can't reproduce the problem so far. > > Paul, > > Does anything change when you save the keysrc file attached to this > e-mail to ~/.dillo/keysrc ? I think I had something similar, but > I didn't have time to report...and now I forgot what it was :/ Did it have anything to do with your earlier mail (http://lists.auriga.wearlab.de/pipermail/dillo-dev/2009-May/006378.html) for restricting the modifiers?

June 7, 2009

[PATCH] fix dillorc path

by corvid＠lavabit.com

Jorge wrote: > On Sun, Jun 07, 2009 at 02:08:22AM +0000, corvid wrote: > > Jorge wrote: > > > On Thu, Jun 04, 2009 at 06:26:40PM +0000, corvid wrote: > > > > Paul wrote: > > > > > When opening dillo from the CLI I noticed the following message: > > > > > > > > > > paths: Cannot open file '/home/user/.dillo/dillorc' > > > > > paths: Cannot open file '/etc/dillo/dillorc' > > > > > paths: Using internal defaults... > > > > > > > > > > Checked my system and saw that dillorc had been installed > > > > > in /usr/etc/dillorc > > > > > > > > > > Checking config.log showed sysconfdir='${prefix}/etc', so no > > > > > surprises there. But Paths::getPrefsFP() in src/paths.cc uses > > > > > PATHS_RC_SYS, which is "/etc/dillo/", so my patch uses DILLORC_SYS, > > > > > as specified in src/Makefile.am, instead. Now all is fine! > > > > > > > > In addition, perhaps we should make sysconfdir have '/dillo' at the end. > > > > If I look in an etc dir and see dillorc, I'd know what it's for, > > > > but I wouldn't know what uses keysrc. > > > > > > Yes, a '/dillo' suffix looks OK. > > > Please merge both ideas and commit. > > > > I defined a DILLO_SYSCONF instead of DILLORC_SYS > > so that a system keysrc will work someday. > > Please test. > > dillorc and dpidrc got into "/usr/local/etc". > (I was expecting them in "/usr/local/etc/dillo"). Was a new 'configure' generated? I get: test -z "/usr/local/etc/dillo" || mkdir -p -- "/usr/local/etc/dillo" list='dillorc'; for p in $list; do \ if test -f "$p"; then d=; else d="./"; fi; \ f=`echo $p | sed -e 's|^.*/||'`; \ echo " /usr/bin/ginstall -c -m 644 '$d$p' '/usr/local/etc/dillo/$f'"; \ /usr/bin/ginstall -c -m 644 "$d$p" "/usr/local/etc/dillo/$f"; \ done

June 7, 2009

[PATCH] fix dillorc path

by Johannes.Hofmann＠gmx.de

On Sun, Jun 07, 2009 at 12:34:31PM -0400, Jorge Arellano Cid wrote: > On Sun, Jun 07, 2009 at 02:08:22AM +0000, corvid wrote: > > Jorge wrote: > > > On Thu, Jun 04, 2009 at 06:26:40PM +0000, corvid wrote: > > > > Paul wrote: > > > > > When opening dillo from the CLI I noticed the following message: > > > > > > > > > > paths: Cannot open file '/home/user/.dillo/dillorc' > > > > > paths: Cannot open file '/etc/dillo/dillorc' > > > > > paths: Using internal defaults... > > > > > > > > > > Checked my system and saw that dillorc had been installed > > > > > in /usr/etc/dillorc > > > > > > > > > > Checking config.log showed sysconfdir='${prefix}/etc', so no > > > > > surprises there. But Paths::getPrefsFP() in src/paths.cc uses > > > > > PATHS_RC_SYS, which is "/etc/dillo/", so my patch uses DILLORC_SYS, > > > > > as specified in src/Makefile.am, instead. Now all is fine! > > > > > > > > In addition, perhaps we should make sysconfdir have '/dillo' at the end. > > > > If I look in an etc dir and see dillorc, I'd know what it's for, > > > > but I wouldn't know what uses keysrc. > > > > > > Yes, a '/dillo' suffix looks OK. > > > Please merge both ideas and commit. > > > > I defined a DILLO_SYSCONF instead of DILLORC_SYS > > so that a system keysrc will work someday. > > Please test. > > dillorc and dpidrc got into "/usr/local/etc". > (I was expecting them in "/usr/local/etc/dillo"). Works fine for me. Did you call ./autogen.sh before configuring/ compiling? Cheers, Johannes

June 7, 2009