[solved] annoying "Search..." in input line at tag search

Wolf P.

hm... don't know exactly, it's slow, but tutorial deletes any input, whereas "Search..." is mostly combined.

If the "Search..." would be killed completety, I would find it more comfortable.

baysmith

I've had the same problem.

[quote author="mariusg" date="1291907962"]Sounds like the JavaScript is slow to load.

If you click this link: http://developer.qt.nokia.com/tags/?tag_search=tutorial

Equally slow?[/quote]

I find this faster.

fcrochik

I noticed the same thing.... In fact, took me a few times before I noticed that it would actually delete the "Search..." by itself.

mgran

We shall remove the "Search..." text, thanks for the feedback.

Wolf P.

Thanks. Have you already added this to the bugtracker? (when yes:) Where?

Wolf P.

...and what about the obfuscating Uppercasing appearing at the list of items tagged with a particular tag mentioned "here":https://developer.qt.nokia.com/forums/viewthread/2016/#9554 ?

mgran

We're going to make the Tag module case-insensitive so we don't have issues like that. It's on the list, but not for the coming release.

Wolf P.

Marius, please have a close look at what get when you click on a beta tag:
"Beta":http://developer.qt.nokia.com/search/tag/beta
(the uppecase Beta in the page title dosn't matter at all)

You'll see this line on top of the page:
Content tagged with Beta Looking for other tags?

The uppercase Beta following the phrase "Content tagged with" is my problem.
...I cannot believe that this little bug has to wait for a further release, or...

mgran

That is indeed a minor issue and the fix for that has already been committed to our git repository. The change was from:

@$tags[$key] = ucwords($tag); @

to

@$tags[$key] = $tag;@

We release a new version of DevNet every two weeks. Should there be critical issues in between releases we of course push them live right away.

I know it looks like a quick fix that could be pushed out in 5 minutes but - as many developers are sure to know - in the long run it's better to have a good release process and not touch the live environment too often[1]. Even trivial things can surprise you.

We typically fix 20-40 issues per release and by doing it in this bi-weekly fashion we ensure proper testing and some order for the release manager and the developers.

fn1. Actually, one day, we want to do "continuous deployment":http://toni.org/2010/05/19/in-praise-of-continuous-deployment-the-wordpress-com-story/ but we're not there yet.

Wolf P.

[quote author="mariusg" date="1291990521"]That is indeed a minor issue and the fix for that has already been committed to our git repository. The change was from:

@$tags[$key] = ucwords($tag); @

to

@$tags[$key] = $tag;@ [/quote]
How good, that I insisted in this point ;) ...and it improves the performance :)

mgran

“Search…” is gone now :)

Wolf P.

:) That's phantastic!