- Dillo-dev - lists.mailman3.com

Feature request: Server connection status message

by james.from.wellington＠gmail.com

Hello Dillo maintainer people, If I set out to write this patch, the first version will be painful. Do you want the change? Do you want to hand-hold me through writing it? Regards, James. > On 9/03/2016, at 4:09 am, Alexander Voigt <Hole.destructor at gmx.de> wrote: > > Hi James, > >> 'Transferring ...' is already covered in the top right corner, where >> there is a number of kilobytes that goes grey when transferring >> finishes. > > ah, you are right, I was not aware of that. > >> I wonder if the other things that you want could be retrofitted into >> that box. I wonder if the set should include: >> - Parse - parsing the URL and preparing to act on it >> - DNS - waiting for the DNS >> - CONN - waiting for a TCP connection to complete >> - SEC - waiting for a security handshake > > Yes, that would be great! It would make even more transparent what > Dillo does in the background. > > Best regards, > Alex > >> On Tue, Mar 08, 2016 at 10:53:49PM +1300, James C wrote: >> Hello Alexander, >> >> 'Transferring ...' is already covered in the top right corner, where >> there is a number of kilobytes that goes grey when transferring >> finishes. >> >> I wonder if the other things that you want could be retrofitted into >> that box. I wonder if the set should include: >> - Parse - parsing the URL and preparing to act on it >> - DNS - waiting for the DNS >> - CONN - waiting for a TCP connection to complete >> - SEC - waiting for a security handshake >> >> Regards, >> James. >> >>> On 08/03/2016, Alexander Voigt <Hole.destructor at gmx.de> wrote: >>> Dear Dillo developers, >>> >>> since the bug tracker is down, please let me propose a new feature >>> over the mailing list. >>> >>> From time to time I am in places with a very bad internet connection. >>> when I surf with Dillo and click on a link it appears that nothing >>> happens, except that the link color has changed. Then I'm usually >>> wondering what's going on now. Did I really click the link? Has the >>> server has been found? Is the server responding very slowly? Does >>> Dillo receive data from it? Or is my connection dead? >>> >>> To avoid this confusion, I'd like to propose a status message which is >>> displayed in the status bar at the very bottom of the Dillo window. >>> The message could say what is currently been done. For example, >>> Firefox says >>> >>> "Looking up www.example.de" >>> "Waiting for www.example.de" >>> "Transferring data from www.example.de" >>> >>> Many thanks and best regards, >>> Alex >>> >>> _______________________________________________ >>> Dillo-dev mailing list >>> Dillo-dev at dillo.org >>> http://lists.dillo.org/cgi-bin/mailman/listinfo/dillo-dev >>>

March 9, 2016

Feature request: Server connection status message

by Hole.destructor＠gmx.de

Hi James, > 'Transferring ...' is already covered in the top right corner, where > there is a number of kilobytes that goes grey when transferring > finishes. ah, you are right, I was not aware of that. > I wonder if the other things that you want could be retrofitted into > that box. I wonder if the set should include: > - Parse - parsing the URL and preparing to act on it > - DNS - waiting for the DNS > - CONN - waiting for a TCP connection to complete > - SEC - waiting for a security handshake Yes, that would be great! It would make even more transparent what Dillo does in the background. Best regards, Alex On Tue, Mar 08, 2016 at 10:53:49PM +1300, James C wrote: > Hello Alexander, > > 'Transferring ...' is already covered in the top right corner, where > there is a number of kilobytes that goes grey when transferring > finishes. > > I wonder if the other things that you want could be retrofitted into > that box. I wonder if the set should include: > - Parse - parsing the URL and preparing to act on it > - DNS - waiting for the DNS > - CONN - waiting for a TCP connection to complete > - SEC - waiting for a security handshake > > Regards, > James. > > On 08/03/2016, Alexander Voigt <Hole.destructor at gmx.de> wrote: > > Dear Dillo developers, > > > > since the bug tracker is down, please let me propose a new feature > > over the mailing list. > > > > From time to time I am in places with a very bad internet connection. > > when I surf with Dillo and click on a link it appears that nothing > > happens, except that the link color has changed. Then I'm usually > > wondering what's going on now. Did I really click the link? Has the > > server has been found? Is the server responding very slowly? Does > > Dillo receive data from it? Or is my connection dead? > > > > To avoid this confusion, I'd like to propose a status message which is > > displayed in the status bar at the very bottom of the Dillo window. > > The message could say what is currently been done. For example, > > Firefox says > > > > "Looking up www.example.de" > > "Waiting for www.example.de" > > "Transferring data from www.example.de" > > > > Many thanks and best regards, > > Alex > > > > _______________________________________________ > > Dillo-dev mailing list > > Dillo-dev at dillo.org > > http://lists.dillo.org/cgi-bin/mailman/listinfo/dillo-dev > >

