- Dillo-dev - lists.mailman3.com

Suggestion & patch for browser identification

by linux seaq

It's a good idea; Would be nice if also the info reported could be configured with dillorc. -- Andres Mauricio Mujica SEAQ SERVICIOS CIA LTDA www.seaq.com.co

July 9, 2003

Re: [Dillo-dev] Porting to Windows?

by Lars Segerlund

It seem's the windows platform is losing ground rather rapidly, so it might not be worth the trouble to support at soon to be obsolete system. ;-) Lars Segerlund. ( there is a smiley above, no flames :-) ). Andreas Tolfsen wrote: > I've just been wondering; Are there any future plans for porting Dillo > to the Windows platform? Or is Dillo to stay on GNU/Linux? > > I think porting to Windows would let Dillo have a much bigger audience > to speak to (since about 90% of the worlds computers run Windows). > > I just wondered if there were any plans? > > > Best regards for a wonderful open-source browser, > > Andreas Tolfsen > <ato(a)itnerd.net> > > > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)lists.auriga.wearlab.de > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

July 9, 2003

the same name ronnie!!!!!!

by ronnie

July 9, 2003

Suggestion & patch for browser identification (user-agent)

by Kelson Vibber

I know this is too late to even consider for 0.7.3, but I thought I'd get this out for discussion. I've been looking at browser statistics on my website, and started thinking about what various browsers do and don't report in their User-Agent identification. All report their name. Many report the rendering engine (Gecko, KHTML, etc.) Many also report the operating system and the type of system (with varying levels of detail), and some even report the language of the user interface. Here are some examples from my website's server logs: Mozilla/4.7 [en] (WinNT; U) Mozilla/5.0 (compatible; Konqueror/3.1; Linux) Mozilla/4.72 [en] (X11; U; Linux 2.4.18 i686) Opera/7.11 (Linux 2.4.20-18.9 i686; U) [en] Opera/6.0 (Macintosh; PPC Mac OS X; U) [en] Mozilla/4.0 (compatible; MSIE 5.22; Mac_PowerPC) Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030524 Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us) AppleWebKit/85 (KHTML, like Gecko) Safari/85 Some interesting notes: - Netscape and Mozilla always use "X11" for anything X-based, and have a separate field to indicate the actual OS (Linux, Solaris, *BSD, etc.) - Konqueror lets you configure the amount of detail you report. The example here is the default. - Most of the *nix-based strings use qhat you get from uname -sm or uname -srm. - Most browsers designed for Mac OS X report "PPC Mac OS X" - There are possible privacy/security implications of revealing too much information, like your system's kernel version or your primary language. I think that knowing the operating system is interesting, but much more than that probably isn't necessary, so I'd like to suggest one of the following syntaxes to extend the Dillo user-agent string: Dillo/<version> (<system>) Dillo/<version> (<platform>; <system>) Where <system> is the output of "uname -sm" (i.e. Linux PPC, FreeBSD i386, etc) and <platform> is of the form (Windows|Macintosh|X11|etc.) as used by Mozilla (see http://www.mozilla.org/build/revised-user-agent-strings.html ). This would result in identification like the following: Dillo/0.8 (Linux i386) Dillo/0.8 (FreeBSD i686) Dillo/0.8 (Linux PPC) Dillo/0.8 (PPC Mac OS X)* and so on, or perhaps: Dillo/0.8 (X11; Linux i386) Dillo/0.8 (X11; CYGWIN_NT-5.0 i686) to fit Netscape/Mozilla's pattern. * (Aside from the reversed order, Mac OS X would probably show up as Darwin unless a special case is made. This would probably mean setting the User-Agent string once and keeping it in memory instead of building it with each HTTP request. And for the longer syntax there's the issue that it still runs under X, so the platform would probably be X11 instead of Macintosh.) I have attached a quick patch which uses the utsname struct to create the first syntax, and I've tested it successfully on Linux and Cygwin on Intel hardware. So does anyone else think this is a good/bad/interesting idea? And is anyone interested in testing it on *BSD/Solaris/Mac/etc.? -- Kelson Vibber www.hyperborea.org

July 9, 2003

some newbie questions!!

by ronnic

hi all I have enjoied dillo and want make it support chinese (a challenge to me ^o^ ),but i encountered some questions: 1)I can not understand the CCC function modules; 2)How the dillo get the HTML documents after establish socket connect; 3)when getting the file how dillo write to the proper dw archtecture; (please tell me by using detail function ) thanks all !!!!! --http://www.eyou.com --ÎÈ¶š¿É¿¿µÄÃâ·Ñµç×ÓÐÅÏä ÓïÒôÓÊŒþ ÒÆ¶¯ÊéÇ© ÈÕÀú·þÎñ ÍøÂçŽæŽ¢...ÒÚÓÊÎŽŸ¡

July 9, 2003

Re: [Dillo-dev] Porting to Windows?

by Kelson Vibber

