原文链接:QML入门教程(3)

经过前面两个教程，文字也能显示，也能处理鼠标事件了，来点动画吧。

这个教程实现了当鼠标按住的时候，Hello,World从顶部到底部的一个旋转过程，并带有颜色渐变的效果。

完整的源代码main.qml

import Qt 4.7

 Rectangle {
     id: page
     width: 500; height: 200
     color: "lightgray"

     Text {
         id: helloText
         text: "Hello World!"
         y: 30
         anchors.horizontalCenter: page.horizontalCenter
         font.pointSize: 24; font.bold: true

         MouseArea { id: mouseArea; anchors.fill: parent }

         states: State {
             name: "down"; when: mouseArea.pressed == true
             PropertyChanges { target: helloText; y: 160; rotation: 180; color: "red" }
         }

         transitions: Transition {
             from: ""; to: "down"; reversible: true
             ParallelAnimation {
                 NumberAnimation { properties: "y,rotation"; duration: 500; easing.type: Easing.InOutQuad }
                 ColorAnimation { duration: 500 }
             }
         }
     }

     Grid {
         id: colorPicker
         x: 4; anchors.bottom: page.bottom; anchors.bottomMargin: 4
         rows: 2; columns: 3; spacing: 3

         Cell { cellColor: "red"; onClicked: helloText.color = cellColor }
         Cell { cellColor: "green"; onClicked: helloText.color = cellColor }
         Cell { cellColor: "blue"; onClicked: helloText.color = cellColor }
         Cell { cellColor: "yellow"; onClicked: helloText.color = cellColor }
         Cell { cellColor: "steelblue"; onClicked: helloText.color = cellColor }
         Cell { cellColor: "black"; onClicked: helloText.color = cellColor }
     }
 }

除了这个main.qml之外，还有一个Cell.qml也是需要的，和教程(2)中的完全一样。下面来看一看比起教程(2)的代码增加出来的内

容。

    Text{
         ...
         states: State {
             name: "down"; when: mouseArea.pressed == true
             PropertyChanges { target: helloText; y: 160; rotation: 180; color: "red" }
         }

         transitions: Transition {
             from: ""; to: "down"; reversible: true
             ParallelAnimation {
                 NumberAnimation { properties: "y,rotation"; duration: 500; easing.type: Easing.InOutQuad }
                 ColorAnimation { duration: 500 }
             }
         }
        ...
     }

states内嵌于Text之中，可以为Text元素添加多个状态，现在的这个例子只增加了一个状态。该状态的名为为”down”,然后由“when”指 定了什么时候触发这个状态。PropertyChanges则指定了哪个元素的哪些属性会发生什么样的变化。例子中PropertyChanges利用 “target”指定了id为”helloText”的元素会发生变化，包括其y,rotation,color等属性。
transitions 是用于增加动画效果的（如果把transitions这一段代码删去，Hello,World的文字也会发生变化,但是看不到中间动画渐变效果)。同样可 以看到transitions是复数形式，意味着可以添加多个动画过程。“from”和”to”指明了当前的动画作用于哪两个状态变化之间。 “from”和”to”的参数名来自于State中的”name”属性。
ParalleAnimation则指定了有多个 有多个动画并行发生。NumberAnimation用于qreal类型的属性变化,ColorAnimation则用于颜色变化。更多 Animation请在QML文档中查找”Animation and Transitions”。
好了，三篇教程到此结 束。更多资源请访问Declarative UI Using QML。
本文源码下载

原文链接:QML入门教程(2)

在上一篇文章里我们使用了最基础的QML类型实现了文字Hello,World的显示。这篇文章中将会增加颜色选项面板，用户可以给Hello,World设置不同的颜色，如下图显示

QML组件

从图中可以看到选项面板由6个颜色小块组成，它们唯一的区别就是颜色不一样。那么我们就可以用组件(Component)来实现一个颜色块，然后在需要的时候使用这个组件就可以了。组件其实和其它编程语言中的宏，函数，类，结构体等功能差不多，就是代码复用。作为程序员，我知道你懂的。
组件由一个单独的QML文件名组成，文件名总是以大写字母开头，要使用该组件的时候直接使用该文件名就可以了。关于如何定义自己的组件，请访问Defining new Components。我们为一个颜色块定义了一个Cell.qml文件，然后使用Cell作为一个去访问它。

Cell.qml的内容

import Qt 4.7

Item {
    id: container
    property alias cellColor: rectangle.color
    signal clicked(color cellColor)
    width: 40; height: 25
    Rectangle {
        id: rectangle
        border.color: "white"
        anchors.fill: parent
    }
    MouseArea {
        anchors.fill: parent
        onClicked: container.clicked(container.cellColor)
    }
}

挨个看代码～

