Welcome to the Dillo Project!

• Dillo is a web browser project completely written in C.
• Dillo is small: source is less than 420 KB, and the binary is around 350 KB!
• Dillo aims to be a multi-platform browser alternative that's small, stable, developer-friendly, usable, fast, and extensible.
• Dillo is mainly based on GTK+ (GNOME is NOT required!)
• Dillo is a free-SW project in the terms of the GNU general public license.
• Dillo's bug meter is a tool to help towards standards compliance.
• Current code uses an improved html-parser (formerly based on gzilla's), and almost everything else was rewritten from scratch!.
• Dillo is very fast!

• The democratization of internet information access.
• Personal security and privacy.
• High software efficiency.

So, you have been using dillo for a while, but have you read about the project objectives? Please give it some time, you'll find some interesting issues there!

The Dillo project is frozen:

• Frozen, waiting for funds or sponsorship.
• Looking for interested developers that want to work steadily on it.
• Both core developers have regular jobs and have almost no spare time.
• We have a very advanced port of Dillo to FLTK2.

A web browser is too complex a task to develop on a part time basis, and it also is a fast-moving target. I dedicated seven years full-time to it, and I'm willing to dedicate more. This doesn't depend on me anymore as I had to take a job to pay the bills. We made great achievments with Dillo and it would be easy to quickly push FLTK2-Dillo if we could have both core developers working full time on it. This is a tiny deal for some sponsors (e. Cell phone maker), and we wish it could happen soon. Through this time we've been supported by individual's donations, and we thank them indeed for believing in our project and to help make it grow to what it is.

If you as a reader, or user, or interested party have a good idea, sponsorship or development time to devote, please don't hesitate to contact me to try to arrange for the future of Dillo.

-- Feb 25, 2007

Current version

Click here for the downloads page.

Code contributions

Current plans

News

[02-May-2006] Dillo-0.8.6 was released. This is hopefully the last GTK1-based Dillo.

You'll find plenty of fixes and improvements in this tarball. Most notably on downloads. Just check the Changelog.

OTOH, our FLTK2-based branch is advanced enough to aim on making our next release with it.

When? This depends on funding.

[15-Jun-2005]

0.8.5 was released with some minor fixes, most notably a couple of security fixes. Upgrade if you haven't already!
This release is one of the last on the GTK1-based Dillo series. Currently the main development is focused on a FLTK2-based dillo prototype. If everything goes as planned, and no critical bugs are found, this new branch will become our next release! (stay tuned).

[11-Jan-2005]

Today, two and a half months after the former release, the new dillo-0.8.4 was released!

It comes with several goodies. The most remarkable is the fix of a memory leak bug that can lead to reduced virtual size memory usage by a factor of 2 to 20 on average! (this depends on usage, pthreads library and OS).

The other big improvement is the ortogonalization of the parser. This brings several benefits detailed in the Changelog.

Finally, among the usual enhancements and improvements, a security bug was also fixed.

Our advice is to upgrade ASAP.

[27-Oct-2004]

After a long period of work, the new dillo-0.8.3 was released today.

It comes with a parser that's able to use W3C's semantics plus some heuristics. This improves the rendering of sites that deliver non-valid HTML. It is expected to provide for better results than the venerable dillo-0.7.3, while keeping the useful diagnostic messages of the bug meter.

[09-Jul-2004]

Just out of popular demand, a donations link was added. This may give us the opportunity to work full time on Dillo, and thus keep improving it at a much faster pace.

All the plans, required knowledge and will is there (i18n, antialiasing, better rendering, frames, https, FLTK, more plugins, ...), but we _need_ to be working on it full-time, to keep with the pace of the evolving technologies.

See the Archive for older news.