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

Height attribute
by richard.jrmy＠gmail.com 18 Jul '09

18 Jul '09

Hello, I'm french, so I'll hope you could understand me. I'm developing for IE 7, Firefox and Dillo. It's not necessary to respect the W3C because it is for local networking use. I need to have a table which have an height of 100% of the page and my attribute doesn't work. I've put " height='100%' " in my <table> and I've tried with CSS too. In Firefox and IE that works but not in Dillo. In Dillo, there is only the width works. So, I would like to know if there is a solution to have a table or the body of 100% of the Dillo windows? I hope that yes, this is a good web browser. Have a good day. Regards. J?r?my

2 2

dpid includes
by jcid＠dillo.org 15 Jul '09

15 Jul '09

Hi, I just removed a bunch of redundant includes from the dpid/ directory. Please compile test on platforms other than GNU/Linux. TIA. -- Cheers Jorge.-

3 2

CSS class handling updated
by Johannes.Hofmann＠gmx.de 13 Jul '09

13 Jul '09

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

1 0

Re: [fltk.general] Cross-compiling Dillo to ARM
by darirf＠yahoo.es 13 Jul '09

13 Jul '09

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

3 2

Bug in Dillo's menu
by Hole.destructor＠gmx.de 12 Jul '09

12 Jul '09

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

2 2

Rv: Re: [Dillo-dev] Re: [fltk.general] Cross-compiling Dillo to ARM
by darirf＠yahoo.es 11 Jul '09

11 Jul '09

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 > > > >

1 0

Re: [fltk.general] Cross-compiling Dillo to ARM
by stevegigijoe＠yahoo.com.tw 09 Jul '09

09 Jul '09

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

2 1

Re: [fltk.general] Cross-compiling Dillo to ARM
by darirf＠yahoo.es 09 Jul '09

09 Jul '09

