Very nice! I like it. :)

I have so far not been able to compile it yet. QJson is failing to compile at this moment… :-(

Thank you. I’ll keep adding little bits to it and post back again when it is usable for a little more than looking at your own points ;-)

@Andre, I am using qjson-0.7.1 which I installed via portage. I have not tried building it by hand.

Managed to build qjson (from git), and with some adjustments to your code (in the .pro file and in the include of qjson you use), I even managed to build the app. Trying to run it instantly crashes though, so I’ll try for a bit more…

Impressive! ;-)

I’ve not tried at all on Windows yet. I’ll see if I can get it workign there tonight. I do not know of any platform-specific things though. Maybe I forgot to initialise a pointer in a ctor or something.

OK, got it working, it was a simple matter of the executable not being able to find the qjson library when running. Now all I have to do is figure out what the app actually does :-)

The changes I had to make to make it compile for me:

In qtdevnet.pro, changed the path handling a bit

In profile.cpp, I changed the include for qjson’s parser.h:

This way, I can actually make QJSONROOT point to where I downloaded and build QJson.

The only thing you can do at present is to go to the “Application->Login…” and enter your QtDevNet credentials (not included support for OpenID yet) and it will login via QNAM (see the Authenticator class). One slight mystery I have not had time to look at yet is why QUrl::toPercentEncoding() will not encode a “/” character. I have to manually replace that with / later. I’ll step into the Qt code later and take a look.

If that works it will start a timer inside the Profile class that polls QtDN for your profile stats once every 60 seconds. The response is parsed using qjson and the properties updated accordingly.

The Profile class is exposed to the QML root context and the qml scene just binds to the properties of it (and one property from the autheticator object which determines if the qml items are visible or not).

It’s just a starter for 10/proof of concept at this stage. Nothing fancy. Having said that it will be simple to extend to cover other features that could be supported by a web API.

Thanks for the mods. I’ll patch my source for win support with it.

Edit: I have applied the patch this in svn now.

Just a small update. The login dialog is now handled via QML too (the actual network stuff is still in C++ of course). It’s in svn if anybody wants to grab the update. Here’s a screenie (no bling-tastic animations yet though).

ps I hope you don’t mind me grabbing artistic assets from the site for use in this client. ;-)

Sweet ZapB, I’ll try out the updates once I get back from the Easter break and to a proper pc :)

OK another hour of playing with QML and the login page now behaves more like you would expect, including things like:

1. Enabling/disabling login button based on user name and password fields being populated
2. Visible feedback on login button status (enabled/disabled has focus/no focus)
3. Tab key navigation between elements

Plus it has some bling now – you’ll have to run it to see it. ;-)

My opinion of QML so far is that it is very nice, but it will be a whole let better once we have one or more decent sets of components to use (desktop components would be really cool – and yes I have seen the blog with them in). It is instructional to develop your own from first principals but requires lots of digging in the docs for QML noobs like me.

Next step is to see if I can get this converted into a mobile app and try in on my N8. Now where did I put that SDK…

Sweet! I just managed to get this running on my N8. It’s very awesome to see the same QML animations running on the phone – smoothly too! :D

It took a little bit of trial and error and I am still not quite sure what made it start to deploy properly and I can still not get qjson to build for the qt-simulator target. I’ll write up some instructions on how to do this and commit my mods to the svn repo shortly.

Edit 1: Code to allow this to be built and deployed for Symbian is now in svn.

Edit 2: Figured out what was stopping me from running this on the device originally. I kept getting the “General OS Error” when trying to deploy and run my app. It turns out that it was because of insufficient capabilities in the qjson lib on which my app depends. By changing the TARGET.CAPABILITY line in qjson/src/src.pro to:

allows my app to load the qjson dll on the device (since my app needs access to the Internet). Read about capabilities [wiki.forum.nokia.com] for more info on this.

I have concerns about how this may scale if several apps want to use the same dll but with different capabilities but that’s something to worry about for another day.

Marius, I wonder if you could help me with something please? I am trying to add avatar support to my little QtDN client and until the API supports returning the avatar image URL I thought I would take the opportunity to try using QXmlQuery to parse the xhtml of the front page of QtDN to extract the gravatar source url.

This is all going fine until I get this error from QXmlQuery:

Looking at the page source I see that line 74 is:

which of course is not valid xhtml (or xml) as advertised by the doctype. I can work around this by stripping this out before I pass it onto the QXmlQuery of course but would you like me to report this as a bug? Or even better is there an easy fix you can apply to get rid of the above non-valid entry please?

Many thanks.

Another piece of invalid xml is found on line 190:

The error is:

The img element is missing the empty tag specifier – ie it should have a “/” at the end of the img tag.

Edit: This input tag on line 532 is also missing a closing “/”