March 8, 2016

Feature request: Server connection status message

by james.from.wellington＠gmail.com

Hello Alexander, 'Transferring ...' is already covered in the top right corner, where there is a number of kilobytes that goes grey when transferring finishes. I wonder if the other things that you want could be retrofitted into that box. I wonder if the set should include: - Parse - parsing the URL and preparing to act on it - DNS - waiting for the DNS - CONN - waiting for a TCP connection to complete - SEC - waiting for a security handshake Regards, James. On 08/03/2016, Alexander Voigt <Hole.destructor at gmx.de> wrote: > Dear Dillo developers, > > since the bug tracker is down, please let me propose a new feature > over the mailing list. > > From time to time I am in places with a very bad internet connection. > when I surf with Dillo and click on a link it appears that nothing > happens, except that the link color has changed. Then I'm usually > wondering what's going on now. Did I really click the link? Has the > server has been found? Is the server responding very slowly? Does > Dillo receive data from it? Or is my connection dead? > > To avoid this confusion, I'd like to propose a status message which is > displayed in the status bar at the very bottom of the Dillo window. > The message could say what is currently been done. For example, > Firefox says > > "Looking up www.example.de" > "Waiting for www.example.de" > "Transferring data from www.example.de" > > Many thanks and best regards, > Alex > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev at dillo.org > http://lists.dillo.org/cgi-bin/mailman/listinfo/dillo-dev >

March 8, 2016

Feature request: Server connection status message

by Hole.destructor＠gmx.de

Dear Dillo developers, since the bug tracker is down, please let me propose a new feature over the mailing list. >From time to time I am in places with a very bad internet connection. when I surf with Dillo and click on a link it appears that nothing happens, except that the link color has changed. Then I'm usually wondering what's going on now. Did I really click the link? Has the server has been found? Is the server responding very slowly? Does Dillo receive data from it? Or is my connection dead? To avoid this confusion, I'd like to propose a status message which is displayed in the status bar at the very bottom of the Dillo window. The message could say what is currently been done. For example, Firefox says "Looking up www.example.de" "Waiting for www.example.de" "Transferring data from www.example.de" Many thanks and best regards, Alex

March 8, 2016

CPU hog

by jcid＠dillo.org

Hi, FYI, https://www.raspberrypi.org/blog/raspberry-pi-3-on-sale/ gives a CPU hog on both dillo and dillo_grows. -- Cheers Jorge.-

March 5, 2016

Dill 3.0.5 breaks on Mac OS

by yesyves＠gmail.com

