Where should I put my Qt tricky examples?



  • Hello All I am new to it couple of days only I joined this. I want to put some tricky examples and some Qt's work around and hacks :) so that other users can be benefited. But I do not know where exactly should I put all those. I saw wiki but should I do that in HOW TO category or code spinet or some where else?



  • If you have small small code which demonstrate some tricky thing in Qt put that in Code Snippet.



  • You can put it in both categories. Just add both tags to your page text (and don't forget to add some tags like "howto" and "code snippet" on the right side once your page is saved).

    It's better to add a separate page for each of your solutions, at best with some comments and explanations of course. You are free to choose the page title, CamelCase is not longer a need (as stated in some wiki help pages).



  • Thank you for quick reply. When I have tricky code only couple of lines of description I have I think I should put that in code snippet, I will put other examples which needs some more explanation in How to category. Thank you for letting me know about Tag thing I did not know about it until now, and thank you for putting tag for this post of mine too :) Have great holidays....!!!



  • Some "guidelines on Tagging":http://developer.qt.nokia.com/wiki/Tagging are in the wiki. I'd suggest you read before to save you from getting your tags deleted ;-)

    And just go ahead with the wiki - we all are curious :-)



  • I see Guidelines on tagging, But I was wondering do we have any guide lines what type of code/example or any content any one can put in?? I mean if some one says he is going to put some code example he can put Hello World example too, isnt it ?
    So Do we have any guideline for that?



  • Immii, I think we all are sensibly people :) Put "hello world" isn't sense. Though I (for example) want see Hello world snippets on PySide (I don't know Python and it will be interesting for me)



  • There are no official guidelines. I think common sense is, that the code snippets should show the solution for a reasonable problem and it should not be just a copy of things that are in the docs anyway. No one can protect against wiki trolling, but our Trolls will clean up things if necessary.



  • [quote author="Volker" date="1293404668"]There are no official guidelines. I think common sense is, that the code snippets should show the solution for a reasonable problem and it should not be just a copy of things that are in the docs anyway. No one can protect against wiki trolling, but our Trolls will clean up things if necessary.[/quote]

    The word "reasonable problem" is little bit vague what is reasonable for me may not be reasonable for every one else. Can we people of QDN should start defining some very very basic rules about this and then get Nokia involve and finalize?



  • There is no official definition of "reasonable" and I doubt there ever will be as applying the rules would open just another level of interpreting things.

    We all are intelligent beings and apart from some project Elf "spamming" or similar effects, most things went out quite well until yet. So why worry? Rules would not prevent from spamming the wiki if the poster does not care about the rules.

    As I mentioned: If the content is in Qt's docs or is quite obvious, it's probably not for a wiki entry. If you're really unsure wether your snippet is worth a wiki entry, just ask in the forum.



  • If you have a complex problem, or an easy problem with an non trivial solution, I think it makes sense. And if you are unsure, put irt to the wiki and start a discussion about the article in the wiki forum. If the result is, does not make sense, it could anyways be deleted ot changed afterwards.

    I juts have on ething: please do not just put a code snippet there witzhout descriptuion (what I have seen in some other places :-( ). If itz has a (good :-) ) description, it nearly always makes sense :-)


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.