[Suggestion] Combinations of tags

  • As one can see in this "thread ":http://developer.qt.nokia.com/forums/viewthread/7785/ Tags have a more prominent place for access now.

    Starting to type changes immediately the list of possible tags. This is really great and helps a lot.
    From my point of view it would be helpful to extend the functionality. At the moment one needs to decide for one tag to use in the search. A possibility to enter a second tag allowing a combined search for threads having the two tags in common (e.g. "linux" and "cross-compile") would be really great. Certainly one may wish to have an "unlimited" count of different tags, but in general a max of three I would consider as most sufficient.

    BTW I have checked the "Advanced search", but it did not provide what I was looking for. Or at least I did not find.

  • Some extent of tags merge is necessary, but it might need a lot of extra work to do it, and the priority might be not on the top.

  • +1

    This proposition seems reasonable as it will provide much better searching and navigation though the pages :)

  • Hi all,

    We had a similar discussion a while ago.
    "Here is the link :":http://developer.qt.nokia.com/forums/viewthread/7147

    "Please vote for it here!":http://bugreports.qt.nokia.com/browse/QTWEBSITE-248

    Marius liked the idea also!



  • Thanks Eddy for pointing to the other thread. Certainly I have deposited my vote on JIRA :-)

  • You're welcome!

    Hopefully this can be added in the next version of devnet that should get on the web this summer. As the number of topics and tags are growing it's getting more and more difficult to find what you need.

  • Yes, you are right. Hopefully we see it in the next version. In my personal opinion I would formulate a harder. The tags may be useless soon, because of teh large variety of possibilities.

    At the beginning a simple "and" of two tags ignoring all dependencies would be sufficient. An acceptable answer is then "no match".

    The more sophisticated approach would be narrowing the choices in a second window by the choices of the first window. That would be a first class solution.

    However, one may raise nice ideas without knowing what the details are behind the implementation. The first approach might be much easier to realize, while the second approach "smells" like required throughput and some more eloborated programming.

    So, let us see what the Trolls are coming up with ;-)

  • We like it a lot as well, and as said by koahnig it's simply needed -> so it's in development right now :) (and has been for a month)

    More info here: QTWEBSITE-135

    It's our highest voted issue in JIRA even, we aim to please :)

  • +1
    Grate proposition @koahnig koahnig

Log in to reply