- Dillo-dev - lists.mailman3.com

Frameset & lanlaw.org

by Frank de Lange

I just noticed that my current version of the tab+frame patch still has problems with sites like lamlaw.com, which put body content outside of frameset content. Even though this is against the spec, I've changed my current version of the patch so it displays the right (frameset) content for sites like this. BTW, lamlaw.com is really weird... The sequence of tags is html - head - frameset - /frameset - noframes - /head - body - /body - /noframes - /frameset - /html. So, it has frameset inside head (wrong), /head inside noframes, an extra /frameset, etc. The document claims to be html-4.0-transitional. Sure. Cheers//Frank -- WWWWW ________________________ ## o o\ / Frank de Lange \ }# \| / +46-734352015 \ \ `--| _/ <Hacker for Hire> \ `---' \ +31-640037120 / \ frank(a)unternet.org / `------------------------' [ "Omnis enim res, quae dando non deficit, dum habetur et non datur, nondum habetur, quomodo habenda est." ]

Aug. 26, 2003

New dpid patch

by Ferdi Franceschini

There is a new dpid patch for dillo-0.8-pre available from http://www.geocities.com/ferdif2003/ Plugins are now stored in a directory structure under libdir/dillo/dpi. You need to put dpi_dir=/usr/local/lib/dillo/dpi in ~/.dillo/dpidrc so that dpid can find the plugins, there should be no other entries in this file. Dpid now uses a .filter suffix in the plugin name to identify plugins which read and write to stdio (eg hello.filter.dpi). The following changes affect the CVS repository: Renamed dpiddir.[ch] to dpi_socket_dir.[ch] New files dpi_service.[ch] Cheers, Ferdi

Aug. 24, 2003

Re: [PATCH]: commands & auto-reload (was Re: dillo / time-controlled reloads)

by Henning Brauer

On Fri, Aug 22, 2003 at 11:30:47PM +0200, Melvin Hadasht wrote: > [Henning, you may be interested: the patch implements a --reload option] hmm, I have one more issue. dillo caches the images too well. try looking at any mrtg-generated page. the mrtg graphs are usually rebuilt every N minutes, where N=5 in my case. tho, now, at 3:20h, it still shows the images from ~ 1:30h. old data is not relevant in this case :-(

Aug. 24, 2003

Re: [PATCH]: commands & auto-reload (was Re: dillo / time-controlled reloads)

by Henning Brauer

On Fri, Aug 22, 2003 at 11:30:47PM +0200, Melvin Hadasht wrote: > [Henning, you may be interested: the patch implements a --reload option] guys, you rock. it's just two days ago that I asked for that. It works great on OpenBSD/i386 and OpenBSD/sparc, all OpenBSD -current (3.4-beta atm). there are two small problems: -if you specify a small reload time, and by that time is over before the page is actually loaded -> coredump -on sparc, using the "void" input drivers for keyboard and mouse -> coredump that must be the visibility check? both issues are unfortunaltely pretty much showstoppers in my application :-((

Aug. 23, 2003

Re: Re: dillo / time-controlled reloads

by Jorge Arellano Cid

On Wed, 20 Aug 2003, Melvin Hadasht wrote: > > Hi Jorge & Melvin, > > Hi Henning & Jorge, > > (Is there a reason why this is not on the ML?) The only reason is that I pressed "reply" on a mail sent to my personal address. :-) > > > > > there's one bit missing. there is NO concept at all about time-based > > > > reloads. the meta refresh header would be reasonably close, but even > > > > better would be something like > > > > > > > > dillo -reload-every 60 http://blah/cgi-bin/blubb.cgi > > > > > > > > it should reload that URL every 60 seconds in that case no matter what. > > > > > > I think reloading it if upon display is also a good choice. I > > > mean, let the user browse other pages without reloading the > > > special URL, and reload it when it's back on display and the > > > timeout has been reached. > > I don't see why a browser should reload an URL if it is not currently viewed, but > I'm not a web expert. > > > > > I looked into adding a sigalrm handler an solving it this way, but > > > > then it turned out that is more complicated > > We can use the glib timeout functions for that. Yes, timeouts are simpler. > > Here is how I would implement the feature: > > - an internal Dillo function to mark/unmark a URL with > "reload periodically when viewed", A simple flag, maybe in the DilloUrl or in the cache entry. > it will also create a timeout > callback that will reload the URL if it is currently viewed. A periodiciy of 0 will > stop reloading. For that, I need to take a look on the browser history/cache, too. Don't worry, I can do that easily (I know pretty well the cache). I'd prefer you to focus on the dpi part. I mean, this dpi will end asking dillo to do the job. For instance: <dpi cmd='set_reload_URL' url='...' always='true'> > > - add a "-r, --reload-every" command line option that calls that function. > In fact, when I finish implementing the "(remote-)command" option, it would be > something like: "-c open(URL, refresh=60)" (that is if I finally decide that > supporting commands with more than one argument is worth the work). Hmmm, I think a simple cli switch to tell dillo to listen to the reloads.dpi is enough: dillo -reloads (or something like it) Then, the client communicates with the dpi socket. All this API is what needs to be designed. I'd appreciate you to work on this part. > > > The first duty is to define what is required for a good, > > > general purpose, kind of reloading dpi. The next one is to reduce > > > the features to a minimum working set, then implement! > > parameters: URL, periodicity (seconds), when (visible|always). This is a good start! For instance: fprintf(reloads_dpi_socket, "push http://localhost/someurl visible\n"); may be all the client program needs to know. Of course it could also be something like: fprintf(reloads_dpi_socket, "<dpi cmd='reloads' url='http://localhost/someurl' visible>" * The first example makes more clear that it goes trough reloads.dpi who parses it and then sends a dpip tag to dillo to request the job done. This may also be handy: "<dpi cmd='reloads' url='http://localhost/someurl' stop>" Note that it may be good to integrate the remote control functionality into the same dpi (and maybe call it remote.dpi?). This means adding a simple and useful API for help programs to use. For instance to let them push new URLs into the same instance of dillo (and not having to start a new dillo per requested page). Ex: The client app. asks the remote control dpi whether there's a running instance of dillo. YES -> send new to-be-pushed URL NO -> start "dillo -rc" (remote control) send new to-be-pushed URL Please polish along these lines. Cheers Jorge.-

Aug. 23, 2003

Re: [Dillo-dev] libc dependency in 0.8.0pre (bug 487)

by Jorge Arellano Cid

On Thu, 21 Aug 2003, Joerg Sonnenberger wrote: > On Wed, Aug 20, 2003 at 01:02:40PM -0400, Jorge Arellano Cid wrote: > [snip] > > Don't panic! > > > > The mkdtemp() issue needs to be solved. Thanks for reporting > > the problem. > > > > If configure has a way to deal with it, we'd need to find it > > out how. If not, just to think of something else (as implementing > > a custom function as you did, or see if there's a wrapper in glib > > etc.) > > > > I'm open to suggestions. > > Well, you could add a portable implementation e.g. from the *BSD libc > to dillo and a AC_CHECK_FUNCS to autoconf to conditionally include > that code. This is the way coreutils and other GNU packages work. > > I'll send you a working copy if you want. Of course! It'd be of great help. Cheers Jorge.-

Aug. 23, 2003

Re: [Dillo-dev] [PATCH]: commands & auto-reload (was Re: dillo / time-controlled reloads)

by Melvin Hadasht

Sorry, it looks the attachment was truncated. Here it is again, gzipped.

Aug. 22, 2003

[PATCH]: commands & auto-reload (was Re: dillo / time-controlled reloads)

by Melvin Hadasht

[Henning, you may be interested: the patch implements a --reload option] Hi, To implement the server and remote commands feature in Dillo, I'm going to go step by step. First, I'll implement commands to control Dillo at startup time, then I'll implement the server mode (where a Dillo instance can send the aforementioned commands to another Dillo instance). This is because I may try two differents approaches for the server mode part and because the commands are just a generalization of the command line options and can be implemented separately. Here is my first step: implement commands (like -c "open(URL)"). Patch is attached and is against CVS version. This is a generalization of the command line interface, and in fact, most of the old command line options are translated to a Dillo -c command. The advantage of such approach is that the commands can take optional parameters, like in: dillo -c "open(URL newwindow reload=10 fullwindow=yes)" which is approximately equivalent to: dillo -f -r 10 URL The commands are passed to Dillo as arguments to the -c, --command command line option: dillo -c "open(http://www.google.com)" 1. Command Syntax The argument to the -c command line option is of the form: CMD([STRING][ PARAM=VALUE]...) CMD: command name STRING: first and generic argument: in general a URL or yes|no PARAM: name of optional parameter VALUE: value of optional parameter. Currently, only booleans (yes|no) and integer values are supported. Boolean value can be omitted, in which case the value is considered to be "yes". Integer value cannot be omitted. Parameters are separated with a single space (no commas, to simplify the parser) Commands can be divided into two groups: actions commands, and options commands 2. Action Commands: They do some action: currently implemented commands: open(URL [ fullwindow[=yes|no]] [ reload=SECONDS] [ spamsafe[=yes|no]] [ xid=XID]) parameters speak for themselves. The "reload" parameter is a new feature: it allows to reload the URL each SECONDS seconds. The reload is halted when the page is not viewed and restarted if the user comes back to it. exit() exit the instance. This will be useful when passed to another Dillo instance running as a server. Other commands can be added. The framework is quite flexible and extensible. 3. Options Commands These commands set some options that will affect the following commands. For example, the parameters used in the open() command act only on that particular URL. But it can be useful to be able to set some defaults values. The currently implemented commands that influence these defaults are: fullwindow([yes|no]) reload(SECONDS) spamsafe([yes|no]) xid(XID) all open() commands that come after these options commands will have these default values, unless explicitly overridden. 4. Examples: dillo -c "open(http://www.google.com)" -c "open(file:///home/mhadasht/test.html newwindow spamsafe)" will open two windows: the first with google, and the second with the local file opened in spamsafe mode. dillo -c "reload(10)" -c "open(http://www.freshmeat.net)" -c "open(http://news.google.com newwindow)" will open 2 windows and will reload both URLs each 10s. This is equivalent to: dillo --reload 10 http://www.freshmeat.net http://news.google.com 5. Implementation details: 5.1. Command Line Parsing Command line options other than the help/version options are translated into a -c command and stored in a list. The list of commands is then executed (or, when the server mode will is implemented, sent to another Dillo instance) 5.2. Reload Function a URL can be set to auto-reload itself if it is currently viewed. For that, a new member (reload_interval [milliseconds]) to DilloUrl is added and set with a_Url_set_reload(). Each BrowserWindow can trigger a timer function if the viewed URL (Nav_open_url()) has a non-zero reload_interval. (As soon as another URL is viewed, or when the BrowserWindow is destroyed, the eventually pending timeout function is removed.) The timer is of the one-shot type: when it is triggered, it requests its BrowserWindow to reload the URL, then it stops itself. There is currently no UI to start/stop an auto-reload of a URL, but it is just a matter of using a_Url_set_reload() to a non-zero or a zero reload interval. 6. Remark The -c command and the normal command line options can be seen as two ways of doing the same thing: passing commands to Dillo. But the -c command is more generic and flexible and has a more powerful syntax. 7. Future Plans I plan to implement the server mode. After reading the dpi doc and source, I found that it cannot be used to make Dillo act as a plugin unless we accept to have only one Dillo server. This is because the socket names are tightly linked to the service name. Each service has only one socket. Whereas Dillo servers must have a distinct socket. If the we add another argument to the "start_plugin" cmd: <dpi cmd="start_plugin" msg="dillo" param="SERVER_NAME"> and if we modify the socket naming scheme, then it could be possible. I have to think about that again. But I may still use the communication infrastructure of the dpi. If I find this overkill, I'll revert to the straightforward approach I used before, that is, I won't use the dpi framework. OK, it's late, I hope I managed to be somewhat clear... Cheers. -- Melvin Hadasht

Aug. 22, 2003

finger plugin

by Andreas Schweitzer

Hi, as promised in a previous mail. Here is the still quite rough finger dpi intended for interested developers : http://www.hs.uni-hamburg.de/~stcd102/dillo/ http://www.hs.uni-hamburg.de/~stcd102/dillo/adpi-0.1.tar.gz It's configure.in is essentially dillo's configure.in :-) you could actually just put finger.c in the ./dpi/ subdirectory of dillo and adjust Makefile.am accordingly. but now I have an actual distribution :-) In the tarball is also what I call so far a library ... well, or at least the routines that have been re-used over and over. Lastly, there is also an experiment : a term plugin, which lets you call arbitrary programs from within dillo (read the source, though !) Installation: just copy the created .dpi files to ~/.dillo/ and edit ~/.dillo/dpidrc (as long as this file exists), then go to dpi:/finger/ If you want dillo to actually recognize the finger URL you will have to edit src/IO/Url.c and sr/capi.c. Search for the string "ftp" inside these two files and duplicate the relevant part for the finger protocol. Or await how dillo evolves :-) Cheers, Andreas -- **************************** NEW ADDRESS ****************************** Hamburger Sternwarte Universitaet Hamburg Gojenbergsweg 112 Tel. ++49 40 42891 4016 D-21029 Hamburg, Germany Fax. ++49 40 42891 4198

Aug. 22, 2003

Re: [Dillo-dev] [PATCH] version 9 of tab+frame patch, frame support 'complete' (?)

by Andreas Schweitzer

Hi, > http://www.geocities.com/ikbenfrank/ > > More specifically for both versions: > > Dillo 0.8.0-pre (CVS) > ===================== > http://www.geocities.com/ikbenfrank/dillo-20030821-tabs.patch.gz > size: 66661 bytes (gzipped, as downloaded) > 281416 bytes (uncompressed) > md5sum: 6afb73d97d3db88c629726cef100f604 (gzipped, as downloaded) > c3b6ee3095d4b230a78cf836516e0023 (uncompressed) > > Dillo 0.7.3 (release) > ===================== > http://www.geocities.com/ikbenfrank/dillo-0.7.3-20030821-tabs.patch.gz > size: 93929 bytes (gzipped, as downloaded) > 399156 bytes (uncompressed) > md5sum: 0363c9ad9f94df9b1bca23e5489e5c5e (gzipped, as downloaded) > 8fca8c49a01cd6a6103661720eb8d60d (uncompressed) or again from my mirror. This time : http://www.hs.uni-hamburg.de/~stcd102/dillo/ Cheers, Andreas -- **************************** NEW ADDRESS ****************************** Hamburger Sternwarte Universitaet Hamburg Gojenbergsweg 112 Tel. ++49 40 42891 4016 D-21029 Hamburg, Germany Fax. ++49 40 42891 4198

Aug. 22, 2003