Item {
id: container
property alias cellColor: rectangle.color
signal clicked(color cellColor)

width: 40; height: 25

Item是最常使用的QML类型，一般用作其它类型的容器，可以理解成最顶级的父类，功能类似于QtGui中的QWidget。用一个属性别名访问其内嵌对象rectangle的color属性。在其它文件中可以用Cell对象的cellColor获得rectangle的color值。
signal clicked(color cellColor)则为对象定义了一个信号，在代码的其它部分可以发出这个信号。

Rectangle {
id: rectangle
border.color: “white”
anchors.fill: parent
}

这一部分没有特别好说的，在Item中内嵌了一个id为rectangle白边框的矩形区域，大小占满整个Item。

MouseArea {
anchors.fill: parent
onClicked: container.clicked(container.cellColor)
}

MouseArea则为Item增加了一块鼠标响应区，看它的anchors知道，在整个Item区域内都是鼠标活动区，都能侦听到鼠标事件。onClicked那一行则相当于为鼠标单击事件增加了一个处理行为，这里是发出了一个clicked()的信号。这个信号正是我们在Item里定义的那个signal。
Cell.qml写完了，再来看看程序的主文件。

main.qml的内容

import Qt 4.7
Rectangle {
     id: page
     width: 500; height: 200
     color: "lightgray"

     Text {
         id: helloText
         text: "Hello world!"
         y: 30
         anchors.horizontalCenter: page.horizontalCenter
         font.pointSize: 24; font.bold: true
     }
    Grid {
         id: colorPicker
         x: 4; anchors.bottom: page.bottom; anchors.bottomMargin: 4
         rows: 2; columns: 3; spacing: 3

         Cell { cellColor: "red"; onClicked: helloText.color = cellColor }
         Cell { cellColor: "green"; onClicked: helloText.color = cellColor }
         Cell { cellColor: "blue"; onClicked: helloText.color = cellColor }
         Cell { cellColor: "yellow"; onClicked: helloText.color = cellColor }
         Cell { cellColor: "steelblue"; onClicked: helloText.color = cellColor }
         Cell { cellColor: "black"; onClicked: helloText.color = cellColor }
     }
 }

这里在原来的基础上增加了一个Grid网格。x坐标是4，底部挨着page的底部，所以我们看到的是在左下角。
新增的6个Cell，名字和Cell.qml是一样的。通过cellColor属性将颜色传给了每个颜色块。
当Cell接收到onClicked事件的时候,关联的代码回去修改Hello,World上的颜色。细心的朋友可能会注意到Cell只是定义了clicked()的信号，并没有定义onClicked()啊，是的这就是Component的语法规则了。如果你在Cell.qml里定义的是plicked(),那么你在main.qml中引用的时候就该用onPlicked()了。

好了，代码也不少了，随便改动改动，你会了解更多QML的秘密的:)
本文源码下载

本站所有文章由本站和原作者保留一切权力，仅在保留本版权信息、原文链接、原文作者的情况下允许转载，转载请勿删改原文内容， 并不得用于商业用途。 谢谢合作。

原文链接:QML入门教程(1)

前言:Qt Declarative UI 传得沸沸扬扬，却很少有中文资料介绍这是一个什么样的技术，以及如何使用它。偶尔能搜到几篇也是掐头去尾的，让人摸不着头脑。CuteQt网友英狐奉献的三篇文章很有参考价值，把我带入了门。我准备翻译的这个入门教程来自于Qt官方文档，更多的是语法性的介绍。说是翻译，其实是我在原文基础上的一个阅读理解吧。

QML是什么？

QML是一种描诉性的脚本语言，文件格式以.qml结尾。语法格式非常像CSS(参考后文具体例子)，但又支持javacript形式的编程控制。我个人认为它结合了QtDesigner UI和QtScript的有点。QtDesigner可以设计出.ui界面文件,但是不支持和Qt原生C++代码的交互。QtScript可以和Qt原生代码进行交互，但是有一个缺点，如果要在脚本中创建一个继承于QObject的图形对象非常不方便，只能在Qt代码中创建图形对象，然后从QtScript中进行访问。而QML可以在脚本里创建图形对象，并且支持各种图形特效，以及状态机等，同时又能跟Qt写的C++代码进行方便的交互，使用起来非常方便。

如何使用？

在Qt C＋＋文件中通过QDeclarativeView加载，就像使用UiLoader加载.ui文件一样。不过本文不会去介绍如何在Qt C＋＋中使用QML，而是把重点放在QML的语法上，不过别担心看不到.qml文件的效果。Qt提供了一个工具QML Viewer可以查看.qml文件生成的效果，该程序在Qt的bin目录下，应用名字叫qml(Windows下叫qml.exe)。所以你在看到别人提供的.qml文件时，你可以用下面命令qml filename.qml 查看.qml的执行结果，咱们的第一个Hello,World生成界面如下

开始QML吧

上面的Hello,World源代码如下

