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

IMG ratio

by Johannes.Hofmann＠gmx.de

Hi Jorge, On Fri, Jan 09, 2009 at 02:00:20PM -0300, Jorge Arellano Cid wrote: > Hi Johannes, > > Now that I have the image process mostly in my head, I'd like > to hook correct image ratio scaling when only one of width/height > is given. > > I see scaling done with the styleengine in a_Html_add_new_image > but 'props' goes away when popping the tag. How do I handle this? > > Do I have to preserve props in the stack until I have the > final data, or is there another way? Please explain. What about just setting the data that is available (width, height, or both) and let the image do the rest? It already handles the case where neither width nor height are given. So it should be possible to make it work with just width or height too. Am I missing something? Cheers, Johannes

Jan. 9, 2009

RE: Dillo in Debian

by devidfil＠gmail.com

Hi, I'm the current dillo Debian maintainer. I know, dillo 2.0 isn't in Debian right now but it isn't caused by me, fltk2 package is missing in Debian so I can't upload the 2.0 version right now. However I've done the fltk2 package for Debian and if all is ok it will uploaded (and accepted) in Debian as soon as possible (but it won't be in Lenny). If you will switch dillo to fltk1.3 then the problem will be the same because actually Debian doesn't have the 1.3 version of fltk (only 1.1) so I will need to work on a new package for fltk1.3 and this will require time (there is no a good documentation about how to work on a static lib package). So please continue to use fltk2. I'm sorry for the delay. Devid Antonio Filoni

Jan. 9, 2009

IMG ratio

by jcid＠dillo.org

Hi Johannes, Now that I have the image process mostly in my head, I'd like to hook correct image ratio scaling when only one of width/height is given. I see scaling done with the styleengine in a_Html_add_new_image but 'props' goes away when popping the tag. How do I handle this? Do I have to preserve props in the stack until I have the final data, or is there another way? Please explain. -- Cheers Jorge.-

Jan. 9, 2009

one more crash

by Johannes.Hofmann＠gmx.de

On Thu, Jan 08, 2009 at 01:31:13PM -0300, Jorge Arellano Cid wrote: > On Thu, Jan 08, 2009 at 01:37:26PM +0100, Johannes Hofmann wrote: > > On Wed, Jan 07, 2009 at 07:54:51PM -0300, Jorge Arellano Cid wrote: > > > On Wed, Jan 07, 2009 at 09:59:22PM +0100, Johannes Hofmann wrote: > > > > Sorry, but I'm seeing one more crash with > > > > current css-prototype. > > > > > > Thanks for the politeness. > > > It's good to be testing. > > > > > > I've long forgotten the mess that image processing code became. > > > That's why I've taken the time to try to push code cleanups... > > > > > > > > > > Program terminated with signal 11, Segmentation fault. > > > > #0 0x08073f8e in dw::core::Layout::createImgbuf (this=0x3, type=dw::core::Imgbuf::RGB, width=140, height=80) > > > > at ../dw/layout.hh:241 > > > > 241 return platform->createImgbuf (type, width, height); > > > > (gdb) bt > > > > #0 0x08073f8e in dw::core::Layout::createImgbuf (this=0x3, type=dw::core::Imgbuf::RGB, width=140, height=80) > > > > at ../dw/layout.hh:241 > > > > #1 0x0805f016 in a_Dicache_set_parms (url=0x28fa2a00, version=1, Image=0x2952d040, width=140, height=80, > > > > type=DILLO_IMG_TYPE_RGB) at dicache.c:268 > > > > #2 0x08072f2e in Jpeg_write (jpeg=0x28f85000, Buf=0x28f97000, BufSize=8000) at jpeg.c:299 > > > > #3 0x08072df4 in Jpeg_callback (Op=0, Client=0x297b4e20) at jpeg.c:246 > > > > #4 0x0805f407 in a_Dicache_callback (Op=0, Client=0x297b4e20) at dicache.c:396 > > > > > > The layout belongs to the bw, so it shouldn't dissappear with > > > repush. It looks like Image is already freed. > > > > > > Let's see: > > > > > > jcid@d620:~/C/Dillo/d2/dillo-css-wc2/src$ srch a_Image_ref > > > image.cc:void a_Image_ref(DilloImage *Image) > > > image.hh:void a_Image_ref(DilloImage *Image); > > > gif.c: a_Image_ref(web->Image); > > > jpeg.c: a_Image_ref(web->Image); > > > png.c: a_Image_ref(web->Image); > > > jcid@d620:~/C/Dillo/d2/dillo-css-wc2/src$ srch a_Image_unref > > > html.cc: a_Image_unref(li->image); > > > image.cc:void a_Image_unref(DilloImage *Image) > > > image.cc: a_Image_unref(Image); > > > image.hh:void a_Image_unref(DilloImage *Image); > > > web.cc: a_Image_unref(web->Image); > > > > > > this looks like unbalanced ref/unref for the Image. > > > Gif/Jpeg/Png match with image.cc > > > The initial Ref=1 matches web.cc > > > html.cc matches ?? > > > > > > Please test with one or two extra a_Image_ref() > > > at dicache.c:269, or at your choice, on the proper place! :-) > > > > That didn't help. Backing out abdae95b1c9e however helps so far. > > OK, let's back it out and see if it becomes stable again. It's been very stable for me after the backout, so I pushed that to css-prototype. We can come back to this later, if someone figures out the root of the problem. Cheers, Johannes

