- Dillo-dev - lists.mailman3.com

printer symbols in dillo

by Johannes.Hofmann＠gmx.de

On Sat, May 28, 2011 at 01:57:23AM +0000, corvid wrote: > I wrote: > > I put dillo through nm, and I saw a bunch of > > Fl_Paged_Device, Fl_PostScript_Printer, T Fl_PostScript_File_Device > > in there. > > > > I didn't pay any attention when they were all enthusiastic about printer > > support for a while there. Is there a justifiable reason that this gets > > pulled in, as opposed to an oversight on their part when #ifdef'ing > > or something? > > Turns out there's a > > if (Fl_Surface_Device::surface()->class_name() == Fl_Printer::class_id) > > in Fl_Text_Display.cxx that pulls it all in. > I'll have to ask them whether there's a reasonable way for them to > do something about this someday... Ah, now I get your point... Would be nice indeed if we could get rid of the Fl_Printer stuff as long as we don't use it. Cheers, Johannes

May 28, 2011

printer symbols in dillo

by Johannes.Hofmann＠gmx.de

On Fri, May 27, 2011 at 10:16:38PM +0000, corvid wrote: > > I put dillo through nm, and I saw a bunch of > Fl_Paged_Device, Fl_PostScript_Printer, T Fl_PostScript_File_Device > in there. > > I didn't pay any attention when they were all enthusiastic about printer > support for a while there. Is there a justifiable reason that this gets > pulled in, as opposed to an oversight on their part when #ifdef'ing > or something? It's part of fltk-1.3: http://fltk.org/doc-1.3/classFl__Device.html I never tried it, but it should be possible to draw to a Fl_PostScript_Graphics_Driver just as drawing to the screen. OTOH it would also be simple enough to write dw::core::View that outputs Postscript. I'm not sure what would be the way to go if we want to add printing support. Cheers, Johannes

May 28, 2011

printer symbols in dillo

by corvid＠lavabit.com

I wrote: > I put dillo through nm, and I saw a bunch of > Fl_Paged_Device, Fl_PostScript_Printer, T Fl_PostScript_File_Device > in there. > > I didn't pay any attention when they were all enthusiastic about printer > support for a while there. Is there a justifiable reason that this gets > pulled in, as opposed to an oversight on their part when #ifdef'ing > or something? Turns out there's a if (Fl_Surface_Device::surface()->class_name() == Fl_Printer::class_id) in Fl_Text_Display.cxx that pulls it all in. I'll have to ask them whether there's a reasonable way for them to do something about this someday...

May 28, 2011

Connection problems on Mac OS X 10.6.7

by rf.opensource＠gmail.com

On Fri, May 27, 2011 at 3:53 PM, Jorge Arellano Cid <jcid(a)dillo.org> wrote: > On Fri, May 27, 2011 at 03:25:32PM -0500, reza farivar wrote: > > On Fri, May 27, 2011 at 3:18 PM, Jorge Arellano Cid <jcid(a)dillo.org> > wrote: > > > > > On Fri, May 27, 2011 at 01:53:08PM -0500, reza farivar wrote: > > > > On Fri, May 27, 2011 at 12:46 PM, Benjamin Johnson < > > > obeythepenguin(a)gmail.com > > > > > wrote: > > > > > > > > > On Fri, 27 May 2011 13:38:43 -0400, reza farivar < > > > rf.opensource(a)gmail.com> > > > > > wrote: > > > > > > > > > > Yes. Well, the only plugin I could see is the save button on the > > > panel, > > > > >> and > > > > >> it can successfully navigate the filesystem and save a page > correctly. > > > > >> > > > > > > > > > > That one isn't a plugin, actually. Does the bookmarks button work? > > > > > > > > > > Yes, bookmarks work. (This is a bit of strange implementation of > > > bookmarks, > > > > no? took me a bit to find out difference of section and item) > > > > > > Good! > > > > > > If you can see the html page from the bookmarks, it means the > > > whole dpi framework is working on Mac; they communicate using > > > sockets. > > > > > > So it seems the main thing pending is socket support in fl_wait > > > for Mac (see my previous email). > > > > > > > Yes, I also think it's the source of this problem (see my other email). > > > > But what really perplexes me is that this happens only when I enter a URL > > manually. When I follow links from one page to another it never happens. > Are > > you guys using different (FLTK) functions when opening a new page or > > following a links (whether in the same tab or in a new tab)? > > No, but when you hit ENTER, FLTK has a chance to queue events > and zero-wait timeouts for the widget callback and necessary > stuff. OTOH, clicking a link goes another path (inside dillo). > > Can you point me to parts of code for either of these two code paths? Filename / line number should suffice. > > > And it seems that as Dillo "warms up" I get less of this problem... > > Timimg issues are moody. > e.g. Have you tried dillo listening a good mp3? :-) > > BTW, good you asked Manolo G. > (FWIW, FLTK2 has code for socket events in Mac). > > -- > Cheers > Jorge.- > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

