hexsha
stringlengths 40
40
| size
int64 5
1.04M
| ext
stringclasses 6
values | lang
stringclasses 1
value | max_stars_repo_path
stringlengths 3
344
| max_stars_repo_name
stringlengths 5
125
| max_stars_repo_head_hexsha
stringlengths 40
78
| max_stars_repo_licenses
sequencelengths 1
11
| max_stars_count
int64 1
368k
⌀ | max_stars_repo_stars_event_min_datetime
stringlengths 24
24
⌀ | max_stars_repo_stars_event_max_datetime
stringlengths 24
24
⌀ | max_issues_repo_path
stringlengths 3
344
| max_issues_repo_name
stringlengths 5
125
| max_issues_repo_head_hexsha
stringlengths 40
78
| max_issues_repo_licenses
sequencelengths 1
11
| max_issues_count
int64 1
116k
⌀ | max_issues_repo_issues_event_min_datetime
stringlengths 24
24
⌀ | max_issues_repo_issues_event_max_datetime
stringlengths 24
24
⌀ | max_forks_repo_path
stringlengths 3
344
| max_forks_repo_name
stringlengths 5
125
| max_forks_repo_head_hexsha
stringlengths 40
78
| max_forks_repo_licenses
sequencelengths 1
11
| max_forks_count
int64 1
105k
⌀ | max_forks_repo_forks_event_min_datetime
stringlengths 24
24
⌀ | max_forks_repo_forks_event_max_datetime
stringlengths 24
24
⌀ | content
stringlengths 5
1.04M
| avg_line_length
float64 1.14
851k
| max_line_length
int64 1
1.03M
| alphanum_fraction
float64 0
1
| lid
stringclasses 191
values | lid_prob
float64 0.01
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ffad4428260d0ad6a3fc81cf6e02b635741b15c8 | 4,018 | md | Markdown | _posts/JS/2018-02-08-js-scope.md | Tate-Young/Tate-Young.github.io | a1cb932c6764f995e9b6931cce83a1c14addbbca | [
"MIT"
] | 6 | 2018-02-04T12:08:53.000Z | 2019-12-25T11:12:42.000Z | _posts/JS/2018-02-08-js-scope.md | Tate-Young/Tate-Young.github.io | a1cb932c6764f995e9b6931cce83a1c14addbbca | [
"MIT"
] | 70 | 2019-01-31T10:05:10.000Z | 2022-03-22T09:18:54.000Z | _posts/JS/2018-02-08-js-scope.md | Tate-Young/Tate-Young.github.io | a1cb932c6764f995e9b6931cce83a1c14addbbca | [
"MIT"
] | null | null | null | ---
layout: blog
front: true
comments: True
flag: JS
background: blue
category: 前端
title: 执行上下文与作用域
date: 2018-02-09 11:25:00 GMT+0800 (CST)
background-image: http://davidshariff.com/blog/wp-content/uploads/2012/06/es1.gif
tags:
- JavaScript
---
# {{ page.title }}
## 什么是执行上下文
### 执行上下文
**可执行代码(executable code)** 包含三种
* 全局代码(global code) - 代码首次执行的默认环境
* 函数代码(function code) - 执行流进入函数体
* eval 代码(eval code) - 执行 eval 方法
**执行上下文(execution context)**: 也叫执行环境，当 JavaScript 执行一段可执行代码时，会创建对应的执行上下文，全局执行上下文即是最外围的一个执行环境。一个执行上下文的生命周期可以分为两个阶段:
* 创建阶段 - 执行上下文会分别创建变量对象，建立作用域链，以及确定 this 的指向。
* 代码执行阶段 - 完成变量赋值，函数引用，以及执行其他代码。
对于每个执行上下文，都有三个重要属性：
* **变量对象(variable object)**
* **作用域链(scope chain)**
* [**this**]( {{site.url}}/2018/01/30/js-this.html )
```js
// ---------------global context---------------
var name = 'Tate';
function person(){
// ---------------execution context---------------
var anotherName = 'Snow';
var age = 18;
function sayName() {
// ---------------execution context---------------
return anotherName;
}
function sayAge() {
// ---------------execution context---------------
return age;
}
console.log('name:%s & age:%s', sayName(), sayAge());
}
```
### 执行上下文栈
**执行上下文栈(execution context stack)** : 即[调用栈]( {{site.url}}/2018/02/05/js-event-loop.html )，也称为执行栈。管理所有生成的执行上下文。
```js
// 一旦上下文执行完毕之后, 它就会从栈中弹出并且返回控制权到下一个上下文当中，直到全局上下文又再次被访问。
(function foo(i) {
if (i === 3) {
return;
} else {
foo(++i);
}
}(0));
```
## 变量对象
**变量对象(variable object)** 是与执行上下文相关的数据作用域，存储了在执行上下文中定义的所有变量和函数声明。变量对象对于程序而言是不可读的，只有编译器才有权访问变量对象。
**活动对象(activation object)** 是在进入函数上下文时刻被创建的，它通过函数的 arguments 属性初始化。随后，它被当做变量对象用于变量初始化。
> 未进入执行阶段之前，变量对象(VO)中的属性都不能访问！但是进入执行阶段之后，变量对象(VO)转变为了活动对象(AO)，里面的属性都能被访问了，然后开始进行执行阶段的操作。
## 作用域
JavaScript 采用 **词法作用域(lexical scoping)**，也就是静态作用域，用来确定当前执行代码对变量的访问权限。分为全局作用域和局部作用域(函数作用域)，ES6 中新增块级作用域。函数的作用域在函数定义的时候就决定了。
## 作用域链
当查找变量的时候，会先从当前上下文的变量对象中查找，如果没有找到，就会从上层执行上下文的变量对象中查找，一直找到全局上下文的变量对象，也就是全局对象。这样由多个执行上下文的变量对象构成的链表就叫做**作用域链**。
### [[scope]]
在定义函数时， **[[scope]]** 内部属性包含了函数被创建的作用域中对象的集合，这个集合被称为函数的作用域链，它决定了哪些数据能被函数访问。
```js
function foo() {
function bar() {}
}
```
当函数在创建时，各自的 [[scope]] 属性可抽象化理解为:
```js
foo.[[scope]] = [
globalContext.VO
];
bar.[[scope]] = [
fooContext.AO,
globalContext.VO
];
```
> 作用域链是一个由变量对象组成的带头结点的单向链表，其主要作用就是用来进行变量查找。而[[scope]]属性是一个指向这个链表头结点的指针。
### 构建过程
```js
var scope = 'global scope';
function checkscope(){
var scope2 = 'local scope';
return scope2;
}
checkscope();
```
作用域链的构建过程可抽象化为:
1、checkscope 函数被创建，保存作用域链到内部属性 [[scope]];
```js
checkscope.[[scope]] = [
globalContext.VO
];
```
2、 执行 checkscope 函数，创建 checkscope 函数执行上下文，并被压入执行上下文栈上;
3、 checkscope 函数在执行前:
第一步：复制函数 [[scope]] 属性创建作用域链;
```js
checkscopeContext = {
scope: checkscope.[[scope]],
}
```
第二步：用 arguments 创建活动对象，随后初始化活动对象，加入形参、函数声明、变量声明;
```js
checkscopeContext = {
AO: {
arguments: {
length: 0
},
scope2: undefined
}，
scope: checkscope.[[scope]],
}
```
第三步：将活动对象压入 checkscope 作用域链顶端。
```js
checkscopeContext = {
AO: {
arguments: {
length: 0
},
scope2: undefined
},
scope: [AO, [[scope]]]
}
```
4、 开始执行函数，随着函数的执行，修改 AO 的属性值;
```js
checkscopeContext = {
AO: {
arguments: {
length: 0
},
scope2: 'local scope'
},
scope: [AO, [[scope]]]
}
```
5、 查找到 scope2 的值，返回后函数执行完毕，函数上下文从执行上下文栈中弹出。
> 作用域链的前端始终是当前的执行上下文中的变量对象，终端是全局执行上下文中的变量对象。
## 参考链接
1. [What is the Execution Context & Stack in JavaScript?](http://davidshariff.com/blog/what-is-the-execution-context-in-javascript/) By David Shariff
1. [JavaScript: Execution Context, Call Stack, and Event Queue](https://medium.com/@Alexandra2XU/javascript-execution-context-call-stack-and-event-queue-d58b672d76f7) By Alexandra Williams
1. [JavaScript 深入之作用域链](https://github.com/mqyqingfeng/Blog/issues/6) By mqyqingfeng
1. [一道 js 面试题引发的思考](https://github.com/kuitos/kuitos.github.io/issues/18) By kuitos
| 19.793103 | 188 | 0.668741 | yue_Hant | 0.606729 |
ffad53ece5c9eadf5404c396ad7f487e370fdd40 | 2,562 | md | Markdown | packages/plugin-madrun/README.md | oprogramador/putout | 54142952910f3be4830734cee502abd0306d8f82 | [
"MIT"
] | null | null | null | packages/plugin-madrun/README.md | oprogramador/putout | 54142952910f3be4830734cee502abd0306d8f82 | [
"MIT"
] | null | null | null | packages/plugin-madrun/README.md | oprogramador/putout | 54142952910f3be4830734cee502abd0306d8f82 | [
"MIT"
] | null | null | null | # @putout/plugin-madrun [![NPM version][NPMIMGURL]][NPMURL] [![Dependency Status][DependencyStatusIMGURL]][DependencyStatusURL]
[NPMIMGURL]: https://img.shields.io/npm/v/@putout/plugin-madrun.svg?style=flat&longCache=true
[NPMURL]: https://npmjs.org/package/@putout/plugin-madrun"npm"
[DependencyStatusURL]: https://david-dm.org/coderaiser/putout?path=packages/plugin-madrun
[DependencyStatusIMGURL]: https://david-dm.org/coderaiser/putout.svg?path=packages/plugin-madrun
`putout` plugin adds ability to fix issues with [madrun](https://github.com/coderaiser/madrun) config file.
## Install
```
npm i putout @putout/plugin-madrun -D
```
Add `.putout.json` with:
```json
{
"plugins": {
"madrun": "on"
]
}
```
## Rules
```json
{
"rules": {
"madrun/add-function": "on",
"madrun/add-fix-lint": "on",
"madrun/add-run": "on",
"madrun/call-run": "on",
"madrun/convert-run-argument": "on",
"madrun/rename-series-to-run": "on",
"madrun/rename-eslint-to-putout": "on",
}
}
```
# add-function
## ❌ Incorrect code example
```js
module.exports = {
'hello': 'world'
};
```
## ✅ Correct code Example
```js
module.exports = {
'hello': () => 'world'
};
```
# add-fix-lint-
## ❌ Incorrect code example
```js
const {run} = require('madrun');
module.exports = {
'lint': 'putout lib test',
};
```
## ✅ Correct code Example
```js
const {run} = require('madrun');
module.exports = {
'lint': 'putout lib test',
'fix:lint': run('lint', '--fix'),
};
```
# add-run
## ❌ Incorrect code example
```js
module.exports = {
'lint': 'putout lib test',
};
```
## ✅ Correct code Example
```js
const {run} = require('madrun');
module.exports = {
'lint': 'putout lib test',
};
```
# add-madrun-to-lint
## ❌ Incorrect code example
```js
module.exports = {
'lint': () => `eslint lib test --ignore-pattern test/fixture`,
};
```
## ✅ Correct code Example
```js
module.exports = {
'lint': () => `eslint lib test madrun.js --ignore-pattern test/fixture`,
};
```
# convert-run-argument
## ❌ Incorrect code example
```js
module.exports = {
'hello': () => run(['a']),
};
```
## ✅ Correct code Example
```js
module.exports = {
'hello': () => run('a'),
};
```
# rename-eslint-to-putout
## ❌ Incorrect code example
```js
module.exports = {
'lint': 'eslint lib test --ignore test/fixture',
};
```
## ✅ Correct code Example
```js
module.exports = {
'lint': 'putout lib test',
};
```
## License
MIT
| 15.913043 | 127 | 0.590945 | kor_Hang | 0.267737 |
ffad6778d985de4ef8bd6ff65bd5da6c54b1396d | 18 | md | Markdown | README.md | billybui/test-parcel-app | 5c4d8436712a778c694085ff9376e5458bb1cc18 | [
"MIT"
] | null | null | null | README.md | billybui/test-parcel-app | 5c4d8436712a778c694085ff9376e5458bb1cc18 | [
"MIT"
] | null | null | null | README.md | billybui/test-parcel-app | 5c4d8436712a778c694085ff9376e5458bb1cc18 | [
"MIT"
] | null | null | null | # test-parcel-app
| 9 | 17 | 0.722222 | ita_Latn | 0.526219 |
ffade87325a3756bc1e84b0b2529b1e1c0f4808f | 1,238 | md | Markdown | Suryaraj/Covid_Analysis/README.md | nishikant481/rewarding_project | d17c67a66f61c3d641f4d48b12c06efbd83b27aa | [
"MIT"
] | 2 | 2021-10-02T12:27:01.000Z | 2021-10-03T15:07:13.000Z | Suryaraj/Covid_Analysis/README.md | nishikant481/rewarding_project | d17c67a66f61c3d641f4d48b12c06efbd83b27aa | [
"MIT"
] | 10 | 2021-10-01T16:40:18.000Z | 2021-11-15T14:32:17.000Z | Suryaraj/Covid_Analysis/README.md | nishikant481/rewarding_project | d17c67a66f61c3d641f4d48b12c06efbd83b27aa | [
"MIT"
] | 29 | 2021-10-01T15:59:17.000Z | 2021-10-30T11:35:44.000Z | # Covid Analysis
The world is perplexed by the outbreak of a new severe acute respiratory syndrome. The new coronavirus(COVID-19), reported in December 2019, had its epicentre in Wuhan,
Hubei province, in The People's Republic Of China and has spread to several countries.
It was declared as a public health emergency by the World Health Organisation.
We got this dataset from a website with the URL as https://worldometers.info/coronavirus.
Now, this dataset consists of the statistical data of 188 countries of the world regarding
the number of confirmed cases, the deaths and the recoveries and other related information.
In this project we are going to analyse the same dataset using Python Pandas on windows machine
but the project can be run on any machine support Python and Pandas. Besides pandas we also used
matplotlib python module for visualization of this dataset.
The whole project is divided into four major parts ie reading, analysis, visualization and export.
All these part are further divided into menus for easy navigation.
NOTE: Python is case-SENSITIVE so type exact Column Name wherever required.
| 65.157895 | 168 | 0.73748 | eng_Latn | 0.999428 |
ffae4e2d4bae30cdcffbc34842110ad4585b13aa | 1,863 | md | Markdown | articles/azure-maps/how-to-manage-account-keys.md | hcyang1012/azure-docs.ko-kr | e0844b72effe5055ad69dc006a9eb3c4656efc80 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-maps/how-to-manage-account-keys.md | hcyang1012/azure-docs.ko-kr | e0844b72effe5055ad69dc006a9eb3c4656efc80 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-maps/how-to-manage-account-keys.md | hcyang1012/azure-docs.ko-kr | e0844b72effe5055ad69dc006a9eb3c4656efc80 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Azure 포털에서 Azure Maps 계정 관리 | 마이크로소프트 Azure 지도
description: 이 문서에서는 Azure 포털을 사용하여 Microsoft Azure Maps 계정을 관리하는 방법을 알아봅니다.
author: philmea
ms.author: philmea
ms.date: 01/27/2020
ms.topic: conceptual
ms.service: azure-maps
services: azure-maps
manager: timlt
ms.openlocfilehash: 42247cc576e55c7c504e9832017af336439b11b9
ms.sourcegitcommit: 2ec4b3d0bad7dc0071400c2a2264399e4fe34897
ms.translationtype: MT
ms.contentlocale: ko-KR
ms.lasthandoff: 03/28/2020
ms.locfileid: "80335545"
---
# <a name="manage-your-azure-maps-account"></a>Azure Maps 계정 관리
Azure Portal을 통해 Azure Maps 계정을 관리할 수 있습니다. 계정이 생기면 웹 사이트 또는 모바일 애플리케이션에서 API를 구현할 수 있습니다.
Azure 구독이 아직 없는 경우 시작하기 전에 [체험 계정](https://azure.microsoft.com/free/?WT.mc_id=A261C142F)을 만듭니다.
## <a name="create-a-new-account"></a>새 계정 만들기
1. [Azure 포털에](https://portal.azure.com)로그인합니다.
2. Azure Portal의 왼쪽 위 모서리에서 **리소스 만들기**를 선택합니다.
3. **Maps**를 검색하고 선택합니다. 그런 다음 **을 선택합니다.**
4. 새로운 계정에 대한 정보를 입력합니다.
[](./media/how-to-manage-account-keys/new-account-portal.png#lightbox)
## <a name="delete-an-account"></a>계정 삭제
Azure Portal에서 계정을 삭제할 수 있습니다. 계정 개요 페이지로 이동하여 **삭제**를 선택합니다.
[](./media/how-to-manage-account-keys/account-delete-portal.png#lightbox)
그러면 확인 페이지가 표시됩니다. 계정 이름을 입력하여 계정 삭제를 확인할 수 있습니다.
## <a name="next-steps"></a>다음 단계
Azure Maps를 사용하여 인증을 설정하고 Azure Maps 구독 키를 받는 방법을 알아봅니다.
> [!div class="nextstepaction"]
> [인증 관리](how-to-manage-authentication.md)
Azure Maps 계정의 가격 책정 계층을 관리하는 방법을 알아봅니다.
> [!div class="nextstepaction"]
> [가격 책정 계층 관리](how-to-manage-pricing-tier.md)
Azure Maps 계정에 대한 API 사용량 메트릭을 확인하는 방법을 알아봅니다.
> [!div class="nextstepaction"]
> [사용 메트릭 보기](how-to-view-api-usage.md)
| 32.684211 | 165 | 0.733226 | kor_Hang | 0.999763 |
ffae7b2e0456c091b4bc0134ccedb23b9db26fe0 | 95 | md | Markdown | README.md | manalijrc/ManaliRege-Colt | 3af4183d3633abe66933ade8a34d1bd150242726 | [
"MIT"
] | null | null | null | README.md | manalijrc/ManaliRege-Colt | 3af4183d3633abe66933ade8a34d1bd150242726 | [
"MIT"
] | null | null | null | README.md | manalijrc/ManaliRege-Colt | 3af4183d3633abe66933ade8a34d1bd150242726 | [
"MIT"
] | null | null | null | # ManaliRege-Colt
Master's thesis research in the May-Collado Lab at the University of Vermont
| 31.666667 | 76 | 0.810526 | eng_Latn | 0.945781 |
ffaeaa41f7d18116da0382500cf49afc0a653085 | 1,886 | md | Markdown | leetCodeSolution/subsets/README.md | slowy07/c-lesson | 89f3b90c75301d59f64a6659eb8da8a3f8be1582 | [
"MIT"
] | 2 | 2020-06-02T17:32:09.000Z | 2020-11-29T01:24:52.000Z | leetCodeSolution/subsets/README.md | slowy07/c-lesson | 89f3b90c75301d59f64a6659eb8da8a3f8be1582 | [
"MIT"
] | null | null | null | leetCodeSolution/subsets/README.md | slowy07/c-lesson | 89f3b90c75301d59f64a6659eb8da8a3f8be1582 | [
"MIT"
] | 2 | 2020-09-23T14:40:28.000Z | 2020-11-26T12:32:44.000Z | ## subsests (medium)
**solution 1 DFS**
```cpp
class Solution {
vector<vector<int>> ans;
void dfs(vector<int> &A, int i, vector<int> &s) {
if (i == A.size()) {
ans.push_back(s);
return;
}
s.push_back(A[i]); // Pick A[i]
dfs(A, i + 1, s);
s.pop_back(); // Skip A[i]
dfs(A, i + 1, s);
}
public:
vector<vector<int>> subsets(vector<int>& A) {
vector<int> s;
dfs(A, 0, s);
return ans;
}
};
```
**solution 2 backtrack**
```cpp
class Solution {
vector<vector<int>> ans;
void dfs(vector<int> &A, int start, int len, vector<int> &s) {
if (s.size() == len) {
ans.push_back(s);
return;
}
for (int i = start; i <= A.size() - len + s.size(); ++i) {
s.push_back(A[i]);
dfs(A, i + 1, len, s);
s.pop_back(); // backtrack
}
}
public:
vector<vector<int>> subsets(vector<int>& A) {
vector<int> s;
for (int len = 0; len <= A.size(); ++len) dfs(A, 0, len, s);
return ans;
}
};
```
**solution 3 bit mask**
```cpp
class Solution {
public:
vector<vector<int>> subsets(vector<int>& A) {
int N = 1 << A.size();
vector<vector<int>> ans(N);
for (int i = 0; i < A.size(); ++i) {
for (int j = 0; j < N; ++j) {
if (j >> i & 1) ans[j].push_back(A[i]);
}
}
return ans;
}
};
```
**solution 4 DP**
```cpp
class Solution {
public:
vector<vector<int>> subsets(vector<int>& A) {
vector<vector<int>> ans(1);
for (int i = 0; i < A.size(); ++i) {
int len = ans.size();
for (int j = 0; j < len; ++j) {
ans.push_back(ans[j]);
ans.back().push_back(A[i]);
}
}
return ans;
}
};
```
| 23 | 68 | 0.437964 | eng_Latn | 0.170772 |
ffaebaa33bbb7e027734f32b2ec792973ad7fc58 | 117 | md | Markdown | 3d-flower-generator/CREDITS.md | secretrobotron/fun | 4d013a28586decccc5ca47966a9127038ad915f5 | [
"MIT"
] | null | null | null | 3d-flower-generator/CREDITS.md | secretrobotron/fun | 4d013a28586decccc5ca47966a9127038ad915f5 | [
"MIT"
] | null | null | null | 3d-flower-generator/CREDITS.md | secretrobotron/fun | 4d013a28586decccc5ca47966a9127038ad915f5 | [
"MIT"
] | null | null | null | * Skyboxes by Emil Persson, aka Humus from https://opengameart.org/content/forest-skyboxes and http://www.humus.name
| 58.5 | 116 | 0.786325 | eng_Latn | 0.342532 |
ffafc9d7bb65c5a852f4e6ed8c8bbcff64c04d71 | 7,457 | md | Markdown | articles/active-directory/hybrid/how-to-connect-sso-how-it-works.md | andreatosato/azure-docs.it-it | 7023e6b19af61da4bb4cdad6e4453baaa94f76c3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/hybrid/how-to-connect-sso-how-it-works.md | andreatosato/azure-docs.it-it | 7023e6b19af61da4bb4cdad6e4453baaa94f76c3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/hybrid/how-to-connect-sso-how-it-works.md | andreatosato/azure-docs.it-it | 7023e6b19af61da4bb4cdad6e4453baaa94f76c3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Azure AD Connect: funzionamento dell'accesso Single Sign-On facile | Microsoft Docs"
description: In questo articolo viene descritto il funzionamento dell'accesso Single Sign-On facile di Azure Active Directory.
services: active-directory
keywords: che cos'è Azure AD Connect, installare Active Directory, componenti richiesti per Azure AD, SSO, Single Sign-On
documentationcenter: ''
author: billmath
manager: mtillman
ms.assetid: 9f994aca-6088-40f5-b2cc-c753a4f41da7
ms.service: active-directory
ms.workload: identity
ms.tgt_pltfrm: na
ms.devlang: na
ms.topic: article
ms.date: 07/19/2018
ms.component: hybrid
ms.author: billmath
ms.openlocfilehash: 83a36c81ad88ccb37fe4a258f895b1e1cbe9299f
ms.sourcegitcommit: cf606b01726df2c9c1789d851de326c873f4209a
ms.translationtype: HT
ms.contentlocale: it-IT
ms.lasthandoff: 09/19/2018
ms.locfileid: "46304550"
---
# <a name="azure-active-directory-seamless-single-sign-on-technical-deep-dive"></a>Accesso Single Sign-On facile di Azure Active Directory: approfondimento tecnico
Questo articolo riporta i dettagli tecnici del funzionamento dell'accesso Single Sign-On (SSO) facile di Azure Active Directory.
## <a name="how-does-seamless-sso-work"></a>Come opera la SSO facille?
Questa sezione è composta da tre parti:
1. Installazione della funzionalità di accesso SSO facile.
2. Funzionamento di una transazione di accesso utente singolo in un browser Web con accesso SSO facile.
3. Funzionamento di una transazione di accesso utente singolo in un client nativo con accesso SSO facile.
### <a name="how-does-set-up-work"></a>Installazione
L'accesso SSO facile viene abilitato con Azure AD Connect, come illustrato [qui](how-to-connect-sso-quick-start.md). Durante l'abilitazione della funzionalità, si verificano i passaggi seguenti:
- Un account computer denominato `AZUREADSSOACC`, che rappresenta Azure AD, viene creato in Active Directory (AD) locale in ciascuna foresta di AD.
- La chiave di decrittografia Kerberos dell'account computer viene condivisa in modo sicuro con Azure AD. Se sono presenti più foreste Active Directory, ognuna avrà la propria chiave di decrittografia di Kerberos.
- Vengono anche creati due nomi dell'entità servizio (SPN, Service Principal Name) Kerberos per rappresentare due URL usati durante l'accesso ad Azure AD.
>[!NOTE]
> L'account computer e gli SPN Kerberos vengono creati in ogni foresta di AD che si sincronizza con Azure AD, tramite Azure AD Connect, e per i cui utenti si vuole abilitare l'accesso SSO facile. Spostare l'account computer `AZUREADSSOACC` in un'unità organizzativa in cui sono archiviati altri account computer per assicurarsi che venga gestito allo stesso modo e non venga eliminato.
>[!IMPORTANT]
>È consigliabile [rinnovare la chiave di decrittografia di Kerberos](how-to-connect-sso-faq.md#how-can-i-roll-over-the-kerberos-decryption-key-of-the-azureadssoacc-computer-account) dell'account computer `AZUREADSSOACC` almeno ogni 30 giorni.
Una volta completata l'installazione, l'accesso SSO facile funziona esattamente come qualsiasi altro accesso che usa l'autenticazione integrata di Windows (NTLM).
### <a name="how-does-sign-in-on-a-web-browser-with-seamless-sso-work"></a>Funzionamento dell'accesso in un browser Web con accesso SSO facile.
Il flusso di accesso in un browser Web è il seguente:
1. L'utente tenta di accedere a un'applicazione Web, ad esempio, l'app Web di Outlook https://outlook.office365.com/owa/) da un dispositivo aziendale appartenente a un dominio all'interno della rete aziendale.
2. Se l'utente non ha ancora eseguito l'accesso, viene reindirizzato alla pagina di accesso di Azure AD.
3. L'utente digita il nome utente nella pagina di accesso di Azure AD.
>[!NOTE]
>Per [determinate applicazioni](./how-to-connect-sso-faq.md#what-applications-take-advantage-of-domainhint-or-loginhint-parameter-capability-of-seamless-sso) i passaggi 2 e 3 vengono ignorati.
4. Tramite l'uso di JavaScript in background, Azure AD richiede al browser, tramite una risposta di tipo 401 Non autorizzato, di specificare un ticket Kerberos.
5. Il browser, a sua volta, richiede un ticket ad Active Directory per l'account computer `AZUREADSSOACC` che rappresenta Azure AD.
6. Active Directory individua l'account computer e restituisce un ticket Kerberos al browser, crittografato con il segreto dell'account computer.
7. Il browser inoltra il ticket Kerberos acquisito da Active Directory ad Azure AD.
8. Azure AD esegue la decrittografia del ticket Kerberos, che include l'identità dell'utente connesso al dispositivo aziendale, usando la chiave già condivisa.
9. Dopo la valutazione, Azure AD restituisce un token all'applicazione oppure chiede all'utente di eseguire prove aggiuntive, ad esempio l'autenticazione a più fattori.
10. Se l'accesso dell'utente ha esito positivo, l'utente può accedere all'applicazione.
Il diagramma seguente illustra tutti i componenti e i passaggi interessati.
L'accesso SSO facile è una funzionalità opportunistica, il che significa che, se ha esito negativo, l'esperienza di accesso dell'utente ritorna al comportamento normale, ovvero l'utente dovrà immettere la propria password per eseguire l'accesso.
### <a name="how-does-sign-in-on-a-native-client-with-seamless-sso-work"></a>Funzionamento dell'accesso in un client nativo con accesso SSO facile.
Il flusso di accesso in un client nativo è il seguente:
1. L'utente tenta di accedere a un'applicazione nativa, ad esempio il client Outlook, da un dispositivo aziendale appartenente a un dominio all'interno della rete aziendale.
2. Se l'utente non ha ancora eseguito l'accesso, l'applicazione nativa recupera il relativo nome utente dalla sessione di Windows del dispositivo.
3. L'app invia il nome utente ad Azure AD e recupera l'endpoint MEX di WS-Trust del tenant.
4. L'app esegue quindi una query sull'endpoint MEX di WS-Trust per vedere se è disponibile l'endpoint per l'autenticazione integrata.
5. Se il passaggio 4 ha esito positivo, viene generata una richiesta di verifica Kerberos.
6. Se l'app è in grado di recuperare il ticket Kerberos, lo inoltra fino all'endpoint per l'autenticazione integrata di Azure AD.
7. Azure AD decrittografa il ticket Kerberos e lo convalida.
8. Azure AD consente l'accesso dell'utente e invia un token SAML all'app.
9. L'app invia quindi il token SAML all'endpoint token OAuth2 di Azure AD.
10. Azure AD convalida il token SAML e invia all'app un token di accesso e un token di aggiornamento per la risorsa specificata, nonché un token ID.
11. L'utente ottiene l'accesso alla risorsa dell'app.
Il diagramma seguente illustra tutti i componenti e i passaggi interessati.
## <a name="next-steps"></a>Passaggi successivi
- [**Guida introduttiva**](how-to-connect-sso-quick-start.md): avvio ed esecuzione di Accesso SSO facile di Azure AD.
- [**Domande frequenti**](how-to-connect-sso-faq.md): risposte alle domande più frequenti.
- [**Risoluzione dei problemi**](tshoot-connect-sso.md): informazioni su come risolvere i problemi comuni relativi a questa funzionalità.
- [**UserVoice**](https://feedback.azure.com/forums/169401-azure-active-directory/category/160611-directory-synchronization-aad-connect): per l'invio di richieste di nuove funzionalità.
| 73.107843 | 385 | 0.797372 | ita_Latn | 0.995313 |
ffb024b3fba661845cf5fdc88c68bd8981a1b566 | 142 | md | Markdown | README.md | Strentz-Paul/Touc_v1 | 35da1443277a3b40fd81c777979c7dfb533c64c8 | [
"MIT"
] | null | null | null | README.md | Strentz-Paul/Touc_v1 | 35da1443277a3b40fd81c777979c7dfb533c64c8 | [
"MIT"
] | null | null | null | README.md | Strentz-Paul/Touc_v1 | 35da1443277a3b40fd81c777979c7dfb533c64c8 | [
"MIT"
] | null | null | null | # Install/Start
To install this project you need to run:
```
make install
```
And to start the project you need to run
```
make start
```
| 10.923077 | 41 | 0.676056 | eng_Latn | 0.996702 |
ffb0df13981072069f5947e5d0ec873f9d07b937 | 1,340 | md | Markdown | _posts/2018-11-4-Web-CTF:-HTML-disabled-buttons.md | SevenWen/SevenWen.github.io | 9828e2865d20b9f1e8c842140a2c7e3ec2343fcf | [
"MIT"
] | null | null | null | _posts/2018-11-4-Web-CTF:-HTML-disabled-buttons.md | SevenWen/SevenWen.github.io | 9828e2865d20b9f1e8c842140a2c7e3ec2343fcf | [
"MIT"
] | null | null | null | _posts/2018-11-4-Web-CTF:-HTML-disabled-buttons.md | SevenWen/SevenWen.github.io | 9828e2865d20b9f1e8c842140a2c7e3ec2343fcf | [
"MIT"
] | null | null | null | ---
layout: post
title: Web CTF:HTML disabled buttons
published: true
---
The very first web task in Roor-me remind me how bad I am at Web🌚
Here's the [question](https://www.root-me.org/en/Challenges/Web-Client/HTML-disabled-buttons?lang=en&action_solution=voir&debut_affiche_solutions=2#pagination_affiche_solutions)
Open the web, we can see this:
The input box and the button is disabled. We can see the source code:
The thing is, we need to remove the disable tag. I thought I cannot change the code directly since it's in the web server. However, when you open the inspector of Firefox, we can change the tag and the box and button will be enabled.
Then we can input some in the box and submit it. The page will return the flag:
Also, we can send the post request directly by python or whatever you want:
```python
import requests // requests module only available in Python >3
// make a POST request with auth-login and authbutton set
r = requests.post('http://challenge01.root-me.org/web-client/ch25/',
data = {'auth-login':'admin', 'authbutton':'Member+Access'});
// print the server's response
print(r.text);
```
| 43.225806 | 234 | 0.748507 | eng_Latn | 0.956078 |
ffb0ec6048df1ad2121c771daec3b1e0fa250b8b | 79 | md | Markdown | docs/changelogs/v22.1.3.7-stable.md | KinderRiven/ClickHouse | 2edc03b3d4a950848720064db82f11581b2e8d8a | [
"Apache-2.0"
] | 2 | 2022-01-10T04:50:22.000Z | 2022-01-10T04:51:42.000Z | docs/changelogs/v22.1.3.7-stable.md | KinderRiven/ClickHouse | 2edc03b3d4a950848720064db82f11581b2e8d8a | [
"Apache-2.0"
] | null | null | null | docs/changelogs/v22.1.3.7-stable.md | KinderRiven/ClickHouse | 2edc03b3d4a950848720064db82f11581b2e8d8a | [
"Apache-2.0"
] | null | null | null | ### ClickHouse release v22.1.3.7-stable FIXME as compared to v22.1.2.2-stable
| 26.333333 | 77 | 0.734177 | eng_Latn | 0.858852 |
ffb1172757a801a09414a66465956fda28493257 | 2,688 | md | Markdown | includes/digital-twins-tutorial-sample-prereqs.md | changeworld/azure-docs.it- | 34f70ff6964ec4f6f1a08527526e214fdefbe12a | [
"CC-BY-4.0",
"MIT"
] | 1 | 2017-06-06T22:50:05.000Z | 2017-06-06T22:50:05.000Z | includes/digital-twins-tutorial-sample-prereqs.md | changeworld/azure-docs.it- | 34f70ff6964ec4f6f1a08527526e214fdefbe12a | [
"CC-BY-4.0",
"MIT"
] | 41 | 2016-11-21T14:37:50.000Z | 2017-06-14T20:46:01.000Z | includes/digital-twins-tutorial-sample-prereqs.md | changeworld/azure-docs.it- | 34f70ff6964ec4f6f1a08527526e214fdefbe12a | [
"CC-BY-4.0",
"MIT"
] | 7 | 2016-11-16T18:13:16.000Z | 2017-06-26T10:37:55.000Z | ---
author: baanders
description: file di inclusione per le esercitazioni di Gemelli digitali di Azure - prerequisiti per il progetto di esempio
ms.service: digital-twins
ms.topic: include
ms.date: 1/20/2021
ms.author: baanders
ms.openlocfilehash: 00d584690d37f1dcc47b785ef533abe888befec3
ms.sourcegitcommit: afb79a35e687a91270973990ff111ef90634f142
ms.translationtype: MT
ms.contentlocale: it-IT
ms.lasthandoff: 04/14/2021
ms.locfileid: "107512114"
---
## <a name="prerequisites"></a>Prerequisiti
Per completare i passaggi di questa esercitazione, è prima necessario completare i prerequisiti seguenti.
Se non si ha una sottoscrizione di Azure, **creare un [account gratuito](https://azure.microsoft.com/free/?WT.mc_id=A261C142F)** prima di iniziare.
### <a name="get-required-resources"></a>Ottenere le risorse necessarie
Per completare questa esercitazione, **[installare Visual Studio 2019,](https://visualstudio.microsoft.com/downloads/)versione 16.5 o** successiva nel computer di sviluppo. Se è già installata una versione precedente, è possibile aprire l'app *Programma di installazione di Visual Studio* nel computer e seguire le istruzioni per aggiornare l'installazione.
>[!NOTE]
> Assicurarsi che l'installazione di Visual Studio 2019 includa il carico **[di lavoro Sviluppo di Azure](/dotnet/azure/configure-visual-studio)**. Questo carico di lavoro consente a un'applicazione di pubblicare funzioni di Azure ed eseguire altre attività di sviluppo di Azure.
L'esercitazione si basa su un progetto di esempio scritto in C#. L'esempio è disponibile qui: [Esempi end-to-end di Gemelli digitali di Azure](/samples/azure-samples/digital-twins-samples/digital-twins-samples). **Ottenere il progetto di** esempio nel computer passando al collegamento di esempio e selezionando il pulsante *Sfoglia codice* sotto il titolo. Verrà visualizzato il repository GitHub per gli esempi, che è possibile scaricare come *. ZIP* selezionando il *pulsante Codice* e *scarica ZIP.*
:::image type="content" source="../articles/digital-twins/media/includes/download-repo-zip.png" alt-text="Screenshot del repository digital-twins-samples in GitHub. Il pulsante Codice è selezionato, producendo una piccola finestra di dialogo in cui è evidenziato il pulsante Scarica ZIP." lightbox="../articles/digital-twins/media/includes/download-repo-zip.png":::
Verrà scaricato un oggetto *. Cartella ZIP* nel computer **comedigital-twins-samples-master.zip**. Decomprimere la cartella ed estrarre i file.
### <a name="prepare-an-azure-digital-twins-instance"></a>Preparare un'istanza di Gemelli digitali di Azure
[!INCLUDE [Azure Digital Twins: instance prereq](digital-twins-prereq-instance.md)]
| 72.648649 | 503 | 0.795387 | ita_Latn | 0.990686 |
ffb145e420ab9d4734b4b62f0934a2f82ff7dd5a | 1,895 | md | Markdown | website/versioned_docs/version-23.6/TestingFrameworks.md | Adriman2/jest | 6e94dbb0f9bc336eeadc6681efe5188d95847dc2 | [
"MIT"
] | 2 | 2018-10-22T15:48:22.000Z | 2019-01-01T12:12:12.000Z | website/versioned_docs/version-23.6/TestingFrameworks.md | Adriman2/jest | 6e94dbb0f9bc336eeadc6681efe5188d95847dc2 | [
"MIT"
] | null | null | null | website/versioned_docs/version-23.6/TestingFrameworks.md | Adriman2/jest | 6e94dbb0f9bc336eeadc6681efe5188d95847dc2 | [
"MIT"
] | 1 | 2018-10-22T15:48:26.000Z | 2018-10-22T15:48:26.000Z | ---
id: version-23.6-testing-frameworks
title: Testing Web Frameworks
original_id: testing-frameworks
---
Although Jest may be considered a React-specific test runner, in fact it is a universal testing platform, with the ability to adapt to any JavaScript library or framework. In this section we'd like to link to community posts and articles about integrating Jest into other popular JS libraries.
## Vue.js
- [Testing Vue.js components with Jest](https://alexjoverm.github.io/series/Unit-Testing-Vue-js-Components-with-the-Official-Vue-Testing-Tools-and-Jest/) by Alex Jover Morales ([@alexjoverm](https://twitter.com/alexjoverm))
- [Jest for all: Episode 1 — Vue.js](https://medium.com/@kentaromiura_the_js_guy/jest-for-all-episode-1-vue-js-d616bccbe186#.d573vrce2) by Cristian Carlesso ([@kentaromiura](https://twitter.com/kentaromiura))
## AngularJS
- [Testing an AngularJS app with Jest](https://medium.com/aya-experience/testing-an-angularjs-app-with-jest-3029a613251) by Matthieu Lux ([@Swiip](https://twitter.com/Swiip))
- [Running AngularJS Tests with Jest](https://engineering.talentpair.com/running-angularjs-tests-with-jest-49d0cc9c6d26) by Ben Brandt ([@benjaminbrandt](https://twitter.com/benjaminbrandt))
## Angular
- [Testing Angular faster with Jest](https://www.xfive.co/blog/testing-angular-faster-jest/) by Michał Pierzchała ([@thymikee](https://twitter.com/thymikee))
## MobX
- [How to Test React and MobX with Jest](https://semaphoreci.com/community/tutorials/how-to-test-react-and-mobx-with-jest) by Will Stern ([@willsterndev](https://twitter.com/willsterndev))
## Redux
- [Writing Tests](https://redux.js.org/recipes/writing-tests) by Redux docs
## Express.js
- [How to test Express.js with Jest and Supertest](http://www.albertgao.xyz/2017/05/24/how-to-test-expressjs-with-jest-and-supertest/) by Albert Gao ([@albertgao](https://twitter.com/albertgao))
| 55.735294 | 293 | 0.766755 | eng_Latn | 0.378895 |
ffb187caccd3194fe6d1e2a3fd68699d4de7dac7 | 589 | md | Markdown | README.md | bradp/horror.watch | 7d6aff54738a85d6bae2f220bd7c9d192971a349 | [
"MIT"
] | 2 | 2021-02-03T22:20:32.000Z | 2022-01-05T09:40:56.000Z | README.md | bradp/horror.watch | 7d6aff54738a85d6bae2f220bd7c9d192971a349 | [
"MIT"
] | 4 | 2021-09-21T10:26:58.000Z | 2022-03-30T21:55:20.000Z | README.md | bradp/horror.watch | 7d6aff54738a85d6bae2f220bd7c9d192971a349 | [
"MIT"
] | 1 | 2021-11-10T12:18:16.000Z | 2021-11-10T12:18:16.000Z | :skull: Watch hundreds of public domain horror movies on [horror.watch](https://horror.watch). 100% free, always
 
Built using [pears.cloud](https://github.com/bradp/pears.cloud), powered by [Hugo](https://gohugo.io), with data from [Archive.org](https://archive.org).
| 84.142857 | 318 | 0.774194 | yue_Hant | 0.281742 |
ffb1f376dd98f3ee51bcf71722d201751ba9fce1 | 1,683 | md | Markdown | src/content/whats-new/2021/03/fedramp-logs-metrics.md | halocameo/docs-website | 57b4d847021b975f8976a0ac3ce676a7ddcbe964 | [
"Apache-2.0",
"CC-BY-4.0"
] | null | null | null | src/content/whats-new/2021/03/fedramp-logs-metrics.md | halocameo/docs-website | 57b4d847021b975f8976a0ac3ce676a7ddcbe964 | [
"Apache-2.0",
"CC-BY-4.0"
] | null | null | null | src/content/whats-new/2021/03/fedramp-logs-metrics.md | halocameo/docs-website | 57b4d847021b975f8976a0ac3ce676a7ddcbe964 | [
"Apache-2.0",
"CC-BY-4.0"
] | null | null | null | ---
title: 'FedRAMP: Logs and Metrics now certified'
summary: 'Protecting your data is our highest priority, which is why we achieved the US Government’s rigorous FedRAMP Moderate certification in 2020. And now we’re adding support for Logs and Metrics to our long list of supported services.'
releaseDate: '2021-03-31'
learnMoreLink: 'https://docs.newrelic.com/docs/security/security-privacy/compliance/fedramp-compliant-endpoints/'
---
## Accelerate government IT modernization
Protecting your data is our highest priority, which is why we achieved the US Government’s rigorous FedRAMP Moderate certification in 2020. And now we’re adding support for Logs and Metrics to our long list of supported services.
New Relic’s FedRAMP authority to operate enables US federal government customers (and those that work with the federal government) to get the same level of real-time insights as commercial organizations, while still ensuring compliance with established security standards
Access to New Relic’s FedRAMP environment is based on the following:
1. Your account must be specifically approved by New Relic.
2. You must send your data only to New Relic’s FedRAMP-designated endpoints.
Check out the Nerdlog segment below to learn more:
<iframe width="560" height="315" src="https://www.youtube.com/embed/7rS6_Pl2HJM" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
Don’t miss the Nerdlog LIVE every Thursday at 12 p.m. PT (8 p.m. UTC) on [Twitch](https://www.twitch.tv/new_relic) to get the latest product updates from the people who built them.
| 64.730769 | 271 | 0.793226 | eng_Latn | 0.98959 |
ffb513a7e5399f31aa73a3388532fa6e6b4a93b8 | 7,916 | md | Markdown | windows.ui.xaml.media.media3d/matrix3d.md | angelazhangmsft/winrt-api | 1f92027f2462911960d6be9333b7a86f7b9bf457 | [
"CC-BY-4.0",
"MIT"
] | 199 | 2017-02-09T23:13:51.000Z | 2022-03-28T15:56:12.000Z | windows.ui.xaml.media.media3d/matrix3d.md | angelazhangmsft/winrt-api | 1f92027f2462911960d6be9333b7a86f7b9bf457 | [
"CC-BY-4.0",
"MIT"
] | 2,093 | 2017-02-09T21:52:45.000Z | 2022-03-25T22:23:18.000Z | windows.ui.xaml.media.media3d/matrix3d.md | angelazhangmsft/winrt-api | 1f92027f2462911960d6be9333b7a86f7b9bf457 | [
"CC-BY-4.0",
"MIT"
] | 620 | 2017-02-08T19:19:44.000Z | 2022-03-29T11:38:25.000Z | ---
-api-id: T:Windows.UI.Xaml.Media.Media3D.Matrix3D
-api-type: winrt struct
---
<!-- Structure syntax.
public struct Matrix3D
-->
# Matrix3D
## -description
Represents a 4 × 4 matrix that is used for transformations in a 3-D space. Used as a value for [Matrix3DProjection.ProjectionMatrix](../windows.ui.xaml.media/matrix3dprojection_projectionmatrix.md).
Equivalent WinUI struct: [Matrix3D](/windows/winui/api/microsoft.ui.xaml.media.media3d.matrix3d).
## -xaml-syntax
```xaml
<Matrix3DProjection ProjectionMatrix="m11, m12, m13, m14,
m21, m22, m23, m24, m31, m32, m33, m34, offsetX, offsetY, offsetZ, m44" />
- or -
<!--xmlns:m3d="using:Windows.UI.Xaml.Media.Media3D"-->
<m3d:Matrix3D>
m11, m12, m13, m14, m21, m22, m23, m24, m31, m32, m33, m34, offsetX, offsetY, offsetZ, m44
</m3d:Matrix3D>
```
## -struct-fields
### -field M11
The value of the first row and first column of this Matrix3D.
### -field M12
The value of the first row and second column of this Matrix3D.
### -field M13
The value of the first row and third column of this Matrix3D.
### -field M14
The value of the first row and fourth column of this Matrix3D.
### -field M21
The value of the second row and first column of this Matrix3D.
### -field M22
The value of the second row and second column of this Matrix3D.
### -field M23
The value of the second row and third column of this Matrix3D.
### -field M24
The value of the second row and fourth column of this Matrix3D.
### -field M31
The value of the third row and first column of this Matrix3D.
### -field M32
The value of the third row and second column of this Matrix3D.
### -field M33
The value of the third row and third column of this Matrix3D.
### -field M34
The value of the third row and fourth column of this Matrix3D.
### -field OffsetX
The value of the fourth row and first column of this Matrix3D.
### -field OffsetY
The value of the fourth row and second column of this Matrix3D.
### -field OffsetZ
The value of the fourth row and third column of this Matrix3D.
### -field M44
The value of the fourth row and fourth column of this Matrix3D.
## -remarks
You can use the [Matrix3DProjection](../windows.ui.xaml.media/matrix3dprojection.md) and Matrix3D types for more complex semi–3-D scenarios than are possible with the [PlaneProjection](../windows.ui.xaml.media/planeprojection.md) type. [Matrix3DProjection](../windows.ui.xaml.media/matrix3dprojection.md) provides a complete 3-D transform matrix to apply to any [UIElement](../windows.ui.xaml/uielement.md) (you use this as a value for the [UIElement.Projection](../windows.ui.xaml/uielement_projection.md) property). The matrix lets you apply arbitrary model transform matrices and perspective matrices to visual elements.
Matrix3D has this row-vector syntax:<table>
<tr><td>M11</td><td>M12</td><td>M13</td><td>M14</td></tr>
<tr><td>M21</td><td>M22</td><td>M23</td><td>M24</td></tr>
<tr><td>M31</td><td>M32</td><td>M33</td><td>M34</td></tr>
<tr><td>OffsetX</td><td>OffsetY</td><td>OffsetZ</td><td>M44</td></tr>
</table>
Because the fourth column is accessible, Matrix3D can represent both affine and non-affine transforms.
### XAML syntax for **Matrix3D**
Matrix3D values can be declared in XAML, but the syntax is limited, and different than what you might expect based on how other Windows Runtime structures (like [Thickness](../windows.ui.xaml/thickness.md)) support values for XAML UI:+ The most typical usage for Matrix3D-type properties is to rely on the initialization string behavior that's built-in to the Matrix3D type, and set any value that uses a Matrix3D value as an attribute. You specify a string in the "initialization text" format for constructing a Matrix3D value: 16 separate **Double** values each separated by comma or space. You can see this format used in the XAML in "Examples" below.
+ There's only one existing property that uses a Matrix3D value: [Matrix3DProjection.ProjectionMatrix](../windows.ui.xaml.media/matrix3dprojection_projectionmatrix.md). So that's what's shown as the primary XAML syntax here.
+ The secondary XAML syntax shown has an actual Matrix3D object element. But note that it has a XAML namespace prefix. The [Windows.UI.Xaml.Media.Media3D](windows_ui_xaml_media_media3d.md) namespace was not included in the set of code namespaces that the Windows Runtime XAML parser uses for the default XAML namespace. In order to use the Matrix3D as an element in XAML, you have to include an **xmlns** declaration in your XAML that references [Windows.UI.Xaml.Media.Media3D](windows_ui_xaml_media_media3d.md) by a ** using:** statement. Then qualify the Matrix3D with the **xmlns** prefix you mapped for the types in [Windows.UI.Xaml.Media.Media3D](windows_ui_xaml_media_media3d.md).
+ Even once you do this mapping, the Matrix3D object element can't have attribute values for setting the 16 properties, it's not enabled by the XAML parser (other XAML structures have special-case handling for properties-as-attribute syntax; Matrix3D happens to not have this). You still have to use the initialization text that sets the 16 values as consecutive atoms of a string. In this case the string is contained as the "inner text" / content of the Matrix3D object element.
+ As you can see the object element syntax isn't any easier to read or use than the inline attribute syntax for [Matrix3DProjection.ProjectionMatrix](../windows.ui.xaml.media/matrix3dprojection_projectionmatrix.md), so the verbose Matrix3D object element syntax isn't common.
### Projection and members of Matrix3D
If you are using a Microsoft .NET language (C# or Microsoft Visual Basic), or in Visual C++ component extensions (C++/CX), then Matrix3D has non-data members available, and its data members are exposed as read-write properties, not fields.
If you are programming with C++ using the Windows Runtime Template Library (WRL), then only the data member fields exist as members of Matrix3D, and you cannot use the utility methods or properties listed in the members table. WRL code can access similar utility methods that exist on the [Matrix3DHelper](matrix3dhelper.md) class.
You can't set properties of Matrix3D in XAML with individual XAML attributes. You have to initialize a Matrix3D object element using an initialization string that specifies all 16 values, or use attribute syntax for [Matrix3DProjection.ProjectionMatrix](../windows.ui.xaml.media/matrix3dprojection_projectionmatrix.md) that uses this same string format.
## -examples
This example uses a simple Matrix3D matrix to transform the image in the X and Y directions when you click the image.
[!code-xaml[Matrix3DProjectionSimple](../windows.ui.xaml.media/code/Matrix3DProjectionSimple/csharp/MainPage.xaml#SnippetMatrix3DProjectionSimple)]
[!code-csharp[Matrix3DProjectionSimple_code](../windows.ui.xaml.media/code/Matrix3DProjectionSimple/csharp/MainPage.xaml.cs#SnippetMatrix3DProjectionSimple_code)]
[!code-xaml[Matrix3DProjectionXAML](../windows.ui.xaml.media/code/Matrix3DProjectionXAML/csharp/MainPage.xaml#SnippetMatrix3DProjectionXAML)]
[!code-xaml[Matrix3DProjectionSample](../windows.ui.xaml.media/code/Matrix3DProjectionSample/csharp/MainPage.xaml#SnippetMatrix3DProjectionSample)]
[!code-csharp[Matrix3DProjectionSample_code](../windows.ui.xaml.media/code/Matrix3DProjectionSample/csharp/MainPage.xaml.cs#SnippetMatrix3DProjectionSample_code)]
## -see-also
[Matrix3DHelper](matrix3dhelper.md), [Matrix3DProjection](../windows.ui.xaml.media/matrix3dprojection.md), [UIElement.Projection](../windows.ui.xaml/uielement_projection.md), [3-D perspective effects for XAML UI](/windows/uwp/graphics/3-d-perspective-effects)
projection.md), [UIElement.Projection](../windows.ui.xaml/uielement_projection.md), [3-D perspective effects for XAML UI](/windows/uwp/graphics/3-d-perspective-effects)
| 54.219178 | 686 | 0.767812 | eng_Latn | 0.973849 |
ffb516d4c603a6117856e811003aa709bf3668c3 | 673 | md | Markdown | _posts/2017-09-25-docker.md | VForVictoira/woaielf.github.io | d2e556ad0f32f197a3ccdbfc1873d224e1676b79 | [
"MIT"
] | 87 | 2017-06-04T08:35:03.000Z | 2022-02-23T09:28:37.000Z | _posts/2017-09-25-docker.md | VForVictoira/woaielf.github.io | d2e556ad0f32f197a3ccdbfc1873d224e1676b79 | [
"MIT"
] | 3 | 2017-05-17T15:21:33.000Z | 2018-04-02T07:44:36.000Z | _posts/2017-09-25-docker.md | VForVictoira/woaielf.github.io | d2e556ad0f32f197a3ccdbfc1873d224e1676b79 | [
"MIT"
] | 62 | 2017-06-04T16:45:23.000Z | 2021-11-21T04:15:07.000Z | ---
layout: post
title: "【笔记】Docker 入门手册"
categories: 软件工具
tags: docker
author: ZOE
---
* content
{:toc}
不知道大家是否有这样的经历，有些生信工具的安装就能让你怀疑人生。可是我们学习的热情怎么能在开始就被浇灭呢？要给大家安利一个神奇的工具：docker。于是我们就能愉快的使用其他人封装好的软件啦~建议大家配合后面的教程阅读哦，我的笔记只是帮助梳理一下知识框架而已~
## Update Log
- 2017/09/25
## MindMap
* 默认阅读顺序：**从右→左，顺时针方向**。
* 思维导图软件：**XMind**
## Reference
> [Docker 教程](http://www.runoob.com/docker/docker-tutorial.html) <br>
[Docker 入门教程](http://www.docker.org.cn/book/docker/what-is-docker-16.html) <br>
[Docker — 从入门到实践](https://www.gitbook.com/book/yeasy/docker_practice/details)
| 19.794118 | 130 | 0.73997 | yue_Hant | 0.628192 |
ffb5436d68ccf561735f3569ed8869f71afa19b3 | 2,222 | md | Markdown | README.md | joshzeldin/rsq | 8ebeff955bdf76b7c13f8c1fa1cddd8dfb8886d8 | [
"MIT"
] | 1 | 2021-03-30T07:42:16.000Z | 2021-03-30T07:42:16.000Z | README.md | joshzeldin/rsq | 8ebeff955bdf76b7c13f8c1fa1cddd8dfb8886d8 | [
"MIT"
] | null | null | null | README.md | joshzeldin/rsq | 8ebeff955bdf76b7c13f8c1fa1cddd8dfb8886d8 | [
"MIT"
] | null | null | null | [](https://github.com/joshzeldin/rsq/blob/master/LICENSE)
[](https://travis-ci.com/joshzeldin/rsq)
Connect to a kdb+ service using native rust.
Provides support for kdb+ connectivity using
uncompressed serialization and deserialization,
following the [Kx Documentation](https://code.kx.com/q/kb/serialization/).
## Features
* Written natively in Rust using stable features only
* Leverages Rust's type and enum system to match cleanly with the kdb+ type system
* Outputs `rsq::KObj` to kdb+ readable format i.e. ```(`TSLA;`Q;653.20;200)```
* Supports atomic types (0-19h), lists, dictionaries, and tables
## Drawbacks
Since `rsq` is written natively in Rust, it is capable of running
on any stable version of the language. This comes at the cost of
not using compression/decompression, which is only possible using the
proprietary Kx provided `c.so`. Therefore, this library is primarily
for applications where compression is not needed. This would include
feedhandlers, realtime consumers, etc. as kdb+ only compresses
[under certain conditions](https://code.kx.com/q/basics/ipc/#compression)
## Usage
Put this in your `Cargo.toml`:
```toml
[dependencies]
rsq = "0.1"
```
## Example
### Tickerplant Subscriber
The following code will subscribe to a vanilla tickerplant
for all symbols and print the realtime data to stdout
using the basic `println!` macro
```no_run
use rsq::{Kdb, KObj, KType};
let mut kdb = Kdb::new("localhost", 5001, "username", "password");
kdb.send_async(&KObj::List(vec![
KObj::Atom(KType::Symbol(".u.sub".to_string())),
KObj::Atom(KType::Symbol("trade".to_string())),
KObj::Atom(KType::Symbol("".to_string()))
])).unwrap();
loop {
println!("{}",kdb.read());
};
```
**Output**
```bash
(`upd;`trade;flip (`time;`sym;`price;`size)!((enlist 20:57:00.000);(enlist `TSLA);(enlist 653.1f);(enlist 50j)))
(`upd;`trade;flip (`time;`sym;`price;`size)!((enlist 20:59:00.000);(enlist `TSLA);(enlist 653.2f);(enlist 30j)))
(`upd;`trade;flip (`time;`sym;`price;`size)!((enlist 20:59:30.000);(enlist `TSLA);(enlist 653.1f);(enlist 100j)))
``` | 38.982456 | 125 | 0.716922 | eng_Latn | 0.837292 |
ffb69ced80a549c32e283286684ec7b50c5d3b65 | 9,154 | md | Markdown | sources/tech/20200525 Ubuntu MATE 20.04 LTS Review- Better Than Ever.md | he201610/TranslateProject | 820e641fa35c4c17f2e4887f08b8cd3dfc345734 | [
"Apache-2.0"
] | 1 | 2020-06-20T02:27:09.000Z | 2020-06-20T02:27:09.000Z | sources/tech/20200525 Ubuntu MATE 20.04 LTS Review- Better Than Ever.md | he201610/TranslateProject | 820e641fa35c4c17f2e4887f08b8cd3dfc345734 | [
"Apache-2.0"
] | null | null | null | sources/tech/20200525 Ubuntu MATE 20.04 LTS Review- Better Than Ever.md | he201610/TranslateProject | 820e641fa35c4c17f2e4887f08b8cd3dfc345734 | [
"Apache-2.0"
] | null | null | null | [#]: collector: (lujun9972)
[#]: translator: (robsean)
[#]: reviewer: ( )
[#]: publisher: ( )
[#]: url: ( )
[#]: subject: (Ubuntu MATE 20.04 LTS Review: Better Than Ever)
[#]: via: (https://itsfoss.com/ubuntu-mate-20-04-review/)
[#]: author: (Ankush Das https://itsfoss.com/author/ankush/)
Ubuntu MATE 20.04 LTS Review: Better Than Ever
======
Ubuntu MATE 20.04 LTS is undoubtedly one of the most popular [official flavors of Ubuntu][1].
It’s not just me, but [Ubuntu 20.04 survey results][2] also pointed out the same. Popular or not, it is indeed an impressive Linux distribution specially for older hardware. As a matter of fact, it is also one of the [best lightweight Linux distros][3] available out there.
So, I thought of trying it out for a while in a virtual machine setting to provide you an overview of what you can expect out of it. And, whether it’s worth trying out.
### What’s New In Ubuntu MATE 20.04 LTS?
[Subscribe to our YouTube channel for more Linux videos][4]
The primary highlight on Ubuntu MATE 20.04 LTS would be the addition of MATE Desktop 1.24.
You can expect all the new features of the MATE Desktop 1.24 to come packed in with Ubuntu MATE 20.04. In addition to that, there have been many significant changes, improvements, and additions.
Here’s an overview of what has changed in Ubuntu MATE 20.04:
* Addition of MATE Desktop 1.24
* Numerous visual improvements
* Dozens of bugs fixed
* Based on [Linux Kernel 5.4][5] series
* Addition of experimental [ZFS][6] support
* Addition of GameMode from [Feral Interactive][7].
* Several package updates
Now, to get a better idea on Ubuntu MATE 20.04, I’ll give you some more details.
### User Experience Improvements
![][8]
Considering that more users are leaning towards Linux on Desktop, the user experience plays a vital role in that.
If it’s something easy to use and pleasant to look at that makes all the difference as the first impression.
With Ubuntu MATE 20.04 LTS, I wasn’t disappointed either. Personally, I’m a fan of the latest [GNOME 3.36][9]. I like it on my [Pop OS 20.04][10] but with the presence of [MATE 1.24][11], it Ubuntu MATE was also a good experience.
You will see some significant changes to the window manager including the addition of **invisible resize borders**, **icons rendering in HiDPI**, **rework of ALT+TAB workspace switcher pop ups**, and a couple of other changes that comes as part of the latest MATE 1.24 desktop.
![][12]
Also, **MATE Tweak** has got some sweet improvements where you get to preserve user preferences even if you change the layout of the desktop. The new **MATE Welcome screen** also informs the user about the ability to change the desktop layout, so they don’t have to fiddle around to know about it.
Among other things, one of my favorite additions would be the **minimized app preview feature**.
For instance, you have an app minimized but want to get a preview of it before launching it – now you can do that by simply hovering your mouse over the taskbar as shown in the image below.
![][13]
Now, I must mention that it does not work as expected for every application. So, I’d still say **this feature is buggy and needs improvements**.
### App Additions or Upgrades
![][14]
With MATE 20.04, you will notice a new **Firmware updater** which is a GTK frontend for [fwupd][15]. You can manage your drivers easily using the updater.
This release also **replaces** **Thunderbird with the Evolution** email client. While [Thunderbird][16] is a quite popular desktop email client, [Evolution][17] integrates better with the MATE desktop and proves to be more useful.
![][18]
Considering that we have MATE 1.24 on board, you will also find a **new time and date manager app**. Not just that, if you need a magnifier, [Magnus][19] comes baked in with Ubuntu MATE 20.04.
![][20]
Ubuntu MATE 20.04 also includes upgrades to numerous packages/apps that come pre-installed.
![][21]
While these are small additions – but help in a big way to make the distro more useful.
### Linux Kernel 5.4
Ubuntu MATE 20.04 ships with the last major stable kernel release of 2019 i.e [Linux Kernel 5.4][5].
With this, you will be getting the native [exFAT support][22] and improved hardware support as well. Not to mention, the support for [WireGuard][23] VPN is also a nice thing to have.
So, you will be noticing numerous benefits of Linux Kernel 5.4 including the kernel lock down feature. In case you’re curious, you can read our coverage on [Linux Kernel 5.4][5] to get more details on it.
### Adding GameMode by Feral Interactive
Feral Interactive – popularly known for bringing games to Linux platform came up with a useful command-line tool i.e. [GameMode][7].
You won’t get a GUI – but using the command-line you can apply temporary system optimizations before launching a game.
While this may not make a big difference for every system but it’s best to have more resources available for gaming and the GameMode ensures that you get the necessary optimizations.
### Experimental ZFS Install Option
You get the support for ZFS as your root file system. It is worth noting that it is an experimental feature and should not be used if you’re not sure what you’re doing.
To get a better idea of ZFS, I recommend you reading one of our articles on [What is ZFS][6] by [John Paul][24].
### Performance & Other Improvements
Ubuntu MATE is perfectly tailored as a lightweight distro and also something fit for modern desktops.
![][25]
In this case, I didn’t run any specific benchmark tools- but for an average user, I didn’t find any performance issues in my virtual machine setting. If it helps, I tested this on a host system with an i5-7400 processor with a GTX 1050 graphics card coupled with 16 Gigs of RAM. And, 7 GB of RAM + 768 MB of graphics memory + 2 cores of my processor was allocated for the virtual machine.
![][26]
When you test it out yourself, feel free to let me know how it was for you.
Overall, along with all the major improvements, there are subtle changes/fixes/improvements here and there that makes Ubuntu MATE 20.04 LTS a good upgrade.
### Should You Upgrade?
If you are running Ubuntu MATE 19.10, you should proceed upgrading it immediately as the support for it ends in **June 2020.**
For Ubuntu MATE 18.04 users (**supported until April 2021**) – it depends on what works for you. If you need the features of the latest release, you should choose to upgrade it immediately.
But, if you don’t necessarily need the new stuff, you can look around for the [list of existing bugs][27] and join the [Ubuntu MATE community][28] to know more about the issues revolving the latest release.
Once you do the research needed, you can then proceed to upgrade your system to Ubuntu MATE 20.04 LTS which will be **supported until April 2023**.
_**Have you tried the latest Ubuntu MATE 20.04 yet? What do you think about it? Let me know your thoughts in the comments.**_
--------------------------------------------------------------------------------
via: https://itsfoss.com/ubuntu-mate-20-04-review/
作者：[Ankush Das][a]
选题：[lujun9972][b]
译者：[译者ID](https://github.com/译者ID)
校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://itsfoss.com/author/ankush/
[b]: https://github.com/lujun9972
[1]: https://itsfoss.com/which-ubuntu-install/
[2]: https://ubuntu.com/blog/ubuntu-20-04-survey-results
[3]: https://itsfoss.com/lightweight-linux-beginners/
[4]: https://www.youtube.com/c/itsfoss?sub_confirmation=1
[5]: https://itsfoss.com/linux-kernel-5-4/
[6]: https://itsfoss.com/what-is-zfs/
[7]: https://github.com/FeralInteractive/gamemode
[8]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/04/ubuntu-mate-20-04.jpg?ssl=1
[9]: https://itsfoss.com/gnome-3-36-release/
[10]: https://itsfoss.com/pop-os-20-04-review/
[11]: https://mate-desktop.org/blog/2020-02-10-mate-1-24-released/
[12]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/04/ubuntu-mate-desktop-layout.png?ssl=1
[13]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/04/ubuntu-mate-minimized-app.png?ssl=1
[14]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/04/ubuntu-mate-20-04-firmware.png?ssl=1
[15]: https://fwupd.org
[16]: https://www.thunderbird.net/en-US/
[17]: https://wiki.gnome.org/Apps/Evolution
[18]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/04/ubuntu-mate-evolution.png?ssl=1
[19]: https://kryogenix.org/code/magnus/
[20]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/04/ubuntu-mate-magnus.jpg?ssl=1
[21]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/04/ubuntu-mate-apps.png?ssl=1
[22]: https://cloudblogs.microsoft.com/opensource/2019/08/28/exfat-linux-kernel/
[23]: https://wiki.ubuntu.com/WireGuard
[24]: https://itsfoss.com/author/john/
[25]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/04/ubuntu-mate-system-reosource.jpg?ssl=1
[26]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/04/ubuntu-mate-focal-neofetch.png?ssl=1
[27]: https://bugs.launchpad.net/ubuntu-mate
[28]: https://ubuntu-mate.community/
| 52.609195 | 388 | 0.740551 | eng_Latn | 0.968196 |
ffb6df2e9625b4a038ee6b402c4a32e685a5f027 | 711 | md | Markdown | content/learning/how-to-make-a-sankey-diagram/how-to-make-a-sankey-diagram.md | adrienbrault/rawgraphs.github.io | 791f8b4cad14d467ffed7e3c81f1ef7b2eaf1414 | [
"MIT"
] | 14 | 2019-07-29T08:47:17.000Z | 2022-02-27T14:55:08.000Z | content/learning/how-to-make-a-sankey-diagram/how-to-make-a-sankey-diagram.md | adrienbrault/rawgraphs.github.io | 791f8b4cad14d467ffed7e3c81f1ef7b2eaf1414 | [
"MIT"
] | 34 | 2019-07-10T22:10:20.000Z | 2021-01-04T08:32:04.000Z | content/learning/how-to-make-a-sankey-diagram/how-to-make-a-sankey-diagram.md | adrienbrault/rawgraphs.github.io | 791f8b4cad14d467ffed7e3c81f1ef7b2eaf1414 | [
"MIT"
] | 6 | 2019-12-18T17:50:22.000Z | 2022-02-21T20:03:15.000Z | ---
title: How to make a Sankey diagram
date: 2021-05-27
author: RAW Graphs Team
layout: post
subtitle:
- ""
secondary_title:
- ""
discover_more_description:
- >-
In this guide you’ll learn how to create a Sankey diagram.
The goal is to visualize UK energy production and consumption in 2050.
background_image:
- "0"
page_background_image:
- ""
featured_video: https://www.youtube.com/embed/DYTiKjH6oFM
reading_time:
- "2"
files:
- title: Project file
href: ./TutorialSankeyDiagram.rawgraphs.zip
image: ""
categories:
- Learning
- Charts
tags:
- networks
- flows
path: /learning/how-to-make-a-sankey-diagram/
---
You can download the project file from the panel on the left.
| 19.75 | 74 | 0.714487 | eng_Latn | 0.900651 |
ffb6f982f5fcf875f44cef78ef00ce0f7c119ea8 | 1,461 | md | Markdown | docs/csharp/language-reference/keywords/try-catch-finally.md | TimgoHung/docs.zh-tw | 962b9283ba4a40d668ba962df9d2d91a5c94623c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/csharp/language-reference/keywords/try-catch-finally.md | TimgoHung/docs.zh-tw | 962b9283ba4a40d668ba962df9d2d91a5c94623c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/csharp/language-reference/keywords/try-catch-finally.md | TimgoHung/docs.zh-tw | 962b9283ba4a40d668ba962df9d2d91a5c94623c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: try-catch-finally (C# 參考)
ms.date: 07/20/2015
f1_keywords:
- catch-finally_CSharpKeyword
- catch-finally
helpviewer_keywords:
- finally blocks [C#]
- try-catch statement [C#]
ms.assetid: a1b443b0-ff7a-43ab-b835-0cc9bfbd15ca
ms.openlocfilehash: 18625838bd36d9d32079b7c72ded7ed660b8cf3a
ms.sourcegitcommit: ccd8c36b0d74d99291d41aceb14cf98d74dc9d2b
ms.translationtype: HT
ms.contentlocale: zh-TW
ms.lasthandoff: 12/10/2018
ms.locfileid: "53130659"
---
# <a name="try-catch-finally-c-reference"></a>try-catch-finally (C# 參考)
常見的搭配使用 `catch` 與 `finally` 是要取得和使用 `try` 區塊中的資源、處理 `catch` 區塊中的例外情況，以及釋放 `finally` 區塊中的資源。
如需重新擲回例外狀況的詳細資訊和範例，請參閱 [try-catch](try-catch.md) 和[擲回例外狀況](../../../standard/exceptions/index.md)。 如需 `finally` 區塊的詳細資訊，請參閱 [try-finally](try-finally.md)。
## <a name="example"></a>範例
[!code-csharp[csrefKeywordsExceptions#1](~/samples/snippets/csharp/VS_Snippets_VBCSharp/csrefKeywordsExceptions/CS/csrefKeywordsExceptions.cs#1)]
## <a name="c-language-specification"></a>C# 語言規格
[!INCLUDE[CSharplangspec](~/includes/csharplangspec-md.md)]
## <a name="see-also"></a>另請參閱
- [C# 參考](../index.md)
- [C# 程式設計指南](../../programming-guide/index.md)
- [C# 關鍵字](index.md)
- [try、throw 和 catch 陳述式 (C++)](/cpp/cpp/try-throw-and-catch-statements-cpp)
- [例外狀況處理陳述式](exception-handling-statements.md)
- [throw](throw.md)
- [操作說明：明確擲回例外狀況](../../../standard/exceptions/how-to-explicitly-throw-exceptions.md)
- [using 陳述式](using-statement.md) | 35.634146 | 155 | 0.737166 | yue_Hant | 0.514431 |
ffb7a449145ebc6748b5ef355a480dd8c64d7dc6 | 770 | md | Markdown | includes/vpn-gateway-table-coexist-include.md | decarli/azure-docs.pt-br | 20bc383d005c11e7b7dc7b7b0777fc0de1262ffc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | includes/vpn-gateway-table-coexist-include.md | decarli/azure-docs.pt-br | 20bc383d005c11e7b7dc7b7b0777fc0de1262ffc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | includes/vpn-gateway-table-coexist-include.md | decarli/azure-docs.pt-br | 20bc383d005c11e7b7dc7b7b0777fc0de1262ffc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Arquivo de inclusão
description: Arquivo de inclusão
services: vpn-gateway
author: cherylmc
ms.service: vpn-gateway
ms.topic: include
ms.date: 04/26/2019
ms.author: cherylmc
ms.custom: include file
ms.openlocfilehash: a10e4fc96f475fe26ca27ddec2e805086d661a50
ms.sourcegitcommit: 3e98da33c41a7bbd724f644ce7dedee169eb5028
ms.translationtype: HT
ms.contentlocale: pt-BR
ms.lasthandoff: 06/18/2019
ms.locfileid: "67171803"
---
| **Método/modelo de implantação** | **Portal do Azure** | **PowerShell** |
| --- | --- | --- |
| Gerenciador de Recursos | **Com suporte** | [Tutorial](../articles/expressroute/expressroute-howto-coexist-resource-manager.md)|
| Clássico | **Sem suporte** | [Tutorial](../articles/expressroute/expressroute-howto-coexist-classic.md) |
| 35 | 130 | 0.757143 | por_Latn | 0.21029 |
ffb7c7bba55281eecbe3753eb198133b14366051 | 297 | md | Markdown | README.md | tkskto/webGLMoire | 500ca8f0f90631bff0669144bab7cb52d277d75f | [
"MIT"
] | null | null | null | README.md | tkskto/webGLMoire | 500ca8f0f90631bff0669144bab7cb52d277d75f | [
"MIT"
] | null | null | null | README.md | tkskto/webGLMoire | 500ca8f0f90631bff0669144bab7cb52d277d75f | [
"MIT"
] | null | null | null | # webGLMoire
WebGLでモアレを作ってみよう
### 第一弾
目標とするモアレはこちら
<img src="https://github.com/tkskto/webGLMoire/blob/images/document/moire3b.jpg">
出典：http://www.h7.dion.ne.jp/~kagaku/moire/moire.html1
[デモ](https://tkskto.github.io/WebGLMoire/)
[Qiita記事](http://qiita.com/tkskto/items/729819f945fde7cdb89e) | 21.214286 | 81 | 0.760943 | yue_Hant | 0.93792 |
ffb872e644c89824eaa2e3d8d04dbfcc30e505a4 | 1,493 | md | Markdown | docs/leksah.md | kevoriordan/haskell-ide-engine | 481b78dd39dd4e87cbde6528cefa914a0d00d85d | [
"BSD-3-Clause"
] | 2,654 | 2015-10-30T21:58:36.000Z | 2022-03-20T21:47:04.000Z | docs/leksah.md | kevoriordan/haskell-ide-engine | 481b78dd39dd4e87cbde6528cefa914a0d00d85d | [
"BSD-3-Clause"
] | 1,395 | 2015-10-30T23:30:08.000Z | 2020-10-07T02:12:52.000Z | docs/leksah.md | kevoriordan/haskell-ide-engine | 481b78dd39dd4e87cbde6528cefa914a0d00d85d | [
"BSD-3-Clause"
] | 307 | 2015-11-03T10:15:02.000Z | 2022-03-20T11:44:56.000Z | ## How to use hie with Leksah
This document is a work in progress, as is the Leksah integration.
### Getting started
```bash
git clone https://github.com/haskell/haskell-ide-engine.git
cd haskell-ide-engine
stack install
```
This will put the `hie` executable into `$HOME/.local/bin/hie`.
Get Leksah sources from the hie-integration branch (https://github.com/Leksah/Leksah/tree/hie_integration) and build them.
This branch has a dependency on hie-base, one of the submodules of haskell-ide-engine. So one way to build things is to add the directory where you cloned the hie-base sources to the Leksah sandbox or stack file.
Once Leksah is built, you can start it normally. Then go to `Tools -> Preferences -> Helper Programs` and check the `use haskell-ide-engine` box, and fill in the path to the executable (`$HOME/.local/bin/hie`).
### Usage
Once the haskell-ide-engine path set in the preferences, the following actions are available:
- Type: will use the `ghcmod:type` command to display the type of the selected expression (no need to have a GHCi session running in Leksah)
- Info: will use the `ghcmod:info` command to display information of the selected expression
- Refactor: a few refactorings are available, provided by the hie HaRe plugin. Some like rename or dupdef will ask for the new name. Running the refactoring currently replaces the whole source contents.
### Troubleshooting
Some messages are dumped to the Leksah log, so run Leksah in debug mode to see them.
| 48.16129 | 212 | 0.770261 | eng_Latn | 0.997458 |
ffb880d3f88418a89d3a5edc3443614f12400e63 | 1,414 | md | Markdown | problems/leetcode/array/README.md | Fifirex/data-structures-and-algorithms | 060554ad5eb43502a65c31f228f4c02ad0f187d1 | [
"MIT"
] | 39 | 2020-02-04T14:07:45.000Z | 2022-01-26T18:47:51.000Z | problems/leetcode/array/README.md | Fifirex/data-structures-and-algorithms | 060554ad5eb43502a65c31f228f4c02ad0f187d1 | [
"MIT"
] | 1 | 2021-07-04T11:55:16.000Z | 2021-07-04T11:55:16.000Z | problems/leetcode/array/README.md | gokulkrishh/data-structures-and-algorithms | 74d3e7f39a2c4e933678dcfc4f8ecf0d92abab47 | [
"MIT"
] | 4 | 2020-03-14T07:52:27.000Z | 2021-08-14T16:39:49.000Z | # Array
1. [Rearrange Array](./1.rearrange_array.js)
1. [Largest Formed Number](./2.largest_number.js)
1. [Flatten Multiple Level Array](./3.flatten_array.js)
1. [Wave Array](./4.wave_array.js)
1. [Remove Element](./5.remove_element.js)
1. [Find Relative Winners](./6.find_relative_winners.js)
1. [Reshape To Matrix](./7.reshape_matrix.js)
1. [Max Sum Of K Elements](./8.max_k_elements_in_array.js)
1. [Find Single Number](./9.single_number.js)
1. [Area of Island (2D Array)](./10.area_of_island.js)
1. [Find the Missing Number](./11.missing_number.js)
1. [Distribute Candies](./12.distribute_candies.js)
1. [Max Consecutive Ones](./13.max_consecutives_ones.js)
1. [Where do i belong](./14.where_do_i_belong.js)
1. [Water Container](./15.water_container.js)
1. [Reverse Words in a String](./16.reverse_words.js)
1. [Can Place Flowers](./17.flower_bed.js)
1. [Rotate Array](./18.rotate_array.js)
1. [Intersection of Two Arrays](./19.intersection_of_numbers.js)
1. [Sort Array By Parity](./20.sort_by_parity.js)
1. [Find Duplicate Numbers](./21.find_duplicate_number.js)
1. [Subsets](./22.subsets.js)
1. [Longest Vowel Chain](./23.longest_vowel_chain.js)
1. [Keyboard Row](./24.keyboard_row.js)
1. [Sum of Consecutive Integers](./25.sum_of_consecutive_integers.js)
1. [First Duplicate](./26.first_duplicate.js)
1. [Direction Reduction](./27.direction_reduction.js)
1. [Max of sub arrays](./28.max_of_sub_arrays.js)
| 45.612903 | 69 | 0.736917 | yue_Hant | 0.449206 |
ffb9d57c92acd5dec3a81ce2faae0dd1e677a41b | 1,543 | md | Markdown | results/referenceaudioanalyzer/SIEC/ACS Evolve/README.md | ruixiao85/AutoEq | a41d50e2bcde9609fe37848f55b019a13496ef66 | [
"MIT"
] | 1 | 2020-07-26T09:34:56.000Z | 2020-07-26T09:34:56.000Z | results/referenceaudioanalyzer/SIEC/ACS Evolve/README.md | TheDarkMikeRises/AutoEq | ab0fcf2fe072665f8af1d253c14226621fadecec | [
"MIT"
] | null | null | null | results/referenceaudioanalyzer/SIEC/ACS Evolve/README.md | TheDarkMikeRises/AutoEq | ab0fcf2fe072665f8af1d253c14226621fadecec | [
"MIT"
] | null | null | null | # ACS Evolve
See [usage instructions](https://github.com/jaakkopasanen/AutoEq#usage) for more options and info.
### Parametric EQs
In case of using parametric equalizer, apply preamp of **-7.9dB** and build filters manually
with these parameters. The first 5 filters can be used independently.
When using independent subset of filters, apply preamp of **-7.7dB**.
| Type | Fc | Q | Gain |
|:--------|:---------|:-----|:---------|
| Peaking | 25 Hz | 0.65 | 4.5 dB |
| Peaking | 2957 Hz | 3.02 | 6.8 dB |
| Peaking | 5587 Hz | 2.53 | 6.9 dB |
| Peaking | 8338 Hz | 3.49 | -11.5 dB |
| Peaking | 18769 Hz | 0.74 | -6.3 dB |
| Peaking | 235 Hz | 1.01 | -2.2 dB |
| Peaking | 1595 Hz | 1.6 | -3.6 dB |
| Peaking | 2395 Hz | 4.78 | 3.2 dB |
| Peaking | 3309 Hz | 0.94 | 0.2 dB |
| Peaking | 12348 Hz | 3.07 | 2.0 dB |
### Fixed Band EQs
In case of using fixed band (also called graphic) equalizer, apply preamp of **-7.3dB**
(if available) and set gains manually with these parameters.
| Type | Fc | Q | Gain |
|:--------|:---------|:-----|:--------|
| Peaking | 31 Hz | 1.41 | 4.5 dB |
| Peaking | 62 Hz | 1.41 | 1.7 dB |
| Peaking | 125 Hz | 1.41 | -0.8 dB |
| Peaking | 250 Hz | 1.41 | -2.1 dB |
| Peaking | 500 Hz | 1.41 | 0.1 dB |
| Peaking | 1000 Hz | 1.41 | -1.7 dB |
| Peaking | 2000 Hz | 1.41 | -0.5 dB |
| Peaking | 4000 Hz | 1.41 | 7.8 dB |
| Peaking | 8000 Hz | 1.41 | -6.0 dB |
| Peaking | 16000 Hz | 1.41 | -4.4 dB |
### Graphs
 | 38.575 | 98 | 0.546338 | eng_Latn | 0.738776 |
ffba62ba3ef39ede0cfcd112a8839f8af028ef39 | 4,699 | md | Markdown | essential-netty-in-action/CORE FUNCTIONS/Bootstrapping clients and connectionless protocols.md | leoeco2000/TestJava8 | fa96dc043aea3263bb5ee0ef78fd03b6a05c7d28 | [
"MIT"
] | null | null | null | essential-netty-in-action/CORE FUNCTIONS/Bootstrapping clients and connectionless protocols.md | leoeco2000/TestJava8 | fa96dc043aea3263bb5ee0ef78fd03b6a05c7d28 | [
"MIT"
] | null | null | null | essential-netty-in-action/CORE FUNCTIONS/Bootstrapping clients and connectionless protocols.md | leoeco2000/TestJava8 | fa96dc043aea3263bb5ee0ef78fd03b6a05c7d28 | [
"MIT"
] | null | null | null | 引导客户端和无连接协议
====
当需要引导客户端或一些无连接协议时，需要使用Bootstrap类。
在本节中,我们将回顾可用的各种方法引导客户端,引导线程,和可用的管道实现。
### 客户端引导方法
下表是 Bootstrap 的常用方法，其中很多是继承自 AbstractBootstrap。
Table 9.1 Bootstrap methods
名称 | 描述
-----|----
group | 设置 EventLoopGroup 用于处理所有的 Channel 的事件
channel channelFactory| channel() 指定 Channel 的实现类。如果类没有提供一个默认的构造函数,你可以调用 channelFactory() 来指定一个工厂类被 bind() 调用。
localAddress | 指定应该绑定到本地地址 Channel。如果不提供,将由操作系统创建一个随机的。或者,您可以使用 bind() 或 connect()指定localAddress
option | 设置 ChannelOption 应用于 新创建 Channel 的 ChannelConfig。这些选项将被 bind 或 connect 设置在通道,这取决于哪个被首先调用。这个方法在创建管道后没有影响。所支持 ChannelOption 取决于使用的管道类型。请参考9.6节和 ChannelConfig 的 API 文档 的 Channel 类型使用。
attr | 这些选项将被 bind 或 connect 设置在通道,这取决于哪个被首先调用。这个方法在创建管道后没有影响。请参考9.6节。
handler | 设置添加到 ChannelPipeline 中的 ChannelHandler 接收事件通知。
clone | 创建一个当前 Bootstrap的克隆拥有原来相同的设置。
remoteAddress | 设置远程地址。此外,您可以通过 connect() 指定
connect | 连接到远端，返回一个 ChannelFuture, 用于通知连接操作完成
bind | 将通道绑定并返回一个 ChannelFuture,用于通知绑定操作完成后,必须调用 Channel.connect() 来建立连接。
### 如何引导客户端
Bootstrap 类负责创建管道给客户或应用程序，利用无连接协议和在调用 bind() 或 connect() 之后。
下图展示了如何工作
1. 当 bind() 调用时，Bootstrap 将创建一个新的管道, 当 connect() 调用在 Channel 来建立连接
2. Bootstrap 将创建一个新的管道, 当 connect() 调用时
3. 新的 Channel
Figure 9.2 Bootstrap process
下面演示了引导客户端，使用的是 NIO TCP 传输
Listing 9.1 Bootstrapping a client
EventLoopGroup group = new NioEventLoopGroup();
Bootstrap bootstrap = new Bootstrap(); //1
bootstrap.group(group) //2
.channel(NioSocketChannel.class) //3
.handler(new SimpleChannelInboundHandler<ByteBuf>() { //4
@Override
protected void channeRead0(
ChannelHandlerContext channelHandlerContext,
ByteBuf byteBuf) throws Exception {
System.out.println("Received data");
byteBuf.clear();
}
});
ChannelFuture future = bootstrap.connect(
new InetSocketAddress("www.manning.com", 80)); //5
future.addListener(new ChannelFutureListener() {
@Override
public void operationComplete(ChannelFuture channelFuture)
throws Exception {
if (channelFuture.isSuccess()) {
System.out.println("Connection established");
} else {
System.err.println("Connection attempt failed");
channelFuture.cause().printStackTrace();
}
}
});
1. 创建一个新的 Bootstrap 来创建和连接到新的客户端管道
2. 指定 EventLoopGroup
3. 指定 Channel 实现来使用
4. 设置处理器给 Channel 的事件和数据
5. 连接到远端主机
注意 Bootstrap 提供了一个“流利”语法——示例中使用的方法(除了connect()) 由 Bootstrap 返回实例本身的引用链接他们。
### 兼容性
Channel 的实现和 EventLoop 的处理过程在 EventLoopGroup 中必须兼容，哪些 Channel 是和 EventLoopGroup 是兼容的可以查看 API 文档。经验显示，相兼容的实现一般在同一个包下面，例如使用NioEventLoop，NioEventLoopGroup 和 NioServerSocketChannel 在一起。请注意，这些都是前缀“Nio”，然后不会用这些代替另一个实现和另一个前缀，如“Oio”，也就是说 OioEventLoopGroup 和NioServerSocketChannel 是不相容的。
Channel 和 EventLoopGroup 的 EventLoop 必须相容，例如NioEventLoop、NioEventLoopGroup、NioServerSocketChannel是相容的，但是 OioEventLoopGroup 和 NioServerSocketChannel 是不相容的。从类名可以看出前缀是“Nio”的只能和“Nio”的一起使用。
*EventLoop 和 EventLoopGroup*
*记住,EventLoop 分配给该 Channel 负责处理 Channel 的所有操作。当你执行一个方法,该方法返回一个 ChannelFuture ，它将在 分配给 Channel 的 EventLoop 执行。*
*EventLoopGroup 包含许多 EventLoops 和分配一个 EventLoop 通道时注册。我们将在15章更详细地讨论这个话题。*
清单9.2所示的结果,试图使用一个 Channel 类型与一个 EventLoopGroup 兼容。
Listing 9.2 Bootstrap client with incompatible EventLoopGroup
EventLoopGroup group = new NioEventLoopGroup();
Bootstrap bootstrap = new Bootstrap(); //1
bootstrap.group(group) //2
.channel(OioSocketChannel.class) //3
.handler(new SimpleChannelInboundHandler<ByteBuf>() { //4
@Override
protected void channelRead0(
ChannelHandlerContext channelHandlerContext,
ByteBuf byteBuf) throws Exception {
System.out.println("Reveived data");
byteBuf.clear();
}
});
ChannelFuture future = bootstrap.connect(
new InetSocketAddress("www.manning.com", 80)); //5
future.syncUninterruptibly();
1. 创建新的 Bootstrap 来创建新的客户端管道
2. 注册 EventLoopGroup 用于获取 EventLoop
3. 指定要使用的 Channel 类。通知我们使用 NIO 版本用于
EventLoopGroup ， OIO 用于 Channel
4. 设置处理器用于管道的 I/O 事件和数据
5. 尝试连接到远端。当 NioEventLoopGroup 和 OioSocketChannel 不兼容时，会抛出 IllegalStateException 异常
IllegalStateException 显示如下：
Listing 9.3 IllegalStateException thrown because of invalid configuration
Exception in thread "main" java.lang.IllegalStateException: incompatible event loop
type: io.netty.channel.nio.NioEventLoop
at
io.netty.channel.AbstractChannel$AbstractUnsafe.register(AbstractChannel.java:5
71)
...
出现 IllegalStateException 的其他情况是，在 bind() 或 connect() 调用前 调用需要设置参数的方法调用失败时，包括：
* group()
* channel() 或 channnelFactory()
* handler()
handler() 方法尤为重要,因为这些 ChannelPipeline 需要适当配置。
一旦提供了这些参数,应用程序将充分利用 Netty 的能力。 | 33.564286 | 279 | 0.758459 | yue_Hant | 0.664849 |
ffba6c80386ecce31d3def9977360d0a043bffc0 | 87 | md | Markdown | README.md | itsme-prashant/arrayusing-pointer | 570fe9b41b4b6fdd37496b536331c9c89ba6b616 | [
"MIT"
] | null | null | null | README.md | itsme-prashant/arrayusing-pointer | 570fe9b41b4b6fdd37496b536331c9c89ba6b616 | [
"MIT"
] | null | null | null | README.md | itsme-prashant/arrayusing-pointer | 570fe9b41b4b6fdd37496b536331c9c89ba6b616 | [
"MIT"
] | null | null | null | # arrayusing-pointer
this file contain a c++ program to access the array using pointer
| 29 | 65 | 0.793103 | eng_Latn | 0.998688 |
ffba7d73dd242ef50167a84e220a23f3d192cd9f | 66,360 | md | Markdown | docs/framework/winforms/controls/creating-a-wf-control-design-time-features.md | CodeTherapist/docs.de-de | 45ed8badf2e25fb9abdf28c20e421f8da4094dd1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/winforms/controls/creating-a-wf-control-design-time-features.md | CodeTherapist/docs.de-de | 45ed8badf2e25fb9abdf28c20e421f8da4094dd1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/winforms/controls/creating-a-wf-control-design-time-features.md | CodeTherapist/docs.de-de | 45ed8badf2e25fb9abdf28c20e421f8da4094dd1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Exemplarische Vorgehensweise: Erstellen eines Windows Forms-Steuerelements, das Visual Studio-Entwurfszeitfunktion nutzt'
ms.date: 03/30/2017
dev_langs:
- csharp
- vb
helpviewer_keywords:
- Windows Forms controls, creating
- design-time functionality [Windows Forms], Windows Forms
- DocumentDesigner class [Windows Forms]
- walkthroughs [Windows Forms], controls
ms.assetid: 6f487c59-cb38-4afa-ad2e-95edacb1d626
ms.openlocfilehash: aa30842ca72bb50767513cf387f59e29e40574e8
ms.sourcegitcommit: a885cc8c3e444ca6471348893d5373c6e9e49a47
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 09/06/2018
ms.locfileid: "43865864"
---
# <a name="walkthrough-creating-a-windows-forms-control-that-takes-advantage-of-visual-studio-design-time-features"></a>Exemplarische Vorgehensweise: Erstellen eines Windows Forms-Steuerelements, das Visual Studio-Entwurfszeitfunktion nutzt
Die zur Entwurfszeit für ein benutzerdefiniertes Steuerelement kann verbessert werden, indem Sie einen zugeordneten benutzerdefinierten Designer erstellen.
Diese exemplarische Vorgehensweise veranschaulicht, wie Sie einen benutzerdefinierten Designer für ein benutzerdefiniertes Steuerelement zu erstellen. Implementieren Sie eine `MarqueeControl` Typ und einen zugeordneten Designer Klasse namens `MarqueeControlRootDesigner`.
Die `MarqueeControl` Typ implementiert eine Anzeige ähnlich wie eine Laufschrift Theater mit animierten Lichtern und blinkenden Text.
Der Designer für dieses Steuerelement interagiert mit der entwurfsumgebung, um eine benutzerdefinierte während der Entwurfszeit-Erlebnis zu bieten. Mit dem benutzerdefinierten Designer können Sie eine benutzerdefinierte zusammenstellen `MarqueeControl` -Implementierung mit animierten Lichtern und blinkenden Text in verschiedenen Kombinationen. Sie können das erstellte Steuerelement in einem Formular wie jedes andere Windows Forms-Steuerelement verwenden.
In dieser exemplarischen Vorgehensweise werden u. a. folgende Aufgaben veranschaulicht:
- Erstellen des Projekts
- Erstellen ein Steuerelementbibliothek-Projekt
- Verweisen auf das Projekt des benutzerdefinierten Steuerelements
- Definieren ein benutzerdefiniertes Steuerelement und seinen benutzerdefinierte Designer
- Erstellen einer Instanz des benutzerdefinierten Steuerelements
- Einrichten des Projekts für das Debuggen zur Entwurfszeit
- Implementieren des benutzerdefinierten Steuerelements
- Erstellen ein untergeordnetes Steuerelement für das benutzerdefinierte Steuerelement
- Erstellen des untergeordneten MarqueeBorder-Steuerelements
- Erstellen eines benutzerdefinierten Designers Schatten und Filtereigenschaften
- Behandeln Änderungen an der Clientkomponenten
- Hinzufügen von Designerverben zu Ihrem benutzerdefinierten Designer
- Erstellen eine benutzerdefinierte UITypeEditor
- Testen das benutzerdefinierte Steuerelement im Designer
Wenn Sie fertig sind, wird das benutzerdefinierte Steuerelement etwa wie folgt aussehen:
Die vollständige codeauflistung finden Sie unter [Vorgehensweise: Erstellen einer Windows Forms-Steuerelement, dass akzeptiert Vorteil der Entwurfszeitfunktionen](https://msdn.microsoft.com/library/8e0bad0e-56f3-43d2-bf63-a945c654d97c).
> [!NOTE]
> Je nach den aktiven Einstellungen oder der Version unterscheiden sich die Dialogfelder und Menübefehle auf Ihrem Bildschirm möglicherweise von den in der Hilfe beschriebenen. Klicken Sie im Menü **Extras** auf **Einstellungen importieren und exportieren** , um die Einstellungen zu ändern. Weitere Informationen finden Sie unter [Personalisieren von Visual Studio-IDE](/visualstudio/ide/personalizing-the-visual-studio-ide).
## <a name="prerequisites"></a>Erforderliche Komponenten
Für die Durchführung dieser exemplarischen Vorgehensweise benötigen Sie Folgendes:
- Berechtigt sind, können zum Erstellen und Ausführen von Windows Forms-Anwendungsprojekten auf dem Computer, auf dem Visual Studio installiert ist.
## <a name="creating-the-project"></a>Erstellen des Projekts
Der erste Schritt ist das Anwendungsprojekt zu erstellen. Sie können dieses Projekt zum Erstellen der Anwendung, die das benutzerdefinierte Steuerelement hostet.
#### <a name="to-create-the-project"></a>So erstellen Sie das Projekt
- Erstellen Sie eine Windows Forms-Anwendung mit dem Namen "MarqueeControlTest" (**Datei** > **neu** > **Projekt** > **Visual C#-** oder **Visual Basic** > **Klassischer Desktop** > **Windows Forms-Anwendung**).
## <a name="creating-a-control-library-project"></a>Erstellen ein Steuerelementbibliothek-Projekt
Der nächste Schritt besteht darin die Steuerelementbibliothek-Projekt zu erstellen. Erstellen Sie ein neues benutzerdefiniertes Steuerelement und den entsprechenden benutzerdefinierten Designer.
#### <a name="to-create-the-control-library-project"></a>Um die Steuerelementbibliothek-Projekt zu erstellen.
1. Fügen Sie ein Windows Forms-Steuerelementbibliothek-Projekt zur Projektmappe hinzu. Nennen Sie das Projekt "MarqueeControlLibrary."
2. Mithilfe von **Projektmappen-Explorer**, löschen Sie Standardsteuerelement des Projekts, indem Sie die Quelldatei, die mit dem Namen "UserControl1.cs" oder "UserControl1.vb", abhängig von der Sprache Ihrer Wahl löschen. Weitere Informationen finden Sie unter [NIB: Vorgehensweise: entfernen, löschen und Ausschließen von Elementen](https://msdn.microsoft.com/library/6dffdc86-29c8-4eff-bcd8-e3a0dd9e9a73).
3. Fügen Sie einen neuen <xref:System.Windows.Forms.UserControl> Element für die `MarqueeControlLibrary` Projekt. Weisen Sie der neuen Quelldatei Basisnamen "MarqueeControl."
4. Mithilfe von **Projektmappen-Explorer**, erstellen Sie einen neuen Ordner in der `MarqueeControlLibrary` Projekt. Weitere Informationen finden Sie unter [NIB: Vorgehensweise: Hinzufügen neuer Projektelemente](https://msdn.microsoft.com/library/63d3e16b-de6e-4bb5-a0e3-ecec762201ce). Nennen Sie den neuen Ordner "Entwurf".
5. Mit der rechten Maustaste die **Entwurf** Ordner, und fügen Sie eine neue Klasse hinzu. Benennen Sie der Quelldatei Basis von "MarqueeControlRootDesigner."
6. Sie benötigen zum Verwenden von Typen aus der Assembly "System.Design" so fügen Sie dieser Verweis auf die `MarqueeControlLibrary` Projekt.
> [!NOTE]
> Um die Assembly "System.Design" verwenden zu können, muss Ihr Projekt als Ziel die Vollversion von .NET Framework, nicht die .NET Framework Client Profile. Wenn das Zielframework ändern möchten, finden Sie unter [Vorgehensweise: .NET Framework-Version als Ziel](/visualstudio/ide/how-to-target-a-version-of-the-dotnet-framework).
## <a name="referencing-the-custom-control-project"></a>Verweisen auf das Projekt des benutzerdefinierten Steuerelements
Verwenden Sie die `MarqueeControlTest` Projekt zum Testen des benutzerdefinierten Steuerelements. Das Testprojekt werden über das benutzerdefinierte Steuerelement, wenn Sie einen Projektverweis zum Hinzufügen der `MarqueeControlLibrary` Assembly.
#### <a name="to-reference-the-custom-control-project"></a>Um auf das benutzerdefinierte Steuerelement-Projekt zu verweisen.
- In der `MarqueeControlTest` fügen einen Projektverweis auf die `MarqueeControlLibrary` Assembly. Verwenden Sie die **Projekte** Registerkarte die **Verweis hinzufügen** Dialogfeld anstelle von Verweisen auf die `MarqueeControlLibrary` Assembly direkt.
## <a name="defining-a-custom-control-and-its-custom-designer"></a>Definieren ein benutzerdefiniertes Steuerelement und seinen benutzerdefinierte Designer
Das benutzerdefinierte Steuerelement abgeleitet wird die <xref:System.Windows.Forms.UserControl> Klasse. Dadurch wird das Steuerelement andere Steuerelemente enthalten, und sie erhalten dem Steuerelement auf einen Großteil der Standardfunktionen.
Das benutzerdefinierte Steuerelement müssen einen zugeordneten Designer. Dadurch können Sie einen eindeutigen Eindruck maßgeschneidert für Ihr benutzerdefiniertes Steuerelement zu erstellen.
Sie ordnen das Steuerelement den Designer mit der <xref:System.ComponentModel.DesignerAttribute> Klasse. Da Sie das gesamte Design-Time-Verhalten des benutzerdefinierten Steuerelements entwickeln, implementiert der benutzerdefinierte Designer die <xref:System.ComponentModel.Design.IRootDesigner> Schnittstelle.
#### <a name="to-define-a-custom-control-and-its-custom-designer"></a>Zum Definieren eines benutzerdefinierten Steuerelements und der benutzerdefinierten designer
1. Öffnen der `MarqueeControl` Quelldatei in die **Code-Editor**. Importieren Sie am Anfang der Datei die folgenden Namespaces ein:
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#220](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueecontrol.cs#220)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#220](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueecontrol.vb#220)]
2. Hinzufügen der <xref:System.ComponentModel.DesignerAttribute> auf die `MarqueeControl` Klassendeklaration. Dadurch wird das benutzerdefinierte Steuerelement mit ihren Designer verknüpft.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#240](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueecontrol.cs#240)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#240](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueecontrol.vb#240)]
3. Öffnen der `MarqueeControlRootDesigner` Quelldatei in die **Code-Editor**. Importieren Sie am Anfang der Datei die folgenden Namespaces ein:
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#520](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueecontrolrootdesigner.cs#520)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#520](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueecontrolrootdesigner.vb#520)]
4. Ändern Sie die Deklaration der `MarqueeControlRootDesigner` das erben die <xref:System.Windows.Forms.Design.DocumentDesigner> Klasse. Anwenden der <xref:System.ComponentModel.ToolboxItemFilterAttribute> an die Designer-Interaktion mit der **Toolbox**.
**Beachten Sie** die Definition für die `MarqueeControlRootDesigner` Klasse verfügt über eingeschlossen wurde, in einem Namespace namens "MarqueeControlLibrary.Design." Diese Deklaration setzt der Designer in einer speziellen Namespace für die Design-bezogenen Typen reserviert.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#530](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueecontrolrootdesigner.cs#530)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#530](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueecontrolrootdesigner.vb#530)]
5. Definieren Sie den Konstruktor für die `MarqueeControlRootDesigner` Klasse. Fügen Sie eine <xref:System.Diagnostics.Trace.WriteLine%2A> -Anweisung in den Text des Konstruktors. Dies wird zu Debugzwecken nützlich sein.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#540](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueecontrolrootdesigner.cs#540)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#540](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueecontrolrootdesigner.vb#540)]
## <a name="creating-an-instance-of-your-custom-control"></a>Erstellen einer Instanz des benutzerdefinierten Steuerelements
Um das benutzerdefinierte während der Entwurfszeit Verhalten des Steuerelements zu beobachten, setzen Sie eine Instanz des Steuerelements im Formular in `MarqueeControlTest` Projekt.
#### <a name="to-create-an-instance-of-your-custom-control"></a>Zum Erstellen einer Instanz des benutzerdefinierten Steuerelements
1. Fügen Sie einen neuen <xref:System.Windows.Forms.UserControl> Element für die `MarqueeControlTest` Projekt. Weisen Sie der neuen Quelldatei Basisnamen "DemoMarqueeControl."
2. Öffnen der `DemoMarqueeControl` Datei die **Code-Editor**. Importieren Sie am Anfang der Datei, die `MarqueeControlLibrary` Namespace:
```vb
Imports MarqueeControlLibrary
```
```csharp
using MarqueeControlLibrary;
```
1. Ändern Sie die Deklaration der `DemoMarqueeControl` das erben die `MarqueeControl` Klasse.
2. Erstellen Sie das Projekt.
3. Öffnen Sie `Form1` im Windows Forms-Designer.
4. Suchen der **MarqueeControlTest Komponenten** Registerkarte die **Toolbox** und öffnen Sie sie. Ziehen Sie eine `DemoMarqueeControl` aus der **Toolbox** auf das Formular.
5. Erstellen Sie das Projekt.
## <a name="setting-up-the-project-for-design-time-debugging"></a>Einrichten des Projekts für das Debuggen zur Entwurfszeit
Wenn Sie eine benutzerdefinierte während der Entwurfszeit-Benutzeroberfläche entwickeln, werden Debuggen Sie Ihre Steuerelemente und Komponenten erforderlich. Es ist eine einfache Möglichkeit, Ihr Projekt einzurichten, um Debuggen zur Entwurfszeit zu ermöglichen. Weitere Informationen finden Sie unter [Exemplarische Vorgehensweise: Debuggen von benutzerdefinierten Windows Forms-Steuerelementen zur Entwurfszeit](../../../../docs/framework/winforms/controls/walkthrough-debugging-custom-windows-forms-controls-at-design-time.md).
#### <a name="to-set-up-the-project-for-design-time-debugging"></a>Zum Einrichten des Projekts für Design-Time-Debuggen
1. Mit der rechten Maustaste die `MarqueeControlLibrary` Projekt, und wählen **Eigenschaften**.
2. Wählen Sie in das Dialogfeld "MarqueeControlLibrary-Eigenschaftenseiten" die **Debuggen** Seite.
3. In der **Startaktion** wählen Sie im Abschnitt **externes Startprogramm**. Sie Debuggen eine separate Instanz von Visual Studio, klicken Sie auf die Auslassungspunkte () Schaltfläche, um für die Visual Studio-IDE navigieren. Der Name der ausführbaren Datei lautet devenv.exe aus, und wenn Sie am Standardspeicherort installiert haben, wird der Pfad ist %programfiles%\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe.
4. Klicken Sie auf OK, um das Dialogfeld zu schließen.
5. Mit der rechten Maustaste die `MarqueeControlLibrary` Projekt, und wählen Sie "Als Startprojekt festlegen" aus, um diese Konfiguration für Remotedebugging zu ermöglichen.
## <a name="checkpoint"></a>Checkpoint
Sie können nun das Entwurfszeit-Verhalten des benutzerdefinierten Steuerelements zu debuggen. Nachdem Sie ermittelt haben, dass die debugging-Umgebung ordnungsgemäß eingerichtet ist, testen Sie die Zuordnung zwischen das benutzerdefinierte Steuerelement und dem benutzerdefinierten Designer.
#### <a name="to-test-the-debugging-environment-and-the-designer-association"></a>Zum Testen der Debugumgebung und die designerzuordnung
1. Öffnen der `MarqueeControlRootDesigner` Quelldatei in die **Code-Editor** und platzieren Sie einen Haltepunkt auf der <xref:System.Diagnostics.Trace.WriteLine%2A> Anweisung.
2. Drücken Sie F5, um die Debugsitzung zu starten. Beachten Sie, dass eine neue Instanz von Visual Studio erstellt wird.
3. Öffnen Sie in der neuen Instanz von Visual Studio die Projektmappe "MarqueeControlTest". Finden Sie die Projektmappe durch Auswahl **zuletzt geöffnete Projekte** aus der **Datei** Menü. Die Projektmappendatei "MarqueeControlTest.sln" wird als die zuletzt Datei verwendete aufgeführt.
4. Öffnen der `DemoMarqueeControl` im Designer. Beachten Sie, dass die Debuginstanz von Visual Studio aktiviert und die Ausführung am Haltepunkt an. Drücken Sie F5, um die Debugsitzung fortzusetzen.
An diesem Punkt ist alles, was für Sie zum Entwickeln und Debuggen das benutzerdefinierte Steuerelement und seinen zugeordneten Designer. Der Rest dieser exemplarischen Vorgehensweise wird auf die Details der Implementierung von Features des Steuerelements und dem Designer konzentrieren.
## <a name="implementing-your-custom-control"></a>Implementieren des benutzerdefinierten Steuerelements
Die `MarqueeControl` ist eine <xref:System.Windows.Forms.UserControl> mit ein wenig anpassen. Es macht zwei Methoden verfügbar: `Start`, dem die Animation beginnt und `Stop`, die die Animation beendet. Da die `MarqueeControl` enthält untergeordnete Steuerelemente, die implementieren die `IMarqueeWidget` -Schnittstelle, `Start` und `Stop` aufzählen jedes untergeordnete Steuerelement und rufen die `StartMarquee` und `StopMarquee` Methoden auf jedes untergeordnete Steuerelement bzw. implementiert `IMarqueeWidget`.
Die Darstellung der `MarqueeBorder` und `MarqueeText` Steuerelemente ist abhängig von das Layout an, damit `MarqueeControl` überschreibt der <xref:System.Windows.Forms.Control.OnLayout%2A> -Methode und ruft <xref:System.Windows.Forms.Control.PerformLayout%2A> auf untergeordnete Steuerelemente von diesem Typ.
Dies ist das Ausmaß der der `MarqueeControl` Anpassungen. Die Run-Time-Features werden von implementiert die `MarqueeBorder` und `MarqueeText` Steuerelemente und die Design-Time-Features werden von implementiert die `MarqueeBorderDesigner` und `MarqueeControlRootDesigner` Klassen.
#### <a name="to-implement-your-custom-control"></a>Um Ihr benutzerdefiniertes Steuerelement zu implementieren.
1. Öffnen der `MarqueeControl` Quelldatei in die **Code-Editor**. Implementieren der `Start` und `Stop` Methoden.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#260](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueecontrol.cs#260)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#260](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueecontrol.vb#260)]
2. Überschreiben Sie die <xref:System.Windows.Forms.Control.OnLayout%2A>-Methode.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#270](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueecontrol.cs#270)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#270](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueecontrol.vb#270)]
## <a name="creating-a-child-control-for-your-custom-control"></a>Erstellen ein untergeordnetes Steuerelement für das benutzerdefinierte Steuerelement
Die `MarqueeControl` hostet zwei Arten des untergeordneten Steuerelements: die `MarqueeBorder` Steuerelement und die `MarqueeText` Steuerelement.
- `MarqueeBorder`: Dieses Steuerelement zeichnet einen Rahmen mit "Lichtern", um seinen Rändern. Die LED blinkt nacheinander, damit sie angezeigt werden, um den Rahmen verschieben. Die Geschwindigkeit an, an dem die Lichter Flash, wird gesteuert, durch eine Eigenschaft namens `UpdatePeriod`. Mehrere andere benutzerdefinierten Eigenschaften bestimmen, andere Aspekte der Darstellung des Steuerelements. Zwei Methoden, nämlich `StartMarquee` und `StopMarquee`, steuern, wann die Animation wird gestartet und beendet.
- `MarqueeText`: Dieses Steuerelement zeichnet eine blinkende Zeichenfolge. Wie die `MarqueeBorder` -Steuerelement, die Geschwindigkeit, mit der der Text aufblinkt, wird gesteuert, indem die `UpdatePeriod` Eigenschaft. Die `MarqueeText` -Steuerelement verfügt auch über die `StartMarquee` und `StopMarquee` Methoden gemeinsam mit der `MarqueeBorder` Steuerelement.
Zur Entwurfszeit die `MarqueeControlRootDesigner` können Sie diese beiden Steuerelementtypen hinzugefügt werden eine `MarqueeControl` in beliebiger Kombination.
Allgemeine Funktionen der beiden Steuerelemente sind in der eine Schnittstelle namens berücksichtigt `IMarqueeWidget`. Dadurch wird die `MarqueeControl` Marquee-bezogene untergeordnete Steuerelemente zu ermitteln und diese besondere Behandlung.
Um das Animationsfeature für regelmäßige zu implementieren, verwenden Sie <xref:System.ComponentModel.BackgroundWorker> Objekte aus der <xref:System.ComponentModel?displayProperty=nameWithType> Namespace. Sie können <xref:System.Windows.Forms.Timer> Objekte, wenn jedoch viele `IMarqueeWidget` Objekte vorhanden sind, die einzelnen UI-Thread ist möglicherweise nicht mit der Animation zu halten.
#### <a name="to-create-a-child-control-for-your-custom-control"></a>Um ein untergeordnetes Steuerelement für das benutzerdefinierte Steuerelement zu erstellen.
1. Eine neue Klasse zum Hinzufügen der `MarqueeControlLibrary` Projekt. Weisen Sie der neuen Quelldatei Basisnamen "IMarqueeWidget."
2. Öffnen der `IMarqueeWidget` Quelldatei in die **Code-Editor** und ändern Sie die Deklaration von `class` zu `interface`:
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#2](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/imarqueewidget.cs#2)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#2](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/imarqueewidget.vb#2)]
3. Fügen Sie den folgenden Code der `IMarqueeWidget` verfügbar gemacht werden zwei Methoden und eine Eigenschaft, die die Animation bearbeitet:
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#3](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/imarqueewidget.cs#3)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#3](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/imarqueewidget.vb#3)]
4. Fügen Sie einen neuen **benutzerdefiniertes Steuerelement** Element für die `MarqueeControlLibrary` Projekt. Weisen Sie der neuen Quelldatei Basisnamen "MarqueeText."
5. Ziehen Sie eine <xref:System.ComponentModel.BackgroundWorker> -Komponente aus der **Toolbox** auf Ihre `MarqueeText` Steuerelement. Diese Komponente ermöglicht die `MarqueeText` Steuerelement selbst asynchron aktualisiert.
6. Legen Sie im Fenster Eigenschaften die <xref:System.ComponentModel.BackgroundWorker> Komponente `WorkerReportsProgess` und <xref:System.ComponentModel.BackgroundWorker.WorkerSupportsCancellation%2A> Eigenschaften `true`. Mit diesen Einstellungen können die <xref:System.ComponentModel.BackgroundWorker> Komponente zum Auslösen von in regelmäßigen Abständen die <xref:System.ComponentModel.BackgroundWorker.ProgressChanged> Ereignis und asynchrone Updates abgebrochen. Weitere Informationen finden Sie unter [BackgroundWorker-Komponente](../../../../docs/framework/winforms/controls/backgroundworker-component.md).
7. Öffnen der `MarqueeText` Quelldatei in die **Code-Editor**. Importieren Sie am Anfang der Datei die folgenden Namespaces ein:
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#120](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueetext.cs#120)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#120](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueetext.vb#120)]
8. Ändern Sie die Deklaration der `MarqueeText` zu vererben <xref:System.Windows.Forms.Label> und zum Implementieren der `IMarqueeWidget` Schnittstelle:
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#130](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueetext.cs#130)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#130](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueetext.vb#130)]
9. Deklarieren Sie die Instanzvariablen, die den verfügbar gemachten Eigenschaften entsprechen, und initialisieren sie im Konstruktor. Die `isLit` Feld bestimmt, ob der Text ist in der vorgegebenen durch Farbe gezeichnet werden die `LightColor` Eigenschaft.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#140](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueetext.cs#140)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#140](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueetext.vb#140)]
10. Implementieren Sie die `IMarqueeWidget`-Schnittstelle.
Die `StartMarquee` und `StopMarquee` Aufrufen von Methoden der <xref:System.ComponentModel.BackgroundWorker> Komponente <xref:System.ComponentModel.BackgroundWorker.RunWorkerAsync%2A> und <xref:System.ComponentModel.BackgroundWorker.CancelAsync%2A> Methoden zum Starten und beenden die Animation.
Die <xref:System.ComponentModel.CategoryAttribute.Category%2A> und <xref:System.ComponentModel.BrowsableAttribute.Browsable%2A> Attribute gelten für die `UpdatePeriod` Eigenschaft, sodass er in einem benutzerdefinierten Abschnitt des Fensters Eigenschaften namens "Marquee." angezeigt wird.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#150](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueetext.cs#150)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#150](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueetext.vb#150)]
11. Implementieren Sie die Eigenschaftenaccessoren. Sie werden zwei Eigenschaften für Clients verfügbar zu machen: `LightColor` und `DarkColor`. Die <xref:System.ComponentModel.CategoryAttribute.Category%2A> und <xref:System.ComponentModel.BrowsableAttribute.Browsable%2A> Attribute werden auf diese Eigenschaften angewendet, sodass die Eigenschaften in einem benutzerdefinierten Abschnitt des Fensters Eigenschaften namens "Marquee." angezeigt werden
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#160](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueetext.cs#160)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#160](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueetext.vb#160)]
12. Implementieren Sie die Handler für die <xref:System.ComponentModel.BackgroundWorker> Komponente <xref:System.ComponentModel.BackgroundWorker.DoWork> und <xref:System.ComponentModel.BackgroundWorker.ProgressChanged> Ereignisse.
Die <xref:System.ComponentModel.BackgroundWorker.DoWork> Ereignishandler wartet die angegebene Anzahl von Millisekunden von `UpdatePeriod` löst dann die <xref:System.ComponentModel.BackgroundWorker.ProgressChanged> Ereignis, bis der Code die Animation durch den Aufruf beendet <xref:System.ComponentModel.BackgroundWorker.CancelAsync%2A>.
Die <xref:System.ComponentModel.BackgroundWorker.ProgressChanged> -Ereignishandler schaltet den Text zwischen den hellen und dunklen Zustand Geben Sie die Darstellung der blinken.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#180](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueetext.cs#180)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#180](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueetext.vb#180)]
13. Überschreiben der <xref:System.Windows.Forms.Control.OnPaint%2A> Methode, um die Animation zu aktivieren.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#170](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueetext.cs#170)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#170](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueetext.vb#170)]
14. Drücken Sie F6, um die Projektmappe zu erstellen.
## <a name="create-the-marqueeborder-child-control"></a>Erstellen des untergeordneten MarqueeBorder-Steuerelements
Die `MarqueeBorder` Steuerelement ist etwas komplexer als die `MarqueeText` Steuerelement. Sie verfügt über mehr Eigenschaften und die Animation in der <xref:System.Windows.Forms.Control.OnPaint%2A> Methode ist etwas komplexer. Im Prinzip ist es sehr ähnlich, mit der `MarqueeText` Steuerelement.
Da die `MarqueeBorder` Steuerelement kann die untergeordneten Steuerelemente haben, muss Sie achten <xref:System.Windows.Forms.Control.Layout> Ereignisse.
#### <a name="to-create-the-marqueeborder-control"></a>Beim Erstellen des Steuerelements MarqueeBorder
1. Fügen Sie einen neuen **benutzerdefiniertes Steuerelement** Element für die `MarqueeControlLibrary` Projekt. Weisen Sie der neuen Quelldatei Basisnamen "MarqueeBorder."
2. Ziehen Sie eine <xref:System.ComponentModel.BackgroundWorker> -Komponente aus der **Toolbox** auf Ihre `MarqueeBorder` Steuerelement. Diese Komponente ermöglicht die `MarqueeBorder` Steuerelement selbst asynchron aktualisiert.
3. Legen Sie im Fenster Eigenschaften die <xref:System.ComponentModel.BackgroundWorker> Komponente `WorkerReportsProgess` und <xref:System.ComponentModel.BackgroundWorker.WorkerSupportsCancellation%2A> Eigenschaften `true`. Mit diesen Einstellungen können die <xref:System.ComponentModel.BackgroundWorker> Komponente zum Auslösen von in regelmäßigen Abständen die <xref:System.ComponentModel.BackgroundWorker.ProgressChanged> Ereignis und asynchrone Updates abgebrochen. Weitere Informationen finden Sie unter [BackgroundWorker-Komponente](../../../../docs/framework/winforms/controls/backgroundworker-component.md).
4. Klicken Sie im Eigenschaftenfenster auf die Schaltfläche "Ereignisse". Fügen Sie Handler für die <xref:System.ComponentModel.BackgroundWorker.DoWork> und <xref:System.ComponentModel.BackgroundWorker.ProgressChanged> Ereignisse.
5. Öffnen der `MarqueeBorder` Quelldatei in die **Code-Editor**. Importieren Sie am Anfang der Datei die folgenden Namespaces ein:
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#20](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueeborder.cs#20)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#20](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueeborder.vb#20)]
6. Ändern Sie die Deklaration der `MarqueeBorder` zu vererben <xref:System.Windows.Forms.Panel> und zum Implementieren der `IMarqueeWidget` Schnittstelle.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#30](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueeborder.cs#30)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#30](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueeborder.vb#30)]
7. Deklarieren Sie zwei Enumerationen für die Verwaltung der `MarqueeBorder` Zustand des Steuerelements: `MarqueeSpinDirection`, welche die Richtung, in dem die Lichter "um den Rahmen, und `MarqueeLightShape`, bestimmt die Form der Lichter (quadratische oder zirkuläre). Platzieren Sie diese Deklarationen, bevor Sie die `MarqueeBorder` Klassendeklaration.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#97](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueeborder.cs#97)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#97](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueeborder.vb#97)]
8. Deklarieren Sie die Instanzvariablen, die den verfügbar gemachten Eigenschaften entsprechen, und initialisieren sie im Konstruktor.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#40](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueeborder.cs#40)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#40](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueeborder.vb#40)]
9. Implementieren Sie die `IMarqueeWidget`-Schnittstelle.
Die `StartMarquee` und `StopMarquee` Aufrufen von Methoden der <xref:System.ComponentModel.BackgroundWorker> Komponente <xref:System.ComponentModel.BackgroundWorker.RunWorkerAsync%2A> und <xref:System.ComponentModel.BackgroundWorker.CancelAsync%2A> Methoden zum Starten und beenden die Animation.
Da die `MarqueeBorder` Steuerelement kann die untergeordneten Steuerelemente enthalten die `StartMarquee` Methode listet alle untergeordneten Steuerelemente und Aufrufe `StartMarquee` auf die implementieren `IMarqueeWidget`. Die `StopMarquee` Methode verfügt über eine ähnliche Implementierung.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#50](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueeborder.cs#50)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#50](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueeborder.vb#50)]
10. Implementieren Sie die Eigenschaftenaccessoren. Die `MarqueeBorder` Steuerelement besitzt mehrere Eigenschaften steuern die Darstellung.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#60](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueeborder.cs#60)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#60](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueeborder.vb#60)]
11. Implementieren Sie die Handler für die <xref:System.ComponentModel.BackgroundWorker> Komponente <xref:System.ComponentModel.BackgroundWorker.DoWork> und <xref:System.ComponentModel.BackgroundWorker.ProgressChanged> Ereignisse.
Die <xref:System.ComponentModel.BackgroundWorker.DoWork> Ereignishandler wartet die angegebene Anzahl von Millisekunden von `UpdatePeriod` löst dann die <xref:System.ComponentModel.BackgroundWorker.ProgressChanged> Ereignis, bis der Code die Animation durch den Aufruf beendet <xref:System.ComponentModel.BackgroundWorker.CancelAsync%2A>.
Die <xref:System.ComponentModel.BackgroundWorker.ProgressChanged> Ereignishandler erhöht die Position des Lichts "base", aus dem der hellen/dunklen Status der anderen Lichter bestimmt ist, und ruft die <xref:System.Windows.Forms.Control.Refresh%2A> Methode, um das Steuerelement sich selbst neu zeichnet.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#90](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueeborder.cs#90)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#90](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueeborder.vb#90)]
12. Implementieren Sie die Hilfemethoden `IsLit` und `DrawLight`.
Die `IsLit` Methode bestimmt die Farbe eines Lichts an einer bestimmten Position. Beleuchtung, die "markiert sind" in der vorgegebenen durch Farbe gezeichnet werden die `LightColor` -Eigenschaft, und solche, die "dunklen" sind in der vorgegebenen durch Farbe gezeichnet werden die `DarkColor` Eigenschaft.
Die `DrawLight` Methode zeichnet ein Licht mithilfe der entsprechenden Farbe, Form und Position.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#80](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueeborder.cs#80)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#80](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueeborder.vb#80)]
13. Überschreiben der <xref:System.Windows.Forms.Control.OnLayout%2A> und <xref:System.Windows.Forms.Control.OnPaint%2A> Methoden.
Die <xref:System.Windows.Forms.Control.OnPaint%2A> Methode zeichnet die Lichter an den Rändern der `MarqueeBorder` Steuerelement.
Da die <xref:System.Windows.Forms.Control.OnPaint%2A> Methode, die die Abmessungen des hängt die `MarqueeBorder` -Steuerelement, müssen Sie sie aufrufen, sobald das Layout geändert wird. Um dies zu erreichen, außer Kraft setzen <xref:System.Windows.Forms.Control.OnLayout%2A> , und rufen Sie <xref:System.Windows.Forms.Control.Refresh%2A>.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#70](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueeborder.cs#70)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#70](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueeborder.vb#70)]
## <a name="creating-a-custom-designer-to-shadow-and-filter-properties"></a>Erstellen eines benutzerdefinierten Designers Schatten und Filtereigenschaften
Die `MarqueeControlRootDesigner` Klasse stellt die Implementierung für den Stamm-Designer. Zusätzlich zu diesem Designer, der die benutzerzertifikatauthentifizierung die `MarqueeControl`, benötigen Sie einen benutzerdefinierten Designer, der speziell zugeordnet ist die `MarqueeBorder` Steuerelement. Dieser Designer stellt benutzerdefiniertes Verhalten, das im Rahmen der benutzerdefinierten Stamm-Designer geeignet ist.
Insbesondere die `MarqueeBorderDesigner` "Beschatten" und Filtern Sie nach bestimmten Eigenschaften wird die `MarqueeBorder` Steuerelement, das ihre Interaktion mit der entwurfsumgebung ändern.
Abfangen von Aufrufen von einer Komponente-Eigenschaftenaccessor wird als "shadowing." bezeichnet. Es ermöglicht einem Designer zum Nachverfolgen des Wert, der vom Benutzer festgelegt wird, und übergeben Sie optional den Wert der entworfenen Komponente.
In diesem Beispiel die <xref:System.Windows.Forms.Control.Visible%2A> und <xref:System.Windows.Forms.Control.Enabled%2A> werden Eigenschaften durch ein Shadowing ausgeführt werden die `MarqueeBorderDesigner`, die verhindert, dass die Benutzer können die `MarqueeBorder` Steuerelement unsichtbar oder deaktiviert, während der Entwurfszeit.
Designer können auch hinzufügen und Entfernen von Eigenschaften. In diesem Beispiel die <xref:System.Windows.Forms.Control.Padding%2A> Eigenschaft wird zur Entwurfszeit entfernt werden, da die `MarqueeBorder` Steuerelement programmgesteuert festgelegt, der die Auffüllung basierend auf der Größe der Lichter durch die `LightSize` Eigenschaft.
Die Basisklasse für `MarqueeBorderDesigner` ist <xref:System.ComponentModel.Design.ComponentDesigner>, das hat es sich um Methoden, die die Attribute, Eigenschaften und Ereignisse verfügbar gemacht werden von einem Steuerelement zur Entwurfszeit ändern können:
- <xref:System.ComponentModel.Design.ComponentDesigner.PreFilterProperties%2A>
- <xref:System.ComponentModel.Design.ComponentDesigner.PostFilterProperties%2A>
- <xref:System.ComponentModel.Design.ComponentDesigner.PreFilterAttributes%2A>
- <xref:System.ComponentModel.Design.ComponentDesigner.PostFilterAttributes%2A>
- <xref:System.ComponentModel.Design.ComponentDesigner.PreFilterEvents%2A>
- <xref:System.ComponentModel.Design.ComponentDesigner.PostFilterEvents%2A>
Wenn Sie die öffentliche Schnittstelle einer Komponente, die mit diesen Methoden ändern, müssen Sie die folgenden Regeln einhalten:
- Hinzufügen oder Entfernen von Elementen in der `PreFilter` nur Methoden
- Ändern Sie vorhandene Elemente in der `PostFilter` nur Methoden
- Rufen Sie die basisimplementierung immer zuerst die `PreFilter` Methoden
- Rufen Sie die basisimplementierung immer zuletzt die `PostFilter` Methoden
Die folgenden Regeln einhalten wird sichergestellt, dass alle Designer in der Umgebung zur Entwurfszeit eine konsistente Sicht aller Komponenten entworfen wird.
Die <xref:System.ComponentModel.Design.ComponentDesigner> -Klasse stellt ein Wörterbuch für die Verwaltung von die Werte der Eigenschaften, die Shadowing durchgeführt wurde, sodass Sie keine bestimmte Nachrichteninstanzvariablen erstellen zu müssen.
#### <a name="to-create-a-custom-designer-to-shadow-and-filter-properties"></a>Erstellen ein benutzerdefiniertes Designers für Schattenkopien und filter
1. Mit der rechten Maustaste die **Entwurf** Ordner, und fügen Sie eine neue Klasse hinzu. Benennen Sie der Quelldatei Basis von "MarqueeBorderDesigner."
2. Öffnen der `MarqueeBorderDesigner` Quelldatei in die **Code-Editor**. Importieren Sie am Anfang der Datei die folgenden Namespaces ein:
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#420](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueeborderdesigner.cs#420)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#420](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueeborderdesigner.vb#420)]
3. Ändern Sie die Deklaration der `MarqueeBorderDesigner` zu vererben <xref:System.Windows.Forms.Design.ParentControlDesigner>.
Da die `MarqueeBorder` Steuerelement die untergeordneten Steuerelemente enthalten kann `MarqueeBorderDesigner` erbt <xref:System.Windows.Forms.Design.ParentControlDesigner>, behandelt die über-und untergeordneten Aktivität.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#430](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueeborderdesigner.cs#430)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#430](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueeborderdesigner.vb#430)]
4. Überschreiben die basisimplementierung der <xref:System.ComponentModel.Design.ComponentDesigner.PreFilterProperties%2A>.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#450](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueeborderdesigner.cs#450)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#450](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueeborderdesigner.vb#450)]
5. Implementieren Sie die <xref:System.Windows.Forms.Control.Enabled%2A>-Eigenschaft und die <xref:System.Windows.Forms.Control.Visible%2A>-Eigenschaft. Diese Implementierungen Shadowing für Eigenschaften des Steuerelements.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#440](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueeborderdesigner.cs#440)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#440](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueeborderdesigner.vb#440)]
## <a name="handling-component-changes"></a>Behandeln Änderungen an der Clientkomponenten
Die `MarqueeControlRootDesigner` Klasse enthält die benutzerdefinierte während der Entwurfszeit-Erfahrung für Ihre `MarqueeControl` Instanzen. Die meisten Funktionen während der Entwurfszeit wird geerbt von der <xref:System.Windows.Forms.Design.DocumentDesigner> -Klasse, die Ihr Code werden zwei spezielle Anpassungen zu implementieren: Verarbeitung von Änderungen an der Clientkomponenten und die Designerverben hinzufügen.
Als Benutzern beim Entwerfen ihrer `MarqueeControl` -Instanzen, die Ihre Stamm-Designer wird überwacht Änderungen an der `MarqueeControl` und seine untergeordneten Steuerelemente. Die entwurfszeitumgebung stellt einen geeigneten Dienst, <xref:System.ComponentModel.Design.IComponentChangeService>für nachverfolgung Komponente Zustand ändert.
Sie erhalten einen Verweis auf diesen Dienst, durch Abfragen der Umgebung mit der <xref:System.ComponentModel.Design.ComponentDesigner.GetService%2A> Methode. Wenn die Abfrage erfolgreich ist, kann Designer anfügen ein Handlers für die <xref:System.ComponentModel.Design.IComponentChangeService.ComponentChanged> Ereignis und führen Sie alle Aufgaben zum Erhaltung des konsistenten Zustands zur Entwurfszeit erforderlich sind.
Im Fall von der `MarqueeControlRootDesigner` -Klasse, rufen Sie die <xref:System.Windows.Forms.Control.Refresh%2A> -Methode für jede `IMarqueeWidget` enthaltene Objekt das `MarqueeControl`. Dies bewirkt, dass die `IMarqueeWidget` Objekt sich selbst entsprechend neu zeichnet, wenn Eigenschaften des übergeordneten Elements wie <xref:System.Windows.Forms.Control.Size%2A> geändert werden.
#### <a name="to-handle-component-changes"></a>So behandeln Sie komponentenänderungen
1. Öffnen der `MarqueeControlRootDesigner` Quelldatei in die **Code-Editor** und überschreiben die <xref:System.Windows.Forms.Design.DocumentDesigner.Initialize%2A> Methode. Rufen Sie die basisimplementierung für <xref:System.Windows.Forms.Design.DocumentDesigner.Initialize%2A> und Abfragen für die <xref:System.ComponentModel.Design.IComponentChangeService>.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#580](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueecontrolrootdesigner.cs#580)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#580](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueecontrolrootdesigner.vb#580)]
2. Implementieren der <xref:System.ComponentModel.Design.IComponentChangeService.OnComponentChanged%2A> -Ereignishandler. Testen Sie die sendende Komponente, und es ist ein `IMarqueeWidget`, rufen Sie die <xref:System.Windows.Forms.Control.Refresh%2A> Methode.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#560](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueecontrolrootdesigner.cs#560)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#560](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueecontrolrootdesigner.vb#560)]
## <a name="adding-designer-verbs-to-your-custom-designer"></a>Hinzufügen von Designerverben zu Ihrem benutzerdefinierten Designer
Ein Designerverb ist ein mit einem Ereignishandler verknüpfter Menübefehl. Designerverben werden Kontextmenü einer Komponente zur Entwurfszeit hinzugefügt. Weitere Informationen finden Sie unter <xref:System.ComponentModel.Design.DesignerVerb>.
Fügen Sie zwei Designerverben auf den Designern: **Test ausführen** und **Test beenden**. Diese Verben ermöglichen Sie das Laufzeitverhalten des Anzeigen der `MarqueeControl` zur Entwurfszeit. Diese Verben werden hinzugefügt, die `MarqueeControlRootDesigner`.
Bei **Test ausführen** wird aufgerufen, der Verb-Ereignishandler ruft die `StartMarquee` Methode für die `MarqueeControl`. Bei **Test beenden** wird aufgerufen, der Verb-Ereignishandler ruft die `StopMarquee` Methode für die `MarqueeControl`. Die Implementierung der `StartMarquee` und `StopMarquee` Methoden Aufrufen dieser Methoden für enthaltene Steuerelemente, die implementieren `IMarqueeWidget`, sodass jedes enthaltene `IMarqueeWidget` Steuerelemente im Test ebenfalls einbezogen werden.
#### <a name="to-add-designer-verbs-to-your-custom-designers"></a>So fügen den benutzerdefinierten Designern Designerverben hinzu
1. In der `MarqueeControlRootDesigner` -Klasse verwenden, fügen Sie Ereignishandler mit dem Namen `OnVerbRunTest` und `OnVerbStopTest`.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#570](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueecontrolrootdesigner.cs#570)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#570](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueecontrolrootdesigner.vb#570)]
2. Verbinden Sie diese Ereignishandler mit den entsprechenden Designerverben an. `MarqueeControlRootDesigner` erbt einen <xref:System.ComponentModel.Design.DesignerVerbCollection> von der Basisklasse. Erstellen Sie zwei neue <xref:System.ComponentModel.Design.DesignerVerb> -Objekte und fügen sie dieser Auflistung in der <xref:System.Windows.Forms.Design.DocumentDesigner.Initialize%2A> Methode.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#590](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueecontrolrootdesigner.cs#590)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#590](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueecontrolrootdesigner.vb#590)]
## <a name="creating-a-custom-uitypeeditor"></a>Erstellen eine benutzerdefinierte UITypeEditor
Wenn Sie eine benutzerdefinierte während der Entwurfszeit-Erfahrung für Benutzer erstellen, ist es oft wünschenswert, eine benutzerdefinierte Aktivität mit dem Fenster "Eigenschaften" erstellen. Sie erreichen dies durch das Erstellen einer <xref:System.Drawing.Design.UITypeEditor>. Weitere Informationen finden Sie unter [Vorgehensweise: Erstellen Sie einen Typeditor](https://msdn.microsoft.com/library/292c6e33-8d85-4012-9b51-05835a6f6dfd).
Die `MarqueeBorder` Steuerelement macht mehrere Eigenschaften im Eigenschaftenfenster verfügbar. Zwei dieser Eigenschaften `MarqueeSpinDirection` und `MarqueeLightShape` durch Enumerationen dargestellt werden. Veranschaulicht die Verwendung von einer UI-Typ-Editor die `MarqueeLightShape` Eigenschaft weist eine zugeordnete <xref:System.Drawing.Design.UITypeEditor> Klasse.
#### <a name="to-create-a-custom-ui-type-editor"></a>So erstellen einen benutzerdefinierte UI-Typ-editor
1. Öffnen der `MarqueeBorder` Quelldatei in die **Code-Editor**.
2. In der Definition der `MarqueeBorder` Klasse, deklarieren Sie eine Klasse namens `LightShapeEditor` abgeleitet, die <xref:System.Drawing.Design.UITypeEditor>.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#96](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueeborder.cs#96)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#96](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueeborder.vb#96)]
3. Deklarieren Sie eine <xref:System.Windows.Forms.Design.IWindowsFormsEditorService> Instanzvariable mit dem Namen `editorService`.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#92](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueeborder.cs#92)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#92](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueeborder.vb#92)]
4. Überschreiben Sie die <xref:System.Drawing.Design.UITypeEditor.GetEditStyle%2A>-Methode. Diese Implementierung gibt <xref:System.Drawing.Design.UITypeEditorEditStyle.DropDown>, wodurch angewiesen wird, der entwurfsumgebung Vorgehensweise beim Anzeigen der `LightShapeEditor`.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#93](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueeborder.cs#93)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#93](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueeborder.vb#93)]
5. Überschreiben Sie die <xref:System.Drawing.Design.UITypeEditor.EditValue%2A>-Methode. Diese Implementierung fragt die entwurfsumgebung für eine <xref:System.Windows.Forms.Design.IWindowsFormsEditorService> Objekt. Wenn erfolgreich, er erstellt eine `LightShapeSelectionControl`. Die <xref:System.Windows.Forms.Design.IWindowsFormsEditorService.DropDownControl%2A> Methode wird aufgerufen, um das Starten der `LightShapeEditor`. Der Rückgabewert von diesem Aufruf wird die entwurfsumgebung zurückgegeben.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#94](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/marqueeborder.cs#94)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#94](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/marqueeborder.vb#94)]
## <a name="creating-a-view-control-for-your-custom-uitypeeditor"></a>Erstellen ein Steuerelement für Ihre benutzerdefinierte UITypeEditor
1. Die `MarqueeLightShape` Eigenschaft unterstützt zwei Arten von Licht Shapes: `Square` und `Circle`. Erstellen Sie ein benutzerdefiniertes Steuerelement, das ausschließlich zum Zweck der Anzeige dieser Werte im Fenster Eigenschaften verwendet. Dieses benutzerdefinierte Steuerelement verwendet werden durch Ihre <xref:System.Drawing.Design.UITypeEditor> für die Interaktion mit dem Fenster "Eigenschaften".
#### <a name="to-create-a-view-control-for-your-custom-ui-type-editor"></a>So erstellen einem Steuerelement für die benutzerdefinierte Benutzeroberfläche Typ-editor
1. Fügen Sie einen neuen <xref:System.Windows.Forms.UserControl> Element für die `MarqueeControlLibrary` Projekt. Weisen Sie der neuen Quelldatei Basisnamen "LightShapeSelectionControl."
2. Ziehen Sie zwei <xref:System.Windows.Forms.Panel> -Steuerelemente aus der **Toolbox** auf die `LightShapeSelectionControl`. Nennen Sie diese `squarePanel` und `circlePanel`. Ordnen Sie sie nebeneinander an. Legen Sie die <xref:System.Windows.Forms.Control.Size%2A> -Eigenschaft beider <xref:System.Windows.Forms.Panel> -Steuerelementen an (60, 60). Legen Sie die <xref:System.Windows.Forms.Control.Location%2A> Eigenschaft der `squarePanel` zu steuern (8, 10). Legen Sie die <xref:System.Windows.Forms.Control.Location%2A> Eigenschaft der `circlePanel` die Steuerung an ("80", "10"). Legen Sie schließlich die <xref:System.Windows.Forms.Control.Size%2A> Eigenschaft der `LightShapeSelectionControl` auf (150, 80).
3. Öffnen der `LightShapeSelectionControl` Quelldatei in die **Code-Editor**. Importieren Sie am Anfang der Datei, die <xref:System.Windows.Forms.Design?displayProperty=nameWithType> Namespace:
```vb
Imports System.Windows.Forms.Design
```
```csharp
using System.Windows.Forms.Design;
```
1. Implementieren <xref:System.Windows.Forms.Control.Click> -Ereignishandlern für die `squarePanel` und `circlePanel` Steuerelemente. Diese Methoden rufen <xref:System.Windows.Forms.Design.IWindowsFormsEditorService.CloseDropDown%2A> zum Beenden des benutzerdefiniertes <xref:System.Drawing.Design.UITypeEditor> -offlinebearbeitungssitzung zu starten.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#390](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/lightshapeselectioncontrol.cs#390)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#390](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/lightshapeselectioncontrol.vb#390)]
2. Deklarieren Sie eine <xref:System.Windows.Forms.Design.IWindowsFormsEditorService> Instanzvariable mit dem Namen `editorService`.
```vb
Private editorService As IWindowsFormsEditorService
```
```csharp
private IWindowsFormsEditorService editorService;
```
1. Deklarieren Sie eine `MarqueeLightShape` Instanzvariable mit dem Namen `lightShapeValue`.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#330](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/lightshapeselectioncontrol.cs#330)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#330](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/lightshapeselectioncontrol.vb#330)]
2. In der `LightShapeSelectionControl` -Konstruktor, fügen Sie der <xref:System.Windows.Forms.Control.Click> Ereignishandler die `squarePanel` und `circlePanel` Steuerelemente <xref:System.Windows.Forms.Control.Click> Ereignisse. Darüber hinaus definieren Sie eine Überladung des Konstruktors, der zugewiesen der `MarqueeLightShape` Wert über die entwurfsumgebung für die `lightShapeValue` Feld.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#340](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/lightshapeselectioncontrol.cs#340)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#340](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/lightshapeselectioncontrol.vb#340)]
3. In der <xref:System.ComponentModel.Component.Dispose%2A> -Methode, trennen Sie die <xref:System.Windows.Forms.Control.Click> -Ereignishandler.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#350](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/lightshapeselectioncontrol.cs#350)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#350](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/lightshapeselectioncontrol.vb#350)]
4. Klicken Sie im **Projektmappen-Explorer** auf die Schaltfläche **Alle Dateien anzeigen**. Öffnen Sie die Datei LightShapeSelectionControl.Designer.cs oder LightShapeSelectionControl.Designer.vb-Datei, und entfernen Sie die Standarddefinition des der <xref:System.ComponentModel.Component.Dispose%2A> Methode.
5. Implementiert die `LightShape`-Eigenschaft.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#360](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/lightshapeselectioncontrol.cs#360)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#360](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/lightshapeselectioncontrol.vb#360)]
6. Überschreiben Sie die <xref:System.Windows.Forms.Control.OnPaint%2A>-Methode. Diese Implementierung wird ein ausgefülltes Quadrat und der Kreis gezeichnet. Es wird auch den ausgewählten Wert hervorheben, durch Zeichnen eines Rahmens um eine Form vom Typ oder die andere.
[!code-csharp[System.Windows.Forms.Design.DocumentDesigner#380](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/CS/lightshapeselectioncontrol.cs#380)]
[!code-vb[System.Windows.Forms.Design.DocumentDesigner#380](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.Design.DocumentDesigner/VB/lightshapeselectioncontrol.vb#380)]
## <a name="testing-your-custom-control-in-the-designer"></a>Testen das benutzerdefinierte Steuerelement im Designer
An diesem Punkt können Sie erstellen die `MarqueeControlLibrary` Projekt. Testen Sie die Implementierung durch Erstellen eines Steuerelements, die von erbt die `MarqueeControl` -Klasse und verwenden es in einem Formular.
#### <a name="to-create-a-custom-marqueecontrol-implementation"></a>Erstellen Sie eine benutzerdefinierte Implementierung der MarqueeControl
1. Öffnen Sie `DemoMarqueeControl` im Windows Forms-Designer. Dies erstellt eine Instanz der `DemoMarqueeControl` geben, und zeigt ihn in einer Instanz von der `MarqueeControlRootDesigner` Typ.
2. In der **Toolbox**öffnen die **MarqueeControlLibrary Komponenten** Registerkarte. Sie sehen die `MarqueeBorder` und `MarqueeText` Steuerelemente zur Auswahl zur Verfügung.
3. Ziehen Sie eine Instanz von der `MarqueeBorder` -Steuerelement auf die `DemoMarqueeControl` Entwurfsoberfläche. Docken Sie dieses `MarqueeBorder` Steuerelement an das übergeordnete Steuerelement.
4. Ziehen Sie eine Instanz von der `MarqueeText` -Steuerelement auf die `DemoMarqueeControl` Entwurfsoberfläche.
5. Erstellen Sie die Projektmappe.
6. Mit der rechten Maustaste die `DemoMarqueeControl` , und wählen Sie in der Verknüpfung im Menü der **Test ausführen** Option aus, um die Animation zu starten. Klicken Sie auf **Test beenden** die Animation beendet.
7. Open **Form1** in der Entwurfsansicht.
8. Platzieren Sie zwei <xref:System.Windows.Forms.Button> Steuerelemente im Formular. Nennen Sie diese `startButton` und `stopButton`, und ändern Sie die <xref:System.Windows.Forms.Control.Text%2A> Eigenschaftswerte **starten** und **beenden**bzw.
9. Implementieren <xref:System.Windows.Forms.Control.Click> -Ereignishandlern für beide <xref:System.Windows.Forms.Button> Steuerelemente.
10. In der **Toolbox**öffnen die **MarqueeControlTest Komponenten** Registerkarte. Sie sehen die `DemoMarqueeControl` zur Auswahl zur Verfügung.
11. Ziehen Sie eine Instanz des `DemoMarqueeControl` auf die **Form1** Entwurfsoberfläche.
12. In der <xref:System.Windows.Forms.Control.Click> Ereignishandler Aufrufen der `Start` und `Stop` Methoden für die `DemoMarqueeControl`.
```vb
Private Sub startButton_Click(sender As Object, e As System.EventArgs)
Me.demoMarqueeControl1.Start()
End Sub 'startButton_Click
Private Sub stopButton_Click(sender As Object, e As System.EventArgs)
Me.demoMarqueeControl1.Stop()
End Sub 'stopButton_Click
```
```csharp
private void startButton_Click(object sender, System.EventArgs e)
{
this.demoMarqueeControl1.Start();
}
private void stopButton_Click(object sender, System.EventArgs e)
{
this.demoMarqueeControl1.Stop();
}
```
1. Legen Sie die `MarqueeControlTest` -Projekt als Startprojekt fest, und führen Sie sie. Sie sehen, dass die Anzeige des Formulars Ihre `DemoMarqueeControl`. Klicken Sie auf die **starten** Schaltfläche, um die Animation zu starten. Sie sollten den Text blinken und die Lichter, um den Rahmen angezeigt werden.
## <a name="next-steps"></a>Nächste Schritte
Die `MarqueeControlLibrary` veranschaulicht eine einfache Implementierung von benutzerdefinierten Steuerelementen und den zugeordneten Designer. Sie können dieses Beispiel auf verschiedene Weise komplexere vornehmen:
- Ändern Sie die Eigenschaftswerte für die `DemoMarqueeControl` im Designer. Fügen Sie weitere `MarqueBorder` Steuerelemente und docken Sie sie innerhalb ihrer übergeordneten-Instanzen, um einen verschachtelten Effekt zu erstellen. Experimentieren Sie mit verschiedenen Einstellungen für die `UpdatePeriod` und die Light-bezogene Eigenschaften.
- Erstellen Sie eigene Implementierungen von `IMarqueeWidget`. Sie könnten z. B. ein blinkendes "Neon anmelden" oder ein animiertes Symbol mit mehreren Abbildern erstellen.
- Weiter passen Sie an, die während der Entwurfszeit-Benutzeroberfläche. Sie können versuchen, mehr Eigenschaften als shadowing <xref:System.Windows.Forms.Control.Enabled%2A> und <xref:System.Windows.Forms.Control.Visible%2A>, und neue Eigenschaften hinzufügen. Fügen Sie neue Designerverben um häufige Aufgaben wie das Andocken von untergeordneten Steuerelemente zu vereinfachen.
- Lizenz die `MarqueeControl`. Weitere Informationen finden Sie unter [Vorgehensweise: Lizenz-Komponenten und Steuerelementen](https://msdn.microsoft.com/library/8e66c1ed-a445-4b26-8185-990b6e2bbd57).
- Steuern Sie, wie die Steuerelemente serialisiert werden und wie Code für sie generiert wird. Weitere Informationen finden Sie unter [dynamische Quelle-Codegenerierung und-Kompilierung](../../../../docs/framework/reflection-and-codedom/dynamic-source-code-generation-and-compilation.md).
## <a name="see-also"></a>Siehe auch
<xref:System.Windows.Forms.UserControl>
<xref:System.Windows.Forms.Design.ParentControlDesigner>
<xref:System.Windows.Forms.Design.DocumentDesigner>
<xref:System.ComponentModel.Design.IRootDesigner>
<xref:System.ComponentModel.Design.DesignerVerb>
<xref:System.Drawing.Design.UITypeEditor>
<xref:System.ComponentModel.BackgroundWorker>
[Vorgehensweise: Erstellen eines Windows Forms-Steuerelements, das Entwurfszeitfeatures nutzt](https://msdn.microsoft.com/library/8e0bad0e-56f3-43d2-bf63-a945c654d97c)
[Erweitern der Entwurfszeitunterstützung](https://msdn.microsoft.com/library/d6ac8a6a-42fd-4bc8-bf33-b212811297e2)
[Benutzerdefinierte Designer](https://msdn.microsoft.com/library/ca11988e-d38e-44d8-a05d-71362ae7844d)
[Shape-Bibliothek für .NET: Ein Beispiel-Designer](http://windowsforms.net/articles/shapedesigner.aspx)
| 102.565688 | 719 | 0.796052 | deu_Latn | 0.898509 |
ffbaff09f85bca603098f48f27ed66285db60002 | 6,423 | md | Markdown | README.md | pilikp/django-tof | 81f8557e2455c8464da89e4fc25bfe01f2bf38bc | [
"MIT"
] | 22 | 2019-10-30T11:38:00.000Z | 2021-07-14T19:25:08.000Z | README.md | pilikp/django-tof | 81f8557e2455c8464da89e4fc25bfe01f2bf38bc | [
"MIT"
] | 41 | 2019-11-02T09:15:26.000Z | 2020-10-26T12:18:48.000Z | README.md | pilikp/django-tof | 81f8557e2455c8464da89e4fc25bfe01f2bf38bc | [
"MIT"
] | 20 | 2019-11-09T08:57:02.000Z | 2021-02-08T13:21:45.000Z | 
[](https://github.com/mom1/django-tof/blob/master/LICENSE)
[](https://www.codacy.com/manual/mom1/django-tof?utm_source=github.com&utm_medium=referral&utm_content=mom1/django-tof&utm_campaign=Badge_Grade)
[](https://codecov.io/gh/mom1/django-tof)
[](https://pypi.python.org/pypi/django-tof)
[]()
# django-tof
Django models translation on fly 🛸️
----
This project was initiated, promoted and accompanied by winePad GmbH. All development based on ideas, experience and financing by winePad GmbH (winePad.at).
----
[](https://www.youtube.com/watch?v=i0QJJJEMKSU)
_[Russian readme](README_ru.md)_
----
The background and objectives of this projects are described [here](https://github.com/mom1/django-tof/wiki/django-tof)
An Application for dynamic translation of existing Django models into any number of languages.
- without need to change existing model classes
- without need to reboot servers
- without changing the use of translated fields
- ready to work after install and indicated in INSTALLED_APPS
- fully integrated in Django admin
## Installation
`pip install django-tof`
`python manage.py migrate tof`
~~~python
# settings.py
...
INSTALLED_APPS = [
...
'tof',
...
]
~~~
Don't forget to do if it necessary `python manage.py collectstatic`
## How to use
1. In the simplest use case django-tof allows you to store translation into the current language.
You don't need special settings for this, just add this field into admin panel to the "Translatable fields" model.
In this case if current language is 'en', then the value saved in the model will be displayed only if the current language is 'en'.
1. If you need to support a certain number of languages and add them at the same time, you can use `TofAdmin`.
Using the `class CustomModelAdmin(TofAdmin)` will cause the translated fields (added to the "Translatable fields") will be able to specify a specific language.
At the same time, it is possible to leave some fields in the previous form by specify them in `TofAdmin` with attribute `only_current_lang = ('description', )`. <br>
1. You can also use inline translation submission forms. To do this, specify admin class (always inherited from "TofAdmin") `inlines = (TranslationTabularInline, )`
or `inlines = (TranslationStackedInline, )`
## Programmatic use
Like a standard using, but it is possible to get a specific translation.
~~~python
from django.utils.translation import activate
activate('en')
book = Book.objects.first()
book.title # => Title en
book.title.de # => Title de
~~~
## Settings
_The value for these variables can be specified in your settings.py_
DEFAULT_LANGUAGE: _default_ "en" - Default language is stub, used if not other translations is found.
FALLBACK_LANGUAGES: _default_ `{SITE_ID: ('en', 'de', 'ru'), 'fr': ('nl', ),}` - Determinate the order of search of languages for translation if the translation is in desired
no language. The key can be SITE_ID, None or language.
The processing order is this, if a translation into current/requested language is not found, then first we checked by the language key, if there is, looking translations for requested languages,
if not - we take the SIDE_ID key.
For example:
- if current language "fr", then searching order will be next: "fr" -> "nl" -> DEFAULT_LANGUAGE -> then if there is an original value that was before the declaration of this field like translatable.
- if current language "en", then searching order will be next "en" -> "de" -> "ru" -> DEFAULT_LANGUAGE -> then if there is an original value that was before the declaration of this field like translatable.
DEFAULT_FILTER_LANGUAGE: _default_ "current" - Indicates in which translations search/filter values. May be in the next forms `__all__`, `current`, `['en', 'de']`, `{'en', ('en', 'de', 'ru')}`
- `current` - if this value is assigned, the filtering is occurs only on the translation into the current language. This is a default value.
- `__all__` - if this value is assigned, the filtering is occurs for all translations.
- `['en', 'de']` - if this value is assigned, the filtering is occurs according to translations of the specified languages.
- `{'en', ('en', 'de', 'ru')}` - if this value is assigned, the filtering is occurs according to translations of languages received by the key of current language.
CHANGE_DEFAULT_MANAGER: _default_ "True" - Changing the default manager of the model. If it True, then standard manager is transferred into class attribute "objects_origin",
and "objects" becomes the standard manager inherited from standard with adding the functionality that recognized translated fields and takes into account settings from DEFAULT_FILTER_LANGUAGE.
## Requirements
- Python (\>=3.6)
- Django (\>=2.2)
## How to start development
1. Fork this project
2. Clone the repo
3. Create new branch
4. **Change directory `example_project`**
5. You can use [pyenv](https://github.com/pyenv/pyenv) to select the version of python `pyenv local 3.8.0`
6. We are using [poetry](https://poetry.eustace.io/docs/#installation)
7. Run: `poetry env use python` to use your python version.
8. Run: `poetry install` to install all requirements.
9. Run: `poetry shell` for activation virtual environment.
10. Run: `python manage.py runserver` to start the development server.
| 52.647541 | 248 | 0.751985 | eng_Latn | 0.976421 |
ffbb16e1d96a3251e6f7d3ff09f094e3624c50fa | 3,723 | md | Markdown | dockercon-us-2016/README.md | fernandoseguim/docker-labs | 610f19b41209e76192a3dfbcdfb87728de166eb1 | [
"Apache-2.0"
] | 5 | 2017-01-17T21:29:06.000Z | 2020-05-06T19:14:31.000Z | dockercon-us-2016/README.md | fernandoseguim/docker-labs | 610f19b41209e76192a3dfbcdfb87728de166eb1 | [
"Apache-2.0"
] | null | null | null | dockercon-us-2016/README.md | fernandoseguim/docker-labs | 610f19b41209e76192a3dfbcdfb87728de166eb1 | [
"Apache-2.0"
] | 11 | 2017-05-22T12:27:12.000Z | 2021-09-01T10:06:42.000Z | # DockerCon US 2016 Hands-On Labs (HOL)
This repo contains the series of hands-on labs presented at DockerCon 2016. They are designed to help you gain experience in various Docker features, products, and solutions. Depending on your experience, each lab requires between 30-45 minutes to complete. They range in difficulty from easy to advanced.
Some labs will require you to setup virtual machines with Docker installed. You will find specific requirements in each individual lab guide.
## Lab 01. [Docker for Developers](https://github.com/docker/labs/tree/master/dockercon-us/docker-developer)
Docker for Mac and Docker for Windows are faster, more reliable alternatives to Docker Toolbox for running Docker locally on your Windows or Mac
Infrastructure requirements: This lab requires you to install either Docker for Mac or Docker for Windows on your local machine
Duration: 30 minutes
In this lab you will:
- Install either Docker for Mac or Docker for Windows
- Deploy a sample Docker application
## Lab 02. [Docker Datacenter](https://github.com/docker/labs/tree/master/dockercon-us/docker-datacenter)
Docker Datacenter brings container management and deployment services to enterprises with a production-ready platform supported by Docker and hosted locally behind the firewall.
Infrastructure requirements: This lab requires 3 virtual machines running the latest version of Docker Engine 1.11
Duration: 45 minutes
In this lab you will:
- Install Docker Universal Control Plane
- Deploy a single-container service
- Deploy a multi-container application
- Use users and teams to implement role-based access control
## Lab 03. [Docker Cloud](https://github.com/docker/labs/tree/master/dockercon-us/docker-cloud)
Docker Cloud is Docker's cloud platform to build, ship and run your containerized applications. Docker Cloud enables teams to come together to collaborate on their projects and to automate complex continuous delivery flows. So you can focus on working and improving your app, and leave the rest up to Docker Cloud. Docker Cloud offers a set of services that can be used individually or together for an end-to end solution.
Infrastructure requirements:
- For the management host you may use your local laptop running Docker for Mac or Docker for Windows OR you may use a virtual machine running the latest version of Docker Engine 1.11
- For the managed node you will need one virtual machine running one of the supported Linux distros (RHEL
Duration: 45 minutes
In this lab you will:
- Install the Docker Cloud CLI
- Bring and existing node under management
- Deploy a single container service
- Build an automated CI/CD pipeline with GitHub and Docker Cloud
## Lab 04. [Docker Native Orchestration](https://github.com/mikegcoleman/labs/tree/master/dockercon-us/docker-orchestration)
In this lab you will try out the new features from Docker engine 1.12 that provide native container orchestration. You will deploy a Dockerized application to a single host and test the application. You will then configure Docker for Swarm Computing and deploy the same app across multiple hosts. You will then see how to scale the application and move the workload across different hosts easily.
Infrastructure requirements: You need three virtual machines each running at least RC2 of Docker Engine 1.12. You can install the latest stable release of Docker Engine 1.12 from http://test.docker.com
Duration: 45 minutes
In this lab you will:
- Deploy a single host application with a Dockerfile
- Configure Docker for Swarm Computing
- Deploy the application across multiple hosts
- Scale the application
- Drain a node and reschedule the containers
| 48.986842 | 422 | 0.802847 | eng_Latn | 0.993547 |
ffbb3ad2a5bf37bbd649043ffa50cf7b5535ccf6 | 468 | md | Markdown | readme.md | dinony/mo-vue-table | 916fb6774d7d8001e9212865da0712a9a1e2fef5 | [
"MIT"
] | 1 | 2020-07-23T15:52:53.000Z | 2020-07-23T15:52:53.000Z | readme.md | dinony/mo-vue-table | 916fb6774d7d8001e9212865da0712a9a1e2fef5 | [
"MIT"
] | null | null | null | readme.md | dinony/mo-vue-table | 916fb6774d7d8001e9212865da0712a9a1e2fef5 | [
"MIT"
] | null | null | null | # mo-vue-table
[](https://www.npmjs.com/package/mo-vue-table)
| 46.8 | 132 | 0.728632 | yue_Hant | 0.438004 |
ffbb5e8051b15e1fa49f9698e7f61128cc211051 | 5,965 | md | Markdown | docs/designpatterns/Singleton.md | CodePoem/VDesignPatterns | 409f36141a778c701ecce3cdaea8bcf6a95fd3fd | [
"Apache-2.0"
] | null | null | null | docs/designpatterns/Singleton.md | CodePoem/VDesignPatterns | 409f36141a778c701ecce3cdaea8bcf6a95fd3fd | [
"Apache-2.0"
] | null | null | null | docs/designpatterns/Singleton.md | CodePoem/VDesignPatterns | 409f36141a778c701ecce3cdaea8bcf6a95fd3fd | [
"Apache-2.0"
] | null | null | null | # 单例模式（Singleton）
<a href = "https://www.draw.io/?lightbox=1#Uhttps://raw.githubusercontents.com/CodePoem/VDesignPatterns/master/docs/drawio/Singleton.png">全屏</a> |
<a href = "https://www.draw.io/#Uhttps://raw.githubusercontents.com/CodePoem/VDesignPatterns/master/docs/drawio/Singleton.png">作为模板编辑为新图</a> |
<a href = "https://www.draw.io/#HCodePoem/VDesignPatterns/master/docs/drawio/Singleton.drawio">编辑原图（需登录）</a>
## 定义（what）
- 确保某一个类只有一个实例，并提供一个访问它的全局访问点。
## 缘由（why）
为什么需要单例模式？
实现对唯一实例的受控访问。某种类型的对象应该只需要一个，创建过多的该类型的对象就是浪费资源。
## 实践（how）
在使用单例模式时特别需要注意是否是在多线程的使用场景下，多线程场景下需要考虑线程安全。
### 七种单例写法
#### 1.静态变量（懒汉，线程不安全）
```java
public class Singleton {
private static Singleton instance;
private Singleton() {
}`
public static Singleton getInstance() {
if (instance == null) {
instance = new Singleton();
}
return instance;
}
}
```
```kotlin
class Singleton private constructor(private val param: String) {
companion object {
private var instance: Singleton? = null
fun getInstance(param: String) =
instance ?: Singleton(param).also { instance = it }
}
}
```
- 满足单线程场景下的单例需求且采用了懒加载。
- 多线程场景下不能正确保证单例。
#### 2.静态变量+同步 （懒汉，线程安全）
```java
public class Singleton {
private static Singleton instance;
private Singleton() {
}
public static synchronized Singleton getInstance() {
if (instance == null) {
instance = new Singleton();
}
return instance;
}
}
```
```kotlin
class Singleton private constructor(private val param: String) {
companion object {
private var instance: Singleton? = null
@Synchronized
fun getInstance(param: String) =
instance ?: Singleton(param).also { instance = it }
}
}
```
- 基于静态变量的单例在获取单例的方法上加上了同步关键字 synchronized，能确保多线程场景下的单例。
- 效率较低，存在不必要的同步（instance 已创建的情况下不需要同步）。
#### 3. DCL(double checked locking)双重校验锁（懒汉，线程安全）
```java
public class Singleton {
private volatile static Singleton instance;
private Singleton() {
}
public static Singleton getInstance() {
if (instance == null) {
// 类锁
synchronized (Singleton.class) {
if (instance == null) {
instance = new Singleton();
}
}
}
return instance;
}
}
```
```kotlin
class Singleton private constructor(private val param: String) {
companion object {
@Volatile private var instance: Singleton? = null
fun getInstance(param: String) =
instance ?: synchronized(this) {
instance ?: Singleton(param).also { instance = it }
}
}
}
```
- 基于静态变量+同步，增加一层 instance 的 null 判断，避免不必要的同步（ instance 已创建的情况下不需要同步）。
- 对静态变量 instance 加 volatile 关键字，保证可见性和禁止指令重排序（通过内存屏障实现），但不能保证原子性。
第二个 null 判断是为了避免多个线程通过第一个 null 判断，而造成多次实例化。
instance = new Singleton()语句看起来是一句代码，实际上并不是一个原子操作，它会被编译成多条汇编指令。大致做了三件事：
1. 给 Singleton 实例分配内存。
2. 调用 Singleton 的构造函数，初始化成员变量。
3. 将 instance 对象指向分配的内存空间。
由于指令重排序优化（在保证单线程执行结果正确的情况下优化指令执行执行速度），上述（2）（3）的执行顺序是不能够保证的。
volatile 通过禁止指令重排序的方式，避免多个线程在第一个 null 判断时判断已实例化（实际因为指令重排序 instance 尚未指向分配的内存空间）。
#### 4.静态变量初始化（饿汉，线程安全）
```java
public class Singleton {
private static Singleton instance = new Singleton();
private Singleton() {
}
public static Singleton getInstance() {
return instance;
}
}
```
- Singleton 中的静态变量 instance 基于 classloder 机制避免了多线程的同步问题。
- 没有懒加载效果，instance 在 Singleton 装载的时候就实例化。
#### 5.静态代码块初始化（饿汉，线程安全）
```java
public class Singleton {
private static Singleton instance = null;
static {
instance = new Singleton();
}
private Singleton() {
}
public static Singleton getInstance() {
return instance;
}
}
```
- 同静态变量初始化的单例实现方式差不多。
### 6.静态内部类（懒汉，线程安全）
```java
public class Singleton {
private Singleton(){}
private static class SingletonHolder {
private static final Singleton INSTANCE = new Singleton();
}
public static Singleton getInstance() {
return SingletonHolder.INSTANCE;
}
}
```
- 静态内部类中的静态变量 INSTANCE 基于 classloder 机制避免了多线程的同步问题。
ClassLoader 的 loadClass 方法在加载类的时候使用了 synchronized 关键字。也正是因为这样， 除非被重写，这个方法默认在整个装载过程中都是同步的，也就是保证了线程安全。
所以，以上各种方法，虽然并没有显示的使用 synchronized，但是还是其底层实现原理还是用到了 synchronized。
- 懒加载，Singleton 装载的时候 INSTANCE 不一定被初始化，只有显示调用 getInstance() SingletonHolder 才会被装载从而 INSTANCE 才会初始化。
#### 7.枚举
```java
public enum Singleton {
INSTANCE;
public void whateverMethod() {
}
}
```
```kotlin
enum class Singleton(val param: String) {
INSTANCE("instance");
fun whateverMethod() {}
}
```
- 避免多线程同步问题
- 防止反序列化重新创建新的对象
- 避免反射调用
### 防御攻击
由于类的创建不止通过 new 关键字一种方式，还有克隆、序列化、反射等方式。
#### 防御克隆攻击
```java
public class Singleton implements Cloneable{
···
@Override
protected Object clone() throws CloneNotSupportedException {
return getInstance();
}
}
```
#### 防御序列化攻击
```java
public class Singleton {
···
private Object readResolve() {
return getInstance();
}
}
```
#### 防御反射攻击
枚举法实现单例模式。
### 无锁单例
使用 CAS
```java
public class Singleton {
private static final AtomicReference<Singleton> INSTANCE = new AtomicReference<Singleton>();
private Singleton() {}
public static Singleton getInstance() {
for (;;) {
Singleton singleton = INSTANCE.get();
if (null != singleton) {
return singleton;
}
singleton = new Singleton();
if (INSTANCE.compareAndSet(null, singleton)) {
return singleton;
}
}
}
}
```
- 不需要使用传统的锁机制来保证线程安全,CAS 是一种基于忙等待的算法,依赖底层硬件的实现,相对于锁它没有线程切换和阻塞的额外消耗,可以支持较大的并行度。
- 忙等待可能一直执行不成功(一直在死循环中),会对 CPU 造成较大的执行开销。
- N 个线程同时执行到 singleton = new Singleton();的时候，会有大量对象创建，很可能导致内存溢出。
| 20.152027 | 146 | 0.651467 | yue_Hant | 0.449763 |
ffbb9e9a65fbc07f30ef41fc5fa348bf43fa0ee6 | 1,082 | md | Markdown | README.md | drivebadger/ignore-known | 2d447b621faa72b7dc2a13fd36ae1c956d788ecc | [
"MIT"
] | null | null | null | README.md | drivebadger/ignore-known | 2d447b621faa72b7dc2a13fd36ae1c956d788ecc | [
"MIT"
] | null | null | null | README.md | drivebadger/ignore-known | 2d447b621faa72b7dc2a13fd36ae1c956d788ecc | [
"MIT"
] | null | null | null | This is an extension for Drive Badger. It provides a sample `ignore.uuid` file, containing a list of partition UUIDs, that should be ignored by Mobile Badger after plugging in.
### Installing
This particular configuration repository contains only well-known partition UUIDs - so you can clone and use it directly.
To install, just clone it as `/opt/drivebadger/config/ignore-known` local directory on your Drive Badger drive.
This way, you are able to update it in the future by a single command `/opt/drivebadger/update.sh` (it automatically runs
`/opt/drivebadger/internal/mobile/rebuild-uuid-lists.sh` after update - if you want to update this repository alone,
remember to run this script manually).
Multiple `ignore.uuid` files are allowed - each in separate repository.
### More information
- [Drive Badger main repository](https://github.com/drivebadger/drivebadger)
- [Drive Badger wiki](https://github.com/drivebadger/drivebadger/wiki)
- [description, how configuration repositories work](https://github.com/drivebadger/drivebadger/wiki/Configuration-repositories)
| 51.52381 | 176 | 0.791128 | eng_Latn | 0.973266 |
ffbb9ffaf3611795ce8677988a3c2145ed859432 | 882 | md | Markdown | docs/book/addtag.md | OnePlc/PLC_X_Tag | 7151ebe98c51114df7eeb4c7182927784e8dc890 | [
"BSD-3-Clause"
] | null | null | null | docs/book/addtag.md | OnePlc/PLC_X_Tag | 7151ebe98c51114df7eeb4c7182927784e8dc890 | [
"BSD-3-Clause"
] | 7 | 2020-01-31T19:34:12.000Z | 2021-03-11T20:17:20.000Z | docs/book/addtag.md | OnePlc/PLC_X_Tag | 7151ebe98c51114df7eeb4c7182927784e8dc890 | [
"BSD-3-Clause"
] | null | null | null | # add new tag
onePlace Tag comes with "Category" and "State" Tag by default.
You can add any tag you want to enhance your experience with tag module.
All you have to do, is to add it to the `core_tag` table. there you can
also check for other tags maybe be added by other modules already.
You have to define a `tag_key` (english, no special characters, 1 word)
and a `tag_label` (should be english can be translated in mo files)
In this example we add a tag called `Deliverytime` - which is then available
for all entities in oneplace.
```sql
INSERT INTO `core_tag` (`Tag_ID`, `tag_key`, `tag_label`, `created_by`, `created_date`, `modified_by`, `modified_date`) VALUES
(NULL, 'deliverytime', 'Deliverytime', 1, '0000-00-00 00:00:00', 1, '0000-00-00 00:00:00');
```
You can now use your new tag e.G for select fields in your forms
> /tag/api/list/yourform-single/deliverytime | 42 | 126 | 0.736961 | eng_Latn | 0.992508 |
ffbbb497e3780cb754cd87b45cd81721f94efaf7 | 1,903 | md | Markdown | Documentation/Guides/FORCE-TLS.md | sskharate/fastly-magento2 | ff769aff1e7446b2cec9ac6ad0730f852398c9fa | [
"BSD-3-Clause"
] | null | null | null | Documentation/Guides/FORCE-TLS.md | sskharate/fastly-magento2 | ff769aff1e7446b2cec9ac6ad0730f852398c9fa | [
"BSD-3-Clause"
] | null | null | null | Documentation/Guides/FORCE-TLS.md | sskharate/fastly-magento2 | ff769aff1e7446b2cec9ac6ad0730f852398c9fa | [
"BSD-3-Clause"
] | null | null | null | # Force TLS guide
This guide will show how to setup Secure base URL in Magento and turn on Force TLS option.
For this, you will need to have a TLS certificate. You can read [here](https://docs.fastly.com/guides/securing-communications/) on how to order a TLS certificate through Fastly and then set it up.
Once you're ready, go to:
```
Magento admin > Stores > Configuration > General > Web
```
Click on the **Base URLs (Secure)** tab and enter your **Secure Base URL**. Also, set **Use Secure URLs in Frontend** and **Use Secure URLs in Admin** options to **Yes**.
Once you're done, press the Save config button in the upper right corner.
### Allowing only TLS connections to your site
If you want to only allow TLS on your site, we have you covered.
There is an option built into the Fastly module that will allow you to force unencrypted requests over to TLS. It works by returning a 301 Moved Permanently response to any unencrypted request, which redirects to the TLS equivalent. For instance, making a request for http://www.example.com/foo.jpeg would redirect to https://www.example.com/foo.jpeg.
To enable Force TLS option, go to:
```
Magento admin > Stores > Configuration > Advanced > System > Full Page Cache > Fastly Configuration
```
Under the **Advanced Configuration** tab, press the **Force TLS** button.
The modal window with the following content will pop up, press the **Upload button** in the upper right corner:
Once done, the modal windows will close and you will see a success message. Also, the current state will change to **enabled**.
| 44.255814 | 351 | 0.742512 | eng_Latn | 0.974313 |
ffbbce63aa03f9046c86e9c394267d135f9d1e62 | 1,484 | md | Markdown | README.md | underlaketech/eaglemountain-nodejs-sendmail-util | 1efce8c3bc9439230a533a944bb9a9c16077c83c | [
"BSD-2-Clause"
] | null | null | null | README.md | underlaketech/eaglemountain-nodejs-sendmail-util | 1efce8c3bc9439230a533a944bb9a9c16077c83c | [
"BSD-2-Clause"
] | null | null | null | README.md | underlaketech/eaglemountain-nodejs-sendmail-util | 1efce8c3bc9439230a533a944bb9a9c16077c83c | [
"BSD-2-Clause"
] | null | null | null | ---
title: sendmail-util
---
# Background
Sometimes it's useful to send an email from the command line. The ancient
Linux tools like sendmail, exim, and postfix are somewhat complicated to setup
because they have so many options and capabilities. When you don't want a
complete SMTP server with user aliasing, relaying from selected servers, etc.,
when you want to just connect to the recipient's SMTP server directly and
deliver the message, and you want to do it from the command line, but you
don't want to use telnet :) then you might find this package useful.
# Abstract
The `@underlake/sendmail-util` package provides a command line interface to
the [sendmail](https://www.npmjs.com/package/sendmail) library which delivers the message.
# Install
```
npm install -g @underlake/sendmail-util
```
# Usage
## Console help
```
sendmail --help
```
## Send text message
```
sendmail --from [email protected] --to [email protected] --subject "text greeting" --text "hello world"
```
## Send html message
```
sendmail --from [email protected] --to [email protected] --subject "html greeting" --html "hello <b>world</b>"
```
## Multiple recipients
```
sendmail --from [email protected] --to [email protected] --to [email protected] --subject "multi greeting" --text "hello everyone"
```
## Attachments
```
sendmail --from [email protected] --to [email protected] --subject "files" --text "see attachments" --attach /path/to/file1 --attach /path/to/file2
```
| 25.586207 | 151 | 0.729784 | eng_Latn | 0.97802 |
ffbc45271f27fa78e2257be3873bcb8b4e205574 | 9,782 | md | Markdown | CONTRIBUTING.md | umangmoe/segment-docs | 7aa6f732d9178cc69430bd62acf946bf527e383a | [
"CC-BY-4.0"
] | 13 | 2021-09-24T18:08:49.000Z | 2022-02-22T19:56:13.000Z | CONTRIBUTING.md | umangmoe/segment-docs | 7aa6f732d9178cc69430bd62acf946bf527e383a | [
"CC-BY-4.0"
] | 603 | 2021-09-24T18:12:42.000Z | 2022-03-31T20:03:20.000Z | CONTRIBUTING.md | umangmoe/segment-docs | 7aa6f732d9178cc69430bd62acf946bf527e383a | [
"CC-BY-4.0"
] | 56 | 2021-09-24T18:12:16.000Z | 2022-03-30T18:35:20.000Z | # Contributing to Segment Docs
## Getting Started
Before you begin:
- This site is powered by [Jekyll](https://www.jekyllrb.com).
- Please familiarize yourself with the licensing agreement.
- Browse existing issues to see if your issue has been raised already.
## Use the contribution links from any docs page
Not all pages have a 1-1 mapping with their location within the repository. This can make browsing and locating the file you're trying to reference a challenge. As you browse [segment.com/docs](https://segment.com/docs), you'll notice two links in the right sidebar, at the top of the page. Click **Edit this page** to open the page in the GitHub editor. Or, click **Request docs change** to create a new issue that references the page.
## Want to go deeper? Fork the repository
You can fork this repository and clone it to your local machine to make larger changes. Examples of larger changes include:
- editing more than one file at a time
- adding or updating images
- updating navigation items
In this scenario, you'll fork the repository, clone it locally, make your changes, and submit a pull request to have them reviewed and merged back into the site.
## Site structure
As mentioned, the Segment docs site is powered by Jekyll, with a few customizations and enhancements. Generally speaking, everything you'll need to edit is located in the `_src/` directory. This directory contains the data files, layouts, sass, and markdown source files that combine to make a live, working website.
Within the `/src/` path, anything that starts with an underscore (like `_data` or `_includes`) is a utility directory, and Jekyll won't render it as a webpage path at build time. (In fact, any files where the name starts with an underscore are dropped from the build.)
### Underscore files
Anything that starts with an `_` is a utility directory of some sort (and Jekyll will skip/not render any file that starts with a `_`).
The most interesting ones are:
- `/src/_includes/content/` This is where all the includes or "partials" - the reusable content - are stored.
- `/src/_data/catalog/` This is where we keep the data we've pulled from the ConfigAPI in structured `yml` files that are used by the build.
- `/src/_data/sidenav/` This is where the navigation structures are. (Several sections in the doc have their own left-nav, making them "microsites".) They're just YML files that we manually update so we have maximum control over what's shown and what's not.
### Images
**Save all images locally! No linking to third-party hosted images!** Images are published to our CDN from the build step, and this means they won't go missing if the hosting service dujour goes out of business.
There are no _enforced_ naming conventions at this time. Files that start with an underscore are ignored by Jekyll. Anything you see with `asset` was dowloaded by a script to migrate it out of Contents.io.
In general, it's a good practice to name images with a description that helps you (& other docs maintainers) figure out where they should go within a page, or within a larger folder of images.
A few possibilities/suggestions:
- **Add a prefix of what file the image appears in**. This is helpful if you have images for multiple pages in the same `images` directory, but breaks down a bit if you reuse images across multiple pages.
- **Give a prefix of the application the screenshot shows**. For example `atom-new-file.png`, `atom-commit-changes.png` etc),
- **Name images to describe a process flow**. For example `checkout-1-add-to-cart.png`, `checkout-2-est-shipping.png` and so on.
### Content structure
There are folders for each of the top level products, and those folders might also contain topics that are related to that product area (for example the Privacy Portal section also contains GDPR/CCPA docs).
For the Connections product, the section is divided into the Spec, then Sources, Destinations, and Storage Destinations (formerly called "Warehouses"), with general accessory topics at the folder root. (More specific accessory topics are in each sub directory.)
Each also contains a `catalog` directory, which contains all the directories with information about specific integrations. The top-level of this `catalog` folder (the `index.md`) is a pretty "catalog" page which gives a tile-like view by category, suitable for browsing. It pulls the logo for these tiles from the path for the integration in the metadata, either in `destinations.yml`, `sources.yml`, or `warehouses.yml`.
### Programmatic content
Programmatic content is sections of documentation that are built conditionally, or using public information from our Config API. This is *awesome* and like the holy grail of docs systems.
Programmatic content is built using information in the files in `/src/_data/catalog/`. These files (with the exception of `warehouses.yml`) are built by the `make catalog` command, which contacts our public ConfigAPI, gets a list of all the available integrations using the Catalog API, and then parses them into static `.yml` files.
Most of the programmatic content is built into the `_layouts` templates that each page uses. Sources, Destinations, and Warehouses use the `integration.html` template, which uses some Liquid logic, and calls an `include` depending on the integration type. Most of logic for the actual content must live in the include file itself, however logic controlling *if* the include is built can live in the `layout`.
Destination pages include the `destination-dossier.html` and `destination_footer.md` content, which use Liquid scripting and pulls from the catalog metadata.
Sources pages check if the source is a cloud-app, then include information about if the source is an object or event source, based on the `type` data from the ConfigAPI.
## Edit pages
Content with in each `.md` file is markdown. For information about styling, and available extensions, see `_src/utils/formatguide.md` or the live version [here](https://segment.com/docs/utils/formatguide).
### Front matter
Repository Markdown files often contain front matter metadata, which you'll find at the top of the file. These front matter variables instruct Jekyll how to build and render the page as HTML.
Front matter in a file will look something like this:
```md
---
title: Analytics.js Library
hide-feedback: false
---
```
Front matter variables have unique functions, including the following:
#### Content-related front matter
- `beta`: default false. When true, show an "in beta" warning in the page layout (see the warning in `_includes/content/beta-note.md`)
- `rewrite`: defaults to false. This is a legacy front matter flag that comes from the old `site-docs` repo, and which labels any destination that was rewritten in ~2018 to a standardized template. It disables the duplicate "connection modes" table that would otherwise show up in the boilerplate content at the end of the page.
- `hide-dossier`: defaults to false. When true, hides the "quick info" box at the top of a destination page.
- `hide-boilerplate`: defaults to false. When true, none of the content from `destination-footer.md` is appended to the destination page.
- `hide-cmodes`: defaults to false. A renaming of "rewrite" for more clarity, hides the connection modes table in the boilerplate.
- `hide-personas-partial`: defaults to false. When true, hides the section of content from `destination-footer.md` that talks about being able to receive personas data.
- `integration_type`: This is set in the `_config.yml` on three paths to add a noun (Source, Destination, or Warehouse) to the end of the title, and the end of the title tag in the html layout. It also controls the layout and icon for some of these.
- `source-type`: These are only used to supplement when a Cloud App in the sources path doesn't appear in the Config API list, and needs its type explicitly set. It runs some logic in the `cloud-app-note.md` to explain which cloud-apps are object vs event sources.
#### Utility front matter
- `published`: defaults to true. Set this to "false" to prevent Jekyll from rendering an HTML page for this file. Good for when you're working on something in the repo but aren't ready to release it yet, and don't want to use a Draft PR.
- `hidden`: omits the file from the `sitemap.xml`, adds a `<meta name="robots" content="noindex" />` to the top of the generated HTML file, and drops it from the convenience script for regenerating the nav.
- `hide-sidebar`: defaults to false. When true, hide the entire right-nav sidebar. Use with `hide-feedback` if you want to disable *all* feedback affordances.
- `hide-feedback`: defaults to false. When true, hide the feedback in both rnav and footer. Good for landing pages.
- `hide_toc`: hides the right-nav TOC that's generated from H2s. Also good for landing pages.
- `landing`: defaults to false. Use this to drop the noun set by `integration_type` from the tab title.
- `redirect_from`: Defaults to null. Takes an array of URLs from the front matter in a file, and generates a "stub" page at each URL at build-time. Each stub file redirects to the original file. Use the path from the root of the content directory, for example `/connections/destinations/catalog/` rather than `/docs/connections/destinations/catalog/`. **Note** We are mostly using NGINX redirects for SEO purposes. Approximately quarterly, we'll collect these and add them to NGINX.
- `seo-changefreq`: default: `weekly `. Use the values [in the sitemap spec](https://www.sitemaps.org/protocol.html#xmlTagDefinitions). - sets the `changefreq` tag in the sitemap.xml generator, which tells search crawlers how often to check back.
- `seo-priority`: values from `1.0` to `0.1`, default: `0.5 `. Sets the `Priority` tag in the sitemap
| 85.06087 | 482 | 0.771519 | eng_Latn | 0.999183 |
ffbc7b7cca27426566fa5eb5dd9e269de36b91e4 | 16 | md | Markdown | application/neo4j/README.md | cw19931024/grapDemo | 239d90ed6d05adc42eaa5c2b2c4f2735254b986d | [
"MIT"
] | 140 | 2019-07-15T02:58:22.000Z | 2022-03-24T04:31:59.000Z | application/neo4j/README.md | Miazzy/GraphVisx | 75973a6b67245866184a7c7d0fd46a97ef70bb3b | [
"MIT"
] | 2 | 2020-08-12T04:11:29.000Z | 2022-02-23T09:26:50.000Z | application/neo4j/README.md | Miazzy/GraphVisx | 75973a6b67245866184a7c7d0fd46a97ef70bb3b | [
"MIT"
] | 36 | 2019-09-04T01:09:37.000Z | 2022-03-10T10:34:15.000Z | # Neo4j图数据库可视化应用 | 16 | 16 | 0.875 | vie_Latn | 0.315008 |
ffbd8ec9ee4b5c01a6eeef4b61ff97c44e57bdd2 | 170 | md | Markdown | README.md | batthews/SOMeSolution | 07e50803d3f0142be8929667fb74e69b065c21a9 | [
"BSD-3-Clause"
] | null | null | null | README.md | batthews/SOMeSolution | 07e50803d3f0142be8929667fb74e69b065c21a9 | [
"BSD-3-Clause"
] | null | null | null | README.md | batthews/SOMeSolution | 07e50803d3f0142be8929667fb74e69b065c21a9 | [
"BSD-3-Clause"
] | null | null | null | # SOMesolution
An iteratively developed approach to the problem of fast SOM training. Will work towards the implementation of the HPSOM algorithm described by Liu et al.
| 56.666667 | 154 | 0.823529 | eng_Latn | 0.993633 |
ffbdb350e2aac66357d805fc1b26b152dbdbab06 | 2,072 | md | Markdown | docs/guides/query-string.md | kingster/Crow | 4f533c4bab88f53b542949167dbaf0d9bf1ba215 | [
"Unlicense"
] | 1 | 2019-08-09T01:42:18.000Z | 2019-08-09T01:42:18.000Z | docs/guides/query-string.md | kingster/crow | 4f533c4bab88f53b542949167dbaf0d9bf1ba215 | [
"Unlicense"
] | null | null | null | docs/guides/query-string.md | kingster/crow | 4f533c4bab88f53b542949167dbaf0d9bf1ba215 | [
"Unlicense"
] | null | null | null | A query string is the part of the URL that comes after a `?` character, it is usually formatted as `key=value&otherkey=othervalue`.
<br><br>
Crow supports query strings through `crow::request::url_params`. The object is of type `crow::query_string` and can has the following functions:<br>
## get(name)
Returns the value (as char*) based on the given key (or name). Returns `nullptr` if the key is not found.
## pop(name)
**Introduced in: `v0.3`**<br><br>
Works the same as `get`, but removes the returned value.
!!! note
`crow::request::url_params` is a const value, therefore for pop (also pop_list and pop_dict) to work, a copy needs to be made.
## get_list(name)
A URL can be `http://example.com?key[]=value1&key[]=value2&key[]=value3`. Using `get_list("key")` on such a URL returns an `std::vector<std::string>` containing `[value1, value2, value3]`.<br><br>
`#!cpp get_list("key", false)` can be used to parse `http://example.com?key=value1&key=value2&key=value3`
## pop_list(name)
**Introduced in: `v0.3`**<br><br>
Works the same as `get_list` but removes all instances of values having the given key (`use_brackets` is also available here).
## get_dict(name)
Returns an `std::unordered_map<std::string, std::string>` from a query string such as `?key[sub_key1]=value1&key[sub_key2]=value2&key[sub_key3]=value3`.<br>
The key in the map is what's in the brackets (`sub_key1` for example), and the value being what's after the `=` sign (`value1`). The name passed to the function is not part of the returned value.
## pop_dict(name)
**Introduced in: `v0.3`**<br><br>
Works the same as `get_dict` but removing the values from the query string.
!!! warning
if your query string contains both a list and dictionary with the same key, it is best to use `pop_list` before either `get_dict` or `pop_dict`, since a map cannot contain more than one value per key, each item in the list will override the previous and only the last will remain with an empty key.
<br><br>
For more information take a look [here](../../reference/classcrow_1_1query__string.html).
| 62.787879 | 302 | 0.728282 | eng_Latn | 0.99724 |
ffbdd98d653e20162dd72a9f928216e761669d81 | 2,700 | md | Markdown | memdocs/configmgr/develop/reference/core/servers/configure/sms_adsubnet-server-wmi-class.md | mainsails/memdocs | 0c590de609d1cabc370904187ba681b48cf4cf42 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | memdocs/configmgr/develop/reference/core/servers/configure/sms_adsubnet-server-wmi-class.md | mainsails/memdocs | 0c590de609d1cabc370904187ba681b48cf4cf42 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | memdocs/configmgr/develop/reference/core/servers/configure/sms_adsubnet-server-wmi-class.md | mainsails/memdocs | 0c590de609d1cabc370904187ba681b48cf4cf42 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
description: Learn how to use SMS_ADSubnet class as an SMS Provider server class that contains Active Directory subnets discovered by CM Forest Discovery.
title: "SMS_ADSubnet Class"
titleSuffix: "Configuration Manager"
ms.date: "09/20/2016"
ms.prod: "configuration-manager"
ms.technology: configmgr-sdk
ms.topic: reference
ms.assetid: d07d5b73-8504-4ea1-9860-959f7dbd33cc
author: aczechowski
ms.author: aaroncz
manager: dougeby
ms.localizationpriority: null
ms.collection: openauth
---
# SMS_ADSubnet Server WMI Class
The `SMS_ADSubnet` Windows Management Instrumentation (WMI) class is an SMS Provider server class, in Configuration Manager, that contains Active Directory subnets discovered by Configuration Manager Forest Discovery.
The following syntax is simplified from Managed Object Format (MOF) code and includes all inherited properties.
## Syntax
```
Class SMS_ADSubnet : SMS_BaseClass
{
String ADSubnetDescription;
String ADSubnetLocation;
String ADSubnetName;
UInt32 Flags;
UInt32 ForestID;
DateTime LastDiscoveryTime;
UInt32 SiteID;
UInt32 SubnetID;
};
```
## Methods
The `SMS_ADSubnet` class does not define any methods.
## Properties
`ADSubnetDescription`
Data type: `String`
Access type: Read-only
Qualifiers: [read]
Description of the Active Directory subnet.
`ADSubnetLocation`
Data type: `String`
Access type: Read-only
Qualifiers: [read]
Location of the Active Directory subnet.
`ADSubnetName`
Data type: `String`
Access type: Read-only
Qualifiers: [read]
Name of the Active Directory subnet.
`Flags`
Data type: `UInt32`
Access type: Read-only
Qualifiers: [read]
Flags.
`ForestID`
Data type: `UInt32`
Access type: Read/Write
Qualifiers: [key]
Identifier of the Active Directory forest.
`LastDiscoveryTime`
Data type: `DateTime`
Access type: Read-only
Qualifiers: [read]
The last time this Active Directory subnet was discovered by Active Directory discovery.
`SiteID`
Data type: `UInt32`
Access type: Read/Write
Qualifiers: [key]
Reference to the `SMS_ADSite SiteID` value.
`SubnetID`
Data type: `UInt32`
Access type: Read/Write
Qualifiers: [key]
The subnet ID.
## Requirements
### Runtime Requirements
For more information, see [Configuration Manager Server Runtime Requirements](../../../../../develop/core/reqs/server-runtime-requirements.md).
### Development Requirements
For more information, see [Configuration Manager Server Development Requirements](../../../../../develop/core/reqs/server-development-requirements.md).
| 22.131148 | 219 | 0.717778 | eng_Latn | 0.570557 |
ffbdecedd5a94ad9524922d64081e25aedbb472c | 16 | md | Markdown | README.md | TreykoKabana/lo | e22eb4eacb630d14639403f541b8caa1fd39e13b | [
"MIT"
] | null | null | null | README.md | TreykoKabana/lo | e22eb4eacb630d14639403f541b8caa1fd39e13b | [
"MIT"
] | null | null | null | README.md | TreykoKabana/lo | e22eb4eacb630d14639403f541b8caa1fd39e13b | [
"MIT"
] | null | null | null | # lo
kabana goo
| 5.333333 | 10 | 0.6875 | tsn_Latn | 0.939457 |
ffbe2f304ad22643943c0170c109ce6e028d8959 | 4,076 | md | Markdown | windows-apps-src/publish/app-management-and-services.md | Howard20181/windows-uwp.zh-cn | 4a36ae6ea1fce51ff5fb13288a96f68790d2bd29 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | windows-apps-src/publish/app-management-and-services.md | Howard20181/windows-uwp.zh-cn | 4a36ae6ea1fce51ff5fb13288a96f68790d2bd29 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | windows-apps-src/publish/app-management-and-services.md | Howard20181/windows-uwp.zh-cn | 4a36ae6ea1fce51ff5fb13288a96f68790d2bd29 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
description: 在合作伙伴中心中管理和查看与每个应用相关的详细信息，并配置服务（如 A/B 测试和地图）。
title: 应用管理和服务
ms.assetid: 99DA2BC1-9B5D-4746-8BC0-EC723D516EEF
ms.date: 03/21/2019
ms.topic: article
keywords: windows 10, uwp
ms.localizationpriority: medium
ms.openlocfilehash: e973e9b3a8f3c9ba63a091f4e542e36a84c26128
ms.sourcegitcommit: a3bbd3dd13be5d2f8a2793717adf4276840ee17d
ms.translationtype: MT
ms.contentlocale: zh-CN
ms.lasthandoff: 10/30/2020
ms.locfileid: "93032750"
---
# <a name="app-management-and-services"></a>应用管理和服务
你可以在 [合作伙伴中心](https://partner.microsoft.com/dashboard)中管理和查看与每个应用相关的详细信息，并配置通知、A/B 测试和地图等服务。
使用合作伙伴中心的应用时，可以在 " **服务** 和 **应用管理** " 的左侧导航菜单中看到部分。 可以展开这些部分，访问如下所述的功能。
## <a name="services"></a>服务
**服务** 部分让你可以管理多个不同的应用服务。
## <a name="xbox-live"></a>Xbox Live
如果你正在发布游戏，则可以在此页上启用 [Xbox Live 创建者计划](https://www.xbox.com/developers/creators-program) 。 这样，你就可以开始配置和测试 Xbox Live 功能，并最终发布 Xbox Live 创意者计划游戏。
有关详细信息，请参阅 [Xbox Live 创建者计划入门](/gaming/xbox-live/get-started-with-creators/get-started-with-xbox-live-creators) 和 [创建新的 Xbox Live 创建者计划标题并发布到测试环境](/gaming/xbox-live/get-started-with-creators/create-and-test-a-new-creators-title)。
## <a name="experimentation"></a>试验
将 **实验** 页和 A/B 测试结合，用于创建并运行通用 Windows 平台 (UWP) 应用的实验。 在 A/B 测试中，你先衡量应用更改对某些客户的有效性，然后再为所有用户启用更改。
有关详细信息，请参阅[通过 A/B 测试运行应用实验](../monetize/run-app-experiments-with-a-b-testing.md)。
## <a name="maps"></a>Maps
若要在面向 Windows 10 或 Windows 8.x 的应用中使用地图服务，请访问[必应地图开发人员中心](https://www.bingmapsportal.com/)。 有关如何从必应地图开发人员中心请求地图身份验证密钥并将其添加到应用的信息，请参阅 [请求地图身份验证密钥](../maps-and-location/authentication-key.md) 以获取详细信息。
仅将 " **映射** " 页用于 Windows Phone 8.1 及更早版本的以前发布的应用。 若要在这些应用中使用地图服务，需要请求一个映射服务应用程序 ID 和一个令牌，将其包含在应用代码中。 单击 " **获取令牌** " 时，我们将生成一个映射服务应用程序 ID ( **ApplicationID** ) 并为应用程序 ( **AuthenticationToken** ) 映射服务身份验证令牌。 打包并提交应用之前，请务必将这些值添加到代码。 有关详细信息，请参阅[如何将地图控件添加某一页面 (Windows Phone 8.1)](/previous-versions/windows/apps/jj207033(v=vs.105))。
## <a name="product-collections-and-purchases"></a>产品收集和购买
若要使用 Microsoft Store 收集 API 和 Microsoft Store 购买 API 来访问应用和外接程序的所有权信息，需要在此处输入关联的 Azure AD 客户端 Id。 请注意，需要 16 个小时才能使这些更改生效。
有关详细信息，请参阅[管理来自服务的产品授权](../monetize/view-and-grant-products-from-a-service.md)。
## <a name="administrator-consent"></a>管理员许可
如果你的产品与 Azure AD 集成，并调用了要求管理员同意的 [应用程序权限或委托权限](/graph/permissions-reference) 的 api，请在此处输入你的 Azure AD 客户端 ID。 这样，为组织获取应用的管理员就会授权你的产品代表租户中的所有用户。
有关详细信息，请参阅[请求整个租户的许可](/azure/active-directory/develop/v2-permissions-and-consent#requesting-consent-for-an-entire-tenant)。
## <a name="app-management"></a>应用管理
可以使用 **应用管理** 部分查看标识和软件包详细信息，并管理你的应用的名称。
## <a name="app-identity"></a>应用标识
此页面向你显示了你的应用在应用商店中的唯一标识的相关详细信息，包括用于链接到应用一览的 URL。
有关详细信息，请参阅[查看应用标识详细信息](view-app-identity-details.md)。
## <a name="manage-app-names"></a>管理应用名称
这是查看已为应用保留的所有名称的位置。 你可以从中保留额外名称，或删除将不再使用的名称。
有关详细信息，请参阅[管理应用名称](manage-app-names.md)。
## <a name="current-packages"></a>当前程序包
可以使用此页面查看与所有已发布程序包相关的详细信息。
> [!NOTE]
> 直到你的应用完成发布后，你才会在此处看到信息。
将显示每个程序包的名称、版本和体系结构。 单击 " **详细信息** " 以显示其他信息，如支持的语言、应用功能和文件大小。 所见到的每个程序包的具体信息可能有所不同，具体取决于目标操作系统和其他因素。
具有 OEM 权限的开发人员还可以从 " **当前包** " 页面 [生成预安装包](generate-preinstall-packages-for-oems.md)。
## <a name="wnsmpns"></a>WNS/MPNS
**WNS/MPNS** 部分提供了一些选项，可帮助你创建通知并将通知发送到应用的客户。
> [!TIP]
> 对于 UWP 应用，我们建议使用合作伙伴中心的 **通知** 功能。 此功能可让你将通知发送到你的应用的所有客户，或发送到你的 Windows 10 客户的目标子集，这些客户满足你在 [客户段](create-customer-segments.md)中定义的条件。 有关详细信息，请参阅[将通知发送到应用客户](send-push-notifications-to-your-apps-customers.md)。
你还可以使用以下选项之一，具体取决于你的应用包类型及其特定要求：
- 可使用 **Windows 推送通知服务 (WNS)** 从自己的云服务中发送 Toast、磁贴、锁屏提醒和原始更新。 有关详细信息，请参阅 [Windows 推送通知服务 (WNS) 概述](../design/shell/tiles-and-notifications/windows-push-notification-services--wns--overview.md)。
- 你可以使用 **Microsoft Azure 移动应用** 发送推送通知、验证和管理应用用户，以及将应用数据存储在云中。 有关详细信息，请参阅[“移动应用”文档](/azure/app-service-mobile/)。
- **Microsoft 推送通知服务 (MPNS)** 可与以前发布的用于 Windows Phone 的 .xap 包一起使用。 你可以在此处发送有限数量的未经验证的通知而不进行任何配置，不过为了避免节流限制，我们建议使用经过验证的通知。 如果使用的是 MPNS，则需要将证书上传到 **WNS/MPNS** 页面上提供的字段。 有关详细信息，请参阅[设置经过验证的 Web 服务以发送 Windows Phone 8 的推送通知](/previous-versions/windows/apps/ff941099(v=vs.105))。
| 40.76 | 330 | 0.76472 | yue_Hant | 0.803628 |
ffbe6ea2d2c2a3d658457f011689475b164c4ba4 | 25 | md | Markdown | README.md | Thiernope/Income-Expenses-Tracker | 6e5f30ad804985adef5804079155c721795dff0e | [
"MIT"
] | null | null | null | README.md | Thiernope/Income-Expenses-Tracker | 6e5f30ad804985adef5804079155c721795dff0e | [
"MIT"
] | null | null | null | README.md | Thiernope/Income-Expenses-Tracker | 6e5f30ad804985adef5804079155c721795dff0e | [
"MIT"
] | null | null | null | # Income-Expenses-Tracker | 25 | 25 | 0.84 | yue_Hant | 0.617006 |
ffbefcc3e9e7f04d8d6b01670c2f748d17142f68 | 5,696 | md | Markdown | support/system-center/scom/cannot-deploy-operations-manager-reports.md | v-lenc/SupportArticles-docs | 8660702bf10594d57fb1b0b5b36219b68bef144b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | support/system-center/scom/cannot-deploy-operations-manager-reports.md | v-lenc/SupportArticles-docs | 8660702bf10594d57fb1b0b5b36219b68bef144b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | support/system-center/scom/cannot-deploy-operations-manager-reports.md | v-lenc/SupportArticles-docs | 8660702bf10594d57fb1b0b5b36219b68bef144b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Operations Manager reports fail to deploy
description: Describes an issue in which a DeploymentException error occurs when you deploy Operations Manager reports together with SQL Server Reporting Services.
ms.date: 06/23/2020
ms.prod-support-area-path: Reporting server installation
---
# Operations Manager 2019 and 1807 reports fail to deploy
This article helps you fix an issue in which deploying Operations Manager reports fails with event 31567 in Operations Manager 2019 and version 1807.
_Original product version:_ System Center 2019 Operations Manager, System Center Operations Manager, version 1807
_Original KB number:_ 4519161
## Symptoms
When you install System Center 2019 Operations Manager together with the latest version of SQL Server Reporting Services (SSRS) 2017, Operations Manager reports don't deploy.
When you open the **Reporting** view in the Operations console, and select any of the folders, the list of reports is empty. Additionally, error messages that resemble the following are logged in the Operations Manager event log:
> Log Name: Operations Manager
Source: Health Service Modules
Date: \<Date> \<Time>
Event ID: 31567
Task Category: Data Warehouse
Level: Error
Keywords: Classic
User: N/A
Computer: \<FQDN>
Description:
Failed to deploy reporting component to the SQL Server Reporting Services server. The operation will be retried.
Exception 'DeploymentException': Failed to deploy reports for management pack with version dependent id '\<ID>'. System.Web.Services.Protocols.SoapException: Uploading or saving files with .CustomConfiguration extension is not allowed. Contact your administrator if you have any questions. --->
Microsoft.ReportingServices.Diagnostics.Utilities.ResourceFileFormatNotAllowedException: Uploading or saving files with .CustomConfiguration extension is not allowed. Contact your administrator if you have any questions.
at Microsoft.ReportingServices.Library.ReportingService2005Impl.CreateResource(String Resource, String Parent, Boolean Overwrite, Byte[] Contents, String MimeType, Property[] Properties, Guid batchId)
at Microsoft.ReportingServices.WebServer.ReportingService2005.CreateResource(String Resource, String Parent, Boolean Overwrite, Byte[] Contents, String MimeType, Property[] Properties)
One or more workflows were affected by this.
Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Report
Instance name: Data Warehouse Synchronization Service
Instance ID: {GUID}
Management group: \<Management Group Name>
> [!NOTE]
> This issue also occurs in System Center Operations Manager version 1807 when you upgrade to SSRS 2017, and then you remove and reinstall Operations Manager Reporting.
## Cause
SSRS 2017 version 14.0.600.1274 and later versions include a new advanced setting **AllowedResourceExtensionsForUpload**. This setting restricts the set of extensions of resources files that can be uploaded to the report server. This issue occurs because Operations Manager Reporting uses extensions that aren't included in the default set in **AllowedResourceExtensionsForUpload**.
## Resolution 1
Add \*.\* to the list of extensions. To do this, follow these steps:
1. Start SQL Server Management Studio, and then connect to a report server instance that Operations Manager uses.
2. Right-click the report server name, select **Properties**, and then select **Advanced**.
3. Locate the **AllowedResourceExtensionsForUpload** setting, add \*.\* to the list of extensions, and then select **OK**.
4. Restart SSRS.
## Resolution 2
Use PowerShell script to add the extensions. To do this, run the following PowerShell script:
```powershell
$ExtensionAdd = @(
'CustomConfiguration'
'Report'
'AvailabilityMonitor'
'TopNApplications'
'Settings'
'License'
'ServiceLevelTrackingSummary'
'CustomPerformance'
'MostCommonEvents'
'PerformanceTop'
'Detail'
'DatabaseSettings'
'ServiceLevelObjectiveDetail'
'PerformanceDetail'
'ConfigurationChange'
'TopNErrorGroupsGrowth'
'AvailabilityTime'
'rpdl'
'mp'
'TopNErrorGroups'
'Downtime'
'TopNApplicationsGrowth'
'DisplayStrings'
'Space'
'Override'
'Performance'
'AlertDetail'
'ManagementPackODR'
'AlertsPerDay'
'EventTemplate'
'ManagementGroup'
'Alert'
'EventAnalysis'
'MostCommonAlerts'
'Availability'
'AlertLoggingLatency'
'PerformanceTopInstance'
'rdl'
'PerformanceBySystem'
'InstallUpdateScript'
'PerformanceByUtilization'
'DropScript'
)
Write-Verbose -Message '***'
$Message = 'Step 12 of 12. Allowed Resource Extensions for Upload'
Write-Verbose -Message $Message
$Uri = [System.Uri]"https://$ServiceAddress/ReportServer/ReportService2010.asmx"
$Proxy = New-WebServiceProxy -Uri $Uri -UseDefaultCredential
$Type = $Proxy.GetType().Namespace + '.Property'
$Property = New-Object -TypeName $Type
$Property.Name = 'AllowedResourceExtensionsForUpload'
$Current = $Proxy.GetSystemProperties( $Property )
$ValueCurrent = $Current.Value -split ','
$ValueAdd = $ExtensionAdd | ForEach-Object -Process {
"*.$psItem"
}
$ValueSet = $ValueCurrent + $ValueAdd | Sort-Object -Unique
$Property.Value = $ValueSet -join ','
$Proxy.SetSystemProperties( $Property )
```
> [!NOTE]
> You have to populate the `$ServiceAddress` variable by using a valid address of your report service for HTTPS. If you don't use HTTPS at all, change the script to use HTTP. The list of extensions in the script may not be exhaustive. Include your own extensions as appropriate.
| 40.978417 | 382 | 0.75948 | eng_Latn | 0.807746 |
ffbf9f3f6232131ca75e0e0b7c65945dd689578b | 2,980 | md | Markdown | docs/xamarin-forms/troubleshooting/questions/android-linkassemblies-error.md | muus84/xamarin-docs.de-de | 4e6aac312707b5f1157b21f430101cb34cb78601 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/xamarin-forms/troubleshooting/questions/android-linkassemblies-error.md | muus84/xamarin-docs.de-de | 4e6aac312707b5f1157b21f430101cb34cb78601 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/xamarin-forms/troubleshooting/questions/android-linkassemblies-error.md | muus84/xamarin-docs.de-de | 4e6aac312707b5f1157b21f430101cb34cb78601 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Android-Buildfehler – unerwarteter Fehler der linkassemblyaufgabe
ms.topic: troubleshooting
ms.prod: xamarin
ms.assetid: EB3BE685-CB72-48E3-89D7-C845E76B9FA2
ms.technology: xamarin-forms
author: davidbritch
ms.author: dabritch
ms.date: 03/07/2019
ms.openlocfilehash: 71305dd7287df56036d0298ebfcf8a8cb7c4d3b3
ms.sourcegitcommit: 6264fb540ca1f131328707e295e7259cb10f95fb
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 08/16/2019
ms.locfileid: "69528374"
---
# <a name="android-build-error--the-linkassemblies-task-failed-unexpectedly"></a>Android-Buildfehler – unerwarteter Fehler der linkassemblyaufgabe
Möglicherweise wird eine Fehlermeldung `The "LinkAssemblies" task failed unexpectedly` angezeigt, wenn Sie ein xamarin. Android-Projekt mit Formularen verwenden. Dies geschieht, wenn der Linker aktiv ist (in der Regel auf einem *Releasebuild* , um die Größe des App-Pakets zu verringern). Dies liegt daran, dass die Android-Ziele nicht auf das neueste Framework aktualisiert werden. (Weitere Informationen: [Xamarin. Forms für Android-Anforderungen](~/get-started/requirements.md#android))
Beheben Sie dieses Problem, indem Sie sicherstellen, dass Sie über die neuesten unterstützten Android SDK Versionen verfügen, und legen Sie das **Ziel Framework** auf die neueste installierte Plattform fest. Außerdem wird empfohlen, dass Sie die **Android-Zielversion** auf die neueste installierte Plattform und die **Android-Mindestversion** auf API 19 oder höher festlegen. Dies gilt als die unterstützte Konfiguration.
## <a name="setting-in-visual-studio-for-mac"></a>Festlegen in Visual Studio für Mac
1. Klicken Sie mit der rechten Maustaste auf das Android-Projekt, und wählen Sie im Menü **Optionen** aus.
2. Wechseln Sie im Dialogfeld **Projektoptionen** zu **Build > Allgemein**.
3. Festlegen der **Kompilierung mit der Android-Version: (Ziel Framework)** auf die neueste installierte Plattform.
4. Wechseln Sie im Dialogfeld " **Projektoptionen** " zu **Build > Android-Anwendung**.
5. Legen Sie die **Android-Mindestversion** auf API-Ebene 19 oder höher und die **Android-Zielversion** auf die neueste installierte Plattform fest, die Sie in ausgewählt haben (3).
## <a name="setting-in-visual-studio"></a>Einstellung in Visual Studio
1. Klicken Sie mit der rechten Maustaste auf das Android-Projekt, und wählen Sie im Menü **properies** aus.
2. Wechseln Sie in den Projekteigenschaften zu **Anwendung**.
3. Festlegen der **Kompilierung mit der Android-Version: (Ziel Framework)** auf die neueste installierte Plattform.
4. Wechseln Sie in den Projekteigenschaften zu **Android-Manifest**.
5. Legen Sie die **Android-Mindestversion** auf API-Ebene 19 oder höher und die **Android-Zielversion** auf die neueste installierte Plattform fest, die Sie in ausgewählt haben (3).
Nachdem Sie diese Einstellungen aktualisiert haben, bereinigen Sie das Projekt, und erstellen Sie es neu, um sicherzustellen, dass Ihre Änderungen übernommen werden.
| 74.5 | 489 | 0.794966 | deu_Latn | 0.990857 |
ffbfde4dfc50f10b35b45fa5f7925ca334b04c12 | 21,838 | md | Markdown | website/docs/api/generated/globals.md | sharingcookies/nodegui | 481062423e52779ea7628999b249c1e77f7f2c6b | [
"MIT"
] | 7,857 | 2019-08-12T17:06:12.000Z | 2022-03-31T09:40:05.000Z | website/docs/api/generated/globals.md | sharingcookies/nodegui | 481062423e52779ea7628999b249c1e77f7f2c6b | [
"MIT"
] | 584 | 2019-08-11T21:39:18.000Z | 2022-03-25T23:37:10.000Z | website/docs/api/generated/globals.md | sharingcookies/nodegui | 481062423e52779ea7628999b249c1e77f7f2c6b | [
"MIT"
] | 310 | 2019-08-16T01:40:14.000Z | 2022-03-29T09:45:31.000Z | ---
id: "globals"
title: "@nodegui/nodegui"
sidebar_label: "Globals"
---
## Index
### Enumerations
* [AcceptMode](enums/acceptmode.md)
* [AlignmentFlag](enums/alignmentflag.md)
* [AnchorPoint](enums/anchorpoint.md)
* [ApplicationAttribute](enums/applicationattribute.md)
* [ApplicationState](enums/applicationstate.md)
* [ArrowType](enums/arrowtype.md)
* [AspectRatioMode](enums/aspectratiomode.md)
* [AutoFormattingFlag](enums/autoformattingflag.md)
* [Axis](enums/axis.md)
* [BGMode](enums/bgmode.md)
* [BlurHint](enums/blurhint.md)
* [BrushStyle](enums/brushstyle.md)
* [ButtonPosition](enums/buttonposition.md)
* [ButtonRole](enums/buttonrole.md)
* [ButtonSymbols](enums/buttonsymbols.md)
* [CacheMode](enums/cachemode.md)
* [CaseSensitivity](enums/casesensitivity.md)
* [CheckState](enums/checkstate.md)
* [ChecksumType](enums/checksumtype.md)
* [ClipOperation](enums/clipoperation.md)
* [ColorDialogOption](enums/colordialogoption.md)
* [ComponentFormattingOption](enums/componentformattingoption.md)
* [ConnectionType](enums/connectiontype.md)
* [ContextMenuPolicy](enums/contextmenupolicy.md)
* [CoordinateSystem](enums/coordinatesystem.md)
* [Corner](enums/corner.md)
* [CorrectionMode](enums/correctionmode.md)
* [CursorMoveStyle](enums/cursormovestyle.md)
* [CursorShape](enums/cursorshape.md)
* [DateFormat](enums/dateformat.md)
* [DayOfWeek](enums/dayofweek.md)
* [DialogCode](enums/dialogcode.md)
* [DialogLabel](enums/dialoglabel.md)
* [Direction](enums/direction.md)
* [DockWidgetArea](enums/dockwidgetarea.md)
* [DragDropMode](enums/dragdropmode.md)
* [DropAction](enums/dropaction.md)
* [EchoMode](enums/echomode.md)
* [Edge](enums/edge.md)
* [EditTrigger](enums/edittrigger.md)
* [EnterKeyType](enums/enterkeytype.md)
* [EventPriority](enums/eventpriority.md)
* [FileMode](enums/filemode.md)
* [FillRule](enums/fillrule.md)
* [FindChildOption](enums/findchildoption.md)
* [Flow](enums/flow.md)
* [FocusPolicy](enums/focuspolicy.md)
* [FocusReason](enums/focusreason.md)
* [FontDialogOption](enums/fontdialogoption.md)
* [GestureFlag](enums/gestureflag.md)
* [GestureState](enums/gesturestate.md)
* [GestureType](enums/gesturetype.md)
* [GlobalColor](enums/globalcolor.md)
* [HitTestAccuracy](enums/hittestaccuracy.md)
* [HorizontalHeaderFormat](enums/horizontalheaderformat.md)
* [ImageConversionFlag](enums/imageconversionflag.md)
* [ImageReaderError](enums/imagereadererror.md)
* [InputDialogOptions](enums/inputdialogoptions.md)
* [InputMethodHint](enums/inputmethodhint.md)
* [InputMethodQuery](enums/inputmethodquery.md)
* [InputMode](enums/inputmode.md)
* [InsertPolicy](enums/insertpolicy.md)
* [ItemDataRole](enums/itemdatarole.md)
* [ItemFlag](enums/itemflag.md)
* [ItemSelectionMode](enums/itemselectionmode.md)
* [ItemSelectionOperation](enums/itemselectionoperation.md)
* [Key](enums/key.md)
* [KeyboardModifier](enums/keyboardmodifier.md)
* [LayoutDirection](enums/layoutdirection.md)
* [LayoutMode](enums/layoutmode.md)
* [LineWrapMode](enums/linewrapmode.md)
* [ListViewMode](enums/listviewmode.md)
* [MaskMode](enums/maskmode.md)
* [MatchFlag](enums/matchflag.md)
* [Mode](enums/mode.md)
* [Modifier](enums/modifier.md)
* [MouseButton](enums/mousebutton.md)
* [MouseEventFlag](enums/mouseeventflag.md)
* [MouseEventSource](enums/mouseeventsource.md)
* [Movement](enums/movement.md)
* [MovieState](enums/moviestate.md)
* [NativeGestureType](enums/nativegesturetype.md)
* [NavigationMode](enums/navigationmode.md)
* [Option](enums/option.md)
* [Orientation](enums/orientation.md)
* [ParsingMode](enums/parsingmode.md)
* [PenCapStyle](enums/pencapstyle.md)
* [PenStyle](enums/penstyle.md)
* [PointerType](enums/pointertype.md)
* [QClipboardMode](enums/qclipboardmode.md)
* [QFontCapitalization](enums/qfontcapitalization.md)
* [QFontStretch](enums/qfontstretch.md)
* [QFontWeight](enums/qfontweight.md)
* [QIconMode](enums/qiconmode.md)
* [QIconState](enums/qiconstate.md)
* [QImageFormat](enums/qimageformat.md)
* [QImageInvertMode](enums/qimageinvertmode.md)
* [QMessageBoxIcon](enums/qmessageboxicon.md)
* [QProgressBarDirection](enums/qprogressbardirection.md)
* [QSettingsFormat](enums/qsettingsformat.md)
* [QSettingsScope](enums/qsettingsscope.md)
* [QStylePixelMetric](enums/qstylepixelmetric.md)
* [QSystemTrayIconActivationReason](enums/qsystemtrayiconactivationreason.md)
* [QTextEditLineWrapMode](enums/qtexteditlinewrapmode.md)
* [QTextOptionWrapMode](enums/qtextoptionwrapmode.md)
* [RenderHint](enums/renderhint.md)
* [ResizeMode](enums/resizemode.md)
* [ScreenOrientation](enums/screenorientation.md)
* [ScrollBarPolicy](enums/scrollbarpolicy.md)
* [ScrollHint](enums/scrollhint.md)
* [ScrollMode](enums/scrollmode.md)
* [ScrollPhase](enums/scrollphase.md)
* [SegmentStyle](enums/segmentstyle.md)
* [SelectionBehavior](enums/selectionbehavior.md)
* [SelectionMode](enums/selectionmode.md)
* [SequenceFormat](enums/sequenceformat.md)
* [SequenceMatch](enums/sequencematch.md)
* [Shadow](enums/shadow.md)
* [Shape](enums/shape.md)
* [ShortcutContext](enums/shortcutcontext.md)
* [SizeAdjustPolicy](enums/sizeadjustpolicy.md)
* [SizeConstraint](enums/sizeconstraint.md)
* [SizeHint](enums/sizehint.md)
* [SizeMode](enums/sizemode.md)
* [SliderAction](enums/slideraction.md)
* [SortOrder](enums/sortorder.md)
* [StepType](enums/steptype.md)
* [SystemFont](enums/systemfont.md)
* [TabBarShape](enums/tabbarshape.md)
* [TabFocusBehavior](enums/tabfocusbehavior.md)
* [TabPosition](enums/tabposition.md)
* [TabletDevice](enums/tabletdevice.md)
* [TextElideMode](enums/textelidemode.md)
* [TextFlag](enums/textflag.md)
* [TextFormat](enums/textformat.md)
* [TextInteractionFlag](enums/textinteractionflag.md)
* [TickPosition](enums/tickposition.md)
* [TileRule](enums/tilerule.md)
* [TimeSpec](enums/timespec.md)
* [TimerType](enums/timertype.md)
* [ToolBarArea](enums/toolbararea.md)
* [ToolButtonPopupMode](enums/toolbuttonpopupmode.md)
* [ToolButtonStyle](enums/toolbuttonstyle.md)
* [TouchPointState](enums/touchpointstate.md)
* [TransformationMode](enums/transformationmode.md)
* [UIEffect](enums/uieffect.md)
* [UrlFormattingOption](enums/urlformattingoption.md)
* [UserInputResolutionOption](enums/userinputresolutionoption.md)
* [VerticalHeaderFormat](enums/verticalheaderformat.md)
* [ViewMode](enums/viewmode.md)
* [WhiteSpaceMode](enums/whitespacemode.md)
* [WidgetAttribute](enums/widgetattribute.md)
* [WidgetEventTypes](enums/widgeteventtypes.md)
* [WindowFrameSection](enums/windowframesection.md)
* [WindowModality](enums/windowmodality.md)
* [WindowState](enums/windowstate.md)
* [WindowType](enums/windowtype.md)
* [WrapMode](enums/wrapmode.md)
* [WritingSystem](enums/writingsystem.md)
### Classes
* [Component](classes/component.md)
* [EventWidget](classes/eventwidget.md)
* [FlexLayout](classes/flexlayout.md)
* [NodeDateTimeEdit](classes/nodedatetimeedit.md)
* [NodeDialog](classes/nodedialog.md)
* [NodeFrame](classes/nodeframe.md)
* [NodeLayout](classes/nodelayout.md)
* [NodeListView](classes/nodelistview.md)
* [NodeObject](classes/nodeobject.md)
* [NodeTableView](classes/nodetableview.md)
* [NodeTextEdit](classes/nodetextedit.md)
* [NodeWidget](classes/nodewidget.md)
* [QAbstractButton](classes/qabstractbutton.md)
* [QAbstractItemView](classes/qabstractitemview.md)
* [QAbstractScrollArea](classes/qabstractscrollarea.md)
* [QAbstractSlider](classes/qabstractslider.md)
* [QAbstractSpinBox](classes/qabstractspinbox.md)
* [QAction](classes/qaction.md)
* [QApplication](classes/qapplication.md)
* [QBoxLayout](classes/qboxlayout.md)
* [QBrush](classes/qbrush.md)
* [QButtonGroup](classes/qbuttongroup.md)
* [QCalendarWidget](classes/qcalendarwidget.md)
* [QCheckBox](classes/qcheckbox.md)
* [QClipboard](classes/qclipboard.md)
* [QColor](classes/qcolor.md)
* [QColorDialog](classes/qcolordialog.md)
* [QComboBox](classes/qcombobox.md)
* [QCursor](classes/qcursor.md)
* [QDate](classes/qdate.md)
* [QDateEdit](classes/qdateedit.md)
* [QDateTime](classes/qdatetime.md)
* [QDateTimeEdit](classes/qdatetimeedit.md)
* [QDesktopWidget](classes/qdesktopwidget.md)
* [QDial](classes/qdial.md)
* [QDialog](classes/qdialog.md)
* [QDoubleSpinBox](classes/qdoublespinbox.md)
* [QDrag](classes/qdrag.md)
* [QDragLeaveEvent](classes/qdragleaveevent.md)
* [QDragMoveEvent](classes/qdragmoveevent.md)
* [QDropEvent](classes/qdropevent.md)
* [QErrorMessage](classes/qerrormessage.md)
* [QEvent](classes/qevent.md)
* [QFileDialog](classes/qfiledialog.md)
* [QFont](classes/qfont.md)
* [QFontDatabase](classes/qfontdatabase.md)
* [QFontDialog](classes/qfontdialog.md)
* [QFontMetrics](classes/qfontmetrics.md)
* [QFrame](classes/qframe.md)
* [QGraphicsBlurEffect](classes/qgraphicsblureffect.md)
* [QGraphicsDropShadowEffect](classes/qgraphicsdropshadoweffect.md)
* [QGraphicsEffect](classes/qgraphicseffect.md)
* [QGridLayout](classes/qgridlayout.md)
* [QGroupBox](classes/qgroupbox.md)
* [QIcon](classes/qicon.md)
* [QImage](classes/qimage.md)
* [QInputDialog](classes/qinputdialog.md)
* [QKeyEvent](classes/qkeyevent.md)
* [QKeySequence](classes/qkeysequence.md)
* [QLCDNumber](classes/qlcdnumber.md)
* [QLabel](classes/qlabel.md)
* [QLineEdit](classes/qlineedit.md)
* [QListView](classes/qlistview.md)
* [QListWidget](classes/qlistwidget.md)
* [QListWidgetItem](classes/qlistwidgetitem.md)
* [QMainWindow](classes/qmainwindow.md)
* [QMenu](classes/qmenu.md)
* [QMenuBar](classes/qmenubar.md)
* [QMessageBox](classes/qmessagebox.md)
* [QMimeData](classes/qmimedata.md)
* [QModelIndex](classes/qmodelindex.md)
* [QMouseEvent](classes/qmouseevent.md)
* [QMovie](classes/qmovie.md)
* [QNativeGestureEvent](classes/qnativegestureevent.md)
* [QObject](classes/qobject.md)
* [QPaintEvent](classes/qpaintevent.md)
* [QPainter](classes/qpainter.md)
* [QPainterPath](classes/qpainterpath.md)
* [QPen](classes/qpen.md)
* [QPicture](classes/qpicture.md)
* [QPixmap](classes/qpixmap.md)
* [QPlainTextEdit](classes/qplaintextedit.md)
* [QPoint](classes/qpoint.md)
* [QPointF](classes/qpointf.md)
* [QProgressBar](classes/qprogressbar.md)
* [QProgressDialog](classes/qprogressdialog.md)
* [QPushButton](classes/qpushbutton.md)
* [QRadioButton](classes/qradiobutton.md)
* [QRect](classes/qrect.md)
* [QRectF](classes/qrectf.md)
* [QScrollArea](classes/qscrollarea.md)
* [QScrollBar](classes/qscrollbar.md)
* [QSettings](classes/qsettings.md)
* [QShortcut](classes/qshortcut.md)
* [QSize](classes/qsize.md)
* [QSlider](classes/qslider.md)
* [QSpinBox](classes/qspinbox.md)
* [QStackedWidget](classes/qstackedwidget.md)
* [QStandardItem](classes/qstandarditem.md)
* [QStandardItemModel](classes/qstandarditemmodel.md)
* [QStatusBar](classes/qstatusbar.md)
* [QStyle](classes/qstyle.md)
* [QSvgWidget](classes/qsvgwidget.md)
* [QSystemTrayIcon](classes/qsystemtrayicon.md)
* [QTabBar](classes/qtabbar.md)
* [QTabWidget](classes/qtabwidget.md)
* [QTableView](classes/qtableview.md)
* [QTableWidget](classes/qtablewidget.md)
* [QTableWidgetItem](classes/qtablewidgetitem.md)
* [QTabletEvent](classes/qtabletevent.md)
* [QTextBrowser](classes/qtextbrowser.md)
* [QTextEdit](classes/qtextedit.md)
* [QTime](classes/qtime.md)
* [QTimeEdit](classes/qtimeedit.md)
* [QToolButton](classes/qtoolbutton.md)
* [QTreeWidget](classes/qtreewidget.md)
* [QTreeWidgetItem](classes/qtreewidgetitem.md)
* [QUrl](classes/qurl.md)
* [QVariant](classes/qvariant.md)
* [QWheelEvent](classes/qwheelevent.md)
* [QWidget](classes/qwidget.md)
* [StyleSheet](classes/stylesheet.md)
* [YogaWidget](classes/yogawidget.md)
### Interfaces
* [Margins](interfaces/margins.md)
* [QAbstractButtonSignals](interfaces/qabstractbuttonsignals.md)
* [QAbstractItemViewSignals](interfaces/qabstractitemviewsignals.md)
* [QAbstractSliderSignals](interfaces/qabstractslidersignals.md)
* [QAbstractSpinBoxSignals](interfaces/qabstractspinboxsignals.md)
* [QActionSignals](interfaces/qactionsignals.md)
* [QApplicationSignals](interfaces/qapplicationsignals.md)
* [QButtonGroupSignals](interfaces/qbuttongroupsignals.md)
* [QCalendarWidgetSignals](interfaces/qcalendarwidgetsignals.md)
* [QCheckBoxSignals](interfaces/qcheckboxsignals.md)
* [QColorDialogSignals](interfaces/qcolordialogsignals.md)
* [QComboBoxSignals](interfaces/qcomboboxsignals.md)
* [QDateTimeEditSignals](interfaces/qdatetimeeditsignals.md)
* [QDialogSignals](interfaces/qdialogsignals.md)
* [QDoubleSpinBoxSignals](interfaces/qdoublespinboxsignals.md)
* [QFileDialogSignals](interfaces/qfiledialogsignals.md)
* [QFontDialogSignals](interfaces/qfontdialogsignals.md)
* [QGraphicsBlurEffectSignals](interfaces/qgraphicsblureffectsignals.md)
* [QGraphicsDropShadowEffectSignals](interfaces/qgraphicsdropshadoweffectsignals.md)
* [QGraphicsEffectSignals](interfaces/qgraphicseffectsignals.md)
* [QGroupBoxSignals](interfaces/qgroupboxsignals.md)
* [QInputDialogSignals](interfaces/qinputdialogsignals.md)
* [QLCDNumberSignals](interfaces/qlcdnumbersignals.md)
* [QLabelSignals](interfaces/qlabelsignals.md)
* [QLineEditSignals](interfaces/qlineeditsignals.md)
* [QListWidgetSignals](interfaces/qlistwidgetsignals.md)
* [QMenuSignals](interfaces/qmenusignals.md)
* [QMessageBoxSignals](interfaces/qmessageboxsignals.md)
* [QMovieSignals](interfaces/qmoviesignals.md)
* [QObjectSignals](interfaces/qobjectsignals.md)
* [QPlainTextEditSignals](interfaces/qplaintexteditsignals.md)
* [QProgressBarSignals](interfaces/qprogressbarsignals.md)
* [QProgressDialogSignals](interfaces/qprogressdialogsignals.md)
* [QShortcutSignals](interfaces/qshortcutsignals.md)
* [QSpinBoxSignals](interfaces/qspinboxsignals.md)
* [QStackedWidgetSignals](interfaces/qstackedwidgetsignals.md)
* [QStandardItemModelSignals](interfaces/qstandarditemmodelsignals.md)
* [QStatusBarSignals](interfaces/qstatusbarsignals.md)
* [QSystemTrayIconSignals](interfaces/qsystemtrayiconsignals.md)
* [QTabBarSignals](interfaces/qtabbarsignals.md)
* [QTabWidgetSignals](interfaces/qtabwidgetsignals.md)
* [QTableWidgetSignals](interfaces/qtablewidgetsignals.md)
* [QTextBrowserSignals](interfaces/qtextbrowsersignals.md)
* [QTextEditSignals](interfaces/qtexteditsignals.md)
* [QToolButtonSignals](interfaces/qtoolbuttonsignals.md)
* [QTreeWidgetSignals](interfaces/qtreewidgetsignals.md)
* [QWidgetSignals](interfaces/qwidgetsignals.md)
* [Range](interfaces/range.md)
### Type aliases
* [FlexLayoutSignals](globals.md#flexlayoutsignals)
* [FlexNode](globals.md#flexnode)
* [ImageFormats](globals.md#imageformats)
* [NativeElement](globals.md#nativeelement)
* [NativeRawPointer](globals.md#nativerawpointer)
* [QAbstractScrollAreaSignals](globals.md#qabstractscrollareasignals)
* [QBoxLayoutSignals](globals.md#qboxlayoutsignals)
* [QDesktopWidgetSignals](globals.md#qdesktopwidgetsignals)
* [QDialSignals](globals.md#qdialsignals)
* [QErrorMessageSignals](globals.md#qerrormessagesignals)
* [QFrameSignals](globals.md#qframesignals)
* [QGridLayoutSignals](globals.md#qgridlayoutsignals)
* [QLayoutSignals](globals.md#qlayoutsignals)
* [QListViewSignals](globals.md#qlistviewsignals)
* [QMainWindowSignals](globals.md#qmainwindowsignals)
* [QMenuBarSignals](globals.md#qmenubarsignals)
* [QPushButtonSignals](globals.md#qpushbuttonsignals)
* [QRadioButtonSignals](globals.md#qradiobuttonsignals)
* [QScrollAreaSignals](globals.md#qscrollareasignals)
* [QScrollBarSignals](globals.md#qscrollbarsignals)
* [QSliderSignals](globals.md#qslidersignals)
* [QTableViewSignals](globals.md#qtableviewsignals)
* [QVariantType](globals.md#qvarianttype)
* [SupportedFormats](globals.md#supportedformats)
### Variables
* [addon](globals.md#const-addon)
* [outer](globals.md#const-outer)
* [scrollArea](globals.md#const-scrollarea)
* [sview](globals.md#const-sview)
* [testImagePath](globals.md#const-testimagepath)
* [textView](globals.md#const-textview)
* [win](globals.md#const-win)
### Functions
* [addDefaultErrorHandler](globals.md#adddefaulterrorhandler)
* [checkIfNapiExternal](globals.md#checkifnapiexternal)
* [checkIfNativeElement](globals.md#checkifnativeelement)
* [createTreeWidget](globals.md#createtreewidget)
* [main](globals.md#main)
* [noop](globals.md#noop)
* [prepareInlineStyleSheet](globals.md#prepareinlinestylesheet)
* [wrapWithActivateUvLoop](globals.md#wrapwithactivateuvloop)
## Type aliases
### FlexLayoutSignals
Ƭ **FlexLayoutSignals**: *[QLayoutSignals](globals.md#qlayoutsignals)*
___
### FlexNode
Ƭ **FlexNode**: *[NativeRawPointer](globals.md#nativerawpointer)‹"YGNodeRef"›*
___
### ImageFormats
Ƭ **ImageFormats**: *"BMP" | "GIF" | "JPG" | "JPEG" | "PNG" | "PBM" | "PGM" | "PPM" | "XBM" | "XPM" | "SVG"*
___
### NativeElement
Ƭ **NativeElement**: *object*
#### Type declaration:
* \[ **key**: *string*\]: any
* **type**: *"native"*
___
### NativeRawPointer
Ƭ **NativeRawPointer**: *Record‹T, unknown›*
___
### QAbstractScrollAreaSignals
Ƭ **QAbstractScrollAreaSignals**: *[QFrameSignals](globals.md#qframesignals)*
___
### QBoxLayoutSignals
Ƭ **QBoxLayoutSignals**: *[QLayoutSignals](globals.md#qlayoutsignals)*
___
### QDesktopWidgetSignals
Ƭ **QDesktopWidgetSignals**: *[QWidgetSignals](interfaces/qwidgetsignals.md)*
> QDesktopWidget is a class that provides access to screen information on multi-head systems..
**This class is a JS wrapper around Qt's [QDesktopWidget Class](https://doc.qt.io/qt-5/qdesktopwidget.html)**
The QDesktopWidget class provides information about the user's desktop, such as its total size, number of screens, the geometry of each screen, and whether they are configured as separate desktops or a single virtual desktop.
### Example
```js
const { QDesktopWidget } = require("@nodegui/nodegui");
const desktop = new QDesktopWidget();
const availableGeometry = desktop.availableGeometry();
const screenGeometry = desktop.screenGeometry();
console.log(availableGeometry.width() + 'x' + availableGeometry.height());
console.log(screenGeometry.width() + 'x' + screenGeometry.height());
console.log(desktop.screenNumber());
```
___
### QDialSignals
Ƭ **QDialSignals**: *[QAbstractSliderSignals](interfaces/qabstractslidersignals.md)*
___
### QErrorMessageSignals
Ƭ **QErrorMessageSignals**: *[QDialogSignals](interfaces/qdialogsignals.md)*
___
### QFrameSignals
Ƭ **QFrameSignals**: *[QWidgetSignals](interfaces/qwidgetsignals.md)*
___
### QGridLayoutSignals
Ƭ **QGridLayoutSignals**: *[QLayoutSignals](globals.md#qlayoutsignals)*
___
### QLayoutSignals
Ƭ **QLayoutSignals**: *[QObjectSignals](interfaces/qobjectsignals.md)*
___
### QListViewSignals
Ƭ **QListViewSignals**: *[QAbstractItemViewSignals](interfaces/qabstractitemviewsignals.md)*
___
### QMainWindowSignals
Ƭ **QMainWindowSignals**: *[QWidgetSignals](interfaces/qwidgetsignals.md)*
___
### QMenuBarSignals
Ƭ **QMenuBarSignals**: *[QWidgetSignals](interfaces/qwidgetsignals.md)*
___
### QPushButtonSignals
Ƭ **QPushButtonSignals**: *[QAbstractButtonSignals](interfaces/qabstractbuttonsignals.md)*
___
### QRadioButtonSignals
Ƭ **QRadioButtonSignals**: *[QAbstractButtonSignals](interfaces/qabstractbuttonsignals.md)*
___
### QScrollAreaSignals
Ƭ **QScrollAreaSignals**: *[QAbstractScrollAreaSignals](globals.md#qabstractscrollareasignals)*
___
### QScrollBarSignals
Ƭ **QScrollBarSignals**: *[QAbstractSliderSignals](interfaces/qabstractslidersignals.md)*
___
### QSliderSignals
Ƭ **QSliderSignals**: *[QAbstractSliderSignals](interfaces/qabstractslidersignals.md)*
___
### QTableViewSignals
Ƭ **QTableViewSignals**: *[QAbstractItemViewSignals](interfaces/qabstractitemviewsignals.md)*
___
### QVariantType
Ƭ **QVariantType**: *[NativeElement](globals.md#nativeelement) | string | number | boolean*
___
### SupportedFormats
Ƭ **SupportedFormats**: *"gif" | "webp"*
## Variables
### `Const` addon
• **addon**: *any* = require('../../../build/Release/nodegui_core.node')
___
### `Const` outer
• **outer**: *[QWidget](classes/qwidget.md)‹›* = new QWidget()
___
### `Const` scrollArea
• **scrollArea**: *[QScrollArea](classes/qscrollarea.md)‹›* = new QScrollArea()
___
### `Const` sview
• **sview**: *[QWidget](classes/qwidget.md)‹›* = new QWidget()
___
### `Const` testImagePath
• **testImagePath**: *string* = path.resolve(__dirname, 'assets', 'nodegui.png')
___
### `Const` textView
• **textView**: *[QLabel](classes/qlabel.md)‹›* = new QLabel()
___
### `Const` win
• **win**: *[QMainWindow](classes/qmainwindow.md)‹›* = new QMainWindow()
## Functions
### addDefaultErrorHandler
▸ **addDefaultErrorHandler**(`native`: [NativeElement](globals.md#nativeelement), `emitter`: EventEmitter): *void*
**Parameters:**
Name | Type |
------ | ------ |
`native` | [NativeElement](globals.md#nativeelement) |
`emitter` | EventEmitter |
**Returns:** *void*
___
### checkIfNapiExternal
▸ **checkIfNapiExternal**(`arg`: any): *boolean*
**Parameters:**
Name | Type |
------ | ------ |
`arg` | any |
**Returns:** *boolean*
___
### checkIfNativeElement
▸ **checkIfNativeElement**(`arg`: any): *boolean*
**Parameters:**
Name | Type |
------ | ------ |
`arg` | any |
**Returns:** *boolean*
___
### createTreeWidget
▸ **createTreeWidget**(): *[QTreeWidget](classes/qtreewidget.md)*
**Returns:** *[QTreeWidget](classes/qtreewidget.md)*
___
### main
▸ **main**(): *void*
**Returns:** *void*
___
### noop
▸ **noop**(): *void*
**Returns:** *void*
___
### prepareInlineStyleSheet
▸ **prepareInlineStyleSheet**‹**Signals**›(`widget`: [NodeWidget](classes/nodewidget.md)‹Signals›, `rawStyle`: string): *string*
**Type parameters:**
▪ **Signals**: *[QWidgetSignals](interfaces/qwidgetsignals.md)*
**Parameters:**
Name | Type |
------ | ------ |
`widget` | [NodeWidget](classes/nodewidget.md)‹Signals› |
`rawStyle` | string |
**Returns:** *string*
___
### wrapWithActivateUvLoop
▸ **wrapWithActivateUvLoop**‹**T**›(`func`: T): *T*
**Type parameters:**
▪ **T**: *Function*
**Parameters:**
Name | Type |
------ | ------ |
`func` | T |
**Returns:** *T*
| 30.757746 | 225 | 0.761929 | yue_Hant | 0.291714 |
ffc0187a8dfc820df7494a4a4ca84e1569a0c6f8 | 4,870 | md | Markdown | posts/Vic.md | mudasobwa/meme-me-ru | b6be12f3b9a7db57f560a5e22981ff3984bd3ce1 | [
"MIT"
] | null | null | null | posts/Vic.md | mudasobwa/meme-me-ru | b6be12f3b9a7db57f560a5e22981ff3984bd3ce1 | [
"MIT"
] | null | null | null | posts/Vic.md | mudasobwa/meme-me-ru | b6be12f3b9a7db57f560a5e22981ff3984bd3ce1 | [
"MIT"
] | null | null | null | ---
title: 'Vic'
date: '2014-10-18 12:00'
tags: [Reisen, España]
categories: Photos
---
<div class='preview'><img src='{{urls.media}}/VicOK.jpg' alt='Vic'></div>
<a id='9dc8f477ce675c33506a67bc373ceb90-600'></a>
<a id='655b675525e838f8b9bb4620691c8499-600'></a>
<a id='ea8a9dd8e57d601540b9e590c4bf4c78-600'></a>
<a id='0aaa407be06b1defe9f432af13c8f625-600'></a>
<a id='a74a790320cae156cfe0c599e7fc3640-600'></a>
<a id='250655058481885c655b94caf7787918-600'></a>
<a id='6ac5ec0ba1de9ce87db59888e590636f-600'></a>
<a id='86852d310af6389fd95065d3df0f2fcd-600'></a>
<a id='907942a20f63d44f41c7f051063ac727-600'></a>
<a id='dc5d32e54298ec9c9ae8eab5c3a677a7-600'></a>
<a id='8df389e18291636a50077c044d925f2e-600'></a>
<a id='b5bef2c4939bff2a94c22bee249be4a0-600'></a>
<a id='740cfd81e603a0dddaebf97851b7bc5b-600'></a>
<a id='d610e7d71820860abcf05142f1c20bd7-600'></a>
<a id='bbf4b532a5339d7ed9b08b2777e39bc6-600'></a>
<a id='d05ae10b899ccc2ec3d88e4f63326fe5-600'></a>
<a id='8016981d6479ee25ee8a8d86e4ac8428-600'></a>
<a id='62954ae36d49fc13c1a24c8de79ab114-600'></a>
<a id='70e7963b3c64bd5f835363abeb9ab20e-600'></a>
<a id='8796fac96d450304c1230dead2fb68f1-600'></a>
<a id='ed84675156be8897876e92dcdc4cb761-600'></a>
<a id='25530ecdfb3d0f33314db9abd36ee098-600'></a>
<a id='2667a02bd5431b8eb5a26602521f606b-600'></a>
<a id='bb7a03d43200eb91d368c7da0f4a14eb-600'></a>
<a id='e064d4498d7d593520d8d9739d8d86d3-600'></a>
<a id='85337d123deba3211cf955065dfc8400-600'></a>
<a id='1a381b8b3cb3d3b310c00e572b5cf67e-600'></a>
<a id='afe7f6b99f06abdc574c30d154cb51dd-600'></a>
<a id='b53f539698fe9c93b295159d6fe19201-600'></a>
<a id='c43b7b4fdf3bde43a348afe747b92e9c-600'></a>
<a id='f7c909f6aee6afe5bc333f3203ebdcf5-600'></a>
<a id='8dbc080f7f9fc006657d3ed7927e11d0-600'></a>
| 66.712329 | 205 | 0.77269 | yue_Hant | 0.096787 |
ffc01b1c96b3afe82d24e887cf9b83fbbdf4183a | 236 | md | Markdown | README.md | microprediction/nflMarkov | ec9ebaf98d760c3bb06b13bd14ef608d3cd7685a | [
"BSD-2-Clause"
] | null | null | null | README.md | microprediction/nflMarkov | ec9ebaf98d760c3bb06b13bd14ef608d3cd7685a | [
"BSD-2-Clause"
] | null | null | null | README.md | microprediction/nflMarkov | ec9ebaf98d760c3bb06b13bd14ef608d3cd7685a | [
"BSD-2-Clause"
] | 2 | 2021-04-18T00:38:34.000Z | 2021-12-19T16:03:02.000Z | nflMarkov
=========
Some code to use Markov chains to analyze (American) football.
The code is described in some detail in the blog post,
https://fivetwentyone.wordpress.com/2014/08/02/nfl-markov-5-of-n-nflmarkov-the-python-code/
| 21.454545 | 91 | 0.741525 | eng_Latn | 0.878072 |
ffc0bbc0e618a86486b5600c5c056da570b8c33b | 166 | md | Markdown | plugins/com.marksandspencer.code-analysis/1.0.7.md | gradle-plugins/gradle-plugins.github.io | 98542184c9519c124d0ae94e8ff3038dbe124e8c | [
"Apache-2.0"
] | 1 | 2018-10-16T08:57:08.000Z | 2018-10-16T08:57:08.000Z | plugins/com.marksandspencer.code-analysis/1.0.7.md | gradle-plugins/gradle-plugins.github.io | 98542184c9519c124d0ae94e8ff3038dbe124e8c | [
"Apache-2.0"
] | null | null | null | plugins/com.marksandspencer.code-analysis/1.0.7.md | gradle-plugins/gradle-plugins.github.io | 98542184c9519c124d0ae94e8ff3038dbe124e8c | [
"Apache-2.0"
] | null | null | null | ---
layout: plugin
pluginId: com.marksandspencer.code-analysis
jarSha1: 0c68d3ad2e303e88c6fe73f520165f3bbab808eb
isJarAvailable: true
error: NONE
violations: []
---
| 16.6 | 49 | 0.807229 | kor_Hang | 0.139909 |
b96ff0164602ffaea014cb4e9ae47e58935f5ee8 | 420 | md | Markdown | docfiles/cljs.repl/source.md | grav/api | ad9dbef61d551a06b2c55b5aa54e6194a1af8c0b | [
"MIT"
] | 129 | 2015-06-28T13:24:40.000Z | 2016-06-22T03:16:04.000Z | docfiles/cljs.repl/source.md | grav/api | ad9dbef61d551a06b2c55b5aa54e6194a1af8c0b | [
"MIT"
] | 79 | 2015-05-17T05:13:31.000Z | 2015-06-25T15:52:49.000Z | docfiles/cljs.repl/source.md | grav/api | ad9dbef61d551a06b2c55b5aa54e6194a1af8c0b | [
"MIT"
] | 17 | 2016-12-16T04:32:28.000Z | 2020-09-25T18:59:28.000Z | ---
name: cljs.repl/source
see also:
- cljs.repl/doc
---
## Summary
## Details
Prints the source code for the given symbol `name`, if it can find it. This
requires that the symbol resolve to a Var defined in a namespace for which the
.cljs is in the classpath.
## Examples
```clj
(source comment)
;; Prints:
;; (defmacro comment
;; "Ignores body, yields nil"
;; {:added "1.0"}
;; [& body])
;;
;;=> nil
```
| 15.555556 | 78 | 0.642857 | eng_Latn | 0.994524 |
b9702b6cf44d305b330115c4638d186d56accb2b | 2,236 | md | Markdown | readme/README-ja.md | myothiha09/box-android-share-sdk | 13a789de25000338352f0efbfbda5794ccb44476 | [
"Apache-2.0"
] | 6 | 2015-08-13T21:38:25.000Z | 2021-05-10T00:07:36.000Z | readme/README-ja.md | doncung/box-android-share-sdk | 35a0f6e9b3ee747bae92d6a9c49ea7e816c25d26 | [
"Apache-2.0"
] | 172 | 2015-04-23T21:45:53.000Z | 2021-02-01T22:57:42.000Z | readme/README-ja.md | doncung/box-android-share-sdk | 35a0f6e9b3ee747bae92d6a9c49ea7e816c25d26 | [
"Apache-2.0"
] | 17 | 2015-04-30T05:27:09.000Z | 2022-03-01T09:33:02.000Z | Box Android Share SDK
==============
このSDKを使用すると、Box上の共有リンクやコラボレータの管理が簡単にできるようになります。
####共有リンク
<img src="https://cloud.box.com/shared/static/cvdtf4475mf39r47s066de79ukpwlwwv.png" width="200"/>
<img src="https://cloud.box.com/shared/static/gqi9a9xzucjd9u9vkmf1zzwulbvnlbki.png" width="200"/>
<img src="https://cloud.box.com/shared/static/xh0n3ewuk1s68o9x8z195fgknqj41ij3.png" width="200"/>
####コラボレータ
<img src="https://cloud.box.com/shared/static/855dkoj2nyk1obtiqpc2k5dr1o85tpp9.png" width="200"/>
<img src="https://cloud.box.com/shared/static/pz3ujyihzwd7du9bqtrn5cqveg5pzdqo.png" width="200"/>
<img src="https://cloud.box.com/shared/static/7r90gmo7zq3q4zs5otjvi0bf4s1ya01g.png" width="200"/>
開発者向け設定
--------------
このSDKは、maven dependencyとして追加するか、プロジェクト内にソースを複製するか、 GitHubのリリースページからコンパイル済みのJARの1つをダウンロードすることで入手できます。
このSDKには次のような依存性があり、プロジェクトに含まれている必要があります:
* [minimal-json v0.9.1](https://github.com/ralfstx/minimal-json) (maven: `com.eclipsesource.minimal-json:minimal-json:0.9.1`)
* [box-content-sdk](https://github.com/box/box-android-content-sdk) (maven: `coming soon`)
クイックスタート
--------------
[box-content-sdk](https://github.com/box/box-android-content-sdk)のBoxItemおよびBoxSessionが必要です。その他の詳細については、box-content-sdkの文書を参照してください。
```java
BoxSession session = new BoxSession(MainActivity.this);
BoxFolder folder = new BoxApiFolder(session).getInfo("<FOLDER_ID>").send();
```
####ファイルまたはフォルダの共有リンク
項目の共有リンクを管理するには、次の処理を実行してください。
```java
startActivity(BoxSharedLinkActivity.getLaunchIntent((MainActivity.this, folder, session));
```
この処理を実行すると、(特定のファイルまたはフォルダの) 共有リンクの設定をすべて管理できるようになります (パスワード制限、権限、有効期限、アクセスレベルなど) 。
####フォルダのコラボレータ
フォルダのコラボレータを管理するには、次の処理を開始してください。
```java
startActivity(BoxCollaborationsActivity.getLaunchIntent(MainActivity.this, folder, session));
```
この処理を実行すると、特定のフォルダへのユーザーアクセスや権限を管理できるようになります。
サンプルのアプリケーション
--------------
サンプルのアプリケーションは、[box-share-sample](../../tree/master/box-share-sample)フォルダ内にあります。
Copyright and License
---------------------
Copyright 2015 Box, Inc. All rights reserved.
Licensed under the Box Terms of Service; you may not use this file except in compliance with the License.
You may obtain a copy of the License at https://www.box.com/legal/termsofservice/
| 39.928571 | 132 | 0.763864 | yue_Hant | 0.557777 |
b9703d12439cdf7e51c223f0752fa881f15fd576 | 757 | md | Markdown | README.md | deljus/ReactUI | 15f116857a254e53e7af20c106a5b178f8da62e0 | [
"MIT"
] | null | null | null | README.md | deljus/ReactUI | 15f116857a254e53e7af20c106a5b178f8da62e0 | [
"MIT"
] | null | null | null | README.md | deljus/ReactUI | 15f116857a254e53e7af20c106a5b178f8da62e0 | [
"MIT"
] | null | null | null | This project for site [cimm.kpfu.ru](https://cimm.kpfu.ru)
The project is divided into 3 independent modules:
- Predictor module
- Search module
- Database form module
Clone the application and run the following commands
```
cd MWUI/ReactUI
npm install
```
## Predictor module
To start the application, run the command
```
npm start-predictor
```
To build the application, run the command
```
npm build-predictor
```
## Search module
To start the application, run the command
```
npm start-search
```
To build the application, run the command
```
npm build-search
```
## Database form module
To start the application, run the command
```
npm start-dbform
```
To build the application, run the command
```
npm build-dbform
```
## License
MIT
| 13.517857 | 58 | 0.722589 | eng_Latn | 0.954443 |
b970598f162f50eb6b054c1345674b3e509a0b31 | 2,455 | md | Markdown | docs/_wdio-ywinappdriver-service.md | Abhi6722/hackers-hub-website | cd8b362856bb3e6ec83582a094988ad7906a5292 | [
"MIT"
] | 4 | 2021-11-29T11:58:59.000Z | 2021-11-29T15:41:57.000Z | docs/_wdio-ywinappdriver-service.md | Abhi6722/hackers-hub-website | cd8b362856bb3e6ec83582a094988ad7906a5292 | [
"MIT"
] | 20 | 2021-11-29T11:47:24.000Z | 2021-11-29T14:40:20.000Z | docs/_wdio-ywinappdriver-service.md | Abhi6722/hackers-hub-website | cd8b362856bb3e6ec83582a094988ad7906a5292 | [
"MIT"
] | 1 | 2021-11-29T10:36:42.000Z | 2021-11-29T10:36:42.000Z | ---
id: wdio-ywinappdriver-service
title: ywinappdriver Service
custom_edit_url: https://github.com/licanhua/wdio-ywinappdriver-service/edit/main//README.md
---
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
> wdio-ywinappdriver-service is a 3rd party package, for more information please see [GitHub](https://github.com/licanhua/wdio-ywinappdriver-service) | [npm](https://www.npmjs.com/package/wdio-ywinappdriver-service)
This service helps you to run the ywinappdriver server seamlessly when running tests with the [WDIO testrunner](https://webdriver.io/guide/testrunner/gettingstarted.html). It starts the [ywinappdriver](https://github.com/licanhua/YWinAppDriver) in a child process.
## Installation
```bash
npm install wdio-ywinappdriver-service --save-dev
```
Instructions on how to install `WebdriverIO` can be found [here.](https://webdriver.io/docs/gettingstarted.html)
## Configuration
In order to use the service you need to add `ywinappdriver` to your service array:
```js
// wdio.conf.js
export.config = {
// ...
services: ['ywinappdriver'],
// ...
};
```
## Options
The following options can be added to the wdio.conf.js file. To define options for the service you need to add the service to the `services` list in the following way:
```js
// wdio.conf.js
export.config = {
// ...
services: [
['ywinappdriver', {
// ywinappdriver service options here
// ...
}]
],
// ...
};
```
### logPath
Path where all logs from the ywinappdriver server should be stored.
Type: `String`
Example:
```js
export.config = {
// ...
services: [
['ywinappdriver', {
logPath : './'
}]
],
// ...
}
```
### command
To use your own installation of winappdriver, e.g. globally installed, specify the command which should be started.
Type: `String`
Example:
```js
export.config = {
// ...
services: [
['ywinappdriver', {
command : 'c:\\xx\\ywinappdriver.exe'
}]
],
// ...
}
```
### args
List of arguments passed directly to `ywinappdriver`.
See [the documentation](https://github.com/licanhua/ywinappdriver) for possible arguments.
Type: `Array`
Default: `[]`
Example:
```js
export.config = {
// ...
services: [
['ywinappdriver', {
args: ['--urls' 'http://127.0.0.1:4723' '--basepath' '/wd/hub']
}]
],
// ...
}
```
| 21.163793 | 264 | 0.638289 | eng_Latn | 0.737488 |
b970aa482dbf5ad5c6bdc0ad2a7fc86c48fa8a4e | 4,520 | md | Markdown | _posts/2016-3-22-iphone-as-ros-camera-node.md | riematrix/riematrix.github.io | 2c25eb39eb6f630fdb437df3070afa2d20d2bb41 | [
"MIT"
] | null | null | null | _posts/2016-3-22-iphone-as-ros-camera-node.md | riematrix/riematrix.github.io | 2c25eb39eb6f630fdb437df3070afa2d20d2bb41 | [
"MIT"
] | null | null | null | _posts/2016-3-22-iphone-as-ros-camera-node.md | riematrix/riematrix.github.io | 2c25eb39eb6f630fdb437df3070afa2d20d2bb41 | [
"MIT"
] | null | null | null | ---
layout: post
title: Turn your iphone into a ros camera node under ubuntu
description: Detail on turning iphone into ros camera node under ubuntu 14.04 with v4l2, Gstreamer and video_stream_opencv.
---
Durning the last four weeks i was exploring some monocular SLAM projects. At first i use my laptop's own camera as a image sensor, which is not good enough for capturing high quality pictures. Also, the camera and the screen are on the same side so it's quite inconvenient to monitoring those SLAM systems with live video input.
I have a DC and an ihpone at hand so i decide to turn them into separate or wireless sensors for my laptop. In this post i'll focus on the approch of iphone(maybe ipad, too) unter ubuntu 14.04. The basic idea came from [this thread](http://ubuntuforums.org/showthread.php?t=2092935)
**1. Make your iphone as a webcam**
It's not so easy to do this under linux especially when you don't have a customized app for camera video streaming on ios. I use [Mini WebCam](http://itunes.apple.com/cn/app/mini-webcam/id379896463?mt=8) to run on my iphone as a live video server. It's free and easy to use.
Open Mini WebCam on your iphone and press the start button. It will then stream of videos to your WLAN which can be simply accessed via browsers. Make sure your iphone and PC are in the same WLAN. You can check the video stream via web browser on ubuntu. Just type the address displayed on iphone into your Firefox's address bar. If you see the live video in your browser then you are done.
**2. Create virtual video devices via v4l2loopback for Ubuntu**
In this step we will create a virtual video devices "/dev/video*" for ros from the live video we created. We need a kernel module called [v4l2loopback](https://github.com/umlaeute/v4l2loopback.git) to create V4L2 loopback devices. You may install it via apt:
sudo apt-get install v4l2loopback-dkms
or from source:
sudo su
git clone https://github.com/umlaeute/v4l2loopback.git
cd v4l2loopback
make && make install
However, the apt-get method may fail durning install and i didn't figure out why (Acturally i checked the log and found that the error occurs when executing 'make', some wranings were treated as errors. Not sure if it's a compiler compatibility issue.).
When the install finished, load the module by executing:
sudo modprobe v4l2loopback
To check the virtual device you've created, run:
v4l2-ctl --list-devices
The output will display your new device for example(* is your device index):
Dummy video device (0x0000) (platform:v4l2loopback-000):
/dev/video*
**3. Use Gstreamer to create a v4l2 video source from your iphone live video**
Run the command below to feed the live video data to your virtual device:
gst-launch souphttpsrc location=http://`<ip>`[:`<port>`]/ ! jpegdec ! ffmpegcolorspace ! v4l2sink device=/dev/video*
(ip/port should be replaces with your own address and * should be replaced with your own index from step 2). [More sample usages of Gstreamer](http://wiki.oz9aec.net/index.php/Gstreamer_cheat_sheet)
**4. Create a ros node from this device**
I use the ros package [video_stream_opencv](wiki.ros.org/video_stream_opencv) to create a camera node from the device. Install this ros package, cd into it's /launch dirctory and make a copy of webcam.launch, (e.g. mywebcam.launch). Edit your launch file and modify the "video_stream_provider" value to your device index and save. Now you may launch the file from ros:
roslaunch video_stream_opencv mywebcam.launch
By default the launch file will start a image view node so you will see a small window display the video from your iphone. If you don't see the video playing try to check your rostopic and see if the image topic exist(e.g. /webcam/image_raw)
There is another impressive way which use epoccam on iphone and [epoccam_linux](https://github.com/ohwgiles/epoccam_linux.git) as driver on ubuntu. epoccam_linux use tray icons which is not enabled by default on ubuntu 14.04. So you may need [a few more steps](http://askubuntu.com/questions/456950/system-tray-icons-disappeared-after-installing-ubuntu-14-04) to get it working. Unfortunatly i didn't figure out how to get the video stream from epoccam driver, cause i'm new to C. It would be very easy for you guys who are familiar with this language. The driver provides two video size: 1280x720(H264 30fps) and 640x480(H264 30fps). It also has a automatic connection feature in WLAN. Anyway, worth trying.
| 65.507246 | 708 | 0.770133 | eng_Latn | 0.993304 |
b970c03eff216d992d4f139c9efb139f18366b9e | 1,303 | md | Markdown | services/svc/filestorage/README.md | rickrain/azure-sdk-for-rust | cca3d9f84e3e813fc9fed842cffa09e6b1ef3ad4 | [
"MIT"
] | null | null | null | services/svc/filestorage/README.md | rickrain/azure-sdk-for-rust | cca3d9f84e3e813fc9fed842cffa09e6b1ef3ad4 | [
"MIT"
] | 4 | 2022-01-11T18:52:32.000Z | 2022-03-02T21:17:54.000Z | services/svc/filestorage/README.md | johnbatty/azure-sdk-for-rust | 5fda503f134e6eb09d03a43a43abe86a4db4c855 | [
"MIT"
] | 1 | 2022-03-24T08:52:01.000Z | 2022-03-24T08:52:01.000Z | # azure_svc_filestorage crate
This is a generated [Azure SDK for Rust](https://github.com/Azure/azure-sdk-for-rust) crate from the Azure REST API specifications listed in:
https://github.com/Azure/azure-rest-api-specs/blob/main/specification/storage/data-plane/Microsoft.FileStorage/readme.md
To get started with these generated service crates, see the [examples](https://github.com/Azure/azure-sdk-for-rust/blob/main/services/README.md#examples).
The default tag is `package-2021-06`.
The following [tags](https://github.com/Azure/azure-sdk-for-rust/blob/main/services/tags.md) are available:
- `package-2021-06` has 47 operations from 1 API versions: `2021-06-08`. Use crate feature `package-2021-06` to enable. The operations will be in the `package_2021_06` module.
- `package-2021-04` has 47 operations from 1 API versions: `2021-04-10`. Use crate feature `package-2021-04` to enable. The operations will be in the `package_2021_04` module.
- `package-2021-02` has 45 operations from 1 API versions: `2021-02-12`. Use crate feature `package-2021-02` to enable. The operations will be in the `package_2021_02` module.
- `package-2020-10` has 45 operations from 1 API versions: `2020-10-02`. Use crate feature `package-2020-10` to enable. The operations will be in the `package_2020_10` module. | 81.4375 | 175 | 0.771297 | eng_Latn | 0.912159 |
b97117895005709d1b4c755e50e6e56d85a64b83 | 2,406 | md | Markdown | vendor/inetprocess/libsugarcrm/CHANGELOG.md | kenbrill/sugarcli-plus | 2b2e5b2feadbf46250ba8a10c4564326f221cc58 | [
"Apache-2.0"
] | null | null | null | vendor/inetprocess/libsugarcrm/CHANGELOG.md | kenbrill/sugarcli-plus | 2b2e5b2feadbf46250ba8a10c4564326f221cc58 | [
"Apache-2.0"
] | null | null | null | vendor/inetprocess/libsugarcrm/CHANGELOG.md | kenbrill/sugarcli-plus | 2b2e5b2feadbf46250ba8a10c4564326f221cc58 | [
"Apache-2.0"
] | null | null | null | Changelog
=========
1.2.3
-----
* Bug when getting the list of hooks: we had only one hook per weight because the array key was the weight
1.2.2
-----
* Added getDB() in Bean
* Check if the custom table exists (because sugar returns the name without checking)
1.2.1
-----
* Added "update_date_modified" in bean in case we want to force the date_modified
1.2.0
-----
* Out of beta \o/
* Install performs offline without a web server
1.1.22-beta
-----
* Fix warning and output on System::repair
1.1.21-beta
-----
* Add more functions for specific Repair and Rebuild
* Tests improved
1.1.20-beta
-----
* Fix tests for Repair and Rebuild
1.1.19-beta
-----
* Fix issue where email address would not be retrieved in `UsersManager`.
1.1.14-beta -> 1.1.18-beta
-----
* Button with capitalized letters was not found in MetadataParser
* Some hardcoded fields in SugarCRM were not detectable in vardefs
* If the entrypoint is loaded again with the same path, now return the same instance
* Add deleteBean + corrected entrypoint to reload the current user
* Remove useless constant and load current user when get entry point
* Lot of new Unit Tests
* Corrected sugarPath
* Invalid attribute makes a change in bean
* Moved method updateBeanFieldsFromCurrentUser in Bean.php
* Corrected a bug with searchBeans and getList that doesn't retrieve more than 40 records
* Added Relationship Diff
* Added exceptions when we can't retrieve the module table
1.1.13-beta
-----
* New class MetadataParser to add / remove buttons via SugarCRM Modulebuilder parser
* New Util to remove a Label
1.1.12-beta
-----
* New methods in System to Disable Activities (speeds up some tasks)
1.1.11-beta
-----
* Change the license from GPL to Apache 2.0
1.1.10-beta
-----
* Bean.php: Utility function to convert to array values.
1.1.9-beta
-----
* LangFileCleaner: Merge global and local version of variables.
* Quick Repair: Fix issue with Sugar7 record.php files not cleared.
1.0.0
-----
* Add UsersManager class.
* Reworked Bean::updateBean
0.9.1
-----
* Protect column identifiers in INSERT and UPDATE queries with QueryFactory
0.9.0
-----
* Add LangFileCleaner class to sort and clean SugarCRM language files and make it easier for VCS
* Add Installer class to extract and install sugar from a zip file.
* Add SugarPDO to connect to sugarcrm database with php PDO
* Add Metadata class to manage `field_meta_data` table.
| 26.152174 | 106 | 0.738986 | eng_Latn | 0.976363 |
b97150102195f249408af5dc5b9d51fe608f301d | 1,047 | md | Markdown | content/talk/talk-41/talk-41.md | SharadaSrinivasan/1WCwebsite | bb0945075f14cc8fbeed246ebd4bbe6a3cb95e02 | [
"MIT"
] | null | null | null | content/talk/talk-41/talk-41.md | SharadaSrinivasan/1WCwebsite | bb0945075f14cc8fbeed246ebd4bbe6a3cb95e02 | [
"MIT"
] | null | null | null | content/talk/talk-41/talk-41.md | SharadaSrinivasan/1WCwebsite | bb0945075f14cc8fbeed246ebd4bbe6a3cb95e02 | [
"MIT"
] | null | null | null | ---
title: ICTDX 2019
event: ICTDX 2019
event_url:
location: Ahmedabad
summary: Sharada Srinivasan attended ICTD X to present a poster on chat applications in telemedicine, based on her fieldwork with the Vanuatu Inter-island Telemedicine and Learning Project.
# Talk start and end times.
# End time can optionally be hidden by prefixing the line with `#`.
date: "2019-01-05"
date_end: "2019-01-08"
all_day: true
authors: []
tags: []
# Is this a featured talk? (true/false)
featured: false
links:
url_video: ""
# Projects (optional).
# Associate this post with one or more of your projects.
# Simply enter your project's folder or file name without extension.
# E.g. `projects = ["internal-project"]` references `content/project/deep-learning/index.md`.
# Otherwise, set `projects = []`.
projects: []
# Enable math on this page?
math: true
---
Sharada Srinivasan presented a poster titled "Chat Applications for Telemedicine" drawing upon her fieldwork in Vanuatu on the Vanuatu Inter-island telemedicine and learning project.
| 28.297297 | 189 | 0.746896 | eng_Latn | 0.988896 |
b9717f5aef9055d384e17516cfd72a7657d2c433 | 443 | md | Markdown | docs/Faithlife.Build/DotNetBuild/GetBuildSummaryArg.md | ddunkin/FaithlifeBuild | a37e31f01f9cd86f4f501d932107c180c65a7310 | [
"MIT"
] | 3 | 2019-07-15T10:06:36.000Z | 2020-08-26T18:39:37.000Z | docs/Faithlife.Build/DotNetBuild/GetBuildSummaryArg.md | ddunkin/FaithlifeBuild | a37e31f01f9cd86f4f501d932107c180c65a7310 | [
"MIT"
] | 23 | 2020-02-29T20:37:20.000Z | 2021-09-02T15:26:59.000Z | docs/Faithlife.Build/DotNetBuild/GetBuildSummaryArg.md | ddunkin/FaithlifeBuild | a37e31f01f9cd86f4f501d932107c180c65a7310 | [
"MIT"
] | 8 | 2019-07-15T09:07:13.000Z | 2021-06-21T19:04:32.000Z | # DotNetBuild.GetBuildSummaryArg method
Gets the argument that specifies whether a build summary should be output.
```csharp
public static string GetBuildSummaryArg(this DotNetBuildSettings settings)
```
## See Also
* class [DotNetBuildSettings](../DotNetBuildSettings.md)
* class [DotNetBuild](../DotNetBuild.md)
* namespace [Faithlife.Build](../../Faithlife.Build.md)
<!-- DO NOT EDIT: generated by xmldocmd for Faithlife.Build.dll -->
| 27.6875 | 74 | 0.76298 | yue_Hant | 0.500092 |
b971d58de1b11af8568b3ea2620ee01a084d3ca5 | 1,202 | md | Markdown | apiproxies/jsforce-sfdc-oauth-nodejs-express-app/README.md | mpramod16/apigee-tutorials | 3774501ca30db871c375b7fe62f32ff1bdecc6c4 | [
"MIT"
] | 55 | 2015-01-28T23:09:40.000Z | 2021-12-23T03:52:51.000Z | apiproxies/jsforce-sfdc-oauth-nodejs-express-app/README.md | brualves/apigee-tutorials | 4bd97cfe1294c24bb536667a70ec9d1cffa32e5d | [
"MIT"
] | 4 | 2016-04-14T14:46:35.000Z | 2021-08-04T16:22:59.000Z | apiproxies/jsforce-sfdc-oauth-nodejs-express-app/README.md | brualves/apigee-tutorials | 4bd97cfe1294c24bb536667a70ec9d1cffa32e5d | [
"MIT"
] | 68 | 2015-06-29T22:54:04.000Z | 2022-01-23T17:26:35.000Z | jsforce-sfdc-oauth-nodejs-express-app
======================================
Example of three-legged oauth with SalesForce leveraging jsforce Node.js module, express, and Apigee.
#### Configuration
Replace app.js with SFDC credentials
```javascript
var sforce_credentials = {
clientId: process.env.clientId || 'REPLACE_WITH_SFDC_CLIENT_ID',
clientSecret: process.env.clientSecret || 'REPLACE_WITH_SFDC_CLIENT_SECRET',
redirectUri: process.env.redirectUri || 'REPLACE_WITH_SFDC_REDIRECT_URI'
}
```
#### Run locally
```bash
$ npm install
$ npm start
```
**use `clientId={clientId} clientSecret={clientSecret} redirectUri={redirectUri} npm start`**
Go to: http://localhost:3000/oauth/auth
#### Run on Apigee
##### Deploy
```bash
$ apigeetool deploynodeapp -n jsforce-oauth-express-nodejs-app -d . -m app.js -o testmyapi -e test -b /jsforce-oauth-express-nodejs-app -u $ae_username -p $ae_password -V
```
Go to:
https://testmyapi-test.apigee.net/jsforce-oauth-express-nodejs-app/oauth/auth
**Uncomment sections to use Apigee Vault to store clientId, clientSecret, and redirectUri.** | 30.05 | 170 | 0.735441 | kor_Hang | 0.364638 |
b9722948f743b1000e6a0d6fe91ca95fa97a666f | 98 | md | Markdown | phpfreelancemanager/readme.md | kadnan/LxD | aa6818ce10f4c5b6d91bb4decc083571a895bb1b | [
"MIT"
] | null | null | null | phpfreelancemanager/readme.md | kadnan/LxD | aa6818ce10f4c5b6d91bb4decc083571a895bb1b | [
"MIT"
] | null | null | null | phpfreelancemanager/readme.md | kadnan/LxD | aa6818ce10f4c5b6d91bb4decc083571a895bb1b | [
"MIT"
] | null | null | null | ## PHP Freelance Manager
A Simple Clients and Project Management tool written in PHP Laravel 5
| 16.333333 | 69 | 0.785714 | eng_Latn | 0.979918 |
b97234c5c41c7f5204637b378523692f403da287 | 2,789 | md | Markdown | Markdown/01000s/05000/don suffer.md | rcvd/interconnected-markdown | 730d63c55f5c868ce17739fd7503d562d563ffc4 | [
"MIT"
] | 2 | 2022-01-19T09:04:58.000Z | 2022-01-23T15:44:37.000Z | Markdown/00500s/05000/don suffer.md | rcvd/interconnected-markdown | 730d63c55f5c868ce17739fd7503d562d563ffc4 | [
"MIT"
] | null | null | null | Markdown/00500s/05000/don suffer.md | rcvd/interconnected-markdown | 730d63c55f5c868ce17739fd7503d562d563ffc4 | [
"MIT"
] | 1 | 2022-01-09T17:10:33.000Z | 2022-01-09T17:10:33.000Z | -
- Suppose first comparison type not sex. Now of pretended old is interested. With Solomon of man we that. Beard have bell the first him.
- There dreams unarmed felt shot of. The were she how room. Good may the be servant of opportunity the. Rich [[storm victory]] is first and thrown the. Children every for king had the. His all these be get quick. From mind the organized in the he. And this would six blockquote gains on the. And of laws at five clearly.
- Disciple of popularity absent thing the contain.
- And the the of i him. Window to i utter which. Very dry confined the she more the. Great were exclaimed there just got statement. Out children was tore himself him knew. Heard eyed was and also. That before return pulled were. Until blind or i Greece. Our her entity or of foolish on it. Or brook them to awful him. And of very pray hour. Rule aware before mind delicate.
- Beset seem attain sweet held train. Of being by buried [[rode]]. And the ever an she had in. Adequate for and first court in remains and. The head joined [[constant farther]]. The not not to by was bliss know. Torture i deserving mournful that opinion. Costs lest repentance far it day. Sweet up simple of still and i. His and [[flesh rode]] moment ever by. The now when must bench in this. But the to or taxation. Next must be seem servants. Comfortably came blushing then evening. From everywhere soon due in. An had to better to same woman. Simultaneously in lead prison mind horse minutes. Etc into he multitude it of that. In will ground the ravine for. Are the of round slept. The would made in was [[suffer carrying]]. The the own fire actor other. Cord prayer this audience heard light i. Ours inhabitants make the was exactly. They than such and were with.
- An room rouse Hampshire women i. Sorrows tea from proved geographical. Opposite [[dressed slow]] the far rescued as. With of twelve with to gorge not whose. Standing the my the life. Of improvements suddenly the trusting lips. Did of falling from 6th the. Minute in the this not [[suffer noise]] as. But those of haughty strike could. Army the i and in the. Be Columbus horses bed defective on human. Dan breast allowed complete and then. Bring [[literature informed]] himself carved best most wondering their. And the eighth he of away. Arabian store creature and she well i were. You occur at fair her. Want agreed water directly he formats to. To that go miles oil and ours. There light himself meal ritual. Can churches away could will you in. Relation in their in everywhere double nursery. Had was given and being give one dear then. The at writing is of. Pages petty to solid had as. And my neck knot looked law. With of own at to priests Anna is. His whole phrases world sort. Letter he come arms it thus statements.
- | 348.625 | 1,027 | 0.77232 | eng_Latn | 0.999928 |
b972b60ee71ab6c38337472bc24bb7f53ffb3522 | 1,972 | md | Markdown | components/menu/README.md | dovidio/barista | 352490ad3ee034e21a7330b995a66a90ac399a00 | [
"Apache-2.0"
] | null | null | null | components/menu/README.md | dovidio/barista | 352490ad3ee034e21a7330b995a66a90ac399a00 | [
"Apache-2.0"
] | null | null | null | components/menu/README.md | dovidio/barista | 352490ad3ee034e21a7330b995a66a90ac399a00 | [
"Apache-2.0"
] | null | null | null | # Menu
The `<dt-menu>` is a generic navigation menu that supports item groups as well
as individual items that do not belong to a group. It has a clear hierarchy and
allows for a condensed way to help users to navigate or perform actions. It can
be used as a standalone component, in a `<dt-drawer>` or in a
`<dt-context-dialog>`.
<ba-live-example name="DtExampleMenuDefault"></ba-live-example>
## Imports
You have to import the `DtMenuModule` when you want to use the `<dt-menu>`.
```typescript
@NgModule({
imports: [DtMenuModule],
})
class MyModule {}
```
## Initialization
To set the content for a menu component, the following tags are available:
- `<dt-menu-group>` - A menu group with a label that can contain one or more
menu items.
- `<a dtMenuItem>`/`<button dtMenuItem>` - A menu item which can either be
represented by an anchor (if the item is used for site navigation) or a button
(in case the item should merely trigger some code).
## DtMenu inputs
| Name | Type | Default | Description |
| ---------- | -------- | ----------- | ------------------------------------------- |
| aria-label | `string` | `undefined` | An accessibility label describing the menu. |
To make our components accessible it is obligatory to provide either an
`aria-label` or `aria-labelledby`.
## DtMenuGroup inputs
| Name | Type | Default | Description |
| ----- | ------ | ----------- | ----------------------------- |
| label | string | `undefined` | The header of the menu group. |
## Menu in use
This component is typically used for static menus, such as the global navigation
menu in combination with a [drawer](/components/drawer) or menus in overlays
(e.g. user menu, or [context dialog](/components/context-dialog)).
<ba-live-example name="DtExampleMenuWithinDrawer" fullwidth="true"></ba-live-example>
<ba-live-example name="DtExampleMenuWithinContextDialog"></ba-live-example>
| 35.214286 | 85 | 0.653651 | eng_Latn | 0.990127 |
b9730c23f7a85ceda5a20b10ee839a6efb3b471b | 748 | md | Markdown | Problemset/magic-index-lcci/README.md | KivenCkl/LeetCode | fcc97c66f8154a5d20c2aca86120cb37b9d2d83d | [
"MIT"
] | 7 | 2019-05-08T03:41:05.000Z | 2020-12-22T12:39:43.000Z | Problemset/magic-index-lcci/README.md | Singularity0909/LeetCode | d46fb1c8ed9b16339d46d5c37f69d44e5c178954 | [
"MIT"
] | 1 | 2021-07-19T03:48:35.000Z | 2021-07-19T03:48:35.000Z | Problemset/magic-index-lcci/README.md | KivenCkl/LeetCode | fcc97c66f8154a5d20c2aca86120cb37b9d2d83d | [
"MIT"
] | 7 | 2019-05-10T20:43:20.000Z | 2021-02-22T03:47:35.000Z |
| [English](README_EN.md) | 简体中文 |
# [面试题 08.03. 魔术索引](https://leetcode-cn.com/problems/magic-index-lcci/)
## 题目描述
<p>魔术索引。 在数组<code>A[0...n-1]</code>中，有所谓的魔术索引，满足条件<code>A[i] = i</code>。给定一个有序整数数组，编写一种方法找出魔术索引，若有的话，在数组A中找出一个魔术索引，如果没有，则返回-1。若有多个魔术索引，返回索引值最小的一个。</p>
<p><strong>示例1:</strong></p>
<pre><strong> 输入</strong>：nums = [0, 2, 3, 4, 5]
<strong> 输出</strong>：0
<strong> 说明</strong>: 0下标的元素为0
</pre>
<p><strong>示例2:</strong></p>
<pre><strong> 输入</strong>：nums = [1, 1, 1]
<strong> 输出</strong>：1
</pre>
<p><strong>说明:</strong></p>
<ol>
<li>nums长度在[1, 1000000]之间</li>
<li>此题为原书中的 Follow-up，即数组中可能包含重复元素的版本</li>
</ol>
## 相关话题
- [数组](https://leetcode-cn.com/tag/array)
- [二分查找](https://leetcode-cn.com/tag/binary-search)
## 相似题目
| 19.179487 | 150 | 0.637701 | yue_Hant | 0.34365 |
b97599c47a3d157265c4f00e5a84e250a223fcca | 34 | md | Markdown | README.md | SyKingW/XQAppVersionManager | 157cb49a2c26e6de8b9e8391b6bdeee29d1132c2 | [
"MIT"
] | null | null | null | README.md | SyKingW/XQAppVersionManager | 157cb49a2c26e6de8b9e8391b6bdeee29d1132c2 | [
"MIT"
] | null | null | null | README.md | SyKingW/XQAppVersionManager | 157cb49a2c26e6de8b9e8391b6bdeee29d1132c2 | [
"MIT"
] | null | null | null | # XQAppVersionManager
进行App一些版本请求
| 11.333333 | 21 | 0.882353 | deu_Latn | 0.459705 |
b9764ba0b00dd061b1282910004e50d3c6b1b087 | 14,234 | markdown | Markdown | README.markdown | seangoedecke/redcarpet | 2357f9a1c8aaa230d21f7be274636e8829632d18 | [
"MIT"
] | 2,695 | 2015-01-01T08:28:40.000Z | 2022-03-28T19:29:56.000Z | README.markdown | seangoedecke/redcarpet | 2357f9a1c8aaa230d21f7be274636e8829632d18 | [
"MIT"
] | 327 | 2015-01-01T14:18:32.000Z | 2022-03-21T12:16:26.000Z | README.markdown | seangoedecke/redcarpet | 2357f9a1c8aaa230d21f7be274636e8829632d18 | [
"MIT"
] | 386 | 2015-01-13T18:31:20.000Z | 2022-03-25T16:14:18.000Z | Redcarpet is written with sugar, spice and everything nice
============================================================
[](https://travis-ci.org/vmg/redcarpet)
[](https://www.codetriage.com/vmg/redcarpet)
[](https://badge.fury.io/rb/redcarpet)
Redcarpet is a Ruby library for Markdown processing that smells like
butterflies and popcorn.
This library is written by people
---------------------------------
Redcarpet was written by [Vicent Martí](https://github.com/vmg). It is maintained by
[Robin Dupret](https://github.com/robin850) and [Matt Rogers](https://github.com/mattr-).
Redcarpet would not be possible without the [Sundown](https://www.github.com/vmg/sundown)
library and its authors (Natacha Porté, Vicent Martí, and its many awesome contributors).
You can totally install it as a Gem
-----------------------------------
Redcarpet is readily available as a Ruby gem. It will build some native
extensions, but the parser is standalone and requires no installed libraries.
Starting with Redcarpet 3.0, the minimum required Ruby version is 1.9.2 (or Rubinius in 1.9 mode).
$ [sudo] gem install redcarpet
If you need to use it with Ruby 1.8.7, you will have to stick with 2.3.0:
$ [sudo] gem install redcarpet -v 2.3.0
The Redcarpet source is available at GitHub:
$ git clone git://github.com/vmg/redcarpet.git
And it's like *really* simple to use
------------------------------------
The core of the Redcarpet library is the `Redcarpet::Markdown` class. Each
instance of the class is attached to a `Renderer` object; the Markdown class
performs parsing of a document and uses the attached renderer to generate
output.
The `Redcarpet::Markdown` object is encouraged to be instantiated once with the
required settings, and reused between parses.
~~~~ ruby
# Initializes a Markdown parser
markdown = Redcarpet::Markdown.new(renderer, extensions = {})
~~~~
Here, the `renderer` variable refers to a renderer object, inheriting
from `Redcarpet::Render::Base`. If the given object has not been
instantiated, the library will do it with default arguments.
Rendering with the `Markdown` object is done through `Markdown#render`.
Unlike in the RedCloth API, the text to render is passed as an argument
and not stored inside the `Markdown` instance, to encourage reusability.
Example:
~~~~ ruby
markdown.render("This is *bongos*, indeed.")
# => "<p>This is <em>bongos</em>, indeed.</p>"
~~~~
You can also specify a hash containing the Markdown extensions which the
parser will identify. The following extensions are accepted:
* `:no_intra_emphasis`: do not parse emphasis inside of words.
Strings such as `foo_bar_baz` will not generate `<em>` tags.
* `:tables`: parse tables, PHP-Markdown style.
* `:fenced_code_blocks`: parse fenced code blocks, PHP-Markdown
style. Blocks delimited with 3 or more `~` or backticks will be considered
as code, without the need to be indented. An optional language name may
be added at the end of the opening fence for the code block.
* `:autolink`: parse links even when they are not enclosed in `<>`
characters. Autolinks for the http, https and ftp protocols will be
automatically detected. Email addresses and http links without protocol,
but starting with `www` are also handled.
* `:disable_indented_code_blocks`: do not parse usual markdown
code blocks. Markdown converts text with four spaces at
the front of each line to code blocks. This option
prevents it from doing so. Recommended to use
with `fenced_code_blocks: true`.
* `:strikethrough`: parse strikethrough, PHP-Markdown style.
Two `~` characters mark the start of a strikethrough,
e.g. `this is ~~good~~ bad`.
* `:lax_spacing`: HTML blocks do not require to be surrounded by an
empty line as in the Markdown standard.
* `:space_after_headers`: A space is always required between the hash
at the beginning of a header and its name, e.g. `#this is my header`
would not be a valid header.
* `:superscript`: parse superscripts after the `^` character; contiguous superscripts
are nested together, and complex values can be enclosed in parenthesis, e.g.
`this is the 2^(nd) time`.
* `:underline`: parse underscored emphasis as underlines.
`This is _underlined_ but this is still *italic*`.
* `:highlight`: parse highlights.
`This is ==highlighted==`. It looks like this: `<mark>highlighted</mark>`
* `:quote`: parse quotes.
`This is a "quote"`. It looks like this: `<q>quote</q>`
* `:footnotes`: parse footnotes, PHP-Markdown style. A footnote works very much
like a reference-style link: it consists of a marker next to the text (e.g.
`This is a sentence.[^1]`) and a footnote definition on its own line anywhere
within the document (e.g. `[^1]: This is a footnote.`).
Example:
~~~~ ruby
markdown = Redcarpet::Markdown.new(Redcarpet::Render::HTML, autolink: true, tables: true)
~~~~
Darling, I packed you a couple renderers for lunch
--------------------------------------------------
Redcarpet comes with two built-in renderers, `Redcarpet::Render::HTML` and
`Redcarpet::Render::XHTML`, which output HTML and XHTML, respectively. These
renderers are actually implemented in C and hence offer brilliant
performance — several degrees of magnitude faster than other Ruby Markdown
solutions.
All the rendering flags that previously applied only to HTML output have
now been moved to the `Redcarpet::Render::HTML` class, and may be enabled when
instantiating the renderer:
~~~~ ruby
Redcarpet::Render::HTML.new(render_options = {})
~~~~
Initializes an HTML renderer. The following flags are available:
* `:filter_html`: do not allow any user-inputted HTML in the output.
* `:no_images`: do not generate any `<img>` tags.
* `:no_links`: do not generate any `<a>` tags.
* `:no_styles`: do not generate any `<style>` tags.
* `:escape_html`: escape any HTML tags. This option has precedence over
`:no_styles`, `:no_links`, `:no_images` and `:filter_html` which means
that any existing tag will be escaped instead of being removed.
* `:safe_links_only`: only generate links for protocols which are considered
safe.
* `:with_toc_data`: add HTML anchors to each header in the output HTML,
to allow linking to each section.
* `:hard_wrap`: insert HTML `<br>` tags inside paragraphs where the original
Markdown document had newlines (by default, Markdown ignores these newlines).
* `:xhtml`: output XHTML-conformant tags. This option is always enabled in the
`Render::XHTML` renderer.
* `:prettify`: add prettyprint classes to `<code>` tags for google-code-prettify.
* `:link_attributes`: hash of extra attributes to add to links.
Example:
~~~~ ruby
renderer = Redcarpet::Render::HTML.new(no_links: true, hard_wrap: true)
~~~~
The `HTML` renderer has an alternate version, `Redcarpet::Render::HTML_TOC`,
which will output a table of contents in HTML based on the headers of the
Markdown document.
When instantiating this render object, you can optionally pass a `nesting_level`
option which takes an integer or a range and allows you to make it render only
headers at certain levels.
Redcarpet also includes a plaintext renderer, `Redcarpet::Render::StripDown`, that
strips out all the formatting:
~~~~ ruby
require 'redcarpet'
require 'redcarpet/render_strip'
markdown = Redcarpet::Markdown.new(Redcarpet::Render::StripDown)
markdown.render("**This** _is_ an [example](http://example.org/).")
# => "This is an example (http://example.org/)."
~~~~
And you can even cook your own
------------------------------
Custom renderers are created by inheriting from an existing renderer. The
built-in renderers, `HTML` and `XHTML` may be extended as such:
~~~~ ruby
# Create a custom renderer that sets a custom class for block-quotes.
class CustomRender < Redcarpet::Render::HTML
def block_quote(quote)
%(<blockquote class="my-custom-class">#{quote}</blockquote>)
end
end
markdown = Redcarpet::Markdown.new(CustomRender, fenced_code_blocks: true)
~~~~
But new renderers can also be created from scratch by extending the abstract
base class `Redcarpet::Render::Base` (see `lib/redcarpet/render_man.rb` for
an example implementation of a Manpage renderer):
~~~~ ruby
class ManPage < Redcarpet::Render::Base
# you get the drill -- keep going from here
end
~~~~
The following instance methods may be implemented by the renderer:
### Block-level calls
If the return value of the method is `nil`, the block will be skipped.
Therefore, make sure that your renderer has at least a `paragraph` method
implemented. If the method for a document element is not implemented, the
block will be skipped.
Example:
~~~~ ruby
class RenderWithoutCode < Redcarpet::Render::HTML
def block_code(code, language)
nil
end
end
~~~~
* block_code(code, language)
* block_quote(quote)
* block_html(raw_html)
* footnotes(content)
* footnote_def(content, number)
* header(text, header_level)
* hrule()
* list(contents, list_type)
* list_item(text, list_type)
* paragraph(text)
* table(header, body)
* table_row(content)
* table_cell(content, alignment, header)
### Span-level calls
A return value of `nil` will not output any data. If the method for
a document element is not implemented, the contents of the span will
be copied verbatim:
* autolink(link, link_type)
* codespan(code)
* double_emphasis(text)
* emphasis(text)
* image(link, title, alt_text)
* linebreak()
* link(link, title, content)
* raw_html(raw_html)
* triple_emphasis(text)
* strikethrough(text)
* superscript(text)
* underline(text)
* highlight(text)
* quote(text)
* footnote_ref(number)
**Note**: When overriding a renderer's method, be sure to return a HTML
element with a level that matches the level of that method (e.g. return a
block element when overriding a block-level callback). Otherwise, the output
may be unexpected.
### Low level rendering
* entity(text)
* normal_text(text)
### Header of the document
Rendered before any another elements:
* doc_header()
### Footer of the document
Rendered after all the other elements:
* doc_footer()
### Pre/post-process
Special callback: preprocess or postprocess the whole document before
or after the rendering process begins:
* preprocess(full_document)
* postprocess(full_document)
You can look at
["How to extend the Redcarpet 2 Markdown library?"](https://web.archive.org/web/20170505231254/http://dev.af83.com/2012/02/27/howto-extend-the-redcarpet2-markdown-lib.html)
for some more explanations.
Also, now our Pants are much smarter
------------------------------------
Redcarpet 2 comes with a standalone [SmartyPants](
http://daringfireball.net/projects/smartypants/) implementation. It is fully
compliant with the original implementation. It is the fastest SmartyPants
parser there is, with a difference of several orders of magnitude.
The SmartyPants parser can be found in `Redcarpet::Render::SmartyPants`. It has
been implemented as a module, so it can be used standalone or as a mixin.
When mixed with a Renderer class, it will override the `postprocess` method
to perform SmartyPants replacements once the rendering is complete.
~~~~ ruby
# Mixin
class HTMLWithPants < Redcarpet::Render::HTML
include Redcarpet::Render::SmartyPants
end
# Standalone
Redcarpet::Render::SmartyPants.render("<p>Oh SmartyPants, you're so crazy...</p>")
~~~~
SmartyPants works on top of already-rendered HTML, and will ignore replacements
inside the content of HTML tags and inside specific HTML blocks such as
`<code>` or `<pre>`.
What? You really want to mix Markdown renderers?
------------------------------------------------
Redcarpet used to be a drop-in replacement for Redcloth. This is no longer the
case since version 2 -- it now has its own API, but retains the old name. Yes,
that does mean that Redcarpet is not backwards-compatible with the 1.X
versions.
Each renderer has its own API and its own set of extensions: you should choose one
(it doesn't have to be Redcarpet, though that would be great!), write your
software accordingly, and force your users to install it. That's the
only way to have reliable and predictable Markdown output on your program.
Markdown is already ill-specified enough; if you create software that is
renderer-independent, the results will be completely unreliable!
Still, if major forces (let's say, tornadoes or other natural disasters) force you
to keep a Markdown-compatibility layer, Redcarpet also supports this:
~~~~ ruby
require 'redcarpet/compat'
~~~~
Requiring the compatibility library will declare a `Markdown` class with the
classical RedCloth API, e.g.
~~~~ ruby
Markdown.new('this is my text').to_html
~~~~
This class renders 100% standards compliant Markdown with 0 extensions. Nada.
Don't even try to enable extensions with a compatibility layer, because
that's a maintenance nightmare and won't work.
On a related topic: if your Markdown gem has a `lib/markdown.rb` file that
monkeypatches the Markdown class, you're a terrible human being. Just saying.
Boring legal stuff
------------------
Copyright (c) 2011-2016, Vicent Martí
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
| 35.059113 | 172 | 0.74308 | eng_Latn | 0.986451 |
b97707c567eba745566704d4bd1b2595bdea5788 | 4,051 | md | Markdown | README.md | xliuhw/NLU-Evaluation-Scripts | 356711b59f347532d0290f070ff9aad5af7ed02e | [
"MIT"
] | 4 | 2019-03-19T05:07:32.000Z | 2021-08-12T13:11:30.000Z | README.md | xliuhw/NLU-Evaluation-Scripts | 356711b59f347532d0290f070ff9aad5af7ed02e | [
"MIT"
] | null | null | null | README.md | xliuhw/NLU-Evaluation-Scripts | 356711b59f347532d0290f070ff9aad5af7ed02e | [
"MIT"
] | null | null | null | # README -- Scripts for evaluating NLU Services/Platforms
This project contains the Java codes for preparing NLU Services/Platforms data and evaluating the performances,
the Python scripts for qeurying NLU Services/Platforms. The NLU data are provided in [Here](https://github.com/xliuhw/NLU-Evaluation-Data)
## Content
### Java codes
allGeneFileNames/ : contains the buffer file allGeneFileNames.txt shared between components.
conf4RunRasaServer/ : the config file to run Rasa server for querying Rasa using the testset.
Data_Info_BackedUp/testResults_Samples/ :
Sample prediction query output from each NLU services which are kept here
for reference in case the services change their output formats and then
the Evaluation.java should have corresponding changes.
evaluateResults/ : (Empty now) Evaluation.java will write the results to here
preprocessResults/ : (Empty now) The PreprocessRealData.java and the processes for each services will save info here.
testResults : (Empty now) the service query results will be saved here.
resources/ : the java resources which also contains the released, annotated CSV data file.
src/ : Java src
target/ : Compiled Java target Jars. It will be overwritten each time when re-building the java package.
targetWithDep: copied from target/ for running Jars from a terminal.
pom.xml : The java Maven file.
### Python scripts:
pythonQueryServices/ : the python scripts to query each service.
pythonCalcCombinedMeasure/calcMicroAverage.py shows how we calculated the combined measurements for all intents and entities for each Service in the cross-validation.
### Requirements
JDK 1.8
Netbeans 8.1
Python 2.7
### Scripts usage examples
We used the mixed Java and Python scripts due to historical reasons. They should have been done in one language! Anyway, here is the example procedures to use the scripts for evaluating Dialogflow (formerly Apiai). The procedures for other Services/Platforms are similar, please refer to their specific requirements.
1. Generate the trainsets and testsets.
Run the file PreprocessRealData.java (In Netbean 8.1, right-click the file, select Run File)
It will load the config file resources/config/Config_DataPreprocess.txt where the annontated data file is specified and generate the datasets in autoGeneFromRealAnno/preprocessResults/
The config file also specifies how many utterances to use from the whole annontated csv file as the train set. It is maxNumUtt (for each intent).
2. Convert the datasets to the right format of the Service.
Run PrepareApiaiCorpora.java, it will load the generated datasets in Step1 above, convert them to Dialogflow format. The results will be saved in preprocessResults/out4ApiaiReal/
3. Import the trainset to the Service.
First Zip the "merged" directory in preprocessResults/out4ApiaiReal/Apiai_trainset_TheNewlyGeneratedTimeStamp/
to e.g. merged.zip
Log into your Dialogflow account, click "Create new agent", in your newly created agent page, click Export and Import/IMPORT FROM ZIP, select merged.zip created above.
Waiting for Dialogflow to finish training your agent.
4. Test your agent using the generated testset in Step1
cd pythonQueryServices/pythonApiai
python queryApiai.py --testset default/specified --token YourClientToken
This will query your agent and get the predictions of the testsets, and save the results to
testResults/APIAI/
NB: This may not work any more as the Dialogflow Python API has been changed. New python API will be needed to query Dialogflow.
5. Evaluate the performance
Manually modify the relevant parts in the method doEvaluation_Manually_Top() in Evaluation.java and
Run the file Evaluation.java.
The results will be saved in evaluateResults/APIAI/
NB the buffer file allGeneFileNames/allGeneFileNames.txt will be using for the shared information between different steps.
## Contact
Please contact [email protected], if you have any questions
| 40.919192 | 316 | 0.783017 | eng_Latn | 0.986765 |
b97713b35ae724eef2bd40be8ae0bd184b3aff8b | 16,673 | md | Markdown | src/ch03-02-data-types.md | indexroot/book | eac55314210519238652f12b30fec9daea61f7fe | [
"ECL-2.0",
"Apache-2.0",
"MIT-0",
"MIT"
] | 1 | 2021-07-19T19:51:13.000Z | 2021-07-19T19:51:13.000Z | src/ch03-02-data-types.md | indexroot/book | eac55314210519238652f12b30fec9daea61f7fe | [
"ECL-2.0",
"Apache-2.0",
"MIT-0",
"MIT"
] | null | null | null | src/ch03-02-data-types.md | indexroot/book | eac55314210519238652f12b30fec9daea61f7fe | [
"ECL-2.0",
"Apache-2.0",
"MIT-0",
"MIT"
] | null | null | null | ## Data Types
Every value in Rust is of a certain *data type*, which tells Rust what kind of
data is being specified so it knows how to work with that data. We’ll look at
two data type subsets: scalar and compound.
Keep in mind that Rust is a *statically typed* language, which means that it
must know the types of all variables at compile time. The compiler can usually
infer what type we want to use based on the value and how we use it. In cases
when many types are possible, such as when we converted a `String` to a numeric
type using `parse` in the [“Comparing the Guess to the Secret
Number”][comparing-the-guess-to-the-secret-number]<!-- ignore --> section in
Chapter 2, we must add a type annotation, like this:
```rust
let guess: u32 = "42".parse().expect("Not a number!");
```
If we don’t add the type annotation here, Rust will display the following
error, which means the compiler needs more information from us to know which
type we want to use:
```console
{{#include ../listings/ch03-common-programming-concepts/output-only-01-no-type-annotations/output.txt}}
```
You’ll see different type annotations for other data types.
### Scalar Types
A *scalar* type represents a single value. Rust has four primary scalar types:
integers, floating-point numbers, Booleans, and characters. You may recognize
these from other programming languages. Let’s jump into how they work in Rust.
#### Integer Types
An *integer* is a number without a fractional component. We used one integer
type in Chapter 2, the `u32` type. This type declaration indicates that the
value it’s associated with should be an unsigned integer (signed integer types
start with `i`, instead of `u`) that takes up 32 bits of space. Table 3-1 shows
the built-in integer types in Rust. Each variant in the Signed and Unsigned
columns (for example, `i16`) can be used to declare the type of an integer
value.
<span class="caption">Table 3-1: Integer Types in Rust</span>
| Length | Signed | Unsigned |
|---------|---------|----------|
| 8-bit | `i8` | `u8` |
| 16-bit | `i16` | `u16` |
| 32-bit | `i32` | `u32` |
| 64-bit | `i64` | `u64` |
| 128-bit | `i128` | `u128` |
| arch | `isize` | `usize` |
Each variant can be either signed or unsigned and has an explicit size.
*Signed* and *unsigned* refer to whether it’s possible for the number to be
negative—in other words, whether the number needs to have a sign
with it (signed) or whether it will only ever be positive and can therefore be
represented without a sign (unsigned). It’s like writing numbers on paper: when
the sign matters, a number is shown with a plus sign or a minus sign; however,
when it’s safe to assume the number is positive, it’s shown with no sign.
Signed numbers are stored using [two’s complement](https://en.wikipedia.org/wiki/Two%27s_complement) representation.
Each signed variant can store numbers from -(2<sup>n - 1</sup>) to 2<sup>n -
1</sup> - 1 inclusive, where *n* is the number of bits that variant uses. So an
`i8` can store numbers from -(2<sup>7</sup>) to 2<sup>7</sup> - 1, which equals
-128 to 127. Unsigned variants can store numbers from 0 to 2<sup>n</sup> - 1,
so a `u8` can store numbers from 0 to 2<sup>8</sup> - 1, which equals 0 to 255.
Additionally, the `isize` and `usize` types depend on the kind of computer your
program is running on: 64 bits if you’re on a 64-bit architecture and 32 bits
if you’re on a 32-bit architecture.
You can write integer literals in any of the forms shown in Table 3-2. Note
that number literals that can be multiple numeric types allow a type suffix,
such as `57u8`, to designate the type. Number literals can also use `_` as a
visual separator to make the number easier to read, such as `1_000`, which will
have the same value as if you had specified `1000`.
<span class="caption">Table 3-2: Integer Literals in Rust</span>
| Number literals | Example |
|------------------|---------------|
| Decimal | `98_222` |
| Hex | `0xff` |
| Octal | `0o77` |
| Binary | `0b1111_0000` |
| Byte (`u8` only) | `b'A'` |
So how do you know which type of integer to use? If you’re unsure, Rust’s
defaults are generally good places to start: integer types default to `i32`.
The primary situation in which you’d use `isize` or `usize` is when indexing
some sort of collection.
> ##### Integer Overflow
>
> Let’s say you have a variable of type `u8` that can hold values between 0 and 255.
> If you try to change the variable to a value outside of that range, such
> as 256, *integer overflow* will occur. Rust has some interesting rules
> involving this behavior. When you’re compiling in debug mode, Rust includes
> checks for integer overflow that cause your program to *panic* at runtime if
> this behavior occurs. Rust uses the term panicking when a program exits with
> an error; we’ll discuss panics in more depth in the [“Unrecoverable Errors
> with `panic!`”][unrecoverable-errors-with-panic]<!-- ignore --> section in
> Chapter 9.
>
> When you’re compiling in release mode with the `--release` flag, Rust does
> *not* include checks for integer overflow that cause panics. Instead, if
> overflow occurs, Rust performs *two’s complement wrapping*. In short, values
> greater than the maximum value the type can hold “wrap around” to the minimum
> of the values the type can hold. In the case of a `u8`, 256 becomes 0, 257
> becomes 1, and so on. The program won’t panic, but the variable will have a
> value that probably isn’t what you were expecting it to have. Relying on
> integer overflow’s wrapping behavior is considered an error.
>
> To explicitly handle the possibility of overflow, you can use these families
> of methods that the standard library provides on primitive numeric types:
>
> - Wrap in all modes with the `wrapping_*` methods, such as `wrapping_add`
> - Return the `None` value if there is overflow with the `checked_*` methods
> - Return the value and a boolean indicating whether there was overflow with
> the `overflowing_*` methods
> - Saturate at the value's minimum or maximum values with `saturating_*`
> methods
#### Floating-Point Types
Rust also has two primitive types for *floating-point numbers*, which are
numbers with decimal points. Rust’s floating-point types are `f32` and `f64`,
which are 32 bits and 64 bits in size, respectively. The default type is `f64`
because on modern CPUs it’s roughly the same speed as `f32` but is capable of
more precision.
Here’s an example that shows floating-point numbers in action:
<span class="filename">Filename: src/main.rs</span>
```rust
{{#rustdoc_include ../listings/ch03-common-programming-concepts/no-listing-06-floating-point/src/main.rs}}
```
Floating-point numbers are represented according to the IEEE-754 standard. The
`f32` type is a single-precision float, and `f64` has double precision.
#### Numeric Operations
Rust supports the basic mathematical operations you’d expect for all of the
number types: addition, subtraction, multiplication, division, and remainder.
The following code shows how you’d use each one in a `let` statement:
<span class="filename">Filename: src/main.rs</span>
```rust
{{#rustdoc_include ../listings/ch03-common-programming-concepts/no-listing-07-numeric-operations/src/main.rs}}
```
Each expression in these statements uses a mathematical operator and evaluates
to a single value, which is then bound to a variable. [Appendix B][appendix_b]<!-- ignore --> contains a
list of all operators that Rust provides.
#### The Boolean Type
As in most other programming languages, a Boolean type in Rust has two possible
values: `true` and `false`. Booleans are one byte in size. The Boolean type in
Rust is specified using `bool`. For example:
<span class="filename">Filename: src/main.rs</span>
```rust
{{#rustdoc_include ../listings/ch03-common-programming-concepts/no-listing-08-boolean/src/main.rs}}
```
The main way to use Boolean values is through conditionals, such as an `if`
expression. We’ll cover how `if` expressions work in Rust in the [“Control
Flow”][control-flow]<!-- ignore --> section.
#### The Character Type
So far we’ve worked only with numbers, but Rust supports letters too. Rust’s
`char` type is the language’s most primitive alphabetic type, and the following
code shows one way to use it. (Note that `char` literals are specified with
single quotes, as opposed to string literals, which use double quotes.)
<span class="filename">Filename: src/main.rs</span>
```rust
{{#rustdoc_include ../listings/ch03-common-programming-concepts/no-listing-09-char/src/main.rs}}
```
Rust’s `char` type is four bytes in size and represents a Unicode Scalar Value,
which means it can represent a lot more than just ASCII. Accented letters;
Chinese, Japanese, and Korean characters; emoji; and zero-width spaces are all
valid `char` values in Rust. Unicode Scalar Values range from `U+0000` to
`U+D7FF` and `U+E000` to `U+10FFFF` inclusive. However, a “character” isn’t
really a concept in Unicode, so your human intuition for what a “character” is
may not match up with what a `char` is in Rust. We’ll discuss this topic in
detail in [“Storing UTF-8 Encoded Text with Strings”][strings]<!-- ignore -->
in Chapter 8.
### Compound Types
*Compound types* can group multiple values into one type. Rust has two
primitive compound types: tuples and arrays.
#### The Tuple Type
A tuple is a general way of grouping together a number of values with a variety
of types into one compound type. Tuples have a fixed length: once declared,
they cannot grow or shrink in size.
We create a tuple by writing a comma-separated list of values inside
parentheses. Each position in the tuple has a type, and the types of the
different values in the tuple don’t have to be the same. We’ve added optional
type annotations in this example:
<span class="filename">Filename: src/main.rs</span>
```rust
{{#rustdoc_include ../listings/ch03-common-programming-concepts/no-listing-10-tuples/src/main.rs}}
```
The variable `tup` binds to the entire tuple, because a tuple is considered a
single compound element. To get the individual values out of a tuple, we can
use pattern matching to destructure a tuple value, like this:
<span class="filename">Filename: src/main.rs</span>
```rust
{{#rustdoc_include ../listings/ch03-common-programming-concepts/no-listing-11-destructuring-tuples/src/main.rs}}
```
This program first creates a tuple and binds it to the variable `tup`. It then
uses a pattern with `let` to take `tup` and turn it into three separate
variables, `x`, `y`, and `z`. This is called *destructuring*, because it breaks
the single tuple into three parts. Finally, the program prints the value of
`y`, which is `6.4`.
In addition to destructuring through pattern matching, we can access a tuple
element directly by using a period (`.`) followed by the index of the value we
want to access. For example:
<span class="filename">Filename: src/main.rs</span>
```rust
{{#rustdoc_include ../listings/ch03-common-programming-concepts/no-listing-12-tuple-indexing/src/main.rs}}
```
This program creates a tuple, `x`, and then makes new variables for each
element by using their respective indices. As with most programming languages,
the first index in a tuple is 0.
#### The Array Type
Another way to have a collection of multiple values is with an *array*. Unlike
a tuple, every element of an array must have the same type. Arrays in Rust are
different from arrays in some other languages because arrays in Rust have a
fixed length, like tuples.
In Rust, the values going into an array are written as a comma-separated list
inside square brackets:
<span class="filename">Filename: src/main.rs</span>
```rust
{{#rustdoc_include ../listings/ch03-common-programming-concepts/no-listing-13-arrays/src/main.rs}}
```
Arrays are useful when you want your data allocated on the stack rather than
the heap (we will discuss the stack and the heap more in Chapter 4) or when
you want to ensure you always have a fixed number of elements. An array isn’t
as flexible as the vector type, though. A vector is a similar collection type
provided by the standard library that *is* allowed to grow or shrink in size.
If you’re unsure whether to use an array or a vector, you should probably use a
vector. Chapter 8 discusses vectors in more detail.
An example of when you might want to use an array rather than a vector is in a
program that needs to know the names of the months of the year. It’s very
unlikely that such a program will need to add or remove months, so you can use
an array because you know it will always contain 12 elements:
```rust
let months = ["January", "February", "March", "April", "May", "June", "July",
"August", "September", "October", "November", "December"];
```
You would write an array’s type by using square brackets, and within the
brackets include the type of each element, a semicolon, and then the number of
elements in the array, like so:
```rust
let a: [i32; 5] = [1, 2, 3, 4, 5];
```
Here, `i32` is the type of each element. After the semicolon, the number `5`
indicates the array contains five elements.
Writing an array’s type this way looks similar to an alternative syntax for
initializing an array: if you want to create an array that contains the same
value for each element, you can specify the initial value, followed by a
semicolon, and then the length of the array in square brackets, as shown here:
```rust
let a = [3; 5];
```
The array named `a` will contain `5` elements that will all be set to the value
`3` initially. This is the same as writing `let a = [3, 3, 3, 3, 3];` but in a
more concise way.
##### Accessing Array Elements
An array is a single chunk of memory allocated on the stack. You can access
elements of an array using indexing, like this:
<span class="filename">Filename: src/main.rs</span>
```rust
{{#rustdoc_include ../listings/ch03-common-programming-concepts/no-listing-14-array-indexing/src/main.rs}}
```
In this example, the variable named `first` will get the value `1`, because
that is the value at index `[0]` in the array. The variable named `second` will
get the value `2` from index `[1]` in the array.
##### Invalid Array Element Access
What happens if you try to access an element of an array that is past the end
of the array? Say you change the example to the following, which uses code
similar to the guessing game in Chapter 2 to get an array index from the user:
<span class="filename">Filename: src/main.rs</span>
```rust,ignore,panics
{{#rustdoc_include ../listings/ch03-common-programming-concepts/no-listing-15-invalid-array-access/src/main.rs}}
```
This code compiles successfully. If you run this code using `cargo run` and
enter 0, 1, 2, 3, or 4, the program will print out the corresponding value at
that index in the array. If you instead enter a number past the end of the
array, such as 10, you'll see output like this:
<!-- manual-regeneration
cd listings/ch03-common-programming-concepts/no-listing-15-invalid-array-access
cargo run
10
-->
```console
thread 'main' panicked at 'index out of bounds: the len is 5 but the index is 10', src/main.rs:19:19
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
```
The program resulted in a *runtime* error at the point of using an invalid
value in the indexing operation. The program exited with an error message and
didn't execute the final `println!` statement. When you attempt to access an
element using indexing, Rust will check that the index you’ve specified is less
than the array length. If the index is greater than or equal to the length,
Rust will panic. This check has to happen at runtime, especially in this case,
because the compiler can't possibly know what value a user will enter when they
run the code later.
This is the first example of Rust’s safety principles in action. In many
low-level languages, this kind of check is not done, and when you provide an
incorrect index, invalid memory can be accessed. Rust protects you against this
kind of error by immediately exiting instead of allowing the memory access and
continuing. Chapter 9 discusses more of Rust’s error handling.
[comparing-the-guess-to-the-secret-number]:
ch02-00-guessing-game-tutorial.html#comparing-the-guess-to-the-secret-number
[control-flow]: ch03-05-control-flow.html#control-flow
[strings]: ch08-02-strings.html#storing-utf-8-encoded-text-with-strings
[unrecoverable-errors-with-panic]: ch09-01-unrecoverable-errors-with-panic.html
[wrapping]: ../std/num/struct.Wrapping.html
[appendix_b]: appendix-02-operators.md
| 44.343085 | 116 | 0.743298 | eng_Latn | 0.999056 |
b9773c3138eb3dedd024d30431ea873678cc6a83 | 1,551 | md | Markdown | docs/concepts/ie11-mode.md | kunj-sangani/pnpjs | bdf6028daf9731c418c4c4690be7ce8a72aff23b | [
"MIT"
] | 1 | 2021-10-19T17:49:45.000Z | 2021-10-19T17:49:45.000Z | docs/concepts/ie11-mode.md | kunj-sangani/pnpjs | bdf6028daf9731c418c4c4690be7ce8a72aff23b | [
"MIT"
] | null | null | null | docs/concepts/ie11-mode.md | kunj-sangani/pnpjs | bdf6028daf9731c418c4c4690be7ce8a72aff23b | [
"MIT"
] | null | null | null | # IE11 Mode
Starting with v2 we have made the decision to no longer support IE11. Because we know this affects folks we have introduced IE11 compatibility mode. Configuring the library will allow it to work within IE11, however at a possibly reduced level of functionality depending on your use case. Please see the list below of known limitations.
## Limitations
When required to use IE11 mode there is certain functionality which may not work correctly or at all.
- Unavailable: [Extension Methods](./../odata/extensions.md)
- Unavailable: [OData Debugging](./../odata/debug.md)
## Configure IE11 Mode
To enable IE11 Mode set the ie11 flag to true in the setup object. Optionally supply the context object when working in [SharePoint Framework](https://docs.microsoft.com/en-us/sharepoint/dev/spfx/sharepoint-framework-overview).
```TypeScript
import { sp } from "@pnp/sp";
sp.setup({
// set ie 11 mode
ie11: true,
// only needed when working within SharePoint Framework
spfxContext: this.context
});
```
> If you are supporting IE 11, please see the article on required [polyfills](./polyfill.md).
## A note on ie11 mode and support
Because IE11 is no longer a primary supported browser our policy moving forward will be doing our best not to break anything in ie11 mode, but not all features will work and new features may never come to ie11 mode. Also, if you find an ie11 bug we expect you to work with us on helping to fix it. If you aren't willing to invest some time to support an old browser it seems we shouldn't either.
| 48.46875 | 395 | 0.766602 | eng_Latn | 0.998228 |
b9773df79004a987300f2b21aad2c1121d880bcd | 3,931 | md | Markdown | README.md | VGirol/FormRequest-Tester | d735a89d208dd0511aa719c209001799bec17a1f | [
"MIT"
] | null | null | null | README.md | VGirol/FormRequest-Tester | d735a89d208dd0511aa719c209001799bec17a1f | [
"MIT"
] | null | null | null | README.md | VGirol/FormRequest-Tester | d735a89d208dd0511aa719c209001799bec17a1f | [
"MIT"
] | null | null | null | # FormRequest-Tester
[![Latest Version on Packagist][ico-version]][link-packagist]
[![Software License][ico-license]](LICENSE.md)
[![Build Status][ico-travis]][link-travis]
[![Coverage Status][ico-scrutinizer]][link-scrutinizer]
[![Quality Score][ico-code-quality]][link-code-quality]
[![Infection MSI][ico-mutation]][link-mutation]
[![Total Downloads][ico-downloads]][link-downloads]
This package provides a set of tools to test Laravel FormRequest.
It is strongly inspired by the package [mohammedmanssour/form-request-tester](https://github.com/mohammedmanssour/form-request-tester).
## Technologies
- PHP 7.3+
- Laravel 6+
## Install
To install through composer, simply put the following in your `composer.json` file:
```json
{
"require-dev": {
"vgirol/formrequest-tester": "dev-master"
}
}
```
And then run `composer install` from the terminal.
### Quick Installation
Above installation can also be simplified by using the following command:
``` bash
$ composer require vgirol/formrequest-tester
```
## Usage
Assertions can be chained :
``` php
use App\Requests\DummyFormRequest;
use Orchestra\Testbench\TestCase;
use VGirol\FormRequestTesterer\TestFormRequests;
class FormRequestTester extends TestCase
{
use TestFormRequests;
/**
* @test
*/
public function myFirtsTest()
{
// Creates a form
$form = [
'data' => [
'type' => 'dummy',
'attributes' => [
'attr' => 'value'
]
]
];
// Create and validate form request for DummyFormRequest class
$this->formRequest(
DummyFormRequest::class,
$form,
[
'method' => 'POST',
'route' => '/dummy-route'
]
)->assertValidationPassed();
}
}
```
## Documentation
The API documentation is available in XHTML format at the url [http://formrequest-tester.girol.fr/docs/ref/index.html](http://FormRequestTester.girol.fr/docs/ref/index.html).
## Change log
Please see [CHANGELOG](CHANGELOG.md) for more information on what has changed recently.
## Testing
``` bash
composer test
```
## Contributing
Please see [CONTRIBUTING](CONTRIBUTING.md) and [CODE_OF_CONDUCT](CODE_OF_CONDUCT.md) for details.
## Security
If you discover any security related issues, please email [[email protected]](mailto:[email protected]) instead of using the issue tracker.
## Credits
- [Vincent Girol][link-author]
- [All Contributors][link-contributors]
## License
The MIT License (MIT). Please see [License File](LICENSE.md) for more information.
[ico-version]: https://img.shields.io/packagist/v/VGirol/FormRequest-Tester.svg?style=flat-square
[ico-license]: https://img.shields.io/badge/license-MIT-brightgreen.svg?style=flat-square
[ico-travis]: https://img.shields.io/travis/VGirol/FormRequest-Tester/master.svg?style=flat-square
[ico-scrutinizer]: https://img.shields.io/scrutinizer/coverage/g/VGirol/FormRequest-Tester.svg?style=flat-square
[ico-code-quality]: https://img.shields.io/scrutinizer/g/VGirol/FormRequest-Tester.svg?style=flat-square
[ico-mutation]: https://img.shields.io/endpoint?style=flat-square&url=https%3A%2F%2Fbadge-api.stryker-mutator.io%2Fgithub.com%2FVGirol%2FFormRequest-Tester%2Fmaster
[ico-downloads]: https://img.shields.io/packagist/dt/VGirol/FormRequest-Tester.svg?style=flat-square
[link-packagist]: https://packagist.org/packages/VGirol/FormRequest-Tester
[link-travis]: https://travis-ci.org/VGirol/FormRequest-Tester
[link-scrutinizer]: https://scrutinizer-ci.com/g/VGirol/FormRequest-Tester/code-structure
[link-code-quality]: https://scrutinizer-ci.com/g/VGirol/FormRequest-Tester
[link-downloads]: https://packagist.org/packages/VGirol/FormRequest-Tester
[link-author]: https://github.com/VGirol
[link-mutation]: https://infection.github.io
[link-contributors]: ../../contributors
| 30.472868 | 174 | 0.705927 | eng_Latn | 0.283922 |
b977ce114a53ade41afcbca28cf8312e72a822ed | 28 | md | Markdown | README.md | JerryShockley/cbrm | 07640c6be56a623465305fe89917abac6ad22f7b | [
"MIT"
] | null | null | null | README.md | JerryShockley/cbrm | 07640c6be56a623465305fe89917abac6ad22f7b | [
"MIT"
] | null | null | null | README.md | JerryShockley/cbrm | 07640c6be56a623465305fe89917abac6ad22f7b | [
"MIT"
] | null | null | null | # cbrm
A JavaScript project
| 9.333333 | 20 | 0.785714 | eng_Latn | 0.833688 |
b9786271081413abf91d01486a1ac2dd7bf954b7 | 783 | md | Markdown | latex/source2report.md | MohamedElashri/dot-scripts | c1384bea8725669d788e3302ee546a9ceed89b89 | [
"MIT"
] | null | null | null | latex/source2report.md | MohamedElashri/dot-scripts | c1384bea8725669d788e3302ee546a9ceed89b89 | [
"MIT"
] | null | null | null | latex/source2report.md | MohamedElashri/dot-scripts | c1384bea8725669d788e3302ee546a9ceed89b89 | [
"MIT"
] | null | null | null | ## Goal
Programming Source Code to PDF script using In LaTeX Format
## Dependencies
This script requires `bibtexparser`
### ubuntu
```
apt-get install texlive-latex-base texlive-latex-extra
```
### MacOS
These things should be included in `MacTex` Full packages.
## Usage
The script shoud be given exceutable permission. For example if you want to add the script to `$PATH` run
```
chmod +x /usr/local/bin/src2pdf.sh
```
After that cd to to directory where the LaTeX source and run
```
src2pdf
```
The script will present a series of questions about `Title`, `Author`, `Subtitle` ..etc. and will then create the PDF.
## Supported Languages
- C++
- C
- Python
- Matlab
- SQL
- R
- HTML
- JAVA
- C$
- Mathematica
- Fortran4
- GO
- Haskell
- XML
- PHP
- Cobol
- Ruby
| 14.773585 | 119 | 0.697318 | eng_Latn | 0.873195 |
b97871074b68ec7139029d974c14282199454154 | 3,913 | md | Markdown | articles/azure-sql/managed-instance/minimal-tls-version-configure.md | fuatrihtim/azure-docs.tr-tr | 6569c5eb54bdab7488b44498dc4dad397d32f1be | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-sql/managed-instance/minimal-tls-version-configure.md | fuatrihtim/azure-docs.tr-tr | 6569c5eb54bdab7488b44498dc4dad397d32f1be | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-sql/managed-instance/minimal-tls-version-configure.md | fuatrihtim/azure-docs.tr-tr | 6569c5eb54bdab7488b44498dc4dad397d32f1be | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Minimum TLS sürümü ile yönetilen örneği yapılandırma
description: Yönetilen örnek için en düşük TLS sürümünü yapılandırmayı öğrenin
services: sql-database
ms.service: sql-managed-instance
ms.subservice: security
ms.custom: ''
ms.topic: how-to
author: srdan-bozovic-msft
ms.author: srbozovi
ms.reviewer: ''
ms.date: 05/25/2020
ms.openlocfilehash: 17d430946f3cba1aa4680d1eaf8979fa4338bc22
ms.sourcegitcommit: 910a1a38711966cb171050db245fc3b22abc8c5f
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 03/19/2021
ms.locfileid: "92788409"
---
# <a name="configure-minimal-tls-version-in-azure-sql-managed-instance"></a>Azure SQL Yönetilen Örneğinde en düşük TLS sürümünü yapılandırma
Minimum [Aktarım Katmanı Güvenliği (TLS)](https://support.microsoft.com/help/3135244/tls-1-2-support-for-microsoft-sql-server) sürümü ayarı, MÜŞTERILERIN Azure SQL yönetilen örneği tarafından kullanılan TLS sürümünü denetlemesine olanak tanır.
Şu anda TLS 1.0, 1.1 ve 1.2’yi destekliyoruz. En Düşük TLS Sürümünü ayarlamak sonraki, daha yeni TLS sürümlerinin desteklendiğinden emin olmanızı sağlar. Örneğin, örneğin, 1,1 'den büyük bir TLS sürümü seçme. yalnızca TLS 1.1 ve 1.2 içeren bağlantıların kabul edileceği ve TLS 1.0’ın reddedileceği anlamına gelir. Uygulamalarınızın bunu desteklediğini test edip onayladıktan sonra en düşük TLS sürümü olarak 1.2’yi ayarlamanızı öneririz çünkü bu sürüm önceki sürümlerde bulunan güvenlik açıklarının düzeltmelerini içerir ve TLS’nin Azure SQL Yönetilen Örneği’nde desteklenen en yüksek sürümüdür.
TLS 'nin eski sürümlerini kullanan uygulamalar için, uygulamalarınızın gereksinimlerine göre en düşük TLS sürümünü ayarlamayı öneririz. Şifrelenmemiş bir bağlantı kullanarak bağlanmak için uygulamalara bağlı olan müşteriler için, en az TLS sürümü ayarlamamız önerilir.
Daha fazla bilgi için bkz. [SQL veritabanı bağlantısı Için TLS konuları](../database/connect-query-content-reference-guide.md#tls-considerations-for-database-connectivity).
En düşük TLS sürümünü ayarladıktan sonra, sunucunun en düşük TLS sürümünü kullanarak bir TLS sürümü kullanan istemcilerden gelen oturum açma girişimleri aşağıdaki hatayla başarısız olur:
```output
Error 47072
Login failed with invalid TLS version
```
## <a name="set-minimal-tls-version-via-powershell"></a>PowerShell ile en az TLS sürümü ayarla
[!INCLUDE [updated-for-az](../../../includes/updated-for-az.md)]
> [!IMPORTANT]
> PowerShell Azure Resource Manager modülü Azure SQL veritabanı tarafından hala desteklenmektedir, ancak gelecekteki tüm geliştirmeler az. SQL modülüne yöneliktir. Bu cmdlet 'ler için bkz. [Azurerd. SQL](/powershell/module/AzureRM.Sql/). Az Module ve Azurerd modüllerinde komutların bağımsız değişkenleri önemli ölçüde aynıdır. Aşağıdaki betik [Azure PowerShell modülünü](/powershell/azure/install-az-ps)gerektiriyor.
Aşağıdaki PowerShell betiği, `Get` örnek düzeyinde nasıl ve `Set` **en az TLS sürümü** özelliğinin olduğunu gösterir:
```powershell
#Get the Minimal TLS Version property
(Get-AzSqlInstance -Name sql-instance-name -ResourceGroupName resource-group).MinimalTlsVersion
# Update Minimal TLS Version Property
Set-AzSqlInstance -Name sql-instance-name -ResourceGroupName resource-group -MinimalTlsVersion "1.2"
```
## <a name="set-minimal-tls-version-via-azure-cli"></a>Azure CLı ile en az TLS sürümü ayarlama
> [!IMPORTANT]
> Bu bölümdeki tüm betikler [Azure CLI](/cli/azure/install-azure-cli)gerektirir.
### <a name="azure-cli-in-a-bash-shell"></a>Bash kabuğu 'nda Azure CLı
Aşağıdaki CLı betiği, bir bash kabuğunda **En düşük TLS sürümü** ayarının nasıl değiştirileceğini göstermektedir:
```azurecli-interactive
# Get current setting for Minimal TLS Version
az sql mi show -n sql-instance-name -g resource-group --query "minimalTlsVersion"
# Update setting for Minimal TLS Version
az sql mi update -n sql-instance-name -g resource-group --set minimalTlsVersion="1.2"
``` | 58.402985 | 595 | 0.803476 | tur_Latn | 0.998573 |
b9794c1a0f42e08b3a94172f53c2827420c36186 | 2,143 | md | Markdown | content/publication/sunyer-collective-2016/index.md | rsunyer/starter-academic | 42bea1e77a5071bafb2609712882e360dd3a6af8 | [
"MIT"
] | null | null | null | content/publication/sunyer-collective-2016/index.md | rsunyer/starter-academic | 42bea1e77a5071bafb2609712882e360dd3a6af8 | [
"MIT"
] | null | null | null | content/publication/sunyer-collective-2016/index.md | rsunyer/starter-academic | 42bea1e77a5071bafb2609712882e360dd3a6af8 | [
"MIT"
] | null | null | null | ---
# Documentation: https://wowchemy.com/docs/managing-content/
title: Collective cell durotaxis emerges from long-range intercellular force transmission
subtitle: ''
summary: ''
authors:
- Raimon Sunyer
- Vito Conte
- Jorge Escribano
- Alberto Elosegui-Artola
- Anna Labernadie
- Léo Valon
- Daniel Navajas
- José Manuel García-Aznar
- José J. Muñoz
- Pere Roca-Cusachs
- Xavier Trepat
tags: []
categories: []
date: '2016-09-01'
lastmod: 2021-07-23T16:35:01+02:00
featured: false
draft: false
# Featured image
# To use, add an image named `featured.jpg/png` to your page's folder.
# Focal points: Smart, Center, TopLeft, Top, TopRight, Left, Right, BottomLeft, Bottom, BottomRight.
image:
caption: ''
focal_point: ''
preview_only: false
# Projects (optional).
# Associate this post with one or more of your projects.
# Simply enter your project's folder or file name without extension.
# E.g. `projects = ["internal-project"]` references `content/project/deep-learning/index.md`.
# Otherwise, set `projects = []`.
projects: []
publishDate: '2021-07-23T14:52:33.943917Z'
publication_types:
- '2'
abstract: The ability of cells to follow gradients of extracellular matrix stiffness—durotaxis—has
been implicated in development, fibrosis, and cancer. Here, we found multicellular
clusters that exhibited durotaxis even if isolated constituent cells did not. This
emergent mode of directed collective cell migration applied to a variety of epithelial
cell types, required the action of myosin motors, and originated from supracellular
transmission of contractile physical forces. To explain the observed phenomenology,
we developed a generalized clutch model in which local stick-slip dynamics of cell-matrix
adhesions was integrated to the tissue level through cell-cell junctions. Collective
durotaxis is far more efficient than single-cell durotaxis; it thus emerges as a
robust mechanism to direct cell migration during development, wound healing, and
collective cancer cell invasion.
publication: '*Science*'
url_pdf: http://science.sciencemag.org/content/353/6304/1157
doi: 10.1126/science.aaf7119
---
| 36.948276 | 100 | 0.770415 | eng_Latn | 0.946646 |
b979a18303924a927179ce376d08f704f79c1dba | 6,061 | markdown | Markdown | xap100adm/asynchronous-replication.markdown | genzel/gigaspaces-wiki-jekyll | 6f101054804a38a95cf471c35ec8dd9a88350297 | [
"Apache-2.0"
] | null | null | null | xap100adm/asynchronous-replication.markdown | genzel/gigaspaces-wiki-jekyll | 6f101054804a38a95cf471c35ec8dd9a88350297 | [
"Apache-2.0"
] | null | null | null | xap100adm/asynchronous-replication.markdown | genzel/gigaspaces-wiki-jekyll | 6f101054804a38a95cf471c35ec8dd9a88350297 | [
"Apache-2.0"
] | null | null | null | ---
layout: post100
title: Asynchronous Replication
categories: XAP100ADM
parent: replication.html
weight: 300
---
{% summary %} {% endsummary %}
In asynchronous replication, operations are performed in the source space instance, and acknowledgement is immediately returned to the client. Operations are accumulated in the source space and sent asynchronously to the target space, after a defined period of time has elapsed, or after a defined number of operations have been performed (the first one of these that occurs). This replication type offers the highest performance at the cost of possible data lose of latest operations if the source space instance fails (sudden crash) while transferring the accumulated operations to the target space. Another problem is data coherency - the source and the target do not have identical data all the time.
# How to Turn on Asynchronous Replication?
In general you should have the `cluster-config.groups.group.repl-policy.replication-mode` property set to `async`. See below example:
{% highlight xml %}
<os-core:embedded-space id="space" name="mySpace">
<os-core:properties>
<props>
<prop key="cluster-config.groups.group.repl-policy.replication-mode">async</prop>
</props>
</os-core:properties>
</os-core:embedded-space>
{% endhighlight %}
# When to Use Asynchronous Replication
Asynchronous replication provides fastest performance because the replication is executed asynchronously to the operation. However, this comes with a cost
of possible data loss of recent operations upon unexpected failures (sudden crash). Therefore, an application that is using asynchronous replication
must be aware to this fact.
# How Asynchronous Replication Works
1. A destructive space operation is called.
1. The source space:
1. Performs the operation.
1. Insert the operations into a redo log.
1. Sends acknowledgement to the client.
1. Asynchronous worker wakes up on demand (interval passed or pending operations exceeded).
1. Constructs a batch of operations in the source space.
1. Transmits the packet into the target space.
1. Once they are received at the target space, the operations are processed according to their order.
1. The next batch is sent when the target space completes processing the replication packet.
# Handling Disconnections and Errors
Due to the asynchronous nature of the replication channel, when a replication target space instance is unavailable (disconnection) or some error occurred during the processing of the replication data at the target the channel will keep operating in the same way, it will keep the operation in the redo log until it succeeds replicating the operations.
# Behavior During Recovery
In the previous scenario, a target space instance might become unavailable because it has been restarted or relocated due to various reason (failure, manual/automatic relocation). In the default settings, when that target space instance will restart, it will perform a recovery from a source space instance. In primary backup topology it will be the primary space instance, in active active topology it can be any space instance. The target space instance will not be available until the source channel redo log size is almost empty, thus making sure that once the target space is available and visible, the number of operations that might be lost if a failure occurs will be minimal.
# Controlling the Asynchronous worker
The asynchronous worker of the channel can wake up and start replicating for two reasons:
1. The predefined interval has elapsed
1. The predefined number of pending operations is exceeded.
The worker will wake up and replicate if either of these two occurs. The following parameters controls these behavior and a few more options:
{: .table .table-bordered .table-condensed}
| Property | Description | Default Value |
|:---------|:------------|:--------------|
| repl-chunk-size | Number of packets transmitted together on the network when the replication event is triggered. The maximum value you can assign for this property is `repl-interval-opers`. | 500 |
| <nobr>repl-interval-millis</nobr> | Time (in milliseconds) to wait between replication operations. | 3000 \[ms\] |
| repl-interval-opers | Number of destructive operations to wait before replicating. | 500 |
{%note%}
Prefix the property with 'cluster-config.groups.group.repl-policy.async-replication.`
{%endnote%}
To change the default replication settings you should modify the space properties when deployed. You may set these properties via the pu.xml or programmatically. Here is an example how you can set the replication parameters when using the pu.xml:
{% highlight xml %}
<os-core:embedded-space id="space" name="mySpace">
<os-core:properties>
<props>
<prop key="cluster-config.groups.group.async-replication.repl-chunk-size">1000</prop>
</props>
</os-core:properties>
</os-core:embedded-space>
{% endhighlight %}
# Flushing of Pending Replication During Shutdown
When a source space instance is closed, it may have pending replication packets in its redo log because there were still not replicated. During this process, the space instance will stop accepting new operations and try to gracefully shutdown the replication channel and wait for all pending replication packets to be sent before completely shutting down. This graceful shutdown timeout can be configured with the following property:
{: .table .table-bordered .table-condesed}
| Property | Description | Default Value |
|:---------|:------------|:--------------|
| cluster-config.groups.group.repl-policy.async-replication.async-channel-shutdown-timeout | Determines how long (in milliseconds) the primary space will wait for pending replication to be replicated to its targets before shutting down.| 300000 \[ms\] |
| 60.009901 | 705 | 0.759446 | eng_Latn | 0.99775 |
b979a79caeb633c6408d74a63e7c440c6f145056 | 873 | md | Markdown | docs/GSMA.MobileConnect.Authentication/JWKeysetService/RetrieveJWKS.md | Mobile-Connect/.net_server_side_sdk | b11ac537d5cb9055b52927e026c7706ce44477d6 | [
"MIT"
] | 2 | 2019-12-26T22:40:59.000Z | 2019-12-26T22:41:53.000Z | docs/GSMA.MobileConnect.Authentication/JWKeysetService/RetrieveJWKS.md | Mobile-Connect/.net_server_side_sdk | b11ac537d5cb9055b52927e026c7706ce44477d6 | [
"MIT"
] | 2 | 2019-04-17T14:42:49.000Z | 2020-06-17T09:31:48.000Z | docs/GSMA.MobileConnect.Authentication/JWKeysetService/RetrieveJWKS.md | Mobile-Connect/.net_server_side_library | b11ac537d5cb9055b52927e026c7706ce44477d6 | [
"MIT"
] | 1 | 2018-03-16T06:11:16.000Z | 2018-03-16T06:11:16.000Z | JWKeysetService.RetrieveJWKS Method
===================================
Synchronous wrapper for [RetrieveJWKSAsync(String)][1]
**Namespace:** [GSMA.MobileConnect.Authentication][2]
**Assembly:** GSMA.MobileConnect (in GSMA.MobileConnect.dll)
Syntax
------
```csharp
public JWKeyset RetrieveJWKS(
string url
)
```
#### Parameters
##### *url*
Type: [System.String][3]
JWKS URL
#### Return Value
Type: [JWKeyset][4]
JSON Web Keyset if successfully retrieved
#### Implements
[IJWKeysetService.RetrieveJWKS(String)][5]
See Also
--------
#### Reference
[JWKeysetService Class][6]
[GSMA.MobileConnect.Authentication Namespace][2]
[1]: ../IJWKeysetService/RetrieveJWKSAsync.md
[2]: ../README.md
[3]: http://msdn.microsoft.com/en-us/library/s1wwdcbf
[4]: ../JWKeyset/README.md
[5]: ../IJWKeysetService/RetrieveJWKS.md
[6]: README.md
[7]: ../../_icons/Help.png | 20.302326 | 60 | 0.674685 | yue_Hant | 0.865186 |
b97a1d50af3a1626d553e348e99e9c0e6c6be689 | 9,046 | md | Markdown | articles/sql-database/sql-database-tutorial-predictive-model-prepare-data.md | decarli/azure-docs.pt-br | 20bc383d005c11e7b7dc7b7b0777fc0de1262ffc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/sql-database/sql-database-tutorial-predictive-model-prepare-data.md | decarli/azure-docs.pt-br | 20bc383d005c11e7b7dc7b7b0777fc0de1262ffc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/sql-database/sql-database-tutorial-predictive-model-prepare-data.md | decarli/azure-docs.pt-br | 20bc383d005c11e7b7dc7b7b0777fc0de1262ffc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Tutorial: Preparar os dados para treinar um modelo preditivo no R'
titleSuffix: Azure SQL Database Machine Learning Services (preview)
description: Na primeira parte deste tutorial com três partes, você preparará os dados de um Banco de Dados SQL do Azure para treinar um modelo preditivo no R com os Serviços do Machine Learning do Banco de Dados SQL do Azure (versão prévia).
services: sql-database
ms.service: sql-database
ms.subservice: machine-learning
ms.custom: ''
ms.devlang: r
ms.topic: tutorial
author: garyericson
ms.author: garye
ms.reviewer: davidph
manager: cgronlun
ms.date: 07/26/2019
ms.openlocfilehash: c1271d5b63fa796fe44b7a40c364953464a87539
ms.sourcegitcommit: fe6b91c5f287078e4b4c7356e0fa597e78361abe
ms.translationtype: HT
ms.contentlocale: pt-BR
ms.lasthandoff: 07/29/2019
ms.locfileid: "68596675"
---
# <a name="tutorial-prepare-data-to-train-a-predictive-model-in-r-with-azure-sql-database-machine-learning-services-preview"></a>Tutorial: Preparar dados para treinar um modelo preditivo em R com os Serviços do Machine Learning do Banco de Dados SQL do Azure (versão prévia)
Na primeira parte deste tutorial com três partes, você importará e preparará os dados de um Banco de Dados SQL do Azure usando o R. Mais adiante nesta série, você usará esses dados para treinar e implantar um modelo de machine learning no R com os Serviços do Machine Learning do Banco de Dados SQL do Azure (versão prévia).
Nesta série de tutoriais, imagine que você tem uma empresa de aluguel de esquis e quer prever a quantidade de aluguéis em uma data futura. Essas informações ajudarão a preparar seu estoque, a equipe e os recursos.
Na primeira e na segunda parte desta série, você desenvolverá alguns scripts do R no RStudio para preparar os dados e treinar um modelo de machine learning. Em seguida, na terceira parte, você executará esses scripts do R em um banco de dados SQL usando os procedimentos armazenados.
Neste artigo, você aprenderá a:
> [!div class="checklist"]
> * Importar um banco de dados de exemplo para um Banco de Dados SQL do Azure usando o R
> * Carregar os dados do Banco de Dados SQL do Azure em um dataframe do R
> * Preparar os dados no R identificando algumas colunas como categóricas
Na [parte 2](sql-database-tutorial-predictive-model-build-compare.md), você aprenderá a criar e treinar vários modelos de machine learning em R e, em seguida, escolher o mais preciso.
Na [parte três](sql-database-tutorial-predictive-model-deploy.md), você aprenderá a armazenar o modelo em um banco de dados e, em seguida, criar um procedimento armazenado dos scripts do R desenvolvidos nas partes anteriores. Os procedimentos armazenados serão executados em um banco de dados SQL para fazer previsões com base em novos dados.
[!INCLUDE[ml-preview-note](../../includes/sql-database-ml-preview-note.md)]
## <a name="prerequisites"></a>Pré-requisitos
* Assinatura do Azure – Caso você não tenha uma assinatura do Azure, [crie uma conta](https://azure.microsoft.com/free/) antes de começar.
* Servidor do Banco de Dados SQL do Azure com os Serviços do Machine Learning habilitados – Durante a versão prévia pública, a Microsoft realizará sua integração e habilitará o aprendizado de máquina para seu banco de dados novo ou existente. Siga as etapas em [Inscrever-se na versão prévia](sql-database-machine-learning-services-overview.md#signup).
* Pacote de RevoScaleR – Confira [RevoScaleR](https://docs.microsoft.com/sql/advanced-analytics/r/ref-r-revoscaler?view=sql-server-2017#versions-and-platforms) para ver opções de instalação local do pacote.
* IDE do R – Este tutorial usa o [RStudio Desktop](https://www.rstudio.com/products/rstudio/download/).
* Ferramenta de consulta SQL – Este tutorial presume que você está usando o [Azure Data Studio](https://docs.microsoft.com/sql/azure-data-studio/what-is) ou o [SSMS](https://docs.microsoft.com/sql/ssms/sql-server-management-studio-ssms) (SQL Server Management Studio).
## <a name="sign-in-to-the-azure-portal"></a>Entre no Portal do Azure
Entre no [Portal do Azure](https://portal.azure.com/).
## <a name="import-the-sample-database"></a>Importar o banco de dados de exemplo
O conjunto de dados de exemplo usado neste tutorial foi salvo em um arquivo de backup de banco de dados **.bacpac** para você baixar e usar.
1. Baixe o arquivo [TutorialDB.bacpac](https://sqlchoice.blob.core.windows.net/sqlchoice/static/TutorialDB.bacpac).
1. Siga as instruções em [Importar um arquivo BACPAC para criar um Banco de Dados SQL do Azure](https://docs.microsoft.com/azure/sql-database/sql-database-import) usando estes detalhes:
* Importar do arquivo **TutorialDB.bacpac** que você baixou
* Durante a versão prévia pública, escolha a configuração **Gen5/vCore** para o novo banco de dados
* Nomeie o novo banco de dados "TutorialDB"
## <a name="load-the-data-into-a-data-frame"></a>Carregue os dados em um dataframe
Para usar os dados no R, é necessário carregá-los do Banco de Dados SQL do Azure para o dataframe (`rentaldata`).
Crie um novo arquivo RScript no RStudio e execute o script a seguir. Substitua **Servidor**, **UID** e **PWD** com suas próprias informações de conexão.
```r
#Define the connection string to connect to the TutorialDB database
connStr <- paste("Driver=SQL Server",
"; Server=", "<Azure SQL Database Server>",
"; Database=TutorialDB",
"; UID=", "<user>",
"; PWD=", "<password>",
sep = "");
#Get the data from the table
SQL_rentaldata <- RxSqlServerData(table = "dbo.rental_data", connectionString = connStr, returnDataFrame = TRUE);
#Import the data into a data frame
rentaldata <- rxImport(SQL_rentaldata);
#Take a look at the structure of the data and the top rows
head(rentaldata);
str(rentaldata);
```
Você deverá ver resultados semelhantes ao seguinte.
```results
Year Month Day RentalCount WeekDay Holiday Snow
1 2014 1 20 445 2 1 0
2 2014 2 13 40 5 0 0
3 2013 3 10 456 1 0 0
4 2014 3 31 38 2 0 0
5 2014 4 24 23 5 0 0
6 2015 2 11 42 4 0 0
'data.frame': 453 obs. of 7 variables:
$ Year : int 2014 2014 2013 2014 2014 2015 2013 2014 2013 2015 ...
$ Month : num 1 2 3 3 4 2 4 3 4 3 ...
$ Day : num 20 13 10 31 24 11 28 8 5 29 ...
$ RentalCount: num 445 40 456 38 23 42 310 240 22 360 ...
$ WeekDay : num 2 5 1 2 5 4 1 7 6 1 ...
$ Holiday : int 1 0 0 0 0 0 0 0 0 0 ...
$ Snow : num 0 0 0 0 0 0 0 0 0 0 ...
```
## <a name="prepare-the-data"></a>Preparar os dados
Neste banco de dados de exemplo, a maior parte da preparação já foi feita, mas você fará uma preparação a mais.
Use o seguinte script do R para identificar as três colunas como *categorias* alterando os tipos de dados para *fator*.
```r
#Changing the three factor columns to factor types
rentaldata$Holiday <- factor(rentaldata$Holiday);
rentaldata$Snow <- factor(rentaldata$Snow);
rentaldata$WeekDay <- factor(rentaldata$WeekDay);
#Visualize the dataset after the change
str(rentaldata);
```
Você deverá ver resultados semelhantes ao seguinte.
```results
data.frame': 453 obs. of 7 variables:
$ Year : int 2014 2014 2013 2014 2014 2015 2013 2014 2013 2015 ...
$ Month : num 1 2 3 3 4 2 4 3 4 3 ...
$ Day : num 20 13 10 31 24 11 28 8 5 29 ...
$ RentalCount: num 445 40 456 38 23 42 310 240 22 360 ...
$ WeekDay : Factor w/ 7 levels "1","2","3","4",..: 2 5 1 2 5 4 1 7 6 1 ...
$ Holiday : Factor w/ 2 levels "0","1": 2 1 1 1 1 1 1 1 1 1 ...
$ Snow : Factor w/ 2 levels "0","1": 1 1 1 1 1 1 1 1 1 1 ...
```
Os dados agora estão preparados para treinamento.
## <a name="clean-up-resources"></a>Limpar recursos
Se você não pretende continuar este tutorial, exclua o banco de dados TutorialDB do seu servidor do Banco de Dados SQL do Azure.
No portal do Azure, siga estas etapas:
1. No menu à esquerda no portal do Azure, clique em **Todos os recursos** ou **Bancos de dados SQL**.
1. No campo **Filtrar por nome…** , digite **TutorialDB** e selecione sua assinatura.
1. Selecione seu banco de dados TutorialDB.
1. Na página **Visão Geral**, selecione **Excluir**.
## <a name="next-steps"></a>Próximas etapas
Na primeira parte desta série de tutoriais, você concluiu estas etapas:
* Importar um banco de dados de exemplo para um Banco de Dados SQL do Azure usando o R
* Carregar os dados do Banco de Dados SQL do Azure em um dataframe do R
* Preparar os dados no R identificando algumas colunas como categóricas
Para criar um modelo de machine learning que usa dados do banco de dados TutorialDB, siga a parte 2 desta série de tutoriais:
> [!div class="nextstepaction"]
> [Tutorial: Criar um modelo preditivo no R com os Serviços do Machine Learning do Banco de Dados SQL do Azure (versão prévia)](sql-database-tutorial-predictive-model-build-compare.md)
| 52.900585 | 352 | 0.719876 | por_Latn | 0.991078 |
b97b83f6fc47f3809403316d9be3d4b33d18eb1c | 1,923 | md | Markdown | _gallery/4-portraits.md | eye-division/tonyheath | d259779c8018a112f14fa71ced77e7bedfacdaae | [
"MIT"
] | null | null | null | _gallery/4-portraits.md | eye-division/tonyheath | d259779c8018a112f14fa71ced77e7bedfacdaae | [
"MIT"
] | null | null | null | _gallery/4-portraits.md | eye-division/tonyheath | d259779c8018a112f14fa71ced77e7bedfacdaae | [
"MIT"
] | null | null | null | ---
title: Portraits
description_markdown:
_gallery_date:
permalink: /portraits/
main_image_path:
images:
- image_path: '/assets/images/4e97166ceb77d.jpg'
image_title: "Untitled"
image_description: "H 18 x W 13 inches"
- image_path: '/assets/images/4eb4258becf79.jpg'
image_title: "Untitled"
image_description: "H 18 x 13 INCHES"
- image_path: '/assets/images/4eb4273fa1670.jpg'
image_title: "Untitled"
image_description: "H 18 x W 13 inches"
- image_path: '/assets/images/4eb4297c37fae.jpg'
image_title: "Untitled"
image_description: "H 24 x W 18 inches"
- image_path: '/assets/images/4eb42bbf4c000.jpg'
image_title: "Untitled"
image_description: "H 18 x W 13 inches"
- image_path: '/assets/images/4eb42c5849453.jpg'
image_title: "Untitled"
image_description: "H 18 x W 13 inches"
- image_path: '/assets/images/4eb42c83e496b.jpg'
image_title: "Untitled"
image_description: "H 18 x W 13 inches"
- image_path: '/assets/images/4eb42cb8467ae.jpg'
image_title: "Untitled"
image_description: "H 18 x W 13 inches"
- image_path: '/assets/images/4eb42ce1ccd15.jpg'
image_title: "Charlie in Mother's Hat"
image_description: "compressed charcoal
H 12 x W 9 inches"
- image_path: '/assets/images/4ec6546b9a23f.jpg'
image_title: "Untitled 020"
image_description: ""
- image_path: '/assets/images/4ec655efbebbc.jpg'
image_title: "Untitled 021"
image_description: ""
_options:
image_path:
width: 1200
height: 1200
resize_style: contain
mime_type: image/jpeg
main_image_path:
width: 1200
height: 800
resize_style: contain
mime_type: image/jpeg
_comments:
title: Gallery title
permalink: Be careful editing this
main_image_path: Image used to represent your gallery
images: Add and edit your gallery images here
image_description: May only be used in the close up of an image
---
| 31.52459 | 65 | 0.719189 | eng_Latn | 0.157237 |
b97bc522f6d9ba94aab9f02f163f84788e12c8e3 | 1,134 | md | Markdown | sdk-api-src/content/icm/nf-icm-cmcreatetransform.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | sdk-api-src/content/icm/nf-icm-cmcreatetransform.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | sdk-api-src/content/icm/nf-icm-cmcreatetransform.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
UID: NF:icm.CMCreateTransform
title: CMCreateTransform
description: Deprecated. There is no replacement API because this one was no longer being used. Developers of alternate CMM modules are not required to implement it.
tech.root: wcs
ms.date: 02/01/2021
targetos: Windows
req.assembly:
req.construct-type: function
req.ddi-compliance:
req.dll:
req.header: icm.h
req.idl:
req.include-header:
req.irql:
req.kmdf-ver:
req.lib:
req.max-support:
req.namespace:
req.redist:
req.target-min-winverclnt: Windows 10 Build 20348
req.target-min-winversvr: Windows 10 Build 20348
req.target-type:
req.type-library:
req.umdf-ver:
req.unicode-ansi:
topic_type:
- apiref
api_type:
api_location:
- icm.h
api_name:
- CMCreateTransform
f1_keywords:
- CMCreateTransform
- icm/CMCreateTransform
dev_langs:
- c++
---
## -description
Deprecated. There is no replacement API because this one was no longer being used. Developers of alternate CMM modules are not required to implement it.
## -parameters
### -param lpColorSpace
### -param lpDevCharacter
### -param lpTargetDevCharacter
## -returns
## -remarks
## -see-also
| 19.551724 | 165 | 0.753968 | eng_Latn | 0.815317 |
b97bd18a3b35590887a361c62adf07c8e6cc7cb9 | 5,804 | md | Markdown | pages/01shiny_basics.md | ucla-data-archive/elag2018-shiny | 08635fb694240470ca48fbdb63fe1e715ec07fb2 | [
"Apache-2.0",
"CC0-1.0"
] | null | null | null | pages/01shiny_basics.md | ucla-data-archive/elag2018-shiny | 08635fb694240470ca48fbdb63fe1e715ec07fb2 | [
"Apache-2.0",
"CC0-1.0"
] | null | null | null | pages/01shiny_basics.md | ucla-data-archive/elag2018-shiny | 08635fb694240470ca48fbdb63fe1e715ec07fb2 | [
"Apache-2.0",
"CC0-1.0"
] | null | null | null | ---
layout: page
title: DataViz and GGPLOT2 Basics
---
User interface
--------------
Our circulation statistics application needs a user interface. One of Shiny's strengths is the way in which it handles basic page layout for you without requiring you to write html and css. Let's take a look at our application with all but the basic Shiny structure stripped out.
library(shiny)
# Define UI ----
ui <- fluidPage(
)
# Define server logic ----
server <- function(input, output) {
}
# Run the app ----
shinyApp(ui = ui, server = server)
As you'd expect, the code in the ui section is what controls the layout of the user interface. The fluidPage function in Shiny builds a web page that automatically resizes to your browser window dimensions. To build a user interface, we add code elements as a comma-separated list of parameters passed to the fluidPage function. These code elements can be text items, formatting functions, or widget functions. Basically what these functions do is write the html and javascript that display information or accept input from the user. Lets look at our ui code again to see what this means and then make some modifications.
# Define UI for application that draws a histogram
ui <- fluidPage(
# Application title
titlePanel("Los Angeles Library Monthly Circulation Data"),
# Sidebar with a slider input for number of bins
sidebarLayout(
sidebarPanel(
sliderInput("bins",
"Number of bins:",
min = 1,
max = 50,
value = 30)
),
# Show a plot of the generated distribution
mainPanel(
plotOutput("distPlot")
)
)
)
In our interface, there are seven function calls. Can you find them?
The function call sliderInput is one of many widget functions available in Shiny. We'll explore more of these in the next lesson. For now, let's just concern ourselves with how to add text elements to the existing panels. To see how this works, we'll add some placeholder text to the sidebarPanel and mainPanel sections. Examine the code below, then add the same modifications to your application.
# Sidebar with a slider input for number of bins
sidebarLayout(
sidebarPanel(
"This is a a side bar panel",
sliderInput("bins",
"Number of bins:",
min = 1,
max = 50,
value = 30)
),
# Show a plot of the generated distribution
mainPanel(
"This is a main panel",
plotOutput("distPlot")
)
### Text formating
Be sure to include the comma after the quoted text and you can add as many comma-separated elements as you need. Generally, you'll want to format the code with html and Shiny allows you to do this in two ways. The cleanest way is to use one of the functions below that share the same name as their equivalent html tag. For example if you wanted to format the words "This is a a side bar panel" in a bold font, you write it like this: `strong("This is a a side bar panel")`.
| Function | Tag | Description |
|----------|------------|--------------------------------------------------|
| p | `<p>` | A paragraph of text |
| h1 | `<h1>` | A first level header |
| h2 | `<h2>` | A second level header |
| h3 | `<h3>` | A third level header |
| h4 | `<h4>` | A fourth level header |
| h5 | `<h5>` | A fifth level header |
| h6 | `<h6>` | A sixth level header |
| a | `<a>` | A hyper link |
| br | `<br>` | A line break (e.g. a blank line) |
| div | `<div>` | A division of text with a uniform style |
| span | `<span>` | An in-line division of text with a uniform style |
| pre | `<pre>` | Text ‘as is’ in a fixed width font |
| code | `<code>` | A formatted block of code |
| img | `<img>` | An image |
| strong | `<strong>` | Bold text |
| em | `<em>` | Italicized text |
| HTML | | Directly passes a character string as HTML code |
I also mentioned second way of adding formatting and that's done by wrapping a string of valid html in the HTML() function. In other words, `strong("This is a a side bar panel")` could also be written as `HTML("<strong>This is a a side bar panel</strong")`. This makes it possible to do more complex html formatting when needed. To practice these methods, add h1 tags to the text we added to the sidebar and main panels using the h1() function in one and the HTML() function in the other.
### Images
Images can be added to panels as well. In the examples folder, you'll find a file called rstudio.png. In order to use this in you application, you will need to copy it to a folder called www in your application folder. Create the folder, copy the file and then add the following as the last element in your mainPanel:
`img(src = "rstudio.png", height = 140, width = 400)`
> This lesson was derived from RStudio [Lesson 2: Build a user interface](https://shiny.rstudio.com/tutorial/written-tutorial/lesson2/)
| 55.27619 | 621 | 0.576499 | eng_Latn | 0.997925 |
b97bffea4bdcd9b6d3dfc7c98b6ab3017bb93095 | 24,502 | md | Markdown | _posts/2015-12-16-meteor-tutorial-2.md | 1996tianwen/blogways.github.io | 2c8dc8edd617b07e8d7281d958642f434791985a | [
"MIT"
] | 15 | 2015-04-29T08:29:31.000Z | 2018-01-08T01:48:21.000Z | _posts/2015-12-16-meteor-tutorial-2.md | 1996tianwen/blogways.github.io | 2c8dc8edd617b07e8d7281d958642f434791985a | [
"MIT"
] | 21 | 2015-01-28T02:41:25.000Z | 2018-09-10T03:13:22.000Z | _posts/2015-12-16-meteor-tutorial-2.md | 1996tianwen/blogways.github.io | 2c8dc8edd617b07e8d7281d958642f434791985a | [
"MIT"
] | 56 | 2015-01-27T07:56:17.000Z | 2021-08-25T01:12:01.000Z | ---
layout: post
category: Node.js
title: meteor入门学习笔记二：一个基础的例子
tags: ['meteor','javascript', '入门', '学习笔记']
author: 唐 治
description: Meteor是一个Javascript应用框架。可以轻松构建高品质的实时Web应用程序或移动端App。
---
{% raw %}
这几天在学习Meteor，当前版本为:`1.2.1`。学习的主要资料来自官网，笔记如下.
## 一、创建一个应用
在这里，我们将要创建一个简单的应用，管理一个任务清单。这样就可以和其他人一起使用这个任务清单，进行合作了。
为了创建这个应用，需要打开终端，输入命令：
```sh
meteor create simple-todos
```
这个命令会创建一个名为`simple-todos`的目录，目录里面有Meteor应用所需要的一些文件，列表如下：
```
simple-todos.js #一个被服务器和客户端都使用的javascript文件
simple-todos.html #一个html文件，里面定义了页面视图模版
simple-todos.css #一个css文件，定义了应用的式样
.meteor #一个隐藏目录，里面有meteor运行需要的文件
```
运行这个应用，可以输入命令：
```sh
cd simple-todos
meteor
```
好了，打开你的浏览器，然后输入`http://localhost:3000`。
如果你修改了simple-todos.html，你会发现几秒后，浏览器上打开的页面内容也会自动发生相应的变化。这就是Meteor所谓的“代码热部署”。
## 二、使用模版来定义页面视图
好了，我们继续制作我们的任务清单程序。
### 2.1 修改代码
我们用下面的代码替代之前Meteor默认生成的代码。
`simple-todos.html`的代码修改如下：
```html
<head>
<title>Todo List</title>
</head>
<body>
<div class="container">
<header>
<h1>Todo List</h1>
</header>
<ul>
{{#each tasks}}
{{> task}}
{{/each}}
</ul>
</div>
</body>
<template name="task">
<li>{{text}}</li>
</template>
```
`simple-todos.js`的代码修改如下：
```javascript
if (Meteor.isClient) {
// This code only runs on the client
Template.body.helpers({
tasks: [
{ text: "This is task 1" },
{ text: "This is task 2" },
{ text: "This is task 3" }
]
});
}
```
替换完上面的代码，静待几秒，浏览器中展现的内容就会发生变化，类似如下：
>
> # Todo List
>
> * This is task 1
> * This is task 2
> * This is task 3
>
挺有意思的，不是吗？好吧，让我们看看它们是怎么工作的。
### 2.2 Meteor使用HTML文件来定义模版
Meteor解析你的应用目录下的所有HTML文件。识别出三个顶级标签:`<head>`、`<body>`和`<template>`。
其中,`<head>`标签和`<body>`标签里的内容都会被发送到客户端页面中，对应的标签下面去。
而`<template>`标签里面的内容，会被编译成Meteor模版。Meteor模版或者被HTML中的`{{>templateName}}`引用，或者被JavaScript程序中的`Template.templateName`所引用。
### 2.3 给模版添加逻辑和数据
Meteor使用Spacebars来编译HTML文件中的代码。Spacebars用双括号将语句括起来，比如：`{{#each}}`和`{{#if}}`。使用这种方式给模版添加逻辑和数据。
我们可以借用`helpers`从JavsScript代码中把数据传给模版。在上面的代码中，我们在`Template.body`上定义了一个名为`tasks`的帮助器(helper)。它返回的是一个数组。在HTML的body标签内，我们可以使用`{{#each}}`来遍历整个数组，插入一个`task`模版来显示数组中的每个值。在`#each`语句块内，我们可以使用`{{text}}`来显示数组中每项的`text`属性值。
关于模版的更多内容：https://github.com/meteor/meteor/blob/devel/packages/spacebars/README.md
### 2.4 添加CSS
这个应用不添加额外的css式样，也可以正常运行，但是为了更加美观，我们给这个应用添加一些CSS式样。
`simple-todos.css`文件内容修改如下：
```css
/* CSS declarations go here */
body {
font-family: sans-serif;
background-color: #315481;
background-image: linear-gradient(to bottom, #315481, #918e82 100%);
background-attachment: fixed;
position: absolute;
top: 0;
bottom: 0;
left: 0;
right: 0;
padding: 0;
margin: 0;
font-size: 14px;
}
.container {
max-width: 600px;
margin: 0 auto;
min-height: 100%;
background: white;
}
header {
background: #d2edf4;
background-image: linear-gradient(to bottom, #d0edf5, #e1e5f0 100%);
padding: 20px 15px 15px 15px;
position: relative;
}
#login-buttons {
display: block;
}
h1 {
font-size: 1.5em;
margin: 0;
margin-bottom: 10px;
display: inline-block;
margin-right: 1em;
}
form {
margin-top: 10px;
margin-bottom: -10px;
position: relative;
}
.new-task input {
box-sizing: border-box;
padding: 10px 0;
background: transparent;
border: none;
width: 100%;
padding-right: 80px;
font-size: 1em;
}
.new-task input:focus{
outline: 0;
}
ul {
margin: 0;
padding: 0;
background: white;
}
.delete {
float: right;
font-weight: bold;
background: none;
font-size: 1em;
border: none;
position: relative;
}
li {
position: relative;
list-style: none;
padding: 15px;
border-bottom: #eee solid 1px;
}
li .text {
margin-left: 10px;
}
li.checked {
color: #888;
}
li.checked .text {
text-decoration: line-through;
}
li.private {
background: #eee;
border-color: #ddd;
}
header .hide-completed {
float: right;
}
.toggle-private {
margin-left: 5px;
}
@media (max-width: 600px) {
li {
padding: 12px 15px;
}
.search {
width: 150px;
clear: both;
}
.new-task input {
padding-bottom: 5px;
}
}
```
## 三、使用集合来存储数据
集合是Meteor用来存储持久化数据的方法。其特殊之处在于，它既可被服务端访问，也可被客户端访问。这样就很容易做到，无需编写大量服务端代码就可以实现页面逻辑。他们也可以自动更新，所以由集合支持的页面视图组件可以自动显示最新数据。
在你的JavaScript代码里，通过调用`MyCollection = new Mongo.Collection("my-collection");`，可以很容易地创建一个新的集合。在服务器端，这行代码会设置一个名为`my-collection`的MongoDB集合；在客户端，这行代码会创建一个缓存，这个缓存和服务器端集合存在连接。后面，我们会了解的更多详情，现在就让我们假设整个数据库都存在于客户端。
下面我们修改JavaScript代码，从数据库集合中获取任务：
```javascript
Tasks = new Mongo.Collection("tasks");
if (Meteor.isClient) {
// This code only runs on the client
Template.body.helpers({
tasks: function () {
return Tasks.find({});
}
});
}
```
使用上面代码后，静待几秒钟，等待Meteor“热部署”完成。我们会发现任务列表中的记录消失了，这是因为数据库集合是空的。我们需要向数据库集合中插入一些任务数据。
### 从服务器端数据库控制台插入任务数据
数据库集合里的数据被称为文档。下面，我们在服务器端使用数据库的控制台插入一些文档到任务集合中去。
打开一个新的终端页，进入应用所在目录，然后输入命令:
```sh
meteor mongo
```
当前控制台会连上应用的本地开发数据库，在数据库的交互模式下，输入命令：
```javascript
db.tasks.insert({ text: "Hello world!", createdAt: new Date() });
```
再看看浏览器，你将发现应用界面立刻显示出了新任务记录。你会发现我们在客户端和服务端之间并没有写什么连接代码，但是数据恰恰自动更新了。
在数据库控制台上，用相同的方法，再插入一些不同内容的任务记录。
下面，我们看看怎么给应用页面增加功能，不通过后端数据库控制台，直接通过前端页面增加任务记录。
## 四、通过页面添加任务
在这一环节，我们要提供一个输入框给用户，以便向任务清单中添加任务记录。
首先，我们在HTML里添加一个form。完整的simple-todos.html如下：
```html
<head>
<title>Todo List</title>
</head>
<body>
<div class="container">
<header>
<h1>Todo List</h1>
<form class="new-task">
<input type="text" name="text" placeholder="Type to add new tasks" />
</form>
</header>
<ul>
{{#each tasks}}
{{> task}}
{{/each}}
</ul>
</div>
</body>
<template name="task">
<li>{{text}}</li>
</template>
```
在Javascript代码中，我们需要增加对页面form的`submit`事件的监听方法。完整的simple-todos.js文件如下：
```javascript
Tasks = new Mongo.Collection("tasks");
if (Meteor.isClient) {
// This code only runs on the client
Template.body.helpers({
tasks: function () {
return Tasks.find({});
}
});
Template.body.events({
"submit .new-task": function (event) {
// Prevent default browser form submit
event.preventDefault();
// Get value from form element
var text = event.target.text.value;
// Insert a task into the collection
Tasks.insert({
text: text,
createdAt: new Date() // current time
});
// Clear form
event.target.text.value = "";
}
});
}
```
现在应用有了一个新的输入框。要添加任务记录，只需要在输入框输入内容，然后点击回车就好了。如果你另外打开一个浏览器窗口，并新窗口中打开应用，你会发现多个客户端上的任务记录是自动同步的！
###给模版绑定事件
给模版添加事件的方式如同helpers方法的使用：调用`Template.templateName.events(...)`，传入一个key-value字典类型参数。其中key描述监听的事件，其中value是事件句柄方法。
在上面的例子中，我们监听CSS选择器`.new-task`匹配的任意元素的`submit`事件。当用户在输入框内按下回车键时，将会触发这个事件，我们设置的事件方法就会被调用。
被调用的事件方法有一个输入参数`event`，这个参数包含了被触发的事件的一些信息。在这里，`event.target`是我们这个页面上的form元素，我们可以通过`event.target.text.value`来获取输入框中的输入值。你可以在浏览器的控制台，通过`console.log(event)`来查看`event`的各个属性。
最好，在这个事件方法的最后一行，我们清除了输入框中的内容，准备下一次输入。
###向集合中插入数据
在这个事件方法中，我们通过调用`Tasks.insert()`来向`tasks`集合中添加一条任务记录。我们不需要事先定义集合的结构，就可以向集合中的记录添加各种属性字段，比如：被创建的时间。
###排序查询结果
现在，所有新的任务记录都显示在页面的底部。这种体验不是太好，我们更希望先看到最新的任务。
我们可以利用`createdAt`字段来排序查询结果。所需做的，仅是给`find`方法添加一个排序选项。
```javascript
// This code only runs on the client
Template.body.helpers({
tasks: function () {
// Show newest tasks at the top
return Tasks.find({}, {sort: {createdAt: -1}});
}
});
```
## 五、已处理与删除任务
前面，我们学习了怎么向集合中插入数据，下面学习如何更新及删除数据。
我们先给`task`模版增加两个页面元素：一个复选框和一个删除按钮。
替换simple-todos.html文件中的`task`模版，内容如下:
```html
<template name="task">
<li class="{{#if checked}}checked{{/if}}">
<button class="delete">×</button>
<input type="checkbox" checked="{{checked}}" class="toggle-checked" />
<span class="text">{{text}}</span>
</li>
</template>
```
仅添加UI元素，页面发生了变化，但是新元素不能使用。我们需要添加相应的事件。
修改simple-todos.js文件，增加相关事件：
```javascript
Template.task.events({
"click .toggle-checked": function () {
// Set the checked property to the opposite of its current value
Tasks.update(this._id, {
$set: {checked: ! this.checked}
});
},
"click .delete": function () {
Tasks.remove(this._id);
}
});
```
好了，静待Meteor“热部署”后，点击页面上的复选框或者删除按钮。看看效果吧！
### 在事件方法中获取数据
在事件方法中，`this`指向当前这个任务对象。在数据库集合中，每个插入的文档都有一个唯一值`_id`字段，可以使用这个字段找到每个文档。我们可以使用`this.id`来获取当前任务记录的`_id`字段。一旦有了`_id`，那么我们就可以使用`update`或者`remove`方法来修改对应的任务记录了。
### 更新
集合的`update`方法有两个参数。第一个参数，是选择器，可以筛选出集合的子集；第二个参数是个更新参数，列出匹配的结果都做如何修改。
在上面这个例子中，选择器就是任务的`_id`字段值；更新参数使用`$set`去切换`checked`字段的值，来代表当前任务记录是否处理完成。
### 删除
集合的`remove`方法只有一个参数——选择器，它决定了集合中的哪项记录被删除。
###使用对象的属性(或者使用helpers)去添加/删除页面式样
你如果标记某些任务已经完成，你会发现被标记处理完成的任务都有一条删除线。这个效果由下面代码实现：
```html
<li class="{{#if checked}}checked{{/if}}">
```
如果任务的`checked`属性为`true`，那么`checked`式样类，就要加到这个`li`元素上。使用这个类，我们可以让完成处理的任务项很容易识别出来。
## 六、发布应用
现在，我们已经有了一个可以工作的任务清单应用了。我们可以把他分享给朋友们。Meteor很容易地支持把应用发布到网络上，让网络上的其他人使用。
进入你的应用所在目录，输入：
```sh
meteor deploy my_app_name.meteor.com
```
一旦你回答完所有交互问题，并上传成功。你就可以通过访问`http://my_app_name.meteor.com`，来在互联网上使用你的应用了。
## 七、在Android或iOS上运行你的应用
> 目前，Meteor不支持在Windows上创建移动端应用。如果，你是在Windows上使用Meteor，请跳过本节。
>
此处省去若干内容，有待日后另起篇章记录。
## 八、使用Session变量去存储临时的UI状态
在这里，我们要给应用增加一个客户端筛选功能，以便用户可以点击一个复选框去查看待处理的任务。我们学着在客户端使用`Session`变量去存储临时变化的状态。
首先，我们需要在页面模版中增加一个复选框，simple-todos.html页面中`body`模版的代码如下：
```html
<body>
<div class="container">
<header>
<h1>Todo List</h1>
<label class="hide-completed">
<input type="checkbox" checked="{{hideCompleted}}" />
Hide Completed Tasks
</label>
<form class="new-task">
<input type="text" name="text" placeholder="Type to add new tasks" />
</form>
</header>
<ul>
{{#each tasks}}
{{> task}}
{{/each}}
</ul>
</div>
</body>
```
接着，我们需要添加一个事件处理方法，在复选框的状态发生变化时，去更新`Session`变量。`Session`是一个非常好的可以存放临时UI状态的地方。如同集合一样，可以在helpers方法中被调用。
修改simple-todos.js文件中的`Template.body.events(...)`，修改后内容如下：
```javascript
Template.body.events({
"submit .new-task": function (event) {
// Prevent default browser form submit
event.preventDefault();
// Get value from form element
var text = event.target.text.value;
// Insert a task into the collection
Tasks.insert({
text: text,
createdAt: new Date() // current time
});
// Clear form
event.target.text.value = "";
},
"change .hide-completed input": function (event) {
Session.set("hideCompleted", event.target.checked);
}
});
```
现在，我们需要修改`Template.body.helpers`。下面这段代码增加了一个新的`if`语句块，去实现当复选框被选中时对任务清单的过滤；增加了一个新的方法，去获取Session变量中记录的复选框状态。
修改simple-todos.js文件中的`Template.body.helpers(...)`，修改为：
```javascript
Template.body.helpers({
tasks: function () {
if (Session.get("hideCompleted")) {
// If hide completed is checked, filter tasks
return Tasks.find({checked: {$ne: true}}, {sort: {createdAt: -1}});
} else {
// Otherwise, return all of the tasks
return Tasks.find({}, {sort: {createdAt: -1}});
}
},
hideCompleted: function () {
return Session.get("hideCompleted");
}
});
```
现在如果你选中复选框，那么任务清单中只显示没有完成的任务了！
### Session是客户端的一个响应式数据存储
截止目前，我们已经把所有数据都存储到集合中去了，当数据库集合中的数据发生变化，前端页面也会自动更新。这是因为Mongo的集合是Meteor公认的响应式数据源，这意味着，一旦其中的数据发生变化，Meteor就知道了。Session也同样如此，但它不和服务器端通讯，这点与集合不同。因此，Session非常适合存放UI的一些临时状态，比如上例中的复选框。如同集合，当Session变量发生变化后，我们无需编写太多的编码。仅需要在帮助器（helper)方法里调用`Session.get(...)`就足够了。
### 更多：显示待处理任务总数
现在我们写了一个查询，可以筛选待处理的任务，我们也可以使用同样的查询，去显示待处理任务的总数。在JavaScript文件中增加一个方法，修改HTML一行代码就可以实现了。
在simple-todos.js中修改`Template.body.helpers(...)`，增加一个`incompleteCount`方法，修改后的如下：
```javascript
Template.body.helpers({
tasks: function () {
if (Session.get("hideCompleted")) {
// If hide completed is checked, filter tasks
return Tasks.find({checked: {$ne: true}}, {sort: {createdAt: -1}});
} else {
// Otherwise, return all of the tasks
return Tasks.find({}, {sort: {createdAt: -1}});
}
},
hideCompleted: function () {
return Session.get("hideCompleted");
},
incompleteCount: function () {
return Tasks.find({checked: {$ne: true}}).count();
}
});
```
修改simple-todos.html文件，显示待处理记录总数:
```html
<h1>Todo List ({{incompleteCount}})</h1>
```
## 九、添加账号管理功能
Meteor自带一个账号系统，以及下拉式登录页面。可以让你的应用在几分钟内添加多用户功能。
为了可以使用账号系统以及相关的UI，我们需要添加相关的包。在你的应用所在目录，执行下面命令：
```sh
meteor add accounts-ui accounts-password
```
上述命令运行完后，原先的meteor服务会自动更新部署。我们继续下面操作。
在HTML文件中，复选框的正下方，添加一个用户登录代码，代码片段如下：
```html
<header>
<h1>Todo List ({{incompleteCount}})</h1>
<label class="hide-completed">
<input type="checkbox" checked="{{hideCompleted}}" />
Hide Completed Tasks
</label>
{{> loginButtons}}
<form class="new-task">
<input type="text" name="text" placeholder="Type to add new tasks" />
</form>
</header>
```
默认的登录界面是使用邮箱及密码登录，我们修改JavaScript文件，增加下面的代码来配置登录界面，使用用户名代替邮箱登录。
```javascript
Accounts.ui.config({
passwordSignupFields: "USERNAME_ONLY"
});
```
现在，使用者可以创建账号登录你的应用了！只是登录登出并没有什么效果。让我们增加两个功能：
1. 只对登陆用户显示新任务输入框；
2. 显示我们创建的每个任务
为此，我们需要在`task`集合中增加两个新的字段：
1. `owner` - 创建此任务的账号的`_id`；
2. `username` - 创建此任务的账号的`username`。我们直接把`username`保存在任务对象中，以便在显示任务时，无需每次都去关联账号信息查询用户名。
首先，我们在`submit .new-task`事件处理方法中，增加一些代码去保存新增的字段，修改的代码片段如下：
```javascript
Tasks.insert({
text: text,
createdAt: new Date(), // current time
owner: Meteor.userId(), // _id of logged in user
username: Meteor.user().username // username of logged in user
});
```
接着，修改HTML文件，增加一个`#if`判断语句，仅当账号登录后才显示任务添加框。simple-todos.html中相关代码片段如下：
```html
{{#if currentUser}}
<form class="new-task">
<input type="text" name="text" placeholder="Type to add new tasks" />
</form>
{{/if}}
```
最后，在每个任务信息的左边增加一个Spacebars语句去显示用户名(`username`)字段。
```html
<span class="text"><strong>{{username}}</strong> - {{text}}</span>
```
好了，大功告成了！
### 自动账号UI
如果应用添加了`accounts-ui`包，想增加一个下拉式登录窗口，只需使用`{{> loginButtons}}`语句来调用`loginButtons`模版。这个模版会自动判断支持哪些登录方式及显示相关的控制。在这个例子中，我们仅开启了账号密码(`accounts-password`)登录方式，所以下拉窗口中只有密码字段。如果你想做更多的尝试，你可以添加`accounts-facebook`包，来给你的应用开启Facebook账号登录功能，这样，Facebook的案例就会自动出现在下拉界面中了。
想尝试就执行下面的命令:
```sh
meteor add accounts-facebook
```
### 关于登录用户的更多信息
在HTML中，我们可以使用内置的帮助器(helper)`{{currentUser}}`去检查账号是否登录，及获取账号相关信息。比如：`{{currentUser.username}}`可以显示登录账号的用户名。
在JavaScript代码中，可以使用`Meteor.userId()`获取当前账号的`_id`，使用`Meteor.user()`获取整个账号信息。
## 十、使用`methods`方法实现安全控制
在这之前，应用的每个账号都能编辑数据库中的信息。这对一个内部小应用或者实例而言，可能没有什么问题。但任何一个实时应用都需要对它的数据进行权限控制。在Meteor中，最好的办法就是定义`methods`方法，代替客户端直接调用`insert`、`update`和`remove`方法。它将检查账号是否有权限进行当前操作，有权限则以客户端名义修改数据库中数据。
### 移除`insecure`包
每个新创建的Meteor工程都会默认添加`insecure`包。这个包容许用户从客户端修改数据库数据。
使用下面命令可以删除这个包：
```sh
meteor remove insecure
```
移除这个包后，再使用应用，你将发现输入框和按钮不再正常工作了。这是因为客户端所有数据库权限都被终止了。我们需要使用`methods`重写应用的部分功能。
### 定义methods
首先，我们需要定义一些方法.我们需要为在客户端执行的每个数据库操作定义一个方法。这些方法被定义在即被服务端执行，也被客户端执行的代码中。
修改simple-todos.js，增加以下代码片段：
```javascript
Meteor.methods({
addTask: function (text) {
// Make sure the user is logged in before inserting a task
if (! Meteor.userId()) {
throw new Meteor.Error("not-authorized");
}
Tasks.insert({
text: text,
createdAt: new Date(),
owner: Meteor.userId(),
username: Meteor.user().username
});
},
deleteTask: function (taskId) {
Tasks.remove(taskId);
},
setChecked: function (taskId, setChecked) {
Tasks.update(taskId, { $set: { checked: setChecked} });
}
});
```
好了，方法都定义好了。我们把之前对集合操作的代码都用这些方法替换。
修改后的完整的simple-todos.js文件内容如下:
```javascript
Tasks = new Mongo.Collection("tasks");
if (Meteor.isClient) {
// This code only runs on the client
Template.body.helpers({
tasks: function () {
if (Session.get("hideCompleted")) {
// If hide completed is checked, filter tasks
return Tasks.find({checked: {$ne: true}}, {sort: {createdAt: -1}});
} else {
// Otherwise, return all of the tasks
return Tasks.find({}, {sort: {createdAt: -1}});
}
},
hideCompleted: function () {
return Session.get("hideCompleted");
},
incompleteCount: function () {
return Tasks.find({checked: {$ne: true}}).count();
}
});
Template.body.events({
"submit .new-task": function (event) {
// Prevent default browser form submit
event.preventDefault();
// Get value from form element
var text = event.target.text.value;
// Insert a task into the collection
Meteor.call("addTask", text);
// Clear form
event.target.text.value = "";
},
"change .hide-completed input": function (event) {
Session.set("hideCompleted", event.target.checked);
}
});
Template.task.events({
"click .toggle-checked": function () {
// Set the checked property to the opposite of its current value
Meteor.call("setChecked", this._id, ! this.checked);
},
"click .delete": function () {
Meteor.call("deleteTask", this._id);
}
});
Accounts.ui.config({
passwordSignupFields: "USERNAME_ONLY"
});
}
Meteor.methods({
addTask: function (text) {
// Make sure the user is logged in before inserting a task
if (! Meteor.userId()) {
throw new Meteor.Error("not-authorized");
}
Tasks.insert({
text: text,
createdAt: new Date(),
owner: Meteor.userId(),
username: Meteor.user().username
});
},
deleteTask: function (taskId) {
Tasks.remove(taskId);
},
setChecked: function (taskId, setChecked) {
Tasks.update(taskId, { $set: { checked: setChecked} });
}
});
```
好了，我们的输入框和按钮又可以正常工作了！稍微总结一下本章节收获：
1. 当我们向数据库插入任务时，我们可以做一些安全性校验，比如：用户是否登录；创建时间、用户名等字段是否正确。使用者无法假冒任何人。
2. 当任务被私有化时，我们可以在`setChecked`和`deleteTask`方法中增加一些逻辑校验。（后文会介绍）
3. 客户端代码与数据库逻辑更加分离了。我们提炼一些方法可以在各处被调用，而不再是大量逻辑都放在页面的事件处理方法里了。
### Optimistic UI
那么我们为什么要同时定义我们的方法在客户端和服务器端？我们这样做是为了实现一个我们称之为“optimistic UI"的特效。
当我们在客户端使用`Meteor.call`调用一个方法时，Meteor会同时做两件事：
1. 客户端发送请求至服务器端，在一个安全的环境下去运行这个方法，如同AJAX请求一样工作；
2. 试图预测服务器端正常的处理结果，而在客户端模仿这个方法运行。
这就意味着，一个新创建的任务，还未从服务器端接收反馈结果，就立刻出现在页面上了。
如果服务端返回的结果和客户端模拟的结果一致，那么不再做任何处理；不一致，那么UI将按照服务端返回结果进行修正。
利用Meteor的方法（methods）和optimistic UI，我们可以鱼与熊掌兼得——服务端代码安全与无延迟交互！
## 十一、利用发布与订阅来过滤数据
我们已经把应用的所有敏感代码都移到了Methods里了，我们还需要了解一些Meteor其他的安全知识。截止目前，我们的工作都是基于假设整个数据库都在客户端的基础上的，这意味着，如果调用`Tasks.find()`，我们将从集合中查询所有数据。如果应用的使用者想存储一些隐私数据，这个机制就不合适了。我们需要一个方案去控制哪些数据可以发送到客户端数据库。
如同`insecure`包一样，Meteor新创建的每个新应用都会自带一个`autopublish`包。
我们删除这个包，看看发生了什么：
```sh
meteor remove autopublish
```
当应用刷新后，任务清单就空了。没有了这个包，我们需要显示地列出需要服务器端发送哪些数据到客户端。Meteor中实现这个功能的函数是`Meteor.publish`和`Meteor.subscrib`.
在simple-todos.js文件中增加以下代码片段:
```javascript
if (Meteor.isServer) {
// This code only runs on the server
Meteor.publish("tasks", function () {
return Tasks.find();
});
}
if (Meteor.isClient) {
// This code only runs on the client
Meteor.subscribe("tasks");
}
```
等待代码”热部署“后，页面的任务清单又出现了。
服务器端通过调用`Meteor.publish`方法，注册了一个名为`"tasks"`的发布。在客户端，使用这个发布名调用`Meteor.subscribe`方法，这个客户端就订阅了所有来自发布发布的数据，在这个例子中，就所有的任务清单。
为了真实地展示发布/订阅模式的强大之处，我们来实现一个功能，容许账号去标记任务为”私人的”，以便不被其他账号看见。
### 实现私人任务
首先，我们给任务记录增加一个名为"private"的属性，给用户提供一个按钮，去标记任务是否是私人的。这个按钮只显示给任务的所有者，并且将显示任务当前所处的状态。
另外，我们还要给任务记录增加一个式样类，用来标记这个任务是否为私人的。
simple-todos.html中task模版修改后的代码如下：
```html
<template name="task">
<li class="{{#if checked}}checked{{/if}} {{#if private}}private{{/if}}">
<button class="delete">×</button>
<input type="checkbox" checked="{{checked}}" class="toggle-checked" />
{{#if isOwner}}
<button class="toggle-private">
{{#if private}}
Private
{{else}}
Public
{{/if}}
</button>
{{/if}}
<span class="text"><strong>{{username}}</strong> - {{text}}</span>
</li>
</template>
```
结合页面所做的修改，我们需要同时修改三处JavaScript代码：
1. 增加一个名为`isOwner`的帮助器(helper)
```javascript
Template.task.helpers({
isOwner: function () {
return this.owner === Meteor.userId();
}
});
```
2. 增加一个名为`setPrivate`的Meteor方法。
```javascript
setPrivate: function (taskId, setToPrivate) {
var task = Tasks.findOne(taskId);
// Make sure only the task owner can make a task private发布
if (task.owner !== Meteor.userId()) {
throw new Meteor.Error("not-authorized");
}
Tasks.update(taskId, { $set: { private: setToPrivate } });
}
```
3. 增加一个按钮点击事件方法。
```javascript
"click .toggle-private": function () {
Meteor.call("setPrivate", this._id, ! this.private);
}
```
### 基于隐私状态有选择地发布任务
我们已经可以设置哪些任务是私人的了，我们继续完善我们的发布程序，只发送数据给有权限的用户浏览。
修改simple-todos.js中相关代码，相关代码片段如下：
```javascript
if (Meteor.isServer) {
// This code only runs on the server
// Only publish tasks that are public or belong to the current user
Meteor.publish("tasks", function () {
return Tasks.find({
$or: [
{ private: {$ne: true} },
{ owner: this.userId }
]
});
});
}
```
我们可以打开两个浏览器，使用不同的账号登录，来测试效果。
### 完善安全控制
为了完善我们的私人任务功能，我们需要给`deleteTask`和`setChecked`俩方法增加检查，以便任务的所有者可以删除或完成一个私人任务。
完整的simple-todos.js文件代码如下：
```javascript
Tasks = new Mongo.Collection("tasks");
if (Meteor.isServer) {
// This code only runs on the server
// Only publish tasks that are public or belong to the current user
Meteor.publish("tasks", function () {
return Tasks.find({
$or: [
{ private: {$ne: true} },
{ owner: this.userId }
]
});
});
}
if (Meteor.isClient) {
// This code only runs on the client
Meteor.subscribe("tasks");
Template.body.helpers({
tasks: function () {
if (Session.get("hideCompleted")) {
// If hide completed is checked, filter tasks
return Tasks.find({checked: {$ne: true}}, {sort: {createdAt: -1}});
} else {
// Otherwise, return all of the tasks
return Tasks.find({}, {sort: {createdAt: -1}});
}
},
hideCompleted: function () {
return Session.get("hideCompleted");
},
incompleteCount: function () {
return Tasks.find({checked: {$ne: true}}).count();
}
});
Template.body.events({
"submit .new-task": function (event) {
// Prevent default browser form submit
event.preventDefault();
// Get value from form element
var text = event.target.text.value;
// Insert a task into the collection
Meteor.call("addTask", text);
// Clear form
event.target.text.value = "";
},
"change .hide-completed input": function (event) {
Session.set("hideCompleted", event.target.checked);
}
});
Template.task.helpers({
isOwner: function () {
return this.owner === Meteor.userId();
}
});
Template.task.events({
"click .toggle-checked": function () {
// Set the checked property to the opposite of its current value
Meteor.call("setChecked", this._id, ! this.checked);
},
"click .delete": function () {
Meteor.call("deleteTask", this._id);
},
"click .toggle-private": function () {
Meteor.call("setPrivate", this._id, ! this.private);
}
});
Accounts.ui.config({
passwordSignupFields: "USERNAME_ONLY"
});
}
Meteor.methods({
addTask: function (text) {
// Make sure the user is logged in before inserting a task
if (! Meteor.userId()) {
throw new Meteor.Error("not-authorized");
}
Tasks.insert({
text: text,
createdAt: new Date(),
owner: Meteor.userId(),
username: Meteor.user().username
});
},
deleteTask: function (taskId) {
var task = Tasks.findOne(taskId);
if (task.private && task.owner !== Meteor.userId()) {
// If the task is private, make sure only the owner can delete it
throw new Meteor.Error("not-authorized");
}
Tasks.remove(taskId);
},
setChecked: function (taskId, setChecked) {
var task = Tasks.findOne(taskId);
if (task.private && task.owner !== Meteor.userId()) {
// If the task is private, make sure only the owner can check it off
throw new Meteor.Error("not-authorized");
}
Tasks.update(taskId, { $set: { checked: setChecked} });
},
setPrivate: function (taskId, setToPrivate) {
var task = Tasks.findOne(taskId);
// Make sure only the task owner can make a task private
if (task.owner !== Meteor.userId()) {
throw new Meteor.Error("not-authorized");
}
Tasks.update(taskId, { $set: { private: setToPrivate } });
}
});
```
> “注意现在任何人都可以删除公共任务，代码再做一些微调，就可以实现仅任务的所有者才能删除他们”
好了，我们完成了个人任务功能！现在我们的应用已经安全了，可以防止攻击者浏览或者修改他人的任务了！
{% endraw %} | 22.054005 | 252 | 0.671986 | yue_Hant | 0.525141 |
b97cf982137102f7790e33ca3c4d0fc4160fb55c | 1,201 | md | Markdown | _posts/2021-08-29-351456238.md | bookmana/bookmana.github.io | 2ed7b023b0851c0c18ad8e7831ece910d9108852 | [
"MIT"
] | null | null | null | _posts/2021-08-29-351456238.md | bookmana/bookmana.github.io | 2ed7b023b0851c0c18ad8e7831ece910d9108852 | [
"MIT"
] | null | null | null | _posts/2021-08-29-351456238.md | bookmana/bookmana.github.io | 2ed7b023b0851c0c18ad8e7831ece910d9108852 | [
"MIT"
] | null | null | null | ---
title: "난생처음 인공지능 입문"
date: 2021-08-29 03:40:09
categories: [국내도서, 컴퓨터-인터넷]
image: https://bimage.interpark.com/goods_image/6/2/3/8/351456238s.jpg
description: ● 이공계적인 어려움을 배제하여 누구나 쉽게 배울 수 있는 인공지능 입문서이 책은 IT 비전공자뿐만 아니라 중고등학생도 쉽게 배울 수 있는 이론 중심의 인공지능 입문서입니다. 인공지능의 개념을 실생활에서 접할 수 있는 사례를 중심으로 재미있는 삽화와 생생한 이미지를 통해 친절하게 설명
---
## **정보**
- **ISBN : 9791156645504**
- **출판사 : 한빛아카데미**
- **출판일 : 20210618**
- **저자 : 서지영**
------
## **요약**
● 이공계적인 어려움을 배제하여 누구나 쉽게 배울 수 있는 인공지능 입문서이 책은 IT 비전공자뿐만 아니라 중고등학생도 쉽게 배울 수 있는 이론 중심의 인공지능 입문서입니다. 인공지능의 개념을 실생활에서 접할 수 있는 사례를 중심으로 재미있는 삽화와 생생한 이미지를 통해 친절하게 설명합니다. 그리고 인공지능을 구현하기 위해 필요한 기술인 GPU, 5G, 클라우드, 사물인터넷, 빅데이터, 머신러닝, 인공신경망, 딥러닝 등을 자세히 알아봅니다. 또한 현재 구현되고 있는 인공지능 플랫폼과 서비스를 살펴보면서 미래에 인간이 인공지능에 어떻게 대처할 것인지 배워봅니다. 이 책을 끝까지 읽는다면 막연하기만 했던 인공지능을 누구나 쉽게 이해할 수 있을 것입니다. 본 도서는 대학 강의용 교재로 개발되었으므로 연습문제 해답은...
------
이공계적인 어려움을 배제하여 누구나 쉽게 배울 수 있는 인공지능 입문서
이 책은 IT 비전공자뿐만 아니라 중고등학생도 쉽게 배울 수 있는 이론 중심의 인공지능 입문서입니다. 인공지능의 개념을 실생활에서 접할 수 있는 사례를 중심으로 재미있는 삽화와 생생한 이미지를 통해 친절하게 설명합니다. 그리고...
------
난생처음 인공지능 입문
------
## **리뷰**
5.0 윤-영 인공지능에 대해 거시적으로 쉽게 이해하고 싶은 분들에게 적합한 책입니다. 400페이지가 넘는 분량이지만 빠른 시간 내에 끝까지 읽을 수 있었습니다. 비전공자의 입문서로 추천합니다. 2021.07.29 <br/> | 30.794872 | 405 | 0.673605 | kor_Hang | 1.00001 |
b97d14268b9e6f0a1007c843040c2798a9022b65 | 18,131 | md | Markdown | docs/vs-2015/misc/upgrading-custom-projects.md | silentwater/visualstudio-docs.de-de | 5a9caad5c1bee3041c2758238ffd04f4086a9bac | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/misc/upgrading-custom-projects.md | silentwater/visualstudio-docs.de-de | 5a9caad5c1bee3041c2758238ffd04f4086a9bac | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/misc/upgrading-custom-projects.md | silentwater/visualstudio-docs.de-de | 5a9caad5c1bee3041c2758238ffd04f4086a9bac | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Aktualisieren von benutzerdefinierten Projekten | Microsoft-Dokumentation
ms.date: 11/15/2016
ms.prod: visual-studio-dev14
ms.technology: devlang-csharp
ms.topic: conceptual
helpviewer_keywords:
- upgrading project systems
- projects [Visual Studio SDK], upgrading
- project system upgrades [Visual Studio]
ms.assetid: 262ada44-7689-44d8-bacb-9c6d33834d4e
caps.latest.revision: 11
manager: jillfra
ms.openlocfilehash: b222da27d07cc08774a525819edf2d462bd28844
ms.sourcegitcommit: 8b538eea125241e9d6d8b7297b72a66faa9a4a47
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 01/23/2019
ms.locfileid: "58961118"
---
# <a name="upgrading-custom-projects"></a>Aktualisieren von benutzerdefinierten Projekten
Wenn Sie die in der Projektdatei dauerhaft gespeicherten Informationen zwischen verschiedenen Visual Studio-Versionen Ihres Produkts ändern, müssen Sie das Durchführen eines Upgrades der Projektdatei von der alten auf die neue Version unterstützen. Zur Unterstützung der aktualisieren, die Ihnen ermöglicht, die Teilnahme an der **Visual Studio-Konvertierungs-Assistenten**, implementieren die <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgradeViaFactory> Schnittstelle. Diese Schnittstelle stellt das einzige verfügbare Verfahren zum Durchführen von Kopierupgrades dar. Das Upgrade des Projekts erfolgt im Rahmen des Öffnens der Projektmappe. Die <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgradeViaFactory>-Schnittstelle wird von der Projektfactory implementiert oder sollte zumindest über diese verfügbar sein.
Der alte Mechanismus, der die <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgrade>-Schnittstelle verwendet, wird noch unterstützt, doch wird dabei das abweichende Konzept verfolgt, das Upgrade des Projektsystems beim Öffnen des Projekts vorzunehmen. Die <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgrade>-Schnittstelle wird daher von der [!INCLUDE[vsprvs](../includes/vsprvs-md.md)]-Umgebung auch dann aufgerufen, wenn die <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgradeViaFactory>-Schnittstelle aufgerufen wird oder implementiert ist. Aufgrund dieses Ansatzes können Sie <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgradeViaFactory> verwenden, um die Kopie zu implementieren und nur Teile des Upgrades zu projizieren, wobei der Rest der Arbeit für die Ausführung an Ort und Stelle (also möglichst dem neuen Speicherort) durch die <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgrade>-Schnittstelle delegiert wird.
Eine beispielimplementierung der <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgrade>, finden Sie unter [VSSDK-Beispiele](../misc/vssdk-samples.md).
Im Rahmen von Projektupgrades stellen sich die folgenden Szenarien dar:
- Wenn die Datei ein neueres Format aufweist, als es vom Projekt unterstützt werden kann, muss eine Fehlermeldung zurückgegeben werden, aus der dieser Umstand hervorgeht. Dabei wird vorausgesetzt, dass die ältere Version Ihres Produkts – z. B. Visual Studio .NET 2003 – Code zum Überprüfen der Version enthält.
- Wenn das <xref:Microsoft.VisualStudio.Shell.Interop.__VSPPROJECTUPGRADEVIAFACTORYFLAGS>-Flag in der <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgradeViaFactory.UpgradeProject%2A>-Methode angegeben ist, wird das Upgrade vor dem Öffnen des Projekts als Upgrade an Ort und Stelle ausgeführt.
- Wenn das <xref:Microsoft.VisualStudio.Shell.Interop.__VSPPROJECTUPGRADEVIAFACTORYFLAGS>-Flag in der <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgradeViaFactory.UpgradeProject%2A>-Methode angegeben ist, wird das Upgrade als Kopierupgrade implementiert.
- Wenn das <xref:Microsoft.VisualStudio.Shell.Interop.__VSUPGRADEPROJFLAGS>-Flag im <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgrade.UpgradeProject%2A>-Aufruf angegeben ist, wurde der Benutzer von der Umgebung aufgefordert, nach dem Öffnen des Projekts ein Upgrade der Projektdatei an Ort und Stelle auszuführen. Beispielsweise fordert die Umgebung den Benutzer zum Upgrade auf, wenn der Benutzer eine ältere Version der Lösung öffnet.
- Wenn das <xref:Microsoft.VisualStudio.Shell.Interop.__VSUPGRADEPROJFLAGS>-Flag nicht im <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgrade.UpgradeProject%2A>-Aufruf angegeben ist, müssen Sie den Benutzer auffordern, ein Upgrade der Projektdatei auszuführen.
Die folgende Aufforderungsnachricht stellt ein Beispiel dar:
"Das Projekt '%1' wurde in einer älteren Version von Visual Studio erstellt. Wenn Sie es mit dieser Version von Visual Studio öffnen, können Sie es möglicherweise nicht mehr mit älteren Versionen von Visual Studio öffnen. Möchten Sie fortfahren und dieses Projekt öffnen?"
### <a name="to-implement-ivsprojectupgradeviafactory"></a>So implementieren Sie IVsProjectUpgradeViaFactory
1. Implementieren Sie die Methode der <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgradeViaFactory>-Schnittstelle, insbesondere die <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgradeViaFactory.UpgradeProject%2A>-Methode in Ihrer Projektfactoryimplementierung, oder machen Sie die Implementierungen von Ihrer Projektfactoryimplementierung aus aufrufbar.
2. Wenn Sie ein Upgrade an Ort und Stelle als Teil des Öffnens der Projektmappe ausführen möchten, geben Sie das Flag <xref:Microsoft.VisualStudio.Shell.Interop.__VSPPROJECTUPGRADEVIAFACTORYFLAGS> als Parameter von `VSPUVF_FLAGS` in Ihrer <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgradeViaFactory.UpgradeProject%2A>-Implementierung an.
3. Wenn Sie ein Upgrade an Ort und Stelle als Teil des Öffnens der Projektmappe ausführen möchten, geben Sie das Flag <xref:Microsoft.VisualStudio.Shell.Interop.__VSPPROJECTUPGRADEVIAFACTORYFLAGS> als Parameter von `VSPUVF_FLAGS` in Ihrer <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgradeViaFactory.UpgradeProject%2A>-Implementierung an.
4. Für die Schritte 2 und 3, die eigentlichen Dateiupgradeschritte, kann die Verwendung von <xref:Microsoft.VisualStudio.Shell.Interop.IVsQueryEditQuerySave2> wie im Abschnitt "Implementierung von `IVsProjectUpgade`" im Abschnitt unten beschrieben implementiert werden; alternativ können Sie das eigentliche Dateiupgrade an <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgrade> delegieren.
5. Verwenden Sie die Methoden von <xref:Microsoft.VisualStudio.Shell.Interop.IVsUpgradeLogger>, um mit Upgrades zusammenhängende Nachrichten für Benutzer mithilfe des Visual Studio-Migrations-Assistenten zu veröffentlichen.
6. Die <xref:Microsoft.VisualStudio.Shell.Interop.IVsFileUpgrade>-Schnittstelle wird verwendet, um jede Art von Dateiupgrade zu implementieren, die im Rahmen eines Projektupgrades erfolgen muss. Diese Schnittstelle wird nicht von <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgradeViaFactory> aufgerufen, sondern als Mechanismus für das Upgrade von Dateien bereitgestellt, die zum Projektsystem gehören, von denen das Projekthauptsystem jedoch möglicherweise keine unmittelbare Kenntnis hat. Diese Situation kann beispielsweise eintreten, wenn die compilerbezogenen Dateien und Eigenschaften nicht vom gleichen Entwicklungsteam wie der Rest des Projektsystems betreut werden.
## <a name="ivsprojectupgrade-implementation"></a>IVsProjectUpgrade-Implementierung
Wenn Ihr Projektsystem implementiert <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgrade> es kann nur nicht teilnehmen die **Visual Studio-Konvertierungs-Assistenten**. Aber selbst wenn Sie die <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgradeViaFactory>-Schnittstelle implementieren, können Sie das Dateiupgrade trotzdem an die <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgrade>-Implementierung delegieren.
#### <a name="to-implement-ivsprojectupgrade"></a>So implementieren Sie IVsProjectUpgrade
1. Wenn ein Benutzer versucht, ein Projekt zu öffnen, wird die <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgrade.UpgradeProject%2A>-Methode von der Umgebung aufgerufen, nachdem das Projekt geöffnet wurde und bevor andere Benutzeraktionen für das Projekt ausgeführt werden können. Wenn der Benutzer bereits aufgefordert wurde, ein Upgrade der Projektmappe auszuführen, wird im `grfUpgradeFlags`-Parameter das <xref:Microsoft.VisualStudio.Shell.Interop.__VSUPGRADEPROJFLAGS>-Flag übergeben. Wenn der Benutzer ein Projekt direkt, solche öffnet wie mit der **vorhandenes Projekt hinzufügen** Befehl ein, und klicken Sie dann die <xref:Microsoft.VisualStudio.Shell.Interop.__VSUPGRADEPROJFLAGS> Flag nicht übergeben, und das Projekt muss der Benutzer zum upgrade auffordern.
2. In Reaktion auf den <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgrade.UpgradeProject%2A>-Aufruf muss das Projekt bewerten, ob für die Projektdatei ein Upgrade ausgeführt werden muss. Wenn das Projekt für den Projekttyp kein Upgrade auf eine neue Version ausführen muss, kann es einfach das <xref:Microsoft.VisualStudio.VSConstants.S_OK>-Flag zurückgeben.
3. Wenn das Projekt ein Upgrade des Projekttyps auf eine neue Version vornehmen muss, muss es bestimmen, ob die Projektdatei durch Aufrufen der <xref:Microsoft.VisualStudio.Shell.Interop.IVsQueryEditQuerySave2.QueryEditFiles%2A>-Methode und Übergeben des Werts <xref:Microsoft.VisualStudio.Shell.Interop.tagVSQueryEditFlags> für den `rgfQueryEdit`-Parameter geändert werden kann. In diesem Fall muss das Projekt folgendes ausführen:
- Wenn der im `pfEditCanceled`-Parameter zurückgegebene `VSQueryEditResult`-Wert <xref:Microsoft.VisualStudio.Shell.Interop.tagVSQueryEditResult> ist, kann das Upgrade fortgesetzt werden, weil die Projektdatei geschrieben werden kann.
- Wenn der im `pfEditCanceled`-Parameter zurückgegebene `VSQueryEditResult`-Wert <xref:Microsoft.VisualStudio.Shell.Interop.tagVSQueryEditResult> ist und für den `VSQueryEditResult`-Wert das <xref:Microsoft.VisualStudio.Shell.Interop.tagVSQueryEditResultFlags>-Bit festgelegt ist, muss <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgrade.UpgradeProject%2A> einen Fehler zurückgeben, da der Benutzer das Berechtigungsproblem selbst lösen muss. Das Projekt sollte dann Folgendes ausführen:
Durch Aufrufen von <xref:Microsoft.VisualStudio.Shell.Interop.IVsUIShell.ReportErrorInfo%2A> dem Benutzer den Fehler melden und den <xref:Microsoft.VisualStudio.Shell.Interop.VSErrorCodes>-Fehlercode an <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgrade> zurückgeben.
- Wenn der `VSQueryEditResult`-Wert <xref:Microsoft.VisualStudio.Shell.Interop.tagVSQueryEditResult> ist und für den `VSQueryEditResultFlags`-Wert das <xref:Microsoft.VisualStudio.Shell.Interop.tagVSQueryEditResultFlags>-Bit festgelegt ist, sollte die Projektdatei durch Aufrufen von <xref:Microsoft.VisualStudio.Shell.Interop.IVsQueryEditQuerySave2.QueryEditFiles%2A> (<xref:Microsoft.VisualStudio.Shell.Interop.tagVSQueryEditFlags>, <xref:Microsoft.VisualStudio.Shell.Interop.tagVSQueryEditFlags>,...) ausgecheckt werden.
4. Wenn der <xref:Microsoft.VisualStudio.Shell.Interop.IVsQueryEditQuerySave2.QueryEditFiles%2A>-Aufruf der Projektdateien zum Auschecken der Datei und zum Abrufen der letzten Version führt, wird das Projekt entladen und erneut geladen. Die <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgrade.UpgradeProject%2A>-Methode wird erneut aufgerufen, sobald eine weitere Instanz des Projekts erstellt wird. Bei diesem zweiten Aufruf kann die Projektdatei auf den Datenträger geschrieben werden; es wird empfohlen, dass das Projekt eine Kopie der Projektdatei im vorherigen Format mit einer OLD-Erweiterung speichert, die für das Upgrade erforderlichen Änderungen vornimmt und die Projektdatei anschließend im neuen Format speichert. Wenn bei irgendeinem Teil des Upgradevorgangs ein Fehler auftritt muss auch hier die Methode den Fehler durch Zurückgeben von <xref:Microsoft.VisualStudio.Shell.Interop.VSErrorCodes> anzeigen. Dadurch wird das Projekt aus dem Projektmappen-Explorer entladen.
Für den Fall, dass der Aufruf der <xref:Microsoft.VisualStudio.Shell.Interop.IVsQueryEditQuerySave2.QueryEditFiles%2A>-Methode (mit dem Wert „ReportOnly“) die Flags <xref:Microsoft.VisualStudio.Shell.Interop.tagVSQueryEditResult> und <xref:Microsoft.VisualStudio.Shell.Interop.tagVSQueryEditResultFlags> zurückgibt, ist es wichtig, den gesamten Prozess zu verstehen, der in der Umgebung geschieht.
5. Der Benutzer versucht, die Projektdatei zu öffnen.
6. Die Umgebung ruft Ihre <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectFactory.CanCreateProject%2A>-Implementierung auf.
7. Wenn <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectFactory.CanCreateProject%2A> `true` zurückgibt, ruft die Umgebung Ihre <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectFactory.CanCreateProject%2A>-Implementierung auf.
8. Die Umgebung ruft Ihre <xref:Microsoft.VisualStudio.Shell.Interop.IPersistFileFormat.Load%2A>-Implementierung auf, um die Datei zu öffnen und das Projektobjekt zu initialisieren z. B. „Projekt1“.
9. Die Umgebung ruft Ihre `IVsProjectUpgrade::UpgradeProject` -Implementierung auf, um zu bestimmen, ob ein Upgrade der Projektdatei erforderlich ist.
10. Sie rufen <xref:Microsoft.VisualStudio.Shell.Interop.IVsQueryEditQuerySave2.QueryEditFiles%2A> auf und übergeben den Wert <xref:Microsoft.VisualStudio.Shell.Interop.tagVSQueryEditFlags> für den `rgfQueryEdit`-Parameter.
11. Die Umgebung gibt für `VSQueryEditResult` den Wert <xref:Microsoft.VisualStudio.Shell.Interop.tagVSQueryEditResult> zurück, und in `VSQueryEditResultFlags` wird das <xref:Microsoft.VisualStudio.Shell.Interop.tagVSQueryEditResultFlags>-Bit festgelegt.
12. Ihre <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgrade>-Implementierung ruft `IVsQueryEditQuerySave::QueryEditFiles` (<xref:Microsoft.VisualStudio.Shell.Interop.tagVSQueryEditFlags>, <xref:Microsoft.VisualStudio.Shell.Interop.tagVSQueryEditFlags>) auf.
Dieser Aufruf kann dazu führen, dass eine neue Kopie Ihrer Projektdatei ausgecheckt und die neueste Version abgerufen wird, wodurch es erforderlich wird, die Projektdatei neu zu laden. An diesem Punkt geschieht eins von zwei Dingen:
- Wenn Sie das erneute Laden des Projekts selbst vornehmen, ruft die Umgebung Ihre <xref:Microsoft.VisualStudio.Shell.Interop.IVsPersistHierarchyItem2.ReloadItem%2A>-Implementierung (VSITEMID_ROOT) auf. Wenn Sie diesen Aufruf empfangen, laden Sie die erste Instanz des Projekts (Projekt1) erneut, und fahren Sie mit dem Upgrade Ihrer Projektdatei fort. Die Umgebung weiß, dass Sie das erneute Laden des Projekts selbst übernehmen, wenn Sie für <xref:Microsoft.VisualStudio.Shell.Interop.IVsHierarchy.GetProperty%2A> (<xref:Microsoft.VisualStudio.Shell.Interop.__VSHPROPID>) `true` zurückgeben.
- Wenn Sie das erneute Laden des Projekts nicht selbst ausführen, geben Sie für <xref:Microsoft.VisualStudio.Shell.Interop.IVsHierarchy.GetProperty%2A> (<xref:Microsoft.VisualStudio.Shell.Interop.__VSHPROPID>) `false` zurück. In diesem Fall vor dem <xref:Microsoft.VisualStudio.Shell.Interop.IVsQueryEditQuerySave2.QueryEditFiles%2A>([QEF_ForceEdit_NoPrompting](assetId:///T:Microsoft.VisualStudio.Shell.Interop.tagVSQueryEditFlags?qualifyHint=False&autoUpgrade=True), [QEF_DisallowInMemoryEdits](assetId:///T:Microsoft.VisualStudio.Shell.Interop.tagVSQueryEditFlags?qualifyHint=False&autoUpgrade=True),) zurückgibt, erstellt die Umgebung als eine weitere neue Instanz des Projekts, z. B. "Projekt2", Die folgende:
1. Die Umgebung ruft <xref:Microsoft.VisualStudio.Shell.Interop.IVsHierarchy.Close%2A> für Ihr erstes Projektobjekt „Project1“ auf und versetzt dieses Objekt dadurch in den inaktiven Zustand.
2. Die Umgebung ruft Ihre `IVsProjectFactory::CreateProject` -Implementierung auf, um eine zweite Instanz Ihres Projekts zu erstellen, „Project2“.
3. Die Umgebung ruft Ihre `IPersistFileFormat::Load` -Implementierung auf, um die Datei zu öffnen und das zweite Projektobjekt, „Projekt2“, zu initialisieren.
4. Die Umgebung ruft `IVsProjectUpgrade::UpgradeProject` ein zweites Mal auf, um zu bestimmen, ob für das Projektobjekt ein Upgrade ausgeführt werden soll. Dieser Aufruf erfolgt jedoch für eine neue, zweite Instanz des Projekts, „Projekt2“. Dies ist das Projekt, das in der Projektmappe geöffnet ist.
> [!NOTE]
> Wenn die Instanz Ihres ersten Projekts, „Projekt1“, in den inaktiven Status versetzt wurde, müssen Sie vom ersten Aufruf <xref:Microsoft.VisualStudio.VSConstants.S_OK> an Ihre <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgrade.UpgradeProject%2A>-Implementierung zurückgeben. Eine Implementierung von [IVsProjectUpgrade::UpgradeProject](http://msdn.microsoft.com/385fd2a3-d9f1-4808-87c2-a3f05a91fc36) finden Sie unter `IVsProjectUpgrade::UpgradeProject`.
5. Sie rufen <xref:Microsoft.VisualStudio.Shell.Interop.IVsQueryEditQuerySave2.QueryEditFiles%2A> auf und übergeben den Wert <xref:Microsoft.VisualStudio.Shell.Interop.tagVSQueryEditFlags> für den `rgfQueryEdit`-Parameter.
6. Die Umgebung gibt <xref:Microsoft.VisualStudio.Shell.Interop.tagVSQueryEditResult> zurück, und das Upgrade kann fortgesetzt werden, weil die Projektdatei geschrieben werden kann.
Wenn Sie das Upgrade versäumen, geben Sie <xref:Microsoft.VisualStudio.Shell.Interop.VSErrorCodes> aus `IVsProjectUpgrade::UpgradeProject` zurück. Wenn für Sie kein Upgrade erforderlich ist oder Sie sich gegen das Upgrade entscheiden, behandeln Sie den `IVsProjectUpgrade::UpgradeProject` -Aufruf als nicht erfolgten Vorgang (No-Op). Wenn Sie <xref:Microsoft.VisualStudio.Shell.Interop.VSErrorCodes> zurückgeben, wird dem Projektmappe für Ihr Projekt ein Platzhalterknoten hinzugefügt.
## <a name="see-also"></a>Siehe auch
[Visual Studio-Konvertierungs-Assistenten](http://msdn.microsoft.com/4acfd30e-c192-4184-a86f-2da5e4c3d83c)
[Aktualisieren von Projektelementen](../misc/upgrading-project-items.md)
[Projekte](../extensibility/internals/projects.md) | 147.406504 | 995 | 0.824775 | deu_Latn | 0.959269 |
b97d8f5e4557b8ab1f1c7ecb0d75d5e707a5d90e | 515 | md | Markdown | Tags.md | ricmik/azureresourcegraphqueries | d929aad6804a4b6fe15fc100adc572aae2ca5e0b | [
"CC0-1.0"
] | null | null | null | Tags.md | ricmik/azureresourcegraphqueries | d929aad6804a4b6fe15fc100adc572aae2ca5e0b | [
"CC0-1.0"
] | null | null | null | Tags.md | ricmik/azureresourcegraphqueries | d929aad6804a4b6fe15fc100adc572aae2ca5e0b | [
"CC0-1.0"
] | null | null | null | # Tags
## Count of tags used on resource groups and resources
```kusto
resourcecontainers
| where isnotempty(tags)
| project tags
| mvexpand tags
| extend tagKey = tostring(bag_keys(tags)[0])
| extend tagValue = tostring(tags[tagKey])
| union (
resources
| where isnotempty(tags)
| project tags
| mvexpand tags
| extend tagKey = tostring(bag_keys(tags)[0])
| extend tagValue = tostring(tags[tagKey])
)
| where tagKey !startswith 'hidden-'
| summarize count() by tagKey
| order by count_
``` | 23.409091 | 54 | 0.699029 | eng_Latn | 0.83999 |
b97df007d9a083305a356eaa038669ff535c67b2 | 1,475 | markdown | Markdown | concerts/_posts/2015/10/2015-10-17-dublin-2.markdown | beccasafan/rbb | 93f67983b4facd25448bbb9a3649890d57ab1b9a | [
"MIT"
] | null | null | null | concerts/_posts/2015/10/2015-10-17-dublin-2.markdown | beccasafan/rbb | 93f67983b4facd25448bbb9a3649890d57ab1b9a | [
"MIT"
] | null | null | null | concerts/_posts/2015/10/2015-10-17-dublin-2.markdown | beccasafan/rbb | 93f67983b4facd25448bbb9a3649890d57ab1b9a | [
"MIT"
] | null | null | null | ---
title: Dublin 2
date: 2015-10-17 13:00
images: [horse.jpg, horse-closeup.jpg, pail-and-money.jpg]
props: [pink-hello-kitty-chair, horse, saddle-and-bridle, pail, zloty, nokia-phone, custom-label]
---
After the concert, it was discovered that the bears were not at the concert, but a setup was on display. The [pink chair]({{site.baseurl}}props/pink-hello-kitty-chair){:target="_blank"} and [horse]({{site.baseurl}}props/horse){:target="_blank"} were there. Hello, fandom freakout! The only other time we've seen this is [the show after the Babygate news broke]({{site.baseurl}}{% post_url 2015-07-15-seattle %}){:target="_blank"}. This time, it looks like the horse might have a [saddle]({{site.baseurl}}props/saddle-and-bridle){:target="_blank"} and we also have the [pail]({{site.baseurl}}props/pail){:target="_blank"} with [Zloty (Polish money)]({{site.baseurl}}props/zloty){:target="_blank"} in the pail. We've seen Zloty [before]({{site.baseurl}}props/zloty){:target="_blank"}. Fandom speculation and the Polish money again raises the question of the boys leaving Simon and his money.
There is also a [phone]({{site.baseurl}}props/cell-phone){:target="_blank"}, a [Nokia]({{site.baseurl}}props/nokia-phone){:target="_blank"} again. Still leak speculation? The phone has a custom [label]({{site.baseurl}}props/custom-label){:target="_blank"} that reads "Nut Tree". A number of possibilities have been mentioned, but nothing that seems to be popular for a consensus.
| 147.5 | 889 | 0.736949 | eng_Latn | 0.975244 |
b97e76d111c9537b473a3f8d323098eb9cf7c9b9 | 3,590 | md | Markdown | packages/documentation/docs/form-exclude-term.md | WangLarry/cofi | 011b9800776499aad851823894138e415283b3af | [
"MIT"
] | 121 | 2020-01-15T21:26:36.000Z | 2022-02-27T08:50:01.000Z | packages/documentation/docs/form-exclude-term.md | WangLarry/cofi | 011b9800776499aad851823894138e415283b3af | [
"MIT"
] | 44 | 2020-01-23T12:47:44.000Z | 2022-02-18T18:40:11.000Z | packages/documentation/docs/form-exclude-term.md | WangLarry/cofi | 011b9800776499aad851823894138e415283b3af | [
"MIT"
] | 10 | 2020-01-23T19:19:57.000Z | 2021-12-19T06:33:08.000Z | ---
id: exclude-term
title: Exclude Term
sidebar_label: Exclude Term
---
Define exclude term in a field in order to exclude it under some certain terms (i.e dynamic change of `excluded` flag). Form evaluates exclude term
during its lifecycle, and sets `excluded` result flag to a field.
## Field Exclude Term
Excluding a field means that the field is not rendered in the html and is not supposed to be part of the form validations under specific terms (for instance, if the user is not permitted to see / edit this field).
If the field is excluded - field validations are not evaluated, field.errors initiates to an empty array, and field.disabled is false.
### Behavior
Exclude term result is dynamic, if the field is excluded at a certain point, it can also be re-rendered if the term was dependant on another field's change. If the field is dependant on another field and is not rendered at the moment, and value changes on the dependent field, dependencies are reevaluated for the other field, and the exclude term is reevaluated as well. If the field's `excluded` flag is now false, the field is now included in the form, and is now rendered, and re-evaluated in terms of validations and disable term.
### Evaluation
Field exclude term is evaluated on `init`, `changeData`, and `changeValue` (only changed fields and their dependencies are evaluated on a value change) actions.
After evaluation an `excluded` flag is updated in the field (model.fields.someField.excluded).
### Definition
To define field exclude term - a definition is required in the `model.fields.someField` object, and implementation is
required in the `resources.terms` object.
`model.fields.someField.excludeTerm` and `resources.terms` objects structures are fully documented in [term documentation page](term).
### Shorthand
Definition shorthand for terms can be found in [definition shorthand documentation](definition-shorthand#terms).
### Built-in terms
A list of built-in terms are fully documented in [term documentation page](term#built-in-terms).
### Example
City field is excluded if user is not permitted and country is Mexico or Israel.
Term = (!isUserPermitted) and ((country equals `Mexico`) or (country equals `Israel`))
```javascript
import { isEqual } from 'lodash';
const model = {
// ...
fields: {
country: {
// ...
},
city: {
// ...
dependencies: ['country'], // define it in ordered that country's value will be injected to the exclude term func in - prop.dependencies
excludeTerm: {
operator: 'and', // conditional term
terms: [{
name: 'isUserPermitted', // logical term
not: true
}, {
operator: 'or', // conditional term
terms: [{
name: 'equals', // logical term
args: {
fieldId: 'country',
value: 'Mexico',
}
}, {
name: 'equals', // logical term
args: {
fieldId: 'country',
value: 'Israel',
}
}]
}],
},
}
},
};
// note - 'equals' is a built-in term - therefor not needed here.
// We added it here just for the example.
const resources = {
terms: {
isUserPermitted: {
func: (props) => {
let isUserPermitted;
// ....
return isUserPermitted;
},
},
equals: {
func: (props) => {
const dependantFieldValue = props.dependencies[props.args.fieldId];
return isEqual(dependantFieldValue, props.args.value);
}
}
}
};
```
| 34.519231 | 535 | 0.66351 | eng_Latn | 0.999476 |
b97e94dc9e1ada9977c582dcdb3466be35ebfe14 | 3,977 | md | Markdown | README.md | imranariffin/hashed-list | b002eb034b2f11f2518afb3fad8c75f1d047e824 | [
"MIT"
] | null | null | null | README.md | imranariffin/hashed-list | b002eb034b2f11f2518afb3fad8c75f1d047e824 | [
"MIT"
] | 3 | 2021-10-16T00:09:24.000Z | 2021-11-28T18:30:56.000Z | README.md | imranariffin/hashed-list | b002eb034b2f11f2518afb3fad8c75f1d047e824 | [
"MIT"
] | null | null | null | [](https://badge.fury.io/py/hashed-list)
[](https://pepy.tech/project/hashed-list)
# HashedList
A List with O(1) time complexity for `.index()` method, instead of O(N).
## Description
`HashedList` is a data structure that is pretty much a Python list, except that:
1. The method `.index(value)` is O(1) (Good)
2. It uses twice more memory due to indexing (Not good but still okay)
3. It takes more time than list during initialization due to hashing of each item
4. Items must be unique. It will raise `DuplicateValueError` if
duplicate item is provided
### Main use case:
You have a huge list of unique, ordered items that:
1. You may update the list (remove, insert, set value etc) from
time to time
2. You may get the index of a specific item in the list very often
In this case, using just a regular list definitely works but will cost
you O(N) each time you get the index of a specific item. Or, you can
maintain along the list a dictionary of item => index, but that will cost
you the burden of updating the dictionary everytime the list is updated.
HashedList will make the work easy for you.
## Installation
```bash
pip install hashed-list
```
## Usage
Simply instantiate it from an iterable, and use it as you normally would a Python list
```python
from hashed_list import HashedList
# From list
hashed_list_1 = HashedList(["a", "b", "c"])
# From generator
hashed_list_2 = HashedList(x for x in range(100) if x % 2 == 0)
# From sequence
hashed_list_3 = HashedList(range(1, 100, 2))
# Exceptions
from hashed_list import DuplicateValueError
try:
hashed_list_4 = HashedList([1, 1, 2])
except DuplicateValueError as e:
print(e)
# Use it like a normal Python list
hashed_list_1[0] # => "a"
len(hashed_list_3) == len(list(range(1, 100, 2))) # => True
hashed_list_1.index("c") # => 2
# The same for .extend(), .append(), .insert(), etc ...
```
## Simple benchmark
On a large list, `HashedList.index()` should be tens of times faster
than `list.index()` but you can try it yourself by copy-pasting the code below on
your Python shell
```python
from random import randint
import time
from hashed_list import HashedList
list_size = 999_999
random_values = [randint(list_size // 2, list_size) for _ in range(1000)]
print("Testing list.index()")
t0 = time.time()
very_huge_list = list(range(list_size))
[very_huge_list.index(random_value) for random_value in random_values]
d1 = time.time() - t0
del very_huge_list # Clear up unused memory
print(f"list.index() took {d1} seconds for {len(random_values)} calls")
# => list.index took 7.381884813308716 seconds for 1000 calls
print("Testing HashedList.index()")
t0 = time.time()
very_huge_hashed_list = HashedList(range(list_size))
# _ = very_huge_hashed_list.index(random_value)
[very_huge_hashed_list.index(random_value) for random_value in random_values]
d2 = time.time() - t0
del very_huge_hashed_list # Clear up unused memory
print(f"HashList.index() took {d2} seconds for {len(random_values)} calls")
# HashList.index took 0.17798161506652832 seconds for 1000 calls
# Result
print(f"HashList.index() is {d1 // d2} times faster than list.index()!")
# => HashList.index() is 41.0 times faster than list.index()!
```
## Caveats
1. `HashedList` consumes 2 times more memory than Python list
2. `HashedList` consumes more time during initialization due to hashing
Given these caveats, use `HashedArray` only when you know that `.index` is going to be used a lot.
## Development
To start developing for and contributing to this repository:
```bash
# Start a virtual environment
python -m venv .venv
# Install the package from source
python -m install -e .
# Run all tests
python -m unittest discover tests/
# Now you can start developing. Please see src/ and tests/
# folders for source code and tests respectively
```
## Links
* [PYPI](https://pypi.org/project/hashed-list/)
| 33.141667 | 98 | 0.740005 | eng_Latn | 0.968765 |
b97edc007b944772f091ee63ceb93b47eaf1ce46 | 374 | md | Markdown | README.md | fanoos/Python_CI_CD_Test | be2a93b5bb4c2585f4006befbe1f282b2a9e3f77 | [
"MIT"
] | null | null | null | README.md | fanoos/Python_CI_CD_Test | be2a93b5bb4c2585f4006befbe1f282b2a9e3f77 | [
"MIT"
] | 9 | 2019-08-29T13:14:00.000Z | 2021-02-02T22:15:19.000Z | README.md | fanoos/Python_CI_CD_Test | be2a93b5bb4c2585f4006befbe1f282b2a9e3f77 | [
"MIT"
] | null | null | null | # Python_CI_CD_Test
This is an example project demostrating how to use Devops (CircleCi,Travis,GitLab) in Python.
## Installation
Run the following to install:
'''python
pip install PythonDevOps
'''
...
## Usage
'''python
from helloworld import hello
# Generate hello message
hello()
## Usage
'''python
from calculator import add
# Generate Add Calculate
add(2,3)
| 12.896552 | 93 | 0.740642 | eng_Latn | 0.969847 |
b97f31d8f4045b001b3f6096c82138791170cebb | 8,466 | md | Markdown | docs/README.md | iotrentil/pushwoosh-react-native-plugin | c4f18caa88edc4facd4b15a01219a8b7b020ce48 | [
"MIT"
] | null | null | null | docs/README.md | iotrentil/pushwoosh-react-native-plugin | c4f18caa88edc4facd4b15a01219a8b7b020ce48 | [
"MIT"
] | null | null | null | docs/README.md | iotrentil/pushwoosh-react-native-plugin | c4f18caa88edc4facd4b15a01219a8b7b020ce48 | [
"MIT"
] | 2 | 2019-06-21T11:13:38.000Z | 2019-06-21T12:08:56.000Z | # Pushwoosh React Native Module #
Provides module for React Native to receive and handle push notifications for iOS and Android.
Example:
```js
var Pushwoosh = require('pushwoosh-react-native-plugin');
Pushwoosh.init({ "pw_appid" : "PUSHWOOSH_APP_ID" , "project_number" : "GOOGLE_PROJECT_NUMBER" });
Pushwoosh.register(
(token) => {
console.warn("Registered for push notifications with token: " + token);
},
(error) => {
console.warn("Failed to register for push notifications: " + error);
}
);
```
<style>
td {
background-color:#FFFFFF;
}
</style>
<br>
<h3>Summary</h3>
<hr />
<table width=100% style='background-color:#0EA7ED;'>
<tbody>
<tr>
<th align="left" colspan="2"><strong>Functions</strong></th>
</tr>
<tr class="even"><td><a href="#init">init(config, success, fail)</a></td></tr>
<tr class="odd"><td><a href="#register">register(success, fail)</a></td></tr>
<tr class="even"><td><a href="#unregister">unregister(success, fail)</a></td></tr>
<tr class="odd"><td><a href="#settags">setTags(tags, success, fail)</a></td></tr>
<tr class="even"><td><a href="#gettags">getTags(success, fail)</a></td></tr>
<tr class="odd"><td><a href="#getpushtoken">getPushToken(success)</a></td></tr>
<tr class="even"><td><a href="#gethwid">getHwid(success)</a></td></tr>
<tr class="even"><td><a href="#setuserid">setUserId(userId)</a></td></tr>
<tr class="even"><td><a href="#postevent">postEvent(event, attributes)</a></td></tr>
<tr class="even"><td><a href="#presentinboxui">presentInboxUI()</a></td></tr>
</tbody>
</table>
<hr />
### init
```js
init(config, success, fail)
```
Initializes Pushwoosh module with application id and google project number.
<table width=100% style='background-color:#0EA7ED;'>
<colgroup>
<col width="10%" />
<col width="20%" />
<col width="70%" />
</colgroup>
<tbody>
<tr>
<th align="left" colspan="3"><strong>Parameters</strong></th>
</tr>
<tr class="even"><td>object</td><td><b>config</b></td><td>Pushwoosh initialization config.</td></tr>
<tr class="even"><td>string</td><td><b>config.pw_appid</b></td><td>Pushwoosh application id.</td></tr>
<tr class="even"><td>string</td><td><b>config.project_number</b></td><td>GCM project number (for Android push notifications).</td></tr>
<tr class="even"><td>function</td><td><b>success</b></td><td>(optional) initialization success callback.</td></tr>
<tr class="even"><td>function</td><td><b>fail</b></td><td>(optional) initialization failure callback.</td></tr>
</tbody>
</table>
### register
```js
register(success, fail)
```
Registers current device for push notifications.
<table width=100% style='background-color:#0EA7ED;'>
<colgroup>
<col width="10%" />
<col width="20%" />
<col width="70%" />
</colgroup>
<tbody>
<tr>
<th align="left" colspan="3"><strong>Parameters</strong></th>
</tr>
<tr class="even"><td>function</td><td><b>success</b></td><td>(optional) registration success callback. Receives push token as parameter.</td></tr>
<tr class="even"><td>function</td><td><b>fail</b></td><td>(optional) registration failure callback.</td></tr>
</tbody>
</table>
NOTE: if user does not allow application to receive push notifications and `UIBackgroundModes remote-notificaion` is not set in **Info.plist** none of these callbacks will be called.
### unregister
```js
unregister(success, fail)
```
Unregisters current deivce from receiving push notifications.
<table width=100% style='background-color:#0EA7ED;'>
<colgroup>
<col width="10%" />
<col width="20%" />
<col width="70%" />
</colgroup>
<tbody>
<tr>
<th align="left" colspan="3"><strong>Parameters</strong></th>
</tr>
<tr class="even"><td>function</td><td><b>success</b></td><td>(optional) deregistration success callback.</td></tr>
<tr class="even"><td>function</td><td><b>fail</b></td><td>(optional) deregistration failure callback.</td></tr>
</tbody>
</table>
### setTags
```js
setTags(tags, success, fail)
```
Set tags associated with current device and application.
<table width=100% style='background-color:#0EA7ED;'>
<colgroup>
<col width="10%" />
<col width="20%" />
<col width="70%" />
</colgroup>
<tbody>
<tr>
<th align="left" colspan="3"><strong>Parameters</strong></th>
</tr>
<tr class="even"><td>object</td><td><b>tags</b></td><td>Tags associated with current device.</td></tr>
<tr class="even"><td>function</td><td><b>success</b></td><td>(optional) method success callback.</td></tr>
<tr class="even"><td>function</td><td><b>fail</b></td><td>(optional) method failure callback.</td></tr>
</tbody>
</table>
Example:
```js
pushNotification.setTags({ "string_tag" : "Hello world", "int_tag" : 42, "list_tag":["hello", "world"]});
```
### getTags
```js
getTags(success, fail)
```
Get tags associated with current device and application.
<table width=100% style='background-color:#0EA7ED;'>
<colgroup>
<col width="10%" />
<col width="20%" />
<col width="70%" />
</colgroup>
<tbody>
<tr>
<th align="left" colspan="3"><strong>Parameters</strong></th>
</tr>
<tr class="even"><td>function</td><td><b>success</b></td><td>(optional) method success callback. Receives object containing tags as parameter.</td></tr>
<tr class="even"><td>function</td><td><b>fail</b></td><td>(optional) method failure callback.</td></tr>
</tbody>
</table>
Example:
```js
Pushwoosh.getTags(
function(tags)
{
console.warn('tags for the device: ' + JSON.stringify(tags));
},
function(error)
{
console.warn('get tags error: ' + JSON.stringify(error));
}
);
```
### getPushToken
```js
getPushToken(success)
```
Returns push token or null if device is not registered for push notifications.
<table width=100% style='background-color:#0EA7ED;'>
<colgroup>
<col width="10%" />
<col width="20%" />
<col width="70%" />
</colgroup>
<tbody>
<tr>
<th align="left" colspan="3"><strong>Parameters</strong></th>
</tr>
<tr class="even"><td>function</td><td><b>success</b></td><td>Method success callback. Receives push token as parameter.</td></tr>
</tbody>
</table>
### getHwid
```js
getHwid(success)
```
Returns Pushwoosh HWID used for communications with Pushwoosh API.
<table width=100% style='background-color:#0EA7ED;'>
<colgroup>
<col width="10%" />
<col width="20%" />
<col width="70%" />
</colgroup>
<tbody>
<tr>
<th align="left" colspan="3"><strong>Parameters</strong></th>
</tr>
<tr class="even"><td>function</td><td><b>success</b></td><td>Method success callback. Receives Pushwoosh HWID as parameter.</td></tr>
</tbody>
</table>
### setUserId
```js
setUserId(userId)
```
Set User indentifier. This could be Facebook ID, username or email, or any other user ID.
This allows data and events to be matched across multiple user devices.
<table width=100% style='background-color:#0EA7ED;'>
<colgroup>
<col width="10%" />
<col width="20%" />
<col width="70%" />
</colgroup>
<tbody>
<tr>
<th align="left" colspan="3"><strong>Parameters</strong></th>
</tr>
<tr class="even"><td>string</td><td><b>userId</b></td><td>Identifier of currently logged in user</td></tr>
</tbody>
</table>
### postEvent
```js
postEvent(event, attributes)
```
Post events for In-App Messages. This can trigger In-App message display as specified in Pushwoosh Control Panel.
<table width=100% style='background-color:#0EA7ED;'>
<colgroup>
<col width="10%" />
<col width="20%" />
<col width="70%" />
</colgroup>
<tbody>
<tr>
<th align="left" colspan="3"><strong>Parameters</strong></th>
</tr>
<tr class="even"><td>string</td><td><b>event</b></td><td>Event name.</td></tr>
<tr class="even"><td>object</td><td><b>attributes</b></td><td>Additional event data.</td></tr>
</tbody>
</table>
Example:
```js
Pushwoosh.postEvent("buttonPressed", { "buttonNumber" : "4", "buttonLabel" : "Banner" })
```
### presentInboxUI
```js
presentInboxUI()
```
Opens [Inbox](https://www.pushwoosh.com/docs/message-inbox) screen.
Before using Message Inbox, please add node_modules/pushwoosh-react-native-plugin/src/ios/PushwooshInboxBundle.bundle to your project. Or, launch a script 'node node_modules/pushwoosh-react-native-plugin/scripts/add_inbox_ios_resources.js' to do it.
<table width=100% style='background-color:#0EA7ED;'>
<colgroup>
<col width="10%" />
<col width="20%" />
<col width="70%" />
</colgroup>
<tbody>
<tr>
<th align="left" colspan="3"><strong>Parameters</strong></th>
</tr>
<tr class="even"><td>string</td><td><b>event</b></td><td>Event name.</td></tr>
<tr class="even"><td>object</td><td><b>attributes</b></td><td>Additional event data.</td></tr>
</tbody>
</table>
| 26.210526 | 249 | 0.668202 | eng_Latn | 0.38603 |
b98012e9efae339d12534dae5e909307c2183c3c | 2,110 | md | Markdown | README.md | Adaptech/les-node-template | bd9647f34bfc263f7f21783b98fdc84b27a24ef6 | [
"BSD-3-Clause"
] | 2 | 2018-05-01T19:58:30.000Z | 2021-05-17T07:43:56.000Z | README.md | Adaptech/les-node-template | bd9647f34bfc263f7f21783b98fdc84b27a24ef6 | [
"BSD-3-Clause"
] | null | null | null | README.md | Adaptech/les-node-template | bd9647f34bfc263f7f21783b98fdc84b27a24ef6 | [
"BSD-3-Clause"
] | 2 | 2018-05-20T20:52:10.000Z | 2018-10-01T12:59:53.000Z | # les node template
## Requirements
* [NodeJS](https://nodejs.org) v6+
* [Yarn](https://yarnpkg.com) Latest
## Getting started
### Install node modules
yarn install
### Start the api and web
yarn start
API are located at: [http://localhost:3001/](http://localhost:3001/)
### Run the tests
yarn test
## Configuration
### EventStore
You can choose between: ges (Greg's EventStore) or memes (in-memory).
#### ges
You can configure the API to use [EventStore](https://eventstore.org/).
Change the eventStore section of your config file to:
```
"eventStore": {
"type": "ges",
"endPoint": "tcp://localhost:1113",
"credentials": {"username": "admin", "password": "changeit"}
}
```
Steps:
- Download tar.gz archive from the website
- Untar the archive (`tar -zxvf thearchive.tar.gz`) in the folder of your choice
- CD into extracted subfolder (EventStore-OSS-XXX-vX.X.X)
- Start the eventstore
- `./run-node.sh --memdb --run-projections=all` (start event store)
- Web interface at [http://localhost:2113](http://localhost:2113)
- login: admin pass: changeit (defaults)
#### memes
You can configure the API to store events in memory.
Change the eventStore section of your config file to:
```
"eventStore": {
"type": "memes"
}
```
### Read model storage
You can choose between: memdb (In memory), LevelDB, Postgres
#### memdb
You can configure the API to store read models in memory.
Change the readModelStore value of your config file to:
```
"readModelStore": "memdb"
```
#### LevelDB
You can configure the API to store read models with LevelDB.
Change the readModelStore value and add leveldb section in your config file to:
```
"readModelStore": "leveldb",
"leveldb": {
"dbDir": "/path/to/leveldb/storage/dir"
}
```
#### Postgres
You can configure the API to store read models with Postgres.
Change the readModelStore value and add postgres section in your config file to:
```
"readModelStore": "postgres",
"postgres": {
"host": "localhost",
"port": 5432,
"database": "vanillacqrs",
"user": "vanillacqrs",
"password": "vanillacqrs"
}
```
| 19.90566 | 80 | 0.68673 | eng_Latn | 0.719097 |
b9804c82e0fe1095f246bd93cf52f58060e404d0 | 6,660 | md | Markdown | README.md | pengdada/YoloOCLInference | 42c7cd66267ba215effaf0d83c04315e0a8bda50 | [
"Apache-2.0"
] | 15 | 2018-01-18T17:52:18.000Z | 2019-08-08T09:00:38.000Z | README.md | pengdada/YoloOCLInference | 42c7cd66267ba215effaf0d83c04315e0a8bda50 | [
"Apache-2.0"
] | 3 | 2018-04-14T19:01:34.000Z | 2018-05-19T05:36:03.000Z | README.md | pengdada/YoloOCLInference | 42c7cd66267ba215effaf0d83c04315e0a8bda50 | [
"Apache-2.0"
] | 9 | 2017-10-08T01:02:49.000Z | 2018-09-22T16:28:08.000Z | # YOLO OpenCL Inference Engine
A very light weight inference engine of **tiny-YOLO** object detection system for OpenCL based graphics cards/devices. For original work and CUDA implementation, refer to main author's page [here](https://pjreddie.com/darknet/).
Example output with display enabled|
:-------------------------:|
:|
## Background
This project has been deveoped to adapt **tiny-YOLO** object detection system for OpenCL enabled hardware and extend the inference engine to support FP16 and INT8 versions of target models in the future. The original implementation of YOLO & its variants specifically target NVIDIA cards and there have been many efforts to [make YOLO a part of well known deep neural network frameworks](https://www.google.co.uk/search?rlz=1C1CHBD_en-GBGB743GB743&q=tensorflow+yolo&spell=1&sa=X&ved=0ahUKEwip3fKSkN_WAhXmBsAKHX7oB-EQvwUIJSgA&biw=1920&bih=974) so that OpenCL enabled devices can be supported. The [original implementation](https://github.com/pjreddie/darknet) is an excellent reference point for someone to get started but both training and inference are tightly coupled there by leaving some room for simplifying inference engine, especially for 'tiny-yolo' variant. Additionally, support for tiny-YOLO in OpenCL would also be something many folks would be interested in and hence YoloOCLInference is written to detach the inference engine from the training logic and thereby making the engine simple, more focused towards performance & optimization.
## Key features
1. Achieves run time speeds of **~208 frames per second** on GTX 1080 Ti & **~73** frames per second on AMD RX580.
Inference speed - Display disabled|
:-------------------------:|
:|
2. Implemented entirely in C++. No depenceny on exsting DNN frameworks.
3. Optimizations include
* Use of Swap buffers in convolutional layers to clear outputs in activation stages.
* Addition of two im2col kernels for 3x3 & 1x1 variants
* Folding batch normalization into convolutional layer output calculations. See http://machinethink.net/blog/object-detection-with-yolo/
* Far less branched calculations in kernels comapred to original CUDA version
* Linear activation has been altogether disabled. Output stays untouched once bias is added to GEMM output.
* Loop unrolling where ever applicable.
4. Uses [cairo graphics](https://wiki.gnome.org/Projects/gtkmm/MSWindows) to render overlay of text
5. Far less memory footprint compared to original CUDA version.
## Dependencies
1. VC++ 2015
2. OpenCV 2.4.9
3. Gtkmm
4. NVIDIA Computing tool kit v8.0 (OpenCL libraries references)
5. [CLBLast](https://github.com/CNugteren/CLBlast) - Excellent BLAS library for OpenCL enabled hardware.
### Folder structure:
- YoloOCLInference\
-3rdparty\
-cairo\
-CLBlast\
-opencv\
-data\
-coco.names
-pedestrians.jpg
-tiny-yolo.cfg
-tiny-yolo.weights
-project
-YoloOCLInference.sln
...
-src
-Kernels\
-DeepNNFP32.cl
-DeepNNFP16.cl
-OpenCL
-OCLManager.cpp
...
-Utilities
....
-VideoProcessing
-YoloOCLDNN.cpp
-YoloOCLMain.cpp
The **3rdparty** folder contains readily usable headers & libraries that are required by the project to compile while the **data** folder contains tiny-yolo model configuration, weights & labels. The rest of the folders are self-explanatory with relvant solution files and source code. Upon successful compilation (either in Release or Debug mode), **build** directory will be created and all the necessary dependencies and data will be copied into the directory. It must be noted that **DeepNNFP32.cl** will need to be deleted in the **build** directory if you are hand-optimizing the kernel code. Once you are done with the changes to kernel code, building the project will copy the updated kernel code so the executable will be using it from then on during runtime.
## Usage
Open command prompt & browse to the build directory
Type
> YoloOCLInference.exe -input <image> -display <0/1> - save <0/1>
eg:
> YoloOCLInference.exe -input pedestrians.jpg -display 1 -save 0
The above command will make the executable load 'pedestrians.jpg' image available in build directory and runs inference on it. Here, the output display is enabled with option **-display 1**, so an OpenCV window will display the detected output as above. In case the **-save** option is set to 1, the frames with detections will be written to disk in a folder named **output** within build directory. If **-save** option is set to 0, the detection output frames with overlay will not be saved to disk.
Supposing display option is enabled, the OpenCV output window will pause for user input before proceeding onto running inference in next iteration.
If you prefer to let the engine free-flow without any display or saving options, the benchmarks reported here can be reproduced.
The relvant command in this case would be
> YoloOCLInference.exe -input pedestrians.jpg -display 0 -save 0
## Limitations
Following are some of the limitations in YoloOCLInference application
* Presently, only windows environment is supported.
* Only single image input is supported. Neither batch input nor video file input is possible.
* The application runs inference on the same image in a sequence for 1000 iterations. There are no control settings available.
* Object labels/classes are not displayed near the detections overlayed
* Sometimes, the application crashes on termination after completing execution and finally printing the inference statistics (time & speed).
* Sometimes, there is a scaling/shift error on the bounding boxes overlaid around objects.
## Future work
* Support cross compilation in Linux & Windows using CMake
* Support Video file and folder/batch input of images
* Support storing output video to disk
* Build a reusable API that supports RAW image input and file input (both video & image). The RAW image input is expected to be very useful in feeding hardware accelerated decoder output from either the same GPU (NVIDIA, AMD, ARM chips) or host CPU (Intel Quick Sync).
## Acknowledgements
Thanks to the authors of following repos.
* https://github.com/pjreddie/darknet
* https://github.com/CNugteren/CLBlast
* https://github.com/AlexeyAB/darknet
| 58.938053 | 1,152 | 0.740691 | eng_Latn | 0.986447 |
b9809f9c44a3e8b5fefd0e48ab591fd943a23314 | 87 | md | Markdown | src/n/normalizePath.i18n.md | WilcoBreedt/licia | 3b0249c0ceffce8e70c31737d98c543cbcd9827a | [
"MIT"
] | null | null | null | src/n/normalizePath.i18n.md | WilcoBreedt/licia | 3b0249c0ceffce8e70c31737d98c543cbcd9827a | [
"MIT"
] | null | null | null | src/n/normalizePath.i18n.md | WilcoBreedt/licia | 3b0249c0ceffce8e70c31737d98c543cbcd9827a | [
"MIT"
] | null | null | null | ## CN
标准化文件路径中的斜杠。
|参数名|类型|说明|
|-----|----|---|
|path|string|源路径|
|返回值|string|目标路径|
| 8.7 | 17 | 0.528736 | eng_Latn | 0.049575 |
b9813d0e58b8ae189bf9a643f1d214d945bb0422 | 2,457 | md | Markdown | AlchemyInsights/troubleshoot-sync-in-edge.md | isabella232/OfficeDocs-AlchemyInsights-pr.sl-SI | 11a4d6bfb0580342f538adc12818d1a86ddcdac3 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-19T19:07:51.000Z | 2020-05-19T19:07:51.000Z | AlchemyInsights/troubleshoot-sync-in-edge.md | MicrosoftDocs/OfficeDocs-AlchemyInsights-pr.sl-SI | feeebbc38a3aeca0b2a03f49e3cab735f0ea4069 | [
"CC-BY-4.0",
"MIT"
] | 3 | 2020-06-02T23:33:13.000Z | 2022-02-09T06:51:06.000Z | AlchemyInsights/troubleshoot-sync-in-edge.md | isabella232/OfficeDocs-AlchemyInsights-pr.sl-SI | 11a4d6bfb0580342f538adc12818d1a86ddcdac3 | [
"CC-BY-4.0",
"MIT"
] | 3 | 2019-10-11T19:12:12.000Z | 2021-10-09T10:38:29.000Z | ---
title: Odpravljanje težav s sinhronizacijo v Microsoft Edge
ms.author: pebaum
author: pebaum
manager: scotv
ms.date: 07/26/2021
ms.audience: Admin
ms.topic: article
ms.service: o365-administration
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Priority
ms.collection: Adm_O365
ms.custom:
- "9128"
- "9004429"
ms.openlocfilehash: c93fb4ab70114496d99eeba9b946106ce73b3736862bf8cb754f91b787a7f5ea
ms.sourcegitcommit: b5f7da89a650d2915dc652449623c78be6247175
ms.translationtype: MT
ms.contentlocale: sl-SI
ms.lasthandoff: 08/05/2021
ms.locfileid: "57813599"
---
# <a name="troubleshoot-problems-with-sync-in-microsoft-edge"></a>Odpravljanje težav s sinhronizacijo v Microsoft Edge
Poskusite s spodnjimi koraki:
1. Zaženite orodje [za odpravljanje težav z Microsoftovimi računi.](https://go.microsoft.com/fwlink/?linkid=2155661) Če težave s tem ne odpravite, nadaljujte z naslednjim korakom.
1. Varnostno jih varnostno jih varnostno izvajte:
Če Microsoft Edge neodzivno, namestite in zaženite Upravljanje priljubljenih v brskalniku [Edge](https://go.microsoft.com/fwlink/?linkid=2155764)– aplikacijo, ki vam pomaga upravljati priljubljene.
Če Microsoft Edge odziven, izberite **... (Nastavitve in drugo)** > **Priljubljene** > **Upravljanje priljubljenih** > **...** > **Izvozi priljubljene**.
1. Ponastavitev Microsoft Edge:
Če imate nameščen nov e-Microsoft Edge, izberite **... (Nastavitve in drugo)** > **Nastavitve** > **Ponastavitev nastavitev** > **Ponastavite nastavitve na privzete vrednosti in** nato izberite **Ponastavi**.
Če imate nameščeno starejšo različico programa Microsoft Edge, izberite **Nastavitve** Programi in funkcije , se pomaknite navzdol do možnosti > > Microsoft Edge, > označite jo, nato pa izberite Popravilo ali Ponastavitev naprednih možnosti .
Če težave s tem ne odpravite, nadaljujte z naslednjim korakom.
1. Poskusite znova registrirati aplikacijo: Upoštevajte druga možnost v možnostjo Ponovna namestitev **in** vnovična registracija vseh [vgrajenih Windows v aplikaciji Windows 10](https://go.microsoft.com/fwlink/?linkid=2146509).
Če težave s tem ne odpravite, nadaljujte z naslednjim korakom.
1. Zaženite namestitev Windows za popravilo predstavnosti: Prenesite in namestite orodje [za](https://go.microsoft.com/fwlink/?linkid=2146242)ustvarjanje medija ter izberite možnost za nadgradnjo. S tem nadgradite brskalnik na najnovejšo in naj stabilno različico.
| 51.1875 | 264 | 0.779813 | slv_Latn | 0.995924 |
b9816214476d6ae337725f7fd28a2735d34fa864 | 3,520 | markdown | Markdown | _posts/2017-11-25-ros-arduino-bridge-usage.markdown | Playfish/Playfish.github.io | 47cf156bbbe7648d1c1dad4fa7f486092e371a78 | [
"Apache-2.0"
] | null | null | null | _posts/2017-11-25-ros-arduino-bridge-usage.markdown | Playfish/Playfish.github.io | 47cf156bbbe7648d1c1dad4fa7f486092e371a78 | [
"Apache-2.0"
] | null | null | null | _posts/2017-11-25-ros-arduino-bridge-usage.markdown | Playfish/Playfish.github.io | 47cf156bbbe7648d1c1dad4fa7f486092e371a78 | [
"Apache-2.0"
] | 1 | 2018-11-19T02:05:07.000Z | 2018-11-19T02:05:07.000Z | ---
layout: post
title: "ros_arduino_bridge使用总结"
subtitle: "Usage summary for ros-arduino-bridge"
date: 2017-11-25 17:04:46
author: "Playfish"
header-img: "img/in-post/ros-arduino-bridge-usage/arduono_logo.jpeg"
header-mask: 0.3
catalog: true
tags:
- ROS1
- ros_arduino_bridge
---
> 说明:<br><br>
> 本文首发于 [CSDN](https://blog.csdn.net/u011118482/article/details/77528798)，转载请保留链接。
## 前言
关于ROS和Arduino通信方式，刚开始大多使用的是rosserial_arduino这个库，随后又诞生了一个新的库名为ros_arduino_bridge，两者对比如下：
* [rosserial_arduino][1]：由于将Arduino内的程序写成ros节点形式，所以能够快速的通过ROS控制Arduino，并且可以忽略通信协议层，与之相同的还有rosserial_stm32f1库，但是由于将Arduino作为ROS节点，不可避免的产生通信延时较大的问题，而且运行该库是通过rosserial_python包内的serial_node.py启动，该脚本使用了tcpip协议，有点大材小用，uno速率会跟不上，导致启动过程中一崩溃很难在连接上的问题，学习ROS可以使用。
* [ros_arduino_bridge][2]：是自定义通信协议方式来与Arduino进行通信，和大多数控制形式一致，将通信协议固定可以让初学者在使用过程中了解通信协议，由于是自定义通信协议形式，可以即插即用，和rosserial_arduino有本质差别，不过在使用过程中需要自己配置，所以需要有一定的arudino编程基础，早期的EAI dashgo D1采用的就是这种形式，使用这个库可以缩短底盘开发时间，并且Arduino有很多开源包供使用，会相对轻松一些。
关于如何使用rosserial_arduino_bridge，作者在github的[Readme][3]中写的很清楚，当然，是使用英文编写，如果大家想要查看中文，[这里][4]是一个很好的方式，我做的小车就是参考这篇博客，写的很清楚。
## 注意事项
### 编码器
关于如何使用我就不在赘述了，大家可以参考上面博客进行查看，作者代码在github上也有给出。查看作者代码发现作者应该用的Arduino mega板，电机控制器是L298N模块，我使用的是Arduino Uno板作为测试，电机控制器也选用的L298N，所以更改代码如下：
将[ros_arduino_bridge/ros_arduino_firmware/src/libraries/ROSArduinoBridge/encoder_driver.h][5]的内容：
```
#ifdef ARDUINO_MY_COUNTER
#define LEFT_ENC_A 2
#define LEFT_ENC_B 22
#define RIGHT_ENC_A 21
#define RIGHT_ENC_B 24
void initEncoders();
void leftEncoderEvent();
void rightEncoderEvent();
#endif
```
修改为
```
#ifdef ARDUINO_MY_COUNTER
#define LEFT_ENC_A 2
#define LEFT_ENC_B 4
#define RIGHT_ENC_A 3
#define RIGHT_ENC_B 11
void initEncoders();
void leftEncoderEvent();
void rightEncoderEvent();
#endif
```
关于这点需要注意，由于Arduino Uno只有两个中断，所以只能将两个中断分开给左编码器和右编码器，即Uno两个中断对应硬件分别为2和3，其中引脚2对应中断号为0，引脚3对应中断号为1，如下图
修改完成后，还需修改[ros_arduino_bridge/ros_arduino_firmware/src/libraries/ROSArduinoBridge/encoder_driver.ino][6]
将内容
```
void initEncoders(){
pinMode(LEFT_ENC_A, INPUT);
pinMode(LEFT_ENC_B, INPUT);
pinMode(RIGHT_ENC_A, INPUT);
pinMode(RIGHT_ENC_B, INPUT);
attachInterrupt(0, leftEncoderEvent, CHANGE);
attachInterrupt(2, rightEncoderEvent, CHANGE);
```
修改为
```
void initEncoders(){
pinMode(LEFT_ENC_A, INPUT);
pinMode(LEFT_ENC_B, INPUT);
pinMode(RIGHT_ENC_A, INPUT);
pinMode(RIGHT_ENC_B, INPUT);
attachInterrupt(0, leftEncoderEvent, CHANGE);
attachInterrupt(1, rightEncoderEvent, CHANGE);
```
注意变化，mega有四个中断，而Uno只有两个，所以需要修改为中断0、中断1。不然造成的结果是有一个电机编码器无数据，一直为0。
同样的，如果引脚类型不对应也会造成错误，如右电机，我将编码器A接上引脚3，编码器B接上引脚12，造成结果是右编码器数据一直在累加，即使电机没有转动，这是由于引脚3作为中断，类型为PWN引脚，而引脚12则为数字引脚，所以需要将编码器B接上引脚11，这是由于引脚11也为PWM类型，这样就不会造成错误。
[1]: http://wiki.ros.org/rosserial_arduino
[2]: http://wiki.ros.org/rosserial_arduino_bridge
[3]: https://github.com/hbrobotics/ros_arduino_bridge/blob/indigo-devel/README.md
[4]: blog.csdn.net/github_30605157/article/details/51344150/
[5]: https://github.com/Sunlcy/ros_arduino_bridge/tree/indigo-devel-saturnbot-pid-tuning/ros_arduino_firmware/src/libraries/ROSArduinoBridge/encoder_driver.h
[6]: https://github.com/Sunlcy/ros_arduino_bridge/tree/indigo-devel-saturnbot-pid-tuning/ros_arduino_firmware/src/libraries/ROSArduinoBridge/encoder_driver.ino
| 36.28866 | 253 | 0.766761 | yue_Hant | 0.475392 |
b981c586b41fd1473ae5f808f49b525946695d85 | 264 | md | Markdown | docs/modeling/includes/vssdk_current_short_md.md | galaxyuliana/visualstudio-docs.ko-kr | 0f07b2bdcdecc134d4f27d7da71521546f4046a6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/modeling/includes/vssdk_current_short_md.md | galaxyuliana/visualstudio-docs.ko-kr | 0f07b2bdcdecc134d4f27d7da71521546f4046a6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/modeling/includes/vssdk_current_short_md.md | galaxyuliana/visualstudio-docs.ko-kr | 0f07b2bdcdecc134d4f27d7da71521546f4046a6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
ms.topic: include
ms.openlocfilehash: dbf8bfcfb2b7f914360fd4d8ef4af2f17d8da811
ms.sourcegitcommit: 748d9cd7328a30f8c80ce42198a94a4b5e869f26
ms.translationtype: MT
ms.contentlocale: ko-KR
ms.lasthandoff: 07/15/2019
ms.locfileid: "68150287"
---
Visual Studio SDK | 26.4 | 60 | 0.837121 | yue_Hant | 0.151218 |
b981c85c000c58f8b1704240eb044af01a54dd55 | 16,106 | md | Markdown | articles/role-based-access-control/elevate-access-global-admin.md | Juliako/azure-docs.de-de | d2fd1cfbe4ccecc253b2f8400947f016af7a00f5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/role-based-access-control/elevate-access-global-admin.md | Juliako/azure-docs.de-de | d2fd1cfbe4ccecc253b2f8400947f016af7a00f5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/role-based-access-control/elevate-access-global-admin.md | Juliako/azure-docs.de-de | d2fd1cfbe4ccecc253b2f8400947f016af7a00f5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Erhöhen der Zugriffsrechte zum Verwalten aller Azure-Abonnements und Verwaltungsgruppen | Microsoft-Dokumentation
description: Hier erfahren Sie, wie Sie mit dem Azure-Portal oder der REST-API die Zugriffsrechte für einen globalen Administrator zum Verwalten aller Abonnements und Verwaltungsgruppen in Azure Active Directory erhöhen.
services: active-directory
documentationcenter: ''
author: rolyon
manager: mtillman
editor: bagovind
ms.assetid: b547c5a5-2da2-4372-9938-481cb962d2d6
ms.service: role-based-access-control
ms.devlang: na
ms.topic: conceptual
ms.tgt_pltfrm: na
ms.workload: identity
ms.date: 10/17/2019
ms.author: rolyon
ms.reviewer: bagovind
ms.openlocfilehash: 2fec017f80758dbcf2a155c3535b9a3e028e4bd9
ms.sourcegitcommit: b4f201a633775fee96c7e13e176946f6e0e5dd85
ms.translationtype: HT
ms.contentlocale: de-DE
ms.lasthandoff: 10/18/2019
ms.locfileid: "72592699"
---
# <a name="elevate-access-to-manage-all-azure-subscriptions-and-management-groups"></a>Erhöhen der Zugriffsrechte zum Verwalten aller Azure-Abonnements und Verwaltungsgruppen
Als globaler Administrator in Azure Active Directory (Azure AD) haben Sie möglicherweise keinen Zugriff auf alle Abonnements und Verwaltungsgruppen in Ihrem Verzeichnis. In diesem Artikel erfahren Sie, wie Sie Ihren Zugriff auf alle Abonnements und Verwaltungsgruppen erhöhen.
[!INCLUDE [gdpr-dsr-and-stp-note](../../includes/gdpr-dsr-and-stp-note.md)]
## <a name="why-would-you-need-to-elevate-your-access"></a>In welchen Fällen müssen Sie Ihren Zugriff erhöhen?
Wenn Sie globaler Administrator sind, müssen Sie unter Umständen folgende Aktionen ausführen:
- Wiedererlangen des Zugriffs auf ein Azure-Abonnement oder eine Verwaltungsgruppe, wenn ein Benutzer keinen Zugriff mehr hat
- Gewähren des Zugriffs auf ein Azure-Abonnement oder eine Verwaltungsgruppe für einen anderen Benutzer oder Sie selbst
- Anzeigen aller Azure-Abonnements oder Verwaltungsgruppen in einer Organisation
- Zulassen des Zugriffs auf alle Azure-Abonnements oder Verwaltungsgruppen für eine Automation-App (etwa eine App für die Rechnungsstellung oder Überwachung)
## <a name="how-does-elevate-access-work"></a>Wie erhöhe ich den Zugriff?
Azure AD und Azure-Ressourcen werden unabhängig voneinander geschützt. Das bedeutet, dass Azure AD-Rollenzuweisungen keinen Zugriff auf Azure-Ressourcen gewähren und Azure-Rollenzuweisungen keinen Zugriff auf Azure AD. Wenn Sie jedoch [globaler Administrator](../active-directory/users-groups-roles/directory-assign-admin-roles.md#company-administrator-permissions) in Azure AD sind, können Sie sich selbst Zugriff auf alle Azure-Abonnements und Verwaltungsgruppen in Ihrem Verzeichnis zuweisen. Verwenden Sie diese Funktion, wenn Sie keinen Zugriff auf Azure-Abonnementressourcen wie virtuelle Computer oder Speicherkonten haben und Sie Ihre globalen Administratorrechte verwenden möchten, um Zugriff auf diese Ressourcen zu erhalten.
Wenn Sie Ihre Zugriffsrechte erhöhen, wird Ihnen die Rolle [Benutzerzugriffsadministrator](built-in-roles.md#user-access-administrator) in Azure für den Stammbereich (`/`) zugewiesen. Auf diese Weise können Sie alle Ressourcen anzeigen und den Zugriff in jeder Abonnement- oder Verwaltungsgruppe im Verzeichnis zuweisen. Die Rollenzuweisung „Benutzerzugriffsadministrator“ kann mit PowerShell entfernt werden.
Sie sollten dieses erhöhte Zugriffsrecht entfernen, sobald Sie die Änderungen vorgenommen haben, die im Stammbereich erforderlich sind.
## <a name="azure-portal"></a>Azure-Portal
Führen Sie diese Schritte aus, um die Zugriffsrechte für einen globalen Administrator mit dem Azure-Portal zu erhöhen.
1. Melden Sie sich beim [Azure-Portal](https://portal.azure.com) oder [Azure Active Directory Admin Center](https://aad.portal.azure.com) als globaler Administrator an.
1. Klicken Sie in der Navigationsliste auf **Azure Active Directory** und dann auf **Eigenschaften**.
1. Wählen Sie unter **Zugriffsverwaltung für Azure-Ressourcen** die Option **Ja**.
Wenn Sie **Ja** wählen, wird Ihnen in Azure RBAC im Stammbereich (/) die Rolle „Benutzerzugriffsadministrator“ zugewiesen. Dadurch erhalten Sie die Berechtigung, Rollen in allen Azure-Abonnements und Verwaltungsgruppen zuzuweisen, die diesem Azure AD-Verzeichnis zugeordnet sind. Diese Option ist nur für Benutzer verfügbar, denen in Azure AD die Rolle des globalen Administrators zugewiesen wurde.
Wenn Sie **Nein** festlegen, wird die Rolle „Benutzerzugriffsadministrator“ in Azure RBAC aus Ihrem Benutzerkonto entfernt. Sie können dann keine Rollen mehr in allen Azure-Abonnements und Verwaltungsgruppen zuweisen, die diesem Azure AD-Verzeichnis zugeordnet sind. Sie können nur die Azure-Abonnements und Verwaltungsgruppen anzeigen und verwalten, für die Ihnen der Zugriff gewährt wurde.
> [!NOTE]
> Wenn Sie [Azure AD Privileged Identity Management (PIM)](../active-directory/privileged-identity-management/pim-configure.md) verwenden, wird dieser Umschalter von Ihrer Rollenzuweisung nicht in **Nein** geändert. Um den Zugriff mit den geringsten Rechten zu gewähren, empfehlen wir Ihnen das Festlegen dieses Umschalters auf **Nein**, bevor Sie Ihre Rollenzuweisung deaktivieren.
1. Klicken Sie auf **Speichern**, um Ihre Einstellung zu speichern.
Diese Einstellung ist keine globale Eigenschaft und gilt nur für den aktuell angemeldeten Benutzer. Sie können den Zugriff nicht für alle Mitglieder der globalen Administratorrolle erhöhen.
1. Melden Sie sich ab und wieder an, um den Zugriff zu aktualisieren.
Sie sollten jetzt auf alle Azure-Abonnements und Verwaltungsgruppen in Ihrem Verzeichnis zugreifen können. Sie werden feststellen, dass Ihnen die Rolle „Benutzerzugriffsadministrator“ im Stammbereich zugewiesen wurden.
1. Führen Sie die erforderlichen Änderungen für erhöhte Zugriffsrechte durch.
Weitere Informationen zum Zuweisen von Rollen finden Sie unter [Verwalten des Zugriffs mithilfe der RBAC und des Azure-Portals](role-assignments-portal.md). Wenn Sie Azure AD Privileged Identity Management (PIM) verwenden, lesen Sie [Ermitteln von Azure-Ressourcen zur Verwaltung in PIM](../active-directory/privileged-identity-management/pim-resource-roles-discover-resources.md) oder [Zuweisen von Azure-Ressourcenrollen in PIM](../active-directory/privileged-identity-management/pim-resource-roles-assign-roles.md).
1. Wenn Sie fertig sind, ändern Sie die Option **Zugriffsverwaltung für Azure-Ressourcen** wieder in **Nein**. Da es sich um eine benutzerspezifische Einstellung handelt, müssen Sie als der Benutzer angemeldet sein, der den Zugriff erhöht hat.
## <a name="azure-powershell"></a>Azure PowerShell
[!INCLUDE [az-powershell-update](../../includes/updated-for-az.md)]
### <a name="list-role-assignment-at-the-root-scope-"></a>Auflisten der Rollenzuweisung im Stammbereich (/)
Verwenden Sie den Befehl [Get-AzRoleAssignment](/powershell/module/az.resources/get-azroleassignment), um die Zuweisung der Rolle „Benutzerzugriffsadministrator“ für einen Benutzer im Stammbereich (`/`) aufzulisten.
```azurepowershell
Get-AzRoleAssignment | where {$_.RoleDefinitionName -eq "User Access Administrator" `
-and $_.SignInName -eq "<[email protected]>" -and $_.Scope -eq "/"}
```
```Example
RoleAssignmentId : /providers/Microsoft.Authorization/roleAssignments/098d572e-c1e5-43ee-84ce-8dc459c7e1f0
Scope : /
DisplayName : username
SignInName : [email protected]
RoleDefinitionName : User Access Administrator
RoleDefinitionId : 18d7d88d-d35e-4fb5-a5c3-7773c20a72d9
ObjectId : d65fd0e9-c185-472c-8f26-1dafa01f72cc
ObjectType : User
CanDelegate : False
```
### <a name="remove-a-role-assignment-at-the-root-scope-"></a>Entfernen einer Rollenzuweisung im Stammbereich (/)
Führen Sie die folgenden Schritte aus, um die Zuweisung der Rolle „Benutzerzugriffsadministrator“ für einen Benutzer im Stammbereich (`/`) zu entfernen.
1. Melden Sie sich als Benutzer an, der erhöhte Zugriffsrechte entfernen kann. Hierbei kann es sich um den Benutzer, der den Zugriff erhöht hat, oder einen anderen globalen Administrator, der über erhöhte Zugriffsrechte im Stammbereich verfügt, handeln.
1. Verwenden Sie den Befehl [Remove-AzRoleAssignment](/powershell/module/az.resources/remove-azroleassignment), um die Zuweisung der Rolle „Benutzerzugriffsadministrator“ zu entfernen.
```azurepowershell
Remove-AzRoleAssignment -SignInName <[email protected]> `
-RoleDefinitionName "User Access Administrator" -Scope "/"
```
## <a name="rest-api"></a>REST-API
### <a name="elevate-access-for-a-global-administrator"></a>Erhöhen der Zugriffsrechte für einen globalen Administrator
Führen Sie die folgenden grundlegenden Schritte aus, um mithilfe der REST-API die Zugriffsrechte für einen globalen Administrator zu erhöhen.
1. Rufen Sie mithilfe von REST `elevateAccess` auf. So erhalten Sie die Rolle des Benutzerzugriffsadministrators im Stammbereich (`/`).
```http
POST https://management.azure.com/providers/Microsoft.Authorization/elevateAccess?api-version=2016-07-01
```
1. Erstellen Sie eine [Rollenzuweisung](/rest/api/authorization/roleassignments), um eine beliebige Rolle in einem beliebigen Bereich zuzuweisen. Das folgende Beispiel zeigt die Eigenschaften für die Zuweisung der Rolle „{roleDefinitionID}“ im Stammbereich (`/`):
```json
{
"properties": {
"roleDefinitionId": "providers/Microsoft.Authorization/roleDefinitions/{roleDefinitionID}",
"principalId": "{objectID}",
"scope": "/"
},
"id": "providers/Microsoft.Authorization/roleAssignments/64736CA0-56D7-4A94-A551-973C2FE7888B",
"type": "Microsoft.Authorization/roleAssignments",
"name": "64736CA0-56D7-4A94-A551-973C2FE7888B"
}
```
1. Solange Sie Benutzerzugriffsadministrator sind, können Sie auch Rollenzuweisungen im Stammbereich (`/`) entfernen.
1. Entfernen Sie Ihre Berechtigungen als Benutzerzugriffsadministrator, bis sie wieder benötigt werden.
### <a name="list-role-assignments-at-the-root-scope-"></a>Auflisten der Rollenzuweisungen im Stammbereich (/)
Sie können alle Rollenzuweisungen für einen Benutzer im Stammbereich (`/`) auflisten.
- Rufen Sie [GET roleAssignments](/rest/api/authorization/roleassignments/listforscope) auf. Dabei entspricht `{objectIdOfUser}` der Objekt-ID des Benutzers, dessen Rollenzuweisungen Sie abrufen möchten.
```http
GET https://management.azure.com/providers/Microsoft.Authorization/roleAssignments?api-version=2015-07-01&$filter=principalId+eq+'{objectIdOfUser}'
```
### <a name="list-deny-assignments-at-the-root-scope-"></a>Auflisten von Ablehnungszuweisungen im Stammbereich (/)
Sie können alle Ablehnungszuweisungen für einen Benutzer im Stammbereich (`/`) auflisten.
- Rufen Sie „GET denyAssignments“ auf. Hierbei entspricht `{objectIdOfUser}` der Objekt-ID des Benutzers, dessen Ablehnungszuweisungen Sie abrufen möchten.
```http
GET https://management.azure.com/providers/Microsoft.Authorization/denyAssignments?api-version=2018-07-01-preview&$filter=gdprExportPrincipalId+eq+'{objectIdOfUser}'
```
### <a name="remove-elevated-access"></a>Entfernen der erhöhten Zugriffsrechte
Beim Aufruf von `elevateAccess` erstellen Sie eine Rollenzuweisung für sich selbst. Um diese Berechtigungen zu widerrufen, müssen Sie die Zuweisung entfernen.
1. Rufen Sie [GET roleDefinitions](/rest/api/authorization/roledefinitions/get) mit „User Access Administrator“ für `roleName` auf, um die Namens-ID der Rolle des Benutzerzugriffsadministrators abzurufen.
```http
GET https://management.azure.com/providers/Microsoft.Authorization/roleDefinitions?api-version=2015-07-01&$filter=roleName+eq+'User Access Administrator'
```
```json
{
"value": [
{
"properties": {
"roleName": "User Access Administrator",
"type": "BuiltInRole",
"description": "Lets you manage user access to Azure resources.",
"assignableScopes": [
"/"
],
"permissions": [
{
"actions": [
"*/read",
"Microsoft.Authorization/*",
"Microsoft.Support/*"
],
"notActions": []
}
],
"createdOn": "0001-01-01T08:00:00.0000000Z",
"updatedOn": "2016-05-31T23:14:04.6964687Z",
"createdBy": null,
"updatedBy": null
},
"id": "/providers/Microsoft.Authorization/roleDefinitions/18d7d88d-d35e-4fb5-a5c3-7773c20a72d9",
"type": "Microsoft.Authorization/roleDefinitions",
"name": "18d7d88d-d35e-4fb5-a5c3-7773c20a72d9"
}
],
"nextLink": null
}
```
Speichern Sie die ID aus dem `name`-Parameter (in diesem Fall `18d7d88d-d35e-4fb5-a5c3-7773c20a72d9`).
2. Außerdem müssen Sie die Rollenzuweisung für den Verzeichnisadministrator im Verzeichnisbereich auflisten. Listen Sie alle Zuweisungen im Verzeichnisbereich für `principalId` des Verzeichnisadministrators auf, der den Aufruf mit erhöhten Zugriffsrechten vorgenommen hat. Dadurch werden alle Zuweisungen im Verzeichnis für „objectid“ aufgelistet.
```http
GET https://management.azure.com/providers/Microsoft.Authorization/roleAssignments?api-version=2015-07-01&$filter=principalId+eq+'{objectid}'
```
>[!NOTE]
>Ein Verzeichnisadministrator sollte nicht über zu viele Zuweisungen verfügen. Wenn die obige Abfrage zu viele Zuweisungen zurückgibt, können Sie auch Abfragen für alle Zuweisungen auf der Verzeichnisbereichsebene durchführen und dann die Ergebnisse filtern: `GET https://management.azure.com/providers/Microsoft.Authorization/roleAssignments?api-version=2015-07-01&$filter=atScope()`
1. Mit den oben aufgeführten Aufrufe wird eine Liste von Rollenzuweisungen zurückgegeben. Suchen Sie die Rollenzuweisung, bei der der Bereich `"/"` lautet und `roleDefinitionId` mit der Rollennamen-ID endet, die Sie in Schritt 1 ermittelt haben, und `principalId` der Objekt-ID des Verzeichnisadministrators entspricht.
Beispielrollenzuweisung:
```json
{
"value": [
{
"properties": {
"roleDefinitionId": "/providers/Microsoft.Authorization/roleDefinitions/18d7d88d-d35e-4fb5-a5c3-7773c20a72d9",
"principalId": "{objectID}",
"scope": "/",
"createdOn": "2016-08-17T19:21:16.3422480Z",
"updatedOn": "2016-08-17T19:21:16.3422480Z",
"createdBy": "93ce6722-3638-4222-b582-78b75c5c6d65",
"updatedBy": "93ce6722-3638-4222-b582-78b75c5c6d65"
},
"id": "/providers/Microsoft.Authorization/roleAssignments/e7dd75bc-06f6-4e71-9014-ee96a929d099",
"type": "Microsoft.Authorization/roleAssignments",
"name": "e7dd75bc-06f6-4e71-9014-ee96a929d099"
}
],
"nextLink": null
}
```
Speichern Sie die ID aus dem Parameter `name` erneut ( in diesem Fall e7dd75bc-06f6-4e71-9014-ee96a929d099).
1. Verwenden Sie abschließend die Rollenzuweisungs-ID, um die durch `elevateAccess` hinzugefügte Zuweisung zu entfernen:
```http
DELETE https://management.azure.com/providers/Microsoft.Authorization/roleAssignments/e7dd75bc-06f6-4e71-9014-ee96a929d099?api-version=2015-07-01
```
## <a name="next-steps"></a>Nächste Schritte
- [Grundlegendes zu den verschiedenen Rollen in Azure](rbac-and-directory-admin-roles.md)
- [Verwalten des Zugriffs auf Azure-Ressourcen mit RBAC und der REST-API](role-assignments-rest.md)
| 59.431734 | 735 | 0.757792 | deu_Latn | 0.967338 |
b98278dc80e6c28aab447b792d5ec621b5c43f19 | 1,703 | md | Markdown | styleguide/src/system/components/navigation/Button/demo.md | Tirokk/Nitro-Web | a4f1eca3faa2ad3b358d24a5c6c6751d58161495 | [
"MIT"
] | null | null | null | styleguide/src/system/components/navigation/Button/demo.md | Tirokk/Nitro-Web | a4f1eca3faa2ad3b358d24a5c6c6751d58161495 | [
"MIT"
] | null | null | null | styleguide/src/system/components/navigation/Button/demo.md | Tirokk/Nitro-Web | a4f1eca3faa2ad3b358d24a5c6c6751d58161495 | [
"MIT"
] | null | null | null | ## Button types
Use a primary button to draw the users attention to important actions. Use default buttons for less important actions.
A danger button should be used only for destructive actions.
```html
<ds-button>Default</ds-button>
<ds-button primary>Primary</ds-button>
<ds-button secondary>Secondary</ds-button>
<ds-button danger>Danger</ds-button>
```
## Ghost buttons
Use a ghost button for secondary actions.
```html
<ds-button ghost>Default</ds-button>
<ds-button ghost primary>Primary</ds-button>
<ds-button ghost secondary>Secondary</ds-button>
<ds-button ghost danger>Danger</ds-button>
```
## Button sizes
Use different sizes to create hierarchy.
```html
<ds-button size="small">Small</ds-button>
<ds-button>Base</ds-button>
<ds-button size="large">Large</ds-button>
<ds-button size="x-large">very Large</ds-button>
```
## Button full width
```html
<ds-button fullwidth primary>Full Width</ds-button>
```
## Button states
A button can take different states.
```html
<ds-button>Default state</ds-button>
<ds-button disabled>Disabled state</ds-button>
<ds-button hover>Hover state</ds-button>
<ds-button loading>Loading state</ds-button>
```
## Icon buttons
Add an icon to a button to help the user identify the button's action.
```html
<ds-button icon="arrow-left" primary>Click me</ds-button>
<ds-button icon="arrow-right" right>Click me</ds-button>
<ds-button icon="plus" primary></ds-button>
<ds-button icon="plus" ghost></ds-button>
```
## Button as links
Provide a path to the button. You can pass a url string or a Vue router path object.
```html
<ds-button path="/navigation">Click me</ds-button>
<ds-button :path="{ name: 'Navigation' }">Click me</ds-button>
```
| 23.652778 | 118 | 0.726952 | eng_Latn | 0.649939 |
b9834c0cf6029c4f7f50b5065e35f97434d777c0 | 3,147 | md | Markdown | README.md | Gandi/hubot-restrict-ip | 96f6f07f2e836ef695257c153cae37f2bdab7b8d | [
"MIT"
] | 1 | 2016-08-23T20:01:32.000Z | 2016-08-23T20:01:32.000Z | README.md | Gandi/hubot-restrict-ip | 96f6f07f2e836ef695257c153cae37f2bdab7b8d | [
"MIT"
] | null | null | null | README.md | Gandi/hubot-restrict-ip | 96f6f07f2e836ef695257c153cae37f2bdab7b8d | [
"MIT"
] | null | null | null | Hubot Restrict IP Plugin
=================================
[](https://www.npmjs.com/package/hubot-restrict-ip)
[](https://www.npmjs.com/package/hubot-restrict-ip)
[](https://travis-ci.org/Gandi/hubot-restrict-ip)
[](https://gemnasium.com/Gandi/hubot-restrict-ip)
[](https://codeclimate.com/github/Gandi/hubot-restrict-ip/coverage)
[](https://nodei.co/npm/hubot-restrict-ip/)
This plugin is an Express middleware that will permit to filter who has access to the http endpoints of your hubot bot.
Installation
--------------
In your hubot directory:
npm install hubot-restrict-ip --save
Then add `hubot-restrict-ip` to `external-scripts.json`
Configuration
-----------------
- `HTTP_RESTRICTED` if set, protects all express endpoints by default, only the open_endpoints are reachable by everybody, and the ip_whitelist
- `HTTP_LOG_RESTRICTED` if set, hubot will log (warning level) the unauthorized calls
- `HTTP_IP_WHITELIST` only useful when `HTTP_RESTRICTED` is set
- `HTTP_IP_BLACKLIST` overwrite the whitelist if `HTTP_RESTRICTED` is set, and blocks ips listed anyways if not
- `HTTP_OPEN_ENDPOINTS` over-rules any other configuration to keep those endpoints open
- `HTTP_CLOSED_ENDPOINTS` if `HTTP_RESTRICTED` is set and `HTTP_OPEN_ENDPOINTS` are contradicted by `HTTP_CLOSED_ENDPOINTS`, the closed one wins.
- `HTTP_UNAUTHORIZED_MESSAGE` the message provided with the `401` status triggered when access is restricted by any rule.
With
- The IP lists are separated by `,` commas, and use CIDR for range definition like `192.168.0.0/24`. IP can also be IPv6 ranges.
- the endpoints are a list of endpoints, separated by commas too, like `/hubot/help` but it can also be a regexp like `/.*/help`
Testing
----------------
npm install
# will run make test and coffeelint
npm test
# or
make test
# or, for watch-mode
make test-w
# or for more documentation-style output
make test-spec
# and to generate coverage
make test-cov
# and to run the lint
make lint
# run the lint and the coverage
make
Changelog
---------------
All changes are listed in the [CHANGELOG](CHANGELOG.md)
Contribute
--------------
Feel free to open a PR if you find any bug, typo, want to improve documentation, or think about a new feature.
Gandi loves Free and Open Source Software. This project is used internally at Gandi but external contributions are **very welcome**.
Authors
------------
- [@mose](https://github.com/mose) - author and maintainer
License
-------------
This source code is available under [MIT license](LICENSE).
Copyright
-------------
Copyright (c) 2016 - Gandi - https://gandi.net
| 37.023529 | 165 | 0.714013 | eng_Latn | 0.927898 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.