Jan. 9, 2009

Dillo in Debian

by akemnade＠tzi.de

Hi, a status update: I just got a notice from the official dillo package maintainer that fltk2 will be added to debian. So I think the chances for dillo 2.0 to go into debian (not lenny) will be good. Greetings Andreas Kemnade

Jan. 8, 2009

Dillo in Debian

by jcid＠dillo.org

Hi Wookey, A post in dillo-dev made me aware of this thread: http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=510348 Thanks for your comment ;-) Some technical facts (all available from dillo.org) * dillo-0.8.x is unmaintained * dillo-2.x is the official stable branch * dillo-2.x uses FLTK2 not GTK2 as stated in the thread IMHO it'd be good to have dillo-0.8.x in Lenny, at least until dillo-2.x makes its way into Debian. We've been working on this branch for more than a year and it's way better than the former (details in the website). I'm aware of the problem distros have with including statically linked packages, and it looks like dillo-2.x will be left out of them until this issue is solved. Unfortunately FLTK-2.0 is stalled and an official release of it is nowhere near in the future. OTOH, an active set of developers is pushing FLTK-1.3.x very fast. This branch provides more or less the same FLTK-2.0 does. It's being actively developed, is less buggy and more stable, and will most probably be released soon (I'm yet to ask the team about dates). At some point in time we'll be migrating to FLTK-1.3.x (it has almost the same API), and hopefully then it'll be easier to include dillo in Debian. If you make progress with the certificate patch, please let us know. We're fully devoted to CSS now, and have no SSL expert in the team :( -- On a personal level, I'd love to have Dillo used in Debian as a help browser. This is, since a long time ago I've noticed applications come with almost no help (F1 button in the old days) and help drives you to an "About" window. But OTOH they have very good HTML docs (usually in usr/share/), that could provide for accurate context-sensitive help pages. The problem is they don't hook a web browser to the help button because a bloated app. that takes a long time to start, only to crawl the computer afterwards, is the last thing a developer hopes as her end user experience. There's the possibility of having a simple API to remote control the browser so the same instance is used. Dillo is fast, lean, and low on library dependencies. Any doubts, just don't hesitate to ask. -- Cheers Jorge.-

Jan. 8, 2009

one more crash

by jcid＠dillo.org