1 import Qt 4.7
2
3 Rectangle {
4     id: page
5     width: 500; height: 200
6     color: “lightgray”
7
8     Text {
9         id: helloText
10         text: “Hello world!”
11         font.pointSize: 24; font.bold: true
12         y: 30; anchors.horizontalCenter: page.horizontalCenter
13     }
14 }

第1行是Qt QML的统一用法，指明当前QML会使用Qt-4.7里已经定义好的类型，比如第3行的Rectangle和第8行的Text。

第3行开始至文章结束处则定义了一个矩形的图形区域对象，第4行则申明了该矩形区域对象的id为”page”可以被其它对象识别并通过该id访问其成员属性，另外几个属性width/height/color则很好理解，语法跟CSS类似，可以写在一行中用分号”;”隔开。
第8行至第12行则是一个文本对象，看它代码的嵌套结构可以知道它是内嵌于Rectangle的。Text的属性除了anchors其它几个都能顾名思义。anchors描诉的是当前对象的位置和其它对象的相对关系，这里看到其水平中心位置在“page“的水平中心位置。如果相对anchors了解更多，请参考锚的解释。
以上就是Hello,World的全部代码，将其存为hellowordl.qml，那么只要执行 qml hellowrold.qml就能看到文章前头的界面了。

更多对象？

在上面的代码中我们用到了Rectangle和Text，那么我还有哪些对象以及这些对象有哪些属性呢。那么请访问QML-Item类,Item类是QML最基础的类，通过查看它的继承类以及这些继承类可用的属性，你可以添加更多你感兴趣的内容。

好吧, Happy QML。

附:英狐的三篇相关文章
QT declarative UI 初探（一）
QT declarative UI 初探（二）
QT declarative UI 初探（三）

有没有基于Clutter的图形控件库呢？The answer is YES! 现在Moblin.org上有一个名为Moblin UI Toolkit（简称MX）的项目，它为开发者提供了一套基于Clutter的常用控件，包括了常用的图形控件如button, toggle button, combobox, progressbar和scrollbar等，也提供了一些用于布局的容器类，如box layout和table。

MX是一套C库，依赖于clutter和glib。从面向对象的角度看，MX中的基类MxWidget继承自ClutterActor，因此所有针对ClutterActor的操作对MxWidget均可用。从MX的API来看，和GTK倒是有几分相似，熟悉GTK开发的程序员上手应该很快。

不过需要注意的是，目前MX还没有到稳定版本，如果要在正式产品中使用，还请慎重考虑。有兴趣的朋友可以到该项目的官方网址http://moblin.org/projects/moblin-ui-toolkit了解更多内容。

以下代码是从MX的示例代码中摘出的，功能并不完整，只是用来说明MX应用程序代码结构。

#include <clutter/clutter.h>

#include <mx/mx.h>

int main (int argc, char *argv[])

