Re: [SailfishDevel] Cover Page Image

2014-06-19 Thread Chris Walker
On Mon, 16 Jun 2014 10:22:20 +0300
Juha Kallioinen juha.kallioi...@jolla.com wrote:

 On 13.06.2014 21:16, Chris Walker wrote:
 
  Is this relevant to my problem above? I don't see how, but you never
  know!
 
  error: unpacking of archive failed on
  file /usr/share/scratchbox2/modes/sdk-build: cpio: rename failed -
  Is a directory
 
  This was from an attempted update after the above failure.
 
 Hi,
 
 I'm not sure if this is relevant to your original problem, but that 
 error looks like one that might come if you update the MerSDK with 
 zypper dup instead of letting the SDK updater update/replace all of
 the components. If this is the case, I suggest that you either let
 the updater do its job or do a complete reinstall of the SDK.

I bit the bullet and did an uninstall and a full reinstall having
deleted the SailfishAlpha folder in my home folder directory structure.

I'm now seeing lots of these errors in a Konsole window however :-

kfilemodule(15749) KDesktopFile::isAuthorizedDesktopFile: Access to '
/home/chris/Sailfish_Git_Projects/GBG_Beertent/GBG_Beertent.desktop '
denied, not owned by root, executable flag not set.

I didn't see them before the reinstallation.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org


Re: [SailfishDevel] Cover Page Image

2014-06-19 Thread Juha Kallioinen

On 19.06.2014 15:49, Chris Walker wrote:


I bit the bullet and did an uninstall and a full reinstall having
deleted the SailfishAlpha folder in my home folder directory structure.

I'm now seeing lots of these errors in a Konsole window however :-

kfilemodule(15749) KDesktopFile::isAuthorizedDesktopFile: Access to '
/home/chris/Sailfish_Git_Projects/GBG_Beertent/GBG_Beertent.desktop '
denied, not owned by root, executable flag not set.

I didn't see them before the reinstallation.



Hi,

looks like some component in KDE is looking at your project's desktop 
file and is trying to evaluate them (or something). I don't know if this 
is a big issue, although the extra warnings can be confusing. Those 
messages do not originate from the SDK code.


Out of interest, what is your linux distro and KDE version?

Best regards,
 Juha

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org


Re: [SailfishDevel] Cover Page Image

2014-06-19 Thread Chris Walker
On Thu, 19 Jun 2014 16:04:34 +0300
Juha Kallioinen juha.kallioi...@jolla.com wrote:

 On 19.06.2014 15:49, Chris Walker wrote:
 
  I bit the bullet and did an uninstall and a full reinstall having
  deleted the SailfishAlpha folder in my home folder directory
  structure.
 
  I'm now seeing lots of these errors in a Konsole window however :-
 
  kfilemodule(15749) KDesktopFile::isAuthorizedDesktopFile: Access to
  '
  /home/chris/Sailfish_Git_Projects/GBG_Beertent/GBG_Beertent.desktop
  ' denied, not owned by root, executable flag not set.
 
  I didn't see them before the reinstallation.
 
 
 Hi,
 
 looks like some component in KDE is looking at your project's desktop 
 file and is trying to evaluate them (or something). I don't know if
 this is a big issue, although the extra warnings can be confusing.

As I'm not seeing them in any Qt Creator windows, I am not too
concerned about them. When copying over a database file, I've seeing
these messages too :-
Soft assert
at 
/home/builder/src/sailfish-qtcreator/src/libs/ssh/sshconnectionmanager.cpp:150

Again, I'm not concerned, more puzzled as to why they're suddenly
appearing.

 Those messages do not originate from the SDK code.
 
 Out of interest, what is your linux distro and KDE version?

The distro is Mageia 4 - 64 bit and KDE is 4.11
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org


Re: [SailfishDevel] Deploy QSQLite database

2014-06-19 Thread Lukas Vogel
Hi,

Thanks all for your answers. Andreys solution works, it complained first
for the simulator,
but seems to work now (after it ran successfully on device).

I now changed the path to /usr/share/harbour-qtimetable/data/stations.db

