- Dillo-dev - lists.mailman3.com

Re: [Dillo-dev] Rendering problem
by Jorge Arellano Cid Sept. 1, 2003

Sept. 1, 2003

On Thu, 28 Aug 2003, Ralph Slooten wrote: > On Thu, 28 Aug 2003 12:57:36 -0400 (EDT) > "Andrew A. Gill" <superluser(a)frontiernet.net> wrote: > > > I've been having a problem with dillo rendering some portions of text. > > For instance, the Google sponsored links always take up vertical space > > before the results. > > > > Normally, this isn't something that I really care about, but now it's > > causing slashdot to be rendered as black-on-black text, thus depriving me > > of my ability to read about the new MD5 sums that the RIAA is using. > > Yes, I'm getting this too since today. It's probably a small html error > somewhere, but it's totally skrewed up dillo's rendering to the fullest here. Unfortunately slashdot is sending awful HTML-like content. The black text can be explained because they explicitly set the background, textcolor and visited links to black! (<BODY ...>). Probably it changes with CSS. > > Since about 2 weeks ago I'm also getting a black border on the right (with > exception to today of course where most of the page is black) which just takes > up valuable space ;-) > > Tried the light mode too like Frank suggests, but I prefer the default layout > myself. Anyway, it's not a dillo problem I think, as I get a total of 530 errors > just on the index page itself!!!!! Check now too if ya want: > http://validator.w3.org/check?uri=http%3A%2F%2Fwww.slashdot.org%2F Try with "force_my_colors=YES". Now, it still shows several rendering problems. If those are because of lack of implementation of "floats" we should fix it someday. If it's because of bad HTML, you know our policy. OTOH, I believe slashdot webmasters will not pose major problems to fix their HTML if they're emailed with the facts... Please investigate those and report to them. Cheers Jorge.-

4 5

path for support chinese
by super_hoo Sept. 1, 2003

Sept. 1, 2003

