QML and Qt Quick

2 beers and cheers to u 2beers :p
glad it worked :)

[quote author="2beers" date="1288996077"]
With other words, I can create my own PushButton using QML Elements, but it will be better to use an official pre-defined PushButton?
[/quote]

Yes, you can create your own PushButton (this is the way to go today). In the future, there will be the option to use the "official" one or keep using yours. Advantages of a "official" component: you won't need to maintain this code by yourself, probably more features, etc.

[quote author="2beers" date="1288996077"]
I found that qt components depends on meego touch library, may I ask why?
[/quote]

If you build the MeeGo configuration, yes, it depends on libmeegotouch. However, if you take a look at the Mx components you'll find a set of components with the look & feel of the Mx toolkit without any external dependency. More details are in the README file located in the root of the project.

[quote author="2beers" date="1288996077"]
aren't qt components build using qml elements? isn't qml cross-platform?
Qt components will be meego specific or they will be used on other platforms? if yes will they look the same as on meego or they'll have the same look as native widgets?
[/quote]

The components may have a part of code in C++, it is expected. The point is: You are assuming "MeeGo Touch integration == Qt-Components", what is not true. The MeeGo touch integration aims to provide an API to allow the development of applications with QML integrated with MeeGo. It is at the same time an initial implementation of how the general components would be and an example of platform integration.

Remember, Qt-Components is still work in progress, there are plans to separate the repository to make it easier to understand and to make clear the difference between what is Qt Components and what is a platform integration.

(Maybe my answer wasn't clear enough, I'm sleepy...)

Forget it, my view delegate was producing items that filled the view port, this is why only one item was visible.

Yes that's right, I have forget that QML is after all just a QWidget (if I'm right) so I can put it in my Qt desktop project.

For that I will need an exemple ... like minehunt ;)
At least I can read the source code :D

is "this ":http://doc.qt.nokia.com/qt-mobility-snapshot/installation.html what you are looking for ?

Hi,

If they are working fine from Creator, but not from qtdemo, running with "-graphicssystem raster" may help (this is set by default when running qmlviewer/qmlobserver, but not when running qtdemo).

Regards,
Michael

Kim informed me that the include order issue above has been addressed and is fixed in Qt 4.7.1

Hi,

In the above code, it looks like each of the newly created objects might have its x-position bound to the same "global" variable, moveOver. If that is the case, when you increment moveOver all of the items would move to the new position (which might look like the previous items were being deleted). If that is the problem, "assigning the x in Component.onCompleted":http://doc.qt.nokia.com/4.7/qdeclarativejavascript.html#property-assignment-vs-property-binding should fix it.

Regards,
Michael

never mind. I found the solution. for those who are interested:

"preferredHighlightBegin":http://doc.qt.nokia.com/4.7/qml-listview.html#preferredHighlightBegin-prop

Didn't find a way that works for linking static plugins. However, you can include the plugin source in your project and use qmlRegisterType().

AFAIK, there is no plan for an official browser plugin. At least it was the position in the last time I saw a developer talking about this subject, but it was in the first semester, don't know if the plans changed since then...

EDIT: "a developer talking about this subject" == "http://lists.trolltech.com/pipermail/qt-qml/2010-April/000213.html":http://lists.trolltech.com/pipermail/qt-qml/2010-April/000213.html =)

Indeed, probably anchor layouts is what you want. If you want, as you said, components to be enlarged only on vertical, you can write, for instance:

@
Item {
id: rootItem

Rectangle { id: anchoredRectangle anchors.top: parent.top anchors.topMargin: 17 anchors.bottom: parent.bottom anchors.bottomMargin: 10 anchors.horizontalCenter: parent.horizontalCenter // or, for example: anchors.right: parent.right }

}
@

This way the Rectangle will be enlarged only on vertical axis when Item is enlarged.

Is something like this what you want?

Well, I don't know it. But it's interesting that all examples in Qt declare as directories for qml files only the current directory, although many of them have qml files in subdirectories and Qt Creator still find them. Maybe one only has to declare the root directory.

Nevertheless, if a .qmlproject file uses the same syntax as a general qml file, then you can specify more than one directory in this manner:

@
QmlFiles {
directory: [ 'a directory', 'another directory']
}
@

Thanks for the help.

Instructions for getting Qt Mobility are here: "http://doc.qt.nokia.com/qt-mobility-snapshot/installation.html":http://doc.qt.nokia.com/qt-mobility-snapshot/installation.html

The second question is outside of my scope, sorry.

Are you looking for blueRectangle to initially be positioned at rectRectangle.x + 120, but not bound to it? (so changing redRectangle.x does not cause blueRectangle to move?) In that case you could either use an absolute value for the position of blueRectangle, or assign a value to blueRectangle.x at component completion:

@
// this assigns a value, and does not establish a binding
Component.onCompleted: blueRectangle.x = redRectangle.x+120 @

Hi,

By default, the first item to accept a mouse press "grabs" the mouse (for more on this behavior, see docs "here":http://doc.qt.nokia.com/4.7/qgraphicsitem.html#mousePressEvent). So currently only one MouseArea can actively handle mouse events. We'd like to make this more flexible -- the task tracking this is "QTBUG-13007":http://bugreports.qt.nokia.com/browse/QTBUG-13007

Regards,
Michael

Can I create a .config file or the equivalent of a .plist file for the settings menu to write to?