>> I do get this message repeated many many times : >> >> Mar 1 17:55:52 dillo[4169] <Error>: CGContextSetShouldAntialias: invalid context 0x0. If you want to see the backtrace, please set CG_CONTEXT_SHOW_BACKTRACE environmental variable. > > what Mac OS and FLTK version are you running and how did you install > FLTK. Also please set the environmental variable as suggested and > post the output. The you go. Mac OS 10.11.3 FLTK 1.1.3 installed through Macports Gandalf:.xinitrc.d yves$ export CG_CONTEXT_SHOW_BACKTRACE=yes Gandalf:.xinitrc.d yves$ dillo paths: Cannot open file '/Users/yves/.dillo/dillorc': No such file or directory paths: Using /opt/local/etc/dillo/dillorc paths: Cannot open file '/Users/yves/.dillo/keysrc': No such file or directory paths: Using /opt/local/etc/dillo/keysrc paths: Cannot open file '/Users/yves/.dillo/domainrc': No such file or directory paths: Using /opt/local/etc/dillo/domainrc Domain: Default accept. dillo_dns_init: Here we go! (threaded) Disabling cookies. ** WARNING **: preferred sans-serif font "DejaVu Sans" not found. ** WARNING **: preferred serif font "DejaVu Serif" not found. ** WARNING **: preferred monospace font "DejaVu Sans Mono" not found. ** WARNING **: preferred cursive font "URW Chancery L" not found. ** WARNING **: preferred fantasy font "DejaVu Sans" not found. Nav_open_url: new url='about:splash' Mar 2 18:36:30 dillo[23010] <Error>: CGContextSetTextPosition: invalid context 0x0. Backtrace: <_Z15fl_text_extentsPKcRiS1_S1_S1_+80> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+1634> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+2707> <_ZN13CssStyleSheetC2Ev+11934> <_ZN8CustTabsC2EiiiPKc+33863> <_ZN8CustTabsC2EiiiPKc+42753> <_ZN8CustTabsC2EiiiPKc+45551> <_ZL8do_timerP16__CFRunLoopTimerPv+42> <__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__+20> <__CFRunLoopDoTimer+1075> <__CFRunLoopDoTimers+298> <__CFRunLoopRun+1841> <CFRunLoopRunSpecific+296> <RunCurrentEventLoopInMode+235> <ReceiveNextEventCommon+184> <_BlockUntilNextEventMatchingListInModeWithFilter+71> <_DPSNextEvent+1067> <-[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:]+454> <_Z7fl_waitd+150> <_Z21fl_mac_flush_and_waitd+155> <_ZN2Fl3runEv+19> <(null)+4361965094> <start+1> Mar 2 18:36:30 dillo[23010] <Error>: CGContextSetShouldAntialias: invalid context 0x0. Backtrace: <_Z15fl_text_extentsPKcRiS1_S1_S1_+80> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+1634> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+2707> <_ZN13CssStyleSheetC2Ev+11934> <_ZN8CustTabsC2EiiiPKc+33863> <_ZN8CustTabsC2EiiiPKc+42753> <_ZN8CustTabsC2EiiiPKc+45551> <_ZL8do_timerP16__CFRunLoopTimerPv+42> <__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__+20> <__CFRunLoopDoTimer+1075> <__CFRunLoopDoTimers+298> <__CFRunLoopRun+1841> <CFRunLoopRunSpecific+296> <RunCurrentEventLoopInMode+235> <ReceiveNextEventCommon+184> <_BlockUntilNextEventMatchingListInModeWithFilter+71> <_DPSNextEvent+1067> <-[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:]+454> <_Z7fl_waitd+150> <_Z21fl_mac_flush_and_waitd+155> <_ZN2Fl3runEv+19> <(null)+4361965094> <start+1> Mar 2 18:36:30 dillo[23010] <Error>: CGContextSetShouldAntialias: invalid context 0x0. Backtrace: <_Z15fl_text_extentsPKcRiS1_S1_S1_+80> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+1634> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+2707> <_ZN13CssStyleSheetC2Ev+11934> <_ZN8CustTabsC2EiiiPKc+33863> <_ZN8CustTabsC2EiiiPKc+42753> <_ZN8CustTabsC2EiiiPKc+45551> <_ZL8do_timerP16__CFRunLoopTimerPv+42> <__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__+20> <__CFRunLoopDoTimer+1075> <__CFRunLoopDoTimers+298> <__CFRunLoopRun+1841> <CFRunLoopRunSpecific+296> <RunCurrentEventLoopInMode+235> <ReceiveNextEventCommon+184> <_BlockUntilNextEventMatchingListInModeWithFilter+71> <_DPSNextEvent+1067> <-[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:]+454> <_Z7fl_waitd+150> <_Z21fl_mac_flush_and_waitd+155> <_ZN2Fl3runEv+19> <(null)+4361965094> <start+1> Mar 2 18:36:30 dillo[23010] <Error>: CGContextSetTextPosition: invalid context 0x0. Backtrace: <_Z15fl_text_extentsPKcRiS1_S1_S1_+80> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+1634> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+2707> <_ZN13CssStyleSheetC2Ev+16841> <_ZN13CssStyleSheetC2Ev+21235> <_ZN11DoctreeNodeD2Ev+13496> <_ZN11DoctreeNodeD2Ev+6209> <_ZN8CustTabsC2EiiiPKc+42885> <_ZN8CustTabsC2EiiiPKc+45551> <_ZL8do_timerP16__CFRunLoopTimerPv+42> <__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__+20> <__CFRunLoopDoTimer+1075> <__CFRunLoopDoTimers+298> <__CFRunLoopRun+1841> <CFRunLoopRunSpecific+296> <RunCurrentEventLoopInMode+235> <ReceiveNextEventCommon+184> <_BlockUntilNextEventMatchingListInModeWithFilter+71> <_DPSNextEvent+1067> <-[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:]+454> <_Z7fl_waitd+150> <_Z21fl_mac_flush_and_waitd+155> <_ZN2Fl3runEv+19> <(null)+4361965094> <start+1> Mar 2 18:36:30 dillo[23010] <Error>: CGContextSetShouldAntialias: invalid context 0x0. Backtrace: <_Z15fl_text_extentsPKcRiS1_S1_S1_+80> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+1634> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+2707> <_ZN13CssStyleSheetC2Ev+16841> <_ZN13CssStyleSheetC2Ev+21235> <_ZN11DoctreeNodeD2Ev+13496> <_ZN11DoctreeNodeD2Ev+6209> <_ZN8CustTabsC2EiiiPKc+42885> <_ZN8CustTabsC2EiiiPKc+45551> <_ZL8do_timerP16__CFRunLoopTimerPv+42> <__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__+20> <__CFRunLoopDoTimer+1075> <__CFRunLoopDoTimers+298> <__CFRunLoopRun+1841> <CFRunLoopRunSpecific+296> <RunCurrentEventLoopInMode+235> <ReceiveNextEventCommon+184> <_BlockUntilNextEventMatchingListInModeWithFilter+71> <_DPSNextEvent+1067> <-[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:]+454> <_Z7fl_waitd+150> <_Z21fl_mac_flush_and_waitd+155> <_ZN2Fl3runEv+19> <(null)+4361965094> <start+1> Mar 2 18:36:30 dillo[23010] <Error>: CGContextSetShouldAntialias: invalid context 0x0. Backtrace: <_Z15fl_text_extentsPKcRiS1_S1_S1_+80> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+1634> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+2707> <_ZN13CssStyleSheetC2Ev+16841> <_ZN13CssStyleSheetC2Ev+21235> <_ZN11DoctreeNodeD2Ev+13496> <_ZN11DoctreeNodeD2Ev+6209> <_ZN8CustTabsC2EiiiPKc+42885> <_ZN8CustTabsC2EiiiPKc+45551> <_ZL8do_timerP16__CFRunLoopTimerPv+42> <__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__+20> <__CFRunLoopDoTimer+1075> <__CFRunLoopDoTimers+298> <__CFRunLoopRun+1841> <CFRunLoopRunSpecific+296> <RunCurrentEventLoopInMode+235> <ReceiveNextEventCommon+184> <_BlockUntilNextEventMatchingListInModeWithFilter+71> <_DPSNextEvent+1067> <-[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:]+454> <_Z7fl_waitd+150> <_Z21fl_mac_flush_and_waitd+155> <_ZN2Fl3runEv+19> <(null)+4361965094> <start+1> Mar 2 18:36:30 dillo[23010] <Error>: CGContextSetTextPosition: invalid context 0x0. Backtrace: <_Z15fl_text_extentsPKcRiS1_S1_S1_+80> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+1634> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+2707> <_ZN13CssStyleSheetC2Ev+16841> <_ZN13CssStyleSheetC2Ev+21235> <_ZN11DoctreeNodeD2Ev+13496> <_ZN11DoctreeNodeD2Ev+6209> <_ZN8CustTabsC2EiiiPKc+42885> <_ZN8CustTabsC2EiiiPKc+45551> <_ZL8do_timerP16__CFRunLoopTimerPv+42> <__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__+20> <__CFRunLoopDoTimer+1075> <__CFRunLoopDoTimers+298> <__CFRunLoopRun+1841> <CFRunLoopRunSpecific+296> <RunCurrentEventLoopInMode+235> <ReceiveNextEventCommon+184> <_BlockUntilNextEventMatchingListInModeWithFilter+71> <_DPSNextEvent+1067> <-[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:]+454> <_Z7fl_waitd+150> <_Z21fl_mac_flush_and_waitd+155> <_ZN2Fl3runEv+19> <(null)+4361965094> <start+1> Mar 2 18:36:30 dillo[23010] <Error>: CGContextSetShouldAntialias: invalid context 0x0. Backtrace: <_Z15fl_text_extentsPKcRiS1_S1_S1_+80> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+1634> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+2707> <_ZN13CssStyleSheetC2Ev+16841> <_ZN13CssStyleSheetC2Ev+21235> <_ZN11DoctreeNodeD2Ev+13496> <_ZN11DoctreeNodeD2Ev+6209> <_ZN8CustTabsC2EiiiPKc+42885> <_ZN8CustTabsC2EiiiPKc+45551> <_ZL8do_timerP16__CFRunLoopTimerPv+42> <__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__+20> <__CFRunLoopDoTimer+1075> <__CFRunLoopDoTimers+298> <__CFRunLoopRun+1841> <CFRunLoopRunSpecific+296> <RunCurrentEventLoopInMode+235> <ReceiveNextEventCommon+184> <_BlockUntilNextEventMatchingListInModeWithFilter+71> <_DPSNextEvent+1067> <-[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:]+454> <_Z7fl_waitd+150> <_Z21fl_mac_flush_and_waitd+155> <_ZN2Fl3runEv+19> <(null)+4361965094> <start+1> Mar 2 18:36:30 dillo[23010] <Error>: CGContextSetShouldAntialias: invalid context 0x0. Backtrace: <_Z15fl_text_extentsPKcRiS1_S1_S1_+80> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+1634> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+2707> <_ZN13CssStyleSheetC2Ev+16841> <_ZN13CssStyleSheetC2Ev+21235> <_ZN11DoctreeNodeD2Ev+13496> <_ZN11DoctreeNodeD2Ev+6209> <_ZN8CustTabsC2EiiiPKc+42885> <_ZN8CustTabsC2EiiiPKc+45551> <_ZL8do_timerP16__CFRunLoopTimerPv+42> <__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__+20> <__CFRunLoopDoTimer+1075> <__CFRunLoopDoTimers+298> <__CFRunLoopRun+1841> <CFRunLoopRunSpecific+296> <RunCurrentEventLoopInMode+235> <ReceiveNextEventCommon+184> <_BlockUntilNextEventMatchingListInModeWithFilter+71> <_DPSNextEvent+1067> <-[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:]+454> <_Z7fl_waitd+150> <_Z21fl_mac_flush_and_waitd+155> <_ZN2Fl3runEv+19> <(null)+4361965094> <start+1> Mar 2 18:36:30 dillo[23010] <Error>: CGContextSetTextPosition: invalid context 0x0. Backtrace: <_Z15fl_text_extentsPKcRiS1_S1_S1_+80> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+1634> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+2707> <_ZN13CssStyleSheetC2Ev+16841> <_ZN13CssStyleSheetC2Ev+21235> <_ZN11DoctreeNodeD2Ev+13496> <_ZN11DoctreeNodeD2Ev+6209> <_ZN8CustTabsC2EiiiPKc+42885> <_ZN8CustTabsC2EiiiPKc+45551> <_ZL8do_timerP16__CFRunLoopTimerPv+42> <__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__+20> <__CFRunLoopDoTimer+1075> <__CFRunLoopDoTimers+298> <__CFRunLoopRun+1841> <CFRunLoopRunSpecific+296> <RunCurrentEventLoopInMode+235> <ReceiveNextEventCommon+184> <_BlockUntilNextEventMatchingListInModeWithFilter+71> <_DPSNextEvent+1067> <-[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:]+454> <_Z7fl_waitd+150> <_Z21fl_mac_flush_and_waitd+155> <_ZN2Fl3runEv+19> <(null)+4361965094> <start+1> Mar 2 18:36:30 dillo[23010] <Error>: CGContextSetShouldAntialias: invalid context 0x0. Backtrace: <_Z15fl_text_extentsPKcRiS1_S1_S1_+80> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+1634> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+2707> <_ZN13CssStyleSheetC2Ev+16841> <_ZN13CssStyleSheetC2Ev+21235> <_ZN11DoctreeNodeD2Ev+13496> <_ZN11DoctreeNodeD2Ev+6209> <_ZN8CustTabsC2EiiiPKc+42885> <_ZN8CustTabsC2EiiiPKc+45551> <_ZL8do_timerP16__CFRunLoopTimerPv+42> <__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__+20> <__CFRunLoopDoTimer+1075> <__CFRunLoopDoTimers+298> <__CFRunLoopRun+1841> <CFRunLoopRunSpecific+296> <RunCurrentEventLoopInMode+235> <ReceiveNextEventCommon+184> <_BlockUntilNextEventMatchingListInModeWithFilter+71> <_DPSNextEvent+1067> <-[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:]+454> <_Z7fl_waitd+150> <_Z21fl_mac_flush_and_waitd+155> <_ZN2Fl3runEv+19> <(null)+4361965094> <start+1> Mar 2 18:36:30 dillo[23010] <Error>: CGContextSetShouldAntialias: invalid context 0x0. Backtrace: <_Z15fl_text_extentsPKcRiS1_S1_S1_+80> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+1634> <_ZN2dw4fltk10FltkImgbuf11scaleBufferEPKhiiPhiiid+2707> <_ZN13CssStyleSheetC2Ev+16841> <_ZN13CssStyleSheetC2Ev+21235> <_ZN11DoctreeNodeD2Ev+13496> <_ZN11DoctreeNodeD2Ev+6209> <_ZN8CustTabsC2EiiiPKc+42885> <_ZN8CustTabsC2EiiiPKc+45551> <_ZL8do_timerP16__CFRunLoopTimerPv+42> <__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__+20> <__CFRunLoopDoTimer+1075> <__CFRunLoopDoTimers+298> <__CFRunLoopRun+1841> <CFRunLoopRunSpecific+296> <RunCurrentEventLoopInMode+235> <ReceiveNextEventCommon+184> <_BlockUntilNextEventMatchingListInModeWithFilter+71> <_DPSNextEvent+1067> <-[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:]+454> <_Z7fl_waitd+150> <_Z21fl_mac_flush_and_waitd+155> <_ZN2Fl3runEv+19> <(null)+4361965094> <start+1> a_Dicache_cleanup: length = 0 Thanks yves