{

ClutterActor *stage, *vbox, *hbox, *holder, *mainbox, *toolbar, *combo;

MxApplication *application;

//

//初始化

// MX: mx_application_new(), 和当年的Hildon很像，呵呵。

// Clutter: clutter_init()

// GTK: gtk_init()

//

application = mx_application_new (&argc, &argv, "Test Mx",

MX_APPLICATION_SINGLE_INSTANCE);

stage = (ClutterActor*) mx_application_create_window (application);

clutter_actor_set_size (stage, 800, 600);

//

//布局方式: Box packing, 用过GTK的朋友应该很熟了

//

mainbox = mx_box_layout_new ();

clutter_actor_set_size (mainbox, 800, 600);

mx_box_layout_set_vertical (MX_BOX_LAYOUT (mainbox), TRUE);

clutter_container_add_actor (CLUTTER_CONTAINER (stage), mainbox);

/* create the toolbar */

toolbar = mx_toolbar_new ();

mx_bin_set_alignment (MX_BIN (toolbar), MX_ALIGN_MIDDLE, MX_ALIGN_MIDDLE);

combo = mx_combo_box_new ();

clutter_container_add_actor (CLUTTER_CONTAINER (toolbar), combo);

mx_combo_box_set_title (MX_COMBO_BOX (combo), "Select");

mx_combo_box_append_text (MX_COMBO_BOX (combo), "Hello");

mx_combo_box_append_text (MX_COMBO_BOX (combo), "World");

/* create the horizontal layout */

hbox = mx_box_layout_new ();

clutter_actor_set_position (hbox, 12, 12);

/* add toolbar and hoizontal layout to main container */

clutter_container_add (CLUTTER_CONTAINER (mainbox), toolbar, hbox, NULL);

/* create a vbox for the list of tests */

vbox = mx_box_layout_new ();

mx_box_layout_set_vertical (MX_BOX_LAYOUT (vbox), TRUE);

clutter_container_add_actor (CLUTTER_CONTAINER (hbox), vbox);

/* create a place holder for the tests */

holder = clutter_group_new ();

clutter_container_add_actor (CLUTTER_CONTAINER (hbox), holder);

group = mx_button_group_new ();

add_tab (CLUTTER_CONTAINER (vbox), group, "Label",

(GCallback) label_main, CLUTTER_CONTAINER (holder));

add_tab (CLUTTER_CONTAINER (vbox), group, "Entry",

(GCallback) entry_main, CLUTTER_CONTAINER (holder));

add_tab (CLUTTER_CONTAINER (vbox), group, "Button", (GCallback) buttons_main,

CLUTTER_CONTAINER (holder));

add_tab (CLUTTER_CONTAINER (vbox), group, "Combo Box",

(GCallback) combo_box_main, CLUTTER_CONTAINER (holder));

add_tab (CLUTTER_CONTAINER (vbox), group, "Progress Bar",

(GCallback) progress_bar_main, CLUTTER_CONTAINER (holder));

add_tab (CLUTTER_CONTAINER (vbox), group, "Slider",

(GCallback) slider_main, CLUTTER_CONTAINER (holder));

add_tab (CLUTTER_CONTAINER (vbox), group, "Toggle",

(GCallback) toggle_main, CLUTTER_CONTAINER (holder));

add_tab (CLUTTER_CONTAINER (vbox), group, "Tooltips",

(GCallback) tooltips_main, CLUTTER_CONTAINER (holder));

add_tab (CLUTTER_CONTAINER (vbox), group, "Expander",

(GCallback) expander_main, CLUTTER_CONTAINER (holder));

add_tab (CLUTTER_CONTAINER (vbox), group, "Scroll Grid",

(GCallback) scroll_grid_main, CLUTTER_CONTAINER (holder));

add_tab (CLUTTER_CONTAINER (vbox), group, "Scroll Bar",

(GCallback) scroll_bar_main, CLUTTER_CONTAINER (holder));

add_tab (CLUTTER_CONTAINER (vbox), group, "Scroll View",

(GCallback) scroll_view_main, CLUTTER_CONTAINER (holder));

add_tab (CLUTTER_CONTAINER (vbox), group, "Styles",

(GCallback) styles_main, CLUTTER_CONTAINER (holder));

clutter_actor_show (stage);

//

//Mainloop

//MX: mx_application_run()

//Clutter: clutter_main()

//GTK: gtk_main()

//

mx_application_run (application);

return EXIT_SUCCESS;

}

可以看到，MX应用程序代码结构和Clutter与GTK程序相比大同小异，这使得程序移植的难度相对降低了。当然，由于目前控件还不是太丰富，因此若是复杂的GTK程序要移植到MX上可能还是要费一番功夫，但是Clutter应用程序的移植相对就容易了许多。

AppUp^SM的正式上线标志着Intel的应用程序商店已具雏形：开发者可以通过Intel® Atom™ Developer Program提交所开发的应用程序，如果该程序通过了审核验证，那么最终用户可以通过Intel® AppUp^SM Center的客户端看到这款软件，并且能购买与下载安装。

更多消息请参考http://www.intel.com/consumer/products/appup.htm?cid=sw:dev4atom291和http://appdeveloper.intel.com/en-us/

以下是Intel AppUp Center客户端的一些截图，由于中国用户暂时无法申请账号，所以就只有这些啦。:)

首先，使用Moblin Image Creator2创建一个Moblin V2的KVM镜像文件。在终端上运行以下命令：

sudo moblin-image-creator --config=2.1-final.ks --format=raw --cache=mycache

命令执行完毕后会在当前目录下生成一个名为moblin-2.1-final-XX的目录，目录中有一个名为moblin-2.1-final-XX-sda.raw的文件，就是我们想要的镜像文件。

再创建一个Moblin V2的LiveCD镜像，我们要从中把Kernel拷贝出来：

sudo moblin-image-creator --config=2.1-final.ks --format=livecd --cache=mycache

命令执行完毕后会在当前目录下生成一个名为moblin-2.1-final-XX.iso的文件，然后在当前目录下建立一个目录，比如chroot-fs-2，通过moblin-chroot命令，将这个文件mount到目录上：

sudo moblin-chroot -s chroot-fs-2 --unpack-only  moblin-2.1-final-XX.iso

最后，只要从chroot-fs-2/boot/下把vmlinuz-XX拷贝出来即可。

第二步，配置Moblin Anjuta Plugin。关于如何安装、启用该插件以及工具链设置，可以参考我的上两篇博客中的相关内容。打开Anjuta后，通过菜单”Edit”->”Preferences”，打开设置对话框，点击左侧的Moblin SDK，打开插件配置界面。在Target Options中，我们选择 “Use QEMU Device Emulator”，Kernel和Root filesystem这两个选项也被激活。Kernel设成刚才拷贝出来的vmlinuz-XX，Root filesystem设成刚才生成的KVM镜像文件即可。

