Looking for engin.io replacement -joining our effort initiative
-
Another but related topic : I have seen on the wiki, that it is encouraged to request for Qt playground project creation even if the project is in early stage. I think, that's would be great in this case so we could have a common repository to collaborate on a great plugin to give Qt App backend services.
Do you know how to proceed for creating playground projects ?
So far, I only sent a request on the development mailing list but I don't know what are the next steps... -
@Charby
Hello,As far as I understood the PIMPL implementation, adding the private class when my plugin design would be mature enough should be a straightforward process. But if you think, I am missing something please tell me, so I could integrate PIMPL right away.
Mostly it's very straightforward process, however there are few "tricks" that are usually closely associated with the PIMPL idiom. I've used two of them in my project (sourced in my previous post), i.e. private slots and private object constructor. The private slots can be substituted with lamda functions if you're willing to enforce C++11. The second one can be implemented at a later stage, but I personally would detest refactoring a full working piece of code only to ensure that the user won't be able to create an object of given class. These two help with the design - not exposing anything besides the barebone interface, but you could certainly skip them (in most cases), or at least defer the[ir] implementation. I hope this is helpful.
Kind regards.
-
@Charby said:
Do you know how to proceed for creating playground projects ?
So far, I only sent a request on the development mailing list but I don't know what are the next steps...The wiki page says "wait for the approval of a maintainer on the mailing list", so the next step is to wait for a response, but as it's been a long time, a bump could help, maybe.
On an unrelated note, my pull request was merged into Parse Server today, so +1 to the Parse Server project. There's now a 100% features parity between the Engin.io REST API and the Parse Server API (at least for the subset I'm using, but Id say I'm using all the most common methods).
-
Just a short post to give feedbacks...
Unfortunately I haven't had too much time to continue working on the BaaS plugin lately, here is the project status :- Authentification : partly done (miss the social linking)
- Object (alias collection) management : done
- JSonModel : partly done (read-only only for now)
- Adaptative QML List view : done
- Files : work in progress, I should have it completed by tomorrow hopefully
As always, comments are welcome !
-
Hi @Charby,
I've just seen this post now. How did your integration go so far?There is a Qt optimized cloud/BaaS alternative: you can look at V-Play Game Network: http://v-play.net/game-network/
Albeit its name, it is not only for games but also for apps.See here for a list of useful components with their Qt API reference:
- http://v-play.net/doc/vplay-webstorage/ - use WebStorage as a cloud-based key/value store. Its data gets synced across devices & platforms.
- http://v-play.net/doc/vplay-vplaygamenetwork/ - GameNetwork supports social login from Facebook so data can be synced across devices & platforms with a single user.
- http://v-play.net/doc/vplay-vplaymultiplayer/ - The multiplayer components supports a chat, push notifications and a friend system. You can add a QML-stylable messenger to your app with this component.
You can also just use some parts of these components, and freely mix it for example with Firebase.
Cheers, Chris
-
Hi @feldifux,
Actually I stopped working on this project for some time now. Currently the API is working fine with Parse server as datastorage. Support for social login and push notifications are missing.
V-Play Albeit sounds very nice !
I will definitely have a try the next time I would need social login or notifications support. Thanks