On Thu, Jan 08, 2009 at 01:37:26PM +0100, Johannes Hofmann wrote: > On Wed, Jan 07, 2009 at 07:54:51PM -0300, Jorge Arellano Cid wrote: > > On Wed, Jan 07, 2009 at 09:59:22PM +0100, Johannes Hofmann wrote: > > > Sorry, but I'm seeing one more crash with > > > current css-prototype. > > > > Thanks for the politeness. > > It's good to be testing. > > > > I've long forgotten the mess that image processing code became. > > That's why I've taken the time to try to push code cleanups... > > > > > > > Program terminated with signal 11, Segmentation fault. > > > #0 0x08073f8e in dw::core::Layout::createImgbuf (this=0x3, type=dw::core::Imgbuf::RGB, width=140, height=80) > > > at ../dw/layout.hh:241 > > > 241 return platform->createImgbuf (type, width, height); > > > (gdb) bt > > > #0 0x08073f8e in dw::core::Layout::createImgbuf (this=0x3, type=dw::core::Imgbuf::RGB, width=140, height=80) > > > at ../dw/layout.hh:241 > > > #1 0x0805f016 in a_Dicache_set_parms (url=0x28fa2a00, version=1, Image=0x2952d040, width=140, height=80, > > > type=DILLO_IMG_TYPE_RGB) at dicache.c:268 > > > #2 0x08072f2e in Jpeg_write (jpeg=0x28f85000, Buf=0x28f97000, BufSize=8000) at jpeg.c:299 > > > #3 0x08072df4 in Jpeg_callback (Op=0, Client=0x297b4e20) at jpeg.c:246 > > > #4 0x0805f407 in a_Dicache_callback (Op=0, Client=0x297b4e20) at dicache.c:396 > > > > The layout belongs to the bw, so it shouldn't dissappear with > > repush. It looks like Image is already freed. > > > > Let's see: > > > > jcid@d620:~/C/Dillo/d2/dillo-css-wc2/src$ srch a_Image_ref > > image.cc:void a_Image_ref(DilloImage *Image) > > image.hh:void a_Image_ref(DilloImage *Image); > > gif.c: a_Image_ref(web->Image); > > jpeg.c: a_Image_ref(web->Image); > > png.c: a_Image_ref(web->Image); > > jcid@d620:~/C/Dillo/d2/dillo-css-wc2/src$ srch a_Image_unref > > html.cc: a_Image_unref(li->image); > > image.cc:void a_Image_unref(DilloImage *Image) > > image.cc: a_Image_unref(Image); > > image.hh:void a_Image_unref(DilloImage *Image); > > web.cc: a_Image_unref(web->Image); > > > > this looks like unbalanced ref/unref for the Image. > > Gif/Jpeg/Png match with image.cc > > The initial Ref=1 matches web.cc > > html.cc matches ?? > > > > Please test with one or two extra a_Image_ref() > > at dicache.c:269, or at your choice, on the proper place! :-) > > That didn't help. Backing out abdae95b1c9e however helps so far. OK, let's back it out and see if it becomes stable again. -- Cheers Jorge.-

Jan. 8, 2009

dillo about to be dropped from debian

by r00t＠constancy.org

FYI: http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=510348 it seems that dillo is about to be dropped from debian, because * ssl lacks proper certificate verification * it still uses gtk1.2 (personally, the first never bothered me, and i consider the second a _feature_) Greetings, Thorben Thuermer

Jan. 8, 2009

one more crash

by Johannes.Hofmann＠gmx.de

