On Mon, 3 Oct 2005, Paul Fox wrote:

i posted this some time ago. are there any developers on the list? i'm wondering if i should just give up on using dillo for any real projects...

http://teki.jpn.ph/pc/software/index-e.shtml The patch there seems to contain updated version of the cache control patch.

...

i was surprised when i figured out that the current dillo code doesn't support any sort of "no cache" or "expires" facility.

it seems that this was done in 2003, in a patch referenced here: http://lists.auriga.wearlab.de/pipermail/dillo-dev/2003-August/001039.html

i tried applying it, and resolving the (many) differences myself, but i seem to have botched it, because now some of my pages don't display at all. :-)

is there a more current version of this patch around? i think it's important functionality...

Hi all not wanting to start a flame war, so any reply, please send directly to my email i feel that i have to reply to this, because many newcomers dont really understand dillo, nor take the time to read past posts in the mailling list to know why dont have replies to some topics. please note that i'm not a developer, not even a small one, just a user and "beta tester" old enough in the mailling list.

...

i posted this some time ago. are there any developers on the list?

yes, but there are only 2 main devs, both usually very busy and try to spend more time coding than reading emails. on that message, there wasnt many things to say... no dillo dont have any expire support, and no one knows when it will have one because the main priority is now the port to FLTK

Hopefully, dillo will move ahead, and in particular do things such as frame support, tabbed browsing, etc. (Apparently, several pactches were done, but it was never incorporated into dillo for reasons best known to the head developers.)

if you had read the mailling list better, you would find that the frame patch was welcome, but it was also huge and changed many of the dillo internals. it was asked to break the patch in small ones to be easy to audit and merge, but instead (and unfortunately ) the patch maker kept adding new thing, making the patch even bigger. after several other things, the patch stop being updated and with dillo code improving, it stopped to work and was (still) too big for someone to keep it in sync or break it up.

What dillo seriously needs is to incorporate stuff whereby browsing becomes a good experience.

dillo will never merge code just because its useful, it must also follow the same line as the existent code... dillo was build to be small and fast, not to be a new mozilla just because there is a patch to call external programs based in the mime type, that doesnt means that it the best way to do it, and even worst, if its safe to do it...

It is no good if we have to use another browser even 20% of the time.

again, dillo isnt set to be the next mozilla... if you want a free software browser that tries to to replace it, go check konqueror... not dillo, w3m, lynx and links

revenue for the project: is anyone seriously going to pay into a browser which will never be able to support frames, javascript, etc?

if its FAST, light, render most pages OK, why not? do you really wants to run mozilla in a palmtop? i spend most of my web time in dillo, its fast and secure, surfing is again fun... but yes, i keep a copy of firefox for those pages that are more complex

There are a lot of people willing to contribute to dillo, it appears, and the main developers could/should use some of the talent.

good, then let the main devs port dillo to fltk and release it and then start building on top of it, following the dillo philosophy and code rules dillo is set to be modular, if you want some new feature, build a dpi (in any language) that talks the dpi protocol, and then only the people that want it will use it. let the main dillo code be about render html code and speak with the dpi processes if you want to help and cant code, donate some money, if the devs dont have food, they have to spend time doing other things to feed themselves and less time to improve dillo.

Clearly, one possibility is to fork dillo.

some people already tried it, to build a "have it all dillo", the result was that it was dropped a few weeks later... most people that use dillo like it because its fast and light, having more features is just a bonus (or not, to some people, it *must* have a disable switch... cookies, javascript, frames, plugins, etc are not welcome to some people) higuita -- Naturally the common people don't want war... but after all it is the leaders of a country who determine the policy, and it is always a simple matter to drag the people along, whether it is a democracy, or a fascist dictatorship, or a parliament, or a communist dictatorship. Voice or no voice, the people can always be brought to the bidding of the leaders. That is easy. All you have to do is tell them they are being attacked, and denounce the pacifists for lack of patriotism and exposing the country to danger. It works the same in every country. -- Hermann Goering, Nazi and war criminal, 1883-1946