My point is, most applications provide a Replace All button.

Can you raise a bug suggesting that in Fremantle the English test for [font=monospace]GTK_STOCK_FIND_AND_REPLACE[/URL] is "Replace", and point to Quim's message?

Isn't this a bug against GTK+ upstream and not Hildon/Maemo?

I think it should be raised in bugs.maemo.org for three reasons:

1. It is typical to report bugs to your provider, who is then responsible for liaising with upstream (admittedly, here this is a low-level developer-focused bug, so this may not apply so strongly)
2. This is more acute for Maemo - and especially in fremantle - where space is restricted and the button size in a dialogue box (where this text is most likely to appear) is fixed.
3. This should be fixed for the fremantle release, and it going upstream to some future Gtk+ version (if at all) is not going to help Maemo developers and users.

From point #3, a bug could be raised saying "fix bug #FOO from bugs.gnome.org in Maemo 5 Gtk+ before release", but there's still then a bug in bugs.maemo.org, just proxying upstream.

I'm fine if you go ahead and file a bug in bugzilla.gnome.org and post the bug ID here, and I'm also fine if you file a bug in bugs.maemo.org that I can forward to bugzilla.gnome.org.

https://bugs.maemo.org/show_bug.cgi?id=4219

Here's set of aisleriot screenshots

(and what the heck is happening to picture sizes?)

I missed it, because i was expecting things to happen in error. The average user faced with this will say "Wait, no cancel button? There must be another way to close the dialog!". I just though "No cancel button? The SDK is broken". The average user would never come to the same conclusion i came to.

What i in fact did was to click the X in the upper right corner and the dialog diappeared. But i once more wasn't sure if it was closed by a failure in the framework or by purpose. Again, an end user won't expect this to be a bug. He'd just think "ok, i clicked the X, now the dialog is gone. This seems to be the way things are supposed to work here".

Single major problem with this: He thinks clicking the X is the supposed way to close the dialog which it in fact isn't. But i can live with that ...

actually the cancel behavior feels pretty intuitive when you use it in practice. Also, it's a one time learning experience.

Getting back to the close button discussion...

First time I deal with the new UI, it seemed pretty logic to me, that clicking outside of the dialog will make it disappear, but since I'm a HCI enthusiastic and so much people here have complains about the lack of close button, I decided to expose the UI to regular computer users.

I asked five friends (windows and mac user's) and three familiars (ubuntu user's - chat, web and office only), to test the Fremantle UI. Just a small test in order to expose them to the lack of close button.

Five of them, used the UI without any complains, and don't even blink when they have to hit outside the dialog to close it. The other three made me two different question:

"Where is the close button ?" and "Should I click outside the dialog to close it ?"

But I didn't have enough time to answer, because they actually close the dialog without my help.

Note that none of this people are programmers/geeks/power users, after the test I asked them: "Why do you clicked outside the dialog to close it ?", and the answers was mainly this two:

"The dialog seems like a pop-up to me, so I clicked outside of it, in order to close it ".

"Why not, when I have layered windows in my desktop and I want to switch the focus to another window, I click in the window that I want".

So in my opinion we can't call this a "Norman interface", I think the majority of the users will learn how to close the dialog in seconds, and as was said before it's a one time learning experience.

My 2 cents :P.