On Wed, Jan 07, 2009 at 07:54:51PM -0300, Jorge Arellano Cid wrote: > On Wed, Jan 07, 2009 at 09:59:22PM +0100, Johannes Hofmann wrote: > > Sorry, but I'm seeing one more crash with > > current css-prototype. > > Thanks for the politeness. > It's good to be testing. > > I've long forgotten the mess that image processing code became. > That's why I've taken the time to try to push code cleanups... > > > > Program terminated with signal 11, Segmentation fault. > > #0 0x08073f8e in dw::core::Layout::createImgbuf (this=0x3, type=dw::core::Imgbuf::RGB, width=140, height=80) > > at ../dw/layout.hh:241 > > 241 return platform->createImgbuf (type, width, height); > > (gdb) bt > > #0 0x08073f8e in dw::core::Layout::createImgbuf (this=0x3, type=dw::core::Imgbuf::RGB, width=140, height=80) > > at ../dw/layout.hh:241 > > #1 0x0805f016 in a_Dicache_set_parms (url=0x28fa2a00, version=1, Image=0x2952d040, width=140, height=80, > > type=DILLO_IMG_TYPE_RGB) at dicache.c:268 > > #2 0x08072f2e in Jpeg_write (jpeg=0x28f85000, Buf=0x28f97000, BufSize=8000) at jpeg.c:299 > > #3 0x08072df4 in Jpeg_callback (Op=0, Client=0x297b4e20) at jpeg.c:246 > > #4 0x0805f407 in a_Dicache_callback (Op=0, Client=0x297b4e20) at dicache.c:396 > > The layout belongs to the bw, so it shouldn't dissappear with > repush. It looks like Image is already freed. > > Let's see: > > jcid@d620:~/C/Dillo/d2/dillo-css-wc2/src$ srch a_Image_ref > image.cc:void a_Image_ref(DilloImage *Image) > image.hh:void a_Image_ref(DilloImage *Image); > gif.c: a_Image_ref(web->Image); > jpeg.c: a_Image_ref(web->Image); > png.c: a_Image_ref(web->Image); > jcid@d620:~/C/Dillo/d2/dillo-css-wc2/src$ srch a_Image_unref > html.cc: a_Image_unref(li->image); > image.cc:void a_Image_unref(DilloImage *Image) > image.cc: a_Image_unref(Image); > image.hh:void a_Image_unref(DilloImage *Image); > web.cc: a_Image_unref(web->Image); > > this looks like unbalanced ref/unref for the Image. > Gif/Jpeg/Png match with image.cc > The initial Ref=1 matches web.cc > html.cc matches ?? > > Please test with one or two extra a_Image_ref() > at dicache.c:269, or at your choice, on the proper place! :-) That didn't help. Backing out abdae95b1c9e however helps so far. Cheers, Johannes

Jan. 8, 2009

one more crash

by jcid＠dillo.org

On Wed, Jan 07, 2009 at 09:59:22PM +0100, Johannes Hofmann wrote: > Sorry, but I'm seeing one more crash with > current css-prototype. Thanks for the politeness. It's good to be testing. I've long forgotten the mess that image processing code became. That's why I've taken the time to try to push code cleanups... > Program terminated with signal 11, Segmentation fault. > #0 0x08073f8e in dw::core::Layout::createImgbuf (this=0x3, type=dw::core::Imgbuf::RGB, width=140, height=80) > at ../dw/layout.hh:241 > 241 return platform->createImgbuf (type, width, height); > (gdb) bt > #0 0x08073f8e in dw::core::Layout::createImgbuf (this=0x3, type=dw::core::Imgbuf::RGB, width=140, height=80) > at ../dw/layout.hh:241 > #1 0x0805f016 in a_Dicache_set_parms (url=0x28fa2a00, version=1, Image=0x2952d040, width=140, height=80, > type=DILLO_IMG_TYPE_RGB) at dicache.c:268 > #2 0x08072f2e in Jpeg_write (jpeg=0x28f85000, Buf=0x28f97000, BufSize=8000) at jpeg.c:299 > #3 0x08072df4 in Jpeg_callback (Op=0, Client=0x297b4e20) at jpeg.c:246 > #4 0x0805f407 in a_Dicache_callback (Op=0, Client=0x297b4e20) at dicache.c:396 The layout belongs to the bw, so it shouldn't dissappear with repush. It looks like Image is already freed. Let's see: jcid@d620:~/C/Dillo/d2/dillo-css-wc2/src$ srch a_Image_ref image.cc:void a_Image_ref(DilloImage *Image) image.hh:void a_Image_ref(DilloImage *Image); gif.c: a_Image_ref(web->Image); jpeg.c: a_Image_ref(web->Image); png.c: a_Image_ref(web->Image); jcid@d620:~/C/Dillo/d2/dillo-css-wc2/src$ srch a_Image_unref html.cc: a_Image_unref(li->image); image.cc:void a_Image_unref(DilloImage *Image) image.cc: a_Image_unref(Image); image.hh:void a_Image_unref(DilloImage *Image); web.cc: a_Image_unref(web->Image); this looks like unbalanced ref/unref for the Image. Gif/Jpeg/Png match with image.cc The initial Ref=1 matches web.cc html.cc matches ?? Please test with one or two extra a_Image_ref() at dicache.c:269, or at your choice, on the proper place! :-) -- Cheers Jorge.-

Jan. 7, 2009