- Dillo-dev - lists.mailman3.com

dillo crashes on (incorrect) tables
by matthias.franz＠ujf-grenoble.fr Oct. 19, 2007

Oct. 19, 2007

Hi, the following (syntactically incorrect) HTML code makes dillo2 crash on my machine. Dillo1 is fine. <html> <table> <tr></tr> <tr><td colspan="3"></td></tr> <td colspan="3"> </table> </html> Cheers, -- Matthias Franz

1 0

Re: receiver patch: html page menu working, image menu present but not called.
by place＠gobigwest.com Oct. 19, 2007

Oct. 19, 2007

Jorge wrote: > On Thu, Oct 18, 2007 at 10:56:39PM +0000, place wrote: > > > The fact of the linkblock not being freed in current code (see warning > > > from compiling html.cc) is just because I haven't found the clean & proper > > > place to hook Html_lb_free() (to widget destruction probably). IIRC there > > > was a ...connect_after() hook in GTK that worked ok after deletion of the > > > object (which I haven't yet found an analog in FLTK2). > > > > So I should regard "linkblock" as "the bag of event handling stuff"? Okay. > > It's a bag for links, form data etc... > > I've longed to get rid of it several times, but I don't see a > much cleaner approach. This may be the time, or maybe not. > > For instance, if the linkblock data is put inside the html > struct, and the whole turned into a class, it would look much > cleaner. It would also be clearer in the case of plain text (it > also receives the signal for page menu), and having a separate > linkblock or receiver for it seems odd. > > OTOH, the data that now belongs to the html-struct is freed > when parsing finishes, and it would remain inside the class, > which is a bit untidy, but if we make this part a pointer inside > the shiny new class, it could go NULL at freeing time. This looks > cleaner. Indeed. > > I now have new code for image signals. In an effort not to add an extra argument > > to the signals (which seemed hacky -- either an image_vs_link sort of argument, > > or an image_number sort of argument), I ended up making a vector of image > > receivers, one per image. I can't decide whether that is bad or reasonably > > sensible. If a better solution is obvious to you, please let me know. > > Not obvious, but I think of the case of pages with hundreds or > thousands of images (e.g.): > > http://chlamydia.fs.ei.tum.de/pub/DragonFly/packages/stable/DragonFly-1.10/… > > Memory consumption for this vector may grow too much. A single > int value working as an index to the proper URL/data from within > a single image signal receiver looks cleaner (from a distance :-) All right. > > So the image menu works, an ugly little button toggles image loading, and > > click-to-load works, though I don't have any placeholder image. > > More than enough for a start! And an opportunity for people who say "I'd love to help dillo, but don't know how to write code" to make a little tiny button... I was going to try having a single patch for all of that, but it was already teetering on the edge between small-enough and too-much. I think I'll try to pull out the menu and the button to send you first, since they're harmless, and then the rest after I redo it. > > (if only forms worked well enough to perform search queries, > > I just about wouldn't need my old dillo around anymore!) > > I know what you mean. Given that, plus the scrolling bug, > search text inside pages and anchors, it'd looks very sexy to me! > > > > BTW, not that it really matters at present, but I discovered that > > in Html_write_raw(), you can get token_start to be greater than bufsize. > > Go through the verbatim part at the top until token_start = buf_index = bufsize, > > then have the isspace() test right below it be true. > > It looks like this is why my iconv buffer code crashed often on me. > > Thanks for the report, I'll look at it when I find some time. > > > BTW, this duscussion is more than worth to have in dillo-dev. > Can I take it there? *cc:s dillo-dev, resists urge to trim quotes*

1 0

./configure confused about FLTK version
by hans＠stare.cz Oct. 19, 2007

Oct. 19, 2007

Hi all, it seems that the ./configure script as generated by ./autogen.sh of current cvs tree will happily go with fltk < 2, giving compilation errors later. Jan $ uname -a OpenBSD dell.stare.cz 4.1 GENERIC#0 i386 $ pkg_info | grep fltk fltk-1.1.7 Fast-Light Tool Kit $ pwd /home/hans/src $ cvs -z3 -d:pserver:anonymous@auriga.wearlab.de:/sfhome/cvs/dillo co dillo2 cvs checkout: Updating dillo2 [...] $ cvs -z3 -d:pserver:anonymous@auriga.wearlab.de:/sfhome/cvs/dillo co dw2 cvs checkout: Updating dw2 [...] $ ln -s dw2 dw-testbed $ cd dw-testbed $ export AUTOCONF_VERSION=2.61 $ export AUTOMAKE_VERSION=1.9 $ ./autogen.sh aclocal found autoheader found autoconf found automake found [Checks passed] Generating... [...] $ ./configure [...] checking FLTK2... yes [...] config.status: executing depfiles commands $ $ gmake [...] if g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -I. -I/usr/local/include -O2 -pipe -I/usr/local/include -I/usr/X11R6/include -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT libDw_fltk_a-fltkcomplexbutton.o -MD -MP -MF ".deps/libDw_fltk_a-fltkcomplexbutton.Tpo" -c -o libDw_fltk_a-fltkcomplexbutton.o `test -f 'fltkcomplexbutton.cc' || echo './'`fltkcomplexbutton.cc; \ then mv -f ".deps/libDw_fltk_a-fltkcomplexbutton.Tpo" ".deps/libDw_fltk_a-fltkcomplexbutton.Po"; else rm -f ".deps/libDw_fltk_a-fltkcomplexbutton.Tpo"; exit 1; fi fltkcomplexbutton.cc:23:25: fltk/events.h: No such file or directory fltkcomplexbutton.cc:24:25: fltk/damage.h: No such file or directory fltkcomplexbutton.cc:25:24: fltk/Group.h: No such file or directory fltkcomplexbutton.cc:26:22: fltk/Box.h: No such file or directory In file included from fltkcomplexbutton.cc:29: fltkcomplexbutton.hh:28:24: fltk/Group.h: No such file or directory In file included from fltkcomplexbutton.cc:29: fltkcomplexbutton.hh:34: error: `fltk' is not a class or namespace fltkcomplexbutton.hh:35: error: `Group' is not a class or namespace fltkcomplexbutton.hh:35: error: invalid base-class specification fltkcomplexbutton.hh:43: error: syntax error before `&' token fltkcomplexbutton.hh:45: error: syntax error before `::' token [...]

3 5

[patch] CPU usage when moving mouse on large page
by Johannes.Hofmann＠gmx.de Oct. 19, 2007

Oct. 19, 2007

Hi, here is another patch regarding the performance of dillo-fltk. It addresses the high CPU usage when moving the cursor on a large page especially if it contains many links and images. See http://chlamydia.fs.ei.tum.de/pub/DragonFly/packages/stable/DragonFly-1.10/… as an example. Note, that also dillo1 uses quite some CPU when moving the mouse on that page. The patch moves Layout::getWidgetAtPoint0() to Widget::getWidgetAtPoint() and makes it virtual so that widgets can provide an own optimzed version of that method. For the Textblock widget an optimized version is implemented that uses findLineIndex(). This patch is a bit more invasive than the scroll-patch, so I would appreciate comments from the dw author(s). Johannes diff --git a/dw/layout.cc b/dw/layout.cc --- a/dw/layout.cc +++ b/dw/layout.cc @@ -703,47 +703,6 @@ void Layout::leaveNotify (View *view, Bu } } -/** - * \brief Search recursively through widget. - * - * Used by dw::core::Layout:getWidgetAtPoint. - */ -Widget *Layout::getWidgetAtPoint0 (Widget *widget, int x, int y, int level) -{ - Iterator *it; - Widget *childAtPoint; - - //_MSG ("%*s-> examining the %s %p (%d, %d, %d x (%d + %d))\n", - // 3 * level, "", gtk_type_name (GTK_OBJECT_TYPE (widget)), widget, - // widget->allocation.x, widget->allocation.y, - // widget->allocation.width, widget->allocation.ascent, - // widget->allocation.descent); - - if (x >= widget->allocation.x && - y >= widget->allocation.y && - x <= widget->allocation.x + widget->allocation.width && - y <= widget->allocation.y + widget->getHeight ()) { - //_MSG ("%*s -> inside\n", 3 * level, ""); - /* - * Iterate over the children of this widget. Test recursively, whether - * the point is within the child (or one of its children...). If there - * is such a child, it is returned. Otherwise, this widget is returned. - */ - childAtPoint = NULL; - it = widget->iterator (Content::WIDGET, false); - - while (childAtPoint == NULL && it->next ()) - childAtPoint = getWidgetAtPoint0 (it->getContent()->widget, - x, y, level + 1); - - if (childAtPoint) - return childAtPoint; - else - return widget; - } else - return NULL; -} - /* * Return the widget at position (x, y). Return NULL, if there is no widget. */ @@ -752,7 +711,7 @@ Widget *Layout::getWidgetAtPoint (int x, //_MSG ("------------------------------------------------------------\n"); //_MSG ("widget at (%d, %d)\n", x, y); if (topLevel) - return getWidgetAtPoint0 (topLevel, x, y, 0); + return topLevel->getWidgetAtPoint (x, y, 0); else return NULL; } diff --git a/dw/layout.hh b/dw/layout.hh --- a/dw/layout.hh +++ b/dw/layout.hh @@ -87,7 +87,6 @@ private: enum ButtonEventType { BUTTON_PRESS, BUTTON_RELEASE, MOTION_NOTIFY }; - Widget *getWidgetAtPoint0 (Widget *widget, int x, int y, int level); Widget *getWidgetAtPoint (int x, int y); void moveToWidget (Widget *newWidgetAtPoint, ButtonState state); diff --git a/dw/textblock.cc b/dw/textblock.cc --- a/dw/textblock.cc +++ b/dw/textblock.cc @@ -1730,6 +1730,50 @@ void Textblock::addLinebreak (core::styl wordWrap (words->size () - 1); } + +/** + * \brief Search recursively through widget. + * + * This is an optimized version of the general + * dw::core::Widget::getWidgetAtPoint method. + */ +core::Widget *Textblock::getWidgetAtPoint(int x, int y, int level) +{ + int lineIndex, wordIndex; + Line *line; + + if (x < allocation.x || + y < allocation.y || + x > allocation.x + allocation.width || + y > allocation.y + getHeight ()) { + return NULL; + } + + lineIndex = findLineIndex (y - allocation.y); + + if (lineIndex < 0 || lineIndex >= lines->size ()) { + return this; + } + + line = lines->getRef (lineIndex); + + for (wordIndex = line->firstWord; wordIndex < line->lastWord; wordIndex++) { + Word *word = words->getRef (wordIndex); + + if (word->content.type == core::Content::WIDGET) { + core::Widget * childAtPoint; + childAtPoint = word->content.widget->getWidgetAtPoint (x, y, + level + 1); + if (childAtPoint) { + return childAtPoint; + } + } + } + + return this; +} + + /** * This function "hands" the last break of a page "over" to a parent * page. This is used for "collapsing spaces". diff --git a/dw/textblock.hh b/dw/textblock.hh --- a/dw/textblock.hh +++ b/dw/textblock.hh @@ -366,6 +366,7 @@ public: void addParbreak (int space, core::style::Style *style); void addLinebreak (core::style::Style *style); + core::Widget *getWidgetAtPoint (int x, int y, int level); void handOverBreak (core::style::Style *style); void changeLinkColor (int link, int newColor); void changeWordStyle (int from, int to, core::style::Style *style, diff --git a/dw/widget.cc b/dw/widget.cc --- a/dw/widget.cc +++ b/dw/widget.cc @@ -676,6 +676,48 @@ Widget *Widget::getNearestCommonAncestor } +/** + * \brief Search recursively through widget. + * + * Used by dw::core::Layout:getWidgetAtPoint. + */ +Widget *Widget::getWidgetAtPoint (int x, int y, int level) +{ + Iterator *it; + Widget *childAtPoint; + + //_MSG ("%*s-> examining the %s %p (%d, %d, %d x (%d + %d))\n", + // 3 * level, "", gtk_type_name (GTK_OBJECT_TYPE (widget)), widget, + // allocation.x, allocation.y, + // allocation.width, allocation.ascent, + // allocation.descent); + + if (x >= allocation.x && + y >= allocation.y && + x <= allocation.x + allocation.width && + y <= allocation.y + getHeight ()) { + //_MSG ("%*s -> inside\n", 3 * level, ""); + /* + * Iterate over the children of this widget. Test recursively, whether + * the point is within the child (or one of its children...). If there + * is such a child, it is returned. Otherwise, this widget is returned. + */ + childAtPoint = NULL; + it = iterator (Content::WIDGET, false); + + while (childAtPoint == NULL && it->next ()) + childAtPoint = it->getContent()->widget->getWidgetAtPoint (x, y, + level + 1); + + if (childAtPoint) + return childAtPoint; + else + return this; + } else + return NULL; +} + + void Widget::scrollTo (HPosition hpos, VPosition vpos, int x, int y, int width, int height) { diff --git a/dw/widget.hh b/dw/widget.hh --- a/dw/widget.hh +++ b/dw/widget.hh @@ -405,6 +405,8 @@ public: inline Layout *getLayout () { return layout; } + virtual Widget *getWidgetAtPoint (int x, int y, int level); + void scrollTo (HPosition hpos, VPosition vpos, int x, int y, int width, int height);