March 2, 2016

Double buffering flicker on window resize.

by johnfound＠asm32.info

On Wed, 2 Mar 2016 21:48:22 +0100 Johannes Hofmann <Johannes.Hofmann at gmx.de> wrote: > > As buffered_drawing=2 uses Fl_Double_Window from FLTK which in turn > tries to use the Xorg DOUBLE-BUFFER extension, you might want to try > xdpyinfo | grep DOUBLE-BUFFER > to see if this extension is enabled on your system and either > disable or enable it in your xorg.conf to see if that makes a > difference. > DOUBLE-BUFFER extension is enabled and running on my system. I made some experiments disabling it in the config file and restarting X. Checked it's presence with "xdpyinfo | grep DOUBLE-BUFFER" and it was missing. Then the ugly flashing artifacts disappeared from Dillo and with buffered_drawing=2 the flickering still appears, visually similar to that of buffered_drawing=1, but much less intrusive. All tests are made by loading some page in the browser and then dragging the window edge in order to resize the window. -- http://fresh.flatassembler.net http://asm32.info John Found <johnfound at asm32.info>

March 2, 2016

Double buffering flicker on window resize.

by Johannes.Hofmann＠gmx.de

On Wed, Mar 02, 2016 at 06:41:21AM +0200, John Found wrote: > On Tue, 1 Mar 2016 22:54:34 +0100 > Johannes Hofmann <Johannes.Hofmann at gmx.de> wrote: > > > with buffered_drawing=2 dillo uses the Fl_Double_Window class from > > FLTK, so the result should be similar to e.g. the test/fonts program > > from FLTK. Do you have it available and can test how that program > > feels when resizing on your system? > > In my setup I only get some light flickering at the scroll bars with > > buffered_drawing=2. Whereas I see heavy flickering with > > buffered_drawing=0. > > Do you see any difference between buffered_drawing=0 and > > buffered_drawing=2? > > > > Yes. These are different kind of flickering. On buffered_drawing=0 I see > how Dillo redraws the page content on the window surface. No artifacts, > only normal redraws one after another. On buffered_drawing=1 is > approximately the same but a little bit rarely. > > While on buffered_drawing=2, when the user resize the window, the whole window becomes > full of garbage - this is specific kind of garbage. It happens when you reuse some > memory previously used to store images with different sizes and then allocate it for > a new image and draw it on the screen as it is. A mess of graphical scanlines, > rectangles full of color, distorted images of different kind. > > Unfortunately, I can't get screenshot, because it is a dynamic effect. After stopping > resizing window, the last redraw is OK. As buffered_drawing=2 uses Fl_Double_Window from FLTK which in turn tries to use the Xorg DOUBLE-BUFFER extension, you might want to try xdpyinfo | grep DOUBLE-BUFFER to see if this extension is enabled on your system and either disable or enable it in your xorg.conf to see if that makes a difference.