第三步，启动KVM。通过菜单”Tools”->”Start QEMU”，启动虚拟机。

问题来了。Anjuta报了一条出错信息：找不到一个叫”poky-qemu”的命令。所谓“外事不决问google”，上google一查这个命令，发现了poky platform builder，它提供了一套完整的Linux下的开发环境，Moblin SDK也是基于它打造的。于是我下载了poky的SDK，从中复制出poky-qemu相关的一堆文件，放到了<moblin sdk root>/moblin-cross-toolchain/bin/下，再次从Anjuta中启动KVM。

旧的错误不见了，新的错误又来了。这次报告不支持”netboo”的机器类型。因此我们需要修改poky-qemu-internal，加入相应的机器类型。改完之后再次运行，虚拟机成功的运行起来了。但是遇到了一个新的问题：过了grub之后，整个虚拟机窗口一片白色，什么内容都没有……关掉Anjuta，从terminal里手动启动KVM：

sudo kvm -m 512 -boot c -hda moblin-2.1-final-XX-sda.raw -vga std

但是结果还是与之前一样……该问题正在解决中。我用的OS是Ubuntu9.04，如果有朋友通过KVM成功启动，欢迎告知。

附上修改过的poky-qemu-internal, 直接复制以下内容并覆盖poky-qemu-internal原有内容即可。


#!/bin/bash
# Handle running Poky images under qemu
#
# Copyright (C) 2006-2008 OpenedHand Ltd.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License version 2 as
# published by the Free Software Foundation.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License along
# with this program; if not, write to the Free Software Foundation, Inc.,
# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

# Call setting:
#   QEMU_MEMORY (optional) - set the amount of memory in the emualted system.
#   SERIAL_LOGFILE (optional) - log the serial port output to a file
#   CROSSPATH - the path to any cross toolchain to use with distcc
#
# Image options:
#   MACHINE - the machine to run
#   TYPE - the image type to run
#   ZIMAGE - the kernel image file to use
#   HDIMAGE - the disk image file to use
#

QEMUIFUP=`which poky-qemu-ifup`
QEMUIFDOWN=`which poky-qemu-ifdown`
KERNEL_NETWORK_CMD="ip=192.168.7.2::192.168.7.1:255.255.255.0"
#QEMU_NETWORK_CMD="-net nic,vlan=0 -net tap,vlan=0,ifname=tap0,script=$QEMUIFUP,downscript=$QEMUIFDOWN"
#QEMU_NETWORK_CMD="-net nic"
KERNCMDLINE="mem=$QEMU_MEMORY"

if [ -z "$QEMU_MEMORY" ]; then
QEMU_MEMORY="64M"
fi

SERIALOPTS=""
if [ "x$SERIAL_LOGFILE" != "x" ]; then
SERIALOPTS="-serial file:$SERIAL_LOGFILE"
fi

case "$MACHINE" in
"qemuarm") ;;
"qemux86") ;;
"akita") ;;
"spitz") ;;
"netboo") ;;
*)
echo "Error: Unsupported machine type $MACHINE"
return
;;
esac

if [ "$TYPE" != "nfs" -a ! -f "$HDIMAGE" ]; then
echo "Error: Image file $HDIMAGE doesn't exist"
return
fi

if [ ! -f "$ZIMAGE" ]; then
echo "Error: Kernel image file $ZIMAGE doesn't exist"
return
fi

if [ "$MACHINE" = "qemuarm" ]; then
QEMU=qemu-system-arm
if [ "$TYPE" = "ext2" ]; then
KERNCMDLINE="root=/dev/sda console=ttyAMA0 console=tty0 mem=$QEMU_MEMORY"
QEMUOPTIONS="$QEMU_NETWORK_CMD -M versatilepb -hda $HDIMAGE -usb -usbdevice wacom-tablet -no-reboot"
fi
if [ "$TYPE" = "nfs" ]; then
if [ "x$HDIMAGE" = "x" ]; then
HDIMAGE=/srv/nfs/qemuarm
fi
if [ ! -d "$HDIMAGE" ]; then
echo "Error: NFS mount point $HDIMAGE doesn't exist"
return
fi
KERNCMDLINE="root=/dev/nfs nfsroot=192.168.7.1:$HDIMAGE rw $KERNEL_NETWORK_CMD mem=$QEMU_MEMORY"
QEMUOPTIONS="$QEMU_NETWORK_CMD -M versatilepb -no-reboot"
fi
fi