1 0

Dillo FLTK2 alpha release for developers
by None Oct. 18, 2007

Oct. 18, 2007

Hi there, This is an alpha release of the next generation of the Dillo web browser. The code underwent a major rewrite: significant parts of the codebase were ported to C++, and the rendering engine now uses the FLTK2 library instead of GTK1. Please read the README inside dillo's tarball. Developers willing to join the project and contribute are highly encouraged. Sebastian did an excellent work documenting the new dillo widget engine (just run doxygen inside DW tree). This is a good milestone in the project's history, we hope to be able to continue working on it. This is one step ahead, and we need other developers help. Please note that this code is under GPL3! BTW, if you want to know what antialiased utf-8 is, just go to: http://www.gnu.org/home.fa.html after compiling dillo-fltk. Here are the instructions on how to get it working: --------------- Get these files --------------- wget http://www.dillo.org/dillo2/fltk-2.0.x-r5917.tar.bz2 wget http://www.dillo.org/dillo2/dw-testbed-0.0.43j.tar.bz2 wget http://www.dillo.org/dillo2/dillo-f15f.tar.bz2 ----- FLTK2 ----- tar jxvf fltk-2.0.x-r5917.tar.bz2 cd fltk-2.0.x-r5917 make // Should compile cleanly if you have the // necessary development packages... cd test; ./demo // You can play with it too! cd .. su make install // Install FLTK2 libraries exit cd .. ---------- dw-0.0.43j ---------- tar jxvf dw-testbed-0.0.43j.tar.bz2 cd dw-testbed-0.0.43j ./configure make cd test // You can test it from here cd ../.. doxygen // Excellent documentation in html cd html; dillo index.html // (start browsing docs here) cd ../.. ln -s dw-testbed-0.0.43j dw-testbed // Don't forget this link ---------- dillo f15j ---------- tar jxvf dillo-f15f.tar.bz2 cd dillo-f15 ./configure make su make install // Needed for dpis exit cd src ./dillo-fltk // This is is it! cd .. -------- dillorc2 -------- There's a "dillorc2" file inside the tarball's top directory: cp dillorc2 ~/.dillo/ that will let you use the new and old dillo without trouble. -- Cheers Jorge.-

10 22

[patch] improve scroll performance of dillo-fltk
by Johannes Hofmann Oct. 16, 2007

Oct. 16, 2007

Hi, below is an initial patch that improves scrolling performance of dillo-fltk by copying screen data instead of rerendering it. It's based on Scroll.cxx from fltk. The difference is noticeable mostly when scrolling large images especially within a remote X11 session. The newly introduced scrollDX / scrollDY could probabely be combined with the existing oldScrollX / oldScrollY variables. Regards, Johannes diff --git a/dw-testbed-0.0.43j/dw/fltkviewbase.cc b/dw-testbed-0.0.43j/dw/fltkviewbase.cc --- a/dw-testbed-0.0.43j/dw/fltkviewbase.cc +++ b/dw-testbed-0.0.43j/dw/fltkviewbase.cc @@ -54,18 +54,16 @@ void FltkViewBase::draw () Group::draw (); - if (damage () & DAMAGE_EXPOSE) { - setcolor (bgColor); - ::fltk::Rectangle rect (0, 0, w(), h()); - fillrect (rect); - - core::Rectangle area; - area.x = translateViewXToCanvasX (0); - area.y = translateViewYToCanvasY (0); - area.width = translateViewXToCanvasX (0 + w ()) - 0; - area.height = translateViewYToCanvasY (0 + h ()) - 0; - theLayout->expose (this, &area); - } + setcolor (bgColor); + ::fltk::Rectangle rect (0, 0, w(), h()); + fillrect (rect); + + core::Rectangle area; + area.x = translateViewXToCanvasX (0); + area.y = translateViewYToCanvasY (0); + area.width = translateViewXToCanvasX (0 + w ()) - 0; + area.height = translateViewYToCanvasY (0 + h ()) - 0; + theLayout->expose (this, &area); } core::ButtonState getDwButtonState () diff --git a/dw-testbed-0.0.43j/dw/fltkviewport.cc b/dw-testbed-0.0.43j/dw/fltkviewport.cc --- a/dw-testbed-0.0.43j/dw/fltkviewport.cc +++ b/dw-testbed-0.0.43j/dw/fltkviewport.cc @@ -131,8 +131,8 @@ void FltkViewport::hscrollbarChanged () { int oldScrollX = scrollX; scrollX = hscrollbar->value (); - /** \bug Inefficient */ - redraw (DAMAGE_EXPOSE); + scrollDX = scrollX - oldScrollX; + redraw (DAMAGE_SCROLL); updateCanvasWidgets (oldScrollX, scrollY); theLayout->scrollPosChanged (this, scrollX, scrollY); } @@ -141,8 +141,8 @@ void FltkViewport::vscrollbarChanged () { int oldScrollY = scrollY; scrollY = vscrollbar->value (); - /** \bug Inefficient */ - redraw (DAMAGE_EXPOSE); + scrollDY = scrollY - oldScrollY; + redraw (DAMAGE_SCROLL); updateCanvasWidgets (scrollX, oldScrollY); theLayout->scrollPosChanged (this, scrollX, scrollY); } @@ -163,6 +163,25 @@ void FltkViewport::layout () { theLayout->viewportSizeChanged (this, w(), h()); adjustScrollbarsAndGadgetsAllocation (); +} + +void FltkViewport::draw_area (void *data, const Rectangle& cr ) +{ + FltkViewport *vp = (FltkViewport*) data; + push_clip(cr); + + vp->FltkWidgetView::draw (); + + //draw_child (*hscrollbar); + //draw_child (*vscrollbar); + + for(Iterator <TypedPointer < ::fltk::Widget> > it = vp->gadgets->iterator (); + it.hasNext (); ) { + ::fltk::Widget *widget = it.getNext()->getTypedValue (); + vp->draw_child (*widget); + } + + pop_clip(); } void FltkViewport::draw () @@ -170,20 +189,16 @@ void FltkViewport::draw () int hdiff = vscrollbar->visible () ? SCROLLBAR_THICKNESS : 0; int vdiff = hscrollbar->visible () ? SCROLLBAR_THICKNESS : 0; Rectangle cr (0, 0, w () - hdiff, h () - vdiff); - push_clip(cr); - - FltkWidgetView::draw (); - - //draw_child (*hscrollbar); - //draw_child (*vscrollbar); - - for(Iterator <TypedPointer < ::fltk::Widget> > it = gadgets->iterator (); - it.hasNext (); ) { - ::fltk::Widget *widget = it.getNext()->getTypedValue (); - draw_child (*widget); - } - - pop_clip(); + int d = damage(); + + if (d == DAMAGE_SCROLL) { + scrollrect(cr, -scrollDX, -scrollDY, draw_area, this); + } else { + draw_area(this, cr); + } + + scrollDX = 0; + scrollDY = 0; } int FltkViewport::handle (int event) @@ -205,8 +220,9 @@ int FltkViewport::handle (int event) case PageUpKey: oldScrollY = scrollY; scrollY -= vscrollbar->pagesize (); + scrollDY = scrollY - oldScrollY; adjustScrollbarValues (); - redraw (DAMAGE_EXPOSE); + redraw (DAMAGE_SCROLL); updateCanvasWidgets (scrollX, oldScrollY); theLayout->scrollPosChanged (this, scrollX, scrollY); return 1; @@ -214,8 +230,9 @@ int FltkViewport::handle (int event) case PageDownKey: oldScrollY = scrollY; scrollY += vscrollbar->pagesize (); + scrollDY = scrollY - oldScrollY; adjustScrollbarValues (); - redraw (DAMAGE_EXPOSE); + redraw (DAMAGE_SCROLL); updateCanvasWidgets (scrollX, oldScrollY); theLayout->scrollPosChanged (this, scrollX, scrollY); return 1; @@ -254,12 +271,13 @@ void FltkViewport::scrollTo (int x, int void FltkViewport::scrollTo (int x, int y) { int oldScrollX = scrollX; - //int oldScrollY = scrollY; + int oldScrollY = scrollY; scrollX = x; scrollY = y; + scrollDX = scrollX - oldScrollX; + scrollDY = scrollY - oldScrollY; adjustScrollbarValues (); - /** \bug Inefficient */ - redraw (DAMAGE_EXPOSE); + redraw (DAMAGE_SCROLL); updateCanvasWidgets (oldScrollX, scrollY); } diff --git a/dw-testbed-0.0.43j/dw/fltkviewport.hh b/dw-testbed-0.0.43j/dw/fltkviewport.hh --- a/dw-testbed-0.0.43j/dw/fltkviewport.hh +++ b/dw-testbed-0.0.43j/dw/fltkviewport.hh @@ -20,6 +20,7 @@ private: enum { SCROLLBAR_THICKNESS = 15 }; int scrollX, scrollY; + int scrollDX, scrollDY; ::fltk::Scrollbar *vscrollbar, *hscrollbar; @@ -35,6 +36,7 @@ private: static void vscrollbarCallback (Widget *vscrollbar, void *viewportPtr); void updateCanvasWidgets (int oldScrollX, int oldScrollY); + static void draw_area (void *data, const Rectangle& cr); protected: int translateViewXToCanvasX (int x);

6 11

Fwd: Re: [Dillo-dev] New CVS directions page
by 4winter＠informatik.uni-hamburg.de Oct. 16, 2007

Oct. 16, 2007

On Fri, 12 Oct 2007 17:41:41 -0400, dillo-dev-bounces(a)dillo.org wrote: > Please let me know if this time the directions work! :-P I would suggest the following changes: - find dw2-cur -name CVS -exec rm \{\} \; - find dillo2-cur -name CVS -exec rm \{\} \; + find dw2-cur dillo2-cur -name CVS | xargs rm -R - cd dw2-cur; ./autogen.sh; ./configure; make + cd dw2-cur; ./autogen.sh && ./configure && make cd .. - cd dillo2-cur; ./autogen.sh; ./configure; make + cd dillo2-cur; ./autogen.sh && ./configure && make Hummel Hummel, Justus

3 2

Re: character entity references produce garbage
by matthias.franz＠ujf-grenoble.fr Oct. 15, 2007

Oct. 15, 2007

On Tue, Oct 09, 2007 at 11:08:21PM +0200, Johannes Hofmann wrote: > I can now reproduce this on a debian system without libxft-dev > installed. > Do you still see this after installing libxft-dev? No. Now it's gone, even if I comment out "freetype" and "type1" in my xorg.conf. (I understand that Xft has something to do with font rasterizing.) But it should work without Xft as well, shouldn't it? -- Matthias Franz

2 3

New CVS and newwest FLTK2 release
by bogus＠does.not.exist.com Oct. 14, 2007

Oct. 14, 2007

Hi there, I just updated the CVS so it can use the latest stable FLTK2. Get FLTK2 from www.fltk.org (r5941), or from here: wget http://www.dillo.org/dillo2/fltk-2.0.x-r5941.tar.bz2 You'll have to configure, compile and install this new version, and to rebuild the whole dw2 and dillo2. That way we stay more current. -- Cheers Jorge.-

1 0

Re: [patch] improve scroll performance of dillo-fltk
by Johannes.Hofmann＠gmx.de Oct. 14, 2007

Oct. 14, 2007

