[SailfishDevel] State of BLE in Sailfish?
What is the current state of BLE support in Sailfish? I know there was a big long story about BlueZ 4 and 5 and Qt versions and so on when I was investigating last summer. Where did we get to on that? I still want to achieve self-hosting on a mobile Linux, and what I show below on Android with the aim of getting that going on Tizen should be equally possible on Sailfish. Easier even, because Qt apps can come across from the desktop easier than on Tizen with EFL the only supported option. https://bobsummerwill.wordpress.com/2014/08/11/first-steps-on-the-path-to-tizen-self-hosting/ Cheers, Bob ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Mono for Sailfish - round #2?
Great news, Dimitar! On Jun 18, 2015 7:20 AM, Dimitar Dobrev dpldob...@yahoo.com wrote: Hi all, Bob, GSoC is over at the end of August. However, I think that some demos will be able to be built at least a month earlier. The reason is that we only need complete support for dependencies. I have already completed the mechanism itself, what I need to do now is fix 5 or 6 bugs revealed by the first dependent module - QtGui. Once that's done, I'll have only QtWidgets to wrap which means that Qt# will be ready for building visual examples. Regards, Dimitar On Thursday, June 18, 2015 10:23 AM, Bob Summerwill b...@summerwill.net wrote: In this context a bind of Xamarin.Form could be really interesting to catch developers attentions and allow for easy app port for the many that are using that technology (and this day seems a lot). Michele I asked Xamarin about that last year. Whether there was an opportunity for me to build Xamarin.Forms support for Tizen/Sailfish with their help/co-operation. The answer was no. Xamarin.Forms is a pure commercial offering from Xamarin, which is built on top of Mono, which is open-sourced on some platforms and closed on others (iOS and Android). Getting a Xamarin.Forms for Tizen/Sailfish would not be binding project. It would be a reverse-engineering product. End-users would need to include some core assemblies in their application which they could only obtain if there were a Xamarin paying customer.And for the Sailfish-specific Xamarin.Form bindings we would need to reverse-engineer how the platform-specific assemblies for Xamarin.Forms are built, and then make one for Sailfish. So while this is technically possible, it is not something which Xamarin would support and it is something they would actively fight in all likelyhood. And it might be a lot of work. As you say, though, it would be damn sweet! Shared XAML for Windows Phone, Surface, PC, XBOX360, iOS, Android and Sailfish would be cool. Cheers, Bob On Thu, Jun 18, 2015 at 2:58 AM, Michele Tameni mich...@tameni.it wrote: In this context a bind of Xamarin.Form could be really interesting to catch developers attentions and allow for easy app port for the many that are using that technology (and this day seems a lot). Michele 2015-06-18 8:42 GMT+02:00 Bob Summerwill b...@summerwill.net: Greetings! Last year the Mono for Sailfish project was announced, development started and then withered and silently died. That was mainly due to reasons related to my own personal situation (I lost a job and had to focus on job-hunting, not Kitsilano Software, etc) rather than any lack of technical merit of the project. http://monoforsailfish.com http://www.mobilelinuxnews.com/2014/08/introduction-mono-sailfish-os-jolla/ Anyway. It is a new year, and circumstances have changed. After several months in the doldrums, the winds have changed in our favor again, sailors! 1. Microsoft have open sourced .NET in a major way, and are supporting it on Linux and Mac OSX. They announced that last November and in April of this year they made the first preview releases for OSX and Linux. See http://venturebeat.com/2015/04/29/microsoft-releases-net-core-preview-for-mac-and-linux/. The did the most amazing .NET Core demo trick during //BUILD, which was creating an ASP.NET http://asp.net/ 5 web app (ASP.NET5 is open-sourced too) in Visual Studio on a Windows PC, deploying that app into a Linux Docker container (so .NET Core assemblies on Linux with the ASP.NET5 assemblies on top of that) and then running that app and hitting a breakpoint and single-stepping through the app).So debugging a .NET app running inside a container, running on a different OS. Kind of cool. .NET Core is going to be an even better base for getting .NET onto mobile Linux than Mono was, because it has the full weight of Microsoft support behind it. They want that .NET platform available for Linux to support ASP.NET http://asp.net/ apps inside Azure. Mono on Linux wasn't supporting any business for Xamarin, so was a little unloved. Their focus is on Android and iOS. Aside - Microsoft also released this - http://www.hanselman.com/blog/IntroducingVisualStudioCodeForWindowsMacAndLinux.aspx . 2. QtSharp (https://github.com/ddobrev/QtSharp), the project on whose completion Mono for Sailfish was dependent, has got funding as part of the Google Summer of Code, so will be brought to functional completeness on Windows, OSX and Linux this year. That is fantastic, because I was personally bankrolling that non-Sailfish-specific work as part of Mono for Sailfish. It moved along for a couple of months under Mono for Sailfish, but it was apparent that there was a lot of work more work to be done to get to that 1.0 version. But that will now be moving ahead independently of Mono for Sailfish, which is great to see. Dimitar Dobrev is
[SailfishDevel] QtSensors SensorGesture
Hello everybody ! This is my first post (and first SailfishOS app), so be indulgent :) I try to use SensorGesture within an app for the Jolla. I particularly want to use the shake gesture. I import for this QtSensors 5.x. But onDetected signal is never raised. availableGestures seems to be empty, at least. Am I missing something ? Thanks for the answer. Regards, Fab ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Mono for Sailfish - round #2?
In this context a bind of Xamarin.Form could be really interesting to catch developers attentions and allow for easy app port for the many that are using that technology (and this day seems a lot). Michele 2015-06-18 8:42 GMT+02:00 Bob Summerwill b...@summerwill.net: Greetings! Last year the Mono for Sailfish project was announced, development started and then withered and silently died. That was mainly due to reasons related to my own personal situation (I lost a job and had to focus on job-hunting, not Kitsilano Software, etc) rather than any lack of technical merit of the project. http://monoforsailfish.com http://www.mobilelinuxnews.com/2014/08/introduction-mono-sailfish-os-jolla/ Anyway. It is a new year, and circumstances have changed. After several months in the doldrums, the winds have changed in our favor again, sailors! 1. Microsoft have open sourced .NET in a major way, and are supporting it on Linux and Mac OSX. They announced that last November and in April of this year they made the first preview releases for OSX and Linux. See http://venturebeat.com/2015/04/29/microsoft-releases-net-core-preview-for-mac-and-linux/. The did the most amazing .NET Core demo trick during //BUILD, which was creating an ASP.NET 5 web app (ASP.NET5 is open-sourced too) in Visual Studio on a Windows PC, deploying that app into a Linux Docker container (so .NET Core assemblies on Linux with the ASP.NET5 assemblies on top of that) and then running that app and hitting a breakpoint and single-stepping through the app).So debugging a .NET app running inside a container, running on a different OS. Kind of cool. .NET Core is going to be an even better base for getting .NET onto mobile Linux than Mono was, because it has the full weight of Microsoft support behind it. They want that .NET platform available for Linux to support ASP.NET apps inside Azure. Mono on Linux wasn't supporting any business for Xamarin, so was a little unloved. Their focus is on Android and iOS. Aside - Microsoft also released this - http://www.hanselman.com/blog/IntroducingVisualStudioCodeForWindowsMacAndLinux.aspx . 2. QtSharp (https://github.com/ddobrev/QtSharp), the project on whose completion Mono for Sailfish was dependent, has got funding as part of the Google Summer of Code, so will be brought to functional completeness on Windows, OSX and Linux this year. That is fantastic, because I was personally bankrolling that non-Sailfish-specific work as part of Mono for Sailfish. It moved along for a couple of months under Mono for Sailfish, but it was apparent that there was a lot of work more work to be done to get to that 1.0 version. But that will now be moving ahead independently of Mono for Sailfish, which is great to see. Dimitar Dobrev is the developer. Hi, Dimitar, and congratulations on securing funding from GSOC! Deliverables: Improve the QT bindings generator to the point that they can be used for a non-trivial QT sample written in idiomatic C#. https://www.google-melange.com/gsoc/project/details/google/gsoc2015/ddobrev/5741031244955648 https://trello.com/c/b34YKGIi/57-cppsharp-continue-mono-net-bindings-for-qt When the QtSharp GSOC project is over (when is that, Dimitar?) and we have a non-trivial Qt sample written in idiomatic C# working on Windows, OSX and Linux, I think we are in a position to look at rebooting this project, though it would be .NET Core for Sailfish now, not Mono for Sailfish. This new project would have much of the same flavor as the last one, but have a smaller scope of effort required to get to a 1.0 release: 1. Get .NET Core runtime for Linux working on Sailfish (should be similar scope to the work which Damien Diederen did for MonoTizen). See http://monotizen.com. 2. Build MonoDevelop plugin for Sailfish (should be similar scope to the work which Damien Diederen did for MonoTizen). See http://monotizen.com. 3. Build wrappers for Sailfish-specific Qt/QML components, so that apps of similar complexity to the deliverable of the GSOC project can be built on Sailfish. With regard to this third point, is there a Wiki page or other posting detailing the latest state of licensing for Silica? Has that moved at all since last year? Are more QML components being open-sourced? And just to be clear, there is no source code hiding going on with Silica, right? It is just that certain files are not under an open source license? Nothing that would hinder this binding work, eh? Cheers, Bob Summerwill Kitsilano Software (http://bobsummerwill.wordpress.com/about) -- b...@summerwill.net ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org -- michele tameni ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to
Re: [SailfishDevel] Mono for Sailfish - round #2?
PS. More info on the MonoDevelop add-in for Tizen, which would be the model for the MonoDevelop add-in for Sailfish: http://kitsilanosoftware.github.io/MonoDevelop.Tizen/ Aside - The Tizen project is even more broken now than it was last year. I now have a deep understanding of the reasons why Carsten and David re-launched the Mer project. Thank god for you guys doing that, because Tizen has played out exactly as you expected, which is presumably exactly the same as MeeGo did, just with Samsung taking the place of Nokia. There is absolutely no consideration of the community within the Tizen Project, which Intel seem to have silently abandoned in the last few months.It is now a pure Samsung show and seems to be pretty indistinguishable from Android in the last it is developed. Everything behind closed doors. Source code drops at major releases. No opportunity for community involvement, and little to no information on what is being worked on until after it is released in a product. Samsung just recently did a preview SDK for the pending Gear watch (round one) which is a move in the right direction, but this is very much on their terms (and again a drop, rather than development in the open): http://www.samsungmobilepress.com/2015/04/24/Samsung-to-Release-SDK-for-Next-Generation-Gear The open governance for Tizen which was announced an incredibly long time ago only applied to Tizen 3.0 development, not to the ongoing Tizen 2.x development on which all of Samsung's products are built. That is all still happening behind closed doors. Tizen 3.0 development was happening in the open, but was only for Tizen IVI and Tizen Common. They did get to a https://wiki.tizen.org/wiki/IVI/Tizen-IVI_3.0 release, but as soon as that happened Intel appeared to silently bugger off, as though they had a legal obligation to ship Tizen IVI, and having met that obligation, they high-tailed it out of Dodge. Of course, they may not admit that reality for months, or indeed ever, but that appears to be what has happened. With that being the case, Tizen 3.0 is essentially a zombie codebase. Some Samsung engineers might be working on Tizen 3.0 profiles, for Mobile, or Wearable, or TV, but those don't correspond to the code which is going into the Tizen-based products which Samsung are actually shipping - Tizen SmartTV (all 2015 models are Tizen), Cameras, Gear smartwatches (Gear 2, Gear S and now pending Gear A), and finally mobile - Samsung Z1, with Z2 and Z3 pending rumored. I see little movement towards Samsung making product based on Tizen 3.0. With Intel having gone, I see no reason whatsoever why Samsung will ever play nice and move to open governance and a Tizen 3.0 codebase for Mobile, Wearable and TV.They can harvest whatever features they like from Tizen 3.0 (Wayland, Multi-User, SMACK, etc) back into their internal Tizen 2.x codelines, and need never be subject to open governance, and claim they never violated any agreement, because the open governance was only for Tizen 3.0 development, and they aren't doing any Tizen 3.0 development. They made a huge API change between Tizen 2.3 Alpha and Tizen 2.4 Beta showing complete contempt for semantic versioning. https://developer.tizen.org/fr/forums/native-application-development/huge-difference-native-environment-between-2.2.1-and-2.3?langswitch=fr. They dropped the C++ OSP framework which had been brought across from Bada between Alpha and Beta, breaking all existing Native applications. Everybody who had been working on native applications for the last 18 months or so was left in the dust. The API which everyone had been told to use, and which books had been written about, was just silently killed with no forewarning or even explicit announcement - until developers noticed the change and responded with WTF! Given that relationship between Samsung and the community, I can see them hiding inside Tizen 2.x forever.The sad thing is that Tizen is maturing quite nicely, and is covering a larger and larger range of profiles and actual devices. Samsung are taking Tizen very seriously. It just is NOT AT ALL development in the open or community-friendly. It is just like Android in that respect, just with a better, more GNU/Linux aligned code-base. Cheers, Bob On Thu, Jun 18, 2015 at 2:42 AM, Bob Summerwill b...@summerwill.net wrote: Greetings! Last year the Mono for Sailfish project was announced, development started and then withered and silently died. That was mainly due to reasons related to my own personal situation (I lost a job and had to focus on job-hunting, not Kitsilano Software, etc) rather than any lack of technical merit of the project. http://monoforsailfish.com http://www.mobilelinuxnews.com/2014/08/introduction-mono-sailfish-os-jolla/ Anyway. It is a new year, and circumstances have changed. After several months in the doldrums, the winds have changed in our favor again, sailors! 1. Microsoft
Re: [SailfishDevel] Mono for Sailfish - round #2?
In this context a bind of Xamarin.Form could be really interesting to catch developers attentions and allow for easy app port for the many that are using that technology (and this day seems a lot). Michele I asked Xamarin about that last year. Whether there was an opportunity for me to build Xamarin.Forms support for Tizen/Sailfish with their help/co-operation. The answer was no. Xamarin.Forms is a pure commercial offering from Xamarin, which is built on top of Mono, which is open-sourced on some platforms and closed on others (iOS and Android). Getting a Xamarin.Forms for Tizen/Sailfish would not be binding project. It would be a reverse-engineering product. End-users would need to include some core assemblies in their application which they could only obtain if there were a Xamarin paying customer.And for the Sailfish-specific Xamarin.Form bindings we would need to reverse-engineer how the platform-specific assemblies for Xamarin.Forms are built, and then make one for Sailfish. So while this is technically possible, it is not something which Xamarin would support and it is something they would actively fight in all likelyhood. And it might be a lot of work. As you say, though, it would be damn sweet! Shared XAML for Windows Phone, Surface, PC, XBOX360, iOS, Android and Sailfish would be cool. Cheers, Bob On Thu, Jun 18, 2015 at 2:58 AM, Michele Tameni mich...@tameni.it wrote: In this context a bind of Xamarin.Form could be really interesting to catch developers attentions and allow for easy app port for the many that are using that technology (and this day seems a lot). Michele 2015-06-18 8:42 GMT+02:00 Bob Summerwill b...@summerwill.net: Greetings! Last year the Mono for Sailfish project was announced, development started and then withered and silently died. That was mainly due to reasons related to my own personal situation (I lost a job and had to focus on job-hunting, not Kitsilano Software, etc) rather than any lack of technical merit of the project. http://monoforsailfish.com http://www.mobilelinuxnews.com/2014/08/introduction-mono-sailfish-os-jolla/ Anyway. It is a new year, and circumstances have changed. After several months in the doldrums, the winds have changed in our favor again, sailors! 1. Microsoft have open sourced .NET in a major way, and are supporting it on Linux and Mac OSX. They announced that last November and in April of this year they made the first preview releases for OSX and Linux. See http://venturebeat.com/2015/04/29/microsoft-releases-net-core-preview-for-mac-and-linux/. The did the most amazing .NET Core demo trick during //BUILD, which was creating an ASP.NET 5 web app (ASP.NET5 is open-sourced too) in Visual Studio on a Windows PC, deploying that app into a Linux Docker container (so .NET Core assemblies on Linux with the ASP.NET5 assemblies on top of that) and then running that app and hitting a breakpoint and single-stepping through the app).So debugging a .NET app running inside a container, running on a different OS. Kind of cool. .NET Core is going to be an even better base for getting .NET onto mobile Linux than Mono was, because it has the full weight of Microsoft support behind it. They want that .NET platform available for Linux to support ASP.NET apps inside Azure. Mono on Linux wasn't supporting any business for Xamarin, so was a little unloved. Their focus is on Android and iOS. Aside - Microsoft also released this - http://www.hanselman.com/blog/IntroducingVisualStudioCodeForWindowsMacAndLinux.aspx . 2. QtSharp (https://github.com/ddobrev/QtSharp), the project on whose completion Mono for Sailfish was dependent, has got funding as part of the Google Summer of Code, so will be brought to functional completeness on Windows, OSX and Linux this year. That is fantastic, because I was personally bankrolling that non-Sailfish-specific work as part of Mono for Sailfish. It moved along for a couple of months under Mono for Sailfish, but it was apparent that there was a lot of work more work to be done to get to that 1.0 version. But that will now be moving ahead independently of Mono for Sailfish, which is great to see. Dimitar Dobrev is the developer. Hi, Dimitar, and congratulations on securing funding from GSOC! Deliverables: Improve the QT bindings generator to the point that they can be used for a non-trivial QT sample written in idiomatic C#. https://www.google-melange.com/gsoc/project/details/google/gsoc2015/ddobrev/5741031244955648 https://trello.com/c/b34YKGIi/57-cppsharp-continue-mono-net-bindings-for-qt When the QtSharp GSOC project is over (when is that, Dimitar?) and we have a non-trivial Qt sample written in idiomatic C# working on Windows, OSX and Linux, I think we are in a position to look at rebooting this project, though it would be .NET Core for Sailfish now, not Mono for Sailfish. This new project would have much of
[SailfishDevel] Flattr support enabled in Jolla Harbour and Jolla Store!
Dear Developers, We are happy to introduce Flattr in Jolla Store and Jolla Harbour! Some of you have already noticed the implementation of Flattr in our development roadmap [0]. The Jolla Store backend and client support have been released in the latest OS update Aaslakkajärvi [1], and we have just deployed Jolla Harbour support for Flattr earlier today. In case you aren't familiar with Flattr [2], it is a micro donation service where consumers can donate money to content creators, e.g. app developers. With the Flattr icon prominently displayed in the description of your app [3], your users and fans can easily reach your Flattr profile and show their support through donations. To enable this, you need to first register for a Flattr account [4]. After that, please add your Flattr username and link to your app website to harbour application submission page, and submit the changes to QA. Setting up the Flattr account is free. For each donation, Flattr keeps 10% and you receive 90%. Jolla does not take any of the funds. For more details, please refer to the FAQ in Jolla Harbour [5], as well as the Flattr FAQ [6]. We hope you will find this a useful and flexible way to support your Sailfish OS development work. Thank you for your continued contributions to the Sailfish OS platform and community! On behalf of Jolla Store/Harbour team [0] https://sailfishos.org/developmentroadmap/ [1] https://together.jolla.com/question/95125/changelog-116aaslakkajarvi/ [2] https://flattr.com/ [3] https://twitter.com/capricotwi/status/611188750505373696/photo/1 [4] https://flattr.com/register [5] https://harbour.jolla.com/faq#Flattr [6] https://flattr.com/support/faq ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
[SailfishDevel] Mono for Sailfish - round #2?
Greetings! Last year the Mono for Sailfish project was announced, development started and then withered and silently died. That was mainly due to reasons related to my own personal situation (I lost a job and had to focus on job-hunting, not Kitsilano Software, etc) rather than any lack of technical merit of the project. http://monoforsailfish.com http://www.mobilelinuxnews.com/2014/08/introduction-mono-sailfish-os-jolla/ Anyway. It is a new year, and circumstances have changed. After several months in the doldrums, the winds have changed in our favor again, sailors! 1. Microsoft have open sourced .NET in a major way, and are supporting it on Linux and Mac OSX. They announced that last November and in April of this year they made the first preview releases for OSX and Linux. See http://venturebeat.com/2015/04/29/microsoft-releases-net-core-preview-for-mac-and-linux/. The did the most amazing .NET Core demo trick during //BUILD, which was creating an ASP.NET 5 web app (ASP.NET5 is open-sourced too) in Visual Studio on a Windows PC, deploying that app into a Linux Docker container (so .NET Core assemblies on Linux with the ASP.NET5 assemblies on top of that) and then running that app and hitting a breakpoint and single-stepping through the app).So debugging a .NET app running inside a container, running on a different OS. Kind of cool. .NET Core is going to be an even better base for getting .NET onto mobile Linux than Mono was, because it has the full weight of Microsoft support behind it. They want that .NET platform available for Linux to support ASP.NET apps inside Azure. Mono on Linux wasn't supporting any business for Xamarin, so was a little unloved. Their focus is on Android and iOS. Aside - Microsoft also released this - http://www.hanselman.com/blog/IntroducingVisualStudioCodeForWindowsMacAndLinux.aspx . 2. QtSharp (https://github.com/ddobrev/QtSharp), the project on whose completion Mono for Sailfish was dependent, has got funding as part of the Google Summer of Code, so will be brought to functional completeness on Windows, OSX and Linux this year. That is fantastic, because I was personally bankrolling that non-Sailfish-specific work as part of Mono for Sailfish. It moved along for a couple of months under Mono for Sailfish, but it was apparent that there was a lot of work more work to be done to get to that 1.0 version. But that will now be moving ahead independently of Mono for Sailfish, which is great to see. Dimitar Dobrev is the developer. Hi, Dimitar, and congratulations on securing funding from GSOC! Deliverables: Improve the QT bindings generator to the point that they can be used for a non-trivial QT sample written in idiomatic C#. https://www.google-melange.com/gsoc/project/details/google/gsoc2015/ddobrev/5741031244955648 https://trello.com/c/b34YKGIi/57-cppsharp-continue-mono-net-bindings-for-qt When the QtSharp GSOC project is over (when is that, Dimitar?) and we have a non-trivial Qt sample written in idiomatic C# working on Windows, OSX and Linux, I think we are in a position to look at rebooting this project, though it would be .NET Core for Sailfish now, not Mono for Sailfish. This new project would have much of the same flavor as the last one, but have a smaller scope of effort required to get to a 1.0 release: 1. Get .NET Core runtime for Linux working on Sailfish (should be similar scope to the work which Damien Diederen did for MonoTizen). See http://monotizen.com. 2. Build MonoDevelop plugin for Sailfish (should be similar scope to the work which Damien Diederen did for MonoTizen). See http://monotizen.com. 3. Build wrappers for Sailfish-specific Qt/QML components, so that apps of similar complexity to the deliverable of the GSOC project can be built on Sailfish. With regard to this third point, is there a Wiki page or other posting detailing the latest state of licensing for Silica? Has that moved at all since last year? Are more QML components being open-sourced? And just to be clear, there is no source code hiding going on with Silica, right? It is just that certain files are not under an open source license? Nothing that would hinder this binding work, eh? Cheers, Bob Summerwill Kitsilano Software (http://bobsummerwill.wordpress.com/about) -- b...@summerwill.net ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
