- Dillo-dev - lists.mailman3.com

Re: [Dillo-dev] Dillo on Windows fork

by Colin Michael Yates

Given that Linux is about choice, and the fact that we Linux users moan so much about MS apps not running on Linux, it kind of seems hypocrtical to support *only* Linux! Fair enough having a personal agenda, but enforcing it on others (i.e. being hostile) isn't really on. I am quite dissapointed now. I moved away from Microsoft to get rid of this kind of thing :) On Wed, 2003-09-03 at 08:09, robert w hall wrote: > In article <02d101c371a7$137a5fd0$0200a8c0@tbird>, Robin Rowe > <rower(a)MovieEditor.com> writes > >Colin, > > > >> Any chance of a downloadable exe? > > > >Yes I'd be glad to, but the Windows port is not ready yet for release. I got > >as far as the splash screen. Still more bugs to fix. Encouraging though. > > > >In response to my request for technical information about Dillo to make it > >easier for me to debug the Windows port, Jorge sent me an email off-list > >last week in which he told me, "you're on your own" and directed me to > >his interview at http://www.dillo.org/interview.html for the reason why. > >What Jorge says there is he is opposed to supporting Windows users as a > >matter of personal politics. > > Well, for me, one of the annoying things about M$ is it's policy of > aggressive obsolescence. Support for NT3.51, NT4, win95, win98 has > already gone - but these systems have life left in them and are > appropriate to the smaller machines of their time. > I would have thought supporting a browser to run on these earlier > machines would in no way be helping the Gates empire to 'world > domination', quite the reverse... > > Bob > >

Sept. 3, 2003

Re: [Dillo-dev] Dillo on Windows fork

by Robin Rowe

Robert, > Well, for me, one of the annoying things about M$ is it's policy of > aggressive obsolescence. Let's not debate the pros and cons of Microsoft. It isn't that interesting and anyone with an opinion is unlikely to change it. In my world, that is, motion picture animation and special effects, the O.S. situation is very different from elsewhere. If you read my articles in Linux Journal then you are aware that in motion picture production Linux dominates as the most popular O.S. on servers and desktops. Windows isn't even a close second. The largest corporate installations of Linux in the world are DreamWorks, ILM, and Disney. To support all operating systems -- even minor ones like Windows -- is a mark of professionalism where I come from. Cheers, Robin --------------------------------------------------------------------------- Robin.Rowe(a)MovieEditor.com Hollywood, California www.CinePaint.org Free motion picture and still image editing software

Sept. 3, 2003

Re: [Dillo-dev] Dillo configure cannot find zlib, jpeglib not libpng

by Sebastian Geerken

On Thu, Aug 14, Scorpio Rising wrote: > I have a configuration problem in Debian stable. > > The configure file cannot find/use the z, jpeg or png libs that are in > /usr/include. > > *** cannot locate***......disabling jpeg/png/libz > > I have tried the command line options and even hardcoding the paths in > configure.in to no avail. > > I have installed the dev-headers for these packages. If you haven't solved the problem otherwise ... Perhaps you have installed the wrong versions. With the following packages, dillo compiles and run fine for me: $ dpkg --list "*zlib*" "*libjpeg*" "*libpng*" Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-==============-==============-============================================ pn libcompress-zl <none> (no description available) pn libzlib-ruby <none> (no description available) un python-zlib <none> (no description available) un zlib <none> (no description available) pn zlib-bin <none> (no description available) pn zlib1 <none> (no description available) pn zlib1-altdev <none> (no description available) un zlib1-dev <none> (no description available) ii zlib1g 1.1.4-1 compression library - runtime ii zlib1g-dev 1.1.4-1 compression library - development pn zlibc <none> (no description available) un libjpeg-dev <none> (no description available) un libjpeg-gif <none> (no description available) pn libjpeg-mmx-de <none> (no description available) pn libjpeg-mmx-pr <none> (no description available) pn libjpeg-progs <none> (no description available) ii libjpeg62 6b-5 The Independent JPEG Group's JPEG runtime li ii libjpeg62-dev 6b-5 Development files for the IJG JPEG library un libjpeg6b <none> (no description available) un libjpegg-dev <none> (no description available) pn libpng-dev <none> (no description available) un libpng1-dev <none> (no description available) ii libpng2 1.0.12-3 PNG library - runtime ii libpng2-dev 1.0.12-3 PNG library - development ii libpng3 1.2.1-1.1 PNG library - runtime un libpng3-dev <none> (no description available) If you still fail with these packages, you should send your config.log to the list. Sebastian