Hi Matthias, I just made a xtrace (http://packages.debian.org/unstable/x11/xtrace) when scrolling the http://www.w3.org/TR/xslt page with patched dillo (result below). I think this is pretty good already. Just the newly exposed glyphs get rendered. Each word is sent to the X-Server seperately. This might be an area for improvement. Could you try the same on your system, so that we find out, whether the patch does not work for you or whether scrolling is still too CPU consuming even with the working patch? Here is what I did to get the trace: xtrace > /tmp/xtrace.out export DISPLAY=:9 dillo-fltk http://www.w3.org/TR/xslt Then scroll using the triangle of the scrollbar for a while and stop dillo. The resulting file is huge but I am only interested in the repeating sections that result from the scrolling and start with CopyArea. Gruss, Johannes 000:<:c474: 16: Request(56): ChangeGC gc=0x01c00009 values={foreground=0x00000000} 000:<:c475: 28: Request(62): CopyArea src-drawable=0x01c00008 dst-drawable=0x01c00008 gc=0x01c00009 src-x=0 src-y=93 dst-x=0 dst-y=73 width=765 height=467 000:>:c475: Event NoExposure(14) drawable=0x01c00008 minor-opcode=0x0000 major-opcode=0x3e 000:<:c476: 20: Request(59): SetClipRectangles ordering=YXBanded(0x03) gc=0x01c00009 clip-x-origin=0 clip-y-origin=0 rectangles ={x=0 y=540 w=765 h=20}; 000:<:c477: 20: RENDERRequest(154): RenderSetPictureClipRectangles picture=0x01c00036 xOrigin=0 yOrigin=0 rectangles={x=0 y=540 w=765 h=20}; 000:<:c478: 20: Request(59): SetClipRectangles ordering=YXBanded(0x03) gc=0x01c00009 clip-x-origin=0 clip-y-origin=0 rectangles ={x=0 y=540 w=765 h=20}; 000:<:c479: 16: Request(56): ChangeGC gc=0x01c00009 values={foreground=0x00e0e0e0} 000:<:c47a: 20: Request(70): PolyFillRectangle drawable=0x01c00008 gc=0x01c00009 rectangles={x=0 y=0 w=780 h=580}; 000:<:c47b: 20: Request(59): SetClipRectangles ordering=YXBanded(0x03) gc=0x01c00009 clip-x-origin=0 clip-y-origin=0 rectangles ={x=0 y=540 w=765 h=20}; 000:<:c47c: 16: Request(56): ChangeGC gc=0x01c00009 values={foreground=0x00dcd1ba} 000:<:c47d: 20: Request(70): PolyFillRectangle drawable=0x01c00008 gc=0x01c00009 rectangles={x=0 y=540 w=765 h=20}; 000:<:c47e: 60: RENDERRequest(154): RenderCompositeGlyphs8 op=Over(0x03) src=0x01c0000f dst=0x01c00036 maskFormat=0x00000026 glyphset=0x01c00063 xSrc=0 ySrc=0 glyphcmds={deltax=5 deltay=530 glyphs=0x1f,0x5b,0x56,0x4f,0x1d,0x44,0x5 3,0x53,0x4f,0x5c,0x10,0x57,0x48,0x50,0x53,0x4f,0x44,0x57,0x48,0x56,0x12,0x21; }; 000:<:c47f: 40: RENDERRequest(154): RenderCompositeGlyphs8 op=Over(0x03) src=0x01c0000f dst=0x01c00036 maskFormat=0x00000026 glyphset=0x01c00037 xSrc=0 ySrc=0 glyphcmds={deltax=5 deltay=554 glyphs=0x5a,0x4b,0x48,0x51; }; 000:<:c480: 40: RENDERRequest(154): RenderCompositeGlyphs8 op=Over(0x03) src=0x01c0000f dst=0x01c00036 maskFormat=0x00000026 glyphset=0x01c00037 xSrc=0 ySrc=0 glyphcmds={deltax=38 deltay=554 glyphs=0x4c,0x57; }; 000:<:c481: 44: RENDERRequest(154): RenderCompositeGlyphs8 op=Over(0x03) src=0x01c0000f dst=0x01c00036 maskFormat=0x00000026 glyphset=0x01c00037 xSrc=0 ySrc=0 glyphcmds={deltax=47 deltay=554 glyphs=0x5a,0x44,0x51,0x57,0x56; }; 000:<:c482: 40: RENDERRequest(154): RenderCompositeGlyphs8 op=Over(0x03) src=0x01c0000f dst=0x01c00036 maskFormat=0x00000026 glyphset=0x01c00037 xSrc=0 ySrc=0 glyphcmds={deltax=82 deltay=554 glyphs=0x57,0x52; }; 000:<:c483: 40: RENDERRequest(154): RenderCompositeGlyphs8 op=Over(0x03) src=0x01c0000f dst=0x01c00036 maskFormat=0x00000026 glyphset=0x01c00037 xSrc=0 ySrc=0 glyphcmds={deltax=95 deltay=554 glyphs=0x46,0x52,0x53,0x5c; }; 000:<:c484: 40: RENDERRequest(154): RenderCompositeGlyphs8 op=Over(0x03) src=0x01c0000f dst=0x01c00036 maskFormat=0x00000026 glyphset=0x01c00037 xSrc=0 ySrc=0 glyphcmds={deltax=124 deltay=554 glyphs=0x57,0x4b,0x48; }; 000:<:c485: 44: RENDERRequest(154): RenderCompositeGlyphs8 op=Over(0x03) src=0x01c0000f dst=0x01c00036 maskFormat=0x00000026 glyphset=0x01c00063 xSrc=0 ySrc=0 glyphcmds={deltax=144 deltay=554 glyphs=0x5b,0x50,0x4f,0x1d,0x4f,0x44,0 x51,0x4a; }; 000:<:c486: 48: RENDERRequest(154): RenderCompositeGlyphs8 op=Over(0x03) src=0x01c0000f dst=0x01c00036 maskFormat=0x00000026 glyphset=0x01c00037 xSrc=0 ySrc=0 glyphcmds={deltax=203 deltay=554 glyphs=0x44,0x57,0x57,0x55,0x4c,0x45,0 x58,0x57,0x48,0x11; };

3 8

two minor bugs
by matthias.franz＠ujf-grenoble.fr Oct. 12, 2007

Oct. 12, 2007

Hi, here are two minor bugs: - If a page is too long to fit inside the dillo window, you get a scrollbar at the right border. Sometimes this scrollbar gets lost when you enlarge the window (by dragging the lower right corner or by clicking on the "full screen" button) although the page still doesn't fit. This seems to depend on the page and doesn't happen very often. For an example, try http://www-fourier.ujf-grenoble.fr/~franz/ . - When opening a new page or when moving through the history list, dillo remembers the screen position although positions on different pages should not be related. PS: I have to specify the cvs repository as given on the dillo web page, namely "-d:pserver:anonymous@auriga.wearlab.de:/sfhome/cvs/dillo". The empty password does not work for jcid(a)auriga.wearlab.de. (This is probably not surprising.) Cheers, -- Matthias Franz

2 1

fix for links within lists
by jcid＠dillo.org Oct. 12, 2007

Oct. 12, 2007

Hi, On Mon, Oct 08, 2007 at 03:18:10PM +0000, place wrote: > BTW, are you still opposed to the idea of click-to-load-images? > I'm on dialup, so one of the first things I had to do was port > my old hacks from my gtk version. I am/was not opposed. I thought a good solution was to have a small tools icon (near bug meter) where you could toggle images on/off, my_colors on/off, wide_rendering on/off etc. Now, being in no-images mode and being able to request a single one instead of all at once looks like a good idea. Of course you'd also have the option of turning images on, and have all requested for that page. As most of the images don't specify a size, a place holder must be provided (as the broken image link in other browser). From there, a right click menu could offer to download that image only. > Also, do you have any thoughts on the proper solution for pages using > character sets that aren't utf-8 or a subset thereof? I made something > that reads the charset from Content-Type in the header or meta tags > and then, in Html->write, runs the buffers through iconv. (Pages are > mostly readable, but I think I'm either losing partial characters at > buffer boundaries or losing partial tags between Html->write_raw() > calls or something...) Basically that. It's not simple though. For instance an http page may specify the charset in Content-Type, but when saved not give any clue in its meta tags. Or have only meta but not Content-Type as served, or give no clue at all, etc. The main idea is to keep the page as is in the cache (so it can be saved verbatim) and to pass it trough a filter to make the conversion to utf-8 inside Dillo. If the iconv backpack adds too much to Dillo's size, the task can be delegated to a dpi, and a small subset with the main conversions be kept inside Dillo. -- Cheers Jorge.-

1 0

fix for links within lists
by place Oct. 12, 2007

Oct. 12, 2007

Hello all, I've hacked up my html.cc too much to provide a proper patch, but it's just one line. If you add: Html_connect_signals(html, list_item); to Html_tag_open_li() (after the item_style->unref(); seemed like a nice place), then links inside lists will work.

4 5

Errata and comments
by bogus＠does.not.exist.com Oct. 11, 2007

Oct. 11, 2007

Hi, Errata: -./autogen.sh -make +./autogen.sh +./configure +make Comments: In the old laptop (Pentium I, 233Mhz) scrolling is much better with the patch. This is, without patch, the CPU is hogged by pressing the scroll arrow and holding it down. It even keeps scrolling after releasing the button (keyb buffer). The patched version uses near 80% of the CPU (not 100%) and stops when releasing. In the same laptop, the over-link-quick-switch-from-arrow-to-hand (i.e. Get a directory listing and move the mouse across the links steadily) rises CPU usage to near 60%. Thre's a bug somewhere... -- Cheers Jorge.-

1 0

character entity references produce garbage
by Matthias Franz Oct. 9, 2007

Oct. 9, 2007

Hi, I've observed that in dillo-fltk character entity references produce garbage after the word they are contained in. Here is an example: <html> <title>character entity references produce garbage</title> no artefact <br> one ärtefact <br> two ärtéfacts <br> three ärtéfâcts </html> Since I'm currently very busy with other (less interesting, but more important) things, so I can only contribute to Dillo by reporting bugs and testing solutions right now. I hope that this will change sometime so that I can again write patches myself. Cheers, -- Matthias Franz

2 2

another patch: allows clicking on images in links
by place Oct. 8, 2007

Oct. 8, 2007

Hello again, First, on the dw side: --- image.hh 2007-10-08 17:30:00.000000000 +0000 +++ image.hh.new 2007-10-08 17:36:38.000000000 +0000 @@ -91,6 +91,7 @@ char *altText; core::Imgbuf *buffer; int altTextWidth; + bool clicking; protected: void sizeRequestImpl (core::Requisition *requisition); @@ -98,8 +99,9 @@ void draw (core::View *view, core::Rectangle *area); - //bool buttonPressImpl (core::EventButton *event); - //bool buttonReleaseImpl (core::EventButton *event); + bool buttonPressImpl (core::EventButton *event); + bool buttonReleaseImpl (core::EventButton *event); + void leaveNotifyImpl (core::EventCrossing *event); //bool motionNotifyImpl (core::EventMotion *event); //core::Iterator *iterator (Content::Type mask, bool atEnd); --- image.cc 2007-10-08 16:50:47.000000000 +0000 +++ image.cc.new 2007-10-08 17:36:55.000000000 +0000 @@ -64,6 +64,7 @@ this->altText = altText ? strdup (altText) : NULL; altTextWidth = -1; // not yet calculated buffer = NULL; + clicking = false; } Image::~Image() @@ -125,6 +126,30 @@ } } +void Image::leaveNotifyImpl (core::EventCrossing *event) +{ + clicking = false; +} + +bool Image::buttonPressImpl (core::EventButton *event) +{ + clicking = true; + return true; +} + +bool Image::buttonReleaseImpl (core::EventButton *event) +{ + int idx; + if (clicking) { + clicking = false; + idx = getStyle()->x_link; + if (idx != -1) { + emitLinkClick (idx, -1, -1, event); + } + } + return true; +} + void Image::draw (core::View *view, core::Rectangle *area) { int dx, dy; And then on the dillo side: --- html.cc 2007-10-08 18:01:47.000000000 +0000 +++ html.cc.new 2007-10-08 18:04:00.000000000 +0000 @@ -2423,8 +2423,9 @@ /* Add a new image widget to this page */ Image = a_Image_new(0, 0, alt_ptr, S_TOP(html)->current_bg_color); if (add) { - Html_add_widget(html, (Widget*)Image->dw, - width_ptr, height_ptr, style_attrs); + Widget *w = (Widget*)Image->dw; + Html_add_widget(html, w, width_ptr, height_ptr, style_attrs); + Html_connect_signals(html, w); } dFree(width_ptr);

1 0

Re: I want to help the Dillo project...
by Jorge Arellano Cid Oct. 8, 2007

Oct. 8, 2007

Hi, On Mon, Oct 08, 2007 at 12:07:21AM +0000, Joseph Sleiman wrote: > Hello, > > I'm not a great programmer, but I'm looking to help the Dillo project. It's > a nifty browser, and I'm hoping that by working on it it'll help me learn > more about programming languages / toolkits like C and FLTK. I'd also > rather not see the project die like this. Excellent! Thank you for commiting to help. We need as much as we can get. First you have to subscribe to dillo-dev (our mailing list). Then, I see a great way for you to help. Recently in the updates I'm going to make public as cvs ASAP, in the /doc directory inside dillo's tree I wrote: <quote> This documents need a review. They were current with dillo1 and now, with dillo2, most of them are obsolete, specially Dw*txt, but Dw2 is fully documented in html using doxygen. The other documents will be reviewed when I have some time. They will give you an overview of what's going on but take them with a pinch of salt. Of course I'd like to have these as doxygen files too! If somebody wants to make this convertion, please let me know to assign higher priority to updating these docs. </quote> So I'd be very happy if you start here. Making the framework for doxygen-type of documentation inside dillo. This will also let you get started knowing the internals of the code, and from then to patching. This is a very important task as it helps all the developers. Sebastian made excellent doxygen documentation in the Dw2 tree. So you can borrow some ideas from there. We need this quick as it can only help all of us. As you advance I can work with you providing more comments in the code and text when needed. For instance Dlib seems a good place to start. Please let me know if you take this duty. Welcome aboard! -- Cheers Jorge.-

1 0

Re: [Dillo-dev] Dillo FLTK2 alpha release for developers
by Jan Stary Oct. 7, 2007

Oct. 7, 2007

Hi Jorge, firstly, thanks for the release! I am trying to compile it here on my FreeBSD 6.2-RELEASE-p8. > ----- > FLTK2 > ----- Installed without problems into /usr/local > ---------- > dw-0.0.43j > ---------- > > tar jxvf dw-testbed-0.0.43j.tar.bz2 > cd dw-testbed-0.0.43j > ./configure > make Fails (see typescript at bottom). The ./configure script finds FLTK, but then, the test subdirectory's Makefile doesn't use no -I option and the FLTK includes are not found. Short summary: $ ./configure [...] checking FLTK2... yes [...] configure: creating ./config.status config.status: creating Makefile config.status: creating lout/Makefile config.status: creating dw/Makefile config.status: creating test/Makefile config.status: creating doc/Makefile config.status: executing depfiles commands $ gmake Making all in lout [...] Making all in dw [...] Making all in test gmake[1]: Entering directory `/home/hans/src/dw-testbed-0.0.43j/test' g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT dw_anchors_test.o -MD -MP -MF .deps/dw_anchors_test.Tpo -c -o dw_anchors_test.o dw_anchors_test.cc dw_anchors_test.cc:24:25: fltk/Window.h: No such file or directory [...] dw_anchors_test.cc:151: error: `run' is not a member of `dw::fltk' gmake[1]: *** [dw_anchors_test.o] Error 1 gmake[1]: Leaving directory `/home/hans/src/dw-testbed-0.0.43j/test' gmake: *** [all-recursive] Error 1 Jan hans@freebsd:dw-testbed-0.0.43j$ pwd /home/hans/src/dw-testbed-0.0.43j hans@freebsd:dw-testbed-0.0.43j$ ./configure checking build system type... i386-unknown-freebsd6.2 checking host system type... i386-unknown-freebsd6.2 checking target system type... i386-unknown-freebsd6.2 checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... ./install-sh -c -d checking for gawk... no checking for mawk... no checking for nawk... nawk checking whether make sets $(MAKE)... yes checking for g++... g++ checking for C++ compiler default output file name... a.out checking whether the C++ compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for style of include used by make... GNU checking dependency style of g++... gcc3 checking for gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking for ranlib... ranlib checking how to run the C preprocessor... gcc -E checking FLTK2... yes checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking for unistd.h... (cached) yes checking sys/uio.h usability... yes checking sys/uio.h presence... yes checking for sys/uio.h... yes configure: creating ./config.status config.status: creating Makefile config.status: creating lout/Makefile config.status: creating dw/Makefile config.status: creating test/Makefile config.status: creating doc/Makefile config.status: executing depfiles commands hans@freebsd:dw-testbed-0.0.43j$ gmake Making all in lout gmake[1]: Entering directory `/home/hans/src/dw-testbed-0.0.43j/lout' g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT container.o -MD -MP -MF .deps/container.Tpo -c -o container.o container.cc mv -f .deps/container.Tpo .deps/container.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT identity.o -MD -MP -MF .deps/identity.Tpo -c -o identity.o identity.cc mv -f .deps/identity.Tpo .deps/identity.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT misc.o -MD -MP -MF .deps/misc.Tpo -c -o misc.o misc.cc mv -f .deps/misc.Tpo .deps/misc.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT object.o -MD -MP -MF .deps/object.Tpo -c -o object.o object.cc mv -f .deps/object.Tpo .deps/object.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT signal.o -MD -MP -MF .deps/signal.Tpo -c -o signal.o signal.cc mv -f .deps/signal.Tpo .deps/signal.Po rm -f liblout.a ar cru liblout.a container.o identity.o misc.o object.o signal.o ranlib liblout.a gmake[1]: Leaving directory `/home/hans/src/dw-testbed-0.0.43j/lout' Making all in dw gmake[1]: Entering directory `/home/hans/src/dw-testbed-0.0.43j/dw' g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT findtext.o -MD -MP -MF .deps/findtext.Tpo -c -o findtext.o findtext.cc mv -f .deps/findtext.Tpo .deps/findtext.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT iterator.o -MD -MP -MF .deps/iterator.Tpo -c -o iterator.o iterator.cc mv -f .deps/iterator.Tpo .deps/iterator.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT layout.o -MD -MP -MF .deps/layout.Tpo -c -o layout.o layout.cc mv -f .deps/layout.Tpo .deps/layout.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT selection.o -MD -MP -MF .deps/selection.Tpo -c -o selection.o selection.cc mv -f .deps/selection.Tpo .deps/selection.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT style.o -MD -MP -MF .deps/style.Tpo -c -o style.o style.cc mv -f .deps/style.Tpo .deps/style.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT types.o -MD -MP -MF .deps/types.Tpo -c -o types.o types.cc mv -f .deps/types.Tpo .deps/types.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT ui.o -MD -MP -MF .deps/ui.Tpo -c -o ui.o ui.cc mv -f .deps/ui.Tpo .deps/ui.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT widget.o -MD -MP -MF .deps/widget.Tpo -c -o widget.o widget.cc mv -f .deps/widget.Tpo .deps/widget.Po rm -f libDw-core.a ar cru libDw-core.a findtext.o iterator.o layout.o selection.o style.o types.o ui.o widget.o ranlib libDw-core.a g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include -Wno-non-virtual-dtor -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT libDw_fltk_a-fltkcomplexbutton.o -MD -MP -MF .deps/libDw_fltk_a-fltkcomplexbutton.Tpo -c -o libDw_fltk_a-fltkcomplexbutton.o `test -f 'fltkcomplexbutton.cc' || echo './'`fltkcomplexbutton.cc mv -f .deps/libDw_fltk_a-fltkcomplexbutton.Tpo .deps/libDw_fltk_a-fltkcomplexbutton.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include -Wno-non-virtual-dtor -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT libDw_fltk_a-fltkflatview.o -MD -MP -MF .deps/libDw_fltk_a-fltkflatview.Tpo -c -o libDw_fltk_a-fltkflatview.o `test -f 'fltkflatview.cc' || echo './'`fltkflatview.cc mv -f .deps/libDw_fltk_a-fltkflatview.Tpo .deps/libDw_fltk_a-fltkflatview.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include -Wno-non-virtual-dtor -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT libDw_fltk_a-fltkimgbuf.o -MD -MP -MF .deps/libDw_fltk_a-fltkimgbuf.Tpo -c -o libDw_fltk_a-fltkimgbuf.o `test -f 'fltkimgbuf.cc' || echo './'`fltkimgbuf.cc mv -f .deps/libDw_fltk_a-fltkimgbuf.Tpo .deps/libDw_fltk_a-fltkimgbuf.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include -Wno-non-virtual-dtor -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT libDw_fltk_a-fltkmisc.o -MD -MP -MF .deps/libDw_fltk_a-fltkmisc.Tpo -c -o libDw_fltk_a-fltkmisc.o `test -f 'fltkmisc.cc' || echo './'`fltkmisc.cc mv -f .deps/libDw_fltk_a-fltkmisc.Tpo .deps/libDw_fltk_a-fltkmisc.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include -Wno-non-virtual-dtor -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT libDw_fltk_a-fltkplatform.o -MD -MP -MF .deps/libDw_fltk_a-fltkplatform.Tpo -c -o libDw_fltk_a-fltkplatform.o `test -f 'fltkplatform.cc' || echo './'`fltkplatform.cc mv -f .deps/libDw_fltk_a-fltkplatform.Tpo .deps/libDw_fltk_a-fltkplatform.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include -Wno-non-virtual-dtor -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT libDw_fltk_a-fltkpreview.o -MD -MP -MF .deps/libDw_fltk_a-fltkpreview.Tpo -c -o libDw_fltk_a-fltkpreview.o `test -f 'fltkpreview.cc' || echo './'`fltkpreview.cc mv -f .deps/libDw_fltk_a-fltkpreview.Tpo .deps/libDw_fltk_a-fltkpreview.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include -Wno-non-virtual-dtor -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT libDw_fltk_a-fltkui.o -MD -MP -MF .deps/libDw_fltk_a-fltkui.Tpo -c -o libDw_fltk_a-fltkui.o `test -f 'fltkui.cc' || echo './'`fltkui.cc mv -f .deps/libDw_fltk_a-fltkui.Tpo .deps/libDw_fltk_a-fltkui.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include -Wno-non-virtual-dtor -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT libDw_fltk_a-fltkviewbase.o -MD -MP -MF .deps/libDw_fltk_a-fltkviewbase.Tpo -c -o libDw_fltk_a-fltkviewbase.o `test -f 'fltkviewbase.cc' || echo './'`fltkviewbase.cc mv -f .deps/libDw_fltk_a-fltkviewbase.Tpo .deps/libDw_fltk_a-fltkviewbase.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include -Wno-non-virtual-dtor -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT libDw_fltk_a-fltkviewport.o -MD -MP -MF .deps/libDw_fltk_a-fltkviewport.Tpo -c -o libDw_fltk_a-fltkviewport.o `test -f 'fltkviewport.cc' || echo './'`fltkviewport.cc mv -f .deps/libDw_fltk_a-fltkviewport.Tpo .deps/libDw_fltk_a-fltkviewport.Po rm -f libDw-fltk.a ar cru libDw-fltk.a libDw_fltk_a-fltkcomplexbutton.o libDw_fltk_a-fltkflatview.o libDw_fltk_a-fltkimgbuf.o libDw_fltk_a-fltkmisc.o libDw_fltk_a-fltkplatform.o libDw_fltk_a-fltkpreview.o libDw_fltk_a-fltkui.o libDw_fltk_a-fltkviewbase.o libDw_fltk_a-fltkviewport.o ranlib libDw-fltk.a g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT alignedtextblock.o -MD -MP -MF .deps/alignedtextblock.Tpo -c -o alignedtextblock.o alignedtextblock.cc mv -f .deps/alignedtextblock.Tpo .deps/alignedtextblock.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT bullet.o -MD -MP -MF .deps/bullet.Tpo -c -o bullet.o bullet.cc mv -f .deps/bullet.Tpo .deps/bullet.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT image.o -MD -MP -MF .deps/image.Tpo -c -o image.o image.cc mv -f .deps/image.Tpo .deps/image.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT listitem.o -MD -MP -MF .deps/listitem.Tpo -c -o listitem.o listitem.cc mv -f .deps/listitem.Tpo .deps/listitem.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT ruler.o -MD -MP -MF .deps/ruler.Tpo -c -o ruler.o ruler.cc mv -f .deps/ruler.Tpo .deps/ruler.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT table.o -MD -MP -MF .deps/table.Tpo -c -o table.o table.cc mv -f .deps/table.Tpo .deps/table.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT tablecell.o -MD -MP -MF .deps/tablecell.Tpo -c -o tablecell.o tablecell.cc mv -f .deps/tablecell.Tpo .deps/tablecell.Po g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT textblock.o -MD -MP -MF .deps/textblock.Tpo -c -o textblock.o textblock.cc mv -f .deps/textblock.Tpo .deps/textblock.Po rm -f libDw-widgets.a ar cru libDw-widgets.a alignedtextblock.o bullet.o image.o listitem.o ruler.o table.o tablecell.o textblock.o ranlib libDw-widgets.a gmake[1]: Leaving directory `/home/hans/src/dw-testbed-0.0.43j/dw' Making all in test gmake[1]: Entering directory `/home/hans/src/dw-testbed-0.0.43j/test' g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -W -Wno-unused-parameter -MT dw_anchors_test.o -MD -MP -MF .deps/dw_anchors_test.Tpo -c -o dw_anchors_test.o dw_anchors_test.cc dw_anchors_test.cc:24:25: fltk/Window.h: No such file or directory dw_anchors_test.cc:25:22: fltk/run.h: No such file or directory In file included from dw_anchors_test.cc:28: ../dw/fltkcore.hh:16:25: fltk/Widget.h: No such file or directory In file included from ../dw/fltkcore.hh:19, from dw_anchors_test.cc:28: ../dw/fltkimgbuf.hh:24: error: ISO C++ forbids declaration of `uchar' with no type ../dw/fltkimgbuf.hh:24: error: expected `;' before '*' token ../dw/fltkimgbuf.hh:57: error: `::fltk' has not been declared ../dw/fltkimgbuf.hh:57: error: `Widget' has not been declared ../dw/fltkimgbuf.hh:58: error: ISO C++ forbids declaration of `target' with no type In file included from ../dw/fltkcore.hh:20, from dw_anchors_test.cc:28: ../dw/fltkplatform.hh:8:23: fltk/Font.h: No such file or directory In file included from ../dw/fltkcore.hh:20, from dw_anchors_test.cc:28: ../dw/fltkplatform.hh:20: error: `::fltk' has not been declared ../dw/fltkplatform.hh:44: error: `::fltk' has not been declared ../dw/fltkplatform.hh:44: error: `Widget' has not been declared ../dw/fltkplatform.hh:45: error: ISO C++ forbids declaration of `widget' with no type ../dw/fltkplatform.hh:46: error: `::fltk' has not been declared ../dw/fltkplatform.hh:46: error: `Widget' has not been declared ../dw/fltkplatform.hh:47: error: ISO C++ forbids declaration of `widget' with no type ../dw/fltkplatform.hh:48: error: `::fltk' has not been declared ../dw/fltkplatform.hh:48: error: `Widget' has not been declared ../dw/fltkplatform.hh:48: error: ISO C++ forbids declaration of `widget' with no type In file included from ../dw/fltkcore.hh:21, from dw_anchors_test.cc:28: ../dw/fltkui.hh:8:25: fltk/Button.h: No such file or directory ../dw/fltkui.hh:9:23: fltk/Menu.h: No such file or directory In file included from ../dw/fltkcore.hh:21, from dw_anchors_test.cc:28: ../dw/fltkui.hh:179: error: `::fltk' has not been declared ../dw/fltkui.hh:179: error: ISO C++ forbids declaration of `Widget' with no type ../dw/fltkui.hh:179: error: expected `;' before '*' token ../dw/fltkui.hh:190: error: `::fltk' has not been declared ../dw/fltkui.hh:190: error: ISO C++ forbids declaration of `Widget' with no type ../dw/fltkui.hh:190: error: `Widget' declared as a `virtual' field ../dw/fltkui.hh:190: error: expected `;' before '*' token ../dw/fltkui.hh:192: error: `::fltk' has not been declared ../dw/fltkui.hh:192: error: `Widget' has not been declared ../dw/fltkui.hh:192: error: ISO C++ forbids declaration of `widget' with no type ../dw/fltkui.hh:230: error: `::fltk' has not been declared ../dw/fltkui.hh:230: error: `Widget' has not been declared ../dw/fltkui.hh:230: error: ISO C++ forbids declaration of `widget' with no type ../dw/fltkui.hh:233: error: `::fltk' has not been declared ../dw/fltkui.hh:233: error: ISO C++ forbids declaration of `Widget' with no type ../dw/fltkui.hh:233: error: expected `;' before '*' token ../dw/fltkui.hh:252: error: `::fltk' has not been declared ../dw/fltkui.hh:252: error: `Widget' has not been declared ../dw/fltkui.hh:252: error: ISO C++ forbids declaration of `widget' with no type ../dw/fltkui.hh:276: error: `::fltk' has not been declared ../dw/fltkui.hh:276: error: ISO C++ forbids declaration of `Widget' with no type ../dw/fltkui.hh:276: error: expected `;' before '*' token ../dw/fltkui.hh:298: error: `::fltk' has not been declared ../dw/fltkui.hh:298: error: `Widget' has not been declared ../dw/fltkui.hh:298: error: ISO C++ forbids declaration of `widget' with no type ../dw/fltkui.hh:301: error: `::fltk' has not been declared ../dw/fltkui.hh:301: error: ISO C++ forbids declaration of `Widget' with no type ../dw/fltkui.hh:301: error: expected `;' before '*' token ../dw/fltkui.hh:323: error: `::fltk' has not been declared ../dw/fltkui.hh:323: error: ISO C++ forbids declaration of `Button' with no type ../dw/fltkui.hh:323: error: `Button' declared as a `virtual' field ../dw/fltkui.hh:323: error: expected `;' before '*' token ../dw/fltkui.hh:324: error: `::fltk' has not been declared ../dw/fltkui.hh:324: error: ISO C++ forbids declaration of `Widget' with no type ../dw/fltkui.hh:324: error: expected `;' before '*' token ../dw/fltkui.hh:342: error: `::fltk' has not been declared ../dw/fltkui.hh:342: error: ISO C++ forbids declaration of `Button' with no type ../dw/fltkui.hh:342: error: expected `;' before '*' token ../dw/fltkui.hh:400: error: `::fltk' has not been declared ../dw/fltkui.hh:400: error: `Widget' has not been declared ../dw/fltkui.hh:400: error: ISO C++ forbids declaration of `widget' with no type ../dw/fltkui.hh:404: error: `::fltk' has not been declared ../dw/fltkui.hh:404: error: ISO C++ forbids declaration of `Button' with no type ../dw/fltkui.hh:404: error: expected `;' before '*' token ../dw/fltkui.hh:436: error: `::fltk' has not been declared ../dw/fltkui.hh:436: error: ISO C++ forbids declaration of `Menu' with no type ../dw/fltkui.hh:436: error: expected `;' before '*' token ../dw/fltkui.hh:437: error: `::fltk' has not been declared ../dw/fltkui.hh:437: error: `Menu' was not declared in this scope ../dw/fltkui.hh:437: error: template argument 1 is invalid ../dw/fltkui.hh:437: error: template argument 1 is invalid ../dw/fltkui.hh:437: error: ISO C++ forbids declaration of `stack' with no type ../dw/fltkui.hh:439: error: `::fltk' has not been declared ../dw/fltkui.hh:439: error: expected `)' before '*' token ../dw/fltkui.hh:447: error: `::fltk' has not been declared ../dw/fltkui.hh:447: error: ISO C++ forbids declaration of `Widget' with no type ../dw/fltkui.hh:447: error: expected `;' before '*' token ../dw/fltkui.hh:448: error: `::fltk' has not been declared ../dw/fltkui.hh:448: error: ISO C++ forbids declaration of `Menu' with no type ../dw/fltkui.hh:448: error: `Menu' declared as a `virtual' field ../dw/fltkui.hh:448: error: expected `;' before '*' token ../dw/fltkui.hh:470: error: `::fltk' has not been declared ../dw/fltkui.hh:470: error: ISO C++ forbids declaration of `Menu' with no type ../dw/fltkui.hh:470: error: expected `;' before '*' token ../dw/fltkui.hh:484: error: `::fltk' has not been declared ../dw/fltkui.hh:484: error: ISO C++ forbids declaration of `Menu' with no type ../dw/fltkui.hh:484: error: expected `;' before '*' token In file included from dw_anchors_test.cc:29: ../dw/fltkviewport.hh:4:24: fltk/Group.h: No such file or directory ../dw/fltkviewport.hh:5:28: fltk/Scrollbar.h: No such file or directory In file included from ../dw/fltkviewport.hh:9, from dw_anchors_test.cc:29: ../dw/fltkviewbase.hh:13: error: `::fltk' has not been declared ../dw/fltkviewbase.hh:14: error: expected class-name before '{' token ../dw/fltkviewbase.hh:69: error: `::fltk' has not been declared ../dw/fltkviewbase.hh:69: error: `Widget' was not declared in this scope ../dw/fltkviewbase.hh:69: error: template argument 1 is invalid ../dw/fltkviewbase.hh:70: error: template argument 1 is invalid ../dw/fltkviewbase.hh:70: error: ISO C++ forbids declaration of `canvasWidgets' with no type ../dw/fltkviewbase.hh:85: error: `::fltk' has not been declared ../dw/fltkviewbase.hh:85: error: `Widget' has not been declared ../dw/fltkviewbase.hh:85: error: ISO C++ forbids declaration of `widget' with no type ../dw/fltkviewbase.hh:86: error: `::fltk' has not been declared ../dw/fltkviewbase.hh:86: error: `Widget' has not been declared ../dw/fltkviewbase.hh:87: error: ISO C++ forbids declaration of `widget' with no type ../dw/fltkviewbase.hh:88: error: `::fltk' has not been declared ../dw/fltkviewbase.hh:88: error: `Widget' has not been declared ../dw/fltkviewbase.hh:88: error: ISO C++ forbids declaration of `widget' with no type In file included from dw_anchors_test.cc:29: ../dw/fltkviewport.hh:24: error: `::fltk' has not been declared ../dw/fltkviewport.hh:24: error: ISO C++ forbids declaration of `Scrollbar' with no type ../dw/fltkviewport.hh:24: error: expected `;' before '*' token ../dw/fltkviewport.hh:27: error: `::fltk' has not been declared ../dw/fltkviewport.hh:27: error: `Widget' was not declared in this scope ../dw/fltkviewport.hh:27: error: template argument 1 is invalid ../dw/fltkviewport.hh:27: error: template argument 1 is invalid ../dw/fltkviewport.hh:27: error: ISO C++ forbids declaration of `gadgets' with no type ../dw/fltkviewport.hh:34: error: `Widget' has not been declared ../dw/fltkviewport.hh:34: error: ISO C++ forbids declaration of `hscrollbar' with no type ../dw/fltkviewport.hh:35: error: `Widget' has not been declared ../dw/fltkviewport.hh:35: error: ISO C++ forbids declaration of `vscrollbar' with no type ../dw/fltkviewport.hh:64: error: `::fltk' has not been declared ../dw/fltkviewport.hh:64: error: `Widget' has not been declared ../dw/fltkviewport.hh:64: error: ISO C++ forbids declaration of `gadget' with no type dw_anchors_test.cc:40: error: expected initializer before '*' token dw_anchors_test.cc:51: error: variable or field `anchorCallback' declared void dw_anchors_test.cc:51: error: `Widget' is not a member of `dw::fltk' dw_anchors_test.cc:51: error: `widget' was not declared in this scope dw_anchors_test.cc:51: error: expected primary-expression before "void" dw_anchors_test.cc:52: error: initializer expression list treated as compound expression dw_anchors_test.cc:52: error: expected `,' or `;' before '{' token dw_anchors_test.cc: In function `void textTimeout(void*)': dw_anchors_test.cc:91: error: `repeat_timeout' is not a member of `dw::fltk' dw_anchors_test.cc: In function `int main(int, char**)': dw_anchors_test.cc:102: error: `window' was not declared in this scope dw_anchors_test.cc:102: error: `dw::fltk::Window' has not been declared dw_anchors_test.cc:113: error: `Button' is not a member of `dw::fltk' dw_anchors_test.cc:113: error: `button' was not declared in this scope dw_anchors_test.cc:114: error: `dw::fltk::Button' has not been declared dw_anchors_test.cc:116: error: `WHEN_RELEASE' is not a member of `dw::fltk' dw_anchors_test.cc:146: error: `add_timeout' is not a member of `dw::fltk' dw_anchors_test.cc:151: error: `run' is not a member of `dw::fltk' gmake[1]: *** [dw_anchors_test.o] Error 1 gmake[1]: Leaving directory `/home/hans/src/dw-testbed-0.0.43j/test' gmake: *** [all-recursive] Error 1

2 1

[Johannes.Hofmann@gmx.de: [Johannes.Hofmann@gmx.de: Re: [Dillo-dev] Dillo FLTK2 alpha release for developers]]
by Jorge Arellano Cid Oct. 3, 2007

Oct. 3, 2007

Hi, -- Cheers Jorge.-

3 3

https and OpenBSD
by None Oct. 2, 2007

Oct. 2, 2007

Hi, > Dear Jorge & dillo fans, > > I can confirm this will run and build on OpenBSD-4.1 with minor > modifications: > > * remove the GL & glut targets from the fltk Makefile if you don't > need it Did you just "./configure --disable-gl"? Or: - DIRS = src $(LOCALIMAGES) images OpenGL fluid glut test + DIRS = src $(LOCALIMAGES) images fluid test else? > * implement a strndup() function in dw/selection.cc in the testbed > as OpenBSD doesn't have that in string.h Yes. > > I still have one question: > > I wanted to try out https (yes I know the README says it doesn't > work). And of course it did not work: It works bery basically. If you can see "https://www.rapidssl.com/test/rapidssl.htm", that's it. > > prefs: Using internal defaults. > dillo_dns_init: Here we go! (threaded) > Enabling cookies as from cookiesrc... > Nav_open_url: Url=>https://www.ccc.de< > [dpid]: dpi.c:70: a_Dpi_rd_dpi_socket_dir: fopen > Dpi_blocking_start_dpid: try 1 > [dpid]: No such file or directory > [dpid]: - /home/ckeen/.dillo/dpi_socket_dir > [dpid]: init_sockdir: The dpi_socket_dir file (null) does not exist > dpid started > a_Dpiapi_dialog: > dpip_tag: <cmd='dialog' msg='The remote certificate cannot be > verified (code 20)' alt1='Continue' alt2='Cancel' '> > mouse button 1 was pressed > a_UIcmd_stop() > > > Is the backward channel form dpis supposed to work? Yes. > If yes I will > look into it. If there is too much missing atm, I would be gladful > for a hint on where to start. The point here is that https is a "filter" dpi (i.e. one instance per request is spawned). The solution is to implement it as a "server" (e.g. like the file server). That way, when a https request has many embedded resources (i.e. many https requests to the same site), the server can make only one query and not flood the backward channel for dpis. With regard to the actual certificate-validating code, AFAIR much of it is already there, it needs some testing and enabling. It would be great if you can work on it. > Thank you very _very_ much for this nice programme and for bearing > with us! Thank you for offering your help. -- Cheers Jorge.-

1 0

new unfinished code
by Diego . Oct. 2, 2007

Oct. 2, 2007

This start to seem like spam. Sorry. I have upload to my page unfinished code for a prefs dpi and my first screenshot :). The patch do not change dillo code, but need dillo code to compile. (dpi lib). The page is: http://personales.ya.com/darkspirit/ If i get time i will try to post some docs about mime code for dillo(unfinished, unpublished, break, etc) and questions about internals of dillo. Diego.

2 2

Re: dillo
by Jorge Arellano Cid Sept. 17, 2007

Sept. 17, 2007

Hi, On Sat, Sep 15, 2007 at 05:36:25AM -0700, j murphy wrote: > Jorge: > I hope that you and your collaborators are > well, and that your plans for releasing the new dillo > are still on track. Yes, still on track. > Despite the work being done on > other lightweight browsers like hv3 and Twibright > Labs' Links, I still prefer to use dillo, :-) > and I need > it for use on some of my older, slower machines that > have less memory, and are too slow with Firefox or > Opera. I'm writing to share with you a few problems > that I have noticed with dillo 0.8.6: I'll answer them below, but please just notice that the main problem we face now is lack of time from the main developers; we know about bugs, and have development plans, but we have no time or funds to quit our jobs and devote 100% to Dillo. > > 1)I often use a browser with tor ( https://tor.eff.org > ) and privoxy ( http://www.privoxy.org )for secure > browsing, and I was using dillo in this way, until I > noticed (through some of the useful diagnostics at > https://torcheck.xenobite.eu ) that dillo doesn't > route https traffic through my web proxy correctly -- > instead it seems to establish a direct connection, > bypassing the proxy, despite the http_proxy setting in > my dillorc file. Normal http traffic seems to be > handled correctly. Does the user need to set a > separate proxy for https traffic? Or does the proxy > handling in dillo have a bug? Dillo's https support is basic. It uses wget for this. You can set a proxy for wget and it should work. > 2)Also, I've had some trouble with dillo's > https.filter.dpi, which often sends an error message > stating that it can't verify a certificate repeatedly, > and sometimes launches multiple instances of itself > when attempting to connect to the same website > securely. This can occasionally lead to crashes in > which https.filter.dpi.core is dumped, and > occasionally brings down the browser as well. I > realize that this information is somewhat vague, but > if you'd like me to send a coredump next time it > occurs, I'll do so. Sad fact: it's a known bug. No need to send the core. The problem is that currently there's no cache for asking for a certificate, so a page with multiple https resources (e.g. images) asks several times for the same certificate flooding the communication socket. > > 3)The fltk downloader has one irritating glitch: when > attempting to save a file, if the user to change the > directory into which the file will be saved, the file > name is cleared, requiring the user to type it in > again, which wastes a lot of time. Yes! This one has bitten me too. This is the default behaviuor of that FLTK dialog. If I find some time and a simple way to change that, I'll fix it. > > 4)When dillo is closed, many of the dpis that were > spawned during a dillo session remain as zombie > processes, when they ought to be terminated along with > the parent dillo process. I realize that file > downloads may have to be handled carefully, and may > sometimes be required to remain open until completion, > even after the parent dillo is closed, but it seems to > me that no useful purpose is served by having the > other dpis remain after dillo is closed. dpidc stop That command tells them to quit. If they remain, that's a bug. > > 5)With the latest snapshots of fltk2 on my machine, > the downloader doesn't refresh itself properly when > multiple files are being downloaded. For instance, a > user starts one download, and the downloader gui is > spawned with a progress tracking entry in the > downloader gui for that particular download. Then the > user starts another download, but the progress > tracking entry for this second download, and for > subsequent downloads, is not displayed properly: it's > somehow underneath the first entry, and partially > obscured by it, so that control of the download or > tracking of it's progress isn't possible. Yes I noticed this too. This simple problems hopefully will be tackled by an interested developer when the code is released (before the end of September. Cross your fingers.). > I hope that this information will help you to improve > your new version of dillo, if these problems have not > already been addressed. If I can help, please let me > know. (Of course I'm a scientist, and not really a > developer, so don't expect miracles.) Yes, your bug report is concise and self explaining. Thanks for it. I wish I had the resources to work hands on in it now. -- Cheers Jorge.-

