Re: [SailfishDevel] CalDAV/CardDAV Contributor Meeting
Hi everyone, Sorry for top-posting, but I'm on an Outlook Web Access client, and it doesn't do quoting. This is just a reminder that this coming Monday the 10th of October we have another CalDAV/CardDAV Contributor Meeting at 0900 UTC. The agenda can be found: https://sailfishos.org/wiki/CalDAV_and_CardDAV_Community_Contributions#10.2F10.2F2016_Meeting Everyone is welcome to attend, even if you are unable to actively contribute at this time. Some highlights from the last month of collaboration: - we have a test VM set up in the Mer infra, plan is to install CalDAV/CardDAV services on it ASAP but first we need to sort out authentication / logins. - I've written a unit test framework for CardDAV to easily allow adding unit tests for parsing server responses - Damien Caliste has started writing a unit test framework for CalDAV, and he has also investigated a variety of CalDAV bugs which are proving to be quite tricky. See you at the meeting on Monday :-) Best regards, Chris. From: Chris Adams Sent: Friday, September 09, 2016 11:55 AM To: Sailfish OS Developers Subject: CalDAV/CardDAV Contributor Meeting Hi everyone, During the recent Sailfish OS Community Meeting, I raised the topic of CalDAV/CardDAV sync plugins for discussion. These plugins provide vital functionality, but due to the complexity of the space (e.g., dozens of different server implementations, each with slightly different behaviour) coupled with resource limitations in Jolla, there have always been issues with them. I asked the community if there would be anyone interested in contributing in some way, and the response was fantastic! As a result, I have created the following wiki page: https://sailfishos.org/wiki/CalDAV_and_CardDAV_Community_Contributions. Please note that currently that SFOS wiki is not able to be edited by community members (we're still trying to figure out how to create a proper review process for edits, and also whether or not it makes sense to provide single-sign-on between Mer and SFOS wiki, etc) but if you have any changes you'd like to make, please send them to me and I can publish them there. Also, I would like to organise a kick-off meeting in #mer-meeting on Freenode IRC this coming Monday the 12th of September at 0900 UTC (which is 7 pm Australian Eastern Standard Time, if that helps anyone else ;-) The agenda can be found in the wiki page. Everyone is welcome and invited to attend, even if you cannot volunteer to help at this point in time. If you cannot make it, don't worry, I will attach minutes from the meeting to the wiki page :-) Best regards, Chris Adams. ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] CalDAV/CardDAV Contributor Meeting
Syyyeyeysseyeys On Thu Oct 6 12:01:01 2016 GMT+0200, Chris Adams wrote: > Hi everyone, > > Sorry for top-posting, but I'm on an Outlook Web Access client, and it > doesn't do quoting. > > This is just a reminder that this coming Monday the 10th of October we have > another CalDAV/CardDAV Contributor Meeting at 0900 UTC. The agenda can be > found: > https://sailfishos.org/wiki/CalDAV_and_CardDAV_Community_Contributions#10.2F10.2F2016_Meeting > > Everyone is welcome to attend, even if you are unable to actively contribute > at this time. > > Some highlights from the last month of collaboration: > - we have a test VM set up in the Mer infra, plan is to install > CalDAV/CardDAV services on it ASAP but first we need to sort out > authentication / logins. > - I've written a unit test framework for CardDAV to easily allow adding unit > tests for parsing server responses > - Damien Caliste has started writing a unit test framework for CalDAV, and > he has also investigated a variety of CalDAV bugs which are proving to be > quite tricky. > > See you at the meeting on Monday :-) > > Best regards, > Chris. > > > From: Chris Adams > Sent: Friday, September 09, 2016 11:55 AM > To: Sailfish OS Developers > Subject: CalDAV/CardDAV Contributor Meeting > > Hi everyone, > > During the recent Sailfish OS Community Meeting, I raised the topic of > CalDAV/CardDAV sync plugins for discussion. These plugins provide vital > functionality, but due to the complexity of the space (e.g., dozens of > different server implementations, each with slightly different behaviour) > coupled with resource limitations in Jolla, there have always been issues > with them. I asked the community if there would be anyone interested in > contributing in some way, and the response was fantastic! > > As a result, I have created the following wiki page: > https://sailfishos.org/wiki/CalDAV_and_CardDAV_Community_Contributions. > Please note that currently that SFOS wiki is not able to be edited by > community members (we're still trying to figure out how to create a proper > review process for edits, and also whether or not it makes sense to provide > single-sign-on between Mer and SFOS wiki, etc) but if you have any changes > you'd like to make, please send them to me and I can publish them there. > > Also, I would like to organise a kick-off meeting in #mer-meeting on Freenode > IRC this coming Monday the 12th of September at 0900 UTC (which is 7 pm > Australian Eastern Standard Time, if that helps anyone else ;-) > > The agenda can be found in the wiki page. > > Everyone is welcome and invited to attend, even if you cannot volunteer to > help at this point in time. > > If you cannot make it, don't worry, I will attach minutes from the meeting to > the wiki page :-) > > Best regards, > Chris Adams. > > > ___ > 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] CalDAV/CardDAV Contributor Meeting
Martin Kolman kirjoitti to lokakuuta 6 15:51:12 2016 GMT+0300: > Syyyeyeysseyeys > Wot, a cat ran over your keyboard...? :) - juice - -- Lähetetty Jollastani ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
[SailfishDevel] SDK version 1609 (2.0.4) is released to Early Access
Hello, Today (Oct 6th) at 17:00 UTC we have published new installers and repositories of the Sailfish OS SDK. This SDK release is called 1609 and it matches Jolla Release 2.0.4. >From now on the SDK releases will be in sync with the early access releases of >Sailfish OS. It means, that developers can now choose between the SDK update >intervals. By switching to the Early Access SDK developers will get SDK >updates in sync with the Sailfish OS early access releases. Otherwise, as >before, they will get the SDK updates in sync with the official public >Sailfish OS releases. Please, read the following notes about the Early Access SDK: - By using the Early Access SDK developers can test their Sailfish OS apps approximately a week before the Sailfish OS release is made public - During the early access time the Early Access SDK should not be used for submitting apps to the Jolla Harbour - The installers for this release of the SDK are available at http://sailfishos.org/wiki/Application_SDK_Early_Access#Latest_Early_Access_SDK_Release - Instructions for adding the early access repository into the SDK can be found from http://sailfishos.org/wiki/Application_SDK_Early_Access#Receiving_Early_Access_SDK_Updates_Automatically If you add the early access repository into your SDK and have an older beta release of the SDK, you should see an update notification in the Sailfish OS IDE. Otherwise, you will see an update notification in the Sailfish OS IDE, when the Jolla Release 2.0.4 is publicly available to all users. SDK content matches Jolla Release 2.0.4.13 (Fiskarsinjoki). Please see below for detailed information of the changes. A couple of things you should be aware of: - As before, in this update the build engine, emulator and targets are reinstalled 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. - Any 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 to select the correct kit in the project configuration step. Both ARM and i486 kits are available. - 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 Beta-Qt5 known issues list. Release Content SDK IDE (Qt Creator) - Qt Creator updated to version 4.0.1 - Official Turing Phone support - Updates to Emulator mode switching - Refreshed API documentation available in the Help mode (Ctrl+7) in Qt Creator to Jolla release 2.0.4.13 level SDK Build engine - Build targets refreshed to Jolla release 2.0.4.13 level - Harbour RPM validator updated Emulator - Emulator packages refreshed to Jolla release 2.0.4.13 level - Fixes to matching Emulator UI assets with the corresponding device UI assets If you have any questions, feel free to either send an email to this mailing list: devel at lists.sailfishos.org, write it up in http://together.jolla.com and tag your issue with 'sdk' or send an e-mail to developer-care at jolla.com. Happy hacking, Jolla SDK Team ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] SDK version 1609 (2.0.4) is released to Early Access
Does it require virtualbox? I am having Blue Screen of Death under Win10 with the anniversary update On Thursday, 6 October 2016, Jarkko Lehtoranta wrote: > Hello, > > Today (Oct 6th) at 17:00 UTC we have published new installers and > repositories of the Sailfish OS SDK. This SDK release is called 1609 and it > matches Jolla Release 2.0.4. > > From now on the SDK releases will be in sync with the early access > releases of Sailfish OS. It means, that developers can now choose between > the SDK update intervals. By switching to the Early Access SDK developers > will get SDK updates in sync with the Sailfish OS early access releases. > Otherwise, as before, they will get the SDK updates in sync with the > official public Sailfish OS releases. > > Please, read the following notes about the Early Access SDK: > - By using the Early Access SDK developers can test their Sailfish OS apps > approximately a week before the Sailfish OS release is made public > - During the early access time the Early Access SDK should not be used for > submitting apps to the Jolla Harbour > - The installers for this release of the SDK are available at > http://sailfishos.org/wiki/Application_SDK_Early_Access# > Latest_Early_Access_SDK_Release > - Instructions for adding the early access repository into the SDK can be > found from http://sailfishos.org/wiki/Application_SDK_Early_Access# > Receiving_Early_Access_SDK_Updates_Automatically > > If you add the early access repository into your SDK and have an older > beta release of the SDK, you should see an update notification in the > Sailfish OS IDE. Otherwise, you will see an update notification in the > Sailfish OS IDE, when the Jolla Release 2.0.4 is publicly available to all > users. > > SDK content matches Jolla Release 2.0.4.13 (Fiskarsinjoki). Please see > below for detailed information of the changes. > > A couple of things you should be aware of: > - As before, in this update the build engine, emulator and targets are > reinstalled 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. > - Any 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 to select the correct kit in the project > configuration step. Both ARM and i486 kits are available. > - 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 Beta-Qt5 known issues list. > > > Release Content > > SDK IDE (Qt Creator) > - Qt Creator updated to version 4.0.1 > - Official Turing Phone support > - Updates to Emulator mode switching > - Refreshed API documentation available in the Help mode (Ctrl+7) in Qt > Creator to Jolla release 2.0.4.13 level > SDK Build engine > - Build targets refreshed to Jolla release 2.0.4.13 level > - Harbour RPM validator updated > Emulator > - Emulator packages refreshed to Jolla release 2.0.4.13 level > - Fixes to matching Emulator UI assets with the corresponding device UI > assets > > If you have any questions, feel free to either send an email to this > mailing list: devel at lists.sailfishos.org, write it up in > http://together.jolla.com and tag your issue with 'sdk' or send an e-mail > to developer-care at jolla.com. > > Happy hacking, > Jolla SDK Team > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > -- Sent from Gmail Mobile ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] SDK version 1609 (2.0.4) is released to Early Access
Yes it's based on virtualbox, and works flawlessly on my win10 anniversary. 06 окт. 2016 г. 20:35 пользователь "Iosif Hamlatzis" написал: > Does it require virtualbox? I am having Blue Screen of Death under Win10 > with the anniversary update > > On Thursday, 6 October 2016, Jarkko Lehtoranta < > jarkko.lehtora...@jolla.com> wrote: > >> Hello, >> >> Today (Oct 6th) at 17:00 UTC we have published new installers and >> repositories of the Sailfish OS SDK. This SDK release is called 1609 and it >> matches Jolla Release 2.0.4. >> >> From now on the SDK releases will be in sync with the early access >> releases of Sailfish OS. It means, that developers can now choose between >> the SDK update intervals. By switching to the Early Access SDK developers >> will get SDK updates in sync with the Sailfish OS early access releases. >> Otherwise, as before, they will get the SDK updates in sync with the >> official public Sailfish OS releases. >> >> Please, read the following notes about the Early Access SDK: >> - By using the Early Access SDK developers can test their Sailfish OS >> apps approximately a week before the Sailfish OS release is made public >> - During the early access time the Early Access SDK should not be used >> for submitting apps to the Jolla Harbour >> - The installers for this release of the SDK are available at >> http://sailfishos.org/wiki/Application_SDK_Early_Access#Late >> st_Early_Access_SDK_Release >> - Instructions for adding the early access repository into the SDK can be >> found from http://sailfishos.org/wiki/Application_SDK_Early_Access#Rece >> iving_Early_Access_SDK_Updates_Automatically >> >> If you add the early access repository into your SDK and have an older >> beta release of the SDK, you should see an update notification in the >> Sailfish OS IDE. Otherwise, you will see an update notification in the >> Sailfish OS IDE, when the Jolla Release 2.0.4 is publicly available to all >> users. >> >> SDK content matches Jolla Release 2.0.4.13 (Fiskarsinjoki). Please see >> below for detailed information of the changes. >> >> A couple of things you should be aware of: >> - As before, in this update the build engine, emulator and targets are >> reinstalled 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. >> - Any 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 to select the correct kit in the project >> configuration step. Both ARM and i486 kits are available. >> - 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 Beta-Qt5 known issues list. >> >> >> Release Content >> >> SDK IDE (Qt Creator) >> - Qt Creator updated to version 4.0.1 >> - Official Turing Phone support >> - Updates to Emulator mode switching >> - Refreshed API documentation available in the Help mode (Ctrl+7) in Qt >> Creator to Jolla release 2.0.4.13 level >> SDK Build engine >> - Build targets refreshed to Jolla release 2.0.4.13 level >> - Harbour RPM validator updated >> Emulator >> - Emulator packages refreshed to Jolla release 2.0.4.13 level >> - Fixes to matching Emulator UI assets with the corresponding device UI >> assets >> >> If you have any questions, feel free to either send an email to this >> mailing list: devel at lists.sailfishos.org, write it up in >> http://together.jolla.com and tag your issue with 'sdk' or send an >> e-mail to developer-care at jolla.com. >> >> Happy hacking, >> Jolla SDK Team >> ___ >> SailfishOS.org Devel mailing list >> To unsubscribe, please send a mail to devel-unsubscribe@lists. >> sailfishos.org >> > > > -- > Sent from Gmail Mobile > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to devel-unsubscribe@lists. > sailfishos.org > ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] SDK version 1609 (2.0.4) is released to Early Access
Finally an upgrade of Qt Creator - jaay! :)
While the QML Profiler (on device) worked perfect with the last SDK
release, it now hard-crashes Qt Creator ("does not work anymore...")
during deployment step.
All other things are working fine (coding, debugging on device, ...).
System is Windows 10 Insider Preview Build 14936.
I hope you can fix this, because this is a really nice tool to find
performance issues in QML code...
Br,
Michael
Am 06.10.2016 19:20, schrieb Jarkko Lehtoranta:
Hello,
Today (Oct 6th) at 17:00 UTC we have published new installers and
repositories of the Sailfish OS SDK. This SDK release is called 1609
and it matches Jolla Release 2.0.4.
From now on the SDK releases will be in sync with the early access
releases of Sailfish OS. It means, that developers can now choose
between the SDK update intervals. By switching to the Early Access SDK
developers will get SDK updates in sync with the Sailfish OS early
access releases. Otherwise, as before, they will get the SDK updates
in sync with the official public Sailfish OS releases.
Please, read the following notes about the Early Access SDK:
- By using the Early Access SDK developers can test their Sailfish OS
apps approximately a week before the Sailfish OS release is made
public
- During the early access time the Early Access SDK should not be used
for submitting apps to the Jolla Harbour
- The installers for this release of the SDK are available at
http://sailfishos.org/wiki/Application_SDK_Early_Access#Latest_Early_Access_SDK_Release
- Instructions for adding the early access repository into the SDK can
be found from
http://sailfishos.org/wiki/Application_SDK_Early_Access#Receiving_Early_Access_SDK_Updates_Automatically
If you add the early access repository into your SDK and have an older
beta release of the SDK, you should see an update notification in the
Sailfish OS IDE. Otherwise, you will see an update notification in the
Sailfish OS IDE, when the Jolla Release 2.0.4 is publicly available to
all users.
SDK content matches Jolla Release 2.0.4.13 (Fiskarsinjoki). Please see
below for detailed information of the changes.
A couple of things you should be aware of:
- As before, in this update the build engine, emulator and targets are
reinstalled 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.
- Any 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 to select the correct kit in the project
configuration step. Both ARM and i486 kits are available.
- 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 Beta-Qt5 known issues list.
Release Content
SDK IDE (Qt Creator)
- Qt Creator updated to version 4.0.1
- Official Turing Phone support
- Updates to Emulator mode switching
- Refreshed API documentation available in the Help mode (Ctrl+7) in
Qt Creator to Jolla release 2.0.4.13 level
SDK Build engine
- Build targets refreshed to Jolla release 2.0.4.13 level
- Harbour RPM validator updated
Emulator
- Emulator packages refreshed to Jolla release 2.0.4.13 level
- Fixes to matching Emulator UI assets with the corresponding device UI
assets
If you have any questions, feel free to either send an email to this
mailing list: devel at lists.sailfishos.org, write it up in
http://together.jolla.com and tag your issue with 'sdk' or send an
e-mail to developer-care at jolla.com.
Happy hacking,
Jolla SDK Team
___
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
