- Dillo-dev - lists.mailman3.com

[Dillo-dev]Problems with the activation of the URL entry

by Sebastian Geerken

Hi! The current CVS version is supposed to visit the URL in the selection, when the user clicks with the middle mouse button on the "clear URL" button. However, I got it once working (strangely), but currently it does not work. I use Gtk+ version 1.2.10. The function Interface_entry_paste_selected first copies the selection into the entry (as you see from the comment, I did not really understand the code), and then calls gtk_widget_activate, which emits the activation signal of the widget, which is "activate" for GtkEntry, and normally emitted when the user presses the enter key within the entry. This signal is connected to the function a_Interface_entry_open_url. When a_Interface_entry_open_url is called in this case, gtk_editable_get_chars returns an empty string, it seems that the "real" copying of the selection in Interface_entry_paste_selected is somehow delayed. As workarounds, I see two possible solutions: 1. Also queueing our code in an idle function. The attached patch demonstrates this successfully, although it has to be cleaned up (in some cases, the active idle function has to be removed again). 2. Calling a_Interface_entry_open_url directly with the contents of the selection. (But how do I get the latter?) I'm not very familiar neither with selection in general (i.e. the protocols provided by ICCCM), nor with the mechanisms Gtk+ provides. If someone knows a better solution, please describe it (or send a patch). If not, I'd clean up and commit solution 1. Sebastian

June 14, 2004

Re: [Dillo-dev]building 0.8.1 on slack4.0 (libc5)

by robert w hall

In article <Pine.LNX.4.58.0406140954350.740(a)infinity.cl>, Jorge Arellano Cid <jcid(a)dillo.org> writes > > >On Sun, 13 Jun 2004, robert w hall wrote: > >> thanks, I'll try that (though I _did_ spot a rather dated reference to >> 3.9 in my browsings, which didn't actually help - referred to the >> problems with non-reentrant X IIRC, which I _suspect_ is not the root >> cause here) > >> [...] > >> Has anybody compiled under slack 4 (or equivalent) within the recent >> past? > > I've compiled and run Dillo on slackware since 3.6 and on every >following version. > > OK, mea culpa! After a torrid afternoon chasing round the ancient Xfree 3.3.3.1 Makefiles, (and lying about the libc major version in linux.cf!) I finally got something to compile which thought it was re-entrant, and that _does_ appear to have done the trick... (Still no libjpeg etc, but it appears to work without, and I may have enough to be able to ditch Netscape 3.04 at last) > Cheers > Jorge.- > >_______________________________________________ >Dillo-dev mailing list >Dillo-dev(a)lists.auriga.wearlab.de >http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev -- robert w hall

June 14, 2004

Re: [Dillo-dev]building 0.8.1 on slack4.0 (libc5)

by Jorge Arellano Cid

On Sun, 13 Jun 2004, robert w hall wrote: > thanks, I'll try that (though I _did_ spot a rather dated reference to > 3.9 in my browsings, which didn't actually help - referred to the > problems with non-reentrant X IIRC, which I _suspect_ is not the root > cause here) > [...] > Has anybody compiled under slack 4 (or equivalent) within the recent > past? I've compiled and run Dillo on slackware since 3.6 and on every following version. Cheers Jorge.-

June 14, 2004

Re: [Dillo-dev]Bug Meter suggestion

by Kyle Amon

