even for development builds,
because
1. Neither the DEPLOYMENTFOLDERS directive
nor the OTHER_FILES mechanism are documented
qmake features.
2. The DEPLOYMENTFOLDERS feature does not seem
to be very reliable (you had to go for clean
builds to make sure your application's content
is up to date with the current state of the *.pro
file).
3. By doing so, we can unfiy the Sailfish and v-play
builds.
4. Last but not least, it enables us to way control
way more granularly, which (QML) files end up in
our build *and which don't*.
Closes#40
// Github issue #48

Both, the Sailfish SDK and the v-play SDK, offer an IconButton
implementation. However, both implementations differ, so that we need to
wrap around that.
The function 'iconBy(type)' returns the framework specific
implementation.
Ref #48

Therefore we connect the Sailfish's clicked(int index) signal with the
selected(int index) signal of v-play's SimpleRow and we pass through
Sailfish's PageStack to v-play's NavigationStack.
Drawback: This commit introduces some type error, which we have to
address in the future.
Ref #48

That way we can get icons from other places in the source code as well.
In the long run, we could even get rid of the IconButton wrapper, if we
return the whole IconButton object via the iconBy() function and not
only the icon string.
Ref #48