afaik Sailfish uses canonical paths. /usr/share/appname for persistent
data and $HOME/.local/share/appname for user data.
On 10.11.2013 17:19, Tone Kastlunger wrote:
Hey;
is there some kind of path reference for Sailfish available yet?
Something like the Harmattan Path reference for instance.
Thanks coderus, this is for apps; how about the other relevant OS paths
(plugins, etc)?
tortoisedoc
On Sun, Nov 10, 2013 at 1:23 PM, Andrey Kozhevnikov
coderusin...@gmail.comwrote:
afaik Sailfish uses canonical paths. /usr/share/appname for persistent
data and $HOME/.local/share/appname for
some system plugins or plugins for your own application? for system
plugins you should know where to put them. And for own application
plugins create /usr/share/appname/plugins folder and keep plugins there.
On 10.11.2013 17:24, Tone Kastlunger wrote:
Thanks coderus, this is for apps; how
That is awesome! :) Thanks for the info
(and sorry for double-posting my question)
Br,
Alessandro
Am Sonntag, 10. November 2013 schrieb Mohammed Hassan :
On Sun, Nov 10, 2013 at 01:28:42AM +0100, Alessandro Portale wrote:
Hi,
I am only able to play wav/pcm audio via QMLs
Hi, The blow is somewhat correct and RPM built with SDK:
./usr/bin/hourtracker
The run-time binary. This is defined in template and thus can be changed if
user wants.
./usr/share/applications/hourtracker.desktop
Icon visible on launcher, also this file defines where the run-time binary is.
Hi,
I'm trying to run an app using qt-components-qt5 (installed in the
emulator). It fails though. The output is:
QML debugging is enabled. Only use this in a safe environment.
Using Wayland-EGL
Module 'com.nokia.meego' does not contain a module identifier directive -
it cannot be protected
Well, it was indeed the problem. (No installing from qmake) Thanks!
--
Marcin
2013/11/1 sonyfe...@ovi.com
Take a look at your yaml and see if there's *.desktop specified in Files
field. Try changing the path to include the subdir.
Also make sure you have specify where to install the
Hi Marcin
Have you installed that package to both the Emulator and the SDK Build
Engine? (and synced in the SDK Control Center?)
My next guess is that you get this error from QML. Normally the qml
types are available in a version of the package with
import-declarative in the name (to be