if [ "$MACHINE" = "qemux86" ]; then
QEMU=qemu
if [ "$TYPE" = "ext2" ]; then
KERNCMDLINE="root=/dev/hda mem=$QEMU_MEMORY $KERNEL_NETWORK_CMD"
QEMUOPTIONS="-std-vga $QEMU_NETWORK_CMD -hda $HDIMAGE -usb -usbdevice wacom-tablet"
fi
if [ "$TYPE" = "nfs" ]; then
if [ "x$HDIMAGE" = "x" ]; then
HDIMAGE=/srv/nfs/qemux86
fi
if [ ! -d "$HDIMAGE" ]; then
echo "Error: NFS mount point $HDIMAGE doesn't exist."
return
fi
KERNCMDLINE="root=/dev/nfs nfsroot=192.168.7.1:$HDIMAGE rw $KERNEL_NETWORK_CMD mem=$QEMU_MEMORY"
QEMUOPTIONS="-std-vga $QEMU_NETWORK_CMD"
fi
fi

if [ "$MACHINE" = "spitz" ]; then
QEMU=qemu-system-arm
if [ "$TYPE" = "ext3" ]; then
echo $HDIMAGE
HDIMAGE=`readlink -f $HDIMAGE`
echo $HDIMAGE
if [ ! -e "$HDIMAGE.qemudisk" ]; then
echo "Adding a partition table to the ext3 image for use by QEMU, please wait..."
poky-addptable2image $HDIMAGE $HDIMAGE.qemudisk
fi
QEMUOPTIONS="$QEMU_NETWORK_CMD -M spitz -hda $HDIMAGE.qemudisk -portrait"
fi
fi

if [ "$MACHINE" = "akita" ]; then
QEMU=qemu-system-arm
if [ "$TYPE" = "jffs2" ]; then
HDIMAGE=`readlink -f $HDIMAGE`
if [ ! -e "$HDIMAGE.qemuflash" ]; then
echo "Converting raw image into flash image format for use by QEMU, please wait..."
raw2flash.akita < $HDIMAGE > $HDIMAGE.qemuflash
fi
QEMUOPTIONS="$QEMU_NETWORK_CMD -M akita -mtdblock $HDIMAGE.qemuflash -portrait"
fi
fi

if [ "$MACHINE" = "netboo" ]; then
QEMU=kvm
QEMUOPTIONS="-m 512 -boot c -hda $HDIMAGE -vga std $QEMU_NETWORK_CMD"
fi

if [ "x$QEMUOPTIONS" = "x" ]; then
echo "Error: Unable to support this combination of options"
return
fi

SDKDIR="/usr/local/poky/eabi-glibc"
if [ "$MACHINE" = "qemuarm" -o "$MACHINE" = "spitz" -o "$MACHINE" = "borzoi" -o "$MACHINE" = "akita" ]; then
SDKPATH="$SDKDIR/arm/arm-poky-linux-gnueabi/bin:$SDKDIR/arm/bin"
fi

if [ "$MACHINE" = "qemux86" ]; then
SDKPATH="$SDKDIR/i586/i586-poky-linux/bin:$SDKDIR/i586/bin"
fi
PATH=$CROSSPATH:$SDKPATH:$PATH

QEMUBIN=`which $QEMU`

if [ ! -x "$QEMUBIN" ]; then
echo "Error: No QEMU binary '$QEMU' could be found."
return
fi

function _quit() {
if [ -n "$PIDFILE" ]; then
#echo kill `cat $PIDFILE`
kill `cat $PIDFILE`
fi
return
}

DISTCCD=`which distccd`
PIDFILE=""

trap _quit INT TERM QUIT

if [ -x "$DISTCCD" ]; then
echo "Starting distccd..."
PIDFILE=`mktemp`
$DISTCCD --allow 192.168.7.2 --daemon --pid-file $PIDFILE &
else
echo "Warning: distccd not present, no distcc support loaded."
fi

echo "Running $QEMU using sudo..."
#echo $QEMUBIN -kernel $ZIMAGE $QEMUOPTIONS $SERIALOPTS --append "$KERNCMDLINE"
#sudo $QEMUBIN -kernel $ZIMAGE $QEMUOPTIONS $SERIALOPTS --append "$KERNCMDLINE" || /bin/true
sudo $QEMUBIN $QEMUOPTIONS || /bin/true

trap - INT TERM QUIT
return

Mobile Device Thieving Soon Won’t Pay

by Lisa Morgan

Intel Anti-Theft Technology (Intel AT) is turning perfectly good laptops into bricks and will eventually turn perfectly good smartphones into rocks.  The company is already teaming up with tracking, remote data removal, encryption or PC recovery software vendors, as well as device recovery service providers and OEMs to deter laptop computer theft.  At the request of partners and end customers, the technology will eventually extend to netbooks, MIDs, and smartphones.

Each year millions of laptops and handheld devices are lost or stolen.  According to Processor, two million laptop computers are reported stolen and 97 percent of them are never recovered.  Asurion estimates that 60 million cell phones are lost, stolen or damaged each year.