1 0

0.6% of people uses Dillo (poll said)
by Diego . Sept. 2, 2007

Sept. 2, 2007

DesktopLinux.com has published the results of its anual (desktop)linux poll. The interesting thing is in the 3rd question: Which web browsers do you frequently use on your Linux desktop(s)? http://www.desktoplinux.com/cgi-bin/survey/survey.cgi?view=archive&id=08132… The interesting thing is that a frozen project have enough users to win over 3 fully developed browsers :) (optimistic without cure) Surely a thawn will increase the dillo users. what about a 1%? The results from less to more Does not apply 0.1 % Netscape 0.1 % Safari 0.2 % Other (please tell us) 0.3 % Flock 0.3 % Galeon 0.4 % Dillo 0.6 % Seamonkey 1.7 % Epiphany 2.3 % Mozilla 3.7 % Text-based browser (Lynx, Links, ELinks, etc.) 4.3 % Opera 11.9 % Konqueror 13.7 % Firefox (aka Iceweasel) 59.6 % Are there news about dillo development? Diego.

3 4

more dillo unfinished code
by Diego . Aug. 8, 2007

Aug. 8, 2007

Hello, i have added a patch to manage scripts with DPIs to my (dully and silly) dillo unfinished code page. The patch only allow dillo to send scripts to DPIs and have bugs. Now i am working in mime DPIs. The test file type DPIs part work but the code is too nasty yet. Please give your opinions about the page and the code. Do not worry to ask any doubt. I need some help about the english part to so do not doubt to blame my english and tell my errors. Like this is not the topic of the list send language errors directly to me. The page is http://personales.ya.com/darkspirit/ Diego.

