Le 14/1/2008, "Roger Breton" <graxx@xxxxxxxxxxxx> a écrit: >> Your idea could be to extend that feature, by adding another param. to >> call a script that will make the measure, instead of the internal one. >> >> I'm wondering if this could not be a good work-arround for new >> unsupported hardwares? This will allow people to try to use other >> methods before Argyll officially support them (the HCFR is an example; I >> didn't try with the latest beta, but I couldn't make it work under >> linux, through the libusb. But it works using the usb-serial linux >> driver). > > It is no rush for me. Whenever Graeme revisits his code to add other > features for other purposes. This is something I was able to do a long time > ago with MacOS9 version of ProfileMakerPro v3, I think. It was possible to > advance in the characterization patches one by one. There was a next button.. > Now that button is gone. Such modification of Argyll could be a first step to a GUI mode... As Graeme explained, making an API from the current Argyll project is not that simple, as the main work is done in final utilities. So, adding a few hooks could be a solution to make it easier to be run from a GUI, and also to be able to add nice features like the above one. What I usually do when I have to implement a GUI over a cli, is to add a special flag. When this flag is set, the output change, and is more computer-oriented: shorter messages (easier to catch), steps messages, and I do not use special char to stay on the same line when outputing a counter, for example, which is sometimes hard to deal with. -- Frédéric