Hi there! This has been a very busy week. I didn't anticipate how much work the dpid (dpi daemon) integration could take. Don't panic though!, the code that binds it all is running (to some extent) in my machine. The time consuming problem is that while making the integration, a lot of design matters spring in, and they take a lot of time to solve. The good news is that it all starts to shape into a more clear design (the code is still hackish at parts, but it is clear what, where and how to fix it). While working the gory details of it, I realized it'd be a good idea to make the 0.7.3 release with what we have now (plus a little bug fix we're working on with Sebastian). That way, there'll be less pressure on us while polishing the new dpid implementation, and hey!, it's been a long time since our last release. I'll keep the CVS free of the dpid code until the 0.7.3 release is done. For the meanwhile, I'll provide a tarball to the new code. (and if I can't wrap the new code before Monday, I'll provide a link to the latest dpid testing tarball I have). Cheers Jorge.-
Hi!
This has been a very busy week. I didn't anticipate how much work the dpid (dpi daemon) integration could take. Don't panic though!, the code that binds it all is running (to some extent) in my machine. The time consuming problem is that while making the integration, a lot of design matters spring in, and they take a lot of time to solve.
The good news is that it all starts to shape into a more clear design (the code is still hackish at parts, but it is clear what, where and how to fix it).
While working the gory details of it, I realized it'd be a good idea to make the 0.7.3 release with what we have now (plus a little bug fix we're working on with Sebastian). That way, there'll be less pressure on us while polishing the new dpid implementation, and hey!, it's been a long time since our last release.
I'll keep the CVS free of the dpid code until the 0.7.3 release is done. For the meanwhile, I'll provide a tarball to the new code. (and if I can't wrap the new code before Monday, I'll provide a link to the latest dpid testing tarball I have).
First, the final code for the 0.7.3 is on the CVS (unless you find a bug in it). It will be released by Wednesday, so please give it a hard test today and tomorrow! With regard to 0.8.0-pre (aka dillo with dpid), here's the good news: * Finally I have a tarball that does bookmarks and downloads with dpid (using wget)! It can handle multiple plugins and is working smoothly. I want to add one more plugin (at least) and update the documentation before commiting it to the CVS (after releasing 0.7.3 of course). For those very interested in studying it, please review: http://dillo.org/download/dpid4.tgz (not my tarball but the dpid testing suite itself) Cheers Jorge.-
I have see the dpi code and think that it is a very good approach. Only one think: how do you integrate a plug-in without patch dillo? I known that dpi is not finished, but i am impatient. If the PIs can add menu entries to dillo menus it can be easy to start/call a PI when a menu entrie is clicked and the PI can ask some dillo state(like url below the mouse) or open a save dialog or etc using a dpi tag. A cfg file can asociate prefix(ftp://), sufix(.swf) and menu entries with PIs. It can be modified on PI install or be generated. There must be some code for dinamics menus in dillo for history yet. About PIs that render to a zone in a web page it can be done like Sylpheed-claws integrate dillo in it(GTK X sockets or something that i think). I hope to help something even if nobody ask. Diego. El Mon, 7 Jul 2003 15:35:30 -0400 (CLT) Jorge Arellano Cid <jcid@softhome.net> escribio:
Hi!
This has been a very busy week. I didn't anticipate how much work the dpid (dpi daemon) integration could take. Don't panic though!, the code that binds it all is running (to some extent) in my machine. The time consuming problem is that while making the integration, a lot of design matters spring in, and they take a lot of time to solve.
The good news is that it all starts to shape into a more clear design (the code is still hackish at parts, but it is clear what, where and how to fix it).
While working the gory details of it, I realized it'd be a good idea to make the 0.7.3 release with what we have now (plus a little bug fix we're working on with Sebastian). That way, there'll be less pressure on us while polishing the new dpid implementation, and hey!, it's been a long time since our last release.
I'll keep the CVS free of the dpid code until the 0.7.3 release is done. For the meanwhile, I'll provide a tarball to the new code. (and if I can't wrap the new code before Monday, I'll provide a link to the latest dpid testing tarball I have).
First, the final code for the 0.7.3 is on the CVS (unless you find a bug in it). It will be released by Wednesday, so please give it a hard test today and tomorrow!
With regard to 0.8.0-pre (aka dillo with dpid), here's the good news:
* Finally I have a tarball that does bookmarks and downloads with dpid (using wget)! It can handle multiple plugins and is working smoothly.
I want to add one more plugin (at least) and update the documentation before commiting it to the CVS (after releasing 0.7.3 of course).
For those very interested in studying it, please review:
http://dillo.org/download/dpid4.tgz
(not my tarball but the dpid testing suite itself)
Cheers Jorge.-
_______________________________________________ Dillo-dev mailing list Dillo-dev@lists.auriga.wearlab.de http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev
On Mon, 14 Jul 2003 10:18 am, Diego Sáenz wrote:
I have see the dpi code and think that it is a very good approach. Only one think: how do you integrate a plug-in without patch dillo? I known that dpi is not finished, but i am impatient. If the PIs can add menu entries to dillo menus it can be easy to start/call a PI when a menu entrie is clicked and the PI can ask some dillo state(like url below the mouse) or open a save dialog or etc using a dpi tag. A cfg file can asociate prefix(ftp://), sufix(.swf) and menu entries with PIs. It can be modified on PI install or be generated. There must be some code for dinamics menus in dillo for history yet. About PIs that render to a zone in a web page it can be done like Sylpheed-claws integrate dillo in it(GTK X sockets or something that i think). I hope to help something even if nobody ask.
Diego.
Also, would the dpi code also allow shockwave, java, client-side scripts, and other plugins to be added, if re-written (ie, utilising kaffe for java). I know that the plugins themselves will take a LOT of work, but I'm asking about the actual dpi...
On Mon, Jul 14, 2003 at 02:18:49AM +0200, Diego S?enz wrote:
I have see the dpi code and think that it is a very good approach. Only one think: how do you integrate a plug-in without patch dillo? I known that dpi is not finished, but i am impatient. If the PIs can add menu entries to dillo menus it can be easy to start/call a PI when a menu entrie is clicked and the PI can ask some dillo state(like url below the mouse) or open a save dialog or etc using a dpi tag. A cfg file can asociate prefix(ftp://), sufix(.swf) and menu entries with PIs. It can be modified on PI install or be generated. There must be some code for dinamics menus in dillo for history yet. About PIs that render to a zone in a web page it can be done like Sylpheed-claws integrate dillo in it(GTK X sockets or something that i think). I hope to help something even if nobody ask.
At the moment there is no means for adding dpi menu entries or buttons to dillo, and it may be a long time before this is implemented. In the meantime maybe we could create a plugins page of dpi urls to launch plugins and then simply provide a link to it on the splash screen. Cheers Ferdi
Jorge Arellano Cid wrote:
Hi there!
This has been a very busy week. I didn't anticipate how much work the dpid (dpi daemon) integration could take. Don't panic though!, the code that binds it all is running (to some extent) in my machine. ...snip...
Cheers Jorge.-
I have been looking at the dpid, and from what I can see it looks good, it would be a piece of cake to whip up some usefull dpi's now :-) ... I will however dig a bit more, the issue that I am concearned is if it prohibits some action to be implemented, ( workarounds are ok for me :-) ). I also have a related question about the dpi's, whith the new interface, how it fx. a https dpi supposed to work ? and would it be possible to make fw a svg dpi ? ( thus enabling the dpi to do the rendering ? Anyhow, for my stumbling attempts whith dpi's it seems to be fully adequat. / regards, Lars Segerlund.
participants (5)
-
Diego Sáenz
-
Ferdi Franceschini
-
Jorge Arellano Cid
-
Lars Segerlund
-
TheStar