May 28, 2011

printer symbols in dillo

by corvid＠lavabit.com

I put dillo through nm, and I saw a bunch of Fl_Paged_Device, Fl_PostScript_Printer, T Fl_PostScript_File_Device in there. I didn't pay any attention when they were all enthusiastic about printer support for a while there. Is there a justifiable reason that this gets pulled in, as opposed to an oversight on their part when #ifdef'ing or something?

May 28, 2011

Connection problems on Mac OS X 10.6.7

by rf.opensource＠gmail.com

On Fri, May 27, 2011 at 4:57 PM, Benjamin Johnson <obeythepenguin(a)gmail.com>wrote: > On Fri, 27 May 2011 17:22:47 -0400, reza farivar <rf.opensource(a)gmail.com> > wrote: > > Thanks Benjamin. I suggest we wait for a day or two before committing to >> back-porting. As Jorge mentioned, it might not be related to the sockets >> after all, in which case it might be fixed with his small patch. I also >> like >> to see what Manolo has to say on the issue, he seems to be quite active >> these days (lots of patches committed to FLTK1.3 in the last month). >> > > Well, for what it's worth, there were actually two different things on > Windows. First sockets didn't work at all, because of a broken select > implementation, then it had 100% CPU usage because it didn't check if FLTK > was idling. I sent in a patch for both and never heard back, though then > again no one's really maintaining 2.x any more. > Well if sockets didn't work at all on win32 you couldn't get any network traffic, right? So you probably had to fix the socket code anyway. Here, I do have network traffic, it just seems it needs a push to get stuff working. Maybe the event queue has to have more than one element to return something? I'm confused. By the way, unfortunately Jorge's patch (setting timeout to something other than 0.0) didn't solve the problem. So I'm running out of ideas, unless Manolo comes to rescue ;-) > Anyway, good luck, and hope you get a response! :-) > > ~Benjamin >

May 28, 2011

Connection problems on Mac OS X 10.6.7

by rf.opensource＠gmail.com

On Fri, May 27, 2011 at 3:53 PM, Jorge Arellano Cid <jcid(a)dillo.org> wrote: > On Fri, May 27, 2011 at 03:25:32PM -0500, reza farivar wrote: > > On Fri, May 27, 2011 at 3:18 PM, Jorge Arellano Cid <jcid(a)dillo.org> > wrote: > > > > > On Fri, May 27, 2011 at 01:53:08PM -0500, reza farivar wrote: > > > > On Fri, May 27, 2011 at 12:46 PM, Benjamin Johnson < > > > obeythepenguin(a)gmail.com > > > > > wrote: > > > > > > > > > On Fri, 27 May 2011 13:38:43 -0400, reza farivar < > > > rf.opensource(a)gmail.com> > > > > > wrote: > > > > > > > > > > Yes. Well, the only plugin I could see is the save button on the > > > panel, > > > > >> and > > > > >> it can successfully navigate the filesystem and save a page > correctly. > > > > >> > > > > > > > > > > That one isn't a plugin, actually. Does the bookmarks button work? > > > > > > > > > > Yes, bookmarks work. (This is a bit of strange implementation of > > > bookmarks, > > > > no? took me a bit to find out difference of section and item) > > > > > > Good! > > > > > > If you can see the html page from the bookmarks, it means the > > > whole dpi framework is working on Mac; they communicate using > > > sockets. > > > > > > So it seems the main thing pending is socket support in fl_wait > > > for Mac (see my previous email). > > > > > > > Yes, I also think it's the source of this problem (see my other email). > > > > But what really perplexes me is that this happens only when I enter a URL > > manually. When I follow links from one page to another it never happens. > Are > > you guys using different (FLTK) functions when opening a new page or > > following a links (whether in the same tab or in a new tab)? > > No, but when you hit ENTER, FLTK has a chance to queue events > and zero-wait timeouts for the widget callback and necessary > stuff. OTOH, clicking a link goes another path (inside dillo). > > That can explain it. Well, then your patch might have a chance, if it's not really a socket issue. I'll give it a try later tonight. > > > And it seems that as Dillo "warms up" I get less of this problem... > > Timimg issues are moody. > e.g. Have you tried dillo listening a good mp3? :-) > :-) > > BTW, good you asked Manolo G. > (FWIW, FLTK2 has code for socket events in Mac). > > Yes, I found it in FLTK2. It turns out fl_wait in FLTK2 (in src/osx/run.cxx) is a complex function, while the equivalent incomplete function in 1.3 only a couple of lines. I think it's best let FLTK guys handle it. -- > Cheers > Jorge.- > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