> Netiquette forbids me to post a frank description of my immediate > response to this. That would be plain old etiquette. The uber-hip neologism conveys nothing beyond the meaning of it's eponymous source in this context. Furthermore, "Netiquette" was an extension of etiquette to encopmass things like not having a .signature file consisting of more than four lines and not using the internet for commercial purposes at all, by the way. Since the great barbarian seige of the internet, however, it has become abundantly clear that this once distictly meaningfull neologism is now little more than a vestigial anachronism used only by those without a proper historical frame of reference. > My more considered intellectual response is: > > *NO!* > > I will *never* use a program that automatically sends unsolicited > email. It is morally wrong to do so. My inbox already overflows with > auto-posted <unflattering_comparison_to_excreta> from > <unflattering_comparison_to_genitalia>s who don't care that I don't > want it. I will not join their ranks. I will not use a program that > requires me to join their ranks, or even makes it possible. Since your "considered *intellectual* response" is predicated on a moral foundation, it obviously isn't worth very much. Investigate the difference between reason and morality, and, while you're at it, lookup the meanings of C and B in UCBE. Also, since you evidently don't make the C and B spam distinction (as what constitutes spam is predominantly "in the inbox of the reciever"), you just have "join[ed] their ranks" as you clearly don't care that I didn't want this unsolicited email from you. Furthermore, I never suggested a requirement. I suggested a few options. Options are are nearly the antithesis of requirements. Relax. You're overreacting. Emotion over reason. > I very much admire the dillo project's commitment to HTML standards > and I want to support your efforts. But turning dillo into a > spam-generator is unacceptable. *Please* don't do it. I admire it as well. But again, what constitutes spam is largely a matter of opinion. For example, since I am not on the Dillo mailing list (I prefer to check the archives when I see fit), I consider semi-irrational, semi-hysterical direct email responses to one of my posts to be spam in my inbox. > > At the very least, along side the W3C and WDG validator links in the > > Bug Meter, a link/exec to send such an email should be provided. > > I'm OK with that. If dillo users *want* to email HTML bug reports to > webmasters then dillo should help them. I would probably use that > feature myself. But user confirmation *must* be mandatory. Again, I suggested two options, no requirements. > If this post is over-the-top then I apologise. But I don't want to > hide the fact that I feel strongly about this. Ditto. :-) -- Kyle -- Kyle Amon email: amonk(a)gnutec.com url: http://www.gnutec.com/~amonk/ KeyID 1024D/4EB96E44 Fingerprint = E9EC 0046 8487 23D7 C91C D757 7B2A 8AE9 4EB9 6E44 "The free man is not anti-American, but anti-imperial. America [now] revisits the time of colonizers drunk on their superiority, convinced of their liberating mission, and counting on reimbursing themselves directly." -- Regis Debray This email Copyright 2004 by Kyle Amon, Inc., a Florida corporation, 12032 Colonial Estates Lane, Riverview, FL 33569-6894: +1 (813) 689-4041 amonk(a)gnutec.com http://www.gnutec.com/~amonk/. All rights reserved.

June 13, 2004

Re: [Dillo-dev]Bug Meter suggestion

by Jeremy Henty

On Sat, Jun 05, 2004 at 07:58:30AM -0400, Kyle Amon wrote: > ... have dillo automatically email these error messages to > webmaster(a)wwwdomain.com Ahem, ... Netiquette forbids me to post a frank description of my immediate response to this. My more considered intellectual response is: *NO!* I will *never* use a program that automatically sends unsolicited email. It is morally wrong to do so. My inbox already overflows with auto-posted <unflattering_comparison_to_excreta> from <unflattering_comparison_to_genitalia>s who don't care that I don't want it. I will not join their ranks. I will not use a program that requires me to join their ranks, or even makes it possible. I very much admire the dillo project's commitment to HTML standards and I want to support your efforts. But turning dillo into a spam-generator is unacceptable. *Please* don't do it. > At the very least, along side the W3C and WDG validator links in the > Bug Meter, a link/exec to send such an email should be provided. I'm OK with that. If dillo users *want* to email HTML bug reports to webmasters then dillo should help them. I would probably use that feature myself. But user confirmation *must* be mandatory. If this post is over-the-top then I apologise. But I don't want to hide the fact that I feel strongly about this. Cheers, Jeremy

June 13, 2004

Re: [Dillo-dev]building 0.8.1 on slack4.0 (libc5)

by robert w hall

In article <Pine.LNX.4.58.0406122039430.740(a)infinity.cl>, Jorge Arellano Cid <jcid(a)dillo.org> writes > > Jorge thanks for reply, see below >On Sat, 12 Jun 2004, robert w hall wrote: > >> I'm trying to compile dillo 0.8.1 to use on my old 486-based laptop >> (with slack 4.0, which is libc5-based). I've compiled glib + gtk 1.2.10 >> from source, but have no other libs like libjpeg, libpng etc. >> >> The binary starts to run then collapses in >> gdk error - error 11 in X-server (or similar message) >> >> Any advice? > > Yes. Install the missing libraries! not got room! > > ... or run: > > ./configure --help > > to learn how to disable them (not recommended). But configure correctly reports/detects they're missing, so isn't that enough? > > > Also read this: > > http://article.gmane.org/gmane.comp.web.dillo.devel/1732/match=+slackware > > (looking for "slackware 3.9" in our mailing list will lead you >to the whole thread; that's how I found it). thanks, I'll try that (though I _did_ spot a rather dated reference to 3.9 in my browsings, which didn't actually help - referred to the problems with non-reentrant X IIRC, which I _suspect_ is not the root cause here) > > Cheers > Jorge.- > > 'To travel in hope is better than to arrive' Has anybody compiled under slack 4 (or equivalent) within the recent past? Bob -- robert w hall

