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

[patch]: fix the meta-refresh warning code

by corvid＠lavabit.com

Johannes wrote: > On Fri, Sep 25, 2009 at 05:11:35PM -0400, Jorge Arellano Cid wrote: > > On Fri, Sep 25, 2009 at 06:15:05PM +0000, corvid wrote: > > > Jorge wrote: > > > > On Fri, Sep 25, 2009 at 07:16:12AM -0400, Jorge Arellano Cid wrote: > > > > > On Thu, Sep 24, 2009 at 06:04:15AM +0100, Jeremy Henty wrote: > > > > > > On Tue, Sep 22, 2009 at 02:25:47PM -0400, Jorge Arellano Cid wrote: > > > > > > > On Tue, Sep 22, 2009 at 04:35:28PM +0000, corvid wrote: > > > > > > > > > > > > > > Would it be less trouble to have this widget as a child of the UI > > > > > > > > instead of in the rendering area? (I sort of had the impression > > > > > > > > that was the plan... > > > > > > > > > > > > > > That's exactly the plan. > > > > > > > > > > > > > > A simple fltk widget that hides/shows (as the findext bar) and > > > > > > > that gives a text message. It should also support a fake HTML link > > > > > > > (underlined word that reacts to left click). > > > > > > > > > > > > Ah, I think I misunderstood the reference to "custom widget" in the TO > > > > > > DO note. I was fixated on the Dillo Widget system and didn't realise > > > > > > it was talking about a new FLTK widget. Maybe my patch isn't the way > > > > > > to go. Still, it would be nice for the custom widget to be properly > > > > > > CSS-styled. Maybe it be could another FltkViewport? > > > > > > > > > > As this is part of the UI, I'd suggest to use Xdefaults as > > > > > Johannes suggested for colors some time ago. > > > > > > > > Ehmmm, by "Xdefaults", I mean the default X resource files. > > > > > > ISTR that the latest was that Johannes was trying > > > to get the FLTKers to enable the relevant code that > > > had been commented out (rather than having dillo > > > do it directly), but nothing happened on the fltk side. > > > > FLTK2 is dead (that's almost official). > > > > Progress will happen in 1.3.x branch (or whatever they chose to > > call a new branch merging FLTK2 and 1.3.x [1]). > > > > In the meanwhile, I'd be OK with a non-themeable warning widget > > with the same colors it used to have. ;-) > > > > FWIW: the patch should implement an fltk widget as described in > > a previous email. So, no further work on the proposed patch is > > necessary. > > You proposed a popup bar similar to the search bar, right? > Do we really need to create a completly new mechansim for user > notifications? Currently we have: > > * window title > * status bar > * popup Windows (from dpi's) > > I think we should try to keep the UI simple and consistent by > reducing the number of concepts. Maybe it would be nice if popup windows turned into something like a popup bar. > PS: I recently tried http://surf.suckless.org/ and I'm rather > impressed by the minimal UI. I read a little about surf and uzbl recently, but then webkit was too big for me to want to download. (Surprised a person would intentionally name a browser 'surf' nowadays. I had thought of web "surfing" as a term as thankfully dead and buried as "information superhighway" or "cyberspace".)

Sept. 27, 2009

[patch]: fix the meta-refresh warning code

by Johannes.Hofmann＠gmx.de

On Fri, Sep 25, 2009 at 05:11:35PM -0400, Jorge Arellano Cid wrote: > On Fri, Sep 25, 2009 at 06:15:05PM +0000, corvid wrote: > > Jorge wrote: > > > On Fri, Sep 25, 2009 at 07:16:12AM -0400, Jorge Arellano Cid wrote: > > > > On Thu, Sep 24, 2009 at 06:04:15AM +0100, Jeremy Henty wrote: > > > > > On Tue, Sep 22, 2009 at 02:25:47PM -0400, Jorge Arellano Cid wrote: > > > > > > On Tue, Sep 22, 2009 at 04:35:28PM +0000, corvid wrote: > > > > > > > > > > > > Would it be less trouble to have this widget as a child of the UI > > > > > > > instead of in the rendering area? (I sort of had the impression > > > > > > > that was the plan... > > > > > > > > > > > > That's exactly the plan. > > > > > > > > > > > > A simple fltk widget that hides/shows (as the findext bar) and > > > > > > that gives a text message. It should also support a fake HTML link > > > > > > (underlined word that reacts to left click). > > > > > > > > > > Ah, I think I misunderstood the reference to "custom widget" in the TO > > > > > DO note. I was fixated on the Dillo Widget system and didn't realise > > > > > it was talking about a new FLTK widget. Maybe my patch isn't the way > > > > > to go. Still, it would be nice for the custom widget to be properly > > > > > CSS-styled. Maybe it be could another FltkViewport? > > > > > > > > As this is part of the UI, I'd suggest to use Xdefaults as > > > > Johannes suggested for colors some time ago. > > > > > > Ehmmm, by "Xdefaults", I mean the default X resource files. > > > > ISTR that the latest was that Johannes was trying > > to get the FLTKers to enable the relevant code that > > had been commented out (rather than having dillo > > do it directly), but nothing happened on the fltk side. > > FLTK2 is dead (that's almost official). > > Progress will happen in 1.3.x branch (or whatever they chose to > call a new branch merging FLTK2 and 1.3.x [1]). > > In the meanwhile, I'd be OK with a non-themeable warning widget > with the same colors it used to have. ;-) > > FWIW: the patch should implement an fltk widget as described in > a previous email. So, no further work on the proposed patch is > necessary. You proposed a popup bar similar to the search bar, right? Do we really need to create a completly new mechansim for user notifications? Currently we have: * window title * status bar * popup Windows (from dpi's) I think we should try to keep the UI simple and consistent by reducing the number of concepts. Cheers, Johannes PS: I recently tried http://surf.suckless.org/ and I'm rather impressed by the minimal UI.

Sept. 27, 2009

Weird chars bug

by Johannes.Hofmann＠gmx.de

On Fri, Sep 25, 2009 at 06:04:10PM +0000, corvid wrote: > Jorge wrote: > > Since dillo-2.1, enabled-CSS makes funny chars in this page: > > > > http://blogdrake.net/node/14916 > > > > Screenshot: > > > > http://www.dillo.org/test/weirdChars.jpg > > > > Disabling it from the tools button solves the problem. > > Does anybody know what's the problem here? > > I suspect it has something to do with the > font: 76% Trebuchet MS, Verdana, Arial, Helvetica, sans-serif; > in http://blogdrake.net/themes/lightdrake/style.css > > Of course with my general paucity of fonts, it looks fine to me :) Looks ok here too. Somehow dillo seems to pick some weird font on your system, that can't properly display the characters. There are quite a few open issues in the font selection code of dillo. Cheers, Johannes

Sept. 27, 2009

Typing Bug when moving Dillo on DWM's Virtual Desktops

by Johannes.Hofmann＠gmx.de

On Sat, Sep 26, 2009 at 08:46:38AM -0400, Jorge Arellano Cid wrote: > Hi Roger, > > On Fri, Sep 25, 2009 at 10:52:11PM -0800, Roger wrote: > > I'm finally tackling a typing bug with Dillo, and have found it occurs > > when moving the Dillo browser to DMW's other virtual desktops. > > > > It doesn't occur when Dillo is first started. > > > > Nothing, if anything at all, shows within gdb. > > > > > > And, I can't really get to the debug output of DWM as I'm running nvidia > > proprietary drivers which blanks the terminal once X is started. I do > > have a laptop for which I can further investigate the DWM debug data, > > but figured I should post what I know to see if any of you notice > > similar. > > > > > > The basic bug scenario, move the Dillo browser to another Virtual > > Desktop within DWM and start typing (within the url field or within the > > Google search field.) I notice only certain keys type their characters > > and most others will either type nothing or may clear the entire field > > (ie. clear line) > > > > Possible a meta key sticks when moving the browser to another desktop?? > > It could be a bug in dwm, fltk2 or dillo. > > I assume you're using dillo2 (the FLTK2-based one). The dillo > UI widgets you describe to fail are plain FLTK2 objects, so > please do the following test: > > * Get to the fltk2 compilation directory and run test/input > program, and then try to reproduce the bug as with dillo. I quickly tried to reproduce the problem as I also use dwm, but could not see any problem until now. I opened dillo, focused the url field, send dillo to another tag with e.g. Alt-Shift 2, then went activated tag 2 with Alt 2, and continued typing. This seems to work here. Are you using the mouse maybe? Cheers, Johannes

Sept. 27, 2009

Typing Bug when moving Dillo on DWM's Virtual Desktops

by jcid＠dillo.org

Hi Roger, On Fri, Sep 25, 2009 at 10:52:11PM -0800, Roger wrote: > I'm finally tackling a typing bug with Dillo, and have found it occurs > when moving the Dillo browser to DMW's other virtual desktops. > > It doesn't occur when Dillo is first started. > > Nothing, if anything at all, shows within gdb. > > > And, I can't really get to the debug output of DWM as I'm running nvidia > proprietary drivers which blanks the terminal once X is started. I do > have a laptop for which I can further investigate the DWM debug data, > but figured I should post what I know to see if any of you notice > similar. > > > The basic bug scenario, move the Dillo browser to another Virtual > Desktop within DWM and start typing (within the url field or within the > Google search field.) I notice only certain keys type their characters > and most others will either type nothing or may clear the entire field > (ie. clear line) > > Possible a meta key sticks when moving the browser to another desktop?? It could be a bug in dwm, fltk2 or dillo. I assume you're using dillo2 (the FLTK2-based one). The dillo UI widgets you describe to fail are plain FLTK2 objects, so please do the following test: * Get to the fltk2 compilation directory and run test/input program, and then try to reproduce the bug as with dillo. -- Cheers Jorge.-

Sept. 26, 2009

Typing Bug when moving Dillo on DWM's Virtual Desktops

by rogerx＠sdf.lonestar.org

I'm finally tackling a typing bug with Dillo, and have found it occurs when moving the Dillo browser to DMW's other virtual desktops. It doesn't occur when Dillo is first started. Nothing, if anything at all, shows within gdb. And, I can't really get to the debug output of DWM as I'm running nvidia proprietary drivers which blanks the terminal once X is started. I do have a laptop for which I can further investigate the DWM debug data, but figured I should post what I know to see if any of you notice similar. The basic bug scenario, move the Dillo browser to another Virtual Desktop within DWM and start typing (within the url field or within the Google search field.) I notice only certain keys type their characters and most others will either type nothing or may clear the entire field (ie. clear line) Possible a meta key sticks when moving the browser to another desktop?? -- Roger http://rogerx.freeshell.org

Sept. 26, 2009

[patch]: fix the meta-refresh warning code

by jcid＠dillo.org

On Fri, Sep 25, 2009 at 06:15:05PM +0000, corvid wrote: > Jorge wrote: > > On Fri, Sep 25, 2009 at 07:16:12AM -0400, Jorge Arellano Cid wrote: > > > On Thu, Sep 24, 2009 at 06:04:15AM +0100, Jeremy Henty wrote: > > > > On Tue, Sep 22, 2009 at 02:25:47PM -0400, Jorge Arellano Cid wrote: > > > > > On Tue, Sep 22, 2009 at 04:35:28PM +0000, corvid wrote: > > > > > > > > > > Would it be less trouble to have this widget as a child of the UI > > > > > > instead of in the rendering area? (I sort of had the impression > > > > > > that was the plan... > > > > > > > > > > That's exactly the plan. > > > > > > > > > > A simple fltk widget that hides/shows (as the findext bar) and > > > > > that gives a text message. It should also support a fake HTML link > > > > > (underlined word that reacts to left click). > > > > > > > > Ah, I think I misunderstood the reference to "custom widget" in the TO > > > > DO note. I was fixated on the Dillo Widget system and didn't realise > > > > it was talking about a new FLTK widget. Maybe my patch isn't the way > > > > to go. Still, it would be nice for the custom widget to be properly > > > > CSS-styled. Maybe it be could another FltkViewport? > > > > > > As this is part of the UI, I'd suggest to use Xdefaults as > > > Johannes suggested for colors some time ago. > > > > Ehmmm, by "Xdefaults", I mean the default X resource files. > > ISTR that the latest was that Johannes was trying > to get the FLTKers to enable the relevant code that > had been commented out (rather than having dillo > do it directly), but nothing happened on the fltk side. FLTK2 is dead (that's almost official). Progress will happen in 1.3.x branch (or whatever they chose to call a new branch merging FLTK2 and 1.3.x [1]). In the meanwhile, I'd be OK with a non-themeable warning widget with the same colors it used to have. ;-) FWIW: the patch should implement an fltk widget as described in a previous email. So, no further work on the proposed patch is necessary. [1] http://fltk.org/newsgroups.php?s7257+gfltk.development+v7263+T0 -- Cheers Jorge.-

Sept. 25, 2009

[patch]: fix the meta-refresh warning code

by corvid＠lavabit.com

Jorge wrote: > On Fri, Sep 25, 2009 at 07:16:12AM -0400, Jorge Arellano Cid wrote: > > On Thu, Sep 24, 2009 at 06:04:15AM +0100, Jeremy Henty wrote: > > > On Tue, Sep 22, 2009 at 02:25:47PM -0400, Jorge Arellano Cid wrote: > > > > On Tue, Sep 22, 2009 at 04:35:28PM +0000, corvid wrote: > > > > > > > > Would it be less trouble to have this widget as a child of the UI > > > > > instead of in the rendering area? (I sort of had the impression > > > > > that was the plan... > > > > > > > > That's exactly the plan. > > > > > > > > A simple fltk widget that hides/shows (as the findext bar) and > > > > that gives a text message. It should also support a fake HTML link > > > > (underlined word that reacts to left click). > > > > > > Ah, I think I misunderstood the reference to "custom widget" in the TO > > > DO note. I was fixated on the Dillo Widget system and didn't realise > > > it was talking about a new FLTK widget. Maybe my patch isn't the way > > > to go. Still, it would be nice for the custom widget to be properly > > > CSS-styled. Maybe it be could another FltkViewport? > > > > As this is part of the UI, I'd suggest to use Xdefaults as > > Johannes suggested for colors some time ago. > > Ehmmm, by "Xdefaults", I mean the default X resource files. ISTR that the latest was that Johannes was trying to get the FLTKers to enable the relevant code that had been commented out (rather than having dillo do it directly), but nothing happened on the fltk side.

Sept. 25, 2009

Weird chars bug

by corvid＠lavabit.com

Jorge wrote: > Since dillo-2.1, enabled-CSS makes funny chars in this page: > > http://blogdrake.net/node/14916 > > Screenshot: > > http://www.dillo.org/test/weirdChars.jpg > > Disabling it from the tools button solves the problem. > Does anybody know what's the problem here? I suspect it has something to do with the font: 76% Trebuchet MS, Verdana, Arial, Helvetica, sans-serif; in http://blogdrake.net/themes/lightdrake/style.css Of course with my general paucity of fonts, it looks fine to me :)

Sept. 25, 2009

[patch]: fix the meta-refresh warning code

by jcid＠dillo.org

On Fri, Sep 25, 2009 at 07:16:12AM -0400, Jorge Arellano Cid wrote: > On Thu, Sep 24, 2009 at 06:04:15AM +0100, Jeremy Henty wrote: > > On Tue, Sep 22, 2009 at 02:25:47PM -0400, Jorge Arellano Cid wrote: > > > On Tue, Sep 22, 2009 at 04:35:28PM +0000, corvid wrote: > > > > > > Would it be less trouble to have this widget as a child of the UI > > > > instead of in the rendering area? (I sort of had the impression > > > > that was the plan... > > > > > > That's exactly the plan. > > > > > > A simple fltk widget that hides/shows (as the findext bar) and > > > that gives a text message. It should also support a fake HTML link > > > (underlined word that reacts to left click). > > > > Ah, I think I misunderstood the reference to "custom widget" in the TO > > DO note. I was fixated on the Dillo Widget system and didn't realise > > it was talking about a new FLTK widget. Maybe my patch isn't the way > > to go. Still, it would be nice for the custom widget to be properly > > CSS-styled. Maybe it be could another FltkViewport? > > As this is part of the UI, I'd suggest to use Xdefaults as > Johannes suggested for colors some time ago. Ehmmm, by "Xdefaults", I mean the default X resource files. -- Cheers Jorge.-

Sept. 25, 2009