Re: [SailfishDevel] The missing HelloWorld. Wizard included
Hi, one thing I am trying to wrap my head around is the usage of a project for different devices/operating systems (why? because a living ecosystem needs to attract more developers and those coming from other platforms will come if they already use Qt or see a chance in switching to Qt but they sure don't want a maintenance nightmare). IMHO something like the rpm folder should go at least one directory level down, so one could differentiate between the brands or operating systems at top level. But so far any tests with rpm in another level broke apart. I am not sure if something is hardcoded here or if I simply don't know where to look? In such an attempt I would rename the folder src to sailfishos or something similar. What's your thoughts about that? BR. Sven On 30.11.2013, at 19:06, Artem Marchenko artem.marche...@gmail.com wrote: Hi All *Short version* Go check this out and contribute corrections - https://github.com/amarchen/helloworld-pro-sailfish *Long version* Just an app templates make my heart cry. Changing them to the proper structure is pain every time you go beyond just a helloworld. So I created a Helloworld Pro for Sailfish. Something that has minimal UI, but proper project structure and a couple of UI and non UI QML tests (includes src, test folders, multipackage .yaml/spec, proper 86x86 icon, etc) and passes harbour acceptance criteria (pending for now). And then I added a wizard script that renames everything to whatever project name you like to help you get started with MyCoolApp instead of helloworld-pro-sailfish Wizard is a bash script validated on Mac only, because that's the platform I use. Similar scripts for Windows and other corrections/improvements (e.g. adding simple app cover) are very welcome via pull requests. You will find the project at https://github.com/amarchen/helloworld-pro-sailfish If you want to do more with QML testing that I greatly encourage, this old presentation is still valid - www.slideshare.net/AgileArtem/test-drivingqml-12941898 Enjoy! Cheers, Artem. -- Artem Marchenko http://agilesoftwaredevelopment.com http://twitter.com/AgileArtem ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
[SailfishDevel] QA app rejected for non absolute icon path
Hi sailors and maybe QA people, I submitted two projects to Jolla Store QA and both where rejected for the following reason: /Validate desktop file/ /Desktop file ./usr/share/applications/harbour-cubetimer.desktop is missing valid Icon declaration!/ // /just:/ /Icon=harbour-cubetimer/ // /no absolute path!/ But I can't understand what's wrong, I used Artems modification in *.pro file to fit the latest Jolla harbour rules. The path is right in my *.desktop file in my project, also it is right in the RPM package, as you can check also in the projects git. https://github.com/AlphaX2/CubeTimer_SailfshOS_Qt5/blob/master/harbour-cubetimer.desktop https://github.com/AlphaX2/CubeTimer_SailfshOS_Qt5/tree/master/RPMS So any ideas or hints whats wrong? Thank you very much in advance. Gabriel ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] community thoughts on app security
Hi Artem and all, 2) Sandboxes are limiting, but matter. It is way more difficult to freeze to death or misuse iPhone than Android. That probably goes against Mer/Sailfish philosophy though. But a sandbox must not be a bad thing per se. We could learn a lot from the app bundle file structure from the Apple universe (OSX and iOS). For those who fear sandboxes like the devil: it should be possible to get more permissions on the device, via policy, manifest whatever you want to call it. This way a SailfishOS device could benefit from the security, a sandbox provides as a default but developers and users would not be limited to it. This also raises questions regarding filesystem access, there is already another thread about that topic. And there are a lot of ways to implement such a sandbox. BR. Sven ___ SailfishOS.org Devel mailing list
[SailfishDevel] QtCreator quirk
Hi all, with the usual QtCreator from the Qt project I have not experienced that but with the one in the SDK there often stays the progressbar named Parsing in the bottom right corner after loading a project. On top it has the color red which indicates an error but everything works just fine. BR. Sven ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] community thoughts on app security
Or maybe just leave it to the user, whether to use a sandbox or not? (set the default behavior and make override rules) -- Marcin 2013/12/1 Sven Putze sailfish...@hardcodes.de 2) Sandboxes are limiting, but matter. It is way more difficult to freeze to death or misuse iPhone than Android. That probably goes against Mer/Sailfish philosophy though. Yeah, I would say properly tested applications community feedback are enough and no artificial limitations are needed. :) But how deep can a tester dive into the app? Maybe it goes bad two weeks after first usage. BR. Sven ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
[SailfishDevel] Developing with SailfishOS - a short introduction
Hi there, first of all: this is far from complete and basically just a skeleton yet. Nevertheless I have started to write down a howto for SailfishOS development. Criticism, suggestions, bugfixes, contribution wanted! https://github.com/hardcodes/developwithsailfishos BR. Sven ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Developing with SailfishOS - a short introduction
Hi Sven Github won't display the pdf, it's too big ... Looking forward to reading your idea; the more of us talking about Software Engineering the better! grüsse aus der Schweiz (mit Schnee) Chris Zitat von Sven Putze sailfish...@hardcodes.de: Hi there, first of all: this is far from complete and basically just a skeleton yet. Nevertheless I have started to write down a howto for SailfishOS development. Criticism, suggestions, bugfixes, contribution wanted! https://github.com/hardcodes/developwithsailfishos BR. Sven ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] The missing HelloWorld. Wizard included
I see the goal for the project in helping with the correct structure and practices from the very beginning. IMHO one minuscule C++ object integrated into QML can improve HelloWorld if: 1. It sits inside a properly structured C++ part of a project 2. Has at least one unit-test located in the proper places 3. Common test script executed both QML and C++ test 4. C++ part is easily throwable away for those who want just QML .. and probably it should really be just an individual C++ class, building en engine library is beyond the scope. Or is it not? A C++ test lib on the other hand has to be a stand alone project. I did C++ Qt and mix of C++/QML code in the past, but mostly I am a QML person. If somebody with more experience on C++ chips in, it would've been great. Focus is, again, on promoting the proper structure and practices, so it'd be cool to have input from those who are into these. Cheers, Artem. On Sun, Dec 1, 2013 at 2:23 PM, Sven Putze sailfish...@hardcodes.de wrote: Hi Artem and all, well, I don't have developed for Android yet and I don't intend to do so :-) Regarding this example, I was thinking if extending this one or create a bigger one as 2nd dive-in option. In such a bigger approach one could provide something like a Sailfish independent business model (the calculator) and maybe a state machine (maybe even MSM from boost, which would raise many question worth getting answered) that keeps track of the actions that can be done to the model. This way we could provide a C++ class that uses Q_PROPERTY but does know nothing about the model, just drives the state machine and have more or less stupid QML files. As an extra cherry on top a non blocking approach. IMHO this would be a great learning experience, not just for new SailfishOS developers. If this one or two example reach a more or less stable state, I could contribute the needed QtCreator Wizards, so that every developer can just start with a pre-organized code stub. BR. Sven On 01.12.2013, at 12:42, artem.marche...@gmail.com wrote: Hi Sven and all I was thinking similar myself and I am migrating too. Just from Symbian-Meego-desktop Qt, not from iOS. And src/test folder structure is standard in Qt world. It annoyed me a lot that I couldn't easily go to this structure from the Creator wizard. Plus just helloworld encourages no-tests development. That is not my dev style and I want to promote test-driven development and unit-testing. As for RPM folder, I was thinking where to put it and it was actually moving between src and top level. It ended up in the top level, because it is, well, a common thing for both src and test subprojects. Wikipedia project that uses same template has even fake subpackage also for grabbing files that annoy harbour check script (unused Qt Quick Test files from an external submodule). That said i'd very happy if you fork a project and make it better suitable for, say, Android people - the project is in public domain just for that. You can even resell the template if u manage :) Cheers, Artem. From: Putze Sven Sent: Sunday, December 1, 2013 11:55 To: Sailfish OS Developers Reply To: Sailfish OS Developers Subject: Re: [SailfishDevel] The missing HelloWorld. Wizard included Hi, one thing I am trying to wrap my head around is the usage of a project for different devices/operating systems (why? because a living ecosystem needs to attract more developers and those coming from other platforms will come if they already use Qt or see a chance in switching to Qt but they sure don't want a maintenance nightmare). IMHO something like the rpm folder should go at least one directory level down, so one could differentiate between the brands or operating systems at top level. But so far any tests with rpm in another level broke apart. I am not sure if something is hardcoded here or if I simply don't know where to look? In such an attempt I would rename the folder src to sailfishos or something similar. What's your thoughts about that? BR. Sven On 30.11.2013, at 19:06, Artem Marchenko artem.marche...@gmail.com wrote: Hi All *Short version* Go check this out and contribute corrections - https://github.com/amarchen/helloworld-pro-sailfish *Long version* Just an app templates make my heart cry. Changing them to the proper structure is pain every time you go beyond just a helloworld. So I created a Helloworld Pro for Sailfish. Something that has minimal UI, but proper project structure and a couple of UI and non UI QML tests (includes src, test folders, multipackage .yaml/spec, proper 86x86 icon, etc) and passes harbour acceptance criteria (pending for now). And then I added a wizard script that renames everything to whatever project name you like to help you get started with MyCoolApp instead of helloworld-pro-sailfish Wizard is a bash script validated on Mac only, because
Re: [SailfishDevel] Developing with SailfishOS - a short introduction
On 01/12/13 15:18, Sven Putze wrote: Hi there, first of all: this is far from complete and basically just a skeleton yet. Nevertheless I have started to write down a howto for SailfishOS development. Criticism, suggestions, bugfixes, contribution wanted! https://github.com/hardcodes/developwithsailfishos Hi Sven This is good stuff - thanks. May I make a suggestion though; please consider using something other than LaTeX as the master for the content. I like LaTeX a lot and in fact the pdf version of the User Guide http://jolla.com/guide/ is produced using LaTeX. However by compromising on layout control and using a simpler markup language we were able to make a nice HTML version *and* make it easy to translate as well as creating the LaTeX version. I actually used org-mode [1] as my markup because a) I know it and use emacs and b) it supports a per-publish-format options which let me tailor the LaTeX macros and CSS output; but in retrospect I think Markdown may have been a better choice Eg this is the original source for some of a chapter from http://jolla.com/guide/#text-3 and it shows a couple of per-output tweaks as well as some comment in the code :: * Lock, Home, Launcher and Events The way your Jolla uses the screen is different - there are no fixed buttons or status areas and the whole screen is available for your apps. #+ATTR_LATEX: :macro \includegraphics #+ATTR_HTML: :class float_img file:img/wf-homelock.png Jolla's main screen has three areas you get to by pulling up and down : they're called Lock, Home and Launcher. The Events screen lists all your notifications and you can access it from everywhere using a swipe gesture starting from the bottom. You arrive at Lock when you wake your Jolla (it's easy to recognise as it shows the time). From here you pull up to see Home (showing your running apps and four useful app icons). Pull up again to see the app icons for all your other apps. Keep pulling down to go back. When you click the power button, you see Lock, so let's start there. # This lets the big image above appear on the left of the page in the HTML and # stops the following headings from looking wrong #+begin_html br style=clear:both; / #+end_html ** Lock screen and icons Lock Apart from the clock, Lock shows if you've missed any calls, texts, emails and so on. It also tells you about updates and other notifications - it's generally an information screen with some useful shortcuts in the menu. So, what can you do here? Quite a bit : * Quickly see if there are any events and notifications. * If you Swipe up (not Pull up) the Events view will reveal more information about the notifications. * Pull up a little to check battery level and network status. * Pull down a little to see the date at the bottom of a Pulley menu. * Pull down more to quickly (un)silence the sounds, and get to the phone, camera or settings. * After you've chosen some favourite Ambiences, swiping from the side lets you pick a favourite Ambience, which changes your ringtones and sounds too. * Pull up more to get to Home. If you're using the [[Device lock][device lock]] to stop people seeing personal information on your device, your Jolla won't respond to some of these actions until you unlock it. To do that just pull up and you see the unlock screen where you can enter your unlock code. #+BEGIN_QUOTE * When you leave your Jolla on the Lock screen screen it goes back to sleep quite quickly. * If Swipe from the side doesn't work, then set some favourite Ambiences from your photos in Gallery. #+END_QUOTE (nb ... for various reasons someone decided to get the HTML 'fixed' by a web-shop so it's a bit broken :) - it looks much better straight out of the convertor) As you can see this will really lower the barrier to contributing to the document and to translating it. If you choose to use org-mode then let me know as I will be automating the batch processing of the content into HTML and pdf. David [1] http://orgmode.org ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Developing with SailfishOS - a short introduction
Hi Sven Have now downloaded. Lots of good content, but I need to read through it a few more times to comment in detail. One thing that immediately occurs to me is: 2.3 Linux While it is not supported, an instalation of Sailfish within a Linux VM hosted on OSX works quite happily. It is some months since I did it (first sDK version), but I was able to install Lubuntu on VMWare Fusion hosted by OSX, and then install VirtualBox and the Sailfish SDK into that. The only problems I had could be replicated on a bare-metal install of Lubuntu. mfg Chris Zitat von Sven Putze sailfish...@hardcodes.de: Hi there, first of all: this is far from complete and basically just a skeleton yet. Nevertheless I have started to write down a howto for SailfishOS development. Criticism, suggestions, bugfixes, contribution wanted! https://github.com/hardcodes/developwithsailfishos BR. Sven ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
[SailfishDevel] Does Sailfish support PyQt5?
Hello,I am a developer of python and I know that Sailfish support Qt with C++, but I am not familiar with C++,So I want to know that if Sailfish support PyQt5 ? Thanks :) ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Does Sailfish support PyQt5?
No it's not really supporting PyQt5, at the moment - in Jolla Store - are only Qt/QML apps with C++ allowed, but it is planned to support PyOtherSide from Thomas Perl. This allows to use a Python backend, with much better performance. As far as I know it's not very hard to understand and use it. Learn more at: http://thp.io/2011/pyotherside/ Gabriel. Am Sonntag, den 01.12.2013, 22:27 +0800 schrieb Ye Zetao: Hello,I am a developer of python and I know that Sailfish support Qt with C++, but I am not familiar with C++,So I want to know that if Sailfish support PyQt5 ? Thanks :) ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
