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

x offset > 64k

by corvid＠lavabit.com

I tried looking at a stylesheet, but nothing displayed. It was a one-line document about 7k chars long. It turned out that fltk::getwidth() calls XftTextExtents32() and the width comes back in a short, so it wrapped at 32k. I chopped the line into 1k-long "words", and now I saw text, but once I made a line somewhere over 8k chars long, drawing would wrap and start at the beginning again. Everything looked all right in fltk::drawtext_transformed() as it called XftDrawString32()... I have no idea whether this is something easy to deal with in some way, or a limitation in X...

May 28, 2009

--xid option

by jcid＠dillo.org

On Tue, May 26, 2009 at 08:17:53PM +0200, Johannes Hofmann wrote: > On Tue, May 19, 2009 at 08:24:14PM +0200, Johannes Hofmann wrote: > > On Tue, May 19, 2009 at 01:34:56PM -0400, Jorge Arellano Cid wrote: > > > On Mon, May 18, 2009 at 11:14:14PM +0200, Johannes Hofmann wrote: > > > > On Mon, May 18, 2009 at 01:48:43PM -0400, Jorge Arellano Cid wrote: > > > > > On Mon, May 18, 2009 at 01:18:11AM +0200, Johannes Hofmann wrote: > > > > > > Hi, > > > > > > > > > > > > attached patch tries to implement the missing --xid option that is > > > > > > used to embed dillo into the claws mailer. > > > > > > The right way to do this would probabely be to implement the > > > > > > complete XEMBED protocol which is also mentioned in > > > > > > doc/fltk-problems.doc. > > > > > > However a simple XReparentWindow() seems to work more or less here. > > > > > > Please test. > > > > > > > > > > It seems like you forgot to commit xembed.{hh,cc} to the repo. > > > > > e.g. hg add xembed.hh xembed.cc > > > > > > > > Oh yes. Should be fixed now. > > > > Btw. I managed to install the claws mail client including the dillo > > > > plugin and it seems to work fine now with dillo2. That's why I just > > > > committed the xembed stuff. > > > > > > This is very good. > > > > > > I'll have to dig for the sylpheed contact to let them know. > > > Does anybody here know the email? > > > > I already contacted them on irc (#claws on freenode). > > It would be good if this get's some testing as there seems to be > > some interaction with the WM in use. I now tested it successful > > on dwm, twm, and fvwm. > > Also there are probabely more elegant ways to do it, but > > for now I think it's better than nothing. > > More testing showed that the current implementation has severe > problems. > The thing is that the window manager that I use (dwm) is one of the > few non-reparenting WMs. Most others reparent new windows and that > can create races with the reparentin we do. > There also seems to be a problem with keyboard events in that case. > Is there anyone on the list with in-depth X11 knowledge who could > help with the xembed stuff? Not me. I've seen new patches in the repo so I assume this is more or less being improved. Please let me know how it goes. AFAIS the current repo is almost dillo-2.1. I'd freeze here and only accept bug fixes and polish from now. Opinions? -- Cheers Jorge.-

May 27, 2009

(no subject)

by bogus＠does.not.exist.com

From: Jorge Arellano Cid <jcid(a)dillo.org> To: Dillo mailing list <dillo-dev(a)dillo.org> Cc: Bcc: Subject: Re: [Dillo-dev] patch: a binding for stop Reply-To: In-Reply-To: <20090527142256.GH6001(a)local.gobigwest.com> On Wed, May 27, 2009 at 02:22:57PM +0000, corvid wrote: > > Wondering whether we can come to a decision on this one.. I don't like much Esc for stop, but if that's FFs default, it may be better than another (as the Ctrl-x clash you spot). Afterall this is what configurable keybindings is suppossed to solve so Esc is OK for me as default. > > Jeremy wrote: > > On Wed, May 06, 2009 at 11:32:31AM -0400, Jorge Arellano Cid wrote: > > > > > > The other one I can think of as mnemonic is <ctrl>x. What do > > > people think? > > > > That clashes with "Cut". Select some text in the URL window and > > <ctrl>+x will delete it. I think it's not a good idea to grab > > something that (a) already has a conventional action, and (b) already > > performs that conventional action in the GUI. > > > > And while we're talking about conventional use: Dillo is highly > > unconventional when it uses <ctrl>+q to close a tab. Everyone else[1] > > uses <ctrl>+w to close a tab (<ctrl>+<shift>+q to close a window) and > > <ctrl>+q to quit. Which can be annoying when switching between the > > two. > > > > Firefox uses Escape to stop, and arora[2] uses <ctrl>+. . > > > > Regards, > > > > Jeremy Henty > > > > [1] ie. Firefox :-) > > [2] http://code.google.com/p/arora/ - WebKit+Qt-based browser. It > > looks very nice and may supplant Firefox as "the browser to fall back > > to when Dillo can't handle the page". > > -- Cheers Jorge.-

May 27, 2009

include guard naming

by jcid＠dillo.org