Hi Alan, A fellow user of the irex iliad tried to compile dillo2 for it (PXA255) and had similar issues with fltk2 (it was http://www.mobileread.com/forums/showpost.php?p=301183&postcount=84 ). Would you mind posting the configure flags that you have used for kdrive, fltk2 and dillo2? Thanks a lot. Hope that those configure also works for the iliad and we can replace the aging dillo 0.8.6 O:). Best regards and thanks again to all involved in dillo development. Dario. --- El mi?, 8/7/09, Alan Carvalho de Assis <acassis(a)gmail.com> escribi?: > De: Alan Carvalho de Assis <acassis(a)gmail.com> > Asunto: [Dillo-dev] Re: [fltk.general] Cross-compiling Dillo to ARM > Para: "Mirror of fltk.general Newsgroup" <fltk(a)easysw.com> > CC: "dillo-dev" <dillo-dev(a)dillo.org> > Fecha: mi?rcoles, 8 julio, 2009 8:58 > Hi Ian, > > On 7/8/09, imacarthur <imacarthur(a)gmail.com> > wrote: > > > > On 8 Jul 2009, at 16:33, Alan Carvalho de Assis > wrote: > > > > fltk-2 is not my strong suit, so what follows is just > guesswork > > really. However, here are some questions that might be > relevant: > > > > What fonts does your target system actually have > installed? Which > > names, what types, etc.? > > > > Now, the reason I ask is that I see from the gdb trace > that your > > program crashed in Font_xlfd.cxx, so presumably it was > attempting to > > load an "old style" XLFD font. > > > > You say your test build works with fltk-1.3, and it > defaults to using > > "new-style" XFT fonts, rather than using XLFD fonts > (although it can > > also use XLFD fonts, *or* can be built to only use > XLFD fonts by > > passing --disable-xft to configure at build time.) > > > > So... I'm guessing that the fltk-1.3 build works for > some reason > > because it is using XFT and the fltk-2 build fails > because it > > attempts to use XLFD. Does that seem feasible? > > > > If so, it might be worth trying to make sure the > fltk-2 build loads > > an XFT rather than XLFD font, see how that goes. > > > > All that said, however, a default flrk-2 build *ought* > to default to > > XFT enabled anyway - unless someone has changed that? > > > > Did you later that setting during config by any > chance? Maybe that is > > somewhere to start looking, if nothing else... > > > > You are right, I compiled Xorg (kdrive) with > "--enable-builtin-fonts", > then FLTK2 doesn't work. > > I think FLTK2 could to work with only "fixed" font, just > like FLTK1 does. > > Thank you very much! > > Regards, > > P.S.: Dillo is working fine on i.MX27 now! > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

2 1

(no subject)
by acassis＠gmail.com 09 Jul '09

09 Jul '09

Hi All, I am trying to port Dillo to i.MX27 (ARM9) processor. Using LTIB build system (www.ltib.org) to cross-compile FLTK. I cross-compiled FLTK2, but it is crashing, I can't run any demo example. To FLTK1.3 everything works fine, I ran all examples successfully. To FLTK2 nothing works. I searched Internet for similar error, but nothing solves it. I tested these FLTK revision: fltk-2.0.x-r6793 fltk-2.0.x-r6101 It appears to crash at "fltk::setfont". In fact I can see "bad font: fixed" message just before that "Segmentation Fault". Could someone give me some suggestion to solve this issue? See below the gdb backtrace. I am running gdbserver on i.MX27 board (IP 192.168.0.180) Best Regards, Alan $ arm-elf-gdb /home/alan/ltib/rootfs/home/test/hello GNU gdb 6.6 Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-linux"... (gdb) target remote 192.168.0.180:3333 Remote debugging using 192.168.0.180:3333 warning: Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. 0x400007e0 in ?? () (gdb) set solib-absolute-prefix /home/alan/ltib/rootfs (gdb) b main Breakpoint 1 at 0xb9e8: file hello.cxx, line 9. (gdb) c Continuing. Breakpoint 1, main (argc=1, argv=0xbeaa5e44) at hello.cxx:9 9 Window *window = new Window(300, 180); (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x4025dfe0 in strcmp () from /home/alan/ltib/rootfs/lib/libc.so.6 (gdb) bt #0 0x4025dfe0 in strcmp () from /home/alan/ltib/rootfs/lib/libc.so.6 #1 0x0000d1e4 in fltk::setfont (font=0x3a0ac, psize=12) at x11/Font_xlfd.cxx:542 #2 0x0001ac80 in fltk::Widget::draw_box (this=0x40b68, r=@0xbeaa5a18) at Widget_draw.cxx:94 #3 0x0001acc0 in fltk::Widget::draw_box (this=0x0) at Widget_draw.cxx:88 #4 0x0001a810 in fltk::Widget::draw (this=0x0) at Widget.cxx:644 #5 0x0000d618 in fltk::Group::draw_child (this=<value optimized out>, w=@0x40b68) at Group.cxx:750 #6 0x0000e218 in fltk::Group::draw (this=0x406e0) at Group.cxx:682 #7 0x00013ff8 in fltk::Window::flush (this=0x406e0) at x11/run.cxx:2566 #8 0x000116d4 in fl_window_flush (window=0x406e0) at run.cxx:657 #9 0x00011784 in fltk::flush () at run.cxx:691 #10 0x00016a60 in fltk::wait (time_to_wait=1.00000002e+20) at run.cxx:484 #11 0x00016b8c in fltk::run () at run.cxx:397 #12 0x402071cc in __libc_start_main () from /home/alan/ltib/rootfs/lib/libc.so.6 #13 0x0000b94c in _start () (gdb)

2 2

Re: [fltk.general] Cross-compiling Dillo to ARM
by acassis＠gmail.com 08 Jul '09

08 Jul '09

Hi Ian, On 7/8/09, imacarthur <imacarthur(a)gmail.com> wrote: > > On 8 Jul 2009, at 16:33, Alan Carvalho de Assis wrote: > > fltk-2 is not my strong suit, so what follows is just guesswork > really. However, here are some questions that might be relevant: > > What fonts does your target system actually have installed? Which > names, what types, etc.? > > Now, the reason I ask is that I see from the gdb trace that your > program crashed in Font_xlfd.cxx, so presumably it was attempting to > load an "old style" XLFD font. > > You say your test build works with fltk-1.3, and it defaults to using > "new-style" XFT fonts, rather than using XLFD fonts (although it can > also use XLFD fonts, *or* can be built to only use XLFD fonts by > passing --disable-xft to configure at build time.) > > So... I'm guessing that the fltk-1.3 build works for some reason > because it is using XFT and the fltk-2 build fails because it > attempts to use XLFD. Does that seem feasible? > > If so, it might be worth trying to make sure the fltk-2 build loads > an XFT rather than XLFD font, see how that goes. > > All that said, however, a default flrk-2 build *ought* to default to > XFT enabled anyway - unless someone has changed that? > > Did you later that setting during config by any chance? Maybe that is > somewhere to start looking, if nothing else... > You are right, I compiled Xorg (kdrive) with "--enable-builtin-fonts", then FLTK2 doesn't work. I think FLTK2 could to work with only "fixed" font, just like FLTK1 does. Thank you very much! Regards, P.S.: Dillo is working fine on i.MX27 now!

1 0