June 13, 2004

Re: [Dillo-dev]building 0.8.1 on slack4.0 (libc5)

by Jorge Arellano Cid

On Sat, 12 Jun 2004, robert w hall wrote: > I'm trying to compile dillo 0.8.1 to use on my old 486-based laptop > (with slack 4.0, which is libc5-based). I've compiled glib + gtk 1.2.10 > from source, but have no other libs like libjpeg, libpng etc. > > The binary starts to run then collapses in > gdk error - error 11 in X-server (or similar message) > > Any advice? Yes. Install the missing libraries! ... or run: ./configure --help to learn how to disable them (not recommended). Also read this: http://article.gmane.org/gmane.comp.web.dillo.devel/1732/match=+slackware (looking for "slackware 3.9" in our mailing list will lead you to the whole thread; that's how I found it). Cheers Jorge.-

June 13, 2004

[Dillo-dev]building 0.8.1 on slack4.0 (libc5)

by robert w hall

I'm trying to compile dillo 0.8.1 to use on my old 486-based laptop (with slack 4.0, which is libc5-based). I've compiled glib + gtk 1.2.10 from source, but have no other libs like libjpeg, libpng etc. The binary starts to run then collapses in gdk error - error 11 in X-server (or similar message) Any advice? -- robert w hall

June 12, 2004

Re: [Dillo-dev]Some remarks on the UI

by Jorge Arellano Cid

On Thu, 10 Jun 2004, Sebastian Geerken wrote: > > [...] > > > > > Furthermore, it should not have a relief, compare to the "Hide > > > > > Controls" button. > > > > > > Also fixed, I've removed the relief. > > > > Yes, the toolbar icons and the "Hide controls" one are OK > > without a relief, but after watching how the bug-meter button > > looks without a relief, and how much it hints the user of being a > > button, I'd much prefer to have the relief back. > > > > Note that the "Hide controls" button has a drawed frame around > > that helps getting the idea of it being a button! Perhaps a more > > orthogonal way of doing it is to have a relief for both, but > > it's simpler to keep it as it was. > > I'd have a further suggestion: Make the right part of the status bar > more look like a tool bar, and keep the reliefs hidden. The number of > bugs should then move out of the button. Something like: > > | viewport | > +-------------------------------------+--------------+-+-----+ > | URLs etc. | 3 bugs found |#| B H | > +-------------------------------------+--------------+-+-----+ > > "B" is the bugmeter button, "H" is the "Hide controls" button, and "#" > is a handle to drag the new button bar out of the window. When designing the bug-meter interface, it took some time to find a way that made the appropriate "gestalt" out of the meter. Separating the bug number from the bug-button requires a new hint because the former gestaltic perception is lost. > Otherwise, I'd prefer both buttons to have a relief. OK, let's have a relief on both. Cheers Jorge.-

June 10, 2004

Re: [Dillo-dev]Some remarks on the UI

by Sebastian Geerken

On Tue, Jun 08, Jorge Arellano Cid wrote: > [...] > * The "View Page Bugs" menu item for the page menu doesn't > work. It went to a segfault once. NOT fixed. Fixed. I removed it temporally, since the signature of the callback did not fit, and forgot it before comitting. I hope that the segfalt does not occur anymore (I could not reproduce it). > [...] > It was nice to see the middle-click over "clear-url" button as > a shortcut for paste. It'd be perfect if the entry can be focused > at the same time. Done. > [...] > > > > Furthermore, it should not have a relief, compare to the "Hide > > > > Controls" button. > > > > Also fixed, I've removed the relief. > > Yes, the toolbar icons and the "Hide controls" one are OK > without a relief, but after watching how the bug-meter button > looks without a relief, and how much it hints the user of being a > button, I'd much prefer to have the relief back. > > Note that the "Hide controls" button has a drawed frame around > that helps getting the idea of it being a button! Perhaps a more > orthogonal way of doing it is to have a relief for both, but > it's simpler to keep it as it was. I'd have a further suggestion: Make the right part of the status bar more look like a tool bar, and keep the reliefs hidden. The number of bugs should then move out of the button. Something like: | viewport | +-------------------------------------+--------------+-+-----+ | URLs etc. | 3 bugs found |#| B H | +-------------------------------------+--------------+-+-----+ "B" is the bugmeter button, "H" is the "Hide controls" button, and "#" is a handle to drag the new button bar out of the window. Otherwise, I'd prefer both buttons to have a relief. Sebastian

June 10, 2004