Sept. 3, 2003

Re: [Dillo-dev] Dillo on Windows fork

by robert w hall

In article <02d101c371a7$137a5fd0$0200a8c0@tbird>, Robin Rowe <rower(a)MovieEditor.com> writes >Colin, > >> Any chance of a downloadable exe? > >Yes I'd be glad to, but the Windows port is not ready yet for release. I got >as far as the splash screen. Still more bugs to fix. Encouraging though. > >In response to my request for technical information about Dillo to make it >easier for me to debug the Windows port, Jorge sent me an email off-list >last week in which he told me, "you're on your own" and directed me to >his interview at http://www.dillo.org/interview.html for the reason why. >What Jorge says there is he is opposed to supporting Windows users as a >matter of personal politics. Well, for me, one of the annoying things about M$ is it's policy of aggressive obsolescence. Support for NT3.51, NT4, win95, win98 has already gone - but these systems have life left in them and are appropriate to the smaller machines of their time. I would have thought supporting a browser to run on these earlier machines would in no way be helping the Gates empire to 'world domination', quite the reverse... Bob -- robert w hall

Sept. 3, 2003

Re: [Dillo-dev] Problems compiling tab+frame patch on Mandrake and RH 7

by Kelson Vibber

On Tuesday 02 September 2003 2:05 am, Frank de Lange wrote: > These errors can be caused by mismatched autotools (when the one used to > create the configure script does not match the installed version). You can > try to run the autotools manually to recreate the files with your installed > versions of the autotools: Thanks! I've updated the RPM spec for the patched version to (a) check for automake and autoconf, and (b) run them before calling configure. So far, so good on fully-patched RH 7.2 and Mandrake 9.1. I can't test it on Mandrake 8.2 yet, because both the spare partition and UML filesystem have stopped working. I'll probably just start from a fresh Mdk 8.2 UML fs and reclaim the partition. RPMs for Mandrake 9.1 i586 and PPC will be up shortly. -- Kelson Vibber www.hyperborea.org

Sept. 3, 2003

Re: [Dillo-dev] Dillo on Win2k

by Robin Rowe

Robert, > any chance of a version that works on NT3.51 (on a 64Mb dx4-75 :-) ) Yes, a good chance. Likely to work on all Win9x flavors, too. As with *nix, will require testing on each platform. Cheers, Robin --------------------------------------------------------------------------- Robin.Rowe(a)MovieEditor.com Hollywood, California www.CinePaint.org Free motion picture and still image editing software

Sept. 2, 2003

Re: [Dillo-dev] Dillo on Windows fork

by Robin Rowe

