Language Selection

English French German Italian Portuguese Spanish

Dillo2 coming in September

Filed under
Software

Imagine my complete and utter surprise after accidentally clicking on the Dillo home page link, and seeing this:

After a very slow 2006, and a project stop in year 2007, the new 2008 came with a renewed work force that kept working steadily behind the scenes. The fruits of this effort are a new and stable dillo based on FLTK2 (aka dillo2), that has more features, bug fixes, goodies and half the memory footprint of the GTK1-based dillo!

This new branch of dillo is scheduled for release in late September or early October 2008.

Oh, I think I may be having a heart attack. Dillo2? Egads, I’ve been looking at the same Dillo version since I started using Linux. A new version might signal the apocalypse.

Bit more here or here




More in Tux Machines

Android Leftovers

Leftovers: OSS

Ubuntu 16.04 Review: What’s New for Desktop Users

Ubuntu is a tricky distribution. As much as I love it on my home server, my desktop is a different ballgame. In my experience, releases between LTS versions have many new technologies that may or may not survive in the next LTS. There were many technologies or features that Canonical thought were ambitious -- HUD, experimenting with menus, online dash search, Ubuntu Software Center, etc. -- but they were abandoned. So, if I were to use Ubuntu on my desktop, I would still choose LTS. Read more

Workflow and efficiency geek talks Drush and Drupal

I started using Drupal because I needed an open source content management system (CMS) to use in several community projects. One of the projects I was involved with was just getting started and had narrowed its CMS selection down to either Drupal or Joomla. At the time I was using a different framework, but I had considered Drupal in the past and knew that I liked it a lot better than Joomla. I convinced them to go with the new Drupal 6 release and converted all of my other projects for consistency. I started working with Drush because I wanted a unified mechanism to work with local and remote sites. My first major contribution to Drush was site aliases and sql-sync in Drush 3. Read more