[SailfishDevel] my letter on switching sides [non-technical]

[Jarko Vihriala]

Hello there!

This is my announcement to Sailfish developer community that I'm switching 
sides. That's right, after next week I will be present in the community only as 
private person with no direct connection to Jolla Oy. If you did not read 
between the lines - I have resigned from my post as chief SDK Engineer in Jolla 
and my last working day is tomorrow, 12.6.2014.

I recently got a once-in-a-lifetime opportunity at somewhere else and just 
could not resist to take it on, you'll find out about it soon enough. Making 
the decision to leave Jolla was not easy.

What now? Actually the SDK team has received new members and they are already 
working on to get the next release out, so there should not be any stalling of 
the engine. The harbour ranks stay intact also, so the biggest difference is 
that you'll see someone else posting SDK announcement mails after this week is 
over. Traditional support channels (#sailfishos irc, devel mailing list and 
TJC) keep running just like before.

I would like to thank you all in the community so far for such unforgettable 
journey. We have shown the world together what it means to be part of this 
tribe. Yes, there have been ups and downs but overall the atmosphere has been 
and is great.

So there, I hate long goodbyes (like I told my colleagues yesterday) so - let's 
keep on rowing and keep those apps hitting the Jolla Store!

with love, Jarko (jake9xx)

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

Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."

[Jarko Vihriala]

when that happens, have you tried to SSH into the MerSDK from command line. We 
have seen issues where the SSH key exchange takes long time for some reason , 
currently that's under investigation. If you want to help in that,
- you could do a SSH session inside MerSDK and run journalctl -fa in terminal
- run deploy commands from Qt Creator
- observe the output, is there a +10s timeout in the log somewhere (looking at 
timestamps)?

thanks, Jarko


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Tone Kastlunger [users.giulie...@gmail.com]
Sent: Saturday, May 31, 2014 11:28 AM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK 
Virtual Machine. Timeout waiting for reply from server."

Hi I for once happen to get the issue every once in a while even during binary 
deployment.
Best,
tk

On Thursday, May 29, 2014, Christopher Lamb 
mailto:christopher.l...@thurweb.ch>> wrote:
Hi All

I am still suffering from this issue, and getting more and more frustrated!

Right now "it" is refusing to deploy as RPM to the Emulator.

Is anything I can do to better debug / understand this issue?

The timeout settings previously suggested are probably red-herrings, as they 
apply to the device (phone / Emulator), whereas the error is a timeout to the 
SDK.

All help greatly appreciated.

Grüsse

Chris



On 28.04.14 08:01, christopher.l...@thurweb.ch wrote:
Hi

Thanks.

I found a well hidden {1} timeout setting in the preferences / devices and 
increased this from the default 2 secs to 10 secs. This does seem to help, but 
as always with sporadic problems only time will tell if this is a fix, or if 
the problem is just dormant for a while.

What I don't understand is, given the error says "Could not connect to
MerSDK Virtual Machine" why should a timeout for connecting to a Jolla device 
play any role?

Is the error misleading? is the problem actually in connecting FROM the MerSDK 
to the Jolla?

Chris

{1} when the preferences pane opens, at least on my OSX host the timeout 
setting is "offscreen" in an embedded pane with scroll bars in the middle of 
the preferences pane. Only if you scroll down in the embedded pane are further 
settings including the timeout revealed. Truly a wonderful bit of UI design 8-)



Zitat von fasza2mob...@gmail.com:

I believe the  timeout setting can be adjusted in QtCreator where you set up 
your mer device(ssh password, etc). By increasing this value you can probably 
prevent the timeout issue altogether. I don't have the SDK in front of me to 
give you the exact menu you need to open, but it isn't too hard to find once 
you know what you're looking for.

On Sat Apr 26 2014 13:41:20 GMT+0100 (BST), christopher.l...@thurweb.ch wrote:
Hi All

I am suffering from sporadic bouts of the error: "Could not connect to
MerSDK Virtual Machine. Timeout waiting for reply from server"

One moment I can be happily hacking and deploying code to my Jolla
without error. Then I make a small change to the code, try to deploy,
and bing! the error rears its ugly head once again like a scandinavian
troll from under a bridge.


Project ERROR: Could not connect to MerSDK Virtual Machine. Timeout
waiting for reply from server.
14:02:28: The process
"/Users/christopherlamb/.config/SailfishAlpha4/mer-sdk-tools/MerSDK/SailfishOS-armv7hl/deploy"
 exited with code
1.
Error while building/deploying project landed26_QT5 (kit:
MerSDK-SailfishOS-armv7hl)
When executing step 'Rpm'
14:02:28: Elapsed time: 00:27.


When the error occurs, there seem to be at least 2 variants:

1) It will successfully deploy "As binaries" without error, but will
give the error on "deploy as RPM".

2) Any kind of deploy gives the error.


The strange thing is, that despite the error, it does seem to
(sometimes) deploy (or possibly partially deploy) code.

Right now I am getting the error in constellation 1), so according to
the error a "deploy as RPM" should fail. Yet the test below indicates
that it is at least partially deploying code.


[root@Jolla javascript]# pwd
/usr/share/landed26_QT5/qml/javascript
[root@Jolla javascript]#
[root@Jolla javascript]# ls -ahl
total 52K
drwxr-xr-x 1 root root  180 2014-04-26 13:56 .
drwxr-xr-x 1 root root  110 2014-04-26 13:56 ..
-rw-r--r-- 1 root root 4.2K 2014-04-26 13:55 jsonpath.js
-rw-r--r-- 1 root root 1.3K 2014-04-26 13:55 jsonSupport.js
-rw-r--r-- 1 root root  349 2014-04-26 13:55 landed.js
-rw-r--r-- 1 root root 1.2K 2014-04-26 13:55 message.js
-rw-r--r-- 1 root root 8.4K 2014-04-26 13:55 readDataModel.js
-rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js
-rw-r--r-- 1 root root 5.2K 2014-04-26 13:55 writeDataModel.js

//create new file testDeploy.js in QtCreator, then attempt deploy as
RPM. Error is generated. Repeat attempt to deploy as RPM. Error is
generated again.
//but testDeploy.js is now on the Jolla!

[root@Jolla javascript]# ls -ahl
total 56K
drwxr-xr-x 1 root roo

Re: [SailfishDevel] Acceptable Behaviour Guidelines - you decide

[Jarko Vihriala]

Ham, pineapple and aura cheese. Forever. And lots of garlic.

On the topic. I prefer ml,but it's archive should have indexer. 

On Sat May 24 2014 21:55:18 GMT+0300 (EEST), Goulagman wrote:
> Hi,
> 
> 
> As per the tools I think the tools are not so relevant as long as the 
> community finds its way to discuss. Personally I don't love forums but that 
> is only my preference, as I don't like pizza with pineapple.
> 
> 
> 
> I think it's becoming too personal here. As a fervent defender of pizzas with 
> pineapple, this is an attack against my most innermost beliefs.
> 
> 
> Apart from that, I think that news groups are a good alternative to forums. 
> People using a mailing list would be slightly disturbed by the change (as 
> newsgroups can be used like mailing lists) and the newsgroups interface is 
> very close to a forum.
> 
> 
> Alex.
>

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

Re: [SailfishDevel] Acceptable Behaviour Guidelines - you decide

[Jarko Vihriala]

True dat. It's actually you, the community herein who should draw the line. 
But, once a 'general' list is up, we can ensure (i.e. set up policies and rules 
easier) here so _this_ group stays healthy.

br,Jarko

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Ville M. Vainio [vivai...@gmail.com]
Sent: Friday, May 23, 2014 10:01 PM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Acceptable Behaviour Guidelines - you decide


I don't think splitting is the solution, as opposed to drawing a line on what's 
acceptable overall.

E.g. on /r/rust, I've seen even subtly insulting comments (about purely 
technical topic at that!) get reprimanded with a request to adjust the tone. It 
seems to work just fine, and helps the 'offender' as much as it helps people 
reading the stuff.

On May 23, 2014 9:47 PM, "Jarko Vihriala" 
mailto:jarko.vihri...@jolla.com>> wrote:
We're looking into splitting the discussions on SF mailing lists. But, let's 
not make hasty moves and keep the technological part alive.

thanks, Jarko


From: 
devel-boun...@lists.sailfishos.org<mailto:devel-boun...@lists.sailfishos.org> 
[devel-boun...@lists.sailfishos.org<mailto:devel-boun...@lists.sailfishos.org>] 
on behalf of Ville M. Vainio [vivai...@gmail.com<mailto:vivai...@gmail.com>]
Sent: Friday, May 23, 2014 9:45 PM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Acceptable Behaviour Guidelines - you decide


Some of the discussions here have been borderline illegal; discouraging such 
behavior even with absence of 'technical' moderator tools (like you have even 
on barbaric environments like phpbb) is not necessarily a bad idea.

On May 22, 2014 5:53 PM, 
mailto:christopher.l...@thurweb.ch>> wrote:
Seconded. I could not have put it better myself.

Since the early days I have enjoyed the very open nature of this forum where 
pretty much anything goes that is vaguely Jolla / Qt / Open Source / technical.

>From my recollection the number of threads that struck me as "definitely 
>better elsewhere" has been refreshingly small. Many of the threads have been 
>helpful or and or insightful.

Keep up the good work

Chris

Zitat von "David Greaves" 
mailto:david.grea...@jolla.com>>:

There's been enough noise on this mailing list recently that some people have
felt they don't want to participate.

We need to be careful about over-policing discussions but there is such a thing
as under-policing too.

How would we (community, not Jolla) determine the line? and what measures do we
think should be taken?

Lorn pointed to this as a useful document:
  http://www.kde.org/code-of-conduct/

FWIW I personally don't think there's anything happened recently that I would
actually take action over. My delete key works fine and history shows that
sometimes cries for help come in strange forms.

David/lbt

PS This thread is for generic guidelines - please keep any specific issues out
of it.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to 
devel-unsubscr...@lists.sailfishos.org<mailto:devel-unsubscr...@lists.sailfishos.org>




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

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

Re: [SailfishDevel] Acceptable Behaviour Guidelines - you decide

[Jarko Vihriala]

We're looking into splitting the discussions on SF mailing lists. But, let's 
not make hasty moves and keep the technological part alive.

thanks, Jarko


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Ville M. Vainio [vivai...@gmail.com]
Sent: Friday, May 23, 2014 9:45 PM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Acceptable Behaviour Guidelines - you decide


Some of the discussions here have been borderline illegal; discouraging such 
behavior even with absence of 'technical' moderator tools (like you have even 
on barbaric environments like phpbb) is not necessarily a bad idea.

On May 22, 2014 5:53 PM, 
mailto:christopher.l...@thurweb.ch>> wrote:
Seconded. I could not have put it better myself.

Since the early days I have enjoyed the very open nature of this forum where 
pretty much anything goes that is vaguely Jolla / Qt / Open Source / technical.

>From my recollection the number of threads that struck me as "definitely 
>better elsewhere" has been refreshingly small. Many of the threads have been 
>helpful or and or insightful.

Keep up the good work

Chris

Zitat von "David Greaves" 
mailto:david.grea...@jolla.com>>:

There's been enough noise on this mailing list recently that some people have
felt they don't want to participate.

We need to be careful about over-policing discussions but there is such a thing
as under-policing too.

How would we (community, not Jolla) determine the line? and what measures do we
think should be taken?

Lorn pointed to this as a useful document:
  http://www.kde.org/code-of-conduct/

FWIW I personally don't think there's anything happened recently that I would
actually take action over. My delete key works fine and history shows that
sometimes cries for help come in strange forms.

David/lbt

PS This thread is for generic guidelines - please keep any specific issues out
of it.
___
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] Technical question: populating ListModel from C++

[Jarko Vihriala]

Actually, that's the best solution so far. Just make sure you follow the 
structure of the in qml/js of data inside QVariantList. Playing around QVariant 
and *List is a bit tricky but once you get the hang of it, it's awesome 
datatype.

thanks,Jarko

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Mikko Leppänen [mleppa...@gmail.com]
Sent: Friday, May 23, 2014 11:20 AM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Technical question: populating ListModel from C++

Hi,

Or if you don't want to subclass e.g. qabstractitemmodel, you can always return 
a QVariantList(or QList) from c++ and expose that sequence to QML. Then use 
that JS array to populate ListModel.

/Mikko


2014-05-23 10:53 GMT+03:00 Markus Svensson 
mailto:markus.svens...@me.com>>:
Hi,

I have done the same thing in my Sailfish learning project. It was way more 
complicated than I would have liked it to be (or maybe I did it in the wrong 
way...).

Feel free to have a look at how I implemented it: 
https://github.com/Ortofta/SilicaNote

The code quality is probably not the best - these are my first baby steps in QT 
and Sailfish. ;)

Regards,
Markus


23 maj 2014 kl. 08:52 skrev Kimmo Lindholm 
mailto:kimmo.lindh...@eke.fi>>:

Hi,,

Thank you Janne and Jarko, I will take a look on both of these approaches;

> use the QSqlQueryModel in your c++ and expose that to QML ; just like in : 
> http://qt-project.org/wiki/How_to_use_a_QSqlQueryModel_in_QML


> subclassing QAbstractItemModel. See 
> http://qt-project.org/doc/qt-5/qtquick-modelviewsdata-cppmodels.html and 
> http://qt-project.org/doc/qt-5/qabstractitemmodel.html to get started.


-kimmo
___

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] Right to silence

[Jarko Vihriala]

Hello,

This is my last and final comment on this topic. After this I instantiate a 
filter that does not let me see this or the previous non-technical topic (you 
all know what I am talking about). This is not , I repeat, this is not 
discriminating anyone. It's my own choice and I have the right for that. I'm 
following up on the developer issues on this mailing list. I don't deal with 
developer relations or alike - for that there is Iekku and other people.

I let the community to decide the rest of the actions on these topics, I cannot 
spend more time on this. The points of people who have expressed their view 
have been seen and no resolution on the original problem is handled.

If Filip or someone else wants to continue, my COMPANY email is 
@jollamobile.com. But, be informed ; my email is so busy 
that it takes me easily ~5d to reply back unless it's:
a) critical technical issue regarding SDK
b) notification I've won in lottery in which I have participated
c) something that deals with physical injury or even death of someone
d)  <- what? :)

Thanks and have a nice day.
-Jarko, one of the SDK guys.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Technical question: populating ListModel from C++

[Jarko Vihriala]

Hi!

Either that or use the QSqlQueryModel in your c++ and expose that to QML ; just 
like in :
http://qt-project.org/wiki/How_to_use_a_QSqlQueryModel_in_QML

thanks, Jarko


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Kimmo Lindholm [kimmo.lindh...@eke.fi]
Sent: Friday, May 23, 2014 9:17 AM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Technical question: populating ListModel from C++

Hi All,

What would be the best method to populate ListModel in QML from the C++ side?

I have sqlite database, which contents I would like to put on ListView.

List is changed only by user when deleting or adding entry, upon this action I 
would like to update sqlite and then refresh listmodel.

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

Re: [SailfishDevel] Discrimination and abuse from Jolla employee Thomas Perl

[Jarko Vihriala]

Dear Kaacz,
You have the right to your opinion. So does everone else. But when you start 
making assumptions, it would be good to check the facts and read things with 
open mind.

We cannot force anyone to settle their private issues if they don't want or 
just right now do not have time to go through the effort. Has there been 
technical query addressed and delivered to our sailor to which he has not 
responded? If so, that is an issue that might touch the company as well. 
Anything else doesn't. No matter how high the volume of such call is. That is 
professional behavior. Being a nice guy is something else. 

