achipa

5 ms·

1.
by achipa 12y ago
There is no difference compared to a web page - the permissions are still handled server-side, I'm just relaying the events via DDP.
2.
by achipa 12y ago
Looks nice - Meteor natively speaks DDP so it makes most sense to use when talking to Meteor, but for other back-ends I will certainly consider WAMP! (no reason why this principle could not be applied to other back-ends hooking into the sam
3.
by achipa 12y ago
This is not the same thing by a long shot - you cannot force a Google Play update, and that update will take hours or days to trickle down to the users. What we're talking about is that the application updates itself instantly , even
4.
by achipa 12y ago
AFAIK The reactive part is not that easy to with Mysql et al - sure, you can hack around stored procedures, UDF and such, but it's far from being elegant. If you "think in SQL", then of course nosql seems to make everything d
5.
by achipa 12y ago
Just wondering - what auto-update mechanisms are we talking about when it comes to native apps?
6.
by achipa 12y ago
Performance-wise Qt is quite good, but still comes up a bit short on the Widget quality and consistency side - this is where project like my native component-wrappers come in to the story (shameless plug - http://achipa.blogspot.
7.
by achipa 12y ago
Yes, I'm using Asteroid to talk DDP/JSON with the rest of the Qt app. In the example, I'm using models (think MVC) and updating that model, which then automagically updates the UI. I'm not (yet) pushing the QML via Meteo
8.
by achipa 12y ago
I used a Chrome extension - Screencastify ( https://www.screencastify.com/ )
9.
by achipa 12y ago
In all honesty, Qt has come a long way since 2012 - QML is reasonably well documented nowadays. Controls (the widget library), while not a silver bullet, are good enough (at least on Android, haven't used iOS all that much) so normally
10.
by achipa 12y ago
That's certainly possible for the data part - but a lot harder for UI/code. With the method I'm using, you can actually push code AND UI to the client on the fly. As far as I know, that's a lot more difficult with Xamari
11.
by achipa 12y ago
True - even for DDP there are already a number of client libraries not strictly related to Meteor front-ends, as seen from http://meteorpedia.com/read/DDP_Clients
12.
by achipa 12y ago
There were some concerns as to how native this is - I'm not rendering any HTML. The client side does use the JSON-style QML, but that's just the declarative UI language of Qt - your high-performance code can be C++, Java, or whate
13.
by achipa 12y ago
This is a more full-stack approach - Qt and Xamarin are geared more towards creating standalone apps. What you get here is the reactive back-end (plus web-site for free). This setup can be used for both data and UI - you could for example p
14.
by achipa 12y ago
Hi, I'm Attila, the developer of Qondrite - the interface between Meteor and Qt in the article. If you have any questions, feel free to ask, I'm always looking for new perspectives, comments and will be happy to answer!
15.
Meteor and Qt(achipa.blogspot.com)
162 points by achipa 12y ago|41 comments
16.
Android example for using QML wrappers for a C++ logic and native UI hybrid app(achipa.blogspot.com)
1 points by achipa 12y ago|0 comments