--- In colorvision_group@yahoogroups.com, CDTobie@... wrote:
>
>
> In a message dated 10/26/07 8:42:57 PM, marko.mili@... writes:
>
>
> > I've come across many of your posts while
> > learning about color management, and it is obvious that you have solid
> > knowledge of that
> > subject, but on this topic, this is just plain FUD.
>
> Please work on your attitute, tone, and politeness. Here are a few
> perspectives you might not have considered:
In many of your posts you come across as condescending - consider following above
advice.
You took the time to respond to my post and came up with a number of reasons why not,
and they all seem to hedge on an assumption that is incorrect - and that is why I suspect
you didn't read the technical note.
http://developer.apple.com/technotes/tn/tn2035.html#TNTAG49
It is a great technical note, covering an array of ColorSync topics, and definitely worth
reading for anyone else interested in under-the-hood details of color management on
Mac platform.
This approach does not replace Apple's visual calibrator. It simply adds your app to the list
of available monitor calibrators, so that when user clicks on Calibrate, a dialog box comes
up asking him to select one of the available installed calibratiors - there is even a
screenshot of this in the technical note.
You are concerned about naive users - this would in fact aid them, since when they
stumble upon this "Calibrate..." button, they won't simply be thrown into Apple's visual
calibrator - if they were really *that* naive, they might think they are using the right
software.
It still does not preclude you from installing your app in /Applications or from having a
dock icon or an optional menu bar thingie. It just makes one more pathway to your app.
> Installing a new OS and finding your monitor calibration software "gone" from
> where you have been using it would stymie such users.
I'm not sure what you mean by "gone". If they reinstall OSX and chose to erase their drive,
then your app would be alltogether inaccessible, obviously, until they reinstall it. If they
upgrade OSX, whether they select "upgrade" or "archive and install", your app would not be
affected - that is why there is /Library as well as /System/Library - /Library is intended to
stay untouched across system upgrades, at least until Apple fundamentaly changes their
OS some years from now.
I can understand the desire to keep your app as consistent across OSes - certainly makes
it easier to do development, and why not. But this is one of those little things - a
preference in build options to create appropriate entry in Info.plist, and an instruction to
installer to create a symlink. I really didn't intend to get into a big debate about it - this
list most certainly cares more about color management with Colorvision products then
intricacies of software development, and I appologize to list members who are not
interested in this topic.
I do have some questions about results of printer profiling that I hope you will be able to
shine some light on, but I will leave that for another post.