What comes to Sailors being seen always as representing the company I strongly 
disagree. Well, if that would be so, then I would happily let our comms 
department to handle anything else than direct email to my company mailbox 
concerning a subject that deals with my work. Is this the path you prefer? 

We work very hard and usually long days. How many more ca.100 person company 
has delivered an OS, smartphone, application sdk, application store and even 
keeps updates rolling. I am sorry if we cannot respond to all signals we get, 
but I assure you it is not because we ignore someone on company level. We are 
just so busy. The recent meetings with community show that we respect our 
community and want to share plans and workload among them. 

Thanks, Jarko


On Fri May 23 2014 00:38:49 GMT+0300 (EEST), k...@iol.cz wrote:
> IMHO .. THP, as sailor, unable to be silent. This is about professionality. 
> 
> Sorry, for now i got feeling: Jolla is unprofessional horde of tech geeks... 
> :\ 
> 
> Thu May 22 2014 17:41:13 GMT+0200 (CEST), Goulagman napsal:
> > On Thu, May 22, 2014 at 3:25 AM, Stefano Mosconi
> > wrote:
> > 
> > >
> > > Sorry Alexander, you are now putting words in my mouth...
> > >
> > > My answer was:
> > >
> > >
> > > "This is a private issue that does not belong here nor to Jolla."
> > >
> > > I didn't say: "Jolla has nothing to say on this case."
> > >
> > > We will have a community meeting today where the issue will be discussed
> > > (with Jolla and community) as it happens in every community.
> > 
> > 
> > Sorry for that. I was aware that the topic would be raised in the community
> > meeting, I wanted to say "Jolla has nothing more to say on this case for
> > the moment". I'm French and my English is not perfect ;).
> > 
> > From now on I mute this topic. Filip, you had a chance of making your point
> > during the community meeting and you didn't take it. I'm not gonna read
> > your wall of text. From my PoV, Jolla gave you a chance to state your case
> > publicly and you missed it. I see no witch-hunt in the IRC logs, I only see
> > people a bit puzzled by your silence and that cannot move forward because
> > you're not answering their questions.
> > 
> > It appears that Thomas Perl does not want to talk to you, that is why he
> > remains silent. So I think the protocol at this point would be to talk to
> > you and then get back to thp and do back and forth. If you don't want to
> > talk when it's your turn, then it's also your right, but then don't
> > complain that you don't have the answers you asked for.
> > 
> > Alex.
> >
> 
> -- 
> Sent from Jolla phone. Powered by Linux. No Windows, no viruses. :)
> ___
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
>

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

Re: [SailfishDevel] Discrimination and abuse from Jolla employee Thomas Perl

[Jarko Vihriala]

This is not about sweeping dust but please take your epistola to some other 
channel. This is a SailfishOS Devel mailing list and it is used to discuss 
technical topics. If there is need, we evaluate existence of other mailing 
lists. If you continue to flood this information channel we have to take 
actions to ensure technical discussion is what goes on in this mail list.

Consider yourself noticed.

Thanks, 
Jarko (jake9xx) 

On Thu May 22 2014 15:54:59 GMT+0300 (EEST), Filip Kłębczyk wrote:
> Hello,
> 
> So as I've promised I will express my opinions on the meeting and what 
> was said there on the mailing list.
> 
> So first of all second meeting point was supposed to be about taking 
> steps to solve the conflict proposed in my mail:
> http://wklej.org/id/1369055/
> 
> I've chosen to be silent, because I wanted to hear what others including 
> Jolla have to say on that matter and if that proposal is at all 
> acceptable for them. Unfortunately discussion turned into something 
> different, that seems to me like a witch-hunt made by Jolla employees 
> who were dominating the meeting. Below are full logs so everyone can 
> have their own opinion on that:
> 
> http://www.merproject.org/meetings/mer-meeting/2014/mer-meeting.2014-05-22-10.00.log.html
> 
> So first of all I had full right to stay silent at the meeting and they 
> should have respected that. Somehow others respect that Thomas Perl is 
> silent all the time, but when it comes to others that want to be silent 
> for a while they fail that pretty simple test and try to force speaking. 
> Double moral standards?
> 
> Now to the points raised by Stefano. During the last days I had a chance 
> to exchange lots of mails with Stefano and answer his questions. Sadly 
> it seems it was a waste of time as he did not get anything from it right.
> 
> Anyway regarding the points raised by Jolla employees:
> 
> *1*. Stefano Mosconi (Jolla): Let's keep those discussions out of the 
> mailing list
> 
> My answer:
> That is truly open approach to remove any uncomfortable topic, that seem 
> to important to at least some part of the community. Seems like the 
> story with dust under the carpet is still valid.
> 
> *2*. Philippe de Swert (Jolla): As there is no point discussing this if 
> the main person involved is not willing to discuss
> 
> My answer:
> Well there was clear proposal sent on the mailing list, but nobody 
> wanted to seriosuly discuss or comment it
> 
> *3* Denis Zalevskiy (as a private person): each Jolla employee is a 
> private person and talks as a private person unless said he represents 
> Jolla, so his intereaction with other people is personal
> 
> My answer:
> Jolla guidelines [1] tell different story. It enough if person is on 
> offcial Jolla communication channel (that includes Together) where 
> Thomas mentioned about hack event in Vienna, from which he tried later 
> to exclude me
> 
> *4* Jarko Vihriala (Jolla), about me being silent: We have other 
> responsibilities apart from this meeting as well. I don't think fk_lx 's 
> current behavior is at any way acceptable.
> 
> My answer:
> But Thomas Perl silence on this matter is completely acceptable?
> 
> *5* Stefano Mosconi (Jolla) commenting discrimination/abuse problem: 
> Event mentioned in this case is organized by Metalab, not Jolla. fk_lx 
> claimed that Jolla is discriminating against him. From related chat logs 
> and posts, it can be shown that this isn't the case. Conclusion from Jolla:
> *a)* Jolla as a company has nothing to do with it this issue
> 
> My answer:
> Yes, nothing at all, besides tolerating it
> 
> *b)* there is no trace that thp has requested Filip to be excluded he 
> just said that if Filip is coming he is not and in saying
> 
> My answer:
> 19:47 < thp> the meetups are in general open to everyone, but fk_lx is 
> excluded and specifically NOT invited for very good reasons.
> 
> see logs: http://wklej.org/hash/8ede3d7b136/
> 
> *c)* thp has reasons to avoid Filip and Filip seems to know why and 
> acknowledged that in his mail
> 
> My answer:
> I left the mail story for the end of this e-mail. Too bad Stefano you 
> haven't understood at all
> 
> *d)* no abuse or discrimination was done by thp, Carsten or any other 
> Jolla employee towards Filip
> 
> My answer:
> I tend to disagree, see my first post in the thread:
> 
> *e)* Jolla did not ignore Filip nor his emails at the time
> 
> My answer:
> What about e-mail from December that was ignored for months? What about 
> promises to answer by 25th/27th of April and failing that? And from the 
> above point we can get another information, that previously me or my 
> 

Re: [SailfishDevel] Discrimination and abuse from Jolla employee Thomas Perl

[Jarko Vihriala]

This case is one topic on the upcoming SailfishOS meeting.  

On Wed May 21 2014 15:20:30 GMT+0300 (EEST), Iosif Hamlatzis wrote:
> I as an indie developer want to know if something is going on that will 
> affect the future of the company. Not only because I have invested money, but 
> more importantly because I am investing time. 
> 
> 
> Also I do want to know what to expect in the future in case I come to a 
> similar situation.
> 
>

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

Re: [SailfishDevel] Spacing issues

[Jarko Vihriala]

What? It's a QML item. You can instantiate the standard magic as you please.
For the documentation, have you visited:
https://sailfishos.org/sailfish-silica/qml-sailfishsilica-backgrounditem.html 
also the SDK (1404 version) has updated Silica documentation in the built-in 
helps. That should get you somewhere.

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Chris Walker [cdw_noki...@the-walker-household.co.uk]
Sent: Tuesday, May 20, 2014 7:09 PM
To: devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] Spacing issues

On Tue, 20 May 2014 21:36:00 +0600
Andrey Kozhevnikov  wrote:

> delegate: BackgroundItem {
>la-la-la
> }

Okay. That's reinstated the list of beers but I'm back to square one in
that the text is overwriting the image.

So it's one step forward and one step back.

Where should I be looking for documentation on this? I've looked at row
stuff online but it lacks the details for how to specify margins,
positioning and the like. Or, the bits *I've* been looking at do ;-)
___
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] Source code of Silica Component Gallery qt-5

[Jarko Vihriala]

Yes, thanks for help Andrey. We have some challenges on the documentation and 
details what is actually in the package... Thanks to our superb community most 
stuff get resolved on mailing list, irc or t.j.c. However we sure need some 
sailfish development 101.. 
thanks, Jarko

On Thu May 01 2014 21:55:50 GMT+0300 (EEST), Nicolas Cisco wrote:
> Thank you!, i didn't notice the existance of the example folder in the SDK.
> 
> 
> 
> 
> 2014-05-01 0:39 GMT-03:00 Andrey Kozhevnikov :
> 
> SailfishOS/examples/componentgallery/
> 
> Where SailfishOS if path you installed SDK in.
> 
> 
> 01.05.2014 09:35, Nicolas Cisco пишет:
> 
> Hi!, 
> i'm a new developer trying out the sailfish sdk, i've found a Silica 
> Component Gallery already installed in the Sailfish Os image of the emulator. 
> I was wondering if someone knows where i can download the source code of the 
> gallery.
> 
> Thanks in advance!
> 
> -- 
> Nicolas Cisco
> www.nckweb.com.ar
> 
> 
> 
> 
> ___
> SailfishOS.org Devel mailing list
> 
> 
> 
> ___
> SailfishOS.org Devel mailing list
> 
> 
> 
> 
> -- 
> Nicolas Cisco
> www.nckweb.com.ar
>

-- 
Sent from my Jolla
___
SailfishOS.org Devel mailing list

[SailfishDevel] SDL2 versions (was: RE: SailfishOS SDK April update available tomorrow.)

[Jarko Vihriala]

The SDK2* stuff in this release are following what was released with the Jolla 
Phone update5.
Just checked and SDL2 is marked as version 2.0.1-1.2.1 and SDK2_mixer is 
2.0.0-1.1.2.

You can browse through the repositories with a web client on: 
http://releases.sailfishos.org/sdk/latest/

thanks, Jarko


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Iosif Hamlatzis [i.hamlat...@gmail.com]
Sent: Wednesday, April 16, 2014 11:33 AM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] SailfishOS SDK April update available tomorrow.

What about fixes on SDL2 and SDL2_mixer libraries? Are they included with this 
update?


On 16 April 2014 11:32, Luca Donaggio 
mailto:donag...@gmail.com>> wrote:
What about localization?
I've seen some work in that area in libsailfishapp git repo, does it make the 
cut and is included in present update?
Can you give some hints on how we should use it?


On Tue, Apr 15, 2014 at 8:36 PM, Jarko Vihriala 
mailto:jarko.vihri...@jolla.com>> wrote:
Hello again,

Tomorrow (16 April) at 10:00 UTC we will publish new installers, and package 
repositories for our Sailfish OS SDK version Alpha-1404-Qt5. Please note that 
links in this email are updated at that time as well.

We apologise for the long delay between the SDK updates. We had to completely 
recreate our SDK production environment before being able to release an update. 
This took longer than expected and is the main reason for the delay.

If you already have an existing Alpha-Qt5 SDK installed you should see the 
Updates Available icon in Qt Creator. If you don't have a previous SDK 
installation you can get the latest installer from http://www.sailfishos.org. 
It is recommended to uninstall the old SDK and download a new installer.

SDK content has been updated to match Jolla Release 1.0.5.16. Please see below 
for detailed information of the changed items.

A couple of things you should be aware of:
- Like before, in this update the build engine, emulator and targets are 
re-installed so you will lose all changes you may have made in those - however, 
if your application packaging is done correctly, rebuilding your projects 
should reinstall the packages you have been using.
- All customization done to SDK (adding new package repositories, adding custom 
targets, additional source paths) will be removed during the installation 
process so make your own backup of those before starting the update.
- If you import existing projects made with a previous version of the Sailfish 
OS SDK, make sure you select the correct kit in the project configuration step. 
Both ARM and i486 kits are available.
- Windows users need to install VC10 runtime from 
http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328 or the 
Installer will ask for admin rights during installation.
- Package repository contents have been updated and consequently using a 
previous SDK version with these package repositories is not supported.
- For more information, please see the SDK Alpha-Qt5 known issues list at: 
https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.
- Oldest Mac OS X supported is now 10.8.5 (Mountain Lion). Other supported 
platforms can be found from: 
https://sailfishos.org/alpha_qt5_sdk_release_notes.html

Here is a summary of changes:

SDK IDE (Qt Creator)
 - Crash fixes on OS X
 - Yaml editor removed from Qt Creator and yaml files are presented as plain 
text
 - Alternate projects folder can be changed from Mer settings page
 - Better path handling for shared directories in Windows
 - Updated Sailfish template project
 - Handle errors in project build/deploy phase more gracefully
 - Debugging with GDB from Qt Creator works with the Emulator and the Device
 - Tooltips are displayed for Virtual Machine statuses
 - Add changelog to your RPM with a .changes file

SDK Control Center:
 - Improved Targets management page
 - Clean build targets are available for download via the Targets page 
(pre-configured targets)
 - Easily install/remove multiple packages from a specific target
 - Updates page has a "Check for updates now" button
 - Added Harbour tools page with RPM validator tool

Installer:
 - Better VirtualBox version checking. Lowest version supported is v4.0
 - Install virtual machines using correct VirtualBox version specific parameters
 - Handle empty alternate projects folder setting
 - Install Sailfish template project as a package making it easier to update
 - Display Sailfish logo on Mac installer
 - MerSDK no longer directly uses User's home directory, but mounts it as 
/home/mersdk/share/ inside the virtual machine
 - User's home directory is no longer polluted with a .scratchbox2 folder
 - Shared mounts are mounted with correct access rights
 - Default i486 target renamed to SailfishOS-i486
 - Rework documentation packaging

Emulator:
 - Applications can be removed from the Emulator's home s

Re: [SailfishDevel] SailfishOS SDK April update available tomorrow. [update:all installers and repositories are online]

[Jarko Vihriala]

Did you run fresh installation or updated ?
If you did fresh install can you check the MD5SUM of that installer file? 
Current MD5 sums are online at:
https://sailfishos.org/wiki/FileInformation_SDK_1404

thanks, Jarko



From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of blood9ra...@gmail.com [blood9ra...@gmail.com]
Sent: Wednesday, April 16, 2014 6:37 PM
To: devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] SailfishOS SDK April update available tomorrow. 
[update:all installers and repositories are online]

I installed it on KDE Archlinux and i did not found any issues?
Should i reinstall?