2 1

so is dillo history?
by Globe Trotter July 10, 2007

July 10, 2007

just wondering....doesn't look promising at all! any suggestions for an alternative light-weight browser for linux users? best, trotter ____________________________________________________________________________________ Need a vacation? Get great deals to amazing places on Yahoo! Travel. http://travel.yahoo.com/

3 2

Re: [Dillo-dev] Some News
by Globe Trotter July 6, 2007

July 6, 2007

I agree entirely, but dillo is fast because it is small. I think javascript will have to be tackled if dillo is meant to have a future. unless more and more people use it, no contributions will come. they will definitely not come if fewer and fewer people use it....disappearing for a year and a half was not a great idea....not to mention that it was at the interface between gtk1 and fltk so no one who wanted to could even contribute....hopefully, the new update will be available soon! trotter --- SZERVÁC Attila <sas(a)321.hu> wrote: > > I can use both Dillo & FF on my 9 years old machine, but Dillo is more > faster than any other graphical browser. So, this is the key feature, > not the small size. Size doesn't matter today :-) > > On Fri, Jul 06, 2007 at 08:58:24AM -0700, Globe Trotter wrote: > > > > I do that. But the subset of sites that can handle dillo keeps becoming > smaller > > and smaller. Pretty soon, at this rate, we will be down to just my > website..... > > -- > sas ( satie ) - SZERVÁC Attila - zenész - szoftvergazda \ > elnökhelyettes - Linux-felhasználók Magyarországi Egyesülete - http://lme.hu/ > > ____________________________________________________________________________________ Need a vacation? Get great deals to amazing places on Yahoo! Travel. http://travel.yahoo.com/