March 2, 2016

Dill 3.0.5 breaks on Mac OS

by Johannes.Hofmann＠gmx.de

On Tue, Mar 01, 2016 at 05:57:41PM -0500, Yves de Champlain wrote: > Hi > > It does the trick indeed. good, I'll commit this change > > I do get this message repeated many many times : > > Mar 1 17:55:52 dillo[4169] <Error>: CGContextSetShouldAntialias: invalid context 0x0. If you want to see the backtrace, please set CG_CONTEXT_SHOW_BACKTRACE environmental variable. what Mac OS and FLTK version are you running and how did you install FLTK. Also please set the environmental variable as suggested and post the output. Johannes > > Thanks > > yves > > > > > Le 28 f?vr. 2016 ? 04:17, Johannes Hofmann <Johannes.Hofmann at gmx.de> a ?crit : > > > > could you please try with attached patch applied? > > > > Cheers, > > Johannes > > > > On Fri, Feb 26, 2016 at 08:58:36PM -0500, Yves de Champlain wrote: > >> Hi > >> > >> As I said in a subsequent mail, 3.0.4 does not work either anymore > >> > >> yves > >> > >> > >>> Le 26 f?vr. 2016 ? 06:00, Johannes Hofmann <Johannes.Hofmann at gmx.de> a ?crit : > >>> > >>> interesting. could you please try again if dillo-3.0.4 still works > >>> with your current setup? > >>> > >>> Cheers, > >>> Johannes > >>> > >>> On Fri, Feb 26, 2016 at 01:29:43PM +0300, Martin Atukunda wrote: > >>>> I tried to send email about this very issue to this mailing list, but the > >>>> mail failed for some obscure reason. > >>>> > >>>> Thanks for bringing this up. > >>>> > >>>> Cheers > >>>> > >>>> - Martin - > >>>> On 23 Feb 2016 23:12, "Yves de Champlain" <yesyves at gmail.com> wrote: > >>>> > >>>>> Hi > >>>>> > >>>>> When compiling dillo 3.0.5 on Mac OS 10.11, I get : > >>>>> > >>>>> /usr/bin/c++ -DHAVE_CONFIG_H -I. -I.. -I.. > >>>>> -DDILLO_SYSCONF='"/opt/local/etc/dillo/"' > >>>>> -DDILLO_DOCDIR='"/opt/local/share/doc/dillo/"' -I/opt/local/include > >>>>> -I/usr/local/include -I/opt/local/include/libpng16 -I/opt/local/include > >>>>> -pipe -Os -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_THREAD_SAFE > >>>>> -D_REENTRANT -pipe -Os -m64 -Wall -W -Wno-unused-parameter -fno-rtti > >>>>> -fno-exceptions -MT xembed.o -MD -MP -MF .deps/xembed.Tpo -c -o xembed.o > >>>>> xembed.cc > >>>>> mv -f .deps/dpiapi.Tpo .deps/dpiapi.Po > >>>>> mv -f .deps/image.Tpo .deps/image.Po > >>>>> mv -f .deps/imgbuf.Tpo .deps/imgbuf.Po > >>>>> mv -f .deps/form.Tpo .deps/form.Po > >>>>> mv -f .deps/findbar.Tpo .deps/findbar.Po > >>>>> mv -f .deps/menu.Tpo .deps/menu.Po > >>>>> In file included from xembed.cc:18: > >>>>> In file included from /opt/local/include/FL/x.H:43: > >>>>> /opt/local/include/FL/mac.H:104:12: fatal error: '../src/Fl_Font.H' file > >>>>> not found > >>>>> # include "../src/Fl_Font.H" > >>>>> > >>>>> > >>>>> It seems that dillo is trying to use X but on Mac, but fltk is using > >>>>> quartz. > >>>>> > >>>>> The problem has been reported on many systems. > >>>>> > >>>>> Dillo 3.0.4 was working fine. > >>>>> > >>>>> Thanks > >>>>> > >>>>> yves > >>>>> > >>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> Dillo-dev mailing list > >>>>> Dillo-dev at dillo.org > >>>>> http://lists.dillo.org/cgi-bin/mailman/listinfo/dillo-dev > >>>>> > >>> > >>>> _______________________________________________ > >>>> Dillo-dev mailing list > >>>> Dillo-dev at dillo.org > >>>> http://lists.dillo.org/cgi-bin/mailman/listinfo/dillo-dev > >>> > >>> > >>> _______________________________________________ > >>> Dillo-dev mailing list > >>> Dillo-dev at dillo.org > >>> http://lists.dillo.org/cgi-bin/mailman/listinfo/dillo-dev > >> > > > > > > <xembed_mac.diff>_______________________________________________ > > Dillo-dev mailing list > > Dillo-dev at dillo.org > > http://lists.dillo.org/cgi-bin/mailman/listinfo/dillo-dev >

March 2, 2016

Dillo crash on HTTPS connection (to MS web site)

by eocene＠gmx.com

On Wed, Feb 24, 2016 at 11:41:48PM +0200, John Found wrote: > ** ERROR **: our TLS mystery error is: error:140C5042:SSL routines:ssl_undefined_function:called a function you should not call If this is indeed the same problem that apache, nginx, et al., are seeing, then the attached should suffice to fix it.

March 2, 2016