On Wed Apr 16 2014 17:03:48 GMT+0200 (CEST), Jarko Vihriala wrote:
> Update: We fixed the issue and after testing also KDE based Linux distros 
> show green light. Go ahead and head to https://www.sailfishos.org/ and update 
> or install SailfishOS SDK 1404.
>
> For Linux users who managed to install/update their setup, it's recommended 
> to reinstall the 1404 SDK to make sure everything is working ok.
>
> We apologize this inconvenience and thank you for your understanding,
> the Jolla SDK Team
>
> 
> From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
> on behalf of Jarko Vihriala [jarko.vihri...@jolla.com]
> Sent: Wednesday, April 16, 2014 2:21 PM
> To: Sailfish OS Developers
> Subject: Re: [SailfishDevel] SailfishOS SDK April update available tomorrow.
>
> Hello all,
>
> We just discovered a serious issue related to using SDK with KDE based Linux 
> distros such as Fedora or KUbuntu. Therefore we have removed the Linux 
> installers from the SailfishOS website. Please do not try to download Linux 
> installers or update your SailfishOS SDK if you are using KDE Linux distro.
>
> We are now working to get the KDE issue solved, please stay tuned. We will 
> inform when SDK updates are again available.
>
> thanks, Jarko
>
>
>
> 
> From: Jarko Vihriala
> Sent: Tuesday, April 15, 2014 9:36 PM
> To: Sailfish OS Developers
> Subject: SailfishOS SDK April update available tomorrow.
>
> Hello again,
>
> Tomorrow (16 April) at 10:00 UTC we will publish new installers, and package 
> repositories for our Sailfish OS SDK version Alpha-1404-Qt5. Please note that 
> links in this email are updated at that time as well.
>
> We apologise for the long delay between the SDK updates. We had to completely 
> recreate our SDK production environment before being able to release an 
> update. This took longer than expected and is the main reason for the delay.
>
> If you already have an existing Alpha-Qt5 SDK installed you should see the 
> Updates Available icon in Qt Creator. If you don't have a previous SDK 
> installation you can get the latest installer from http://www.sailfishos.org. 
> It is recommended to uninstall the old SDK and download a new installer.
>
> SDK content has been updated to match Jolla Release 1.0.5.16. Please see 
> below for detailed information of the changed items.
>
> A couple of things you should be aware of:
> - Like before, in this update the build engine, emulator and targets are 
> re-installed so you will lose all changes you may have made in those - 
> however, if your application packaging is done correctly, rebuilding your 
> projects should reinstall the packages you have been using.
> - All customization done to SDK (adding new package repositories, adding 
> custom targets, additional source paths) will be removed during the 
> installation process so make your own backup of those before starting the 
> update.
> - If you import existing projects made with a previous version of the 
> Sailfish OS SDK, make sure you select the correct kit in the project 
> configuration step. Both ARM and i486 kits are available.
> - Windows users need to install VC10 runtime from 
> http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328 or the 
> Installer will ask for admin rights during installation.
> - Package repository contents have been updated and consequently using a 
> previous SDK version with these package repositories is not supported.
> - For more information, please see the SDK Alpha-Qt5 known issues list at: 
> https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.
> - Oldest Mac OS X supported is now 10.8.5 (Mountain Lion). Other supported 
> platforms can be found from: 
> https://sailfishos.org/alpha_qt5_sdk_release_notes.html
>
> Here is a summary of changes:
>
> SDK IDE (Qt Creator)
>  - Crash fixes on OS X
>  - Yaml editor removed from Qt Creator and yaml files are presented as plain 
> text
>  - Alternate projects folder can be changed 

Re: [SailfishDevel] SailfishOS SDK April update available tomorrow. [update:all installers and repositories are online]

[Jarko Vihriala]

Update: We fixed the issue and after testing also KDE based Linux distros show 
green light. Go ahead and head to https://www.sailfishos.org/ and update or 
install SailfishOS SDK 1404.

For Linux users who managed to install/update their setup, it's recommended to 
reinstall the 1404 SDK to make sure everything is working ok.

We apologize this inconvenience and thank you for your understanding,
the Jolla SDK Team


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Jarko Vihriala [jarko.vihri...@jolla.com]
Sent: Wednesday, April 16, 2014 2:21 PM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] SailfishOS SDK April update available tomorrow.

Hello all,

We just discovered a serious issue related to using SDK with KDE based Linux 
distros such as Fedora or KUbuntu. Therefore we have removed the Linux 
installers from the SailfishOS website. Please do not try to download Linux 
installers or update your SailfishOS SDK if you are using KDE Linux distro.

We are now working to get the KDE issue solved, please stay tuned. We will 
inform when SDK updates are again available.

thanks, Jarko




From: Jarko Vihriala
Sent: Tuesday, April 15, 2014 9:36 PM
To: Sailfish OS Developers
Subject: SailfishOS SDK April update available tomorrow.

Hello again,

Tomorrow (16 April) at 10:00 UTC we will publish new installers, and package 
repositories for our Sailfish OS SDK version Alpha-1404-Qt5. Please note that 
links in this email are updated at that time as well.

We apologise for the long delay between the SDK updates. We had to completely 
recreate our SDK production environment before being able to release an update. 
This took longer than expected and is the main reason for the delay.

If you already have an existing Alpha-Qt5 SDK installed you should see the 
Updates Available icon in Qt Creator. If you don't have a previous SDK 
installation you can get the latest installer from http://www.sailfishos.org. 
It is recommended to uninstall the old SDK and download a new installer.

SDK content has been updated to match Jolla Release 1.0.5.16. Please see below 
for detailed information of the changed items.

A couple of things you should be aware of:
- Like before, in this update the build engine, emulator and targets are 
re-installed so you will lose all changes you may have made in those - however, 
if your application packaging is done correctly, rebuilding your projects 
should reinstall the packages you have been using.
- All customization done to SDK (adding new package repositories, adding custom 
targets, additional source paths) will be removed during the installation 
process so make your own backup of those before starting the update.
- If you import existing projects made with a previous version of the Sailfish 
OS SDK, make sure you select the correct kit in the project configuration step. 
Both ARM and i486 kits are available.
- Windows users need to install VC10 runtime from 
http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328 or the 
Installer will ask for admin rights during installation.
- Package repository contents have been updated and consequently using a 
previous SDK version with these package repositories is not supported.
- For more information, please see the SDK Alpha-Qt5 known issues list at: 
https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.
- Oldest Mac OS X supported is now 10.8.5 (Mountain Lion). Other supported 
platforms can be found from: 
https://sailfishos.org/alpha_qt5_sdk_release_notes.html

Here is a summary of changes:

SDK IDE (Qt Creator)
 - Crash fixes on OS X
 - Yaml editor removed from Qt Creator and yaml files are presented as plain 
text
 - Alternate projects folder can be changed from Mer settings page
 - Better path handling for shared directories in Windows
 - Updated Sailfish template project
 - Handle errors in project build/deploy phase more gracefully
 - Debugging with GDB from Qt Creator works with the Emulator and the Device
 - Tooltips are displayed for Virtual Machine statuses
 - Add changelog to your RPM with a .changes file

SDK Control Center:
 - Improved Targets management page
 - Clean build targets are available for download via the Targets page 
(pre-configured targets)
 - Easily install/remove multiple packages from a specific target
 - Updates page has a "Check for updates now" button
 - Added Harbour tools page with RPM validator tool

Installer:
 - Better VirtualBox version checking. Lowest version supported is v4.0
 - Install virtual machines using correct VirtualBox version specific parameters
 - Handle empty alternate projects folder setting
 - Install Sailfish template project as a package making it easier to update
 - Display Sailfish logo on Mac installer
 - MerSDK no longer directly uses User's home directory, but mounts it as 
/home/mersdk/share/ inside the virtual machine
 - Us

Re: [SailfishDevel] SailfishOS SDK April update available tomorrow.

[Jarko Vihriala]

Hello all,

We just discovered a serious issue related to using SDK with KDE based Linux 
distros such as Fedora or KUbuntu. Therefore we have removed the Linux 
installers from the SailfishOS website. Please do not try to download Linux 
installers or update your SailfishOS SDK if you are using KDE Linux distro.

We are now working to get the KDE issue solved, please stay tuned. We will 
inform when SDK updates are again available.

thanks, Jarko




From: Jarko Vihriala
Sent: Tuesday, April 15, 2014 9:36 PM
To: Sailfish OS Developers
Subject: SailfishOS SDK April update available tomorrow.

Hello again,

Tomorrow (16 April) at 10:00 UTC we will publish new installers, and package 
repositories for our Sailfish OS SDK version Alpha-1404-Qt5. Please note that 
links in this email are updated at that time as well.

We apologise for the long delay between the SDK updates. We had to completely 
recreate our SDK production environment before being able to release an update. 
This took longer than expected and is the main reason for the delay.

If you already have an existing Alpha-Qt5 SDK installed you should see the 
Updates Available icon in Qt Creator. If you don't have a previous SDK 
installation you can get the latest installer from http://www.sailfishos.org. 
It is recommended to uninstall the old SDK and download a new installer.

SDK content has been updated to match Jolla Release 1.0.5.16. Please see below 
for detailed information of the changed items.

A couple of things you should be aware of:
- Like before, in this update the build engine, emulator and targets are 
re-installed so you will lose all changes you may have made in those - however, 
if your application packaging is done correctly, rebuilding your projects 
should reinstall the packages you have been using.
- All customization done to SDK (adding new package repositories, adding custom 
targets, additional source paths) will be removed during the installation 
process so make your own backup of those before starting the update.
- If you import existing projects made with a previous version of the Sailfish 
OS SDK, make sure you select the correct kit in the project configuration step. 
Both ARM and i486 kits are available.
- Windows users need to install VC10 runtime from 
http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328 or the 
Installer will ask for admin rights during installation.
- Package repository contents have been updated and consequently using a 
previous SDK version with these package repositories is not supported.
- For more information, please see the SDK Alpha-Qt5 known issues list at: 
https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.
- Oldest Mac OS X supported is now 10.8.5 (Mountain Lion). Other supported 
platforms can be found from: 
https://sailfishos.org/alpha_qt5_sdk_release_notes.html

Here is a summary of changes:

SDK IDE (Qt Creator)
 - Crash fixes on OS X
 - Yaml editor removed from Qt Creator and yaml files are presented as plain 
text
 - Alternate projects folder can be changed from Mer settings page
 - Better path handling for shared directories in Windows
 - Updated Sailfish template project
 - Handle errors in project build/deploy phase more gracefully
 - Debugging with GDB from Qt Creator works with the Emulator and the Device
 - Tooltips are displayed for Virtual Machine statuses
 - Add changelog to your RPM with a .changes file

SDK Control Center:
 - Improved Targets management page
 - Clean build targets are available for download via the Targets page 
(pre-configured targets)
 - Easily install/remove multiple packages from a specific target
 - Updates page has a "Check for updates now" button
 - Added Harbour tools page with RPM validator tool

Installer:
 - Better VirtualBox version checking. Lowest version supported is v4.0
 - Install virtual machines using correct VirtualBox version specific parameters
 - Handle empty alternate projects folder setting
 - Install Sailfish template project as a package making it easier to update
 - Display Sailfish logo on Mac installer
 - MerSDK no longer directly uses User's home directory, but mounts it as 
/home/mersdk/share/ inside the virtual machine
 - User's home directory is no longer polluted with a .scratchbox2 folder
 - Shared mounts are mounted with correct access rights
 - Default i486 target renamed to SailfishOS-i486
 - Rework documentation packaging

Emulator:
 - Applications can be removed from the Emulator's home screen by long-clicking 
on the application icon, just like it is done on the phone.

If you have any questions, you can either send email to this mailing list: 
devel@lists.sailfishos.org or write it up in http://together.jolla.com and tag 
your issue with 'sdk'.

Happy hacking,
Jolla SDK Team.

___
SailfishOS.org Devel mailing list

[SailfishDevel] SailfishOS SDK April update available tomorrow.

[Jarko Vihriala]

Hello again,

Tomorrow (16 April) at 10:00 UTC we will publish new installers, and package 
repositories for our Sailfish OS SDK version Alpha-1404-Qt5. Please note that 
links in this email are updated at that time as well.

We apologise for the long delay between the SDK updates. We had to completely 
recreate our SDK production environment before being able to release an update. 
This took longer than expected and is the main reason for the delay.

If you already have an existing Alpha-Qt5 SDK installed you should see the 
Updates Available icon in Qt Creator. If you don't have a previous SDK 
installation you can get the latest installer from http://www.sailfishos.org. 
It is recommended to uninstall the old SDK and download a new installer.

SDK content has been updated to match Jolla Release 1.0.5.16. Please see below 
for detailed information of the changed items.

A couple of things you should be aware of:
- Like before, in this update the build engine, emulator and targets are 
re-installed so you will lose all changes you may have made in those - however, 
if your application packaging is done correctly, rebuilding your projects 
should reinstall the packages you have been using.
- All customization done to SDK (adding new package repositories, adding custom 
targets, additional source paths) will be removed during the installation 
process so make your own backup of those before starting the update.
- If you import existing projects made with a previous version of the Sailfish 
OS SDK, make sure you select the correct kit in the project configuration step. 
Both ARM and i486 kits are available.
- Windows users need to install VC10 runtime from 
http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328 or the 
Installer will ask for admin rights during installation.
- Package repository contents have been updated and consequently using a 
previous SDK version with these package repositories is not supported.
- For more information, please see the SDK Alpha-Qt5 known issues list at: 
https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.
- Oldest Mac OS X supported is now 10.8.5 (Mountain Lion). Other supported 
platforms can be found from: 
https://sailfishos.org/alpha_qt5_sdk_release_notes.html

Here is a summary of changes:

SDK IDE (Qt Creator)
 - Crash fixes on OS X
 - Yaml editor removed from Qt Creator and yaml files are presented as plain 
text
 - Alternate projects folder can be changed from Mer settings page
 - Better path handling for shared directories in Windows
 - Updated Sailfish template project
 - Handle errors in project build/deploy phase more gracefully
 - Debugging with GDB from Qt Creator works with the Emulator and the Device
 - Tooltips are displayed for Virtual Machine statuses
 - Add changelog to your RPM with a .changes file

SDK Control Center:
 - Improved Targets management page
 - Clean build targets are available for download via the Targets page 
(pre-configured targets)
 - Easily install/remove multiple packages from a specific target
 - Updates page has a "Check for updates now" button
 - Added Harbour tools page with RPM validator tool

Installer:
 - Better VirtualBox version checking. Lowest version supported is v4.0
 - Install virtual machines using correct VirtualBox version specific parameters
 - Handle empty alternate projects folder setting
 - Install Sailfish template project as a package making it easier to update
 - Display Sailfish logo on Mac installer
 - MerSDK no longer directly uses User's home directory, but mounts it as 
/home/mersdk/share/ inside the virtual machine
 - User's home directory is no longer polluted with a .scratchbox2 folder
 - Shared mounts are mounted with correct access rights
 - Default i486 target renamed to SailfishOS-i486
 - Rework documentation packaging

Emulator:
 - Applications can be removed from the Emulator's home screen by long-clicking 
on the application icon, just like it is done on the phone.

If you have any questions, you can either send email to this mailing list: 
devel@lists.sailfishos.org or write it up in http://together.jolla.com and tag 
your issue with 'sdk'.

Happy hacking,
Jolla SDK Team.

___
SailfishOS.org Devel mailing list

[SailfishDevel] SailfishOS SDK January update available today.

[Jarko Vihriala]

Hello again,

Today at 16:00 UTC we are publishing a little update on SailfishOS SDK. The 
update itself touches only the Build Engine.

What you need to do is to boot up the Build Engine after the updates have been 
published (i.e. click the sdk icon in Qt Creator) and wait 10 minutes while it 
refreshes its repositories. Then access the SDK Control Center Updates view and 
you should see that Engine updates are available.

Release note:
 - SDK Control Center

  *   - Download and reinstall build targets (i.e.) sysroots. This is done 