I knowed that it had a patch for dillo0.7.2 to supportting Chinese. Where could I find this patch ? thanks a lot. ______________________________________ =================================================================== µ±µ±ÍøÈ«³¡ÒôÏñ5ÕÛ·â¶¥£¬ÓÅ»ÝŒŽœ«œáÊø£¡ (http://ad4.sina.com.cn/sina/dangdang0825.html)

1 0

Problems with tab patch
by Nigel Wilkinson Aug. 29, 2003

Aug. 29, 2003

Evenin' all I'm trying to patch the CVS with the tab patch but I haven't used patch much. The problem I'm haveing is that I don't know which directory to run the path from, it keeps complaining that it can't find the file to patch Cheers Nigel

2 4

[PATCH]: commands & auto-reload (was Re: dillo / time-controlled reloads)
by Melvin Hadasht Aug. 29, 2003

Aug. 29, 2003

[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

2 5

Rendering
by Jorge Arellano Cid Aug. 29, 2003

Aug. 29, 2003

Hi Sebastian! Hope you're not under a pile of workload... Please review this site: http://cocoon.apache.org/index2.html When loaded slowly (dialup speed) it renders the leftmost column too wide (almost a screen), but Back&Forward fixes it. I you can also give a look at the slashdot problem it'd be great. I'm much more interested in the first though. Regards Jorge.-

1 0

Re: Tab + frame patch, any progress?
by Jorge Arellano Cid Aug. 29, 2003

Aug. 29, 2003

On Wed, 27 Aug 2003, Frank de Lange wrote: > Any progress on the CSS front by the way? Sometime ago we concluded with Sebastian that it may take near three months of work of both of us. We're focusing on other priorities now. I hope we can review your patch soon with him. Cheers Jorge.-

1 0

Running external Gtk programs under Tabs (fwd)
by Jorge Arellano Cid Aug. 29, 2003

Aug. 29, 2003

---------- Forwarded message ---------- Date: Wed, 27 Aug 2003 23:48:14 -0700 From: t <loveall(a)qwest.net> To: Jorge Arellano Cid <jcid(a)softhome.net> Subject: Running external Gtk programs under Tabs Jorge, Please forward this to the dillo/dev mailing list unless you think it is not appropriate. Nice job on dillo, guys! Have been using it since at least 0.2.1. Nice work on the tabs, Frank. They have added a whole new dimension to dillo. Recently, while working on a multi-media project, noticed that I had way too many instances of a text editor open. Couldn't easily find the desired file. About then Frank put up the tab/frame patch. Spent a day or so getting external Gtk apps to run in a tabbed window. This turned dillo into an MDI interface with built-in file picker and HTML help file viewer. This has been working for me in a stable manner, e.g. no seg faults, for about two weeks under heavy use. Which means it will only take someone else about 5 minutes to induce a failure:-). Have modified a file manager, my personal text editor and the erwin HTML editor to run as client Gtk apps, just like dillo. As a matter of fact, dillo can run itself as an external Gtk app in a tabbed window. The patch file for the tab/frame patched version of dillo is set up to do this as a working example. You can download it from: http://www.users.qwest.net/~loveall/xid8-patch.gz !!!! NOTE !!!! This patch is valid only on dillo-0.7.3 patched with Franks version 9 tab/frame patch: http://www.geocities.com/ikbenfrank/dillo-0.7.3-20030821-tabs.patch.gz To modify a typical Gtk app to act as a client requires just the following: In function main(), add these lines at the beginning just after the data declarations: guint32 xid = 0; int i = 1; if (i < argc-1 && !strcmp(argv[i++],"-x")){ xid = strtol(argv[i], NULL, 10); argc -= 2; argv += 2; if(xid == LONG_MIN || xid == LONG_MAX) xid = 0; } This requires that the first two args when calling dillo be '-x <Xid number>'. Find and replace the (typically) single line: main_window = gtk_window_new (GTK_WINDOW_TOPLEVEL); with: if(!xid) main_window = gtk_window_new (GTK_WINDOW_TOPLEVEL); else main_window = gtk_plug_new (xid); See also the working source which references 'xid' in dillo.c and interface.c. Thanks again, to the dillo crew. You guys are awesome. Regards, Terry Loveall

2 1

CinePaint and Windows port
by Robin Rowe Aug. 28, 2003

Aug. 28, 2003

Hi. I'm the project leader for CinePaint, an open source paint program used mainly by the motion picture industry. Our code was branched from GIMP in 1998. How would the Dillo project feel about Dillo being embedded in another application as a help browser? We're looking for a new help system browser and considering Dillo. We are impressed how compact your implementation is. We only need a limited set of HTML features: links, images, tables, bullet lists, number lists, headings, ordinary text, bold, and italic. In these features we need the browser to be absolutely stable. Any issues there? We support all platforms, including Windows. One of the first things I would intend to do is port Dillo to Windows. I saw in your archives that you had made some effort in that direction, but it seemed to peter out. What are the problems? Thanks! Robin --------------------------------------------------------------------------- Robin.Rowe(a)MovieEditor.com Hollywood, California www.CinePaint.org Free motion picture and still image editing software

4 5

Rendering problem
by Andrew A. Gill Aug. 28, 2003

Aug. 28, 2003

I've been having a problem with dillo rendering some portions of text. For instance, the Google sponsored links always take up vertical space before the results. Normally, this isn't something that I really care about, but now it's causing slashdot to be rendered as black-on-black text, thus depriving me of my ability to read about the new MD5 sums that the RIAA is using. (bug 493) -- |Andrew A. Gill |I posted to Silent-Tristero and| |<superluser(a)frontiernet.net> |all I got was this stupid sig! | |alt.tv.simpsons CBG-FAQ author | | | (Report all obscene mail to Le Maitre Pots)| |Nothing here yet: <http://www.needsfoodbadly.com> Temporary sig: -- But thanks for everything else.

3 2

Re: Re: dillo / time-controlled reloads
by Jorge Arellano Cid Aug. 28, 2003

Aug. 28, 2003

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

2 1