1 0

Re: [Dillo-dev] Some News
by Globe Trotter July 6, 2007

July 6, 2007

--- Beartooth <karhunhammas(a)Lserv.com> wrote: > On Fri, 6 Jul 2007, Globe Trotter wrote: > > > Btw, I think we know how you feel about javascript but this has > > to be brought in at some point, since there are increasingly > > more and more sites which can not be viewed without any other > > option. > > Don't be too sure. I keep Dillo named my default browser, > and when I hit a site it can't handle, I either shrug and skip > it, or copy the URL and paste it into some more ponderous > browser. I figure that's the price I pay for Dillo's speed and > security, and well worth it. > > I have no idea how many other users may be doing the > same, but I'll give odds I'm not the only one. In fact, you might > soon find you prefer doing it that way yourself. > I do that. But the subset of sites that can handle dillo keeps becoming smaller and smaller. Pretty soon, at this rate, we will be down to just my website..... I think hv3 (which I did not know about till yesterday) has finally accepted this fact (so they say) and is moving towards incorporating javascript as a priority. Trotter. ____________________________________________________________________________________ Get your own web address. Have a HUGE year through Yahoo! Small Business. http://smallbusiness.yahoo.com/domains/?p=BESTDEAL

1 0

Some News
by Jorge Arellano Cid July 6, 2007

July 6, 2007

Hi there, We've advanced a lot towards a release of Dillo. So expect good news soon! What currently worries us most is the lack of developers. Manpower to help the project. With Sebastian we have little spare time and would appreciate some help. From patches, patch review, bug fixing, web site maintaining, documentation, packaging, etc. -- Cheers Jorge.-

2 1

contacts
by Jorge Arellano Cid May 29, 2007

May 29, 2007

Hi there, Thanks to those of you that made some diligences and sent me email about finding Sebastian. We had a phone talk and will have a chat soon. Once again, thank you. -- Cheers Jorge.-

2 1

more [un]finished code
by Diego . May 28, 2007

May 28, 2007

Hello, I have code a (dull, silly, ...) web page to upload my unfinished dillo code. I tend to start too much things and i finish very few of them. I will upload finished code too. At this moment there are a unfinished tabs dpi and two finished patches that together alow to wrote DilloPlugIns for protocols without touching dillo code. I will try to upload a unfinished preferences DPI and to code patches to allow DPIs to manage mime types and scripting, but i have few time. Please give your opinions on the page and the code. Do not worry to ask any doubt. I need some help about the english part to so do not doubt to blame my english and tell my errors. Like this is not the topic of the list send language errors directly to me. The page is http://personales.ya.com/darkspirit/ Any news from Sebastian? Diego

2 1

LinuxBIOS with X Server Inside
by Alan Carvalho de Assis May 4, 2007

May 4, 2007

Hi guys, as I said before I am developing a minimal graphic distro Linux. Now I extended the idea and place everything inside BIOS. There is the video: http://www.youtube.com/watch?v=nuzRsXKm_NQ I hope Dillo FLTK become free soon, then we can integrate it inside BIOS too. I am developing the tutorial at http://www.linuxabordo.com.br/wiki/index.php?title=LinuxBIOS_Graphical I hope you enjoy! Cheers, Alan

8 18

non released unfinished code (try 2)
by Diego Sáenz April 2, 2007

April 2, 2007

It seems that my previous mail came bad, so i try again: Hello. I agree (in the general discussion) that it is a bad idea to keep closed the dillo FLTK code. (I reserve other opinions for other mail) This mail is only because i have some unfinished code for dillo and want to open/show/give to the rest of the list. One can not demand something without do the same. I have a Dillo PlugIn that add tabs to dillo. The plug in is a GTK 1.2 app and a DPI at the same time. I do not known GTK 1.2 and do not have time to learn it. I was waiting for the FLTK dillo to program a FLTK version, but now i think that it is better to show bad programed unfinished code instead of wait. Try to run it before watch the code (based on a GTK 1.2 example) I hope that some GTK programer can finish it. How do it work: Now dillo can be embedded in other program. This is used by sylpheed for example. The app create a especial gtk widget get its xid and run dillo like that: $ dillo -x xid(this is a number) Then that dillo will appear in the gkt widget and not in a separate window. With a few changes (18 lines added to dillo) dillo can ask the xid to a DPI when it want to open a new window. The DPI is a GTK window with a notebook widget. Each time dillo ask it for a xid the DPI adds a new tab and pass its xid to dillo and dillo appear in the tab. (If the xid returned by the DPI is 0 dillo open a separate window) TODO: - Remove the GTK example code - Add menus to tabs, close tab button ... - maybe add a configuration file Instructions to test it: download the patch attached to this mail (tabs_dpi.diff) get the last dillo cvs (if asked for a password, press ENTER) $ cvs -z3 -d:pserver:anonymous@auriga.wearlab.de:/sfhome/cvs/dillo login $ cvs -z3 -d:pserver:anonymous@auriga.wearlab.de:/sfhome/cvs/dillo co dillo change to the dillo cvs directory and apply the patch $ cd dillo $ patch -p1 < ../tabs_dpi.diff generate configure, configure code and compile it $ ./autogen.sh && ./configure --disable-dlgui && make install the tabs dpi and optionaly the patched dillo # make install run the patched dillo comanding it to ask the xid and with a given size (only to see the dillo window entirely) $ dillo -x ask -g 700x500 To open a new tab use midle click on a link or the menu file->new browser To close a tab use the remove page button or the menu file->close window Excuse me my english and please test and tell what you think about this. Diego.