using the new pull-down menu called 'Pre-configured targets'  in 'Targets' view 
of Control Center.

  *   - Provide a tool to verify that basic submission criterias are fulfilled 
with Harbour intake requirements. This is done from the new view called 
'Harbour Tools' in Control Center.

If you have any questions, you can either send email to this mailing list: 
devel@lists.sailfishos.org or write it up on together.jolla.com and tag your 
issue with 'sdk'.

Happy hacking,
Jolla SDK Team.
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Harbour/Jolla store improvement suggestion to separate Android/Sailfish apps

[Jarko Vihriala]

Once the co-creation site is open, I strongly recommend keeping this alive 
there - it's the best way to influence our doings.

thanks, Jarko

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Aapi Hämäläinen [aapi.hamalai...@gmail.com]
Sent: Thursday, December 19, 2013 9:46 PM
To: devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] Harbour/Jolla store improvement suggestion to 
separate Android/Sailfish apps

On 19.12.2013 21:24, Marko Koschak wrote:
> On Do, 2013-12-19 at 18:44 +, Kimmo Lindholm wrote:
>> Can you add information about whether the application is for Android
>> (apk) or for Sailfish (rpm) into the Jolla store?
>> [...]
>> And, please, also make there a filter – Show only Sailfish apps.
>>
>> Any +1 ? anyone?
> +1

+1 -- a filter would be really handy.

--
aapi
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list

[SailfishDevel] Quickfix for SailfishOS SDK available today.

[Jarko Vihriala]

Hello again,

Today at 10:00 UTC we will publish an update for Qt Creator (SailfishOS SDK 
IDE), which fixes the missing application output logs.

The update will be made available via the SDK maintenance tool and Qt Creator 
will display an update notifier when it is ready for downloading.

Here's are the release notes for this update:

SailfishOS SDK IDE:
* Qt Creator updated to version 2.8.1-4
* Fixes missing application output logs - emulator traces can be now seen in Qt 
Creator's application output window.

If you encounter any issues, please report them to Sailfish developers mailing 
list at devel@lists.sailfishos.org

Happy hacking,
The Jolla SDK Team


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] How to deploy app to Jolla device?

[Jarko Vihriala]

Hello,
The thing we did not document is that host needs to have static IP of 192.168.2 
and then device creation works like in 
https://sailfishos.org/develop-firstapp-article.html chapter 'Create a 
connection to Mer ARM device.".

thanks, Jarko


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Seppo Tiainen [seppo.tiai...@gmail.com]
Sent: Saturday, December 14, 2013 6:12 PM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] How to deploy app to Jolla device?

Please check thread 'Connecting Jolla device to SDK', 5th December below. It is 
not too simple yet.


2013/12/14 Kalle Lammenoja 
mailto:kalle.lammen...@gmail.com>>
There is propably a quide somewhere, i just havent found it. So how do i deploy 
an app on sailfish IDE directly to Jolla device connected with usb on dev mode? 
On windows and linux?

___
SailfishOS.org Devel mailing list

___
SailfishOS.org Devel mailing list

[SailfishDevel] SailfishOS SDK December update available today.

[Jarko Vihriala]

Hello again,

Today at 14:00 UTC we will publish new installers, package repositories and 
updated website documentation for our SailfishOS SDK version Alpha-1312-Qt5.

If you already have an existing Alpha-Qt5 SDK installed you should see updates 
available icon in Qt Creator. If you don't have it installed, you can get the 
latest installer from www.sailfishos.org. It is 
recommended to uninstall the old SDK and download a new installer.

This update brings the long-awaited Mer ARM device support to Qt Creator and 
fixes issues with the application template regarding requirements for Harbour 
submissions. Qt Creator Sailfish kits now also support shadow building, which 
separates the different architecture builds from each other negating the need 
to always clean the build directory when switching between ARM and i486 kits.

A couple of things you should be aware of:
- Like before, in this update the build engine, emulator and targets are 
re-installed so you will lose all changes you may have made in those - however, 
if your application packaging is done correctly, rebuilding your projects 
should reinstall the packages you have been using.
- All customization done to SDK (adding new package repositories, adding custom 
targets, additional source paths) will be removed during the installation 
process so make your own backup of those before starting the update.
- If you import existing projects made with a previous version of the Sailfish 
OS SDK, make sure you select the correct kit in the project configuration step. 
Both ARM and i486 kits are available.
- Windows users need to install VC10 runtime from 
http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328 or Installer 
will ask for admin rights during installation.
- Package repository structure on SailfishOS.org has changed to be closer to 
the released Jolla phone repositories, so previous SDK installations will not 
work.
- For more information, please see SDK Alpha-Qt5 known issues list at: 
https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.

Here are the release notes of this update.

Installer:
* Setting the additional application source folder now actually works. This 
setting can be used to specify a project location that is outside of your home 
directory.

SailfishOS SDK IDE:
* Qt Creator updated to version 2.8.1-3
* Qt Creator uses new wizard to create Mer ARM device, device creation is 
described on https://sailfishos.org/develop-firstapp-article.html in section 
'Create a connection to Mer ARM device'
* Shadow building is supported, you can now safely build applications for both 
architectures without them clashing.
* Shadow building is on by default for each new project, but can be turned off 
in project's settings.
* Latest SDK Application template is integrated so Harbour application 
requirements can be more easily fulfilled.
* User settings are now stored in a new directory (Linux/OSX: 
$HOME/.config/SailfishAlpha3, 
Windows:C:\users\username\AppData\Roaming\SailfishAlpha3) so deleting old 
settings directory is not mandatory.

Templates/examples/tutorials
* Templates are updated with the latest SDK Application template.
* Quite a few Qt5 tutorial applications were ported to Sailfish OS, they can be 
found from ~/SailfishOS/tutorials and they can be used to study Sailfish OS 
application behaviour. Each tutorial's project directory has a README.md file 
which contains notes from a developer when porting the application from Desktop 
QML to Sailfish OS. Some of the notes might be outdated.

SDK Maintenance Tool:
* Installer version updated to 1.4.0-2.

Documentation:
* Documentation is updated with latest available versions. Documentation may 
contain references to Qt 5.0 - please see known issues list at: 
https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.

Build Engine:
* Shadow building creates separate build directories outside your project 
directory named build-PROJECTNAME-KITNAME-[Debug|Release]
* The RPM packages for your project are also created under the shadow build 
directory
* Build Engine will not treat missing qtc_ macros in spec file as fatal.

SailfishOS Emulator:
* Emulator software is updated to match Jolla Phone release 1.0.1-10 
"Laadunjärvi".
* SSH login password for nemo user can be set with Developer settings in 
Settings application.
* Package repositories can be refreshed with Developer settings in Settings 
application.
* Icon sizes are matched to Harbour requirements.

SailfishOS Targets:
* Both i486 and ARM target builds based on updated Jolla baseline.

If you encounter any issues, please report them to Sailfish developers mailing 
list at devel@lists.sailfishos.org

Happy hacking,
The Jolla SDK Team
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Emulator: Mouse pointer not visible

[Jarko Vihriala]

Hello,

This incident seems to be related to distros running KDE ; we are looking at it 
and will provide more info as we find out why mouse is not released. In my 
Ubuntu box (on Gnome) I cannot reproduce the problem.

However, I'd like to ask you guys to test this. Can you please do multiple 
mouse clicks on VM window when emulator is booting and check if mouse 
disappears on emulator.

If it does, I'd like to know the distro and used wm.

thanks, Jarko
<https://connect.emailsrvr.com/owa/?ae=PreFormAction&a=ReplyAll&t=IPM.Note&id=RgDU2c726YgTTqYYUcDTI%2bBYBwAnRyCdpd8gRb2aabwlJA8kAAA3v3jsAAAnRyCdpd8gRb2aabwlJA8kAAA3v4XXAAAJ&pspid=_1386667722027_22251467#>


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Mikael Hermansson [m...@7b4.se]
Sent: Sunday, December 08, 2013 10:01 PM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Emulator: Mouse pointer not visible


I have also seen this issue randomly on my kubuntu box.



The solution for me is to restart sailfish emulator when it happens.



I got the feeling that it has to do with how Vbox mouse has focus inside VM 
when booting the sailfishos? I noticed that if you accidently click inside the 
emulator when sf is booting the mousepointer will not appear when UI has 
started. I have tested this now 10 times or so if the mouse pointer is not 
inside when boot it always success. But if mouse pointer inside area and click 
when kernel has started print it messages, it often fails.



Seems like kernel gets that event and hijack the sailfish mousehandling or 
something?





Regards



Mikael







On Sunday 08 December 2013 19.29.13 Jarko Vihriala wrote:

> Well we have seen on-site one setup like this where user had manually

> modified VBox settings and thus causing mouse to non-work.

>

> However, let's try to solve this first of all

> a)what it the distro ?

> b)do you have started the VBox kernel drivers on host?

> c)have you tested other VBox machines

> d)does dmesg / syslog / journalcrtl reveal any errors?

>

> thanks, Jarko

> 

> From: devel-boun...@lists.sailfishos.org

> [devel-boun...@lists.sailfishos.org] on behalf of Uwe Koch

> [as...@yahoo.com] Sent: Sunday, December 08, 2013 10:38 AM

> To: devel@lists.sailfishos.org

> Subject: [SailfishDevel] Emulator: Mouse pointer not visible

>

> Hi,

>

> quite disappointing for me - can't catch the mouse inside the Sailfish SDK

> emulator. Nothing to see - so no clicking and dragging ;-(

>

> Installed latest Virtualbox environment - both in KDE and Linux Mint.

> Any help how to see where the problem is?

>

> Can't find anything in virtualbox forums - so ask here if anyone has same

> problem!

>

> Best regards,

> Uwe

>

> __ _-_

> \|).---'---`---.

>

> || \._./

> ||

> || / ,' `---'

>

> ___||_,--' -._

