Xslimmer 1.2 is Out!

That's right. The anticipated release of Xslimmer that allows language stripping from applications is here. In this release, we include a series of benefits:

* Language stripping. Xslimmer 1.2 allows you to easily select how many languages you want to preserve and will remove the rest, thus greatly increasing the amount of disk space you'll free.
* Send apps to exclusion list. A new menu option allows you to easily add applications to your personal list of excluded ones, directly from the Xslimmer window. No more search for the app to exclude!
* Quicksilver integration. Allows Xslimmer to become a target for Quicksilver's "Open with..." feature.
* Localizations. Xslimmer is now available in English, Spanish, French and Italian!
* UI improvements. A variety of minor UI improvements have been added that contribute to (we hope) a sound, consistent and polished user experience.

Hope you enjoy using Xslimmer 1.2.

Xslimmer Language Stripping Ready for Beta

Time for a new beta! This one will be smaller than the original one, but we want to find out if there could be any issues, that we did not forsee or find out, with the new language stripping system that we have implemented onto Xslimmer 1.2.

This means that we have finished Xslimmer 1.2 development, and we are ready to let our original beta testers check it out. If you are interested in testing it out too, you are more than welcome to write to us. We are limiting total new submissions to 10.

New Version Design

We have finished the version 1.1.x roadmap. It is time to move on to 1.2. As you probably know, 1.2 shall include app language stripping capabilities. This means that many parts of the Xslimmer app will have to be adapted or even rewritten.

The most obvious change will be the main window. How do we indicate that an app has multiple languages? should we show what the final language will be? what happens after the language stripping has been done? But, most importantly, how do we combine both features into one single application and make sure that it is still attractive and easy to use?

Then you have the history or log information. The operation needs to be reflected in there, and in a compatible way with the current existing slim log.

Blacklist. Does it need to change? Will apps behave in equal manner when stripped from languages than when stripped from architectures? There is some testing to do.

These and many more details, are our current thoughts on making 1.2. It will take a few weeks, and a new beta test to get it out, but, as we are in the design phase this week, it would be great to hear any ideas you might want to see included in this or other future versions.