April 2004 - Dillo-dev - lists.mailman3.com

Re: [Dillo-dev]Can't start dpid

by Jorge Arellano Cid

On Wed, 14 Apr 2004, Barry Kauler wrote: > > > the problem is dpid won't start in my custom Puppy Linux > > > distro. > > Jorge, > 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. Hmmm, it could be an issue with wget. The https dpi is an experimental prototype, that's why it wasn't announced with fanfare in 0.8.0. Currently, Madis and I are working on making an SSL library based https dpi (not wget based)... Please don't worry about the https dpi until it comes out of this "for developers" stage. > > 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 This should be working. > So, I celebrated too soon! > Do these messages mean anything much to you? > Any suggestion what I should try next? Yes and yes. First, check whether the bookmarks dpi works. If it does, then the dpid launch (by dillo) and dpi launch (by dpid) are ok. If this is true, test with the hello and the ftp dpis. If all of them work, we should be looking closer into the downloads dpi. Cheers Jorge.-

April 15, 2004

Re: [Dillo-dev]Can't start dpid

by Barry Kauler

> > 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

April 14, 2004

Re: [Dillo-dev]Can't start dpid

by Barry Kauler

> > the problem is dpid won't start in my custom Puppy Linux > > distro. Jorge, 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

April 14, 2004

[Dillo-dev]international encodings

by honza m.

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

April 14, 2004

[Dillo-dev]dillo 0.8 fails to build on OS X 10.2.8

by Brett Wynkoop

FYI- Just tried to build a stock out of the box dillo 0.8 on Mac OS X. Here are the results: In file included from /usr/local/include/gtk-1.2/gdk/gdktypes.h:33, from /usr/local/include/gtk-1.2/gdk/gdk.h:31, from /usr/local/include/gtk-1.2/gtk/gtk.h:31, from mime.h:11, from mime.c:12: /usr/local/include/glib.h:491: conflicting types for `gssize' /usr/local/include/glibconfig.h:57: previous declaration of `gssize' /usr/local/include/glib.h:492: conflicting types for `gsize' /usr/local/include/glibconfig.h:58: previous declaration of `gsize' *** Error code 1 Stop in /Users/wynkoop/src/www/dillo-0.8.0/src/IO. *** Error code 1 Stop in /Users/wynkoop/src/www/dillo-0.8.0/src. *** Error code 1 Stop in /Users/wynkoop/src/www/dillo-0.8.0. *** Error code 1 Stop in /Users/wynkoop/src/www/dillo-0.8.0. ibook:~/src/www/dillo-0.8.0: Looks like a tail chasing issue to me. Will try and much with it sometime latter and see what I can do to fix it. -Brett -- DRM is theft! We are the stakeholders! http://www.nyfairuse.org/

April 13, 2004

[Dillo-dev]Re: bug in dillo.0.8 rendering

by Jorge Arellano Cid

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.-

April 12, 2004

Re: [Dillo-dev]A button theme for Dillo 0.8.0

by Gregg

Hi Jorge, I did, thanks! Sorry about the double post - I couldn't remember which email I used for the Dillo list, so I sent it from both ;-) Thanks again! -- Gregg Behold, Jorge Arellano Cid scribed in runic symbols on a tube chassis: > > > On Wed, 7 Apr 2004, Geek wrote: > > > While I was stuck with no internet, I made a theme for Dillo I call "cobalt". > > > > Enjoy! > > Oh, it was added to > > http://www.dillo.org/Icons/ > > by Apr 8! :-) > > I assume you didn't get the answer message. > > Thxs & Cheers > Jorge.- > > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)lists.auriga.wearlab.de > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

April 12, 2004

[Dillo-dev]what's the use of "EndTag" component of struct TagInfo?

by Lei Jin

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

April 12, 2004

Re: [Dillo-dev]Can't start dpid

by Jorge Arellano Cid

On Sat, 10 Apr 2004, Barry Kauler wrote: > 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? It seem so! You need either the global rc files (dillorc and dpidrc), or placing them under each ~/.dillo directory in every account. > 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! Please confirm me that it works for you now. > 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. Appart from the comments for each option, and maybe format, the only additions to 0.8.0's dillorc are: <q> # The new parser is more accurate detecting HTML errors. # Also pages may look better or worst (after all is bad-formed HTML). # Uncomment this line if you want to use the old parser. #use_old_parser=YES # Generic messsages (mainly for debugging specific parts) # Uncomment the following line to disable them. #show_msg=NO </q> You can safely append those lines to each user's dillorc and thus, have them upgraded. > Looks like Puppy and Dillo are back in business! > Puppy v0.8.5 should be out soon, like maybe another week. Great. When I get your confirmation of Dillo working OK on it, I'll add Puppy to our compatibility list and place a link to its home page. Cheers Jorge.-

April 12, 2004

Re: [Dillo-dev]Can't start dpid

by Jorge Arellano Cid

On Sat, 10 Apr 2004, Barry Kauler 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. Good to know! Let's make 0.8.0 also work then... > > 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? Exactly that! Well, it's a filter. I was just trying to assert is that it was present, at the right directory, and with exec permissions. Now, I can search the bug elsewhere. Cheers Jorge.-

April 12, 2004