Oct 5, 2001
553 Vues
0 0

WindowMaker 0.70.0 dispo

Ecrit par

WindowMaker encore plus léger, encore plus petit…. et encore plus stable ;))

voici le mail:

There’s a new Window Maker release available on http://windowmaker.org/

Along with the usual bug fixes, this release brings a new copy/paste feature for the docked appicons and the removal of libPropList as a dependency. New code to handle property lists was integrated in the

WINGs libraries being now more robust and also about 3-4 times smaller then the old libPropList code.

People are encouraged to test this new version (especially the parts regarding property lists) and to report any problems they see about handling the configuration files.

The easiest way to test proplist code is to use WPrefs.app to edit the configuration files and the application menus, and the getstyle/setstyle and other utilities that perform actions on the Window Maker config files (the proplist config files that is).

Also adding/removing icons from dock/clip will change a proplist file (WMState)

Info for developers about new proplist code ——————————————-

This rewrite of proplist handling code was needed (at least from the developers point of view) because libPropList has some serious design flaws coming from the fact it mixed concepts from property lists with

concepts from UserDefaults and the original property list concepts (like retain/release) conflicted with these borrowed concepts from UserDefaults.

This conflict led to situations where with certain actions performed on a property list using libPropList functions the program could get a segmentation fault, and the worst thing was that even if the problem was known it could not be fixed. To be able to fix it one of the conflicting concepts needs to be removed, and this is what the new

proplist handling code in WINGs does. It removed the borrowed concepts from UserDefaults keeping the native retain/release concept (that was an obvious decision 😉 ). Removing these UserDefaults concepts should not reduce functionality at all, because if someone needs UserDefaults he should use UserDefaults (which WINGs also provides) not property lists (even though UserDefaults are in fact based on proplists plus some extra things).

With this, the property lists handling code is much simpler, smaller and more robust.

Catégorie:
News

Laissez un commentaire

Menu Title