9 Apr
2011
9 Apr
'11
7:52 p.m.
Benjamin wrote:
A much more practical solution, as far as I'm concerned, is simply to build that functionality into the browser: - It's simpler, since there's on interprocess communication required. - It's more portable, for the same reason. - It's easier to distribute, since you only need one executable.
I personally like the idea of dillo in one piece. I think a lot of people who give it a try don't get dillo + dpid + the dpis talking to each other correctly, and then they don't want to waste their time fighting with a random unfamiliar computer program. (Semi-relevant: I'm trying softphone programs out now, and they all demand lots of everything, and I can't tell which ones are worth how much trouble.)