May 27, 2011

Connection problems on Mac OS X 10.6.7

by obeythepenguin＠gmail.com

On Fri, 27 May 2011 16:53:40 -0400, Jorge Arellano Cid <jcid(a)dillo.org> wrote: > (FWIW, FLTK2 has code for socket events in Mac). Might be worth backporting, assuming 2.x's implementation is halfway decent... though the Windows version was so broken, I had to backport from 1.3! Anyway, I think I remember that part of the code, so I'll be happy to provide whatever help I can. I do remember fl_wait is probably the nastiest function I've ever worked on, though the select call is the very least of its problems. ~Benjamin

May 27, 2011

Connection problems on Mac OS X 10.6.7

by jcid＠dillo.org

On Fri, May 27, 2011 at 03:25:32PM -0500, reza farivar wrote: > On Fri, May 27, 2011 at 3:18 PM, Jorge Arellano Cid <jcid(a)dillo.org> wrote: > > > On Fri, May 27, 2011 at 01:53:08PM -0500, reza farivar wrote: > > > On Fri, May 27, 2011 at 12:46 PM, Benjamin Johnson < > > obeythepenguin(a)gmail.com > > > > wrote: > > > > > > > On Fri, 27 May 2011 13:38:43 -0400, reza farivar < > > rf.opensource(a)gmail.com> > > > > wrote: > > > > > > > > Yes. Well, the only plugin I could see is the save button on the > > panel, > > > >> and > > > >> it can successfully navigate the filesystem and save a page correctly. > > > >> > > > > > > > > That one isn't a plugin, actually. Does the bookmarks button work? > > > > > > > > Yes, bookmarks work. (This is a bit of strange implementation of > > bookmarks, > > > no? took me a bit to find out difference of section and item) > > > > Good! > > > > If you can see the html page from the bookmarks, it means the > > whole dpi framework is working on Mac; they communicate using > > sockets. > > > > So it seems the main thing pending is socket support in fl_wait > > for Mac (see my previous email). > > > > Yes, I also think it's the source of this problem (see my other email). > > But what really perplexes me is that this happens only when I enter a URL > manually. When I follow links from one page to another it never happens. Are > you guys using different (FLTK) functions when opening a new page or > following a links (whether in the same tab or in a new tab)? No, but when you hit ENTER, FLTK has a chance to queue events and zero-wait timeouts for the widget callback and necessary stuff. OTOH, clicking a link goes another path (inside dillo). > And it seems that as Dillo "warms up" I get less of this problem... Timimg issues are moody. e.g. Have you tried dillo listening a good mp3? :-) BTW, good you asked Manolo G. (FWIW, FLTK2 has code for socket events in Mac). -- Cheers Jorge.-

May 27, 2011

Connection problems on Mac OS X 10.6.7

by obeythepenguin＠gmail.com

On Fri, 27 May 2011 16:19:23 -0400, reza farivar <rf.opensource(a)gmail.com> wrote: > I'll wait a few hours to see if I get a response back from Manolo, > otherwise > I'll give his patch a try. However, FL_wait in linux version of FLTK-1.3 > uses "select" which can return socket events, while the mac version > doesn't > have that. That's almost certainly it. I should have looked closer at that part of the file, really, since that's where a lot of Windows problems were, too -- it seems FLTK really can't be bothered testing this stuff on non-Linux platforms. One last thing you could try while you're waiting: force it to use Fl_mac.cxx instead of Fl_cocoa.mm, and compile FLTK and Dillo as 32-bit. Offhand I have no idea how to do that, since I don't own a Mac, but I understand 32-bit apps can still use the old Carbon API (unlike 64-bit, which have to use Cocoa). ~Benjamin

May 27, 2011