- Dillo-dev - lists.mailman3.com

Re: [Dillo-dev]dillo-0.8.1.tar.bz2 final on ps2
by Jorge Arellano Cid May 14, 2004

May 14, 2004

On Fri, 14 May 2004, robert w hall wrote: > works OK on playstation2-linux with a 2.2.21 kernel (from xrhino). > I haven't tried it on the default (sony) 2.2.1 kernel (kids seem to have > deleted it!) - but dimly recollect pthreads is a library not a kernel > feature, (so it shouldn't matter???) POSIX threads is one of "those" complex matters. It depends on several things including the kernel and glibc. To add flavour, Linux comes/came with linux threads, which is close to POSIX but not fully. The New POSIX Threads Library (NPTL) is POSIX compatible, and requires special kernel threading (as of 2.5.36), glibc 2.3 and other bindings (RedHat 9 was going to be the first to provide such environment). Furthermore, there are several different threading libraries among the platforms we support, so go figure! You can read much more than you wanted to know here: http://lwn.net/Articles/10465/ http://people.redhat.com/drepper/nptl-design.pdf As you may have begun to suspect after this short exposition, it's hard to know, and certainly I don't know, whether it will also run with Sony's 2.2.1 kernel! :-) Regards Jorge.-

1 0

[Dillo-dev]pre release
by Frank W McCormick May 13, 2004

May 13, 2004

Hi all Compiled and running the pre on Linux 2.4.24. No problems yet, but one thing that's been bothering me since Dillo was given DL capabilities....right clicking on a direct link gives you the DL but were it not for the eth0 indicator in ICEWM I wouldn't have any indication that DL was going ahead. Is this normal ? -- -------------- Frank McCormick Montreal --------------

2 1

[Dillo-dev]Re: null byte in HTML
by Jorge Arellano Cid May 13, 2004

May 13, 2004

---------- Forwarded message ---------- Date: Thu, 13 May 2004 12:33:13 +0300 (EEST) From: Jukka K. Korpela <jkorpela(a)cs.tut.fi> To: Jorge Arellano Cid <jcid(a)dillo.org> Subject: Re: Is the null byte allowed in HTML? On Wed, 12 May 2004, Jorge Arellano Cid wrote: > I can't yet found whether the null byte character is allowed in > HTML. Can you shed some light on this? It is not. You could use http://validator.w3.org to check for disallowed characters (it reports "non SGML character number 0"), but the ultimate reference is a) for HTML 4, the SGML declaration http://www.w3.org/TR/html4/sgml/sgmldecl.html where UNUSED effectively means 'disallowed' b) for XHTML, the XML specification, see http://www.w3.org/TR/REC-xml/#charsets which say, among other things, that all characters below 9 (HT) are disallowed. Thanks for a good question - I'm just finalizing a book on XHTML (in Finnish, sorry) and I realized that I had forgotten to discuss the character issue in sufficient detail. (I just realized that various generators may produce data with control characters.) -- Jukka "Yucca" Korpela, http://www.cs.tut.fi/~jkorpela/

2 1

[Dillo-dev]null byte in HTML
by Jorge Arellano Cid May 12, 2004

May 12, 2004

Hi there! Does anyone know whether a null-byte ('\0') is allowed inside HTML or SGML or XML? Cheers Jorge.-

1 0

[Dillo-dev]download problem on OpenBSD
by Riccardo Mottola May 11, 2004

May 11, 2004

Hello, using pre2 I went to sourceforge do download a file. On the mirror page I selected one and clicked on the "here" message for the non-stadard refresh which gives a direct link to the file (I could use it for d/l with wget). Clicking on it brought up a file location requester, I selected my home directory and gave ok. Dillo crashed with: Nav_open_url: Url=>http://prdownloads.sourceforge.net/ayttm/ayttm-0.4.6.tar.gz?use_mirror=hean…< Connecting to 66.35.250.217 Nav_open_url: Url=>http://heanet.dl.sourceforge.net/sourceforge/ayttm/ayttm-0.4.6.tar.gz< Dns_server [0]: heanet.dl.sourceforge.net is 0x721cb8 Connecting to 193.1.219.87 HTTP warning: Unhandled MIME type: <application/x-gzip> dpi.c:71: a_Dpi_rd_dpi_socket_dir: fopen : No such file or directory - /home/multix/.dillo/dpi_socket_dir debug_msg - init_sockdir: The dpi_socket_dir file does not exist dpid started Riccardo

2 2

Re: [Dillo-dev]dillo interface and motif, athena etc
by Riccardo Mottola May 11, 2004

May 11, 2004

david feldman wrote: > > I think your questions are very good, I hope you get good answer! > unfortunately there was no follow up. I wonder if anyone else beside you was interested. -R

2 1

[Dillo-dev]BUG#522
by Jorge Arellano Cid May 10, 2004

May 10, 2004

Hi, Can anyone reproduce BUG#522? 522 Impact: soft error At: run time Type: crash Comments: Url=>http://www.rti-zone.org/dillo/Html.testsuite/jorge/c2.html< Gdk-ERROR **: BadValue (integer parameter out of range for operation) serial 4689 error_code 2 request_code 45 minor_code 0 HTReproduce: debian unstable WorkedBy: nobody Cheers Jorge.-

2 1

Re: [Dillo-dev]BUG#522
by Jorge Arellano Cid May 10, 2004

May 10, 2004

On Mon, 10 May 2004, Riccardo Mottola wrote: > Jorge Arellano Cid wrote: > > > > Hi, > > > > Can anyone reproduce BUG#522? > > [...] > > No I cannot reproduce it on solaris. > > I compiled dillo on Solaris, UltraSparc too (alyazs solaris 2.6, gcc > 3.3) You might add this to the compatibility list too. So we have: Solaris 2.6, gcc 3.3, Sparc v8 processor (=32bit) Solaris 2.6, gcc 3.3, UltraSparc (64bit?) What SunOS do they report? Cheers Jorge.-

1 0

[Dillo-dev]dillo-0.8.1-pre2.tar.bz2
by Jorge Arellano Cid May 10, 2004

May 10, 2004

Hi there! It took a long time, but finally, dillo-0.8.1-pre2.tar.bz2 is ready for download. The problem was that the patch for the problem of left-clicking an unhandled MIME type involved changes, inside the cache module, that were not trivial. I pondered the situation carefully trying to decide whether to make the patch and delay the next release, or leave it for 0.8.2. After studying the situation and developing a patch, important changes were made in the cache (for instance all the cached URLs use new code now, and the main scheduler was also changed, and the posibility of deleting an active URL-transfer was made possible). After all that, it only remained to offer a download dialog for the aborted transfer, and as the patch was already major, I went ahead and the result was one of those improvements you can't leave out. What does it do? well, now you can left-click on any URL; if it happens to be of an unhandled MIME type, the transfer is aborted, and a download dialog appears to offer the possibility of saving the resource locally. Simple and clean. Now you can click carelessly on those fake-download links from SF until you reach the real source ;). The tradeoff: the possibility of labelling this release as "beta stable" is not as clear as before. This tarball requires plenty of testing, so please download it and give it a hard time! Any use of the browser serves, specially testing the new download feature and multiple windows at the same time. Get it from: http://www.dillo.org/download/dillo-0.8.1-pre2.tar.bz2 and report back to dillo-dev. Cheers Jorge.- PS: Kudos are also welcome! ;)

3 6

[Dillo-dev]compile problems on AIX + gcc
by Riccardo Mottola May 7, 2004

May 7, 2004

