Hi,
On 27.12.2013 18:48, Ruediger Gad wrote:
Hi,
two of my apps (MeePasswords and Q To-Do) are being rejected because
they are linked against libraries that are not "allowed".
I read the according FAQ at https://harbour.jolla.com/faq and understand
your motivation for being so restrictive.
How
Hi,
On 07.12.2013 21:37, Mikael Hermansson wrote:
I think harbour store should allow libcrypt/openssl because AFAIK that
API will not change very often and is probadly already used in sailfishos?
as mentioned in several places before. Harbour QA started on 07. Jan
2015 to accept submissions
On Thu, Jan 8, 2015 at 6:40 PM, Oleg Linkin
wrote:
> I am not agree with you. Transfer engine plugins give us possibility to
> share some staff with services, but for showing picasa images in gallery
> like for facebook - it is not transfer engine issue
>
Facebook plugin already open can be find
Hi,
i've seen that apps can be configure thought the settings app, but didn't
found any documentation about it, how that can be done?.
The same question goes for the account section of Settings, custom apps can
be managed through that account configuration?.
Best regards.
--
Nicolas Cisco
www.n
Hi Kim,
You can switch off the overlay scrollbar thing with "export
LIBOVERLAY_SCROLLBAR=0", did you try if that helps? Alternatively you could
find out wether it is a Unity problem by installing another desktop say
LXDE; I doubt it is related.
___
Sailfi
Hi
I'm still having problems installing the SDK, also with the latest
release.
I have proven the problem to be in merssh, by executing it from a cli
with the following command:
/home/kif/SailfishOS/bin/merssh generatesshkeys
'/home/kif/SailfishOS/vmshare/ssh/private_keys/engine/root'
'/home/kif/
Ok, found the root cause for this.
In my project, I have two sub projects (lets name them a and b)
Sub project a is a tool, and is not used in any rpm, so it does not have
the .spec file.
Sub project b is my real deal, and has a proper .spec file.
I updated the sdk, opened the project file and sw
Ok, found the problem.
the location of the rpm folder containing the .spec file has changed - yet
again.
I keep on pushing it from the root directory of the project to my
subproject root directory every once in a while .
Can anyone explain why this happens?
On Thu, Jan 8, 2015 at 11:25 PM, Tone Ka
It seems I am facing a similar problem, but on the pc side (win7):
Fatal: No spec file found in '/home/mersdk/share//debota/rpm/' and couldn't
make one from a yaml #1
23:23:58: The process
"C:\sviluppo\sailfish\sdk\settings\SailfishBeta1\mer-sdk-tools\MerSDK\SailfishOS-armv7hl\rpm.cmd"
exited wit
Thanks Michael,
Creating the /opt/sdk/ path seems to have soved the issue, I can't remember
ever having to do this manually. I very recently restored my Jolla to
factory settings so that might have had something to do with it as well.
Thanks again
Kris
On 8 January 2015 at 18:35, Michael Neufing
Hi Kris,
are you using deployment by copying binaries to device?
If yes, can you check if the folder /opt/sdk exists on your device? If
not, create it and test again.
This solved my problems with this deployment mode.
You could also set the deployment mode to RPM.
Michael.
Zitat von Krisz
Hi list,
I installed the new SDK yesterday, but since it's installed I cant seem to
be able to deploy onto device fails due to an rsync error:
rsync: mkdir "/opt/sdk/Trash" failed: No such file or directory (2)
rsync error: error in file IO (code 11) at main.c(656) [Receiver=3.1.0]
Deploy failed
On 07.01.2015 12:06, Sami Kananoja wrote:
> Hi,
>
> This should do the trick:
>
> SilicaFlickable {
> id: flickable
> anchors.fill: parent
> contentHeight: textAreaLog.height
> contentY: Math.max(0, contentHeight - height)
> TextArea {
> id:
Thanks to fellows on #sailfishos
i had made a bad thing: (or bad copypaste)
#define pi (3.14159)
in some other place someone else;
QtMetaTypePrivate::QPairVariantInterfaceImpl pi =
v.value();
And seems that my #define messed things up.
Now it builds correctly.
-kimmo
From: devel-boun...@lis
Okay I thought he's looking gor sharing plugins. :-) Sorry for confusing.
Am Do. Jan. 8 14:40:24 2015 GMT+0100 schrieb Oleg Linkin:
> I am not agree with you. Transfer engine plugins give us possibility to share
> some staff with services, but for showing picasa images in gallery like for
> face
I am not agree with you. Transfer engine plugins give us possibility to share
some staff with services, but for showing picasa images in gallery like for
facebook - it is not transfer engine issue
В письме от 8 января 2015 13:23:50 пользователь Gabriel Böhme написал:
> Nemo Transfer Engine is wha
Nemo Transfer Engine is what you are looking for, there is a GIT repo with an
example.
But it's not very well documented and not allowed in harbour.
Am Do. Jan. 8 12:58:13 2015 GMT+0100 schrieb Oleg Linkin:
> Are there any sources or documentations or examples of creating this type of
> plugins
Are there any sources or documentations or examples of creating this type of
plugins?
I want to add google picasa to google buteo-sync-plugin but without possibility
showing it in gallery all this hasn't any sense.
Thx.
___
SailfishOS.org Devel mailing
Am 05.01.2015 um 01:56 schrieb Aaron McCarthy:
> On Mon, 15 Dec 2014 17:53:34 Harald Schmitt wrote:
>> Am 15.12.2014 um 13:35 schrieb Harald Schmitt:
>>> Am 11.12.2014 um 17:45 schrieb Harald Schmitt:
Am 10.12.2014 um 18:24 schrieb Richard Rondu:
> Hi, the backport is not completely up-to-
Regarding SIP integration, I'm very interested in that.
I can test and possibly also contribute with development, but time is a bit
limited.
Also I can provide SIP accounts on a kamailio server I'm running.
Regards,
Sander van Grieken
___
SailfishOS.
My toholed daemon is built on mer-obs, succesfully built previously during
October.
Now the repo has propably been updated to latest sailfish release, and build
fails strangely. (Rebuilt for some reason 6th Jan)
That include file trace doesn't help at all.
build-log says this for error:
(Comple
21 matches
Mail list logo
