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

patch: changeLinkColor
by corvid＠lavabit.com Sept. 28, 2008

Sept. 28, 2008

I just took the 0.8.6 version and replaced everything in it with dillo2 versions. (well, then had to add in the widget part) The fact that it seems to be working is kind of shocking. As for whether this is still the right way to do it, I leave this matter for the experts. The registerName is because html.cc needs to have that working in order to call changeLinkColor.

2 3

panel_size=small hides the menubar
by onepoint＠starurchin.org Sept. 28, 2008

Sept. 28, 2008

If I add "panel_size=small" to ~/.dillo/dillo2rc then the menubar disappears! Huh? (~/.dillo/dillo2rc is otherwise identical to the default /etc/dill2rc) Regards, Jeremy Henty

2 2

Dillo in OSX
by Johannes.Hofmann＠gmx.de Sept. 27, 2008

Sept. 27, 2008

On Thu, Sep 04, 2008 at 04:09:30PM -0400, Jorge Arellano Cid wrote: > On Wed, Sep 03, 2008 at 06:28:49PM +0200, Johannes Hofmann wrote: > > On Tue, Sep 02, 2008 at 09:20:03AM -0400, Jorge Arellano Cid wrote: > > > On Mon, Sep 01, 2008 at 01:42:26PM +0200, Johannes Hofmann wrote: > > > > Hi Jorge, > > > > > > > > how did You setup the OSX box to get a compiler and header files? > > > > Did You install that huge XCode stuff, or is there another way? > > > > I may get access to an OSX box to try dillo on it. > > > > > > How do I disable the double-buffer? > > > > Use the --disable-doublebuffer option when configuring dw2. > > Oh, yes, I forgot... > (tried running ./configure --help in dillo2 not dw2) > > > > I tried dillo "as is" with clear_double_buffer() and without it, > > > and the result is the same... > > > > Yeah, dw2 implements doublebuffering internally, so that does not > > make a difference. > > I'll have access to that machine again sarting on September 12. > Just tried current dillo on OSX with --disable-doublebuffer. It works ok with some issues: * Some of the buttens disapear from time to time (Back button for example). * The font size seems a bit too large so that there is not enough space between words and lines. * Incoming data does not reliably trigger a page update. An additional event like a mouse movement is necessary. Apart from that it's quite nice. Tabs are working fine. Cheers, Johannes

2 1

SEGFAULT with mouse click
by jcid＠dillo.org Sept. 27, 2008

Sept. 27, 2008

On Thu, Sep 25, 2008 at 11:14:28PM -0700, Donald Chai wrote: > On Thu, Sep 25, 2008 at 3:58 PM, Jorge Arellano Cid <jcid(a)dillo.org> wrote: > > I just came accross an easy to reproduce segfault, that's > > present since long ago. > > > > Middle-clicking works OK right? > > > > Well, try middle-clicking a link with a two mouse button (i.e. > > pressing both at the same time). The link menu stays open and > > after a second click (e.g. left click to make it dissapear) > > it segfaults. > > [...] > > I see this problem as well. If I very quickly press the left then > right mouse button (NOT at the same time), then I get a segfault. > Dillo seems to try to select some text on the old page, after the new > page is loaded. This hinted me towards a timing issue and found this way to crash dillo (most probably akin to the "middle-click" bug): 1.- Left click over a remote URL link (to have some time while DNS is resolving) 2.- Move the mouse pointer out of the link and right-click to get the popup menu, before the new page starts downloading. 3.- Once the new page starts to show, click again to get rid of the popup, and it'll crash. -- Cheers Jorge.-

3 7

Icon for Dillo window
by jcid＠dillo.org Sept. 27, 2008

Sept. 27, 2008

Hi, I was thinking it'd be good to provide an icon for the WM to use. Does anybody know how to do it with FLTK2? -- Cheers Jorge.-

4 20

Tabs!!!
by jcid＠dillo.org Sept. 26, 2008

Sept. 26, 2008

Hi there, The tabs patch has grown to a quite usable state, so it was committed for you to test. I know we're close to the release so we can still rollback. It's just that I'd much like to have it in the main tree before dillo2 goes out. The patch comes with several assorted cleanups and normalizations. For instance: derived widgets now use the "Cust" prefix instead of "New", the window->user_data() holds a pointer to the current UI, and child widgets get it from there, etc. OK, so to the tabs... This implementation uses one UI per tab, and it's quite fast. You can switch tabs with the mouse, Shift+{Left, Right} or {Ctrl,Ctrl+Shift}+TAB. Use Ctrl+N, or middle click over a link to open a new tab (just as it was with new windows). Ctrl+Q closes the tab. The idea is that in the future the user can dillo2rc-choose whether to use windows or tabs, and windows with tabs. Some issues: 1.- Tab Tooltips are commented out because FLTK has problems with them. 2.- Shift+{Left, Right} work even when the location is focused. In the latter case you may need to click the right key twice for it to focus and work (don't know why, the Left key works OK). 3.- Currently there's no hidden tabs widget, when there's only one tab (haven't even tried, it may be as simple as hiding the group). 4.- There's no close tab icon in the tab label. 5.- No warning popup for close window with multiple open tabs. OK, please take it for a ride and test. Comments, fixes and patches are welcomed. -- Cheers Jorge.-

3 19

PATCH: select new tabs
by onepoint＠starurchin.org Sept. 26, 2008

Sept. 26, 2008

This patch is more of a call for discussion than a fix as it fiddles with the UI. It makes Dillo select the new tab after creating it. As a special case, middle-clicking a link does not select the new tab unless the Shift key is down. (This is the same behaviour as Firefox which saves learning a new set of reflexes.) What do people think? Regards, Jeremy Henty

5 7

cut off word ends with italic fonts
by Johannes.Hofmann＠gmx.de Sept. 26, 2008

Sept. 26, 2008

Hi, somtimes the end of italic words get cut off e.g. in <html> <body> <i><a href="foo">FUU</a>BAR</i> </body> </html> when seen with vw_fontname="helvetica". This is due to a change in html.cc (I think it was introduced with rev 1.36). This change sets the backgroundColor for all words which means that for each word, the bounding box get's drawn before the actual text. This obviously has a performance impact too. I'm not sure how to get back to the original behaviour (backgroundColor == NULL for normal words) without breaking anything. Can someone please have a look? Cheers, Johannes

4 13

SEGFAULT with mouse click
by jcid＠dillo.org Sept. 26, 2008

Sept. 26, 2008

Hi, I just came accross an easy to reproduce segfault, that's present since long ago. Middle-clicking works OK right? Well, try middle-clicking a link with a two mouse button (i.e. pressing both at the same time). The link menu stays open and after a second click (e.g. left click to make it dissapear) it segfaults. -- Cheers Jorge.-

2 3

patch: Re: [Dillo-dev] what's next
by corvid＠lavabit.com Sept. 25, 2008

Sept. 25, 2008

Johannes wrote (way back in June!): > * The cursor is not always updated properly when over a link. This > happens while page is rendered and also when drag-scrolling with > the middle mouse button. How about updating it from layout()?

3 6