Ask / Submit
21

Coming up: architectural changes

asked 2016-11-23 15:22:57 +0200

tortoisedoc gravatar image

updated 2016-11-23 20:25:34 +0200

r0kk3rz gravatar image

This is meant mostly for developers.

As per announcement on blog.jolla.com; can we have a list of things that will not change in the next (supposedly big) update? specifically im talking about middleware and lipstick.

edit retag flag offensive close delete

Comments

5

if it contains things like Bluez5 and Qt5.6 then the answer is "not much". That said, if you're using stable APIs for things then they shouldn't change.

r0kk3rz ( 2016-11-23 16:02:37 +0200 )edit
3

@rokk3rz you mean alot will change? qt5.6 is definitely welcomed

tortoisedoc ( 2016-11-23 18:09:51 +0200 )edit
2

+1 for qt5.6 :)

pigg ( 2016-11-23 19:21:50 +0200 )edit
2

@tortoisedoc yes, you can imagine that swapping in a new Qt version is going to require a lot of updated packages. If there are any major breaking developer APIs I hope they would tell us, but so far they have been very careful about those for harbour apps

r0kk3rz ( 2016-11-23 20:09:12 +0200 )edit
4

@r0kk3rz thats why this thread We need more specifcs; the open parts should not be a problem to talk about I believe; if something can go wrong, it will go wrong. also this is not about reassuring any worries i/someone else might have, but rather helping prepare for the change. given the roadmap is a year old this would give us at least SOME visibility

tortoisedoc ( 2016-11-23 20:23:20 +0200 )edit

2 Answers

Sort by » oldest newest most voted
10

answered 2016-12-02 18:54:21 +0200

r0kk3rz gravatar image

updated 2016-12-05 15:58:04 +0200

I have added a topic to the next Meeting(Monday 5th of December 2016 , 09:00 UTC) about this:

https://together.jolla.com/question/54157/sailfishos-open-source-collaboration-meeting-planning/

EDIT: Issue was discussed, notes can be found here. In general most things should be fine, but developers should join the Early Access group and test their applications at the earliest possible opportunity.

Also bare in mind that if you rebuild your app it won't work on older versions of Sailfish OS.

edit flag offensive delete publish link more

Comments

That means that developers should organize themselves and have two software instances if they want to have their apps compatible for each sfos versions?
Seems that sfos will have it first fragmentation....

cemoi71 ( 2016-12-06 11:02:19 +0200 )edit
1

First? This is the second time this has happened. Post-Uitukka apps suffered the same issue. The only people this is likely to affect is those still clinging onto the Sailfish 1.X UI.

r0kk3rz ( 2016-12-06 11:29:46 +0200 )edit

ok we can't see with it that i came afterwards...

cemoi71 ( 2016-12-06 12:12:32 +0200 )edit
7

answered 2016-12-17 10:16:19 +0200

When upgrading to Qt5.6, one should pay attention to the multi-line strings in Javascript. They won't work anymore, see this commit for Sailfish Documents.

edit flag offensive delete publish link more

Comments

Oh wow. I hadn't known about that.

chris.adams ( 2016-12-20 03:56:39 +0200 )edit

That sounds like something that could break numerous apps. Any idea what's the reason for this changing in 5.6 ?

MartinK ( 2016-12-21 02:05:54 +0200 )edit
2

Well, I've learnt after this PR that Javascript doesn't have multi-line strings, as stated in this Stackoverflow question. I guess Qt changes its Javascript engine at one point between 5.2 and 5.6 and became more strict, which is good IMHO, but can break some applications (mine included).

Damien Caliste ( 2016-12-21 12:06:19 +0200 )edit
Login/Signup to Answer

Question tools

Follow
5 followers

Stats

Asked: 2016-11-23 15:22:57 +0200

Seen: 2,174 times

Last updated: Dec 21 '16