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

CSS class handling updated

by Johannes.Hofmann＠gmx.de

Hi, the CSS class handling has been updated to support multiple class names as defined in the CSS 2.1 specification. Obviously dillo now has to do some more work to handle the cases with multiple class names. However I hope that at least on pages that do not use this feature performance did not change noticably. If you find a case where the current code feels slower than 2.1.1 please let me know. Cheers, Johannes

July 13, 2009

Re: [fltk.general] Cross-compiling Dillo to ARM

by acassis＠gmail.com

Hi Johannes, On 7/10/09, Johannes Hofmann <Johannes.Hofmann(a)gmx.de> wrote: > Excellent! > Is the softkeyboard support something that needs to be added to > fltk, or are modifications to dillo needed? How is this handled > for other apps? > On my board (i.MX27ADS) I used a hardware keyboard. Do you find any softkeyboard to use with fltk2 app? > Cheers, > Johannes > Cheers, Alan

July 13, 2009

Bug in Dillo's menu

by Hole.destructor＠gmx.de

On Sun, Jul 12, 2009 at 03:24:40PM +0000, corvid wrote: > Alexander wrote: > > I just found a little bug in the dillo's menu: When I click on the > > tool button (the one, where one can de/activate CSS) and I don't want > > to click on one of it's items (maybe because I pressed the wrong > > button or something), it is impossible to get out. I just can't > > simply close the menu by again click on the tool button. Clicking > > somewhere else (i.e. on another menu button) will not close the tool > > button. > > > > The only way to close the menu seems to be a click on one of it's > > items. > > > > Exactly the same thing happens with the F-menu button. > > > > What I also noticed: Sometimes dillo seems to hang, when visiting the > > "Bug Insertion" page on the dillo homepage: When I click on some of > > the drop-down menus or the text field, suddenly dillo freezes. > > > > I'm using Dillo 2.1.1 (Ubuntu binary "dillo+ssl" > > dillo_2.1.1-0+dillo1~jaunty1_amd64.deb, > > libfltk2.0-dev_2.0.0~r6671-0+devfil1_amd64.deb). It would be nice, if > > anyone could have a look into this. > > What window manager are you using? I'm sorry for my complaint, after a restart of X (I'm using Gnome), dillo works as expected and all above mentioned bugs are gone. This is very strange. Thus, please ignore this bug report. :) Best, Alexander

July 12, 2009

Bug in Dillo's menu

by corvid＠lavabit.com

Alexander wrote: > I just found a little bug in the dillo's menu: When I click on the > tool button (the one, where one can de/activate CSS) and I don't want > to click on one of it's items (maybe because I pressed the wrong > button or something), it is impossible to get out. I just can't > simply close the menu by again click on the tool button. Clicking > somewhere else (i.e. on another menu button) will not close the tool > button. > > The only way to close the menu seems to be a click on one of it's > items. > > Exactly the same thing happens with the F-menu button. > > What I also noticed: Sometimes dillo seems to hang, when visiting the > "Bug Insertion" page on the dillo homepage: When I click on some of > the drop-down menus or the text field, suddenly dillo freezes. > > I'm using Dillo 2.1.1 (Ubuntu binary "dillo+ssl" > dillo_2.1.1-0+dillo1~jaunty1_amd64.deb, > libfltk2.0-dev_2.0.0~r6671-0+devfil1_amd64.deb). It would be nice, if > anyone could have a look into this. What window manager are you using?

July 12, 2009

Bug in Dillo's menu

by Hole.destructor＠gmx.de

Dear Dillo developers, I just found a little bug in the dillo's menu: When I click on the tool button (the one, where one can de/activate CSS) and I don't want to click on one of it's items (maybe because I pressed the wrong button or something), it is impossible to get out. I just can't simply close the menu by again click on the tool button. Clicking somewhere else (i.e. on another menu button) will not close the tool button. The only way to close the menu seems to be a click on one of it's items. Exactly the same thing happens with the F-menu button. What I also noticed: Sometimes dillo seems to hang, when visiting the "Bug Insertion" page on the dillo homepage: When I click on some of the drop-down menus or the text field, suddenly dillo freezes. I'm using Dillo 2.1.1 (Ubuntu binary "dillo+ssl" dillo_2.1.1-0+dillo1~jaunty1_amd64.deb, libfltk2.0-dev_2.0.0~r6671-0+devfil1_amd64.deb). It would be nice, if anyone could have a look into this. Many thanks in advance, Alexander

July 12, 2009

Rv: Re: [Dillo-dev] Re: [fltk.general] Cross-compiling Dillo to ARM

