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 listlengths 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 listlengths 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 listlengths 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
08b6f43e6392928e21bda7b7c3d0fcea72cde667 | 62 | md | Markdown | README.md | tracnet/tracnet-android | a74e85f66a855f95812d5ae716f3f288e613b026 | [
"MIT"
] | null | null | null | README.md | tracnet/tracnet-android | a74e85f66a855f95812d5ae716f3f288e613b026 | [
"MIT"
] | null | null | null | README.md | tracnet/tracnet-android | a74e85f66a855f95812d5ae716f3f288e613b026 | [
"MIT"
] | null | null | null | # tracnet-android
Android client app of track net application
| 20.666667 | 43 | 0.822581 | eng_Latn | 0.617812 |
08b71ec7ded80b38499ccb7af22858ae777e2de3 | 167 | md | Markdown | package/docs/docs/tools/git.md | zhuqinb/note | 136d8d2127c6bf684e51a885e3ed23d8e5f340aa | [
"MIT"
] | null | null | null | package/docs/docs/tools/git.md | zhuqinb/note | 136d8d2127c6bf684e51a885e3ed23d8e5f340aa | [
"MIT"
] | 8 | 2021-03-01T20:42:25.000Z | 2021-10-06T09:01:00.000Z | package/docs/docs/tools/git.md | wadeazhu/note | 136d8d2127c6bf684e51a885e3ed23d8e5f340aa | [
"MIT"
] | null | null | null | ### git 规则
.gitignore 只能忽略那些原来没有被 track 的文件，如果某些文件已经被纳入了版本管理中，则修改.gitignore 是无效的
解决办法
```shell
git rm -r --cached .
git add .
git commit -m 'update .gitignore'
```
| 13.916667 | 69 | 0.706587 | kor_Hang | 0.33865 |
08b7f1181f9afa45f2600700e48e53561f0a729b | 213 | md | Markdown | content/navbar.md | villevpe/static-site | 96dae2d23270f2ddb7edfbc7b5631c6786935a6d | [
"MIT"
] | null | null | null | content/navbar.md | villevpe/static-site | 96dae2d23270f2ddb7edfbc7b5631c6786935a6d | [
"MIT"
] | null | null | null | content/navbar.md | villevpe/static-site | 96dae2d23270f2ddb7edfbc7b5631c6786935a6d | [
"MIT"
] | null | null | null | ---
templateKey: navbar
items:
- label: Site name
href: '#home'
style: 'logo'
- label: Section 1
href: '#section1'
style: 'item'
- label: Section 2
href: '#section2'
style: 'item'
--- | 16.384615 | 21 | 0.56338 | eng_Latn | 0.223999 |
08b853b6fcb5c770586150fff0574da7de081015 | 4,567 | md | Markdown | packages/site/docs/api/graphFunc/find.en.md | SLin0218/G6 | 0a6f4770cb5ac6c2e830da1544327d9a8babd743 | [
"MIT"
] | 4,945 | 2017-02-26T14:14:57.000Z | 2019-11-28T03:10:32.000Z | packages/site/docs/api/graphFunc/find.en.md | SLin0218/G6 | 0a6f4770cb5ac6c2e830da1544327d9a8babd743 | [
"MIT"
] | 2,415 | 2019-11-28T04:46:50.000Z | 2022-03-31T08:23:02.000Z | packages/site/docs/api/graphFunc/find.en.md | SLin0218/G6 | 0a6f4770cb5ac6c2e830da1544327d9a8babd743 | [
"MIT"
] | 699 | 2019-11-28T05:10:46.000Z | 2022-03-27T08:36:02.000Z | ---
title: Find Element
order: 5
---
### graph.getNodes()
Get all the node items in the graph.
<span style="background-color: rgb(251, 233, 231); color: rgb(139, 53, 56)"><strong>⚠️Attention:</strong></span> it returns the items but not data models.
**Return**
- Type of the return value: Array;
- Return the node items in the graph.
**Usage**
```javascript
const nodes = graph.getNodes();
```
### graph.getEdges()
Get all the edge items in the graph.
<span style="background-color: rgb(251, 233, 231); color: rgb(139, 53, 56)"><strong>⚠️Attention:</strong></span> it returns the items but not data models.
**Return**
- Type of the return value: Array;
- Return the edge items in the graph.
**Usage**
```javascript
const edges = graph.getEdges();
```
### graph.getCombos()
Get all the combo items in the graph.
**Return**
- Type of the return value: Array;
- Return the combo items in the graph.
**Usage**
```javascript
const combos = graph.getCombos();
```
### graph.getComboChildren(combo)
Get the children of the `combo`.
**Parameters**
| Name | Type | Required | Description |
| ----- | --------------- | -------- | ---------------------------------------- |
| combo | string / ICombo | true | The ID or of the combo or the combo item |
**Return**
- Type of the return value: Object. Formated as:
```javascript
{
nodes: INode[],
edges: ICombo[]
}
```
- Return the children (sub nodes and combos) of the `combo`.
**Usage**
```
const elements: {
nodes: INode[],
combos: ICombo[]
} = graph.getComboChildren('combo1')
```
### graph.getNeighbors(node, type)
**Parameters**
| Name | Type | Required | Description |
| --- | --- | --- | --- |
| node | string / INode | true | node ID or the node instance |
| type | 'source' / 'target' / undefined | false | The type of the neighbors, 'source': only return the source nodes; 'target': only return the target nodes, undefined: return all of the neighbors |
**Return**
- Type of the return value: Array;
- Return a list of node items.
**Usage**
```javascript
const neighbors = graph.getNeighbors('node1', 'source');
```
### graph.find(type, fn)
Find single item according to a rule.
**Parameters**
| Name | Type | Required | Description |
| ---- | -------- | -------- | ---------------------------------------------- |
| type | string | true | Type of the item. Options: `'node'`, `'edge'`. |
| fn | Function | true | Rule for searching. |
**Return**
- Type of the return value: Object;
- If there are items that match the rule, return the first one. Return `undefined` otherwise.
**Usage**
```javascript
const findNode = graph.find('node', (node) => {
return node.get('model').x === 100;
});
```
### graph.findById(id)
Find an item by id.
**Parameters**
| Name | Type | Required | Description |
| ---- | ------ | -------- | ----------- |
| id | string | true | 元素 ID |
**Return**
- Type of the return value: Object;
- If there are items that match the rule, return the first one. Return `undefined` otherwise.
**Usage**
```javascript
const node = graph.findById('node');
```
### graph.findAll(type, fn)
Find all the items that match the rule.
**Parameters**
| Name | Type | Required | Description |
| ---- | -------- | -------- | -------------------------------------------------- |
| type | string | true | The type of the item. Options: `'node'`, `'edge'`. |
| fn | Function | true | Rule for searching. |
**Return**
- Type of the return value: Array;
- If there are items that match the rule, return all of them. Return `undefined` otherwise.
**Usage**
```javascript
const nodes = graph.findAll('node', (node) => {
return node.get('model').x;
});
```
### graph.findAllByState(type, state)
Find all the items whose value of state is true.
**Parameters**
| Name | Type | Required | Description |
| ----- | ------ | -------- | -------------------------------------------------- |
| type | string | true | The type of the item. Options: `'node'`, `'edge'`. |
| state | string | true | State for searching. |
**Return**
- Type of the return value: Array;
- Return all the items that match the state.
**Usage**
```javascript
// Find all the items whose 'selected' state is true
const nodes = graph.findAllByState('node', 'selected');
```
| 23.065657 | 198 | 0.559886 | eng_Latn | 0.772239 |
08b922e034dbedd15d4f4d6e839626f0d68339e4 | 367 | md | Markdown | ddj/simplified-chinese.md | karpalig/sbs | e3a23a0f99abf9dfff9d1fb07579eb83bf1fcaf2 | [
"Unlicense"
] | null | null | null | ddj/simplified-chinese.md | karpalig/sbs | e3a23a0f99abf9dfff9d1fb07579eb83bf1fcaf2 | [
"Unlicense"
] | null | null | null | ddj/simplified-chinese.md | karpalig/sbs | e3a23a0f99abf9dfff9d1fb07579eb83bf1fcaf2 | [
"Unlicense"
] | null | null | null | Title: Дао Дэ Цзин
Author: Laozi
Year: 400 BC
Language: Chinese
道可道，非常道。
名可名，非常名。
无名天地之始；
有名万物之母。
故常无欲，以观其妙；
常有欲，以观其徼。
此两者，同出而异名，同谓之玄。
玄之又玄，众妙之门。
---
天下皆知美之为美，斯恶已。
皆知善之为善，斯不善已。
故有无相生，难易相成，长短相较，高下相倾，音声相和，前后相随。
是以圣人处无为之事，行不言之教；
万物作焉而不辞，生而不有。
为而不恃，功成而弗居。
夫唯弗居，是以不去。
---
不尚贤，使民不争；
不贵难得之货，使民不为盗；
不见可欲，使心不乱。
是以圣人之治，虚其心，实其腹，弱其志，强其骨。
常使民无知无欲。
使夫1知者不敢为也。
为无为，则无不治。
| 11.46875 | 31 | 0.716621 | yue_Hant | 0.248893 |
08b9af79f10e3f59093fd4de1770ec02a57fec8c | 8,754 | md | Markdown | articles/active-directory-b2c/active-directory-b2c-reference-tokens.md | huiw-git/azure-content-zhtw | f20103dc3d404c9c929c155b36c5a47aee5baed6 | [
"CC-BY-3.0"
] | null | null | null | articles/active-directory-b2c/active-directory-b2c-reference-tokens.md | huiw-git/azure-content-zhtw | f20103dc3d404c9c929c155b36c5a47aee5baed6 | [
"CC-BY-3.0"
] | null | null | null | articles/active-directory-b2c/active-directory-b2c-reference-tokens.md | huiw-git/azure-content-zhtw | f20103dc3d404c9c929c155b36c5a47aee5baed6 | [
"CC-BY-3.0"
] | 1 | 2020-11-04T04:34:56.000Z | 2020-11-04T04:34:56.000Z | <properties
pageTitle="Azure Active Directory B2C 預覽 | Microsoft Azure"
description="在 Azure Active Directory B2C 預覽中簽發的權杖類型。"
services="active-directory-b2c"
documentationCenter=""
authors="dstrockis"
manager="msmbaldwin"
editor=""/>
<tags
ms.service="active-directory-b2c"
ms.workload="identity"
ms.tgt_pltfrm="na"
ms.devlang="na"
ms.topic="article"
ms.date="01/21/2016"
ms.author="dastrock"/>
# Azure AD B2C 預覽︰權杖參考
Azure Active Directory (Azure AD) B2C 會在處理每個[驗證流程](active-directory-b2c-apps.md)時發出數種安全性權杖。本文件說明每種權杖的格式、安全性特性和內容。
[AZURE.INCLUDE [active-directory-b2c-preview-note](../../includes/active-directory-b2c-preview-note.md)]
## 權杖的類型
Azure AD B2C 支援 [OAuth 2.0 授權通訊協定](active-directory-b2c-reference-protocols.md)，該通訊協定會使用存取權杖與重新整理權杖。它也支援透過 [OpenID Connect](active-directory-b2c-reference-protocols.md) 進行驗證和登入，這引進第三種類型的權杖：ID 權杖。每個權杖都是以持有人權杖表示。
持有人權杖是輕巧型的安全性權杖，授權「持有人」存取受保護的資源。持有人是可出示權杖的任何一方。Azure AD 必須先驗證合作對象，才能接收持有人權杖。但若傳輸和儲存時未採取必要的步驟來保護權杖，它可能會被非預期的一方攔截和使用。某些安全性權杖有內建的機制，可防止未授權的合作對象使用它們，但持有人權杖沒有這項機制。它們必須在安全的通道 (例如傳輸層安全性 (HTTPS)) 中傳輸。
如果持有人權杖是在安全通道外部進行傳輸，則惡意人士就能使用攔截式攻擊來取得權杖，然後未經授權存取受保護的資源。儲存或快取持有人權杖供以後使用時，也適用相同的安全性原則。務必確定您的應用程式以安全的方式傳輸和儲存持有人權杖。
如需持有人權杖的其他安全性考量，請參閱 [RFC 6750 第 5 節](http://tools.ietf.org/html/rfc6750)。
許多由 Azure AD B2C 所簽發的權杖都實作為 JSON Web 權杖 (JWT)。JWT 是一種精簡的 URL 安全方法，可在兩方之間傳輸資訊。JWT 包含稱為宣告的資訊。這些是權杖持有人及主體相關資訊的判斷提示。JWT 中的宣告是為了傳輸而編碼和序列化的 JSON 物件。因為 Azure AD B2C 所簽發的 JWT 已簽署但未加密，所以您可以輕鬆地檢查 JWT 的內容以便偵錯。有一些工具可以這樣做，包括 [calebb.net](https://calebb.net)。如需 JWT 的詳細資訊，請參閱 [JWT 規格](http://self-issued.info/docs/draft-ietf-oauth-json-web-token.html)。
### ID 權杖
ID 權杖是您的應用程式從 Azure AD B2C `authorize` 和 `token` 端點接收的一種安全性權杖。ID 權杖以 [JWT](#types-of-tokens) 表示，而且包含宣告讓您用來識別應用程式中的使用者。從 `authorize` 端點取得 ID 權杖時，通常會用來讓使用者登入 Web 應用程式。從 `token` 端點取得 ID 權杖時，可在相同應用程式或服務的兩個元件之間進行通訊時在 HTTP 要求中傳送。您可以依需要在 ID 權杖中使用宣告。它們通常用來顯示帳戶資訊，或決定應用程式中的存取控制。
ID 權杖已簽署，但這次不加密。當您的應用程式或 API 收到 ID 權杖時，它必須[驗證簽章](#token-validation)以證明權杖的真實性。您的應用程式或 API 也必須驗證權杖中的幾個宣告，以證明它有效。應用程式所驗證的宣告會視案例需求而有所不同，但您的應用程式必須在每一種案例中執行一些[常見的宣告驗證](#token-validation)。
本指南稍後會列出 ID 權杖中的宣告的其他詳細資料，以及下列範本 ID 權杖。請注意，ID 權杖中的宣告不依任何特定順序傳回。此外，隨時都可以在 ID 權杖中加入新的宣告。加入新的宣告時，您的應用程式不會損壞。清單包含本文撰寫時您的應用程式可確實解譯的宣告。在練習時，請試著將範例 ID 權杖中的宣告貼入 [calebb.net](https://calebb.net) 中進行檢查。在 [OpenID Connect 規格](http://openid.net/specs/openid-connect-core-1_0.html)中可找到進一步的詳細資料。
#### 範例 ID 權杖
```
// Line breaks for display purposes only
eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsImtpZCI6IklkVG9rZW5TaWduaW5nS2V5Q29udGFpbmVyIn0.
eyJleHAiOjE0NDIzNjAwMzQsIm5iZiI6MTQ0MjM1NjQzNCwidmVyIjoiMS4wIiwiaXNzIjoiaHR0cHM6Ly9s
b2dpbi5taWNyb3NvZnRvbmxpbmUuY29tLzc3NTUyN2ZmLTlhMzctNDMwNy04YjNkLWNjMzExZjU4ZDkyNS92
Mi4wLyIsImFjciI6ImIyY18xX3NpZ25faW5fc3RvY2siLCJzdWIiOiJOb3Qgc3VwcG9ydGVkIGN1cnJlbnRs
eS4gVXNlIG9pZCBjbGFpbS4iLCJhdWQiOiI5MGMwZmU2My1iY2YyLTQ0ZDUtOGZiNy1iOGJiYzBiMjlkYzYi
LCJpYXQiOjE0NDIzNTY0MzQsImF1dGhfdGltZSI6MTQ0MjM1NjQzNCwiaWRwIjoiZmFjZWJvb2suY29tIn0.
h-uiKcrT882pSKUtWCpj-_3b3vPs3bOWsESAhPMrL-iIIacKc6_uZrWxaWvIYkLra5czBcGKWrYwrAC8ZvQe
DJWZ50WXQrZYODEW1OUwzaD_I1f1HE0c2uvaWdGXBpDEVdsD3ExKaFlKGjFR2V7F-fPThkVDdKmkUDQX3bVc
yyj2V2nlCQ9jd7aGnokTPfLfpOjuIrTsAdPcGpe5hfSEuwYDmqOJjGs9Jp1f-eSNEiCDQOaTBSvr479L5ptP
XWeQZyX2SypN05Rjr05bjZh3j70ZUimiocfJzjibeoDCaQTz907yAg91WYuFOrQxb-5BaUoR7K-O7vxr2M-_
CQhoFA
```
#### ID 權杖中的宣告
當您使用 Azure AD B2C 時，您可以精確控制權杖的內容。您可以設定[原則](active-directory-b2c-reference-policies.md)，以在宣告中傳送您的應用程式運作時所需的幾組特定的使用者資料。這些宣告可以包含標準的屬性，例如使用者的 `displayName` 和 `emailAddress`。其中也可以包含您在 B2C 目錄中可定義的[自訂使用者屬性](active-directory-b2c-reference-custom-attr.md)。您收到的每個 ID 權杖會包含一組特定的安全性相關宣告。您的應用程式可以使用這些宣告來安全地驗證使用者和要求。以下是 Azure AD B2C 所簽發的每個 ID 權杖中應該會有的宣告。其他任何宣告由原則決定。
| 名稱 | 宣告 | 範例值 | 說明 |
| ----------------------- | ------------------------------- | ------------ | --------------------------------- |
| 對象 | `aud` | `90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6` | 對象宣告識別權杖的預定接收者。在 ID 權杖中，對象是在應用程式註冊入口網站中指派給應用程式的應用程式識別碼。您的應用程式應驗證此值並拒絕不相符的權杖。 |
| Issuer | `iss` | `https://login.microsoftonline.com/775527ff-9a37-4307-8b3d-cc311f58d925/v2.0/` | 此宣告會識別負責建構並傳回權杖的 Security Token Service (STS)。它也會識別用於驗證使用者的 Azure AD 目錄。您的應用程式應驗證簽發者宣告，以確保權杖來自 v2.0 端點。 |
| 發出時間 | `iat` | `1438535543` | 此宣告是簽發權杖的時間，以新紀元時間表示。 |
| 到期時間 | `exp` | `1438539443` | 此到期時間宣告是權杖失效的時間，以新紀元時間表示。您的應用程式應使用此宣告來驗證權杖存留期的有效性。 |
| 生效時間 | `nbf` | `1438535543` | 此宣告是權杖生效的時間，以新紀元時間表示。這通常與權杖的簽發時間相同。您的應用程式應使用此宣告來驗證權杖存留期的有效性。 |
| 版本 | `ver` | `1.0` | 這是 Azure AD 所定義的 ID 權杖版本。 |
| 代碼雜湊 | `c_hash` | `SGCPtt01wxwfgnYZy2VJtQ` | 只有當 ID 權杖與 OAuth 2.0 授權碼一起簽發時，權杖才會包含代碼雜湊。代碼雜湊可用來驗證授權碼的真實性。如需有關如何執行此驗證的詳細資訊，請參閱 [OpenID Connect 規格](http://openid.net/specs/openid-connect-core-1_0.html)。 |
| 存取權杖雜湊 | `at_hash` | `SGCPtt01wxwfgnYZy2VJtQ` | 只有當 ID 權杖與 OAuth 2.0 存取權杖一起簽發時，權杖才會包含存取權杖雜湊。存取權杖雜湊可用來驗證存取權杖的真實性。如需有關如何執行此驗證的詳細資訊，請參閱 [OpenID Connect 規格](http://openid.net/specs/openid-connect-core-1_0.html)。 |
| Nonce | `nonce` | `12345` | Nonce 是用來緩和權杖重新執行攻擊的策略。您的應用程式可以使用 `nonce` 查詢參數，在授權要求中指定 Nonce。您在要求中提供的值將會在 ID 權杖的 `nonce` 宣告中發出 (未經修改)。這可讓您的應用程式根據在要求上指定的值驗證此值，使應用程式的工作階段與給定的 ID 權杖產生關聯。您的應用程式應在 ID 權杖驗證程序中執行這項驗證。 |
| 主旨 | `sub` | `Not supported currently. Use oid claim.` | 這是權杖聲稱資訊時所針對的主體，例如應用程式的使用者。這個值不可變，而且無法重新指派或重複使用。它可用來安全地執行授權檢查，例如當權杖用於存取資源時。不過，尚未在 Azure AD B2C 預覽中實作主體宣告。您應該設定原則以包含物件識別碼 `oid` 宣告及使用其值來識別使用者，而不是使用主體宣告進行授權。 |
| 驗證內容類別參考 | `acr` | `b2c_1_sign_in` | 這是用來取得 ID 權杖的原則名稱。 |
| 驗證期間 | `auth_time | `1438535543` | 此宣告是使用者上次輸入認證的時間，以新紀元時間表示。 |
### 存取權杖
Azure AD B2C 此時不會簽發存取權杖。預覽階段不支援兩個合作對象之間的驗證。不過，您可以使用 ID 權杖在相同應用程式的元件之間進行通訊。深入了解 [Azure AD B2C 預覽所支援的應用程式和驗證案例](active-directory-b2c-apps.md)。
### 重新整理權杖
重新整理權杖是可供您的應用程式在 OAuth 2.0 流程中取得新的 ID 權杖和存取權杖的安全性權杖。它們可讓您的應用程式代表使用者來長期存取資源，而不需與使用者互動。
若要在權杖回應中接收重新整理權杖，您的應用程式必須要求 `offline_acesss` 範圍。若要深入了解 `offline_access` 範圍，請參閱 [Azure AD B2C 通訊協定參考](active-directory-b2c-reference-protocols.md)。
重新整理權杖永遠對您的應用程式完全不透明。它們是由 Azure AD 所簽發，只能由 Azure AD 檢查和解譯。它們屬於長效權杖，但在撰寫您的應用程式時，不應該期待重新整理權杖會持續一段特定時間。重新整理權杖可能會因為各種原因而隨時失效。讓您的應用程式知道重新整理權杖是否有效的唯一方式，就是對 Azure AD 提出權杖要求以嘗試兌換。
當您以重新整理權杖來兌換新的權杖時 (而且如果您的應用程式已獲得 `offline_access` 範圍)，您會在權杖回應中收到新的重新整理權杖。您應儲存新簽發的重新整理權杖。它應該取代您先前使用於要求中的重新整理權杖。這有助於保證您的重新整理權杖盡可能長期保持有效。
## 權杖驗證
您的應用程式目前唯一應該執行的權杖驗證就是驗證 ID 權杖。若要驗證 ID 權杖，您的應用程式應該驗證該權杖的簽章和宣告。
<!-- TODO: Link -->
視您偏好的語言而定，有許多開放原始碼程式庫可用來驗證 JWT。我們建議您探索這些選項，而不是實作您自己的驗證邏輯。本指南中的資訊有助於您了解如何適當使用這些程式庫。
### 驗證簽章
JWT 包含三個區段 (以 `.` 字元分隔)。第一個區段是**標頭**，第二個是**主體**，而第三個是**簽章**。簽章區段可用來驗證 ID 權杖的真實性，以便獲得應用程式的信任。
ID 權杖是經由業界標準非對稱式加密演算法 (例如 RSA 256) 進行簽署。ID 權杖的標頭包含用來簽署權杖的金鑰和加密方法的相關資訊：
```
{
"typ": "JWT",
"alg": "RS256",
"kid": "GvnPApfWMdLRi8PDmisFn7bprKg"
}
```
`alg` 宣告指出用來簽署權杖的演算法。`kid` 或 `x5t` 宣告指出用來簽署權杖的特定公開金鑰。
無論何時，Azure AD 可能會使用任何一組特定的公開-私密金鑰組來簽署 ID 權杖。Azure AD 會定期替換一組可能的金鑰，所以應將您的應用程式撰寫成自動處理這些金鑰變更。檢查 Azure AD 所用公開金鑰的更新的合理頻率為每 24 小時。
Azure AD B2C 具有 OpenID Connect 中繼資料端點。這可讓應用程式在執行階段擷取 Azure AD B2C 的相關資訊。這項資訊包括端點、權杖內容和權杖簽署金鑰。您的 B2C 目錄包含每個原則的 JSON 中繼資料文件。例如，`fabrikamb2c.onmicrosoft.com` 中的 `b2c_1_sign_in` 原則中繼資料文件位於：
`https://login.microsoftonline.com/fabrikamb2c.onmicrosoft.com/v2.0/.well-known/openid-configuration?p=b2c_1_sign_in`
您可以使用位於下列位置的 OpenID Connect 中繼資料文件來取得驗證簽章所需的簽署金鑰資料：
```
https://login.microsoftonline.com/fabrikamb2c.onmicrosoft.com/v2.0/.well-known/openid-configuration?p=b2c_1_sign_in
```
`fabrikamb2c.onmicrosoft.com` 是用來驗證使用者的 B2C 目錄，而 `b2c_1_sign_in` 是用來取得 ID 權杖的原則。若要判斷哪個原則用來簽署 ID 權杖 (以及何處可擷取中繼資料)，您有兩個選項。首先，原則名稱包含在 ID 權杖的 `acr` 宣告中。您可以將 JWT 主體進行 base 64 解碼，並將產生的 JSON 字串還原序列化，以剖析 JWT 主體中的宣告。`acr` 宣告會是用來簽發 ID 權杖的原則名稱。另一個選項是當您發出要求時在 `state` 參數的值中將原則編碼，然後將它解碼以判斷使用了哪個原則。任一種方法都有效。
中繼資料文件是包含幾項實用資訊的 JSON 物件。其中包括執行 OpenID Connect 驗證時所需端點的位置。它們還包含 `jwks_uri`，指出用來簽署權杖的公用金鑰組的位置。這裡提供該位置，但最好使用中繼資料文件並剖析 `jwks_uri` 來動態擷取該位置：
`https://login.microsoftonline.com/fabrikamb2c.onmicrosoft.com/discovery/v2.0/keys?p=b2c_1_sign_in`
位於此 URL 的 JSON 文件包含特定時刻使用的所有公開金鑰資訊。您的應用程式可以使用 JWT 標頭中的 `kid` 或 `x5t` 宣告，以選取 JSON 文件中用來簽署特定權杖的公開金鑰。接著可以使用正確的公開金鑰和指定的演算法來執行簽章驗證。
描述如何執行簽章驗證已超出本文的範圍。如果需要的話，有許多開放原始碼程式庫可協助您處理這方面。
### 驗證宣告
當您的應用程式或 API 收到 ID 權杖時，還應該對 ID 權杖中的宣告執行一些檢查。其中包含：
- **對象**宣告：這會確認 ID 權杖預定要提供給您的應用程式。
- **生效時間**和**到期時間**宣告：這些會確認 ID 權杖尚未過期。
- **簽發者**宣告：這會確認權杖已由 Azure AD 簽發給您的應用程式。
- **Nonce**：這是用來緩和權杖重新執行攻擊的策略。
先前的 [ID 權杖一節](#id-tokens)包含這些宣告的預期值的詳細資料。
## 權杖存留期
下列權杖存留期讓您了解更透徹。當您開發及偵錯應用程式時，它們可以協助您。請注意，撰寫您的應用程式時，請不要認為任何存留期會維持不變。它們會變更。
| 權杖 | 存留期 | 說明 |
| ----------------------- | ------------------------------- | ------------ |
| ID 權杖 | 一小時 | ID 權杖的有效期通常為 1 小時。Web 應用程式可以使用此存留期來維持它自己與使用者之間的工作階段 (建議選項)。您也可以選擇不同的工作階段存留期。如果您的應用程式需要取得新的 ID 權杖，它只需要對 Azure AD 提出新的登入要求。如果使用者與 Azure AD 之間存在有效的瀏覽器工作階段，該使用者可能不需要再次輸入認證。 |
| 重新整理權杖 | 最多 14 天 | 單一重新整理權杖的有效期最多 14 天。不過，重新整理權杖可能由於許多原因而隨時失效。您的應用程式應繼續嘗試使用重新整理權杖，直到要求失敗，或您的應用程式更換新的重新整理權杖為止。在使用者上次輸入認證之後經過 90 天，重新整理權杖也會失效。 |
| 授權碼 | 五分鐘 | 授權碼是刻意設計成短期。它們應在收到時立即兌換成存取權杖、ID 權杖或重新整理權杖。 |
<!---HONumber=AcomDC_0224_2016--> | 53.705521 | 352 | 0.791867 | yue_Hant | 0.966303 |
08ba374d18a252a23f691a2aa7c8db4ddcbe2db5 | 10,273 | md | Markdown | README.md | emqx/mqtt-jmeter | 40c73181efbac8cdc386a0bf09c9cab3689cc459 | [
"Apache-2.0"
] | 153 | 2018-08-31T07:35:27.000Z | 2020-08-18T05:43:52.000Z | README.md | emqx/mqtt-jmeter | 40c73181efbac8cdc386a0bf09c9cab3689cc459 | [
"Apache-2.0"
] | 49 | 2018-09-28T07:44:32.000Z | 2020-08-06T02:18:32.000Z | README.md | emqx/mqtt-jmeter | 40c73181efbac8cdc386a0bf09c9cab3689cc459 | [
"Apache-2.0"
] | 86 | 2018-09-12T10:05:09.000Z | 2022-03-31T07:24:24.000Z | # mqtt-jmeter Overview
MQTT JMeter Plugin extends your JMeter's capability to test against MQTT protocol, just as easy as ordinary HTTP protocal.
It has been used to benchmark EMQ server performance, and here is the [report link](https://github.com/emqx/emq-xmeter-cn).
This plugin is developed and maintained by [XMeter](https://www.xmeter.net). XMeter is a professional performance testing service provider.
# Install instruction
The plugin is a standard JMeter plugin. You can download the latest version of mqtt-jmeter from [here](https://github.com/emqx/mqtt-jmeter/releases), and then copy the downloaded JAR files into $JMETER_HOME/lib/ext folder. After restarting the JMeter, you can see "MQTT samplers" provided by this plugin.
To use this plugin, we recommend you to install JMeter 3.2 or above.
## Build from source code
If you'd like to build binary by yourself, please clone the project and run 'mvn install'. Maven will download some JMeter dependency binary files, so the build elapsed time will up to your network status.
# How to use
The plugin includes 4 samplers:
- Connect sampler: Initiate MQTT server connection on behalf of a device. In addition to normal connection setup, this sampler can be used to simulate massive "background" connections(no data transimission but regular hearbeat signals) to the designated MQTT server or cluster system.
- Pub sampler: publish various messages to the target MQTT server.
- Sub sampler: subscribe message(s) from target MQTT server.
- DisConnect sampler: Reset the connection to target MQTT server.
If MQTT JMeter plugin is successfully installed, you can find these MQTT samplers under JMeter 'Sampler' context menu.
## Connect Sampler
### MQTT connection
This section includes basic connection settings.
- **Server name or IP**: The MQTT target to be tested. It can be either IP address or server name. The default value is 127.0.0.1. **DO NOT** add protocol (e.g. tcp:// or ssl://) before server name or IP address!
- **Port number**: The port opened by MQTT server. Typically 1883 is for TCP protocol, and 8883 for SSL protocol.
- **MQTT version**: The MQTT version, default is 3.1, and another option is 3.1.1. Sometimes we found version 3.1.1 is required to establish connection to [Azure IoTHub](https://github.com/emqx/mqtt-jmeter/issues/21).
- **Timeout(s)**: The connection timeout seconds while connecting to MQTT server. The default is 10 seconds.
### MQTT Protocol
The sampler supports 4 protocols, TCP, SSL, WS, WSS.
For SSL and WSS protocols, it includes normal SSL and dual SSL authentication.
If **'Dual SSL authentication'** is checked, please follow 'Certification files for SSL/TLS connections' at end of this doc to set the client SSL configuration properly.
### User authentication
User can configure MQTT server with user name & password authentication, refer to [EMQ user name and password authentication guide](http://emqtt.com/docs/v2/guide.html#id3).
- **User name**: If MQTT server is configured with user name, then specify user name here.
- **Password**: If MQTT server is configured with password, then specify password here.
### Connection options
- **ClientId**: Identification of the client, i.e. virtual user or JMeter thread. Default value is 'conn_'. If 'Add random client id suffix' is selected, JMeter plugin will append generated uuid as suffix to represent the client, otherwise, the text of 'ClientId' will be passed as 'clientId' of current connection.
- **Keep alive(s)**: Ping packet send interval in seconds. Default value is 300, which means each connection sends a ping packet to MQTT server every 5 minutes.
- **Connect attampt max**: The maximum number of reconnect attempts before an error is reported back to the client on the first attempt by the client to connect to a server. Set to -1 to use unlimited attempts. Defaults to 0.
- **Reconnect attampt max**: The maximum number of reconnect attempts before an error is reported back to the client after a server connection had previously been established. Set to -1 to use unlimited attempts. Defaults to 0.
- **Clean session**: If you want to maintain state information between sessions, set it to false; otherwise, set it to true.
## Pub Sampler
Pub sampler reuses previously established connection (by Connect sampler) to publish a message. If connection is not ready at this moment, pub sampler will just fail immediately.
### Pub options
- **QoS level**: The available QoS value, 0 is AT_MOST_ONCE, 1 is AT_LEAST_ONCE and 2 is EXACTLY_ONCE.
- **Retained messages**: Set it to true if the Pub sampler wants the broker to keep the last message on the given topic, so that the client subscribed to that topic receives the retained message immediately after subscription.
- **Topic name**: Name of the topic that the message will be sent to.
- **Add timestamp in payload**: Add timestamp in the payload or not. If the checkbox is enabled, then timestamp of running pub sampler will be added before real payload. Mostly it's used together with **Sub sampler** to calculate message latency time.
### Payloads
**Message type**: 3 types of message can be used.
- String: The normal string that sent to MQTT server. It can also be a JMeter variable.
- Hex string: The hex string that sent to MQTT server. The chars input must be [0-9] or [A-F] or [a-f]. The hex string will be converted to binary and send to server. It can also be a JMeter variable.
- Random string with fixed length: Refer to below screenshot. If the option is selected, then it requires user to input 'Length'. The length means the auto generated string length. Default is 1024, which means generated a 1kb size of random string.
## Sub Sampler
Sub sampler reuses previously established connection (by Connect sampler) to subscribe message(s). If connection is not ready at this moment, sub sampler will just fail immediately.
### Sub options
- **QoS level**: The available QoS value, 0 is AT_MOST_ONCE, 1 is AT_LEAST_ONCE and 2 is EXACTLY_ONCE.
- **Topic name(s)**: A list of topic names (comma-separated) that will be subscribed to.
- **Payload includes timestamp**: If the checkbox is enabled, then it means the payload includes timestamp. It can be used to calcuate the message latency time.
```
message_latency = timestamp_in_sub_when_receive_msg - timestamp_in_payload (timestamp in pub machine when sending out message)
Please notice, if the machine publish message is not the same as subscriber, then the calculated message latency time is not accurate.
It's because the time is almost not the same in different machines. So the latency time calculated by sub sampler could be only be a reference.
```
- **Sample on**: It controls how to sample. The default value is '**elapsed with specified time(ms)**', which means a sub sampler will occur every specified milli-seconds (default is 1000ms). During the 1000 ms, multiple messages could be received, and result in report is the summarized data during 1000 ms. If the value is set to 2000, then means summarized report during 2000 ms. Another option is '**number of received messages**', which means a sub sampler will occur after receiving these specified number of messages (default is 1).
- **Debug response**: If checked, the received message will be print in response. It's recommended to enable this option when you debug your script.
## DisConnect Sampler
This sampler is very simple, it just clear the previous created connection. Therefore, next time you run Connect sampler, it will initiate a new MQTT server connection for you. As you can imagine, Disconnect sample will fail immediately if no connection is detected at this moment.
## Example JMeter Scripts
As a reference, you can check out some example scripts in SampleScripts folder.
1) background_connection.jmx:
Simulate massive background MQTT connections to server. You can optionally subscribe to a topic when connecting. (Please modify "xmeter_runtime_vars" UDV to fit your needs.)
2) pubsub_unidirection.jmx:
Demonstrate how sub sampler can get messages from corresponding pub sampler, with two JMeter user groups and delay between opertions.
3) pubsub_bidirection.jmx:
Demonstrate how a set of Devices and Mobiles exchange messages in both directions.
## Certification files for SSL/TLS connections
After deploying emqtt server, you get the following OOTB (out of the box) SSL/TLS certification files under ${EMQTTD_HOME}/etc/certs directory:
1) **cacert.pem** : the self-signed CA certification
2) **cert.pem** : certification for emqtt server
3) **client-cert.pem** : certfication for emqtt client in order to connect to server via SSL/TLS connection. In this jmeter plugin case, the client implies jmeter "virtual user"
4) **client-key.pem** **key.pem** : key files to protect client and server certification respectively
[Note:] The above server and client certifications are both issued by the self-signed CA. If you would like to use official certifications for your EMQTT deployment, please check out relevant document to configure it.
We will use the OOTB test certfications (as an example) to show you how to prepare the required certification files for this EMQTT JMeter plugin.
```
export PATH=$PATH:<YOUR_JDK_HOME>/bin
keytool -import -alias cacert -keystore emqtt.jks -file cacert.pem -storepass <YOUR_PASSWORD> -trustcacerts -noprompt
keytool -import -alias client -keystore emqtt.jks -file client-cert.pem -storepass <YOUR_PASSWORD>
keytool -import -alias server -keystore emqtt.jks -file cert.pem -storepass <YOUR_PASSWORD>
openssl pkcs12 -export -inkey client-key.pem -in client-cert.pem -out client.p12 -password pass:<YOUR_PASSWORD>
```
#### Specify key store, client certfication and corresponding pass phrases in plugin sampler:
| 59.726744 | 541 | 0.776599 | eng_Latn | 0.996277 |
08ba4306b61baf92ba6c953d562e10579a036c30 | 4,598 | md | Markdown | _posts/2019-11-20-embedded-programing.md | rydeenworks/rydeenworks.github.io | 9ab0ea427a3ddf1bbf5a490f202b649f3a96b152 | [
"MIT"
] | null | null | null | _posts/2019-11-20-embedded-programing.md | rydeenworks/rydeenworks.github.io | 9ab0ea427a3ddf1bbf5a490f202b649f3a96b152 | [
"MIT"
] | null | null | null | _posts/2019-11-20-embedded-programing.md | rydeenworks/rydeenworks.github.io | 9ab0ea427a3ddf1bbf5a490f202b649f3a96b152 | [
"MIT"
] | null | null | null | ---
layout: post
title: "組み込みプログラミングのためのハードウェア基礎知識"
date: 2019-11-20
categories: programming
---
**組み込み系のC言語/C++の開発現場に配属された人**
組み込み系のC言語/C++の開発現場に配属されたんだけど、なんか、CPUやメモリなどハードウェアの事についてよく知らない、組み込みプログラミングの基礎知識が欲しい。あと、ついでに良い学習の仕方があれば知りたい、と考えていませんか？
本記事では、この疑問を解決します。
**本記事の内容**
- ハードウェアの基礎知識
- ハードウェアの基礎知識の学習方法
**著者について**
この記事を書いている私はプログラミング歴が15年ほどあり、直近5年は組み込みプログラミングの開発をしています。
デスクトップアプリ開発５年(C/C++)→スマホアプリ開発５年(Java/Objective-C)→組み込みアプリ開発５年(C/C++)
経歴は上記の通りですが、初心者の時に学んだハードウェアの基礎知識はずっと役に立ってきました。
# 1 ハードウェアの基礎知識
## 1.1 ハードウェア特性の理解
プログラムはハードウェア上で動作しますので、ハードウェアの特性を理解してプログラムする必要があります。
たくさんの種類の部品が集合してハードウェアを構成していますが、はじめのうちは主要なものだけ理解すれば良いです。
- CPU
- メモリ
- ストレージ
- ネットワーク
各ハードの主要な特性は以下の通りです。
### CPU
- CPUはプログラムで命令した計算処理を行うハード
- 一定時間内にどれだけの計算量をこなせるかはCPUによって決まる
- 一定時間内の計算量上限に達するとCPU使用率100%になる、それ以上の計算は待たされるので最終的な計算完了までの時間が長くなる。
- たくさんの計算量をこなせるCPUは高価
### メモリ
- メモリはプログラムで処理するデータを保持するハード
- 保持できるデータサイズはメモリによって決まる
- メモリが保持できるデータサイズの上限を超えた場合、メモリ上のデータをストレージに退避する。退避処理が発生するとプログラム動作が遅くなる。ストレージに退避したデータをメモリに復帰させる処理も、同様にプログラム動作が遅くなる。
- たくさんのデータを保持できるメモリは高価
### ストレージ
- ストレージはデータをファイルとして保存するハード
- プログラムはファイルからデータを読み込んでメモリに保持する、またデータをファイルに保存する
- ストレージに保存できるデータサイズ上限はストレージ容量によって決まる
- ストレージ容量を超えて保存させようとした場合、保存処理は失敗する
- ストレージのハードの種類は色々ある(ハードディスク/SSD/USBメモリ/SDカード)
- ハードディスクはSSDに比べて安くて大容量、ただしデータ保存・読み込みのためにディスクを物理的に回転させるのでプログラムの動作が遅くなる
- たくさんのデータを保持できるストレージは高価
### ネットワーク
- ネットワークはコンピュータ間でデータを送受信するためのハード
- 一定時間内にどれだけの通信量をこなせるかはネットワーク環境とハードで決まる
- 一定時間内の通信量上限に達するとネットワーク使用率100%になる、それ以上の通信は待たされるので最終的な通信完了までの時間が長くなる。
- たくさんの通信量をこなせるハード・ネットワーク環境は高価
## 1.2 利用可能なハードウェア資源の確認
ハードウェア特性の理解 を踏まえて、実際にプログラムする上で利用可能なハードウェア資源を確認します。
### 全般
- ハードウェア上で動作するプログラムは１つだけか？
複数のプログラムを同時に実行する場合、１つのプログラムがハードウェア資源を使い切ってしまうと困るので確認します。
### CPU
- CPU使用率100%まで使い切って問題ないか？
基本的には100%まで使い切るのは良くありません。CPUが熱くなったり、電力をたくさん消費したり、他のプログラムが止まってしまったり、色々と支障があります。
### メモリ
- プログラムが利用可能なメモリサイズ上限は？
### ストレージ
- プログラムが利用可能なストレージ容量上限は？
### ネットワーク
- プログラムが利用可能な通信量上限は？
## 1.3 ソフトウェア設計の確認
利用可能なハードウェア資源を踏まえてソフトウェア設計します。
基本的には以下のことを行うイメージです。
- 設計上のハードウェア資源使用量を算出する
- 資源使用量の実績値をログ出力して可視化する
- 設計改善によって資源使用量を削減する
基本的にはハードウェア資源使用量を減らすということは、性能がそれだけ落ちます。ハードウェア資源使用量と性能のバランスを理解した上でトレードオフします。（処理データ量削減やアルゴリズム改善によってハードウェア資源使用量を減らした場合は性能は落ちません）
### CPU
- 計算量が多いプログラムの特定
- 計測処理ログ出力(処理時間、CPU使用率)の検討
- 改善設計の検討(データ削減、アルゴリズム改善)
### メモリ
- プログラムの設計上のメモリ使用量の算出
- メモリ使用量のログ出力の検討
- 改善設計の検討(データ削減、アルゴリズム改善)
### ストレージ
- プログラムの設計上のストレージ使用量の算出
- ストレージ読み書き処理のログ出力(ファイルサイズ、処理時間)の検討
- 改善設計の検討(データ削減、ストレージアクセス回数削減)
### ネットワーク
- プログラムの設計上の通信量の算出
- 通信ログ出力(通信量、通信回数)の検討
- 改善設計の検討(データ削減、アルゴリズム改善)
# 2 ハードウェアの基礎知識の学習方法
## 2.1 組み込み系なら初学者のうちに基礎知識を習得しましょう
ハードウェアの知識はなるべく早く身につけた方が良いです。
なぜなら、どんなハードウェアもCPU/メモリ/ストレージというハードウェア構成は変わらないため、一度これらの知識を身につけておくと一生この知識がプログラミングで生かせてコストパフォーマンスが良いからです。
また、近年ではネットワーク常時接続が当たり前になっているためネットワークの知識を持っている方が良いです。
## 2.2 学習の仕方
インターネットでたくさんの情報が得られますが、それらは断片的で体系的ではない事があり初学者に情報の取捨選択するのは大変だと思います。
そのため、評判の良い本でハードウェアの基礎知識について体系的な全体像を学ぶのがおすすめです。以下の方法で調べると良いでしょう。
- Google検索で評判の良い本を調べる
- Amazonで本のレビューを調べる
## 2.3 ハードウェア基礎知識の学習の実例
初学者には次の本が特にオススメです。
<iframe style="width:120px;height:240px;" marginwidth="0" marginheight="0" scrolling="no" frameborder="0" src="https://rcm-fe.amazon-adsystem.com/e/cm?ref=tf_til&t=dynamitecruis-22&m=amazon&o=9&p=8&l=as1&IS2=1&detail=1&asins=4822281655&linkId=1d286cf9ce36cf74cc6ed7834b3251e3&bc1=000000<1=_blank&fc1=333333&lc1=0066c0&bg1=ffffff&f=ifr">
</iframe>
<iframe style="width:120px;height:240px;" marginwidth="0" marginheight="0" scrolling="no" frameborder="0" src="https://rcm-fe.amazon-adsystem.com/e/cm?ref=tf_til&t=dynamitecruis-22&m=amazon&o=9&p=8&l=as1&IS2=1&detail=1&asins=4822283151&linkId=48d8b55dbc42075d55aea109bcaf0aa0&bc1=000000<1=_blank&fc1=333333&lc1=0066c0&bg1=ffffff&f=ifr">
</iframe>
<iframe style="width:120px;height:240px;" marginwidth="0" marginheight="0" scrolling="no" frameborder="0" src="https://rcm-fe.amazon-adsystem.com/e/cm?ref=tf_til&t=dynamitecruis-22&m=amazon&o=9&p=8&l=as1&IS2=1&detail=1&asins=4822283119&linkId=235547d37a920430e71c6880ee38e387&bc1=000000<1=_blank&fc1=333333&lc1=0066c0&bg1=ffffff&f=ifr">
</iframe>
# 図書館の予約を便利にするアプリの紹介
私は図書館をよく利用するのですが、上記の本も図書館から借りました。本が図書館にあるかAndroidアプリ [図書さがし(Google Play)](https://play.google.com/store/apps/details?id=com.rydeenworks.mybooksearch)で簡単に調べることができて便利です。
| 20.995434 | 338 | 0.808177 | yue_Hant | 0.434247 |
08ba53aec826edcb7ce31dac5706c88e77596ab5 | 1,689 | md | Markdown | README.md | danielsioli/DICI | c4b261d791201f27a2f1f09589b177a2bb79649e | [
"MIT"
] | null | null | null | README.md | danielsioli/DICI | c4b261d791201f27a2f1f09589b177a2bb79649e | [
"MIT"
] | null | null | null | README.md | danielsioli/DICI | c4b261d791201f27a2f1f09589b177a2bb79649e | [
"MIT"
] | null | null | null | # pyDICI
Pacote para enviar dados ao DICI
## Install
```
pip install pyDICI
```
## Use
Importar pacote
```
import pyDICI as dici
```
Arquivo Excel
Montar um arquivo Excel (XLSX) com o seguinte formato. Podem ser adicionadas quantas linhas forem necessárias.
|Cronograma|Leiaute|Ano|Entrega|Entidade|Arquivo|
|----------|-------|---|-------|--------|-------|
|Nome do Cronograma|Nome do Leiaute|Ano 4 Dígitos|Tipo de Entrega|Nome da Entidade|Caminho para arquivo com dados a serem carregados|
Salve o arquivo no formato Excel XLSX (ex.: C:\arquivos.xlsx)
Os cronogramas e leiautes precisam já estar cadastrados no DICI.
Exemplo:
|Cronograma|Leiaute|Ano|Entrega|Entidade|Arquivo|
|----------|-------|---|-------|--------|-------|
|Acessos SMP 2019|Acessos SMP|2019|MES_2|CLARO S.A. (40.432.544/0001-47)|C:\claro.csv|
|Cronograma Marca|Cronograma Marca|2019|Pontual|AGENCIA NACIONAL DE TELECOMUNICACOES - SEDE (02.030.715/0001-12)|C:\marca.xml|
|Credenciadas do SMP|Credenciadas do SMP|2019|Pontual|AGENCIA NACIONAL DE TELECOMUNICACOES - SEDE (02.030.715/0001-12)|C:\credenciadas.csv|
Mantenha o chromedriver.exe (http://chromedriver.chromium.org/downloads) no %PATH% ou na pasta do seu projeto.
Enviar dados para o servidor de produção
```
dici.enviar_dados('C:\\arquivos.xlsx')
```
Enviar dados para o servidor de homologação
```
dici.enviar_dados('C:\\arquivos.xlsx', hm=True)
```
Endereço do servidor de produção
```
dici.servidor_producao
```
Endereço do servidor de homologação
```
dici.servidor_homologacao
```
Tipos de entrega aceitas
```
dici.entregas
```
Tipos de arquivos de dados aceitos
```
dici.formatos
``` | 28.15 | 140 | 0.692718 | por_Latn | 0.8895 |
08ba8378723fb745351e2d73559c2cee1a17f9f4 | 10,235 | md | Markdown | content/blog/EN/5/123eb179ba072a631fdb8b78e6c46695_t.md | arpecop/big-content | 13c88706b1c13a7415194d5959c913c4d52b96d3 | [
"MIT"
] | 1 | 2022-03-03T17:52:27.000Z | 2022-03-03T17:52:27.000Z | content/blog/EN/5/123eb179ba072a631fdb8b78e6c46695_t.md | arpecop/big-content | 13c88706b1c13a7415194d5959c913c4d52b96d3 | [
"MIT"
] | null | null | null | content/blog/EN/5/123eb179ba072a631fdb8b78e6c46695_t.md | arpecop/big-content | 13c88706b1c13a7415194d5959c913c4d52b96d3 | [
"MIT"
] | null | null | null | ---
title: 123eb179ba072a631fdb8b78e6c46695_t
mitle: "5 Signs You Have Too Many Toxins In Your Kidneys"
description: "Some symptoms that your body has way too many toxins and it’s time to stop"
image: "https://cdnone.netlify.com/db/2017/05/tapoos-logo.png"
---
<i></i> <i></i> <i></i> -1<p><img src="https://cdnone.netlify.com/db/2017/12/download-1-1.jpg"/></p> <img src="https://cdnone.netlify.com/db/2017/12/word-image-1607.jpeg"/>Shutterstock <p>Kidneys are bean shaped organs, located just below the ribcage. One on each side of the spine. Kidneys function as the filter in our body clearing it of toxins produced by all the body processes. They do so by filtering about 120 to 250 quarts of blood and producing around 1 to 2 quarts of urine which then flows out of our body. This process helps balance your levels of sodium, potassium, phosphorous, and acid in the blood. Our kidneys are always on duty, throughout the day as well as at night when we’re sleeping.</p> <p>At times, your kidneys cannot function properly. This is because of consumption of too many medications, preservatives and artificial food. Over exposed to pollution, household cleaning products and other products with strong chemicals in them can also contribute to poor health of the kidney. Because the function of the kidneys is to remove toxins, with poor kidneys your body will not be properly disposed of these pollutants. This can cause fatal illnesses.</p> <p>Below are some symptoms that your body has way too many toxins and it’s time to stop that now:</p> <h2>Change in Urine</h2> <p>The product of the kidney, urine can be checked to see if your body has a lot of poisonous toxins. If you notice change in the color or frequency of urine it’s time to be cautious. Dark yellow urine is not a good sign. More abnormal cases could include brown, pink, orange, black or red colored urine.</p> <p>In more serious cases, you could have difficulty urinating, urgency to use the washroom in the middle of your sleep cycle. This could be worse if your urine contains blood or is foamy. This is because of pus or forth in the urine. Pus or forth are results of underlying infections.</p> <h2>Swollen Face, Feet, Ankles and Face</h2> <img src="https://cdnone.netlify.com/db/2017/12/word-image-1608.jpeg"/>Shutterstock <p>With urine, excess sodium is removed. For adults, normal urine sodium values are generally 20 mEq/L in a random urine sample. When enough is not retained, excess sodium flows in with the blood. Sodium keeps the levels of fluid inside and outside the cell balanced. With excess sodium the fluids rush into the cells through osmosis and causes the tissues to swell. This condition is called pitting Edema (swollen feet because of high levels of sodium in blood). Pitting edema can be confirmed by smearing force on the swollen area with a finger. If the pressing shows a hollow dent that continues for some time even after the release of the pressure this could be a case of pitting Edema.</p> <h2>Feeling Tired or Having Trouble Concentrating</h2> <img src="https://cdnone.netlify.com/db/2017/12/word-image-1609.jpeg"/>Shutterstock <p>If you feel tired and lazy all the time, even though all you did was rest the entire day then may be the toxins are to blame. Most of the time you’re just procrastinating (we all do), but if you feel like working yet still your energy’s all drained out then the excess toxins can be the cause. Too many toxins in the kidney can also cause loss of concentration. This is because these toxins cause hindrances in the body functions resulting in exhausting the body and make you feel at unrest.</p> <h2>Skin Rashes</h2> <img src="https://cdnone.netlify.com/db/2017/12/word-image-1610.jpeg"/>Shutterstock <p>Itchy skin and rashes can also be a symptom of a weak kidney. If you feel that your skin is irritated easily lately, or skin rashes have increased then the quantity of toxins in your kidneys is high. These cannot easily be treated with lotions or creams because they are formed away from the skin surface. They fall deeper than the normal skin rashes. Too much uric acid in the blood causes these itchy rashes. They’re tiny red bumps visible on the skin.</p> <h2>Muscle Cramps</h2> <img src="https://cdnone.netlify.com/db/2017/12/word-image-1611.jpeg"/>Shutterstock <p>Kidneys also balance the electrolytes in our blood, for example sodium, potassium etc. Imbalance of electrolytes can cause muscle cramps. When the rate of toxins in kidneys is high you may have calcium levels near to the ground or unrestrained phosphorous in your blood. Both of these environments bases muscle contractions and spasms.</p> <h2>Leg Pain</h2> <img src="https://cdnone.netlify.com/db/2017/12/word-image-1612.jpeg"/>Shutterstock <p>Kidney stones and infections can cause aching in legs. The most targeted are is the back of the legs and lower back. If you feel discomfort in these areas it’s better to get your kidney tested. Because the kidneys are located with other vital organs of the body and you cannot pinpoint which organ is not functioning properly without appropriate tests and medical assistance.</p> <h2>Nausea and Shortness of Breath</h2> <img src="https://cdnone.netlify.com/db/2017/12/word-image-1613.jpeg"/>Shutterstock <p>Shortness of breath may happen as the blood’s pH levels are inconsistent. This loads more burden on the respiratory system. Queasiness and nausea may be experience as these toxins hoard in the blood stream.</p> <h2>Prevention and Treatment</h2> <img src="https://cdnone.netlify.com/db/2017/12/word-image-1614.jpeg"/>Shutterstock <p>Reading all these symptoms might scare you to death before the toxins could but, here’s the good news. Your kidney’s health is in your hands. Most of the mild conditions can be corrected with a change in lifestyle and health habits.</p> <h2>The Magic Potion: Water</h2> <img src="https://cdnone.netlify.com/db/2017/12/word-image-1615.jpeg"/>Facthacker <p>Drinking 2 liters of water is recommended for healthy kidneys, hence a healthy body. Make sure to drink your 8 glasses every day, no excuse! Water helps you aid the kidney in its job and wash away the toxins. The major reason for kidney failures is of intake of water. We lose so much water every day in sweating, chemical reactions in the body, urine etc. This needs to be recovered back by increased consumption. The leading cause of kidney stones is lack of water as well.</p> <h2>Reduce Meat and Dairy Intake</h2> <img src="https://cdnone.netlify.com/db/2017/12/word-image-1616.jpeg"/>Shutterstock <p>Consuming and digesting protein and dairy products have its benefits but they both produce uric acid as a byproduct. Uric acid id one of the toxins the kidneys filter out of blood. Patients of weak kidneys should cut down the consumption to minimal. Replace protein with healthier choices like fruit or vegetables. Fresh fruits and vegetables increase alkaline levels in blood, which helps lower the blood pressure. Lower blood pressure makes it easier for the kidneys to do its job.</p> <h2>Switch to Organic, Unprocessed Food</h2> <img src="https://cdnone.netlify.com/db/2017/12/word-image-1617.jpeg"/>Shutterstock <p>Almost everything now has added flavors and chemicals in them. Eating food with high proportion of preservatives, artificial flavors and chemicals causes overload for the kidney. A better choice would be healthier organic foods which are free of additives, pesticides, antibiotics and hormones. Organic foods are available in the market. Or you could grow them in your garden.</p> <h2>Reduce Intake of Salt</h2> <img src="https://cdnone.netlify.com/db/2017/12/word-image-1618.jpeg"/>Shutterstock <p>Salt is guilty of causing kidney failure. Increased salt intake upsurges the toxins in your kidneys. Salt can be found in unsuspicious things like pre-packaged, canned, and processed foods. With too much consumption of salt, your body requires extra water to maintain its intercellular solutions and fluids balanced. Rather than getting rid of water, your body retains it instead. This increases your blood volume meaning your blood pressure. This overburdens your kidneys.</p> <h2>Detoxification Drinks and Juices</h2> <img src="https://cdnone.netlify.com/db/2017/12/word-image-1619.jpeg"/>Shutterstock <p>Detox drinks specified for kidney detox can help you jumpstart towards a better kidney. Where plain water provides hydration, detox drinks can provide extra cleaning boost. Beets juice, for example, contains betaine. It has antioxidant abilities and increases the acidity of urine. This can benefit by clearing calcium phosphate accumulation in the kidneys. The elimination of calcium in the kidneys upholds kidney’s task and lowers the possibility of kidney stones.</p> <p>Lemon juice also is a good detoxification juice for better function of the kidneys. Because of being naturally acidic it helps increase citrate levels in urine. Just squeeze 4-5 lemons into a quart of cold water and drink up (tastes better ice cold). Or squeeze half a lemon into 8 ounces of hot water daily if you have a taste for hot beverages.</p> <p>If you don’t like these then there are a lot more recipes for detoxification. The Internet is full of them.</p> <p>Adapt the habit of eating healthy and drinking plenty of water and your kidneys will thank you. Even if you don’t have an excess amount of toxins or any kidney problem it’s still recommended to take your daily water intake and avoid too much salt in your food, or eating too much of artificial food, just to be on the safe side. All these habits won’t only help your kidneys function better but also save you from many other diseases such as heart problems or skin issues.</p> <p>If you feel that you have too many toxins in your blood and kidneys it is better to consult a doctor immediately. Because sometimes we cannot confirm the source of the problem by just looking at it. Medical assistance is required. Lab test and detailed reports can only diagnose the issues properly. This is why it is important to have monthly checkups. Urine test it also really important because not only does it confirm about toxin related issues but also other kidney problems such as diabetes.</p> <i></i> | 1,279.375 | 9,972 | 0.786224 | eng_Latn | 0.99895 |
08bab50dbdc384843a78b16399dd6e97fa35ec6c | 338 | md | Markdown | src/pages/pages/2019-12-06--start/index.md | Koo-S/sangmo-dev-blog | 19c6dc73689bb928a0938b288733b42a77ee263f | [
"MIT"
] | 1 | 2020-06-16T06:55:49.000Z | 2020-06-16T06:55:49.000Z | src/pages/pages/2019-12-06--start/index.md | Koo-S/sangmo-dev-blog | 19c6dc73689bb928a0938b288733b42a77ee263f | [
"MIT"
] | null | null | null | src/pages/pages/2019-12-06--start/index.md | Koo-S/sangmo-dev-blog | 19c6dc73689bb928a0938b288733b42a77ee263f | [
"MIT"
] | null | null | null | ---
title: "블로그 시작!"
layout: page
path: "/start"
---
블로그를 시작하면서 어떤 마음 가짐을 가져야 할까 많은 고민을 하였다.
큰 마음을 먹고 시작해야 한다고 생각했는데 막상 그냥 시간 조금 투자 해서 진행하면 가능한거 같다.
머리속으로 앞으로 무엇을 해야 한다는 걸 알고는 있었으나 하지 않았다.
물론 내가 알고 있는 것이 옳은 것인지는 정확히 모른다. 그러나 앞으로는 하나씩 해보려 한다.
블로그를 통해서 내 생각과 내가 할 수 있는 일을 정리 할 것이다.
더 좋은 개발자가 되기 위해 노력하자!
| 18.777778 | 55 | 0.650888 | kor_Hang | 1.00001 |
08bbbc5d0783500fc13c5c7adee554ccec45c22d | 3,617 | md | Markdown | wdk-ddi-src/content/d3dkmddi/nc-d3dkmddi-dxgkddi_enumvidpncofuncmodality.md | sathishcg/windows-driver-docs-ddi | 238bb4dc827cb3d2c64e535cf3f91d205b20c943 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-08-12T00:32:04.000Z | 2021-07-17T15:32:12.000Z | wdk-ddi-src/content/d3dkmddi/nc-d3dkmddi-dxgkddi_enumvidpncofuncmodality.md | sathishcg/windows-driver-docs-ddi | 238bb4dc827cb3d2c64e535cf3f91d205b20c943 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | wdk-ddi-src/content/d3dkmddi/nc-d3dkmddi-dxgkddi_enumvidpncofuncmodality.md | sathishcg/windows-driver-docs-ddi | 238bb4dc827cb3d2c64e535cf3f91d205b20c943 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
UID: NC:d3dkmddi.DXGKDDI_ENUMVIDPNCOFUNCMODALITY
title: DXGKDDI_ENUMVIDPNCOFUNCMODALITY
author: windows-driver-content
description: The DxgkDdiEnumVidPnCofuncModality function makes the source and target modes sets of a VidPN cofunctional with the VidPN's topology and the modes that have already been pinned.
old-location: display\dxgkddienumvidpncofuncmodality.htm
ms.assetid: 6dda82bd-1a43-4ffe-b398-a9f8cee6d1c1
ms.author: windowsdriverdev
ms.date: 5/10/2018
ms.keywords: DXGKDDI_ENUMVIDPNCOFUNCMODALITY, DXGKDDI_ENUMVIDPNCOFUNCMODALITY callback, DmFunctions_e8c49ebf-a4af-4a36-a32b-0ab6874e660a.xml, DxgkDdiEnumVidPnCofuncModality, DxgkDdiEnumVidPnCofuncModality callback function [Display Devices], d3dkmddi/DxgkDdiEnumVidPnCofuncModality, display.dxgkddienumvidpncofuncmodality
ms.prod: windows-hardware
ms.technology: windows-devices
ms.topic: callback
req.header: d3dkmddi.h
req.include-header:
req.target-type: Desktop
req.target-min-winverclnt: Available in Windows Vista and later versions of the Windows operating systems.
req.target-min-winversvr:
req.kmdf-ver:
req.umdf-ver:
req.ddi-compliance:
req.unicode-ansi:
req.idl:
req.max-support:
req.namespace:
req.assembly:
req.type-library:
req.lib:
req.dll:
req.irql: PASSIVE_LEVEL
topic_type:
- APIRef
- kbSyntax
api_type:
- UserDefined
api_location:
- d3dkmddi.h
api_name:
- DxgkDdiEnumVidPnCofuncModality
product:
- Windows
targetos: Windows
tech.root: display
req.typenames:
---
# DXGKDDI_ENUMVIDPNCOFUNCMODALITY callback function
## -description
The <i>DxgkDdiEnumVidPnCofuncModality</i> function makes the source and target modes sets of a VidPN cofunctional with the VidPN's topology and the modes that have already been pinned.
## -parameters
### -param hAdapter [in]
A handle to a context block associated with a display adapter. The display miniport driver previously provided this handle to the DirectX graphics kernel subsystem in the <i>MiniportDeviceContext</i> output parameter of the <a href="https://msdn.microsoft.com/5fd4046f-54c3-4dfc-8d51-0d9ebcde0bea">DxgkDdiAddDevice</a> function.
### -param pEnumCofuncModality
#### - pEnumCofuncModalityArg [in]
A pointer to a <a href="https://msdn.microsoft.com/library/windows/hardware/ff557583">DXGKARG_ENUMVIDPNCOFUNCMODALITY</a> structure that contains function arguments.
## -returns
<i>DxgkDdiEnumVidPnCofuncModality</i> returns STATUS_SUCCESS if it succeeds; otherwise, it returns one of the error codes defined in <i>Ntstatus.h</i>.
## -remarks
The <b>hConstrainingVidPn</b> member of <i>pEnumCofuncModalityArg</i> is a handle to a VidPN object called the constraining VidPN. Other members of <i>pEnumCofuncModalityArg</i> identify one video present source or target as the pivot of the enumeration (or specify that there is no pivot).
<i>DxgkDdiEnumVidPnCofuncModality</i> must perform the following tasks:
<ul>
<li>
Examine the topology and mode sets of the constraining VidPN.
</li>
<li>
Update each mode set that is not the pivot and does not already have a pinned mode. The updated mode sets must be cofunctional with the VidPN's topology and with any modes that have already been pinned.
</li>
</ul>
Note that if a source or target is identified as the pivot of the enumeration, the mode set for that source or target must not change. For more information about how to update source and target mode sets, see <a href="https://msdn.microsoft.com/f1aa6277-7af6-4ba0-8ff1-d562f7029540">Enumerating Cofunctional VidPN Source and Target Modes</a>.
The <i>DxgkDdiEnumVidPnCofuncModality</i> function should be made pageable.
| 32.00885 | 343 | 0.798728 | eng_Latn | 0.778825 |
08bc34339e4cccc3f3eef15b09d58d78b0dfd563 | 65 | md | Markdown | README.md | weissxu/base | 6cbd20d9529d26a3ddc1719e7c167302af52f015 | [
"Apache-2.0"
] | null | null | null | README.md | weissxu/base | 6cbd20d9529d26a3ddc1719e7c167302af52f015 | [
"Apache-2.0"
] | null | null | null | README.md | weissxu/base | 6cbd20d9529d26a3ddc1719e7c167302af52f015 | [
"Apache-2.0"
] | null | null | null | # base
the base project with springboot, together with mybatis,
| 21.666667 | 57 | 0.784615 | eng_Latn | 0.999569 |
08bcddf25371dceb3d27d8fd48b57c9021767b77 | 10,742 | md | Markdown | _posts/2020-10-08-openfaas-functions-with-github-actions.md | utsavanand2/openfaas.github.io | 922054be0f216d3fc5dc2d88dc0e123daf28cb85 | [
"MIT"
] | null | null | null | _posts/2020-10-08-openfaas-functions-with-github-actions.md | utsavanand2/openfaas.github.io | 922054be0f216d3fc5dc2d88dc0e123daf28cb85 | [
"MIT"
] | null | null | null | _posts/2020-10-08-openfaas-functions-with-github-actions.md | utsavanand2/openfaas.github.io | 922054be0f216d3fc5dc2d88dc0e123daf28cb85 | [
"MIT"
] | null | null | null | ---
title: "Build and deploy OpenFaaS functions with GitHub Actions"
description: "Build and deploy functions to OpenFaaS anywhere with GitHub Actions and multi-arch images"
date: 2020-10-13
image: /images/2020-10-github-actions/lego.jpg
categories:
- faas-netes
- faasd
- cicd
- github
- multi-arch
author_staff_member: utsav
dark_background: true
---
Build and deploy functions to OpenFaaS anywhere with GitHub Actions and multi-arch images
## Introduction: automating function updates
OpenFaaS was created to have the freedom to run serverless functions anywhere you want, whether that be within your on-premises environment, on AWS, or even on a Raspberry Pi in your home. Whichever way you're running OpenFaaS, you won't get far without a way to build and deploy functions, and at small scale, you may be doing this manually.
When you're ready to level-up your operations, and update functions after each commit is pushed, or each Pull Request is merged, then build systems like GitLab CI, Travis, CircleCI and GitHub Actions become essentials parts of your infrastructure.
Over the past few years this has meant installing Docker on the build system, and running the `docker` command to build an image, push it to a registry, and to then deploy it. Recently advancements in cross-compilation and the newer container builder `buildkit` means we can build images for multiple platforms with ease, so that an image can be deployed to an AWS Graviton instance with an ARM processor, and to a regular EC2 node using a `x86_64` (Intel) processor.
So in this tutorial I'll show you how to build and deploy functions anywhere using GitHub Actions and multi-arch images that can run on a cloud instance, or on your Raspberry Pi homelab.
### Prerequisites
Kubernetes is our recommendation for teams running at scale, but [faasd](https://www.openfaas.com/blog/faasd-tls-terraform/) provides a suitable alternative for smaller teams.
* An OpenFaaS deployment using Kubernetes or faasd
You can deploy OpenFaaS [here](https://docs.openfaas.com/deployment/)
* Publicly accessible network OpenFaaS gateway
Your OpenFaaS gateway should be accessible from the Internet and have TLS enabled for security. If you are running behind a firewall, or at home then checkout the [inlets-operator project](https://docs.inlets.dev/) to make your OpenFaaS gateway accessible from the Internet.
* faas-cli
faas-cli is a command line tool used to interact with OpenFaaS, from deploying your functions to viewing logs.
Follow the installation instructions [here](https://docs.openfaas.com/cli/install/)
> All code samples are available in this repo: [github.com/utsavanand2/hello](https://github.com/utsavanand2/hello)
### Create a function using the Golang template
Create a repository on GitHub called `hello` and clone it.
I'm going to create and deploy a Golang function for this tutorial using the `golang-http` template, which closely resembles a HTTP handler in Go's standard library.
```bash
# Change the directory into the repository
cd hello
# Pull golang-http templates
faas-cli template store pull golang-http
# Create a new function with faas-cli
faas-cli new hello --lang golang-http
```
If you look into the root directory of the project, faas-cli has created two additional files:
```bash
./hello/handler.go
./hello.yml
```
The content of our handler looks something like this:
The YAML file is used to configure the deployment and the build and runtime environment of the function
### Setup a workflow file for GitHub Actions
[GitHub Action workflows](https://docs.github.com/en/free-pro-team@latest/actions/learn-github-actions/introduction-to-github-actions) is one of the many core components of GitHub Actions that lets users add an automated workflow that executes on an event, and can be used to test, build and deploy our code.
A workflow can be composed of multiple steps, each executing a particular action.
There are many published [Actions](https://github.com/marketplace?type=actions) that provide nice wrappers for common actions and tools making them easier to use, but we can also use any published Docker image. The OpenFaaS team already publishes an image for `faas-cli` that is ready to use for any workflow.
Our workflow is a simple linear process:
In the root directory of the project run:
```sh
mkdir -p .github/workflows
nano ./github/workflows/main.yml
```
And paste in the following contents into main.yml file
```yaml
name: CI/CD
on:
push:
branches:
- master
jobs:
func-build:
runs-on: ubuntu-latest
steps:
-
name: Checkout
uses: actions/checkout@v2
-
name: Define ENV VARS
id: define_env
run: echo "::set-output name=github-sha-short::$(echo $GITHUB_SHA | cut -c 1-7)"
-
name: Pull template
uses: docker://openfaas/faas-cli:latest-root
with:
args: template store pull golang-http
-
name: Run shrinkwrap build
uses: docker://openfaas/faas-cli:latest-root
with:
args: build -f hello.yml --shrinkwrap
-
name: Login to OpenFaaS Gateway
uses: docker://openfaas/faas-cli:latest-root
with:
args: login -p {% raw %}${{ secrets.OPENFAAS_GATEWAY_PASSWD }}{% endraw %} \
-g {% raw %}${{ secrets.OPENFAAS_GATEWAY }}{% endraw %}
-
name: Login to DockerHub
if: success()
uses: docker/login-action@v1
with:
username: {% raw %}${{ secrets.DOCKER_USERNAME }}{% endraw %}
password: {% raw %}${{ secrets.DOCKER_PASSWORD }}{% endraw %}
-
name: Set up Docker Buildx
uses: docker/setup-buildx-action@v1
-
name: Build and Push the OpenFaaS function
uses: docker/build-push-action@v2
with:
context: ./build/hello/
file: ./build/hello/Dockerfile
push: true
tags: utsavanand2/hello:latest-{% raw %}${{ steps.define_env.outputs.github-sha-short }}{% endraw %}
-
name: Deploy the function
uses: docker://openfaas/faas-cli:latest-root
with:
args: deploy -f hello.yml --tag sha
```
> Note: replace the `DOCKER_USERNAME` from the image tag name with your own.
Since GitHub Actions requires us to use a Docker image that has a root user invoking the commands using the Docker action, so we're using the root variant of the faas-cli Docker image. Read more about it [here](https://docs.github.com/en/free-pro-team@latest/actions/creating-actions/dockerfile-support-for-github-actions#user)
The faas-cli:latest-root image has the faas-cli installed as the entrypoint, so everything set in args is passed to the faas-cli.
This will work with any of the faas-cli root tags, you can pin to any specific version of faas-cli, for example: `openfaas/faas-cli:0.12.14-root`.
We're also using using the second step in the workflow to get a short seven characters long SHA of the git commit to tag our Docker image with in the `Build and Push the OpenFaaS function` step of the workflow.
In the last step of the build `Deploy the function` we're using the arg `--tag sha` which will call the OpenFaaS API Gateway for it to expect an image with the tag `latest-${7 char long commit SHA}`.
This explains the tag we're using in the `Build and Push the OpenFaaS function` step as well.
### Add secrets to your GitHub repo for the build
Add the following secrets and their values to the repo for GitHub Actions to build push and deploy your OpenFaaS functions. Make sure that the secret names correspond with the GitHub workflow YAML file as defined above in the previous section.
Now trigger a build by editing one of the files and running `git push`.
### Check the status of your GitHub Actions build
Under the `Actions` tab we can check the status of the workflow
Since we have successfully built and deployed our functions let's invoke it with curl.
### Invoke the function with curl
```sh
export OPENFAAS_GATEWAY=<The OPENFAAS_GATEWAY of your OpenFaaS deployment>
curl http://$OPENFAAS_GATEWAY/function/hello
```
## Take it further
You can take this to the next level by leveraging multi-arch builds with Docker's [Buildx](https://docs.docker.com/buildx/working-with-buildx/) and the golang-http-templates which now support multi-arch builds. This means that you can deploy the same function to architectures like arm, arm64 of amd64 from a single build.
The two changes are to set up an emulation tool for Linux called [qemu](https://www.qemu.org/) and to provide a list of desired architectures for the images.
```yaml
-
name: Login to DockerHub
if: success()
uses: docker/login-action@v1
with:
username: {% raw %}${{ secrets.DOCKER_USERNAME }}{% endraw %}
password: {% raw %}${{ secrets.DOCKER_PASSWORD }}{% endraw %}
-
name: Set up QEMU
uses: docker/setup-qemu-action@v1
-
name: Set up Docker Buildx
uses: docker/setup-buildx-action@v1
-
name: Build and Push the OpenFaaS function
uses: docker/build-push-action@v2
with:
context: ./build/hello/
file: ./build/hello/Dockerfile
push: true
platforms: linux/amd64,linux/arm64,linux/arm/v7
tags: utsavanand2/hello:latest-{% raw %}${{ steps.define_env.outputs.github-sha-short }}{% endraw %}
```
You can see the full workflow YAML file supporting multi-arch builds here: [main.yml](https://github.com/utsavanand2/hello/blob/multi-arch/.github/workflows/main.yml):
### Join the community
Have you got questions, comments, or suggestions? Join the community on [Slack](https://slack.openfaas.io).
Would you like help setting up your OpenFaaS installation, or someone to call when things don't quite go to plan? [Our Premium Subscription plan](https://www.openfaas.com/support/) gives you a say in the project roadmap, a support contact, and access to Enterprise-grade authentication with OIDC.
### Acknowledgements
Special Thanks to [Lucas Rosler](https://twitter.com/TheAxeR) and [Alex Ellis](https://twitter.com/alexellisuk) for all guidance and for merging changes into OpenFaaS to better support this workflow.
Thanks to [Dan Burton](https://unsplash.com/@single_lens_reflex) for the background picture. | 46.103004 | 467 | 0.726494 | eng_Latn | 0.983653 |
08bd0ea55ac24307adea0d99043a2acc06c880c7 | 657 | md | Markdown | README.md | barhouum7/PostMailManagement | 56f5f799907c5e747e1c16ea5211d7e1a0c2945d | [
"MIT"
] | null | null | null | README.md | barhouum7/PostMailManagement | 56f5f799907c5e747e1c16ea5211d7e1a0c2945d | [
"MIT"
] | null | null | null | README.md | barhouum7/PostMailManagement | 56f5f799907c5e747e1c16ea5211d7e1a0c2945d | [
"MIT"
] | null | null | null | # PostMailManagement
Simple Java application that simulates mail management within a post office. Anyone can learn the OOP concepts through this Java application.
It's a core java (Console App) without any SE or EE application.
## Project Notes🗒📝
Have a look at the project statement.
Which is written in French.
If you want to improve this repo, whatever maybe you want to translate the project statement or something else, please feel free to make your contribution, I'd be grateful.
### Contribution
1. Fork this repo
2. Update a local clone or make changes directly on the forked repo, adding your changes
3. Send in a PR and I'd be happy to merge.
| 41.0625 | 172 | 0.782344 | eng_Latn | 0.999047 |
08bd9dc63df5191b2d3d56cd78b0425492191301 | 553 | md | Markdown | _site/_units/gunfortress.md | jaguilar87/tp.net-armageddon.org | be0b6e1c8278fc7c32e73d9b2d58cc692da81059 | [
"0BSD"
] | 2 | 2018-01-23T13:17:37.000Z | 2021-07-29T17:48:58.000Z | _site/_units/gunfortress.md | jaguilar87/tp.net-armageddon.org | be0b6e1c8278fc7c32e73d9b2d58cc692da81059 | [
"0BSD"
] | 16 | 2015-08-13T21:43:54.000Z | 2022-02-17T14:37:29.000Z | _site/_units/gunfortress.md | jaguilar87/tp.net-armageddon.org | be0b6e1c8278fc7c32e73d9b2d58cc692da81059 | [
"0BSD"
] | 6 | 2019-11-28T20:52:11.000Z | 2021-12-29T16:54:52.000Z | ---
name: Gunfortress
type: WE
speed: 30cm
armour: 4+
cc: 4+
ff: 4+
special_rules:
- damage-capacity-3
- transport
notes:
|
May transport four infantry units without _Jump Packs_ or _Mounted_; only one of the four units may be a Big Gunz; plus two units of Grotz. Critical Hit Effect: Move the unit D6cm in a random direction, all units under it suffer a hit. The unit is destroyed and all units being carried are destroyed unless they roll a 6+.
weapons:
-
id: twin-big-shoota
multiplier: 5
-
id: big-gun
multiplier: 3
--- | 26.333333 | 326 | 0.708861 | eng_Latn | 0.996056 |
08bdec6a641c207dae35d04d369227825233b7b0 | 474 | md | Markdown | bower_components/qrcode-generator/js/README.md | isabella232/pongnub | d4a7e9126b91cff4392a7bb11659536f59e1b34a | [
"MIT"
] | 12 | 2015-04-27T21:30:48.000Z | 2020-11-19T09:13:22.000Z | bower_components/qrcode-generator/js/README.md | pubnub/pongnub | d4a7e9126b91cff4392a7bb11659536f59e1b34a | [
"MIT"
] | 1 | 2021-02-24T02:49:01.000Z | 2021-02-24T02:49:01.000Z | bower_components/qrcode-generator/js/README.md | isabella232/pongnub | d4a7e9126b91cff4392a7bb11659536f59e1b34a | [
"MIT"
] | 8 | 2015-09-18T20:32:52.000Z | 2021-01-13T10:36:22.000Z | QR Code Generator
===
1. Include qrcode.js in your html.
2. Prepare a place holder.
3. Generate QR and render it.
```html
<script type="text/javascript" src="qrcode.js"></script>
```
```html
<div id="placeHolder"></div>
```
```javascript
var typeNumber = 4; // 1~40
var errorCorrectionLevel = 'L'; // 'L','M','Q','H'
var qr = qrcode(typeNumber, errorCorrectionLevel);
qr.addData('Hi!');
qr.make();
document.getElementById('placeHolder').innerHTML = qr.createImgTag();
```
| 21.545455 | 69 | 0.675105 | yue_Hant | 0.393678 |
08be0ac5fa189b4bd71b0616013876338d9ab6eb | 472 | md | Markdown | README.md | tipsy/javalin-async-example | 26377ca183b78888e21bb85d05ed1fa9f830a561 | [
"Apache-2.0"
] | 8 | 2018-04-13T10:37:42.000Z | 2022-03-28T10:26:50.000Z | README.md | tipsy/javalin-async-example | 26377ca183b78888e21bb85d05ed1fa9f830a561 | [
"Apache-2.0"
] | 1 | 2018-04-13T21:49:40.000Z | 2018-04-13T21:52:35.000Z | README.md | tipsy/javalin-async-example | 26377ca183b78888e21bb85d05ed1fa9f830a561 | [
"Apache-2.0"
] | null | null | null | # javalin-async-example
This repo contains a benchmarking tool created for playing around with futures in [Javalin](https://javalin.io).
It's only intended as an illustration of the concepts of running requests asynchronously. Since your browser is being used
as a benchmarking tool results will become wildly inaccurate if you try to send too many requests.
| 52.444444 | 122 | 0.809322 | eng_Latn | 0.992902 |
08beb11785afa61044e6c6ed5d79657ceb6a051b | 1,063 | md | Markdown | class-08.md | osamamousa204/reading-notes-301 | d756ca790e73be2f8c33f06b1bacc7832ca3cd00 | [
"MIT"
] | null | null | null | class-08.md | osamamousa204/reading-notes-301 | d756ca790e73be2f8c33f06b1bacc7832ca3cd00 | [
"MIT"
] | null | null | null | class-08.md | osamamousa204/reading-notes-301 | d756ca790e73be2f8c33f06b1bacc7832ca3cd00 | [
"MIT"
] | 1 | 2020-03-28T17:45:00.000Z | 2020-03-28T17:45:00.000Z | # SQL
SQL, or Structured Query Language, is a language designed to allow both technical and non-technical users query, manipulate, and transform data from a relational database. And due to its simplicity, SQL databases provide safe and scalable storage for millions of websites and mobile applications.
# Relational databases
A relational database represents a collection of related (two-dimensional) tables. Each of the tables are similar to an Excel spreadsheet, with a fixed number of named columns (the attributes or properties of the table) and any number of rows of data.
# SELECT queries
To retrieve data from a SQL database, we need to write SELECT statements, which are often colloquially refered to as queries. A query in itself is just a statement which declares what data we are looking for, where to find it in the database, and optionally, how to transform it before it is returned. It has a specific syntax though, which is what we are going to learn in the following exercises.
[Home Page](https://osamamousa204.github.io/reading-notes-301/) | 81.769231 | 398 | 0.799624 | eng_Latn | 0.999771 |
08bed8252cf4c99e59f04c428168dc13e03132af | 198 | md | Markdown | LogicMonitor/Device Groups/LM get device group list/Readme.md | MithunKulkarniCTS/MithunKulkarniCTS | a9c264209d25495dea7ae919b8ad7080449f5db2 | [
"MIT"
] | 4 | 2019-12-07T03:27:41.000Z | 2021-03-11T02:30:40.000Z | LogicMonitor/Device Groups/LM get device group list/Readme.md | MithunKulkarniCTS/MithunKulkarniCTS | a9c264209d25495dea7ae919b8ad7080449f5db2 | [
"MIT"
] | 2 | 2021-08-17T03:06:52.000Z | 2021-09-17T13:18:19.000Z | LogicMonitor/Device Groups/LM get device group list/Readme.md | MithunKulkarniCTS/MithunKulkarniCTS | a9c264209d25495dea7ae919b8ad7080449f5db2 | [
"MIT"
] | 37 | 2019-08-19T19:41:16.000Z | 2022-02-03T08:43:59.000Z | <br># LogicMonitor</br>
<br>get device group list</br>
<br>LM get device group list</br>
<br>Method: Get</br>
<br>OperationID: getDeviceGroupList</br>
<br>EndPoint:</br>
<br>/device/groups</br>
| 24.75 | 40 | 0.686869 | eng_Latn | 0.162551 |
08bf65b09c93720498baef7a8cdf34c598d647a9 | 61,176 | md | Markdown | docs/project/create-a-project-add-in-that-uses-rest-with-an-on-premises-odata-service.md | danielgwilson/office-js-docs-pr | 75bf20ac62a0d50b2954e37d0e17111886efcac3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/project/create-a-project-add-in-that-uses-rest-with-an-on-premises-odata-service.md | danielgwilson/office-js-docs-pr | 75bf20ac62a0d50b2954e37d0e17111886efcac3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/project/create-a-project-add-in-that-uses-rest-with-an-on-premises-odata-service.md | danielgwilson/office-js-docs-pr | 75bf20ac62a0d50b2954e37d0e17111886efcac3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Create a Project add-in that uses REST with an on-premises Project Server OData service
description: ''
ms.date: 06/20/2019
localization_priority: Priority
---
# Create a Project add-in that uses REST with an on-premises Project Server OData service
This article describes how to build a task pane add-in for Project Professional 2013 that compares cost and work data in the active project with the averages for all projects in the current Project Web App instance. The add-in uses REST with the jQuery library to access the **ProjectData** OData reporting service in Project Server 2013.
The code in this article is based on a sample developed by Saurabh Sanghvi and Arvind Iyer, Microsoft Corporation.
## Prerequisites for creating a task pane add-in that reads Project Server reporting data
The following are the prerequisites for creating a Project task pane add-in that reads the **ProjectData** service of a Project Web App instance in an on-premises installation of Project Server 2013:
- Ensure that you have installed the most recent service packs and Windows updates on your local development computer. The operating system can be Windows 7, Windows 8, Windows Server 2008, or Windows Server 2012.
- Project Professional 2013 is required to connect with Project Web App. The development computer must have Project Professional 2013 installed to enable **F5** debugging with Visual Studio.
> [!NOTE]
> Project Standard 2013 can also host task pane add-ins, but cannot log on to Project Web App.
- Visual Studio 2015 with Office Developer Tools for Visual Studio includes templates for creating Office and SharePoint Add-ins. Ensure that you have installed the most recent version of Office Developer Tools; see the _Tools_ section of the [Office Add-ins and SharePoint downloads](https://developer.microsoft.com/office/docs).
- The procedures and code examples in this article access the **ProjectData** service of Project Server 2013 in a local domain. The jQuery methods in this article do not work with Project on the web.
Verify that the **ProjectData** service is accessible from your development computer.
### Procedure 1. To verify that the ProjectData service is accessible
1. To enable your browser to directly show the XML data from a REST query, turn off the feed reading view. For information about how to do this in Internet Explorer, see Procedure 1, step 4 in [Querying OData feeds for Project reporting data](/previous-versions/office/project-odata/jj163048(v=office.15)).
2. Query the **ProjectData** service by using your browser with the following URL: **http://ServerName /ProjectServerName /_api/ProjectData**. For example, if the Project Web App instance is `http://MyServer/pwa`, the browser shows the following results:
```xml
<?xml version="1.0" encoding="utf-8"?>
<service xml:base="http://myserver/pwa/_api/ProjectData/"
xmlns="https://www.w3.org/2007/app"
xmlns:atom="https://www.w3.org/2005/Atom">
<workspace>
<atom:title>Default</atom:title>
<collection href="Projects">
<atom:title>Projects</atom:title>
</collection>
<collection href="ProjectBaselines">
<atom:title>ProjectBaselines</atom:title>
</collection>
<!-- ... and 33 more collection elements -->
</workspace>
</service>
```
3. You may have to provide your network credentials to see the results. If the browser shows "Error 403, Access Denied," either you do not have logon permission for that Project Web App instance, or there is a network problem that requires administrative help.
## Using Visual Studio to create a task pane add-in for Project
Office Developer Tools for Visual Studio includes a template for task pane add-ins for Project 2013. If you create a solution named **HelloProjectOData**, the solution contains the following two Visual Studio projects:
- The add-in project takes the name of the solution. It includes the XML manifest file for the add-in and targets the .NET Framework 4.5. Procedure 3 shows the steps to modify the manifest for the **HelloProjectOData** add-in.
- The web project is named **HelloProjectODataWeb**. It includes the webpages, JavaScript files, CSS files, images, references, and configuration files for the web content in the task pane. The web project targets the .NET Framework 4. Procedure 4 and Procedure 5 show how to modify the files in the web project to create the functionality of the **HelloProjectOData** add-in.
### Procedure 2. To create the HelloProjectOData add-in for Project
1. Run Visual Studio 2015 as an administrator, and then select **New Project** on the Start page.
2. In the **New Project** dialog box, expand the **Templates**, **Visual C#**, and **Office/SharePoint** nodes, and then select ** Office Add-ins**. Select **.NET Framework 4.5.2** in the target framework drop-down list at the top of the center pane, and then select **Office Add-in** (see the next screenshot).
3. To place both of the Visual Studio projects in the same directory, select **Create directory for solution**, and then browse to the location you want.
4. In the **Name** field, typeHelloProjectOData, and then choose **OK**.
*Figure 1. Creating an Office Add-in*
5. In the **Choose the add-in type** dialog box, select **Task pane** and choose **Next** (see the next screenshot).
*Figure 2. Choosing the type of add-in to create*
6. In the **Choose the host applications** dialog box, clear all check boxes except the **Project** check box (see the next screenshot) and choose **Finish**.
*Figure 3. Choosing the host application*
Visual Studio creates the **HelloProjectOdata** project and the **HelloProjectODataWeb** project.
The **AddIn** folder (see the next screenshot) contains the App.css file for custom CSS styles. In the **Home** subfolder , the Home.html file contains references to the CSS files and the JavaScript files that the add-in uses, and the HTML5 content for the add-in. Also, the Home.js file is for your custom JavaScript code. The **Scripts** folder includes the jQuery library files. The **Office** subfolder includes the JavaScript libraries such as office.js and project-15.js, plus the language libraries for standard strings in the Office Add-ins. In the **Content** folder, the Office.css file contains the default styles for all of the Office Add-ins.
*Figure 4. Viewing the default web project files in Solution Explorer*
The manifest for the **HelloProjectOData** project is the HelloProjectOData.xml file. You can optionally modify the manifest to add a description of the add-in, a reference to an icon, information for additional languages, and other settings. Procedure 3 simply modifies the add-in display name and description, and adds an icon.
For more information about the manifest, see [Office Add-ins XML manifest](../develop/add-in-manifests.md) and [Schema reference for Office Add-ins manifests (v1.1)](../develop/add-in-manifests.md#see-also).
### Procedure 3. To modify the add-in manifest
1. In Visual Studio, open the HelloProjectOData.xml file.
2. The default display name is the name of the Visual Studio project ("HelloProjectOData"). For example, change the default value of the **DisplayName** element to"Hello ProjectData".
3. The default description is also "HelloProjectOData". For example, change the default value of the Description element to "Test REST queries of the ProjectData service".
4. Add an icon to show in the **Office Add-ins** drop-down list on the **PROJECT** tab of the ribbon. You can add an icon file in the Visual Studio solution or use a URL for an icon.
The following steps show how to add an icon file to the Visual Studio solution:
1. In **Solution Explorer**, go to the folder named Images.
2. To be displayed in the **Office Add-ins** drop-down list, the icon must be 32 x 32 pixels. For example, install the Project 2013 SDK, and then choose the **Images** folder and add the following file from the SDK: `\Samples\Apps\HelloProjectOData\HelloProjectODataWeb\Images\NewIcon.png`
Alternately, use your own 32 x 32 icon; or, copy the following image to a file named NewIcon.png, and then add that file to the `HelloProjectODataWeb\Images` folder:
3. In the HelloProjectOData.xml manifest, add an **IconUrl** element below the **Description** element, where the value of the icon URL is the relative path to the 32x32 icon file. For example, add the following line: **<IconUrl DefaultValue="~remoteAppUrl/Images/NewIcon.png" />**. The HelloProjectOData.xml manifest file now contains the following (your **Id** value will be different):
```XML
<?xml version="1.0" encoding="UTF-8"?>
<OfficeApp xmlns="http://schemas.microsoft.com/office/appforoffice/1.1"
xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance" xsi:type="TaskPaneApp">
<Id>c512df8d-a1c5-4d74-8a34-d30f6bbcbd82 </Id>
<Version>1.0</Version>
<ProviderName> [Provider name]</ProviderName>
<DefaultLocale>en-US</DefaultLocale>
<DisplayName DefaultValue="Hello ProjectData" />
<Description DefaultValue="Test REST queries of the ProjectData service"/>
<IconUrl DefaultValue="~remoteAppUrl/Images/NewIcon.png" />
<Hosts>
<Host Name="Project" />
</Hosts>
<DefaultSettings>
<SourceLocation DefaultValue="~remoteAppUrl/AddIn/Home/Home.html" />
</DefaultSettings>
<Permissions>ReadWriteDocument</Permissions>
</OfficeApp>
```
## Creating the HTML content for the HelloProjectOData add-in
The **HelloProjectOData** add-in is a sample that includes debugging and error output; it is not intended for production use. Before you start coding the HTML content, design the UI and user experience for the add-in, and outline the JavaScript functions that interact with the HTML code. For more information, see[Design guidelines for Office Add-ins](../design/add-in-design.md).
The task pane shows the add-in display name at the top, which is the value of the **DisplayName** element in the manifest. The **body** element in the HelloProjectOData.html file contains the other UI elements, as follows:
- A subtitle indicates the general functionality or type of operation, for example, **ODATA REST QUERY**.
- The **Get ProjectData Endpoint** button calls the **setOdataUrl** function to get the endpoint of the **ProjectData** service, and display it in a text box. If Project is not connected with Project Web App, the add-in calls an error handler to display a pop-up error message.
- The **Compare All Projects** button is disabled until the add-in gets a valid OData endpoint. When you select the button, it calls the **retrieveOData** function, which uses a REST query to get project cost and work data from the **ProjectData** service.
- A table displays the average values for project cost, actual cost, work, and percent complete. The table also compares the current active project values with the average. If the current value is greater than the average for all projects, the value is displayed as red. If the current value is less than the average, the value is displayed as green. If the current value is not available, the table displays a blue **NA**.
The **retrieveOData** function calls the **parseODataResult** function, which calculates and displays values for the table.
> [!NOTE]
> In this example, cost and work data for the active project are derived from the published values. If you change values in Project, the **ProjectData** service does not have the changes until the project is published.
### Procedure 4. To create the HTML content
1. In the **head** element of the Home.html file, add any additional **link** elements for CSS files that your add-in uses. The Visual Studio project template includes a link for the App.css file that you can use for custom CSS styles.
2. Add any additional **script** elements for JavaScript libraries that your add-in uses. The project template includes links for the jQuery- _[version]_.js, office.js, and MicrosoftAjax.js files in the **Scripts** folder.
> [!NOTE]
> Before you deploy the add-in, change the office.js reference and the jQuery reference to the content delivery network (CDN) reference. The CDN reference provides the most recent version and better performance.
The **HelloProjectOData** add-in also uses the SurfaceErrors.js file, which displays errors in a pop-up message. You can copy the code from the _Robust Programming_ section of [Create your first task pane add-in for Project 2013 by using a text editor](../project/create-your-first-task-pane-add-in-for-project-by-using-a-text-editor.md), and then add a SurfaceErrors.js file in the **Scripts\Office** folder of the **HelloProjectODataWeb** project.
Following is the updated HTML code for the **head** element, with the additional line for the SurfaceErrors.js file:
```HTML
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8" />
<meta http-equiv="X-UA-Compatible" content="IE=Edge" />
<title>Test ProjectData Service</title>
<link rel="stylesheet" type="text/css" href="../Content/Office.css" />
<!-- Add your CSS styles to the following file -->
<link rel="stylesheet" type="text/css" href="../Content/App.css" />
<!-- Use the CDN reference to the mini-version of jQuery when deploying your add-in. -->
<!--<script src="http://ajax.aspnetcdn.com/ajax/jquery/jquery-1.9.0.min.js"></script> -->
<script src="../Scripts/jquery-1.7.1.js"></script>
<!-- Use the CDN reference to office.js when deploying your add-in. -->
<!--<script src="https://appsforoffice.microsoft.com/lib/1/hosted/office.js"></script>-->
<!-- Use the local script references for Office.js to enable offline debugging -->
<script src="../Scripts/Office/1.0/MicrosoftAjax.js"></script>
<script src="../Scripts/Office/1.0/Office.js"></script>
<!-- Add your JavaScript to the following files -->
<script src="../Scripts/HelloProjectOData.js"></script>
<script src="../Scripts/SurfaceErrors.js"></script>
</head>
<body>
<!-- See the code in Step 3. -->
</body>
</html>
```
3. In the **body** element, delete the existing code from the template, and then add the code for the user interface. If an element is to be filled with data or manipulated by a jQuery statement, the element must include a unique **id** attribute. In the following code, the **id** attributes for the **button**, **span**, and **td** (table cell definition) elements that jQuery functions use are shown in bold font.
The following HTML adds a graphic image, which could be a company logo. You can use a logo of your choice, or copy the NewLogo.png file from the Project 2013 SDK download, and then use **Solution Explorer** to add the file to the `HelloProjectODataWeb\Images` folder.
```HTML
<body>
<div id="SectionContent">
<div id="odataQueries">
ODATA REST QUERY
</div>
<div id="odataInfo">
<button class="button-wide" onclick="setOdataUrl()">Get ProjectData Endpoint</button>
<br /><br />
<span class="rest" id="projectDataEndPoint">Endpoint of the
<strong>ProjectData</strong> service</span>
<br />
</div>
<div id="compareProjectData">
<button class="button-wide" disabled="disabled" id="compareProjects"
onclick="retrieveOData()">Compare All Projects</button>
<br />
</div>
</div>
<div id="corpInfo">
<table class="infoTable" aria-readonly="True" style="width: 100%;">
<tr>
<td class="heading_leftCol"></td>
<td class="heading_midCol"><strong>Average</strong></td>
<td class="heading_rightCol"><strong>Current</strong></td>
</tr>
<tr>
<td class="row_leftCol"><strong>Project Cost</strong></td>
<td class="row_midCol" id="AverageProjectCost">&nbsp;</td>
<td class="row_rightCol" id="CurrentProjectCost">&nbsp;</td>
</tr>
<tr>
<td class="row_leftCol"><strong>Project Actual Cost</strong></td>
<td class="row_midCol" id="AverageProjectActualCost">&nbsp;</td>
<td class="row_rightCol" id="CurrentProjectActualCost">&nbsp;</td>
</tr>
<tr>
<td class="row_leftCol"><strong>Project Work</strong></td>
<td class="row_midCol" id="AverageProjectWork">&nbsp;</td>
<td class="row_rightCol" id="CurrentProjectWork">&nbsp;</td>
</tr>
<tr>
<td class="row_leftCol"><strong>Project % Complete</strong></td>
<td class="row_midCol" id="AverageProjectPercentComplete">&nbsp;</td>
<td class="row_rightCol" id="CurrentProjectPercentComplete">&nbsp;</td>
</tr>
</table>
</div>
<img alt="Corporation" class="logo" src="../../images/NewLogo.png" />
<br />
<textarea id="odataText" rows="12" cols="40"></textarea>
</body>
```
## Creating the JavaScript code for the add-in
The template for a Project task pane add-in includes default initialization code that is designed to demonstrate basic get and set actions for data in a document for a typical Office 2013 add-in. Because Project 2013 does not support actions that write to the active project, and the **HelloProjectOData** add-in does not use the **getSelectedDataAsync** method, you can delete the script within the **Office.initialize** function, and delete the **setData** function and **getData** function in the default HelloProjectOData.js file.
The JavaScript includes global constants for the REST query and global variables that are used in several functions. The **Get ProjectData Endpoint** button calls the **setOdataUrl** function, which initializes the global variables and determines whether Project is connected with Project Web App.
The remainder of the HelloProjectOData.js file includes two functions: the **retrieveOData** function is called when the user selects **Compare All Projects**; and the **parseODataResult** function calculates averages and then populates the comparison table with values that are formatted for color and units.
### Procedure 5. To create the JavaScript code
1. Delete all code in the default HelloProjectOData.js file, and then add the global variables and **Office.initialize** function. Variable names that are all capitals imply that they are constants; they are later used with the **_pwa** variable to create the REST query in this example.
```js
var PROJDATA = "/_api/ProjectData";
var PROJQUERY = "/Projects?";
var QUERY_FILTER = "$filter=ProjectName ne 'Timesheet Administrative Work Items'";
var QUERY_SELECT1 = "&$select=ProjectId, ProjectName";
var QUERY_SELECT2 = ", ProjectCost, ProjectWork, ProjectPercentCompleted, ProjectActualCost";
var _pwa; // URL of Project Web App.
var _projectUid; // GUID of the active project.
var _docUrl; // Path of the project document.
var _odataUrl = ""; // URL of the OData service: http[s]://ServerName /ProjectServerName /_api/ProjectData
// The initialize function is required for all add-ins.
Office.initialize = function (reason) {
// Checks for the DOM to load using the jQuery ready function.
$(document).ready(function () {
// After the DOM is loaded, app-specific code can run.
});
}
```
2. Add **setOdataUrl** and related functions. The **setOdataUrl** function calls **getProjectGuid** and **getDocumentUrl** to initialize the global variables. In the [getProjectFieldAsync method](/javascript/api/office/office.document), the anonymous function for the _callback_ parameter enables the **Compare All Projects** button by using the **removeAttr** method in the jQuery library, and then displays the URL of the **ProjectData** service. If Project is not connected with Project Web App, the function throws an error, which displays a pop-up error message. The SurfaceErrors.js file includes the **throwError** method.
> [!NOTE]
> If you run Visual Studio on the Project Server computer, to use **F5** debugging, uncomment the code after the line that initializes the **_pwa** global variable. To enable using the jQuery **ajax** method when debugging on the Project Server computer, you must set the **localhost** value for the PWA URL.If you run Visual Studio on a remote computer, the **localhost** URL is not required. Before you deploy the add-in, comment out that code.
```js
function setOdataUrl() {
Office.context.document.getProjectFieldAsync(
Office.ProjectProjectFields.ProjectServerUrl,
function (asyncResult) {
if (asyncResult.status == Office.AsyncResultStatus.Succeeded) {
_pwa = String(asyncResult.value.fieldValue);
// If you debug with Visual Studio on a local Project Server computer,
// uncomment the following lines to use the localhost URL.
//var localhost = location.host.split(":", 1);
//var pwaStartPosition = _pwa.lastIndexOf("/");
//var pwaLength = _pwa.length - pwaStartPosition;
//var pwaName = _pwa.substr(pwaStartPosition, pwaLength);
//_pwa = location.protocol + "//" + localhost + pwaName;
if (_pwa.substring(0, 4) == "http") {
_odataUrl = _pwa + PROJDATA;
$("#compareProjects").removeAttr("disabled");
getProjectGuid();
}
else {
_odataUrl = "No connection!";
throwError(_odataUrl, "You are not connected to Project Web App.");
}
getDocumentUrl();
$("#projectDataEndPoint").text(_odataUrl);
}
else {
throwError(asyncResult.error.name, asyncResult.error.message);
}
}
);
}
// Get the GUID of the active project.
function getProjectGuid() {
Office.context.document.getProjectFieldAsync(
Office.ProjectProjectFields.GUID,
function (asyncResult) {
if (asyncResult.status == Office.AsyncResultStatus.Succeeded) {
_projectUid = asyncResult.value.fieldValue;
}
else {
throwError(asyncResult.error.name, asyncResult.error.message);
}
}
);
}
// Get the path of the project in Project web app, which is in the form <>\ProjectName .
function getDocumentUrl() {
_docUrl = "Document path:\r\n" + Office.context.document.url;
}
```
3. Add the **retrieveOData** function, which concatenates values for the REST query and then calls the **ajax** function in jQuery to get the requested data from the **ProjectData** service. The **support.cors** variable enables cross-origin resource sharing (CORS) with the **ajax** function. If the **support.cors** statement is missing or is set to **false**, the **ajax** function returns a **No transport** error.
> [!NOTE]
> The following code works with an on-premises installation of Project Server 2013. For Project on the web, you can use OAuth for token-based authentication. For more information, see [Addressing same-origin policy limitations in Office Add-ins](../develop/addressing-same-origin-policy-limitations.md).
In the **ajax** call, you can use either the _headers_ parameter or the _beforeSend_ parameter. The _complete_ parameter is an anonymous function so that it is in the same scope as the variables in **retrieveOData**. The function for the _complete_ parameter displays results in the **odataText** control and also calls the **parseODataResult** method to parse and display the JSON response. The _error_ parameter specifies the named **getProjectDataErrorHandler** function, which writes an error message to the **odataText** control and also uses the **throwError** method to display a pop-up message.
```js
/****************************************************************
* Functions to get and parse the Project Server reporting data.
*****************************************************************/
// Get data about all projects on Project Server,
// by using a REST query with the ajax method in jQuery.
function retrieveOData() {
var restUrl = _odataUrl + PROJQUERY + QUERY_FILTER + QUERY_SELECT1 + QUERY_SELECT2;
var accept = "application/json; odata=verbose";
accept.toLocaleLowerCase();
// Enable cross-origin scripting (required by jQuery 1.5 and later).
// This does not work with Project on the web.
$.support.cors = true;
$.ajax({
url: restUrl,
type: "GET",
contentType: "application/json",
data: "", // Empty string for the optional data.
//headers: { "Accept": accept },
beforeSend: function (xhr) {
xhr.setRequestHeader("ACCEPT", accept);
},
complete: function (xhr, textStatus) {
// Create a message to display in the text box.
var message = "\r\ntextStatus: " + textStatus +
"\r\nContentType: " + xhr.getResponseHeader("Content-Type") +
"\r\nStatus: " + xhr.status +
"\r\nResponseText:\r\n" + xhr.responseText;
// xhr.responseText is the result from an XmlHttpRequest, which
// contains the JSON response from the OData service.
parseODataResult(xhr.responseText, _projectUid);
// Write the document name, response header, status, and JSON to the odataText control.
$("#odataText").text(_docUrl);
$("#odataText").append("\r\nREST query:\r\n" + restUrl);
$("#odataText").append(message);
if (xhr.status != 200 && xhr.status != 1223 && xhr.status != 201) {
$("#odataInfo").append("<div>" + htmlEncode(restUrl) + "</div>");
}
},
error: getProjectDataErrorHandler
});
}
function getProjectDataErrorHandler(data, errorCode, errorMessage) {
$("#odataText").text("Error code: " + errorCode + "\r\nError message: \r\n"
+ errorMessage);
throwError(errorCode, errorMessage);
}
```
4. Add the **parseODataResult** method, which deserializes and processes the JSON response from the OData service. The **parseODataResult** method calculates average values of the cost and work data to an accuracy of one or two decimal places, formats values with the correct color and adds a unit ( **$**, **hrs**, or **%**), and then displays the values in specified table cells.
If the GUID of the active project matches the **ProjectId** value, the **myProjectIndex** variable is set to the project index. If **myProjectIndex** indicates the active project is published on Project Server, the **parseODataResult** method formats and displays cost and work data for that project. If the active project is not published, values for the active project are displayed as a blue **NA**.
```js
// Calculate the average values of actual cost, cost, work, and percent complete
// for all projects, and compare with the values for the current project.
function parseODataResult(oDataResult, currentProjectGuid) {
// Deserialize the JSON string into a JavaScript object.
var res = Sys.Serialization.JavaScriptSerializer.deserialize(oDataResult);
var len = res.d.results.length;
var projActualCost = 0;
var projCost = 0;
var projWork = 0;
var projPercentCompleted = 0;
var myProjectIndex = -1;
for (i = 0; i < len; i++) {
// If the current project GUID matches the GUID from the OData query,
// store the project index.
if (currentProjectGuid.toLocaleLowerCase() == res.d.results[i].ProjectId) {
myProjectIndex = i;
}
projCost += Number(res.d.results[i].ProjectCost);
projWork += Number(res.d.results[i].ProjectWork);
projActualCost += Number(res.d.results[i].ProjectActualCost);
projPercentCompleted += Number(res.d.results[i].ProjectPercentCompleted);
}
var avgProjCost = projCost / len;
var avgProjWork = projWork / len;
var avgProjActualCost = projActualCost / len;
var avgProjPercentCompleted = projPercentCompleted / len;
// Round off cost to two decimal places, and round off other values to one decimal place.
avgProjCost = avgProjCost.toFixed(2);
avgProjWork = avgProjWork.toFixed(1);
avgProjActualCost = avgProjActualCost.toFixed(2);
avgProjPercentCompleted = avgProjPercentCompleted.toFixed(1);
// Display averages in the table, with the correct units.
document.getElementById("AverageProjectCost").innerHTML = "$"
+ avgProjCost;
document.getElementById("AverageProjectActualCost").innerHTML
= "$" + avgProjActualCost;
document.getElementById("AverageProjectWork").innerHTML
= avgProjWork + " hrs";
document.getElementById("AverageProjectPercentComplete").innerHTML
= avgProjPercentCompleted + "%";
// Calculate and display values for the current project.
if (myProjectIndex != -1) {
var myProjCost = Number(res.d.results[myProjectIndex].ProjectCost);
var myProjWork = Number(res.d.results[myProjectIndex].ProjectWork);
var myProjActualCost = Number(res.d.results[myProjectIndex].ProjectActualCost);
var myProjPercentCompleted =
Number(res.d.results[myProjectIndex].ProjectPercentCompleted);
myProjCost = myProjCost.toFixed(2);
myProjWork = myProjWork.toFixed(1);
myProjActualCost = myProjActualCost.toFixed(2);
myProjPercentCompleted = myProjPercentCompleted.toFixed(1);
document.getElementById("CurrentProjectCost").innerHTML = "$" + myProjCost;
if (Number(myProjCost) <= Number(avgProjCost)) {
document.getElementById("CurrentProjectCost").style.color = "green"
}
else {
document.getElementById("CurrentProjectCost").style.color = "red"
}
document.getElementById("CurrentProjectActualCost").innerHTML = "$" + myProjActualCost;
if (Number(myProjActualCost) <= Number(avgProjActualCost)) {
document.getElementById("CurrentProjectActualCost").style.color = "green"
}
else {
document.getElementById("CurrentProjectActualCost").style.color = "red"
}
document.getElementById("CurrentProjectWork").innerHTML = myProjWork + " hrs";
if (Number(myProjWork) <= Number(avgProjWork)) {
document.getElementById("CurrentProjectWork").style.color = "red"
}
else {
document.getElementById("CurrentProjectWork").style.color = "green"
}
document.getElementById("CurrentProjectPercentComplete").innerHTML = myProjPercentCompleted + "%";
if (Number(myProjPercentCompleted) <= Number(avgProjPercentCompleted)) {
document.getElementById("CurrentProjectPercentComplete").style.color = "red"
}
else {
document.getElementById("CurrentProjectPercentComplete").style.color = "green"
}
}
else {
document.getElementById("CurrentProjectCost").innerHTML = "NA";
document.getElementById("CurrentProjectCost").style.color = "blue"
document.getElementById("CurrentProjectActualCost").innerHTML = "NA";
document.getElementById("CurrentProjectActualCost").style.color = "blue"
document.getElementById("CurrentProjectWork").innerHTML = "NA";
document.getElementById("CurrentProjectWork").style.color = "blue"
document.getElementById("CurrentProjectPercentComplete").innerHTML = "NA";
document.getElementById("CurrentProjectPercentComplete").style.color = "blue"
}
}
```
## Testing the HelloProjectOData add-in
To test and debug the **HelloProjectOData** add-in with Visual Studio 2015, Project Professional 2013 must be installed on the development computer. To enable different test scenarios, ensure that you can choose whether Project opens for files on the local computer or connects with Project Web App. For example, do the following steps:
1. On the **FILE** tab on the ribbon, choose the **Info** tab in the Backstage view, and then choose **Manage Accounts**.
2. In the **Project web app Accounts** dialog box, the **Available accounts** list can have multiple Project Web App accounts in addition to the local **Computer** account. In the **When starting** section, select **Choose an account**.
3. Close Project so that Visual Studio can start it for debugging the add-in.
Basic tests should include the following:
- Run the add-in from Visual Studio, and then open a published project from Project Web App that contains cost and work data. Verify that the add-in displays the **ProjectData** endpoint and correctly displays the cost and work data in the table. You can use the output in the **odataText** control to check the REST query and other information.
- Run the add-in again, where you choose the local computer profile in the **Login** dialog box when Project starts. Open a local .mpp file, and then test the add-in. Verify that the add-in displays an error message when you try to get the **ProjectData** endpoint.
- Run the add-in again, where you create a project that has tasks with cost and work data. You can save the project to Project Web App, but don't publish it. Verify that the add-in displays data from Project Server, but **NA** for the current project.
### Procedure 6. To test the add-in
1. Run Project Professional 2013, connect with Project Web App, and then create a test project. Assign tasks to local resources or to enterprise resources, set various values of percent complete on some tasks, and then publish the project. Quit Project, which enables Visual Studio to start Project for debugging the add-in.
2. In Visual Studio, press **F5**. Log on to Project Web App, and then open the project that you created in the previous step. You can open the project in read-only mode or in edit mode.
3. On the **PROJECT** tab of the ribbon, in the **Office Add-ins** drop-down list, select **Hello ProjectData** (see Figure 5). The **Compare All Projects** button should be disabled.
*Figure 5. Starting the HelloProjectOData add-in*
4. In the **Hello ProjectData** task pane, select **Get ProjectData Endpoint**. The **projectDataEndPoint** line should show the URL of the **ProjectData** service, and the **Compare All Projects** button should be enabled (see Figure 6).
5. Select **Compare All Projects**. The add-in may pause while it retrieves data from the **ProjectData** service, and then it should display the formatted average and current values in the table.
*Figure 6. Viewing results of the REST query*
6. Examine output in the text box. It should show the document path, REST query, status information, and JSON results from the calls to **ajax** and **parseODataResult**. The output helps to understand, create, and debug code in the **parseODataResult** method such as `projCost += Number(res.d.results[i].ProjectCost);`.
Following is an example of the output with line breaks and spaces added to the text for clarity, for three projects in a Project Web App instance:
```json
Document path: <>\WinProj test1
REST query:
http://sphvm-37189/pwa/_api/ProjectData/Projects?$filter=ProjectName ne 'Timesheet Administrative Work Items'
&$select=ProjectId, ProjectName, ProjectCost, ProjectWork, ProjectPercentCompleted, ProjectActualCost
textStatus: success
ContentType: application/json;odata=verbose;charset=utf-8
Status: 200
ResponseText:
{"d":{"results":[
{"__metadata":
{"id":"http://sphvm-37189/pwa/_api/ProjectData/Projects(guid'ce3d0d65-3904-e211-96cd-00155d157123')",
"uri":"http://sphvm-37189/pwa/_api/ProjectData/Projects(guid'ce3d0d65-3904-e211-96cd-00155d157123')",
"type":"ReportingData.Project"},
"ProjectId":"ce3d0d65-3904-e211-96cd-00155d157123",
"ProjectActualCost":"0.000000",
"ProjectCost":"0.000000",
"ProjectName":"Task list created in PWA",
"ProjectPercentCompleted":0,
"ProjectWork":"16.000000"},
{"__metadata":
{"id":"http://sphvm-37189/pwa/_api/ProjectData/Projects(guid'c31023fc-1404-e211-86b2-3c075433b7bd')",
"uri":"http://sphvm-37189/pwa/_api/ProjectData/Projects(guid'c31023fc-1404-e211-86b2-3c075433b7bd')",
"type":"ReportingData.Project"},
"ProjectId":"c31023fc-1404-e211-86b2-3c075433b7bd",
"ProjectActualCost":"700.000000",
"ProjectCost":"2400.000000",
"ProjectName":"WinProj test 2",
"ProjectPercentCompleted":29,
"ProjectWork":"48.000000"},
{"__metadata":
{"id":"http://sphvm-37189/pwa/_api/ProjectData/Projects(guid'dc81fbb2-b801-e211-9d2a-3c075433b7bd')",
"uri":"http://sphvm-37189/pwa/_api/ProjectData/Projects(guid'dc81fbb2-b801-e211-9d2a-3c075433b7bd')",
"type":"ReportingData.Project"},
"ProjectId":"dc81fbb2-b801-e211-9d2a-3c075433b7bd",
"ProjectActualCost":"1900.000000",
"ProjectCost":"5200.000000",
"ProjectName":"WinProj test1",
"ProjectPercentCompleted":37,
"ProjectWork":"104.000000"}
]}}
```
7. Stop debugging (press **Shift + F5**), and then press **F5** again to run a new instance of Project. In the **Login** dialog box, choose the local **Computer** profile, not Project Web App. Create or open a local project .mpp file, open the **Hello ProjectData** task pane, and then select **Get ProjectData Endpoint**. The add-in should show a **No connection!** error (see Figure 7), and the **Compare All Projects** button should remain disabled.
*Figure 7. Using the add-in without a Project web app connection*
8. Stop debugging, and then press **F5** again. Log on to Project Web App, and then create a project that contains cost and work data. You can save the project, but don't publish it.
In the **Hello ProjectData** task pane, when you select **Compare All Projects**, you should see a blue **NA** for fields in the **Current** column (see Figure 8).
*Figure 8. Comparing an unpublished project with other projects*
Even if your add-in is working correctly in the previous tests, there are other tests that should be run. For example:
- Open a project from Project Web App that has no cost or work data for the tasks. You should see values of zero in the fields in the **Current** column.
- Test a project that has no tasks.
- If you modify the add-in and publish it, you should run similar tests again with the published add-in. For other considerations, see [Next steps](#next-steps).
> [!NOTE]
> There are limits to the amount of data that can be returned in one query of the **ProjectData** service; the amount of data varies by entity. For example, the **Projects** entity set has a default limit of 100 projects per query, but the **Risks** entity set has a default limit of 200. For a production installation, the code in the **HelloProjectOData** example should be modified to enable queries of more than 100 projects. For more information, see [Next steps](#next-steps) and [Querying OData feeds for Project reporting data](/previous-versions/office/project-odata/jj163048(v=office.15)).
## Example code for the HelloProjectOData add-in
### HelloProjectOData.html file
The following code is in the `Pages\HelloProjectOData.html` file of the **HelloProjectODataWeb** project.
```HTML
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8" />
<meta http-equiv="X-UA-Compatible" content="IE=Edge" />
<title>Test ProjectData Service</title>
<link rel="stylesheet" type="text/css" href="../Content/Office.css" />
<!-- Add your CSS styles to the following file -->
<link rel="stylesheet" type="text/css" href="../Content/App.css" />
<!-- Use the CDN reference to the mini-version of jQuery when deploying your add-in. -->
<!--<script src="http://ajax.aspnetcdn.com/ajax/jquery/jquery-1.9.0.min.js"></script> -->
<script src="../Scripts/jquery-1.7.1.js"></script>
<!-- Use the CDN reference to Office.js when deploying your add-in -->
<!--<script src="https://appsforoffice.microsoft.com/lib/1/hosted/office.js"></script>-->
<!-- Use the local script references for Office.js to enable offline debugging -->
<script src="../Scripts/Office/1.0/MicrosoftAjax.js"></script>
<script src="../Scripts/Office/1.0/Office.js"></script>
<!-- Add your JavaScript to the following files -->
<script src="../Scripts/HelloProjectOData.js"></script>
<script src="../Scripts/SurfaceErrors.js"></script>
</head>
<body>
<div id="SectionContent">
<div id="odataQueries">
ODATA REST QUERY
</div>
<div id="odataInfo">
<button class="button-wide" onclick="setOdataUrl()">Get ProjectData Endpoint</button>
<br />
<br />
<span class="rest" id="projectDataEndPoint">Endpoint of the
<strong>ProjectData</strong> service</span>
<br />
</div>
<div id="compareProjectData">
<button class="button-wide" disabled="disabled" id="compareProjects"
onclick="retrieveOData()">
Compare All Projects</button>
<br />
</div>
</div>
<div id="corpInfo">
<table class="infoTable" aria-readonly="True" style="width: 100%;">
<tr>
<td class="heading_leftCol"></td>
<td class="heading_midCol"><strong>Average</strong></td>
<td class="heading_rightCol"><strong>Current</strong></td>
</tr>
<tr>
<td class="row_leftCol"><strong>Project Cost</strong></td>
<td class="row_midCol" id="AverageProjectCost">&nbsp;</td>
<td class="row_rightCol" id="CurrentProjectCost">&nbsp;</td>
</tr>
<tr>
<td class="row_leftCol"><strong>Project Actual Cost</strong></td>
<td class="row_midCol" id="AverageProjectActualCost">&nbsp;</td>
<td class="row_rightCol" id="CurrentProjectActualCost">&nbsp;</td>
</tr>
<tr>
<td class="row_leftCol"><strong>Project Work</strong></td>
<td class="row_midCol" id="AverageProjectWork">&nbsp;</td>
<td class="row_rightCol" id="CurrentProjectWork">&nbsp;</td>
</tr>
<tr>
<td class="row_leftCol"><strong>Project % Complete</strong></td>
<td class="row_midCol" id="AverageProjectPercentComplete">&nbsp;</td>
<td class="row_rightCol" id="CurrentProjectPercentComplete">&nbsp;</td>
</tr>
</table>
</div>
<img alt="Corporation" class="logo" src="../../images/NewLogo.png" />
<br />
<textarea id="odataText" rows="12" cols="40"></textarea>
</body>
</html>
```
### HelloProjectOData.js file
The following code is in the `Scripts\Office\HelloProjectOData.js` file of the **HelloProjectODataWeb** project.
```js
/* File: HelloProjectOData.js
* JavaScript functions for the HelloProjectOData example task pane app.
* October 2, 2012
*/
var PROJDATA = "/_api/ProjectData";
var PROJQUERY = "/Projects?";
var QUERY_FILTER = "$filter=ProjectName ne 'Timesheet Administrative Work Items'";
var QUERY_SELECT1 = "&$select=ProjectId, ProjectName";
var QUERY_SELECT2 = ", ProjectCost, ProjectWork, ProjectPercentCompleted, ProjectActualCost";
var _pwa; // URL of Project Web App.
var _projectUid; // GUID of the active project.
var _docUrl; // Path of the project document.
var _odataUrl = ""; // URL of the OData service: http[s]://ServerName /ProjectServerName /_api/ProjectData
// The initialize function is required for all add-ins.
Office.initialize = function (reason) {
// Checks for the DOM to load using the jQuery ready function.
$(document).ready(function () {
// After the DOM is loaded, app-specific code can run.
});
}
// Set the global variables, enable the Compare All Projects button,
// and display the URL of the ProjectData service.
// Display an error if Project is not connected with Project Web App.
function setOdataUrl() {
Office.context.document.getProjectFieldAsync(
Office.ProjectProjectFields.ProjectServerUrl,
function (asyncResult) {
if (asyncResult.status == Office.AsyncResultStatus.Succeeded) {
_pwa = String(asyncResult.value.fieldValue);
// If you debug with Visual Studio on a local Project Server computer,
// uncomment the following lines to use the localhost URL.
//var localhost = location.host.split(":", 1);
//var pwaStartPosition = _pwa.lastIndexOf("/");
//var pwaLength = _pwa.length - pwaStartPosition;
//var pwaName = _pwa.substr(pwaStartPosition, pwaLength);
//_pwa = location.protocol + "//" + localhost + pwaName;
if (_pwa.substring(0, 4) == "http") {
_odataUrl = _pwa + PROJDATA;
$("#compareProjects").removeAttr("disabled");
getProjectGuid();
}
else {
_odataUrl = "No connection!";
throwError(_odataUrl, "You are not connected to Project Web App.");
}
getDocumentUrl();
$("#projectDataEndPoint").text(_odataUrl);
}
else {
throwError(asyncResult.error.name, asyncResult.error.message);
}
}
);
}
// Get the GUID of the active project.
function getProjectGuid() {
Office.context.document.getProjectFieldAsync(
Office.ProjectProjectFields.GUID,
function (asyncResult) {
if (asyncResult.status == Office.AsyncResultStatus.Succeeded) {
_projectUid = asyncResult.value.fieldValue;
}
else {
throwError(asyncResult.error.name, asyncResult.error.message);
}
}
);
}
// Get the path of the project in Project web app, which is in the form <>\ProjectName .
function getDocumentUrl() {
_docUrl = "Document path:\r\n" + Office.context.document.url;
}
/****************************************************************
* Functions to get and parse the Project Server reporting data.
*****************************************************************/
// Get data about all projects on Project Server,
// by using a REST query with the ajax method in jQuery.
function retrieveOData() {
var restUrl = _odataUrl + PROJQUERY + QUERY_FILTER + QUERY_SELECT1 + QUERY_SELECT2;
var accept = "application/json; odata=verbose";
accept.toLocaleLowerCase();
// Enable cross-origin scripting (required by jQuery 1.5 and later).
// This does not work with Project on the web.
$.support.cors = true;
$.ajax({
url: restUrl,
type: "GET",
contentType: "application/json",
data: "", // Empty string for the optional data.
//headers: { "Accept": accept },
beforeSend: function (xhr) {
xhr.setRequestHeader("ACCEPT", accept);
},
complete: function (xhr, textStatus) {
// Create a message to display in the text box.
var message = "\r\ntextStatus: " + textStatus +
"\r\nContentType: " + xhr.getResponseHeader("Content-Type") +
"\r\nStatus: " + xhr.status +
"\r\nResponseText:\r\n" + xhr.responseText;
// xhr.responseText is the result from an XmlHttpRequest, which
// contains the JSON response from the OData service.
parseODataResult(xhr.responseText, _projectUid);
// Write the document name, response header, status, and JSON to the odataText control.
$("#odataText").text(_docUrl);
$("#odataText").append("\r\nREST query:\r\n" + restUrl);
$("#odataText").append(message);
if (xhr.status != 200 && xhr.status != 1223 && xhr.status != 201) {
$("#odataInfo").append("<div>" + htmlEncode(restUrl) + "</div>");
}
},
error: getProjectDataErrorHandler
});
}
function getProjectDataErrorHandler(data, errorCode, errorMessage) {
$("#odataText").text("Error code: " + errorCode + "\r\nError message: \r\n"
+ errorMessage);
throwError(errorCode, errorMessage);
}
// Calculate the average values of actual cost, cost, work, and percent complete
// for all projects, and compare with the values for the current project.
function parseODataResult(oDataResult, currentProjectGuid) {
// Deserialize the JSON string into a JavaScript object.
var res = Sys.Serialization.JavaScriptSerializer.deserialize(oDataResult);
var len = res.d.results.length;
var projActualCost = 0;
var projCost = 0;
var projWork = 0;
var projPercentCompleted = 0;
var myProjectIndex = -1;
for (i = 0; i < len; i++) {
// If the current project GUID matches the GUID from the OData query,
// then store the project index.
if (currentProjectGuid.toLocaleLowerCase() == res.d.results[i].ProjectId) {
myProjectIndex = i;
}
projCost += Number(res.d.results[i].ProjectCost);
projWork += Number(res.d.results[i].ProjectWork);
projActualCost += Number(res.d.results[i].ProjectActualCost);
projPercentCompleted += Number(res.d.results[i].ProjectPercentCompleted);
}
var avgProjCost = projCost / len;
var avgProjWork = projWork / len;
var avgProjActualCost = projActualCost / len;
var avgProjPercentCompleted = projPercentCompleted / len;
// Round off cost to two decimal places, and round off other values to one decimal place.
avgProjCost = avgProjCost.toFixed(2);
avgProjWork = avgProjWork.toFixed(1);
avgProjActualCost = avgProjActualCost.toFixed(2);
avgProjPercentCompleted = avgProjPercentCompleted.toFixed(1);
// Display averages in the table, with the correct units.
document.getElementById("AverageProjectCost").innerHTML = "$"
+ avgProjCost;
document.getElementById("AverageProjectActualCost").innerHTML
= "$" + avgProjActualCost;
document.getElementById("AverageProjectWork").innerHTML
= avgProjWork + " hrs";
document.getElementById("AverageProjectPercentComplete").innerHTML
= avgProjPercentCompleted + "%";
// Calculate and display values for the current project.
if (myProjectIndex != -1) {
var myProjCost = Number(res.d.results[myProjectIndex].ProjectCost);
var myProjWork = Number(res.d.results[myProjectIndex].ProjectWork);
var myProjActualCost = Number(res.d.results[myProjectIndex].ProjectActualCost);
var myProjPercentCompleted = Number(res.d.results[myProjectIndex].ProjectPercentCompleted);
myProjCost = myProjCost.toFixed(2);
myProjWork = myProjWork.toFixed(1);
myProjActualCost = myProjActualCost.toFixed(2);
myProjPercentCompleted = myProjPercentCompleted.toFixed(1);
document.getElementById("CurrentProjectCost").innerHTML = "$" + myProjCost;
if (Number(myProjCost) <= Number(avgProjCost)) {
document.getElementById("CurrentProjectCost").style.color = "green"
}
else {
document.getElementById("CurrentProjectCost").style.color = "red"
}
document.getElementById("CurrentProjectActualCost").innerHTML = "$" + myProjActualCost;
if (Number(myProjActualCost) <= Number(avgProjActualCost)) {
document.getElementById("CurrentProjectActualCost").style.color = "green"
}
else {
document.getElementById("CurrentProjectActualCost").style.color = "red"
}
document.getElementById("CurrentProjectWork").innerHTML = myProjWork + " hrs";
if (Number(myProjWork) <= Number(avgProjWork)) {
document.getElementById("CurrentProjectWork").style.color = "red"
}
else {
document.getElementById("CurrentProjectWork").style.color = "green"
}
document.getElementById("CurrentProjectPercentComplete").innerHTML = myProjPercentCompleted + "%";
if (Number(myProjPercentCompleted) <= Number(avgProjPercentCompleted)) {
document.getElementById("CurrentProjectPercentComplete").style.color = "red"
}
else {
document.getElementById("CurrentProjectPercentComplete").style.color = "green"
}
}
else { // The current project is not published.
document.getElementById("CurrentProjectCost").innerHTML = "NA";
document.getElementById("CurrentProjectCost").style.color = "blue"
document.getElementById("CurrentProjectActualCost").innerHTML = "NA";
document.getElementById("CurrentProjectActualCost").style.color = "blue"
document.getElementById("CurrentProjectWork").innerHTML = "NA";
document.getElementById("CurrentProjectWork").style.color = "blue"
document.getElementById("CurrentProjectPercentComplete").innerHTML = "NA";
document.getElementById("CurrentProjectPercentComplete").style.color = "blue"
}
}
```
### App.css file
The following code is in the `Content\App.css` file of the **HelloProjectODataWeb** project.
```css
/*
* File: App.css for the HelloProjectOData app.
* Updated: 10/2/2012
*/
body
{
font-size: 11pt;
}
h1
{
font-size: 22pt;
}
h2
{
font-size: 16pt;
}
/******************************************************************
Code label class
******************************************************************/
.rest
{
font-family: 'Courier New';
font-size: 0.9em;
}
/******************************************************************
Button classes
******************************************************************/
.button-wide {
width: 210px;
margin-top: 2px;
}
.button-narrow
{
width: 80px;
margin-top: 2px;
}
/******************************************************************
Table styles
******************************************************************/
.infoTable
{
text-align: center;
vertical-align: middle
}
.heading_leftCol
{
width: 20px;
height: 20px;
}
.heading_midCol
{
width: 100px;
height: 20px;
font-size: medium;
font-weight: bold;
}
.heading_rightCol
{
width: 101px;
height: 20px;
font-size: medium;
font-weight: bold;
}
.row_leftCol
{
width: 20px;
font-size: small;
font-weight: bold;
}
.row_midCol
{
width: 100px;
}
.row_rightCol
{
width: 101px;
}
.logo
{
width: 135px;
height: 53px;
}
```
### SurfaceErrors.js file
You can copy code for the SurfaceErrors.js file from the _Robust Programming_ section of [Create your first task pane add-in for Project 2013 by using a text editor](../project/create-your-first-task-pane-add-in-for-project-by-using-a-text-editor.md).
## Next steps
If **HelloProjectOData** were a production add-in to be sold in AppSource or distributed in a SharePoint app catalog, it would be designed differently. For example, there would be no debug output in a text box, and probably no button to get the **ProjectData** endpoint. You would also have to rewrite the **retireveOData** function to handle Project Web App instances that have more than 100 projects.
The add-in should contain additional error checks, plus logic to catch and explain or show edge cases. For example, if a Project Web App instance has 1000 projects with an average duration of five days and average cost of $2400, and the active project is the only one that has a duration longer than 20 days, the cost and work comparison would be skewed. That could be shown with a frequency graph. You could add options to display duration, compare similar length projects, or compare projects from the same or different departments. Or, add a way for the user to select from a list of fields to display.
For other queries of the **ProjectData** service, there are limits to the length of the query string, which affects the number of steps that a query can take from a parent collection to an object in a child collection. For example, a two-step query of **Projects** to **Tasks** to task item works, but a three-step query such as **Projects** to **Tasks** to **Assignments** to assignment item may exceed the default maximum URL length. For more information, see [Querying OData feeds for Project reporting data](/previous-versions/office/project-odata/jj163048(v=office.15)).
If you modify the **HelloProjectOData** add-in for production use, do the following steps:
- In the HelloProjectOData.html file, for better performance, change the office.js reference from the local project to the CDN reference:
```HTML
<script src="https://appsforoffice.microsoft.com/lib/1/hosted/office.js"></script>
```
- Rewrite the **retrieveOData** function to enable queries of more than 100 projects. For example, you could get the number of projects with a `~/ProjectData/Projects()/$count` query, and use the _$skip_ operator and _$top_ operator in the REST query for project data. Run multiple queries in a loop, and then average the data from each query. Each query for project data would be of the form:
`~/ProjectData/Projects()?skip= [numSkipped]&$top=100&$filter=[filter]&$select=[field1,field2, ???????]`
For more information, see [OData System Query Options Using the REST Endpoint](/previous-versions/dynamicscrm-2015/developers-guide/gg309461(v=crm.7)). You can also use the [Set-SPProjectOdataConfiguration](/powershell/module/sharepoint-server/Set-SPProjectOdataConfiguration?view=sharepoint-ps) command in Windows PowerShell to override the default page size for a query of the **Projects** entity set (or any of the 33 entity sets). See [ProjectData - Project OData service reference](/previous-versions/office/project-odata/jj163015(v=office.15)).
- To deploy the add-in, see [Publish your Office Add-in](../publish/publish.md).
## See also
- [Task pane add-ins for Project](project-add-ins.md)
- [Create your first task pane add-in for Project 2013 by using a text editor](create-your-first-task-pane-add-in-for-project-by-using-a-text-editor.md)
- [ProjectData - Project OData service reference](/previous-versions/office/project-odata/jj163015(v=office.15))
- [Office Add-ins XML manifest](../develop/add-in-manifests.md)
- [Publish your Office Add-in](../publish/publish.md)
| 54.475512 | 656 | 0.67023 | eng_Latn | 0.854345 |
08bf728ee7c06b4df831dc6e95d947bfa9ebcfc4 | 521 | md | Markdown | add/metadata/System.Activities.Statements/CompensableActivity.meta.md | ferdeen/dotnet-api-docs | 233109a79714842b6ce02e919ad1cb078267f434 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-06-16T22:24:36.000Z | 2020-06-16T22:24:36.000Z | add/metadata/System.Activities.Statements/CompensableActivity.meta.md | ferdeen/dotnet-api-docs | 233109a79714842b6ce02e919ad1cb078267f434 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | add/metadata/System.Activities.Statements/CompensableActivity.meta.md | ferdeen/dotnet-api-docs | 233109a79714842b6ce02e919ad1cb078267f434 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-11-26T07:32:59.000Z | 2019-11-26T07:32:59.000Z | ---
uid: System.Activities.Statements.CompensableActivity
---
---
uid: System.Activities.Statements.CompensableActivity.#ctor
---
---
uid: System.Activities.Statements.CompensableActivity.Body
---
---
uid: System.Activities.Statements.CompensableActivity.CompensationHandler
---
---
uid: System.Activities.Statements.CompensableActivity.Variables
---
---
uid: System.Activities.Statements.CompensableActivity.CancellationHandler
---
---
uid: System.Activities.Statements.CompensableActivity.ConfirmationHandler
---
| 18.607143 | 73 | 0.786948 | yue_Hant | 0.926135 |
08c091f40c093123673b8ed342ba663d971e3b3c | 61 | md | Markdown | README.md | Enestst/euler-project | c72ed812b9bc3504d1da86f9bc80159e33c23e9d | [
"MIT"
] | null | null | null | README.md | Enestst/euler-project | c72ed812b9bc3504d1da86f9bc80159e33c23e9d | [
"MIT"
] | null | null | null | README.md | Enestst/euler-project | c72ed812b9bc3504d1da86f9bc80159e33c23e9d | [
"MIT"
] | null | null | null | # euler-project
some solutions of euler project with python.
| 20.333333 | 44 | 0.803279 | eng_Latn | 0.997452 |
08c0e4ae64a462e595ddc8ff2b579e6cad048841 | 2,533 | md | Markdown | docs/framework/unmanaged-api/debugging/icordebugprocess5-gettypefields-method.md | lucieva/docs.cs-cz | a688d6511d24a48fe53a201e160e9581f2effbf4 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2018-12-19T17:04:23.000Z | 2018-12-19T17:04:23.000Z | docs/framework/unmanaged-api/debugging/icordebugprocess5-gettypefields-method.md | lucieva/docs.cs-cz | a688d6511d24a48fe53a201e160e9581f2effbf4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/unmanaged-api/debugging/icordebugprocess5-gettypefields-method.md | lucieva/docs.cs-cz | a688d6511d24a48fe53a201e160e9581f2effbf4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: ICorDebugProcess5::GetTypeFields – metoda
ms.date: 03/30/2017
api_name:
- ICorDebugProcess5.GetTypeFields
api_location:
- mscordbi.dll
api_type:
- COM
f1_keywords:
- ICorDebugProcess5::GetTypeFields
helpviewer_keywords:
- GetTypeFields method, ICorDebugProcess5 interface [.NET Framework debugging]
- ICorDebugProcess5::GetTypeFields method [.NET Framework debugging]
ms.assetid: 6a0ad3ee-dacb-47e9-abae-4536bcc4804b
topic_type:
- apiref
author: rpetrusha
ms.author: ronpet
ms.openlocfilehash: 214fc97e41d8d220547a5f8bd28117ff411fa89b
ms.sourcegitcommit: 3d5d33f384eeba41b2dff79d096f47ccc8d8f03d
ms.translationtype: MT
ms.contentlocale: cs-CZ
ms.lasthandoff: 05/04/2018
ms.locfileid: "33418402"
---
# <a name="icordebugprocess5gettypefields-method"></a>ICorDebugProcess5::GetTypeFields – metoda
Poskytuje informace o pole, které patří do typu.
## <a name="syntax"></a>Syntaxe
```
HRESULT GetTypeFields(
[in] COR_TYPEID id,
[in] ULONG32 celt,
[out] COR_FIELD fields[],
[out] ULONG32 *pceltNeeded
);
```
#### <a name="parameters"></a>Parametry
`id`
[v] Identifikátor typu je načíst informace o jejichž pole.
`celt`
[v] Počet [cor_field –](../../../../docs/framework/unmanaged-api/debugging/cor-field-structure.md) objekty, jejichž informace pole se mají být načteny.
`fields`
[out] Pole [cor_field –](../../../../docs/framework/unmanaged-api/debugging/cor-field-structure.md) objekty, které obsahují informace o pole, které patří k typu.
`pceltNeeded`
[out] Ukazatel na počet [cor_field –](../../../../docs/framework/unmanaged-api/debugging/cor-field-structure.md) objektů obsažených v `fields`.
## <a name="remarks"></a>Poznámky
`celt` Parametr, který určuje počet polí, jejichž pole informace metoda používá k naplnění `fields`, by měla odpovídat hodnotě `COR_TYPE_LAYOUT::numFields` pole.
## <a name="requirements"></a>Požadavky
**Platformy:** najdete v části [požadavky na systém](../../../../docs/framework/get-started/system-requirements.md).
**Záhlaví:** CorDebug.idl, CorDebug.h
**Knihovna:** CorGuids.lib
**Verze rozhraní .NET framework:** [!INCLUDE[net_current_v45plus](../../../../includes/net-current-v45plus-md.md)]
## <a name="see-also"></a>Viz také
[ICorDebugProcess5 – rozhraní](../../../../docs/framework/unmanaged-api/debugging/icordebugprocess5-interface.md)
[Rozhraní pro ladění](../../../../docs/framework/unmanaged-api/debugging/debugging-interfaces.md)
| 36.710145 | 164 | 0.711804 | ces_Latn | 0.720174 |
08c119bbf2d798aa6063aee2e432423b5f7f85ed | 223 | md | Markdown | wiki/specs_tfgrid3/tfgrid_substrate/substrate_readme.md | LeeSmet/info_threefold_pub | 1047d8a6e895947bf12b21255e285f4eb798804a | [
"Apache-2.0"
] | 1 | 2022-01-03T12:26:07.000Z | 2022-01-03T12:26:07.000Z | wiki/specs_tfgrid3/tfgrid_substrate/substrate_readme.md | LeeSmet/info_threefold_pub | 1047d8a6e895947bf12b21255e285f4eb798804a | [
"Apache-2.0"
] | 52 | 2021-09-28T15:33:06.000Z | 2022-03-14T15:40:06.000Z | wiki/specs_tfgrid3/tfgrid_substrate/substrate_readme.md | LeeSmet/info_threefold_pub | 1047d8a6e895947bf12b21255e285f4eb798804a | [
"Apache-2.0"
] | 1 | 2021-09-22T14:47:43.000Z | 2021-09-22T14:47:43.000Z | # Grid3 Substrate
Substrate is the main technology used for our Blockchain needs.
- [usage](substrate_usage)
- [griddb](griddb)
- [grid substrate smart contract](grid_substrate_contract)
- [Bridge](grid_substrate_bridge) | 27.875 | 63 | 0.784753 | eng_Latn | 0.921703 |
08c14be2b02603f8109ce0331e2d9a32ab2b98dc | 473 | md | Markdown | _posts/2021-07-08/2021-07-03-Colombian-pussy-tastes-better-and-thats-a-fact-20210703135343373508.md | ipussy/ipussy.github.io | 95d19a74e38bb54303cf18057a99a57c783e76bf | [
"Apache-2.0"
] | null | null | null | _posts/2021-07-08/2021-07-03-Colombian-pussy-tastes-better-and-thats-a-fact-20210703135343373508.md | ipussy/ipussy.github.io | 95d19a74e38bb54303cf18057a99a57c783e76bf | [
"Apache-2.0"
] | null | null | null | _posts/2021-07-08/2021-07-03-Colombian-pussy-tastes-better-and-thats-a-fact-20210703135343373508.md | ipussy/ipussy.github.io | 95d19a74e38bb54303cf18057a99a57c783e76bf | [
"Apache-2.0"
] | null | null | null | ---
title: "Colombian pussy tastes better and that's a fact."
metadate: "hide"
categories: [ Pussy ]
image: "https://external-preview.redd.it/qHBCLcCImt1X80rMgOmmhpCIk-IiCQBUq8OTX9jQzJI.jpg?auto=webp&s=ec5b3db39abeee1087757ea6e081cdac527f91ae"
thumb: "https://external-preview.redd.it/qHBCLcCImt1X80rMgOmmhpCIk-IiCQBUq8OTX9jQzJI.jpg?width=1080&crop=smart&auto=webp&s=568e13f1fe32a2c216d1f1b5c6f07022c9b7f6ba"
visit: ""
---
Colombian pussy tastes better and that's a fact.
| 47.3 | 164 | 0.809725 | kor_Hang | 0.132716 |
08c1d81b88420a47aafc2a6de14f061fdd1973fd | 7,586 | md | Markdown | docs/controls/charts/stockchart/data-binding.md | davidda/kendo-ui-core | 1cd612b2ccc4d6bdfc222948b74af1c4d37e2d9f | [
"Apache-2.0"
] | 1 | 2020-11-15T10:40:31.000Z | 2020-11-15T10:40:31.000Z | docs/controls/charts/stockchart/data-binding.md | davidda/kendo-ui-core | 1cd612b2ccc4d6bdfc222948b74af1c4d37e2d9f | [
"Apache-2.0"
] | null | null | null | docs/controls/charts/stockchart/data-binding.md | davidda/kendo-ui-core | 1cd612b2ccc4d6bdfc222948b74af1c4d37e2d9f | [
"Apache-2.0"
] | null | null | null | ---
title: Data Binding
page_title: jQuery Charts Documentation | StockChart Data Binding | Kendo UI
description: "Get started with the jQuery StockChart by Kendo UI and learn how to bind it to data."
slug: databinding_kendoui_stockcharts
position: 2
---
# Data Binding
The Kendo UI StockChart provides the [single data-source](#single-data-source-mode) and [master and navigator data-source](#master-and-navigator-data-source-mode) binding modes.
In both modes, you have to set a [`dateField`](/api/javascript/dataviz/ui/stock-chart/configuration/datefield) to indicate the field that contains the date of the data item.
> * The StockChart supports only binding to time series.
> * Discrete categories and XY or Scatter series are not supported.
## Getting Started
You can bind the StockChart to both local and remote data over its DataSource.
The following example demonstrates a service that returns stock price history data as JSON.
[
{
"Date": "2000/01/03",
"Open": 41.62,
"High": 41.69,
"Low": 39.81,
"Close": 40.12,
"Volume": 2632000
},
...
]
The following example demonstrates how to bind the StockChart to the remote service.
$("#stockChart").kendoStockChart({
dataSource: {
transport: {
read: "/stock?symbol=BA"
}
},
dateField: "Date"
});
The following example demonstrates how to define the main and the Navigator series.
$("#stockChart").kendoStockChart({
dataSource: {
transport: {
read: "/stock?symbol=BA"
}
},
dateField: "Date"
series: [{
type: "candlestick",
openField: "Open",
highField: "High",
lowField: "Low",
closeField: "Close"
}],
navigator: {
series: {
type: "area",
field: "Volume"
}
}
});
## Single Data-Source Mode
In the single data-source binding mode, the StockChart is set up with a single data source and that single Data Source instance is used for both the main and the **Navigator** panes. The single data-source binding mode is used for all series in the Chart including the **Navigator** pane. The Data Source is [fetched](/api/javascript/data/datasource/methods/fetch) once and is filtered internally by the Chart. No additional requests will be made unless the API methods of the Data Source are invoked. For a runnable example, refer to the [demo on the basic usage of the StockChart](https://demos.telerik.com/kendo-ui/financial/virtualization).
The following example demonstrates a StockChart in a single data-source binding mode.
```dojo
<div id="stock-chart"></div>
<script>
$("#stock-chart").kendoStockChart({
dataSource: {
data: [{
"Date": "2016/01/01",
"Open": 41.62,
"High": 41.69,
"Low": 39.81,
"Close": 40.12,
"Volume": 2632000
}, {
"Date": "2016/03/01",
"Open": 40.62,
"High": 39.69,
"Low": 40.81,
"Close": 39.12,
"Volume": 2631986
}
]
},
dateField: "Date",
series: [{
type: "candlestick",
openField: "Open",
highField: "High",
lowField: "Low",
closeField: "Close"
}],
navigator: {
series: {
type: "area",
field: "Volume"
}
}
});
</script>
```
### Master and Navigator Data-Source Mode
You can configure a second data source to load the **Navigator** data usually with reduced time resolution. This approach enables the filtering of the main data source and can be made more efficient. In the master and navigator data-source binding mode, the StockChart is set up with two data source instances—one for the main chart (master) and one for the **Navigator** pane (navigator). For a runnable example, refer to the [demo on virtualization](https://demos.telerik.com/kendo-ui/financial/virtualization).
This mode is useful when the service is expected to provide views over the data with a different time resolution. The navigator can then load a low resolution preview while the main data source handles the detailed data.
The data for the **Navigator** will be fetched only once and without any filters. To change this behavior, change its configuration or call methods directly on the DataSource. The fetched data will be displayed in its entirety in the **Navigator** pane.
The main data source will be filtered based on the selected date range before being fetched. It is recommended that you use [server filtering](/api/javascript/data/datasource/configuration/serverfiltering) to make sure that only the visible range data is transferred. Even without applying server filtering, a reduction in the processing time will occur which is needed by the Chart to display the data.
Each subsequent pan, zoom, and selection operation will update the filters on the main data source and fetch it.
The following example demonstrates a StockChart in the master and navigator data-source binding mode.
```dojo
<div id="stock-chart"></div>
<script>
var stockDataSchema = {
model: {
fields: {
Date: {
type: "date"
}
}
}
};
$("#stock-chart").kendoStockChart({
dataSource: {
serverFiltering: true,
transport: {
read: {
url: "https://demos.telerik.com/kendo-ui/service/StockData",
dataType: "jsonp"
},
parameterMap: function(data) {
return { filter: JSON.stringify(data.filter) };
}
},
schema: stockDataSchema
},
title: {
text: "The ACME Company"
},
dateField: "Date",
series: [{
type: "candlestick",
openField: "Open",
highField: "High",
lowField: "Low",
closeField: "Close"
}],
navigator: {
dataSource: {
transport: {
read: {
url: "https://demos.telerik.com/kendo-ui/service/StockData",
dataType: "jsonp"
}
},
schema: stockDataSchema
},
series: {
type: "area",
field: "High"
},
select: {
from: "2009/02/05",
to: "2011/10/07"
}
}
});
</script>
```
The following example demonstrates a sample filter submitted by the StockChart for the main data source. The `filter` field is always `Date` regardless of the `dateField` setting.
```json
{
"logic": "and",
"filters": [
{
"field": "Date",
"operator": "gte",
"value": "2009-01-31T22:00:00.000Z"
},
{
"field": "Date",
"operator": "lt",
"value": "2011-10-06T21:00:00.000Z"
}
]
}
```
## See Also
* [Basic Usage of the StockChart (Demo)](https://demos.telerik.com/kendo-ui/financial/index)
* [JavaScript API Reference of the StockChart](/api/javascript/dataviz/ui/stock-chart)
| 35.12037 | 644 | 0.579093 | eng_Latn | 0.946659 |
08c1e21060208afd593fb8ffe1cb8cc6f4ffe928 | 793 | md | Markdown | README.md | DanOnTheMoon21/twitch-bots | 4c901ab4131440fdd89bed70d383a437a0afd327 | [
"MIT"
] | null | null | null | README.md | DanOnTheMoon21/twitch-bots | 4c901ab4131440fdd89bed70d383a437a0afd327 | [
"MIT"
] | 2 | 2020-09-04T22:04:46.000Z | 2021-05-07T13:22:48.000Z | README.md | DanOnTheMoon21/twitch-bots | 4c901ab4131440fdd89bed70d383a437a0afd327 | [
"MIT"
] | null | null | null | # twitch-bots
These are my personal one-off twitch bots. I haven't put much effort into them, and they should not be used for production purposes. On top of them, I have leveraged [Vorpal](https://vorpal.js.org/) to manage them.
These bots should not be used in a twitch channel without the permission of the broadcaster. Some of them can be especially annoying to the viewers and/or broadcasters.
I do not condone the improper usage of these bots, especially, if the implementation of the bot breaks Twitch's Terms of Service. Nor am I responsible for their usage outside of my own personal use.
For all of the above, I have not included a how-to for this repo, but I cannot prevent people from reverse engineering the code here or building bots based off the same fundamental principles. | 88.111111 | 214 | 0.789407 | eng_Latn | 0.999905 |
08c26e0af62a811afc65bf744945515fcc44fff2 | 588 | md | Markdown | clients/java/generated/docs/GithubRepository.md | cliffano/jenkins-api-clients-generator | 522d02b3a130a29471df5ec1d3d22c822b3d0813 | [
"MIT"
] | null | null | null | clients/java/generated/docs/GithubRepository.md | cliffano/jenkins-api-clients-generator | 522d02b3a130a29471df5ec1d3d22c822b3d0813 | [
"MIT"
] | null | null | null | clients/java/generated/docs/GithubRepository.md | cliffano/jenkins-api-clients-generator | 522d02b3a130a29471df5ec1d3d22c822b3d0813 | [
"MIT"
] | null | null | null |
# GithubRepository
## Properties
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**propertyClass** | **String** | | [optional]
**links** | [**GithubRepositorylinks**](GithubRepositorylinks.md) | | [optional]
**defaultBranch** | **String** | | [optional]
**description** | **String** | | [optional]
**name** | **String** | | [optional]
**permissions** | [**GithubRepositorypermissions**](GithubRepositorypermissions.md) | | [optional]
**_private** | **Boolean** | | [optional]
**fullName** | **String** | | [optional]
| 28 | 100 | 0.55102 | yue_Hant | 0.141398 |
08c33da56db4f03c87d85032df5a0edd025588a7 | 547 | md | Markdown | doc/README.md | AriFordsham/plutus | f7d34336cd3d65f62b0da084a16f741dc9156413 | [
"Apache-2.0"
] | 1,299 | 2018-10-02T13:41:39.000Z | 2022-03-28T01:10:02.000Z | doc/README.md | AriFordsham/plutus | f7d34336cd3d65f62b0da084a16f741dc9156413 | [
"Apache-2.0"
] | 2,493 | 2018-09-28T19:28:17.000Z | 2022-03-31T15:31:31.000Z | doc/README.md | AriFordsham/plutus | f7d34336cd3d65f62b0da084a16f741dc9156413 | [
"Apache-2.0"
] | 399 | 2018-10-05T09:36:10.000Z | 2022-03-31T11:18:25.000Z | # Plutus and Marlowe documentation site
This is a sphinx site. You can build it with sphinx directly (assuming you're in a `nix-shell`):
```
sphinx-build -j 4 -n . _build
```
Or you can build it with Nix at the top level, which will also build the Haddock for the project and link it in:
```
nix build -f default.nix docs.site
```
The doc site from master is built automatically and hosted [here](https://plutus.readthedocs.io/en/latest).
Additionally, the site is built for all PRs, and a link to a preview can be found in the PR statuses.
| 32.176471 | 112 | 0.734918 | eng_Latn | 0.99952 |
08c3c8c9c4cbce09a300a38050e844b5a1e418c5 | 478 | md | Markdown | pallets/ico/README.md | FelixMeyr/dico-chain | 84fe53ae89f24ea5d11dfcbe7974bbdd141bf811 | [
"Apache-2.0",
"MIT"
] | null | null | null | pallets/ico/README.md | FelixMeyr/dico-chain | 84fe53ae89f24ea5d11dfcbe7974bbdd141bf811 | [
"Apache-2.0",
"MIT"
] | null | null | null | pallets/ico/README.md | FelixMeyr/dico-chain | 84fe53ae89f24ea5d11dfcbe7974bbdd141bf811 | [
"Apache-2.0",
"MIT"
] | null | null | null | # ICO
***
## Interface
### Dispatchable Functions
* For general users
* join
* user_release_ico_amount
* unlock
* get_reward
* For sudo super-users(Sudo)
* set_system_ico_amount_bound
* For project party
* initiate_ico
* request_release
* initiator_set_ico_amount_bound
* initiator_set_ico_max_count
* user_release_ico_amount
* For DICO foundation
* permit_ico
* reject_ico
* For DAO
* terminate_ico
* permit_release
| 17.071429 | 36 | 0.692469 | eng_Latn | 0.636405 |
08c47bb81193f7fd621a511b58bfd05d02234a0d | 5,119 | md | Markdown | guides/en/discouraged.md | rscRoman/cfdocs | 3f6bf390c8624c028bdad95ad1d5357fc6923316 | [
"MIT-feh"
] | 143 | 2015-03-05T15:35:04.000Z | 2022-01-11T21:15:02.000Z | guides/en/discouraged.md | rscRoman/cfdocs | 3f6bf390c8624c028bdad95ad1d5357fc6923316 | [
"MIT-feh"
] | 895 | 2015-01-24T01:35:47.000Z | 2022-03-04T18:09:32.000Z | guides/en/discouraged.md | rscRoman/cfdocs | 3f6bf390c8624c028bdad95ad1d5357fc6923316 | [
"MIT-feh"
] | 370 | 2015-01-20T10:49:18.000Z | 2022-03-05T16:03:15.000Z | # Discouraged
##The following tags/functions are discouraged to use
### `array`
Lucee recommends to use the inline array notation.
### `cfapplication`
Use Application.cfc instead of Application.cfm files. The Application component provides better organization and additional features. Note that if you are using Application.cfm it should contain a cfapplication tag.
### `cfcol`
The use of tags that generate client side UI code is generally discouraged by the CFML community. See: http://static.raymondcamden.com/cfuitherightway/cftable/index.html
### `cfdiv`
The use of tags generating UI is generally discouraged by the CFML community. See: https://static.raymondcamden.com/cfuitherightway/cfdiv/index.html
### `cfgrid`
The use of tags generating UI is generally discouraged by the CFML community. See: https://static.raymondcamden.com/cfuitherightway/cfgrid/index.html
### `cfgridcolumn`
The use of tags generating UI is generally discouraged by the CFML community. See: https://static.raymondcamden.com/cfuitherightway/cfgrid/index.html
### `cfgridrow`
The use of tags generating UI is generally discouraged by the CFML community. See: https://static.raymondcamden.com/cfuitherightway/cfgrid/index.html
### `cfgridupdate`
The use of tags generating UI is generally discouraged by the CFML community. See: https://static.raymondcamden.com/cfuitherightway/cfgrid/index.html
### `cflayout`
The use of tags generating UI is generally discouraged by the CFML community. See: http://static.raymondcamden.com/cfuitherightway/cfpod/index.html
### `cflayoutarea`
The use of tags generating UI is generally discouraged by the CFML community. See: http://static.raymondcamden.com/cfuitherightway/cfpod/index.html
### `cfmap`
The use of tags generating UI is generally discouraged by the CFML community. See: https://static.raymondcamden.com/cfuitherightway/cfmap/index.html
### `cfmapitem`
The use of tags generating UI is generally discouraged by the CFML community. See: https://static.raymondcamden.com/cfuitherightway/cfmap/index.html
### `cfmenu`
The use of tags generating UI is generally discouraged by the CFML community. See: https://static.raymondcamden.com/cfuitherightway/cfmenu/index.html
### `cfmenuitem`
The use of tags generating UI is generally discouraged by the CFML community. See: https://static.raymondcamden.com/cfuitherightway/cfmenu/index.html
### `cfpod`
The use of tags generating UI is generally discouraged by the CFML community. See: http://static.raymondcamden.com/cfuitherightway/cfpod/index.html
### `cfprogressbar`
The use of tags generating UI is generally discouraged by the CFML community. See: https://static.raymondcamden.com/cfuitherightway/cfprogressbar/index.html
### `cfselect`
The use of tags generating UI is generally discouraged by the CFML community. See: http://static.raymondcamden.com/cfuitherightway/cfpod/index.html
### `cftable`
The use of tags that generate client side UI code is generally discouraged by the CFML community. See: http://static.raymondcamden.com/cfuitherightway/cftable/index.html
### `cftooltip`
The use of tags generating UI is generally discouraged by the CFML community. See: https://static.raymondcamden.com/cfuitherightway/cftooltip/index.html
### `cftree`
The use of tags generating UI is generally discouraged by the CFML community. See: https://static.raymondcamden.com/cfuitherightway/cftree/index.html
### `cftreeitem`
The use of tags generating UI is generally discouraged by the CFML community. See: https://static.raymondcamden.com/cfuitherightway/cftree/index.html
### `cfusion_Decrypt`
The use of this function is discouraged. It is an internal function, call decrypt(string,key,"cfmx_compat","hex") instead.
### `cfusion_Encrypt`
The use of this function is discouraged. It is an internal function, call encrypt(string,key,"cfmx_compat","hex") instead.
### `cfwindow`
The use of tags generating UI is generally discouraged by the CFML community. See: https://static.raymondcamden.com/cfuitherightway/cfwindow/index.html
### `evaluate`
In almost all cases evaluate is unnecessary (use bracket notation instead). Use of evaluate can lead to performance and security issues.
### `iIf`
Use the ternary operator CF9+ instead because it does not evaluate.
Example ternary operator: `( (condition) ? valueIfTrue : valueIfFalse )`
### `lsParseEuroCurrency`
Use LSParseCurrency instead
### `preserveSingleQuotes`
The use of preserveSingleQuotes often (but not always) results in code that will be vulnerable to SQL Injection. Use the cfqueryparam tag instead, and you will not need to worry about single quotes.
### `setVariable`
This function is no longer required in well-formed CFML pages
### `sizeOf`
This function is in an early state. Do not use in production!
### `urlEncodedFormat`
The continued use of this function is discouraged. It is recommended that you use EncodeForURL for all new applications.
### `urlSessionFormat`
Putting session identifiers in the URL may lead to session hijacking.
### `xmlFormat`
Adobe recommends using encodeForXML instead of xmlFormat. | 37.639706 | 215 | 0.785114 | eng_Latn | 0.939847 |
08c4c6dc83acef4914188bcf76e174b9f201115f | 2,730 | md | Markdown | articles/sql-database/sql-database-cloud-migrate-fix-compatibility-issues-ssms.md | OpenLocalizationTestOrg/azure-docs-pr15_hr-HR | 94470f6d3849fb1d48d443d49ffe0217ddba2f80 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/sql-database/sql-database-cloud-migrate-fix-compatibility-issues-ssms.md | OpenLocalizationTestOrg/azure-docs-pr15_hr-HR | 94470f6d3849fb1d48d443d49ffe0217ddba2f80 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/sql-database/sql-database-cloud-migrate-fix-compatibility-issues-ssms.md | OpenLocalizationTestOrg/azure-docs-pr15_hr-HR | 94470f6d3849fb1d48d443d49ffe0217ddba2f80 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | <properties
pageTitle="Rješavanje problema kompatibilnosti baze podataka za SQL Server pomoću SQL Server upravljanje Studio prije migracije s bazom podataka SQL | Microsoft Azure"
description="Microsoft Azure SQL baze podataka, Migracija baze podataka, kompatibilnost, čarobnjak za migraciju SQL Azure"
services="sql-database"
documentationCenter=""
authors="CarlRabeler"
manager="jhubbard"
editor=""/>
<tags
ms.service="sql-database"
ms.devlang="NA"
ms.topic="article"
ms.tgt_pltfrm="NA"
ms.workload="sqldb-migrate"
ms.date="08/24/2016"
ms.author="carlrab"/>
# <a name="fix-sql-server-database-compatibility-issues-using-sql-server-management-studio-before-migration-to-sql-database"></a>Rješavanje problema kompatibilnosti baze podataka za SQL Server pomoću SQL Server Management Studio prije migracije u SQL baze podataka
> [AZURE.SELECTOR]
- Koristite [Čarobnjak za migraciju Azure SQL](sql-database-cloud-migrate-fix-compatibility-issues.md)
- Korištenje [SSDT](sql-database-cloud-migrate-fix-compatibility-issues-ssdt.md)
- Korištenje [SSMS](sql-database-cloud-migrate-fix-compatibility-issues-ssms.md)
Napredni korisnici možete ispraviti SQL Server baze podataka probleme s kompatibilnošću pomoću SQL Server Management Studio prije migracije s bazom podataka SQL Azure.
> [AZURE.IMPORTANT] Preporučuje se da uvijek koristite najnoviju verziju Management Studio ostati sinkronizirani s ažuriranjima za Microsoft Azure i SQL baze podataka. [Ažuriranje SQL Server Management Studio](https://msdn.microsoft.com/library/mt238290.aspx).
## <a name="using-sql-server-management-studio"></a>Pomoću SQL Server Management Studio
Da biste riješili probleme s kompatibilnošću pomoću različite Transact-SQL naredbe, kao što su **Izmjena baze podataka**pomoću SQL Server Management Studio. Ta metoda prvenstveno za napredne korisnike koji su upoznati radi Transact-SQL na bazu podataka uživo. U suprotnom, preporučuje se da koristite SSDT.
## <a name="next-steps"></a>Daljnji koraci
- [Najnovija verzija sustava SSDT](https://msdn.microsoft.com/library/mt204009.aspx)
- [Najnovija verzija sustava SQL Server Management Studio](https://msdn.microsoft.com/library/mt238290.aspx)
- [Migriranje kompatibilne baze podataka SQL Server u SQL baze podataka](sql-database-cloud-migrate.md#migrate-a-compatible-sql-server-database-to-sql-database)
## <a name="additional-resources"></a>Dodatni resursi
- [V12 baze podataka SQL](sql-database-v12-whats-new.md)
- [SQL transakcija djelomično ili nepodržane funkcije](sql-database-transact-sql-information.md)
- [Migracija baze podataka koje nisu iz programa SQL Server pomoću pomoćnika za SQL Server migracije](http://blogs.msdn.com/b/ssma/)
| 55.714286 | 307 | 0.789011 | hrv_Latn | 0.665967 |
08c52fdbcc1ff12d9a75a5efb3baf10641ec3def | 5,188 | md | Markdown | articles/communication-services/concepts/authentication.md | flexray/azure-docs.pl-pl | bfb8e5d5776d43b4623ce1c01dc44c8efc769c78 | [
"CC-BY-4.0",
"MIT"
] | 12 | 2017-08-28T07:45:55.000Z | 2022-03-07T21:35:48.000Z | articles/communication-services/concepts/authentication.md | flexray/azure-docs.pl-pl | bfb8e5d5776d43b4623ce1c01dc44c8efc769c78 | [
"CC-BY-4.0",
"MIT"
] | 441 | 2017-11-08T13:15:56.000Z | 2021-06-02T10:39:53.000Z | articles/communication-services/concepts/authentication.md | flexray/azure-docs.pl-pl | bfb8e5d5776d43b4623ce1c01dc44c8efc769c78 | [
"CC-BY-4.0",
"MIT"
] | 27 | 2017-11-13T13:38:31.000Z | 2022-02-17T11:57:33.000Z | ---
title: Uwierzytelnianie w usłudze Azure Communications Services
titleSuffix: An Azure Communication Services concept document
description: Dowiedz się więcej na temat różnych sposobów uwierzytelniania aplikacji lub usługi w ramach usług komunikacyjnych.
author: mikben
manager: jken
services: azure-communication-services
ms.author: mikben
ms.date: 03/10/2021
ms.topic: conceptual
ms.service: azure-communication-services
ms.openlocfilehash: 9edfb63f5ce43ed325b4c4a1fa67e0e9ca52dc89
ms.sourcegitcommit: 32e0fedb80b5a5ed0d2336cea18c3ec3b5015ca1
ms.translationtype: MT
ms.contentlocale: pl-PL
ms.lasthandoff: 03/30/2021
ms.locfileid: "105110869"
---
# <a name="authenticate-to-azure-communication-services"></a>Uwierzytelnianie w usłudze Azure Communications Services
Każdy klient korzystający z usług Azure Communications Services musi zostać uwierzytelniony. W typowej architekturze zapoznaj się z tematem [Architektura klienta i serwera](./client-and-server-architecture.md), *klucze dostępu* lub *tożsamości zarządzane* są używane do uwierzytelniania.
Inny typ uwierzytelniania korzysta z *tokenów dostępu użytkowników* do uwierzytelniania względem usług, które wymagają udziału użytkownika. Na przykład usługa Chat lub wywołująca korzysta z *tokenów dostępu użytkowników* , aby umożliwić Dodawanie użytkowników w wątku i konwersację ze sobą.
## <a name="authentication-options"></a>Opcje uwierzytelniania
W poniższej tabeli przedstawiono zestawy SDK usług Azure Communication Services i ich opcje uwierzytelniania:
| SDK | Opcja uwierzytelniania |
| ----------------- | ----------------------------------------------------|
| Tożsamość | Klucz dostępu lub tożsamość zarządzana |
| SMS | Klucz dostępu lub tożsamość zarządzana |
| Numery telefonów | Klucz dostępu lub tożsamość zarządzana |
| Rozmów | Token dostępu użytkownika |
| Czat | Token dostępu użytkownika |
Każdą opcję autoryzacji można krótko opisać poniżej:
### <a name="access-key"></a>Klucz dostępu
Uwierzytelnianie klucza dostępu jest odpowiednie dla aplikacji usługi działających w środowisku zaufanej usługi. Klucz dostępu można znaleźć w portalu usługi Azure Communication Services. Aplikacja usługi używa jej jako poświadczeń do inicjowania odpowiednich zestawów SDK. Zobacz przykład sposobu użycia w [zestawie SDK tożsamości](../quickstarts/access-tokens.md).
Ponieważ klucz dostępu jest częścią parametrów połączenia zasobu, uwierzytelnianie za pomocą parametrów połączenia jest równoważne z uwierzytelnianiem przy użyciu klucza dostępu.
Jeśli chcesz ręcznie wywołać interfejsy API usługi ACS przy użyciu klucza dostępu, musisz podpisać żądanie. Podpisywanie żądania zostało szczegółowo opisane w [samouczku](../tutorials/hmac-header-tutorial.md).
### <a name="managed-identity"></a>Tożsamość zarządzana
Zarządzane tożsamości, zapewniają lepsze zabezpieczenia i łatwość użycia nad innymi opcjami autoryzacji. Na przykład przy użyciu usługi Azure AD unika się, aby nie trzeba było przechowywać klucza dostępu do konta w kodzie, jak w przypadku autoryzacji klucza dostępu. Mimo że można nadal korzystać z autoryzacji klucza dostępu przy użyciu aplikacji usług komunikacyjnych, firma Microsoft zaleca przechodzenie do usługi Azure AD, jeśli to możliwe.
Aby skonfigurować tożsamość zarządzaną, [Utwórz zarejestrowaną aplikację przy użyciu interfejsu wiersza polecenia platformy Azure](../quickstarts/managed-identity-from-cli.md). Następnie punkt końcowy i poświadczenia mogą służyć do uwierzytelniania zestawów SDK. Zobacz przykłady użycia [tożsamości zarządzanej](../quickstarts/managed-identity.md) .
### <a name="user-access-tokens"></a>Tokeny dostępu użytkowników
Tokeny dostępu użytkowników są generowane przy użyciu zestawu SDK tożsamości i są skojarzone z użytkownikami utworzonymi w zestawie SDK tożsamości. Zobacz przykład [tworzenia użytkowników i generowania tokenów](../quickstarts/access-tokens.md). Następnie tokeny dostępu użytkowników są używane do uwierzytelniania uczestników dodanych do konwersacji w programie Chat lub wywołaniu zestawu SDK. Aby uzyskać więcej informacji, zobacz [Dodawanie rozmowy do aplikacji](../quickstarts/chat/get-started.md). Uwierzytelnianie tokenu dostępu użytkowników jest różne w porównaniu z kluczem dostępu i uwierzytelnianiem tożsamości zarządzanej w celu uwierzytelnienia użytkownika, a nie zabezpieczonego zasobu platformy Azure.
## <a name="next-steps"></a>Następne kroki
> [!div class="nextstepaction"]
> [Tworzenie zasobów](../quickstarts/create-communication-resource.md)
> usług komunikacyjnych i zarządzanie nimi [Tworzenie aplikacji do zarządzania tożsamościami Azure Active Directory przy użyciu interfejsu wiersza polecenia](../quickstarts/managed-identity-from-cli.md)
> platformy Azure [Utwórz tokeny dostępu użytkowników](../quickstarts/access-tokens.md)
Aby uzyskać więcej informacji, zobacz następujące artykuły:
- [Informacje o architekturze klienta i serwera](../concepts/client-and-server-architecture.md)
| 78.606061 | 714 | 0.777371 | pol_Latn | 0.999963 |
08c6392720b0ea82eb39b1877370b333f526c2e7 | 2,456 | md | Markdown | articles/spatial-anchors/spatial-anchor-support.md | gschrijvers/azure-docs.nl-nl | e46af0b9c1e4bb7cb8088835a8104c5d972bfb78 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/spatial-anchors/spatial-anchor-support.md | gschrijvers/azure-docs.nl-nl | e46af0b9c1e4bb7cb8088835a8104c5d972bfb78 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/spatial-anchors/spatial-anchor-support.md | gschrijvers/azure-docs.nl-nl | e46af0b9c1e4bb7cb8088835a8104c5d972bfb78 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Ondersteuningsopties
description: Informatie over het openen van een aanvraag met het Azure spatiale-ankers ondersteunings team.
author: ramonarguelles
manager: vriveras
services: azure-spatial-anchors
ms.author: rgarcia
ms.date: 02/24/2019
ms.topic: troubleshooting
ms.service: azure-spatial-anchors
ms.openlocfilehash: 371cb9ade54da42af1ed75c3e9857b6d1a7a0f4f
ms.sourcegitcommit: 849bb1729b89d075eed579aa36395bf4d29f3bd9
ms.translationtype: MT
ms.contentlocale: nl-NL
ms.lasthandoff: 04/27/2020
ms.locfileid: "74276971"
---
# <a name="azure-spatial-anchors-support-options"></a>Ondersteunings opties voor Azure spatiale ankers
## <a name="open-a-tech-support-ticket"></a>Een technische ondersteunings ticket openen
Een technische ondersteunings ticket openen in azure portal voor ruimtelijke beankeringen van Azure:
1. Selecteer, terwijl de [Azure Portal](https://azure.microsoft.com/account/) geopend, het Help-pictogram in de bovenste menu balk en selecteer vervolgens de knop **Help + ondersteuning** .
1. Klik op de pagina Help en ondersteuning op openen en selecteer **+ nieuwe ondersteunings aanvraag**.
1. Bij het volt ooien van de velden voor het ondersteunings ticket:
- Type probleem: Technisch
- Service: ruimtelijke ankers
## <a name="community-support"></a>Ondersteuning voor community
Voor ondersteuning van de gebruikers community raadpleegt u de [Azure spatiale ankers op stack overflow](https://stackoverflow.com/questions/tagged/azure-spatial-anchors).
## <a name="provide-content-feedback"></a>Feedback geven over inhoud
Op de onderkant van elk inhouds artikel kunt u een GitHub-probleem openen en feedback geven over de inhoud van het ruimtelijke-anker van Azure.
## <a name="provide-product-feedback"></a>Productfeedback geven
Als u feedback wilt geven, deelt u een idee of suggestie voor de Azure spatiale ankers-service of stem u af op de ideeën die anderen hebben ingediend, gaat u naar het [Feedback forum van Azure Spatial-ankers](https://feedback.azure.com/forums/919252-azure-spatial-anchors).
## <a name="next-steps"></a>Volgende stappen
Zie de pagina [Veelgestelde](spatial-anchor-faq.md) vragen voor veelgestelde vragen over ruimtelijke ankers van Azure.
| 45.481481 | 273 | 0.797231 | nld_Latn | 0.979669 |
08c698630a3f701751abecbf471e3162e4195122 | 1,360 | md | Markdown | _posts/2017-03-21-Notes-on-Merleau-Ponty.md | worlding/worlding.github.io | 99d097b310ee870e9db49adc84d0409f9ffc1044 | [
"MIT"
] | null | null | null | _posts/2017-03-21-Notes-on-Merleau-Ponty.md | worlding/worlding.github.io | 99d097b310ee870e9db49adc84d0409f9ffc1044 | [
"MIT"
] | null | null | null | _posts/2017-03-21-Notes-on-Merleau-Ponty.md | worlding/worlding.github.io | 99d097b310ee870e9db49adc84d0409f9ffc1044 | [
"MIT"
] | null | null | null | ---
layout: post
title: Notes on Merleau-Ponty
author: worlding
tags: Merleau-Ponty
eye_catch:
---
Hegel: there is not pure impression.
* Conditions of possibility: Kant
* Conditions of existence: Heidegger
- what are the enabling conditions
Perception is not conceptual.
Husserl’s phenomenological method: detached reflection on your experience while you are observing something
Merleau-Ponty’s method: describe the world while you are coping with it
What is going on when you perceive? Phenomenology deals with what withdraws so that we can experience objects.
Heidegger’s angle: breakdown.
What experiences makes it possible for us to see stable objects.
Striving to get maximal grip on the things we perceive.
Constancy hypothesis: correlation between sense organs and experience.
Constancy phenomena.
Meditation is not the same as a phenomenology of being involved. Meditation is like a breakdown situation. Too subjective. Not illuminating about ordinary coping.
Mediating stories don’t work. We open our eyes and see stable objects with constant properties.
An experience of objectivity (predicate, properties) or subjectivity is on the basis of your general experience of object in the world.
Generative mechanisms. Phenomenology.
Merleau-Ponty: Your experience constantly needs to be stabilised. We are composing the text of the world.
| 33.170732 | 162 | 0.807353 | eng_Latn | 0.998095 |
08c777c9688b2fa0bdc2d76887b6e20e61ad7dbe | 469 | md | Markdown | examples/browser/README.md | neupauer/meilisearch-js | c7fc4ce162a9693e3e4e0d1ef74b7f5ffc03a48c | [
"MIT"
] | null | null | null | examples/browser/README.md | neupauer/meilisearch-js | c7fc4ce162a9693e3e4e0d1ef74b7f5ffc03a48c | [
"MIT"
] | null | null | null | examples/browser/README.md | neupauer/meilisearch-js | c7fc4ce162a9693e3e4e0d1ef74b7f5ffc03a48c | [
"MIT"
] | null | null | null | # Browser demo
## Requirements
Build the base project `/meilisearch-js` as this example uses the locally build bundles from `meilisearch-js`.
```
$ cd meilisearch-js
$ yarn build
```
## Credentials
This example uses the following MeiliSearch address: `http://127.0.0.1:7700`. Feel free to change the credentials to meet your MeiliSearch address.
The credentials are written in `index.html`.
## Try out
To try out this html file, just open it using any browser.
| 22.333333 | 147 | 0.744136 | eng_Latn | 0.99011 |
08c7fdadac689247d0e53849f339bd536af1a771 | 10,245 | md | Markdown | articles/virtual-machines/linux/cloud-init-troubleshooting.md | matmahnke/azure-docs.pt-br | 6c96d25caf8663547775f333164198e3ed03972f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/virtual-machines/linux/cloud-init-troubleshooting.md | matmahnke/azure-docs.pt-br | 6c96d25caf8663547775f333164198e3ed03972f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/virtual-machines/linux/cloud-init-troubleshooting.md | matmahnke/azure-docs.pt-br | 6c96d25caf8663547775f333164198e3ed03972f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Solucionar problemas usando Cloud-init
description: Solucionar problemas de provisionamento de uma VM do Azure usando Cloud-init.
author: danielsollondon
ms.service: virtual-machines-linux
ms.subservice: imaging
ms.topic: troubleshooting
ms.date: 07/06/2020
ms.author: danis
ms.reviewer: cynthn
ms.openlocfilehash: 6412036e3f16e2efb3bbf6669f6a31e9dc6e3584
ms.sourcegitcommit: 829d951d5c90442a38012daaf77e86046018e5b9
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 10/09/2020
ms.locfileid: "89434632"
---
# <a name="troubleshooting-vm-provisioning-with-cloud-init"></a>Solucionando problemas de provisionamento de VM com Cloud-init
Se você estiver criando imagens personalizadas generalizadas, usando Cloud-init para fazer o provisionamento, mas tiver encontrado que a VM não foi criada corretamente, você precisará solucionar problemas de suas imagens personalizadas.
Alguns exemplos de problemas com o provisionamento:
- A VM fica presa em ' criando ' por 40 minutos e a criação da VM é marcada como com falha
- `CustomData` Não é processado
- Falha na montagem do disco efêmero
- Os usuários não são criados ou há problemas de acesso do usuário
- A rede não está configurada corretamente
- Trocar falhas de arquivo ou partição
Este artigo orienta você sobre como solucionar problemas de Cloud-init. Para obter detalhes mais detalhados, consulte [aprofundamento da Cloud-init](./cloud-init-deep-dive.md).
## <a name="step-1-test-the-deployment-without-customdata"></a>Etapa 1: testar a implantação sem `customData`
O Cloud-init pode aceitar `customData` , que é passado para ele, quando a VM é criada. Primeiro, você deve garantir que isso não esteja causando problemas com implantações. Tente provisionar a VM sem passar por nenhuma configuração. Se você achar que a VM não está provisionada, continue com as etapas abaixo. se você achar que a configuração que está passando não está sendo aplicada, vá para a [etapa 4]().
## <a name="step-2-review-image-requirements"></a>Etapa 2: examinar os requisitos de imagem
A principal causa da falha de provisionamento da VM é que a imagem do sistema operacional não atende aos pré-requisitos para execução no Azure. Verifique se suas imagens estão adequadamente preparadas antes de tentar provisioná-las no Azure.
Os artigos a seguir ilustram as etapas para preparar várias distribuições do Linux com suporte no Azure:
- [Distribuições com base em CentOS](create-upload-centos.md)
- [Debian Linux](debian-create-upload-vhd.md)
- [Flatcar Container Linux](flatcar-create-upload-vhd.md)
- [Oracle Linux](oracle-create-upload-vhd.md)
- [Red Hat Enterprise Linux](redhat-create-upload-vhd.md)
- [SLES e openSUSE](suse-create-upload-vhd.md)
- [Ubuntu](create-upload-ubuntu.md)
- [Outros: Distribuições não endossadas](create-upload-generic.md)
Para as [imagens do Azure cloud-init com suporte](./using-cloud-init.md), as distribuições do Linux já têm todos os pacotes e configurações necessários para provisionar corretamente a imagem no Azure. Se você achar que sua VM não está conseguindo criar a partir de sua própria imagem organizada, experimente uma imagem do Azure Marketplace com suporte que já esteja configurada para Cloud-init, com o opcional `customData` . Se o `customData` funcionar corretamente com uma imagem do Azure Marketplace, provavelmente haverá um problema com a imagem organizada.
## <a name="step-3-collect--review-vm-logs"></a>Etapa 3: coletar & examinar os logs da VM
Quando a VM não puder ser provisionada, o Azure mostrará o status ' criando ', por 20 minutos, e reinicializará a VM e aguardará mais 20 minutos antes de finalmente marcar a implantação da VM como com falha, antes de finalmente marcá-la com um `OSProvisioningTimedOut` erro.
Enquanto a VM estiver em execução, você precisará dos logs da VM para entender por que houve falha no provisionamento. Para entender por que o provisionamento de VM falhou, não pare a VM. Mantenha a VM em execução. Você precisará manter a VM com falha em um estado de execução para coletar logs. Para coletar os logs, use um dos seguintes métodos:
- [Console Serial](../troubleshooting/serial-console-grub-single-user-mode.md)
- [Habilite o diagnóstico de inicialização](./tutorial-monitor.md#enable-boot-diagnostics) antes de criar a VM e, em seguida, [exibi](./tutorial-monitor.md#view-boot-diagnostics) -las durante a inicialização.
- [Execute AZ VM Repair](../troubleshooting/repair-linux-vm-using-azure-virtual-machine-repair-commands.md) para anexar e montar o disco do sistema operacional, o que permitirá que você colete esses logs:
```bash
/var/log/cloud-init*
/var/log/waagent*
/var/log/syslog*
/var/log/rsyslog*
/var/log/messages*
/var/log/kern*
/var/log/dmesg*
/var/log/boot*
```
Para iniciar a solução de problemas inicial, comece com os logs de Cloud-init e entenda onde a falha ocorreu, use os outros logs para aprofundar-se e fornecer informações adicionais.
* /var/log/Cloud-init.log
* /var/log/cloud-init-output.log
* Logs de série/inicialização
Em todos os logs, comece a procurar "falha", "aviso", "avisar", "Err", "erro", "erro". É recomendável definir a configuração para ignorar pesquisas que diferenciam maiúsculas de minúsculas.
> [!TIP]
> Se você estiver solucionando problemas de uma imagem personalizada, considere adicionar um usuário durante a imagem. Se o provisionamento falhar ao definir o usuário administrador, você ainda poderá fazer logon no sistema operacional.
## <a name="analyzing-the-logs"></a>Analisando os logs
Aqui estão mais detalhes sobre o que procurar em cada log de inicialização de nuvem.
### <a name="varlogcloud-initlog"></a>/var/log/Cloud-init.log
Por padrão, todos os eventos Cloud-init com uma prioridade de debug ou superior são gravados no `/var/log/cloud-init.log` . Isso fornece logs detalhados de cada evento ocorrido durante a inicialização de Cloud-init.
Por exemplo:
```console
2019-10-10 04:51:25,321 - util.py[DEBUG]: Failed mount of '/dev/sr0' as 'auto': Unexpected error while running command.
Command: ['mount', '-o', 'ro,sync', '-t', 'auto', u'/dev/sr0', '/run/cloud-init/tmp/tmpLIrklc']
Exit code: 32
Reason: -
Stdout:
Stderr: mount: unknown filesystem type 'udf'
2020-01-31 00:21:53,352 - DataSourceAzure.py[WARNING]: /dev/sr0 was not mountable
```
Depois de encontrar um erro ou aviso, leia para trás no log de inicialização de nuvem para entender o que a Cloud-init estava tentando antes de atingir o erro ou o aviso. Em muitos casos, o Cloud-init terá comandos do sistema operacional executados ou executará operações de provisionamento anteriores ao erro, o que pode fornecer informações sobre por que os erros apareciam nos logs. O exemplo a seguir mostra que a Cloud-init tentou montar um dispositivo imediatamente antes de clicar em um erro.
```output
2019-10-10 04:51:24,010 - util.py[DEBUG]: Running command ['mount', '-o', 'ro,sync', '-t', 'auto', u'/dev/sr0', '/run/cloud-init/tmp/tmpXXXXX'] with allowed return codes [0] (shell=False, capture=True)
```
Se você tiver acesso ao [console serial](../troubleshooting/serial-console-grub-single-user-mode.md), poderá tentar executar novamente o comando que a Cloud-init estava tentando realizar.
O registro em log para `/var/log/cloud-init.log` também pode ser reconfigurado em/etc/cloud/cloud.cfg.d/05_logging. cfg. Para obter mais detalhes sobre o log de inicialização de nuvem, consulte a [documentação de inicialização de nuvem](https://cloudinit.readthedocs.io/en/latest/topics/logging.html).
### <a name="varlogcloud-init-outputlog"></a>/var/log/cloud-init-output.log
Você pode obter informações do `stdout` e `stderr` durante os [estágios de Cloud-init](cloud-init-deep-dive.md). Isso normalmente envolve informações de tabela de roteamento, informações de rede, informações de verificação de chave de host SSH `stdout` e `stderr` para cada estágio de Cloud-init, juntamente com o carimbo de data/hora de cada estágio. Se desejar, `stderr` e o `stdout` registro em log pode ser reconfigurado de `/etc/cloud/cloud.cfg.d/05_logging.cfg` .
### <a name="serialboot-logs"></a>Logs de série/inicialização
Cloud-init tem várias dependências, elas são documentadas em pré-requisitos obrigatórios para imagens no Azure, como rede, armazenamento, capacidade de montar um ISO e montar e formatar o disco temporário. Qualquer um deles pode gerar erros e causar falha na inicialização de nuvem. Por exemplo, se a VM não puder obter uma concessão DHCP, a inicialização de nuvem falhará.
Se ainda não for possível isolar por que a Cloud-init falhou ao provisionar, você precisará entender quais estágios de Cloud-init e quando os módulos são executados. Consulte [aprofundando-se na inicialização de nuvem](cloud-init-deep-dive.md) para obter mais detalhes.
## <a name="step-4-investigate-why-the-configuration-isnt-being-applied"></a>Etapa 4: investigar por que a configuração não está sendo aplicada
Nem toda falha em Cloud-init resulta em uma falha de provisionamento fatal. Por exemplo, se você estiver usando o `runcmd` módulo em uma configuração de inicialização de nuvem, um código de saída diferente de zero do comando que está sendo executado fará com que o provisionamento da VM falhe. Isso ocorre porque ele é executado após a funcionalidade de provisionamento principal que ocorre nos três primeiros estágios de Cloud-init. Para solucionar problemas por que a configuração não foi aplicada, examine os logs nos módulos etapa 3 e Cloud-init manualmente. Por exemplo:
- `runcmd` -os scripts são executados sem erros? Execute a configuração manualmente do terminal para garantir que elas sejam executadas conforme o esperado.
- Instalando pacotes – a VM tem acesso aos repositórios de pacotes?
- Você também deve verificar a `customData` configuração de dados fornecida para a VM, que está localizada em `/var/lib/cloud/instances/<unique-instance-identifier>/user-data.txt` .
## <a name="next-steps"></a>Próximas etapas
Se você ainda não puder isolar por que a Cloud-init não executou a configuração, precisará olhar mais detalhadamente o que acontece em cada estágio Cloud-init e quando os módulos são executados. Consulte aprofundando [-se na configuração do Cloud-init](./cloud-init-deep-dive.md) para obter mais informações.
| 74.781022 | 575 | 0.783699 | por_Latn | 0.99885 |
08c88b01ed6394b7d321943dc2d0731ba954c137 | 7,190 | md | Markdown | docs/vs-2015/ide/get-started-developing-with-visual-studio.md | walterlv/visualstudio-docs | a8418c7d6f46d0dfc1e11a0adf99b5245d5ce3cb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/ide/get-started-developing-with-visual-studio.md | walterlv/visualstudio-docs | a8418c7d6f46d0dfc1e11a0adf99b5245d5ce3cb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/ide/get-started-developing-with-visual-studio.md | walterlv/visualstudio-docs | a8418c7d6f46d0dfc1e11a0adf99b5245d5ce3cb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Get Started Developing | Microsoft Docs"
ms.custom: ""
ms.date: 11/15/2016
ms.prod: "visual-studio-dev14"
ms.reviewer: ""
ms.suite: ""
ms.technology:
- "vs-ide-general"
ms.tgt_pltfrm: ""
ms.topic: "article"
helpviewer_keywords:
- "Visual Studio, getting started"
ms.assetid: 041ef726-f117-4a91-9c18-fef043bf2529
caps.latest.revision: 67
author: gewarren
ms.author: gewarren
manager: "ghogen"
---
# Get Started Developing with Visual Studio
[!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
Welcome to Visual Studio! After you have [downloaded](http://www.visualstudio.com/community) the product, these pages will help you get started coding.
- **[Make web apps](https://www.visualstudio.com/features/modern-web-tooling-vs):** Tools to create and deploy modern web applications.
[Do a tutorial](https://docs.asp.net/en/latest/tutorials/your-first-aspnet-application.html) | [Browse the docs](https://docs.asp.net/) | [Watch a video](http://www.asp.net/vnext)
- **[Make cross-platform mobile apps in HTML/Javascript (Apache Cordova)](http://taco.visualstudio.com/docs/get-started-first-mobile-app/)** : Apache Cordova is an open-source cross-platform environment that is based on HTML/CSS/Javascript. Your Javascript code executes in a wrapper that targets a specific platform and enables access to all the hardware capabilities of the device. Develop apps for the Apple Store, the Android store, and the Windows Store.
[Load a sample](https://github.com/Microsoft/cordova-samples/tree/master/todo-angularjs) | [Do a tutorial](http://taco.visualstudio.com/docs/get-started-first-mobile-app/) | [Browse the docs](http://taco.visualstudio.com/docs/get-started-vs-tools-apache-cordova/) | [Watch a video](https://channel9.msdn.com/Blogs/Seth-Juarez/Getting-Started-with-Apache-Cordova-in-Visual-Studio)
- **[Make cross-platform mobile apps in C# or Visual Basic (Xamarin)](../cross-platform/visual-studio-and-xamarin.md)** : Get started using Visual Studio and Tools for Xamarin to create mobile apps that run on Android, iOS, and the Universal Windows Platform from a shared code base.
Load a sample:[Tasky Portable](http://developer.xamarin.com/samples/mobile/TaskyPortable/) (native UI) or [Xamarin Forms Todo sample](https://github.com/xamarin/xamarin-forms-samples/tree/master/Todo) (Xamarin.Forms shared UI) | [Do a tutorial](https://msdn.microsoft.com/library/dn879698\(v=vs.140\).aspx) | [Browse the docs](https://msdn.microsoft.com/library/mt299001.aspx) | [Watch a video](https://channel9.msdn.com/Series/Cross-Platform-Development-with-Xamarin--Visual-Studio/01)
- **[Make native cross-platform apps and libraries in C++](https://www.visualstudio.com/explore/cplusplus-mdd-vs.aspx)** Go here to get started creating C++ apps and libraries that run on Android, iOS, and the Universal Windows Platform.
[Load a sample](https://code.msdn.microsoft.com/MoreTeaPots-Android-a9bd8549) | [Do a tutorial](https://msdn.microsoft.com/library/dn707595.aspx) | [Browse the docs](https://msdn.microsoft.com/library/dn707591.aspx) | [Watch a video](https://channel9.msdn.com/Series/ConnectOn-Demand/239)
- **[Make games with DirectX](https://msdn.microsoft.com/library/windows/desktop/ee663274\(v=vs.85\).aspx)** : Get started creating Universal Windows Platform games using DirectX.
[Load a sample](https://msdn.microsoft.com/library/windows/desktop/bb153300\(v=vs.85\).aspx) | [Do a tutorial](https://msdn.microsoft.com/library/windows/desktop/bb153264\(v=vs.85\).aspx) | [Browse the docs](https://msdn.microsoft.com/library/windows/desktop/ee663274\(v=vs.85\).aspx) | [Watch a video](https://channel9.msdn.com/Series/Introduction-to-C-and-DirectX-Game-Development/01)
- **[Make games with Unity](../cross-platform/visual-studio-tools-for-unity.md)** : Get started creating cross-platform games using Unity framework.
[Load a sample](http://unity3d.com/learn/resources/downloads) | [Do a tutorial](http://unity3d.com/learn/tutorials/projects/roll-ball-tutorial) | [Browse the docs](https://msdn.microsoft.com/library/dn940019\(v=vs.140\).aspx) | [Watch a video](https://www.youtube.com/playlist?list=PLReL099Y5nRfseAg0k1SJOlpqdcsDs8Em)
- **[Make Universal Windows Platform apps](https://dev.windows.com/windows-apps)** : Get started creating apps that run on the Universal Windows Platform (XBox, PCs, tablets, Windows Phone, Surface Hub, and Internet of Things).
[Load a sample](https://github.com/Microsoft/Windows-universal-samples) | [Do a tutorial](https://msdn.microsoft.com/library/windows/apps/dn765018.aspx) | [Browse the docs](https://dev.windows.com) | [Watch a video](https://channel9.msdn.com/Blogs/One-Dev-Minute/Getting-started-with-Windows-10)
- **[Make desktop applications](https://dev.windows.com/desktop)** : Go here to get started creating traditional desktop applications that run on Windows PCs.
[Load a sample](https://github.com/microsoft/windows-classic-samples) | [Do a tutorial](https://msdn.microsoft.com/library/dd492171.aspx) | [Browse the docs](https://dev.windows.com/desktop)
- **[Make Office applications](https://msdn.microsoft.com/library/fp161347.aspx)** : Get started creating Office applications that extend and customize Word, Excel, Outlook and PowerPoint with Office 365 services.
[Load a sample](https://code.msdn.microsoft.com/office365/) | [Do a tutorial](http://dev.office.com/getting-started/office365apis) | [Browse the docs](https://msdn.microsoft.com/office/aa905340.aspx) | [Watch a video](http://dev.office.com/videos)
- **[Tour Visual Studio Team Services and Team Foundation Server](https://www.visualstudio.com/products/visual-studio-team-services-vs)** Learn more about Visual Studio Team Services and Team Foundation Server.
## In this section
|||
|-|-|
|[Getting Started with Visual C# and Visual Basic](../ide/getting-started-with-visual-csharp-and-visual-basic.md)|[Writing JavaScript Code](http://msdn.microsoft.com/library/cte3c772\(v=vs.94\).aspx)|
|[Visual C++ for Cross-Platform Mobile Development](../cross-platform/visual-cpp-for-cross-platform-mobile-development.md)|[Introduction to Functional Programming with F#](http://msdn.microsoft.com/library/vstudio/dd233147.aspx)|
|[Getting Started with C++](../ide/getting-started-with-cpp-in-visual-studio.md)|[Getting Started with Debugging in Visual Studio 2015](../ide/getting-started-with-debugging-in-visual-studio-2015.md)|
| 102.714286 | 570 | 0.687204 | eng_Latn | 0.26015 |
08c8e809a4af220460f67c91fa144f0f61f8c244 | 1,427 | md | Markdown | 2020/09/04/2020-09-04 19:40.md | zhzhzhy/WeiBoHot_history | 32ce4800e63f26384abb17d43e308452c537c902 | [
"MIT"
] | 3 | 2020-07-14T14:54:15.000Z | 2020-08-21T06:48:24.000Z | 2020/09/04/2020-09-04 19:40.md | zhzhzhy/WeiBoHot_history | 32ce4800e63f26384abb17d43e308452c537c902 | [
"MIT"
] | null | null | null | 2020/09/04/2020-09-04 19:40.md | zhzhzhy/WeiBoHot_history | 32ce4800e63f26384abb17d43e308452c537c902 | [
"MIT"
] | null | null | null | 2020年09月04日19时数据
Status: 200
1.罗冠军
微博热度:3249593
2.父亲出门拿快递惊喜遇退役儿子
微博热度:1789227
3.修护大师黑钥匙面霜
微博热度:1765912
4.李东海身材
微博热度:1764684
5.社会性死亡
微博热度:1654504
6.姐姐的舞台力量
微博热度:1620315
7.乘风破浪的姐姐成团之夜节目单
微博热度:1527875
8.韩国老牌泡菜厂出现集体感染
微博热度:778366
9.2021考研7个专业学位不再统一划线
微博热度:700844
10.钟南山入选世卫组织专家组
微博热度:665761
11.罗冠军称梁颖方愿意公开道歉
微博热度:648323
12.原来唐朝就有猪腰子鞋了
微博热度:633659
13.罗志祥 关你屁事
微博热度:526804
14.为泄私愤篡改上百名同学中考志愿
微博热度:513352
15.梁颖
微博热度:468221
16.教育部回应非全硕士受歧视
微博热度:421920
17.苹果市值单日蒸发1.23万亿元
微博热度:336461
18.姜思达露背长裙
微博热度:333936
19.重庆人都不胖的原因
微博热度:329905
20.袁家军
微博热度:319712
21.李纯80小时练舞vlog
微博热度:302350
22.杀人犯未按规服刑死者母亲发声
微博热度:299609
23.物理老师用纸杯留声机成功留声
微博热度:277719
24.崔雪莉纪录片预告
微博热度:276001
25.十二天会掉多少头发
微博热度:266995
26.考研时间
微博热度:266604
27.陕西严查高中空挂学籍
微博热度:248393
28.糖豆人服务器
微博热度:237119
29.湖北省政府秘书长别必雄接受调查
微博热度:205603
30.陈赫ins
微博热度:205017
31.在劫难逃
微博热度:182776
32.信条
微博热度:180162
33.台风致吉林玉米大面积倒伏
微博热度:179472
34.警方悬赏50万通缉在逃夫妻
微博热度:179116
35.郑栅洁任浙江省代省长
微博热度:179016
36.夏天的云朵有多好看
微博热度:178343
37.黄晓明端水有始有终
微博热度:177815
38.泰国广告是如何劝你吃蔬菜的
微博热度:176529
39.家长齐聚校门口给孩子剪发入学
微博热度:163211
40.王一博换包了
微博热度:155541
41.让社恐感到安心的瞬间
微博热度:151896
42.哈里梅根签约奈飞当制作人
微博热度:141945
43.AirPods Studio
微博热度:140297
44.韩国医界长达半月的罢诊结束
微博热度:133388
45.陈木胜追思会
微博热度:123517
46.当狗子成为社畜时
微博热度:120975
47.乡村教师超半数拥有本科以上学历
微博热度:120887
48.吴谨言近身防身术教程
微博热度:117146
49.检方回应杀人犯纸面服刑15年
微博热度:114399
50.16岁少年去世捐器官救4人
微博热度:108639
| 6.995098 | 20 | 0.784163 | yue_Hant | 0.331408 |
08c92b20f5d8489d84564ed47d085232445a5362 | 1,100 | md | Markdown | README.md | samurai71/fip-organDonation | 83640e0e64bc34d833352c4fb0f06e0c0aa86c12 | [
"MIT"
] | null | null | null | README.md | samurai71/fip-organDonation | 83640e0e64bc34d833352c4fb0f06e0c0aa86c12 | [
"MIT"
] | null | null | null | README.md | samurai71/fip-organDonation | 83640e0e64bc34d833352c4fb0f06e0c0aa86c12 | [
"MIT"
] | null | null | null | # fip-organDonation
Final Integrated Project at Fanshawe College for Organ donation awarenss in Ontario, Canada
## Getting Started
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
You will need a copy of MAMP or WAMP installing and runing on your computer. Then install this repo in a folder in the root directory of that server and navigate to that directory in your favourite web browser.
### Prerequisites
MAMP for a MAC and WAMP for a windows machine
## Deployment
Add additional notes about how to deploy this on a live system
## Built With
* [Foundation](https://foundation.zurb.com/) - The web framework used
## Team Members
* ** Lexi Sterio – Project Manager/Designer
* ** Nolan Martin – Motion Design
* ** Shane Fry – Back End Developer/Front End Developer
* ** Mark Landeryou – Front end Developer/ Back end Developer
## License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details
| 31.428571 | 210 | 0.767273 | eng_Latn | 0.995725 |
08c971a9cbb4bc17a44cee8723be23d3c6e16ef9 | 11,273 | md | Markdown | docs/guide/integrations/payment-gateway.md | wasmonia/vue-storefront | 4517712bcff0f3e1506da516c9901fd60d7ec877 | [
"MIT"
] | 1 | 2018-03-06T11:06:21.000Z | 2018-03-06T11:06:21.000Z | docs/guide/integrations/payment-gateway.md | wasmonia/vue-storefront | 4517712bcff0f3e1506da516c9901fd60d7ec877 | [
"MIT"
] | 59 | 2021-04-28T01:01:58.000Z | 2021-09-17T01:02:44.000Z | docs/guide/integrations/payment-gateway.md | szb512/vue-storefront | 8185781d43a0700250407c56bcc13c7253ea69dd | [
"MIT"
] | 1 | 2020-02-12T10:16:35.000Z | 2020-02-12T10:16:35.000Z | # Payment Gateway Integration
Vue Storefront is a platform-agnostic app. This means it can be connected to virtually any eCommerce backend. At the same time, most of the existing eCommerce platforms integrate the Payment Gateways (PG) using some kind of frontend hooks:
- Some gateways are integrated by iframe component
- Others are injected by JavaScript snippet etc.
In this situation, it's a rare case when you can modify your payment gateway with PWA—without creating the integration code by yourself.
## Community resources
Our community members created some really cool docs and reference implementation of payment modules You could and probably should base yours on:
- Blog post: [How to create VS 1.6 payment module](https://www.develodesign.co.uk/news/development-of-the-paypal-module-for-vue-storefront/)
- Paypal integration: [Paypal integration by Develodesign](https://github.com/develodesign/vsf-payment-paypal)
- Braintree integration: [Braintree integration by Daniel Coull](https://github.com/danrcoull/vsf-payment-braintree)
## Frontend integration
First step is to create a [Vue Storefront Module](../modules/introduction.md) to integrate the payment provider in the frontend. Any of the payment handling logic UI is handled solely via the Module. For the most basic version of how a Payment Module is, the "src/modules/payment-cash-on-delivery".
- The Payment Module, where applicable, should catch the `checkout-payment-method-changed`vent. If the payment method code is the desired one, then you have the option to dynamically inject any components into the order review section on the checkout—for example, credit card input fields, payment method information, etc.
- You are required to catch the `checkout-before-placeOrder` event and do any processing required for the payment method before placing the order.
- You are required to emit the `checkout-do-placeOrder` event with an optional payload to complete the placeorder process.
- For your payment method to display, add it to the Payment Methods collection in storage `app.\$store.state.payment.methods.push(paymentMethodConfig)`.
- Unregister any events when they are no longer required.
- For clarity in growing extensions, payment extensions should be named clearly `payment-{VENDOR}-{PAYMENT_METHOD}`
### Cash on delivery example
Here is an example of a "Cash on delivery" payment method main logic. It's placed in the `src/modules/payment-cash-on-deliver/hooks/afterRegistration.ts` which is usually a good entry point for registering custom event hooks:
```js
import InfoComponent from '../components/Info.vue'
import rootStore from '@vue-storefront/core/store'
export function afterRegistration({ Vue, config, store, isServer }) {
// Place the order. Payload is empty as we don't have any specific info to add for this payment method '{}'
const placeOrder = function () {
Vue.prototype.$bus.$emit('checkout-do-placeOrder', {})
}
if (!Vue.prototype.$isServer) {
// Update the methods
let paymentMethodConfig = {
'title': 'Cash on delivery',
'code': 'cashondelivery',
'cost': 0,
'costInclTax': 0,
'default': true,
'offline': true
}
rootStore.dispatch('payment/addMethod', paymentMethodConfig)
// Mount the info component when required.
Vue.prototype.$bus.$on('checkout-payment-method-changed', (paymentMethodCode) => {
if (paymentMethodCode === 'cashondelivery') {
// Register the handler for what happens when they click the place order button.
Vue.prototype.$bus.$on('checkout-before-placeOrder', placeOrder)
// Dynamically inject a component into the order review section (optional)
const Component = Vue.extend(InfoComponent)
const componentInstance = (new Component())
componentInstance.$mount('#checkout-order-review-additional')
} else {
// unregister the extensions placeorder handler
Vue.prototype.$bus.$off('checkout-before-placeOrder', placeOrder)
}
})
}
}
```
### More examples
You can find much more sophisticated solutions for [Paypal](https://github.com/develodesign/vsf-payment-paypal) on our partner - **Develodesign** github and [Braintree](https://github.com/danrcoull/vsf-payment-braintree)
More info:
- [How to create VS 1.6 Payment module](https://www.develodesign.co.uk/news/development-of-the-paypal-module-for-vue-storefront/)
## Backend Integration
After successfully integrating the payments on the frontend, you're sending the users and transactions to the payment integrator. Then, we need to get back the payment token/identifier and update the order status as soon as the payment integrator will let us know that the transaction finished.
To store the transaction info you'll get from the payment service, you may emit an event:
```js
placeOrderWithPayload (payload) {
this.$bus.$emit('checkout-do-placeOrder', payload)
```
where the payload equals to JSON object with additional order information. This object will be transferred to the server along with the order object in the `order.payment_method_additional` property.
### The order workflow - server side
To get it right, first we must understand how Vue Storefront processes orders. Vue Storefront sends orders to the server asynchronously because of the offline orders support (orders can be sent immediately after they’replaced, minutes after or even hours).
The order is being sent to the `vue-storefront-api/api/order/create` endpoint. This API endpoint pushes the order to the queue from where it's being transferred to the eCommerce backend by a cron-run process called `order_2_magento2.js` (o2m). You will find the source code of `o2m` in the `vue-storefront-api/worker` folder.
As you can see, we don't have the backend's order number immediately after the order has been placed. To pair the client-side order ID and server-side metadata, `order_2_magento.js` process stores special metadata entries in `Redis` cache:
```js
api.cart.order(null, cartId, {
"paymentMethod":
{
"method":orderData.addressInformation.payment_method_code,
"additional_data":orderData.addressInformation.payment_method_additional
}
}, isThisAuthOrder).then(result => {
logger.info(THREAD_ID, result)()
if(job) job.progress(currentStep++, TOTAL_STEPS);
logger.info(THREAD_ID + '[OK] Order placed with ORDER ID', result);()
logger.debug(THREAD_ID + result)()
redisClient.set("order$$id$$" + orderData.order_id, JSON.stringify(
{
platform_order_id: result,
transmited: true,
transmited_at: new Date(),
platform: 'magento2',
order: orderData
}));
redisClient.set("order$$totals$$" + orderData.order_id, JSON.stringify(result[1]));
if(job) job.progress(currentStep++, TOTAL_STEPS);
return done(null, { magentoOrderId: result, transferedAt: new Date() });
```
As you can see, you can get the order data using the **client-side** order ID by accessing the `order$$id$${clientsideorderid}` in the local Redis instance.
You can check `vue-storefront-api/src/api/sync.js` with the `check` method:
```js
export default ({ config, db }) => {
let syncApi = Router();
/**
* GET get stock item
*/
syncApi.get('/order/:order_id', (req, res) => {
const Redis = require('redis');
let redisClient = Redis.createClient(config.redis); // redis client
redisClient.on('error', function(err) {
// workaround for https://github.com/NodeRedis/node_redis/issues/713
redisClient = Redis.createClient(config.redis); // redis client
});
redisClient.get('order$$id$$' + req.param('order_id'), function(
err,
reply,
) {
const orderMetaData = JSON.parse(reply);
if (orderMetaData) {
orderMetaData.order = null; // for security reasons we're just clearing out the real order data as it's set by `order_2_magento2.js`
}
apiStatus(res, err ? err : orderMetaData, err ? 500 : 200);
});
});
return syncApi;
};
```
As this method returns the order data by non-secured URL with just the client-side order ID, there is an `order` property being removed to return just the platform ID of their order.
### Status change for the order
The example shown above was a prep step for updating the Magento (or other platform) order status based on the response from the payments integrator.
First, you need to add the special endpoint under the public URL that will be getting the notifications / statuses from the payments provider. Here is an example [how to add custom API endpoint to the `vue-storefront-api`](Extending vue-storefront-api.md).
To add the API extension to `vue-storefront-api`:
1. Create the folder within `src/api/extensions`. For example 'custom-payment-method`
2. Then add the `index.js` file and put the API methods code inside. We're using Express.js. Here is a boilerplate/example for the extension code:
```js
import { apiStatus } from '../../../lib/util';
import { Router } from 'express';
module.exports = ({ config, db }) => {
let mcApi = Router();
/**
* POST create an user
*/
mcApi.post('/status', (req, res) => {
const notificationData = req.body;
const order_id = ''; // we should extract the client's order id from the notification status
/// ... business logic related to the status verification
// getting the data from Redis - the original order
const Redis = require('redis');
const Magento2Client = require('magento2-rest-client').Magento2Client;
let redisClient = Redis.createClient(config.redis); // redis client
redisClient.on('error', function(err) {
// workaround for https://github.com/NodeRedis/node_redis/issues/713
redisClient = Redis.createClient(config.redis); // redis client
});
redisClient.get('order$$id$$' + order_id, function(err, reply) {
const orderMetaData = JSON.parse(reply);
if (orderMetaData) {
// now we can use the api client to update the order status in Magento
const client = Magento2Client(config.magento2.api);
client.addMethods('invoice', function(restClient) {
var module = {};
module.create = function() {
return restClient.post('/invoice/create'); // the real Magento2 endpoint should be here - this is just an example
};
return module;
});
client.invoice
.create()
.then(result => {
apiStatus(res, result, 200); // just dump it to the browser, result = JSON object
})
.catch(err => {
apiStatus(res, err, 500);
});
}
});
});
return mcApi;
};
```
3. Add the extension to `config/local.json`:
```json
"registeredExtensions": ["custom-payment-method"],
```
4. Restart the `vue-storefront-api`
5. Your new API method is available on `localhost:8080/api/ext/<extension_name>/<extension_method>` for example: `localhost:8080/api/ext/custom-payment-method/status`
In this extension above, you may want to get the order data by the client-side order ID (passed to the payment service and probably returned with the notification). Then **you may use the Magento 2 API to update the payment status**, likely by executing the `invoice` method.
| 46.390947 | 325 | 0.720571 | eng_Latn | 0.946406 |
08cb15ae2983b81fde68aab48dbf64f4ff743798 | 5,357 | md | Markdown | objetivos/kaizensamuel.md | kaizensamuel/IV-18-19 | 3ed4b279395284c85e0dd086b651b8b00abe308a | [
"Artistic-2.0"
] | null | null | null | objetivos/kaizensamuel.md | kaizensamuel/IV-18-19 | 3ed4b279395284c85e0dd086b651b8b00abe308a | [
"Artistic-2.0"
] | null | null | null | objetivos/kaizensamuel.md | kaizensamuel/IV-18-19 | 3ed4b279395284c85e0dd086b651b8b00abe308a | [
"Artistic-2.0"
] | null | null | null | # Samuel Alarcón Cuadros para la asignatura IV-18-19
# Semana del 12 de septiembre
# Objetivos
1. [X] Entender la metodología docente, de evaluación y de interacción de la asignatura.
2. [X] Darse de alta y comprender el funcionamiento básico de GitHub y el
grupo de Telegram de la asignatura y conocer el resto de los recursos de la asignatura.
3. [X] Entender el concepto de software libre y su aplicación práctica en esta asignatura.
4. [X] Entender la importancia de metodologías ágiles como SCRUM en el desarrollo de proyectos informáticos, incluyendo proyectos de
infraestructura.
# Semana del 17 de septiembre
# Objetivos
1. [X] Comenzar a entender los conceptos fundamentales relacionados con la virtualización.
2. [X] Comprender las técnicas de cálculo del coste de amortización de un equipo informático y aplicarlo al cálculo del coste de uso de un recurso.
3. [X] Entender el soporte en hardware de las técnicas de virtualización y cómo se extiende ese soporte al núcleo de los sistemas operativos. Saber si el ordenador habitual lo usa.
4. [X] Comprender los niveles de virtualización y sus denominaciones genéricas.
5. [X] Comprender el concepto de *X as a service* y comprender los
criterios necesarios para su elección.
6. [X] Entender qué implica diseñar un proyecto que se irá elaborando durante la asignatura.
# Hito 0
1. [X] Configuración correcta de Git
2. [X] Enviar fichero de objetivos al repositorio de JJ
3. [X] [Fork del repositorio JJ IV-18-19](https://github.com/kaizensamuel/IV-18-19)
4. [X] Creación de un par de claves y subida de clave pública a GitHub.
## Enlace Repositorio del proyecto iv-18-19
5. [X] Repositorio del [Pozyx-localizacion-interiores](https://github.com/kaizensamuel/Pozyx-localizacion-interiores)
## Enlace Repositorio de ejercicios iv-18-19
6. [X] Repositorio de [Ejercicios-IV](https://github.com/kaizensamuel/Ejercicios-IV)
# Semana del 24 de septiembre
# Objetivos
1. [x] Comprender cómo las pruebas de software encajan dentro del concepto de infraestructura virtual.
2. [x] Usar los gestores de versiones en diferentes lenguajes de programación y entender su utilidad.
3. [x] Entender los ficheros de requisitos o dependencias y su utilidad en las infraestructuras virtuales.
## Enlace Repositorio del proyecto iv-18-19
5. [X] Repositorio del [Tienda online componentes](https://github.com/kaizensamuel/proyecto-IV-18-19)
# Semana del 01 de octubre
# Objetivos
1. [x] Comenzar con la configuración de los sistemas de integración continua
2. [x] Comprender cómo las pruebas de software encajan dentro del concepto de infraestructura virtual.
3. [x] Comprender el nivel plataforma de la infraestructura virtual y su uso en prueba y producción.
# Semana del 08 de octubre
# Objetivos
1. [x] Terminar la configuración de los sistemas de integración continua
2. [x] Estudiar el nivel plataforma de la infraestructura virtual y su uso en prueba y producción y darse de alta en alguno.
# Semana del 22 de octubre
# Objetivos
1. [x] Comprender las diferencias y parecidos entre diferentes sistemas PaaS comerciales, exclusivos o parte de un proveedor cloud como Azure.
2. [x] Elegir uno o varios sistemas para llevar a cabo los ejercicios y proyecto de la asignatura.
3. [x] Internalizar el concepto de PaaS, su aplicación y sus limitaciones.
3. [x] Entender el concepto de despliegue y cómo la infraestructura
virtual y su especificación son esenciales para el mismo.
4. [x] Comprender qué herramientas de desarrollo y lenguajes de programación
se pueden usar en diferentes PaaS con facilidad.
3. [x] Resolver los problemas que surjan en los primeros despliegues.
## Otros objetivos
1. [x] Darse de alta y probar diferentes servicios PaaS como Heroku, Zeit.co y Azure Web services.
# Semana del 29 de octubre
Para terminar el hito 3 y emprender el camino al siguiente hito,
usando PaaS
## Objetivos
1. [x] Probar diferentes PaaS con sus sistemas de despliegue correspondientes.
2. [x] Probar diferentes formas de desplegar aplicaciones desde línea de órdenes y repositorios.
# Semana del 5 de Noviembre
1. [x] Comprender la importancia de los contenedores en el el desarrollo
informático actual
2. [x] Entender la base del aislamiento de recursos en el sistema operativo.
3. [x] Entender las diferentes formas de aislar recursos en Linux u otros sistemas operativos.
4. [x] Entender las arquitecturas software basadas en contenedores
# Semana 12 de Noviembre
1. [x] Entender la base del aislamiento de recursos en el sistema operativo.
2. [x] Entender las diferentes formas de aislar recursos en Linux u otros sistemas operativos.
# Semana 19 de Noviembre
1. [x] Entender los conceptos fundamentales de virtualización
2. [x] Comprender el concepto de hipervisor y los diferentes tipos que hay.
# Semana 26 de Noviembre
1. [x] Usar el API de hipervisores locales y remotos desde Vagrant para crear máquinas virtuales.
# Semana 3 de Diciembre
1. [x] Trabajar con proveedores en la nube y apreciar los parecidos y diferencias con los locales.
2. [x] Entender los conceptos de los servicios en la nube.
3. [x] Entender el concepto de provisionamiento.
# Semana 10 de Diciembre
1. [x] Entender el concepto de aprovisionamiento y cómo encaja con la orquestación de máquinas virtuales y el resto de conceptos vistos en la asignatura.
| 39.681481 | 180 | 0.778981 | spa_Latn | 0.997264 |
08cb282f978ceb518baf77cb8a6e897889458122 | 458 | md | Markdown | iterations/103/ticket.morph-1.6.0.md | ckauhaus/nixos-vulnerability-roundup | 07589f47223f811b06f5fd62000c1adeadd37e6d | [
"BSD-3-Clause"
] | 5 | 2018-11-08T08:38:04.000Z | 2021-11-14T17:12:14.000Z | iterations/103/ticket.morph-1.6.0.md | ckauhaus/nixos-vulnerability-roundup | 07589f47223f811b06f5fd62000c1adeadd37e6d | [
"BSD-3-Clause"
] | 8 | 2019-09-30T19:58:28.000Z | 2019-11-23T17:56:05.000Z | iterations/103/ticket.morph-1.6.0.md | ckauhaus/nixos-vulnerability-roundup | 07589f47223f811b06f5fd62000c1adeadd37e6d | [
"BSD-3-Clause"
] | 2 | 2019-02-17T11:28:32.000Z | 2019-10-27T10:53:24.000Z | # Vulnerability roundup 103: morph-1.6.0: 1 advisory [7.5]
[search](https://search.nix.gsc.io/?q=morph&i=fosho&repos=NixOS-nixpkgs), [files](https://github.com/NixOS/nixpkgs/search?utf8=%E2%9C%93&q=morph+in%3Apath&type=Code)
* [ ] [CVE-2019-15080](https://nvd.nist.gov/vuln/detail/CVE-2019-15080) CVSSv3=7.5 (nixos-21.05, nixos-unstable)
Scanned versions: nixos-21.05: 0b8b127125e; nixos-unstable: 1905f5f2e55.
Cc @adamtulinius
Cc @johanot
Cc @kalbasit
| 35.230769 | 165 | 0.733624 | yue_Hant | 0.214538 |
08cb5140c70b6181c942698b8ba459d6be5a98e6 | 1,214 | md | Markdown | README.md | san00/REST-countries-API | 625bb38eaa4125d92b4c992ca109d847ce2ef1d7 | [
"MIT"
] | null | null | null | README.md | san00/REST-countries-API | 625bb38eaa4125d92b4c992ca109d847ce2ef1d7 | [
"MIT"
] | 3 | 2019-05-31T15:43:07.000Z | 2022-02-12T10:09:39.000Z | README.md | san00/REST-countries-API | 625bb38eaa4125d92b4c992ca109d847ce2ef1d7 | [
"MIT"
] | null | null | null | # Countries of the World app
App designed & built from scratch to search and view detailed information about countries of the world.
## Live preview
[See it here](https://countries-of-the-world.netlify.com/)
Build an app similar to this challenge on [frontendmentor](https://beta.frontendmentor.io/challenges/rest-countries-api-with-color-theme-switcher-5cacc469fec04111f7b848ca).
## Installation
* Download or clone the repository
* Install dependencies - `npm install`
* Run gulp & watch for changes - `gulp` or `npx gulp`
## Brief:
**Use the REST countries API to pull and display country data, enabling users to:**
1. See all countries from the API on the homepage
2. Search for a country using an input field
3. Filter countries by region
4. Click on a country to see more detailed information on a separate page
5. Click through to the border countries on the detail page
6. Toggle the color scheme between light and dark mode (optional)
## Technologies
* Gulp
* Sass
* HTML5
* Javascript
* Flexbox
* Grid
* REST Countries API
### License:
MIT 2019
| 31.947368 | 172 | 0.76112 | eng_Latn | 0.935445 |
08cbff38baa5260e662abcd4644f200d0a5c67d1 | 67 | md | Markdown | README.md | tirinox/thorcasino-back | e24dad4a417d4717c75be1e0bfefbb9ee0f0cd28 | [
"MIT"
] | null | null | null | README.md | tirinox/thorcasino-back | e24dad4a417d4717c75be1e0bfefbb9ee0f0cd28 | [
"MIT"
] | null | null | null | README.md | tirinox/thorcasino-back | e24dad4a417d4717c75be1e0bfefbb9ee0f0cd28 | [
"MIT"
] | null | null | null | # thorcasino-back
THORCasion: experiment for gambling on THORChain
| 22.333333 | 48 | 0.835821 | eng_Latn | 0.622865 |
08cc39cf05ea7f3bb7fc6fbe28670f385ea2adaf | 2,577 | md | Markdown | content/tech2/tech2_using/connecting_to_techline/usb-to-serial/usb2serial_working.md | trawaisaweeb/tech2wiki-website | 8855987461fc92ae0e9f99933d231464fc37f785 | [
"CC0-1.0"
] | null | null | null | content/tech2/tech2_using/connecting_to_techline/usb-to-serial/usb2serial_working.md | trawaisaweeb/tech2wiki-website | 8855987461fc92ae0e9f99933d231464fc37f785 | [
"CC0-1.0"
] | null | null | null | content/tech2/tech2_using/connecting_to_techline/usb-to-serial/usb2serial_working.md | trawaisaweeb/tech2wiki-website | 8855987461fc92ae0e9f99933d231464fc37f785 | [
"CC0-1.0"
] | null | null | null | ---
sort: 100
---
# Working
| Manufacturer | Model | Chipset | Driver | Status |
| --- | --- | --- | --- | --- |
| [Tripp Lite](http://www.tripplite.com/) | [USA-19HS](https://www.tripplite.com/keyspan-high-speed-usb-to-serial-adapter~USA19HS/) | [Texas Instruments/TI](https://www.ti.com/) | [USA-19HS](https://www.tripplite.com/support/USA19HS) | GM/Bosch recommended device |
| [FTDI](https://ftdichip.com/) | [US232R-100](http://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_US232R-10_R-100-500.pdf) | [FT232RQ](https://www.ftdichip.com/Support/Documents/DataSheets/ICs/DS_FT232R.pdf) | [FT232RQ](https://ftdichip.com/drivers/d2xx-drivers/) | Working 100% |
| [Belkin](https://www.belkin.com/) | [F5U103CP](http://cache-www.belkin.com/support/dl/pxxxxxea_f5u103ea_man.pdf) | FTDI | [F5U103CP](https://www.belkin.com/us/support-article?articleNum=4486) | Working 100% |
| [TRENDnet](https://www.trendnet.com/) | [TU-S9](https://www.trendnet.com/products/product-detail?prod=150_TU-S9) | [PL-2303HXD](http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=156&pcid=41) | [PL-2303HXD](https://www.trendnet.com/support/support-detail.asp?prod=150_TU-S9) | Working 100% |
| [EK-Interface](http://www.ek-interface.com/) | USB RS232 Adapter | [PL-2303](http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41) | [PL-2303](http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41) | Working 100% |
| [VSCOM](http://www.vscom.de/index.htm) | [USB-COM CBL/25CM](http://www.vscom.de/datasheet/619_datasheet.pdf) | FT235RL | [FT235RL](http://www.ftdichip.com/Drivers/VCP.htm) | Working 100% |
| [Deltaco](https://www.deltaco.se/) | [UC-232B9](https://www.deltaco.se/varum%C3%A4rken/vscom/serieportar-via-usb/1-port/UC-232B9) | FT235RL | [FT235RL](http://www.ftdichip.com/Drivers/VCP.htm) | Working 100% |
| Various | USB RS232 Adapter | CH340/HL340 | [CH340/HL340](http://www.microcontrols.org/wp-content/uploads/2015/05/DRIVER1_CH340.zip) | Working 100% |
| [Aten](https://www.aten.com/) | [UC232A](https://assets.aten.com/product/manual/uc232a-uc232a1_um_w_2019-12-11.pdf) | [PL-2303](http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41) | [PL-2303](http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41) | Working 100% [Tested on VMware] |
| [24hshop](http://www.24hshop.no/) | [USB to RS232 Adapter](https://www.24hshop.no/datatilbehor/usb-datatilbehor/adaptere-til-usb/usb-til-rs232-adapter?gclid=Cj0KCQjw59n8BRD2ARIsAAmgPmKN41GR-vkY_Rt_gw1AwBOccqxt4DDqYSI8x1r7pc-FSvZIS5pYdpoaAvR1EALw_wcB) | - | - | Working 100% [Tested on VMware] |
| 143.166667 | 307 | 0.719053 | yue_Hant | 0.767784 |
08cc5cfec4a84ff9b35617266f7be5584ac967a9 | 720 | md | Markdown | content/en/docs/limd/iMobileDevice.MobileBackup2/MobileBackup2Api/mobilebackup2_client_free.md | qmfrederik/docsy-perf | dcd7c1309adfca26120740a9983de179368f5600 | [
"Apache-2.0"
] | 1 | 2020-12-29T23:42:04.000Z | 2020-12-29T23:42:04.000Z | content/en/docs/limd/iMobileDevice.MobileBackup2/MobileBackup2Api/mobilebackup2_client_free.md | qmfrederik/docsy-perf | dcd7c1309adfca26120740a9983de179368f5600 | [
"Apache-2.0"
] | null | null | null | content/en/docs/limd/iMobileDevice.MobileBackup2/MobileBackup2Api/mobilebackup2_client_free.md | qmfrederik/docsy-perf | dcd7c1309adfca26120740a9983de179368f5600 | [
"Apache-2.0"
] | null | null | null | ---
title: MobileBackup2Api.mobilebackup2_client_free method
---
Disconnects a mobilebackup2 client from the device and frees up the mobilebackup2 client data.
```csharp
public virtual MobileBackup2Error mobilebackup2_client_free(IntPtr client)
```
| parameter | description |
| --- | --- |
| client | The mobilebackup2 client to disconnect and free. |
## Return Value
MOBILEBACKUP2_E_SUCCESS on success, or MOBILEBACKUP2_E_INVALID_ARG if client is NULL.
## See Also
* enum [MobileBackup2Error](../MobileBackup2Error.md)
* class [MobileBackup2Api](../MobileBackup2Api.md)
* namespace [iMobileDevice.MobileBackup2](../../iMobileDevice-net.md)
<!-- DO NOT EDIT: generated by xmldocmd for iMobileDevice-net.dll -->
| 27.692308 | 94 | 0.763889 | eng_Latn | 0.498665 |
08cc5def4b9e09796efcbd909e1097d7ae1b5e04 | 12,546 | md | Markdown | docs/_documentation/platform/android/android-view-presenter.md | millerd8/MvvmCross | 9952752bb98759dce7e05d11dde4dc5ebdf58f69 | [
"MS-PL"
] | 3 | 2021-04-21T07:10:00.000Z | 2021-04-21T10:51:01.000Z | docs/_documentation/platform/android/android-view-presenter.md | millerd8/MvvmCross | 9952752bb98759dce7e05d11dde4dc5ebdf58f69 | [
"MS-PL"
] | 3 | 2021-05-21T00:01:53.000Z | 2022-01-22T14:48:35.000Z | docs/_documentation/platform/android/android-view-presenter.md | millerd8/MvvmCross | 9952752bb98759dce7e05d11dde4dc5ebdf58f69 | [
"MS-PL"
] | null | null | null | ---
layout: documentation
title: Android View Presenter
category: Platforms
---
## View Presenter Overview
The default presenter for Android named `MvxAndroidViewPresenter` or `MvxAppCompatViewPresenter` when using the Android AppCompat support library offers out of the box support for the following navigation patterns / strategies:
- Activities
- Fragments
- Nested Fragments
- Dialog Fragments
- TabLayout / ViewPager
Navigation patterns that should be easy to implement with this are:
- NavigationDrawer
- BottomNavigationBar (single backstack)
- BottomSheetDialog
- Master/Detail Flows
- Nested navigation
Also if your app needs another kind of presentation mode, you can easily extend it!
## Presentation Attributes
The presenter uses a set of `PresentationAttributes` to define how a view will be displayed. The existing attributes are:
### MvxActivityPresentationAttribute
Use this attribute if you want to display an Activity in your application. An Activity will be the root of your application and can also act as a host for fragments. Alongside the attribute, your view can customize the presentation by using these attribute properties:
| Name | Type | Description |
| ---- | ---- | ----------- |
| Extras | `Bundle` | Use this `Bundle` to add any extra parameters to the Activity Intent. |
### MvxFragmentPresentationAttribute
A Fragment is hosted inside an Activity (or a fragment). By using this ViewPresenter, you can decide whether to make all of your screens Activities, or to use an Activity host and many Fragments inside of it. MvvmCross can handle both scenarios smoothly.
The ViewPresenter also supports nested fragments in one level: This means you can show fragments inside of a Fragment without extending any code!
Use this attribute over a Fragment view class and customize its presentation by using these properties:
| Name | Type | Description |
| ---- | ---- | ----------- |
| ActivityHostViewModelType | `Type` | The __ViewModel type__ of the Activity that will be the host of your fragment. In case that Activity is not the current one in foreground, the ViewPresenter will show it before showing the fragment. Can be left empty only in case of fragments nesting. |
| FragmentHostViewType | `Type` | The __View type__ of the Fragment that will be the host of your fragment. Use this property only in case you want a fragment to be shown as nested. |
| FragmentContentId | `int` | Resource id where your fragment will be presented. |
| AddToBackStack | `bool` | Default value is `false`. If you set it to `true` the FragmentTransaction will be added to the backstack. |
| EnterAnimation | `int` | Resource id for the animation that will be run when the fragment is shown. |
| ExitAnimation | `int` | Resource id for the animation that will be run when the fragment is closed. |
| PopEnterAnimation | `int` | Resource id for the animation that will be run when the fragment comes back to foreground. |
| PopExitAnimation | `int` | Resource id for the animation that will be run when the fragment is retrieved from foreground. |
| TransitionStyle | `int` | In case you want to use a Transition Style, use this property by setting its resource id. |
| IsCacheableFragment | `bool` | Default value is false. You should leave it that way unless you really want/need to reuse a fragment view (for example, in case you are displaying a WebView, you might want to cache the already loaded URL). If it is set to `true`, the ViewPresenter will try to find a Fragment instance already present in the FragmentManager object before instantiating a new one and will reuse that object. |
When providing a value for EnterAnimation you need to provide one for ExitAnimation as well, otherwise the animation won't work (same applies in the other way around).
Same as above, if you want to set a Pop animation, you will need to set four animation resources: EnterAnimation, ExitAnimation, PopEnterAnimation and PopExitAnimation. Otherwise the animation won't work.
### MvxDialogFragmentPresentationAttribute
This attribute extends `MvxFragmentPresentationAttribute`, which means you can use all the properties it provides to customize the presentation. Use this attribute over a FragmentDialog view class to display a dialog and take advantage of even more customization with this property:
| Name | Type | Description |
| ---- | ---- | ----------- |
| Cancelable | `bool` | Default value is `true`. This property indicates if the dialog can be canceled. |
### MvxViewPagerFragmentPresentationAttribute (AppCompat only)
This attribute extends `MvxFragmentPresentationAttribute`, which means you can use all the properties it provides to customize the presentation. use this attribute over a Fragment view class to display a fragment inside of a ViewPager and take advantage of even more customization with these properties:
| Name | Type | Description |
| ---- | ---- | ----------- |
| Title | `string` | Title for the ViewPager. It will also be used as Title for the TabLayout when using MvxTabLayoutPresentationAttribute. |
| ViewPagerResourceId | `int` | The resource id for the ViewPager that will be used as host. |
Note: If you intend to display your fragment in more than one host activity, please remember to set the property ActivityHostViewModelType on each attribute!
### MvxTabLayoutPresentationAttribute (AppCompat only)
This attribute extends `MvxViewPagerFragmentPresentationAttribute`, which means you can use all the properties it provides to customize the presentation. use this attribute over a Fragment view class to display a fragment inside of a ViewPager with TabLayout and take advantage of even more customization with this property:
| Name | Type | Description |
| ---- | ---- | ----------- |
| TabLayoutResourceId | `int` | The resource id for the TabLayout that will be used. |
Note: If you intend to display your fragment in more than one host activity, please remember to set the property ActivityHostViewModelType on each attribute!
## Views without attributes: Default values
- If a view class has no attribute over it, the presenter will check the type and try to create the correct attribute for it:
- Activity -> `MvxActivityPresentationAttribute`
- Fragment -> `MvxFragmentPresentationAttribute`
- DialogFragment -> `MvxDialogFragmentPresentationAttribute`
## Override a presentation attribute at runtime
To override a presentation attribute at runtime you can implement the `IMvxOverridePresentationAttribute` in your view and determine the presentation attribute in the `PresentationAttribute` method like this:
```c#
public MvxBasePresentationAttribute PresentationAttribute(MvxViewModelRequest request)
{
return new MvxFragmentPresentationAttribute()
{
};
}
```
As you can see in the code snippet, you will be able to make your choice using a `MvxViewModelRequest`. This object will contain the `PresentationValues` dictionary alongside other properties.
If you return `null` from the `PresentationAttribute` method, the ViewPresenter will fallback to the attribute used to decorate the view. If the view is not decorated with any presentation attribute, then it will use the default attribute instead.
__Hint:__ Be aware that `this.ViewModel` property will be null during `PresentationAttribute`. If you want to have the ViewModel instance available, you need to use the `MvxNavigationService` and cast the `request` parameter to `MvxViewModelInstanceRequest`.
## Shared Element transitions
To add a Shared Element transition navigating to an Activity or Fragment implement the `IMvxAndroidSharedElements` in your hosting Activity. You can then use `FetchSharedElementsToAnimate` to assign the view elements you want to transition.
```C#
public IDictionary<string, View> FetchSharedElementsToAnimate(MvxBasePresentationAttribute attribute, MvxViewModelRequest request)
{
IDictionary<string, View> sharedElements = new Dictionary<string, View>();
if (request.ViewModelType == typeof(SharedElementSecondChildViewModel))
{
var selectedLogo = FindViewById<ImageView>(Resource.Id.img_logo);
sharedElements.Add("identifier", selectedLogo);
}
return sharedElements;
}
```
`FetchSharedElementsToAnimate` provides access to the `MvxViewModelRequest` used for the navigation as well as the attributed used by the view navigating to. The dictionary that is returned must contain an `identifier` as well as the view element to transition.
__Hint:__ Be aware that you must have already specified the transition name on the view elements you add to the dictionary.
The view you are navigating to will receive a `Bundle` that contains additional metadata. Being the identifier as well as the transition name. MvvmCross provides an extension method to assist with extracting this metadata, `GetSharedElementTransitionNames` , which can be used to get identifier and transition name pairs.
```C#
static IDictionary<string, string> GetSharedElementTransitionNames(this Bundle bundle)
```
Furthermore, if the identifier you passed through is the Android resource id name or Android resource tag. You can make use of the following extension method to find the corresponding view element and apply the transition name if required.
```C#
static void SetSharedElementsByTag(this Bundle bundle, View view)
static void SetSharedElementsById(this Bundle bundle, View view)
```
You can also check out the Playground Shared Elements sample.
## Extensibility
### Attributes
The presenter is completely extensible! You can override any attribute and customize attribute members.
You can also define new attributes to satisfy your needs. The steps to do so are:
1. Add a new attribute that extends `MvxBasePresentationAttribute`
2. Subclass `MvxAndroidViewPresenter` or `MvxAppCompatViewPresenter` and make it the presenter of your application in Setup.cs (by overriding the method `CreatePresenter`).
3. Override the method `RegisterAttributeTypes` and add a registry to the dictionary like this:
```c#
_attributeTypesToShowMethodDictionary.Add(
typeof(MyCustomModePresentationAttribute),
new MvxPresentationAttributeAction
{
ShowAction = (view, attribute, request) => ShowMyCustomModeView(view, (MyCustomPresentationAttribute)attribute, request),
CloseAction = (viewModel, attribute) => CloseMyCustomModeView(viewModel, (MyCustomPresentationAttribute)attribute)
});
```
4. Implement a method that takes care of the presentation mode (in the example above, `ShowMyCustomModeView`) and a method that takes care of a ViewModel closing (in the example above, `CloseMyCustomModeView`).
5. Use your attribute over a view class. Ready!
### Fragment Lifecycle
To get more control over your Fragment lifecycle (or activity) and transitions, you can override the following methods. You can also modify your fragment transitions :
__MvxAndroidViewPresenter__
```c#
void OnBeforeFragmentChanging(FragmentTransaction ft, Fragment fragment, MvxFragmentPresentationAttribute attribute, MvxViewModelRequest request)
void OnFragmentChanged(FragmentTransaction ft, Fragment fragment, MvxFragmentPresentationAttribute attribute, MvxViewModelRequest request)
void OnFragmentChanging(FragmentTransaction ft, Fragment fragment, MvxFragmentPresentationAttribute attribute, MvxViewModelRequest request)
void OnFragmentPopped(FragmentTransaction ft, Fragment fragment, MvxFragmentPresentationAttribute attribute)
```
__MvxAppCompatViewPresenter__
```c#
void OnBeforeFragmentChanging(FragmentTransaction ft, Fragment fragment, MvxFragmentPresentationAttribute attribute, MvxViewModelRequest request)
void OnFragmentChanged(FragmentTransaction ft, Fragment fragment, MvxFragmentPresentationAttribute attribute, MvxViewModelRequest request)
void OnFragmentChanging(FragmentTransaction ft, Fragment fragment, MvxFragmentPresentationAttribute attribute, MvxViewModelRequest request)
void OnFragmentPopped(FragmentTransaction ft, Fragment fragment, MvxFragmentPresentationAttribute attribute)
```
### Activity Transitions
In case you want to override the transition options bundle pasted between 2 activities you can override the following method :
```c#
Bundle CreateActivityTransitionOptions(Intent intent, MvxActivityPresentationAttribute attribute, MvxViewModelRequest request)
```
## Sample please!
You can browse the code of the [Playground](https://github.com/MvvmCross/MvvmCross/blob/master/Projects/Playground/) (Android project) to see this presenter in action.
| 55.76 | 425 | 0.792364 | eng_Latn | 0.978384 |
08cd170b402287d799cd74f4e6a261ae2f07032e | 41,896 | md | Markdown | docs/mfc/reference/cdaoquerydef-class.md | POMATOpl/cpp-docs.pl-pl | ae1925d41d94142f6a43c4e721d45cbbbfeda4c7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/mfc/reference/cdaoquerydef-class.md | POMATOpl/cpp-docs.pl-pl | ae1925d41d94142f6a43c4e721d45cbbbfeda4c7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/mfc/reference/cdaoquerydef-class.md | POMATOpl/cpp-docs.pl-pl | ae1925d41d94142f6a43c4e721d45cbbbfeda4c7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
description: 'Dowiedz się więcej na temat: Klasa CDaoQueryDef'
title: Klasa CDaoQueryDef
ms.date: 11/04/2016
f1_keywords:
- CDaoQueryDef
- AFXDAO/CDaoQueryDef
- AFXDAO/CDaoQueryDef::CDaoQueryDef
- AFXDAO/CDaoQueryDef::Append
- AFXDAO/CDaoQueryDef::CanUpdate
- AFXDAO/CDaoQueryDef::Close
- AFXDAO/CDaoQueryDef::Create
- AFXDAO/CDaoQueryDef::Execute
- AFXDAO/CDaoQueryDef::GetConnect
- AFXDAO/CDaoQueryDef::GetDateCreated
- AFXDAO/CDaoQueryDef::GetDateLastUpdated
- AFXDAO/CDaoQueryDef::GetFieldCount
- AFXDAO/CDaoQueryDef::GetFieldInfo
- AFXDAO/CDaoQueryDef::GetName
- AFXDAO/CDaoQueryDef::GetODBCTimeout
- AFXDAO/CDaoQueryDef::GetParameterCount
- AFXDAO/CDaoQueryDef::GetParameterInfo
- AFXDAO/CDaoQueryDef::GetParamValue
- AFXDAO/CDaoQueryDef::GetRecordsAffected
- AFXDAO/CDaoQueryDef::GetReturnsRecords
- AFXDAO/CDaoQueryDef::GetSQL
- AFXDAO/CDaoQueryDef::GetType
- AFXDAO/CDaoQueryDef::IsOpen
- AFXDAO/CDaoQueryDef::Open
- AFXDAO/CDaoQueryDef::SetConnect
- AFXDAO/CDaoQueryDef::SetName
- AFXDAO/CDaoQueryDef::SetODBCTimeout
- AFXDAO/CDaoQueryDef::SetParamValue
- AFXDAO/CDaoQueryDef::SetReturnsRecords
- AFXDAO/CDaoQueryDef::SetSQL
- AFXDAO/CDaoQueryDef::m_pDAOQueryDef
- AFXDAO/CDaoQueryDef::m_pDatabase
helpviewer_keywords:
- CDaoQueryDef [MFC], CDaoQueryDef
- CDaoQueryDef [MFC], Append
- CDaoQueryDef [MFC], CanUpdate
- CDaoQueryDef [MFC], Close
- CDaoQueryDef [MFC], Create
- CDaoQueryDef [MFC], Execute
- CDaoQueryDef [MFC], GetConnect
- CDaoQueryDef [MFC], GetDateCreated
- CDaoQueryDef [MFC], GetDateLastUpdated
- CDaoQueryDef [MFC], GetFieldCount
- CDaoQueryDef [MFC], GetFieldInfo
- CDaoQueryDef [MFC], GetName
- CDaoQueryDef [MFC], GetODBCTimeout
- CDaoQueryDef [MFC], GetParameterCount
- CDaoQueryDef [MFC], GetParameterInfo
- CDaoQueryDef [MFC], GetParamValue
- CDaoQueryDef [MFC], GetRecordsAffected
- CDaoQueryDef [MFC], GetReturnsRecords
- CDaoQueryDef [MFC], GetSQL
- CDaoQueryDef [MFC], GetType
- CDaoQueryDef [MFC], IsOpen
- CDaoQueryDef [MFC], Open
- CDaoQueryDef [MFC], SetConnect
- CDaoQueryDef [MFC], SetName
- CDaoQueryDef [MFC], SetODBCTimeout
- CDaoQueryDef [MFC], SetParamValue
- CDaoQueryDef [MFC], SetReturnsRecords
- CDaoQueryDef [MFC], SetSQL
- CDaoQueryDef [MFC], m_pDAOQueryDef
- CDaoQueryDef [MFC], m_pDatabase
ms.assetid: 9676a4a3-c712-44d4-8c5d-d1cc78288d3a
ms.openlocfilehash: cb07457746f6fc569823917bc47d43a3e0b41078
ms.sourcegitcommit: d6af41e42699628c3e2e6063ec7b03931a49a098
ms.translationtype: MT
ms.contentlocale: pl-PL
ms.lasthandoff: 12/11/2020
ms.locfileid: "97250724"
---
# <a name="cdaoquerydef-class"></a>Klasa CDaoQueryDef
Reprezentuje definicję zapytania lub "querydef", zazwyczaj jeden zapisany w bazie danych.
## <a name="syntax"></a>Składnia
```
class CDaoQueryDef : public CObject
```
## <a name="members"></a>Elementy członkowskie
### <a name="public-constructors"></a>Konstruktory publiczne
|Nazwa|Opis|
|----------|-----------------|
|[CDaoQueryDef::CDaoQueryDef](#cdaoquerydef)|Konstruuje `CDaoQueryDef` obiekt. Następne wywołanie `Open` lub `Create` , w zależności od potrzeb.|
### <a name="public-methods"></a>Metody publiczne
|Nazwa|Opis|
|----------|-----------------|
|[CDaoQueryDef:: Append](#append)|Dołącza obiekt querydef do kolekcji QueryDefs bazy danych jako zapisane zapytanie.|
|[CDaoQueryDef:: Update](#canupdate)|Zwraca wartość różną od zera, jeśli zapytanie może aktualizować bazę danych.|
|[CDaoQueryDef:: Close](#close)|Zamyka obiekt querydef. Zniszcz obiekt C++ po zakończeniu pracy z nim.|
|[CDaoQueryDef:: Create](#create)|Tworzy źródłowy obiekt DAO querydef. Użyj elementu querydef jako zapytania tymczasowego lub zadzwoń `Append` do zapisania go w bazie danych.|
|[CDaoQueryDef:: Execute](#execute)|Wykonuje zapytanie zdefiniowane przez obiekt querydef.|
|[CDaoQueryDef:: GetConnect](#getconnect)|Zwraca parametry połączenia skojarzone z elementem querydef. Parametry połączenia identyfikują źródło danych. (Dotyczy tylko zapytań przekazujących kod SQL; w przeciwnym razie jest to pusty ciąg).|
|[CDaoQueryDef::GetDateCreated](#getdatecreated)|Zwraca datę utworzenia zapisanego zapytania.|
|[CDaoQueryDef::GetDateLastUpdated](#getdatelastupdated)|Zwraca datę ostatniej aktualizacji zapisanego zapytania.|
|[CDaoQueryDef::GetFieldCount](#getfieldcount)|Zwraca liczbę pól zdefiniowanych przez querydef.|
|[CDaoQueryDef:: GetFieldInfo](#getfieldinfo)|Zwraca informacje dotyczące określonego pola zdefiniowanego w zapytaniu.|
|[CDaoQueryDef:: GetName](#getname)|Zwraca nazwę obiektu querydef.|
|[CDaoQueryDef::GetODBCTimeout](#getodbctimeout)|Zwraca wartość limitu czasu używaną przez ODBC (dla kwerendy ODBC), gdy obiekt querydef jest wykonywany. Pozwala to określić, jak długo ma być możliwe ukończenie akcji zapytania.|
|[CDaoQueryDef::GetParameterCount](#getparametercount)|Zwraca liczbę parametrów zdefiniowanych dla zapytania.|
|[CDaoQueryDef:: GetParameterInfo](#getparameterinfo)|Zwraca informacje o określonym parametrze do zapytania.|
|[CDaoQueryDef::GetParamValue](#getparamvalue)|Zwraca wartość określonego parametru do zapytania.|
|[CDaoQueryDef::GetRecordsAffected](#getrecordsaffected)|Zwraca liczbę rekordów, których dotyczy zapytanie akcji.|
|[CDaoQueryDef::GetReturnsRecords](#getreturnsrecords)|Zwraca wartość różną od zera, jeśli zapytanie zdefiniowane przez program querydef zwraca rekordy.|
|[CDaoQueryDef::GetSQL](#getsql)|Zwraca ciąg SQL, który określa zapytanie zdefiniowane przez querydef.|
|[CDaoQueryDef:: GetType](#gettype)|Zwraca typ zapytania: delete, Update, append, Make-Table i tak dalej.|
|[CDaoQueryDef:: IsOpen](#isopen)|Zwraca wartość różną od zera, jeśli jest otwarta i może zostać wykonana.|
|[CDaoQueryDef:: Open](#open)|Otwiera istniejący obiekt querydef przechowywany w kolekcji QueryDefs bazy danych.|
|[CDaoQueryDef:: SetConnect](#setconnect)|Ustawia parametry połączenia dla zapytania przekazującego SQL na źródle danych ODBC.|
|[CDaoQueryDef:: SetName](#setname)|Ustawia nazwę zapisanego zapytania, zastępując nazwę używaną podczas tworzenia obiektu querydef.|
|[CDaoQueryDef::SetODBCTimeout](#setodbctimeout)|Ustawia wartość limitu czasu używaną przez ODBC (dla kwerendy ODBC), gdy obiekt querydef jest wykonywany.|
|[CDaoQueryDef::SetParamValue](#setparamvalue)|Ustawia wartość określonego parametru do zapytania.|
|[CDaoQueryDef::SetReturnsRecords](#setreturnsrecords)|Określa, czy querydef zwraca rekordy. Ustawienie tego atrybutu na wartość TRUE jest prawidłowe tylko dla zapytań przekazujących SQL.|
|[CDaoQueryDef::SetSQL](#setsql)|Ustawia ciąg SQL, który określa zapytanie zdefiniowane przez querydef.|
### <a name="public-data-members"></a>Publiczne elementy członkowskie danych
|Nazwa|Opis|
|----------|-----------------|
|[CDaoQueryDef:: m_pDAOQueryDef](#m_pdaoquerydef)|Wskaźnik do interfejsu OLE dla bazowego obiektu DAO querydef.|
|[CDaoQueryDef:: m_pDatabase](#m_pdatabase)|Wskaźnik do obiektu, `CDaoDatabase` z którym jest skojarzona wartość querydef. Querydef może być zapisany w bazie danych programu.|
## <a name="remarks"></a>Uwagi
Querydef to obiekt dostępu do danych, który zawiera instrukcję SQL opisującą zapytanie i jego właściwości, takie jak "Data utworzenia" i "limit czasu ODBC". Można również tworzyć tymczasowe obiekty querydef bez zapisywania, ale jest to wygodne i bardziej wydajne — do zapisywania często ponownie używanych zapytań w bazie danych. Obiekt [CDaoDatabase](../../mfc/reference/cdaodatabase-class.md) przechowuje kolekcję o nazwie kolekcja obiektów, która zawiera zapisane w niej obiekty querydef.
> [!NOTE]
> Klasy bazy danych DAO różnią się od klas baz danych MFC opartych na Open Database Connectivity (ODBC). Wszystkie nazwy klas baz danych DAO mają prefiks "CDao". Nadal można uzyskać dostęp do źródeł danych ODBC przy użyciu klas DAO. Ogólnie rzecz biorąc, klasy MFC oparte na obiektach DAO są bardziej możliwością niż klasy MFC oparte na ODBC; klasy oparte na DAO mogą uzyskiwać dostęp do danych, w tym za pośrednictwem sterowników ODBC, za pośrednictwem własnego aparatu bazy danych. Klasy oparte na obiektach DAO obsługują również operacje języka definicji danych (DDL), takie jak Dodawanie tabel za pośrednictwem klas, bez konieczności bezpośredniego wywoływania obiektów DAO.
## <a name="usage"></a>Użycie
Użyj obiektów querydef do pracy z istniejącym zapisanym zapytaniem lub w celu utworzenia nowego zapisanego zapytania lub zapytania tymczasowego:
1. We wszystkich przypadkach najpierw konstruuje `CDaoQueryDef` obiekt, dostarczając wskaźnik do obiektu [CDaoDatabase](../../mfc/reference/cdaodatabase-class.md) , do którego należy zapytanie.
1. Następnie wykonaj następujące czynności, w zależności od tego, co chcesz zrobić:
- Aby użyć istniejącego zapisanego zapytania, wywołaj funkcję [otwierającego](#open) elementu członkowskiego obiektu querydef, podając nazwę zapisanego zapytania.
- Aby utworzyć nowe zapisane zapytanie, wywołaj funkcję [tworzenia](#create) elementu członkowskiego obiektu querydef, podając nazwę zapytania. Następnie zadzwoń do [dołączenia](#append) , aby zapisać zapytanie przez dołączenie go do kolekcji QueryDefs bazy danych. `Create` umieszcza obiekt querydef w stanie otwartym, dlatego po wywołaniu `Create` nie jest wywoływana `Open` .
- Aby utworzyć tymczasowy obiekt querydef, wywołaj `Create` . Przekaż pusty ciąg jako nazwę zapytania. Nie wywołuj `Append` .
Po zakończeniu korzystania z obiektu querydef należy wywołać jego funkcję [zamykającą](#close) . następnie Zniszcz obiekt querydef.
> [!TIP]
> Najprostszym sposobem tworzenia zapisanych zapytań jest ich utworzenie i zapisanie ich w bazie danych przy użyciu programu Microsoft Access. Następnie możesz otworzyć i używać ich w kodzie MFC.
## <a name="purposes"></a>Płatnicz
Obiektu querydef można użyć do dowolnego z następujących celów:
- Aby utworzyć `CDaoRecordset` obiekt
- Aby wywołać `Execute` funkcję członkowską obiektu do bezpośredniego wykonania zapytania akcji lub zapytania przekazującego SQL
Można użyć obiektu querydef dla dowolnego typu zapytania, w tym instrukcji SELECT, Action, krzyżowe, DELETE, Update, dołączania, tworzenia tabeli, definicji danych, przekazywania zapytania SQL, Unii i zapytań zbiorczych. Typ zapytania jest określany na podstawie zawartości instrukcji SQL dostarczonej przez użytkownika. Aby uzyskać informacje na temat typów zapytań, zobacz `Execute` i [GetType](#gettype) funkcje składowe. Zestawy rekordów są często używane dla zapytań zwracających wiersze, zazwyczaj przy użyciu **SELECT... Z** słów kluczowych. `Execute` jest najczęściej używany do operacji zbiorczych. Aby uzyskać więcej informacji, zobacz [Execute](#execute) and [CDaoRecordset](../../mfc/reference/cdaorecordset-class.md).
## <a name="querydefs-and-recordsets"></a>QueryDefs i zestawy rekordów
Aby użyć obiektu querydef do utworzenia `CDaoRecordset` obiektu, zazwyczaj tworzysz lub otwierasz obiekt querydef zgodnie z powyższym opisem. Następnie Utwórz obiekt zestawu rekordów, przekazując wskaźnik do obiektu querydef podczas wywoływania [CDaoRecordset:: Open](../../mfc/reference/cdaorecordset-class.md#open). Przekazany obiekt querydef musi znajdować się w stanie otwartym. Aby uzyskać więcej informacji, zobacz Klasa [CDaoRecordset](../../mfc/reference/cdaorecordset-class.md).
Nie można użyć obiektu querydef do utworzenia zestawu rekordów (najczęściej używany dla querydef), chyba że jest w stanie otwartym. Umieść parametr querydef w stanie otwartym przez wywołanie metody `Open` lub `Create` .
## <a name="external-databases"></a>Zewnętrzne bazy danych
Obiekty querydef są preferowanym sposobem korzystania z natywnego dialektu SQL zewnętrznego aparatu bazy danych. Można na przykład utworzyć zapytanie Transact SQL (używane na Microsoft SQL Server) i zapisać je w obiekcie querydef. Jeśli musisz użyć zapytania SQL, który nie jest oparty na aparacie bazy danych Microsoft Jet, musisz podać parametry połączenia wskazujące zewnętrzne źródło danych. Zapytania z prawidłowymi parametrami połączenia pomijają aparat bazy danych i przekazują zapytanie bezpośrednio do zewnętrznego serwera bazy danych w celu przetworzenia.
> [!TIP]
> Preferowanym sposobem pracy z tabelami ODBC jest dołączenie ich do aparatu Microsoft Jet (. MDB).
Aby uzyskać powiązane informacje, zobacz temat "QueryDef Object", "kolekcja zadań" i "CdbDatabase Object" w zestawie DAO SDK.
## <a name="inheritance-hierarchy"></a>Hierarchia dziedziczenia
[CObject](../../mfc/reference/cobject-class.md)
`CDaoQueryDef`
## <a name="requirements"></a>Wymagania
**Nagłówek:** afxdao. h
## <a name="cdaoquerydefappend"></a><a name="append"></a> CDaoQueryDef:: Append
Wywołaj tę funkcję elementu członkowskiego po wywołaniu metody [Create](#create) , aby utworzyć nowy obiekt querydef.
```
virtual void Append();
```
### <a name="remarks"></a>Uwagi
`Append` zapisuje obiekt querydef w bazie danych przez dołączenie go do kolekcji QueryDefs bazy danych. Obiekt querydef można użyć jako obiektu tymczasowego bez dołączania go, ale jeśli chcesz, aby go utrwalał, musisz wywołać metodę `Append` .
Jeśli próbujesz dołączyć tymczasowy obiekt querydef, MFC zgłosi wyjątek typu [CDaoException](../../mfc/reference/cdaoexception-class.md).
## <a name="cdaoquerydefcanupdate"></a><a name="canupdate"></a> CDaoQueryDef:: Update
Wywołaj tę funkcję elementu członkowskiego, aby określić, czy można modyfikować parametry querydef, takie jak zmiana jego nazwy lub ciągu SQL.
```
BOOL CanUpdate();
```
### <a name="return-value"></a>Wartość zwracana
Niezerowe, jeśli masz uprawnienia do modyfikowania wartości querydef; w przeciwnym razie 0.
### <a name="remarks"></a>Uwagi
Można zmodyfikować:
- Nie jest on oparty na bazie danych, która jest otwarta tylko do odczytu.
- Masz uprawnienia do aktualizacji bazy danych.
Jest to zależne od tego, czy zostały zaimplementowane funkcje zabezpieczeń. MFC nie zapewnia obsługi zabezpieczeń; należy zaimplementować go samodzielnie, wywołując obiekt DAO bezpośrednio lub przy użyciu programu Microsoft Access. Zapoznaj się z tematem "Właściwość uprawnienia" w pomocy DAO.
## <a name="cdaoquerydefcdaoquerydef"></a><a name="cdaoquerydef"></a> CDaoQueryDef::CDaoQueryDef
Konstruuje `CDaoQueryDef` obiekt.
```
CDaoQueryDef(CDaoDatabase* pDatabase);
```
### <a name="parameters"></a>Parametry
*pDatabase*<br/>
Wskaźnik do otwartego obiektu [CDaoDatabase](../../mfc/reference/cdaodatabase-class.md) .
### <a name="remarks"></a>Uwagi
Obiekt może reprezentować istniejącą wartość querydef przechowywaną w kolekcji QueryDefs bazy danych, nowe zapytanie, które ma być przechowywane w kolekcji lub tymczasowe zapytanie, które nie ma być przechowywane. Następny krok zależy od typu querydef:
- Jeśli obiekt reprezentuje istniejący obiekt querydef, wywołaj funkcję [otwierającego](#open) elementu członkowskiego obiektu, aby ją zainicjować.
- Jeśli obiekt reprezentuje nową querydef do zapisania, wywołaj funkcję [tworzenia](#create) elementu członkowskiego obiektu. Spowoduje to dodanie obiektu do kolekcji QueryDefs bazy danych. Następnie Wywołaj `CDaoQueryDef` funkcje członkowskie, aby ustawić atrybuty obiektu. Na koniec Wywołaj [dołączenie](#append).
- Jeśli obiekt reprezentuje tymczasowy element querydef (nie można zapisać w bazie danych), wywołaj `Create` , przekazując pusty ciąg jako nazwę zapytania. Po wywołaniu `Create` , zainicjuj metodę querydef, bezpośrednio ustawiając jej atrybuty. Nie wywołuj `Append` .
Aby ustawić atrybuty obiektu querydef, można użyć funkcji [SetName](#setname), [SetSQL](#setsql), [SetConnect](#setconnect), [SetODBCTimeout](#setodbctimeout)i [SetReturnsRecords](#setreturnsrecords) .
Po zakończeniu pracy z obiektem querydef należy wywołać jego funkcję [zamykającą](#close) . Jeśli masz wskaźnik do obiektu querydef, użyj **`delete`** operatora, aby zniszczyć obiekt C++.
## <a name="cdaoquerydefclose"></a><a name="close"></a> CDaoQueryDef:: Close
Wywołaj tę funkcję elementu członkowskiego po zakończeniu korzystania z obiektu querydef.
```
virtual void Close();
```
### <a name="remarks"></a>Uwagi
Zamknięcie interfejsu querydef powoduje zwolnienie bazowego obiektu DAO, ale nie niszczy zapisanego obiektu DAO querydef lub `CDaoQueryDef` obiektu C++. Ta wartość nie jest taka sama jak [CDaoDatabase::D eletequerydef](../../mfc/reference/cdaodatabase-class.md#deletequerydef), która usuwa obiekt querydef z kolekcji QueryDefs bazy danych w DAO (jeśli nie jest to tymczasowy obiekt querydef).
## <a name="cdaoquerydefcreate"></a><a name="create"></a> CDaoQueryDef:: Create
Wywołaj tę funkcję elementu członkowskiego, aby utworzyć nową zapisaną kwerendę lub nową tymczasową kwerendę.
```
virtual void Create(
LPCTSTR lpszName = NULL,
LPCTSTR lpszSQL = NULL);
```
### <a name="parameters"></a>Parametry
*lpszName*<br/>
Unikatowa nazwa zapytania zapisanego w bazie danych. Aby uzyskać szczegółowe informacje na temat ciągu, zobacz temat "Metoda". "w pomocy DAO. W przypadku zaakceptowania wartości domyślnej, pustego ciągu, zostanie utworzony tymczasowy obiekt querydef. Takie zapytanie nie jest zapisane w kolekcji QueryDefs.
*lpszSQL*<br/>
Ciąg SQL, który definiuje zapytanie. W przypadku zaakceptowania domyślnej wartości NULL należy później wywołać [SetSQL](#setsql) , aby ustawić ciąg. Do tego czasu zapytanie jest niezdefiniowane. Można jednak użyć niezdefiniowanego zapytania, aby otworzyć zestaw rekordów; Aby uzyskać szczegółowe informacje, zobacz uwagi. Instrukcja SQL musi być zdefiniowana, aby można było dołączyć do kolekcji QueryDefs.
### <a name="remarks"></a>Uwagi
W przypadku przekazania nazwy w *lpszName* można następnie wywołać [dołączenie](#append) w celu zapisania obiektu querydef w kolekcji QueryDefs bazy danych. W przeciwnym razie obiekt jest tymczasowy querydef i nie jest zapisywany. W obu przypadkach obiekt querydef jest w stanie otwartym i można go użyć do utworzenia obiektu [CDaoRecordset](../../mfc/reference/cdaorecordset-class.md) lub wywołania funkcji elementu członkowskiego [Execute](#execute) .
Jeśli nie podasz instrukcji SQL w *lpszSQL*, nie można uruchomić zapytania z, ale można `Execute` go użyć do utworzenia zestawu rekordów. W takim przypadku MFC używa domyślnej instrukcji SQL zestawu rekordów.
## <a name="cdaoquerydefexecute"></a><a name="execute"></a> CDaoQueryDef:: Execute
Wywołaj tę funkcję elementu członkowskiego, aby uruchomić zapytanie zdefiniowane przez obiekt querydef.
```
virtual void Execute(int nOptions = dbFailOnError);
```
### <a name="parameters"></a>Parametry
*nOptions*<br/>
Liczba całkowita, która określa charakterystykę zapytania. Aby uzyskać powiązane informacje, zobacz temat "Metoda Execute" w pomocy DAO. Można użyć operatora bitowego lub ( **|**), aby połączyć następujące stałe dla tego argumentu:
- `dbDenyWrite` Odmów uprawnienia do zapisu innym użytkownikom.
- `dbInconsistent` Niespójne aktualizacje.
- `dbConsistent` Spójne aktualizacje.
- `dbSQLPassThrough` Przekazywanie SQL. Powoduje przekazanie instrukcji SQL do bazy danych ODBC w celu przetworzenia.
- `dbFailOnError` Wartość domyślna. Wycofaj aktualizacje w przypadku wystąpienia błędu i Zgłoś błąd użytkownikowi.
- `dbSeeChanges` Generuj błąd czasu wykonywania, jeśli inny użytkownik zmienia edytowane dane.
> [!NOTE]
> Aby uzyskać wyjaśnienie warunków "niespójne" i "spójne", zobacz temat "Metoda Execute" w pomocy DAO.
### <a name="remarks"></a>Uwagi
Obiekty querydef używane do wykonywania w ten sposób mogą reprezentować tylko jeden z następujących typów zapytań:
- Zapytania akcji
- Zapytania przekazujące SQL
`Execute` nie działa w przypadku zapytań, które zwracają rekordy, takich jak zapytania select. `Execute` jest często używany do wykonywania zapytań operacji zbiorczych, takich jak **Update**, **INSERT** lub **SELECT INTO** lub dla operacji języka definicji danych (DDL).
> [!TIP]
> Preferowanym sposobem pracy ze źródłami danych ODBC jest dołączenie tabel do programu Microsoft Jet (. MDB). Aby uzyskać więcej informacji, zobacz temat "Uzyskiwanie dostępu do zewnętrznych baz danych za pomocą DAO" w pomocy DAO.
Wywołaj funkcję członkowską [GetRecordsAffected](#getrecordsaffected) obiektu querydef, aby określić liczbę rekordów, których dotyczy ostatnie `Execute` wywołanie. Na przykład `GetRecordsAffected` zwraca informacje o liczbie rekordów usuniętych, zaktualizowanych lub wstawianych podczas wykonywania zapytania akcji. Zwracana liczba nie będzie odzwierciedlać zmian w powiązanych tabelach, gdy są włączone kaskadowe aktualizacje lub usunięcia.
Jeśli dołączysz oba elementy `dbInconsistent` i `dbConsistent` lub jeśli nie dołączysz żadnego z nich, wynik jest wartością domyślną `dbInconsistent` .
`Execute` nie zwraca zestawu rekordów. Użycie `Execute` w zapytaniu, które wybiera rekordy powoduje, że MFC zgłasza wyjątek typu [CDaoException](../../mfc/reference/cdaoexception-class.md).
## <a name="cdaoquerydefgetconnect"></a><a name="getconnect"></a> CDaoQueryDef:: GetConnect
Wywołaj tę funkcję elementu członkowskiego, aby uzyskać parametry połączenia skojarzone ze źródłem danych querydef.
```
CString GetConnect();
```
### <a name="return-value"></a>Wartość zwracana
[CString](../../atl-mfc-shared/reference/cstringt-class.md) zawierający parametry połączenia dla elementu querydef.
### <a name="remarks"></a>Uwagi
Ta funkcja jest używana tylko ze źródłami danych ODBC i określonymi sterownikami ISAM. Nie jest on używany z programem Microsoft Jet (. MDB) — bazy danych w tym przypadku `GetConnect` zwraca pusty ciąg. Aby uzyskać więcej informacji, zobacz [SetConnect](#setconnect).
> [!TIP]
> Preferowanym sposobem pracy z tabelami ODBC jest dołączenie ich do. Baza danych MDB. Aby uzyskać więcej informacji, zobacz temat "Uzyskiwanie dostępu do zewnętrznych baz danych za pomocą DAO" w pomocy DAO.
Aby uzyskać informacje na temat parametrów połączenia, zobacz temat "Connect Property" w pomocy DAO.
## <a name="cdaoquerydefgetdatecreated"></a><a name="getdatecreated"></a> CDaoQueryDef::GetDateCreated
Wywołaj tę funkcję elementu członkowskiego, aby uzyskać datę utworzenia obiektu querydef.
```
COleDateTime GetDateCreated();
```
### <a name="return-value"></a>Wartość zwracana
Obiekt [COleDateTime](../../atl-mfc-shared/reference/coledatetime-class.md) zawierający datę i godzinę utworzenia obiektu querydef.
### <a name="remarks"></a>Uwagi
Aby uzyskać powiązane informacje, zobacz temat "DateCreated, LastUpdated Properties" w pomocy DAO.
## <a name="cdaoquerydefgetdatelastupdated"></a><a name="getdatelastupdated"></a> CDaoQueryDef::GetDateLastUpdated
Wywołaj tę funkcję elementu członkowskiego, aby uzyskać datę ostatniej aktualizacji obiektu querydef — w przypadku zmiany jego właściwości, takich jak nazwa, ciąg SQL lub jego parametry połączenia.
```
COleDateTime GetDateLastUpdated();
```
### <a name="return-value"></a>Wartość zwracana
Obiekt [COleDateTime](../../atl-mfc-shared/reference/coledatetime-class.md) zawierający datę i godzinę ostatniej aktualizacji obiektu querydef.
### <a name="remarks"></a>Uwagi
Aby uzyskać powiązane informacje, zobacz temat "DateCreated, LastUpdated Properties" w pomocy DAO.
## <a name="cdaoquerydefgetfieldcount"></a><a name="getfieldcount"></a> CDaoQueryDef::GetFieldCount
Wywołaj tę funkcję elementu członkowskiego, aby pobrać liczbę pól w zapytaniu.
```
short GetFieldCount();
```
### <a name="return-value"></a>Wartość zwracana
Liczba pól zdefiniowanych w zapytaniu.
### <a name="remarks"></a>Uwagi
`GetFieldCount` jest przydatne do zapętlania przez wszystkie pola w querydef. W tym celu należy użyć `GetFieldCount` w połączeniu z [GetFieldInfo](#getfieldinfo).
## <a name="cdaoquerydefgetfieldinfo"></a><a name="getfieldinfo"></a> CDaoQueryDef:: GetFieldInfo
Wywołaj tę funkcję elementu członkowskiego, aby uzyskać różne rodzaje informacji dotyczących pola zdefiniowanego w wywołaniu obiektu querydef.
```cpp
void GetFieldInfo(
int nIndex,
CDaoFieldInfo& fieldinfo,
DWORD dwInfoOptions = AFX_DAO_PRIMARY_INFO);
void GetFieldInfo(
LPCTSTR lpszName,
CDaoFieldInfo& fieldinfo,
DWORD dwInfoOptions = AFX_DAO_PRIMARY_INFO);
```
### <a name="parameters"></a>Parametry
*nIndex*<br/>
Indeks (liczony od zera) żądanego pola w kolekcji pól querydef dla wyszukiwania według indeksu.
*FieldInfo*<br/>
Odwołanie do `CDaoFieldInfo` obiektu, który zwraca żądane informacje.
*dwInfoOptions*<br/>
Opcje określające, które informacje o polu pobrać. Dostępne opcje są wymienione tutaj wraz z tym, co powodują, że funkcja zwraca:
- AFX_DAO_PRIMARY_INFO (domyślnie) nazwa, typ, rozmiar, atrybuty
- AFX_DAO_SECONDARY_INFO informacje podstawowe plus: pozycja porządkowa, wymagane, Zezwalaj na zerową długość, pole źródłowe, Nazwa obca, tabela źródłowa, porządek sortowania
- AFX_DAO_ALL_INFO informacje podstawowe i pomocnicze oraz: wartość domyślna, walidacja tekstu, reguła walidacji
*lpszName*<br/>
Ciąg zawierający nazwę żądanego pola, dla wyszukiwania według nazwy. Możesz użyć [CString](../../atl-mfc-shared/reference/cstringt-class.md).
### <a name="remarks"></a>Uwagi
Aby uzyskać opis informacji zwracanych w elemencie *FieldInfo*, zobacz strukturę [CDaoFieldInfo —](../../mfc/reference/cdaofieldinfo-structure.md) . Ta struktura zawiera elementy członkowskie, które odpowiadają opisowym informacjom w obszarze *dwInfoOptions* powyżej. Jeśli zażądasz jednego poziomu informacji, uzyskasz również informacje o wcześniejszych poziomach.
## <a name="cdaoquerydefgetname"></a><a name="getname"></a> CDaoQueryDef:: GetName
Wywołaj tę funkcję elementu członkowskiego, aby pobrać nazwę zapytania reprezentowanego przez element querydef.
```
CString GetName();
```
### <a name="return-value"></a>Wartość zwracana
Nazwa zapytania.
### <a name="remarks"></a>Uwagi
Nazwy querydef są unikatowymi nazwami definiowanymi przez użytkownika. Aby uzyskać więcej informacji na temat nazw querydef, zobacz temat "name property" w pomocy DAO.
## <a name="cdaoquerydefgetodbctimeout"></a><a name="getodbctimeout"></a> CDaoQueryDef::GetODBCTimeout
Wywołaj tę funkcję elementu członkowskiego, aby pobrać bieżący limit czasu, zanim zapytanie do źródła danych ODBC przekroczy limit czasu.
```
short GetODBCTimeout();
```
### <a name="return-value"></a>Wartość zwracana
Liczba sekund przed upływem limitu czasu zapytania.
### <a name="remarks"></a>Uwagi
Aby uzyskać informacje o tym limicie czasu, zobacz temat "Właściwość ODBCTimeout" w pomocy DAO.
> [!TIP]
> Preferowanym sposobem pracy z tabelami ODBC jest dołączenie ich do aparatu Microsoft Jet (. MDB). Aby uzyskać więcej informacji, zobacz temat "Uzyskiwanie dostępu do zewnętrznych baz danych za pomocą DAO" w pomocy DAO.
## <a name="cdaoquerydefgetparametercount"></a><a name="getparametercount"></a> CDaoQueryDef::GetParameterCount
Wywołaj tę funkcję elementu członkowskiego, aby pobrać liczbę parametrów w zapisanej kwerendzie.
```
short GetParameterCount();
```
### <a name="return-value"></a>Wartość zwracana
Liczba parametrów zdefiniowanych w zapytaniu.
### <a name="remarks"></a>Uwagi
`GetParameterCount` jest przydatne do zapętlania przez wszystkie parametry w querydef. W tym celu należy użyć `GetParameterCount` w połączeniu z [GetParameterInfo](#getparameterinfo).
Aby uzyskać powiązane informacje, zobacz tematy "obiekt parametrów", "Kolekcja parametrów" i "parametry deklaracji (SQL)" w pomocy DAO.
## <a name="cdaoquerydefgetparameterinfo"></a><a name="getparameterinfo"></a> CDaoQueryDef:: GetParameterInfo
Wywołaj tę funkcję elementu członkowskiego, aby uzyskać informacje o parametrze zdefiniowanym w elemencie querydef.
```cpp
void GetParameterInfo(
int nIndex,
CDaoParameterInfo& paraminfo,
DWORD dwInfoOptions = AFX_DAO_PRIMARY_INFO);
void GetParameterInfo(
LPCTSTR lpszName,
CDaoParameterInfo& paraminfo,
DWORD dwInfoOptions = AFX_DAO_PRIMARY_INFO);
```
### <a name="parameters"></a>Parametry
*nIndex*<br/>
Indeks (liczony od zera) odpowiedniego parametru w kolekcji parametrów querydef dla wyszukiwania według indeksu.
*paraminfo*<br/>
Odwołanie do obiektu [CDaoParameterInfo —](../../mfc/reference/cdaoparameterinfo-structure.md) , który zwraca żądane informacje.
*dwInfoOptions*<br/>
Opcje określające informacje o parametrach do pobrania. Dostępna opcja jest wyświetlana w tym miejscu wraz z tym, co powoduje, że funkcja zwraca:
- Nazwa AFX_DAO_PRIMARY_INFO (domyślnie), typ
*lpszName*<br/>
Ciąg zawierający nazwę żądanego parametru dla wyszukiwania według nazwy. Możesz użyć [CString](../../atl-mfc-shared/reference/cstringt-class.md).
### <a name="remarks"></a>Uwagi
Aby uzyskać opis informacji zwracanych w *ParamInfo*, zobacz [CDaoParameterInfo —](../../mfc/reference/cdaoparameterinfo-structure.md) Structure. Ta struktura zawiera elementy członkowskie, które odpowiadają opisowym informacjom w obszarze *dwInfoOptions* powyżej.
Aby uzyskać powiązane informacje, zobacz temat "parametry deklaracji (SQL)" w pomocy DAO.
## <a name="cdaoquerydefgetparamvalue"></a><a name="getparamvalue"></a> CDaoQueryDef::GetParamValue
Wywołaj tę funkcję elementu członkowskiego, aby pobrać bieżącą wartość określonego parametru przechowywanego w kolekcji parametrów obiektu querydef.
```
virtual COleVariant GetParamValue(LPCTSTR lpszName);
virtual COleVariant GetParamValue(int nIndex);
```
### <a name="parameters"></a>Parametry
*lpszName*<br/>
Nazwa parametru, którego wartość ma być wyszukiwana według nazwy.
*nIndex*<br/>
Liczony od zera indeks parametru w kolekcji parametrów querydef dla wyszukiwania według indeksu. Tę wartość można uzyskać za pomocą wywołań [GetParameterCount](#getparametercount) i [GetParameterInfo](#getparameterinfo).
### <a name="return-value"></a>Wartość zwracana
Obiekt klasy [COleVariant](../../mfc/reference/colevariant-class.md) , który zawiera wartość parametru.
### <a name="remarks"></a>Uwagi
Możesz uzyskać dostęp do parametru według nazwy lub według pozycji porządkowej w kolekcji.
Aby uzyskać powiązane informacje, zobacz temat "parametry deklaracji (SQL)" w pomocy DAO.
## <a name="cdaoquerydefgetrecordsaffected"></a><a name="getrecordsaffected"></a> CDaoQueryDef::GetRecordsAffected
Wywołaj tę funkcję elementu członkowskiego, aby określić liczbę rekordów, na które miało wpływ ostatnie wywołanie metody [Execute](#execute).
```
long GetRecordsAffected();
```
### <a name="return-value"></a>Wartość zwracana
Liczba rekordów, których to dotyczy.
### <a name="remarks"></a>Uwagi
Zwracana liczba nie będzie odzwierciedlać zmian w powiązanych tabelach, gdy są włączone kaskadowe aktualizacje lub usunięcia.
Aby uzyskać powiązane informacje, zobacz temat "Właściwość RecordsAffected" w pomocy DAO.
## <a name="cdaoquerydefgetreturnsrecords"></a><a name="getreturnsrecords"></a> CDaoQueryDef::GetReturnsRecords
Wywołaj tę funkcję elementu członkowskiego, aby określić, czy obiekt querydef jest oparty na zapytaniu zwracającym rekordy.
```
BOOL GetReturnsRecords();
```
### <a name="return-value"></a>Wartość zwracana
Różne od zera, jeśli obiekt querydef jest oparty na zapytaniu zwracającym rekordy; w przeciwnym razie 0.
### <a name="remarks"></a>Uwagi
Ta funkcja członkowska jest używana tylko w przypadku zapytań przekazujących SQL. Aby uzyskać więcej informacji na temat zapytań SQL, zobacz [wykonywanie](#execute) funkcji składowej. Aby uzyskać więcej informacji na temat pracy z kwerendami przekazującymi dane SQL, zobacz funkcja członkowska [SetReturnsRecords](#setreturnsrecords) .
Aby uzyskać powiązane informacje, zobacz temat "Właściwość ReturnsRecords" w pomocy DAO.
## <a name="cdaoquerydefgetsql"></a><a name="getsql"></a> CDaoQueryDef::GetSQL
Wywołaj tę funkcję elementu członkowskiego, aby pobrać instrukcję SQL, która definiuje zapytanie, na którym bazuje.
```
CString GetSQL();
```
### <a name="return-value"></a>Wartość zwracana
Instrukcja SQL definiująca zapytanie, na którym bazuje querydef.
### <a name="remarks"></a>Uwagi
Następnie prawdopodobnie przeanalizuje ciąg słów kluczowych, nazw tabel i tak dalej.
Aby uzyskać powiązane informacje, zobacz temat "Właściwość SQL", "porównanie aparatu bazy danych Microsoft Jet SQL i ANSI SQL" oraz "wykonywanie zapytania względem bazy danych SQL w kodzie" w pomocy DAO.
## <a name="cdaoquerydefgettype"></a><a name="gettype"></a> CDaoQueryDef:: GetType
Wywołaj tę funkcję elementu członkowskiego, aby określić typ zapytania dla obiektu querydef.
```
short GetType();
```
### <a name="return-value"></a>Wartość zwracana
Typ zapytania zdefiniowany przez querydef. Aby uzyskać wartości, zobacz uwagi.
### <a name="remarks"></a>Uwagi
Typ zapytania jest ustawiany przez wartość określoną w ciągu SQL obiektu querydef podczas tworzenia obiektu querydef lub wywołaj funkcję członkowską [SetSQL](#setsql) istniejącej obiektu querydef. Typ zapytania zwracany przez tę funkcję może być jedną z następujących wartości:
- `dbQSelect` Zaznaczenia
- `dbQAction` Transakcji
- `dbQCrosstab` Krzyż
- `dbQDelete` Usunięty
- `dbQUpdate` Aktualizacji
- `dbQAppend` Łączono
- `dbQMakeTable` Utwórz tabelę
- `dbQDDL` Definicja danych
- `dbQSQLPassThrough` Przekazywanie
- `dbQSetOperation` Unii
- `dbQSPTBulk` Używany z programem w `dbQSQLPassThrough` celu określenia zapytania, które nie zwraca rekordów.
> [!NOTE]
> Aby utworzyć kwerendę przekazującą SQL, nie ustawiaj `dbSQLPassThrough` stałej. Ta wartość jest ustawiana automatycznie przez aparat bazy danych Microsoft Jet podczas tworzenia obiektu querydef i ustawiania parametrów połączenia.
Aby uzyskać informacje o ciągach SQL, zobacz [GetSQL](#getsql). Aby uzyskać informacje na temat typów zapytań, zobacz [Execute](#execute).
## <a name="cdaoquerydefisopen"></a><a name="isopen"></a> CDaoQueryDef:: IsOpen
Wywołaj tę funkcję elementu członkowskiego, aby określić, czy `CDaoQueryDef` obiekt jest aktualnie otwarty.
```
BOOL IsOpen() const;
```
### <a name="return-value"></a>Wartość zwracana
Niezerowe, jeśli `CDaoQueryDef` obiekt jest aktualnie otwarty; w przeciwnym razie 0.
### <a name="remarks"></a>Uwagi
Obiekt querydef musi znajdować się w stanie otwartym przed użyciem go do wywołania [Execute](#execute) lub do utworzenia obiektu [CDaoRecordset](../../mfc/reference/cdaorecordset-class.md) . Aby umieścić obiekt querydef w wywołaniu w stanie otwartym, [Utwórz](#create) (dla nowego obiektu querydef) lub [Otwórz](#open) (dla istniejącego obiektu querydef).
## <a name="cdaoquerydefm_pdatabase"></a><a name="m_pdatabase"></a> CDaoQueryDef:: m_pDatabase
Zawiera wskaźnik do obiektu [CDaoDatabase](../../mfc/reference/cdaodatabase-class.md) skojarzonego z obiektem querydef.
### <a name="remarks"></a>Uwagi
Użyj tego wskaźnika, jeśli chcesz uzyskać bezpośredni dostęp do bazy danych — na przykład, aby uzyskać wskaźniki do innych obiektów querydef lub Recordset w kolekcjach baz danych.
## <a name="cdaoquerydefm_pdaoquerydef"></a><a name="m_pdaoquerydef"></a> CDaoQueryDef:: m_pDAOQueryDef
Zawiera wskaźnik do interfejsu OLE dla bazowego obiektu DAO querydef.
### <a name="remarks"></a>Uwagi
Ten wskaźnik zapewnia kompletność i spójność z innymi klasami. Jednak, ponieważ MFC nie pełni hermetyzowa obiektów DAO, prawdopodobnie nie będą potrzebne. W razie potrzeby należy zachować ostrożność — w szczególności nie należy zmieniać wartości wskaźnika, chyba że wiesz, co robisz.
## <a name="cdaoquerydefopen"></a><a name="open"></a> CDaoQueryDef:: Open
Wywołaj tę funkcję elementu członkowskiego, aby otworzyć obiekt querydef wcześniej zapisany w kolekcji QueryDefs bazy danych.
```
virtual void Open(LPCTSTR lpszName = NULL);
```
### <a name="parameters"></a>Parametry
*lpszName*<br/>
Ciąg, który zawiera nazwę zapisanego obiektu querydef do otwarcia. Możesz użyć [CString](../../atl-mfc-shared/reference/cstringt-class.md).
### <a name="remarks"></a>Uwagi
Gdy obiekt querydef jest otwarty, można [wywołać jego funkcję](#execute) elementu członkowskiego lub użyć obiektu querydef do tworzenia obiektów [CDaoRecordset](../../mfc/reference/cdaorecordset-class.md) .
## <a name="cdaoquerydefsetconnect"></a><a name="setconnect"></a> CDaoQueryDef:: SetConnect
Wywołaj tę funkcję elementu członkowskiego, aby ustawić parametry połączenia obiektu querydef.
```cpp
void SetConnect(LPCTSTR lpszConnect);
```
### <a name="parameters"></a>Parametry
*lpszConnect*<br/>
Ciąg zawierający parametry połączenia dla skojarzonego obiektu [CDaoDatabase](../../mfc/reference/cdaodatabase-class.md) .
### <a name="remarks"></a>Uwagi
Parametry połączenia służą do przekazywania dodatkowych informacji do ODBC i niektórych sterowników ISAM zgodnie z wymaganiami. Nie jest on używany w programie Microsoft Jet (. MDB).
> [!TIP]
> Preferowanym sposobem pracy z tabelami ODBC jest dołączenie ich do. Baza danych MDB.
Przed wykonaniem obiektu querydef reprezentującego kwerendę przekazujące SQL do źródła danych ODBC, należy ustawić parametry połączenia z `SetConnect` i wywołać [SetReturnsRecords](#setreturnsrecords) , aby określić, czy zapytanie zwraca rekordy.
Aby uzyskać więcej informacji o strukturze i przykładach parametrów połączenia, zobacz temat "Connect Property" w pomocy DAO.
## <a name="cdaoquerydefsetname"></a><a name="setname"></a> CDaoQueryDef:: SetName
Wywołaj tę funkcję elementu członkowskiego, jeśli chcesz zmienić nazwę obiektu querydef, która nie jest tymczasowa.
```cpp
void SetName(LPCTSTR lpszName);
```
### <a name="parameters"></a>Parametry
*lpszName*<br/>
Ciąg, który zawiera nową nazwę dla nietymczasowego zapytania w skojarzonym obiekcie [CDaoDatabase](../../mfc/reference/cdaodatabase-class.md) .
### <a name="remarks"></a>Uwagi
Nazwy querydef są unikatowe, zdefiniowane przez użytkownika nazwy. Możesz wywołać `SetName` przed dołączeniem obiektu querydef do kolekcji QueryDefs.
## <a name="cdaoquerydefsetodbctimeout"></a><a name="setodbctimeout"></a> CDaoQueryDef::SetODBCTimeout
Wywołaj tę funkcję elementu członkowskiego, aby ustawić limit czasu, zanim zapytanie ze źródłem danych ODBC przekroczyło limit czasu.
```cpp
void SetODBCTimeout(short nODBCTimeout);
```
### <a name="parameters"></a>Parametry
*nODBCTimeout*<br/>
Liczba sekund przed upływem limitu czasu zapytania.
### <a name="remarks"></a>Uwagi
Ta funkcja członkowska pozwala zastąpić domyślną liczbę sekund przed upływem limitu czasu dla kolejnych operacji w połączonym źródle danych. Operacja może przekroczyć limit czasu, ponieważ występują problemy z dostępem do sieci, nadmierny czas przetwarzania zapytania i tak dalej. Wywołaj `SetODBCTimeout` przed wykonaniem zapytania przy użyciu tego elementu querydef, jeśli chcesz zmienić wartość limitu czasu zapytania. (Jako że ODBC ponownie używa połączeń, wartość limitu czasu jest taka sama dla wszystkich klientów w ramach tego samego połączenia).
Wartość domyślna dla limitów czasu zapytania to 60 sekund.
## <a name="cdaoquerydefsetparamvalue"></a><a name="setparamvalue"></a> CDaoQueryDef::SetParamValue
Wywołaj tę funkcję elementu członkowskiego, aby ustawić wartość parametru w wywołaniu obiektu querydef w czasie wykonywania.
```
virtual void SetParamValue(
LPCTSTR lpszName,
const COleVariant& varValue);
virtual void SetParamValue(
int nIndex,
const COleVariant& varValue);
```
### <a name="parameters"></a>Parametry
*lpszName*<br/>
Nazwa parametru, którego wartość ma zostać ustawiona.
*varValue*<br/>
Wartość do ustawienia; Zobacz uwagi.
*nIndex*<br/>
Pozycja porządkowa parametru w kolekcji parametrów querydef. Tę wartość można uzyskać za pomocą wywołań [GetParameterCount](#getparametercount) i [GetParameterInfo](#getparameterinfo).
### <a name="remarks"></a>Uwagi
Parametr musi już zostać ustanowiony jako część ciągu SQL obiektu querydef. Możesz uzyskać dostęp do parametru według nazwy lub według pozycji porządkowej w kolekcji.
Określ wartość, która ma zostać ustawiona jako `COleVariant` obiekt. Aby uzyskać informacje na temat ustawiania żądanej wartości i typu w `COleVariant` obiekcie, zobacz Klasa [COleVariant](../../mfc/reference/colevariant-class.md).
## <a name="cdaoquerydefsetreturnsrecords"></a><a name="setreturnsrecords"></a> CDaoQueryDef::SetReturnsRecords
Wywołaj tę funkcję elementu członkowskiego w ramach procesu konfigurowania zapytania przekazującego SQL do zewnętrznej bazy danych.
```cpp
void SetReturnsRecords(BOOL bReturnsRecords);
```
### <a name="parameters"></a>Parametry
*bReturnsRecords*<br/>
Należy przekazać wartość TRUE, jeśli zapytanie dotyczące zewnętrznej bazy danych zwraca rekordy; w przeciwnym razie FALSE.
### <a name="remarks"></a>Uwagi
W takim przypadku należy utworzyć obiekt querydef i ustawić jego właściwości przy użyciu innych `CDaoQueryDef` funkcji Członkowskich. Aby uzyskać opis zewnętrznych baz danych, zobacz [SetConnect](#setconnect).
## <a name="cdaoquerydefsetsql"></a><a name="setsql"></a> CDaoQueryDef::SetSQL
Wywołaj tę funkcję elementu członkowskiego, aby ustawić instrukcję SQL, która jest wykonywana przez querydef.
```cpp
void SetSQL(LPCTSTR lpszSQL);
```
### <a name="parameters"></a>Parametry
*lpszSQL*<br/>
Ciąg zawierający kompletną instrukcję SQL, odpowiednią do wykonania. Składnia tego ciągu zależy od systemu DBMS, do którego odwołuje się zapytanie. Omówienie składni używanej w aparacie bazy danych Microsoft Jet można znaleźć w temacie "Kompilowanie instrukcji SQL w kodzie" w pomocy DAO.
### <a name="remarks"></a>Uwagi
Typowym zastosowaniem `SetSQL` jest skonfigurowanie obiektu querydef do użycia w zapytaniu przekazującym SQL. (Składnia zapytań przekazujących SQL w docelowym systemie DBMS znajduje się w dokumentacji systemu DBMS).
## <a name="see-also"></a>Zobacz też
[Klasa CObject](../../mfc/reference/cobject-class.md)<br/>
[Wykres hierarchii](../../mfc/hierarchy-chart.md)<br/>
[Klasa CDaoRecordset](../../mfc/reference/cdaorecordset-class.md)<br/>
[Klasa CDaoDatabase](../../mfc/reference/cdaodatabase-class.md)<br/>
[Klasa CDaoTableDef](../../mfc/reference/cdaotabledef-class.md)<br/>
[Klasa CDaoException](../../mfc/reference/cdaoexception-class.md)
| 49.463991 | 730 | 0.784132 | pol_Latn | 0.999623 |
08cd45e71b673f5ade8c4f12677a2ff929c622df | 42 | md | Markdown | README.md | pokeguys/KiraraFantasia-Bot | 5d1f81693ead5c794df4034346e3de040e11daff | [
"MIT"
] | 1 | 2018-02-08T13:30:55.000Z | 2018-02-08T13:30:55.000Z | README.md | pokeguys/KiraraFantasia-Bot | 5d1f81693ead5c794df4034346e3de040e11daff | [
"MIT"
] | null | null | null | README.md | pokeguys/KiraraFantasia-Bot | 5d1f81693ead5c794df4034346e3de040e11daff | [
"MIT"
] | null | null | null | # KiraraFantasia-Bot
Kirara Fantansia Bot
| 14 | 20 | 0.833333 | cat_Latn | 0.177676 |
08cdc4e3843c08edadbcba02c1649bc5988b4474 | 18,680 | md | Markdown | docs/mfc/reference/cmfcribbonstatusbar-class.md | yecril71pl/cpp-docs.pl-pl | 599c99edee44b11ede6956ecf2362be3bf25d2f1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/mfc/reference/cmfcribbonstatusbar-class.md | yecril71pl/cpp-docs.pl-pl | 599c99edee44b11ede6956ecf2362be3bf25d2f1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/mfc/reference/cmfcribbonstatusbar-class.md | yecril71pl/cpp-docs.pl-pl | 599c99edee44b11ede6956ecf2362be3bf25d2f1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Klasa CMFCRibbonStatusBar
ms.date: 11/04/2016
f1_keywords:
- CMFCRibbonStatusBar
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::AddDynamicElement
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::AddElement
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::AddExtendedElement
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::AddSeparator
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::Create
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::CreateEx
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::FindByID
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::FindElement
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::GetCount
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::GetElement
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::GetExCount
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::GetExElement
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::GetExtendedArea
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::GetSpace
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::IsBottomFrame
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::IsExtendedElement
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::IsInformationMode
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::RecalcLayout
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::RemoveAll
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::RemoveElement
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::SetInformation
- AFXRIBBONSTATUSBAR/CMFCRibbonStatusBar::OnDrawInformation
helpviewer_keywords:
- CMFCRibbonStatusBar [MFC], AddDynamicElement
- CMFCRibbonStatusBar [MFC], AddElement
- CMFCRibbonStatusBar [MFC], AddExtendedElement
- CMFCRibbonStatusBar [MFC], AddSeparator
- CMFCRibbonStatusBar [MFC], Create
- CMFCRibbonStatusBar [MFC], CreateEx
- CMFCRibbonStatusBar [MFC], FindByID
- CMFCRibbonStatusBar [MFC], FindElement
- CMFCRibbonStatusBar [MFC], GetCount
- CMFCRibbonStatusBar [MFC], GetElement
- CMFCRibbonStatusBar [MFC], GetExCount
- CMFCRibbonStatusBar [MFC], GetExElement
- CMFCRibbonStatusBar [MFC], GetExtendedArea
- CMFCRibbonStatusBar [MFC], GetSpace
- CMFCRibbonStatusBar [MFC], IsBottomFrame
- CMFCRibbonStatusBar [MFC], IsExtendedElement
- CMFCRibbonStatusBar [MFC], IsInformationMode
- CMFCRibbonStatusBar [MFC], RecalcLayout
- CMFCRibbonStatusBar [MFC], RemoveAll
- CMFCRibbonStatusBar [MFC], RemoveElement
- CMFCRibbonStatusBar [MFC], SetInformation
- CMFCRibbonStatusBar [MFC], OnDrawInformation
ms.assetid: 921eb57f-3b40-49fa-a38c-3f2fb6dc2893
ms.openlocfilehash: 8d90e01db022c33edd654e83af05e9986799f2b9
ms.sourcegitcommit: 7a6116e48c3c11b97371b8ae4ecc23adce1f092d
ms.translationtype: MT
ms.contentlocale: pl-PL
ms.lasthandoff: 04/22/2020
ms.locfileid: "81754058"
---
# <a name="cmfcribbonstatusbar-class"></a>Klasa CMFCRibbonStatusBar
Klasa `CMFCRibbonStatusBar` implementuje formant paska stanu, który może wyświetlać elementy wstążki.
## <a name="syntax"></a>Składnia
```
class CMFCRibbonStatusBar : public CMFCRibbonBar
```
## <a name="members"></a>Elementy członkowskie
### <a name="public-methods"></a>Metody publiczne
|Nazwa|Opis|
|----------|-----------------|
|[CMFCRibbonStatusBar::AddDynamicElement](#adddynamicelement)|Dodaje element dynamiczny do paska stanu wstążki.|
|[CMFCRibbonStatusBar::AddElement](#addelement)|Dodaje nowy element wstążki do paska stanu wstążki.|
|[CMFCRibbonStatusBar::AddExtendedElement](#addextendedelement)|Dodaje element wstążki do rozszerzonego obszaru paska stanu wstążki.|
|[CMFCRibbonStatusBar::AddSeparator](#addseparator)|Dodaje separator do paska stanu wstążki.|
|[CMFCRibbonStatusBar::Tworzenie](#create)|Tworzy pasek stanu wstążki.|
|[CMFCRibbonStatusBar::CreateEx](#createex)|Tworzy pasek stanu wstążki z rozszerzonym stylem.|
|[CMFCRibbonStatusBar::FindByID](#findbyid)||
|[CMFCRibbonStatusBar::FindElement](#findelement)|Zwraca wskaźnik do elementu, który ma określony identyfikator polecenia.|
|[CMFCRibbonStatusBar::GetCount](#getcount)|Zwraca liczbę elementów znajdujących się w głównym obszarze paska stanu wstążki.|
|[CMFCRibbonStatusBar::GetElement](#getelement)|Zwraca wskaźnik do elementu, który znajduje się w określonym indeksie.|
|[CMFCRibbonStatusBar::GetExCount](#getexcount)|Zwraca liczbę elementów, które znajdują się w rozszerzonym obszarze paska stanu wstążki.|
|[CMFCRibbonStatusBar::GetExElement](#getexelement)|Zwraca wskaźnik do elementu, który znajduje się przy określonym indeksie w rozszerzonym obszarze paska stanu wstążki.|
|[CMFCRibbonStatusBar::GetExtendedArea](#getextendedarea)||
|[CMFCRibbonStatusBar::GetSpace](#getspace)||
|[CMFCRibbonStatusBar::IsBottomFrame](#isbottomframe)||
|[CMFCRibbonStatusBar::IsExtendedElement](#isextendedelement)||
|[CMFCRibbonStatusBar::IsInformationMode](#isinformationmode)|Określa, czy tryb informacyjny jest włączony dla paska stanu wstążki.|
|[CMFCRibbonStatusBar::RecalcLayout](#recalclayout)|(Zastępuje [CMFCRibbonBar::RecalcLayout](../../mfc/reference/cmfcribbonbar-class.md#recalclayout).)|
|[CMFCRibbonStatusBar::UsuńWszystki](#removeall)|Usuwa wszystkie elementy z paska stanu wstążki.|
|[CMFCRibbonStatusBar::UsuńElement](#removeelement)|Usuwa element o określonym identyfikatorze polecenia z paska stanu wstążki.|
|[CMFCRibbonStatusBar::SetInformation](#setinformation)|Włącza lub wyłącza tryb informacyjny paska stanu wstążki.|
### <a name="protected-methods"></a>Metody chronione
|Nazwa|Opis|
|----------|-----------------|
|[CMFCRibbonStatusBar::OnDrawInformation](#ondrawinformation)|Wyświetla ciąg informacji wyświetlany na pasku stanu wstążki po włączeniu trybu informacyjnego.|
## <a name="remarks"></a>Uwagi
Użytkownicy mogą zmieniać widoczność elementów wstążki na pasku stanu wstążki za pomocą wbudowanego menu kontekstowego paska stanu wstążki. Elementy można dodawać lub usuwać dynamicznie.
Pasek stanu wstążki ma dwa obszary: główny obszar i obszar rozszerzony. Rozszerzony obszar jest wyświetlany po prawej stronie paska stanu wstążki i jest wyświetlany w innym kolorze niż główny obszar.
Zazwyczaj w głównym obszarze paska stanu są wyświetlane powiadomienia o stanie, a w rozszerzonym obszarze są wyświetlane formanty widoku. Rozszerzony obszar pozostaje widoczny tak długo, jak to możliwe, gdy użytkownik zmieni rozmiar paska stanu wstążki.
## <a name="example"></a>Przykład
W poniższym przykładzie pokazano, jak `CMFCRibbonStatusBar` używać różnych metod w klasie. W przykładzie pokazano, jak dodać nowy element wstążki do paska stanu wstążki, dodać element wstążki do rozszerzonego obszaru paska stanu wstążki, dodać separator i włączyć tryb normalny paska stanu wstążki.
[!code-cpp[NVC_MFC_RibbonApp#15](../../mfc/reference/codesnippet/cpp/cmfcribbonstatusbar-class_1.cpp)]
[!code-cpp[NVC_MFC_RibbonApp#16](../../mfc/reference/codesnippet/cpp/cmfcribbonstatusbar-class_2.cpp)]
## <a name="inheritance-hierarchy"></a>Hierarchia dziedziczenia
[Cobject](../../mfc/reference/cobject-class.md)
[Ccmdtarget](../../mfc/reference/ccmdtarget-class.md)
[Cwnd](../../mfc/reference/cwnd-class.md)
[Panel CBasePane](../../mfc/reference/cbasepane-class.md)
[Cpane](../../mfc/reference/cpane-class.md)
[Cmfcribbonbar](../../mfc/reference/cmfcribbonbar-class.md)
[CMFCRibbonStatusBar](../../mfc/reference/cmfcribbonstatusbar-class.md)
## <a name="requirements"></a>Wymagania
**Nagłówek:** afxribbonstatusbar.h
## <a name="cmfcribbonstatusbaradddynamicelement"></a><a name="adddynamicelement"></a>CMFCRibbonStatusBar::AddDynamicElement
Dodaje element dynamiczny do paska stanu wstążki.
```cpp
void AddDynamicElement(CMFCRibbonBaseElement* pElement);
```
### <a name="parameters"></a>Parametry
*pElement (właśc.*<br/>
[w] Wskaźnik do elementu dynamicznego.
### <a name="remarks"></a>Uwagi
W przeciwieństwie do zwykłych elementów, elementy dynamiczne nie są konfigurowalne, a menu dostosowywania paska stanu nie wyświetla ich.
## <a name="cmfcribbonstatusbaraddelement"></a><a name="addelement"></a>CMFCRibbonStatusBar::AddElement
Dodaje nowy element wstążki do paska stanu wstążki.
```cpp
void AddElement(
CMFCRibbonBaseElement* pElement,
LPCTSTR lpszLabel,
BOOL bIsVisible=TRUE);
```
### <a name="parameters"></a>Parametry
*pElement (właśc.*<br/>
[w] Wskaźnik do dodanego elementu.
*lpszLabel (lpszLabel)*<br/>
[w] Etykieta tekstowa elementu.
*bIsVisible (Widoczne)*<br/>
[w] PRAWDA, jeśli chcesz dodać element jako widoczny, FALSE, jeśli chcesz dodać element jako ukryty.
## <a name="cmfcribbonstatusbaraddextendedelement"></a><a name="addextendedelement"></a>CMFCRibbonStatusBar::AddExtendedElement
Dodaje element wstążki do rozszerzonego obszaru paska stanu wstążki.
```cpp
void AddExtendedElement(
CMFCRibbonBaseElement* pElement,
LPCTSTR lpszLabel,
BOOL bIsVisible=TRUE);
```
### <a name="parameters"></a>Parametry
*pElement (właśc.*<br/>
[w] Wskaźnik do dodanego elementu.
*lpszLabel (lpszLabel)*<br/>
[w] Etykieta tekstowa elementu.
*bIsVisible (Widoczne)*<br/>
[w] PRAWDA, jeśli chcesz dodać element jako widoczny, FALSE, jeśli chcesz dodać element jako ukryty.
### <a name="remarks"></a>Uwagi
Rozszerzony obszar znajduje się po prawej stronie kontrolki paska stanu.
## <a name="cmfcribbonstatusbaraddseparator"></a><a name="addseparator"></a>CMFCRibbonStatusBar::AddSeparator
Dodaje separator do paska stanu wstążki.
```cpp
void AddSeparator();
```
### <a name="remarks"></a>Uwagi
Struktura dodaje separator po metodzie [CMFCRibbonStatusBar::AddElement](#addelement). wstawia ostatni element.
## <a name="cmfcribbonstatusbarcreate"></a><a name="create"></a>CMFCRibbonStatusBar::Tworzenie
Tworzy pasek stanu wstążki.
```
BOOL Create(
CWnd* pParentWnd,
DWORD dwStyle=WS_CHILD|WS_VISIBLE|CBRS_BOTTOM,
UINT nID=AFX_IDW_STATUS_BAR);
```
### <a name="parameters"></a>Parametry
*pParentWnd*<br/>
[w] Wskaźnik do okna nadrzędnego.
*Dwstyle*<br/>
[w] Logiczna kombinacja stylów sterowania lub.
*Nid*<br/>
[w] Identyfikator formantu paska stanu.
### <a name="return-value"></a>Wartość zwracana
PRAWDA, jeśli pasek stanu został utworzony pomyślnie, w przeciwnym razie WARTOŚĆ FAŁSZUj.
## <a name="cmfcribbonstatusbarcreateex"></a><a name="createex"></a>CMFCRibbonStatusBar::CreateEx
Tworzy pasek stanu wstążki o rozszerzonym stylu.
```
BOOL CreateEx(
CWnd* pParentWnd,
DWORD dwCtrlStyle=0,
DWORD dwStyle=WS_CHILD|WS_VISIBLE|CBRS_BOTTOM,
UINT nID=AFX_IDW_STATUS_BAR);
```
### <a name="parameters"></a>Parametry
*pParentWnd*<br/>
Wskaźnik do okna nadrzędnego.
*dwCtrlStyle*<br/>
Logiczna kombinacja lub dodatkowych stylów do tworzenia obiektu paska stanu.
*Dwstyle*<br/>
Styl sterowania paska stanu.
*Nid*<br/>
Identyfikator formantu paska stanu.
### <a name="return-value"></a>Wartość zwracana
PRAWDA, jeśli pasek stanu został utworzony pomyślnie, w przeciwnym razie WARTOŚĆ FAŁSZUj.
## <a name="cmfcribbonstatusbarfindbyid"></a><a name="findbyid"></a>CMFCRibbonStatusBar::FindByID
Aby uzyskać więcej informacji, zobacz kod źródłowy znajdujący się w folderze **vc\\\\atlmfc src\\mfc** instalacji programu Visual Studio.
```
CMFCRibbonBaseElement* FindByID(UINT uiCmdID, BOOL = TRUE);
```
### <a name="parameters"></a>Parametry
[w] *identyfikator uiCmdID*<br/>
[w] *BOOL (BOOL)*<br/>
### <a name="return-value"></a>Wartość zwracana
### <a name="remarks"></a>Uwagi
## <a name="cmfcribbonstatusbarfindelement"></a><a name="findelement"></a>CMFCRibbonStatusBar::FindElement
Zwraca wskaźnik do elementu, który ma określony identyfikator polecenia.
```
CMFCRibbonBaseElement* FindElement(UINT uiID);
```
### <a name="parameters"></a>Parametry
*Uiid*<br/>
[w] Identyfikator elementu.
### <a name="return-value"></a>Wartość zwracana
Wskaźnik do elementu, który ma określony identyfikator polecenia. NULL, jeśli nie ma takiego elementu.
## <a name="cmfcribbonstatusbargetcount"></a><a name="getcount"></a>CMFCRibbonStatusBar::GetCount
Zwraca liczbę elementów znajdujących się w głównym obszarze paska stanu wstążki.
```
int GetCount() const;
```
### <a name="return-value"></a>Wartość zwracana
Liczba elementów znajdujących się w głównym obszarze paska stanu wstążki.
## <a name="cmfcribbonstatusbargetelement"></a><a name="getelement"></a>CMFCRibbonStatusBar::GetElement
Zwraca wskaźnik do elementu, który znajduje się w określonym indeksie.
```
CMFCRibbonBaseElement* GetElement(int nIndex);
```
### <a name="parameters"></a>Parametry
*Nindex*<br/>
[w] Określa indeks od zera elementu, który znajduje się w głównym obszarze formantu paska stanu.
### <a name="return-value"></a>Wartość zwracana
Wskaźnik do elementu, który znajduje się w określonym indeksie. NULL, jeśli indeks jest ujemny lub przekracza liczbę elementów na pasku stanu.
### <a name="remarks"></a>Uwagi
## <a name="cmfcribbonstatusbargetexcount"></a><a name="getexcount"></a>CMFCRibbonStatusBar::GetExCount
Zwraca liczbę elementów, które znajdują się w rozszerzonym obszarze paska stanu wstążki.
```
int GetExCount() const;
```
### <a name="return-value"></a>Wartość zwracana
Liczba elementów znajdujących się w rozszerzonym obszarze paska stanu wstążki.
## <a name="cmfcribbonstatusbargetexelement"></a><a name="getexelement"></a>CMFCRibbonStatusBar::GetExElement
Zwraca wskaźnik do elementu, który znajduje się przy określonym indeksie w rozszerzonym obszarze paska stanu wstążki. Rozszerzony obszar znajduje się po prawej stronie kontrolki paska stanu.
```
CMFCRibbonBaseElement* GetExElement(int nIndex);
```
### <a name="parameters"></a>Parametry
*Nindex*<br/>
[w] Określa indeks od zera elementu, który znajduje się w rozszerzonym obszarze formantu paska stanu.
### <a name="return-value"></a>Wartość zwracana
Wskaźnik do elementu, który znajduje się przy określonym indeksie w rozszerzonym obszarze paska stanu wstążki. NULL, jeśli *nIndex* jest ujemny lub przekracza liczbę elementów w rozszerzonym obszarze paska stanu wstążki.
### <a name="remarks"></a>Uwagi
## <a name="cmfcribbonstatusbargetextendedarea"></a><a name="getextendedarea"></a>CMFCRibbonStatusBar::GetExtendedArea
Aby uzyskać więcej informacji, zobacz kod źródłowy znajdujący się w folderze **vc\\\\atlmfc src\\mfc** instalacji programu Visual Studio.
```
virtual BOOL GetExtendedArea(CRect& rect) const;
```
### <a name="parameters"></a>Parametry
[w] *rect*<br/>
### <a name="return-value"></a>Wartość zwracana
### <a name="remarks"></a>Uwagi
## <a name="cmfcribbonstatusbargetspace"></a><a name="getspace"></a>CMFCRibbonStatusBar::GetSpace
Aby uzyskać więcej informacji, zobacz kod źródłowy znajdujący się w folderze **vc\\\\atlmfc src\\mfc** instalacji programu Visual Studio.
```
int GetSpace() const;
```
### <a name="return-value"></a>Wartość zwracana
### <a name="remarks"></a>Uwagi
## <a name="cmfcribbonstatusbarisbottomframe"></a><a name="isbottomframe"></a>CMFCRibbonStatusBar::IsBottomFrame
Aby uzyskać więcej informacji, zobacz kod źródłowy znajdujący się w folderze **vc\\\\atlmfc src\\mfc** instalacji programu Visual Studio.
```
BOOL IsBottomFrame() const;
```
### <a name="return-value"></a>Wartość zwracana
### <a name="remarks"></a>Uwagi
## <a name="cmfcribbonstatusbarisextendedelement"></a><a name="isextendedelement"></a>CMFCRibbonStatusBar::IsExtendedElement
Aby uzyskać więcej informacji, zobacz kod źródłowy znajdujący się w folderze **vc\\\\atlmfc src\\mfc** instalacji programu Visual Studio.
```
BOOL IsExtendedElement(CMFCRibbonBaseElement* pElement) const;
```
### <a name="parameters"></a>Parametry
[w] *pElement (właśc.*<br/>
### <a name="return-value"></a>Wartość zwracana
### <a name="remarks"></a>Uwagi
## <a name="cmfcribbonstatusbarisinformationmode"></a><a name="isinformationmode"></a>CMFCRibbonStatusBar::IsInformationMode
Określa, czy tryb informacyjny jest włączony dla paska stanu wstążki.
```
BOOL IsInformationMode() const;
```
### <a name="return-value"></a>Wartość zwracana
PRAWDA, jeśli pasek stanu może działać w trybie informacyjnym; w przeciwnym razie FALSE.
### <a name="remarks"></a>Uwagi
W trybie informacyjnym pasek stanu ukrywa wszystkie zwykłe okienka i wyświetla ciąg komunikatu.
## <a name="cmfcribbonstatusbarondrawinformation"></a><a name="ondrawinformation"></a>CMFCRibbonStatusBar::OnDrawInformation
Wyświetla ciąg wyświetlany na pasku stanu wstążki, gdy włączony jest tryb informacyjny.
```
virtual void OnDrawInformation(
CDC* pDC,
CString& strInfo,
CRect rectInfo);
```
### <a name="parameters"></a>Parametry
*Pdc*<br/>
[w] Wskaźnik do kontekstu urządzenia.
*strInfo (strInfo)*<br/>
[w] Ciąg informacyjny.
*rectInfo*<br/>
[w] Prostokąt ograniczający.
### <a name="remarks"></a>Uwagi
Zastąpi tę metodę w klasie pochodnej, jeśli chcesz dostosować wygląd ciągu informacji na pasku stanu. Użyj [CMFCRibbonStatusBar::SetInformation](#setinformation) metody umieścić pasek stanu w trybie informacyjnym. W tym trybie pasek stanu ukrywa wszystkie okienka i wyświetla ciąg informacji określony przez *strInfo*.
## <a name="cmfcribbonstatusbarrecalclayout"></a><a name="recalclayout"></a>CMFCRibbonStatusBar::RecalcLayout
Aby uzyskać więcej informacji, zobacz kod źródłowy znajdujący się w folderze **vc\\\\atlmfc src\\mfc** instalacji programu Visual Studio.
```
virtual void RecalcLayout();
```
### <a name="remarks"></a>Uwagi
## <a name="cmfcribbonstatusbarremoveall"></a><a name="removeall"></a>CMFCRibbonStatusBar::UsuńWszystki
Usuwa wszystkie elementy z paska stanu wstążki.
```cpp
void RemoveAll();
```
## <a name="cmfcribbonstatusbarremoveelement"></a><a name="removeelement"></a>CMFCRibbonStatusBar::UsuńElement
Usuwa element o określonym identyfikatorze polecenia z paska stanu wstążki.
```
BOOL RemoveElement(UINT uiID);
```
### <a name="parameters"></a>Parametry
*Uiid*<br/>
[w] Identyfikator elementu do usunięcia z paska stanu.
### <a name="return-value"></a>Wartość zwracana
PRAWDA, jeśli element o określonym *identyfikatorze użytkownika* zostanie usunięty. FAŁSZ inaczej.
## <a name="cmfcribbonstatusbarsetinformation"></a><a name="setinformation"></a>CMFCRibbonStatusBar::SetInformation
Włącza lub wyłącza tryb informacyjny paska stanu wstążki.
```cpp
void SetInformation(LPCTSTR lpszInfo);
```
### <a name="parameters"></a>Parametry
*lpszInfo*<br/>
[w] Ciąg informacyjny.
### <a name="remarks"></a>Uwagi
Ta metoda służy do umieszczania paska stanu w trybie informacyjnym. W tym trybie pasek stanu ukrywa wszystkie okienka i wyświetla ciąg informacji określony przez *lpszInfo*.
Gdy lpszInfo jest NULL, pasek stanu powraca do trybu regularnego.
## <a name="see-also"></a>Zobacz też
[Wykres hierarchii](../../mfc/hierarchy-chart.md)<br/>
[Klasy](../../mfc/reference/mfc-classes.md)<br/>
[Klasa CMFCRibbonBar](../../mfc/reference/cmfcribbonbar-class.md)<br/>
[Klasa CMFCRibbonBaseElement](../../mfc/reference/cmfcribbonbaseelement-class.md)<br/>
[Klasa CMFCRibbonBar](../../mfc/reference/cmfcribbonbar-class.md)
| 35.44592 | 318 | 0.771413 | pol_Latn | 0.96791 |
08cdd5f827ba87afb406aeafe8cf57eab7ba22b8 | 6,464 | md | Markdown | _posts/2009-12-29-nmake-guide-6.md | lengerrong/lengerrong.github.io | d11ccebbf084617dfd4060bf7a8a7c911462533a | [
"MIT"
] | null | null | null | _posts/2009-12-29-nmake-guide-6.md | lengerrong/lengerrong.github.io | d11ccebbf084617dfd4060bf7a8a7c911462533a | [
"MIT"
] | null | null | null | _posts/2009-12-29-nmake-guide-6.md | lengerrong/lengerrong.github.io | d11ccebbf084617dfd4060bf7a8a7c911462533a | [
"MIT"
] | null | null | null | ---
layout: post
title: NMAKE Guide (六)
tags: NMAKE
categories: build
---
推导规则
推导规则是种模板，该模板定义了如何由一种后缀文件生成另一种后缀文件。
NMAKE使用推导规则为更新目标提供命令和为目标推导规则。
在依赖树中，推导规则为目标提供推导的依赖项就像在依赖行中显示指定的依赖一样，请查阅569页的"推导依赖项“一节。
.SUFFIXES名单决定了推导规则应用时的优先级，请查看570页的”点指令“一节。
推导规则提为常用操作提供了一种便捷的方式。
举个例子，可以用推导规则来避免在多个描述块中重复写同样的命令。
您也可以定义自己的推导规则或是使用预定义的推导规则。
推导规则可以在makefile文件中或是TOOLS.INI文件中指定。
推导规则可以用在以下的场景中：
如果NMAKE遇到没有命令的描述块，NMAKE将检查.SUFFIXES名单和当前或是指定目录下的文件，
然后搜索一条和目标文件后缀匹配的推导规则和在.SUFFIXES名单中有最高优先级的已经存在的依赖项文件。
如果一个依赖文件不存在但并没有作为目标文件列在其他描述块中，NMAKE寻找一条演示了如何由另一个同名的文件创建缺失的依赖项的推导规则。
如果一个目标没有依赖项且它的描述块并没有命令，NMAKE可以使用一条推导规则来创建目标。
如果一个在命令行参数列表中列出的目标且没有指定makefile文件（或是在makefile文件中没有提及该目标文件），
NMAKE将使用推导规则来创建目标文件。
如果一个目标在多个单分号的依赖关系中使用，推导规则或许并不如预期的一样适用，详情请参阅539页的”依赖关系中目标的积累“一节。
推导规则语法
使用如下的语法来定义一条推导规则：
.fromext.toext:
commands
第一行列出两个后缀：fromext代表了依赖文件的后缀；toext代表了目标文件的后缀。
后缀并不区分大小写。可以调用宏来代表fromext和toext，宏在处理时展开。
fromext前的.号必须出现在行的开始位置。冒号前可以放置一个或多个空格或是制表符，它后面只能有空格或是制表符。
；分号指定一条命令，#描述了一条注释或是换行符。不允许有其他的空格。
推导规则只能在目标和依赖有着相同的文件名时适用。
一条推导规则不可能适应多种目标或是依赖文件。
举个例子，您不能定义一个推导规则来替代一个库文件中的多个模块，因为从一个目标库在出来的所有模块必须有且不同的文件名。
推导规则只适用于拥有在.SUFFIXES名单中后缀的依赖文件。
（更多信息关于.SUFFIXES，请查看570页的”点指令“一节。）
如果一个过时的依赖并没有命令块，如果同时在.SUFFIXES名单中包含有该依赖项的后缀，
那么NMAKE寻找一条和目标后缀匹配的推导规则和当前或指定的目录中存在的文件来生成目标。
如果多个推导规则和存在的依赖文件匹配，NMAKE使用.SUFFIXES名单中后缀的顺序来决定使用那条推导规则。
名单中的先后顺序由左到右。NMAKE也许会调用一条推导规则即使有显示地的指定依赖项，更多的信息请参阅569页的”推导规则"一节。
推导规则告知NMAKE如何去生成在命令参数行中指定的目标，如果没有提供makefile文件或是在makefile文件中并没有关于指定目标的依赖关系。
如果NMAKE不知道如何去生成命令中指定的目标，NMAKE会找寻一条推导规则来生成它。
如果您在预定义的推导规则和在TOOLS.INI定义的推导规则足够满足您的目标生成需要，那么您可以运行NMAKE程序而无须指定makefile文件。
推导规则搜索路径
先前描述的推导规则定义语法告诉NMAKE在当前目录寻找指定的文件来生成目标。
当然您也可以告知NMAKE搜索目录。指定搜索路径的推导规则的语法如下 ：
{frompath}.fromext{topath}.toext:
commands
中间不允许有空格。frompath目录必须和指定的依赖文件的目录匹配；同样的，topath目录必须和目标文件目录匹配。
为让NMAKE为一依赖关系应用一条推导规则，在依赖行中指定的目录必须和推导规则中指定的目录精确的一致。
举个例子，如果当前目录为PROJ，那么推导规则
{../proj}.exe{../proj}.obj:
并不应用于下面的依赖关系
project1.exe : project1.obj
如果您在推导规则中为一个后缀使用了目录，您必须为所有的后缀都使用目录。
您可以用.或是一对空的大括号来表示当前目录。
您在推导规则中只能为每种后缀指定一条路径。
如果需要指定多个路径，您必须为每个路径实现独立的推导规则。
宏调用可以用来代表frompath和path，宏在处理里展开。
用户自定义推导规则
下面的例子演示了写推导规则的几种方式：
例子1
下面的makefile文件包含了一条推导规则和一个最小的描述块：
.c.obj:
cl /c $<
sample.obj
推导规则告诉NMAKE如果由a.c文件来生成a.obj文件。
预定义宏$<代表比目标文件有更新时间戳的依赖文件。
描述块只列出了目标SAMPLE.OBJ文件，但并没有依赖项或是命令。
但是，根据目标文件名和后缀再加上推导规则，NMAKE有足够的信息来生成目标。
在检查到.c后缀有列在.SUFFIXES名单中，NMAKE寻找一个与目标同名的以.c为后缀的文件来生成目标。
如果SAMPLE.C文件存在（没有更高的优先级的后缀的同名文件的存在），NMAKE比较该文件和sample.obj文件的时间戳的先后。
如果SAMPLE.C文件有新的修改，NMAKE编译sample.c通过列在推导规则中的CL命令来生成sample.obj文件：cl /c sample.c
例子2
下面的推导规则当前目录下的.c文件和在其他目录下的对应的.obj文件：
{.}.c{c:/objects}.obj:
cl /c $<;
为.c文件指定的路径是.，代表着当前目录。
依赖文件的后缀也必须指定搜索路径，因为目标的后缀指定了搜索路径。
这条推导规则适用于包含同样的路径的依赖关系，就像下面的：
c:/objects/test.obj : test.c
那条规则没不适用于下面的依赖关系:
test.obj : test.c
例子3
下面的推导规则调用宏来指定推导规则中的路径：
C_DIR = proj1src
OBJ_DIR = proj1obj
{$(C_DIR)}.c{$(OBJ_DIR)}.obj:
cl /c $
如果宏重新定义了，NMAKE使用在处理时有效的那个定义。
要重用一条推导规则用另一个宏定义，您必须重复推导规则使用新的定义：
C_DIR = proj1src
OBJ_DIR = proj1obj
{$(C_DIR)}.c{$(OBJ_DIR)}.obj:
cl /c $<
C_DIR = proj2src
OBJ_DIR = proj2obj
{$(C_DIR)}.c{$(OBJ_DIR)}.obj:
cl /c $<
预定义推导规则
NMAKE提供了预定义推导规则包含命令来创建对象、可执行文件和资源文件。
表16.1描述了预定义推导规则：
Table 16.1 Predefined Inference Rules
------------------------------------------------------------
Rule Command Default Action
------------------------------------------------------------
.asm.exe $(AS)$(AFLAGS)$*.asm ML $*.ASM
.asm.obj $(AS)$(AFLAGS)/c $*.asm ML /c $*.ASM
.c.exe $(CC)$(CFLAGS)$*.c CL $*.C
.c.obj $(CC)$(CFLAGS)/c$*.c CL /c $*.C
.cpp.exe $(CPP)$(CPPFLAGS)$*.cpp CL $*.CPP
.cpp.obj $(CPP)$(CPPFLAGS)/c$*.cpp CL /c $*.CPP
.cxx.exe $(CXX)$(CXXFLAGS)$*.cxx CL $*.CXX
.cxx.obj $(CXX)$(CXXFLAGS)/c$*.cxx CL /c $*.CXX
.bas.obj $(BC)$(BFLAGS)$*.bas; BC $*.BAS;
.cbl.exe $(COBOL)$(COBFLAGS)$*.cbl,$*.exe; COBOL $*.CBL,$*.EXE;
.cbl.obj $(COBOL)$(COBFLAGS)$*.cbl; COBOL $*.CBL;
.for.exe $(FOR)$(FFLAGS)$*.for FL $*.FOR
.for.obj $(FOR)/c$(FFLAGS)$*.for FL /c $*.FOR
.pas.exe $(PASCAL)$(PFLAGS)$*.pas PL $*.PAS
.pas.obj $(PASCAL)/c$(PFLAGS) $*.pas PL /c $*.PAS
.rc.res $(RC)$(RFLAGS)/r$* RC /r $*
------------------------------------------------------------------------
举个例子，假设您有下面的makefile文件：
sample.exe :
上面的描述块列出了一个目标但并没有依赖项和命令。
NMAKE查看目标文件的后缀（.exe）然后搜索一条描述如何生成一个.exe文件推导规则。
由表16.1中可以看出，有多条推导规则可以生成.exe文件。
NMAKE根据在.SUFFIXES名单中的后缀名顺序来决定使用那条推导规则来生成目标文件。
然后NMAKE在当前目录或是指定目录在搜索与目标同名的且具有.SUFFIXES名单中的后缀名的文件，
它依个检查.SUFFIXEX名单中后缀名直到在目录中找到一个匹配的依赖文件。
举个例子，如果一个名为sample.asm的文件存在，NMAKE使用.asm.exe推导规则。
如果sample.c和sample.asm同时存在，如果在.SUFFIXES名单中.c后缀出现在.asm前，
那么NMAKE使用.c.exe推导规则来编译SAMPLE.C然后链接生成文件sample.obj文件来生成SAMPLE.EXE。
-----------------------------------------------------------------------------------------------------------
注意：默认情况下，选项宏（AFLAGS,CFLAGS，等等）是没有定义的。
按照在554页中“宏的使用”一节中的解释，这并不会引起任何问题。
NMAKE使用空串来替换一个未定义的宏。
由于这些预定义宏有在推导规则中使用，您可以重定义这些宏然后将给其分配的值自动传递到这些预定义的推导规则中。
-----------------------------------------------------------------------------------------------------------
推导的依赖项
NMAKE可以为目标假想一些推导的依赖项如果存在一条适当的推导规则。
一条适当的推导规则符合如下条件：
推导规则中toext后缀名和检测的目标文件的后缀一致。
推导规则中fromext后缀名和当前或是指定目录下的一个与目标文件同名的文件的后缀名一样。
fromext后缀名有列出在.SUFFIXES名单中。
在匹配的推导规则中没有其他的fromext后缀名列出在.SUFFIXES名单中具有更高的优先级。
没有显示地指定更高优先级后缀的依赖项。
如果一个存在的依赖项和一个推导规则匹配并且有一个后缀名拥有更高的.SUFFIXES优先级，
那么NMAKE并不推导出一个依赖。
NMAKE并不需要执行推导规则中的命令块为一个推导的依赖项。
如果一个目标的描述块中包含有命令，NMAKE执行描述块中的命令而不是匹配的推导规则的命令块。
下面的例子演示了推导的依赖项的作用:
project.obj :
cl /Zi /c project.c
如果一个makefile文件包含上面的描述块，并且当前目录中包含一个名为PROJECT.C的文件，没有其他的文件，
那么NMAKE使用预定义推导规则.c.obj推导出依赖项project.c。
NMAKE并不执行预定义推导规则中的命令，而是执行在makefile文件中指定的命令：cl /c project.c。
推导的依赖项可能会引起预料之外的影响。
在下面的例子中，假设PROJECT.ASM和PROJECT.C同时存在同时.SUFFIXES包含默认的设置。
如果makefile包含下面的描述块：
project.obj : project.c
NMAKE推导的依赖项project.asm优先于project.c，因为在.SUFFIXES中.asm中.c之前且存在.asm.obj的推导规则。
如果project.asm或是project.c过期了，NMAKE将执行推导规则.asm.obj中命令。
但是，之前例子中的依赖关系中添加命令块，NMAKE执行命令块中的命令，而不是提供推导的依赖项的推导规则中的命令。
另一副作用产生了，因为NMAKE生成目标如果任一一个依赖文件过期了，不管是显示指定的还是推导的依赖项。
举个例子，如果PROJECT.OBJ相对于PROJECT.C文件是最新的，但是对于PROJECT.ASM却是过期的 ，如果makefile包含：
project.obj : project.c
cl /Zi /c project.c
NMAKE推导出依赖项为PROJECT.ASM，于是乎使用描述块的指定的命令来更新目标文件。
推导规则的优先级
如果同一个推导规则在多处定义，NMAKE使用具有最高优先级的推导规则。
优先级从高到低如下：
1.makefile文件中定义的推导的规则。如果定义了多个，那么应用最后的那一个。
2.在TOOLS.INI文件中定义的推导规则。如果定义了多个，那么应用最后一个。
3.预定义的推导规则。
用户自定义了推导规则总是会覆盖预定义的推导规则。
NMAKE使用预定义推导规则如果对于给定的目标和依赖并没有存在用户自定义的推导规则。
如果两个推导规则匹配一个目标文件的后缀且没有指定依赖，NMAKE使用推导规则中的那个依赖项的后缀出现在.SUFFIXES名单中较前的那个。 | 25.752988 | 107 | 0.747525 | yue_Hant | 0.62139 |
08ce9659795688cf3855169991633cda8b48aa14 | 1,348 | md | Markdown | cross/LZ 008 0.06k.md | farmer-lu/GoAIRatings | b395122a0530691bdb566886a2e9e39d45765e03 | [
"MIT"
] | null | null | null | cross/LZ 008 0.06k.md | farmer-lu/GoAIRatings | b395122a0530691bdb566886a2e9e39d45765e03 | [
"MIT"
] | null | null | null | cross/LZ 008 0.06k.md | farmer-lu/GoAIRatings | b395122a0530691bdb566886a2e9e39d45765e03 | [
"MIT"
] | null | null | null | ## LZ 008 0.06k ##
ELO: -1799
Opponent | Rank | ELO | Black | White | Total | Win rate
---------|-----:|----:|-------|-------|-------|-------:
[LZ 010 0.06k](LZ%20010%200.06k.md) | 15k | -1164 | - | 0 / 2 | 0 / 2 | 0.0%
[LZ 008 0.2k](LZ%20008%200.2k.md) | 16k | -1316 | 0 / 3 | 0 / 4 | 0 / 7 | 0.0%
[LZ 009 0.1k](LZ%20009%200.1k.md) | 16k | -1357 | 2 / 4 | 0 / 7 | 2 / 11 | 18.2%
[LZ 009 0.06k](LZ%20009%200.06k.md) | 17k | -1560 | 18 / 41 | 5 / 67 | 23 / 108 | 21.3%
[LZ 008 0.1k](LZ%20008%200.1k.md) | 18k | -1603 | 23 / 51 | 2 / 68 | 25 / 119 | 21.0%
[LZ 009 0.04k](LZ%20009%200.04k.md) | 18k | -1678 | 47 / 67 | 13 / 102 | 60 / 169 | 35.5%
[LZ 006 0.2k](LZ%20006%200.2k.md) | 19k | -1903 | 49 / 86 | 43 / 62 | 92 / 148 | 62.2%
[LZ 008 0.04k](LZ%20008%200.04k.md) | 19k | -1931 | 61 / 73 | 30 / 52 | 91 / 125 | 72.8%
[LZ 007 0.2k](LZ%20007%200.2k.md) | 20k | -2053 | 44 / 59 | 27 / 33 | 71 / 92 | 77.2%
[LZ 008 0.02k](LZ%20008%200.02k.md) | 20k | -2140 | 36 / 38 | 9 / 12 | 45 / 50 | 90.0%
[LZ 006 0.1k](LZ%20006%200.1k.md) | 20k | -2147 | 29 / 35 | 10 / 11 | 39 / 46 | 84.8%
[LZ 006 0.06k](LZ%20006%200.06k.md) | 21k | -2321 | - | 1 / 1 | 1 / 1 | 100.0%
[LZ 008 0.01k](LZ%20008%200.01k.md) | 21k | -2327 | 4 / 4 | - | 4 / 4 | 100.0%
Total | | | 313 / 594 | 140 / 288 | 453 / 882 |
Win rate| | | 52.7% | 48.6% | 51.4% |
| 61.272727 | 90 | 0.479228 | yue_Hant | 0.082481 |
08ced17c920c8d04d1c87b04e3319b8cba6f2840 | 6,972 | md | Markdown | docs/debugger/debug-interface-access/interfaces-debug-interface-access-sdk.md | jcarmon4/visualstudio-docs.es-es | 2f133c9f0a90eb92429dcca0573a0b3f458cdcf3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/debugger/debug-interface-access/interfaces-debug-interface-access-sdk.md | jcarmon4/visualstudio-docs.es-es | 2f133c9f0a90eb92429dcca0573a0b3f458cdcf3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/debugger/debug-interface-access/interfaces-debug-interface-access-sdk.md | jcarmon4/visualstudio-docs.es-es | 2f133c9f0a90eb92429dcca0573a0b3f458cdcf3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Interfaces (Debug Interface Access SDK) | Microsoft Docs
ms.date: 11/04/2016
ms.topic: conceptual
dev_langs:
- C++
helpviewer_keywords:
- interfaces [DIA SDK]
- DIA SDK, interfaces
ms.assetid: 62aee7c3-d314-4272-a32b-b2818f32fab8
author: mikejo5000
ms.author: mikejo
manager: jillfra
ms.workload:
- multiple
ms.openlocfilehash: 7f60f4b9018f5b2fff9a5426c28dba40177d9ae9
ms.sourcegitcommit: 94b3a052fb1229c7e7f8804b09c1d403385c7630
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 04/23/2019
ms.locfileid: "62840696"
---
# <a name="interfaces-debug-interface-access-sdk"></a>Interfaces (Debug Interface Access SDK)
Los métodos están enumerados alfabéticamente en cada interfaz en la tabla de contenido y en la página de interfaz en el orden de Vtable.
## <a name="in-this-section"></a>En esta sección
[IDiaAddressMap](../../debugger/debug-interface-access/idiaaddressmap.md)
Proporciona control sobre cómo el SDK de DIA calcula direcciones virtuales relativas y virtuales para los objetos de depuración.
[IDiaDataSource](../../debugger/debug-interface-access/idiadatasource.md)
Inicia el acceso a un origen de símbolos de depuración.
[IDiaEnumDebugStreamData](../../debugger/debug-interface-access/idiaenumdebugstreamdata.md)
Proporciona acceso a los registros en un flujo de datos de depuración.
[IDiaEnumDebugStreams](../../debugger/debug-interface-access/idiaenumdebugstreams.md)
Enumera los distintos flujos de depuración contenidos en el origen de datos.
[IDiaEnumFrameData](../../debugger/debug-interface-access/idiaenumframedata.md)
Enumera los distintos elementos de datos del marco contenidos en el origen de datos.
[IDiaEnumInjectedSources](../../debugger/debug-interface-access/idiaenuminjectedsources.md)
Enumerar los distintos orígenes insertados contenidos en el origen de datos.
[IDiaEnumLineNumbers](../../debugger/debug-interface-access/idiaenumlinenumbers.md)
Enumera los distintos números de línea incluidos en el origen de datos.
[IDiaEnumSectionContribs](../../debugger/debug-interface-access/idiaenumsectioncontribs.md)
Enumera las distintas contribuciones de sección contenidas en el origen de datos.
[IDiaEnumSegments](../../debugger/debug-interface-access/idiaenumsegments.md)
Enumera los distintos segmentos contenidos en el origen de datos.
[IDiaEnumSourceFiles](../../debugger/debug-interface-access/idiaenumsourcefiles.md)
Enumera los distintos archivos de origen contenidos en el origen de datos.
[IDiaEnumStackFrames](../../debugger/debug-interface-access/idiaenumstackframes.md)
Enumera los distintos marcos de pila disponible.
[IDiaEnumSymbols](../../debugger/debug-interface-access/idiaenumsymbols.md)
Enumera los símbolos distintos contenidos en el origen de datos.
[IDiaEnumSymbolsByAddr](../../debugger/debug-interface-access/idiaenumsymbolsbyaddr.md)
Enumera por dirección de los símbolos distintos contenidos en el origen de datos.
[IDiaEnumTables](../../debugger/debug-interface-access/idiaenumtables.md)
Enumera las distintas tablas contenidas en el origen de datos.
[IDiaFrameData](../../debugger/debug-interface-access/idiaframedata.md)
Expone los detalles de un marco de pila.
[IDiaImageData](../../debugger/debug-interface-access/idiaimagedata.md)
Expone los detalles de los desplazamientos de memoria y la ubicación bases del módulo o la imagen.
[IDiaInjectedSource](../../debugger/debug-interface-access/idiainjectedsource.md)
Accesos el código fuente del programa se almacena en el origen de datos DIA.
[IDiaLineNumber](../../debugger/debug-interface-access/idialinenumber.md)
Accede a información que describe el proceso de asignación de un bloque de bytes de texto de la imagen a un número de línea del archivo de origen.
[IDiaLoadCallback](../../debugger/debug-interface-access/idialoadcallback.md)
Recibe las devoluciones de llamada desde el símbolo DIA localizar el procedimiento, lo que permite una interfaz de usuario informar sobre el progreso del intento de ubicación.
[IDiaLoadCallback2](../../debugger/debug-interface-access/idialoadcallback2.md)
Recibe las devoluciones de llamada desde el símbolo DIA localizar procedimiento, lo que permite a las restricciones a imponerse en el proceso de localización.
[IDiaPropertyStorage](../../debugger/debug-interface-access/idiapropertystorage.md)
Permite leer las propiedades de un conjunto de propiedades DIA persistentes.
[IDiaReadExeAtRVACallback](../../debugger/debug-interface-access/idiareadexeatrvacallback.md)
Permite que una aplicación cliente proporcionar los bytes de un archivo ejecutable como especificado por la posición del archivo.
[IDiaReadExeAtOffsetCallback](../../debugger/debug-interface-access/idiareadexeatoffsetcallback.md)
Permite que una aplicación cliente proporcionar los bytes de un archivo ejecutable especificado por una dirección virtual relativa.
[IDiaSectionContrib](../../debugger/debug-interface-access/idiasectioncontrib.md)
Recupera los datos que describe una contribución de sección, es decir, un bloque de memoria contiguo contribuciones a la imagen de una operación de compilación.
[IDiaSegment](../../debugger/debug-interface-access/idiasegment.md)
Asigna datos de la sección número a segmentos del espacio de direcciones.
[IDiaSession](../../debugger/debug-interface-access/idiasession.md)
Proporciona un contexto de consulta para símbolos de depuración.
[IDiaSourceFile](../../debugger/debug-interface-access/idiasourcefile.md)
Representa un archivo de origen.
[IDiaStackFrame](../../debugger/debug-interface-access/idiastackframe.md)
Expone las propiedades de un marco de pila.
[IDiaStackWalker](../../debugger/debug-interface-access/idiastackwalker.md)
Proporciona métodos para hacer una pila del recorrido con el archivo PDB.
[IDiaStackWalkFrame](../../debugger/debug-interface-access/idiastackwalkframe.md)
Mantiene el contexto de la pila entre las invocaciones de la [Idiaframedata](../../debugger/debug-interface-access/idiaframedata-execute.md) método.
[IDiaStackWalkHelper](../../debugger/debug-interface-access/idiastackwalkhelper.md)
Facilita el recorrido de la pila mediante el archivo de base de datos (PDB) de depuración de programa.
[IDiaSymbol](../../debugger/debug-interface-access/idiasymbol.md)
Describe las propiedades de una instancia de símbolo.
[IDiaTable](../../debugger/debug-interface-access/idiatable.md)
Enumera una tabla de origen de datos DIA.
## <a name="related-sections"></a>Secciones relacionadas
[Enumeraciones y estructuras](../../debugger/debug-interface-access/enumerations-and-structures.md)
Describe las enumeraciones y estructuras utilizadas por las diversas interfaces de DIA (SDK).
[Constantes (Debug Interface Access SDK)](../../debugger/debug-interface-access/constants-debug-interface-access-sdk.md)
Describe las constantes disponibles en el SDK de DIA.
## <a name="see-also"></a>Vea también
- [Referencia](../../debugger/debug-interface-access/debug-interface-access-sdk-reference.md) | 40.77193 | 175 | 0.799627 | spa_Latn | 0.883892 |
08cfabf8adc16466aea099cd5fd294b83da716b4 | 390 | md | Markdown | it/python/arithmeticOperators/14.md | nank1ro/Codigo-Questions | 559cf998c8b5fbf7a9aee2db08fe57c8abc63408 | [
"BSD-3-Clause"
] | 5 | 2021-08-30T05:36:45.000Z | 2022-03-18T16:25:39.000Z | it/python/arithmeticOperators/14.md | nank1ro/Codigo-Questions | 559cf998c8b5fbf7a9aee2db08fe57c8abc63408 | [
"BSD-3-Clause"
] | 33 | 2021-10-04T12:52:45.000Z | 2022-03-07T11:32:13.000Z | it/python/arithmeticOperators/14.md | nank1ro/Codigo-Questions | 559cf998c8b5fbf7a9aee2db08fe57c8abc63408 | [
"BSD-3-Clause"
] | 1 | 2021-12-07T16:04:12.000Z | 2021-12-07T16:04:12.000Z | ---
language: python
exerciseType: 2
---
# --instructions--
Calcola la parte intera (divisione floor) dei numeri 75.0 (*quoziente*) e 8 (*divisore*), quindi stampa il `risultato`
# --seed--
```python
risultato = [/][/][/]
print(risultato)
```
# --answers--
- 75.0
- -
- *
- **
- //
- 8
# --solutions--
```python
risultato = 75.0 // 8
print(risultato)
```
# --output--
9.0
| 10.833333 | 118 | 0.566667 | ita_Latn | 0.544777 |
08d05c0d6607e723ba1ad8281b42de19b10f2d3e | 2,334 | md | Markdown | _posts/2020-03-18-routing.md | jchack1/web-dev-blog | 8ab09a32068e4afe1c3b72a5eb6efd880eb28efc | [
"MIT"
] | null | null | null | _posts/2020-03-18-routing.md | jchack1/web-dev-blog | 8ab09a32068e4afe1c3b72a5eb6efd880eb28efc | [
"MIT"
] | 3 | 2021-03-02T20:23:04.000Z | 2021-03-02T20:23:59.000Z | _posts/2020-03-18-routing.md | jchack1/web-dev-blog | 8ab09a32068e4afe1c3b72a5eb6efd880eb28efc | [
"MIT"
] | null | null | null | ---
layout: post
title: "Update and Routing"
date: 2020-03-18 17:12
tags: dotnet MVC routing
navigation: true
class: post-template
current: post
---
A lot has happened in the month since I last wrote.
I was very busy with my practicum and neglected some of my own projects. I then went on vacation to Maui for one week, and started watching the Covid-19 crisis unfold from afar. Currently I am at home in self-isolation, working remotely to finish my practicum. I have great luck and timing - 14 day self-isolation, with 2 weeks left of my practicum. After that, I'm not sure what my situation will be. Perhaps it will be an opportunity to continue my dev learning full time. Let's go with that.
I'm going to try writing posts with one topic only, for now. This post will explain what I know about routing in .NET.
One definition I will use:
Overload: in C#, some methods will have the same name but can accept different parameters(aka arguements, in other languages). These different options are called "overloads". You overload one method, rather than writing multiple methods that do the same thing but use different parameters.
You deal with routing in your RouteConfig.cs file. To create custom routes you have 2 main approaches: Convention-based and Attribute routing. Attribute routing is cleaner and is the recommended way.
Convention-based:
- in RegisterRoutes, put routes in order of most specific to most generic
- create routes.MapRoute(); before default route
- the most commonly used overload accepts 3 parameters: name, url, and default
- default defines the controller and action that you will use
- once you create this, you go to the corresponding controller and create the action result
- MapRoute() can accept another argument for constraints (like number of digits in a year or month) - can define using regular expressions
For large applications, you can accumulate many custom routes in your RouteConfig.cs file, so you can use attribute routing to make it cleaner.
Attribute routing:
- use attribute above action in controller, rather than creating it in RouteConfig.cs
- in RouteConfig.cs, add routes.MapMvcAttributeRoutes();
- for example, in controller type the following above your action [Route("movies/release/{year}/{month:regex(\\d{2}")})]
- constraints placed directly in attribute
| 61.421053 | 497 | 0.782776 | eng_Latn | 0.999408 |
08d0f8255935e86151dee5e43a2b369a66594bc3 | 3,062 | md | Markdown | docs/framework/unmanaged-api/debugging/icordebugeval-createvalue-method.md | lucieva/docs.cs-cz | a688d6511d24a48fe53a201e160e9581f2effbf4 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2018-12-19T17:04:23.000Z | 2018-12-19T17:04:23.000Z | docs/framework/unmanaged-api/debugging/icordebugeval-createvalue-method.md | lucieva/docs.cs-cz | a688d6511d24a48fe53a201e160e9581f2effbf4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/unmanaged-api/debugging/icordebugeval-createvalue-method.md | lucieva/docs.cs-cz | a688d6511d24a48fe53a201e160e9581f2effbf4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: ICorDebugEval::CreateValue – metoda
ms.date: 03/30/2017
api_name:
- ICorDebugEval.CreateValue
api_location:
- mscordbi.dll
api_type:
- COM
f1_keywords:
- ICorDebugEval::CreateValue
helpviewer_keywords:
- ICorDebugEval::CreateValue method [.NET Framework debugging]
- CreateValue method [.NET Framework debugging]
ms.assetid: 9a1c0b47-6f10-4fcb-844a-4ab2d7990140
topic_type:
- apiref
author: rpetrusha
ms.author: ronpet
ms.openlocfilehash: 6d67784daee055106f104d74d098b9926c6de2ec
ms.sourcegitcommit: 3d5d33f384eeba41b2dff79d096f47ccc8d8f03d
ms.translationtype: MT
ms.contentlocale: cs-CZ
ms.lasthandoff: 05/04/2018
ms.locfileid: "33417109"
---
# <a name="icordebugevalcreatevalue-method"></a>ICorDebugEval::CreateValue – metoda
Vytvoří hodnotu zadaného typu, s počáteční hodnotou nula nebo hodnotu null.
Tato metoda je zastaralé v rozhraní .NET Framework verze 2.0. Použití [icordebugeval2::createvaluefortype –](../../../../docs/framework/unmanaged-api/debugging/icordebugeval2-createvaluefortype-method.md) místo.
## <a name="syntax"></a>Syntaxe
```
HRESULT CreateValue (
[in] CorElementType elementType,
[in] ICorDebugClass *pElementClass,
[out] ICorDebugValue **ppValue
);
```
#### <a name="parameters"></a>Parametry
`elementType`
[v] Hodnota [CorElementType](../../../../docs/framework/unmanaged-api/metadata/corelementtype-enumeration.md) výčet, který určuje typ hodnoty.
`pElementClass`
[v] Ukazatel na [ICorDebugClass](../../../../docs/framework/unmanaged-api/debugging/icordebugclass-interface.md) objekt, který určuje třída hodnoty, pokud typ není primitivní typ.
`ppValue`
[out] Ukazatel na adresu "ICorDebugValue" objekt, který představuje hodnotu.
## <a name="remarks"></a>Poznámky
`CreateValue` vytvoří `ICorDebugValue` objekt daného typu za účelem používání ve vyhodnocení funkce. Tento objekt hodnota slouží k předávání konstanty uživatele jako parametry.
Pokud je typ hodnoty primitivní typ, jeho počáteční hodnota je nulová nebo má hodnotu null. Použití [icordebuggenericvalue::SetValue –](../../../../docs/framework/unmanaged-api/debugging/icordebuggenericvalue-setvalue-method.md) nastavit hodnotu primitivního typu.
Pokud hodnota `elementType` je ELEMENT_TYPE_CLASS, získat "ICorDebugReferenceValue" (vrátí `ppValue`) představující odkaz na hodnotu null. Tento objekt můžete použít k vyhodnocení funkce, s parametry odkaz na objekt předat hodnotu null. Nelze nastavit `ICorDebugValue` k ničemu; vždy zůstává hodnotu null.
## <a name="requirements"></a>Požadavky
**Platformy:** najdete v části [požadavky na systém](../../../../docs/framework/get-started/system-requirements.md).
**Záhlaví:** CorDebug.idl, CorDebug.h
**Knihovna:** CorGuids.lib
**Verze rozhraní .NET framework:** 1.1, 1.0
## <a name="see-also"></a>Viz také
[CreateValueForType – metoda](../../../../docs/framework/unmanaged-api/debugging/icordebugeval2-createvaluefortype-method.md)
ICorDebugValue
| 42.527778 | 308 | 0.739386 | ces_Latn | 0.957832 |
08d237c67feec55672f55464fd3a753ee8ce7fce | 10,467 | md | Markdown | README.md | darlandieterich/minha-receita | fc410c2b967c8586e9b7442d3e470c2b6d20ec9d | [
"MIT"
] | null | null | null | README.md | darlandieterich/minha-receita | fc410c2b967c8586e9b7442d3e470c2b6d20ec9d | [
"MIT"
] | null | null | null | README.md | darlandieterich/minha-receita | fc410c2b967c8586e9b7442d3e470c2b6d20ec9d | [
"MIT"
] | null | null | null | # Minha Receita [](https://github.com/cuducos/minha-receita/actions)
API web para consulta de informações do CNPJ (Cadastro Nacional da Pessoa Jurídica) da Receita Federal.
1. [Sobre](#sobre)
1. [Histórico](#historico)
1. [Propósito](#proposito)
1. [Qual a URL para acesso?](#qual-a-url-para-acesso)
1. [Instalação](#instalacao)
1. [Requisitos](#requisitos)
1. [Configurações](#configuracoes)
1. [Uso](#uso)
1. [Download dos dados](#download-dos-dados)
1. [Carregamento do banco de dados](#carregamento-do-banco-de-dados)
1. [API web](#api-web)
1. [Contribuindo](#contribuindo)
1. [Muito obrigado](#muito-obrigado)
## Sobre
### Histórico
Pela [Lei de Acesso à Informação](http://www.acessoainformacao.gov.br/assuntos/conheca-seu-direito/a-lei-de-acesso-a-informacao), os dados de CNPJ devem ser públicos e acessíveis por máquina. A Receita Federal oferece esses dados escondidos atrás de um CAPTCHA ou em formato pouco convencional (um _fixed-width text file_), com links lentos e instáveis para download arquivos somando gigas. Isso não é acessível o suficiente.
O [Turicas](https://twitter.com/turicas) já baixou e converteu esses arquivos para CSV, e ainda oferece um _mirror_ para download mais estável desses arquivos — tudo isso no [`socios-brasil`]() e disponibilizado no [Brasil.IO](https://brasil.io/).
### Propósito
O código desse repositório faz esses dados ainda mais acessíveis:
1. Transformando os dados em CSV (assim como o [`socios-brasil`](https://github.com/turicas/socios-brasil) já faz)
2. Importando automaticamente os dados para um banco de dados PostgreSQL
3. Adicionando dados com descrições dos CNAEs (inexistente nos arquivos da Receita Federal)
4. Fornecendo uma API web para a consulta de dados de um CNPJ
### Qual a URL para acesso?
Disponibilizo essa aplicação para que cada um rode na sua própria infraestrutura, mas existe um protótipo no ar em [minhareceita.org](https://minhareceita.org). O protótipo não tem nenhuma [garantia de nível de serviço](https://pt.wikipedia.org/wiki/Acordo_de_n%C3%ADvel_de_servi%C3%A7o) e a única forma de aumentar sua disponibilidade é contribuindo via [financiamento coletivo aqui no GitHub](https://github.com/sponsors/cuducos). Mais sobre o protótipo nesse [fio](https://twitter.com/cuducos/status/1339980776985808901).
Não tenho interesse em desenvolver um sistema para cobrar por esse serviço.
## Instalação
### Requisitos
Existem duas formas de rodar essa aplicação:
* ou diretamente a partir do seu sistema operacional
* ou com Docker
_Talvez_ seja necessário um sistema UNIX (Linux ou macOS), mas não tenho certeza pois não testei em Windows.
É necessário cerca de 30Gb disponíveis de espaço em disco para armazenar os dados.
#### Requisitos e instalação sem Docker
* [Go](https://golang.org/) versão 1.15
* Cliente [PostgreSQL](https://www.postgresql.org/) (comando `psql` disponível no seu terminal — em sistemas Debian, `apt install postgresql-client` resolve)
* Variável de ambiente`POSTGRES_URI` com credenciais de acesso a um banco de dados PostgreSQL (como no exemplo `.env.sample`)
Baixe as dependências e compile a aplicação para um diretório incluído no `PATH`, por exemplo:
```console
$ go get
$ go build -o /usr/local/bin minha-receita
```
#### Requisitos e instalação com Docker
* [Docker](https://www.docker.com/)
* [Docker Compose](https://docs.docker.com/compose/install/)
Gere as imagens dos containers com:
```console
$ docker-compose build
```
### Configurações
Todas as configurações são passadas via variáveis de ambiente e estão documentadas no `--help` da aplicação.
#### Exemplo
Sem Docker:
```console
$ minha-receita --help
$ minha-receita api --help
```
Com Docker:
```console
$ docker-compose run --rm minha-receita --help
$ docker-compose run --rm minha-receita api --help
```
## Uso
### Download dos dados
O comando `download` faz o download dos arquivos necessários para alimentar o banco de dados. Na sequência, o comando `parse` transforma os arquivos para o formato CSV. Ambos aceitam o argumento `--directory` (ou `-d`) com um diretório onde encontrar os dados (o padrão é `data/`).
Por padrão o comando `download` baixa dados do servidor da Receita Federal, que é lento e instável, então, como alternativa, podemos utilizar o _mirror_ do [Brasil.IO](https://brasil.io) com a opção `--mirror`.
#### Exemplo
Sem Docker:
```console
$ minha-receita download --mirror
$ minha-receita parse
```
Com Docker:
```console
$ docker-compose run --rm minha-receita download --directory /mnt/data/
$ docker-compose run --rm minha-receita parse --directory /mnt/data/
```
### Carregamento do banco de dados
Primeiro é necessário criar as tabelas no banco de dados, para isso utlize o comando `create`.
Caso seja necessário limpar o banco de dados para começar um novo carregamento de dados, é possível excluir as tabelas com comando `drop`.
Para importar os dados, utilize o comando `import` — esse comando pode demorar horas, depdendendo do equipamento. Esse comando também aceita a opção `--directory` ou `-d` para especificar um local diferente do padrão onde encontrar os arquivos.
#### Questões de privacidade
Assim como o [`socios-brasil`](https://github.com/turicas/socios-brasil#privacidade) removemos alguns dados para evitar exposição de dados sensíveis de pessoas físicas, bem como SPAM. Ao contrário do `socios-brasil`, não temos uma opção para desativar essa camada de provacidade (mas PRs são bem-vindos).
#### Exemplos de uso
Sem Docker:
```console
$ minha-receita drop # caso necessário
$ minha-receita create
$ minha-receita import
```
Com Docker:
```console
$ docker-compose run --rm minha-receita drop # caso necessário
$ docker-compose run --rm minha-receita create
$ docker-compose run --rm minha-receita import -d /mnt/data/
```
### API web
A API web é uma aplicação super simples que, por padrão, ficará disponível em [`localhost:8000`](http://localhost:8000).
#### Exemplos de uso
Sem Docker:
```console
$ minha-receita api
```
Com Docker:
```console
$ docker-compose up
```
A API web tem apenas dois _endpoints_:
##### `POST /`
| Caminho da URL | Tipo de requisição | Dados enviados | Código esperado na resposta | Conteúdo esperado na resposta |
|---|---|---|---|---|
| `/` | `GET` | | 405 | `{"message": "Essa URL aceita apenas o método POST."}` |
| `/` | `HEAD` | | 405 | `{"message": "Essa URL aceita apenas o método POST."}` |
| `/` | `POST` | | 400 | `{"message": "conteúdo inválido na requisição POST."}` |
| `/` | `POST` | `cpf=foobar` | 400 | `{"message": "CNPJ não enviado na requisição POST."}` |
| `/` | `POST` | `cnpj=foobar` | 400 | `{"message": "CNPJ foobar inválido."}` |
| `/` | `POST` | `cnpj=00000000000000` | 404 | `{"message": "CNPJ 00.000.000/0001-91 não encontrado."}` |
| `/` | `POST` | `cnpj=19131243000197` | 200 | _Ver JSON de exemplo abaixo._ |
| `/` | `POST` | `cnpj=19.131.243/0001-97` | 200 | _Ver JSON de exemplo abaixo._ |
###### Exemplo de requisição usando o `curl`
```console
$ curl -i -X POST -d cnpj=19131243000197 0.0.0.0:8000
```
###### Exemplo de resposta válida
```json
{
"cnpj": "19131243000197",
"identificador_matriz_filial": 1,
"descricao_matriz_filial": "Matriz",
"razao_social": "OPEN KNOWLEDGE BRASIL",
"nome_fantasia": "REDE PELO CONHECIMENTO LIVRE",
"situacao_cadastral": 2,
"descricao_situacao_cadastral": "Ativa",
"data_situacao_cadastral": "2013-10-03",
"motivo_situacao_cadastral": 0,
"nome_cidade_exterior": null,
"codigo_natureza_juridica": 3999,
"data_inicio_atividade": "2013-10-03",
"cnae_fiscal": 9430800,
"cnae_fiscal_descricao": "Atividades de associações de defesa de direitos sociais",
"descricao_tipo_logradouro": "ALAMEDA",
"logradouro": "FRANCA",
"numero": "144",
"complemento": "APT 34",
"bairro": "JARDIM PAULISTA",
"cep": 1422000,
"uf": "SP",
"codigo_municipio": 7107,
"municipio": "SAO PAULO",
"ddd_telefone_1": "11 23851939",
"ddd_telefone_2": null,
"ddd_fax": null,
"qualificacao_do_responsavel": 10,
"capital_social": 0.0,
"porte": 5,
"descricao_porte": "Demais",
"opcao_pelo_simples": false,
"data_opcao_pelo_simples": null,
"data_exclusao_do_simples": null,
"opcao_pelo_mei": false,
"situacao_especial": null,
"data_situacao_especial": null,
"cnaes_secundarios": [
{
"codigo": 9493600,
"descricao": "Atividades de organizações associativas ligadas à cultura e à arte"
},
{
"codigo": 9499500,
"descricao": "Atividades associativas não especificadas anteriormente"
},
{
"codigo": 8599699,
"descricao": "Outras atividades de ensino não especificadas anteriormente"
},
{
"codigo": 8230001,
"descricao": "Serviços de organização de feiras, congressos, exposições e festas"
},
{
"codigo": 6204000,
"descricao": "Consultoria em tecnologia da informação"
}
],
"qsa": [
{
"identificador_de_socio": 2,
"nome_socio": "NATALIA PASSOS MAZOTTE CORTEZ",
"cnpj_cpf_do_socio": "***059967**",
"codigo_qualificacao_socio": 10,
"percentual_capital_social": 0,
"data_entrada_sociedade": "2019-02-14",
"cpf_representante_legal": null,
"nome_representante_legal": null,
"codigo_qualificacao_representante_legal": null
}
]
}
```
##### `GET /healthz`
| Caminho da URL | Tipo de requisição | Código esperado na resposta | Conteúdo esperado na resposta |
|---|---|---|---|
| `/healthz` | `GET` | 200 | |
| `/healthz` | `HEAD` | 405 | `{"message": "Essa URL aceita apenas o método GET."}` |
| `/healthz` | `POST` | 405 | `{"message": "conteúdo inválido na requisição GET."}` |
## Contribuindo
Escreva testes, rode os testes e reconstrua os containers para saber se está tudo certo:
```console
$ go test ./...
$ docker-compose build
```
## Muito obrigado
Ao [Turicas](https://twitter.com/turicas) por todo ativismo mais o trabalho de coleta, tratamento, e carinho que faz os dados serem cada vez mais acessíveis. Muito desse projeto se deve a ele. Ao [Bruno](https://twitter.com/555112299jedi), sem o qual [nunca teríamos acesso a esses dados por menos de R$ 500 mil](https://medium.com/serenata/o-dia-que-a-receita-nos-mandou-pagar-r-500-mil-para-ter-dados-p%C3%BAblicos-8e18438f3076). E ao [Fireman](https://twitter.com/daniellfireman), pela amizade e pela mentoria em Go!
| 36.093103 | 524 | 0.711379 | por_Latn | 0.994869 |
08d27c96271a4c0b7adb2b5e70ddbfdd9eb25e83 | 291 | md | Markdown | src/bindings/io/doc/README.md | kodebach/libelektra | c0399960d9455befb68299ce9b82312154679af2 | [
"MIT",
"BSD-3-Clause-Clear",
"Apache-2.0",
"BSD-3-Clause"
] | 188 | 2015-01-07T20:34:26.000Z | 2022-03-16T09:55:09.000Z | src/bindings/io/doc/README.md | kodebach/libelektra | c0399960d9455befb68299ce9b82312154679af2 | [
"MIT",
"BSD-3-Clause-Clear",
"Apache-2.0",
"BSD-3-Clause"
] | 3,813 | 2015-01-02T14:00:08.000Z | 2022-03-31T14:19:11.000Z | src/bindings/io/doc/README.md | kodebach/libelektra | c0399960d9455befb68299ce9b82312154679af2 | [
"MIT",
"BSD-3-Clause-Clear",
"Apache-2.0",
"BSD-3-Clause"
] | 149 | 2015-01-10T02:07:50.000Z | 2022-03-16T09:50:24.000Z | - infos =
- infos/author = Thomas Wahringer <waht@libelektra.org>
- infos/licence = BSD
- infos/status =
- infos/provides =
- infos/description =
# Example I/O Binding
This directory contains a complete example of an I/O binding for documentation
purposes.
This binding is not functional.
| 22.384615 | 78 | 0.752577 | eng_Latn | 0.966285 |
08d28ea54d399f1f85dc229c8146baca07f60437 | 47 | md | Markdown | README.md | BLannoo/openCV | ceee03b792cfb384555998a6b9352dffba97c3e7 | [
"MIT"
] | null | null | null | README.md | BLannoo/openCV | ceee03b792cfb384555998a6b9352dffba97c3e7 | [
"MIT"
] | null | null | null | README.md | BLannoo/openCV | ceee03b792cfb384555998a6b9352dffba97c3e7 | [
"MIT"
] | null | null | null | # openCV
Experimenting with the openCV library
| 15.666667 | 37 | 0.829787 | eng_Latn | 0.99232 |
08d3d2902bb01fa650f01eb1afd62f151a9bf828 | 379 | md | Markdown | docs/ru/faq/_010_general/README.md | OLFDB/ioBroker.docs | 26501a66cacd9b0c65976a3d10760de201f39a86 | [
"MIT"
] | 47 | 2017-08-15T12:55:53.000Z | 2021-12-25T23:25:20.000Z | docs/ru/faq/_010_general/README.md | gaudes/ioBroker.docs | 59a32ab5b17da58604c272b9718246fe3eb41f5a | [
"MIT"
] | 253 | 2017-03-28T20:20:48.000Z | 2022-03-08T08:49:52.000Z | docs/ru/faq/_010_general/README.md | gaudes/ioBroker.docs | 59a32ab5b17da58604c272b9718246fe3eb41f5a | [
"MIT"
] | 148 | 2017-03-24T21:32:12.000Z | 2022-03-10T07:17:46.000Z | ---
translatedFrom: de
translatedWarning: Если вы хотите отредактировать этот документ, удалите поле «translationFrom», в противном случае этот документ будет снова автоматически переведен
editLink: https://github.com/ioBroker/ioBroker.docs/edit/master/docs/ru/faq/_010_general/README.md
title: Общие вопросы
hash: r+xs78o3xnC8PyivmT4FH3IUArETqBefgwCe8HT+YaQ=
---
# Общие вопросы | 47.375 | 165 | 0.825858 | rus_Cyrl | 0.518394 |
08d409157747c4362ca703e8f6955af4856f93b6 | 311 | md | Markdown | latest/functions-framework/golang/OpenFuncAsync/README.md | wanjunlei/samples | 5fcc86529b9ca632878952c7180905e2841c1f90 | [
"Apache-2.0"
] | 1 | 2021-08-23T02:46:33.000Z | 2021-08-23T02:46:33.000Z | v0.4.0/functions-framework/golang/OpenFuncAsync/README.md | penghuima/samples | 998d151cecc0512d95689c568af59a8f51b90b01 | [
"Apache-2.0"
] | null | null | null | v0.4.0/functions-framework/golang/OpenFuncAsync/README.md | penghuima/samples | 998d151cecc0512d95689c568af59a8f51b90b01 | [
"Apache-2.0"
] | 3 | 2021-01-29T09:51:30.000Z | 2021-06-04T03:34:03.000Z | # OpenFuncAsync Runtime examples
In order to follow these examples, you need to install [Dapr](https://docs.dapr.io/getting-started/install-dapr-selfhost/) and [Go 1.15+](https://golang.org/doc/install).
## OpenFunction Context Function
- Bindings
- [example](bindings)
- Pubsub
- [example](pubsub)
| 22.214286 | 170 | 0.723473 | eng_Latn | 0.781549 |
08d42139e4cd1bfa5556feb56c8c6d5f7a3c56f4 | 2,905 | md | Markdown | src/pages/inclusivity/index.md | arnevit83/gatsby | 7206925d56a8d68e169a4602e8df3be3d5bc42d0 | [
"MIT"
] | null | null | null | src/pages/inclusivity/index.md | arnevit83/gatsby | 7206925d56a8d68e169a4602e8df3be3d5bc42d0 | [
"MIT"
] | null | null | null | src/pages/inclusivity/index.md | arnevit83/gatsby | 7206925d56a8d68e169a4602e8df3be3d5bc42d0 | [
"MIT"
] | null | null | null | ---
templateKey: inclusivity-page
headerobject:
title: Childlessness and inclusivity
description: "Welcome to Butterfly and Beyond. I am glad you are here. If you
are childless not by choice or by circumstance, and are wondering what life
holds for you now, I want to let you know that you are not alone, you are
not less than, and that it is possible to live a meaningful and fulfilled
life without children. "
pagetitle: Inclusivity
sections: []
footerobjects:
- footerstyle: Email
- footerstyle: Blog
---
During recent years, increasing numbers of organisations have started to realise the importance of promoting equality, diversity and inclusion within the workplace. The global COVID-19 pandemic, and incidents of racial injustice, have heightened unconscious bias and the need for inclusivity amongst those whose voices have traditionally been marginalised.
<br /><br />
The issues that parents face at work in terms of bias has been well-documented. What may be less well recognised are the issues surrounding childlessness. Childlessness could be considered an “invisible” aspect of inclusivity. Childless women may make up to twenty percent of women employees - the figures for men are less certain, and women without children have been found to work the longest hours of any group. Although the work-life interface is interpreted differently within organisations, if initiatives around it exclude their growing childless employee base, the initiatives will be less effective and may render a feeling of injustice with counter-productive effects.
<br /><br />
In addition, some of these employees may be struggling with fertility issues, may have experienced pregnancy loss, or may be permanently childlessness not by choice or by circumstance, all of which need to be handled sensitively, and with awareness. Childless employees may feel excluded and isolated at work if the predominant narrative is one of families and children.
<br /><br />
Areas in which I can help by providing training to raise awareness are:
<br /><br />
- Uncovering omissions - childlessness may be a blind-spot and omitted from work-life balance considerations, e.g. expanding the concept of what ‘life’ and ‘family’ mean to be inclusive, so that flexibility principles are applied equitably regardless of reason.
- Creating an environment in which affected individuals feel safe to be open about issues affecting them.
- Raising awareness of appropriate communication and language within the workplace, e.g., questions around whether someone has children, or why they do not, may be immensely private and painful for some.
<br />
If these issues are not dealt with sensitively it can lead to reduced performance and engagement, increased absenteeism and could even lead to loss of talent.
<br /><br />
To discuss a tailored program for your organisation please [click here.](/contact)
| 80.694444 | 678 | 0.794148 | eng_Latn | 0.999938 |
08d5715c49c4c72456abad20a85f60261687d8bf | 498 | md | Markdown | pages/wgg/Periodes/718.md | Utanapishti/utanapishti.github.io | b2ecf8e10414f2abdfbdba4d0338533c61a5d927 | [
"MIT",
"BSD-3-Clause"
] | null | null | null | pages/wgg/Periodes/718.md | Utanapishti/utanapishti.github.io | b2ecf8e10414f2abdfbdba4d0338533c61a5d927 | [
"MIT",
"BSD-3-Clause"
] | 3 | 2021-05-20T02:11:08.000Z | 2022-02-26T04:57:44.000Z | pages/wgg/Periodes/718.md | Utanapishti/utanapishti.github.io | b2ecf8e10414f2abdfbdba4d0338533c61a5d927 | [
"MIT",
"BSD-3-Clause"
] | null | null | null | ---
title: "Batalla de Tsushima"
permalink: periodes_718.html
layout: periode
dataInici: 1905-05-27
dataFi: 1905-05-28
sidebar: periodes
pares:
- id: 520
title: "Guerra ruso-japonesa"
dataInici: "(1904-02-08)"
dataFi: "(1905-09-05)"
fills:
jocsPrincipals:
- title: "Tsushima"
bggId: 5994
dataInici:
dataFi:
jocsEscenaris:
jocsEpoca:
- title: "Fire When Ready"
bggId: 5194
escenari: "Tsushima Straits"
dataInici:
dataFi:
jocsEpocaEscenaris:
---
| 16.064516 | 33 | 0.664659 | cat_Latn | 0.135716 |
08d5f107a1ee62ba19b5054f7e21c11ce5be55e2 | 3,466 | md | Markdown | readme.md | Lindomarc/ga-analytcs | ecfed47c27f044e4613a9112047b63d248ddb642 | [
"Unlicense"
] | 3 | 2015-06-09T07:54:56.000Z | 2022-03-16T23:09:18.000Z | readme.md | rayz90/ga-multisite-dashboard | 6e0829157bb362b42572c8c67741e90f1b3fe4dd | [
"Unlicense"
] | null | null | null | readme.md | rayz90/ga-multisite-dashboard | 6e0829157bb362b42572c8c67741e90f1b3fe4dd | [
"Unlicense"
] | null | null | null | Google Analytics multi-site dashboard
=========
This is a dashboard that shows the visitors of multiple different websites using the Google Analytics API. For each websites it shows a graph of the vistors in the last 24 hours and the realtime vistors.
The idea and layout is shamelessly ripped from https://github.com/Code4SA/dashboard
Screenshot
----
_A nice screenshot with some mock data_
Installation
-----
1. Clone the project.
2. Edit your Apache config, so the Document Root points to the docroot folder of this project. For other webservers, [check this](http://silex.sensiolabs.org/doc/web_servers.html).
3. Run `composer install`.
4. Copy your Google p12 key to `config/key.p12` (for more info check below).
5. Add your service account, websites and dispay preferences to `config/config.json`.
6. Enjoy your dashboard.
Google Analytics OAuth2 Key
--------
All the information regarding the OAuth2 key can also be found [here](https://developers.google.com/accounts/docs/OAuth2ServiceAccount).
1. Go to the Google Developers Console.
2. Select a project, or create a new one.
3. In the sidebar on the left, expand APIs & auth. Next, click APIs. In the list of APIs, make sure the Analytics API shows a status of ON.
4. In the sidebar on the left, select Credentials.
5. To set up a new service account, do the following:
- Under the OAuth heading, select Create new Client ID.
- When prompted, select Service Account and click Create Client ID.
- A dialog box appears. To proceed, click Okay, got it.
If you already have a service account, you can generate a new key by clicking the appropriate button beneath the existing service-account credentials table.
6. Download the P12 key.
7. Now go to the Admin page of Google Analytics.
8. Add the service account as user to all the GA accounts you are using for the dashboard.
Contributing
----
Front-end stuff is not really my cup of tea. Basically, my implemention of AJAX is ye olde meta-refresh. So, feel free to improve the JS/CSS/HTML to your liking, I will gladly review your pull request. Although, I would appreciate it if you keep the general look-and-feel intact.
I think the back-end (the index.php file) is pretty solid, but there is always room for improvement. So, don't hesitate to send me a pull request for this as well.
License
----
Copyright (c) 2014 Raymond Vermaas
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.
| 61.892857 | 460 | 0.774957 | eng_Latn | 0.951061 |
08d67bc981000e599a0b09494c3a34325e0b12e1 | 8,441 | md | Markdown | README.md | jhlothamer/godot_project_starter | bcefca30291e7341027337da676fc5b0cc378af4 | [
"MIT"
] | 20 | 2019-04-26T07:05:09.000Z | 2022-03-31T17:09:30.000Z | README.md | jhlothamer/godot_project_starter | bcefca30291e7341027337da676fc5b0cc378af4 | [
"MIT"
] | null | null | null | README.md | jhlothamer/godot_project_starter | bcefca30291e7341027337da676fc5b0cc378af4 | [
"MIT"
] | 2 | 2019-10-04T00:48:00.000Z | 2021-11-09T22:12:14.000Z | # Godot Project Starter
This is a starter project for Godot Engine 3.x. To use simply clone or download this repository. Then copy the "game" folder to another location and rename it. You'll then be able to open the copied project in Godot and start updating.
## Why use a Project Starter?
There are a few things every game should have, even a quick project hacked out during a game jam. Such things are
- A title
- Crediting your work and the works of others
- Instructions on how to play the game
- Transition affects between scenes
- A hud (heads up display) with Pause and Game Over dialogs
All of this is somewhat configurable, but you can also completely modify the scenes if you want, or even replace them. But for a game jam, or a simple prototype build where you don't want or can't spend the time on such things, this project may be for you.
In addition to the above items the start pack comes with these other goodies!
- TransitionMgr singleton - transition smoothly from scene to scene via code
- ScreenshotMgr singleton - capture frame images for screenshots in game
- Cover Image Generator scene - generate properly sized cover images for itch.io and other game hosting sites
## The Minimum You Should Change
If you use this project starter then they are a few things you'll want to change. The rest is optional.
1. Update The project name in the Project Settings. (Application > Config > Name) This will be loaded by the title scene. If you don't do this the title will say "Godot Project Starter".
2. Update the how_to_play.txt file (located at assets\data\how_to_play.txt)
3. In the howToPlay scene, update the the PlayBtn control to refer to your game scene in it's Scene To Load property. By default this just sends the player back to the title scene.
4. Update the credits.txt file (located at assets\data\credits.txt).
## What's Configurable?
### Title Scene Game Title
The Title scene uses the configured application name for the title. Just change the Name under Application > Config in the Project Settings. Note: this will take affect at runtime only.
### Credits Scene Text
The Credits scene loads it's text from the credits.txt file. Just update this file to give credit for any asset or component you need to. It's ALWAYS a good idea to list credit for any asset you don't own.
### How to Play Text
The How to Play scene load's it's text from the how_to_play.txt file. Just update this file to provide instructions about your game. Note: The How to Place scene is shown before every game session by default.
### What Scene a Button Transitions To
The buttons have a custom property called "Scene To Load". Just set this to the resource path of the scene you want to transition to when the button is clicked.
### Button Transition Speed and Sound Fade Out/In
The buttons use the transition manager (see below), which allows for a fade out/in affect when switching scenes. You can set the transition speed (in seconds) and whether the audio fades out/in. Note that a speed of zero or less will cause the default speed to be used. That speed is found in the Project Settings -> Globals -> Transition Mgr Default Speed.
## Pause and Game Over Dialogs
The pause and game over dialogs are contained in a scene called a hud. To include the dialogs in your game, just instance the hud scene into your game's scene.
### Pause Dialog
The pause dialog is setup to automatically appear when the "pause" action is pressed. This action is set up in the Input Map in the Project Settings. Out of the box the pause dialog will popup when the escape key or start button on a gamepad are pressed.
The pause dialog has 3 buttons: a resume, restart and main menu button. Resume hides the pause menu. Restart does nothing out of the box: you'll have to set the "Scene To Load" property to your games main scene or connect the button's pressed event to a new function. The main menu button takes the player to the title scene.
### Game Over Dialog
The game over dialog automatically appears when the "game_over" action is "pressed". Of course, there's no button for this. You must send this action in code to initiate the game over dialog. Here's the code for that.
> var a = InputEventAction.new()<br>
> a.action = "game_over"<br>
> a.pressed = true<br>
> Input.parse_input_event(a)
### Other Dialogs
You can add additional dialogs by creating a new Control scene with DialogBackground child node and the additional dialog buttons/controls you need to add.
Whenever the custom control appears, either in reaction to an event or by command, you'll want to set the paused property of the scene tree to true to pause the game. And don't forget to set it back to false when the dialog disappears.
## Other Goodies
### Transition Manager
The transition manager is a singleton that manages the transition between scenes. It simply fades the screen to black, switches scenes and then fades back in. It can also fade out the main audio bus's so the difference in background music isn't as jarring.
The Transition manager, called TransitionMgr, has only one public function called transition_to. It accepts a scene path, transition speed (in seconds) and a flag indicating if the main audio bus should be faded out and in as well.
A speed of transition no longer needs to be passed into the transition_to function. When speed isn't provided to the function, a new project setting (Project Settings -> Globals -> Transition Mgr Default Speed) is used. This allows you to set the speed for the while project in one place and override it for special cases.
### Screenshot Manager
The screenshot manager is a singleton that takes screenshots each frame and saves them to a new folder in the app data folder for the game. This new folder's name is based on the current date/time. Screenshots are toggled on and off by activating the "toggle_screenshots" action. Once activated a screenshot will be taken each frame until deactivated or a max number of files is created. This will allow you to either choose the best shot during an action sequence or combine the images into an animated GIF. (You can use a site like ezgif.com to make animated gifs.)
#### How to Make It Work
The screenshot manager is disabled by default. To enable it you must add a key/button binding to the "toggle_screenshots" action in the Input Map. Out of the box this action has none and so no screenshots can be taken with the manager. This is to keep players from accidentally activating the manager.
#### Disabled for Release Exports
The screenshot manager also frees itself for release exports (i.e. when you uncheck "Export With Debug" when exporting the project). Translation: you can only use it during debugging or debug exports. If you want to change this, just update the screenshot_mgr.gd script.
#### Project Settings
The screenshot manager has several settings located in the Project Settings under the Global section. They are:
- Screenshot Mgr Max Images - the maximum number of screenshots taken at a time. Default is 1000.
- Screenshot Mgr Resize Factor - Use this to shrink (or enlarge) the images saved. Default is 1.0 - so no resizing by default.
- Screenshot Mgr Toggle Action Name - defaulted to "toggle_screenshots".
- Screenshot Mgr Frame Delay - Controls how often a frame is saved as a screenshot. This corresponds to the frame delay when making a gif out of the images. Default is 0.1, which corresponds to a frame delay of 10/100 of a second between animated gif frames. This default results in a smoothly animated gif that is also smaller as well as a lot fewer image files being created.
### Cover Image Generator Scene
Creating a cover image for sites like itch.io is easy to do with game assets added to this non-game scene. Just add the assets, labels and animations and hook up the start of any animations with the start/stop button. This scene will capture screenshots that are cropped to the size of the "Cover" control node in the scene.
## Where Did the SoundTrackMgr and SignalMgr Components go?
If you used the project starter in the past you may have used the SoundTrackMgr and SignalMgr components. These are no longer included in the project starter but instead can be found Godot Helper Pack which is an add-on pack containing many useful components to make developing in GDScript easier. You can download the helper pack [here](https://github.com/jhlothamer/godot_helper_pack).
| 84.41 | 567 | 0.782016 | eng_Latn | 0.999493 |
08d69ed6080cc23039aa1b457a07793d2bb05409 | 2,361 | md | Markdown | README.md | rubrafmex/gopherconuk | 22b10a453a6cde3b64f88053daef9a0eaa2776c4 | [
"MIT"
] | 226 | 2018-08-07T21:48:32.000Z | 2022-02-10T06:45:38.000Z | README.md | rubrafmex/gopherconuk | 22b10a453a6cde3b64f88053daef9a0eaa2776c4 | [
"MIT"
] | 2 | 2019-12-07T06:57:55.000Z | 2021-12-13T05:54:32.000Z | README.md | rubrafmex/gopherconuk | 22b10a453a6cde3b64f88053daef9a0eaa2776c4 | [
"MIT"
] | 60 | 2018-09-01T03:58:31.000Z | 2022-03-16T10:59:17.000Z | # Go micro-service in ~30 minutes
This is a Go micro-service written from scratch.
It shows how to use [net/http](https://godoc.org/net/http), and how to structure a Go project.
It relies on Go 1.11 Beta 2 and the upcoming "Go modules" (formerly known as "vgo") support.
Dependency injection is used to insert a logger instance into the handler.
You can also notice how the test is constructed in order to provide testing for the handler.
A Docker container is available, thanks to the Dockerfile. It shows how to construct such containers.
## How to use
Because this project uses go modules, as long as you are using Go 1.11 Beta 2+ or Go 1.10 with vgo support,
you should be ok.
Clone this anywhere in your computer and create a project in your editor. I'm using [GoLand IDE](https://jetbrains.com/go) in order to work
on the project during the presentation as well as have support for go modules.
The bundled, self-signed, certificates are bound to either ` dev.localhost:8080 ` or ` docker.localhost:8080 `. I obviously
do not recommend using these in production.
## Presentation link
I created this as part of the presentation at [GopherCon UK 18](https://www.gophercon.co.uk/).
The link for the video will be updated here when the presentation is out.
## References
### Structuring Go applications
In order to learn how to approach package design in Go, you can read the following resources:
- [Style guideline for Go packages - JBD](https://rakyll.org/style-packages/)
- [Standard Package Layout - Ben Johnson](https://medium.com/@benbjohnson/standard-package-layout-7cdbc8391fc1#.ds38va3pp)
- [Go best practices, six years in - Peter Bourgon](https://peter.bourgon.org/go-best-practices-2016/#repository-structure)
Once done, this article will help you understand the [Design Philosophy On Packaging by William Kennedy](https://www.ardanlabs.com/blog/2017/02/design-philosophy-on-packaging.html).
### Exposing Go applications to the Internet
[This article](https://blog.cloudflare.com/exposing-go-on-the-internet/) describes how you can start approaching
## Thank you
I would like to thank you [William "Bill" Kennedy](https://twitter.com/goinggodotnet) for the inspiration he provided on
getting me to do this talk.
## License
This project is under the MIT license. Please see the [LICENSE](LICENSE) file for more details.
| 41.421053 | 181 | 0.766624 | eng_Latn | 0.991182 |
08d7baaae2921713359cf3e42e5789b201db7bca | 1,710 | md | Markdown | AlchemyInsights/teams-chat-functionality.md | isabella232/OfficeDocs-AlchemyInsights-pr.vi-VN | 18a0b2fe64df0f41e705a51ee20a4f422a5ac9aa | [
"CC-BY-4.0",
"MIT"
] | 4 | 2020-05-19T19:08:25.000Z | 2021-02-19T19:52:24.000Z | AlchemyInsights/teams-chat-functionality.md | isabella232/OfficeDocs-AlchemyInsights-pr.vi-VN | 18a0b2fe64df0f41e705a51ee20a4f422a5ac9aa | [
"CC-BY-4.0",
"MIT"
] | 3 | 2020-06-02T23:31:24.000Z | 2022-02-09T06:55:29.000Z | AlchemyInsights/teams-chat-functionality.md | isabella232/OfficeDocs-AlchemyInsights-pr.vi-VN | 18a0b2fe64df0f41e705a51ee20a4f422a5ac9aa | [
"CC-BY-4.0",
"MIT"
] | 3 | 2019-10-09T20:33:30.000Z | 2021-10-09T10:36:59.000Z | ---
title: Teams năng trò chuyện
ms.author: pebaum
author: pebaum
ms.audience: ITPro
ms.topic: article
ms.service: o365-administration
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Priority
ms.assetid: ''
ms.custom:
- "9000738"
- "4367"
ms.openlocfilehash: c41ab0552985681f14090cc049f8bd77b8b49242823a418822674cd21dea0f77
ms.sourcegitcommit: b5f7da89a650d2915dc652449623c78be6247175
ms.translationtype: MT
ms.contentlocale: vi-VN
ms.lasthandoff: 08/05/2021
ms.locfileid: "53909011"
---
# <a name="teams-chat-functionality"></a>Teams năng trò chuyện
- [Bắt đầu trò chuyện](https://support.office.com/article/start-a-chat-in-teams-0c71b32b-c050-4930-a887-5afbe742b3d8) trong Microsoft Teams.
- [Lịch sử trò chuyện, xuất hoặc lưu và Teams chuyện](https://docs.microsoft.com/alchemyinsights/chat-history-in-microsoft-teams).
- Bạn cần trò chuyện với người dùng từ một tổ chức khác? Bạn muốn [Trò chuyện Riêng](https://docs.microsoft.com/microsoftteams/native-chat-for-external-users) (liên kết) cho tổ Teams của bạn.
- Bạn cần người dùng Teams trò chuyện với người **dùng Skype tiêu dùng** của mình? Bạn có thể [bật tùy chọn đó ở đây.](https://docs.microsoft.com/microsoftteams/manage-external-access#step-1---enable-your-organization-to-communicate-with-another-teams-organization)
- [Giữ lại hoặc xóa bỏ cuộc Teams với chính](https://docs.microsoft.com/microsoftteams/retention-policies) sách duy trì.
- Tạo Nhóm [toàn tổ chức để trò](https://docs.microsoft.com/microsoftteams/create-an-org-wide-team) chuyện với toàn bộ tổ chức của bạn.
- [Ẩn, tắt tiếng hoặc ghim cuộc trò chuyện trong Teams.](https://support.office.com/article/hide-mute-or-pin-a-chat-in-teams-9aee02ef-713d-495b-8a73-9762d8e4b066)
| 47.5 | 266 | 0.781287 | vie_Latn | 0.990951 |
08d88179d76295f1a2a8c08073c8232c3b79bfe6 | 3,202 | md | Markdown | video-prototypes/brainlink-daniel-paul/index.md | FH-Potsdam/prototyping-machines | de648ad3ab467aa3062437a7d947634251243931 | [
"MIT"
] | null | null | null | video-prototypes/brainlink-daniel-paul/index.md | FH-Potsdam/prototyping-machines | de648ad3ab467aa3062437a7d947634251243931 | [
"MIT"
] | null | null | null | video-prototypes/brainlink-daniel-paul/index.md | FH-Potsdam/prototyping-machines | de648ad3ab467aa3062437a7d947634251243931 | [
"MIT"
] | null | null | null | ---
layout: default
title: "Brainlink Research Lab"
author: "Daniel Boubet, Paul Roeder"
author-url: "http://paulroeder.com - https://incom.org/profil/7955"
summary: "We video-prototyped a brain interface to control a domestic device."
type: "video"
---
## Introduction
The seminar "Prototyping Machines" of Fabian Morón Zirfas was dedicated to learn and experiment with a variety of common prototyping techniques to enhance our capabilities of visualizing, testing and iterating ideas and concepts.
As the technological complexity increases, it becomes even harder to design high-fidelity prototypes. Both time and budget often restrict realistic implementations. Therefore it can be useful to "fake" prototypes by by-passing an actual implementation: Video prototypes enable us to create our own reality instead of building a working product. Common tools like Adobe After Effects, stop motion animations and further editing techniques can lead to great results.
After a kick-off workshop on After Effect we were well prepared to create our own videos. To avoid that we won't stuck in the ideation process and rather focus on the technical aspect of the video, we drew lots containing inspiring terms.
## The irascible iron
[](https://vimeo.com/216327129)
Daniel Boubet and Paul Roeder collaborated to prototype an "irascible iron". Since this negatively connoted adjective usually would not be a typical attribute of a commercial product, we tried to think of a way how the iron might be "hot-tempered" on a meaningful way.
For this reason we envisioned the story around the fictional "FHP Brainlink Research Group", working on a novel brain interface technology that enables research subjects to control objects just by using there mind. In this way even domestic appliances can be controlled.
As our video-prototype wants to prove: the technology works well and the required hardware is minimal (just a blinking head). The video shows a guy precisely ironing a shirt. However, since the object does exactly what the subject feels, there is a major unsolved problem: As the subject gets angry and doesn't want to iron anymore, the iron won't iron as well. The reason is a lack of "emotional stability", a feature which is not yet considered by the technology.
In this way we had an irascible iron.
## Prototyping techniques
To create a plausible and entertaining video, we made use of some video techniques:
### Motion tracking
To introduce the researcher we animated a chyron which moves with his face by motion-tracking the nose and mapping it to the text position.
### Stop motion
The rotating box is controlled by the subjects mind and moves around. We manually took a bunch of pictures while we were moving it step by step. We imported the files as a picture sequence to After Effects and rendered a video scene out of it.
### Look and feel
To create an authentic look and feel of the video, we found the interface lab in our university the right place to film our scenario. Furthermore we hang up some prints of scientific visuals. We filmed the story as an interview, since this is a common format to present research results.
| 69.608696 | 465 | 0.795753 | eng_Latn | 0.999458 |
08d991184e1ffbcc8313ef8983fd11156795d56e | 5,130 | md | Markdown | StarterKit/Session1/agenda.md | julo15/Resources | 871a1de38c9c690732075ce657f1391e54fa1f12 | [
"MIT"
] | null | null | null | StarterKit/Session1/agenda.md | julo15/Resources | 871a1de38c9c690732075ce657f1391e54fa1f12 | [
"MIT"
] | null | null | null | StarterKit/Session1/agenda.md | julo15/Resources | 871a1de38c9c690732075ce657f1391e54fa1f12 | [
"MIT"
] | null | null | null | # Code Reading Club - Session 1 agenda
## TOTAL time (75 mins)
You will need:
- a printed copy of the code for the club and coloured pens, crayons or pencils
-or-
- an electronic means of scribbling on a code PDF (e.g. a tablet and tablet pen or PDF annotation software)
## Why are we doing this?
Take a few minutes to talk about your motivation for doing the club. This is important because it will help you support each other and make it more likely that your group will feel that the club sessions have value for them.
### (2 mins) Independently - Note down one thing about the club:
* that you are looking forward to or excited about
* that you are worried or confused about
### (5 mins) Together - Discuss
* Give everyone a chance to read out their hopes and fears
* Use the remaining time to discuss collectively what you want to get out of the club
* Decide how long you want your sessions to be and how often you want to run them
* Decide if the same person will facilitate all of the sessions or if you want to take turns
* Think about how to accommodate members of your group who might have varying levels of experience and confidence
## First glance
The goal of this exercise is to practice to get a first impression of code and to act upon that. We all have different instincts and strategies for where to start when faced with a new piece of code. It doesn't matter how trivial you think the first and second things you noticed are.
### (1 min) Independently - Glance at the code
It's important that is an immediate reaction.
* Right away, note down the first thing that catches your eye.
* Then note down the second thing that catches your eye.
* Take the remainder of the minute to think about why you noticed those things first.
### (5 mins) Together - Discuss the results
Talk about why things might have jumped out for different people. It might be tempting for some people to start talking about the big picture; try to steer discussion back to individual details, rather than summaries.
* How do those initial observations help with deciding what to look at next?
* What lines or facts or concepts were chosen by everyone versus by only a few people?
Reflect also on what kind of knowledge you used in this exercise:
* Knowledge of the domain, of the programming language? Of a framework?
* What knowledge do you think might be needed to better understand this code?
## Code structure
The goal of this exercise is to be a concrete thing to *do* when looking at new code for the first time. New code can be scary, doing something will help! Digital annotation can take a bit longer than on paper. Leave time for your group members to settle on a technique that works for them.
### (9 mins) Independently - Examine structure
Variables
* Go through the code and circle all variables in red
* Then draw a link between variables and their uses
Function / method calls
* Go through the code and circle all methods in blue
* Then draw a link between methods and their invocations
Instantiation
* Go through the code and circle all instances of classes in green
* Then draw a link between classes and their instances
### (9 mins) Together - Discuss the results
* Did anyone have trouble deciding what constituted a variable, function or class?
* What patterns are visible from the colors and links only?
* How does the data flow through the code?
* What parts of the code seem to warrant more attention?
## Content
The goal of this exercise is to start to think about which lines in the code define its essence, have the biggest impact or need to be paid close attention to.
### (8 mins) Independently - Identify most important lines
Briefly discuss what it means to be important as a group (if you want to)
* then, identify the 5 lines you consider most important
### (10 mins) Together - Discuss
Discuss in the group:
* lines covered by many people?
* lines named but not by a lot of people
* Agree less than 8 of the most important lines
Take turns in the group, and let every member talk about the code for 30 seconds (or less/more, could also be one sentence each). Try to add new information and not repeat things that have been said, and repeat until people do not know new things anymore.
[Save the last word for me protocol](https://lead.nwp.org/knowledgebase/save-the-last-word-for-me-protocol/)
## Stop - Time check! (20 minutes for the full thing, 5 minutes to just jump to the conclusion)
## Summary
The goal of this exercise is to think about the core purpose or function of this code.
### (5 mins) Independently - Summarize
* try to write down the essence of the code in a few sentences
### (10 mins) Together - Discuss
* topics covered by many vs few
* strategies used to create the summary (e.g. method names, documentation, variable names, prior knowledge of system)
## Reflect on the session
If you have time, it's helpful to wrap up the session with a little reflection
### (5 mins) Together - note down things about the session
* that went well or felt good
* you want to try to do differently next time because they didn't work or felt bad
| 40.714286 | 290 | 0.764522 | eng_Latn | 0.999894 |
08d995037e038690b1a3393258dfa9e389cce9bf | 2,410 | md | Markdown | doc/README.md | voltan/pi | 1b9f9d67bc83805586de048858dddff9fa14bf0c | [
"BSD-3-Clause"
] | 120 | 2015-01-05T02:11:43.000Z | 2022-02-17T05:57:12.000Z | doc/README.md | chunhuili/pi | d43a0620a621a0c812c288cc01d8f23a97aabe6a | [
"BSD-3-Clause"
] | 225 | 2015-01-01T09:35:11.000Z | 2021-10-03T09:10:29.000Z | doc/README.md | chunhuili/pi | d43a0620a621a0c812c288cc01d8f23a97aabe6a | [
"BSD-3-Clause"
] | 84 | 2015-01-08T13:18:43.000Z | 2022-03-12T04:22:04.000Z | Pi Engine is a role oriented application development engine for web and mobile, designed as the next generation and a successor to Xoops.
Pi is developed upon PHP and MySQL with selected third-party frameworks including but not limited to Zend Framework library, jQuery, Bootstrap and Backbone.
Pi Project follows the philosophy of open standard, open design, open development and open structure. Pi is born as a complete open source project and intended to build a sustainable ecosystem that benefits all contributors and users.
Pi Engine is started by [Taiwen Jiang](http://github.com/taiwen) (Xoops Project Lead and Dev Lead), [Marc Desrousseaux](http://github.com/MarcoXoops) (Xoops QA Lead), [Hossein Azizabadi](http://github.com/voltan) (Xoops Persian Lead), [Kris](http://github.com/krisxoofoo) (Xoops Council Member and Xoops France Lead), etc. [Pi Team](https://github.com/pi-engine/pi/wiki/Pi-Team) is highly inspired by the Xoops led by onokazu (Ono Kazumi), skalpa and phppp (Taiwen Jiang, or D.J.) successively since 2001 and will continue to support and promote Xoops.
The Engine is released under a New BSD License.
Selected features and practices:
1. Modularization for functionality and applications
2. Components for basic libraries and services for fundamental system functions
3. Theming for presentation and appearance
4. Design-friendly templating
5. DevOps oriented architecture
6. Centralized security enhancement
Pi Engine tries to be strict standard compliant, including by not limited to:
1. Versioning - [Semantic Versioning Specification](http://semver.org)
2. PHP - [PSR compliant](https://github.com/php-fig/fig-standards), [Zend Framework Coding Standards](http://framework.zend.com/wiki/display/ZFDEV2/Coding+Standards)
3. HTML/CSS - [Google HTML/CSS Style Guide](http://google-styleguide.googlecode.com/svn/trunk/htmlcssguide.xml)
4. JavaScript - [Google JavaScript Style Guide](http://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml)
5. All code must be strictly compliant to its corresponding standards, no warning/notice messages allowed
Third-party frameworks utilized in this framework:
1. PHP - [Zend Framework 2](https://github.com/zendframework/zf2)
2. JavaScript - [jQuery](https://github.com/jquery/jquery)
3. CSS/JS - [Bootstrap](https://github.com/twitter/bootstrap)/[Backbone](https://github.com/documentcloud/backbone)
Taiwen Jiang
| 61.794872 | 552 | 0.790041 | eng_Latn | 0.864758 |
08d999d3d3f9cd40b008c65a6b6be75dc77a1ac8 | 205 | md | Markdown | aboutme.md | kuangzheng800/kuangzheng800.github.io | 141137f9e4b68b000d830dc445a581282cf26fd1 | [
"MIT"
] | null | null | null | aboutme.md | kuangzheng800/kuangzheng800.github.io | 141137f9e4b68b000d830dc445a581282cf26fd1 | [
"MIT"
] | null | null | null | aboutme.md | kuangzheng800/kuangzheng800.github.io | 141137f9e4b68b000d830dc445a581282cf26fd1 | [
"MIT"
] | null | null | null | ---
layout: page
title: About me
subtitle: A brief personal history of the person who made this website
cover-img: /assets/img/aboutme/about_background.jpg
share-img: /assets/img/aboutme/head_shot.jpg
---
| 25.625 | 70 | 0.77561 | eng_Latn | 0.954605 |
08d9d8fc44f6878989d6219a9988b3efdbcc3bb9 | 4,654 | md | Markdown | content/page/apis/email-apis.md | johncaruso/blog | ba418073d8dd360161767980879fe36413c3b69a | [
"MIT"
] | null | null | null | content/page/apis/email-apis.md | johncaruso/blog | ba418073d8dd360161767980879fe36413c3b69a | [
"MIT"
] | null | null | null | content/page/apis/email-apis.md | johncaruso/blog | ba418073d8dd360161767980879fe36413c3b69a | [
"MIT"
] | null | null | null | ---
title: Email APIs
category: servicenow
author: jace
layout: post
date: 2018-08-16 22:05:54 +0000
tags:
- server-side-api
url: "/email/"
aliases:
- "/email/"
---
# Email APIs
<!--more-->
## email
| Property/Method | Description |
| --- | --- |
| addAddress | Type can be cc or bcc |
| setBody | Override the body of the message |
| setFrom | Override the sender address |
| setReplyTo | Override the reply to address |
| setSubject | Override the subject of the message |
## template
| Property/Method | Description |
| --- | --- |
| print | Outputs message to the email body |
| space | Outputs spaces to the email body |
## email_action
| Property/Method | Description |
| --- | --- |
| action_insert | Send an email whenever a new record is inserted into the selected table |
| action_update | Send an email whenever a record in the selected table is modified |
| active | |
| advanced_condition | |
| affected_field_on_event | The field in the event that must be affected for this notification to send to subscribed users |
| category | Notification Preference Category. |
| collection | |
| condition | Send Notification when conditions evaluate to true |
| content_type | Specify whether the message is sent with a format of HTML, plain text, or both |
| default_interval | |
| description | |
| digest_from | |
| digest_html | |
| digest_reply_to | |
| digest_separator_html | |
| digest_separator_text | |
| digest_subject | |
| digest_template | |
| digest_text | |
| digestable | |
| event_name | |
| event_parm_1 | The first event parameter contains a recipient, either a user sys_id, group sys_id or an email address, who should receive this notification |
| event_parm_2 | The second event parameter contains a recipient, either a user sys_id, group sys_id or an email address, who should receive this notification |
| exclude_delegates | Do not send the notification to any delegates of this notification’s recipients |
| force_delivery | Bypass settings that would normally prevent sending to the recipient (e.g., device.schedule, user.notification) |
| from | Email address you want to appear in the From field |
| generation_type | Action that causes an email to be sent. Specifies whether to send email based on a trigger, an event firing, or an action against a record. |
| importance | Importance/Priority flag for the email |
| include_attachments | Send all attachments from the triggering record as email attachments |
| item | The sys_id of the subscribed item |
| item_table | The table that the subscribed item resides in |
| mandatory | Prevent users from unsubscribing/filtering-out this notification |
| message | |
| message_html | |
| message_list | |
| message_text | |
| name | |
| omit_watermark | Omitting watermark prevents any email replies from updating the triggering record |
| order | |
| push_message_only | |
| recipient_fields | Field in the currently-selected table that contains a reference to a user or group that will receive an email notification |
| recipient_groups | List of groups that will receive an email notification |
| recipient_users | List of users or email addresses that will receive an email notification |
| reply_to | Email address to be used when replying to the email notification |
| send_self | |
| sms_alternate | |
| style | |
| subject | |
| subscribable | Allow users to choose this notification when subscribing to their messages |
| sys_class_name | |
| sys_created_by | |
| sys_created_on | |
| sys_domain | Domain to which the rule belongs |
| sys_domain_path | |
| sys_id | |
| sys_mod_count | |
| sys_name | Display name for this application file |
| sys_overrides | Rule being overridden by the current record |
| sys_package | |
| sys_policy | Determines how application files are protected when downloaded or installed |
| sys_scope | Application containing this record |
| sys_update_name | |
| sys_updated_by | |
| sys_updated_on | |
| sys_version | Notification Version |
| template | |
| type | |
| weight | Used to decide which notification takes precedence when more than one qualifies |
## event
| Property/Method | Description |
| --- | --- |
| claimed_by | Cluster node that claimed this event |
| descriptive_name | |
| instance | |
| name | |
| parm1 | |
| parm2 | |
| process_on | |
| processed | |
| processing_duration | Time it took to process the event (milliseconds) |
| queue | Queue name for processor |
| state | |
| sys_created_by | |
| sys_created_on | |
| sys_id | |
| sys_mod_count | |
| sys_updated_by | |
| sys_updated_on | |
| table | |
| uri | |
| user_id | |
| user_name | |
| 35.526718 | 161 | 0.715728 | eng_Latn | 0.99436 |
08d9ee0470ee4b8757be3b07a6b6b9211b9e9e98 | 1,405 | md | Markdown | CONTRIBUTING.md | johnlunney/evergreen-skills-developers | 2c7be3d64566dde86a0e713cd8dab81f37e5136e | [
"MIT"
] | null | null | null | CONTRIBUTING.md | johnlunney/evergreen-skills-developers | 2c7be3d64566dde86a0e713cd8dab81f37e5136e | [
"MIT"
] | null | null | null | CONTRIBUTING.md | johnlunney/evergreen-skills-developers | 2c7be3d64566dde86a0e713cd8dab81f37e5136e | [
"MIT"
] | null | null | null | # Contributing to this repository
This page provides information about contributing code to this list of Evergreen Skills for Software Developers.
## Getting started
### Get your copy
* Fork the repository on GitHub.
* Clone the forked repository to your machine.
* Set up the official repository as a new "remote" in your cloned repository so that you can fetch new changes from it.
For more information, please refer to [GitHub's instructions on this](https://help.github.com/articles/fork-a-repo/).
## Propose Changes
To submit changes:
* Make sure your local copy is updated.
* Create a dedicated branch locally (`git checkout -b <nombre-de-la-rama>`).
* Add your changes by creating [_micro commits_](https://lucasr.org/2011/01/29/micro-commits/).
* Once your changes are completed, push them to your fork.
* Finally, create a [GitHub Pull Request](https://help.github.com/articles/creating-a-pull-request-from-a-fork/) from your fork, by using GitHub's web interface.
When your Pull Request is ready to be merged, the repository maintainers will integrate it and it will be published in the next release.
## Code of Conduct
This project and everyone participating in it is governed by the following [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [contact@romenrg.com](mailto:contact@romenrg.com).
| 48.448276 | 259 | 0.772954 | eng_Latn | 0.996472 |
08da1af4805ccc54a796157b7ae7fac34971819e | 19,011 | md | Markdown | docs/usage.md | ARCCA/circrna | 530893c909e14652fc3c5f659cf09fa7b5151d67 | [
"MIT"
] | 19 | 2021-02-11T10:12:28.000Z | 2022-03-25T04:14:35.000Z | docs/usage.md | ARCCA/circrna | 530893c909e14652fc3c5f659cf09fa7b5151d67 | [
"MIT"
] | 24 | 2021-02-11T11:31:40.000Z | 2022-03-24T11:34:56.000Z | docs/usage.md | ARCCA/circrna | 530893c909e14652fc3c5f659cf09fa7b5151d67 | [
"MIT"
] | 3 | 2021-04-22T14:54:19.000Z | 2022-02-21T11:30:38.000Z | # nf-core/circrna: Usage
It is recommended that first time users run `nf-core/circrna` with the minimal test dataset either locally or on a HPC, referring to the [output documentation](https://nf-co.re/circrna/dev/output) before running a full analysis.
```console
nextflow run nf-core/circrna -profile test
```
Run the test dataset on a HPC:
```console
nextflow run nf-core/circrna -profile test,<docker/singularity/podman/institute>
```
## Running the pipeline
A typical command for running the pipeline is as follows:
```console
nextflow run nf-core/circrna \
-profile <docker/singularity/podman/institute> \
--genome 'GRCh37' \
--input 'samples.csv' \
--input_type 'fastq'
```
By default, `nf-core/circrna` runs the circRNA discovery analysis module using `CIRCexplorer2`. The above command will perform circRNA quantification using these tools on ENSEMBL GRCh37 reference annotation files as defined in the iGenomes config.
### Updating the pipeline
To make sure that you're running the latest version of the pipeline, make sure that you regularly update the cached version of the pipeline:
```console
nextflow pull nf-core/circrna
```
When you run the above command, Nextflow automatically pulls the pipeline code from GitHub and stores it as a cached version. When running the pipeline after this, it will always use the cached version if available - even if the pipeline has been updated since.
### Reproducibility
It's a good idea to specify a pipeline version when running the pipeline on your data. This ensures that a specific version of the pipeline code and software are used when you run your pipeline. If you keep using the same tag, you'll be running the same version of the pipeline, even if there have been changes to the code since.
First, go to the [nf-core/circrna releases page](https://github.com/nf-core/circrna/releases) and find the latest version number - numeric only (eg. `1.3.1`). Then specify this when running the pipeline with `-r` (one hyphen) - eg. `-r 1.3.1`.
This version number will be logged in reports when you run the pipeline, so that you'll know what you used when you look back in the future.
## Input specifications
Input data can be passed to `nf-core/circrna` in two possible ways using the `--input` parameter.
### `--input "<path>"`
The simplest way to pass input data to `nf-core/circrna` is by providing the path to the input data with a suitable wildcard glob pattern:
#### fastq
```console
--input "/data/*_r{1,2}.fastq.gz"
```
##### bam
```console
--input "/data/*.bam"
```
> Beware that providing a path to input data will result in samples being named according to the common tuple key based on the glob pattern supplied. Take this into consideration when designing your phenotype file for differential expression analysis.
### `--input samples.csv`
Alternatively, the user may wish to provide a CSV file containing the absolute paths to input fastq/bam files.
The headers of the CSV file must be: `Sample_ID,Read1,Read2,Bam`.
> This approach is recommended for most real life situations, where in-house sequencing facilities file naming convention requires the user to manually match file names to metadata. The below input files use `TCGA` identifiers as proof of concept.
Valid examples for fastq/bam input data in a CSV file is given below:
| Sample_ID | Read1 | Read2 | Bam |
| ---------------- | :----------------------------------------------------------- | ------------------------------------------------------------ | ---- |
| TCGA-EJ-7783-11A | /data/f4c1b2b1-ba1f-4355-a1ac-3e952cf351a5_gdc_realn_rehead_R1.fastq.gz | /data/f4c1b2b1-ba1f-4355-a1ac-3e952cf351a5_gdc_realn_rehead_R2.fastq.gz | NA |
| TCGA-G9-6365-11A | /data/8a36555b-9e27-40ee-a8df-4b15d6580a02_gdc_realn_rehead_R1.fastq.gz | /data/8a36555b-9e27-40ee-a8df-4b15d6580a02_gdc_realn_rehead_R2.fastq.gz | NA |
| TCGA-EJ-7782-11A | /data/8b3d4a3d-2bfa-48f8-b31f-901f49a5bf6b_gdc_realn_rehead_R1.fastq.gz | /data/8b3d4a3d-2bfa-48f8-b31f-901f49a5bf6b_gdc_realn_rehead_R2.fastq.gz | NA |
| TCGA-CH-5772-01A | /data/b6546f66-3c13-4390-9643-d1fb3d660a2f_gdc_realn_rehead_R1.fastq.gz | /data/b6546f66-3c13-4390-9643-d1fb3d660a2f_gdc_realn_rehead_R2.fastq.gz | NA |
| TCGA-EJ-5518-01A | /data/afbbc370-5970-43d3-b9f8-f40f8e649bb6_gdc_realn_rehead_R1.fastq.gz | /data/afbbc370-5970-43d3-b9f8-f40f8e649bb6_gdc_realn_rehead_R2.fastq.gz | NA |
| TCGA-KK-A8I4-01A | /data/81254692-ee1e-4985-bd0a-4929eed4c620_gdc_realn_rehead_R1.fastq.gz | /data/81254692-ee1e-4985-bd0a-4929eed4c620_gdc_realn_rehead_R2.fastq.gz | NA |
***
| Sample_ID | Read1 | Read2 | Bam |
| :--------------- | ----- | ----- | :----------------------------------------------------------- |
| TCGA-EJ-7783-11A | NA | NA | /data/f4c1b2b1-ba1f-4355-a1ac-3e952cf351a5_gdc_realn_rehead.bam |
| TCGA-G9-6365-11A | NA | NA | /data/8a36555b-9e27-40ee-a8df-4b15d6580a02_gdc_realn_rehead.bam |
| TCGA-EJ-7782-11A | NA | NA | /data/8b3d4a3d-2bfa-48f8-b31f-901f49a5bf6b_gdc_realn_rehead.bam |
| TCGA-CH-5772-01A | NA | NA | /data/b6546f66-3c13-4390-9643-d1fb3d660a2f_gdc_realn_rehead.bam |
| TCGA-EJ-5518-01A | NA | NA | /data/afbbc370-5970-43d3-b9f8-f40f8e649bb6_gdc_realn_rehead.bam |
| TCGA-KK-A8I4-01A | NA | NA | /data/81254692-ee1e-4985-bd0a-4929eed4c620_gdc_realn_rehead.bam |
> Do not leave any cell empty in the CSV file.
### `--phenotype`
When running the differential expression analysis module, an input `phenotype.csv` file is required to specify levels for `DESeq2`. At a minimum, the user must supply one column of levels for `DESeq2` which **must be called condition**. This should be the primary contrast of interest in your experiment (e.g case vs. control). If additional columns are supplied to the phenotype file, they will be controlled for in the linear mixed model. A brief proof of concept is given below in R notation:
```R
colnames(phenotype)
[1] 'Sample_ID' 'condition'
print(dds$design)
[1] ' ~ condition'
```
```R
colnames(phenotype)
[1] 'Sample_ID' 'condition' 'replicates' 'location'
print(dds$design)
[1] ' ~ location + replicates + condition'
```
It is recommended to use an input CSV file in conjunction with your phenotype file as the `Sample_ID` column **must match** the first column of the `phenotype.csv` file.
A valid example of a `phenotype.csv` file (matching the TCGA example input CSV file above) is given below:
| Sample_ID | condition |
| ---------------- | --------- |
| TCGA-EJ-7783-11A | control |
| TCGA-G9-6365-11A | control |
| TCGA-EJ-7782-11A | control |
| TCGA-CH-5772-01A | tumor |
| TCGA-EJ-5518-01A | tumor |
| TCGA-KK-A8I4-01A | tumor |
## Analysis modules
`nf-core/circrna` provides 3 analysis modules to the user:
1. circRNA quantification & annotation.
2. miRNA target prediction.
3. Differential circRNA expression analysis.
### circRNA discovery
The core module of `nf-core/circrna`, the user can utilise the most popular circRNA quantification tools to fully characterise the circRNA profile in samples. Currently, supported tools include `CIRCexplorer2`, `circRNA finder`, `CIRIquant`, `DCC`, `find circ` , `MapSplice` & `Segemehl` however, the authors of `nf-core/circrna` welcome contributions from authors of novel quantification tools to keep the workflow current.
By default, `nf-core/circrna` runs the circRNA discovery analysis module.
```console
nextflow run nf-core/circrna \
-profile <docker/singularity/podman/institute> \
--genome 'GRCh37' \
--input 'samples.csv' \
--input_type 'fastq' \
--module 'circrna_discovery'
```
To view the outputs of the module, please see the output [documentation](https://nf-co.re/circrna/dev/output#circrna-quantification).
> Please note that this module must be included for every run of the workflow
#### Tool selection
The user may use one, all or any combination of circRNA quantification tools listed above in the analysis. To select which tools to use for the analysis, specify the `--tool` parameter in the configuration profile or pass it via the command line when running the workflow:
```console
nextflow run nf-core/circrna \
-profile <docker/singularity/podman/institute> \
--genome 'GRCh37' \
--input 'samples.csv' \
--input_type 'fastq' \
--module 'circrna_discovery' \
--tool 'ciriquant, dcc, find_circ'
```
> When providing multiple tools, separate each entry with a comma.
#### circRNA filtering
`nf-core/circrna` offers robust filtering of each called circRNA to reduce the number of spurious calls within the dataset.
##### BSJ reads
The user can specify the minimum number of reads spanning the back-splice junction site required for a circRNA to be considered for further analysis. circRNAs with counts below this value will be filtered to remove from the results.
To apply this filtering method, specify the `--bsj_reads` parameter in the configuration profile or pass it via the command line when running the workflow:
```console
nextflow run nf-core/circrna \
-profile <docker/singularity/podman/institute> \
--genome 'GRCh37' \
--input 'samples.csv' \
--input_type 'fastq' \
--phenotype 'phenotype.csv' \
--module 'circrna_discovery' \
--tool 'ciriquant, dcc, find_circ' \
--bsj_reads 2
```
Disable the filter by setting the value to 0.
##### Multiple tool filtering
When more than one tool has been provided using the `--tool` parameter, the user can specify the minimum number of tools circRNAs must be called by using `--tool_filter`. Setting this parameter to 0 or 1 will result in the union being output, i.e no filtering is applied. Setting this parameter to 2 will output circRNAs that have been called by at least 2 quantification tools and so on.
> The integer provided to the parameter must be less than or equal to the number of quantification tools provided to `--tool`.
To apply this filtering method, specify the `--tool_filter` parameter in the configuration profile or pass it via the command line when running the workflow:
```console
nextflow run nf-core/circrna \
-profile <docker/singularity/podman/institute> \
--genome 'GRCh37' \
--input 'samples.csv' \
--input_type 'fastq' \
--module 'circrna_discovery' \
--tool 'ciriquant, dcc, find_circ' \
--bsj_reads 2 \
--tool_filter 2
```
> This filtering method is reflected in the circRNA count matrix. Per tool circRNA annotations are subject to back-splice read filtering only.
### miRNA prediction
The second module of `nf-core/circrna`, `mirna_prediction` analyses the mature spliced sequences of circRNAs to test for the presence of miRNA response elements using both `miRanda` and `TargetScan`. Results from both tools are consolidated and filtering methods are applied to produce robust miRNA target predictions of circRNAs in the dataset.
To invoke the module, specify the `--module` parameter via the configuration profile or pass it via the command line when running the workflow:
```console
nextflow run nf-core/circrna \
-profile <docker/singularity/podman/institute> \
--genome 'GRCh37' \
--input 'samples.csv' \
--input_type 'fastq' \
--module 'circrna_discovery, mirna_prediction'
```
To view the outputs of the module, please see the output [documentation](https://nf-co.re/circrna/dev/output#mirna-prediction).
### Differential circRNA analysis
The third and final module of `nf-core/circrna` performs differential expression analysis of circRNAs, returning `DESeq2` result outputs, plots and diagnostic plots for the user. In order to run this module, it is essential that your `phenotype.csv` file is in the correct format - please refer to the input [specifications](https://nf-co.re/circrna/dev/usage#differential-expression-analysis).
To invoke the module, specify the `--module` parameter via the configuration profile or pass it via the command line when running the workflow:
```console
nextflow run nf-core/circrna \
-profile <docker/singularity/podman/institute> \
--genome 'GRCh37' \
--input 'samples.csv' \
--input_type 'fastq' \
--phenotype 'phenotype.csv' \
--module 'circrna_discovery, differential_expression'
```
To view the outputs of the module, please see the output [documentation](https://nf-co.re/circrna/dev/output#differential-expression-analysis).
## Core Nextflow arguments
> **NB:** These options are part of Nextflow and use a _single_ hyphen (pipeline parameters use a double-hyphen).
### `-profile`
Use this parameter to choose a configuration profile. Profiles can give configuration presets for different compute environments.
Several generic profiles are bundled with the pipeline which instruct the pipeline to use software packaged using different methods (Docker, Singularity, Podman, Shifter, Charliecloud, Conda) - see below.
> We highly recommend the use of Docker or Singularity containers for full pipeline reproducibility, however when this is not possible, Conda is also supported.
The pipeline also dynamically loads configurations from [https://github.com/nf-core/configs](https://github.com/nf-core/configs) when it runs, making multiple config profiles for various institutional clusters available at run time. For more information and to see if your system is available in these configs please see the [nf-core/configs documentation](https://github.com/nf-core/configs#documentation).
Note that multiple profiles can be loaded, for example: `-profile test,docker` - the order of arguments is important!
They are loaded in sequence, so later profiles can overwrite earlier profiles.
If `-profile` is not specified, the pipeline will run locally and expect all software to be installed and available on the `PATH`. This is _not_ recommended.
* `docker`
* A generic configuration profile to be used with [Docker](https://docker.com/)
* Pulls software from Docker Hub: [`nfcore/circrna`](https://hub.docker.com/r/nfcore/circrna/)
* `singularity`
* A generic configuration profile to be used with [Singularity](https://sylabs.io/docs/)
* Pulls software from Docker Hub: [`nfcore/circrna`](https://hub.docker.com/r/nfcore/circrna/)
* `podman`
* A generic configuration profile to be used with [Podman](https://podman.io/)
* Pulls software from Docker Hub: [`nfcore/circrna`](https://hub.docker.com/r/nfcore/circrna/)
* `shifter`
* A generic configuration profile to be used with [Shifter](https://nersc.gitlab.io/development/shifter/how-to-use/)
* Pulls software from Docker Hub: [`nfcore/circrna`](https://hub.docker.com/r/nfcore/circrna/)
* `charliecloud`
* A generic configuration profile to be used with [Charliecloud](https://hpc.github.io/charliecloud/)
* Pulls software from Docker Hub: [`nfcore/circrna`](https://hub.docker.com/r/nfcore/circrna/)
* `conda`
* Please only use Conda as a last resort i.e. when it's not possible to run the pipeline with Docker, Singularity, Podman, Shifter or Charliecloud.
* A generic configuration profile to be used with [Conda](https://conda.io/docs/)
* Pulls most software from [Bioconda](https://bioconda.github.io/)
* `test`
* A profile with a complete configuration for automated testing
* Includes links to test data so needs no other parameters
### `-resume`
Specify this when restarting a pipeline. Nextflow will used cached results from any pipeline steps where the inputs are the same, continuing from where it got to previously.
You can also supply a run name to resume a specific run: `-resume [run-name]`. Use the `nextflow log` command to show previous run names.
### `-c`
Specify the path to a specific config file (this is a core Nextflow command). See the [nf-core website documentation](https://nf-co.re/usage/configuration) for more information.
#### Custom resource requests
Each step in the pipeline has a default set of requirements for number of CPUs, memory and time. For most of the steps in the pipeline, if the job exits with an error code of `143` (exceeded requested resources) it will automatically resubmit with higher requests (2 x original, then 3 x original). If it still fails after three times then the pipeline is stopped.
Whilst these default requirements will hopefully work for most people with most data, you may find that you want to customise the compute resources that the pipeline requests. You can do this by creating a custom config file. For example, to give the workflow process `star` 32GB of memory, you could use the following config:
```nextflow
process {
withName: star {
memory = 32.GB
}
}
```
To find the exact name of a process you wish to modify the compute resources, check the live-status of a nextflow run displayed on your terminal or check the nextflow error for a line like so: `Error executing process > 'bwa'`. In this case the name to specify in the custom config file is `bwa`.
See the main [Nextflow documentation](https://www.nextflow.io/docs/latest/config.html) for more information.
If you are likely to be running `nf-core` pipelines regularly it may be a good idea to request that your custom config file is uploaded to the `nf-core/configs` git repository. Before you do this please can you test that the config file works with your pipeline of choice using the `-c` parameter (see definition above). You can then create a pull request to the `nf-core/configs` repository with the addition of your config file, associated documentation file (see examples in [`nf-core/configs/docs`](https://github.com/nf-core/configs/tree/master/docs)), and amending [`nfcore_custom.config`](https://github.com/nf-core/configs/blob/master/nfcore_custom.config) to include your custom profile.
If you have any questions or issues please send us a message on [Slack](https://nf-co.re/join/slack) on the [`#configs` channel](https://nfcore.slack.com/channels/configs).
### Running in the background
Nextflow handles job submissions and supervises the running jobs. The Nextflow process must run until the pipeline is finished.
The Nextflow `-bg` flag launches Nextflow in the background, detached from your terminal so that the workflow does not stop if you log out of your session. The logs are saved to a file.
Alternatively, you can use `screen` / `tmux` or similar tool to create a detached session which you can log back into at a later time.
Some HPC setups also allow you to run nextflow within a cluster job submitted your job scheduler (from where it submits more jobs).
#### Nextflow memory requirements
In some cases, the Nextflow Java virtual machines can start to request a large amount of memory.
We recommend adding the following line to your environment to limit this (typically in `~/.bashrc` or `~./bash_profile`):
```console
NXF_OPTS='-Xms1g -Xmx4g'
```
| 54.472779 | 696 | 0.736153 | eng_Latn | 0.98588 |
08daec5406d87da929cc8ef6ffb6f87bb6405227 | 8,155 | md | Markdown | _posts/2018-12-02-react-native-modules-bridge-communication-activitiy-fragment-android.md | chicio/old.chicio.github.io | 3aadcc8ed190a53dc7ca643b3f008de7ab1302e3 | [
"MIT"
] | null | null | null | _posts/2018-12-02-react-native-modules-bridge-communication-activitiy-fragment-android.md | chicio/old.chicio.github.io | 3aadcc8ed190a53dc7ca643b3f008de7ab1302e3 | [
"MIT"
] | null | null | null | _posts/2018-12-02-react-native-modules-bridge-communication-activitiy-fragment-android.md | chicio/old.chicio.github.io | 3aadcc8ed190a53dc7ca643b3f008de7ab1302e3 | [
"MIT"
] | null | null | null | ---
layout: post
title: "React Native: a simple architecture for Native Modules communication with your Activities and Fragments on Android"
description: "In this post I will talk about a simple architecture for communication between React Native Native
modules (aka bridges) and your native code on Android."
date: 2018-12-02
image: /assets/images/posts/native-modules-communication-android.jpg
tags: [react native, javascript, swift, objective-c, ios, apple, android, java, mobile application development]
comments: true
math: false
seo:
- type: "BlogPosting"
authors: [felice_giovinazzo, fabrizio_duroni]
---
*In this post I will talk about a simple architecture for communication between React Native Native modules (aka bridges) and your native code on Android.*
---
Sometimes a React Native app needs to access to the native API or needs/want to call some existing native code you already have in place. This is why Native Modules have been created for both [iOS](https://facebook.github.io/react-native/docs/native-modules-ios) and [Android](https://facebook.github.io/react-native/docs/native-modules-android). Sometimes when you integrated React Native in an existing app, you will want to be able let your Native Modules bridges communicate with your activities and fragment, especially the ones that contain the React Native View. In this post I will show you an architecture to put in place this communication on Android, that will be compatible with all the features of React Native (for example it will work also with the live reload functionality). This is an architecture I put in place with my colleague [Felice Giovinazzo](https://www.linkedin.com/in/felice-giovinazzo-17277b55/) in our apps at [lastminute.com group](https://lmgroup.lastminute.com/ "lastminute.com"). Felice is a senior fullstack developer with many years of experiences (he is the "lastminute" veteran of our team) and a computer graphics enthusiast like me :revolving_hearts::sparkling_heart:.
To show you this architecture I will create a simple app that show a React Native screen as a modal. I will then implement the close button functionality by calling a native module from the `onPress` on a React Native button.
Below you can see the final result.
{% include youtube.html videoId="MdNqDQHNjRc" %}
The architecture we put in place is based on a **Event Bus** in which the Native Modules bridges notify the subscribed Activities/Fragments of the actions to be executed. So each one of them is subscribed to specific events to which they are able to respond. We choose [Otto](https://square.github.io/otto/) as event bus library (we don't want to reinvent the wheel :bomb:). Let's start from the `MainActivity`. In it there's only a button with an action to start the React Native modal activity.
```java
public class MainActivity extends AppCompatActivity {
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
}
public void showReactNativeModal(View view) {
startActivity(new Intent(this, ReactNativeModalActivity.class));
}
}
```
The `ReactNativeModalActivity` is an `Activity` with the setup needed to launch a React Native context. This activity is registered to the event bus to be able to listen to events from the Native Modules bridges. In this case the activity is subscribed to just one event with the method `@Subscribe public void close(ReactNativeModalBridge.CloseModalEvent event)`.
```java
public class ReactNativeModalActivity extends AppCompatActivity implements DefaultHardwareBackBtnHandler {
private final int OVERLAY_PERMISSION_REQ_CODE = 8762;
private ReactRootView mReactRootView;
private ReactInstanceManager mReactInstanceManager;
@Override
protected void onCreate(@Nullable Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
registerToReactEvents();
askReactDrawingPermission();
setupReactView();
}
@Override
protected void onDestroy() {
super.onDestroy();
unregisterToReactEvents();
if (mReactInstanceManager != null) {
mReactInstanceManager.onHostDestroy(this);
}
if (mReactRootView != null) {
mReactRootView.unmountReactApplication();
}
}
private void registerToReactEvents() {
((NativeModulesApplication)getApplication())
.getBus()
.register(this);
}
private void unregisterToReactEvents() {
((NativeModulesApplication)getApplication())
.getBus()
.unregister(this);
}
@Subscribe
public void close(ReactNativeModalBridge.CloseModalEvent event) {
finish();
}
private void askReactDrawingPermission() {
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {
if (!Settings.canDrawOverlays(this)) {
Intent intent = new Intent(
Settings.ACTION_MANAGE_OVERLAY_PERMISSION,
Uri.parse("package:" + getPackageName())
);
startActivityForResult(intent, OVERLAY_PERMISSION_REQ_CODE);
}
}
}
private void setupReactView() {
...
}
...
}
```
Now let's have a look at Native Module created for the app, the `ReactNativeModalBridge`. In this bridge there just one react method, `closeModal`. This is the one called from the React Native JS side. In this method we are sending an event of type `CloseModalEvent`. The `ReactNativeModalActivity` is subscribed to this type of event (as we saw above). This basically means that when the `closeModal` bridge method will be called from the React Native Javascript code a new event `CloseModalEvent` is generated and the `ReactNativeModalActivity` will execute the subscribed method defined in it. We have all setup to have our Native Modules communication with our activities (and eventually fragment with the same approach if we need them :neckbeard:).
```java
public class ReactNativeModalBridge extends ReactContextBaseJavaModule {
public ReactNativeModalBridge(ReactApplicationContext reactContext) {
super(reactContext);
}
@Override
public String getName() {
return this.getClass().getSimpleName();
}
@ReactMethod
public void closeModal() {
final Activity currentActivity = getCurrentActivity();
currentActivity.runOnUiThread(new Runnable() {
@Override
public void run() {
((NativeModulesApplication) currentActivity.getApplication())
.getBus()
.post(new CloseModalEvent());
}
});
}
public class CloseModalEvent { }
}
```
Now it's time to see the javascript code. Below you can see the `ReactNativeModal` component. Inside this component there is a call to the native module `NativeModules.ReactNativeModalBridge.closeModal()` described above. In this way the modal will be closed directly from the native side.
```jsx
class ReactNativeModal extends React.Component {
render() {
return (
<View style={styles.container}>
<Text style={styles.hello}>Hello modal!</Text>
<Text style={styles.message}>
I'm a react native component. Click on the button to close me using native function.
</Text>
<Button
title={"Close me"}
onPress={() => NativeModules.ReactNativeModalBridge.closeModal()}
/>
</View>
);
}
}
```
That's all for our native modules communication architecture on Android. You can find the complete example in [this github repository](https://github.com/chicio/React-Native-Native-Modules-Communication). If you want to know how we managed the same problem on the iOS platform :apple::iphone::heartbeat: you can read [my other post about the same topic](/2018/12/03/react-native-modules-bridge-communication-uiviewcontroller-ios.html).
| 49.72561 | 1,211 | 0.710975 | eng_Latn | 0.941095 |
08db0e18f51302fa0442c4cd63dd893b6a2cb7d2 | 2,967 | md | Markdown | articles/azure-monitor/app/status-monitor-v2-api-get-config.md | decarli/azure-docs.pt-br | 20bc383d005c11e7b7dc7b7b0777fc0de1262ffc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-monitor/app/status-monitor-v2-api-get-config.md | decarli/azure-docs.pt-br | 20bc383d005c11e7b7dc7b7b0777fc0de1262ffc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-monitor/app/status-monitor-v2-api-get-config.md | decarli/azure-docs.pt-br | 20bc383d005c11e7b7dc7b7b0777fc0de1262ffc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Referência da API do agente do insights Aplicativo Azure
description: Referência de API do agente Application Insights. Get-ApplicationInsightsMonitoringConfig. Monitore o desempenho do site sem reimplantar o site. Funciona com aplicativos Web ASP.NET hospedados localmente, em VMs ou no Azure.
ms.service: azure-monitor
ms.subservice: application-insights
ms.topic: conceptual
author: TimothyMothra
ms.author: tilee
ms.date: 04/23/2019
ms.openlocfilehash: 91e7bcbe79dfde8bbd4011748b40b692015af1c2
ms.sourcegitcommit: 5acd8f33a5adce3f5ded20dff2a7a48a07be8672
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 10/24/2019
ms.locfileid: "72899745"
---
# <a name="application-insights-agent-api-get-applicationinsightsmonitoringconfig"></a>API do agente de Application Insights: Get-ApplicationInsightsMonitoringConfig
Este artigo descreve um cmdlet que é membro do [módulo AZ. ApplicationMonitor do PowerShell](https://www.powershellgallery.com/packages/Az.ApplicationMonitor/).
## <a name="description"></a>Descrição
Obtém o arquivo de configuração e imprime os valores no console.
> [!IMPORTANT]
> Este cmdlet requer uma sessão do PowerShell com permissões de administrador.
## <a name="examples"></a>Exemplos
```powershell
PS C:\> Get-ApplicationInsightsMonitoringConfig
```
## <a name="parameters"></a>parâmetros
Nenhum parâmetro é necessário.
## <a name="output"></a>Saída
#### <a name="example-output-from-reading-the-config-file"></a>Exemplo de saída da leitura do arquivo de configuração
```
RedfieldConfiguration:
Filters:
0)InstrumentationKey: AppFilter: WebAppExclude MachineFilter: .*
1)InstrumentationKey: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx2 AppFilter: WebAppTwo MachineFilter: .*
2)InstrumentationKey: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxdefault AppFilter: .* MachineFilter: .*
```
## <a name="next-steps"></a>Próximos passos
Exiba sua telemetria:
- [Explore as métricas](../../azure-monitor/app/metrics-explorer.md) para monitorar o desempenho e o uso.
- [Pesquise eventos e logs](../../azure-monitor/app/diagnostic-search.md) para diagnosticar problemas.
- Use a [análise](../../azure-monitor/app/analytics.md) para consultas mais avançadas.
- [Crie painéis](../../azure-monitor/app/overview-dashboard.md).
Adicione mais telemetria:
- [Crie testes da Web](monitor-web-app-availability.md) para garantir que seu site permaneça ativo.
- [Adicione telemetria de cliente Web](../../azure-monitor/app/javascript.md) para ver exceções do código de página da Web e para habilitar chamadas de rastreamento.
- [Adicione o SDK do Application insights ao seu código](../../azure-monitor/app/asp-net.md) para que você possa inserir chamadas de rastreamento e log.
Faça mais com Application Insights agente:
- Use nosso guia para [solucionar problemas](status-monitor-v2-troubleshoot.md) do Application insights Agent.
- Faça alterações na configuração usando o cmdlet [set config](status-monitor-v2-api-set-config.md) .
| 44.283582 | 237 | 0.780249 | por_Latn | 0.883633 |
08db1b7e76a74146dccb9ca9f1c57a1837496f82 | 1,155 | md | Markdown | README.md | am-trinity/angular-helpers | 3b58cc1e81dcf1b0faac580f08de5238e8419ceb | [
"MIT"
] | null | null | null | README.md | am-trinity/angular-helpers | 3b58cc1e81dcf1b0faac580f08de5238e8419ceb | [
"MIT"
] | null | null | null | README.md | am-trinity/angular-helpers | 3b58cc1e81dcf1b0faac580f08de5238e8419ceb | [
"MIT"
] | null | null | null | # angular-helpers
* Reactive forms: https://angular.io/guide/reactive-forms
* Dynamic form: https://angular.io/guide/dynamic-form
* Dynamic component loading: https://angular.io/guide/dynamic-component-loader
```typescript
import { Component, OnInit } from '@angular/core';
import { DialogService } from './dialog/dialog.service';
@Component({
selector: 'app-dummy',
template: `<p>Dummy</p>`
}) export class DummyComponent { }
@Component({
selector: 'app-example',
template: `
<app-form [fields]="formFields"></app-form>
<button (click)="handleButtonClick(event)">Show dialog</button>
<app-dialog [dialogID]="dialogID"></app-dialog>
`
})
export class ExampleComponent implements OnInit {
dialogID = 'testDialog';
formFields = [
{
type: 'string',
name: 'username',
label: 'User name',
value: 'myname',
order: 1
}
];
constructor(private dialog: DialogService) { }
ngOnInit() { }
handleButtonClick(event) {
this.dialog.set(this.dialogID, 'component', DummyComponent);
this.dialog.set(this.dialogID, 'params', {});
this.dialog.show(this.dialogID);
}
}
```
| 21.792453 | 78 | 0.658009 | kor_Hang | 0.284888 |
08db71a102b22a8971fd385a7d2e13fcf249e866 | 789 | md | Markdown | extensions/owner/README.md | darkleaf/cckit | bfba2a6c9d535ed1391f83c5150ffdbfc07623f4 | [
"MIT"
] | 1 | 2019-09-17T14:47:59.000Z | 2019-09-17T14:47:59.000Z | extensions/owner/README.md | darkleaf/cckit | bfba2a6c9d535ed1391f83c5150ffdbfc07623f4 | [
"MIT"
] | null | null | null | extensions/owner/README.md | darkleaf/cckit | bfba2a6c9d535ed1391f83c5150ffdbfc07623f4 | [
"MIT"
] | 2 | 2019-07-14T12:24:40.000Z | 2019-08-28T13:08:17.000Z | # Owner - access control hyperledger fabric chaincode extension
In many cases during chaincode instantiating we need to define permissions for chaincode functions -
"who is allowed to do this thing", incredibly important in the world of smart contracts, but in many examples access control
implemented at the application level but not at the blockchain layer.
The most common and basic form of access control is the concept of `ownership`: there's one account (combination
of MSP and certificate identifiers) that is the owner and can do administrative tasks on contracts. This
approach is perfectly reasonable for contracts that only have a single administrative user.
CCKit provides `owner` extension for implementing ownership and access control in Hyperledger Fabric chaincodes. | 71.727273 | 125 | 0.818758 | eng_Latn | 0.999456 |
08dc99d616df586572b6114f65743c191355ac5b | 593 | md | Markdown | src/api/mock/README.md | xuae/vue-admin-ant | bf8557058afba52839e78e9bb4f13b3db39bce13 | [
"MIT"
] | 5 | 2020-04-19T11:47:12.000Z | 2021-12-12T20:01:14.000Z | src/api/mock/README.md | xuae/vue-admin-ant | bf8557058afba52839e78e9bb4f13b3db39bce13 | [
"MIT"
] | 2 | 2020-08-19T12:34:09.000Z | 2020-08-19T12:34:09.000Z | src/api/mock/README.md | xuae/vue-admin-ant | bf8557058afba52839e78e9bb4f13b3db39bce13 | [
"MIT"
] | 2 | 2020-03-24T17:24:27.000Z | 2020-04-02T16:57:44.000Z | # Mock 规范
- <a href='#directory'>文件结构</a>
- <a href='#standard'>代码规范</a>
## <h2 id='directory'>文件结构</h2>
```
├─account.js #账号类接口模拟数据
├─index.js #mock数据合集，启动mock配置
├─mock-server.js #启动mock server配置
├─util.js #mock工具类
└─README.md #Mock文件说明
```
## <h2 id='standard'>代码规范</h2>
- 文件名都采用 kebab-case 的命名方式
- 文件名与 api 文件夹下的 ts 文件对应
- xxx.js 模拟数据文件模板
``` javascript
import Util from './util';
export default[
Util.request({
uri: '',
method: '',
response: config => {},
}),
]
```
| 16.942857 | 47 | 0.509275 | yue_Hant | 0.146863 |
08dd3c3f07917a01dfbc41295c28c6bdc2f93312 | 1,935 | md | Markdown | README.md | darethas/oktad | 6213f1abb7e2a06554e20d64310dd9c573a0ea6d | [
"Apache-2.0"
] | null | null | null | README.md | darethas/oktad | 6213f1abb7e2a06554e20d64310dd9c573a0ea6d | [
"Apache-2.0"
] | null | null | null | README.md | darethas/oktad | 6213f1abb7e2a06554e20d64310dd9c573a0ea6d | [
"Apache-2.0"
] | null | null | null | # oktad
[okta-aws](https://github.com/RedVentures/okta-aws), but in go. This program authenticates with Okta and then assumes role twice in Amazon.
## Installation
Grab a binary for your OS from the [latest release](https://github.com/RedVentures/oktad/releases/latest), and put it somewhere in your PATH. Only supports Linux and OSX for now!
If you're on OSX like me, this might be all you need...
```sh
curl -L -o /usr/local/bin/oktad https://github.com/RedVentures/oktad/releases/download/`curl -v 'https://github.com/RedVentures/oktad/releases/latest' 2>&1 | grep Location | grep -E -o 'v[0-9]+\.[0-9]+\.[0-9]+'`/oktad-darwin-amd64 && chmod +x /usr/local/bin/oktad
```
## Setup
First, create an `~/.okta-aws/config` file with your Ookta base URL and app URL, like below:
```
[okta]
baseUrl=https://mycompany.okta.com/
appUrl=https://mycompany.okta.com/app/YOUR_APP/OKTA_MAGIC/sso/saml
```
Third, set up an AWS CLI config file. You need to create `~/.aws/config` and fill it with a profile containing the ARN for a role you ultimately want to get temporary credentials for. This file might look like the following:
```
[default]
output = json
region = us-east-1
[profile my_subaccount]
role_arn = arn:aws:iam::MY_ACCOUNT_ID:role/wizards
```
With those things set up, you should be able to run `oktad my_subaccount -- [command]` to run whatever `[command]` is with a set of temporary credentials from Amazon.
## Usage
```sh
$ oktad [AWS profile] -- [command]
```
for example
```sh
$ oktad production -- aws ec2 describe-instances
```
## Debugging
Login didn't work? Launch this program with `DEBUG=oktad*` in your environment for more debugging info:
```sh
$ DEBUG=oktad* oktad production -- aws ec2 describe-instances
```
## Contributors
- Dimitrios Arethas [darethas@redventures.com]
- Thomas Hopkins [thopkins@redventures.com]
- Todd Lunter [@tlunter]
- Gildas Le Nadan [@endemics]
- Lee Standen [@lstanden]
| 29.318182 | 263 | 0.725065 | eng_Latn | 0.842164 |
08de83fea22f52bb99be2b34d62622ae0dae271c | 653 | md | Markdown | _posts/2019-09-12-linux.md | middaywords/middaywords.github.io | 0ecfdca344b28793d3ca431437e46b62918fec57 | [
"MIT"
] | null | null | null | _posts/2019-09-12-linux.md | middaywords/middaywords.github.io | 0ecfdca344b28793d3ca431437e46b62918fec57 | [
"MIT"
] | null | null | null | _posts/2019-09-12-linux.md | middaywords/middaywords.github.io | 0ecfdca344b28793d3ca431437e46b62918fec57 | [
"MIT"
] | null | null | null | ---
title: ubuntu install
date: 2019-09-12
permalink: /posts/2019/09/ubuntuinstall/
tags:
- opss
---
#### 配置信息
1. msi gf63:
- 8300H
- 16G mem
- 128G SSD + 1T HDD
- GTX 1050Ti
2. Rufus 制作镜像
3. 长按delete进入bios，关闭secure boot，长按F11选择启动方式，选择u盘启动
4. 坑1
1. 进入grub后不能直接install， 会卡死
2. 解决方案：按e修改启动参数，`quiet splash --- `改为 `quiet splash --- nomodeset`，屏蔽NVIDIA独显，F10进入ubuntu试用系统，可以开始安装。此时分辨率是800*600，没法改
3. 注意设置四个分区
1. `/` 主分区， 30G
2. `/boot` 放在SSD上，可能可以加速，400M
3. `/home` 70G
4. `swap` 交换内存区
5. 坑2：
1. 进入安装成功的系统后需要在 soft&update 里更新 drivers 中的NVIDIA驱动。
2. 但这个时候还是800*600分辨率
3. 需要在grub界面将之前的`nomodeset`删除 | 22.517241 | 122 | 0.658499 | yue_Hant | 0.637437 |
08dea91ffe04d8d294d7f4d87d71a7b23bb0bfeb | 2,895 | md | Markdown | docs/framework/wcf/feature-details/interoperable-object-references.md | lolisia/docs.ko-kr | 3b0f7390b761296bd1d0bbbaed9d4437394bf983 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wcf/feature-details/interoperable-object-references.md | lolisia/docs.ko-kr | 3b0f7390b761296bd1d0bbbaed9d4437394bf983 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wcf/feature-details/interoperable-object-references.md | lolisia/docs.ko-kr | 3b0f7390b761296bd1d0bbbaed9d4437394bf983 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 상호 운용 가능한 개체 참조
ms.date: 04/15/2019
ms.assetid: cb8da4c8-08ca-4220-a16b-e04c8f527f1b
ms.openlocfilehash: 0927f217a1666f8f27ca9c3e68f80a96b9c0f2b1
ms.sourcegitcommit: 7588136e355e10cbc2582f389c90c127363c02a5
ms.translationtype: MT
ms.contentlocale: ko-KR
ms.lasthandoff: 03/12/2020
ms.locfileid: "79184701"
---
# <a name="interoperable-object-references"></a>상호 운용 가능한 개체 참조
기본적으로 개체를 값별로 <xref:System.Runtime.Serialization.DataContractSerializer> 직렬화합니다. 속성을 <xref:System.Runtime.Serialization.DataContractAttribute.IsReference%2A> 사용하여 개체를 직렬화할 때 데이터 계약 serializer에 개체 참조를 보존하도록 지시할 수 있습니다.
## <a name="generated-xml"></a>생성된 XML
예를 들어 다음과 같은 개체를 살펴보세요.
```csharp
[DataContract]
public class X
{
SomeClass someInstance = new SomeClass();
[DataMember]
public SomeClass A = someInstance;
[DataMember]
public SomeClass B = someInstance;
}
public class SomeClass
{
}
```
<xref:System.Runtime.Serialization.DataContractSerializer.PreserveObjectReferences%2A>를 `false`(기본값)로 설정하면 다음 XML이 생성됩니다.
```xml
<X>
<A>contents of someInstance</A>
<B>contents of someInstance</B>
</X>
```
<xref:System.Runtime.Serialization.DataContractSerializer.PreserveObjectReferences%2A>를 `true`로 설정하면 다음 XML이 생성됩니다.
```xml
<X>
<A id="1">contents of someInstance</A>
<B ref="1"></B>
</X>
```
그러나 <xref:System.Runtime.Serialization.XsdDataContractExporter> `id` `preserveObjectReferences` 속성이 로 설정된 `ref` 경우에도 해당 스키마의 및 특성을 설명하지 `true`않습니다.
## <a name="using-isreference"></a>IsReference 사용
이를 설명하는 스키마에 따라 유효한 개체 참조 정보를 생성하려면 형식에 특성을 <xref:System.Runtime.Serialization.DataContractAttribute> 적용하고 <xref:System.Runtime.Serialization.DataContractAttribute.IsReference%2A> 플래그를 `true`로 설정합니다. 다음 예제에서는 다음 `X` 예제에서 클래스를 `IsReference`추가 하 여 클래스를 수정 합니다.
```csharp
[DataContract(IsReference=true)]
public class X
{
SomeClass someInstance = new SomeClass();
[DataMember]
public SomeClass A = someInstance;
[DataMember]
public SomeClass B = someInstance;
}
public class SomeClass
{
}
````
생성되는 XML은 다음과 같습니다.
```xml
<X>
<A id="1">
<Value>contents of A</Value>
</A>
<B ref="1"></B>
</X>
```
`IsReference`를 사용하면 메시지 라운드트립이 준수됩니다. 스키마에서 형식이 생성될 때 해당 형식의 XML 출력이 원래 가정된 스키마와 반드시 호환되는 것은 아닙니다. 즉, `id` 및 `ref` 특성이 serialize되었더라도 원래 스키마 때문에 이러한 특성 또는 모든 특성이 XML에서 발생하지 않았을 수 있습니다. 데이터 `IsReference` 멤버에 적용하면 멤버는 라운드 트립시 *참조 가능한* 것으로 계속 인식됩니다.
## <a name="see-also"></a>참고 항목
- <xref:System.Runtime.Serialization.DataContractAttribute>
- <xref:System.Runtime.Serialization.CollectionDataContractAttribute>
- <xref:System.Runtime.Serialization.DataContractAttribute.IsReference?displayProperty=nameWithType>
- <xref:System.Runtime.Serialization.CollectionDataContractAttribute.IsReference?displayProperty=nameWithType>
| 31.467391 | 261 | 0.71468 | kor_Hang | 0.996681 |
08df3bfef9fb7d348988ff0c9ad875d60df98aef | 5,988 | md | Markdown | README.md | dbrowne/rust_client | c17ff790483d139782d56ce62f0fcb2bf4911e8b | [
"MIT"
] | null | null | null | README.md | dbrowne/rust_client | c17ff790483d139782d56ce62f0fcb2bf4911e8b | [
"MIT"
] | null | null | null | README.md | dbrowne/rust_client | c17ff790483d139782d56ce62f0fcb2bf4911e8b | [
"MIT"
] | null | null | null | <!--
*** Taken from Best-README-Template:
*** https://github.com/othneildrew/Best-README-Template
*** If you have a suggestion that would make this better,
*** please fork the repo and create a pull request
*** or simply open an issue with the tag "enhancement".
*** Thanks again! Now go create something AMAZING! :D
***
***
***
*** To avoid retyping too much info. Do a search and replace for the following:
*** github_username, repo_name, twitter_handle, email, project_title, project_description
-->
<!-- PROJECT SHIELDS -->
<!--
*** I'm using markdown "reference style" links for readability.
*** Reference links are enclosed in brackets [ ] instead of parentheses ( ).
*** See the bottom of this document for the declaration of the reference variables
*** for contributors-url, forks-url, etc. This is an optional, concise syntax you may use.
*** https://www.markdownguide.org/basic-syntax/#reference-style-links
-->
[![Contributors][contributors-shield]][contributors-url]
[![Forks][forks-shield]][forks-url]
[![Stargazers][stars-shield]][stars-url]
[![Issues][issues-shield]][issues-url]
[![MIT License][license-shield]][license-url]
[![LinkedIn][linkedin-shield]][linkedin-url]
<!-- PROJECT LOGO -->
<br />
<p align="center">
<a href="https://github.com/dbrowne/rust_client.git">
<img src="images/riding.png" alt="Logo" width="80" height="80">
</a>
<h3 align="center">Rust TCP Client</h3>
<p align="center">
Sends a message on a port n times with a delay and expect a response
<br />
<br />
<br />
<a href="https://github.com/dbrowne/rust_client/issues">Report Bug</a>
<br/>
<a href="https://github.com/dbrowne/rust_client/issues">Request Feature</a>
</p>
<!-- TABLE OF CONTENTS -->
<details open="open">
<summary><h2 style="display: inline-block">Table of Contents</h2></summary>
<ol>
<li>
<a href="#about-the-project">About The Project</a>
<ul>
<li><a href="#built-with">Built With</a></li>
</ul>
</li>
<li>
<a href="#getting-started">Getting Started</a>
<ul>
<li><a href="#prerequisites">Prerequisites</a></li>
<li><a href="#installation">Installation</a></li>
</ul>
</li>
<li><a href="#usage">Usage</a></li>
<li><a href="#roadmap">Roadmap</a></li>
<li><a href="#contributing">Contributing</a></li>
<li><a href="#license">License</a></li>
<li><a href="#contact">Contact</a></li>
<li><a href="#acknowledgements">Acknowledgements</a></li>
</ol>
</details>
<!-- ABOUT THE PROJECT -->
## About The Project
A simple TCP client written in rust. Might be useful for some
### Built With
* [Rust](https://www.rust-lang.org/tools/install)
<!-- GETTING STARTED -->
## Getting Started
To get a local copy up and running follow these simple steps.
### Prerequisites
* rust
```sh
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
```
### Installation
1. Clone the repo
```sh
git clone https://github.com/dbrowne/rust_client.git
```
1. Build and run the code
```sh
cd rust_client
cargo build --release
./target/release/rust_client [OPTIONS]
```
1. Alternatively
```sh
export CLIENT_PORT='6669'
export CLIENT_HOST='somehost.com'
export CLIENT_DURATION='7'
export CLIENT_ITERATIONS='300'
export CLIENT_MESSAGE='Hey! How Judoon?'
cargo run
output::
Finished dev [unoptimized + debuginfo] target(s) in 0.02s
Running target/debug/rust_client
Using environment vars: with the following values
port: 6669
Host: somehost.com
delay duration: 7
# of Iterations: 300
Env Message to be sent: Hey! How Judoon?
<!-- USAGE EXAMPLES -->
## Usage
```sh
./target/release/rust_client -h some_host_target -p 3377 -d 0 -i 10
```
You are sending 10 messages to some_host_target on port 3377 with no delay
<!-- ROADMAP -->
## Roadmap
No real roadmap for this it is just a simple client
<!-- CONTRIBUTING -->
## Contributing
If you really want to...
1. Fork the Project
2. Create your Feature Branch (`git checkout -b feature/AmazingFeature`)
3. Commit your Changes (`git commit -m 'Add some AmazingFeature'`)
4. Push to the Branch (`git push origin feature/AmazingFeature`)
5. Open a Pull Request
<!-- LICENSE -->
## License
Distributed under the MIT License. See `LICENSE` for more information.
<!-- CONTACT -->
## Contact
Dwight J. Browne - [@dwightb2](https://twitter.com/dwightb2) - dwight[-dot-]browne[-at-]colorado[-dot-]edu
Project Link: [https://github.com/dbrowne/rust_client.git](https://github.com/dbrowne/rust_client.git)
<!-- ACKNOWLEDGEMENTS -->
## Acknowledgements
* [google](www.google.com)
* [stackoverflow](www.stackoverflow.com)
* [docs.rs](https://docs.rs/)
<!-- MARKDOWN LINKS & IMAGES -->
<!-- https://www.markdownguide.org/basic-syntax/#reference-style-links -->
[contributors-shield]: https://img.shields.io/github/contributors/dbrowne/rust_client
[contributors-url]: https://github.com/dbrowne/rust_client/graphs/contributors
[forks-shield]: https://img.shields.io/github/forks/dbrowne/rust_client
[forks-url]: https://github.com/dbrowne/rust_client/network/members
[stars-shield]: https://img.shields.io/github/stars/dbrowne/rust_client
[stars-url]: https://github.com/dbrowne/rust_client/stargazers
[issues-shield]: https://img.shields.io/github/issues/dbrowne/rust_client
[issues-url]: https://github.com/dbrowne/rust_client/issues
[license-shield]: https://img.shields.io/github/license/dbrowne/rust_client
[license-url]: https://github.com/dbrowne/rust_client/blob/master/LICENSE.txt
[linkedin-shield]: https://img.shields.io/badge/-LinkedIn-black.svg?style=for-the-badge&logo=linkedin&colorB=555
[linkedin-url]: https://linkedin.com/in/dwightbrowne | 26.972973 | 112 | 0.658317 | eng_Latn | 0.328062 |
08df7799fa7a97e1d394bcd648a1ba8b66d6869a | 1,577 | md | Markdown | docs/ado/reference/adox-api/inherittypeenum.md | Sticcia/sql-docs.it-it | 31c0db26a4a5b25b7c9f60d4ef0a9c59890f721e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/ado/reference/adox-api/inherittypeenum.md | Sticcia/sql-docs.it-it | 31c0db26a4a5b25b7c9f60d4ef0a9c59890f721e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/ado/reference/adox-api/inherittypeenum.md | Sticcia/sql-docs.it-it | 31c0db26a4a5b25b7c9f60d4ef0a9c59890f721e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: InheritTypeEnum | Microsoft Docs
ms.prod: sql
ms.prod_service: connectivity
ms.technology: connectivity
ms.custom: ''
ms.date: 01/19/2017
ms.reviewer: ''
ms.topic: conceptual
apitype: COM
f1_keywords:
- InheritTypeEnum
helpviewer_keywords:
- InheritTypeEnum enumeration [ADOX]
ms.assetid: c2f6ce79-c4b3-4d40-ac95-21025208f991
author: MightyPen
ms.author: genemi
manager: craigg
ms.openlocfilehash: 249616f2f08b8b8f6138ce13621d26c5f7af9e1e
ms.sourcegitcommit: f7fced330b64d6616aeb8766747295807c92dd41
ms.translationtype: MT
ms.contentlocale: it-IT
ms.lasthandoff: 04/23/2019
ms.locfileid: "63213342"
---
# <a name="inherittypeenum"></a>InheritTypeEnum
Specifica il modo in cui gli oggetti ereditano le autorizzazioni impostate con [SetPermissions](../../../ado/reference/adox-api/setpermissions-method-adox.md).
|Costante|Value|Descrizione|
|--------------|-----------|-----------------|
|**adInheritBoth**|3|Sia gli oggetti e gli altri contenitori contenute dall'oggetto primario ereditano la voce.|
|**adInheritContainers**|2|Altri contenitori che sono contenuti nell'oggetto primario ereditano la voce.|
|**adInheritNone**|0|Valore predefinito. Si verifica alcun ereditarietà.|
|**adInheritNoPropagate**|4|Il **adInheritObjects** e **adInheritContainers** flag non vengono propagati a una voce ereditata.|
|**adInheritObjects**|1|Gli oggetti non-contenitore nel contenitore ereditano le autorizzazioni.|
## <a name="applies-to"></a>Si applica a
[Metodo SetPermissions (ADOX)](../../../ado/reference/adox-api/setpermissions-method-adox.md)
| 40.435897 | 161 | 0.757134 | ita_Latn | 0.562488 |
08dffb873634585eaa2fb1be893dd19813adcb3d | 4,039 | md | Markdown | wdk-ddi-src/content/ehstorioctl/ni-ehstorioctl-ioctl_ehstor_device_set_queue_state.md | MikeMacelletti/windows-driver-docs-ddi | 5436c618dff46f9320544766618c9ab4bef6a35e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | wdk-ddi-src/content/ehstorioctl/ni-ehstorioctl-ioctl_ehstor_device_set_queue_state.md | MikeMacelletti/windows-driver-docs-ddi | 5436c618dff46f9320544766618c9ab4bef6a35e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | wdk-ddi-src/content/ehstorioctl/ni-ehstorioctl-ioctl_ehstor_device_set_queue_state.md | MikeMacelletti/windows-driver-docs-ddi | 5436c618dff46f9320544766618c9ab4bef6a35e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
UID: NI:ehstorioctl.IOCTL_EHSTOR_DEVICE_SET_QUEUE_STATE
title: IOCTL_EHSTOR_DEVICE_SET_QUEUE_STATE (ehstorioctl.h)
description: The IOCTL_EHSTOR_DEVICE_SET_QUEUE_STATE request is sent by silo drivers and applications to change the state of a storage device queue. IO requests in the storage device queue are held when the device is temporarily unauthorized.
old-location: storage\ioctl_ehstor_device_set_queue_state.htm
tech.root: storage
ms.assetid: 83AFAC73-39B8-442A-822E-411D08130F88
ms.date: 03/29/2018
keywords: ["IOCTL_EHSTOR_DEVICE_SET_QUEUE_STATE IOCTL"]
ms.keywords: IOCTL_EHSTOR_DEVICE_SET_QUEUE_STATE, IOCTL_EHSTOR_DEVICE_SET_QUEUE_STATE control, IOCTL_EHSTOR_DEVICE_SET_QUEUE_STATE control code [Storage Devices], ehstorioctl/IOCTL_EHSTOR_DEVICE_SET_QUEUE_STATE, storage.ioctl_ehstor_device_set_queue_state
f1_keywords:
- "ehstorioctl/IOCTL_EHSTOR_DEVICE_SET_QUEUE_STATE"
req.header: ehstorioctl.h
req.include-header: EhStorIoctl.h
req.target-type: Windows
req.target-min-winverclnt: Available starting with Windows 8
req.target-min-winversvr:
req.kmdf-ver:
req.umdf-ver:
req.ddi-compliance:
req.unicode-ansi:
req.idl:
req.max-support:
req.namespace:
req.assembly:
req.type-library:
req.lib:
req.dll:
req.irql:
topic_type:
- APIRef
- kbSyntax
api_type:
- HeaderDef
api_location:
- EhStorIoctl.h
api_name:
- IOCTL_EHSTOR_DEVICE_SET_QUEUE_STATE
product:
- Windows
targetos: Windows
req.typenames:
---
# IOCTL_EHSTOR_DEVICE_SET_QUEUE_STATE IOCTL
## -description
The <b>IOCTL_EHSTOR_DEVICE_SET_QUEUE_STATE</b> request is sent by silo drivers and applications to change the state of a storage device queue. IO requests in the storage device queue are held when the device is temporarily unauthorized.
## -ioctlparameters
### -input-buffer
The input buffer at <b>Irp->AssociatedIrp.SystemBuffer</b> contains an <b> ACT_QUEUE_STATE</b> structure. <b>ACT_QUEUE_STATE</b> is declared in <i>ehstorioctl.h</i> as the following.
<div class="code"><span codelanguage=""><table>
<tr>
<th></th>
</tr>
<tr>
<td>
<pre>typedef struct tagACT_QUEUE_STATE
{
BOOLEAN fFrozen;
} ACT_QUEUE_STATE;</pre>
</td>
</tr>
</table></span></div>
#### -fFrozen
The freeze state of the IO request queue for a storage device. If set to TRUE, the queue is frozen and all IO requests sent to the storage device are held. Otherwise, IO requests in the device queue are processed.
### -input-buffer-length
The length of an <b> ACT_QUEUE_STATE</b> structure.
### -output-buffer
None.
### -output-buffer-length
None.
### -in-out-buffer
### -inout-buffer-length
### -status-block
One of the following values can be returned in the <b>Status</b> field.
<table>
<tr>
<th>Status Value</th>
<th>Description</th>
</tr>
<tr>
<td>STATUS_SUCCESS</td>
<td>The queue state was changed successfully.</td>
</tr>
<tr>
<td>STATUS_INVALID_BUFFER_SIZE</td>
<td>The input buffer length is too small.</td>
</tr>
<tr>
<td>STATUS_ACCESS_DENIED</td>
<td>The IOCTL request was not issued by a silo driver.</td>
</tr>
</table>
## -remarks
Silo drivers or applications can freeze the storage device IO request queue if temporary unauthorization is needed. Normally, temporary unauthorization occurs during low power states or when a policy requires locking of Enhanced Storage devices such as a locked user session. In such a case, it is preferable to put pending IO requests on hold rather than fail the IO requests and cause data loss.
To prevent abuse of the <b>IOCTL_EHSTOR_DEVICE_SET_QUEUE_STATE</b> request by applications, only a driver can issue this IOCTL. If sent from a user mode application, this request will fail with STATUS_ACCESS_DENIED.
## -see-also
<a href="https://docs.microsoft.com/windows-hardware/drivers/ddi/ehstorioctl/ni-ehstorioctl-ioctl_ehstor_device_get_queue_state">IOCTL_EHSTOR_DEVICE_GET_QUEUE_STATE</a>
| 24.779141 | 399 | 0.743253 | eng_Latn | 0.777531 |
08e13e1f9467600a5be742bcad9533eb9759c513 | 40 | md | Markdown | _includes/03-links.md | zachallen8/markdown-portfolio | d2b7ae6874ce276f7bf774f6ddd3520f1541b8a0 | [
"MIT"
] | null | null | null | _includes/03-links.md | zachallen8/markdown-portfolio | d2b7ae6874ce276f7bf774f6ddd3520f1541b8a0 | [
"MIT"
] | 5 | 2021-02-09T20:58:55.000Z | 2021-02-09T21:54:57.000Z | _includes/03-links.md | zachallen8/markdown-portfolio | d2b7ae6874ce276f7bf774f6ddd3520f1541b8a0 | [
"MIT"
] | null | null | null | [GitHub](https://github.com/zachallen8)
| 20 | 39 | 0.75 | hun_Latn | 0.145431 |
08e145c1383745a6d9361987168bf0610b6e11b3 | 1,722 | md | Markdown | docs/README.md | Microservice-API-Patterns/MDSL-Specification | bcf53776304acd9d2de95a539189b35002d08102 | [
"Apache-2.0"
] | 23 | 2020-05-27T12:21:30.000Z | 2022-03-27T04:06:18.000Z | docs/README.md | Microservice-API-Patterns/MDSL-Specification | bcf53776304acd9d2de95a539189b35002d08102 | [
"Apache-2.0"
] | 4 | 2021-09-21T15:28:16.000Z | 2022-02-28T01:47:37.000Z | docs/README.md | Microservice-API-Patterns/MDSL-Specification | bcf53776304acd9d2de95a539189b35002d08102 | [
"Apache-2.0"
] | 1 | 2020-08-11T17:05:19.000Z | 2020-08-11T17:05:19.000Z | # MDSL Doc Page
This folder contains the MDSL Github page available at [https://microservice-api-patterns.github.io/MDSL-Specification/](https://microservice-api-patterns.github.io/MDSL-Specification/).
## Preview Page Locally
To preview the page locally (in case you want to make changes to the page), run the following commands within this folder:
1. `bundle install`
2. `bundle exec jekyll serve`
### Preconditions
To be able to preview the page as described above, you must have installed the following tools on your system:
* [Jekyll](https://jekyllrb.com/docs/installation/)
* Jekyll is a [Ruby Gem](https://rubygems.org/pages/download), so you have to install [Ruby](https://www.ruby-lang.org/en/downloads/) and [RubyGems](https://rubygems.org/pages/download) to be able to run it:
* Verify that the following commands are available on your terminal:
* `ruby -v`
* `gem -v`
* Installation instructions can be found [here](https://jekyllrb.com/docs/installation/).
## Eclipse Update Site
The folder _updates_ of this Github page contains an Eclipse update site with the latest version of the MDSL plugin. The update site can be updated as follows:
1. Build the Update Site ZIP file as described in the README of the Xtext project: [Xtext project README](./../dsl-core#build-eclipse-update-site-locally) (`mvn clean verify`)
2. Unzip the generated file (`dsl-core/io.mdsl.repository/target/io.mdsl.repository-x.x.x-SNAPSHOT.zip`)
3. Copy the contents to the `docs/updates` folder of this repository (overwrite)
4. Commit and push the changes
1. `git add docs/updates/* -f`
2. `git commit -m "Update MDSL update site for release vx.x.x"`
3. `git push origin master`
| 55.548387 | 210 | 0.739257 | eng_Latn | 0.901055 |
08e159f4497ae9031b54d7bcf7b5689563638cc9 | 62 | md | Markdown | README.md | SandwichBoy/spring-boot-jsp | b3dfcb3016eef577217225b7132532e4d8d65034 | [
"Apache-2.0"
] | null | null | null | README.md | SandwichBoy/spring-boot-jsp | b3dfcb3016eef577217225b7132532e4d8d65034 | [
"Apache-2.0"
] | null | null | null | README.md | SandwichBoy/spring-boot-jsp | b3dfcb3016eef577217225b7132532e4d8d65034 | [
"Apache-2.0"
] | null | null | null | # spring-boot-jsp
A project to test jsp access in spring boot
| 20.666667 | 43 | 0.774194 | eng_Latn | 0.65732 |
08e18ca237b98849863784ffe90fd8a496f006e7 | 370 | md | Markdown | README.md | wojjy001/infliximabapp | 5fc313a3b331071c17214c631bba6ca0341a5c52 | [
"MIT"
] | null | null | null | README.md | wojjy001/infliximabapp | 5fc313a3b331071c17214c631bba6ca0341a5c52 | [
"MIT"
] | null | null | null | README.md | wojjy001/infliximabapp | 5fc313a3b331071c17214c631bba6ca0341a5c52 | [
"MIT"
] | null | null | null | # infliximabapp
Shiny application that performs Bayesian estimation and simulation of individual infliximab concentration-time profiles, and subsequent dose optimisation to achieve a target trough concentration.
The model, Bayesian estimation inferences and R/Shiny application code have not been validated for clinical/patient use.
Use for demonstration purposes only.
| 74 | 195 | 0.851351 | eng_Latn | 0.98434 |
08e208227382f2e4e7ed5110b7232ddc963c330f | 1,240 | md | Markdown | _posts/2006-08-01-walt-whitman-and-the-most-boring-lecture-yet.md | joahua/blog | 85f14d2005d3bf4d6ad020a41147ad0f25d73196 | [
"MIT"
] | null | null | null | _posts/2006-08-01-walt-whitman-and-the-most-boring-lecture-yet.md | joahua/blog | 85f14d2005d3bf4d6ad020a41147ad0f25d73196 | [
"MIT"
] | null | null | null | _posts/2006-08-01-walt-whitman-and-the-most-boring-lecture-yet.md | joahua/blog | 85f14d2005d3bf4d6ad020a41147ad0f25d73196 | [
"MIT"
] | null | null | null | ---
title: Walt Whitman and the Most Boring Lecture Yet
author: Josh Street
layout: post
permalink: /2006/08/01/walt-whitman-and-the-most-boring-lecture-yet/
categories:
- School/Uni
tags:
- butcher
- Emily Dickinson
- lecturer
- same lecturer
- Whitman
---
Well, it might be the simpler English course this semester, but that doesn’t mean its potential for frustration is in any way diminished. Some lecturer wasted an hour of my life today talking about the binding and cover of Whitman’s *Leaves of Grass*, the three metaphors in the title of that work, parroting some Emerson essay for about thirty minutes, and extolling the virtues of the American character as though it were some homoerotic process of creative inspiration. Oh. Dear. And I won’t even start on her ineptitude in the art of clicking “next” in Powerpoint. Shoot me now.
Unfortunately it is the same lecturer again tomorrow. I’m going to be getting an aisle seat close to the door.
Then there is (mercifully) a one-week hiatus, after which she will proceed to (probably) butcher Emily Dickinson — who looks vastly more interesting than Whitman to start with, but I fear this can only mean there is further to fall. | 65.263158 | 612 | 0.773387 | eng_Latn | 0.999252 |
08e21394df1ab28167c264ebb624598676bffeee | 103 | md | Markdown | references/@barbierEvaluationFormation2001.md | damienbelveze/obsidian2021 | a4121f60bdf4df7afa62f73a29cd01268baf3dd5 | [
"CC-BY-4.0"
] | null | null | null | references/@barbierEvaluationFormation2001.md | damienbelveze/obsidian2021 | a4121f60bdf4df7afa62f73a29cd01268baf3dd5 | [
"CC-BY-4.0"
] | null | null | null | references/@barbierEvaluationFormation2001.md | damienbelveze/obsidian2021 | a4121f60bdf4df7afa62f73a29cd01268baf3dd5 | [
"CC-BY-4.0"
] | null | null | null | auteurs: Jean-Marie Barbier,
titre: L'évaluation en formation
publication:,
année: 2001,
p.,
URL:
| 12.875 | 32 | 0.718447 | fra_Latn | 0.845043 |
08e24f2720b7c19a4dfbc0d41ff5849009da5fc5 | 12 | md | Markdown | xyztiles/README.md | dronebird/oam_shizuoka20170822mtfuji | f147c3f151b12337bb1e85cbf2f262a1b4e1255c | [
"CC-BY-4.0"
] | 1 | 2017-08-24T08:32:41.000Z | 2017-08-24T08:32:41.000Z | xyztiles/README.md | dronebird/oam_shizuoka20170822mtfuji | f147c3f151b12337bb1e85cbf2f262a1b4e1255c | [
"CC-BY-4.0"
] | 1 | 2017-08-24T07:54:53.000Z | 2017-08-24T08:39:03.000Z | xyztiles/README.md | dronebird/oam_shizuoka20170822mtfuji | f147c3f151b12337bb1e85cbf2f262a1b4e1255c | [
"CC-BY-4.0"
] | null | null | null | # XYZ tiles
| 6 | 11 | 0.666667 | ast_Latn | 0.447416 |
08e2c7c634bd15197767124e18a33e9be777e016 | 1,761 | md | Markdown | README.md | abdurezakMussa/Updated-Portfolio-Page | 12d22716b1a3823a63e3bab80ed08990cc2a564b | [
"Unlicense"
] | null | null | null | README.md | abdurezakMussa/Updated-Portfolio-Page | 12d22716b1a3823a63e3bab80ed08990cc2a564b | [
"Unlicense"
] | null | null | null | README.md | abdurezakMussa/Updated-Portfolio-Page | 12d22716b1a3823a63e3bab80ed08990cc2a564b | [
"Unlicense"
] | null | null | null | # Updated-Portfolio-Page
## Description
I made this site for the University of Richmond Bootcamp. The goal is to create a My portfolio site. I utilized HTML,CSS and javaScript to create my portfolio website. I had to follow a specific style and specifications. I deployed using Github Pages.
As a web developer, I need to a portfolio site deployed that will show my skills to potential employers and clients to hire me. This site also gives me an opportunity to introduce myself, while also providing a way for employers and clients to reach out to me.
## Website
https://abdurezakmussa.github.io/Updated-Portfolio-Page/
## License
Copyright (c) 2020 Abdurezak Abdelkader
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 (if chill enough) 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. | 92.684211 | 460 | 0.798978 | eng_Latn | 0.867387 |
08e305b7b1ff9fd153849e69957a36b6e835e5ba | 233 | md | Markdown | README.md | jawu/hsedit | 2ebd449b0d9a0936b892ae718d731702cfa16ec7 | [
"Unlicense"
] | null | null | null | README.md | jawu/hsedit | 2ebd449b0d9a0936b892ae718d731702cfa16ec7 | [
"Unlicense"
] | null | null | null | README.md | jawu/hsedit | 2ebd449b0d9a0936b892ae718d731702cfa16ec7 | [
"Unlicense"
] | null | null | null | # hsedit
An Eclipse plugin for creating, editing and running haskell code files.
Uses GHCI as compiler so you'll need it for running your code.
This is an university project in the class "plugin development for Eclipse" FH Flensburg
| 46.6 | 88 | 0.802575 | eng_Latn | 0.997588 |
08e30774def39eeae5e6110b032aa1b79f5b6dbb | 7,249 | md | Markdown | README.md | pedropbazzo/react-native-desafio3 | 47175e188445473c2555d43f92c7a8e197283331 | [
"MIT"
] | null | null | null | README.md | pedropbazzo/react-native-desafio3 | 47175e188445473c2555d43f92c7a8e197283331 | [
"MIT"
] | null | null | null | README.md | pedropbazzo/react-native-desafio3 | 47175e188445473c2555d43f92c7a8e197283331 | [
"MIT"
] | null | null | null | # React Native - Desafio 3
[](https://github.com/osvaldokalvaitir/react-native-desafio3/blob/master/LICENSE)
[](https://code.visualstudio.com/)
Aplicação usando React Native, ESLint, EditorConfig, Babel Root Import, Redux, Redux-Saga, Ducks, Reactotron e Mapbox.
## Desafio 3
Crie uma aplicação do zero e configura as ferramentas: ESLint, Reactotron, Babel Root Import e EditorConfig.
Nesse desafio você utilizará mapas para construir uma interface de cadastro de localização de usuários do Github, o processo é simples, ao pressionar o mapa, um modal será aberto com o campo para digitar um usuário do Github, ao clicar em “Salvar”, uma requisição à API do Github deve ser feita buscando dados como nome, avatar e bio do usuário e aparecer no mapa com seu avatar, ao clicar em cima do usuário no mapa, deve aparecer uma caixa em cima do usuário exibindo seu nome e bio.
A interface da aplicação será como a seguinte:
### Regras
- Você pode utilizar a biblioteca [React Native MapBox](https://github.com/mapbox/react-native-mapbox-gl) para criar o mapa, siga os passos de instalação [aqui](https://github.com/mapbox/react-native-mapbox-gl#installation), ou seguindo [esse post](https://blog.rocketseat.com.br/react-native-mapbox/) no blog da Rocketseat;
- A localização inicial do mapa deve ser: Latitude: -27.2177659 e Longitude: -49.6451598, a latitudeDelta deve ser 0.0042 e longitudeDelta 0.0031. Você pode alterar esse valores caso ache melhor.
- O modal para cadastro de localidade só deve ser aberto após o usuário manter pressionado o mapa algum tempo (não é um simples clique).
- A localização utilizada para cadastro deve ser a mesma que o usuário pressionou no mapa.
- Deve-se buscar o nome, bio e avatar do usuário no Github ao cadastrar.
- Ao clicar em cima do avatar do usuário no mapa deve-se exibir seu nome e bio em uma caixa branca, isso pode ser utilizando o recurso de [callout](https://github.com/mapbox/react-native-mapbox-gl/blob/master/docs/Callout.md).
- A requisição à API deve ser feita utilizando Redux Saga;
### Dicas
- Você irá precisar criar uma conta na aplicação MapBox no plano grátis para conseguir utilizar os mapas: https://www.mapbox.com/signin/
- Para personalizar a marcação no mapa com o avatar do usuário, é necessária a utilização de uma tag Image dentro da tag PointAnnotation do MapBox.
- Para detectar um clique longo em cima do mapa é necessária a utilização da função [onLongPress](https://github.com/mapbox/react-native-mapbox-gl/blob/master/docs/MapView.md) do MapView;
- Para criar o Modal, utilize o componente [Modal](https://facebook.github.io/react-native/docs/modal.html) do React Native.
## Índice
- [Capturas de Tela](#capturas-de-tela)
- [Principal](#principal)
- [Novo Usuário](#novo-usuário)
- [Desenvolvimento](#desenvolvimento)
- [Configuração do Ambiente](#configuração-do-ambiente)
- [Instalação do Projeto](#instalação-do-projeto)
- [Execução do Projeto](#execução-do-projeto)
- [Utilizados no Projeto](#utilizados-no-projeto)
- [Bibliotecas](#bibliotecas)
- [APIs](#apis)
- [Ferramentas](#ferramentas)
## Capturas de Tela
### Principal
Nesta tela, encontra-se um mapa com todos os usuários do GitHub que foi adicionado pelo usuário, podendo também, adicionar novos usuários dando um toque longo.
### Novo Usuário
Esta tela é responsável por adicionar um usuário que esteja cadastrado no GitHub, sendo obrigatório informar o nome para inserí-lo.
## Desenvolvimento
### Configuração do Ambiente
Clique [aqui](https://github.com/osvaldokalvaitir/projects-settings/blob/master/README.md) e siga `Configuração de Ambiente`.
### Instalação do Projeto
Clique [aqui](https://github.com/osvaldokalvaitir/projects-settings/blob/master/nodejs/nodejs.md) e siga `Instalação de Projeto`.
### Execução do Projeto
Clique [aqui](https://github.com/osvaldokalvaitir/projects-settings/blob/master/nodejs/libs/react-native-cli.md) e siga `Execução de Projeto para Desenvolvimento`.
## Utilizados no Projeto
### Bibliotecas
- [Axios](https://github.com/osvaldokalvaitir/projects-settings/blob/master/nodejs/libs/axios.md)
- [Babel Root Import](https://github.com/osvaldokalvaitir/projects-settings/blob/master/nodejs/libs/babel-plugin-root-import.md)
- [babel-eslint](https://github.com/osvaldokalvaitir/projects-settings/blob/master/nodejs/libs/babel-eslint.md)
- [Ducks](https://github.com/osvaldokalvaitir/projects-settings/blob/master/nodejs/libs/ducks.md)
- [eslint](https://github.com/osvaldokalvaitir/projects-settings/blob/master/nodejs/libs/eslint.md)
- [ESLint plugin for React Native](https://github.com/osvaldokalvaitir/projects-settings/blob/master/nodejs/libs/eslint-plugin-react-native.md)
- [eslint-import-resolver-babel-plugin-root-import](https://github.com/osvaldokalvaitir/projects-settings/blob/master/nodejs/libs/eslint-import-resolver-babel-plugin-root-import.md)
- [Mapbox Maps SDK for React Native](https://github.com/osvaldokalvaitir/projects-settings/blob/master/nodejs/libs/@mapbox-react-native-mapbox-gl.md)
- [prop-types](https://github.com/osvaldokalvaitir/projects-settings/blob/master/nodejs/libs/prop-types.md)
- [React Redux](https://github.com/osvaldokalvaitir/projects-settings/blob/master/nodejs/libs/react-redux.md)
- [react-native-cli](https://github.com/osvaldokalvaitir/projects-settings/blob/master/nodejs/libs/react-native-cli.md)
- [reactotron-react-native](https://github.com/osvaldokalvaitir/projects-settings/blob/master/nodejs/libs/reactotron-react-native.md)
- [reactotron-redux](https://github.com/osvaldokalvaitir/projects-settings/blob/master/nodejs/libs/reactotron-redux.md)
- [reactotron-redux-saga](https://github.com/osvaldokalvaitir/projects-settings/blob/master/nodejs/libs/reactotron-redux-saga.md)
- [Redux](https://github.com/osvaldokalvaitir/projects-settings/blob/master/nodejs/libs/redux.md)
- [Redux-Saga](https://github.com/osvaldokalvaitir/projects-settings/blob/master/nodejs/libs/redux-saga.md)
### APIs
- **[GitHub](https://api.github.com)**
- **Rotas**
- Usuários
- Busca dados de um usuário
### Ferramentas
- [Reactotron](https://github.com/osvaldokalvaitir/projects-settings/blob/master/inspector/reactotron.md)
- [Mapbox](https://github.com/osvaldokalvaitir/projects-settings/blob/master/map/mapbox.md)
| 50.692308 | 485 | 0.775555 | por_Latn | 0.913561 |
08e41c172f4dfaccdd6caab6828081f5d5c2d9a9 | 273 | md | Markdown | snippets/native-platforms/ios-facebook-login/facebook-button-permissions.md | enak/docs | 097d0058fc03a75415e07933967a0d5da381f8eb | [
"MIT"
] | 336 | 2015-02-03T21:32:33.000Z | 2022-03-27T07:42:33.000Z | snippets/native-platforms/ios-facebook-login/facebook-button-permissions.md | enak/docs | 097d0058fc03a75415e07933967a0d5da381f8eb | [
"MIT"
] | 3,640 | 2015-01-05T19:16:40.000Z | 2022-03-21T15:34:43.000Z | snippets/native-platforms/ios-facebook-login/facebook-button-permissions.md | enak/docs | 097d0058fc03a75415e07933967a0d5da381f8eb | [
"MIT"
] | 2,052 | 2015-01-05T07:10:33.000Z | 2022-03-17T17:24:51.000Z | Set the requested permissions to `.publicProfile` and `.email`. This way, the user email will also be included as part of the response, provided the access request is accepted by the user.
```swift
let loginButton = FBLoginButton(permissions: [.publicProfile, .email])
``` | 54.6 | 188 | 0.765568 | eng_Latn | 0.999052 |
08e46eb2c29d913c686dcb79ac7d470867803b9b | 586 | md | Markdown | README.md | pedrobautistamx/caudal.site | ee04e66c3ff1df2087aef41af3ab43b1723db8b4 | [
"MIT"
] | 2 | 2018-02-26T18:43:10.000Z | 2018-04-28T01:42:17.000Z | README.md | pedrobautistamx/caudal.site | ee04e66c3ff1df2087aef41af3ab43b1723db8b4 | [
"MIT"
] | 1 | 2018-06-14T03:03:11.000Z | 2018-06-14T03:03:11.000Z | README.md | pedrobautistamx/caudal.site | ee04e66c3ff1df2087aef41af3ab43b1723db8b4 | [
"MIT"
] | 7 | 2018-01-29T14:59:29.000Z | 2018-03-07T14:39:33.000Z | # Caudal Official Website
[ ](https://app.codeship.com/projects/269660)
## Requirements
NPM & Hexo
``` bash
npm install hexo-cli -g
```
## Getting Started
Install dependencies as follow:
``` bash
$ git clone https://github.com/interwaremx/caudal.site.git
$ cd caudal.site
$ npm install
```
Generate:
``` bash
$ hexo generate
```
Run server:
``` bash
$ hexo server
```
## License
[CC BY 4.0](http://creativecommons.org/licenses/by/4.0/)
| 16.277778 | 184 | 0.711604 | yue_Hant | 0.325233 |
08e5ef6f194d83aba5e939e43cacb890036d10d1 | 384 | md | Markdown | readme.md | klawdyo/Inflector-BR | 6ab5f1b91f99bc065d39be71b3d607a8c7b0dd8c | [
"MIT"
] | 9 | 2018-12-17T13:21:23.000Z | 2021-04-27T13:35:10.000Z | readme.md | klawdyo/Inflector-BR | 6ab5f1b91f99bc065d39be71b3d607a8c7b0dd8c | [
"MIT"
] | 1 | 2015-02-18T22:42:20.000Z | 2015-02-18T22:42:20.000Z | readme.md | klawdyo/Inflector | 6ab5f1b91f99bc065d39be71b3d607a8c7b0dd8c | [
"MIT"
] | 7 | 2015-01-15T18:25:19.000Z | 2018-07-08T01:49:07.000Z | ## Exemplos
### Instalação
```sh
composer require klawdyo/inflector-br
```
### Como usar
```php
/**
* Usando inflexões de palavras em português brasileiro
*/
use Inflector\Inflector;
//Transformando a palavra para o plural
echo Inflector::pluralize('mês');
//Retorna "meses"
//Transformando a palavra para o singular
echo Inflector::singularize('meses');
//Retorna "mês"
```
| 14.769231 | 55 | 0.710938 | por_Latn | 0.961975 |