asked 2016-11-23 15:22:57 +0300
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.
answered 2016-12-02 18:54:21 +0300
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.
answered 2016-12-17 10:16:19 +0300
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.
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 +0300 )editAsked: 2016-11-23 15:22:57 +0300
Seen: 2,222 times
Last updated: Dec 21 '16
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 +0300 )edit@rokk3rz you mean alot will change? qt5.6 is definitely welcomed
tortoisedoc ( 2016-11-23 18:09:51 +0300 )edit+1 for qt5.6 :)
pigg ( 2016-11-23 19:21:50 +0300 )edit@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 +0300 )edit@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 +0300 )edit