1 0

non released unfinished code
by Diego . April 2, 2007

April 2, 2007

Hello. I agree (in the general discussion) that it is a bad idea to keep closed the dillo FLTK code. (I reserve other opinions for other mail) This mail is only because i have some unfinished code for dillo and want to open/show/give to the rest of the list. I have a Dillo PlugIn that add tabs to dillo. The plug in is a GTK 1.2 app and a DPI at the same time. I do not known GTK 1.2 and do not have time to learn it. I was waiting for the FLTK dillo to program a FLTK version, but now i think that it is better to show bad programed unfinished code instead of wait. Try to run it before watch the code (based on a notebook GTK 1.2example) I hope that some GTK programer can finish it. How do it work: Now dillo can be embedded in other program. This is used by sylpheed for example. The app create a especial gtk widget get its xid and run dillo like that: $ dillo -x xid(this is a number) Then that dillo will appear in the gkt widget and not in a window. With a few changes dillo can ask the xid to a DPI when it want to open a new window. The DPI is a GTK window with a notebook widget. Each time dillo ask it for a xid the DPI adds a new tab and pass its xid to dillo and dillo appear in the tab. Instructions to test it: download the patch attached to this mail (tabs_dpi.diff) get the last dillo cvs (if asked for a password, press ENTER) $ cvs -z3 -d:pserver:anonymous@auriga.wearlab.de:/sfhome/cvs/dillo login $ cvs -z3 -d:pserver:anonymous@auriga.wearlab.de:/sfhome/cvs/dillo co dillo change to the dillo cvs directory and apply the patch $ cd dillo $ patch -p1 < ../tabs_dpi.diff generate configure, configure code and compile it $ ./autogen.sh && ./configure --disable-dlgui && make install the tabs dpi and optionaly the patched dillo # make install run the patched dillo comanding it to ask the xid and with a given size (only to see the dillo window entirely) $ dillo -x ask -g 700x500 To open a new tab use midle click on a link or the menu file->new browser To close a tab use the remove page button or the menu file->close window Excuse me my english and please test and tell what you think about this. Diego.

1 0

PledgeBank ?
by Vincent Thomasset Feb. 25, 2007

Feb. 25, 2007

Hi Jorge, What do you think of trying to raise some funds using pledgebank ? I know this is not really the type of funding you're expecting for Dillo, but it should be interesting to see if there's a response. Considering what recently happened to the nouveau project [1] (someone raised 1300+ 10$ donations in their name), if think it could be interesting to take the chance. On a related note, the FOSDEM will be held 5 minutes away from my place, i could drop some "Fund Dillo" posters there to get some publicity. What do you think ? Cheers, Vincent

3 4

Web page update
by Jorge Arellano Cid Feb. 25, 2007

Feb. 25, 2007

Hi there, As said sometime ago in this mailing list, I went to update the front page of Dillo's site to let our users know what the current status of the project is, and what we're doing/expecting. It is just a small section under the "Project Objectives". Please give it a read and send your feedback here if any. I know the "funding" link would benefit from an update, but sometime ago it was quite current and as it yielded no results, I'm not sure it to be worth the effort anymore ;-). Perhaps an alternative way could work better. -- Cheers Jorge.-

1 0

FLTK2 port to DirectFB
by Diego . Feb. 16, 2007

Feb. 16, 2007

It seems that somebody is working on the port of FLTK2 to DirectFB http://www.fltk.org/newsgroups.php?gfltk.development+v:4889 I do not get to compile it, but i hope that somebody can. (It is in a very early stage yet) Nothing more, good bye. Diego.

1 0

Port/package for Nokia 770 / N800
by Anuj Verma (Kevin) Feb. 15, 2007

Feb. 15, 2007

Hello list, I am curious to know if there is a package of Dillo for Nokia 770 or N800 ? Will someone be please interested to contribute one ? Refer: http://en.wikipedia.org/wiki/Nokia_N800 http://maemo.org Cheers, Kevin

3 2

Re: [Dillo-dev] PledgeBank ?
by Jorge Arellano Cid Feb. 8, 2007

Feb. 8, 2007

Hi Johannes and R.L, Please excuse my delay to answer. Finally I found some time to address this. On Thu, Feb 01, 2007 at 05:25:49PM +0100, Johannes Hofmann wrote: > Hi Jorge, > > On Thu, Feb 01, 2007 at 08:56:47AM -0300, Jorge Arellano Cid wrote: > > > > Another important point is that we're not working with GTK1 > > anymore, but with FLTK2 (antialiasing, UTF-8, statical linking in > > 700KB, less dependencies, etc). We have an advanced prototype. > > This is important for potential developers. > > > > We're looking for interested developers to work on Dillo. This > > is also key to the success of the project. This is the kind of > > developer that not only sends patches but that contributes to the > > core of it. > > > > Sometime ago I asked in this list for interested developers and > > got only one answer for a "patch-developer" so to speak. > > I'm a long time dillo user and have some experience with fltk1 and > fltk2 from my small spare time projects. > I would be happy to contribute to the dillo project but my time > will be limited... "R.L. Horn" wrote: > > Sometime ago I asked in this list for interested developers and > >got only one answer for a "patch-developer" so to speak. > > Actually, I volunteered some time back and never got a response. I > haven't fiddled with FLTK development, but I reckon I could pick it up in > a week or so. Thanks for commiting some time to Dillo! PLease let me know a rough estimate of how much time could this be. Just to have an idea of what kind of task you both can work in based on your expertise and available time. At this moment, much of Dillo is quite similar to what we had in 0.8.x series. The main differences are: - Dw was ported to C++ (some new capabilities, similar API). - HTML/text/script parser was ported to C++. - The Concomitant callback chain was redesigned for simplicity. (Now, instead of one CCC branch per task, an anhanced universal branch handles Dpi, HTML, text and images). - Bug fixes/injections ;-) A great thing is that Dw is well documented (Doxygen), it has a testbed, it's isolated from Dillo and it can be studied comfortably. OTOH, there's a lot of middle/minor work to be done to complete its implementation. If I get your time availability it would be easier to plan with Sebastian what to suggest you to work on. Thanks a lot for your commitment. May thy example be followed by the listeners! :-) -- Cheers Jorge.-

2 2

Re: [Dillo-dev] [marco@hep.uchicago.edu: Re: Dillo not compiling]
by Livio Soares Feb. 8, 2007

Feb. 8, 2007

Hi Marco, Marco Mambelli writes: > Hi Livio, > Thank you, I added glib-devel and gtk+-devel > > autogen and configure are fine now. Nice. > In compilation there are some warning (signedness mainly) and errors in > downloads.cc compilation: > if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include > -I/usr/include/glib-1.2 -I/usr/lib/glib/include -g -O2 -MT downloads.o -MD > -MP -MF ".deps/downloads.Tpo" -c -o downloads.o downloads.cc; \ > then mv -f ".deps/downloads.Tpo" ".deps/downloads.Po"; else rm -f > ".deps/downloads.Tpo"; exit 1; fi > downloads.cc:34:22: error: fltk/run.h: No such file or directory > downloads.cc:35:25: error: fltk/Window.h: No such file or directory > downloads.cc:36:25: error: fltk/Widget.h: No such file or directory > downloads.cc:37:25: error: fltk/damage.h: No such file or directory > ... and many other errors depending probably on the missing files > (undefined variables, scope problems, ...) > > I installed fltk and fltk-devel libraries but this did not solved the > problem. Unfortunately, this isn't very well documented, but you actually need FLTK 2, to allow the download DPI to work. If I remember correctly (Jorge can correct me if I'm wrong), compiling the download DPI is optional (--disable-dlgui, I think, was the configure option). So, you can either forget about the download DPI, find RPMs for FLTK2 (both library and -devel), or build/install FLTK2 yourself. Now, don't you just _love_ recursive build dependences ;P Good luck, Livio

2 1

[marco@hep.uchicago.edu: Re: Dillo not compiling]
by Jorge Arellano Cid Feb. 6, 2007

Feb. 6, 2007

-- Cheers Jorge.-

2 1

[grigory@cisnet.ru: an article about dillo]
by Jorge Arellano Cid Jan. 25, 2007

Jan. 25, 2007

-- Cheers Jorge.-

1 1

Re: Your Web Pages
by Jorge Arellano Cid Jan. 11, 2007

Jan. 11, 2007

