Informatique

Navigation rapide

Nouveautés ➪

  1. Grands Étasuniens
  2. Neverwinter Nights

Bloc-notes ➪

Calendrier ➪

Following The Great 10.4 Wish List, I decided to put my very own wish list online.

Thanks to Hiroshi Kobayashi for his comments.

Preliminary notes

Voir LinuxFR pour pas mal de suggestions.

Table of contents

Wish list

Installing

System

Network

Aqua

Exposé

Dock

Finder

Interface

Trash

Contextual menus

A real politic of contextual menus:

Safari

Fonts

Textedit

Stickies

Speed

Multimedia

iTunes

iPhoto

Preview

Video

Filesystems

Mail.app

Addressbook

iCal

Code

Calculator

Startup/Shutdown

Graphisms

UNIX

Terminal

Help

Energy

Text engine

Hardware

Printing

Hard drives

Drivers

Miscellaneous

Details

Uninstalling

I propose an elegant, Mac-style (read: not patching the code à la Windows) way to implement what may be the best uninstaller on any of the “Big Tree” (Linux, MacOS, Window).

First of all, I’m not a programmer; I coul not even write an “Hello world” in Delphi. As a consequence, everything I’m writing is pure speculation. I just tried to take the Apple route: do it low-level and do it well.

For burning a CD from the Finder, one have to throw it to Trash (it is counter intuitive, but anyway…); MacOS X detects an eject event with a to-be-burned CD. If it can do this, so can it for other Trash events.

Proposal : when Mac OS X detects the user is deleting a .app file from the /Applications directory, it should launch a pop-up like this:

The system has detected that you would delete a program. Do you want to:
Only remove the program (recommended)
Choose this option if you think you will reuse this program some day;
Also delete preferences
Choose this option if you are sure you won’t reuse this program;
Also delete preferences for other users
Require administrator password

Your opinion?

The technology already exists (burning from the Finder). In each three cases (wich are cumulatives), Mac OS X will look for dependances by itself. This is simpler and more efficient that Windows (where programs only propose to remove preferences on a case-by-case basis, one of such software being the Moldavian The Bat! email program. Here it would be included right into the OS). The new folder action functionnality may be a way for implementing my proposal.

Obviously, if an application had not been installed in the /Applications directory (as well as all non-Cocoa programs), it won’t work. But my postulate is the programming guidelines will be respected.

We can not hope programmers will write a correct dependancy file (such as .deb packages for Debian, for instance). Choosing an automatised and internal process (i.e. from MacOS X, not from the software to be installed) is choosing a secure way, a safeguard against poor coding or, more importantly, spywares and other hidden files. Mac OS X itself is logging everything.

This being made on system level (wich means full access to the kernel and the filesystem), that means the logging could be operated by the kernel (instead of using such a thing as strace. As for versionning (=updating an already installed application), the filesystem could act as a CVS. That could imply a new filesystem.

Open Source

For those who don’t read French, this guy basically says that Apple is less and less commited to Open-Source. Cupertino tries hard to grab what she can’t from the Open-Source without giving anything back (Safari being an exception; because of the license, they have too and still, they obfuscate the changes to make it harder to port to Konqueror).

Heh, les forums Open Source, c’est plein de gens qui n’ont jamais écrit une ligne de code de leur vie.

Apple au début publiait la majorité de ses pilotes. Entre 10.0 et 10.1, on en a perdu pas mal. Entre 10.1 et 10.2 on en a perdu la majorité. Là avec 10.3, c’est même pas la peine.

Apple ne publie rien comme Open Source. Ils publient juste ce qu’ils sont obligés de publier, comme les trucs en GPL.

Et encore, ils ont modifié les trucs tellement que c’est en général inutilisable (cf. as et les binutils/cctools).

Les gens sur les « forums Open Source » qui sont contents d’Apple, c’est parce qu’il voient des changements dans KHTML qu’Apple est obligé de publier de toute façon.

Ils ne se rendent pas compte qu’ils se font enc*ler à sec pour tout le reste, et que par exemple Linux/PPC a de moins en moins d’info pour tout sur les machines récentes, parce qu’Apple a « oublié » de publier les infos.