Re: [SailfishDevel] was "Acceptable Behaviour.." --> Forum
Hi Stefano first make Wifi actually work, then invest time in building a better Stack overflow/Forum. As it is, I stopped using my Jolla as my main phone. This was mainly due to not being able to connect to wifi at work, and having to reboot every 5 days. Regards Erlend PS: Taking time to actually answer the valid questions from Filip (SIM, Opensource, etc) would also be nice. On 26.05.2014, at 09:50, Stefano Mosconi wrote: > On 26/05/14 10:21, Ruediger Gad wrote: >> Hi, >> >> just to add a bit of my opinion as well. >> >> Just a mailing list is imho not enough. >> >> Personally, I like a forum. >> Even though, due to its nature(?), it might attract more OT discussion. >> However, such OT discussion can be canalized by proper categorization, >> e.g., OT sections etc. >> Canalizing discussions into topics, e.g., hardware, software, OT, >> general, etc. is imho one nice feature of a forum. >> But other neat features had been mentioned here already as well. >> >> I think Q&A sites like stackoverflow or tjc are also very handy. >> >> Why not let the users make the decision? >> I.e., we have a mailing list and a Q&A site already, just the forum is >> missing. > > Aren't a Q&A site *and* a forum quite overlapping? > > What is missing from the current together.jolla.com that you would have in a > forum? > > Currently (to my knowledge): > * You can edit your posts afterwards > * You can have sticky posts > * You can find quickly the right [TM] answer > * You can have karma > * You cannot have sections and subsections (but you have tags) > * You can have mail notifications of posts > > Should we invest our time into making a better together.jolla.com rather than > a different platform (this is not rhetorical)? > > Stefano > ___ > 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] Mitakuuluu now full opensource application.
Hi Andrey Just some quick feedback from a fellow programmer: Mitakuuluu was the only native app that I was using on a daily basis. I hope you will keep developing it. One day when my jolla will actually be able to connect to the wifi in the office, and my two other spare time projects are finished (Android version of my 'PoBi' iOS app, and a new version of my 'offline dictionary' iOS app), your program will be the first I will have a look at :-) Regards Erlend Sent from my iPhone > On 20.04.2014, at 18:05, Andrey Kozhevnikov wrote: > > Just announcing to mailing lists my recent Mitakuuluu update. > > Now you can fork it, build yourself, make patches and send merge requests. > Contributions and ideas are welcome! > > Licensed under WTFPL, you can do whatever you want with sources, i'll be > happy if any piece of my code will help you in your own projects. > > https://github.com/CODeRUS/mitakuuluu2 > ___ > SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
[SailfishDevel] Repository Wishlist
Dear David, As a user I would like to have a repo with the following characteristics: * Guarantee that apps do not break my device by installing incompatible versions of libraries. * App Ratings, and download numbers, and ability to sort the list of apps based on these. * App comments * Easy search functionality, categories. * A clear statement that applications that “snoop on the user” are not welcome, except for sending statistics back to the repo itself. * If possible, a guarantee that the application has been audited to not “phone home”. One possible option would be that applications that use the internet could voluntarily have a “whitelist” of sites that it will connect to. That will make me trust the application more! As a developer, I would like to have a repro with the following characteristics * Clear guidelines that show what is allowed, and how to package the apps. * Example projects that are “ready out of the box”. * Automated checks that I can run before I upload the package, so that most errors are caught before upload. * Clear, timely feedback if my application is not compliant * An analytics library that I can use in my application, that would send usage statistics to the repo. All other “snooping” on the user would be disallowed. * Statistics about downloads, analytics, etc Regards, Erlend On 05.02.2014, at 16:00, David Greaves wrote: > On 04/02/14 07:40, "Thomas B. Rücker" wrote: >> My question has been lingering for a while. ( >> https://together.jolla.com/question/13605/visible-open-source-app-community-supported-by-jolla/ >> ) >> >> But during FOSDEM we had a Sailfish/Jolla Community Round-Table ( >> https://together.jolla.com/question/11303/are-you-going-to-fosdem-2014-irl-floss-meeting-in-belgium/?answer=13864#post-id-13864 >> ). This topic was brought up and seems Sailors are committed to address >> this with pushing forward towards a clean open source app repository >> with community QA and easy on-device access after enabling developer mode. > > That's my personal goal, yes. > > For those who don't know, I run the infra and OBS for Mer - I used to run the > community OBS and other infra for MeeGo too. I am a sailor - but today I'm > mailing as a community guy. > > I setup Chum as a place to build Jolla apps on an OBS. It just works. There is > no fancy storefront or BOSS integration. We need that. > > I'd like to see some public docs on the Chum rules and governance so that we > can > reasonably expect Jolla to trust us to do a professional job. I know that they > worry about reputation and customer experience. So do I. > > I don't think we need full automation of the checks yet - but I do think we > can > clearly state the boundaries: open source only; auditability; community QA... > > I'd like to see what our target is from a user perspective ... eg how do we > make > sure users can upgrade their devices. It's a technically difficult problem. We > may well need to ask Jolla for hooks into SailfishOS ... but luckily we may > also > be able to write those hooks in Mer/Nemo and have Jolla just get them. > > I also recall that community QA was not terribly effective - I think this > needs > adressing. > > I used "Chum" as the repo title (it's the bloody fish guts you use to attract > sharks!) - I'm not sure it's a good name but there are plenty of attacks :) > >> This would provide something like Maemo Extras and would be community >> QA'd to ensure the apps don't pose major problems when installed. On the >> other hand it would provide an easy middle ground for apps that don't >> fit into harbour for various reasons (API calls, dependencies, etc.). > > Yes - I'd like to explore how we can add one or more library areas to devices > for sets of shared libraries. Eg I use bullet physics engine in my 3D Dice > game > - I don't want to have to ship it. But how do we cope when bullet v3 comes > out? > >> It will be backed by an OBS project on Mer community OBS, which has >> Sailfish targets. OBS has come a very long way since we've seen it >> first. I've personally had several apps build out of the box by just >> _clicking_: >> * create package >> * source provision through tar_git >> If the app builds on a clean SDK, then it's highly likely to build out >> of the box also on OBS. > > Good. We need more docs though. > >> You may now say "what about openrepos?". They have chosen to be a site >> for one-click RPM hosting repositories with no QA. Despite their best >> efforts this approach has led to significant problems. Also it does >> binary only uploads and thus non-free/closed applications and no >> traceable chain from source to binary. >> That said, if the openrepos client (warehouse) passes community QA it >> will for sure be included in the community repository. Thus allowing >> users to install it easily, if they so wish. We're not hostile towards >> it, it just doesn't offer the level of trust to be a viable avenue for a >> default community r
Re: [SailfishDevel] Is there a bug tracker?
Hi all, I agree completely. Also, for me it is not always easy to understand in which component the problem is, should I report it to this list, or to the mer, or to the nemo team? So I would go even further and say that not only would it be good to have a Sailfish bug tracker, but that it would be helpful if I could report all bugs to it, and somebody will then decide if it is a Sailfish problem, or a problem in one of the underlying libraries. Regards Erlend On 07.08.2013, at 12:53, christopher.l...@thurweb.ch wrote: > Hi > > on the Sailfish Support Page: > > " > Bug Tracking Tool > We are in a phase of rapid development, so a formal bug tracking tool is not > the best solution yet. Nevertheless, we would like to hear your feedback via > the mailing list. > " > > This always struck me as a little bit weak / weird. I would have thought that > a small team working hard on a fast developing project needs a bug tracking > tool just as much as any other, possibly even more so. But I agree, it does > not need to be formal, but there should be something to ensure that issues > don't get lost. > > This list is great for discussing stuff we find. As we are all learning, many > of our problems may not actually be caused by bugs, rather by mistakes we are > making. But if after a bit of discussion it is decided that the behaviour is > down to a bug, then it would be great to be able to park the issue somewhere > knowing it won't get lost. > > Chris > > > Zitat von "Thomas B. Rücker" : > >> On 08/07/2013 10:17 AM, Putze Sven wrote: >>> Hi there, >>> >>> is there a bugtracker for reported issues or new issues anywhere around >>> (Sailfish OS / SDK / Installer)? Or is everything handled via this list >>> here so far? >> >> For the first alpha release there was a significant collection of known >> issues listed on the page. Bugs are mostly reported here and on IRC >> (although here is better for documentation purposes). >> Issues that can be clearly identified to have originated in Mer or Nemo >> are tracked here: >> - https://bugs.merproject.org/ >> - https://bugs.nemomobile.org/ >> >> I'm not entirely sure how Jolla owned bugs are prioritized. The one I >> reported with one of my first mails to the list in February (and got >> ack'd by Jolla) is still there. >> >> Cheers >> >> Thomas >> ___ >> SailfishOS.org Devel mailing list >> > > > ___ > SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] sqlite "out of memory" error
Hoi Chris
I will use the localstorage for my settings, so a blog entry would very much be
appreciated :-)
My main DB is however opened in C++, to do this I use the QSqlDatabase class.
it then fails with out of memory on open(). In Alpha 1 it worked perfectly.
QSqlDatabase db = QSqlDatabase:addDatabase("QSQLITE");
db.setDatabaseName(pathToDB);
bool opened = db.open();
I checked the VM memory, and its was 1 GB, so it should be enough.
This evening I will try to increase it, but I cannot understand why just
opening the DB should use so much memory. Does anybody know how I can debug
this, or if there are some SQLITE specific options that I must set?
Opening the db in the sqlite3 command line client works in the simulator, so
I'm confident that the DB is not corrupted.
Greetings from Zürich
Erlend
On 05.08.2013, at 10:23, christopher.l...@thurweb.ch wrote:
> Sali Erlend
>
> Sorry, pressed send too soon on my last ...
>
> How exactly are you trying to access Sqlite? via QtQuick LocalStorage API, or
> by some other means?
>
> The error message you quote sounds as though the Emulator is having problems
> opening a 1.7 GB Database due to memory problems. I think the memory
> allocated to the Emulator VM is fairly low, so you might try increasing it.
>
> In the meantime I have just managed to migrate LocalStorage DB to Qt5. I had
> to make a few changes to do so, and tore quite a bit of hair out until I hit
> the correct solution. I can provide examples if it helps (and will update my
> blog during the day)
>
> Chris
>
> p.s Hoi sounds Swiss (or Swiss aware ..)
>
>
> - Weitergeleitete Nachricht von christopher.l...@thurweb.ch -
> Datum: Mon, 05 Aug 2013 10:16:04 +0200
> Von: christopher.l...@thurweb.ch
> Betreff: Re:sqlite "out of memory" error
>An: "Erlend Boe"
>Cc: devel@lists.sailfishos.org
>
> Zitat von "Erlend Boe" :
>
>> Hoi Chris
>>
>> after using the patch, it is also working for me.
>>
>> However, I have some other problems:
>> * opening my sqlite DB (1.7 GB) fails with QSqlError(-1, "Error opening
>> database", "out of memory")
>> * debugging fails with "connection to remote server failed:
>> tcp:localhost:1: Bad file descriptor. (although the application Output
>> shows "Listening on port 1")
>>
>> opening the db worked fine in the previous release.
>> Does anybody know what would cause this problem, or how I can debug it?
>>
>>
>> I'm using a mac with osx 10.8.4, and virtualbox 4.2.16.
>> I can log on to the simulator with: ssh -i
>> ~/SailfishOS/vmshare/ssh/private_keys/1/root root@localhost -p 2223
>>
>> Regards
>> Erlend
>>
>>
>>
>> On 04.08.2013, at 18:56, christopher.l...@thurweb.ch wrote:
>>
>>> Hi All
>>>
>>> Just a quick note to say that
>>>
>>> Q_DECL_EXPORT int main(int argc, char *argv[])
>>> {
>>> QScopedPointer app(Sailfish::createApplication(argc,
>>> argv));
>>> QScopedPointer view(Sailfish::createView());
>>> view->rootContext()->setContextProperty("cppproperty", "Hello world");
>>> Sailfish::setView(view.data(), "main.qml");
>>> Sailfish::showView(view.data());
>>> return app->exec();
>>> }
>>>
>>> works (so far) without error if Lucien's patch to sailfishapplication.cpp
>>> is applied. This can be found here:
>>> https://lists.sailfishos.org/pipermail/devel/attachments/20130802/2367c686/attachment.cpp
>>>
>>> Chris
>>>
>>> - Weitergeleitete Nachricht von christopher.l...@thurweb.ch -
>>> Datum: Sun, 04 Aug 2013 18:36:06 +0200
>>> Von: christopher.l...@thurweb.ch
>>> Betreff: Re: [SailfishDevel] Alpha 2: passing simple properties from
>>> main.cpp to qml: A bug?
>>> An: "Lucien XU"
>>> Cc: devel@lists.sailfishos.org
>>>
>>> Salut Lucien
>>>
>>> Maybe it is clearer with Code examples
>>>
>>> I was doing this, which gives me an error, but seems to work!
>>>
>>> Q_DECL_EXPORT int main(int argc, char *argv[])
>>> {
>>> QScopedPointer app(Sailfish::createApplication(argc,
>>> argv));
>>> QScopedPointer view(Sailfish::createView("main.qml"));
>>> view->rootContext()->setContextProperty("cppproperty", "Hello world");
>>> Sailfish::showView(view.data());
>>> return app->exec();
>>> }
>>>
>>> You suggest I could this:
>>>
>>> Q_DECL_EXPORT int main(int argc, char *argv[])
>>> {
>>> QScopedPointer app(Sailfish::createApplication(argc,
>>> argv));
>>> QScopedPointer view(Sailfish::createView());
>>> view->rootContext()->setContextProperty("cppproperty", "Hello world");
>>> Sailfish::setView(view.data(), "main.qml");
>>> Sailfish::showView(view.data());
>>> return app->exec();
>>> }
>>>
>>> ..but will then run into your template error:
>>> file:///usr/share/setContextPropertyDemo/main.qml: File not found
>>>
>>> Maybe the qmlRegister**Type is the best approach after all. The downside is
>>> (unless I have missed something) that I will then have to create a class
>>> for my property, whereas with the setContextProperty I can use a string
>
Re: [SailfishDevel] Persistent storage
Hei Markus, It is already included in the simulator. All I had to do was to add QT+=sql to the qmake project file. Erlend Sent from my Jolla ;-) On 29.05.2013, at 22:23, Joseph Crowell wrote: > SQLite is in use on a wide range of applications. I would assume it would be > bundled on the device along with the other core Qt plugins. > > On 5/30/2013 6:18 AM, Markus Svensson wrote: >> Hi Chris, >> >> Thank you for your reply. >> >> I believe QT Quick uses SQLite under the hood as well, but I have not had to >> add any extra packages so far. But then I haven't gotten very far with my >> app yet... >> >> Is it known if SQLite will be available on production devices, or will each >> app have to bundle it separately? >> >> Thanks! >> >> Skickat från min iPhone >> >> 29 maj 2013 kl. 21:31 skrev christopher.l...@thurweb.ch: >> >>> Hi Markus >>> >>> SQLite works for me, but you need to install the packages to the SDK and >>> Emulator first. >>> >>> Grüsse >>> >>> Chris >>> >>> Zitat von "Markus Svensson" : >>> Hi, What is the preferred way of doing persistent database type storage in a Sailfish OS application? I'm thinking of using QT Quick's Offline Storage API - will this work, or is there a better way? Thanks! Regards, Markus ___ SailfishOS.org Devel mailing list >> ___ >> SailfishOS.org Devel mailing list > > ___ > SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
