Deprecated on 10.7 and later

Question

Recently I've noticed these log messages submitted by different sources including Apple Apps.
Can anyone explain these? The meaning is clear to me but it appears that developers with Apple are still using deprecated library calls. Is my interpretation correct?
I've also checked the logs on my macmini which runs the same OSX version (10.8.5) as a file, media and webserver. No such messages were found.
Sender: UserNotificationCenter
*** WARNING: Method userSpaceScaleFactor in class NSWindow is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead.
Sender: Mail
*** WARNING: Method userSpaceScaleFactor in class NSWindow is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead.
Sender: DiskImages UI Agent
*** WARNING: Method userSpaceScaleFactor in class NSWindow is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead.
Sender: SystemUIServer
*** WARNING: Method convertRectToBase: in class NSView is deprecated on 10.7 and later. It should not be used in new applications.
Sender: EndNote X7
Setting a table column identifier of type '__NSCFNumber'.  For applications linked on or after 10.7, NSTableColumns expect NSString identifiers.  This app should move to using NSString identifiers for table columns.

Answer 1

t.a.51 wrote:
However; I dont agree that the logs are meant for developers exclusively. First because developers cannot see these logs unless users take action or when these messages are forwarded through Apple via de crash reports et cetera. In this case user input is sometimes required to relate messages and users actions. Second because computers like other man-made tools require maintanance. Users like me when experiencing problems must dive into these matters in order to comprehend what part of the machine needs support.
It is the responsibility of developers, not users, to make sure their apps work properly with the versions of OS X they claim to support. There are many ways they can do this, including paying Apple a modest yearly fee for technical support through the Mac Developer Program, private or public beta tests of prerelease candidates, & so on.
Developers who are diligent about maintaining their software do not need to see user-submitted crash reports to know they are using deprecated system calls -- if a developer needs that, it is a strong indication that they are not keeping up with the development of OS X, & that you should look elsewhere for products you can continue to use with future OS X versions.
Accordingly, if you are experiencing problems with some software the first thing you should do is not to dive into system logs but to check that you are running the latest, most up-to-date version of it. Nine times out of ten, updating to the current version will solve the problem, & do so quickly & easily, without requiring any effort on your part other than downloading & installing the update.
When that doesn't resolve the issue, the next thing you should do is check the developer's support info to see if yours is a known issue; if anything is being done about it & if so when a resolution is expected; & if there are any suggested workarounds available until the issue is resolved. If you can find nothing like that, consider that the problem may well have some other cause, like an incompatible third party addition to your system, corrupted files or the file system itself, etc. System logs are sometimes helpful in diagnosing such things, but since the issue is not with the developer's software itself, there is no point in sending the log to the developer or hoping they will fix something they have no control over.
Only if none of the above solves your problem should you assume there is any reason to 'dive into' the system logs. Even if you are willing to do that there is little reason to think you will see anything helpful unless you are an experienced OS X programmer, or at least have a good understanding of how the OS works & what the terminology means.
That will take considerable effort on your part. You can begin by browsing through the Apple's developer docs, particularly the Getting Started section of the Mac Developer Library.