来源: 互联网  发布时间: 2014-02-18

如何在qml ListModel 里国际化文字

翻译qml里的文字是，一般使用的 qsTr()，

 

但是如果在ListModel 里用，

比如：

 

ListModel {
    ListElement { title: qsTr( "Calendar" ) ; iconSource: "icons/calendar.png" }

 

 

 

则会报错

ListElement: cannot use script for property value

 

：

 

    import QtQuick 1.0
     
    ListModel {
        ListElement { iconSource: "icons/calendar.png" }
        ListElement { iconSource: "icons/develop.png" }
        ListElement { iconSource: "icons/globe.png" }
        ListElement { iconSource: "icons/mail.png" }
        ListElement { iconSource: "icons/music.png" }
        ListElement { iconSource: "icons/phone.png" }
        function title( index) {
            if ( title[ "text" ] === undefined) {
                title.text = [
                    qsTr( "Calendar" ) ,
                    qsTr( "Setup" ) ,
                    qsTr( "Internet" ) ,
                    qsTr( "Messages" ) ,
                    qsTr( "Music" ) ,
                    qsTr( "Call" )
                ]
            }
            return title.text [ index]
        }
    }

 

 

然后在listview里设置

text: view.model .title ( view.currentIndex )

 

 

    

    来源: 互联网  发布时间: 2014-02-18

spring security原理图及其解释（四）
How requests are authorized?

The final servlet filter in the default Spring Security filter chain, FilterSecurityInterceptor, is the filter responsible for coming up with a decision on whether or not a particular request will be accepted or denied. At this point the FilterSecurityInterceptor filter is invoked, the principal has already been authenticated, so the system knows that they are valid users. Remember that the Authentication interface specifies a method (List<GrantedAuthority> getAuthorities()), which returns a list of authorities for the principal. The authorization process will use the information from this method to determine, for a particular request, whether or not the request should be allowed.

在默认的Spring Security filter链中，最后的servlet filter是FilterSecurityInterceptor，它是负责处理这个特殊的request是否被通过。在这种情况下FilterSecurityInterceptor被触发，而且principal已经被验证，所以系统知道他们是可用的用户。我们知道Authentication接口指定了一个方法（List<GrantedAuthority> getAuthorities()），它返回authorities的数组。授权程序就会用这些信息来决定一个特殊的请求会不会被通过。


Smart object-oriented design is pervasive within the Spring Security framework, and authorization decision management is no exception. Recall from our discussion earlier in the chapter that a component known as the access decision manager is responsible for making authorization determinations.

The implementation of AccessDecisionManager is completely configurable using standard Spring Bean binding and references. The default AccessDecisionManager implementation provides an access granting mechanism based on AccessDecisionVoter and vote aggregation.

A voter is an actor in the authorization sequence whose job is to evaluate any or all of the following:

The context of the request for a secured resource (such as URL requesting
IP address)
The credentials (if any) presented by the user
The secured resource being accessed
The configuration parameters of the system, and the resource itself


As you may have guessed from the design of access decision-related objects and interfaces, this portion of Spring Security has been designed so that it can be applicable to authentication and access control scenarios that aren't exclusively in the web domain. We'll encounter voters and access decision managers when we look at method-level security in Chapter 5, Fine-Grained Access Control.

When we put this all together, the overall flow of the "default authentication check for web requests" is similar to the following diagram:


注意上面是loop voters

Configuration of access decision aggregation

Spring Security does actually allow configuration of the AccessDecisionManager in the security namespace. The access-decision-manager-ref attribute on the <http> element allows you to specify a Spring Bean reference to an implementation of AccessDecisionManager. Spring Security ships with three implementations of this interface, all in the o.s.s.access.vote package:



第一个有一个同意就通过；第二个票数多的通过；第三全得通过才能通过。

Configuring to use a UnanimousBased access decision manager

If we want to modify our application to use the UnanimousBased access decision manager, we'd require two modifications. Let's add the access-decision-manager-ref attribute to the <http> element:

如果我们想用UnanimousBased Manager，我们需要修改两个地方。首先添加access-decision-manager-ref元素：

<http auto-config="true" access-decision-manager-ref="unanimousBased">

This is a standard Spring Bean reference, so this should correspond to the id attribute of a bean. We'll go on and declare the bean (in dogstore-base.xml) now, with the same ID we referenced:

这是一个标准Spring Bean,所以他应该对应一个bean id。现在我们声明这个bean：

<bean 
id="unanimousBased">
<property name="decisionVoters">
<list>
<ref bean="roleVoter"/>
<ref bean="authenticatedVoter"/>
</list>
</property>
</bean>
<bean 
id="roleVoter"/>
<bean class="org.springframework.security.access.vote.
AuthenticatedVoter" id="authenticatedVoter"/>

You may be wondering what the decisionVoters property is about. This property is auto-configured until we declare our own AccessDecisionManager. The default AccessDecisionManager requires us to declare the list of voters who are consulted to arrive at the authentication decisions. The two voters listed here are the defaults supplied by the security namespace configuration.

你或许会奇怪decisionVoters是干什么的。当我们声明了AccessDecisionManager的时候，这个属性是自动装配的。默认的AccessDecisionManager要求我们声明一个系列的voter，用它们来决定是否验证通过。这里列出的两个voter是spring默认提供的。

Unfortunately, Spring Security doesn't come supplied with a wide variety of voters, but it is trivial to implement the AccessDecisionVoter interface and add our own implementation. We'll see an example of this in Chapter 6.

不幸的是Spring Security没有为我们提供需要不同的voter实现，但是我们可以实现AccessDecisionVoter来添加我们的实现。

The two voter implementations that we reference here do the following:

    

    来源: 互联网  发布时间: 2014-02-18

zxing 源码解读日志 02

zxing并不适合于单图像识别，或者作者本来就把它作为视频识别来处理的。因为预处理的时候会强制缩放原始图像到一定的大小，作者没有提供比较合适的图片检测接口。又或者你必需预先设定好剪裁的区域。否则识别效果很差，难道是缩放致？？？

 

iPhone拍摄出来的图片居然是有方向的，晕哦。处理的时候要注意。

//************************************************************************************

基本完成阅读：

1 定位点判断不需要修改

2 实际上红色channel看起来反而对红色表格线隐藏效果更好，但是这个和打印效果、光源有太大关系，测试了一下，只取红色channel对数据读取有影响，作用不大，放弃。

3 或者应该比对一下zbar做一些比较，粗略看了一下，zbar的代码会更难看，因为基本都堆在一个文件中做解码。

4 有一个想法就是在每一次扫描中都把bit matrix叠加在某个数组中，做一个经验积累数组，再以此读取数据，这个几乎要推翻整个结构重写了，可能堆3G／3GS的成像比较模糊的情况会有所改善吧。

 

Shappy Say

2012／02／13