by darirf＠yahoo.es

Ups! This one was intented for the list. Sorry. --- El s?b, 11/7/09, Dario Rodriguez <darirf(a)yahoo.es> escribi?: > De: Dario Rodriguez <darirf(a)yahoo.es> > Asunto: Re: [Dillo-dev] Re: [fltk.general] Cross-compiling Dillo to ARM > Para: "Johannes Hofmann" <Johannes.Hofmann(a)gmx.de> > Fecha: s?bado, 11 julio, 2009 9:07 > Hi, > > --- El vie, 10/7/09, Johannes Hofmann <Johannes.Hofmann(a)gmx.de> > escribi?: > > >? ? Screenshot at: > > >? ? ???http://www.mobileread.com/forums/showpost.php?p=517459&postcount=92 > > > > Excellent! > > Is the softkeyboard support something that needs to > be > > added to > > fltk, or are modifications to dillo needed? How is > this > > handled > > for other apps? > As the iliad is an e-ink book reader, its software is a bit > unusual. > > The changes are specific to the iliad software stack. All > ported apps have to be modified to have the main window > CLASS to be "sh" and call a couple o functions on an iliad > library to enable the soft-keyboard button. > > Not so long ago we had to also add a library call to update > the screen whenever it changed, but we managed to build a > daemon for that using the XDamage extension. > > Cheers, Dario > > > >

July 11, 2009

Re: [fltk.general] Cross-compiling Dillo to ARM

by Johannes.Hofmann＠gmx.de

On Fri, Jul 10, 2009 at 12:39:04PM +0000, Dario Rodriguez wrote: > > Hi Alan, Steve: > > With Steve's fltk2 patch it has compiled correctly and works :), so I don't have to replace the X server binary (great!). > > Screenshot at: > http://www.mobileread.com/forums/showpost.php?p=517459&postcount=92 Excellent! Is the softkeyboard support something that needs to be added to fltk, or are modifications to dillo needed? How is this handled for other apps? Cheers, Johannes

July 10, 2009

Re: [fltk.general] Cross-compiling Dillo to ARM

by darirf＠yahoo.es

Hi Alan, Steve: With Steve's fltk2 patch it has compiled correctly and works :), so I don't have to replace the X server binary (great!). Screenshot at: http://www.mobileread.com/forums/showpost.php?p=517459&postcount=92 Thanks a lot to all :-D. Best regards, Dario

July 10, 2009

Re: [fltk.general] Cross-compiling Dillo to ARM

by acassis＠gmail.com

Hi Steve, On 7/9/09, =AA=F8=AE=F5 =B1i <stevegigijoe(a)yahoo.com.tw> wrote: > Hi Alan > > I just found a problem around src/x11/Font_xlfd:538last week > Below is my solution > > void fltk::setfont(Font* font, float psize) { > FontSize* f =3D current; > IFont* t =3D (IFont*)font; > > // only integers supported right now (this can be improved): > psize =3D int(psize+.5); > unsigned size =3D unsigned(psize); > // See if the current font is correct: > if(f && f->encoding && encoding_) { <<-- Suggest t= o > add some check > if (font =3D=3D current_font_ && psize =3D=3D current_size_ && <<-- M= ay crash > here > (f->encoding=3D=3Dencoding_ || > (!encoding_ || !strcmp(f->encoding, encoding_)))) > return; > } > current_font_ =3D font; current_size_ =3D psize; > Great! Your work around fixed the issue! Thank you very much, Alan

July 9, 2009

Re: [fltk.general] Cross-compiling Dillo to ARM

by stevegigijoe＠yahoo.com.tw

Hi Alan I just found a problem around src/x11/Font_xlfd:538last week Below is my solution void fltk::setfont(Font* font, float psize) { FontSize* f = current; IFont* t = (IFont*)font; // only integers supported right now (this can be improved): psize = int(psize+.5); unsigned size = unsigned(psize); // See if the current font is correct: if(f && f->encoding && encoding_) { <<-- Suggest to add some check if (font == current_font_ && psize == current_size_ && <<-- May crash here (f->encoding==encoding_ || (!encoding_ || !strcmp(f->encoding, encoding_)))) return; } current_font_ = font; current_size_ = psize; Steve ______________________________________________________________________________________________________ ¥I¶O€~®e¶qµL€W¡HYahoo!©_Œ¯¹q€l«Hœc2.0§K¶Oµ¹§A¡A«H¥ó¥Ã»·€£¥²§R¡I http://tw.mg0.mail.yahoo.com/dc/landing

July 9, 2009