I have quite a big read-only part (list of train-stations) but I want to
store things like favorites and stuff.
Would you suggest creating 2 separate db, or copying the whole db at first
start-up to the write-able location?

Thanks for your help,
Lukas



2014-06-18 7:42 GMT+00:00 Michael Neufing m.neuf...@yahoo.de:

 Hi,

 my app needs an SQLITE db, also. I deploy it into
 /usr/share/harbour-{APPNAME}/data.
 You could then use it either from this location, or copy it into the home
 dir on the first run.

 As the db seems to be readonly, I think you don't need to copy it into the
 home dir.

 Mit freundlichen Grüßen,

 Michael Neufing


   Saija Saarenpää setel...@live.com schrieb am 8:41 Mittwoch, 18.Juni
 2014:


 Hi,

 What comes to having datalocation path variable in the .pro file:
 I was having similar thoughts when I wanted to install something in the
 writable storage location, but I was corrected. Nothing should be installed
 in the home directory with the application, but under application directory
 /usr/share/harbour-yourappname/. There can be also subdirs under that
 location. Then, at runtime, you can create the writable storage location if
 it does not exist, and copy or create stuff there. Preferably the app would
 not pre-install any data, but everything would be downloaded / created
 runtime. That would be the ideal though, not always applicable.

 - Saija
 @setelani
 matrixx #sailfishOS

 Lähetetty iPadista

 Andrey Kozhevnikov coderusin...@gmail.com kirjoitti 18.6.2014 kello
 8.50:

  you should build and deploy as RPM package ;)

 18.06.2014 03:42, Lukas Vogel пишет:

 Hi there,

  I try to create an app in which I want to have an existing database bind
 in the binary.

  My approach was the following:
 in pro file:
  QT += sql

 database.files = stations.db

 database.path = /home/nemo/.local/share/harbour-qtimetable/harbour-qtimetable

 INSTALLS += database

 To open the database:

 db = QSqlDatabase::addDatabase(QSQLITE);
 db.setDatabaseName(DB_NAME);
 db.setUserName(USER_NAME);
 db.setPassword(PASSWORD);
 db.setConnectOptions(QSQLITE_OPEN_READONLY=1);

 if(db.open()) {...}

 for DB_NAME I use 
 QStandardPaths::writableLocation(QStandardPaths::DataLocation) with 
 stations.db appended.

 However when I deploy this will fail as the path on emulator has

 home/deploy/installroot/ prefix, and when deploying on device there is 
 /opt/sdk/..

 prefix.

 This makes testing quite annoying, is there a genuine way to get the database 
 to open both in the emulator and the device?

 Side question is there a standard path::datalocation variable for the .pro 
 file?

 Thanks for any help,

 Lukas



 ___SailfishOS.org 
 http://sailfishos.org/ Devel mailing list
 To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org


 ___
 SailfishOS.org http://sailfishos.org/ Devel mailing list
 To unsubscribe, please send a mail to
 devel-unsubscr...@lists.sailfishos.org


 ___
 SailfishOS.org Devel mailing list
 To unsubscribe, please send a mail to
 devel-unsubscr...@lists.sailfishos.org

 ___
 SailfishOS.org Devel mailing list
 To unsubscribe, please send a mail to
 devel-unsubscr...@lists.sailfishos.org



 ___
 SailfishOS.org Devel mailing list
 To unsubscribe, please send a mail to
 devel-unsubscr...@lists.sailfishos.org

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Deploy QSQLite database

2014-06-19 Thread Chris Walker
On Thu, 19 Jun 2014 15:37:41 +
Lukas Vogel lukedirtwalker...@gmail.com wrote:

 Hi,
 
 Thanks all for your answers. Andreys solution works, it complained
 first for the simulator,
 but seems to work now (after it ran successfully on device).
 
 I now changed the path
 to /usr/share/harbour-qtimetable/data/stations.db
 
 I have quite a big read-only part (list of train-stations) but I want
 to store things like favorites and stuff.
 Would you suggest creating 2 separate db, or copying the whole db at
 first start-up to the write-able location?

I'm interested in this one too as I have a large database which is used
'as is' but I want to store my own settings for it. I'm thinking along
the lines of a separate SQL file and not touching the 'supplied'
database.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org