Colin, > Any chance of a downloadable exe? Yes I'd be glad to, but the Windows port is not ready yet for release. I got as far as the splash screen. Still more bugs to fix. Encouraging though. In response to my request for technical information about Dillo to make it easier for me to debug the Windows port, Jorge sent me an email off-list last week in which he told me, "you're on your own" and directed me to his interview at http://www.dillo.org/interview.html for the reason why. What Jorge says there is he is opposed to supporting Windows users as a matter of personal politics. On Friday the 29th I sent an email to Jorge asking he reconsider, but he hasn't responded. The text of my message is below. I am not enclosing Jorge's message because I don't know if he intended that to be for the record. It seems that contributing to Dillo on Windows is unwelcome and requires forking it. I didn't come to the project with the idea that I would take it over and am a bit perplexed. I'm wondering how others who have been with the project longer may feel. Should Dillo for Windows go elsewhere? If yes, does anyone want to help with it? Thanks, Robin --------------------------------------------------------------------------- Robin.Rowe(a)MovieEditor.com Hollywood, California www.CinePaint.org Free motion picture and still image editing software ----- Original Message ----- From: "Robin Rowe" <rower(a)MovieEditor.com> To: "Jorge Arellano Cid" <jcid(a)softhome.net> Sent: Friday, August 29, 2003 7:04 PM Subject: Re: [Dillo-dev] Dillo Windows port > Jorge, > > Before discussing Windows issues I thought you may like to know that Tom > Huffman announced today on cinepaint-developers he has completed making > Dillo into a Linux help system plug-in for CinePaint. I anticipate we'll > start including Dillo with CinePaint in October. > > We've been using the GIMP tips widget as our help system. Everyone is > excited about Dillo as a big improvement. We plan to add an editing > capability to Dillo so we can edit our help pages from within Dillo. > > As I said, I'm not using Cygwin. Cygwin, clever as it is, has many > drawbacks. I'm running Dillo natively on Windows. > > It took me about 24 hours to accomplish that, to make some adjustments to > compile Dillo in Microsoft Visual C++. Mostly it involved adding > conditionals to change the names of included header files. Because your > design didn't anticipate that a few of the POSIX calls you use are not > available in Windows, it will take a little more work to replace those, to > complete the job. > > Although Windows is not 100% POSIX compatible, it is much more compatible > than you seem to think. POSIX-based programs can be made to work on Windows > without much trouble if you try. I haven't added any Windows API calls to > the existing Dillo code. > > Thanks for the link. Very interesting. You sound quite hostile to Windows > users as a matter of personal politics. > > May I ask, what does a policy of denying Dillo technical support to Windows > users accomplish? Do you intend to prevent people from using software they > have already paid for anyway? Should I throw away my copy of Windows 2000 to > accommodate your political views? To what point? You can't think it could > hurt Microsoft. You must know they aren't going to give me a refund. > > If you change your mind and decide to answer my questions about what a few > troublesome pieces of Dillo code are intended to do that would be nice. But, > if you prefer not to it is no big deal. I've ported much more difficult > programs without help. > > Cheers, > > Robin > > P.S. For anyone doesn't know, I lead the GTK1 for Windows and the Mac > GTK+OSX port projects in addition to CinePaint. > -------------------------------------------------------------------------- - > Robin.Rowe(a)MovieEditor.com Hollywood, California > www.CinePaint.org Free motion picture and still image editing software

Sept. 2, 2003

Re: [Dillo-dev] CPU hog with large selections

by Jorge Arellano Cid

Sebastian, > Hi, > > On Tue, Sep 02, Jorge Arellano Cid wrote: > > Yesterday I came accross this bug while reading: > > > > http://freshmeat.net/articles/view/889/ (272KB) > > > > If you go to a comment in the middle of the page, start > > selecting text with the mouse, and move it to the leftmost border > > (so it selects all the text up to the start), the CPU will hog > > and dillo will become unresponsive as it was in a dead loop. > > > > For instance, from the bottom line it takes 10 minutes to > > recover on a pentium II 233Mhz. I almost sure this can be > > improved. > > > > Please someone give a hand to fixing it. > > Fixed and comitted. Great! One less problem on the list. > BTW, there is (still) a memory leak in the selection (reproduce this > simply by selecting text several times), but this leak exists also in > the old code, so it is not likely to be caused by the recent changes. I understand. It'd be good if we can coordinate to review the tab + frames patch this week (and next). Do you have some time? Regards Jorge.- PS: I added the missing include for <string.h>

Sept. 2, 2003

Re: [Dillo-dev] CPU hog with large selections

by Sebastian Geerken

Hi, On Tue, Sep 02, Jorge Arellano Cid wrote: > Yesterday I came accross this bug while reading: > > http://freshmeat.net/articles/view/889/ (272KB) > > If you go to a comment in the middle of the page, start > selecting text with the mouse, and move it to the leftmost border > (so it selects all the text up to the start), the CPU will hog > and dillo will become unresponsive as it was in a dead loop. > > For instance, from the bottom line it takes 10 minutes to > recover on a pentium II 233Mhz. I almost sure this can be > improved. > > Please someone give a hand to fixing it. Fixed and comitted. BTW, there is (still) a memory leak in the selection (reproduce this simply by selecting text several times), but this leak exists also in the old code, so it is not likely to be caused by the recent changes. Sebastian

Sept. 2, 2003

Re: [Dillo-dev] Dillo on Win2k

by robert w hall

In article <1062518524.636.16.camel(a)xterm.home>, Colin Michael Yates <colin.yates(a)orange.net> writes >Any chance of a downloadable exe? any chance of a version that works on NT3.51 (on a 64Mb dx4-75 :-) ) -- robert w hall

Sept. 2, 2003