Hello, I'm trying to compile 0.8.1-pre1 on AIX 4.1 : One never knows, maybe som4e progress was made :) I had still to use CFLAGS="-lpthreads" to have configure pthread working at configure. I notice the following warnings gcc -DHAVE_CONFIG_H -I. -I. -I.. -DDILLORC_SYS='"/usr/local/etc/dillorc"' -I/u sr/local/include -I/usr/local/include/gtk-1.2 -I/usr/local/include/glib-1.2 -I/u sr/local/lib/glib/include -lpthreads -D_REENTRANT -D_THREAD_SAFE -Wall -Waggreg ate-return -c `test -f 'dw_bullet.c' || echo './'`dw_bullet.c gcc: -lpthreads: linker input file unused since linking not done should I have used LDFLAGS or something else? isn't there a more elegant solution to work around this pthread regnition problem? like a configure option? Cheers, Riccardo

1 0

[Dillo-dev]Re: about gtk on solaris 2.6
by Jorge Arellano Cid May 6, 2004

May 6, 2004

Riccardo, On Thu, 6 May 2004, Riccardo Mottola wrote: > > Hey Jorge, > > just a quick precisation. On the box where i have the old 0.7.3 dillo > which gives GTK errors, I have GIMP installed and that one works fine, I > have edited quite some images. > > SO I suspect it is something in the way dillo calls GTK that could > trigger the error, before saying GTK is bugged on that platform totally. There may be some good news for you: Try this patch: diff -pru dillo/src/dillo.c dillo-0.8.0/src/dillo.c --- dillo/src/dillo.c 2004-04-21 16:47:34.000000000 -0400 +++ dillo-0.8.0/src/dillo.c 2004-05-06 11:11:31.000000000 -0400 @@ -216,6 +216,8 @@ gint main(int argc, char *argv[]) /* Initialize GUI and parse GTK related args */ gtk_init(&argc, &argv); gdk_rgb_init(); + gtk_widget_set_default_colormap (gdk_rgb_get_cmap()); + gtk_widget_set_default_visual (gdk_rgb_get_visual()); /* Handle command line options */ while ((opt_flg = Dillo_get_opt(Options, argc, argv, &opt_argv, &idx))) { It fixes the colormap and visual detection/settings on some systems. The documentation is a bit vague about this calls, they are deprecated now, formerly suggested as initialization for most cases and removed from theGTK+2.0 API (with compatibility defines). If you're lucky, it may help with AIX too. Please test it and report. Note: The patch is in CVS now, but use a "pre1" patched tarball for the test. That asserts the use of the same configure script. Cheers Jorge.-

1 0

[Dillo-dev]downloads and pre2
by Jorge Arellano Cid May 6, 2004

May 6, 2004

On Tue, 4 May 2004, Yves de Champlain wrote: > Hi > [...] > Everything works fine except for this : > > av_open_url: Url=>http://ftp.gnu.org/gnu/ddd/ddd-3.2.1.tar.gz< > Connecting to 199.232.41.7 > warning: Unhandled MIME type: <application/x-tar> > > ** CRITICAL **: file web.c: line 57 (a_Web_dispatch_by_type): assertion > `dw != NULL' failed. > > Of course, this does not start any download but after this, > I still get messages in the shell but I will > not have those from wget once I do "save link as" > like I have if I do "save link as" before. Effectively, a left click on a non-dillo-viewable MIME type URL triggers this error message. The code inside dillo assigns it to a "null-client" which means it continues to download but it's "ignored". This has some side effects, one of them is the transfer not being aborted (so it continues wasting bandwidth and memory). It also keeps a cache entry, so when a dpi download is requested it hits and gets fed from the cache! (not from a dpi). That's clearly a bug. This days I've been reviewing the code with a view to patch it, but it seems that a full patch (aborting the transfer, cleaning the cache entry, stopping the clients and offering a download dialog) may be too complex to debug in this pre-release testing stage. Aborting the download (which would allow for the later dpi download) looks simpler. I'm currently working on this. That, plus the two patches in CVS seem to round "pre2" and most probably become 0.8.1. Cheers Jorge.-

1 0

[Dillo-dev]dillo-0.8.1-pre1.tar.bz2
by Jorge Arellano Cid May 6, 2004

May 6, 2004

Hi there, It took a long time to prepare the pre1 tarball for the next release. Mainly because complex problems were discovered in the last minute. For instance, a race condition in the dpi chain that produced segfaults (it took three days to find and fix), and several problems with the downloads server (it had troubles when saving unnamed pages as "index.html" when the file already existed, it was also not renaming those pages, etc). The "pre1" tarball can be found at: http://www.dillo.org/download/dillo-0.8.1-pre1.tar.bz2 When testing it, please pay special attention to the new detection routine for socklen_t (at ./configure time), and give the downloads server a hard test. Feedback is very important now, because I want to remove the "alpha software" label from dillo and name it as stable (beta). Thanks in advance Jorge.-

3 11

[Dillo-dev]CVS renamed ?
by Jens Arm May 5, 2004

May 5, 2004

Hi If I try to do a CVS checkout I get: [tux@tux dillo]$ cvs -z9 update -dP /sfhome/cvs/dillo: no such repository What happend ? Jens

2 1

[Dillo-dev]libpng-1.2.4 detection
by Jorge Arellano Cid May 4, 2004

May 4, 2004

Hi, Is anyone here using libpng-1.2.4? Rubén sent me a bug report and effectively we were not detecting libpng-1.2.4 right (this only happens with 1.2.4). A patch for this is in CVS, and it will appear in "pre2". I'll keep expecting more feedback from "pre1" because the png lib detection is the only change so far (it's minor and doesn't affect the work of the browser, just compilation). If anyone is using libpng-1.2.4, please let me know. Cheers Jorge.-

2 1

[Dillo-dev]GTK FLTK and other Render
by shuishuila May 3, 2004

May 3, 2004

Hi, dillo-dev， I want to port dillo to set-top box as menu(OSD). But it don't have X11,GTK. How many work need to do if I have to write widget myself? I think it's a pity that dillo combine tightly with glib/gtk, so it is hard to port to X,FrameBuffer,DirectFB etc. If dillo have it's own widget and event handle, it is a excellent broswer for embedded system. Regards, 　　　　　　　　shuishuila 　　　　　　　　shuishuila(a)hotmail.com 　　　　　　　　　　2004-04-30

2 1

Re: Re: [Dillo-dev]GTK FLTK and other Render
by shuishuila May 3, 2004

May 3, 2004

Hi,Jorge, Thank you for your reply. FLTK need X, so I need to port microwindows at least. Why no let dillo's render engine more scalable? And I think that few desktop system have FLTK. Regards, shuishuila(a)hotmail.com 　　　　　　　　　　2004-05-03 ======= 2004-05-02 10:41:00 You Wrote：======= >On Fri, 30 Apr 2004, shuishuila wrote: > >> Hi, dillo-dev， > > Hi. > >> >> I want to port dillo to set-top box as menu(OSD). But it don't have >> X11,GTK. How many work need to do if I have to write widget myself? > > That's a lot of work, but... > >> >> I think it's a pity that dillo combine tightly with glib/gtk, so it >> is hard to port to X,FrameBuffer,DirectFB etc. >> >> If dillo have it's own widget and event handle, it is a excellent >> broswer for embedded system. > > We're almost done with a plan to port Dillo to FLTK. > > You can read about it in our mailing list archives. Start here: > > http://lists.auriga.wearlab.de/pipermail/dillo-dev/2004-April/001882.html > > > If you have FLTK knowledge and are willing to help us doing the >port it'd be great. > > Cheers > Jorge.- = = = = = = = = = = = = = = = = = = = =

1 0

[Dillo-dev]is anyone planning to add SpiderMonkey (JavaScript-C) Engine to Dillo?
by Miernik May 1, 2004

May 1, 2004

Is any work going on to add SpiderMonkey (JavaScript-C) Engine to Dillo? http://www.mozilla.org/js/spidermonkey/ I once saw a post of somebody who planned to do something like that, but heard of no progress later. I would be very interested in such implementation. -- Miernik _________________________ xmpp:miernik@amessage.info ___________________/__ tel: +48888299997 __/ mailto:miernik@ctnet.pl http://www.miernik.ctnet.pl/

1 0

[Dillo-dev]dillo interface and motif, athena etc
by Riccardo Mottola May 1, 2004

May 1, 2004

Hello. I have never looked at dillo's source code directly, so I am asking some general questions here I have always liked dillo's speed and use of system resources because it brings back the fun of browsing and works on older workstations too, as every browser should. But I never liked dillo's interface too much. I'd like to make it a proper interface, more like other browsers have, taking inspiration for example from Mosaic's bar and bookmarks, from chimera's simplicity, from HotJava cutsomization, etc. Also, I dislike GTK: they are slow and don't work well on 256 color screens. I would use Motif for writing the interface with having an eye on LessTif of course. Motif/Lesstif is extremely fast and works like a charm on my old 20Mhz IBM RS6k witha 256 color card. Also, most free OS users have one of the either installed too, to run stuff like the excellent NEdit. Being able to install dillo on AIX, Solaris, IRIX, HP-UX without having to install an additional toolkit would just be nice. Athena is also present everywhere, but let's say it is a bit primitve. Of course, super-fast :) So I ask: how much of dillo's code is GTK dependent and how difficult would it be to port it to another toolkit? I have quite little experience with toolkits and since I don't know GTK it seems impossible to me alone. One of the nicest things, IMHO, would be a toolkit-independent dillo. Have a look at what the excellet GVIM does or at what amaya does (or, at least, did). Choose your toolkit! I don't know how they structured their code and their graphic drawing, but it would be interesting to investigate. -Riccardo