At 03:37 AM 7/7/2003, Andreas Tolfsen wrote: >I've just been wondering; Are there any future plans for porting Dillo to >the Windows platform? Or is Dillo to stay on GNU/Linux? Good question. (Although technically it's not Linux-only right now, it's Linux & Unix only.) Just for fun I tried building it on Windows 2000 with Cygwin. It seems to work fine, although I can't say I've done any serious stress testing. Note that you do need to download and compile glib and gtk+ <http://www.gtk.org/> and make one change to the glib source <http://www.cygwin.com/ml/cygwin-xfree/2002-07/msg00276.html>. Of course this is no real solution, because you have to: (1) Install Cygwin with XFree86, (2) Install Glib/GTK+, and (3) Run X every time you want to use Dillo. There is a port of GTK+ to Windows, though, which was originally done for the Windows port of GIMP <http://www.gimp.org/~tml/gimp/win32/>. I have no idea what else would be needed to port Dillo using these, or whether any of the main developers would think it was worth the effort. Kelson Vibber www.hyperborea.org

July 8, 2003

Re: Some news...

by Jorge Arellano Cid

Hi! > > This has been a very busy week. I didn't anticipate how much > work the dpid (dpi daemon) integration could take. Don't panic > though!, the code that binds it all is running (to some extent) > in my machine. The time consuming problem is that while making > the integration, a lot of design matters spring in, and they take > a lot of time to solve. > > The good news is that it all starts to shape into a more clear > design (the code is still hackish at parts, but it is clear what, > where and how to fix it). > > While working the gory details of it, I realized it'd be a good > idea to make the 0.7.3 release with what we have now (plus a > little bug fix we're working on with Sebastian). That way, > there'll be less pressure on us while polishing the new dpid > implementation, and hey!, it's been a long time since our last > release. > > I'll keep the CVS free of the dpid code until the 0.7.3 release > is done. For the meanwhile, I'll provide a tarball to the new > code. (and if I can't wrap the new code before Monday, I'll > provide a link to the latest dpid testing tarball I have). First, the final code for the 0.7.3 is on the CVS (unless you find a bug in it). It will be released by Wednesday, so please give it a hard test today and tomorrow! With regard to 0.8.0-pre (aka dillo with dpid), here's the good news: * Finally I have a tarball that does bookmarks and downloads with dpid (using wget)! It can handle multiple plugins and is working smoothly. I want to add one more plugin (at least) and update the documentation before commiting it to the CVS (after releasing 0.7.3 of course). For those very interested in studying it, please review: http://dillo.org/download/dpid4.tgz (not my tarball but the dpid testing suite itself) Cheers Jorge.-

July 7, 2003

Re: [Dillo-dev] When does dillo plan on getting ported to GTK2 and pango?

by Kelson Vibber

At 04:34 AM 7/7/2003, Timothy Beyer wrote: >As for the gtk2, I believe its already in dillo, I think I enabled it at >one point using --enable-gtk2 on ./configure (Correct me if I'm wrong) Out of curiosity, I tried this on my Linux box at work (Red Hat 9). It still built with GTK+ 1.2 (Try "ldd /path/to/dillo" and see what version it's linked to.) I then tried removing the GTK+ 1.2 development package, at which point configure couldn't detect GTK at all. Kelson Vibber www.hyperborea.org

July 7, 2003

Nostradamus

by Kelson Vibber

At 12:35 PM 7/5/2003, Jorge Arellano Cid wrote: > > "Come the millennium month 12, in the home > > of the greatest power, the village idiot will come > > forth to be acclaimed the leader."--Nostradamus 1555 > > Quite interesting tag! Is it really from Nostradamus? > Can you provide a URL to the full text of Nostradamus verses? No, it's not from Nostradamus, it's just a joke someone made up around the time of the election. I don't have a list of his full verses, but I often visit a site that investigates urban legends. Here's what they have to say about this one: http://www.snopes.com/humor/iftrue/nostra.htm Kelson Vibber www.hyperborea.org

July 7, 2003

Re: [Dillo-dev] When does dillo plan on getting ported to GTK2 and pango?

by Timothy Beyer

On Wed, 2 Jul 2003, Todd Slater wrote: As for the gtk2, I believe its already in dillo, I think I enabled it at one point using --enable-gtk2 on ./configure (Correct me if I'm wrong) > Please, no! Is it my imagination, or is everything slower with GTK2? No, not really, the performance should be roughly the same. (Actually gtk2 should be faster as it gets more efficient) A major factor is the engine you use. I ported the pixmap "AbsoluteE" theme to gtk2 and it was slower than a snail (gdk pixbuf). However, I run the mist (etria.org-blue) engines on my gtk1 and gtk2 themes and both are incredibly quick. One factor COULD be xft, (although I think its possible, although by no means a standard practice to enable xft on gtk1) which might slow things down a bit, but personally, I would stay away from a non-antialiased browser... Tim

July 7, 2003