I agree, I have been trying to 'break out' the bookmark dpi into a loadable object file, ( loads at runtime, and installs the button and such ), in order to do work on a dpi plugin myself. If something about loading dpi modules were in place it would be much nicer. I have tried to hack a list of dpi modules in .dillo/dpis which is loaded at runtime, but so far not much sucess. Is there a plan on how these things will work in the future ? Because then one can progress with the dpi itself and the infrastructure. / Lars Segerlund. Andreas Schweitzer wrote:
Hi,
Just a comment on one of your plans :
Appart from that, I still have to finish the design of dpi initialization, addition, managing etc. (needed to support several dpis at the same time).
I think this will be important, since it kept me somewhat from playing with dpi's. I did some experiments, but an automatic dpi initilization makes coding much easier. And I have the feeling others think the same :-)
Something like dpi:/foo/ starts the dpi foo[possible-extra-name-part] from some location like $PATH or some other "repository". And dpi:/foo/command passes "command" to the dpi foo. Just some rambling :-)
Cheers, Andreas