On Wed, May 27, 2009 at 12:59:09AM +0000, corvid wrote: > Jorge wrote: > > On Sun, May 24, 2009 at 03:09:53PM -0400, corvid(a)lavabit.com wrote: > > > I was just going through and changing the include guards > > > that don't follow the dillo convention, and then > > > I glanced at http://en.wikipedia.org/wiki/Include_guard > > > and it reminds me that the C++ standard prohibits '_'s > > > at the beginning. > > > > > > Does anyone care enough to have an opinion? > > > If we want to rm the leading or surrounding underscores, > > > I might as well do that too before committing. > > > > A "D_" prefix looks OK to me. > > > > e.g. > > > > #ifndef D_BINARYCONST_H > > #define D_BINARYCONST_H > > > > ... > > > > #endif /* D_BINARYCONST_H */ > > Is that D_IO_, D_DLIB_, etc., on the dillo side > and LOUT_, DW_, etc., on the dw side? > (not sure whether dw is still supposed to maintain an > independence of sorts...) Good question... I'd say in that case an all around "G_" or "IG_" prefix (INCLUDE GUARD) may fit better. -- Cheers Jorge.-

May 27, 2009

[patch]: [doc]: escape some hash in the text

by corvid＠lavabit.com

Jeremy wrote: > When you're sick of bugs, clean up the docs! This escapes some '#' > characters so that "#define" and "#include" appear properly in the > text. It also silences some Doxygen warnings (it was trying to > interpret those words as links). Committed.

May 27, 2009

include guard naming

by corvid＠lavabit.com

Jorge wrote: > On Sun, May 24, 2009 at 03:09:53PM -0400, corvid(a)lavabit.com wrote: > > I was just going through and changing the include guards > > that don't follow the dillo convention, and then > > I glanced at http://en.wikipedia.org/wiki/Include_guard > > and it reminds me that the C++ standard prohibits '_'s > > at the beginning. > > > > Does anyone care enough to have an opinion? > > If we want to rm the leading or surrounding underscores, > > I might as well do that too before committing. > > A "D_" prefix looks OK to me. > > e.g. > > #ifndef D_BINARYCONST_H > #define D_BINARYCONST_H > > ... > > #endif /* D_BINARYCONST_H */ Is that D_IO_, D_DLIB_, etc., on the dillo side and LOUT_, DW_, etc., on the dw side? (not sure whether dw is still supposed to maintain an independence of sorts...)

May 27, 2009

include guard naming

by jcid＠dillo.org

On Sun, May 24, 2009 at 03:09:53PM -0400, corvid(a)lavabit.com wrote: > I was just going through and changing the include guards > that don't follow the dillo convention, and then > I glanced at http://en.wikipedia.org/wiki/Include_guard > and it reminds me that the C++ standard prohibits '_'s > at the beginning. > > Does anyone care enough to have an opinion? > If we want to rm the leading or surrounding underscores, > I might as well do that too before committing. A "D_" prefix looks OK to me. e.g. #ifndef D_BINARYCONST_H #define D_BINARYCONST_H ... #endif /* D_BINARYCONST_H */ -- Cheers Jorge.-

May 27, 2009

patch: Re: [Dillo-dev] https through a proxy

by corvid＠lavabit.com

Here you go. As I said, I have not had the opportunity to test this under a wide range of conditions.

May 27, 2009

--xid option

by Johannes.Hofmann＠gmx.de

On Tue, May 19, 2009 at 08:24:14PM +0200, Johannes Hofmann wrote: > On Tue, May 19, 2009 at 01:34:56PM -0400, Jorge Arellano Cid wrote: > > On Mon, May 18, 2009 at 11:14:14PM +0200, Johannes Hofmann wrote: > > > On Mon, May 18, 2009 at 01:48:43PM -0400, Jorge Arellano Cid wrote: > > > > On Mon, May 18, 2009 at 01:18:11AM +0200, Johannes Hofmann wrote: > > > > > Hi, > > > > > > > > > > attached patch tries to implement the missing --xid option that is > > > > > used to embed dillo into the claws mailer. > > > > > The right way to do this would probabely be to implement the > > > > > complete XEMBED protocol which is also mentioned in > > > > > doc/fltk-problems.doc. > > > > > However a simple XReparentWindow() seems to work more or less here. > > > > > Please test. > > > > > > > > It seems like you forgot to commit xembed.{hh,cc} to the repo. > > > > e.g. hg add xembed.hh xembed.cc > > > > > > Oh yes. Should be fixed now. > > > Btw. I managed to install the claws mail client including the dillo > > > plugin and it seems to work fine now with dillo2. That's why I just > > > committed the xembed stuff. > > > > This is very good. > > > > I'll have to dig for the sylpheed contact to let them know. > > Does anybody here know the email? > > I already contacted them on irc (#claws on freenode). > It would be good if this get's some testing as there seems to be > some interaction with the WM in use. I now tested it successful > on dwm, twm, and fvwm. > Also there are probabely more elegant ways to do it, but > for now I think it's better than nothing. More testing showed that the current implementation has severe problems. The thing is that the window manager that I use (dwm) is one of the few non-reparenting WMs. Most others reparent new windows and that can create races with the reparentin we do. There also seems to be a problem with keyboard events in that case. Is there anyone on the list with in-depth X11 knowledge who could help with the xembed stuff? Cheers, Johannes > > Cheers, > Johannes

May 26, 2009

https through a proxy

by corvid＠lavabit.com

I wrote: > Yesterday I hacked up (it's still very hacky right now) > some code that is intended to make https work through > a proxy, but I haven't tested it on an actual proxy yet. > > Do you have any suggestions on what would be > the most convenient way to go about this? > (It'd be nicer just to test with something > that's running out there than to do a bunch > of building and configuring for something I'll > just rm again afterward.) I built privoxy, which went smoothly, and found that my code is working.

May 26, 2009