1 0

[Dillo-dev]Test for socklen_t in configure.in
by Jorge Arellano Cid April 30, 2004

April 30, 2004

Hi there, Our configure.in is in need of a test for socklen_t. I thought this one could be a good one: dnl ------------------- dnl Check for socklen_t dnl ------------------- dnl AC_MSG_CHECKING(for socklen_t) AC_TRY_COMPILE([#include <sys/types.h> #include <sys/socket.h> socklen_t x; ], [], [AC_MSG_RESULT(yes)], [ AC_TRY_COMPILE([#include <sys/types.h> #include <sys/socket.h> int accept(int, struct sockaddr *, size_t *); ], [], [ AC_MSG_RESULT(size_t) AC_DEFINE(socklen_t, size_t)], [ AC_MSG_RESULT(int) AC_DEFINE(socklen_t, int)])]) but my autoheader complains... Can someone please complete the patch, I'm currently chasing a segfault bug I found... TIA Jorge.-

2 3

[Dillo-dev]Preparing the 0.8.1 release
by Jorge Arellano Cid April 28, 2004

April 28, 2004

Hi guys, 0.8.1 is getting closer every day. It will feature what's currently in the CVS (basically the improved HTML bug detection and rendering). I'd love to be able to switch this dillo version from alpha to beta stable, but for that there's a lot of testing required. That is, the new parser (going to lots of sites and asserting there're no crashes), and the recently found problems with puppy linux and downloading and FTP (has anyone experienced trouble with these dillo plugins on their systems?). Please test our current CVS hardly, and tell us how it did. Thanks to Jim, who was the first one to send some feesback: > Wow! I can see a big improvement, lots of sites that rendered readably, > but 'iffy', are now much clearer and cleaner. Cheers Jorge.-

10 16

[Dillo-dev]what should do after the window is scrolled?
by Lei Jin April 27, 2004

April 27, 2004

After the window is scrolled, should the new contents of the window be redrawed by the code written by human? Can we output the whole contents to a place, then when the window is scrolled, we only need to updated the visible rectangle parameter? --------------------------------- Do You Yahoo!? 惠普TT游戏剧，玩游戏，中大奖！

1 0

[Dillo-dev]install-dpi-local missing?
by Livio Baldini Soares April 26, 2004

April 26, 2004

Hello everyone, Long time no see, I know, I know... My life has been a (wonderful) big roller-coaster for the last 1 to 2 years, and it seems that the remainder of this year will be the same. Anyways, just wanted to try to report that reading the README file, one gets the impression that an "install-dpi-local" script should exist to install the dpis in your ~/.dillo/ directory for you. I have googled for it, and tried searching in the CVS ATTIC with no success. Things are working for me just fine, because I know how/where to copy the dpi files, but I can imagine that some of our users might be frustated, or require additional assistance. So, before releasing 0.8.1 it might be a good idea to fix the README, explaining what is needed for a "local" install, or even better, resurrect the install-dpi-local script. best regards to all! Livio

2 1

[Dillo-dev]About porting Dillo to FLTK.
by Jorge Arellano Cid April 24, 2004

April 24, 2004

Hi there, We've had long email threads (between our core developers and some FLTK core devs.) dicussing about how the port of dillo to FLTK could be done. We've explored different paths (in abstract) and posting all the threads to dillo-dev would add more to confussion than clarity because each one was explored as it were the chosen one. For simplicity and to keep all the developers in dillo-dev well informed (and certainly inviting the interested ones to take part in the process), I prepared this recapitulation about the more relevant issues. It's a long document with a lot of information. Cheers Jorge.- PS: Previous background on this topic can be found at dillo-dev's archives: http://www.dillo.org/search-dillo-dev.html. For instance: search for "FLTK" by "jcid" sorted by "Relevance". This will not only bring my posts but also the ones from Michael Sweet that I forwarded to dillo-dev. ---------------------------------------------------------------- > [Sebastian] > Furthermore, I have plans to extract at least the core of Dw, and make > an own library of it. The package is already finished, I'm just > polishing another package, which uses Dw. (This is "rtfl", the program > for which the macros in "debug.h" are for.) > > Perhaps it is at least possible, to make Dw itself independent of the > widget toolkit (Gtk/FLTK), ... > [Sebastian] > Dw can be rather simply extracted, and probably it is the best to > start with a testbed. I've attached a test program (I searched > for it somewhere in the mailing list, therefore the french > identifiers :-), you have to build dillo first, to run > it. Perhaps it is simpler to include it into the dillo tarball > itself. > [Sebastian] > Another aspect is portability: When using other toolkits than Gtk, > GtkDwViewport may be replaced. > > For archieving this, the following new design will be sufficient: > > +--------------------+ 1 * +-------------------+ > | DwRenderingContext |---------->| DwRenderingWindow | > +--------------------+ +-------------------+ > 1 ^ | 1 > | | > viewport | | child (the top-level DwWidget) > | | > * | V 0..1 > +----------+ 0..1 > | DwWidget |--. parent > +----------+ | > * | | > `-------' > (children) > [Sebastian] > As for the actual porting, I'm currently working on two topics, which > should make porting simpler, since they reduce the Gtk/Gdk specific > stuff into single modules: > > 1. I'm currently changing the design of image handling as I > described in doc/DwImage.txt in the tarball, section "Future > Extensions". As I've seen now, this is also necessary for > topic 2. > > 2. After this, I'll implement the ideas I wrote before (abstraction > of the actual drawing), in the best case, it should be a simple > matter to write a replacement for the viewport, plus some > changes in dw_style.[ch]. (Dependance of the GtkObject model not > yet considered.) > [Matt] > Abstraction is definitely the best thing to do here. I am pretty sure > we can cross reference between the a-layer and whatever FLTK has to > offer. Spontaneously I see the need for buttons and input fields, line, > box, text and image drawing, image scaling and the dreaded 16-bit vs. > 32-bit coordinates. > > [Jorge] > > Once again, I'd wish to know how a seasoned FLTK developer > > foresees the merging path (from their point of view). With regard > > to Dw, you're the authoritative source! ;) > > [Matt] > At this point - if you guys are still interested - I guess I should > take an extensive tour through the Dw code and see, which parts map > directly onto FLTK, and which parts would need modifications or even > rewriting. ------------------ 32 bit coordinates ------------------ > [Jorge] > > Hi Michael, > > We have been extensively discussing how to port Dillo to FLTK > with Mattias M. and Sebastian. One of the key points is how to > provide for a widget that overcomes the problem of 16 bit > coordinates (GtkLayout currently solves this). > > In a formar email you told me that FLTK2.0 had 32 bit > coordinates, but suggested me to use 1.2.x release that would > also come with 32 bit coordinates. > > Matt was somewhat surprised by this... > [Matt] > I talked to Mike. He changed the coordinates to 32 bit in his local > version already. So in short, fltk 1.2 will have 32 bit coordinates. > Versions 1.1 and 1.0 will not be changed anymore, however 1.2 should > become the standard as soon as we release it, since it is source code > compatible to 1.1. > [Matt] > I went through the current CVS code yesterday, and it seems like we had > a mixup between 1.1 and 1.2. Not a biggie, but I re-merged with a > previous CVS version. The current CVS is now fully 32 bit. tested and > working. > [Jorge] > So we have to use 1.2.x CVS, but which docs are recommended for it? > > [Matt] > The 1.2 cvs contains the full 1.1 documentation and is beeing corrected > to reflect 1.2 changes and additions. I am in the process of adding > doxygen style comments to all fltk classes and methods (95% done), so > simply running the command 'doxygen' will create a second, more > 'techie' documentation in docs/html/index.html. ------- Signals ------- > [Jorge] > Appart from that, the 32 bit issue and the signals (perhaps > solved with Fl_Signal). > [Sebastian] > As for signals: This should be rather simple to re-implement. I just > hacked a prototype of very simple framework for signals, which can be > downloaded at <http://www.dillo.org/misc_files/signals-0.0.1.tar.gz>. > It lacks events returning boolean (which we need), and some more > features (which we do not need), but shows that signals aren't really > a problem. ------- Plugins ------- >> OK, there's no plugin API in FLTK. > > Do you mean what GtkPlug/GtkSocket does? There protocol has been (or > is currently?) standardized at freedesktop.org, if an implemtation is > possible (and why should it not?), this is certainly a candidate for > merging into FLTK. > > > [Matt] > > Yeah, I talked to Bill, and we decided that we will create an Fl > > utility library that offers cross platform access to files and sockets, > > provides threads and locks, and also some standardised plugin > > interface. We will be smarter this time and write it in FLTK2 with an > > FLTK1 compatibility layer... . ------------------------------ About how to approach the port ------------------------------ > > >> [Sebastian] > > >> I'm more > > >> than ever convinced that this was the right decision, especially since > > >> then, incremental resizing has been added, what would have been very > > >> difficult in Gtk. Furthermore, this shows the benefit of having an own > > >> widget set, which can be infinitively changed to our needs. > > > > > > [Jorge] > > > In that case, it seems that the path to go is to port Dw to > > > FLTK, and maybe get rid of some widgets (as DwImage) when they > > > can be replaced by an FLTK embedded one. > > > > > > In anycase, Matt is better qualified than me to comment on > > > this. > > > > [Matt] > > All images in FLTK can be resized at any point. > > > > I understand that you prefer to have your own widget set, and I surely > > don't want to convince you different (because we wanted the same thing > > and that's why we wrote FLTK in the first place). However, should you > > decide to go with FLTK, then all the source code is available to you, > > so you can do the same modifications that you would do in your code. If > > those changes (or additions) are useful for the FLTK toolkit, I'll be > > happy to do them for you (ah, that's where the benefit is for you). > > [Jorge] > This is a very interesting collaboration scenery. I believe we > could start as Sebastian suggests, and merge those features you > see could benefit FLTK. (as for images, and maybe the "complex > resize" widget using size hints to name two). > > [Sebastian] > To make this clear again: What we currently have is an own widget > toolkit within Gtk, i.e. Dw widgets, from which the page is build, are > not Gtk widgets, but instead, for Gtk, a tree of Dw widgets is a just > _one_ huge Gtk widget. (With the exception of Gtk widgets embedded > into Dw.) > > I'd like to stick with the same design (with FLTK instead of Gtk), > also on the long run. For this, there are rather few requirements for > the GUI toolkit, mainly only the 32 bit issue. Integrating both > toolkits, in the way that Dw widgets will become FLTK widgets, will > however make things generally more complicated, we will have a hybrid > which has to deal with both rendering HTML (and other) documents on > one hand and GUIs on the other hand. The duplicate code in the current > design (like event handling), is rather minimal, but integrating would > mean one of the following possibilities: > > 1. Making FLTK as abstract as possible: This would make Dw as > complex as it is now, but instead add an unneccessary > dependency, where the development of dillo will often have to > deal with the limits which any GUI toolkit has. > > 2. Incorperating stuff from Dw into FLTK: This would IMO a very bad > decision of the FLTK team. Dw was designed for rendering > documents etc., and its layout mechanism has several ad hoc > features (size hints, width extremes, incremental resizing), > which should not be in a toolkit for GUIs. Actually, the design > is quite ugly at some points. > > Furthermore, the design often changes, some historical examples: > > - Dw widgets had baselines from the beginning, but they were > fist used much later. (I was indeed hesitating at the > beginning.) > - Tables made it neccessary to introduce width extremes. > (Very ad hoc: Why not height extremes? Because texts are -- > in most languages -- written horizontally, and then > vertically split into lines.) > > - Also with tables (although noticed some time later), it > became clear that the current resizing mechanism was > inefficient and had to be extended. (Notice that Dw > requires that several resizes per second must be handled, > much more what is neededfor GUIs.) > > These were certainly not the last changes, e.g. for CSS, we will > have some other requirements, which are yet not specified. Also, > this shows that most requirements are not obvious before they > are first needed. > > If FLTK wants to adopt Dw features, it will be neccecary to > change FLTK often, and since it is not part of dillo, the > development of dillo will be slowed down, until new FLTK > releases. > > 3. We move stuff from Dw into our own version of FLTK: This would > probably the worst possible desicion, we would fork FLTK and > have to maintain it, also the parts which deal with pure GUI > aspects. > > Dw will work fine with FLTK in the way analogue to the current way, > and the problems with this split are really not as dramatic as Jorge > describes it. The FLTK developers should not make the mistake to take > just one (probably rather prominent) project and change their work so > that it just fits within it. And dillo should keep it dependencies as > low as neccessary. ------------ Porting Plan ------------ > [Sebastian] > I'd suggest the following: > > 1. Finish the planned abstractions. The general idea is to have the > Gtk/FLTK specific code in small modules, which may be rewritten in > a simple way. > > 2. Extract Dw from dillo, and write a test program for several aspects > of Dw. > > 3. Rewrite those modules mentioned in 1, and adjust the test > program. This step will still make Gtk necessary, because of the > Gtk object model, but UI control, event handling etc. will be done > by FLTK. > > AFAIS, the affected modules are the new GtkDwViewport, ImgBuf, and > DwStyle. The abstraction in step 1 may taken a bit more extreme, by > splitting up the latter two into toolkit-dependant and -independant > parts, we'll see. The dillo widgets themselves should not be > modified, if this is really necessary, this is a fault of the said > abstraction. > > After this, we will have a version of Dw, which works with FLTK. The > next step is to see how the parts we take from Gtk (object model with > signals) and GLib (several utilities) can be replaced, so that we can > get rid of the Gtk dependencies. Another topic it the port of the > actual UI; AFAIS, there should be no major problems. Appendix -------- -------------- About printing -------------- > > [Jorge] > > Is printing lost because the widget tree is not native FLTK, or > > is it assured by using FLTK's drawing primitives? > > [Sebastian] > Some remarks on this. First, we still have a "native" FLTK widget, > just that we have one large, complex FLTK widget (which complexity is > manages by Dw), instead of multiple smaller and simpler FLTK > widgets. The reimplementation of the viewport should use FLTK methods > for drawing, so there is no problem at all. > > Second, the abstraction described above should make this possible with > any toolkit, it should be simple to write a printing "viewport". > > Third, printing will anyway become more complex, for several > reasons. For one reason, I quote myself from a mail I sent Jorge, this > may also be interesting for Matt: > > <q> > I'm very sceptical about the idea to use the current rendering for > printing, for two reasons: First, the current rendering is designed > for dealing with viewports, not for pages. Pages are in some ways > different, e.g. you must break pages (instead of having one page of > unlimited height), and you cannot widen the page, you must break a > word, when it does not fit into the line, while it is more > reasonable to let the user scroll to the right, when this is > possible. (Furthermore, from a typographic point of view, dillo's > typesetting quality is sufficient for screen rendering, but rather > poor for printing, especially page breaking cannot be done as > simply as line breaking.) > > Second, most of the complexity has its roots in the requirement of > incremental rendering, which is neither needed, nor desired for > printing. Actually, it makes use for printing more complicated and > inefficient. (Although one rendering iteration has a nearly > constant time, it is as a whole still slower than a simple > non-iterative run.) > > [...] > </q> > > Furthermore, even if we would use Dw for printing (with ugly page > breaks etc.), we would need another widget tree, with the same content > of the current one, but with a state, which is different, e.g. the > top-level available width, which is the window width for the screen, > but the standard paper width for the printer.

1 0

Re: [Dillo-dev]Can't start dpid
by Barry Kauler April 24, 2004

April 24, 2004

> > the problem is dpid won't start in my custom Puppy Linux > > distro. Jorge, Thanks for the feedback. Now that I have dillorc file, dpid does load, but it still isn't working. If I start dillo from the commandline, and enter a url https://www.paypal.com, nothing at all happens in the browser, no error msg even. I get this output from dillo on the stdout/errout: Nav_open_url: Url=>https://www.paypal.com< url_str = https://www.paypal.com Dpi_parse_token: [<dpi cmd='answer' to_cmd='open_url' msg='nothing sent...'>] Dpi: [Dpi_process_io] IOClose The paypal site is working, I just checked with Mozilla. If I right-click on a link to a file on a webpage and choose to "Save link as...", the destination choice window comes up, but after pressing OK button, the stdout/errout is this: ERROR: [Dpi_get_token] Can't find token start ERROR: [Dpi_get_token] Can't find token start ERROR: [Dpi_get_token] Can't find token start ERROR: [Dpi_get_token] Can't find token start Dpi: [Dpi_process_io] IOClose So, I celebrated too soon! Do these messages mean anything much to you? Any suggestion what I should try next? Regards, Barry Kauler

1 1

[Dillo-dev]FTP
by Pete April 23, 2004

April 23, 2004

Morning all, Seeing as someone has mentioned 'FTP', I thought I would get in here. I cant seem to FTP with dillo. If I type is ftp://ftp.somewhere.com it will just hang there. If I type in ftp.somewhere.com it will take me to http://ftp.somewhere.com. So tell me, how do you FTP with Dillo? I am using CVS build. Thanks, -- Pete http://milneweb.com http://nomorevirus.com

1 0

Re: [Dillo-dev]About proxy authorization && password storing
by Jorge Arellano Cid April 23, 2004

April 23, 2004

On Fri, 23 Apr 2004, Ivan Daniluk wrote: > > [...] > > - renamed a_Http_use_proxy_passwd() to a_Http_set_proxy_passwd(). > > - Made the password not visible when typed. > > - Added a commented entry for "http_proxyuser" in dillorc. > > > > This patch is now in CVS, but is not tested because I don't > > have a proxy at hand! :-) > I've tested - it seems to be ok. Good. > And one correction from Francis Daly: > ------------------------------------------- > > From: "Francis Daly" <francis(a)daoine.org> > > To: "Ivan Daniluk" <Ivan.Daniluk(a)ucl.com.ua> > > > > On Thu, Apr 08, 2004 at 06:49:45PM +0300, Ivan Daniluk wrote: > > Hi there, > > One small thing: > > > + static const char *base64_hex = "ABCDEFGHIJKLMNOPQRSTUVWXYZ" > > > + "abcdefghijklmnopqrstuvwxyz" > > > + "0123456789._"; > > > > RFC 2068 (HTTP/1.1) defers to RFC 2045 (MIME), which uses "+/" as the > > final two elements, instead of "._". > > > > RFC 1945 (HTTP/1.0) defers to RFC 1521 (MIME, obsoleted by 2045) which > > uses the same. Done! > PS. I've sent a letter to Madis, but have got no reply yet. Yes, he's under too much work now (we were working on the SSL plugin and he had to stop because of his duties). Please allow him some time. BTW, we have a new SSL dpi prototype (not for the next release though). More on this later. I'll send a recapitualtion about the FLTK port first... Cheers Jorge.-

1 0

Re: [Dillo-dev]Can't start dpid
by Barry Kauler April 22, 2004

April 22, 2004

Ok, I've joined the dillo-dev list! On Fri, 9 Apr 2004 08:13:17 -0400 (CLT) Jorge Arellano Cid <jcid(a)dillo.org> wrote: > > I should also explain that I have my own distro, Puppy Linux, > > and everything is compiled against uClibc, not glibc. > > (www.goosee.com/puppy) > > Oh, it would be interesting to have Dillo running under uClibc! Dillo has been in Puppy right from the start (which was about one year ago). A few months ago I changed over to uClibc and recompiled everything, including Dillo, and all was well until I upgraded to Dillo v0.8.0. > Check if you can run them crom the CLI: > > cd /usr/local/lib/dillo/dpi/hello > ./hello.filter.dpi I'm doing this as root. When I try this I get: hello.dpi:: starting... and that's it, nothing more, doesn't exit until I ctrl-c. No error message. ...what is it supposed to do? Regards, Barry Kauler

4 11

[Dillo-dev]Re: [Fink-devel] [Dillo] FONTS
by Joe Corneli April 22, 2004

April 22, 2004

Thanks. I'm somewhat amazed that the Dillo people didn't catch that. >> My ~/.dillo/.dillorc Note that the file should be named ~/.dillo/dillorc (leave the second dot). I do think it would be nice to support a .dillorc too, for people who, like me, automatically type the `.'.

2 1

Re: [Dillo-dev]About proxy authorization && password storing
by Jorge Arellano Cid April 21, 2004

April 21, 2004

On Fri, 2 Apr 2004, Ivan Daniluk wrote: > Hi Jorge. Hi! > > > Maybe, we should open popup dialogue and ask user for > > > login/password? > > > > The login may be specified in dillorc, and the password asked > > in a popup dialog (whenever there's a login in dillorc :). > > > > This adds the burden of entering the password, but keeps things > > a bit more private. > I've implement this burden :), but stuck in a problem and need advice > and/or suggestion from you. > First, look to the attached current patch for stable dillo 0.8.0 > release. Oh, I haven't yet. Anyway, here's the answer. > Main problem for me is the way to stopping the query, waiting > until password will be entered or canceled, and resuming it. > When we call a_Interface_proxy_passwd_dialog(), the dialog window pops > up, and query goes forward, without being formed with proxy password. > So, I see two ways: > 1) to stop the query forming(in Http_get() function) and wait, while > proxy_passwd_dialog_window will be destroyed. > 2) to abort the query, and recall it when password will be entered. > > I'm a newbie in gtk programming, and can't figure out how to graceful > open dialog window and wait until it'll be closed. If it's possible, > than imho it's the best way. > About second choice.. There are complexity for me in a_Http_ccc stuff. > Sure, I'll win this problem, but it will take more time. And really > want to hear your thoughts about it. Use the third alternative! :-) AFAIS the simplest way to to it is to ask for the proxy password when dillo starts, that is, before any query is made, probably after the splash screen is displayed. That way, things would reach the same simplicity as in the first patch! > One more question around it. > Password dialog window is activating in case if there is option > "http_proxyuser" in config, but not when http query gets "Cache Access > Denied" error. > Is this way ok? AFAIU, yes. The proxy login/password pair is one thing, and HTTP's simple authentication mechanism (section 11) is another. It may happen that you reach a realm/password protected page through a login/password authenticated proxy. Now, if after this patch, you want to keep on working on basic authentication, be sure to contact Madis (AFAIR he once worked on it), and I can make the CCC bindings to stop/resume/forward the querying process. > And, the last note on patch. It's about following lines in IO/http.c: > + if ( strchr(prefs.http_proxyuser, ':') ) > + { > + DEBUG_MSG(5, "Storing proxy password in dillorc is insecure!\n"); > + ask_proxy_passwd = FALSE; > + HTTP_Proxy_Auth_base64 = a_Misc_encode_base64(prefs.http_proxyuser); > + } > It allows user to store in config file not only proxy user name, but > pair "user:password" as well. I've done it's mainly for convenience, > but of cource we can remove it from patch. Hmmm, this is one I'm not yet sure of. On one hand, it is very handy not to have to enter the password every time, and on the other, stealing the proxy's password becomes quite simple (for instance, a bathroom break and it's gone! ;). [minutes thinking...] It's not a thing I'd recommend. Now, as Dillo project is explicitly concerned about security, it can't do otherwise. Perhaps you may leave that portion of code commented out, so the responsibility is left to the one that decides to enable it. I'd like to hear comments about this. Specially from sysadmins. > Your suggestion for me are welcome. Thanks. Cheers Jorge.-

2 2

[Dillo-dev]fonts
by Joe Corneli April 20, 2004

April 20, 2004

My ~/.dillo/.dillorc contains # Fontname for variable width rendering (most of the text). # - some fonts may slow down rendering, some others not! # - try to tune a fontname/font_factor combination. # Ex. {helvetica, lucida, times, "new century schoolbook", utopia, ...} vw_fontname=utopia # Fontname for fixed width rendering (mainly <pre> quoted text) fw_fontname=courier # All fontsizes are scaled by this value (default is 1.0) font_factor=3.0 The font that is actually used appears to be the same as the default. Can you please suggest how to debug this or how to actually change the font? I'm running OS X, using Dillo 0.8.0 from Fink. Joe

2 1

[Dillo-dev]Who posted BUG#544?
by Jorge Arellano Cid April 20, 2004

April 20, 2004

Hi, I wonder who posted this report: BUG# 544 Impact: feature fault At : run time Type : other Comments: I love the html bug detector but I can't copy the data from it! This greatly reduces it's strength... my students are using dillo almost everyday now in a web dev class.. HTReproduce: get a buggy html site/ click on ck html / try to copy the errors WorkedBy: nobody Obviously doing Copy&Paste from the error window solves the problem. It's be very interesting for us to know where and how is dillo used in a web dev class. Cheers Jorge.-

1 0

[Dillo-dev]BAD HTML and Good Webmasters
by Jorge Arellano Cid April 20, 2004

April 20, 2004

Hi there, These days have brought several good surprises with regard to HTML and good webmasters. For instace, from the sites that appear in our splash screen: The Register: switched to XML! (no BUGS) Slashdot : they're fixing the HTML (some old detected bugs don't show anymore) Monster news: In the process of fixing. Dillo's site: Fixed! (Yes, the new parser catched hidden bugs) also, sourceforge.net and newsforge.com look better with the new parser (not a merit of the sites, but a good new anyway). To finish this report, and with a view to exemplify what you should expect from a good webmaster, I'd like to forward a couple of emails I had with the webmaster of www.fluxagent.org: ---------- Forwarded message ---------- Date: Thu, 15 Apr 2004 21:50:12 +0200 From: Markus Kroetzsch <Markus.Kroetzsch(a)inf.tu-dresden.de> To: Jorge Arellano Cid <jcid(a)dillo.org> Subject: Re: www.fluxagent.org and Dillo Dear Jorge, thank you for your answer. Setting the area > tag fixes the problem, even on my old Dillo 0.7.2. The webpages will be updated shortly to reflect this insight. When viewing the uncorrected page sources with Mozilla, the missing ">" actually shows up automagically, which might be the reason why nobody noticed so far (the pages are auto-generated by a script, so there is just one place where ">" is missing...). Best regards Markus > Hi, > > Sometime ago someone filled the following bug record with > regard to www.fluxagent.org: > > BUG#478 > Impact : soft error > At : run time > Type : misbehaviour > Comments: Images used for navigation within a table (each equiped > with some polygon-area mouse-<map>) do not always (but sometimes) > actually work as links. Maybe related to bug 317? > - PS: Great project! - > HTReproduce: Go to www.fluxagent.org (valid html4.01). Check the > navbar: only the first link works, no matter which sub-page is > viewed. > WorkedBy : nobody > > I tried to get the webmaster's email address from: > > http://www.fluxagent.org/emails.htm > > but it didn't show for Matthias Fichtner, so I write to you. > > > The problem is that for some reason I don't yet know of, SGML > allows for omitting the '>' closing tag character for the <area> > element. > > If you check the page with W3C, it validates, but if you do > with the WDG validator, then it shows: > > http://www.htmlhelp.org/cgi-bin/validate.cgi? > url=http%3A%2F%2Fwww.fluxagent.org&warnings=yes > > The easiest solution is to add the missing '>' for each <area> tag. > > > Hope this helps > Jorge.- > http://www.dillo.org ------- End of Forwarded message -------- Cheers Jorge.-

1 0

[Dillo-dev]Bookmarks, Tabs
by Tom Barnes-Lawrence April 18, 2004

April 18, 2004

Hi all, I've got 2 questions to ask: 1)- I was on the list back in January, and amongst other things, I mentioned that I'd consider it a huge improvement if the bookmarks DPI were made to allow for a nested hierarchy of sections. Jorge and Thorben pointed out that it wasn't a priority at the time, and that I should write it myself if I wanted it. Unfortunately, I too had things to be doing back then, but about a month ago, I set about doing some work on such a thing. -It is written in Perl, rather than C; it seemed a good choice due to all the text manipulation, etc. This might be considered a problem if Dillo is being used on platforms where Perl isn't (readily) available, but AFAICT the Windows version of Dillo is a purely 3rd party thing that isn't directly supported by the project, and Perl for Windows does *exist*... I don't know if there'd be any other issues with this decision though. -I moved much of the Dillo-DPI specific stuff into a separate file, hoping to make it a Perl Module, but I know nothing about how that works (and I can't get the Camel book ATM because I'm broke) and couldn't understand the relevant man page, so I don't think it turned out how modules are supposed to. I mention this because it could maybe end up useable by any other Perl-based DPIs that get written. -It currently uses the "ngbm" DPI name (for "Next Generation BookMarks"), and uses ngbm.txt for the bookmarks file, to avoid breaking the existing bookmarks program. That's because it's not ready yet. -It *does* implement the nested sections stuff I wanted that the current bm dpi doesn't, with a file format that's backwards compatible with the current one- so you can get it to read your existing bm.txt file. -BUT I only worked on it for about a day, and much of that was spent trying to figure out how it was supposed to communicate, so it still doesn't have much of the important functionality, such as actually adding or modifying any bookmarks or sections. Also, as I was hacking away a lot to try to get it to work at all, there's a lot of commented-out debug stuff, and much of the notes and comments are probably wrong now (I don't think I fixed them whilst I was changing the code and the design). I didn't want to go quietly working away at it for ages and then find that actually someone else was quietly working away at the same thing, for example (also the DPI handling stuff got incredibly frustrating, which put me off doing any more for a while). Unfortunately, I kept forgetting to do *anything else* about it because I had other things to think about :P SO: Would this be of any interest to the project in whatever way? I figure I could (a) post the existing code, get a bit of feedback and then do some more work on it, or (b) give the code to the project and let someone else take it over from me. (or (c) I could just keep it to myself...) 2)-Since my high-res monitor blew up in December, I installed Frank's tabs+ frames patch, and I find it helps enormously- I don't think I could manage without it now. Unfortunately, AFAICT Frank has either left the project or gone on holiday or something (though I can't find any explanation anywhere), and the latest version on his site (which I'm using) only works with an old CVS version from November, so I'm still having to put up with the bugs that have been fixed in 0.8. Gah! I saw after 0.8 was released, someone on the list said he'd try to take on the tabs/frames patch in some way, but I didn't hear anything more about it. Is there *any* news on this whatsoever? I'd really like to be able to upgrade. Thanks in advance, Tom Barnes-Lawrence -- Signature? I have no need of signatures

2 1

[Dillo-dev]HTML Policy and New parser improvements
by Jorge Arellano Cid April 16, 2004

April 16, 2004

Hi there, Most of us are familiarized with the aforism about our HTML parsing policy stated in the [Project Notes]: "Our policy with HTML is not to try to render badly written HTML, ideally send a warning message, and not to crash!" Here goes the rationale behind it. I wrote it sometime ago as an email answer, and here I quote an improved version: <q> About our parsing policy ------------------------ These days I have thought a lot about this subject. In fact an important part of the work of a project maintainer is indeed to make a stance on the difficult decisions; those that are not white or black, but a trade off. With regard to our parsing policy, imagine a triangle with the following vertices: * Standards (W3C) * Web site authors * Users Each vertex represents the exact position of its naming group. The inside area, the whole space of stances anyone could take. Each group has its own interests, sometimes opposed and sometimes very near. The position of a web browser can be visualized as a point within the area of that triangle determined by its development team. Dillo should have to be in the vertex of the W3C, but that would make it almost useless because of the horrible state of the HTML in the Web (aka. "Tag Soup"). For that reason we make some exceptions so that dillo can render a larger set of the web, by correcting some HTML faults, but we keep close to the W3C vertex. An standards compatible browser, as Mozilla, should be close to the W3C, but I understand it would never manage to be a canditate to replace IE if it did (a trade off). Actually it locates alongside the authors-users side AFAIU. As our main objective is the democratization of the access to the internet's information, and that has direct relation with the use of standards, we follow the path of respecting and promoting them. The idea of adding an HTML quality meter to the interface, in the form of a face icon and the number of detected errors, surges as a good idea to improve dillo as a QA tool for content authors. I've also thought of adding a "combat mode rendering" button. That is a way of parsing the worst sites into a basic an simple rendering. That way, users would be one click away from being able to "see" pages with awful HTML. These two ideas would help dillo to keep close to the correct vertex of the triangle, while also becoming a tool to help web authors to provide more standards compliant content. </q> After the new parser was introduced (0.8.0), Dillo featured much better HTML error detection, but it rendered malformed HTML a bit worst. It was a good trade off from the "standards" vertex of the above mentioned triangle, but I also knew that it was not going to be that much amusing for the "users" vertex. These days I've been working on improving the parser and bug-meter by introducing information about the inline, block and flow content models of HTML. After having that information in place, it was easy to produce better and more accurate bug detection and also to improve the rendering more towards what it used to be. So that's the good news: the new CVS contains code with an improved parser that hopefully will be a glad surprise for our users. From the Changelog: * Added container|inline model information to the HTML element table, and made the bug-meter and the parser aware of it. This both improves bug detection and rendering. * Fixed newly detected HTML bugs in bookmarks dpi and file.c. * Fixed opening files with a ':' character in its name (again). * Added binaryconst.h (allows for binary constants in C). * Fixed The ladder effect with lists (BUG#534). So go ahead and try it! Cheers Jorge.-

2 1

[Dillo-dev]what's the use of "EndTag" component of struct TagInfo?
by Lei Jin April 15, 2004

April 15, 2004

Its value can be "O" "F" "R", so what do they mean? AND Why use them? --------------------------------- Do You Yahoo!? 惠普TT游戏剧，玩游戏，中大奖！

2 1

[Dillo-dev]Re: bug in dillo.0.8 rendering
by Jorge Arellano Cid April 15, 2004

April 15, 2004

On Sun, 11 Apr 2004, Brett E. Wynkoop wrote: > > Greeting- Hi. > just built it on FreeBSD 4.6.2. Great job on getting https > going using wget! Thanks. Now we're moving to a library-based one. > I found a bug in the handeling of both <ul> and > <ol> sections of pages. Use dillo to go to http://zaurus.wynn.com/ > and also http://zaurus.wynn.com/tricks/. > Note the staircase effect on the list items and that in the > <ol> section everything is numero uno! Thanks a lot for the report. It also shows on some manuals (as for xfig). I went chasing the bug and solved it in my source tree, I'm studying it further trying to find a more generic way to handle it. I'll let you know when it goes to the CVS. > Building on FreeBSD required hand tweeking of the make file. > In spite my telling configure that the libraries & headers it was > looking for were under /usr/local it could not find them and generated > make files without the correct information. I still have to play > with it a bit more to see if I can set something up to allow configure > to do the right thing. If I get it I will send it to you. Weird, we tested FreeBSD before the release. Please tell us what you find. Cheers Jorge.-

2 2

[Dillo-dev]international encodings
by honza m. April 15, 2004

April 15, 2004

hi, first of all, some words of praise: i -love- dillo :e) fast, small, doesn't repair html, has no javascript ... it's just great. biiig thanks to all developers :e) anyway, i know there is a problem with non iso-8859-1 encodings, and i'd like to help fixing it. but i've found that bug in the bugtracker in "being worked on" and also in "not being worked on" bugs, so i know nothing. and the mailing list search engine is so chaotic that i was unable to find relevant posts. so please some one tell me what's the status of this issue, or what are the main problems, or something which would help me help you ;e) thanks m. -- matejcik, the one who is not --- ..: imagine a thousand million minds ..: imagine them all become one ..: imagine the overmindNet

2 1

[Dillo-dev]A button theme for Dillo 0.8.0
by Geek April 12, 2004

April 12, 2004

While I was stuck with no internet, I made a theme for Dillo I call "cobalt". Enjoy! -- Gregg t3h g33k http://geek.scorpiorising.ca

3 2

Re: [Dillo-dev]Can't start dpid
by Barry Kauler April 12, 2004

April 12, 2004

Ok, I've joined the dillo-dev list! On Fri, 9 Apr 2004 08:13:17 -0400 (CLT) Jorge Arellano Cid <jcid(a)dillo.org> wrote: > > I should also explain that I have my own distro, Puppy Linux, > > and everything is compiled against uClibc, not glibc. > > (www.goosee.com/puppy) > > Oh, it would be interesting to have Dillo running under uClibc! Dillo has been in Puppy right from the start (which was about one year ago). A few months ago I changed over to uClibc and recompiled everything, including Dillo, and all was well until I upgraded to Dillo v0.8.0. > Check if you can run them crom the CLI: > > cd /usr/local/lib/dillo/dpi/hello > ./hello.filter.dpi I'm doing this as root. When I try this I get: hello.dpi:: starting... and that's it, nothing more, doesn't exit until I ctrl-c. No error message. ...what is it supposed to do? Regards, Barry Kauler

2 1

Re: [Dillo-dev]Can't start dpid
by Barry Kauler April 10, 2004

April 10, 2004

Ok, for those reading this thread for the first time, the problem is dpid won't start in my custom Puppy Linux distro. Maybe I've found the solution? I have a build environment, but then I run a script to create the Puppy filesystem, which copies files from the build environment. It copies dillo, dpid, dpidc into /usr/local/bin, all of the stuff in /usr/local/lib/dillo gets copied across, however, the script doesn't copy dpidrc and dillorc from /usr/local/etc, as in Puppy all of /usr is read-only. Instead, I have placed dpidrc and dillorc into ~/.dillo, except that this seems to have not been upgraded. I'm running Puppy right now and what I see in ~/.dillo are the files .073 cookiesrc dillorc So, is this my problem? I just checked the dates on those files, and they are from the old 0.7.3 version. It does seem that my oversight is to blame here! One question though, is there any problem with continuing to use the old dillorc? I ask this as when people upgrade to the latest Puppy they may have modified dillorc and I don't want to just overwrite their dillorc file. Looks like Puppy and Dillo are back in business! Puppy v0.8.5 should be out soon, like maybe another week. Regards, Barry Kauler On Sat, 10 Apr 2004 00:56:07 -0600 Barry Kauler <bkauler(a)goosee.com> wrote: > Ok, I've joined the dillo-dev list! > > On Fri, 9 Apr 2004 08:13:17 -0400 (CLT) > Jorge Arellano Cid <jcid(a)dillo.org> wrote: > > > > I should also explain that I have my own distro, Puppy Linux, > > > and everything is compiled against uClibc, not glibc. > > > (www.goosee.com/puppy) > > > > Oh, it would be interesting to have Dillo running under uClibc! > > Dillo has been in Puppy right from the start (which was about one > year ago). A few months ago I changed over to uClibc and recompiled > everything, including Dillo, and all was well until I upgraded to > Dillo v0.8.0. > > > Check if you can run them crom the CLI: > > > > cd /usr/local/lib/dillo/dpi/hello > > ./hello.filter.dpi > > I'm doing this as root. When I try this I get: > > hello.dpi:: starting... > > and that's it, nothing more, doesn't exit until I ctrl-c. > No error message. > ...what is it supposed to do? > > Regards, > Barry Kauler > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)lists.auriga.wearlab.de > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

1 0

[Dillo-dev]Re: bugfix for bug#500
by Jorge Arellano Cid April 8, 2004

April 8, 2004

On Thu, 8 Apr 2004, Andreas Mueller wrote: > Hi, Hi! > the attached small patch fixes bug#500. > > > Andreas Thanks a lot, that one was hard to chase! Commited. Cheers Jorge.-

1 0

[Dillo-dev]Theme for Dillo 0.8.0
by Gregg April 8, 2004

April 8, 2004

Hi all, I made a button theme for 0.8.0 - Cobalt. Enjoy! -- Gregg

2 1

[Dillo-dev]GTK 1.2 and Dillo's future
by John April 8, 2004

April 8, 2004

As a major fan of lite-weight apps I am very unhappy that so many of my favorite applications are being ported to GTK2. I've been following the Dillo Dev list and I know that there is an effort to port Dillo over to FLTK which may be a good alternative to GTK2. But I have to ask, why not just keep using GTK 1.2? GTK 1.2 is mature, and lite. Perhaps it will start an effort to keep GTK 1.x alive? John

2 1

[Dillo-dev]why use "ccc chain" instead of calling the function directly?
by Lei Jin April 7, 2004

April 7, 2004

Use "ccc chain" mechanism makes the code seeming uniform. But it cause the source code difficult to understand because lots of indirect function call and variety of parameters. I wonder whether we can call the target function directly instead of using "ccc chain", but I do not know if there is difference between these two methods ??? ( such as the process's address space??? )..... --------------------------------- Do You Yahoo!? 惠普TT游戏剧，玩游戏，中大奖！

2 3

[Dillo-dev]New dillo user (contributor?)
by January Weiner April 7, 2004

April 7, 2004

Hello, first of all, let me thank you for this great piece of software. It's fast, it's simple, it keeps up good Unix traditions -- small, efficient programs which do one job. I have used dillo a couple of years ago, but it was a little too brittle and not mature enough for me, especially due to the lack of tables (or was it CSS?) -- anyway, it is very nice now[*]. A thing that's really lacking (at least for me) -- is a.. man page. I'm an unbelievably traditional when it comes to man pages, mostly because of the apropos database[#]. Further, an introductory readme page for users (with shortcuts etc., and not necessarily compilator options) would also be a nice thing to have, I think. How about that -- if you do not have anything principally against man pages / readme's for newbie's, I'll write it, and promise to keep up with Dillo's releases for the next 12 months. I do not have much time, but at least a rudimentary man page should be in each programs distribution. Is there any document available on Dillos shortcuts and configuration, or should I download the sources right away? Regards, January P.S. A nice detail: when running dillo for the first time, make it copy the dillorc into ~/.dillo/. This is the first place a literate Unix user will look for a configuration when he or she notices that Dillo created ~/.dillo/. Tested on three individuals :-) [*] the only thing I really miss is the support for ISO-8859-2. [#] besides, it took me a couple of minutes to figure out that "s <keyword>" is not a thing you should type in the address widget, but an abbreviation for "ctrl-s keyword", esp. because ctrl-s is such a widespread shortcut for "save". -- ------------ Dr January Weiner 3 ------------------+--------------- Division of Bioinformatics, University of Muenster | Schlo�platz 4 (+49)(251)21634 | D48149 M�nster http://www.uni-muenster.de/Biologie.Botanik/ebb/ | Germany

1 1

[Dillo-dev]Disable toolbars
by Florian Angehrn April 7, 2004

April 7, 2004

if i don't want both toolbars, what do i have to change in the sourcecode? many thanks for your great product (and an answer :)!

2 1

[Dillo-dev]Can't start dpid
by Barry Kauler April 7, 2004

April 7, 2004

Hi, I'm not on the list, so hope this can be submitted! Kindly also reply a copy to bk(a)goosee.com I have been following Dillo for sometime, as a user, and recently upgraded to v0.8.0. Problem is, when I click on a ftp url, the message: "Error: can't start dpid daemon" So, I tried to start dpid directly on the commandline: # dpid # dpid.c:352: register_all: fatal error: -can't find the directory for dpis So, is there something missing here? -- what is dpis? Appreciate any advice on this! Regards, Barry Kauler

2 1

Re: [Dillo-dev]progress on AIX? (fwd)
by Jorge Arellano Cid April 7, 2004

April 7, 2004

---------- Forwarded message ---------- Date: Tue, 06 Apr 2004 22:29:57 +0200 From: Riccardo Mottola <rollei(a)tiscalinet.it> To: Jorge Arellano Cid <jcid(a)dillo.org> Subject: Re: [Dillo-dev]progress on AIX? Jorge Arellano Cid wrote: > > On Thu, 4 Mar 2004, Riccardo wrote: > > > > [...] > > > Please try changing these to int. This is: > > > > > > #define socklen_t int > > I did that right now and recompiled. Only a bunch of files recompiled. > > > > I still get the same SIGILL, illegal instruction. > > Does current CVS produce SIGILL too? This time, boostrapping and configuring was like a charm. but I get a SIGILL anyway... And no usable bt, as always. Program received signal SIGILL, Illegal instruction. 0x0 in ?? () from /usr/local/build/dillo-cvs/dillo/src/dillo (gdb) bt #0 0x0 in ?? () from /usr/local/build/dillo-cvs/dillo/src/dillo clueless. I remember there was a german guy on the list who used AIX. -R

1 0

[Dillo-dev]progress on AIX?
by Riccardo April 6, 2004

April 6, 2004

Hello, I posted the buildlog I got on AIX... did someone had a look at it to see if there are some warnings or errors that could explain the brokeness of dillo on aix? -Ric

2 4