<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><br><div id="yui_3_16_0_1_1439986914805_92047"><span id="yui_3_16_0_1_1439986914805_92089"> Hello Bob, glad to hear from you again!</span></div><div id="yui_3_16_0_1_1439986914805_100420"><br><span id="yui_3_16_0_1_1439986914805_92089"></span></div><div id="yui_3_16_0_1_1439986914805_93650" dir="ltr"><span id="yui_3_16_0_1_1439986914805_92089"> 1. There are 10 more days to go but I am more or less done for the Google summer. There's a single bug in our parser which blocks QtWidgets from being wrapped - which means from building GUI examples with Qt#. I am unfortunately busy with other work until the end of the month so I mostly rely on Joao for this one;</span></div><div id="yui_3_16_0_1_1439986914805_93651" dir="ltr"><span id="yui_3_16_0_1_1439986914805_92089"> 2. I personally would hardly be able to spare any effort on non-Qt parts of Sailfish. However, the Qt binding which is an essential module has been going well and I expect little trouble with platforms other than Windows;</span></div><div id="yui_3_16_0_1_1439986914805_94640" dir="ltr"> 3. It's a long story for a single e-mail. Let's say that Qt Quick is, as far as GUI is concerned, an alternative to QtWidgets. What is of main concern to us is that the approach in QML is radically different which means it's not enough just to wrap the C++ code and work with QML. Integration with the host language has to be added, so that when a property is changed or a signal in emitted in QML, C# can detect that. This makes wrapping QML an entirely new and non-trivial task;</div><div id="yui_3_16_0_1_1439986914805_96627" dir="ltr"> 4. I am little familiar with Silica but as long as it's standard C++ headers, libs, and QML files, I cannot think of any trouble we might have - provided that point 3. has been completed, of course;</div><div id="yui_3_16_0_1_1439986914805_97952" dir="ltr"> 5. C++# works with headers and libs, it does not need source code. So for our particular job we couldn't care less if Silica's closed or not.</div><div id="yui_3_16_0_1_1439986914805_99339" dir="ltr"> <br></div><div id="yui_3_16_0_1_1439986914805_99351" dir="ltr"> I hope I have been helpful, otherwise let me know.</div><div id="yui_3_16_0_1_1439986914805_99687" dir="ltr"><br></div><div id="yui_3_16_0_1_1439986914805_99688" dir="ltr"><br></div><div id="yui_3_16_0_1_1439986914805_99689" dir="ltr"> Regards,</div><div id="yui_3_16_0_1_1439986914805_99690" dir="ltr"> Dimitar<br></div><div id="yui_3_16_0_1_1439986914805_99346" dir="ltr"> <br></div><br><div class="qtdSeparateBR"><br><br></div><div style="display: block;" class="yahoo_quoted"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div dir="ltr"> <font face="Arial" size="2"> On Wednesday, August 19, 2015 3:24 PM, Bob Summerwill <bob@summerwill.net> wrote:<br> </font> </div> <br><br> <div class="y_msg_container"><div id="yiv1790546277"><div><div dir="ltr">Greetings! </div>
<div dir="ltr">How was the Summer of Code QtSharp project gone, Dimitar and Joao? Is the period ended or still ongoing?</div>
<div dir="ltr">Where would you say we are now sitting in terms of being able to start of a revival of Mono for Sailfish or .NET Core for Sailfish and the Qt binding to go with that? </div>
<div dir="ltr">Perhaps somebody could also educate me on QtWidgets Vs QtQuick, and on differences in approach of Qt use in KDE, Plasma, Ubuntu Touch and Sailfish? Any other platforms we need to consider? </div>
<div dir="ltr">Also, if somebody could confirm that there is nothing hidden in Silica, and that it will be physically possible to bind, that would be great.</div>
<div dir="ltr">Also, if somebody could make a definitive statement on the current licensing status of Silica, that would be much appreciated. Maybe with the company split, there will be more appetite for starting to talk about paths to open sourcing of Silica again? </div>
<div dir="ltr">Is Silica the ONLY non-open-sourced part of Sailfish? Alien Dalvik is obviously commercial, but isn't really part of Sailfish per se, right? It is just something which was bundled with the Jolla Phone. Is it bundled with the Tablet too? </div>
<div class="yiv1790546277gmail_quote">On Jun 20, 2015 2:54 AM, "Giuliettasw" <<a rel="nofollow" shape="rect" ymailto="mailto:users.giulietta@gmail.com" target="_blank" href="mailto:users.giulietta@gmail.com">users.giulietta@gmail.com</a>> wrote:<br clear="none"><blockquote class="yiv1790546277gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="yiv1790546277yqt0910680733" id="yiv1790546277yqt38033"><div><div>Qtquick 2.0 is to be preferred over qtwidgets starting qt 5.0 btw.</div><div>Iirc qtwidgets support on sfos is limited?</div><div><br clear="none"></div><div>Besz,</div><div>tortoisedoc<br clear="none"><br clear="none">Von meinem iPad gesendet</div><div><br clear="none">Am 18.06.2015 um 14:20 schrieb Dimitar Dobrev <<a rel="nofollow" shape="rect" ymailto="mailto:dpldobrev@yahoo.com" target="_blank" href="mailto:dpldobrev@yahoo.com">dpldobrev@yahoo.com</a>>:<br clear="none"><br clear="none"></div><blockquote type="cite"><div><div style="color:#000;background-color:#fff;font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"><div><br clear="none"><span></span></div><div><span> Hi all,</span></div><div><br clear="none"><span></span></div><div><span> 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.</span></div><div><br clear="none"><span></span></div><div><span> Regards,</span></div><div> Dimitar<br clear="none"><span></span></div><div><span></span></div> <br clear="none"><div><br clear="none"><br clear="none"></div><div style="display:block;"> <div style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"> <div style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"> <div dir="ltr"> <font face="Arial" size="2"> On Thursday, June 18, 2015 10:23 AM, Bob Summerwill <<a rel="nofollow" shape="rect" ymailto="mailto:bob@summerwill.net" target="_blank" href="mailto:bob@summerwill.net">bob@summerwill.net</a>> wrote:<br clear="none"> </font> </div> <br clear="none"><br clear="none"> <div><div><div><div dir="ltr"><span style="font-size:12.8000001907349px;">>> In this context a bind of Xamarin.Form could be really interesting to catch developers attentions</span><div><span style="font-size:12.8000001907349px;">>> and allow for easy app port for the many that are using that technology (and this day seems a lot).</span></div><div><span style="font-size:12.8000001907349px;">>> </span><span style="font-size:12.8000001907349px;">Michele</span><div style="font-size:12.8000001907349px;"><br clear="none"></div></div><div style="font-size:12.8000001907349px;">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.</div><div style="font-size:12.8000001907349px;"><br clear="none"></div><div style="font-size:12.8000001907349px;">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).</div><div style="font-size:12.8000001907349px;"><br clear="none"></div><div style="font-size:12.8000001907349px;">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.</div><div style="font-size:12.8000001907349px;"><br clear="none"></div><div style="font-size:12.8000001907349px;">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.</div><div style="font-size:12.8000001907349px;"><br clear="none">As you say, though, it would be damn sweet! Shared XAML for Windows Phone, Surface, PC, XBOX360, iOS, Android and Sailfish would be cool.</div><div style="font-size:12.8000001907349px;"><br clear="none"></div><div style="font-size:12.8000001907349px;"><br clear="none"></div><div style="font-size:12.8000001907349px;">Cheers,</div><div style="font-size:12.8000001907349px;">Bob</div></div><div><br clear="none"><div><div>On Thu, Jun 18, 2015 at 2:58 AM, Michele Tameni <span dir="ltr"><<a rel="nofollow" shape="rect" ymailto="mailto:michele@tameni.it" target="_blank" href="mailto:michele@tameni.it">michele@tameni.it</a>></span> wrote:<br clear="none"><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div dir="ltr">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).<div>Michele</div></div><div><br clear="none"><div><div><div>2015-06-18 8:42 GMT+02:00 Bob Summerwill <span dir="ltr"><<a rel="nofollow" shape="rect" ymailto="mailto:bob@summerwill.net" target="_blank" href="mailto:bob@summerwill.net">bob@summerwill.net</a>></span>:<br clear="none"></div></div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div><div dir="ltr">Greetings!<div><br clear="none"></div><div>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.</div><div><br clear="none"><div> <a rel="nofollow" shape="rect" target="_blank" href="http://monoforsailfish.com/">http://monoforsailfish.com</a><br clear="none"></div><div> <a rel="nofollow" shape="rect" target="_blank" href="http://www.mobilelinuxnews.com/2014/08/introduction-mono-sailfish-os-jolla/">http://www.mobilelinuxnews.com/2014/08/introduction-mono-sailfish-os-jolla/</a><br clear="none"></div><div><br clear="none"></div><div>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!</div><div><br clear="none"></div><div>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 <a rel="nofollow" shape="rect" target="_blank" href="http://venturebeat.com/2015/04/29/microsoft-releases-net-core-preview-for-mac-and-linux/">http://venturebeat.com/2015/04/29/microsoft-releases-net-core-preview-for-mac-and-linux/</a>. The did the most amazing .NET Core demo "trick" during //BUILD, which was creating an <a rel="nofollow" shape="rect" target="_blank" href="http://asp.net/">ASP.NET</a> 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 <a rel="nofollow" shape="rect" target="_blank" href="http://asp.net/">ASP.NET</a> 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.</div><div><br clear="none"></div><div>Aside - Microsoft also released this - <a rel="nofollow" shape="rect" target="_blank" href="http://www.hanselman.com/blog/IntroducingVisualStudioCodeForWindowsMacAndLinux.aspx">http://www.hanselman.com/blog/IntroducingVisualStudioCodeForWindowsMacAndLinux.aspx</a>.</div><div><br clear="none"></div><div>2. QtSharp (<a rel="nofollow" shape="rect" target="_blank" href="https://github.com/ddobrev/QtSharp">https://github.com/ddobrev/QtSharp</a>), 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!</div><div><span style="font-weight:700;color:rgb(77,77,77);font-family:'Helvetica Neue', Arial, Helvetica, sans-serif;font-size:14px;line-height:18px;background-color:rgb(237,239,240);"><br clear="none"></span></div><div><span style="font-weight:700;color:rgb(77,77,77);font-family:'Helvetica Neue', Arial, Helvetica, sans-serif;font-size:14px;line-height:18px;background-color:rgb(237,239,240);">Deliverables</span><span style="color:rgb(77,77,77);font-family:'Helvetica Neue', Arial, Helvetica, sans-serif;font-size:14px;line-height:18px;background-color:rgb(237,239,240);">: Improve the QT bindings generator to the point that they can be used for a non-trivial QT sample written in idiomatic C#.</span><br clear="none"></div><div><span style="color:rgb(77,77,77);font-family:'Helvetica Neue', Arial, Helvetica, sans-serif;font-size:14px;line-height:18px;background-color:rgb(237,239,240);"><br clear="none"></span></div><div><a rel="nofollow" shape="rect" target="_blank" href="https://www.google-melange.com/gsoc/project/details/google/gsoc2015/ddobrev/5741031244955648">https://www.google-melange.com/gsoc/project/details/google/gsoc2015/ddobrev/5741031244955648</a><br clear="none"></div><div><br clear="none"></div><div><a rel="nofollow" shape="rect" target="_blank" href="https://trello.com/c/b34YKGIi/57-cppsharp-continue-mono-net-bindings-for-qt">https://trello.com/c/b34YKGIi/57-cppsharp-continue-mono-net-bindings-for-qt</a><br clear="none"></div><div><br clear="none"></div><div>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.</div><div><br clear="none"></div><div>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:</div><div><br clear="none"></div><div>1. Get .NET Core runtime for Linux working on Sailfish (should be similar scope to the work which Damien Diederen did for MonoTizen). See <a rel="nofollow" shape="rect" target="_blank" href="http://monotizen.com/">http://monotizen.com</a>.</div><div><br clear="none"></div><div>2. Build MonoDevelop plugin for Sailfish (should be similar scope to the work which Damien Diederen did for MonoTizen). See <a rel="nofollow" shape="rect" target="_blank" href="http://monotizen.com/">http://monotizen.com</a>.</div><div><br clear="none"></div><div>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.</div><div><br clear="none"></div><div><br clear="none"></div><div>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?</div><div><br clear="none"></div><div><br clear="none"></div><div>Cheers,</div><div>Bob Summerwill</div><div>Kitsilano Software</div><div>(<a rel="nofollow" shape="rect" target="_blank" href="http://bobsummerwill.wordpress.com/about">http://bobsummerwill.wordpress.com/about</a>)<span><font color="#888888"><br clear="none"></font></span></div><span><font color="#888888"></font></span><div><br clear="none"></div><div><div><br clear="none"></div>-- <br clear="none"><div><a rel="nofollow" shape="rect" ymailto="mailto:bob@summerwill.net" target="_blank" href="mailto:bob@summerwill.net">bob@summerwill.net</a><br clear="none"><br clear="none"></div>
</div></div></div>
<br clear="none"></div></div>_______________________________________________<br clear="none">
<a rel="nofollow" shape="rect" target="_blank" href="http://sailfishos.org/">SailfishOS.org</a> Devel mailing list<br clear="none">
To unsubscribe, please send a mail to <a rel="nofollow" shape="rect" ymailto="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank" href="mailto:devel-unsubscribe@lists.sailfishos.org">devel-unsubscribe@lists.sailfishos.org</a><span><font color="#888888"><br clear="none"></font></span></blockquote></div><span><font color="#888888"><br clear="none"><br clear="all"></font></span><div><br clear="none"></div>-- <br clear="none"><div>michele tameni<br clear="none"></div>
</div>
</blockquote></div></div><br clear="none"><br clear="all"><div><br clear="none"></div>-- <br clear="none"><div><a rel="nofollow" shape="rect" ymailto="mailto:bob@summerwill.net" target="_blank" href="mailto:bob@summerwill.net">bob@summerwill.net</a><br clear="none"><br clear="none"></div>
</div></div></div><br clear="none"><br clear="none"></div> </div> </div> </div></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br clear="none"><span><a rel="nofollow" shape="rect" target="_blank" href="http://sailfishos.org/">SailfishOS.org</a> Devel mailing list</span><br clear="none"><span>To unsubscribe, please send a mail to <a rel="nofollow" shape="rect" ymailto="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank" href="mailto:devel-unsubscribe@lists.sailfishos.org">devel-unsubscribe@lists.sailfishos.org</a></span></div></blockquote></div></div><br clear="none">_______________________________________________<br clear="none">
SailfishOS.org Devel mailing list<br clear="none">
To unsubscribe, please send a mail to <a rel="nofollow" shape="rect" ymailto="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank" href="mailto:devel-unsubscribe@lists.sailfishos.org">devel-unsubscribe@lists.sailfishos.org</a><br clear="none"></blockquote></div></div></div><br><br></div> </div> </div> </div></div></body></html>