Fix surrendering of TextArea focus when clicked outside

TextArea and TextField are supposed to give up focus after any outside
click. In TextArea, this didn't work, because the InverseMouseArea was
bound to the activeFocus property of an element that won't have active
focus.
Hide toolbar shadows when the toolbar is not visible

Toolbars were made invisible by setting the height to 0, which
doesn't hide the shadows surrounding them. As a result of this and
a bug that creates a toolbar even when none is needed, every Page
without a toolbar had a shadow at the bottom of the screen.

Fixed by setting visible:false after animating the toolbar offscreen.
Avoid unnecessary layouts in ToolBarLayout

'width' is undefined here, the intent was to use toolbarLayout.width.
The layout is redone when width is changed.
Only set DialogStatus.Closed when Dialog is really, truly gone.

Due to part of the disappearing animation for Dialog being controlled
by a different component, Closed status was incorrectly set before
the dialog had faded from the display.

In the case of dynamically-allocated dialogs destroyed on Closed, this
would leave the display with unexpected content (an unfaded black
rectangle, partially alpha) until the next full redraw.
Fixes NEMO#272: SelectionDialog doesn't work with C++ model out of the box.

model.count relied upon the model having a count property, likewise
model.length required a length property. Out of the box, C++ models don't have
these properties, and the behaviour for not having them is very unintuitive: it
just stops working.

ListView.count is a C++-implemented property that wraps all the different types
of models' differences so that we don't have to deal with this. We're already
using its notify signal, so why not just use ListView.count to calculate our
data, too? :-)
Fixes NEMO#272: MultiSelectionDialog doesn't work with C++ model out of the box.

Port of the fix from SelectionDialog in 4c627a3d.
Port an inconsequential code change to MultiSelectionDialog

The implementations of SelectionDialog and MultiSelectionDialog
are very similar, so let's keep them that way.

This may also compile more efficiently as per 7f63f110
Sync Utils.js with extras/Utils.js.

Because we somehow stupidly ended up with two copies of this file, they've
already started to get out of sync, which has caused problems with EditBubble at
least.

Sync them up. Let's try figure out how to merge them in the future.
sectionscroller: better cope with custom model types.

By using ListView::count, we can avoid all of the stupid fiddling
to determine what property models are using to expose their length
this week.

This also avoids the need to expose count/length properties in C++
models, which is an major pain with proxy models.

As an added bonus, we no longer need to explicitly connect to
rowsInserted/rowsRemoved, because we'll see those implicitly with
the model length changing.
remove meegotouch build option.

i18n codepaths will be changed to use libmlocale instead, see
NEMO#486.
Remove background color of Window
Remove an unnecessary Item in PageStackWindow
Remove isPixmapProviderOnline check from MDeclarativeStatusBar

This is a completely unnecessary round-trip to DBus; if the provider
isn't online, the call will fail or it'll be dbus-launched if
appropriate.
Avoid dbus introspection overhead in MDeclarativeStatusBar
Change mthemedaemon socket path to homedir

This corresponds with a patch to libmeegotouch to avoid the use of
/var/run.
Fix compilation broken by 4632135
Make dialogs transparent again.

Don't flicker when using a Fader with a custom opacity (which is most
probably why they were disabled...)
Revert "Remove background color of Window"

This reverts commit 01937bcc17233002d01ae721088ad442ab06eb3c.

This caused visual breakage on animation of some applications.
sectionscroller: don't allow stealing

when we e.g. overlay a ListView, the ListView would intercept swipe
gestures after delivering onPressed, and thus we would never recieve
onReleased, breaking things.

Since we are basically a gesture in our own right, we shouldn't allow
that stealing.
sectionscroller: fix drag handle position occasionally screwing up

Using ListView's dragging stuff to position our item seems to trigger
some interesting bug when we need to reset the dragged item's position.

Instead of using a hybrid of ListView and our own techniques, let's just
position it ourselves.