Talk:Augmented Reality Applications with NyARToolkit and Qt3D
Hamishwillee - Subedited
Very impressive - its technically dense, but this article is interesting, pretty cool, and would clearly be very useful for anyone wanting to do anything remotely similar.
From a writing point of view I think it flows well and the English is fine. Only thing that wasn't clear was in the introduction what it is that NyARToolkitCPP gives to you - you say "imaging algorithms", but it would be good to say a bit more about what they do e.g. imaging algorithms that ensure that the 3D shape always looks in the right direction (or whatever it does). At the moment that isn't very clear.
I have given this is a subedit for "wiki correctness".
- Usually we use Template:Icode to markup inline code because this draws classes etc in monotype like the the code blocks. For the first appearance of a new class I use a link to the reference documentation (if this is "core" Qt then you can use the Template:Qapiname to direclty link).
- I tend to use bold for filenames and text of buttons to be pressed only.
- Links are what makes a wiki work - where you had bold text followed by an URL I've just made this as the text with link to URL. That is enough highlighting and makes it all more readable.
- Just add a line space to get new lines - BR is not needed and having a space makes the text easier to read while editing
- Don't add style like bold to headings "by default" - you can if a word needs to be highlighted. Reason is that there is a standard wiki style for headings, and it makes everything look more consistent
You will also note that I've removed almost all the bold (some for the reasons given above). The way it looked before there was so much highlight it was impossible to work out what was important - that makes it harder to read. As a rule, it is better to use your highlight for those things that the user really MUST KNOW :-) Highlight in this context can mean italic, bold or capitalisation. Note that code fragments are an exception to this rule, which is why they have a special style. Hope that makes sense - IMO this is definitely a "better looking" document now, with very little actual change to content.
Lastly, I moved your images down to screenshots at the bottom, and your video into its place. In this case the video is much more useful for understanding the app than the images.
Thanks for contributing this to the wiki and entering the competition. I for one am most impressed.
05:28, 31 May 2012 (EEST)
Fred.duarte - Re:
thank you for the feedback, the editing and the suggestions, Hamish. I very much appreciate it.
Second, I see your point on the Introduction part. As I was going back and forth when writing the text, i was so obsessed in "showing" mostly "core source code" that this part kind went undetected. I'll work on that.
And sorry for all the BOLD caption, i guess i just like to mark every keyword i see as important (old study habit :) ).
I am still trying to figure out the MEMORY ISSUE on Symbian^3 devices. I can't quite pinpoint the actual root of the problem (if it is on the Camera side or on the Qt3D side or ON BOTH). But, i've contacted the guys at the Qt3D project to see if they shine a light of clarity on the matter.
Again,thank you for the feedback and all that editing. It definitely looks much more presentable now.
08:23, 31 May 2012 (EEST)
Hamishwillee - Not a worry
You're welcome. Its easy to tidy up minor stylistic and formatting issue (or even major ones) if the structure and technical content are good. From my perspective very minor effort for great reward.
05:33, 1 June 2012 (EEST)
Andreslb151 -Is it possible to make it totally in C++ instead of using that QML at the end?
talk) 09:41, 1 October 2013 (EEST)(
Hamishwillee - I should think so
It is quite possible Fred is no longer watching this article - suggest you raise query on the N9 or Symbian Qt forum to get more eyes on it - perhaps linking here. In general you can do anything in C++ you can do in QML - however creating a QML UI is much easier.
talk) 12:52, 2 October 2013 (EEST)(