> /___ ||(-

> `---._-'

> ___

> SailfishOS.org Devel mailing list

> ___

> SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Emulator: Mouse pointer not visible

[Jarko Vihriala]

Well we have seen on-site one setup like this where user had manually modified 
VBox settings and thus causing mouse to non-work.

However, let's try to solve this first of all
a)what it the distro ?
b)do you have started the VBox kernel drivers on host?
c)have you tested other VBox machines
d)does dmesg / syslog / journalcrtl reveal any errors?

thanks, Jarko

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Uwe Koch [as...@yahoo.com]
Sent: Sunday, December 08, 2013 10:38 AM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Emulator: Mouse pointer not visible

Hi,

quite disappointing for me - can't catch the mouse inside the Sailfish SDK 
emulator.
Nothing to see - so no clicking and dragging ;-(

Installed latest Virtualbox environment - both in KDE and Linux Mint.
Any help how to see where the problem is?

Can't find anything in virtualbox forums - so ask here if anyone has same 
problem!

Best regards,
Uwe

__  _-_
\|).---'---`---.
||\._./
|| / ,'   `---'
___||_,--'  -._
/___  ||(-
`---._-'
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Connecting Jolla device to SDK

[Jarko Vihriala]

Hello,

Currently (SDK tagged as 1310) is not capable of doing device deployment. What 
we are testing right now is a SDK that allows you to create a valid device in 
Qt Creator and deploy to that directly from Qt Creator's UI. There are couple 
little quirks still remaining but we're working on them.

Hopefully we can push it out really soon.

thanks, Jarko


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Seppo Tiainen [seppo.tiai...@gmail.com]
Sent: Thursday, December 05, 2013 3:01 PM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Connecting Jolla device to SDK

First, is the current Alpha2 QtCreator/SDK capable of connecting to the new 
Jolla phone through USB for testing apps under development?

If yes, there are many parameters (Device type, Username/Password...) that need 
to be correctly set. Short instructions would be very welcome.

I did not succeed yet. Anybody tried?

Seppo
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Fwd: Massive issues while installing SailfishOS IDE

[Jarko Vihriala]

This happens when Qt Creator cannot instantiate the Mer Plugin and thus cannot 
prepare you a kit for it. If you run VirtualBox console, do you still see those 
VMs ?

thanks, Jarko

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Kajetan Dobczyk [kajetan.dobc...@gmail.com]
Sent: Friday, November 22, 2013 12:58 PM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Fwd: Massive issues while installing SailfishOS IDE

Hello,
I am being forced to install SailfishOS IDE on another laptop, because my own 
is being repaired right now. On my laptop, everything worked perfectly - I 
downloaded the IDE, installed it and could code right away.

On this one however, I have several issues.
Machine specs:
i3 M390 2.67GHz
4096MB RAM
Windows 7 Home Premium x64
Intel(R) HD Graphics (Core i3), 1696MB

After the IDE installation:

- There's no Sailfish project option in "File -> New File or Project", although 
Mer is checked in "Help -> About Plugins"

- In "Tools -> Options -> Mer", when I click "Start Emulator", nothing happens, 
either in SailfishOS Emulator / MerSDK. My VirtualBox is 4.1.8, I've tried with 
the newest one too. After one of many installations, I could turn on the 
emulator, but when I tested the connection, I got this message: "ssh connection 
failure: server rejected key.".
I see that some other folders are created on my hard drive - IDE is installed 
in "Sailfish", and near it are "SailfishOS" and "Sailfish OS". Maybe the 
uninstall utility doesn't clear everything?

- When I click on "SailfishOS" in the main menu, I get the message "The SDK VM 
is not responding. Create a new SailfishOS project (or open an existing one) 
and press the Start SDK button on the lower left."

- When i try on the Examples' "Sailfish Silica Component" or "Media Gallery", 
the "import Sailfish.Silica 1.0" is underline and the module can't be found.

Does anyone know what can I do to simply start the emulator and be able to make 
or open a Sailfish Sila project? It's driving me insane, I spent about 10 hours 
struggling with this and I'm out of ideas.

Regards,
Kajetan

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Connection to Emulator not working if PC offline

[Jarko Vihriala]

Hello all,

We tested the offline situation as well when preparing the images so we did 
obviously something differently. We'll visit this issue for sure before we 
launch next release of SDK.

Right now we are working hard to make the emulator content and it's APIs to 
match 1:1 the stuff that real device uses. There were many changes even on the 
repository layouts so things just take time.

But ; next SDK is coming up pretty soon.

thanks, Jarko

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Luciano Montanaro [mikel...@gmail.com]
Sent: Wednesday, November 20, 2013 1:49 PM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Connection to Emulator not working if PC offline

Hi Andrey,

this happens to me too. I am using Linux, Kubuntu 13.10.

The workaround I have found is to ifconfig 192.168.0.1 (or something like that)
to give an address to the network. This usually lets me use the emulator.

Luciano


On Wed, Nov 20, 2013 at 9:28 AM, Andrey Kozhevnikov
 wrote:
> I'm not connected via wlan or lan. just not connected. want to code when i'm
> on long road to home without any internet connection :)
>
>
> On 20.11.2013 14:26, Jarko Vihriala wrote:
>>
>> party, but the name acrynym is not that obivious, it is
>> (P)rogram(R)esponsiveness(I)dle(S)ystem(M)anagement :)
>>
>> Joke's aside. It's interesting to see that happen with your PC as we tried
>> both offline and online with the 1310 SDK package. Obiviously we did not
>> test some combination. Are you on WLAN or LAN?
>>
>> thanks, Jarko
>>
>> 
>> From: devel-boun...@lists.sailfishos.org
>> [devel-boun...@lists.sailfishos.org] on behalf of Andrey Kozhevnikov
>> [coderusin...@gmail.com]
>> Sent: Wednesday, November 20, 2013 10:05 AM
>> To: Sailfish OS Developers
>> Subject: [SailfishDevel] Connection to Emulator not working if PC offline
>>
>> Just found weird problem. If my laptop not connected to internet,
>> Sailfish Emulator not responding and i can't work with it.
>> Anyone else have same problem?
>> ___
>> SailfishOS.org Devel mailing list
>> ___
>> SailfishOS.org Devel mailing list
>
>
> ___
> SailfishOS.org Devel mailing list



--
Luciano Montanaro

Anyone who is capable of getting themselves made President should on
no account be allowed to do the job. -- Douglas Adams
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Connection to Emulator not working if PC offline

[Jarko Vihriala]

party, but the name acrynym is not that obivious, it is 
(P)rogram(R)esponsiveness(I)dle(S)ystem(M)anagement :)

Joke's aside. It's interesting to see that happen with your PC as we tried both 
offline and online with the 1310 SDK package. Obiviously we did not test some 
combination. Are you on WLAN or LAN? 

thanks, Jarko


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Andrey Kozhevnikov [coderusin...@gmail.com]
Sent: Wednesday, November 20, 2013 10:05 AM
To: Sailfish OS Developers
Subject: [SailfishDevel] Connection to Emulator not working if PC offline

Just found weird problem. If my laptop not connected to internet,
Sailfish Emulator not responding and i can't work with it.
Anyone else have same problem?
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Updating application icons. After a couple of days of sweat, blood and swear

[Jarko Vihriala]

Hello,

There is a known issue with Lipstick on this icon case and once that is solved 
it should not require all those steps. We are working on to get it out.

As workaround the steps you describe are as good as it gets and like you said, 
sometimes even that does not help. Funny enough, sometimes just by deinstalling 
the app from launcher and re-installing it fixes this, so there is some random 
behavior...

But, we are working on to get it right.

thanks, Jarko


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Artem Marchenko [artem.marche...@gmail.com]
Sent: Tuesday, November 19, 2013 9:26 PM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Updating application icons. After a couple of days of 
sweat, blood and swear

Dear sailors

Please, add to FAQ a guide on how to *update* the application icon or maybe 
make deployment process handle it if possible.

I was trying to update the icon for my app, I just couldn't figure it out, was 
blaming my not exactly default project structure (I use src/tests folders), 
uninstalling packages via zypper, manually deleting files in the emulator, 
rebooting emulator, even reinstalling SDK. What was most frustrating was that 
some tricks worked sometimes and sometimes they didn't.

In the end I figured the procedure that sort of works most of the time:
1. Stop your app
2. Uninstall package with zypper
3. Restart emulator
4. Clean your project
5. Rebuild and run
.. and sometimes it still doesn't seem to work for the first time.

I might be missing something real simple, but so the other developers probably. 
It would be great if you could add instructions on how to update the icon 
probably or if you could make Qt Creator handle it on its own somehow.

Best regards,
Artem.

P.S.
What if published application decides to upgrade its icon. Will the user have 
the same issues after the update? What I was seeing is not even the old icon 
staying in place, there was no icon at all. Hopefully end users won't 
experience it.

--
Artem Marchenko
http://agilesoftwaredevelopment.com
http://twitter.com/AgileArtem
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] SDK paths reference

[Jarko Vihriala]

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.

./usr/share/hourtracker/qml/

Location of QML stuff

./usr/share/icons/hicolor/86x86/apps/hourtracker.png

Icon that shows up in launcher

thanks, Jarko


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Andrey Kozhevnikov [coderusin...@gmail.com]
Sent: Sunday, November 10, 2013 1:23 PM
To: devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] SDK paths reference

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.

Best,
tortoisedoc



___
SailfishOS.org Devel mailing list

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Can't open emulator after updating the latest emulator

[Jarko Vihriala]

Thanks,
from the log: it tries to load:
http://releases.sailfishos.org/sdk/repository/linux-32/org.merproject.maintenance/0.0.8-2sdkmaintenance.7z

But that is not to be found, instead it should be:
http://releases.sailfishos.org/sdk/repository/linux-32/org.merproject.maintenance/1.4.0-1sdkmaintenance.7z

So it cannot find the right packages. Also the log tells it cannot find for 
example:
http://releases.sailfishos.org/sdk/repository/common/org.merproject.mersdk/2013.10.18-0mersdk.7z

But that is a valid url, so I'm guessing some network error there. What happens 
if you just run update again from Qt Creator? Or even better, run 
SDKMaintenancetool with -v and paste the output here if you encounter more 
errors.

thanks, Jarko

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of flash yan [flashya...@gmail.com]
Sent: Sunday, November 03, 2013 11:40 AM
To: devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] Can't open emulator after updating the latest 
emulator

Hello,

The virtualbox version is 4.2.6_OSE r82870.
I don't remember clearly,maybe closed.
Please see the attached file.
The day is October 30.

brad

On 11/03/2013 03:23 PM, Jarko Vihriala wrote:
> Hello,
> We have not tested with OpenSUSE at all, but let's start cracking it:
> - what is VirtualBox version you have?
> - was emulator running when you ran update?
>
> There is a file "InstallationLog.txt" in ~/SailfishOS , can you please send 
> it here?
>
> thanks, Jarko
> 
> From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
> on behalf of flash yan [flashya...@gmail.com]
> Sent: Sunday, November 03, 2013 5:48 AM
> To: devel@lists.sailfishos.org
> Subject: [SailfishDevel] Can't open emulator after updating the latest  
> emulator
>
> Hi all,
>
> At Wednesday I have updated the latest updating.It is about emulator.
> After downloading,it reported install vbox error.And then,there is no
> emulator in my SDK.
> When I clicked the emulator icon,error is shown as below:
>
> VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001),
> component VirtualBox, interface IVirtualBox, callee nsISupports
> VBoxManage: error: Context: "FindMachine(Bstr(pszVM).raw(),
> machine.asOutParam())" at line 563 of file VBoxManageMisc.cpp
>
> What's wrong with this updating?
>
> THanks.
>
> brad_qqq
> ___
> SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Can't open emulator after updating the latest emulator

[Jarko Vihriala]

Hello,
We have not tested with OpenSUSE at all, but let's start cracking it:
- what is VirtualBox version you have?
- was emulator running when you ran update?

There is a file "InstallationLog.txt" in ~/SailfishOS , can you please send it 
here?

thanks, Jarko

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of flash yan [flashya...@gmail.com]
Sent: Sunday, November 03, 2013 5:48 AM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Can't open emulator after updating the latest  emulator

Hi all,

At Wednesday I have updated the latest updating.It is about emulator.
After downloading,it reported install vbox error.And then,there is no
emulator in my SDK.
When I clicked the emulator icon,error is shown as below:

VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001),
component VirtualBox, interface IVirtualBox, callee nsISupports
VBoxManage: error: Context: "FindMachine(Bstr(pszVM).raw(),
machine.asOutParam())" at line 563 of file VBoxManageMisc.cpp

What's wrong with this updating?

THanks.

brad_qqq
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Installer Freeze after "Set Project Directory" Step

[Jarko Vihriala]

resending to devel list as well - my stupid email program did not send it there 
by default :(



From: Jarko Vihriala
Sent: Saturday, November 02, 2013 11:53 PM
To: cckwes
Subject: RE: [SailfishDevel] Installer Freeze after "Set Project Directory" Step

Hello,
This was new instance of the Gtk-CRITICAL stuff that on 'installer' category in:
"https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues";

as it did not have that in trace. But , end is good, all is good. Thanks for 
bringing this up. We'll update the wiki soon.

thanks, Jarko



From: cckwes [cck...@gmail.com]
Sent: Saturday, November 02, 2013 5:49 PM
To: Jarko Vihriala
Subject: Re: [SailfishDevel] Installer Freeze after "Set Project Directory" Step

Hi,

 After googling around for the solution, I come across this thread on 
ubuntu forum: 
http://ubuntuforums.org/showthread.php?t=1988663&s=b5ac629d4ec9992bc05889673dd037d2

 I follow the fix by adding "LIBOVERLAY_SCROLLBAR=0" in front of 
./SailfishOSSDK-Alpha-1310-Qt5-linux-64-offline.run and hoorah! It's working!

 I found that I need to prepend the above line also if I want to run the 
SDKMaintenanceTool or else it will freeze again after checking for updates.

 Thanks for your kind support and I finally found the fix for this problem. 
Thank you very much

Regards,
Wesley


On Sat, Nov 2, 2013 at 10:57 PM, cckwes 
mailto:cck...@gmail.com>> wrote:
Hi,

 I've run the installer with -v option and attach the output with this mail.

Thanks,
Wesley


On Sat, Nov 2, 2013 at 9:13 PM, Jarko Vihriala 
mailto:jarko.vihri...@jolla.com>> wrote:
Hello,
Thanks for the list, unfortunately it did not reveal too much I can tell that 
components.xml is not found but why not - is a mystery.

Can I please get a -v trace from the installation: i.e. run the installer but 
with -v option. It should create a log or open another command prompt (it does 
that in windows) and it should tell what is going on... So please do that & 
paste the log here.

thanks, Jarko


From: cckwes [cck...@gmail.com<mailto:cck...@gmail.com>]
Sent: Saturday, November 02, 2013 12:39 AM
To: Jarko Vihriala
Subject: Re: [SailfishDevel] Installer Freeze after "Set Project Directory" Step

Hi,

 I have try run the installer with strace and attach the output with this 
mail.

Thanks
Wesley


On Sat, Nov 2, 2013 at 1:01 AM, Jarko Vihriala 
mailto:jarko.vihri...@jolla.com>> wrote:
Hello,
I haven't seen that happen ever... have you run installer with strace or 
similar to get more info of the operation?

thanks, Jarko


From: 
devel-boun...@lists.sailfishos.org<mailto:devel-boun...@lists.sailfishos.org> 
[devel-boun...@lists.sailfishos.org<mailto:devel-boun...@lists.sailfishos.org>] 
on behalf of cckwes [cck...@gmail.com<mailto:cck...@gmail.com>]
Sent: Thursday, October 31, 2013 3:50 PM
To: devel@lists.sailfishos.org<mailto:devel@lists.sailfishos.org>
Subject: [SailfishDevel] Installer Freeze after "Set Project Directory" Step

Hi,

I just installed Elementary OS Luna (base on Ubuntu 12.04) on my laptop and 
I'm installing Sailfish OS SDK (1310 64bit).

The installer and the system freeze after i click "Next" at "Set Project 
Directory" step. At first, I thought it's a corrupted installer but I've 
re-download the installer and verify that it's not corrupted.

Also, I found this bug which is similar to the problem I've encountered. 
https://bugreports.qt-project.org/browse/QTBUG-25994 . I try install the SDK 
using sudo as suggested by the bug report but failed because installer does not 
allow root installation.

Please help me to solve this problem. Thanks

--
Wesley Chong




--
Wesley Chong

Email: cck...@gmail.com<mailto:cck...@gmail.com>
Blog: http://blog.linux4us.org



--
Wesley Chong

Email: cck...@gmail.com<mailto:cck...@gmail.com>
Blog: http://blog.linux4us.org



--
Wesley Chong

Email: cck...@gmail.com<mailto:cck...@gmail.com>
Blog: http://blog.linux4us.org
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Installer Freeze after "Set Project Directory" Step

[Jarko Vihriala]

Hello,
I haven't seen that happen ever... have you run installer with strace or 
similar to get more info of the operation?

thanks, Jarko


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of cckwes [cck...@gmail.com]
Sent: Thursday, October 31, 2013 3:50 PM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Installer Freeze after "Set Project Directory" Step

Hi,

I just installed Elementary OS Luna (base on Ubuntu 12.04) on my laptop and 
I'm installing Sailfish OS SDK (1310 64bit).

The installer and the system freeze after i click "Next" at "Set Project 
Directory" step. At first, I thought it's a corrupted installer but I've 
re-download the installer and verify that it's not corrupted.

Also, I found this bug which is similar to the problem I've encountered. 
https://bugreports.qt-project.org/browse/QTBUG-25994 . I try install the SDK 
using sudo as suggested by the bug report but failed because installer does not 
allow root installation.

Please help me to solve this problem. Thanks

--
Wesley Chong

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] How to check Emulator version

[Jarko Vihriala]

Hello,
At least with Qt Creator's updater you can check the versions of each 
component. 

If you can pull additional packages from sailfishos.org to your emulator, it 
has been updated - simple as that.

thanks, Jarko

From: christopher.l...@thurweb.ch [christopher.l...@thurweb.ch]
Sent: Wednesday, October 30, 2013 9:50 PM
To: Jarko Vihriala; devel@lists.sailfishos.org
Subject: How to check Emulator version

Hi Jarko

Is there a way of checking the Emulator version? (e.g. by terminal
command on the emulator?).

Today's update bugged out on OSX, but after that the Emulator still
starts, so either
a) the update did nothing, and I have the old state
b) the update more or less succeeded, I have the new version despite
the errors during update.

Chris


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Maintenance tool uninstall components not possible

[Jarko Vihriala]

True, component de/selection will be delivered in beta sdk.

thanks, Jarko


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Tone Kastlunger [users.giulie...@gmail.com]
Sent: Wednesday, October 30, 2013 8:49 PM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Maintenance tool uninstall components not possible

all items in the treeview are "gray"'ed out, making deselecting them singularly 
impossible.
Only possible solution is to remove everything.

Best,
tortoisedoc
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Updated emulator in SailfishOS SDK available

[Jarko Vihriala]

Hello again,

The nasty bad hash issue hit us as our service cloud did not update all files. 
We fixed that and improved process there so it should not hit us again.

Sorry for the inconvenience ; updates should be fully operational now.

by the way, if use IRC we can be reached from #sailfishos on FreeNode.

thanks, Jarko


From: Jarko Vihriala
Sent: Wednesday, October 30, 2013 12:03 PM
To: devel@lists.sailfishos.org
Subject: Updated emulator in SailfishOS SDK available

Hello again,

Like it was disclosed earlier, the SailfishOS Emulator had a bug that it would 
not refresh its package repositories. If you were required to install new 
packages to it, it would eventually fail on RPM deployment.
Now there is a fixed version available. We have uploaded an updated emulator to 
the SDK repository. The new emulator bears the label '2013.10.28-0' and the old 
one was '2013.10.18-0'.

As always you should shut down all VMs before starting the update.

This means that your Qt Creator should pick up the update and you should see 
'Updates' icon in Qt Creator's ui, here's how to proceed with update:
1. click update icon (or run updater from toolbar), sdk maintenance tool will 
open
2. sdk maintenance tool should be set up already for the update action, click 
next.
3. you should see that the current emulator version is 2013.10.18-0 and it's 
going to be updated, click next
4. click update to proceed. sdk maintenance tool downloads the new emulator and 
installs it.
5. once it's completed, click finish. You now have the new emulator installed.

Here's the release note for this update:
SailfishOS Emulator:
* when emulator boots, it refreshes its package repositories with pkcon refresh 
and thus is then capable to retrieve package dependencies from sailfishos.org.
Any other component:
* no changes.

If you encounter any issues, please report them to Sailfish developers mailing 
list at devel@lists.sailfishos.org
Happy hacking!

Best regards,
Jolla Sailfish SDK Team
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Updated emulator in SailfishOS SDK available

[Jarko Vihriala]

Are you updating from 1310 or from older alpha? If you do it from older alpha 
SDK you need to update it all the way. 
Can you please tell what is your development computer as well (mac,linux 32bit, 
linux 64bit or windows) ?

thanks, Jarko

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Kaj-Michael Lang [mil...@tal.org]
Sent: Wednesday, October 30, 2013 1:52 PM
To: devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] Updated emulator in SailfishOS SDK available

On Wed, 2013-10-30 at 10:03 +, Jarko Vihriala wrote:
> 1. click update icon (or run updater from toolbar), sdk maintenance
> tool will open
> 2. sdk maintenance tool should be set up already for the update
> action, click next.

I'm having problems with the updater, it complains "Could not download
meta information for component: org.merproject.documentation. Error: Bad
hash."

--
Kaj-Michael Lang 

___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list

[SailfishDevel] Updated emulator in SailfishOS SDK available

[Jarko Vihriala]

Hello again,

Like it was disclosed earlier, the SailfishOS Emulator had a bug that it would 
not refresh its package repositories. If you were required to install new 
packages to it, it would eventually fail on RPM deployment.
Now there is a fixed version available. We have uploaded an updated emulator to 
the SDK repository. The new emulator bears the label '2013.10.28-0' and the old 
one was '2013.10.18-0'.

As always you should shut down all VMs before starting the update.

This means that your Qt Creator should pick up the update and you should see 
'Updates' icon in Qt Creator's ui, here's how to proceed with update:
1. click update icon (or run updater from toolbar), sdk maintenance tool will 
open
2. sdk maintenance tool should be set up already for the update action, click 
next.
3. you should see that the current emulator version is 2013.10.18-0 and it's 
going to be updated, click next
4. click update to proceed. sdk maintenance tool downloads the new emulator and 
installs it.
5. once it's completed, click finish. You now have the new emulator installed.

Here's the release note for this update:
SailfishOS Emulator:
* when emulator boots, it refreshes its package repositories with pkcon refresh 
and thus is then capable to retrieve package dependencies from sailfishos.org.
Any other component:
* no changes.

If you encounter any issues, please report them to Sailfish developers mailing 
list at devel@lists.sailfishos.org
Happy hacking!

Best regards,
Jolla Sailfish SDK Team
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Installing packages to the SDK and Emulator via the rpm/yaml file

[Jarko Vihriala]

Hello Chrispher, I'll inline some comments with "JV:"

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of christopher.l...@thurweb.ch [christopher.l...@thurweb.ch]
Sent: Monday, October 28, 2013 11:32 PM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Installing packages to the SDK and Emulator via the
rpm/yaml file

Hi all

Until recently when I needed extra packages on the SDK and Emulator
installed using the SDK Control Center (for the SDK) and zypper (for
the Emulator).

However from previous posts in this forum I gathered that it was also
possible to do the same using an app's yaml and spec files, both of
which are in the rpm directory.

I have had some success at getting this to work by trial and error,
but don't yet fully understand it.  The process is quite possibly well
documented somewhere, but if so, I have not yet succeeded in finding
the docus!

it is also possible that the whole thing is blinding obviously, and it
will suddenly go click ?.

So far I have established that:

1) The yaml / spec install process only works with "Deploy as RPM"

JV:Yes, this is correct. All dedendecies that application has, must be 
installed to device via rpm packaging. You should never assume that there is 
something there, because one day it might be changed or removed. But if your 
rpm spec has the right stuff in, you can be sure that if it buids, it's very 
likely to install and run as well.

2) The spec file is auto-generated based on the yaml file, so it is
the yaml file that we should be configuring. (the yaml file refers to
the format rather than what it does).

JV:Correct again. In our SDK there is a Yaml editor for making the things easy. 
Spec gets generated from Yaml. Spec itself has sections that are safe to tune. 
If you write stuff _outside_ those areas (marked with >> and <<) and modify 
yaml -> changes in spec are lost.

3) Within the yaml file there are 3 sections to which packages may be
added: PkgConfigBR:,  PkgBR:, and Requires:

JV:PkgConfigBR and PkgBR do the same, but PkgConfigBR queries the real name 
from pkg-config. They both install what is needed to compile and link the 
application, i.e. build it. (BR = BuildRequires).

4) Requires: installs "stuff" to the Emulator.

JV:Correct, Requires: is a run-time dependencylist.

5) I think that PkgConfigBR: and PkBR: install things to the SDK, but
I have not worked out the difference. However the format of the
package names these two sections accept is different.

Then there is the question of exactly which package belongs where.
There are xxx-devel packages which I guess belong on the SDK, but not
on the Emulator; and qt5-declarative--xxx packages for QML which I
think are required on both. Not to mention the debug packages ?.

JV: xxx-devel packages go only to the build environment, never to the target 
itself.

It would be fantastic if someone who understands this well could
explain, perhaps with an example. Let's say we want to use the
QtPositioning 5.x functionality and will be using the QML elements.
What should be where in the app.yaml file?

JV: I'll take that up in upcoming SDK documentation works, we can improve 
there, thanks for the heads up.

thanks in advance

Chris


___
SailfishOS.org Devel mailing list

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] rpm repositories in emulator are not refreshed in latest SDK

[Jarko Vihriala]

I think it's same issue. Zypper/PackageKit shows only the stuff that is locally 
available. With new emulator this is fixed so that repositories are refreshed 
automatically and there should be no problems.

thanks, Jarko


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of christopher.l...@thurweb.ch [christopher.l...@thurweb.ch]
Sent: Saturday, October 26, 2013 7:11 PM
To: Jarko Vihriala
Cc: devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] rpm repositories in emulator are not   
refreshed   in latest SDK

Hi Jarko

I don't know if this is related (but it sounds like it ...)

On first using zypper after the update, it only showed installed
packages (as opposed to all those available). zypper refresh cured it

Chris

Zitat von "Jarko Vihriala" :

> Hello all,
>
> We discovered that PackageKit that is used in our emulator does not
> automatically refresh repositories so if your rpmbuild requires
> additional stuff to be pulled to emulator - it will eventually fail.
> <https://connect.emailsrvr.com/owa/?ae=Item&a=New&t=IPM.Note&cc=MTQuMy4xNTguMSxlbi1VUyw0Mjk0OTY3Mjk1LEhUTUwsMCww&pspid=_1382779855830_872310806#>
>
> Good news is that quickfix is in the works and should be out next
> week. But before that is applicable this workaround needs to be done:
> 1. login to emulator (best is to press ctrl- on emulator's
> window to get login prompt) as root. On my ubuntu f2 seems to cut it.
> 2. refresh repos with 'pkcon refresh'
> optionally then:
> 3. test that repos got refreshed (do f.ex 'pkcon search
> sensorfw-qt5-devel') if you see stuff like 'Available..' then your
> emulator has updated lists and you're good to go. If not - run 2)
> again.
>
> Sorry for the extra trouble, we'll publish new emulator soon and it
> is delivered via SDK update (you'll get notice in Qt Creator's UI on
> that).
>
> thanks, Jarko
>
>



___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list

[SailfishDevel] rpm repositories in emulator are not refreshed in latest SDK

[Jarko Vihriala]

Hello all,

We discovered that PackageKit that is used in our emulator does not 
automatically refresh repositories so if your rpmbuild requires additional 
stuff to be pulled to emulator - it will eventually fail.


Good news is that quickfix is in the works and should be out next week. But 
before that is applicable this workaround needs to be done:
1. login to emulator (best is to press ctrl- on emulator's window to 
get login prompt) as root. On my ubuntu f2 seems to cut it.
2. refresh repos with 'pkcon refresh'
optionally then:
3. test that repos got refreshed (do f.ex 'pkcon search sensorfw-qt5-devel') if 
you see stuff like 'Available..' then your emulator has updated lists and 
you're good to go. If not - run 2) again.

Sorry for the extra trouble, we'll publish new emulator soon and it is 
delivered via SDK update (you'll get notice in Qt Creator's UI on that).

thanks, Jarko

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] SailfishOS SDK update available today: Changes to SSH security?

[Jarko Vihriala]

Hello,
Emulator changed a bit and the 'nemo' password is not default nemo anymore - I 
cannot even say it here as its generated per device.
However, to access emulator you can do:
ssh -p 2223 -i ~/SailfishOS/vmshare/ssh/private_keys/1/root root@localhost

or 

ssh -p 2223 -i ~/SailfishOS/vmshare/ssh/private_keys/1/nemo nemo@localhost

On Windows it's equivalent, but you need to find a)SSH tool b)use Windows paths 
to locate keys etc. On MobaXTerm/Cygwin it's similar to real ssh command line 
but on Putty you need to work it to use right key etc - and currently I don't 
have Windows PC to try it out :/

thanks, Jarko 


From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of christopher.l...@thurweb.ch [christopher.l...@thurweb.ch]
Sent: Friday, October 25, 2013 9:10 AM
To: Jarko Vihriala
Cc: devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] SailfishOS SDK update available today: Changes 
to SSH security?

Hi Jarko

When I SSH into the Emulator as user nemo using a rsa key, I am now
asked for a password (memo). I am sure this was not the case prior to
the update. Has the security changed?

The same applies to the user root - for which I don't know the
password. But I guess we should be doing everything (e.g. zypper) as
memo?

SSHing to the SDK Build Engine VM using the existing key (or with
password) does not work at all, I get Permission denied (publickey).

Chris


___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] SSH after update : IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Error

[Jarko Vihriala]

Thanks for the tip, we might amend it to known issues later on.

This happens because host uid changes and ssh still assumes it to be the old 
one. In ubuntu/debianish systems you get additional helper line for ssh-keygen 
but on Fedora you don't. UID for any VMs is unique and is created when the VM 
boots up the first time.

The 'workaround' is to put the known hosts point to /dev/null so you don't get 
those warnings anymore but that renders rest of your ssh setup to kind of 
unsafe state so I would not recommend doing it.

thanks, Jarko


From: christopher.l...@thurweb.ch [christopher.l...@thurweb.ch]
Sent: Friday, October 25, 2013 8:59 AM
To: devel@lists.sailfishos.org
Cc: Jarko Vihriala
Subject: SSH after update : IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING  
NASTY! Error

Hi All

If, after the SDK update, you get the following errors when SSHing to
the Emulator or SDK VMs read on.

apple-pip:abstractui christopherlamb$ ssh -p 2223  -i
~/.ssh/mer-qt-creator-rsa  nemo@localhost

@@@
@WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
83:7e:fe:55:2a:dc:22:e7:69:dc:fb:6c:a3:bd:5c:2d.
Please contact your system administrator.
Add correct host key in /Users/christopherlamb/.ssh/known_hosts to get
rid of this message.
Offending RSA key in /Users/christopherlamb/.ssh/known_hosts:8
RSA host key for [localhost]:2223 has changed and you have requested
strict checking.
Host key verification failed.
apple-pip:abstractui christopherlamb$ zypper se
-bash: zypper: command not found

The solution is very easy, but it is one of those that always has me
for scratching my head for a few minutes trying to remember how I last
did this:

Find the know_hosts file in ./ssh

Make a back up copy of the file

 From the original, remove the two entries starting with:

[localhost]:2223

[localhost]:

Happy hacking

Chris

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Problems porting our game to Sailfish - welcome any advice

[Jarko Vihriala]

Without deeper traces from emulator it's hard to say where it goes wrong. 
However, the white screen in startup usually tells that QML parsing is broken 
somewhere. If you look at traces from emulator (as root: journalctl -f) you 
should see reference to broken qml in that situation.

thanks,Jarko

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Duncan Waugh [duncan_wa...@hotmail.co.uk]
Sent: Thursday, October 24, 2013 5:20 PM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Problems porting our game to Sailfish - welcome any
advice

Hello everyone,

I've started work porting our Qt-based game from Symbian over to Sailfish and 
I'm hitting a pretty major roadblock at the moment. It looks like I haven't set 
something up in the graphics system properly and would be very grateful for any 
help that anyone can provide.

A brief outline:
* The application uses the QGraphicsView framework. We set up the QGraphicsView 
object once at the start of the game and then replace the QGraphicsScene object 
at various points as the user moves through the application.
* We have overriden the drawForeground() method within the QGraphicsScene 
objects and manually pass the QPainter object that we receive to the various 
elements of the UI, which use it to draw to the screen.
* The QGraphicsView object is set not to update itself.  We have a timer in a 
manager class, which fires 60 times a second, from where we manually call 
repaint() on the QGraphicsView object.

Current state:
* All code has been tidied up to build under Qt5 and non-Sailfish components, 
such as Phonon, are currently #ifdeffed out.
* On execution the game runs and moves through a couple of QGraphicsScenes, but 
only ever displays a white screen.  The calls to QGraphicsView::repaint() are 
ignored and the QDisplayScenes only have their drawForeground() methods called 
once, directly after instantiation.  Why we only get a white screen I'm also 
not sure.  This is all on the latest emulator.

An excerpt from the log is shown below with basic class hierarchy:
DisplayScene ->- QGraphicsScene
BootupScene ->- DisplayScene
TitleMenuScene ->- DisplayScene

0:Using Wayland-EGL
1:libpng warning: Malformed iTXt chunk
2:
3:calling QGraphicsView::SetScene()
4:DisplayScene::drawForeground  QRectF(1,1 538x958)
5:BootupScene::UpdateNotification  52
6:>>GameManager::FrameTimerTick - repaint
7:<>GameManager::FrameTimerTick - repaint
10:   <>GameManager::FrameTimerTick - repaint
15:   <>GameManager::FrameTimerTick - repaint
19:   <>GameManager::FrameTimerTick - repaint
23:   TitleMenuScene::drawForeground
24:   DisplayScene::drawForeground  QRectF(1,1 538x958)
25:   <>GameManager::FrameTimerTick - repaint
27:   <>GameManager::FrameTimerTick - repaint
32:   User requested stop. Shutting down...
33- QApplication

0:int main(int argc, char *argv[])
1:{
2:MyApplication a(argc, argv);
3:
4:QWidget* screen = QApplication::desktop()->screen();
5:GameManager w(screen->width(), screen->height(), a);
6:return a.exec();
7:}

I based the Sailfish installation files off of the sample application, it's 
possible I made an error here.
Yaml:

0:Name: PuzzleStones
1:Summary: My SailfishOS Application
2:Version: 0.1
3:Release: 1
4:Group: Qt/Qt
5:License: LICENSE
6:Sources:
7:- '%{name}-%{version}.tar.bz2'
8:Description: |
9:  Short description of my SailfishOS Application
10:   Configure: none
11:   Builder: qtc5
12:   PkgConfigBR:
13:   - sailfishapp
14:   - Qt5Quick
15:   - Qt5Qml
16:   - Qt5Core
17:   Requires:
18:   - sailfishsilica-qt5
19:   Files:
20:   - '%{_bindir}'
21:   - '%{_datadir}/%{name}/qml'
22:   - '%{_datadir}/applications/%{name}.desktop'
23:   - '%{_datadir}/icons/hicolor/90x90/apps/%{name}.png'
24:   - /usr/bin
25:   - /usr/share/PuzzleStones
26:   - /usr/share/applications
27:   - /usr/share/icons/hicolor/90x90/apps

Spec:

0:#
1:# Do NOT Edit the Auto-generated Part!
2:# Generated by: spectacle version 0.27
3:#
4:
5:Name:   PuzzleStones
6:
7:# >> macros
8:# << macros
9:
10:   %{!?qtc_qmake:%define qtc_qmake %qmake}
11:   %{!?qtc_qmake5:%define qtc_qmake5 %qmake5}
12:   %{!?qtc_make:%define qtc_make make}
13:   %{?qtc_builddir:%define _builddir %qtc_builddir}
14:   Summary:My SailfishOS Application
15:   Version:0.1
16:   Release:1
17:   Group:  Qt/Qt
18:   License:LICENSE
19:   Source0:%{name}-%{version}.tar.bz2
20:   Source100:  PuzzleStones.yaml
21:   Requires:   sailfishsilica-qt5
22:   BuildRequires:  pkgconfig(sailfishapp)
23:   BuildRequires:  pkgconfig(Qt5Quick)
24:   BuildRequires:  pkgconfig(Qt5Qml)
25:  

Re: [SailfishDevel] DeclarativeGlassImageProvider

[Jarko Vihriala]

Hi,
In Qt5 version of Silica there is no DeclarativeGlassImageProvider item as 
such, the current item names of Silica can be found from plugins.qmltypes of 
Silica in /usr/lib/qt5/qml/Sailfish/Silica. With quick look closest matching to 
your request would be DeclarativeGlassItem.

All in all, if you have Qt4 based application done with Alpha SDK, it should be 
ported to Qt5 using Alpha-Qt5 SDK as almost everything below the APIs 
themselves have changed. 

thanks, Jarko

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Tero Siironen [tero.siiro...@iki.fi]
Sent: Thursday, October 24, 2013 1:38 PM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] DeclarativeGlassImageProvider

Hi,

I've used glass background for my app successfully in the first alpha
sdk, but since the second alpha sdk, DeclarativeGlassImageProvider hasn't 
worked.

Whatever I try to set to source of image element I get error similar to this:

QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
DeclarativeGlassImageProvider::requestImage(): source image "" is not available.
qrc:/qml/Silica/AlbumContentPage.qml:66:5: QML Image: Failed to get image from 
provider: image://glass//home/nemo/.cache/cuteremote/album/127.png

The code is here:
Image {
id: backgroundImage
source: "image://glass/" + __artFileName
sourceSize { width: parent.width; height: parent.height }
}

where __artFileName changes to correct path 
(/home/nemo/.cache/cuteremote/album/127.png, file does exists)

Is the DeclarativeGlassImageProvider still supported, has the API changed or is 
it just broken?


--
Tero
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] SailfishOS SDK update available today.

[Jarko Vihriala]

Thank you!
Nice to hear all went ok.

Kind of stating the obvious here but MerSDK UI was made optional on this 
update. If you want to see it, feel free to enable it from Tools->Options->Mer, 
just tick the 'Headless' option off.

thanks, Jarko

From: christopher.l...@thurweb.ch [christopher.l...@thurweb.ch]
Sent: Tuesday, October 22, 2013 7:34 PM
To: Jarko Vihriala
Cc: devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] SailfishOS SDK update available today.

HI Jarko

Good work, the latest update installs faultlessly on OSX.

The only thing that caught me out (so far) is that the SDK VM runs
without a GUI - but that is in the small print of your instructions ...


Chris


___
SailfishOS.org Devel mailing list

[SailfishDevel] SailfishOS SDK update available today.

[Jarko Vihriala]

Hello again,

Today 13:00 UTC we will publish new installers and repositories for our 
SailfishOS SDK, Alpha-Qt5-update2 to be exact.
If you have Alpha-Qt5 you should see updates available icon in Qt Creator. If 
you don't have SailfishOS SDK installed, you can get the latest installers from 
www.sailfishos.org.

This update is a major step before the launch of the Jolla device as it brings 
ARM package building to developers.

A couple of things you should be aware of:
-  In this update the build engine, emulator and targets are re-installed so 
you will lose any changes you may have made in those - however, if your 
application packaging is done correctly, rebuilding your projects should 
reinstall the packages you have been using.
- All customizations done to SDK (adding new zypper repositories, adding custom 
targets, additional source paths) will be removed during installation process 
so make your own backup of those before starting the update.
- If you import existing project made with a previous version of the SailfishOS 
SDK, make  sure you select the correct kit in project configuration step. Both 
ARM and i486 kits will now be available.
- Windows users need to install VC10 runtime from 
http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328 or Installer 
will ask for admin rights during installation.
- For more information, please see SDK Alpha-Qt5 known issues list at: 
https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues

Update itself is performed like the previous one using SDK Maintenance tool 
with three following steps:
1. maintenance tool itself is updated first. In SailfishOS SDK IDE click on 
help->start updater->next->next->Update
2. maintenance tool needs to restarted to update the rest of the SDK, click 
Restart on the UI.
3. once updater has restarted, it asks for the next action, just click Next to 
proceed ('Update components' is selected by default). Updater lists all the 
items that are being updated, click Next->Update to proceed.

Here's the release note for this update:

SailfishOS SDK IDE:
* Qt Creator updated to 2.8.1 version.
* Building RPM packages for ARM target is introduced. This is done by selecting 
ARM kit and running deployment. Deployment to real ARM devices is not supported 
yet.
* MerSDK VM starts without UI (if MerSDK is to be accessed, UI can be activated 
from tools->options->mer menu)
* If MerSDK VM is running when Qt Creator is shut down - a prompt is displayed 
to close it.
* QML profiling is enabled.

Templates/examples:
* SailfishOS application template is updated. The current template does not 
have so-called boilerplate and is easier to use.
* SailfishOS application examples are updated to build with the latest template.

SDK Maintenance Tool:
* Whole installer framework is based on version 1.4.
* bug fixes, no new functionality.

Documentation:
* Documentations are updated with latest available versions.

Build Engine:
* Support for ARM target introduced
* Support to deploy to emulator using PackageKit
* Lots of fixes to build toolchain.

SailfishOS Emulator:
* Emulator is built from updated Jolla baseline.
* QML profiling support introduced.
* Bug in QML debugging fixed.
* Emulator screen size matches the upcoming Jolla phone.
* Application icon texts are displayed when application grid is pushed up.

SailfishOS Target(s):
* ARM target introduced.
* Both i486 and ARM target builds done on updated Jolla baseline.

If you encounter any issues, please report them to Sailfish developers mailing 
list at devel@lists.sailfishos.org

Happy hacking!

Best regards,
Jolla Sailfish SDK Team
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Managing screen resolution

[Jarko Vihriala]

Hello,
This resolution is updated to match real device and this change is delivered in 
next SDK update. This SDK update is already undergoing tests so we should be 
able to release it soon. 

In general apps should not use fixed values of device screen but use relative 
bindings.

thanks, Jarko

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Seppo Tiainen [seppo.tiai...@gmail.com]
Sent: Friday, October 11, 2013 7:29 AM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Managing screen resolution

The SailfishOS SDK (Qt5 Alpha) assumes a screen resolution of 854 × 480 which 
is the same as on N9. It seems, however, the first Jolla device will have a 960 
× 540 pixel display. How should one prepare for that? I have understood that 
the current advice is to use 16:9 aspect ratio and no hard-coding in number of 
pixels.

But if you are porting an app that has been hard-coded for N9 screen size, what 
is the best approach?

1) Will there be a global parameter to fix the 'magnification'? (would be 
great!)
2) Is there any other way to fix the resolution easily?
3) Should the whole app UI be redesigned? (would be a lot of work...)

Seppo
___
SailfishOS.org Devel mailing list

[SailfishDevel] Changelog for : Update for SailfishOS SDK

[Jarko Vihriala]

Hello again,

First, sorry for not being able to deliver this list when we pushed out
the update.
But here it is. This will be available on sailfishos.org's wiki soon too.

SailfishOS SDK IDE
==
* 'Copy Project to writable Location?' dialog added when compiling examples
* Detecting right platform when compiling examples
* Multiple kits creation fixed when adding targets
* Rsync deployment of examples fixed
* Do not overwrite devices.xml if it's edited whileQtCreator is running

Templates/examples:
===
* Application template deployment errors fixed
* Updated component gallery example code

SDK Maintenance Tool:
=
* SDK Updater fixes for OS X

Documentation
=
* Documentation updates after revision change

Build Engine
 
* Fixes for build toolchain
* Fixes for SDK Control Center
(datailed info & exact package list can be found on SDK Control Center
before updating)

SailfishOS Emulator
===
* No changes

SailfishOS Target
=
* No changes


Best regards,
Jolla Sailfish SDK Team




On 09/18/2013 01:56 PM, Jarko Vihriala wrote:
> Hello all!
>
> We have now uploaded a minor update of Sailfish SDK, which will update
> your SailfishOS SDK IDE (based on QtCreator), fix some issues in
> examples, update documentation and bring updates to your SDK Build Engine. 
>
> We didn't change much and in fact this is paving way to a bigger update
> coming soonish and making sure everything on the update flow works ok.
>
> Updating is simple. In SailfishOS SDK IDE click on help->start updater
> and it will tell you if it found updates. Updating the Build engine is
> even simpler;five minutes after it has booted up, check theUpdates tab
> on the SDK Control Center (behind theSailfishOS icon in SailfishOS SDK
> IDE). A message "Engine updates available" will pop up-you can start the
> updatefrom there.
>
> If you encounter anyissues, please report them to Sailfish developers
> mailing list at devel@lists.sailfishos.org
>
> Happy hacking!
>
> Best regards,
> Jolla Sailfish SDK team
>
> ___
> SailfishOS.org Devel mailing list
>

___
SailfishOS.org Devel mailing list

[SailfishDevel] Update for SailfishOS SDK available

[Jarko Vihriala]

Hello all!

We have now uploaded a minor update of Sailfish SDK, which will update
your SailfishOS SDK IDE (based on QtCreator), fix some issues in
examples, update documentation and bring updates to your SDK Build Engine. 

We didn't change much and in fact this is paving way to a bigger update
coming soonish and making sure everything on the update flow works ok.

Updating is simple. In SailfishOS SDK IDE click on help->start updater
and it will tell you if it found updates. Updating the Build engine is
even simpler;five minutes after it has booted up, check theUpdates tab
on the SDK Control Center (behind theSailfishOS icon in SailfishOS SDK
IDE). A message "Engine updates available" will pop up-you can start the
updatefrom there.

If you encounter anyissues, please report them to Sailfish developers
mailing list at devel@lists.sailfishos.org

Happy hacking!

Best regards,
Jolla Sailfish SDK team

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] SDK without VirtualBox

[Jarko Vihriala]

Hello,

Yes, it's exactly like Lucien wrote. QtC in SailfishOS SDK assumes there is a 
VBox named 'MerSDK' and uses VBox control APIs to run start/stop an monitor it. 
'MerSDK' VBox does not exist, you cannot build and deploy from QtCreator.

HOWEVER

if you want to experiment stuff on your own you need to unzip relevant parts of 
the target rootfs to ~/SailfishOS/mersdk/targets/ and QtCreator should 
give you the needed autocompletion. In this scenario you don't necessarily need 
a VM at all (in Linux) but all compilation & deployment steps you need to do 
manually on command line. I know some people run SDK like that but it's totally 
on the wild frontier - good luck and please take time to document the steps.

thanks, Jarko

On 09/16/2013 01:54 PM, Lucien XU wrote:

Hello !



It is technically possible to use other virtualization software, but it is not 
supported. The installer checks if VBox is installed because it needs to 
configure VBox to add the new virtual machines.



If you want, you can try with other virtualization softwares, but you have to 
install virtualbox to complete the installation, then remove it and play with 
the vdis and settings.



Good luck with it, and if you succeded in using (eg) KVM, please do a blog post 
or a wiki post (assuming SailfishOS.org wiki is writeable, but I'm not sure 
about it anymore) about how you managed to do it.



Cheers,

Lucien



Le lundi 16 septembre 2013 12:39:56 Pali Rohár a écrit :

> Hello,

>

> I tried to install SDK on linux, but it show me this error:

>

> You need a working VirtualBox installation. Please download it

> from www.virtualbox.org, install it and then rerun 
> this

> installer.

>

> Why it is not possible to use any other virtualization software

> (e.g. KVM)? I think that VirtualBox is needed only for running

> x86 disk image (where is build env). If this is true, than using

> any other virtualization tool can be possible. But now installer

> refuse to do anything if VirtualBox is missing in system (even

> unpack data from installer).

>

> --

> Pali Rohár

> pali.ro...@gmail.com

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Sailfish OS on Nokia N950

[Jarko Vihriala]

Hello,

Ahmed, in addition if the emulator lacks some features specific to your 
application, please reply to this mailing list and we'll see if we can improve 
it (emulator) on SDK on that issue.

thanks, Jarko

On 09/16/2013 01:07 PM, Michael Faro-Tusino wrote:
Hi Ahmed,

For starters, there currently is no way to install Sailfish on ARM-based 
devices (N9, N950, N900 etc.), unless you are inside Jolla and have internal 
firmware - clearly not an option for us. It may be available in the future, but 
I don't have a crystal ball.

Secondly, N950 does not have NFC technology, and as such, your app would run 
the same as it would in the Emulator. You would need to test your app on an N9. 
Though, refer to my first point.

Advice would be test what you can using the emulator, and when the Jolla Device 
is released (or a Sailfish build for the N9) then you can test the NFC 
functionality.

BR,
Michael

-
Michael Faro-Tusino
Twitter: @MFaroTusino
[X]



From: ahmed...@hotmail.com
To: devel@lists.sailfishos.org
Date: Mon, 16 Sep 2013 10:59:29 +0200
Subject: [SailfishDevel] Sailfish OS on Nokia N950

hi Devs
How i can run Sailfish OS on my Nokia N950 to test my NFC APP

with Love
Ahmed Ghattas



___ SailfishOS.org Devel mailing 
list

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Wrong Qt version in package manager description?

[Jarko Vihriala]

Hello all,

Yes, Robin is right. We took the SDK snapshot from internal devel some
time ago just to make sure it's stable and we had time to hone features
we planned to release in good shape.

Qt5 version among other things will upgrade as new updates to SDK are
being pushed out.

We have not disclosed strategy how often we make updates but I can
assure that it's more rapid than 1-2 a year, if fact we plan to release
as often we can. The upgrade mechanisms used allow us to have rolling
updates on engine, target and emulator. If changes are needed to QtC and
ifw we'll upgrade them using SDKMaintenancetool's interface.

thanks, Jarko

On 08/02/2013 09:48 AM, Robin Burchell wrote:
> Hi,
>
> On 2. aug. 2013, at 02:24, Ketil Kvifte  wrote:
>> Have you been working too fast? To me it looks like the package manager
>> think it have Qt-5.0.2 installed, while the libraries themselves say
>> they come from the Qt-5.1.0 release.
> At the time the SDK was snapshotted, Qt 5.1 had not yet been released, so we 
> couldn't exactly call the packages 5.1. Now that 5.1 is out "for real", we're 
> also following 5.1 internally:
>
> [root@localhost ~]# rpm -q qt5-qtcore
> qt5-qtcore-5.1.0+git3-1.8.2.armv7hl
>
> I'd imagine this will find its way into the first SDK update.
>
> BR,
>
> Robin
> ___
> SailfishOS.org Devel mailing list
>

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Sailfish Beta SDK with Qt5

[Jarko Vihriala]

Hello,
The official message in Dev Days was "This summer" and I can tell you it's soon 
ready to ship!

thanks, Jarko (SDK PM)

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of FIlip Kłębczyk [fklebc...@gmail.com]
Sent: Monday, July 15, 2013 8:18 AM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Sailfish Beta SDK with Qt5

Now that we already have learned about some key changes in Sailfish OS
the question is when the new SDK will be publicly available?
It's quite obvious for me that in current situation the one available on
the website has already become in large part obsolete.

Best regards,
Filip
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] 无法发布到手机

[Jarko Vihriala]

Yes this is a known issue and we're working on it. The build "flow" 
would be

0. Launch Sailfish OS IDE
1. run the app wizard (or create empty project)
2. click 'Play'
3. accept dialog of Build VM not running
4. again click 'Play'
5. accept dialog of Emulator VM not running
6. and then finally click Play.

-> App should run in emulator. If you encounter problems make sure you 
have correct version on VirtualBox installed (4.2 or newer is recommened).


If the VM is not started by Qt Creator it might not recognize them 
running (it should though -> report a bug in VirtualBox's APIs..) so 
shutting them down in that case might help.


thanks, Jarko

On 06/06/2013 07:29 PM, z...@ovi.com wrote:

Hi,

Probably the SailfishOS Emulator is currently not running, because the 
error is saying:


*16:47:22: Virtual Machine 'SailfishOS Emulator' is not running!*

So, you need to check it first and make sure it is running.
1, If no, you should start it. by either click the "Start Emulator" 
button on the bottom left of SailfishOS IDE(qt-creator) or start it 
via VirtualBox manually.


2, If yes, maybe you can stop it and click that button to restart it, 
then try to deploy again. (not sure if it will work, just guessed).


Good luck!

Br,
zhxt


--- On *Wed, 6/5/13, 汪福东 //* wrote:


From: 汪福东 
Subject: [SailfishDevel] 无法发布到手机
To: devel@lists.sailfishos.org
Date: Wednesday, June 5, 2013, 4:48 PM

16:47:22: Checking whether to start Emulator...

*16:47:22: Virtual Machine 'SailfishOS Emulator' is not running!*

*16:47:25: **部署步骤失败。*

Error while building/deploying project FF (kit:
MerSDK-SailfishOS-i486-x86)

当 执行步骤'Start Emulator, if necessary'时


-Inline Attachment Follows-

___
SailfishOS.org Devel mailing list



___
SailfishOS.org Devel mailing list



--
We are #unlike.
Jolla Oy, http://www.jolla.com

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] R: R: change resolution of the emulator?

[Jarko Vihriala]

And do notice if you change resolution with VBoxManage some of the apps 
on ui might not act accordingly, so if f.ex width of an app is fixed to 
some value, it does not get altered. So our advice is not to tweak the 
resolution.


On 06/06/2013 02:28 PM, David Greaves wrote:

The SailfishOS Emulator resolution itself can't reasonably be changed.

However you can enable 'scale mode' in virtualbox to allow it to fit onto a
smaller laptop display for example. 'Host + C' key in View menu should do it.

David


On 06/06/13 08:18, wsvries wrote:

SailfishOS Emulator.vbox (changing this cripples the emulator!):
  
This is FWVGA and not any HD!
Even with qHD (540x960) I need to change the resolution of the emulator...
Any hints?


Garret Raziel schreef op 2013-06-05 16:20:

I still hope that they are not willing to tell it, because they are
negotiating... I personally hope for HD resolution :-).

On Wed, Jun 5, 2013 at 3:54 PM,  wrote:


Which is the most likely solution it seems, at least from the info we got at
jolla love day

DA: Garret Raziel
INVIATO: mercoledì 5 giugno 2013 15:53
A: Michael Faro-Tusino
CC: and.berna...@gmail.com; devel@lists.sailfishos.org
OGGETTO: Re: [SailfishDevel] R: change resolution of the emulator?

This may even mean qHD, one quarter of HD resolution...

On Wed, Jun 5, 2013 at 3:45 PM, Michael Faro-Tusino 
wrote:


It was in a video from Engadget that went hands on with Marc Dillon and he
said it will be one of the HD resolutions.

Sent from my Z10

-
From: and.berna...@gmail.com
Sent: 5/06/2013 11:37 PM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] R:  change resolution of the emulator?

Where did you the jolla has HD resolution?
Really, do not give that for granted ;)

DA: Wim de Vries
INVIATO: mercoledì 5 giugno 2013 14:50
A: devel@lists.sailfishos.org
OGGETTO: [SailfishDevel] change resolution of the emulator?

Hi,
I want to change the screen resolution to at least the lowest HD
(720x1280), since the Jolla phone would be HD...
I am not very virtualbox knowledgeable, but what I can digest from
googling a lot, is that the target OS has to set the resolution. So,
that would be in Sailfish itself.
Any ideas how to do that? Or is this not yet feasible in the alpha?
Thanks.
___
SailfishOS.org Devel mailing list

___
SailfishOS.org Devel mailing list

___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list

___
SailfishOS.org Devel mailing list

___
SailfishOS.org Devel mailing list



--
We are #unlike.
Jolla Oy, http://www.jolla.com

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Creating daemons

[Jarko Vihriala]

I don't know if this is the best way but I've done it so:

1. "Daemon" is basically a QCoreApplication which has dbus-interface
2. It's invoked by sending first dbus message to it (I use session for this)
3. It does not have systemd dependecy so it needs to take care of it's 
own living. I use a ShMem block so I need to make sure that block is 
available when this daemon wakes up

4. UI application is just a QML/C++ app that has interface to dbus

In a nutshell you need
1. app based on QCoreApplication
2. dbus service and interface definition
3. take care of the "daemon's" lifecycle

thanks, Jarko

On 05/07/2013 10:56 PM, David Greaves wrote:

On 07/05/13 19:37, Shantanu Tushar Jha wrote:

Hi,

I'm trying to run one of my harmattan apps using Sailfish SDK. My app consists
of a daemon and a UI app which communicate with each other. I couldn't find any
info on how to create daemons on Sailfish/nemo. Any pointers?

In general daemons are run using systemd. We use systemd user sessions.

This typically makes writing a daemon easier as it does not need to worry about
forking or respawning.

Lots of detail here:
   http://www.freedesktop.org/software/systemd/man/daemon.html

David

___
SailfishOS.org Devel mailing list



--
We are #unlike.
Jolla Oy, http://www.jolla.com

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Sailfish OS Emulator and Windows 8

[Jarko Vihriala]

Hello,
We don't officially support Windows8 on the alpha SDK but it's in the 
works. In general the Emulator VM depends on the characteristics of the 
VirtualBox setup on the host. Do you have enough RAM, do you have 
VirtualBox 4.2 or newer (I think we officially support 4.1 onwards tho).


When the emulator freezes, can you still ssh into it (i.e. using cygwin 
or equivalent : ssh -i ~/.ssh/mer-qt-creator-rsa -p 2223 root@localhost) ?


thanks, Jarko

On 05/01/2013 09:50 PM, Michal Prevratil wrote:

Hi,
I would like to ask if anybody got to work Sailfish SDK with Windows 
8? I am asking because of my problems with emulator. After booting up 
it seems like freezed (tried Host + H, not working) but sometimes it 
boots up normally and works ok. Is there any workaround?


Thank you
Michal



___
SailfishOS.org Devel mailing list



--
We are #unlike.
Jolla Oy, http://www.jolla.com

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] developer on windows

[Jarko Vihriala]

Hi,
Upcoming releases will support building of apps outside user's home directory. 
This Alpha SDK release relies on assumption that SDK VM is accessed through 
mounts done directories under user's home directory.

thanks, Jarko



From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Daniel Gomes [dgo...@bancofator.com.br]
Sent: Friday, April 19, 2013 8:59 PM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] developer on windows

Hi ,

I tryed to test one simple app and when I doing my app exemplo I save on 
another local outside of my home user windows, but a got the following error:

:-1: error: Project is outside of shared home 'C:\Users\dgomes'

My exemplo is on d:\projeto\celular\hello

Daniel
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] QGraphicsView support?

[Jarko Vihriala]

Hi,
Looking at the current SDK build engine:
[root@SailfishSDK SailfishOS-i486-x86]# find . -name QGraphicsView
./usr/include/qt4/QtGui/QGraphicsView

So yes, the stuff is there all right, at least for time being. Look for 
API changes as If QGraphicsView is going to be deprecated in the future 
- you'll need to do changes.


I think the best way for you is to give it a go and find out the results 
then. That's why we in first place put out the SDK's for all major 
development PC environments - so that people can experiment SailfishOS 
with their own app.


As you progress, people on this mailing list will surely help you out.

thanks, Jarko

On 04/18/2013 08:06 PM, Duncan Waugh wrote:

Hi there,

I've seen a number of posts stating that QML is the paradigm of choice 
for UI apps under Sailfish.  We have a game framework that uses 
QGraphicsView for all the rendering, and migrating everything over to 
QML is not an option.  Can anyone confirm is it possible to produce a 
Sailfish application without using any QML, by sticking purely to 
QGraphicsView?


Thanks for any help.


___
SailfishOS.org Devel mailing list



--
We are #unlike.
Jolla Oy, http://www.jolla.com

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] adding a module to the Qt-sdk

[Jarko Vihriala]

Yes, in that case you need to manually ssh to both SDK build machine 
(port ) and SDK emulator (port 2223) to install packages needed for 
compilation and running of the app. SDK Control Center can take care of 
the packages it knows to handle see SDK Control Center -> Target -> 
Manage -> .


Reasoning is that SDK build machine needs to have the headers and libs 
to link againts when building the app. Emulator VM can run the app only 
if the needed QML imports and/or shared libs are present in the 
emulator's run-time config.


thanks, Jarko

On 04/14/2013 09:17 AM, christopher.l...@thurweb.ch wrote:

Hi Wim

I am the process of learning this sort of thing myself...

My (still somewhat hazy) understanding is that you will have to add 
new packages to both the SDK and the Emulator.


Packages on the SDK can be managed from within Qt Creator. (You should 
have a SailfishOS Icon to the left of your screen (under the Projects 
Icon).


To update the Emulator do the following:
1. connect to the Emulator via ssh:
ssh -i ~/.ssh/mer-qt-creator-rsa root@localhost -p 2223

2. su - (root password is "nemo")

3. zypper in 

b.t.w if you need to ssh to the Emulator:
ssh -i ~/.ssh/mer-qt-creator-rsa root@localhost -p 

Ciao

Chris


Zitat von "Wim de Vries" :


Hi,
I have an aircraft navigation system (open source, see 
https://sourceforge.net/projects/pilotnavigator/) running on Ubuntu.

I have recently added the QtSerialPort module to it.
Now I want to port the system to Sailfish and I am running into 
problems with the QtSerialPort part.
On Ubuntu I build QtSerialPort into the Qt SDK, by running the qmake 
of the current SDK on the pro file of QtSerialPort source set.


I want to do the same for Sailfish but I don know how. As far as I 
understand does qmake (and the rest of the SDK) run on the MerSDK on 
a virtual box?
Should I copy the QtSerialPort source tree to this box and build it 
on this box?

Will it stay there?

Thanks.
___
SailfishOS.org Devel mailing list




___
SailfishOS.org Devel mailing list



--
We are #unlike.
Jolla Oy, http://www.jolla.com

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] no c++ in Sailfish?

[Jarko Vihriala]

Hello,

The QML is a markup language and brings javascript and native bindings 
to declarative ui. The ui is the code and vice versa. The traditional 
widget model is phasing out on the Qt development, this is more apparent 
in the late instances of Qt.


Code-wise there are no problems of using mix-and-match c++ plugins in 
QML on Sailfish OS. The only limiting factor would be those API's that 
are needed to compile and link against some middleware component ; most 
of the packages Sailfish OS ships with have the -devel or -dev package 
but not all. Also if you're bringing a new middleware library within 
your project you need to make sure all the dependencies are in place.


Like it was said before in this thread, only some native 3D accelerated 
games would benefit from using native UI but that's the only corner-case 
; almost all other variations of the ui theme are actually better off 
when done with QML.


But try it out! I don't recall we explicitly removed ant QWidget stuff 
so it can be that your stuff will compile and work out of the box. The 
new project wizard in the Sailfish OS might not have the right options 
but if you have existing Harmattan/Symbian/? Qt project you should have 
no problems importing the existing stuff.


thanks, Jarko

On 04/14/2013 11:48 PM, Wim de Vries wrote:

Hi,
My project is C++.
It looks like Sailfish is only Qt Quick (new project only allows this 
option).

Is C++ a no-go for sailfish?
If not, how do I proceed.
Thanks.
___
SailfishOS.org Devel mailing list



--
We are #unlike.
Jolla Oy, http://www.jolla.com

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] cannot deploy on emulator

[Jarko Vihriala]

You beat me to it. Anyway, it might also be a DNS thing, see

https://sailfishos.org/wiki/SDK_Alpha_Known_Issues#Emulator

-->
"If deployment fails with: "Could not connect to host: Timeout waiting 
for reply from server." then there is a problem with VirtualBox and DNS 
resolution. To fix either ssh in to the emulator as root or press 
right-ctrl+F2 and login as root/nemo. Then echo nameserver 8.8.8.8 > 
/etc/resolv.conf inside the emulator. (right-ctrl+F1 to get graphics back) "


I'll take a look at that timeout value update, seems like a good 
workaround as well.


thanks, Jarko

On 04/04/2013 01:09 PM, Wim de Vries wrote:

Well, answering myself:
QtCreator->Tools->Options->Devices I increased the time-out value to 
60secs.

Now it works!


Wim de Vries schreef op 2013-04-04 11:33:

Hi,
 Ubuntu 12.10 64bits.
 i am trying to build and deploy the mediagallery example, but it fails.
 When the emulator starts I see some some mounting errors related to
ext-fs, but it all flashes away...
 I can get the sailfish screen with ctrl-H.

 See below the compile output.
 thanks.

11:31:21: Running steps for project mediagallery...

11:31:21: Starting:
"/home/wim/SailfishOS/share/qtcreator/MerProject/mer-sdk-tools/MerSDK/SailfishOS-i486-x86/qmake" 


/home/wim/SailfishOS/examples/SailfishOS/mediagallery/mediagallery.pro
-r -spec linux-g++-32 CONFIG+=debug CONFIG+=declarative_debug -after
OBJECTS_DIR=obj MOC_DIR=moc UI_DIR=ui RCC_DIR=rcc

Project MESSAGE: Building with qdeclarative-boostable support

11:31:23: The process
"/home/wim/SailfishOS/share/qtcreator/MerProject/mer-sdk-tools/MerSDK/SailfishOS-i486-x86/qmake" 


exited normally.

11:31:23: Starting:
"/home/wim/SailfishOS/share/qtcreator/MerProject/mer-sdk-tools/MerSDK/SailfishOS-i486-x86/make" 


-w

make: Entering directory
`/home/mersdk/SailfishOS/examples/SailfishOS/mediagallery'

make: Nothing to be done for `first'.

make: Leaving directory
`/home/mersdk/SailfishOS/examples/SailfishOS/mediagallery'

11:31:25: The process
"/home/wim/SailfishOS/share/qtcreator/MerProject/mer-sdk-tools/MerSDK/SailfishOS-i486-x86/make" 


exited normally.

11:31:25: Checking whether to start Emulator...

11:31:25: Emulator is already running. Nothing to do.

11:31:25: Connecting to device...

11:31:35: Could not connect to host: Timeout waiting for reply from 
server.


Did the emulator fail to start?

11:31:35: Deploy step failed.

Error while building/deploying project mediagallery (kit:
MerSDK-SailfishOS-i486-x86)

When executing step 'Start Emulator, if necessary'

___
SailfishOS.org Devel mailing list

___
SailfishOS.org Devel mailing list



--
We are #unlike.
Jolla Oy, http://www.jolla.com

___
SailfishOS.org Devel mailing list