“Smaller devices are becoming more powerful and [mobile users] want to access to their data from anywhere,” said Mauricio Cuervo, marketing manager, PC Client Group in Intel’s Anti-Theft Services Group.  “We’re starting with laptops but getting requests from partners and end users to support smaller formats.”

Intel AT is included in the new Centrino 2 processor-based laptops.  It provides dedicated security and manageability functions as well as dedicated circuitry and firmware making Intel AT far more difficult to compromise than software solutions alone.  In fact, Absolute Software, PGP, Phoenix Technologies, WinMagic and others are teaming up with Intel to add yet another layer of security.  For example, using Phoenix Technologies, IT administrators are able to manage and  remotely remove or retrieve data from a lost or stolen laptop.  With the addition of Intel AT administrators can also render the machine completely inoperable.

In addition to working with ISVs and recovery service providers like Absolute Software, Intel provides hardware and an SDK so OEMs can make their laptops AT ready.  To take advantage of the technology, the purchaser of a laptop must buy an AT-ready laptop as well as software from the likes of PGP, WinMagic or Absolute Software.

When a laptop has been reported lost or stolen, or a pre-defined event has been triggered, Intel AT disables the laptop via a “poison pill”.  The poison pill can be delivered over the Internet, locally, or via an SMS message.  Even if the OS is reinstalled, or the hard disk replaced, the laptop remains disabled.  However, the machine can be easily reactivated by administrators, assigned users or both, easily without causing data loss or damage to the PC.

“There are three key areas of anti-theft,” said Cuervo.  “Detection, response, and reactivation.”

Lost laptops can be detected in a number of ways, the most obvious of which is the user notifying the IT department or asset recovery service provider.  When a laptop has been reported lost or stolen, it is flagged in a central server.  When rebooted and connected to the Internet, it automatically receives a poison pill.

Intel AT includes support for pre-boot authentication (PBA) modules which includes a hardware-based PBA login timer and PBA login failure counter to detect potential theft.  The PBA login timer controls the time it takes to login.  The PBA login failure counter monitors failed login attempts and triggers a response when the number of failed attempts exceed a pre-defined threshold.

Intel AT also supports a rendezvous timer that requires the laptop to check in periodically with a central server. If the laptop fails to check in within the required time frame, a policy-based response triggers a local poison pill.

Intel AT further includes tamper monitoring so if a user tries to alter a key element like the firmware or BIOS, a poison pill is automatically activated locally.  There is also a dedicated controller that blocks the boot process regardless of what device (e.g. hard drive, USB key, CD, DVD, external hard disk, etc) is used to boot the OS.

With solutions from encryption vendors like PGP and WinMagic, there is an additional level of data protection. In addition to disabling computer operation, a poison pill can also block data access by deleting or hiding the end-user credentials or the encryption keys or similar cryptographic material stored in the the chipset.  When a poison pill is triggered, the encryption keys can be deleted or hidden to prevent access to the data, even if the credentials have been compromised.

“If you bind the encryption key to the platform the data in the hard drive is only available to that laptop,” said Cuervo.  “And if you remove the drive you won’t be able to access the data, even if you know the credentials.”

In the absence of any anti-theft protection whatsoever, laptops and the data on them are completely exposed. “If you don’t have any protection you can read and extract the data on the drive.  You can also reformat, reuse or swap out the drive,” said Cuervo.  Not so with Intel AT.

After the poison pill is received, the laptop becomes completely inoperable with or without a new hard drive.  The OS will not boot and cannot be reimaged.

Once disabled, a reactivation screen appears, indicating that the laptop has been disabled and the options to reactivate it.  Administrators can also include a custom message in that screen such as where a third party may return the machine to receive a reward.

Reactivation by an authorized user, administrator or both is quick and easy.  Users can enter a password they pre-defined (if their IT policy allows it) or an administrator can provide the user with a one-time recovery token that only works on that laptop.  The machine can also be reactivated by an administrator who sends a code via a secure text message (which requires the presence of a 3G card).

At the present time, Intel AT is available on some laptops based on the Intel Centrino 2 processor with vPro Technology.  In 2010, Intel AT will expand its reach beyond enterprise customers to consumers as well as small to medium enterprises (SMEs) via the Core i3, Core i5, and Core i7 processors with the proper chipsets.  Because OEMs will be rolling out products in phases, Cuervo suggests consumers contact the OEM to verify the machine is AT capable.

Cuervo also encourages Moblin community members to get their hands on a Core i3, Core i5, or Core i7 system and play with it.

“We’d love to get their feedback because our customers and partners want us to build Intel AT into smaller devices,” he said.

Although he did not provide a timeframe specifying when more mobile devices will be supported, he did say it is likely netbooks will be targeted first, followed by MIDs and smartphones.

ISVs, OEMs, ODMs, service providers and independent developers can get more information about Intel AT here. Cuervo said he can also be contacted directly at Mauricio.cuervo@intel.com and will gladly route inquiries to the appropriate parties.