Hi John, First of all, thanks for checking the project. Hero go some answers... On Wed, Jan 10, 2007 at 09:58:37PM -0800, John Gutierrez wrote: > Jorge, > > Will you site be updated anytime soon. Some of your pages have a date of > July 24, 2003 (funding.html). I check your site from time to time, but > rarely see new information. > > Plans.html has not had an update since August 2006. I would imagine that the > bullet colors would have changed by now. > > The ChangeLog.html shows a date of Apr 26, 2006 (no new version since then?) > > The FAQ.html still references version 8.4. and talks about FLTK port as of > 2005! > > Fosdem 2005 and LSM 2005 are OLD events - anything current? > > The Achievements (A_gols.html was last modified October 2,2006 - anything > new? The Dillo project is currently frozen. I'm expecting the vacation season in Germany to end to communicate with Sebastian and update the site with an official statement of the current situation. (I've tried to reach him since late 2006 so I assume he's on holidays). The latter time was spent trying to rise funds for continuing the development with at least two people working full time on it. Funding didn't happen so I had to take a job, and as Sebastian had a job, the situation now is we're both on a spare time basis that in practice has been close to nil. OTOH, the port to FLTK2 has gone very good with no surprises and a very good transition. The problem is lack of manpower because of lack of funds. The project is frozen because it is impossible to develop a web browser (very complex task), keeping pace with the evolving technologies, by working on a spare time basis. The web site will be updated after I have a virtual meeting to discuss the points with Sebastian, or in mid February, whatever comes first. -- Cheers Jorge.-

1 0

Re: [Dillo-dev] dillo chat in Logroño/La Rioja/Spain
by Diego . Dec. 5, 2006

Dec. 5, 2006

Ok, but with FALSE (DwPage owns a button that owns the image) the button fail to draw the alt text when can not load the image and do not use width and height atributes of the html tag. Using your patch and seting the parameter to TRUE it use width, height and alt, but do not redraw alt text. Without your patch dillo segfaults if that parameter is true. Diego. 2006/12/2, Jorge Arellano Cid <jcid(a)dillo.org>: > > Hi Diego, > > On Fri, Dec 01, 2006 at 02:23:01AM +0100, Diego . wrote: > > Very thanks for the fast patch and the advices. > > One question ¿In Html_input_image why is the function Html_add_new_image > > called with the FALSE parameter? > > Quick answer: > > Because the image is embedded inside a button that's already > inside the DwPage. > > In other words: there's no need to add the image to the DwPage > because the button "owns" the image (think of an object), thus > only the button object needs to be added. > > -- > Cheers > Jorge.- >

2 1

dillo chat in Logroño/La Rioja/Spain
by Diego . Nov. 29, 2006

Nov. 29, 2006

Hello. I am Diego Sáenz. I use this mail address now (I had mail problems and lost some mails, but i have read them in the list archive). I am associate of AULIR (Asociacion de Usuarios de GNU/Linux de La Rioja) a spanish LUG and will give a chat about how to wrote dillo plug-ins. I will explain a few the dillo internals too. There are not very much programers in AULIR(one of them program anjelica.sourceforge.net) but i will try to wake interest about dillo. Any advice for the chat? I will try to show a preferences plug in as example. Is the bug #695 solved somewhere? i think i will need to use it for a feature of the plug in. Diego. ps: i hoppe that this do not seem spam* *

2 1

Re: invalid (?) relative url resolve issue +patch
by Jorge Arellano Cid Nov. 29, 2006

Nov. 29, 2006

Hi, On Wed, Nov 29, 2006 at 12:47:39AM +0100, Schilter Roland wrote: > Hello, > first of all, thanks for dillo :) ;) > I think I found a bug or at least, a misbehaviour that is handled in famous browsers differently. > I looked through the code and finally figured out where to change code to get the expected behaviour. > (Took some time though :p ) > > I need to mention that I didn't read the RFC2396 about URIs and I have the feeling that the implementation > in dillo may be according to specifications but nevertheless, i couldn't browse several sites... :) > > The problem is, if a `href' attribute of html-tag `a' starts only with a query (`?test') > then the path of the baseurl is only taken until the last slash: > > <a href="?test">test</a> while the baseurl being `www.example.com/example' > > this link will resolve to www.example.com/?test although I expected it to go to www.example.com/example?test Give a look to RFC-2396 C.1 Normal examples: base = http://a/b/c/d;p?q#f relative = ?y resolved => http://a/b/c/?y Dillo passes all those tests, including the abnormal section. Ah and we also test for these extra tests: http://www.ics.uci.edu/~fielding/url/test2.html http://www.ics.uci.edu/~fielding/url/test3.html http://www.ics.uci.edu/~fielding/url/test4.html http://www.ics.uci.edu/~fielding/url/test5.html HTH. -- Cheers Jorge.-

1 0

The sound of silence
by Joonas Saarinen Nov. 29, 2006

Nov. 29, 2006

Hello, It has been almost two months of silence on this list and I thought to ask how are you doing? :) Anything new about the "Campaign to help Dillo survive"? Etc.

2 1

Re: [Fwd: Dillo article precisions]
by Jorge Arellano Cid Oct. 4, 2006

Oct. 4, 2006

Hi Henry, On Tue, Oct 03, 2006 at 02:30:33PM -0700, Henry Kingman wrote: > Hi Jorge, > > I tried to update our article with some of the details you sent. > > Thanks, and good luck with the Dillo project! I hope you find funding. Thanks for the corrections. One important precision: the dillo project needs at least two core developers working on it fulltime. Not only me. If there's only one person working full time on it, it's not enough to keep the pace of evolving technologies. That's what I meant when writing: > > The situation is this: there're two core developers. We need at > >least to be both working on Dillo full time (ideally three devs.) > >otherwise the project would lag behind the moving target that > >Internet browsing is. I find this paragraph misleading: "Alternatively, Cid says he will release the FLTK2 port if he finds enough funding to be able to continue working fulltime on the port himeself. He said, "Given the current situation, the best option seems to be to remain closed until funding happens." and it's not true. Please make the correction. -- Cheers Jorge.- > > -Henry > > cc: Rick, executive editor > > -- > Henry Kingman, senior editor > LinuxDevices.com > Ziff Davis Internet > 775 625-4547 > > > > > > > >-------- Original Message -------- > >Subject: Dillo article precisions > >Date: Tue, 3 Oct 2006 09:40:28 -0400 > >From: Jorge Arellano Cid <jcid(a)dillo.org> > >To: Rick Lehrbaum <rick(a)linuxdevices.com> > >CC: Dillo mailing list <dillo-dev(a)lists.auriga.wearlab.de> > > > >Hi Rick, > > > > It's being a long time since my last article at linuxdevices, > >receive my greetings from Chile! > > > > With regard to the new article: > > > > http://linuxdevices.com/news/NS4370323584.html > > > > It caught me by surprise. There was a thread in dillo-dev and > >some users suggested that campaign. I was commenting on gross > >factual mistakes in the wiki when it was announced that an > >article was live at linuxdevices. > > > > It's good to see our users' interest in keeping the project > >alive, so I'll comment the article here so you can correct and > >improve the article: > > > > > >>A project to create an ultra-lightweight web browser for use in > >>embedded devices and other resource-constrained hardware has > >>issued a plea for financial help. The Dillo Project says it needs > >>to find a corporate sponsor in order to add anti-aliased text, > >>CSS, Javascript, and internationalization/localization support. > > > > We've almost finished the port to FLTK2, and it already has > >anti-aliased text. (Dillo doesn't compile with FLTK1) > > > > FLTK2 uses UTF8 and provides antialiasing so it solves the > >problem of using GTK1 (this was one of the reasons for GTK1 to go > >GTK2). > > > > UTF8 also makes it easy to add i18n and l10n without breaking > >things inside the browser. > > > > I point this technical details because unofficial patches have > >been developed for antialiasing, i18n and l10n for GTK1. This is > >a good workaround but not a long term solution. > > > > > >> > >>(Click for larger screenshot of Dillo) > > > > Here you'll find a screenshot of dillo-fltk2: > > > > http://www.dillo.org/test/ph2.png > > > > (it shows antialiasing) > > > > > >> > >>Dillo is a very lightweight (about 350 KB) browser supporting a > >>subset of HTML, CGI, SSL, and cookies. > > > > And plugins. > > + Images (GIF, PNG and JPEG) > > > >> Dillo is not really > >>practical for browsing the modern Internet, due to missing > >>support for frames, CSS, Javascript, and other commonly used > >>standards and protocols. It also lacks support for anti-aliased > >>text, something even Linux desktop users have long taken for > >>granted, and appears to have only rudimentary HTML error handling > >>capabilities. > > > > The HTML error handling has improved a lot (the bug meter can > >atest that), but yes, error handling is not as advanced as with > >Firefox. > > > > Anyway, sometimes there're pages with a few hundred mistakes > >handled gracefully. ;-) > > > > > >>Nonetheless, Dillo is extremely fast and lightweight, using less > >>memory in some cases than popular text-based browsers such as > >>lynx. And, since it supports CGI, it could be useful as a > >>framework for simple device interfaces based on Web standards, > >>such as survey kiosks and other closed, "walled garden" > >>applications. > > > > BTW, the new Dillo with a statically linked FLTK2 is about > >820 Kilobytes. > > > >> > >>Additionally, Dillo is popular with web developers due to > >>excellent HTML error reporting. > > > > :-) > > > > > >> > >>Dillo is expected to gain support for anti-aliased text after its > >>development team completes a port to FLTK (fast light toolkit, > >>aka "fulltick"). > > > > [Already there, see above] > > > >> However, founder Jorge Arellano Cid appears > >>adamant that funding be located prior to release of his > >>nearly-complete FLTK port, according to a "save Dillo" campaign > >>page hosted here. > > > > True. > > > > The situation is this: there're two core developers. We need at > >least to be both working on Dillo full time (ideally three devs.) > >otherwise the project would lag behind the moving target that > >Internet browsing is. > > > > Sebastian (the other core developer) is employed fulltime in > >Germany so he has almost no time to Develop. I don't have funds > >to keep on working fulltime too, so if there're no funds the > >project will loose the main developers and their knowledge. > > > > With regard to releasing. That's what I've done for 6+ years > >with GTK1 and no funding happened ;-). > > > > If there were more interested developers in working with Dillo > >(lets say 6 serious and qualified people) I would consider > >releasing because the project could advance in that case. > > > > Believe it or not I asked in dillo-dev, and there was only one > >answer from a dev that could put 4 hours/week and that had no > >FLTK2 knowledge nor on Dillo internals. > > > > Given the current situation, the best option seems to remain > >closed until funding happens. > > > > > >> > >>Other ongoing Dillo development efforts reportedly include CSS > >>support (said to be "70 percent complete") and JavaScript > >>support, as well as additional internationalization (I18n) and > >>localization (l10n) features. > > > > I reported 70% on CSS. This is on the FLTK2 branch, not from > >external efforts. > > > > The interesting part is that we paved the way for all these in > >the newest branch, so now it's much easier to develop them over > >the new code base than with the old branch. > > > > A rough timeline estimation would be near 2 years to have the > >whole set: antialiasing, CSS, I18n, l10n, Frames, Tabs, SSL and > >good Javascript. > > > > We could make a release in 6 months and thenceforth go on > >incrementally adding features in any desired order (probably this > >would be up to the sponsors' needs). > > > > > >>Additional details about Dillo can be found on Dillo's official > >>funding presentations page. For additional background, be sure to > >>read Cid's 2002 introduction to the browser, here. > >> > >>The Dillo project previously sought funding in February of 2004, > >>and was successful in obtaining a one-time grant through the > >>Linux Fund. > > > > > > Thanks a lot for your time and commitment. > > > > > > > -- > Henry Kingman, senior editor > LinuxDevices.com > Ziff Davis Internet > 775 625-4547 >

2 2

Dillo article precisions
by Jorge Arellano Cid Oct. 3, 2006

Oct. 3, 2006

Hi Rick, It's being a long time since my last article at linuxdevices, receive my greetings from Chile! With regard to the new article: http://linuxdevices.com/news/NS4370323584.html It caught me by surprise. There was a thread in dillo-dev and some users suggested that campaign. I was commenting on gross factual mistakes in the wiki when it was announced that an article was live at linuxdevices. It's good to see our users' interest in keeping the project alive, so I'll comment the article here so you can correct and improve the article: > A project to create an ultra-lightweight web browser for use in > embedded devices and other resource-constrained hardware has > issued a plea for financial help. The Dillo Project says it needs > to find a corporate sponsor in order to add anti-aliased text, > CSS, Javascript, and internationalization/localization support. We've almost finished the port to FLTK2, and it already has anti-aliased text. (Dillo doesn't compile with FLTK1) FLTK2 uses UTF8 and provides antialiasing so it solves the problem of using GTK1 (this was one of the reasons for GTK1 to go GTK2). UTF8 also makes it easy to add i18n and l10n without breaking things inside the browser. I point this technical details because unofficial patches have been developed for antialiasing, i18n and l10n for GTK1. This is a good workaround but not a long term solution. > > (Click for larger screenshot of Dillo) Here you'll find a screenshot of dillo-fltk2: http://www.dillo.org/test/ph2.png (it shows antialiasing) > > Dillo is a very lightweight (about 350 KB) browser supporting a > subset of HTML, CGI, SSL, and cookies. And plugins. + Images (GIF, PNG and JPEG) > Dillo is not really > practical for browsing the modern Internet, due to missing > support for frames, CSS, Javascript, and other commonly used > standards and protocols. It also lacks support for anti-aliased > text, something even Linux desktop users have long taken for > granted, and appears to have only rudimentary HTML error handling > capabilities. The HTML error handling has improved a lot (the bug meter can atest that), but yes, error handling is not as advanced as with Firefox. Anyway, sometimes there're pages with a few hundred mistakes handled gracefully. ;-) > Nonetheless, Dillo is extremely fast and lightweight, using less > memory in some cases than popular text-based browsers such as > lynx. And, since it supports CGI, it could be useful as a > framework for simple device interfaces based on Web standards, > such as survey kiosks and other closed, "walled garden" > applications. BTW, the new Dillo with a statically linked FLTK2 is about 820 Kilobytes. > > Additionally, Dillo is popular with web developers due to > excellent HTML error reporting. :-) > > Dillo is expected to gain support for anti-aliased text after its > development team completes a port to FLTK (fast light toolkit, > aka "fulltick"). [Already there, see above] > However, founder Jorge Arellano Cid appears > adamant that funding be located prior to release of his > nearly-complete FLTK port, according to a "save Dillo" campaign > page hosted here. True. The situation is this: there're two core developers. We need at least to be both working on Dillo full time (ideally three devs.) otherwise the project would lag behind the moving target that Internet browsing is. Sebastian (the other core developer) is employed fulltime in Germany so he has almost no time to Develop. I don't have funds to keep on working fulltime too, so if there're no funds the project will loose the main developers and their knowledge. With regard to releasing. That's what I've done for 6+ years with GTK1 and no funding happened ;-). If there were more interested developers in working with Dillo (lets say 6 serious and qualified people) I would consider releasing because the project could advance in that case. Believe it or not I asked in dillo-dev, and there was only one answer from a dev that could put 4 hours/week and that had no FLTK2 knowledge nor on Dillo internals. Given the current situation, the best option seems to remain closed until funding happens. > > Other ongoing Dillo development efforts reportedly include CSS > support (said to be "70 percent complete") and JavaScript > support, as well as additional internationalization (I18n) and > localization (l10n) features. I reported 70% on CSS. This is on the FLTK2 branch, not from external efforts. The interesting part is that we paved the way for all these in the newest branch, so now it's much easier to develop them over the new code base than with the old branch. A rough timeline estimation would be near 2 years to have the whole set: antialiasing, CSS, I18n, l10n, Frames, Tabs, SSL and good Javascript. We could make a release in 6 months and thenceforth go on incrementally adding features in any desired order (probably this would be up to the sponsors' needs). > Additional details about Dillo can be found on Dillo's official > funding presentations page. For additional background, be sure to > read Cid's 2002 introduction to the browser, here. > > The Dillo project previously sought funding in February of 2004, > and was successful in obtaining a one-time grant through the > Linux Fund. Thanks a lot for your time and commitment. -- Cheers Jorge.-

2 1

Campaign to help Dillo survive
by Alan Carvalho de Assis Oct. 3, 2006

Oct. 3, 2006

Hi all, I am writing a document to convince some company to help Dillo project. I think it is an idea we need fight for. I invite everybody to help to improve this document, when we get a powerful document we will send it for some friends at Nokia, Motorola and others. The early version can found here: http://fornix.sourceforge.net/wiki/index.php/Campaign_to_help_Dillo_survive Be free do edit this wiki. Thank you, -- ------------------------------------------------------------ | Alan Carvalho de Assis | ------------------------------------------------------------ -- Não importa o que os outros irão pensar, A cura para a infelicidade é a felicidade

4 11

[jcid@dillo.org: Re: [Dillo-dev] Campaign to help Dillo survive]
by Jorge Arellano Cid Oct. 2, 2006

Oct. 2, 2006

-- Cheers Jorge.-

1 0