124179: trigger update User Fields and related Input Fields when user directly edits a User Field Input Field

- assure that no recursive updates occur

to make the source of some log messages more clear

Patch-by: jsc@apache.org

having a MainController class in the global namespace of an application with
gazillions of MVC patterns is not a good idea. Renaming it to better match
its scope (i.e. the Apple Remote) cleans this up.

Patch-by: j.nitschke@ok.de
Review-by: hdu@apache.org

now that its nasty stability problems on 64bit AOO for OSX are fixed

the RemoteControl is already initialized anyway

iterating beyond the end of a frame-list must be avoided

import - import table's left margin
import - set table's bottom margin explicitly

i123922 Refactored D&D and insert picture from file in all apps for all object types to work the same

for getting the parent window of an A11y enabled NSView. The method
viewElementForParent() was abused for that purpose, but it was mis-named
and mis-typed. The new method cleans this up and the now unused
viewElementForParent() method can be retired.

Patch By: Aivaras Stepukonis
Review By: jsc

i124143 for draw:frame containing multiple draw:image and draw:glue-point it is necessary to move the GluePoints from the last draw:image where they were automatically imported to the surviving one if these are different

Boost's shared_dynamic_cast and shared_static_cast were deprecated since
boost 1.35 and removed in boost 1.53, so they have to be replaced
Found-by: Ariel Constenla-Haile <arielch@apache.org>
Suggested-by: Ariel Constenla-Haile <arielch@apache.org>
Reviewed-by: Herbert Duerr <hdu@apache.org>

so its symbol can be used for dynamic loading, e.g. in vcl

Review by: hdu at apache dot org

Patch-by: j.nitschke@ok.de
Review-by: hdu@apache.org

Patch-by: j.nitschke@ok.de
Review-by: hdu@apache.org

i123993 When executing rotation actions from the Sidebar PosSizePropertyPanel, take UIScale into account.

Patch By: hanya
Review By: alg

Some newer Mac SDKs are backward compatible with an OSX 10.7 deployment target.
Allowing the build with such compatible SDKs enables the use of plain XCode,
even when XCode>=5 dropped the 10.7 SDK.