* All names and brands are the property of their respective owners.

­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­

1. 使用Linux Project Generator(LPG)生成项目。通过LPG图形化的界面，用户可以设置项目类型(终端或图形)，开发语言(C/C++/python)，项目路径，License以及编译参数等内容。当生成项目时，LPG帮助用户生成项目框架，其中包括了代码框架，文档框架以及项目编译时所需的autogen框架文件。

2. 使用Anjuta导入生成的项目。进入Anjuta，通过菜单选择File->New->Project From Existing Source，就能轻松的将项目导入。

3. Coding & Coding

4. 编译。如果是第一次编译(Makefile还未生成)，通过菜单选择Build->Configure project...来检查依赖关系与生成Makefile。如果已经生成了Makefile，通过菜单选择Build->Build project进行编译。

5.远程调试。假设上网本上openssh server, rsync和gdb server都安装好了，那么首先将需要调试的程序部署到上网本上，通过菜单选择Tools->Deploy轻松搞定，通过deploy记录我们可以看到可执行文件被部署的具体位置。接下来我们要远程运行xhost +和gdbserver了，这可以通过Anjuta菜单中Tools->Run Remote来实现。等到gdb server起来后，通过菜单中Run->Debug Remote Target...使用TCP/IP连接到上网本，就能像调试本地程序一样来调试远程的程序了。

6.调试成功后，到了软件发布的时间。使用Moblin Package Creator对应用进行打包，它可以打rpm和deb包。

首先要做一点准备工作：

1. Linux台式机一台，作为开发机，使用Fedora和Ubuntu均可。

2. 安装有Moblin V2镜像的上网本一台，用来调试程序。如果没有，也没有关系。

清单就到此为止，挺简单的吧，呵呵。准备完毕后，我们就要开始搭环境了。

第一步，下载安装Moblin SDK到开发机。下载地址是

http://moblin.org/sites/all/files/moblin-sdk-0.8.tar.bz2。下载完成后找个目录把压缩包解开，编辑目录中的envsetup.sh，将$MOBLIN_TOOLCHAIN的值设成Moblin工具链的实际路径。假如Moblin SDK是在~下解开的，并且解压目录是moblin-sdk-0.8，则需要

export MOBLIN_TOOLCHAIN=~/moblin-sdk-0.8/moblin-cross-toolchain

第二步，下载安装Anjuta。用户直接通过yum或者apt下载安装即可。不过依照本人的使用经历，下载之前要注意下Anjuta的版本，不能太旧，要高于2.4，也不能太新，我一开始装了最新的2.28，结果在安装Moblin的Anjuta插件时报某符号找不到，死活装不上，卸载后安装Anjuta 2.26就天下太平了。

第三步，安装Moblin的Anjuta插件。在http://moblin.org/projects/moblin-anjuta-plug-in上可以下载到预先编译好的安装包，rpm和deb都有，当然也有源码包，可以根据自身需要下载安装。这个插件为Anjuta IDE提供了以下一些功能：

1. 交叉编译使用Autotool的项目。对于使用Linux Project Generator(另一个Moblin.org上的项目)生成的项目有着非常好的支持。

2. 可以将编译好的程序部署到远程的上网本中(通过网络连接)。

3. 可以远程运行上网本中的程序。

4. 可以远程调试上网本中的程序。

插件安装完后重新启动Anjuta，我们要启用Moblin插件并进行设置。选择菜单栏上的”Edit”->”Preferences”，打开Anjuta Preferences对话框。点击右上Installed Plugins标签，在插件列表中选择Moblin SDK，此时在对话框左边就会出现 Moblin SDK，点击Moblin SDK，出现Moblin插件的设置界面。在这里我们要设置两项内容：IDE所使用的工具链和目标机位置。

交叉编译：选择“Use an external toolchain”。之前下载的Moblin SDK中包含了整套工具链，所以只需将SDK root设成SDK安装目录下的moblin-cross-toolchain目录即可。Toolchain triplet设为i586-moblin-linux.

目标机位置：因为手边有上网本，所以选择”Use an external device”，并输入上网本的ip地址。

花开两朵，各表一枝。开发机上的环境差不多搭好了，第四步就该设置上网本了。上网本上已经安装了Moblin V2，为了让开发机可以远程访问和调试，我们需要安装openssh-server, rsync和gdbserver。通过以下命令可以完成上述软件包的安装：

sudo yum install openssh-server rsync gdb-gdbserver

安装完成后，在终端上输入xhost +，使其他用户可以访问X server。

至此，交叉编译与调试环境就搭好了。

目前Moblin软件加油站和Moblin Application Installer还处于开发阶段，仅供测试。

想知道更多内容，可以访问http://garage.moblin.org/welcome-moblin-garage-catalog