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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2f65797561252405430521fe4abd21ab9384462e | 1,017 | md | Markdown | docs/visual-basic/misc/bc2033.md | roel4ez/docs | 3924cfceca7eb9ee88706129f99cf9aa2aeeb668 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2019-09-24T17:36:44.000Z | 2022-03-27T22:37:38.000Z | docs/visual-basic/misc/bc2033.md | roel4ez/docs | 3924cfceca7eb9ee88706129f99cf9aa2aeeb668 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2018-12-03T20:19:56.000Z | 2019-06-12T17:48:50.000Z | docs/visual-basic/misc/bc2033.md | roel4ez/docs | 3924cfceca7eb9ee88706129f99cf9aa2aeeb668 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2019-09-22T20:06:22.000Z | 2019-10-05T14:34:46.000Z | ---
title: "Error embedding Win32 manifest: Option -win32manifest conflicts with -nowin32manifest"
ms.date: 07/20/2015
f1_keywords:
- "vbc2033"
- "bc2033"
helpviewer_keywords:
- "BC2033"
ms.assetid: e921b34a-1ab3-4ba0-81b3-e45c62de4718
---
# Error embedding Win32 manifest: Option /win32manifest conflicts with /nowin32manifest
The Visual Basic compiler has been passed both a `/win32manifest` compiler option and a `/nowin32manifest` compiler option. Only one of these options can be passed to the Visual Basic compiler.
**Error ID:** BC2033
## To correct this error
1. Remove either the `/win32manifest` compiler option or the `/nowin32manifest` compiler option.
## See also
- [/win32manifest (Visual Basic)](../../visual-basic/reference/command-line-compiler/win32manifest.md)
- [/nowin32manifest (Visual Basic)](../../visual-basic/reference/command-line-compiler/nowin32manifest.md)
- [Visual Basic Command-Line Compiler](../../visual-basic/reference/command-line-compiler/index.md)
| 40.68 | 195 | 0.751229 | eng_Latn | 0.670435 |
2f657ff0a0ef40214c1fd96d9e937342b1ed058c | 2,720 | md | Markdown | docs/framework/wpf/controls/listview-how-to-topics.md | wangshuai-007/docs.zh-cn | b0f422093b4d46695643d4ef95ea85c51ef3c702 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wpf/controls/listview-how-to-topics.md | wangshuai-007/docs.zh-cn | b0f422093b4d46695643d4ef95ea85c51ef3c702 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wpf/controls/listview-how-to-topics.md | wangshuai-007/docs.zh-cn | b0f422093b4d46695643d4ef95ea85c51ef3c702 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "ListView 帮助主题"
ms.custom:
ms.date: 03/30/2017
ms.prod: .net-framework
ms.reviewer:
ms.suite:
ms.technology: dotnet-wpf
ms.tgt_pltfrm:
ms.topic: article
f1_keywords: AutoGeneratedOrientationPage
helpviewer_keywords:
- controls [WPF], ListView
- ListView controls [WPF], how-to topics
ms.assetid: aafce40c-9bfe-45ec-86a3-599616a11276
caps.latest.revision: "68"
author: dotnet-bot
ms.author: dotnetcontent
manager: wpickett
ms.openlocfilehash: 98b0d38ab78bb36337461495cc6e8e782160617a
ms.sourcegitcommit: c2e216692ef7576a213ae16af2377cd98d1a67fa
ms.translationtype: MT
ms.contentlocale: zh-CN
ms.lasthandoff: 10/22/2017
---
# <a name="listview-how-to-topics"></a>ListView 帮助主题
本部分中的主题介绍如何使用<xref:System.Windows.Controls.ListView>控件来显示组的数据项。
## <a name="in-this-section"></a>本节内容
[在标题获得单击时对 GridView 列进行排序](../../../../docs/framework/wpf/controls/how-to-sort-a-gridview-column-when-a-header-is-clicked.md)
[创建 ListView 的自定义视图模式](../../../../docs/framework/wpf/controls/how-to-create-a-custom-view-mode-for-a-listview.md)
[使用模板设置使用 GridView 的 ListView 的样式](../../../../docs/framework/wpf/controls/how-to-use-templates-to-style-a-listview-that-uses-gridview.md)
[创建拖动的 GridView 列标题的样式](../../../../docs/framework/wpf/controls/how-to-create-a-style-for-a-dragged-gridview-column-header.md)
[使用 GridView 显示 ListView 内容](../../../../docs/framework/wpf/controls/how-to-display-listview-contents-by-using-a-gridview.md)
[使用触发器在 ListView 中设置选定项的样式](../../../../docs/framework/wpf/controls/how-to-use-triggers-to-style-selected-items-in-a-listview.md)
[使用 CheckBox 创建 ListViewItem](../../../../docs/framework/wpf/controls/how-to-create-listviewitems-with-a-checkbox.md)
[使用 GridViewRowPresenter 显示数据](../../../../docs/framework/wpf/controls/how-to-display-data-by-using-gridviewrowpresenter.md)
[在实现 GridView 的 ListView 中对项进行分组](../../../../docs/framework/wpf/controls/how-to-group-items-in-a-listview-that-implements-a-gridview.md)
[在实现 GridView 的 ListView 中设置行样式](../../../../docs/framework/wpf/controls/how-to-style-a-row-in-a-listview-that-implements-a-gridview.md)
[更改 ListView 中列的水平对齐方式](../../../../docs/framework/wpf/controls/how-to-change-the-horizontal-alignment-of-a-column-in-a-listview.md)
[处理 ListView 中每一项的 MouseDoubleClick 事件](../../../../docs/framework/wpf/controls/how-to-handle-the-mousedoubleclick-event-for-each-item-in-a-listview.md)
## <a name="reference"></a>参考
<xref:System.Windows.Controls.ListView>
<xref:System.Windows.Controls.ListViewItem>
<xref:System.Windows.Controls.GridView>
## <a name="related-sections"></a>相关章节
[ListView 概述](../../../../docs/framework/wpf/controls/listview-overview.md)
| 52.307692 | 155 | 0.728676 | yue_Hant | 0.34074 |
2f662da4e3ae10f1575aad216927635d8a8857ae | 2,051 | md | Markdown | README.md | chessbr/rust-exchange | 135bc2a6b2c8ee2f76418a4704e4337b25e9641e | [
"MIT"
] | 1 | 2022-03-09T10:54:40.000Z | 2022-03-09T10:54:40.000Z | README.md | chessbr/rust-exchange | 135bc2a6b2c8ee2f76418a4704e4337b25e9641e | [
"MIT"
] | null | null | null | README.md | chessbr/rust-exchange | 135bc2a6b2c8ee2f76418a4704e4337b25e9641e | [
"MIT"
] | 3 | 2021-12-11T12:57:22.000Z | 2022-03-11T06:56:44.000Z | # Rust Exchange
A simple exchange built using Rust. The project uses microservices that work together to process buy and sell orders.
The project has the following services:
#### **Order Handler**
This is the service that will communicate with the users directly through a TCP connection using a simple protocol. The user connects to the service host and submits a payload through the socket. Once the order is successfully received (and logged), the user received a response. This communication should be fast (~10ms) as all the hard work (storing into the database and matching orders) will be done asynchronously.
The order handler will read the asset from the payload and it will enqueue the order to the correct queue - every asset should have its own queue.
The service won’t return whether the order was executed or not, it is not its responsibility. The user must register to the Market Data Notifier service to receive notifications about his order.
#### **Order Processing Queue**
The order receiver will log the request to the database and notify the correct Matching Engine that a new order message was received.
#### **Matching Engine**
The Matching Engine will consume the order messages and processes them. When a buy order matches one or more sell orders (or vice-versa), the Matching Engine sends the resulting trades to the Trade Processing Queue and updates the order book.
The order book is stored in memory to prevent I/O overheads like writing to the disk or waiting for a network request.
#### **Trade Processing Queue**
This service will receive messages from the Matching Engine about orders executed, canceled, or changed. The service will then log the message to the database and will dispatch a message to Market Data Notifier.
#### **Market Data Notifier**
This service will have thousands of users connected waiting for order notifications. The service will broadcast the trades for the users. Also, users can register to receive notifications about their own orders
## License
MIT
| 53.973684 | 419 | 0.787421 | eng_Latn | 0.999196 |
2f6638b0c8c1ef5aa5ab80b5db50df30c23978f1 | 713 | md | Markdown | _bg/dep/csubjpass.md | mjabrams/docs | eef96df1ce8f6752e9f80660c8255482b2a07c45 | [
"Apache-2.0"
] | null | null | null | _bg/dep/csubjpass.md | mjabrams/docs | eef96df1ce8f6752e9f80660c8255482b2a07c45 | [
"Apache-2.0"
] | null | null | null | _bg/dep/csubjpass.md | mjabrams/docs | eef96df1ce8f6752e9f80660c8255482b2a07c45 | [
"Apache-2.0"
] | null | null | null | ---
layout: relation
title: 'csubjpass'
shortdef: 'clausal passive subject'
---
A clausal passive subject is a clausal syntactic subject of a passive
clause (or more generally, any voice where the proto-agent argument does not become the subject
of the clause).
Participle passive (the meaning is “It is said that belief will save us.”)
~~~ sdparse
Казано е, вярата ще ни спаси . \n Said is, belief will us save .
csubjpass(Казано, спаси)
csubjpass(Said, save)
~~~
Reflexive passive (the meaning is “It is costly for one on our Earth to be a human.”)
~~~ sdparse
Скъпо се плаща на тая земя да бъдеш човек . \n Costly REFL.pay at this land to be a-human .
csubjpass(плаща, бъдеш)
csubjpass(REFL.pay, be)
~~~
| 27.423077 | 96 | 0.736325 | eng_Latn | 0.988263 |
2f6681d45b93bfc72c48cc4af465ba30fe4f4661 | 68 | md | Markdown | README.md | embeaver/Dog-breed-classifier | 954c6394d135e54c91c204669bb23da9383185cf | [
"MIT"
] | null | null | null | README.md | embeaver/Dog-breed-classifier | 954c6394d135e54c91c204669bb23da9383185cf | [
"MIT"
] | null | null | null | README.md | embeaver/Dog-breed-classifier | 954c6394d135e54c91c204669bb23da9383185cf | [
"MIT"
] | null | null | null | # Dog-breed-classifier
Use pre-trained model to classify dog breeds
| 22.666667 | 44 | 0.808824 | eng_Latn | 0.906934 |
2f66fe72f7c700e9b572668a800f7cc710c331f2 | 332 | md | Markdown | content/wiki/service/slats/index.md | caitken-com/NRCHKB.github.io | 19e0da0477ee1438def2d1aa6e431600d36ece89 | [
"MIT"
] | null | null | null | content/wiki/service/slats/index.md | caitken-com/NRCHKB.github.io | 19e0da0477ee1438def2d1aa6e431600d36ece89 | [
"MIT"
] | null | null | null | content/wiki/service/slats/index.md | caitken-com/NRCHKB.github.io | 19e0da0477ee1438def2d1aa6e431600d36ece89 | [
"MIT"
] | null | null | null | ---
title: "Slats"
description: "Slats"
lead: ""
date: 2021-04-17T18:50:12.034Z
lastmod: 2021-08-03T21:21:00+01:00
draft: false
images: []
menu:
docs:
parent: "service"
toc: true
service:
name: "Slats"
contributors: ["caitken-com"]
---
Used as an accessory to control slats/window blinds. Either as horizontal or vertical.
| 17.473684 | 86 | 0.698795 | eng_Latn | 0.417648 |
2f677c00c3349b8ff98bce53002dac4d1617dfea | 1,300 | md | Markdown | datastore/README.md | nielm/java-docs-samples | fab1be853df2ccb470fe22bfd878cf52474cd179 | [
"Apache-2.0"
] | 1 | 2019-09-06T18:33:00.000Z | 2019-09-06T18:33:00.000Z | datastore/README.md | nielm/java-docs-samples | fab1be853df2ccb470fe22bfd878cf52474cd179 | [
"Apache-2.0"
] | 2 | 2021-03-10T23:28:18.000Z | 2021-06-23T21:02:01.000Z | datastore/README.md | nielm/java-docs-samples | fab1be853df2ccb470fe22bfd878cf52474cd179 | [
"Apache-2.0"
] | 1 | 2020-06-12T09:27:40.000Z | 2020-06-12T09:27:40.000Z | ## Datastore Samples
<a href="https://console.cloud.google.com/cloudshell/open?git_repo=https://github.com/GoogleCloudPlatform/java-docs-samples&page=editor&open_in_editor=datastore/README.md">
<img alt="Open in Cloud Shell" src ="http://gstatic.com/cloudssh/images/open-btn.png"></a>
This directory contains sample code used in Google Cloud Datastore documentation. Included here is a sample command line application, `TaskList`, that interacts with Datastore to manage a to-do list.
## Run the `TaskList` sample application.
1. Ensure that you have:
* Created a Google Developers Console project with the Datastore API enabled. Follow [these instructions](https://cloud.google.com/docs/authentication#preparation) to get your project set up.
* Installed the Google Cloud SDK and run the following commands in command line: `gcloud auth application-default login` and `gcloud config set project [YOUR PROJECT ID]`.
* Installed [Maven](https://maven.apache.org/) and Java 8 (or above).
2. Compile the program by typing `mvn clean compile` in command line.
3. Run the program by typing `mvn exec:java` in command line. In addition to listing tasks via this command line interface, you can view tasks you create in the [Google Cloud Developer's Console](https://console.cloud.google.com/).
| 72.222222 | 231 | 0.776154 | eng_Latn | 0.837237 |
2f67911654ceb9f2ac798900ca23262dc8d01751 | 1,031 | md | Markdown | docs/framework/wcf/diagnostics/tracing/system-servicemodel-droppedamessage.md | yunuskorkmaz/docs.tr-tr | e73dea6e171ca23e56c399c55e586a61d5814601 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wcf/diagnostics/tracing/system-servicemodel-droppedamessage.md | yunuskorkmaz/docs.tr-tr | e73dea6e171ca23e56c399c55e586a61d5814601 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wcf/diagnostics/tracing/system-servicemodel-droppedamessage.md | yunuskorkmaz/docs.tr-tr | e73dea6e171ca23e56c399c55e586a61d5814601 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
description: ': System. ServiceModel. DroppedAMessage hakkında daha fazla bilgi edinin'
title: System.ServiceModel.DroppedAMessage
ms.date: 03/30/2017
ms.assetid: a299401f-2983-45ea-b4f3-963bece3602e
ms.openlocfilehash: 3f74764cdde28c9ef5e96049c649015efbcb5da3
ms.sourcegitcommit: ddf7edb67715a5b9a45e3dd44536dabc153c1de0
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 02/06/2021
ms.locfileid: "99633796"
---
# <a name="systemservicemodeldroppedamessage"></a>System.ServiceModel.DroppedAMessage
System.ServiceModel.DroppedAMessage
## <a name="description"></a>Description
Bir yanıt iletisi alındı, ancak bu ileti için bekleyen bir istek yok. İleti Windows Communication Foundation (WCF) çalışma zamanı tarafından bırakılıyor.
Bu izleme, kayıp iletilerde hata ayıklama için kullanılabilir.
## <a name="see-also"></a>Ayrıca bkz.
- [İzleme](index.md)
- [Uygulamanızda Sorun Giderme için İzleme Kullanma](using-tracing-to-troubleshoot-your-application.md)
- [Yönetim ve tanılama](../index.md)
| 36.821429 | 156 | 0.791465 | tur_Latn | 0.923992 |
2f67a0228e91c84e5b1cc551651907fd3432dc2f | 6,567 | md | Markdown | site/content/blog/melihat-potensi-patungan-bisnis-melalui-sistem-securities-crowdfunding-untuk-investasi-jangka-panjang.md | landx-id/blog | 561beb4f33c21dee89f179f79c60d0c10d83993f | [
"MIT"
] | null | null | null | site/content/blog/melihat-potensi-patungan-bisnis-melalui-sistem-securities-crowdfunding-untuk-investasi-jangka-panjang.md | landx-id/blog | 561beb4f33c21dee89f179f79c60d0c10d83993f | [
"MIT"
] | 1 | 2022-01-06T05:27:23.000Z | 2022-01-06T05:27:23.000Z | site/content/blog/melihat-potensi-patungan-bisnis-melalui-sistem-securities-crowdfunding-untuk-investasi-jangka-panjang.md | landx-id/blog | 561beb4f33c21dee89f179f79c60d0c10d83993f | [
"MIT"
] | null | null | null | ---
draft: false
author: Abdul Wahhab
slug: melihat-potensi-patungan-bisnis-melalui-sistem-securities-crowdfunding-untuk-investasi-jangka-panjang
title: "Patungan Bisnis dengan Sistem Investasi Securities Crowdfunding "
metaTitle: "Patungan Bisnis dengan Sistem Investasi Securities Crowdfunding "
metaDescription: Securities crowdfunding merupakan sistem investasi yang
memudahkan investor ritel untuk ikut patungan membangun bisnis
intro: Yuk simak seluk-beluk investasi dengan sistem securities crowdfunding
date: 2021-09-27T06:30:08.000Z
tag:
- Securities Crowdfunding untuk Pengembangan UMKM di Indonesia
- Equity Crowdfunding
- crowdfunding
- crowdfunding indonesia
- Situs Crowdfunding
- investasi bisnis
- bisnis patungan
featuredImage:
src: https://accountgram-production.sfo2.cdn.digitaloceanspaces.com/landx_ghost/2021/09/patungan-bisnis-menguntungkan-bareng-landx-5.png
alt: Cara Patungan Bisnis lewat sistem securities crowdfunding
title: Simak cara investasi menguntungkan dengan sistem securities crowdfunding
image: https://accountgram-production.sfo2.cdn.digitaloceanspaces.com/landx_ghost/2021/09/patungan-bisnis-menguntungkan-bareng-landx-5.png
category:
- Cara Investasi di Securities Crowdfunding
- Investasi
- Keuangan
---
Apabila kamu ingin memiliki bisnis namun terhambat karena keterbatasan modal dan kemampuan mengelola bisnis, patungan bisnis melalui securities crowdfunding adalah solusi untuk semua kendala tersebut.
Sistem bisnis patungan ini sangat menguntungkan bisnis dan investor pemula karena mereka bisa menikmati keuntungan dari suatu bisnis dengan modal kecil dan risiko yang lebih minim. [](https://landx.id/)
[Securities crowdfunding](https://landx.id/) merupakan salah satu sistem yang membantu mempertemukan para investor dan pebisnis untuk patungan membangun suatu bisnis.
Supaya kamu lebih paham, yuk kita bahas lebih lanjut tentang bagaimana cara patungan bisnis menguntungkan melalui securities crowdfunding.
- - -
## Apa yang Dimaksud dengan Bisnis Patungan?
Bisnis patungan adalah adalah kesatuan bisnis yang terbentuk dari beberapa pihak untuk membangun suatu bisnis bersama-sama. Para investor atau orang yang terlibat dalam patungan akan mendapatkan bagian kepemilikan atau saham yang disesuaikan dengan besar dana yang mereka keluarkan.
Pembangunan bisnis melalui sistem patungan merupakan cara yang sudah ada sejak dulu namun dalam cakupan yang terbilang sempit karena dilakukan oleh beberapa orang saja dengan modal yang cukup besar.
Saat ini, sistem patungan bisnis menjadi lebih mudah seiring perkembangan teknologi informasi karena kini ada platform securities crowdfunding yang memberikan investor kesempatan untuk ikut patungan bisnis dengan modal kecil.
Melalui securities crowdfunding, investor bisa ikut patungan dan berinvestasi ke berbagai bisnis dari **privat seperti UMKM** yang sebelumnya cukup sulit untuk diakses dengan modal kecil.
Pembagian keuntungan berdasarkan sistem bagi hasil berupa dividen yang nilainya menyesuaikan jumlah saham yang kamu miliki dan besar keuntungan dari bisnis tersebut.
## Tips Penting dalam Memulai Patungan Bisnis
Dalam membangun bisnis dengan sistem patungan anda perlu memperhatikan beberapa hal penting terutama terkait dengan potensi keuntungan jangka panjang dari bisnis tersebut.
Platform securities crowdfunding yang baik akan melakukan kurasi terhadap bisnis yang akan didanai investor, sehingga proses seleksi bisnis terbaik untuk anda danai semakin mudah.
Namun anda tetap harus paham dengan jelas tentang bisnis dan potensi perkembangan dari bisnis ini dalam beberapa periode yang akan datang.
Hal ini karena setiap jenis bisnis memiliki potensi dan risiko yang berbeda-beda sehingga anda perlu memahami hal ini dengan baik.
Anda tetap harus bisa memahami berbagai resiko yang akan timbul saat anda terlibat dalam patungan bisnis. Oleh sebab itu anda perlu mencari tahu lebih lanjut tentang bisnis yang akan danai mulai dari potensi perkembangan bisnis hingga bagaimana pengelolaan bisnis.
Karena itu, kamu perlu melihat profil penerbit agar tahu rekam jejak pengelola dari bisnis yang akan kamu danai. Karena pengalaman dalam menjalankan bisnis merupakan faktor penting yang menentukan apakah bisnis tersebut dapat berjalan dalam jangka panjang atau tidak.
Selain itu anda perlu melihat dari sisi lain seperti *payback period, net present value, return on investment rate,* serta strategi mitigasi risiko yang dilakukan bisnis tersebut untuk meghadapi berbagai kondisi tidak terduga di masa mendatang.
## **Cara Cerdas Memulai Patungan Bisnis**
Cara terbaik untuk memulai investasi bisnis adalah mulai dengan memilih platform equity [crowdfunding](https://landx.id/) terbaik yang sudah berpengalaman dalam memfasilitasi pengumpulan dana untuk bisnis patungan.
Anda harus melihat apakah sebuah platform memiliki rekam jejak yang baik dalam menghimpun dana untuk bisnis patungan yang akan dijalankan.
Setelah itu, anda harus memilih bisnis yang memiliki prospek perkembangan jangka panjang dan tidak termakan oleh waktu. Anda harus melihat kematangan konsep dari bisnis tersebut dan apakah dijalankan oleh pihak yang profesional dan sudah berpengalaman dalam bidang bisnis tersebut karena bisnis yang potensial sekali pun tidak akan berkembang apabila tidak diatur dengan baik.
Oleh sebab itu…
## **[Yuk Patungan Bisnis Menguntungkan Bareng LandX](https://landx.id/)**
[LandX](https://landx.id/) merupakan [platform equity crowdfunding](https://landx.id/) terpercaya yang telah berizin OJK dan telah berpengalaman membantu investor menemukan bisnis terbaik untuk investasi bisnis jangka panjang anda.
[
](https://landx.id/)
**[Jangan Lupa!! Follow @landx.id di Instagram Supaya Terus Update Berbagai Info Seputar Investas](https://instagram.com/landx.id?utm_medium=copy_link)i**
- - -
**Baca Juga:**
* **[Return on Investment (ROI): Cara Menghitung dan Jenis-Jenis ROI](https://landx.id/blog/return-on-investment-roi-adalah/)**
* **[Menelusuri Sejarah Mulainya Equity Crowdfunding di Indonesia: Melihat Perkembangan Equity Crowdfunding Resmi OJK](https://landx.id/blog/equity-crowdfunding-indonesia/)**
- - -
**\#YukPatunganBisnis #LandX.id #landx #landx.id #InvestasiBisnis #SecuritiesCrowdfunding #EquityCrowdfunding #InvestasiMenguntungkan #Urundana #BisnisPatungan #InvestasiUsaha** | 69.126316 | 376 | 0.820466 | ind_Latn | 0.981073 |
2f67fc675eb43d91af1ff7cc11b7724762dbade4 | 4,039 | md | Markdown | README.md | vinaykakkad/Airline-management-system | 2acd725f87bc40abd405630356cb2cf0411f42ad | [
"MIT"
] | null | null | null | README.md | vinaykakkad/Airline-management-system | 2acd725f87bc40abd405630356cb2cf0411f42ad | [
"MIT"
] | 1 | 2021-06-28T08:38:31.000Z | 2021-06-28T08:42:41.000Z | README.md | vinaykakkad/Airline-management-system | 2acd725f87bc40abd405630356cb2cf0411f42ad | [
"MIT"
] | 1 | 2021-06-28T07:02:35.000Z | 2021-06-28T07:02:35.000Z | # Airline Management System ✈
<!-- ALL-CONTRIBUTORS-BADGE:START - Do not remove or modify this section -->
[](#contributors-)
<!-- ALL-CONTRIBUTORS-BADGE:END -->
Airline Management System made for the course Database Management System
## Report 🧾
Report contains description, database schemas, ER diagrams and screenshots
[Report](https://drive.google.com/file/d/1jxFr9ybLeA09HHFTRGrl6VvEmVko_YtL/view)
## Environment Variables ⚙
To run this project, you will need to add the following environment variables to a .env file
`DATABASE_URL` - Your postgreSQL database uri
`SECRETY_KEY` - Secret key for the flask app
## Run Locally 🚀
Clone the project
```bash
git clone https://github.com/vinaykakkad/Airline-management-system.git
```
Creatre a virtual environment and activate
```bash
python -m venv env
env\Scripts\activate
```
Install dependencies
```bash
pip install -r requirements.txt
```
- Setup your postgreSQL database and add the database URI to environment variables
- Run the sql scripts to add tables, functions, triggers and procedures to your databse
Run locally from the ```/webapp``` directory
```bash
python app.py
```
## Tech Stack
**Frontend:** HTML, CSS, Bootstrap
**Backend:** Flask
**Database:** PostgreSQL
## License
[MIT](https://github.com/vinaykakkad/Airline-management-system/blob/main/LICENSE)
## Contributors ✨
Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/docs/en/emoji-key)):
<!-- ALL-CONTRIBUTORS-LIST:START - Do not remove or modify this section -->
<!-- prettier-ignore-start -->
<!-- markdownlint-disable -->
<table>
<tr>
<td align="center"><a href="https://github.com/vinaykakkad"><img src="https://avatars.githubusercontent.com/u/56934712?v=4?s=100" width="100px;" alt=""/><br /><sub><b>Vinay Kakkad</b></sub></a><br /><a href="https://github.com/vinaykakkad/Airline-management-system/commits?author=vinaykakkad" title="Code">💻</a> <a href="https://github.com/vinaykakkad/Airline-management-system/commits?author=vinaykakkad" title="Documentation">📖</a> <a href="#design-vinaykakkad" title="Design">🎨</a> <a href="#maintenance-vinaykakkad" title="Maintenance">🚧</a></td>
<td align="center"><a href="https://github.com/ankitdevani17"><img src="https://avatars.githubusercontent.com/u/56442204?v=4?s=100" width="100px;" alt=""/><br /><sub><b>Ankit Devani</b></sub></a><br /><a href="https://github.com/vinaykakkad/Airline-management-system/commits?author=ankitdevani17" title="Code">💻</a> <a href="https://github.com/vinaykakkad/Airline-management-system/commits?author=ankitdevani17" title="Documentation">📖</a> <a href="#design-ankitdevani17" title="Design">🎨</a> <a href="#maintenance-ankitdevani17" title="Maintenance">🚧</a></td>
<td align="center"><a href="https://github.com/tirth8205"><img src="https://avatars.githubusercontent.com/u/56442204?v=4?s=100" width="100px;" alt=""/><br /><sub><b>Tirth Bharatbhai Kanani</b></sub></a><br /><a href="https://github.com/vinaykakkad/Airline-management-system/commits?author=tirth8205" title="Code">💻</a> <a href="https://github.com/vinaykakkad/Airline-management-system/commits?author=tirth8205" title="Documentation">📖</a> <a href="#design-tirth8205" title="Design">🎨</a> <a href="#maintenance-tirth8205" title="Maintenance">🚧</a></td>
<td align="center"><a href="https://www.linkedin.com/in/jeet-karia-628773170/"><img src="https://avatars.githubusercontent.com/u/50065408?v=4?s=100" width="100px;" alt=""/><br /><sub><b>Jeet Karia</b></sub></a><br /><a href="https://github.com/vinaykakkad/Airline-management-system/commits?author=JeetKaria06" title="Documentation">📖</a></td>
</tr>
</table>
<!-- markdownlint-restore -->
<!-- prettier-ignore-end -->
<!-- ALL-CONTRIBUTORS-LIST:END -->
This project follows the [all-contributors](https://github.com/all-contributors/all-contributors) specification. Contributions of any kind welcome!
| 38.836538 | 564 | 0.71899 | yue_Hant | 0.198733 |
2f69e70371a87bf3e1cf49a5160aa080f96a590e | 175 | md | Markdown | lua/README.md | ftassi/7_more_languages_in_7_weeks | 3100ac8cdbbe5f3a41110e97a42553d922e5becc | [
"MIT"
] | null | null | null | lua/README.md | ftassi/7_more_languages_in_7_weeks | 3100ac8cdbbe5f3a41110e97a42553d922e5becc | [
"MIT"
] | null | null | null | lua/README.md | ftassi/7_more_languages_in_7_weeks | 3100ac8cdbbe5f3a41110e97a42553d922e5becc | [
"MIT"
] | null | null | null | # Resources about Lua
* [wiki](http://lua-users.org/wiki/)
* [programming in Lua](https://www.lua.org/pil/contents.html)
* [Reference manual](http://www.lua.org/manual/5.3/)
| 29.166667 | 61 | 0.691429 | yue_Hant | 0.636087 |
2f6afe61947b78869ed73ea9112592ad0cf9b870 | 358 | md | Markdown | _posts/2011-09-30-39-7084.md | ashmaroli/mycad.github.io | 47fb8e82e4801dd33a3d4335a3d4a6657ec604cf | [
"MIT"
] | null | null | null | _posts/2011-09-30-39-7084.md | ashmaroli/mycad.github.io | 47fb8e82e4801dd33a3d4335a3d4a6657ec604cf | [
"MIT"
] | null | null | null | _posts/2011-09-30-39-7084.md | ashmaroli/mycad.github.io | 47fb8e82e4801dd33a3d4335a3d4a6657ec604cf | [
"MIT"
] | null | null | null | ---
layout: post
amendno: 39-7084
cadno: CAD2011-A340-06
title: 起落架-主起落架收放作动筒活塞杆-检查/改装
date: 2011-09-30 00:00:00 +0800
effdate: 2011-09-30 00:00:00 +0800
tag: A340
categories: 民航华东地区管理局适航审定处
author: 龙飞君
---
##适用范围:
本指令适用于空客 A340-211, A340-212, A340-213, A340-311, A340-312及A340-313所有生产序列号的飞机，除非在制造时两个主起落架已完成了空客改装MOD 52980。
在制造过程中完成了空客改装MOD 54500的飞机不适用本指令。
| 21.058824 | 107 | 0.768156 | yue_Hant | 0.363219 |
2f6b88143900842a412a0dab8ca68501a3b2c83b | 214 | md | Markdown | mc/Voyage-Model-Core.package/VOSaveOperation.class/README.md | ranomine/voyage | 14952674b28d70d531efb018cfe7ff005c2a93b1 | [
"MIT"
] | 27 | 2016-06-09T14:49:05.000Z | 2021-11-16T12:34:59.000Z | mc/Voyage-Model-Core.package/VOSaveOperation.class/README.md | ranomine/voyage | 14952674b28d70d531efb018cfe7ff005c2a93b1 | [
"MIT"
] | 112 | 2016-06-09T12:52:23.000Z | 2021-08-17T08:14:32.000Z | mc/Voyage-Model-Core.package/VOSaveOperation.class/README.md | ranomine/voyage | 14952674b28d70d531efb018cfe7ff005c2a93b1 | [
"MIT"
] | 20 | 2016-09-09T08:26:01.000Z | 2021-12-28T21:03:58.000Z | I represent a save operation to a database. Saves are either insert or update operations hence my subclasses.
I know about an object that should be saved and an id which will be the external presentation of myself | 71.333333 | 109 | 0.813084 | eng_Latn | 0.999933 |
2f6cac4e56ce79770086d20be80bea5af051d8e9 | 1,978 | md | Markdown | README.md | glaucia86/demo-mvpconf-latam-2019 | d57f3f3893222ed5d81a0311435141fffc556b75 | [
"MIT"
] | 2 | 2019-04-29T17:17:11.000Z | 2020-02-27T21:04:57.000Z | README.md | glaucia86/demo-mvpconf-latam-2019 | d57f3f3893222ed5d81a0311435141fffc556b75 | [
"MIT"
] | null | null | null | README.md | glaucia86/demo-mvpconf-latam-2019 | d57f3f3893222ed5d81a0311435141fffc556b75 | [
"MIT"
] | null | null | null | # Demo: MVP Conf 2019 - Palestra: Desenvolvendo Aplicações Node.js com Azure - A Nuvem que Escala!
[](https://postimg.cc/kVZLgHpZ)
A demo consiste no desenvolvimento de uma aplicação MEAN (TODO-LIST) com integração com os serviços do Azure: **[Azure App Service](https://aka.ms/AA4qm7c)** integrado com o **[CosmosDb](https://aka.ms/AA4qm7e)**
## Recursos Utilizados no Desenvolvimento da Aplicação :rocket:
- **[VS Code](http://bit.ly/2IhTeUb)**
- **[Node.js](https://nodejs.org/en/)**
- **[Azure App Service](https://aka.ms/AA4qm7c)**
- **[MongoDb Community Server](https://www.mongodb.com/download-center/community)**
- **[MongoDb Compass GUI](https://www.mongodb.com/download-center/compass)**
- **[Cadastro Site Azure](http://bit.ly/2I7Kj8u)**
- **[AngularJs](https://angularjs.org/)**
## Executando a Aplicação Localmente 🔥
1) Instalar os pacotes com o comando:
```
> npm install
```
```
> npm run dev
```
Depois bastam abrir o browser em: **localhost:8000**
## Demo da Aplicação (Online) ⭐️
Caso desejam visualizar a demo em produção, com a integração com Azure & CosmosDb, bastam acessar o link **[AQUI](https://teste-todo-workshop.azurewebsites.net/)**.
## Quero aprender o Passo a Passo! Como faço?!
Simples! Basta acessar o acervo criado em **[AQUI](/passo-a-passo/02-hospedagem-webapp-azure.md)** para acompanhar todos os scripts criados e aprender a migrar sua base local para o CosmosDb e como hospedar a sua aplicação no Azure!
## Dúvidas?! ❓
Se tiverem alguma dúvida referente ao código desenvolvido ou para configurar o ambiente bastam criar uma **[ISSUE](https://github.com/glaucia86/workshop-azure-fundamentals/issues)** no GitHub que estarei respondendo a vocês!! :heart: :heart: :heart: :blush:
_Código baseado no projeto do Scotch.io. Porém com alterações significativas e com muitas melhorias no código. [Node Todo App by scotch.io](https://github.com/scotch-io/node-todo)_
| 44.954545 | 257 | 0.731041 | por_Latn | 0.988698 |
2f6d59b956ae002ccfc01f0d77efa4d77ccb1823 | 5,419 | md | Markdown | docs/documentation/94/ds-ds.md | radist-nt/pgjdbc | fda4299e1e3b76aa7e0c0031f3e11c61dd05c64b | [
"BSD-2-Clause"
] | 9 | 2020-06-30T17:06:49.000Z | 2022-03-08T09:20:47.000Z | docs/documentation/94/ds-ds.md | radist-nt/pgjdbc | fda4299e1e3b76aa7e0c0031f3e11c61dd05c64b | [
"BSD-2-Clause"
] | 11 | 2019-01-09T12:20:08.000Z | 2021-11-22T15:56:57.000Z | docs/documentation/94/ds-ds.md | radist-nt/pgjdbc | fda4299e1e3b76aa7e0c0031f3e11c61dd05c64b | [
"BSD-2-Clause"
] | 11 | 2020-07-01T05:21:10.000Z | 2022-01-20T11:58:49.000Z | ---
layout: default_docs
title: Applications DataSource
header: Chapter 11. Connection Pools and Data Sources
resource: media
previoustitle: Application Servers ConnectionPoolDataSource
previous: ds-cpds.html
nexttitle: Tomcat setup
next: tomcat.html
---
PostgreSQL™ includes two implementations of `DataSource`, as shown in [Table 11.2, “`DataSource` Implementations”](ds-ds.html#ds-ds-imp).
One that does pooling and the other that does not. The pooling implementation
does not actually close connections when the client calls the `close` method,
but instead returns the connections to a pool of available connections for other
clients to use. This avoids any overhead of repeatedly opening and closing
connections, and allows a large number of clients to share a small number of
database connections.
The pooling data-source implementation provided here is not the most feature-rich
in the world. Among other things, connections are never closed until the pool
itself is closed; there is no way to shrink the pool. As well, connections
requested for users other than the default configured user are not pooled. Its
error handling sometimes cannot remove a broken connection from the pool. In
general it is not recommended to use the PostgreSQL™ provided connection pool.
Check your application server or check out the excellent [jakarta commons DBCP](http://jakarta.apache.org/commons/dbcp/)
project.
<a name="ds-ds-imp"></a>
**Table 11.2. `DataSource` Implementations**
<table summary="DataSource Implementations" border="1">
<tr>
<th>Pooling</th>
<th>Implementation Class</th>
</tr>
<tbody>
<tr>
<td>No</td>
<td>`org.postgresql.ds.PGSimpleDataSource</td>
</tr>
<tr>
<td>Yes</td>
<td>`org.postgresql.ds.PGPoolingDataSource</td>
</tr>
</tbody>
</table>
Both implementations use the same configuration scheme. JDBC requires that a
`DataSource` be configured via JavaBean properties, shown in [Table 11.3, “`DataSource` Configuration Properties”](ds-ds.html#ds-ds-props),
so there are get and set methods for each of these properties.
<a name="ds-ds-props"></a>
**Table 11.3. `DataSource` Configuration Properties**
<table summary="DataSource Configuration Properties" border="1">
<tr>
<th>Property</th>
<th>Type</th>
<th>Description</th>
</tr>
<tbody>
<tr>
<td>serverName</td>
<td>STRING</td>
<td>PostgreSQL™ database server host name</td>
</tr>
<tr>
<td>databaseName</td>
<td>STRING</td>
<td>PostgreSQL™ database name</td>
</tr>
<tr>
<td>portNumber</td>
<td>INT</td>
<td>TCP port which the PostgreSQL™
database server is listening on (or 0 to use the default port)</td>
</tr>
<tr>
<td>user</td>
<td>STRING</td>
<td>User used to make database connections</td>
</tr>
<tr>
<td>password</td>
<td>STRING</td>
<td>Password used to make database connections</td>
</tr>
<tr>
<td>ssl</td>
<td>BOOLEAN</td>
<td> If true, use SSL encrypted
connections (default false) </td>
</tr>
<tr>
<td>sslfactory</td>
<td>STRING</td>
<td> Custom javax.net.ssl.SSLSocketFactory
class name (see the section called [“Custom
SSLSocketFactory”](ssl-factory.html))</td>
</tr>
</tbody>
</table>
The pooling implementation requires some additional configuration properties,
which are shown in [Table 11.4, “Additional Pooling `DataSource` Configuration Properties](ds-ds.html#ds-ds-xprops).
<a name="ds-ds-xprops"></a>
**Table 11.4. Additional Pooling `DataSource` Configuration Properties**
<table summary="Additional Pooling DataSource Configuration Properties" border="1">
<tr>
<th>Property</th>
<th>Type</th>
<th>Description</th>
</tr>
<tbody>
<tr>
<td>dataSourceName</td>
<td>STRING</td>
<td>Every pooling DataSource must
have a unique name.</td>
</tr>
<tr>
<td>initialConnections</td>
<td>INT</td>
<td>The number of database connections to be created when the
pool is initialized.</td>
</tr>
<tr>
<td>maxConnections</td>
<td>INT</td>
<td>The maximum number of open database connections to allow.
When more connections are requested, the caller will hang until a
connection is returned to the pool.</td>
</tr>
</tbody>
</table>
[Example 11.1, “`DataSource` Code Example”](ds-ds.html#ds-example) shows an example
of typical application code using a pooling `DataSource`.
<a name="ds-example"></a>
**Example 11.1. `DataSource` Code Example**
Code to initialize a pooling `DataSource` might look like this:
`PGPoolingDataSource source = new PGPoolingDataSource();`
`source.setDataSourceName("A Data Source");`
`source.setServerName("localhost");`
`source.setDatabaseName("test");`
`source.setUser("testuser");`
`source.setPassword("testpassword");`
`source.setMaxConnections(10);`
Then code to use a connection from the pool might look like this. Note that it
is critical that the connections are eventually closed. Else the pool will
“leak” connections and will eventually lock all the clients out.
<pre><code>
Connection conn = null;
try
{
conn = source.getConnection();
// use connection
}
catch (SQLException e)
{
// log error
}
finally
{
if (con != null)
{
try { conn.close(); } catch (SQLException e) {}
}
}
</code></pre> | 30.44382 | 139 | 0.691271 | eng_Latn | 0.899566 |
2f6d6722e5bc8980eb1f3c30bbc3d51576696990 | 1,371 | md | Markdown | docs/visual-basic/misc/bc30452.md | nicolaiarocci/docs.it-it | 74867e24b2aeb9dbaf0a908eabd8918bc780d7b4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/misc/bc30452.md | nicolaiarocci/docs.it-it | 74867e24b2aeb9dbaf0a908eabd8918bc780d7b4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/misc/bc30452.md | nicolaiarocci/docs.it-it | 74867e24b2aeb9dbaf0a908eabd8918bc780d7b4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Operatore '<operatorname>'non è definito per i tipi'<type1>'e'<type2>'
ms.date: 07/20/2015
f1_keywords:
- bc30452
- vbc30452
helpviewer_keywords:
- BC30452
ms.assetid: a3ceed45-b918-4572-9379-cc90619bddab
ms.openlocfilehash: 15485df726afbec36ce618782b9c1289fb56e1ca
ms.sourcegitcommit: 5c1abeec15fbddcc7dbaa729fabc1f1f29f12045
ms.translationtype: MT
ms.contentlocale: it-IT
ms.lasthandoff: 03/15/2019
ms.locfileid: "58050761"
---
# <a name="operator-operatorname-is-not-defined-for-types-type1-and-type2"></a>Operatore '\<nomeoperatore >' non è definito per i tipi\<type1 >' e '\<type2 >'
Si è provato a usare un operatore binario per eseguire un'operazione che non è valida per i due elementi di codice interessati che restituiscono un valore.
**ID errore:** BC30452
## <a name="to-correct-this-error"></a>Per correggere l'errore
- Controllare i due elementi e assicurarsi che siano compatibili.
## <a name="see-also"></a>Vedere anche
- [Operatori ed espressioni](../../visual-basic/programming-guide/language-features/operators-and-expressions/index.md)
- [Combinazione efficace di operatori](../../visual-basic/programming-guide/language-features/operators-and-expressions/efficient-combination-of-operators.md)
- [Precedenza tra gli operatori in Visual Basic](../../visual-basic/language-reference/operators/operator-precedence.md)
| 44.225806 | 158 | 0.768053 | ita_Latn | 0.808341 |
2f6e3a0c6add745f25a2560fc759045259c850b0 | 46 | md | Markdown | sample_chapters/README.md | AnanthaVamshi/PySpark_Tutorials | fd94f9af0517f0bffca26d4c7b751333d42b8f3d | [
"Apache-2.0"
] | 60 | 2019-07-09T10:34:48.000Z | 2022-03-17T00:04:43.000Z | sample_chapters/README.md | AnanthaVamshi/PySpark_Tutorials | fd94f9af0517f0bffca26d4c7b751333d42b8f3d | [
"Apache-2.0"
] | 2 | 2022-02-14T00:11:51.000Z | 2022-02-14T00:25:13.000Z | sample_chapters/README.md | AnanthaVamshi/PySpark_Tutorials | fd94f9af0517f0bffca26d4c7b751333d42b8f3d | [
"Apache-2.0"
] | 34 | 2019-07-03T13:24:45.000Z | 2022-02-14T00:11:45.000Z | ## Sample Chapters of PySpark Algorithms Book
| 23 | 45 | 0.804348 | eng_Latn | 0.738821 |
2f6e3bae3cca3eeb18a1b82f73bf8982404dc281 | 829 | md | Markdown | docs/extension/logging.md | boekkooi-lengoo/goengine | 8909e7a03f2162ddeace90ba4753af1df7825d88 | [
"MIT"
] | 117 | 2017-01-23T10:17:06.000Z | 2022-02-13T00:46:46.000Z | docs/extension/logging.md | boekkooi-lengoo/goengine | 8909e7a03f2162ddeace90ba4753af1df7825d88 | [
"MIT"
] | 53 | 2017-03-08T14:01:52.000Z | 2022-03-16T12:43:12.000Z | docs/extension/logging.md | boekkooi-lengoo/goengine | 8909e7a03f2162ddeace90ba4753af1df7825d88 | [
"MIT"
] | 17 | 2016-12-11T23:21:50.000Z | 2022-03-19T18:51:04.000Z | # Logrus
In order to use [logrus] as your logger GoEngine provides a wrapper for both `*logrus.Logger` and `*logrus.Entry`.
```golang
import (
"github.com/hellofresh/goengine/v2"
goengineLogger "github.com/hellofresh/goengine/v2/extension/logrus"
"github.com/sirupsen/logrus"
)
var logger goengine.Logger
logger = goengineLogger.Wrap(s.Logger)
logger = goengineLogger.WrapEntry(s.Logger.WithField("source": "goengine"))
```
# Zap
In order to use [zap] as your logger GoEngine provides a wrapper for `*zap.Logger`.
```golang
import (
"github.com/hellofresh/goengine/v2"
goengineLogger "github.com/hellofresh/goengine/v2/extension/zap"
"go.uber.org/zap"
)
var logger goengine.Logger
logger = goengineLogger.Wrap(zap.NewNop())
```
[logrus]: https://github.com/sirupsen/logrus
[zap]: https://github.com/uber-go/zap/
| 23.685714 | 115 | 0.745476 | yue_Hant | 0.626353 |
2f6ec4db981a600b875a28487b9dad8a66249f40 | 404 | md | Markdown | _posts/news/2016-09-22-panama-city-beach-florida-show.md | jglickmantpz/the-petting-zoo.github.io | a0d0cc547301078c92d619662abcc909b1beb207 | [
"MIT"
] | null | null | null | _posts/news/2016-09-22-panama-city-beach-florida-show.md | jglickmantpz/the-petting-zoo.github.io | a0d0cc547301078c92d619662abcc909b1beb207 | [
"MIT"
] | null | null | null | _posts/news/2016-09-22-panama-city-beach-florida-show.md | jglickmantpz/the-petting-zoo.github.io | a0d0cc547301078c92d619662abcc909b1beb207 | [
"MIT"
] | 1 | 2019-01-02T15:39:02.000Z | 2019-01-02T15:39:02.000Z | ---
category: blog
layout: default
published: true
title: Panama City Beach Florida Show
---
Grab your sunglasses and come hang with the cool kids at The Zoo! We will attend the Panama City Beach Show September 28th through 30th. Come see our New Plush and place an order with us. Booth 417 and 419.
| 40.4 | 206 | 0.779703 | eng_Latn | 0.979141 |
2f6f84948ee44c00da5ddb0da3afec5737c38a91 | 239 | md | Markdown | translations/zh-CN/data/reusables/sponsors/change-tier.md | kyawburma/docs | 0ff7de03be7c2432ced123aca17bfbf444bee1bf | [
"CC-BY-4.0",
"MIT"
] | 20 | 2021-02-17T16:18:11.000Z | 2022-03-16T08:30:36.000Z | translations/zh-CN/data/reusables/sponsors/change-tier.md | kyawburma/docs | 0ff7de03be7c2432ced123aca17bfbf444bee1bf | [
"CC-BY-4.0",
"MIT"
] | 419 | 2021-01-27T03:39:25.000Z | 2022-03-26T20:28:31.000Z | translations/zh-CN/data/reusables/sponsors/change-tier.md | kyawburma/docs | 0ff7de03be7c2432ced123aca17bfbf444bee1bf | [
"CC-BY-4.0",
"MIT"
] | 46 | 2020-11-05T10:39:05.000Z | 2021-07-23T11:35:59.000Z | 1. 在“{% data variables.product.prodname_sponsors %}”下，在被赞助开源贡献者的右侧，单击被赞助帐户旁边的 {% octicon "triangle-down" aria-label="The down triangle octicon" %}，然后单击 **Change tier（更改等级）**。 
| 119.5 | 238 | 0.753138 | yue_Hant | 0.587156 |
2f6fab2255ab58f9f6e15cb597e42e085714e309 | 32 | md | Markdown | README.md | xiaominghe2014/github_statistics | 00a598b5f86a3febcd108d1c827cd82994c1dad3 | [
"MIT"
] | 1 | 2019-08-08T06:13:14.000Z | 2019-08-08T06:13:14.000Z | README.md | xiaominghe2014/github_statistics | 00a598b5f86a3febcd108d1c827cd82994c1dad3 | [
"MIT"
] | null | null | null | README.md | xiaominghe2014/github_statistics | 00a598b5f86a3febcd108d1c827cd82994c1dad3 | [
"MIT"
] | null | null | null | # github_statistics
github 语言分析
| 10.666667 | 19 | 0.84375 | gle_Latn | 0.173559 |
2f7034473fc4b8c65ec389b03781a83f5cc1e56a | 409 | md | Markdown | _conjuntura/cc18022020.md | vitorwilher/vitorwilher.github.io | 13bc15711510e822dae46e91df4c0d200b44a957 | [
"MIT"
] | 1 | 2019-12-13T07:48:33.000Z | 2019-12-13T07:48:33.000Z | _conjuntura/cc18022020.md | vitorwilher/vitorwilher.github.io | 13bc15711510e822dae46e91df4c0d200b44a957 | [
"MIT"
] | null | null | null | _conjuntura/cc18022020.md | vitorwilher/vitorwilher.github.io | 13bc15711510e822dae46e91df4c0d200b44a957 | [
"MIT"
] | null | null | null | ---
title: "Desemprego de longo prazo no Brasil"
collection: conjuntura
type: "Comentário de Conjuntura"
permalink: /conjuntura/cc18022020
venue: "Comentário de Conjuntura"
date: 2020-02-18
---
Nesse comentário, fazemos uma análise do comportamento do desemprego de longo prazo no Brasil. [PDF disponível aqui](https://github.com/vitorwilher/conjuntura/blob/master/cc18022020.pdf){:target="_blank"}. | 40.9 | 205 | 0.770171 | por_Latn | 0.991951 |
2f70a253d971711a0c60fc576528ac9a6b7a73c4 | 3,090 | md | Markdown | _posts/2018-12-19-Download-hyundai-elantra-engine-diagram-crankshaft.md | Luanna-Lynde/28 | 1649d0fcde5c5a34b3079f46e73d5983a1bfce8c | [
"MIT"
] | null | null | null | _posts/2018-12-19-Download-hyundai-elantra-engine-diagram-crankshaft.md | Luanna-Lynde/28 | 1649d0fcde5c5a34b3079f46e73d5983a1bfce8c | [
"MIT"
] | null | null | null | _posts/2018-12-19-Download-hyundai-elantra-engine-diagram-crankshaft.md | Luanna-Lynde/28 | 1649d0fcde5c5a34b3079f46e73d5983a1bfce8c | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
categories: Other
---
## Download Hyundai elantra engine diagram crankshaft book
Jay grinned, his bowels hyundai elantra engine diagram crankshaft quiet. the night. The mameluke took compassion on him and said to him, beaming at him, in the dark. Why did it blow against them. So the young man went out, and over dinner she hyundai elantra engine diagram crankshaft, he said, "here is no summoning, Angel said. In one sense, reaching a Reluctant to leave the girl's side. Wait here, he would be reluctant to damage the property of another in this fashion. ), no part Have I in those who walk the ways, tensing to slam the door, he sent to give King El Aziz the glad tidings of his son's return and acquainted him with that which he had heard from the prince's servant. Her father or a brother. "Oh, While Jacob ate, 253, a bundle of amulets fastened with a He frowned slightly. All six had the same blood group. PETROVITSCH BARJATINSKY was _vojvode_ at Yakutsk (1667-75), there is the reactive pain? door. She conceived by him and bore a handsome boy and fearing Er Reshid, anyway," Sirocco said, deliberate movement while he brought his feelings under control. Nemmerle had given it to him! Begone from hyundai elantra engine diagram crankshaft. to Sterm. 126 have to fix her head immovable and tape open her eyes. " When the king heard this, except to sell my story of bein' de- b, which perhaps is only perceptible by the winter darkness was changed a second time to YOHI HISHA, with the San Francisco Police Department. " Singapore is situated exactly halfway, as you well know, in which case they might all make it inside before he funding scheme for the long term, or unusual hair; she had nothing unusual. He used human skin to make lampshades and to upholster might earn a transfer to the psychiatric ward. Woman and girl walk hand in hand, "and then at once followed by a second, shadowy in the subdued light coming from out side. She did. Hyundai elantra engine diagram crankshaft Paul sold his house to move in with Agnes, they cast the turban from his head and were about to bind his eyes, who was the first to move. "It was in your heart, ii, "Well, pledging to honour her inheritance and be true to Iria, we are here. "Why didn't God make me furry?" number of skin-boats, taken in a single swallow. alone in hyundai elantra engine diagram crankshaft apartment. El Fezl did his brother's bidding and released all but the young Damascene, however, it was a military installation containing munitions, of course, to be our own dogs. " saw one before?" way as the Studebaker rolled forward, what a self-deceiving parched. It was Friday, the free men of her crew all asleep but the helmsman and the lookout. 73). Why, he noticed the woman standing on the far side of the entrance, whereas an organism that arises from sexual reproduction (except where self-fertilization is possible) has two parents. Besides, too. "A wizard so great and old and so terrible that you and I need never worry hyundai elantra engine diagram crankshaft him. | 343.333333 | 2,975 | 0.782524 | eng_Latn | 0.999913 |
2f7104885e07b857a5b530548c530fb13f6099a1 | 2,427 | md | Markdown | docs/architecture.md | isteps-sps-lab/bf-fams | dfa53317fd45c7a90954a2feed99f28c94952d21 | [
"Apache-2.0"
] | null | null | null | docs/architecture.md | isteps-sps-lab/bf-fams | dfa53317fd45c7a90954a2feed99f28c94952d21 | [
"Apache-2.0"
] | null | null | null | docs/architecture.md | isteps-sps-lab/bf-fams | dfa53317fd45c7a90954a2feed99f28c94952d21 | [
"Apache-2.0"
] | null | null | null | # Architecture
Within the Better Factory project, the FaMS is deployed as part of the Cognitive
Human Robot Interaction (C-HRI) scenario. The deployment is based on Docker
Compose, and the set of initialized components is depicted in the picture here
below:
``` mermaid
flowchart LR
classDef supsi fill:#B4C7DC;
classDef pub fill:#B2B2B2
classDef pvt fill:#E8F2A1
subgraph SUPSI
direction TB
fams:::supsi <--> middleware:::supsi
kafka-message-model:::supsi --> middleware:::supsi
end
subgraph Private Deps
models:::pvt <--> fams:::supsi
end
subgraph Public Deps
models:::pvt <--> models-db:::pub
end
```
The blue-colored components represent the core components for which SUPSI
provides and maintains a Docker image; the other components (grey- and
green-colored) represent dependencies that are provided as Docker images by
third parties.
!!! info
In this deployment version, the only external dependencies that is available
only in a private registry is *models*. The *models* image is provided and
maintained by Holonix (HOL) within the Better Factory project.
## Dependencies
### middleware
The image is based on the [fast-data-dev
(v2.6.2)](https://github.com/lensesio/fast-data-dev/tree/fdd/2.6.2) project by
Lenses.io and runs a full fledged Kafka installation (including extra services,
e.g., UIs).
In addition, the Schema Registry is automatically populated with schemas
available under the `/schemas` directory. In our deployment, the `/schemas`
directory is read from the *kafka-message-model* component.
The middleware is run in secure mode and can be accessed at
[localhost:3040](localhost:3040) (credentials are stored in the docker-compose
file).
### kafka-message-model
This component embeds the data model shared within the Better Factory project.
The data model is automatically uploaded to the Schema Registry available within
the *middleware*.
### models
The *models* component exposes a REST API to access the data model shared among
all the components involved in the C-HRI scenario. The API is accessed by the
*fams* component to fetch information about workers and other factory elements.
!!! important
This image is available in a private Docker registry hosted at GitLab.
Please ask HOLONIX to get access to this image.
### models-db
The *models-db* component runs an official MySql docker image (v5.7).
| 31.519481 | 80 | 0.752781 | eng_Latn | 0.996545 |
2f7169036d0a649999f6efa8e82de8c401dafee2 | 221 | md | Markdown | snowflake/README.md | anback/Lean | 92ddac542a432bce1a29ab4b6f5f154f3e903412 | [
"Apache-2.0"
] | 5 | 2018-04-17T10:42:26.000Z | 2020-05-01T15:14:00.000Z | snowflake/README.md | anback/Lean | 92ddac542a432bce1a29ab4b6f5f154f3e903412 | [
"Apache-2.0"
] | 12 | 2018-03-06T03:41:57.000Z | 2018-03-09T18:29:16.000Z | snowflake/README.md | anback/Lean | 92ddac542a432bce1a29ab4b6f5f154f3e903412 | [
"Apache-2.0"
] | null | null | null | ### Pre req
node 6+
npm 3+
```
$ git clone https://github.com/rrag/react-stockcharts-examples2
$ cd examples/<example you wish>
$ npm install
$ npm start # this should launch a browser with http://localhost:3000
```
| 14.733333 | 69 | 0.692308 | eng_Latn | 0.770068 |
2f71b4fd122a0f94828edd5682cf006f08e2de23 | 139 | md | Markdown | core/resources/plugin-trenton.md | chunyu3/autorest | 58a6aade142cc17c2a1528bd3cc561cf3fd7f5ca | [
"MIT"
] | 1 | 2020-04-08T04:44:40.000Z | 2020-04-08T04:44:40.000Z | core/resources/plugin-trenton.md | chunyu3/autorest | 58a6aade142cc17c2a1528bd3cc561cf3fd7f5ca | [
"MIT"
] | 1 | 2021-02-23T23:45:23.000Z | 2021-02-23T23:45:23.000Z | core/resources/plugin-trenton.md | chunyu3/autorest | 58a6aade142cc17c2a1528bd3cc561cf3fd7f5ca | [
"MIT"
] | null | null | null | # Default Configuration - trenton
``` yaml $(trenton)
use-extension:
"@autorest/trenton": "latest"
try-require: ./readme.trenton.md
```
| 17.375 | 33 | 0.690647 | ita_Latn | 0.200499 |
2f71cd8bfa8d1323dbf09bd42d6123acd7ebb4fe | 1,642 | md | Markdown | docs/import/heading.md | kenlowrie/smd | 47018693eaedafa7b786fcc72dbdcfa277b6da7f | [
"Apache-2.0"
] | 1 | 2021-09-30T19:29:30.000Z | 2021-09-30T19:29:30.000Z | docs/import/heading.md | kenlowrie/smd | 47018693eaedafa7b786fcc72dbdcfa277b6da7f | [
"Apache-2.0"
] | 7 | 2018-07-16T22:52:55.000Z | 2020-05-20T23:48:36.000Z | docs/import/heading.md | kenlowrie/smd | 47018693eaedafa7b786fcc72dbdcfa277b6da7f | [
"Apache-2.0"
] | 1 | 2018-05-24T22:58:44.000Z | 2018-05-24T22:58:44.000Z | // This document contains the standard document heading for my scripts
// First let's declare some common links and aliases (variables)
// [workingtitle] and [storysummary] need to be defined *before* you include
// this template.
@link _id="cls" _inherit="_template_" _text="Cloudy Logic Studios" href="https://cloudylogic.com"
[cloudylogic.com]=[link.cls._qlink(_qtext="cloudylogic.com")]
@link _id="you" _inherit="_template_" _text="you@yourdomain.com" href="mailto:you@yourdomain.com"
@link _id="fbemailaddr" _inherit="_template_" _text="Your Name" href="mailto:you@yourdomain.com?subject=[workingtitle]%20Feedback"
@@ [var.cover(title="[workingtitle]" author="**Confidential**" logline="[storysummary].")]
@@ [var.cover(title="", logline="", author="**DISCLAIMER**: This document is strictly private, confidential and personal to its recipients and should not be copied, distributed or reproduced in whole or in part, nor passed to any third party without the expressed, written consent of [link.cls], LLC.")]
@@ [var.revision(revision="1d")]
@@ [var.contact(cn="Ken Lowrie" ph="*512-867-5309*" em="[link.you]" c1="Copyright (c) 2018 by [cls], LLC." c2="All Rights Reserved." c3="www.cloudylogic.com")]
{: .pba.review }--- divTitle Notes to Reviewer
Please send [link.fbemailaddr] any and all feedback, preferably by marking up the PDF using embedded comments. If you edit the PDF text, do so inline using comment boxes, or if you edit the text directly, change the color and/or font size so I can easily find it. Within different versions of this proposal, ++additions are marked like this++ and ~~deletions are marked like this~~
| 102.625 | 385 | 0.74665 | eng_Latn | 0.952692 |
2f734de92e4cac83f8496bd23df99e931369c688 | 149 | md | Markdown | README.md | ppizarror/espectro-nch433 | 3124b17507125ccd7b0d734fb0e8769268484dae | [
"MIT"
] | 1 | 2019-01-25T13:11:16.000Z | 2019-01-25T13:11:16.000Z | README.md | ppizarror/espectro-nch433 | 3124b17507125ccd7b0d734fb0e8769268484dae | [
"MIT"
] | null | null | null | README.md | ppizarror/espectro-nch433 | 3124b17507125ccd7b0d734fb0e8769268484dae | [
"MIT"
] | null | null | null | # espectro-nch433
Crea el espectro de diseño según la norma NCh 433.Of1996-2012.
## Autor
[Pablo Pizarro R.](https://ppizarror.com) | 2019 - 2022
| 18.625 | 62 | 0.718121 | spa_Latn | 0.773576 |
2f737855dd92d23006f6b555b3adbadb8bab3fd6 | 116 | md | Markdown | _drafts/2016-08-11-Basic_Electron-App.md | karlobrien/karlobrien.github.com | d82fa7551c7e792abb6a6405cbc6d418d8769e41 | [
"MIT"
] | null | null | null | _drafts/2016-08-11-Basic_Electron-App.md | karlobrien/karlobrien.github.com | d82fa7551c7e792abb6a6405cbc6d418d8769e41 | [
"MIT"
] | null | null | null | _drafts/2016-08-11-Basic_Electron-App.md | karlobrien/karlobrien.github.com | d82fa7551c7e792abb6a6405cbc6d418d8769e41 | [
"MIT"
] | null | null | null | ---
layout: post
title: Electron application with basic navigation
tags:
- node
- electron
- javascript
---
Draft
| 10.545455 | 50 | 0.724138 | eng_Latn | 0.891573 |
2f73aa4a1f4a1bf005bbb39c6126305cbb71305a | 2,643 | md | Markdown | website/translated_docs/ja/ORDA/remoteDatastores.md | Sieste68/docs | 63c06aaa9f06de535d3943294aca4a09fdac454a | [
"CC-BY-4.0"
] | null | null | null | website/translated_docs/ja/ORDA/remoteDatastores.md | Sieste68/docs | 63c06aaa9f06de535d3943294aca4a09fdac454a | [
"CC-BY-4.0"
] | null | null | null | website/translated_docs/ja/ORDA/remoteDatastores.md | Sieste68/docs | 63c06aaa9f06de535d3943294aca4a09fdac454a | [
"CC-BY-4.0"
] | 1 | 2019-03-27T06:57:51.000Z | 2019-03-27T06:57:51.000Z | ---
id: datastores
title: リモートデータストアの利用
---
4D アプリケーション上で公開された [データストア](dsMapping.md#データストア) は、異なるクライアントにより同時にアクセスすることができます:
- 4D リモートアプリケーションは ORDA を使っていれば、`ds` コマンドでメインデータストアにアクセスできます。 この 4D リモートアプリケーションは従来のモードでもデータベースにアクセスできます。 これらのアクセスを処理するのは **4Dアプリケーションサーバー** です。
- 他の 4Dアプリケーション (4Dリモート、4D Server) は、`Open datastore` コマンドを使ってリモートデータストアのセッションを開始できます。 アクセスを処理するのは **HTTP REST サーバー** です。
- iOS アプリケーションを更新するため、4D for iOS のクエリでアクセスできます。 アクセスを処理するのは **HTTP サーバー** です。
`Open datastore` コマンドによって参照されるリモートデータストアの場合、リクエスト元プロセスとリモートデータストア間の接続はセッションにより管理されます。
## セッションの開始
4Dアプリケーション (のプロセス) が `Open datastore` コマンドを使って外部のデータストアを開くと、この接続を管理するためにリモートデータストアではセッションが開始されます。 このセッションは内部的にセッションID によって識別され、4Dアプリケーション上では ` localID` と紐づいています。 データ、エンティティセレクション、エンティティへのアクセスはこのセッションによって自動的に管理されます。
`localID` はリモートデータストアに接続しているマシンにおけるローカルな識別IDです:
* 同じアプリケーションの別プロセスが同じリモートデータストアに接続する場合、`localID` とセッションは共有することができます。
* 同じアプリケーションの別プロセスが別の `localID` を使って同じデータストアに接続した場合、リモートデータストアでは新しいセッションが開始されます。
* 他のマシンが同じ `localID` を使って同じデータストアに接続した場合、新しいセッションが新しい cookie で開始されます。
これらの原則を下図に示します:
> REST リクエストによって開かれたセッションについては、[ユーザーとセッション](REST/authUsers.md) を参照ください。
## セッションの監視
データストアアクセスを管理しているセッションは 4D Server の管理画面に表示されます:
* プロセス名: "REST Handler: \<process name\>"
* タイプ: HTTP Server Worker
* セッション: `Open datastore` コマンドに渡されたユーザー名
次の例では、1つのセッション上で 2つのプロセスが実行中です:
## ロッキングとトランザクション
エンティティロッキングやトランザクションに関連した ORDA 機能は、ORDA のクライアント / サーバーモードと同様に、リモートデータストアにおいてもプロセスレベルで管理されます:
* あるプロセスがリモートデータストアのエンティティをロックした場合、セッションの共有如何に関わらず、他のすべてのプロセスに対してそのエンティティはロックされた状態です ([エンティティロッキング](entities.md#エンティティロッキング) 参照)。 同一のレコードに対応する複数のエンティティが 1つのプロセスによってロックされている場合、同プロセス内でそれらがすべてアンロックされないと、ロックは解除されません。 なお、ロックされたエンティティに対する参照がメモリ上に存在しなくなった場合にも、ロックは解除されます。
* トランザクションは `dataStore.startTransaction( )`、`dataStore.cancelTransaction( )`、`dataStore.validateTransaction( )` のメソッドを使って、リモートデータストアごとに個別に開始・認証・キャンセルすることができます。 これらの操作は他のデータストアには影響しません。
* 従来の 4Dランゲージコマンド (`START TRANSACTION`, `VALIDATE TRANSACTION`, `CANCEL TRANSACTION`) は `ds` で返されるメインデータストアに対してのみ動作します。 リモートデータストアのエンティティがあるプロセスのトランザクションで使われている場合、セッションの共有如何に関わらず、他のすべてのプロセスはそのエンティティを更新できません。
* 次の場合にエンティティのロックは解除され、トランザクションはキャンセルされます:
* プロセスが強制終了された
* サーバー上でセッションが閉じられた
* サーバー管理画面からセッションが強制終了された
## セッションの終了
アクティビティなしにタイムアウト時間が経過すると、4D は自動的にセッションを終了します。 デフォルトのタイムアウト時間は 60分です。`Open datastore` コマンドの `connectionInfo` パラメーターを指定して、タイムアウト時間を変更することができます。
セッション終了後にリクエストがリモートデータストアに送信された場合、セッションは可能な限り (ライセンスがあり、サーバーが停止していない、など) 再開されます。 ただしセッションが再開しても、ロックやトランザクションに関わるコンテキストは失われていることに留意が必要です (前述参照)。
| 43.327869 | 266 | 0.828604 | jpn_Jpan | 0.916628 |
2f73d581ede7ad71cd5f022f529ce31637a4b416 | 94 | md | Markdown | README.md | KarthikGangadhar/sensor | 0c5e35561af9a6bde17e72bf8332bad996c24338 | [
"Apache-2.0"
] | 1 | 2018-12-12T18:43:32.000Z | 2018-12-12T18:43:32.000Z | README.md | KarthikGangadhar/sensor | 0c5e35561af9a6bde17e72bf8332bad996c24338 | [
"Apache-2.0"
] | null | null | null | README.md | KarthikGangadhar/sensor | 0c5e35561af9a6bde17e72bf8332bad996c24338 | [
"Apache-2.0"
] | null | null | null | # sensor
Android application for serial communication using BLE(Bluetooth Low Energy) module
| 31.333333 | 84 | 0.829787 | eng_Latn | 0.928913 |
2f74aa6153b00bef2b95dfdd7db7c02cb96723e9 | 885 | md | Markdown | content/en/docs/reference/commands/jx_create_addon_owasp.md | gmacario/jx-docs | 908cf075a09fd73a8727d4eb819d664205f84747 | [
"Apache-2.0",
"CC0-1.0"
] | null | null | null | content/en/docs/reference/commands/jx_create_addon_owasp.md | gmacario/jx-docs | 908cf075a09fd73a8727d4eb819d664205f84747 | [
"Apache-2.0",
"CC0-1.0"
] | 3 | 2018-06-12T01:52:57.000Z | 2018-06-23T14:29:27.000Z | content/en/docs/reference/commands/jx_create_addon_owasp.md | gmacario/jx-docs | 908cf075a09fd73a8727d4eb819d664205f84747 | [
"Apache-2.0",
"CC0-1.0"
] | null | null | null | ---
date: 2018-07-18T14:25:14Z
title: "jx create addon owasp"
slug: jx_create_addon_owasp
url: /commands/jx_create_addon_owasp/
---
## jx create addon owasp
Create a owasp addon for dynamic security checks
### Synopsis
Creates the Owasp dyanmic security testing addon
```
jx create addon owasp [flags]
```
### Examples
```
# Create the kubeless addon in the kubeless namespace
jx create addon owasp
```
### Options
```
-l, --backoff-limit int32 The backoff limit: how many times to retry the job before considering it failed) to run in the Job (default 2)
-h, --help help for owasp
-i, --image string The OWASP image to use to run the ZA Proxy baseline scan (default "owasp/zap2docker-live:latest")
```
### SEE ALSO
* [jx create addon](/commands/jx_create_addon/) - Creates an addon
###### Auto generated by spf13/cobra on 18-Jul-2018
| 22.692308 | 140 | 0.691525 | eng_Latn | 0.936286 |
2f74f10816de49c9603aa217e38d6bda8923681f | 7,899 | md | Markdown | articles/expressroute/expressroute-circuit-peerings.md | Jontii/azure-docs.sv-se | d2551c12e17b442dc0b577205d034dcd6c73cff9 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/expressroute/expressroute-circuit-peerings.md | Jontii/azure-docs.sv-se | d2551c12e17b442dc0b577205d034dcd6c73cff9 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/expressroute/expressroute-circuit-peerings.md | Jontii/azure-docs.sv-se | d2551c12e17b442dc0b577205d034dcd6c73cff9 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Azure-ExpressRoute: kretsar och peering'
description: Den här sidan innehåller en översikt över ExpressRoute-kretsar och routningsdomäner/peering.
services: expressroute
author: duongau
ms.service: expressroute
ms.topic: conceptual
ms.date: 12/13/2019
ms.author: duau
ms.openlocfilehash: 87fed1d2ac4f5fa85c01d7af10bec10c1412744f
ms.sourcegitcommit: 957c916118f87ea3d67a60e1d72a30f48bad0db6
ms.translationtype: MT
ms.contentlocale: sv-SE
ms.lasthandoff: 10/19/2020
ms.locfileid: "92202352"
---
# <a name="expressroute-circuits-and-peering"></a>ExpressRoute-kretsar och peering
ExpressRoute-kretsar ansluter din lokala infrastruktur till Microsoft via en anslutnings leverantör. Den här artikeln hjälper dig att förstå ExpressRoute-kretsar och routningsdomäner/peering. Följande bild visar en logisk representation av anslutningen mellan WAN och Microsoft.
> [!IMPORTANT]
> Azures offentliga peering är inaktuell och är inte tillgänglig för nya ExpressRoute-kretsar. Nya kretsar stöder Microsoft-peering och privat peering.
>
## <a name="expressroute-circuits"></a><a name="circuits"></a>ExpressRoute-kretsar
En ExpressRoute-krets representerar en logisk anslutning mellan din lokala infrastruktur och Microsofts moln tjänster via en anslutnings leverantör. Du kan beställa flera ExpressRoute-kretsar. Varje krets kan finnas i samma eller olika regioner och kan anslutas till dina lokaler via olika anslutnings leverantörer.
ExpressRoute-kretsar mappar inte till några fysiska entiteter. En krets identifieras unikt av ett standard-GUID som kallas för en tjänst nyckel (s-Key). Tjänst nyckeln är den enda informations enhet som utbyts mellan Microsoft, anslutnings leverantören och dig. S-nyckeln är inte en hemlighet av säkerhets synpunkt. Det finns en 1:1-mappning mellan en ExpressRoute-krets och s-nyckeln.
Nya ExpressRoute-kretsar kan omfatta två oberoende peering: privat peering och Microsoft-peering. Befintliga ExpressRoute-kretsar kan innehålla tre peer-datorer: Azure offentlig, Azure Private och Microsoft. Varje peering är ett par oberoende BGP-sessioner, som var och en har kon figurer ATS redundant för hög tillgänglighet. Det finns en 1: N (1 <= N <= 3) mappning mellan en ExpressRoute-krets och routningsdomäner. En ExpressRoute-krets kan ha en, två eller alla tre peering-aktiverade per ExpressRoute-krets.
Varje krets har en fast bandbredd (50 Mbit/s, 100 Mbit/s, 200 Mbit/s, 500 Mbps, 1 Gbit/s, 10 Gbit/s) och mappas till en anslutnings leverantör och en peering-plats. Bandbredden som du väljer delas mellan alla krets-peering
### <a name="quotas-limits-and-limitations"></a><a name="quotas"></a>Kvoter, gränser och begränsningar
Standard kvoter och-gränser gäller för varje ExpressRoute-krets. Se sidan för [Azure-prenumeration och tjänst begränsningar, kvoter och begränsningar](../azure-resource-manager/management/azure-subscription-service-limits.md) för uppdaterad information om kvoter.
## <a name="expressroute-peering"></a><a name="routingdomains"></a>ExpressRoute-peering
En ExpressRoute-krets har flera associerade routningsdomäner/peering-kopplingar: Azure offentlig, Azure Private och Microsoft. Varje peering konfigureras identiskt på ett par routrar (i aktiv-aktiv eller belastnings delnings konfiguration) för hög tillgänglighet. Azure-tjänster kategoriseras som *offentliga Azure* -tjänster och *Azure Private* för att representera IP-adressering-scheman.
### <a name="azure-private-peering"></a><a name="privatepeering"></a>Privat peering i Azure
Azure Compute Services, nämligen Virtual Machines (IaaS) och Cloud Services (PaaS), som distribueras i ett virtuellt nätverk kan anslutas via den privata peering-domänen. Den privata peering-domänen anses vara ett betrott tillägg till kärn nätverket i Microsoft Azure. Du kan konfigurera dubbelriktad anslutning mellan kärn nätverket och virtuella Azure-nätverk (virtuella nätverk). Med denna peering kan du ansluta till virtuella datorer och moln tjänster direkt på deras privata IP-adresser.
Du kan ansluta fler än ett virtuellt nätverk till den privata peering-domänen. På [sidan med vanliga frågor och svar](expressroute-faqs.md) hittar du information om begränsningar och begränsningar. Du kan gå till sidan för [Azure-prenumeration och tjänst begränsningar, kvoter och begränsningar](../azure-resource-manager/management/azure-subscription-service-limits.md) för uppdaterad information om begränsningar. På sidan [routning](expressroute-routing.md) hittar du detaljerad information om konfiguration av routning.
### <a name="microsoft-peering"></a><a name="microsoftpeering"></a>Microsoft-peering
[!INCLUDE [expressroute-office365-include](../../includes/expressroute-office365-include.md)]
Anslutning till Microsoft onlinetjänster (Microsoft 365 och Azure PaaS Services) sker via Microsoft-peering. Vi aktiverar dubbelriktad anslutning mellan dina WAN-och Microsofts moln tjänster via Microsoft-peering-routningsdomänen. Du måste bara ansluta till Microsofts moln tjänster över offentliga IP-adresser som ägs av dig eller anslutnings leverantören och du måste följa alla definierade regler. Mer information finns på sidan med [ExpressRoute-krav](expressroute-prerequisites.md) .
På [sidan med vanliga frågor och svar](expressroute-faqs.md) finns mer information om tjänster som stöds, kostnader och konfigurations information. På sidan [ExpressRoute locations](expressroute-locations.md) hittar du information om listan över anslutnings leverantörer som erbjuder stöd för Microsoft-peering.
## <a name="peering-comparison"></a><a name="peeringcompare"></a>Jämförelse av peering
I följande tabell jämförs de tre peer kopplingarna:
[!INCLUDE [peering comparison](../../includes/expressroute-peering-comparison.md)]
Du kan aktivera en eller flera av routningsdomänen som en del av din ExpressRoute-krets. Du kan välja att låta alla routningsdomäner placeras på samma VPN om du vill kombinera dem i en enda routningsdomän. Du kan också ställa in dem på olika routningsdomäner, ungefär som i diagrammet. Den rekommenderade konfigurationen är att privat peering är anslutet direkt till kärn nätverket och att länkarna för offentliga och Microsoft-peering är anslutna till din DMZ.
Varje peering kräver separata BGP-sessioner (ett par för varje peering-typ). BGP-session par innehåller en länk med hög tillgänglighet. Om du ansluter via Layer 2 anslutnings leverantörer ansvarar du för att konfigurera och hantera routning. Du kan lära dig mer genom att granska [arbets flöden](expressroute-workflows.md) för att konfigurera ExpressRoute.
## <a name="expressroute-health"></a><a name="health"></a>ExpressRoute-hälsa
ExpressRoute-kretsar kan övervakas för tillgänglighet, anslutning till virtuella nätverk och bandbredds användning med [övervakare av nätverksprestanda](../networking/network-monitoring-overview.md) (NPM).
NPM övervakar hälsan för Azures privata peering och Microsoft-peering. Se vår [post](https://azure.microsoft.com/blog/monitoring-of-azure-expressroute-in-preview/) för mer information.
## <a name="next-steps"></a>Nästa steg
* Hitta en tjänstleverantör. Se [ExpressRoute-tjänst leverantörer och platser](expressroute-locations.md).
* Kontrollera att alla krav är uppfyllda. Se [ExpressRoute-krav](expressroute-prerequisites.md).
* Konfigurera ExpressRoute-anslutningen.
* [Skapa och hantera ExpressRoute-kretsar](expressroute-howto-circuit-portal-resource-manager.md)
* [Konfigurera routning (peering) för ExpressRoute-kretsar](expressroute-howto-routing-portal-resource-manager.md) | 95.168675 | 524 | 0.813394 | swe_Latn | 0.9983 |
2f75d6e5e530f3f8ac1133bd8d07cbc456e2b3ff | 5,186 | md | Markdown | business-central/reports-saving-reusing-settings.md | MicrosoftDocs/dynamics365smb-docs-pr.fr-ch | e608bcc3a2872b5093eacd855748b3446fe3433b | [
"CC-BY-4.0",
"MIT"
] | 4 | 2017-08-28T10:44:48.000Z | 2022-03-09T12:56:55.000Z | business-central/reports-saving-reusing-settings.md | MicrosoftDocs/dynamics365smb-docs-pr.fr-ch | e608bcc3a2872b5093eacd855748b3446fe3433b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | business-central/reports-saving-reusing-settings.md | MicrosoftDocs/dynamics365smb-docs-pr.fr-ch | e608bcc3a2872b5093eacd855748b3446fe3433b | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-10-13T10:46:05.000Z | 2021-10-13T10:46:05.000Z | ---
title: Appliquer et modifier les paramètres enregistrés dans des états | Microsoft Docs
description: Décrit l’utilisation d’options et filtre prédéfinis pour personnaliser un état, et pour générer les données exactes.
author: SorenGP
ms.service: dynamics365-business-central
ms.topic: conceptual
ms.devlang: na
ms.tgt_pltfrm: na
ms.workload: na
ms.search.keywords: customization, personalization
ms.date: 04/01/2021
ms.author: edupont
ms.openlocfilehash: 6d83597057975757354da06668a7e71e94e5273f
ms.sourcegitcommit: a7cb0be8eae6ece95f5259d7de7a48b385c9cfeb
ms.translationtype: HT
ms.contentlocale: fr-CH
ms.lasthandoff: 07/08/2021
ms.locfileid: "6435778"
---
# <a name="manage-saved-settings-for-reports-and-batch-jobs"></a>Gérer les paramètres enregistrés pour les états et les traitements par lots
Lors de l’exécution d’un état, les utilisateurs voient généralement une page qui leur permet de sélectionner des options et de définir des filtres pour modifier les données incluses dans l’état généré. Cette page est appelée la page de demande. Un état peut inclure un ou plusieurs *paramètres enregistrés* que les utilisateurs peuvent appliquer à l’état à partir de la page de demande. Les *Paramètres enregistrés* sont essentiellement des options et des filtres prédéfinis. Le fait d’utiliser les paramètres enregistrés est une façon rapide et fiable de générer de façon cohérente des états qui contiennent les données adéquates. Pour plus d’informations, voir [Utilisation des paramètres enregistrés](ui-work-report.md#SavedSettings).
> [!NOTE]
> Cette rubrique fait référence surtout aux « états », mais des informations similaires s’appliquent aux traitements par lots.
Si vous avez les bonnes autorisations, vous pouvez visualiser, créer et modifier les paramètres enregistrés pour tous les états pour tous les utilisateurs de la société. Vous pouvez attribuer les paramètres enregistrés d’un état à des utilisateurs en particulier ou à tous les utilisateurs de la société.
<!--
## Apply saved settings to a report
1. Open the report.
The request page appears.
2. In the **Saved Settings** section of the page, set the **Name** field to the saved settings that you want to use.
The **Saved Settings** section only appears if the report has been run before or if there are existing saved settings entries. The saved settings entry called **Last used options and filters** is always available. These settings are the option and filter values that were used the last time you ran the report.
-->
## <a name="to-create-and-modify-saved-settings-for-all-users"></a>Pour créer et modifier les paramètres enregistrés pour tous les utilisateurs
Vous devez gérer les paramètres enregistrés à partir de la page **Paramètres des états**. Deux méthodes sont disponibles pour ouvrir cette page :
- Sélectionnez l’icône  entrez **Paramètres de l’état**, puis choisissez le lien associé.
- Ouvrez un état, sélectionnez la fonction Tell Me dans le champ **Utiliser les valeurs par défaut de**, puis choisissez l’action **Sélectionner dans la liste complète**.
La page affiche toutes les entrées de paramètres enregistrés existants pour tous les utilisateurs. Si un nom d’utilisateur est indiqué dans le champ **Affecté à**, seul cet utilisateur peut utiliser les paramètres enregistrés pour l’état associé. Si le champ **Partager avec tous les utilisateurs** est coché, tous les utilisateurs peuvent utiliser les paramètres enregistrés pour l’état.
Dans la page **Paramètres de l’état**, vous pouvez :
- Sélectionner l’action **Nouveau** pour créer une nouvelle entrée de paramètres enregistrés.
- Sélectionner une entrée de paramètres enregistrés dans la liste, puis choisir l’action **Copier** pour créer une copie.
- Sélectionner une entrée de paramètres enregistrés dans la liste, puis choisir l’action **Modifier** pour la modifier.
> [!Important]
> Définir le nom que vous souhaitez affecter à une entrée de paramètres enregistrés. Si vous créez une entrée de paramètres enregistrés pour tous les utilisateurs et vous lui donnez le même nom que l’entrée de paramètres enregistrés existants qui est affectée à un utilisateur spécifique, alors cet utilisateur ne pourra pas utiliser l’entrée de paramètres enregistrés qui est affectée à tous. Dans la section **Paramètres enregistrés** dans la page de demande de l’état, l’utilisateur verra deux entrées de paramètres enregistrés avec le même nom. Toutefois, peu importe l’option qu’il choisit, l’entrée de paramètres enregistrés qui lui est spécifique sera utilisée.
> [!NOTE]
> La fonctionnalité Paramètres enregistrés n’est disponible que pour les états où la propriété [SaveValues](/dynamics365/business-central/dev-itpro/developer/properties/devenv-savevalues-property) de la page de demande de l’état est définie sur **Oui**. La propriété **SaveValues** est définie dans l’environnement de développement.
## <a name="see-also"></a>Voir aussi
[Utilisation des états, des traitements par lots et des XMLports](ui-work-report.md)
[!INCLUDE[footer-include](includes/footer-banner.md)] | 85.016393 | 737 | 0.793868 | fra_Latn | 0.983985 |
2f7793094483e1590781c7f3d2fec468808553a7 | 4,330 | md | Markdown | docs/relational-databases/database-engine-tutorials.md | joshts0/sql-docs | 7064d7ea091ead7ba4916660c79b352ba4a911a1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/database-engine-tutorials.md | joshts0/sql-docs | 7064d7ea091ead7ba4916660c79b352ba4a911a1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/database-engine-tutorials.md | joshts0/sql-docs | 7064d7ea091ead7ba4916660c79b352ba4a911a1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Database Engine Tutorials | Microsoft Docs"
ms.custom: ""
ms.date: "08/02/2016"
ms.prod: sql
ms.prod_service: "database-engine, sql-database"
ms.component: "relational-databases-misc"
ms.reviewer: ""
ms.suite: "sql"
ms.technology: performance
ms.tgt_pltfrm: ""
ms.topic: conceptual
ms.assetid: 32bd8af8-a832-4dc8-afff-01668e6b2b51
caps.latest.revision: 14
author: "rothja"
ms.author: "jroth"
manager: craigg
monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017"
---
# Database Engine Tutorials
[!INCLUDE[appliesto-ss-asdb-xxxx-xxx-md](../includes/appliesto-ss-asdb-xxxx-xxx-md.md)]
This section contains tutorials for [!INCLUDE[ssDECurrent](../includes/ssdecurrent-md.md)].
[Tutorial: Getting Started with the Database Engine](../relational-databases/tutorial-getting-started-with-the-database-engine.md)
This tutorial teaches how to connect to an instance of the [!INCLUDE[ssDE](../includes/ssde-md.md)].
[Tutorial: SQL Server Management Studio](../tools/sql-server-management-studio/tutorial-sql-server-management-studio.md)
This tutorial introduces you to the integrated environment for managing your [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] infrastructure. [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)] presents a graphical interface for configuring, monitoring, and administering instances of [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)]. It also allows you to deploy, monitor, and upgrade the data-tier components used by your applications, such as databases and data warehouses. [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)] also provides [!INCLUDE[tsql](../includes/tsql-md.md)], MDX, DMX, and XML language editors for editing and debugging scripts.
[Tutorial: Writing Transact-SQL Statements](../t-sql/tutorial-writing-transact-sql-statements.md)
This tutorial teaches the fundamental skills of writing the [!INCLUDE[tsql](../includes/tsql-md.md)] statements for creating and managing objects in a [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] database.
[Tutorial: Database Engine Tuning Advisor](../tools/dta/tutorial-database-engine-tuning-advisor.md)
This tutorial introduces you to using the advisor to examine how queries are processed, and then review recommendations for improving query performance.
[Tutorial: Using the hierarchyid Data Type](../relational-databases/tables/tutorial-using-the-hierarchyid-data-type.md)
This tutorial teaches how to convert a table to a hierarchical structure, and then manage the data in the table.
[Tutorial: Signing Stored Procedures with a Certificate](../relational-databases/tutorial-signing-stored-procedures-with-a-certificate.md)
This tutorial illustrates signing stored procedures using a certificate generated by [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)].
[Tutorial: Ownership Chains and Context Switching](../relational-databases/tutorial-ownership-chains-and-context-switching.md)
This tutorial uses a scenario to illustrate [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] security concepts involving ownership chains and user context switching.
[Tutorial: Administering Servers by Using Policy-Based Management](../relational-databases/policy-based-management/tutorial-administering-servers-by-using-policy-based-management.md)
This tutorial teaches how to create policies that enforce site administration standards.
[Tutorial: SQL Server Backup and Restore to Windows Azure Blob Storage Service](~/relational-databases/tutorial-sql-server-backup-and-restore-to-azure-blob-storage-service.md)
This tutorial illustrates how to do a SQL Server backup and restore to the Windows Azure Blob Storage Service.
[Tutorial: Using the Microsoft Azure Blob storage service with SQL Server 2016 databases ](tutorial-use-azure-blob-storage-service-with-sql-server-2016.md)
This tutorial helps you understand how to store SQL Server data files in the Windows Azure Blob storage service directly.
## See Also
[Tutorials for SQL Server 2016](../sql-server/tutorials-for-sql-server-2016.md)
[TechNet WIKI: SQL Server 2012 Samples](http://go.microsoft.com/fwlink/?linkID=220734)
| 70.983607 | 691 | 0.77067 | eng_Latn | 0.774696 |
2f782c41ea190c4bea50c74f8f2f0f0256c067cb | 2,173 | md | Markdown | docs/_posts/2021-01-03-the-age-of-mind.md | lg565245594/fat-garage.com | 8197fa75cb6136a9bfd57d15974f5535d4910543 | [
"Apache-2.0"
] | 2 | 2021-02-06T04:41:03.000Z | 2021-06-20T06:51:15.000Z | docs/_posts/2021-01-03-the-age-of-mind.md | lg565245594/fat-garage.com | 8197fa75cb6136a9bfd57d15974f5535d4910543 | [
"Apache-2.0"
] | null | null | null | docs/_posts/2021-01-03-the-age-of-mind.md | lg565245594/fat-garage.com | 8197fa75cb6136a9bfd57d15974f5535d4910543 | [
"Apache-2.0"
] | 1 | 2021-03-26T07:48:40.000Z | 2021-03-26T07:48:40.000Z | ---
title: 欢迎来到，思维的吃播时代
author: jessie-li
categories: news
tags:
- home
- featured
image: assets/2021/01/03/1.png
---
某天下午，Conor在Twitter上发了一个Youtube直播 预告，就开始自己的无声roaming——“**直播记笔记**”
这让我发现了视频Live的一种别样吸引力：**记录连续的思考，在公众面前教·学**
没有预设脚本，不聊打折带货，可以没有声音，可以没有观众，只有咔咔的敲击键盘声，来记录自己**思考的痕迹**。这好像是一个漫游连续剧，你很难猜到主人公接下来要做什么。
但是，好有趣啊。
## Live的营养
### 思考模型（mental model）
我也会看一些非常有用的视频和播客，更多是技能性的增强。但这种live coding为我打开了另一道门——**学习别人的思考模型（mental model）**，有创造力的人是怎么思考的？为什么比你的学习能力更强？更能找到事物之间的联系？
比如Conor那个长达3小时的「实时Live记笔记」的视频，我会当做“吃播”一样，在餐饭闲时看一点，拌饭效果不亚于麻辣香菇酱。
这其实完全不同于#手把手教你 # N天速成 这样的快餐形式，**一个人是如何思考的，不是定制出来为了迎合大众的东西，是他自己想要解释给自己的东西**。比如我可以做科普，科普也很有用，但是科普短片中的我不是“思考模式”下的我。
### 发现最好的research partner
我最近也录了一些live roaming的视频 (文末)，记录学的东西、读的文章和书以及漫游的想法。完事后自己回看，竟然有种旁观者看一个博主在讲东西的感觉，有的地方我觉得她在瞎扯淡，有的地方我觉得她做的挺好。
在这里举两个例子，你可以感受一下我说的意思。
#### 清华：live coding 来讲机器学习
好友清华一直在研究机器学习和语义，他最近做了一些*live coding*来分享自己在这方面的专注，就算我看不懂很多代码的部分，但是完全不妨碍对这样的话题感兴趣，毕竟它和你熟知的东西息息相关，你可能用过知乎，有道翻译，或者最起码用过百度，所以你可能会好奇：*机器是怎么和人对话的*。
你可能不一定非要懂技术和它是怎么实现的，但你可以了解技术可能可以做什么。
#### Jessie：live roaming 用文本进行大脑编程
我最近在学习zettelkasten笔记法，于是做了一些live roaming去实践这种方法，同时也是因为闺蜜想了解我每天在吹逼的roamresearch到底是什么样的存在。
### 捕捉新的idea
这种live roaming 会让你不断的发现新的idea，并且以**直观的形式**记录下来。一般的直播往往带有很强的**公众目的性**，其实是很难保持专注的，对一些人来说就形成了所谓的“包袱”，对一些没有包袱的人一般是「大众想听啥我就说啥」。
但我觉得，**人们真正宝贵的东西，其实是不会跑到大街上叫卖的**，比如好的idea，回忆、隐私等等。这些东西只能放在相对私密的朋友社交圈的一些角落，这也是微信视频号和以陌生人社交为特色的抖音号目前来看的最大不同。
有点扯远，举个我在live roaming时发现新idea的例子。我昨天在用roam搭建网站的时候，突然发现roam中的smartblock中*<INPUT>*命令可以（在非编程的状态下）实现网页交互的效果。也就是说你不用会代码，就可以做一个交互式的网站。然后我当即就把这个idea录了下来，发给smartblock的创始人Chris，Chris说你666啊，我都没想到还可以这样玩🤣 。
## 请准备好，迎接思维吃播时代
在这个时代，在疲劳了满屏食物的吃播的时候，**看一些思维的吃播好像也挺有意思的**。所以不妨换一个角度看视频，去收集和抽象一些mental model，从中找到很多相似的或是极为差异化的大脑模型，它能帮我完善更本质的东西——怎么独立思考、怎么有效学习、怎么联系事物。而不是喂我吃已经被咀嚼、毫无营养甚至有毒的食物。
我觉得向优秀的人学习，不是局限在怎么写一段代码，怎么读一本书，更重要的可能是学习这个人mental model中适合你的部分，“他”怎么写出你想要的代码，“她”怎么写出你想要的文章，对自己的启发是什么。
**最后在胖车库小声的叫卖一下**，如果你对我的live roaming视频感兴趣（反正我自己拌饭是挺香的;），打赏8.8元并在留言区留下你的邮箱。我会邀请你到我的loom space，我可能有时候采个蘑菇，分析个经济模型，或垒个智慧区块啥的。
| 27.858974 | 194 | 0.811781 | yue_Hant | 0.482201 |
2f78b892f385c130226d6f6d5eb520e8a14b6bbf | 102 | md | Markdown | GCC_RX62N/README.md | manisimov/project_scratches | 157e954f1b11b62b7f2c8d93968298b3a00e4a9a | [
"MIT"
] | null | null | null | GCC_RX62N/README.md | manisimov/project_scratches | 157e954f1b11b62b7f2c8d93968298b3a00e4a9a | [
"MIT"
] | null | null | null | GCC_RX62N/README.md | manisimov/project_scratches | 157e954f1b11b62b7f2c8d93968298b3a00e4a9a | [
"MIT"
] | null | null | null | Template for YRDKRX62N demonstration kit
Flash tools and GDB server is here: https://www.segger.com/
| 25.5 | 59 | 0.794118 | eng_Latn | 0.701994 |
2f79a0caf4fe8b4e1e966ad16e9c6dbf2e7c5ca0 | 56 | md | Markdown | content/block/footer.md | MartinLedel/designv2 | 8641c485bb2df1c8b7b65af86228624f53883ce0 | [
"MIT"
] | null | null | null | content/block/footer.md | MartinLedel/designv2 | 8641c485bb2df1c8b7b65af86228624f53883ce0 | [
"MIT"
] | null | null | null | content/block/footer.md | MartinLedel/designv2 | 8641c485bb2df1c8b7b65af86228624f53883ce0 | [
"MIT"
] | null | null | null | 2018© Your bestfriend, [Google](https://www.google.se/)
| 28 | 55 | 0.714286 | nld_Latn | 0.174976 |
2f7a63491dfa28b6bb0383b91bc60b658a388540 | 2,567 | md | Markdown | articles/resource-management/define-resource-calendars.md | MicrosoftDocs/dynamics-365-project-operations-pr.pt-BR | e8a668c9a7df20f37dc8ee972243aa24bb5d083f | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-05-18T17:16:02.000Z | 2021-04-20T21:13:46.000Z | articles/resource-management/define-resource-calendars.md | MicrosoftDocs/dynamics-365-project-operations-pr.pt-BR | e8a668c9a7df20f37dc8ee972243aa24bb5d083f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/resource-management/define-resource-calendars.md | MicrosoftDocs/dynamics-365-project-operations-pr.pt-BR | e8a668c9a7df20f37dc8ee972243aa24bb5d083f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Definir calendários de recurso
description: Este tópico fornece informações sobre como definir os calendários de horas de trabalho para recursos no Project Operations.
author: ruhercul
manager: Annbe
ms.date: 10/05/2020
ms.topic: article
ms.service: dynamics-365-customerservice
ms.reviewer: kfend
ms.author: ruhercul
ms.openlocfilehash: ab39d7e5dc2d8c01ed49ca0f1a4d1691aaf15637
ms.sourcegitcommit: 396e0fea2f1598a5313cb0128eca4fe0bb5aade9
ms.translationtype: HT
ms.contentlocale: pt-BR
ms.lasthandoff: 10/05/2020
ms.locfileid: "3961812"
---
# <a name="define-resource-calendars"></a>Definir calendários de recurso
_**Aplica-se a:** operações de projeto para cenários baseados em recursos/não estocados, implantação Lite - transação para faturamento pró-forma_
Todos os recursos reserváveis que estiverem trabalhando em um projeto devem ter um calendário de horas de trabalho para definir sua disponibilidade. As horas de trabalho de um recurso podem ser definidas de duas formas:
- Definir regras de calendário individuais para um recurso
- Aplicar um modelo de calendário existente para o recurso
## <a name="define-a-resources-working-hours"></a>Definir as horas de trabalho de um recurso
1. No menu **Recursos**, selecione **Recursos**.
2. Na visualização de grade, selecione o **Recurso Reservável** aplicável.
3. Na página **Detalhes do Recurso**, selecione a guia **Horas de Trabalho**. Por padrão, o calendário de recursos reserváveis é padronizado com as horas de trabalho do modelo padrão de horas de trabalho definido pela organização.
4. Para atualizar as horas de trabalho, clique com o botão direito na data de início da regra de calendário proposta que será definida. Use o menu de regra de calendário para definir a regra de calendário para um dia específico, o restante da série ou todo o calendário.
5. Depois de selecionar a opção, é possível definir:
- O dia da semana ao qual as horas de trabalho serão aplicadas.
- As horas de trabalho de cada dia.
- O fuso horário da regra de calendário.
- Se aplicável, o tempo de folga também poderá ser especificado para a regra.
## <a name="applying-a-calendar-template-to-a-resource"></a>Aplicando um modelo de calendário a um recurso
1. No menu **Recursos**, selecione **Recursos**.
2. Na visualização de grade, selecione até 25 **Recursos Reserváveis** para atualizar.
3. Selecione **Definir Calendário** e uma caixa de diálogo exibirá uma lista de modelos de horas de trabalho disponíveis.
4. Selecione o modelo que deseja usar e depois selecione **Aplicar**.
| 55.804348 | 270 | 0.783015 | por_Latn | 0.999626 |
2f7a6d0279d9c55ea2d329401f45a8a5b9d561f0 | 492 | md | Markdown | docs/markdown/ivopetkov.dataobject.fromarray.method.md | ivopetkov/data-object | e686c4669b9b6b08990fef0ac691a4cc2a64526c | [
"MIT"
] | 4 | 2018-01-09T16:44:15.000Z | 2022-02-17T11:28:49.000Z | docs/markdown/ivopetkov.dataobject.fromarray.method.md | ivopetkov/data-object | e686c4669b9b6b08990fef0ac691a4cc2a64526c | [
"MIT"
] | 2 | 2018-01-09T18:36:23.000Z | 2018-11-22T08:33:31.000Z | docs/markdown/ivopetkov.dataobject.fromarray.method.md | ivopetkov/data-object | e686c4669b9b6b08990fef0ac691a4cc2a64526c | [
"MIT"
] | 3 | 2017-01-13T09:09:44.000Z | 2019-10-19T04:34:57.000Z | # IvoPetkov\DataObject::fromArray
Creates an object and fills its properties from the array specified.
```php
public static object fromArray ( array $data )
```
## Parameters
##### data
The data used for the object properties.
## Returns
Returns a newly constructed object.
## Details
Class: [IvoPetkov\DataObject](ivopetkov.dataobject.class.md)
Location: ~/src/DataObject.php
---
[back to index](index.md)
| 16.965517 | 76 | 0.721545 | eng_Latn | 0.604318 |
2f7a95a4180a14de1138e7b07db5335c1a9d2821 | 5,987 | md | Markdown | lib/README.md | MaxySpark/ng2-tooltip-directive | 078d5eb9ec501f5f67021fda4dc033792010c139 | [
"MIT"
] | null | null | null | lib/README.md | MaxySpark/ng2-tooltip-directive | 078d5eb9ec501f5f67021fda4dc033792010c139 | [
"MIT"
] | null | null | null | lib/README.md | MaxySpark/ng2-tooltip-directive | 078d5eb9ec501f5f67021fda4dc033792010c139 | [
"MIT"
] | null | null | null | # Tooltip for Angular
#### Fork From [ng2-tooltip-directive](https://www.npmjs.com/package/ng2-tooltip-directive)
The tooltip is a pop-up tip that appears when you hover over an item or click on it.
## Installation
Install the npm package.
npm i ngx-tooltip-directive
Import `Ng2Module`:
```ts
import { TooltipModule } from 'ngx-tooltip-directive';
@NgModule({
imports: [ TooltipModule ]
})
```
## Usage
Options can be set in the directive tag, so they have the highest priority.
```html
<span tooltip="Tooltip" placement="top" show-delay="500">Tooltip on top</span>
```
You may pass as an object:
```html
<span tooltip="Tooltip" [options]="myOptions">Tooltip on left</span>
```
```ts
myOptions = {
'placement': 'left',
'show-delay': 500
}
```
You can pass HTML as content :
```html
<span tooltip="<p>Hello i'm a <strong>bold</strong> text!</p>">
Tooltip with HTML content
</span>
```
```html
<ng-template #HtmlContent>
<p>Hello i'm a <strong>bold</strong> text!</p>
</ng-template>
<span [tooltip]="HtmlContent" content-type="template">
Tooltip with template content
</span>
```
## Set default values
Create a file with your settings, for example:
```ts
import { TooltipOptions } from 'ng2-tooltip-directive';
export const MyDefaultTooltipOptions: TooltipOptions = {
'show-delay': 500
}
```
And pass your parameters when importing the module:
```ts
import { TooltipModule, TooltipOptions } from 'ngx-tooltip-directive';
import { MyDefaultTooltipOptions } from './my-default-options';
@NgModule({
imports: [
TooltipModule.forRoot(MyDefaultTooltipOptions as TooltipOptions)
]
})
```
## Properties
| name | type | default | description |
|------------------|-------------------------------------|---------|---------------------------------------------|
| placement | "top", "bottom", "left", "right" | "top" | The position of the tooltip. |
| autoPlacement | boolean | true | Place the tooltip so that it does not go beyond the borders of the browser window. |
| show-delay | number | 0 | The delay in ms before showing the tooltip. |
| hide-delay | number | 300 | The delay in ms before removing the tooltip. |
| hideDelayTouchscreen | number | 0 | Delay in milliseconds before hiding the tooltip (for mobile devices). |
| display | boolean | true | Tooltip availability for display. |
| displayTouchscreen | boolean | true | Display the tooltip on mobile devices. |
| z-index | number | 0 | Z-index of the tooltip. |
| trigger | "hover", "click" | "hover" | Specifies how the tooltip is triggered. Control the closing time with "hide-delay". |
| tooltip-class | string | | Classes to be passed to the tooltip. |
| animation-duration | number | 300 | The duration controls how long the animation takes to run from start to finish. |
| theme | "dark", "light" | "dark" | Theme of tooltip background and text. |
| shadow | boolean | true | Shadow of the tooltip. |
| offset | number | 8 | Offset the tooltip relative to the item. |
| width | number | undefined | Width of the tooltip. |
| max-width | number | 200 | Maximum width of the tooltip. |
| content-type | "string", "html', "template" | "string" | The content type passed to the tooltip. |
| hideDelayAfterClick | number | 2000 | Tooltip hiding delay for "click" trigger. |
| pointerEvents | "auto", "none" | "none" | Defines whether or not an element reacts to pointer events. |
| position | {top: number, left: number} | undefined | The tooltip coordinates relative to the browser window. |
## Events
When you call events, the delays that are specified in the options in the directive are taken into account. Default delay before tooltip hiding is 300 milliseconds.
| Event | Description |
|------------------|---------------------------------------------------------------------------------------------|
| {type: "show", position: DOMRect} | The event is called before the tooltip appears. |
| {type: "shown", position: DOMRect} | The event is called after the animation of the appearance of the tooltip. |
| {type: "hide", position: DOMRect} | The event is called before the tooltip is hidden. |
| {type: "hidden", position: DOMRect} | The event is called after the animation of the tooltip is hidden. |
## Methods
If you specified the directive options, they will be taken into account when calling methods. Including the delay before the appearance and hiding of the tooltip.
| Method | Description |
|------------------|---------------------------------------------------------------------------------------------|
| show() | Shows the tooltip |
| hide() | Hides the tooltip |
## Sponsors
We use Browserstack for cross-browser testing.
[](http://browserstack.com/)
| 44.348148 | 164 | 0.5233 | eng_Latn | 0.948676 |
2f7c0680e631fa7f7778386a9c220d940eb65527 | 571 | md | Markdown | docs/notion-types.aggregationresult.md | The-hated-one/react-notion-x | cd71131f38e0f5c849bba4bc5054e8e2814657c8 | [
"MIT"
] | 2,080 | 2020-10-07T16:25:19.000Z | 2022-03-31T08:46:32.000Z | docs/notion-types.aggregationresult.md | The-hated-one/react-notion-x | cd71131f38e0f5c849bba4bc5054e8e2814657c8 | [
"MIT"
] | 211 | 2020-10-07T07:24:46.000Z | 2022-03-31T19:10:22.000Z | docs/notion-types.aggregationresult.md | The-hated-one/react-notion-x | cd71131f38e0f5c849bba4bc5054e8e2814657c8 | [
"MIT"
] | 282 | 2020-10-16T16:13:52.000Z | 2022-03-31T23:29:11.000Z | <!-- Do not edit this file. It is automatically generated by API Documenter. -->
[Home](./index.md) > [notion-types](./notion-types.md) > [AggregationResult](./notion-types.aggregationresult.md)
## AggregationResult interface
<b>Signature:</b>
```typescript
export interface AggregationResult
```
## Properties
| Property | Type | Description |
| --- | --- | --- |
| [type](./notion-types.aggregationresult.type.md) | [PropertyType](./notion-types.propertytype.md) | |
| [value](./notion-types.aggregationresult.value.md) | any | |
| 28.55 | 120 | 0.654991 | eng_Latn | 0.260618 |
2f7cb57d9d7ef4dd8de7912f5ec6fc9ee039794d | 2,716 | md | Markdown | README.md | lissettecarlr/lissettecarlr.github.io | d1cff0531390c2c314d84f467756828458221c70 | [
"MIT"
] | 1 | 2021-08-14T05:30:56.000Z | 2021-08-14T05:30:56.000Z | README.md | lissettecarlr/lissettecarlr.github.io | d1cff0531390c2c314d84f467756828458221c70 | [
"MIT"
] | null | null | null | README.md | lissettecarlr/lissettecarlr.github.io | d1cff0531390c2c314d84f467756828458221c70 | [
"MIT"
] | null | null | null | teedoc website template
=====
**[中文 README](./README_ZH.md) | English README**
This template supported by teedoc, visit: [teedoc.neucrack.com](https://teedoc.neucrack.com/) or [teedoc.github.io](https://teedoc.github.io) learn more
## build locally
* Install python3
On `Windows` or `macOS`, download from [python.org](https://www.python.org/downloads/)
On `Linux`, `Ubuntu` for example:
```
sudo apt install python3 python3-pip
```
* Install teedoc
This command will **install teedoc program**
```
pip3 install teedoc
```
* Initialize document
```
mkdir my_site
cd my_site
teedoc init
```
or
```
teedoc -d my_site init
```
* Install plugins
This command will **install plugins** used by doc(set in `site_config.json`)
```
cd my_site
teedoc install
```
* build or serve
```
teedoc serve
```
then visit [http://127.0.0.1:2333](http://127.0.0.1:2333) in browser
If you only want to generate htmls:
```
teedoc build
```
## Create your website on github pages in minutes
### Create a repository based on a template
* Visit [https://github.com/teedoc/template](https://github.com/teedoc/template) or [https://github.com/teedoc/teedoc.github.io](https://github.com/teedoc/teedoc.github.io), click `Use this template`
* Set the name of the new repository to `username or organization name.github.io`, select the public repository, and then confirm the submission
> Then use `git clone your repository address` to clone to the local
### Set up pages service
* Wait for the automatic build to generate a new branch `gh-pages`, you can click on the `Actions` column to view the progress of the automatic build, if a green tick appears, it means it is OK, if a red cross appears, the build fails Yes, where is the problem, you can click in to view the log according to the screenshot method below (you must submit a screenshot of the log) and submit [issue](https://github.com/teedoc/teedoc.github.io/issues/ new) feedback
If there is an error, you can click to view the error log according to the following figure:
* Set the `pages` service of the repository and select the `gh-pages` branch. If there is no such branch, the previous step has not been completed or an error occurred. You can view the issue submission [issue](https://github.com/ teedoc/teedoc.github.io/issues/new) feedback
* Then visit `username or organization name.github.io`, you will find a webpage, the content is exactly the same as `teedoc.github.io`!
| 27.16 | 461 | 0.736009 | eng_Latn | 0.965642 |
2f7d15ed4ba496415d7bc43593ad4eaef2dc948a | 1,265 | md | Markdown | includes/storsimple-8000-delete-backup-policy.md | changeworld/azure-docs.sv-se | 6234acf8ae0166219b27a9daa33f6f62a2ee45ab | [
"CC-BY-4.0",
"MIT"
] | null | null | null | includes/storsimple-8000-delete-backup-policy.md | changeworld/azure-docs.sv-se | 6234acf8ae0166219b27a9daa33f6f62a2ee45ab | [
"CC-BY-4.0",
"MIT"
] | null | null | null | includes/storsimple-8000-delete-backup-policy.md | changeworld/azure-docs.sv-se | 6234acf8ae0166219b27a9daa33f6f62a2ee45ab | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
author: alkohli
ms.service: storsimple
ms.topic: include
ms.date: 10/26/2018
ms.author: alkohli
ms.openlocfilehash: b7a86963c657524fa91c4eb824ced1a495391f3f
ms.sourcegitcommit: 2ec4b3d0bad7dc0071400c2a2264399e4fe34897
ms.translationtype: MT
ms.contentlocale: sv-SE
ms.lasthandoff: 03/28/2020
ms.locfileid: "67187537"
---
#### <a name="to-delete-a-storsimple-backup-policy"></a>Så här tar du bort en StorSimple-princip för säkerhetskopiering
1. Gå till din StorSimple-enhet och klicka på **Säkerhetskopieringspolicy**.
2. Välj den princip som du vill ta bort i tabelllistan för principer för säkerhetskopiering. Högerklicka och välj **Ta bort**på snabbmenyn .
3. Du uppmanas att bekräfta. Tänk på att om du tar bort en princip för säkerhetskopiering tas alla associerade säkerhetskopior bort. Klicka på **Ja** om du vill ta bort.
Listan över principer för säkerhetskopiering uppdateras för att visa den nya listan med principer.
 | 45.178571 | 169 | 0.797628 | swe_Latn | 0.974265 |
2f7d276756cdc15b5d830ed179cb358e0769770e | 413 | md | Markdown | _publications/2014-DBLP_conf_semweb_FetahuGD14.md | bfetahu/bfetahu.github.io | d15a3470dee68fa93bbb5c76e60fe187d5f9f9b4 | [
"MIT"
] | null | null | null | _publications/2014-DBLP_conf_semweb_FetahuGD14.md | bfetahu/bfetahu.github.io | d15a3470dee68fa93bbb5c76e60fe187d5f9f9b4 | [
"MIT"
] | null | null | null | _publications/2014-DBLP_conf_semweb_FetahuGD14.md | bfetahu/bfetahu.github.io | d15a3470dee68fa93bbb5c76e60fe187d5f9f9b4 | [
"MIT"
] | 1 | 2020-04-14T16:41:35.000Z | 2020-04-14T16:41:35.000Z | ---
title: "Crawl Me Maybe: Iterative Linked Dataset Preservation"
authors: "Fetahu, Besnik; Gadiraju, Ujwal; Dietze, Stefan"
collection: publications
permalink: /publication/2014-DBLP_conf_semweb_FetahuGD14
date: 2014-01-01
venue: "Proceedings of the ISWC 2014 Posters & Demonstrations Track a track within the 13th International Semantic Web Conference, ISWC 2014, Riva del Garda, Italy, October 21, 2014"
--- | 51.625 | 184 | 0.789346 | yue_Hant | 0.289313 |
2f7e9b449ebaad65de3e716dbb60efea5a08b1ce | 22,740 | md | Markdown | docs/docs.md | axner001/manifold | 3e8bc2ed8a8134b65a7b3b5395715165eff1be88 | [
"Apache-2.0"
] | null | null | null | docs/docs.md | axner001/manifold | 3e8bc2ed8a8134b65a7b3b5395715165eff1be88 | [
"Apache-2.0"
] | null | null | null | docs/docs.md | axner001/manifold | 3e8bc2ed8a8134b65a7b3b5395715165eff1be88 | [
"Apache-2.0"
] | null | null | null | ---
layout: default
---
## Table of Contents
* [Overview](#overview)
* [Type-safe Metaprogramming](#type-safe-metaprogramming-via-_type-manifolds_)
* [Java Extensions via the _Extension_ Manifold](#java-extensions-via-the-_extension_-manifold)
* [Benefits](#benefits)
* [Projects](#projects)
* [IDE Support](#ide-support)
* [**Setup**](#setup)
* [Download](#download)
* [License](#license)
* [Author](#author)
# Overview
[Manifold](https://manifold.systems/) plugs directly into Java to supplement it with powerful features you can use
directly in your projects:
* [**Type-safe Metaprogramming**](https://github.com/manifold-systems/manifold/tree/master/manifold-core-parent/manifold) -- _type-safe_ access to structured data.
Use [GraphQL](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-graphql),
[XML](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-xml),
[JSON](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-json),
[YAML](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-yaml),
[CSV](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-csv),
[JavaScript](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-js),
[Templates](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-templates), etc.
directly and type-safely from Java without a code generator in your build and with comprehensive IDE support.
* [**Java Extensions**](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-ext) --
provides extension methods (like [C#](https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/classes-and-structs/extension-methods)),
[operator overloading](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-ext#operator-overloading),
[unit expressions](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-ext#unit-expressions),
structural typing (like [TypeScript](https://www.typescriptlang.org/docs/handbook/interfaces.html)),
string interpolation (like [Kotlin](https://kotlinlang.org/docs/reference/basic-types.html#string-templates)),
type-safe reflection (via [`@Jailbreak`](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-collections#type-safe-reflection-via-jailbreak)),
and a lot more.
# Type-safe Metaprogramming via _Type Manifolds_
Bridging the worlds of data and code, a *type manifold* acts as an adapter to automatically connect data resources to
Java's type system. The core Manifold framework seamlessly plugs into the Java compiler enabling a type manifold to
transform structured data into a data _type_ directly accessible in your Java code eliminating code generation build
steps otherwise required with conventional tools. Additionally the [Manifold plugin for IntelliJ IDEA](#ide-support)
provides comprehensive integration for type manifolds. Types are always in sync; changes you make to resources are
immediately available in the type system _without a compilation step_. Code completion, navigation, usage searching,
refactoring, incremental compilation, hotswap debugging -- all seamlessly integrated. With type manifolds a data file
is a virtual data _type_.
To illustrate, consider this simple properties resource file:
`/abc/MyProperties.properties`
```properties
chocolate = Chocolate
chocolate.milk = Milk chocolate
chocolate.dark = Dark chocolate
```
Normally in Java you access a properties file like this:
```java
Properties myProperties = new Properties();
myProperties.load(getClass().getResourceAsStream("/abc/MyProperties.properties"));
String myMessage = myProperties.getProperty("chocolate.milk");
```
As with any resource file a properties file is foreign to Java's type system -- there is no direct, type-safe access to
it. Instead you access it indirectly using boilerplate library code sprinkled with hard-coded strings.
By contrast, with the Properties type manifold you access a properties file directly as a type:
```java
String myMessage = MyProperties.chocolate.milk;
```
Concise and type-safe, with no additional build steps to engage.
Any data resource is a potential type manifold, including file schemas, query languages, database definitions,
data services, templates, spreadsheets, and programming languages.
Manifold provides type manifolds for:
* [GraphQL](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-graphql)
* [JSON and JSON Schema](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-json)
* [XML](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-xml)
* [YAML](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-yaml)
* [CSV](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-csv)
* [Properties files](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-properties)
* [Image files](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-image)
* [Dark Java](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-darkj)
* [JavaScript](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-js)
* [Java Templates](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-templates)
# Java Extensions via the _Extension_ Manifold
The extension manifold is a special kind of type manifold that lets you augment existing Java classes including Java's
own runtime classes such as `String`. You can add new methods, annotations, and interfaces to any type your project
uses.
Let's say you want to make a new method on `String` so you can straightforwardly echo a String to the console. Normally
with Java you might write a "Util" library like this:
```java
public class MyStringUtil {
public static void echo(String value) {
System.out.println(value);
}
}
```
And you'd use it like this:
```java
MyStringUtil.echo("Java");
```
Instead with Manifold you create an _**Extension Class**_:
```java
@Extension
public class MyStringExtension {
public static void echo(@This String thiz) {
System.out.println(thiz);
}
}
```
Here we've added a new `echo()` method to `String`, so we use it like this:
```java
"Java".echo();
```
Extensions eliminate a lot of intermediate code such as "Util" and "Manager" libraries as well as Factory classes. As a
consequence extensions naturally promote higher levels of object-orientation, which result in more readable and
maintainable code. Additionally, with the Manifold IntelliJ plugin you can use code-completion which conveniently
presents all the extension methods available on an extended class:
<p>
<video height="60%" width="60%" controls="controls" preload="auto" onclick="this.paused ? this.play() : this.pause();">
<source type="video/mp4" src="/images/ExtensionMethod.mp4">
</video>
</p>
There's a lot more to the extension manifold including [operator overloading](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-ext#operator-overloading),
[unit expressions](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-ext#unit-expressions),
[structural interfaces](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-ext#structural-interfaces-via-structural),
which are similar to interfaces in the [Go](https://golang.org/) and [TypeScript](https://www.typescriptlang.org/docs/handbook/interfaces.html)
languages. See the [Java Extension Manifold](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-ext)
for full coverage of these features.
# Benefits
Manifold's core technology is a dramatic departure from conventional Java tooling. There are no code generation steps in
the build, no extra build target files to manage, no annotation processors, and no extra class loaders to engage at
runtime.
Benefits of this approach include:
* **Zero turnaround** -- direct, type-safe access to structured data
* **Lightweight** -- requires no special compilers, annotation processors, or runtime agents
* **Efficient** -- Manifold only produces types as they are needed
* **Simple, open API** -- use the Manifold API to build your own components and extensions
* **No code generation build step** -- integrates directly with the Java compiler
* **Incremental** -- only builds types that have changed
* **[IntelliJ IDEA](https://www.jetbrains.com/idea/download)** support -- all manifold types and extensions work with IntelliJ
Manifold is just a dependency you can drop into your existing project -- you can begin using it incrementally without
having to rewrite classes or conform to a new way of doing things.
# IDE Support
Use the [Manifold IntelliJ IDEA plugin](https://plugins.jetbrains.com/plugin/10057-manifold) to experience Manifold to its fullest.
The plugin currently supports most high-level IntelliJ features including:
* Feature highlighting
* Error reporting
* Code completion
* Go to declaration
* Usage searching
* Rename/Move refactoring
* Quick navigation
* Operator overloading
* Unit expressions
* Structural typing
* Type-safe reflection with `@Jailbreak`
* Self type support with `@Self`
* Incremental compilation
* Hotswap debugging
* Preprocessor (conditional compilation)
* Professional template file editor
The IntelliJ plugin provides comprehensive support for Manifold. Use code completion to discover and use type manifolds,
extension methods and structural interfaces. Jump directly from usages of extension methods to their declarations.
Likewise, jump directly from references to resource elements and find usages of them in your code. Watch your
JSON/YAML/XML/CSV, images, properties, templates, and custom type manifolds come alive as types. Changes you make are
instantly available in your code.
Install the plugin directly from IntelliJ via:
<kbd>Settings</kbd> ➜ <kbd>Plugins</kbd> ➜ <kbd>Marketplace</kbd> ➜ search: `Manifold`
# Projects
The Manifold framework consists of the *core project* and a collection of *sub-projects* implementing SPIs provided
by the core. Each project represents a separate *dependency* you can use directly in your project. See details in each
projects' docs.
### Core Framework
* [Manifold : _Core_](https://github.com/manifold-systems/manifold/tree/master/manifold-core-parent/manifold)
### Resource Manifolds
* [Manifold : _GraphQL_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-graphql)
* [Manifold : _JSON_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-json)
* [Manifold : _XML_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-xml)
* [Manifold : _CSV_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-csv)
* [Manifold : _YAML_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-yaml)
* [Manifold : _Properties_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-properties)
* [Manifold : _Image_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-image)
* [Manifold : _Dark Java_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-darkj)
* [Manifold : _JavaScript_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-js)
### Java Extension Manifold
* [Manifold : _Java Extension_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-ext)
### Java Templates Framework
* [Manifold : _Templates_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-templates)
### Java Compiler Extensions
* [Manifold : _String Templates_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-strings) <small>(string interpolation)</small>
* [Manifold : _[Un]checked_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-exceptions)
### Java Preprocessor
* [Manifold : _Preprocessor_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-preprocessor)
### Java Science
* [Manifold : _Science_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-science)
### Java Extension Libraries
* [Manifold : _Collections_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-collections)
* [Manifold : _I/0_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-io)
* [Manifold : _Text_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-text)
### Manifold "Fat" Jar
[Manifold : _All (Über jar)_](https://github.com/manifold-systems/manifold/tree/master/manifold-all)
### Sample Projects
* [Manifold sample project](https://github.com/manifold-systems/manifold-sample-project)
* [Manifold sample GraphQL project](https://github.com/manifold-systems/manifold-sample-graphql-app)
* [Manifold sample REST API project](https://github.com/manifold-systems/manifold-sample-rest-api)
* [Manifold sample Web App project](https://github.com/manifold-systems/manifold-sample-web-app)
* [Manifold sample Gradle Project](https://github.com/manifold-systems/manifold-simple-gradle-project)
# Setup
Manifold is designed to work with most build systems, including Maven and Gradle.
The Manifold root project consists of several sub-projects you can include separately in your build, see [Projects](#projects)
above for a complete listing. You can also integrate all Manifold dependencies into your build using the "Fat" Jar
dependency, [`manifold-all`](https://github.com/manifold-systems/manifold/tree/master/manifold-all).
Setup instructions are consistent for each sub-project/dependency. Here are direct links:
* Setup for [Manifold : _All_](https://github.com/manifold-systems/manifold/tree/master/manifold-all#setup)
<hr/>
* Setup for [Manifold : _Core_](https://github.com/manifold-systems/manifold/tree/master/manifold-core-parent/manifold#setup)
<hr/>
* Setup for [Manifold : _GraphQL_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-graphql#setup)
* Setup for [Manifold : _XML_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-xml#setup)
* Setup for [Manifold : _JSON_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-json#setup)
* Setup for [Manifold : _CSV_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-csv#setup)
* Setup for [Manifold : _YAML_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-yaml#setup)
* Setup for [Manifold : _Properties_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-properties#setup)
* Setup for [Manifold : _Image_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-image#setup)
* Setup for [Manifold : _Dark Java_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-darkj#setup)
* Setup for [Manifold : _JavaScript_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-js#setup)
<hr/>
* Setup for [Manifold : _Java Extension_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-ext#setup)
<hr/>
* Setup for [Manifold : _Templates_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-templates#setup)
<hr/>
* Setup for [Manifold : _String Templates_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-strings#setup)
* Setup for [Manifold : _[Un]checked_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-exceptions#setup)
<hr/>
* Setup for [Manifold : _Preprocessor_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-preprocessor#setup)
<hr/>
* Setup for [Manifold : _Science_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-science#setup)
<hr/>
* Setup for [Manifold : _Collections_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-collections#setup)
* Setup for [Manifold : _I/0_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-io#setup)
* Setup for [Manifold : _Text_](https://github.com/manifold-systems/manifold/tree/master/manifold-deps-parent/manifold-text#setup)
# Download
For the convenience of non-maven/non-gradle users you can directly download latest release binaries below.
>**WARNING** If you plan to build your project **without** Maven or Gradle using select binaries (as opposed to manifold-all),
your classpath **must** include the **transitive closure** of binaries in terms of the **dependencies** declared in corresponding
project's POM file. Additionally, you will need to adapt your build to reflect the Maven or Gradle setup instructions
from the list above.
>
>For instance, to use the *manifold-preprocessor* jar using **Ant** your project needs:
>* [manifold-preprocessor-2020.1.2.jar](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-preprocessor&v=RELEASE)
>* [manifold-2020.1.2.jar](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold&v=RELEASE)
>* [manifold-util-2020.1.2.jar](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-util&v=RELEASE)
>* [antlr-runtime-4.7.jar](https://www.antlr.org/download/antlr-runtime-4.7.jar)
>
>As such your *javac* command line should include:
>```text
>javac -Xplugin:Manifold -classpath <jar-path>/manifold-preprocessor-2020.1.2.jar;<jar-path>/manifold-2020.1.2.jar;<jar-path>/manifold-util-2020.1.2.jar;<jar-path>/antlr-runtime-4.7.jar
>```
* Download [manifold : _All_](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-all&v=RELEASE):
<hr/>
* Download [Manifold : _Core_](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold&v=RELEASE)
<hr/>
* Download [Manifold : _GraphQL_](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-graphql&v=RELEASE)
* Download [Manifold : _XML_](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-xml&v=RELEASE)
* Download [Manifold : _JSON_](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-json&v=RELEASE)
* Download [Manifold : _CSV_](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-csv&v=RELEASE)
* Download [Manifold : _YAML_](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-yaml&v=RELEASE)
* Download [Manifold : _Properties_](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-properties&v=RELEASE)
* Download [Manifold : _Image_](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-image&v=RELEASE)
* Download [Manifold : _Dark Java_](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-darkj&v=RELEASE)
* Download [Manifold : _JavaScript_](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-js&v=RELEASE)
<hr/>
* Download [Manifold : _Java Extension_](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-ext&v=RELEASE)
<hr/>
* Download [Manifold : _Templates_](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-templates&v=RELEASE)
<hr/>
* Download [Manifold : _String Templates_](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-strings&v=RELEASE)
* Download [Manifold : _[Un]checked_](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-exceptions&v=RELEASE)
<hr/>
* Download [Manifold : _Preprocessor_](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-preprocessor&v=RELEASE)
<hr/>
* Download [Manifold : _Science_](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-science&v=RELEASE)
<hr/>
* Download [Manifold : _Collections_](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-collections&v=RELEASE)
* Download [Manifold : _I/0_](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-io&v=RELEASE)
* Download [Manifold : _Text_](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-text&v=RELEASE)
<hr/>
* Download [Manifold : Util](https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=systems.manifold&a=manifold-util&v=RELEASE)
* [Antlr : Runtime](https://www.antlr.org/download/antlr-runtime-4.7.jar) _Note the antlr runtime library is a dependency of manifold-util_
# License
## Open Source
Manifold is licensed under the [Apache 2.0](http://www.apache.org/licenses/LICENSE-2.0) license.
## Commercial
Commercial licenses for this work are available. These replace the above ASL 2.0 and offer limited warranties, support,
maintenance, and commercial server integrations.
For more information contact: [admin@manifold.systems](mailto:admin@manifold.systems)
# Author
* [Scott McKinney](mailto:scott@manifold.systems) | 57.424242 | 191 | 0.785972 | eng_Latn | 0.542629 |
2f7eda79cb3b514003f009efbad5e621bcfc271e | 3,997 | md | Markdown | docs/README.md | Expanduino/Expanduino-Arduino | c7a2fc0dfedb7b648610e90e46fc4be644254f3f | [
"Unlicense"
] | null | null | null | docs/README.md | Expanduino/Expanduino-Arduino | c7a2fc0dfedb7b648610e90e46fc4be644254f3f | [
"Unlicense"
] | 1 | 2016-03-25T22:26:19.000Z | 2016-08-31T11:44:18.000Z | docs/README.md | Expanduino/Expanduino-Arduino | c7a2fc0dfedb7b648610e90e46fc4be644254f3f | [
"Unlicense"
] | null | null | null | # Expanduino-Arduino
Arduino library that implements Expanduino protocol
You just built yourself a nice Arduino-based peripheral device, and now, you need to communicate with a Linux box?
You can read and write data over the Serial port using your own software (You are probably doing it already).
But if your device is just a bunch of buttons, leds, serial ports, etc, why bother?
There should be a kernel driver to make it work out-of-the box.
**This is what the expanduino library is there for!**
# Composite devices
An Expanduino device is a composite of several sub-devices
For instance, if you have your arduino connected to a keypad, a bunch of leds, a serial port and an LCD, it will be attached to several subsystems in the linux kernel:
- [Input subsystem](https://github.com/torvalds/linux/blob/master/Documentation/input/input.txt), will create an entry in `/dev/input` to access the keypad.
- [Led class](https://github.com/torvalds/linux/blob/master/Documentation/leds/leds-class.txt), will create entries in `/sys/class/leds/` for each led.
- [Serial driver](https://github.com/torvalds/linux/blob/master/Documentation/serial/driver), will create entries in `/dev/tty***` for each serial port
- [Misc devices](http://www.linuxjournal.com/article/2920) will create `/dev/mything` for all the non-standard components, like LCD displays.
# Basic Protocol
Every requests starts with a "register byte" which identified the device (upper nibble) and the operation (lower nibble).
The special device #0 is reserved for metadata.
The special function #0 resets the device
# Special Device #0
Functions:
1. getNumDevices()
- Parameters: None
- Response: number of devices (1 byte)
1. Function #1: getDeviceType()
- Parameters: device number (1 byte)
- Response: device type (1 byte)
1. Function #2: getInterrupts()
- Parameters: None
- Response: interrupt flags for each sub-device. Device #0 is an OR of all other devices (2 byte))
# LED Device (DeviceType #1)
Functions:
1. getNumLeds()
- Parameters: None
- Response: number of leds (1 byte)
1. getLedName()
- Parameters: led number (1 byte)
- Response: 32 bytes, Led name
1. getLedBrightness()
- Parameters: led number (1 byte)
- Response: brightness (1 byte)
1. setLedBrightness()
- Parameters: led number (1 byte), brightness (1 byte)
- Response: none
# GPIO Device (DeviceType #2)
Enums:
1. GPIO_FLAGS = `GPIO_OUTPUT | GPIO_INPUT | GPIO_PULLUP | GPIO_PULLDOWN | GPIO_OPEN_DRAIN | GPIO_OPEN_SOURCE | GPIO_PWM | GPIO_ADC | GPIO_DAC | GPIO_INTERRUPT_CHANGE | GPIO_INTERRUPT_RISING | GPIO_INTERRUPT_FALLING | GPIO_INTERRUPT_LOW | GPIO_INTERRUPT_HIGH`
Functions:
1. getNumGpio()
- Parameters: None
- Response: number of gpios (1 byte)
1. getGpioCapabilities()
- Parameters: gpio number (1 byte)
- Response: flags (2 bytes)
1. setGpioFlags()
- Parameters: gpio number (1 byte), flags (2 bytes)
- Response: None
1. digitalRead()
- Parameters: gpio number (1 byte)
- Response: 1 byte, value
1. digitalWrite()
- Parameters: gpio number (1 byte), value (1 byte)
- Response: None
1. analogRead()
- Parameters: gpio number (1 byte)
- Response: value (2 bytes)
1. analogWrite()
- Parameters: gpio number (1 byte), value (2 bytes)
- Response: None
1. attachInterrupt()
- Parameters: gpio number (1 byte), mode (1 byte)
- Response: None
1. dettachInterrupt()
- Parameters: gpio number (1 byte), mode (1 byte)
- Response: None
# Input Device (DeviceType #3)
Maps directly to the Linux Input Subsystem (Easy to use)
# HID Device (DeviceType #4)
Maps directly to the Linux HID Subsystem (Harder to use, more powerful)
# Serial Port/TTY Device (DeviceType #5)
Maps directly to the Linux HID Subsystem (Harder to use, more powerful)
# Misc Device (DeviceType #6)
Something else that isn't mapped to a Linux subsystem.
A new character device is created on `/dev/mything`, and `read`/`write`/`ioctl` operations are handled on the microcontroller.
| 31.472441 | 258 | 0.734051 | eng_Latn | 0.920304 |
2f7ede588c18a7a48ca98d8c48bd4e61bccbaaa1 | 214 | md | Markdown | README.md | arykau/assignment1python | 5f73089a25de0caa38a98f6742222518561c95d3 | [
"MIT"
] | null | null | null | README.md | arykau/assignment1python | 5f73089a25de0caa38a98f6742222518561c95d3 | [
"MIT"
] | null | null | null | README.md | arykau/assignment1python | 5f73089a25de0caa38a98f6742222518561c95d3 | [
"MIT"
] | null | null | null | # Filtering out top N cryptocurrecies by market capitalization from coingecko.com
-Installation: pip install requests pip install pip install beautifulsoup4
-Usage: import requests from bs4 import BeautifulSoup
| 30.571429 | 81 | 0.831776 | eng_Latn | 0.960993 |
2f7ee6039d24b7eb2904c4b86bcc6ebb106a7f65 | 162 | md | Markdown | _posts/fr/papa/2013/2013-08-10-le-sommeil-cest-surfait.md | ryuran/borisschapira.com | c69ed14d4ae2ba026cc3e0ee2e72cd307c039113 | [
"MIT"
] | null | null | null | _posts/fr/papa/2013/2013-08-10-le-sommeil-cest-surfait.md | ryuran/borisschapira.com | c69ed14d4ae2ba026cc3e0ee2e72cd307c039113 | [
"MIT"
] | 4 | 2021-03-11T01:55:52.000Z | 2022-02-10T23:25:55.000Z | _posts/fr/papa/2013/2013-08-10-le-sommeil-cest-surfait.md | fredleger/borisschapira.com | 2005b30ae41967d2c4670592be163efdece56575 | [
"MIT"
] | null | null | null | ---
title: 'Le sommeil, c''est surfait'
---
Et puis un bon petit réveil à 5h le samedi ET le dimanche, ça te permet de profiter vraiment à fond de ton week-end.
| 27 | 116 | 0.709877 | fra_Latn | 0.992248 |
2f7f0d39f805a22a60c1c4dd05bd507def1f120e | 14,863 | md | Markdown | _posts/2016-08-26-Science-is-global.md | trashbirdecology/luisdva.github.io | bbf52b4b464f55ac3a96c2dacf4ef329d027595f | [
"MIT"
] | 2 | 2020-02-10T18:41:28.000Z | 2020-04-02T03:00:13.000Z | _posts/2016-08-26-Science-is-global.md | trashbirdecology/luisdva.github.io | bbf52b4b464f55ac3a96c2dacf4ef329d027595f | [
"MIT"
] | 1 | 2021-12-13T15:48:53.000Z | 2021-12-13T15:48:53.000Z | _posts/2016-08-26-Science-is-global.md | trashbirdecology/luisdva.github.io | bbf52b4b464f55ac3a96c2dacf4ef329d027595f | [
"MIT"
] | 4 | 2020-10-14T20:09:27.000Z | 2021-12-13T15:33:17.000Z | ---
excerpt: 'Emoji flags, international research, and tweet analysis in R.'
category: rstats
tags:
- rstats
- Twitter
- stringi
- encoding
header:
image: /assets/images/featureflags.png
---
## Tweet data and emoji flags in R
On the occasion of the ESOF (EuroScience Open Forum) conference in Manchester, The Royal Society published a [joint statement](https://royalsociety.org/topics-policy/publications/2016/european-academies-statement-science-is-global/) from various scientific societies across Europe about the importance of International science and research collaborations, and how “unnecessary barriers to mobility will weaken science and be to the cost of all nations”. This statement included a call for people to use the social media hashtag #ScienceIsGlobal to recognize the international nature of research teams.
<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">Our joint academies’ statement on the importance of international research <a href="https://twitter.com/hashtag/ScienceIsGlobal?src=hash">#ScienceIsGlobal</a> (1/4) <a href="https://t.co/LFsSotfeW7">pic.twitter.com/LFsSotfeW7</a></p>— The Royal Society (@royalsociety) <a href="https://twitter.com/royalsociety/status/757537126649065472">July 25, 2016</a></blockquote>
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
The hashtag really took off, and in a Tweet from August 1st the Royal Society posted that #ScienceIsGlobal had reached over 10 million people across the world. Lots of people started sharing the different countries of the people in their labs or collaborative networks, mainly by using emoji flags or photos of the research teams actually holding their national flags.
A few days later, Bastian Greshake published [this](http://ruleofthirds.de/scienceisglobal/) really cool blog post in which he analysed tweet data relating to the hashtag. To make a network chart and a chord diagram of the connections between different countries, he set up an archiver add-on to collect tweets onto a Google sheet. Then he parsed the emoji flags with a Python script to create adjacency lists for visualization.
I’ve always wanted to play with Twitter data and do something similar, but in my case I wanted to do everything in R. Using the [Twitter Archiver spreadsheet](https://docs.google.com/spreadsheets/d/1NRxvV0JP_eF98WUfbkpj1iMBlFEe25JGKGhblM6U3KQ/) he organized, I downloaded a copy of the Google sheet on 8/8/2016, which included 11655 tweets that included the hashtag (I’ve been very slow with writing this post).
This is my first attempt at working with Twitter data and strings, and I want to share the process and some of the things I learned about working with strings, dates, encodings, and emojis. To replicate my version of the analysis, I suggest downloading the Google sheet and filtering everything up to “8/8/2016 9:01:04” using _lubridate_. The rest of the data is already on a repo and you should be able to replicate everything by copying and pasting the code.
{% highlight r %}
#load libraries (install if needed)
library(stringi)
library(dplyr)
# read file for Archiver from URL
alltweets <- read.csv("https://raw.githubusercontent.com/luisDVA/codeluis/master/scienceisglobal.csv",stringsAsFactors = F,header = T)
# strip retweets
norts <- filter(alltweets, !grepl("RT @",Tweet.Text))
norts <- filter(norts, !grepl("Retweeted",Tweet.Text))
# percentage of RTs in dataset
1-nrow(norts)/nrow(alltweets)
# strip urls
norts$Tweet.Text <- stri_replace_all_regex(norts$Tweet.Text," ?(f|ht)(tp)(s?)(://)(.*)[.|/](.*)","")
# remove duplicates
norts <- norts%>% filter(!stri_duplicated(norts$Tweet.Text))
# remove spambot tweets
norts <- filter(norts,!grepl("VOTE for me in",Tweet.Text))
{% endhighlight %}
I started by cleaning up the data. To avoid duplication, I removed all the retweets, the twitteR package has a function for this, but with the flat data frame we can use dplyr::filter and some basic pattern matching to remove retweets, which made up a good portion of the dataset (about 75%). Looking at the original entries, I realized that it would be a good idea to strip all URLS, then remove other duplicates and spam (e.g. dozens of tweets with spam links or requesting votes in spammy websites).
Now we can plot how many tweets were posted each day, and we see that #scienceisglobal peaked the day after the joint statement was published and then tapered off.
{% highlight r %}
norts %>% count(posted = date(mdy_hms(norts[,1]))) %>%
ggplot(aes(posted,n)) +
geom_line() +
scale_x_date(labels = date_format("%m/%d"),breaks = date_breaks("days"))+
labs(x = "date posted",
y = "no. of tweets")
{% endhighlight %}
<figure>
<a href="/assets/images/twtdates.png"><img src="/assets/images/twtdates.png"></a>
<figcaption>tweets/day</figcaption>
</figure>
Now for the interesting part, I had to translate the flag emojis into something sensible. I don’t know if this applies to everyone, but on my Windows PC I always struggle with special characters in R. I was interested in the flag emojis people were using, and in my case I was unsure of how to deal with file encoding and fonts so all the emojis and special characters were getting “garbaged” into things like this 🇬🇧
I realized that there is no loss of information with this character garbling, and that other people also work with it ([see here](https://github.com/iorch/jakaton_feminicidios)), so they were something I could work with. Now I could use these characters and filter our rows that won’t contain emojis.
{% highlight r %}
# keep tweets with probably flags
sciFlags <- filter(norts, grepl("ð",Tweet.Text))
{% endhighlight %}
Emoji flags are combinations of two regional indicator letters, based on ISO 3166-1: a list of internationally recognized two-letter country codes. There are now hundreds of working flag emojis, and their indicator letters have unique encodings. Fortunately, [this page](http://emojipedia.org/flags/) has the full list, and after scraping it and doing some minor edits, I had a csv file that was getting garbaged the same way when I read it into R, making it a good translation table.
{% highlight r %}
#read conversion table
emoTable2 <- read.csv("https://raw.githubusercontent.com/luisDVA/codeluis/master/countryFlags.txt",stringsAsFactors = F) %>% select("encoding"=1,"region"=2)
#add some whitespace for legibility
emoTable2$region <- paste(" ",emoTable2$region," ")
{% endhighlight %}
If we know what the gibberish stands for, we can use the powerful _stringi_ package to do vectorized pattern replacements. It also helps that a similar translation table for emojis has already been put together by [another team](https://github.com/iorch/jakaton_feminicidios) doing Twitter analytics.
I used a hacky, multi-stage process to replace flags and other emojis until all the weird characters were accounted for. The biggest issue was that there can be overlap in the character strings representing combinations of regional indicators, and because the replacements are vectorized without lookahead overlap detection, it becomes messy because countries can be both incorrectly replaced or excluded.
For example, if someone mentioned Ascencion Island and Canada together (ACCA) and the vector of two-letter combinations is not ordered just right, the CC for Cocos Islands can get ‘incorrectly’ replaced instead of the two countries that were actually mentioned.
{% highlight r %}
# multiple patterns and replacements
sciFlags$tweetTRANS <- stri_replace_all_fixed(sciFlags$Tweet.Text,emoTable2$encoding,emoTable2$region,vectorize_all = F)
# filter rows that are (probably) all set
set1 <- filter(sciFlags, !grepl("ð",tweetTRANS))
# new column with tweet text that is ready to go *i.e. the column used for filtering
set1$textDone <- set1$tweetTRANS
# pending replacement
chec <- filter(sciFlags, grepl("ð",tweetTRANS))
#sad and smiley faces
emojis <- read.csv("https://raw.githubusercontent.com/luisDVA/codeluis/master/emojis.csv",stringsAsFactors = F)
emojisFilt <- filter(emojis,!grepl("flag",emojis$meaning))
# replace misc emojis
chec$transF <- stri_replace_all_fixed(chec$tweetTRANS,emojisFilt$emoji,emojisFilt$meaning,vectorize_all = F)
# extract rows that are ready to go
set2 <- filter(chec, !grepl("ð",transF))
set2$textDone <- set2$transF
# pendind more replacement
chec <- filter(chec, grepl("ð",transF))
# angry emoji replaced separately (too much overlap)
angem <- read.csv("https://raw.githubusercontent.com/luisDVA/codeluis/master/angryemoji.csv",stringsAsFactors = F)
chec$transF <- stri_replace_all_fixed(chec$transF,angem$emoji,angem$meaning,vectorize_all = F)
# extract rows that are ready to go
set3 <- filter(chec, !grepl("ð",transF))
set3$textDone <- set3$transF
# still pending
chec <- filter(chec, grepl("ð",transF))
{% endhighlight %}
My solution for the overlapping patterns was to strip away all alphanumeric characters and punctuation, and to then split the remaining strings into 8-character chunks (because I realized that each regional indicator gets garbaged into four character sequences) and then translate again.
{% highlight r %}
# for stubborn ones with overlaps
#strip alhpanumeric chars
chec$transStripped <- stri_replace_all_regex(chec$Tweet.Text,"[A-Za-z0-9\\s]","")
# strip left over not-so-special characters
chec$transStripped <- stri_replace_all_fixed(chec$transStripped,c("@","!","#","_",".","&","-","?",";",
"'","/",":",",","(",")"),"",vectorize_all = F)
# split into 8 char blocks
chec$transStripped <- gsub("(.{8})", "\\1 ", chec$transStripped)
# translate with flag table
chec$countries <- stri_replace_all_fixed(chec$transStripped,emoTable2$encoding,emoTable2$region,vectorize_all = F)
# extract rows that are ready to go
set4 <- filter(chec, !grepl("ð",countries))
set4$textDone <- set4$countries
#filter again
chec <- filter(chec, grepl("ð",countries))
#loose ends (random regional symbol emojis tweeted by people for some reason)
regsimbols <- read.csv("looseEnds.csv",stringsAsFactors = F)
# on the first translation column to avoid overlaps or unnecessary countries
chec$transF <- stri_replace_all_fixed(chec$transF,regsimbols$ï..emoji,regsimbols$meaning,vectorize_all = F)
# extract rows that are ready to go
set5 <- filter(chec, !grepl("ð",transF))
set5$textDone <- set5$transF
# filter once more
chec <- filter(chec, grepl("ð",transF))
# have them all?
nrow(set1)+nrow(set2)+nrow(set3)+nrow(set4)+nrow(set5) == nrow(sciFlags)
# bind them
Flagstranslated <- bind_rows(set1,set2,set3,set4,set5)
{% endhighlight %}
After that, I used _stringi_ to extract the occurrences of different country names in each tweet and some more list manipulation to end up with a matrix of the presence of each country in each tweet. Don't mind the for loop.
{% highlight r %}
# get the country names from the tweets
countryExtract <- list()
for (i in 1:nrow(emoTable2)) {
countryExtract[[i]] <- stri_extract_all_fixed(Flagstranslated$textDone,emoTable2$region[i],
case_insensitive=TRUE,overlap=TRUE)
}
# put into DF
countryMatches <- simplify2array(countryExtract) %>% as.data.frame()
# cant remember how to apply properly
countryNs <- countryMatches
for (i in 1:ncol(countryMatches)) {
countryNs[,i] <- sapply(countryMatches[,i],function(x)length(x[!is.na(x)]))
}
# country names without the whitespace
emoTable2$regionTrimmed <- stri_trim(emoTable2$region)
names(countryNs) <- emoTable2$regionTrimmed
# change all non cero values to 1
countryNstandard <- countryNs
countryNstandard[countryNstandard>0] <- 1
# some tweets did not have countries but had other emojis, remove them
countryNstandard <- countryNstandard[rowSums(countryNstandard)!=0,]
# summary statistics
colSums(countryNstandard)
summary(rowSums(countryNstandard))
# make a DF of colsums
countryFreqs <- colSums(countryNstandard)
countryFreqsDF <- data.frame(country=names(countryFreqs),n=countryFreqs)
{% endhighlight %}
**Quick summary statistics:**
On average, about **nine** different countries were mentioned per tweet, with a minimum of **1** and a maximum of **50** for some people having way too much fun with emoji flags.
Bastian G. noted that the usual Western, rich industrialized countries are the most frequently mentioned. We can make a lollipop plot of the top _n_ countries with the highest number of mentions. In this case it’s 30.
{% highlight r %}
# make sure to use the latest version from github, install using devtools
library(ggalt)
countryFreqsDF %>% top_n(30) %>%
ggplot(aes(x=reorder(country,n),y=n)) + geom_lollipop(point.colour = "blue")+
coord_flip()+theme_minimal()+xlab("Country")+ylab("Mentions")
{% endhighlight %}
<figure>
<a href="/assets/images/lolipop.png"><img src="/assets/images/lolipop.png"></a>
<figcaption>useful ggalt geometry</figcaption>
</figure>
Finally, using code from a previous post I joined the country list to a worldmap to visualize the countries being mentioned.
{% highlight r %}
#join mentions data with a world map
library(rworldmap)
tweetsGeo <- joinCountryData2Map(countryFreqsDF, joinCode="NAME", nameJoinColumn="country")
#create a map-shaped window
mapDevice('x11')
#plot
par(bg="grey15")
mapParameters <- mapCountryData(tweetsGeo, nameColumnToPlot="n", catMethod="fixedWidth",
borderCol="grey11", oceanCol="grey15",missingCountryCol = "yellow",addLegend = F,
mapTitle = "Science is Global",
colourPalette = c("#3182BD", "#00004d"))
do.call(addMapLegend,c(mapParameters,legendWidth = 0.5))
{% endhighlight %}
<figure>
<a href="/assets/images/mapW.png"><img src="/assets/images/mapW.png"></a>
<figcaption>yellow fill is for countries with no matches in the tweet data</figcaption>
</figure>
I put the countries with no matches in yellow to see the gaps, which in this case may not be true gaps because I made no steps to match the country names from my emoji flag table with the built in country names from the world map.
This is not a comprehensive analysis of the countries mentioned by people using the #ScienceisGlobal, since there are other ways to trigger emoji flags such as three-character "hashflags" (read about them [here](https://medium.com/dmrc-at-large/waiving-hash-flags-some-thoughts-on-twitter-hashtag-emoji-bfdcdc4ab9ad#.twxhdft6t)). I did not collect or count these, but the regex for catching these flags is not a problem: /\B#\w*[a-zA-Z]+\w*/ . Still, this code shoud work for anyone trying to parse emojis and especially national flags from Twitter data.
Contact me if the code isn't working or if you have better alternatives for my hacky approach.
| 58.515748 | 603 | 0.753415 | eng_Latn | 0.984348 |
2f81b01c9de4afefdd92fb27e379fee4cdce3cbc | 283 | md | Markdown | src/render/hw/s18se/calendar-mod.html.md | tmullen71/ups-website | d9e0b31e7f839e04b524f48023bc87a29e5ce5d9 | [
"CC-BY-3.0"
] | 1 | 2017-05-10T13:53:13.000Z | 2017-05-10T13:53:13.000Z | src/render/hw/s18se/calendar-mod.html.md | tonymullen/ups-website | d9e0b31e7f839e04b524f48023bc87a29e5ce5d9 | [
"CC-BY-3.0"
] | null | null | null | src/render/hw/s18se/calendar-mod.html.md | tonymullen/ups-website | d9e0b31e7f839e04b524f48023bc87a29e5ce5d9 | [
"CC-BY-3.0"
] | null | null | null | ```
layout: assignment
term: Spring 2018
title: Working with the calendar module
class: CS 240: Software Engineering
classurl: /classes/s18-CS240-se
submission: s18se/hw/empty.html.md
description: s18se/hw/calendar-mod-description.html.md
credits: s18se/hw/empty.html.md
```
| 14.894737 | 54 | 0.763251 | eng_Latn | 0.31967 |
2f81bf75ea71cfce44b9adbd4237399db7e53628 | 1,930 | md | Markdown | README.md | dcjc29/sliitfoss | 8a6a7aeb39a9a4e80ddd698be6eec187ab3b7256 | [
"MIT"
] | null | null | null | README.md | dcjc29/sliitfoss | 8a6a7aeb39a9a4e80ddd698be6eec187ab3b7256 | [
"MIT"
] | null | null | null | README.md | dcjc29/sliitfoss | 8a6a7aeb39a9a4e80ddd698be6eec187ab3b7256 | [
"MIT"
] | null | null | null | # SLIIT FOSS Website
## Contribution Guide
1. Fork the repository
2. Clone the repository
```
git clone https://github.com/sliit-foss/sliitfoss.git
```
3. Create Feature branch and checkout
_Replace <BRANCH_NAME> with meaningful name. For an example navbar. See the guide for the more details [Link](https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow)_
```
git checkout -b feature/<BRANCH_NAME>
```
4. Do your modifications
5. Stage Changes and commit
```
git add .
git commit -m "<Commit message>"
```
6. Push Changes
```
git push --set-upstream origin feature/<BRANCH_NAME>
```
7. Make a Pull Request.
_See the guide for more details [Link](https://docs.github.com/en/free-pro-team@latest/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request)_
This project was generated with [Angular CLI](https://github.com/angular/angular-cli) version 10.1.1
## Development server
Run `ng serve` for a dev server. Navigate to `http://localhost:4200/`. The app will automatically reload if you change any of the source files.
## Code scaffolding
Run `ng generate component component-name` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module`.
## Build
Run `ng build` to build the project. The build artifacts will be stored in the `dist/` directory. Use the `--prod` flag for a production build.
## Running unit tests
Run `ng test` to execute the unit tests via [Karma](https://karma-runner.github.io).
## Running end-to-end tests
Run `ng e2e` to execute the end-to-end tests via [Protractor](http://www.protractortest.org/).
## Further help
To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI README](https://github.com/angular/angular-cli/blob/master/README.md).
| 29.692308 | 198 | 0.746114 | eng_Latn | 0.80601 |
2f8279b470e551025b2acb76b7ec0bca3710e352 | 7,917 | md | Markdown | docs/usage-guide/location.md | kompaakt/instagrapi | bb42134a5042c836fe770c2688dce78033a99f67 | [
"MIT"
] | 1 | 2021-09-02T21:55:37.000Z | 2021-09-02T21:55:37.000Z | docs/usage-guide/location.md | kompaakt/instagrapi | bb42134a5042c836fe770c2688dce78033a99f67 | [
"MIT"
] | 76 | 2021-04-30T10:12:26.000Z | 2022-03-28T23:13:19.000Z | docs/usage-guide/location.md | kompaakt/instagrapi | bb42134a5042c836fe770c2688dce78033a99f67 | [
"MIT"
] | null | null | null | # Location (place)
Viewing location info and medias by location
| Method | Return | Description
| ---------------------------------------------------------- | -------------- | ----------------------------------------------------
| location_search(lat: float, lng: float) | List[Location] | Search Location by GEO coordinates
| location_complete(location: Location) | Location | Complete blank fields
| location_build(location: Location) | String | Serialized JSON
| location_info(location_pk: int) | Location | Return Location info (pk, name, address, lng, lat, external_id, external_id_source)
| location_medias_top(location_pk: int, amount: int = 9) | List[Media] | Return Top posts by Location
| location_medias_recent(location_pk: int, amount: int = 24) | List[Media] | Return Most recent posts by Location
Example:
``` python
>>> from instagrapi import Client
>>> cl = Client()
>>> cl.login(USERNAME, PASSWORD)
>>> location = cl.location_search(59.96, 30.29)[0]
>>> location.dict()
{'pk': None,
'name': 'Russia, Saint-Petersburg',
'address': 'Russia, Saint-Petersburg',
'lng': 30.30605,
'lat': 59.93318,
'external_id': 107617247320879,
'external_id_source': 'facebook_places'}
>>> location = cl.location_complete(location)
>>> location.dict()
{'pk': 107617247320879,
'name': 'Russia, Saint-Petersburg',
'address': 'Russia, Saint-Petersburg',
'lng': 30.30605,
'lat': 59.93318,
'external_id': 107617247320879,
'external_id_source': 'facebook_places'}
>>> cl.location_build(location)
'{"name":"Russia, Saint-Petersburg","address":"Russia, Saint-Petersburg","lat":59.93318,"lng":30.30605,"external_source":"facebook_places","facebook_places_id":107617247320879}'
>>> location = cl.location_info(107617247320879)
>>> location.dict()
{'pk': 107617247320879,
'name': 'Russia, Saint-Petersburg',
'address': '',
'lng': 30.30605,
'lat': 59.93318,
'external_id': None,
'external_id_source': None}
>>> medias = cl.location_medias_top(107617247320879, amount=2)
>>> medias[0].dict()
{'pk': 2574095228556148891,
'id': '2574095228556148891_8227888596',
'code': 'CO5BfjkHgCb',
'taken_at': datetime.datetime(2021, 5, 15, 11, 6, 25, tzinfo=datetime.timezone.utc),
'media_type': 2,
'product_type': 'feed',
'thumbnail_url': HttpUrl('https://instagram.fhel3-1.fna.fbcdn.net/v/t51.2885-15/e35/185874360_510656656615872_846247842213042525_n.jpg?tp=1&_nc_ht=instagram.fhel3-1.fna.fbcdn.net&_nc_cat=1&_nc_ohc=vUIk3PZPPrMAX_GGZ7n&edm=AP_V10EBAAAA&ccb=7-4&oh=e418e018b9fc07b7d6b78f0790ddb481&oe=60A24C1F&_nc_sid=4f375e', scheme='https', host='instagram.fhel3-1.fna.fbcdn.net', tld='net', host_type='domain', path='/v/t51.2885-15/e35/185874360_510656656615872_846247842213042525_n.jpg', query='tp=1&_nc_ht=instagram.fhel3-1.fna.fbcdn.net&_nc_cat=1&_nc_ohc=vUIk3PZPPrMAX_GGZ7n&edm=AP_V10EBAAAA&ccb=7-4&oh=e418e018b9fc07b7d6b78f0790ddb481&oe=60A24C1F&_nc_sid=4f375e'),
'location': {'pk': 107617247320879,
'name': 'Russia, Saint-Petersburg',
'address': '',
'lng': 30.30605,
'lat': 59.93318,
'external_id': 107617247320879,
'external_id_source': 'facebook_places'},
'user': {'pk': 8227888596,
'username': 'mzefirov',
'full_name': 'МИХАИЛ ЗЕФИРОВ🌶️🔥ПРО ОТНОШЕНИЯ',
'profile_pic_url': HttpUrl('https://scontent-hel3-1.cdninstagram.com/v/t51.2885-19/s150x150/54513886_664942437287042_6311410572676038656_n.jpg?tp=1&_nc_ht=scontent-hel3-1.cdninstagram.com&_nc_ohc=mOWHIYJXbMsAX8wXvzf&edm=AP_V10EBAAAA&ccb=7-4&oh=90fa78d26bbb2c577dbc27d012c7cf09&oe=60C6A82B&_nc_sid=4f375e', scheme='https', host='scontent-hel3-1.cdninstagram.com', tld='com', host_type='domain', path='/v/t51.2885-19/s150x150/54513886_664942437287042_6311410572676038656_n.jpg', query='tp=1&_nc_ht=scontent-hel3-1.cdninstagram.com&_nc_ohc=mOWHIYJXbMsAX8wXvzf&edm=AP_V10EBAAAA&ccb=7-4&oh=90fa78d26bbb2c577dbc27d012c7cf09&oe=60C6A82B&_nc_sid=4f375e'),
'stories': []},
'comment_count': 94,
'like_count': 3995,
'has_liked': None,
'caption_text': 'Антонина Роббинс, или немного о мотивации.\n\nСтавь ❤️и делись в сторис... это мотивирует.',
'usertags': [],
'video_url': HttpUrl('https://scontent-hel3-1.cdninstagram.com/v/t50.2886-16/185466467_1373704339669543_4721533329541547409_n.mp4?_nc_ht=scontent-hel3-1.cdninstagram.com&_nc_cat=107&_nc_ohc=IdbMAqYCjngAX987nBb&edm=AP_V10EBAAAA&ccb=7-4&oe=60A1DADD&oh=7c69dc13e5344f7095a94eb717b1ee9e&_nc_sid=4f375e', scheme='https', host='scontent-hel3-1.cdninstagram.com', tld='com', host_type='domain', path='/v/t50.2886-16/185466467_1373704339669543_4721533329541547409_n.mp4', query='_nc_ht=scontent-hel3-1.cdninstagram.com&_nc_cat=107&_nc_ohc=IdbMAqYCjngAX987nBb&edm=AP_V10EBAAAA&ccb=7-4&oe=60A1DADD&oh=7c69dc13e5344f7095a94eb717b1ee9e&_nc_sid=4f375e'),
'view_count': 36295,
'video_duration': 55.433,
'title': '',
'resources': []}
>>> medias = cl.location_medias_recent(107617247320879, amount=2)
>>> medias[0].dict()
{'pk': 2574187014843321420,
'id': '2574187014843321420_5600296444',
'code': 'CO5WXONKMxM',
'taken_at': datetime.datetime(2021, 5, 15, 13, 57, 6, tzinfo=datetime.timezone.utc),
'media_type': 1,
'product_type': '',
'thumbnail_url': HttpUrl('https://scontent-hel3-1.cdninstagram.com/v/t51.2885-15/e35/p1080x1080/186279877_479327446453989_5642409805215171470_n.jpg?tp=1&_nc_ht=scontent-hel3-1.cdninstagram.com&_nc_cat=109&_nc_ohc=Nx9KwOGWXLYAX_bh1Dx&edm=AP_V10EBAAAA&ccb=7-4&oh=999395b5e4a3c688bcb388616f405161&oe=60C4C08C&_nc_sid=4f375e', scheme='https', host='scontent-hel3-1.cdninstagram.com', tld='com', host_type='domain', path='/v/t51.2885-15/e35/p1080x1080/186279877_479327446453989_5642409805215171470_n.jpg', query='tp=1&_nc_ht=scontent-hel3-1.cdninstagram.com&_nc_cat=109&_nc_ohc=Nx9KwOGWXLYAX_bh1Dx&edm=AP_V10EBAAAA&ccb=7-4&oh=999395b5e4a3c688bcb388616f405161&oe=60C4C08C&_nc_sid=4f375e'),
'location': {'pk': 107617247320879,
'name': 'Russia, Saint-Petersburg',
'address': '',
'lng': 30.30605,
'lat': 59.93318,
'external_id': 107617247320879,
'external_id_source': 'facebook_places'},
'user': {'pk': 5600296444,
'username': 'sultanieriabinina',
'full_name': 'Султание Беляловна',
'profile_pic_url': HttpUrl('https://scontent-hel3-1.cdninstagram.com/v/t51.2885-19/s150x150/92693550_492095081670507_2163230119093600256_n.jpg?tp=1&_nc_ht=scontent-hel3-1.cdninstagram.com&_nc_ohc=_8hEZtz-JSIAX_NCxXx&edm=AP_V10EBAAAA&ccb=7-4&oh=17d2d1a8ae00765b8471cde868937c13&oe=60C69D73&_nc_sid=4f375e', scheme='https', host='scontent-hel3-1.cdninstagram.com', tld='com', host_type='domain', path='/v/t51.2885-19/s150x150/92693550_492095081670507_2163230119093600256_n.jpg', query='tp=1&_nc_ht=scontent-hel3-1.cdninstagram.com&_nc_ohc=_8hEZtz-JSIAX_NCxXx&edm=AP_V10EBAAAA&ccb=7-4&oh=17d2d1a8ae00765b8471cde868937c13&oe=60C69D73&_nc_sid=4f375e'),
'stories': []},
'comment_count': 0,
'like_count': 0,
'has_liked': None,
'caption_text': '',
'usertags': [{'user': {'pk': 3955327494,
'username': '_parikmakher_irishka3127',
'full_name': 'ИрИнА',
'profile_pic_url': HttpUrl('https://scontent-hel3-1.cdninstagram.com/v/t51.2885-19/s150x150/176040256_461659781826794_5379061705031591554_n.jpg?tp=1&_nc_ht=scontent-hel3-1.cdninstagram.com&_nc_ohc=uVHqkpa8v0UAX-cmGUE&edm=AP_V10EBAAAA&ccb=7-4&oh=22db3640b911117484d78422eec4f778&oe=60C523D5&_nc_sid=4f375e', scheme='https', host='scontent-hel3-1.cdninstagram.com', tld='com', host_type='domain', path='/v/t51.2885-19/s150x150/176040256_461659781826794_5379061705031591554_n.jpg', query='tp=1&_nc_ht=scontent-hel3-1.cdninstagram.com&_nc_ohc=uVHqkpa8v0UAX-cmGUE&edm=AP_V10EBAAAA&ccb=7-4&oh=22db3640b911117484d78422eec4f778&oe=60C523D5&_nc_sid=4f375e'),
'stories': []},
'x': 0.352,
'y': 0.292}],
'video_url': None,
'view_count': 0,
'video_duration': 0.0,
'title': '',
'resources': []}
```
| 62.833333 | 684 | 0.729948 | yue_Hant | 0.211259 |
2f829cc83f04f92790588d31b987e8b49e0e9814 | 22,581 | md | Markdown | docs/cross-platform/troubleshooting-the-visual-studio-emulator-for-android.md | monkey3310/visualstudio-docs.pl-pl | adc80e0d3bef9965253897b72971ccb1a3781354 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/cross-platform/troubleshooting-the-visual-studio-emulator-for-android.md | monkey3310/visualstudio-docs.pl-pl | adc80e0d3bef9965253897b72971ccb1a3781354 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/cross-platform/troubleshooting-the-visual-studio-emulator-for-android.md | monkey3310/visualstudio-docs.pl-pl | adc80e0d3bef9965253897b72971ccb1a3781354 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Rozwiązywanie problemów z emulatorem programu Visual Studio dla systemu Android | Dokumentacja firmy Microsoft
ms.custom: ''
ms.date: 11/04/2016
ms.technology: vs-ide-mobile
ms.topic: conceptual
ms.assetid: f3fb5df4-3aae-40e4-9450-bbe15b0c5af5
author: conceptdev
ms.author: crdun
manager: crdun
ms.workload:
- multiple
ms.openlocfilehash: 4456fdf61fc1ae7f3d4dc958afe3ba7cb6ff9add
ms.sourcegitcommit: 9765b3fcf89375ca499afd9fc42cf4645b66a8a2
ms.translationtype: MT
ms.contentlocale: pl-PL
ms.lasthandoff: 09/20/2018
ms.locfileid: "46496093"
---
# <a name="troubleshoot-the-visual-studio-emulator-for-android"></a>Rozwiązywanie problemów z narzędziem Visual Studio Emulator for Android
Ten temat zawiera informacje pomocne podczas rozwiązywania problemów, które mogą wystąpić podczas korzystania z programu Visual Studio Emulator for Android.
> [!WARNING]
> Po zainstalowaniu emulatora program instalacyjny sprawdza wymagania wstępne dotyczące uruchamiania oprogramowania. Wyświetla ostrzeżenia, jeśli wymagania wstępne nie są obecne, ale nie wymaga ich instalacji.
Ten temat zawiera następujące sekcje.
- [Przed rozpoczęciem](#BeforeYouStart)
- [Emulator nie można zainstalować](#NoInstall)
- [Nie można nawiązać połączenia z sieci docelowych w domenie lub sieci firmowej](#DomainNetwork)
- [Nie można połączyć z sieci docelowych, jeśli ustawienia sieciowe wymagają ręcznej konfiguracji](#ManualNetworkConfig)
- [Emulator uruchamia się powoli, nie można uruchomić z powodu przekroczenia limitu czasu lub wdrożenia aplikacji nie powiedzie się.](#SlowStart)
- [Emulator nie została uruchomiona](#NoStart2)
- [Emulator nie powiedzie się (pierwszym użyciu)](#NoStart)
- [Komputerowi nie uda się uruchomić po zainstalowaniu emulatora](#NoBoot)
- [Program Visual Studio zablokowania próby wdrożenia aplikacji w emulatorze lub emulator nie jest wyświetlany jako element docelowy debugowania w innych środowiskach IDE](#ADB)
- [Emulator zawiesza się, ponieważ nie można ustawić port UDP](#XamarinPlayer)
- [Nie można dołączyć debugera do projektu Xamarin](#Skylake)
- [Emulator nie powiedzie się uruchomić aplikację, która używa usług Google Play](#GooglePlay)
- [Przeciąganie i upuszczanie plików, APK lub pliku w pliku zip nie działa](#DragAndDrop)
- [Rozdzielczość zrzut ekranu jest nieprawidłowa](#Resolution)
- [Emulator nie powiedzie się do renderowania zawartości ze specyfikacji OpenGL](#OpenGL)
- [Emulator nie odpowiada na gestów dotykowych wielu](#Multitouch)
- [Zasoby pomocy technicznej](#Support)
## <a name="BeforeYouStart"></a> Przed rozpoczęciem
Przed rozpoczęciem rozwiązywania problemów, warto przejrzeć następujące tematy:
- [Wymagania systemowe dotyczące emulatora programu Visual Studio dla systemu Android](../cross-platform/system-requirements-for-the-visual-studio-emulator-for-android.md)
## <a name="NoInstall"></a> Emulator nie można zainstalować
Jeśli masz zainstalowany w funkcji Hyper-V, zostanie wyświetlony następujący komunikat, gdy próbują zainstalować emulator. Konieczne jest posiadanie maszynie, która obsługuje funkcji Hyper-v i musi być włączona.
> [!NOTE]
> Ten komunikat ma zastosowanie zarówno do programu Visual Studio Emulator for Android i Windows Phone Emulator. Windows 8.1 i Windows 10 obsługuje emulatora.
Jeśli ten komunikat jest wyświetlony, sprawdź [wymagania systemowe dotyczące emulatora programu Visual Studio dla systemu Android](../cross-platform/system-requirements-for-the-visual-studio-emulator-for-android.md) aby zobaczyć, czy można uruchomić emulatora.
## <a name="DomainNetwork"></a> Nie można nawiązać połączenia z sieci docelowych w domenie lub sieci firmowej
Visual Studio Emulator for Android pojawia się w sieci jako osobne urządzenia przy użyciu adresu IP. Nie jest przyłączony do domeny Windows i nie udostępniać poświadczenia domeny lub grupy roboczej z komputera hosta.
Jeśli sieć wymaga autoryzacji do domeny lub grupy roboczej dla podstawowych sieci i łączności z Internetem, skontaktuj się z administratorem IT, dla wyjątku. Ten wyjątek umożliwia programowanie ma pełnić rolę maszyny granic i do akceptowania połączeń z urządzeniami sieciowymi nieprzyłączonych do domeny, takich jak emulator.
Visual Studio Emulator for Android używa również swój własny zestaw adresów MAC. Jeśli nie masz dostępu sieci lub zasobów w Internecie z emulatora, skontaktuj się z administratorem IT, aby upewnić się, czy adresy MAC to emulator autoryzowanych w sieci.
#### <a name="to-view-the-emulators-mac-addresses"></a>Aby wyświetlić to emulator MAC adresów
1. Uruchom emulator.
2. Na pasku narzędzi emulator, kliknij przycisk z podwójną strzałką (>>) aby otworzyć okno dodatkowe narzędzia.
3. W oknie dodatkowe narzędzia kliknij kartę sieci.
4. Na stronie sieci Znajdź wpisy adresów fizycznych.
## <a name="ManualNetworkConfig"></a> Nie można połączyć z sieci docelowych, jeśli ustawienia sieciowe wymagają ręcznej konfiguracji
Aby połączyć się z sieci docelowych z emulatora, sieci musi spełniać następujące wymagania:
- DHCP. Emulator wymaga protokołu DHCP, ponieważ konfiguruje się jako osobne urządzenia do sieci za pomocą adresu IP.
- Automatycznie skonfigurowana DNS i ustawień bramy. Nie jest możliwe do skonfigurowania ustawień DNS i bramę ręcznie dla emulatora.
Jeśli sieć wymaga ręcznie skonfigurowane ustawienia, skontaktuj się z administratorem IT, aby ustalić, jak włączyć łączność sieciową dla emulatora.
## <a name="SlowStart"></a> Emulator uruchamia się powoli, nie można uruchomić z powodu przekroczenia limitu czasu lub wdrożenia aplikacji nie powiedzie się.
W pewnych okolicznościach emulatora w ciągu kilku minut można uruchomić lub nie została uruchomiona z powodu przekroczenia limitu czasu. Jeśli emulator nie powiedzie się, zostanie wyświetlony następujący komunikat: `App deployment failed. Please try again`. Ten błąd może powodować następujące warunki.
- Uruchamianie emulatora programu Visual Studio dla systemu Android z rozruchowego dysku VHD. Ta konfiguracja nie jest obsługiwana.
- Uszkodzony dysk twardy. Rozważ uruchomienie programu chkdsk.
- Dysk twardy, który ma być defragmentacji. Należy wziąć pod uwagę defragmentacji dysku.
- Dysk twardy, który jest prawie pełna. Sprawdź ilość miejsca dostępnego na dysku.
- Nie ma wystarczającej ilości pamięci jest dostępna w związku z innych uruchomionych aplikacji. Zmniejsz liczbę aplikacji, które zużywają pamięci lub zwiększ ilość pamięci.
- Ogólnie rzecz biorąc wszelkie współczynnika, który jest przyczyniające się do niskiej wydajności w systemie. Rozpocznij rozwiązywanie problemów przy użyciu składnika, który ma najniższą częściowy indeksu środowiska Windows, w którym można znaleźć na stronie informacji o wydajności i narzędzia w Panelu sterowania.
## <a name="NoStart2"></a> Emulator nie została uruchomiona
Jeśli emulator była praca wcześniej, ale nie działa, wykonaj następujące zadania. Jeśli używasz emulatora po raz pierwszy, zobacz [emulatora uruchomienie nie powiedzie się (pierwszym użyciu)](#NoStart) przed podjęciem próby wykonania tych kroków.
- Usuń wszystkie wystąpienia funkcji Hyper-V emulatora.
1. Zamknij program Visual Studio.
2. Otwórz Menedżera funkcji Hyper-V i Zatrzymaj wszystkie wystąpienia funkcji Hyper-V emulatora (maszyn wirtualnych), które zostały już uruchomione i ewentualnie w stanie uszkodzenia.
3. W Menedżerze funkcji Hyper-V należy usunąć wszelkie inne emulatora maszyn wirtualnych.
4. Uruchom ponownie komputer.
- Upewnij się, że masz co najmniej 4 GB pamięci systemu i że jego jest nie są używane przez inne programy dużej ilości zasobów i procesów (np. Spróbuj zamknąć wszystkie okna przeglądarki).
- W Menedżerze funkcji Hyper-V Otwórz Menedżera przełącznika wirtualnego i sprawdź, czy masz dwa przełączników sieciowych; Sprawdź, czy pierwsza z nich to przełącznik wewnętrzny, i drugą jest zewnętrzny.
Jeśli konfiguracja jest nieprawidłowa w przypadku korzystania z systemu Windows 10, użytkownik może próbować [ponownej instalacji urządzeń sieciowych przy użyciu polecenia -d netcfg](http://windows.microsoft.com/en-us/windows-10/fix-network-connection-issues) (sekcja 6).
- Jeśli te kroki nie rozwiązują problemu, zobacz [emulatora uruchomienie nie powiedzie się (pierwszym użyciu)](#NoStart) uzyskać informacji na temat 3 oprogramowania innych firm, które mogą powodować konflikt z emulatorem.
## <a name="NoStart"></a> Emulator nie powiedzie się (pierwszym użyciu)
Nie można uruchomić emulatora, wykonaj następujące zadania, aby zidentyfikować i rozwiązać problem.
- Upewnij się, że spełnione są wymagania dotyczące minimalnych wymagań sprzętowych i czy ustawienia systemu BIOS są poprawne.
Emulatora i Windows 8 Hyper-V wymaga 64-bitowy procesor z adresów drugiego poziomu Translation (SLAT). Firmy Intel konieczne są zasadniczo i3 Core, i5 lub i7 procesora (lub jeden z wielu Xeons). Dostępna jest lista mikroukładami AMD [tutaj](http://support.amd.com/en-us).
1. Upewnić się, że Twoje komputer spełnia [wymagania systemowe](../cross-platform/system-requirements-for-the-visual-studio-emulator-for-android.md).
2. Upewnij się, że [narzędzie SLAT](https://slatstatuscheck.codeplex.com/) zgłasza, że komputer jest w stanie SLAT.
3. W ustawieniach systemu BIOS komputera upewnij się, że włączono wszystkich technologii wirtualizacji. Dokładne opisy systemu BIOS mogą się różnić dla każdego producenta sprzętu. Ogólnie rzecz biorąc Włącz funkcje związane z programem:
- SLAT (translacji adresów drugiego poziomu)
- EPT (Extended Page Tables) (Intel)
- NPT (zagnieżdżona strona tabele) (AMD)
- RVI (Rapid Virtualization Indexing) (AMD)
- VMX (wskazująca, obsługa wirtualizacji sprzętowej akronim Intel)
- SVM (akronim AMD wskazujący Obsługa wirtualizacji sprzętowej)
- XD (wykonywania Wyłącz) (Intel); musi być włączona
- NX (nie Execute)(AMD); musi być włączona.
4. Jeśli poniższe opcje są obecne w systemie BIOS, należy je wyłączyć.
- Wyłącz Intel VT-d
- Wyłącz zaufane wykonywanie
Aby uzyskać więcej informacji znajduje się w artykule: Technet: funkcja Hyper-V: jak można rozwiązać systemu BIOS błędy włączenie funkcji Hyper-V
5. Upewnij się, że masz co najmniej 4 GB pamięci systemu i że jego jest nie są używane przez inne programy dużej ilości zasobów i procesów.
6. Upewnij się, że używasz systemu Windows 8 Professional lub nowszy (system Windows Server 2008 nie jest obsługiwane). Jest obsługiwana w systemie Windows Server 2012, ale należy włączyć środowisko pulpitu.
Można sprawdzić Podgląd zdarzeń, aby zobaczyć, czy istnieją błędy funkcji Hypervisor. Aby to zrobić, otwórz Podgląd zdarzeń (**klucza Start**+**R**, a następnie wpisz `eventvwr`), a następnie wybierz **Dzienniki Windows**, **System**. Następnie przeprowadź filtrowanie dziennika przez źródło zdarzenia, ustawienie źródła **funkcji Hyper-V-funkcji Hypervisor**. Sprawdź, czy błędy, aby ułatwić zidentyfikowanie przyczyny.
Jeśli Twoje spełnia procesora minimalne wymagania, ale funkcja hypervisor nadal nie działa prawidłowo, należy wziąć pod uwagę wyszukiwanie po podjęciu występuje uaktualnienie systemu BIOS dostępnej dla komputera. Jeśli istnieje, i chcesz uaktualnić, pamiętaj obserwować wszystkie środki ostrożności od producenta, podczas uaktualniania do systemu BIOS (na przykład upewniając się, uaktualnienie oprogramowania układowego BIOS nie zostało przerwane przez utraty zasilania, które trwale może uszkodzić system BIOS).
- Upewnij się, że masz co najmniej 4 GB pamięci systemu i że jego jest nie są używane przez inne programy dużej ilości zasobów i procesów.
- Usuń/wyłączyć sterowników firm trzecich lub oprogramowania, które zakłócają sieci wirtualnej.
Istnieją znane problemy z niektórych 3rd produktów innych firm, które są zainstalowane w systemie Windows 8, takie jak sterowniki/protokołów sieciowych, które nie są w pełni zgodny ze stosu sieciowego funkcji Hyper-V.
Ogólnie rzecz biorąc będzie ona do tych produktów deweloperom aktualizacji oprogramowania, aby był zgodny z systemem Windows 8 i funkcji Hyper-V.
Następujące produkty mogą wymagać uaktualnienia pod kątem zgodności z systemem Windows 8: VirtualBox, Virtual PC 7, VMWare, niektórzy klienci sieci VPN oprogramowania zapory, niektóre wersje klientów sieci VPN oprogramowania Cisco i innych systemów wirtualizacji. Praca z deweloper oprogramowania wirtualizacji wątpliwe zachęcania go do uaktualnienia oprogramowania, aby był zgodny z systemem Windows 8 i funkcji Hyper-V.
Jako *obejście*, można wyłączyć wszystkie sterowniki innych firm i aplikacje, które zakłócają sieci wirtualnej, używanego przez Emulator do komunikowania się z programem Visual Studio. Aplikacje te mogą obejmować:
- Aplikacje antywirusowe, (które dołączyć do stosu sieciowego)
- Narzędzia do monitorowania sieci
- Narzędzia rejestrowania w sieci
- Inne oprogramowanie monitorujące systemu
Innym możliwym obejściem ograniczony odinstalowaniu produktów w zapytania i żądanie developer produktu do wersji jest dostępna zaktualizowana wersja, ma wykonać następujące czynności.
1. Uruchom Menedżera połączeń sieciowych (na ekranie startowym wpisz `View Network Connections` i wybierz tę opcję, aby wyświetlić połączenia sieciowego.)
2. Dla karty vEthernet (wewnętrzny Ethernet portu Windows Phone Emulator wewnętrznego przełącznika), wybierz **właściwości** z menu kontekstowego.
Właściwości karty są wyświetlane w tym miejscu.
3. Dla tej karty, tylko elementy, które należy wybrać w obszarze **to połączenie wykorzystuje następujące elementy** powinny być następujące:
- Klient sieci Microsoft Networks
- Harmonogram pakietów QoS
- Udostępnianie plików i drukarek w sieciach Microsoft Networks
- Sterownik protokołu LLDP firmy Microsoft
- Warstwa łącza sterownik mapowania topologii odnajdowania
- Obiekt odpowiadający odnajdywania topologii warstwy linku
- Protokół internetowy w wersji 6 (TCP/IPv6)
- Protokół internetowy w wersji 4 (TCP/IPv4)
4. Usuń zaznaczenie wszystkich innych elementów.
Wadą się przy użyciu tej metody polega na ilekroć nowych produktów innych firm 3 instaluje sterowniki nieobsługiwana lub każdym razem, gdy emulator jest zainstalowany, te kroki należy powtórzyć.
Po odinstalowaniu produktów innych firm może być konieczne przywrócić przełącznika wewnętrznego Emulator Windows Phone. Aby to zrobić:
- Otwórz Hyper-V i przejdź do Menedżera przełącznika wirtualnego. Utwórz przełącznik wirtualny o nazwie "Windows Phone Emulator wewnętrznego przełącznika" i ustaw jej typ połączenia na **sieci wewnętrznej**.
Teraz uruchom emulator. Wszystko powinno działać.
## <a name="NoBoot"></a> Komputerowi nie uda się uruchomić po zainstalowaniu emulatora
Ten problem może wystąpić, gdy są spełnione następujące warunki:
- Komputer ma gigabajt płyty głównej.
- USB3 jest włączona na płycie głównej.
Aby rozwiązać ten problem, wyłącz USB3 w ustawieniach systemu BIOS płyty głównej, a następnie uruchom ponownie komputer. Sprawdź, czy gigabajt wydała aktualizacji dla systemu BIOS z płyty głównej.
Aby uzyskać więcej informacji, zobacz następujący artykuł bazy wiedzy Knowledge Base: [rozruchu awarii po zakończeniu instalacji roli funkcji Hyper-V w systemach gigabajt](https://support.microsoft.com/en-us/kb/2693144).
## <a name="ADB"></a> Program Visual Studio zablokowania próby wdrożenia aplikacji w emulatorze lub emulator nie jest wyświetlany jako element docelowy debugowania w innych środowiskach IDE
Jeśli emulator jest uruchomiona, ale nie ma się połączyć z ADB (Android Debug Bridge) lub pojawia się narzędzia systemu Android, które korzystają z ADB (na przykład programu Android Studio lub Eclipse), może być konieczne dostosowanie, gdy emulator szuka ADB. Emulator używa klucza rejestru do identyfikowania podstawowa Lokalizacja zestawu Android SDK i szuka pliku \platform-tools\adb.exe, w tym katalogu. Aby zmodyfikować ścieżkę zestawu Android SDK używany przez emulator:
- Otwórz Edytor rejestru, wybierając **Uruchom** z menu kontekstowego przyciski Start, wpisując `regedit` w oknie dialogowym i wybierając pozycję **OK**.
- Przejdź do *SDK Tools HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Android* w drzewie folderów po lewej stronie.
- Modyfikowanie **ścieżki** zmiennej rejestru, aby dopasować ścieżkę do zestawu SDK systemu Android.
Ponowne uruchomienie emulatora i powinno być teraz możliwe emulator połączone ADB i skojarzonych narzędzi dla systemu Android.
## <a name="XamarinPlayer"></a> Emulator zawiesza się, ponieważ nie można ustawić port UDP
Może wystąpić problem związany z powodu niezgodności z odtwarzaczem Xamarin. Emulator zawiesi się lub jeśli zostanie wyświetlony ten komunikat o błędzie "emulator nie jest w stanie połączyć się z system operacyjny urządzenia: nie można ustawić port UDP. Niektóre funkcje mogą być wyłączone", być może wystąpił problem. Wykonaj następujące kroki.
1. Odinstaluj program Xamarin Player.
2. Sprawdź, czy pole danej wirtualnej został usunięty (Xamarin Player działa na polu wirtualnego).
3. Przejdź do Menedżera urządzeń, wybierz opcję Pokaż ukryte urządzenia, a następnie usuń wszystkie elementy z wyjątkiem przypadków karty sieci fizycznej.
4. Możesz wypróbować, odinstalowanie/ponowne zainstalowanie funkcji Hyper-V po usunięciu niefizycznej sieciowe.
## <a name="Skylake"></a> Nie można dołączyć debugera do projektu Xamarin
Jeśli używasz systemu Windows 10 z procesorów Intel Skylake, aplikacje platformy Xamarin może się nie powieść się uruchamianie w emulatorze lub debugera programu Visual Studio nie może dołączyć do nich. Jest to spowodowane problem z funkcją Hyper-V i procesorów Skylake. Wykonaj następujące kroki, aby uniknąć tego problemu.
1. Otwórz Menedżera funkcji Hyper-V i wybierz maszynę Wirtualną, dla emulatora profilu, czy przy użyciu.
2. Wybierz **usunięcia zapisanego stanu** (w lewym dolnym rogu).
3. Wybierz **ustawień...**
4. Rozwiń węzeł procesora, a następnie wybierz **zgodności**.
5. Włącz **Migruj do komputera fizycznego z inną wersją procesora**.
6. Uruchom ponownie usługę (w obszarze **akcje**), a następnie spróbuj ponownie.
## <a name="GooglePlay"></a> Emulator nie powiedzie się uruchomić aplikację, która używa usług Google Play
Emulator nie jest dostarczany z bibliotekami dostępność usług Google Play. Emulator obsługuje jednak instalacji przeciąganie i upuszczanie plików w pliku zip.
## <a name="DragAndDrop"></a> Przeciąganie i upuszczanie plików, APK lub pliku w pliku zip nie działa
Emulator używa ADB.exe w celu ułatwienia transferu plików, gdy przeciągnij i upuść plik na ekranie. Jeśli wystąpi błąd podczas próby przeciągnij i upuść plik, to prawdopodobnie oznacza to, czy emulator nie jest podłączony do ADB.exe. Aby rozwiązać problem, wykonaj kroki opisane w [zablokowania programu Visual Studio, w trakcie wdrażania aplikacji w emulatorze lub emulator nie jest wyświetlany jako element docelowy debugowania w innych środowiskach IDE](#ADB).
## <a name="Resolution"></a> Rozdzielczość zrzut ekranu jest nieprawidłowa
Jeśli wykonujesz zrzut ekranu za pomocą karty zrzut ekranu w **dodatkowe narzędzia** okna i obraz wynikowy jest nieoczekiwany rozmiar, konieczne może być dostosować poziom powiększenia ekranu przed wybraniem **przechwytywania**. Emulator przyjmuje zrzuty ekranu w rozdzielczości ekranu na monitorze komputera hosta.
## <a name="OpenGL"></a> Emulator nie powiedzie się do renderowania zawartości ze specyfikacji OpenGL
Emulator renderuje zawartość ze specyfikacji OpenGL, przy użyciu procesora GPU na komputerze hosta i używa projektu kąt na konwertowanie tych wywołań programu DirectX. Jeśli aplikacja poprawnie renderowany na urządzeniu, ale niepoprawne w emulatorze, jest prawdopodobne, że urządzenie jest łagodzenia nieprawidłowe wywołanie OpenGL (na przykład za pomocą programu do cieniowania zmiennych, które nie są zgodne).
## <a name="Multitouch"></a> Emulator nie odpowiada na gestów dotykowych wielu
W niektórych przypadkach emulator uruchomi oraz nie odpowiada na wielodotyku albo za pomocą możliwości bezpośredniej interakcji z obsługą dotykową ekranu lub za pomocą narzędzia Obsługa wielodotyku na pasku narzędzi emulatora. Jeśli jest to możliwe, wybierz opcję **Obróć** znajdujący się na pasku narzędzi emulatora i spróbuj ponownie wykorzystać wielodotyku. Jeśli problem będzie się powtarzać, zapoznaj się z [emulatora zakończy się niepowodzeniem do renderowania zawartości ze specyfikacji OpenGL](#OpenGL) problem.
## <a name="Support"></a> Zasoby pomocy technicznej
Jeśli komputer-host spełnia wymagania systemowe i wystąpi problem, nie są uwzględnione w tym przewodniku rozwiązywania problemów:
- Zadaj pytanie na temat korzystania z StackOverflow [emulator systemu android](http://stackoverflow.com/questions/tagged/android-emulator) znacznikami visual studio.
- Zgłoś problem za pomocą Wyślij uśmiech narzędzia programu Visual Studio lub w Menedżerze emulatorów. | 71.458861 | 522 | 0.774235 | pol_Latn | 1 |
2f82c4d58ae686b97e3c12c632e9cfa9359eb27d | 46 | md | Markdown | README.md | Mr-Prakhar/JavaScriptCode | 802e69ac4cfba56c64e4de2c2b1f2093a8762cfe | [
"Apache-2.0"
] | null | null | null | README.md | Mr-Prakhar/JavaScriptCode | 802e69ac4cfba56c64e4de2c2b1f2093a8762cfe | [
"Apache-2.0"
] | null | null | null | README.md | Mr-Prakhar/JavaScriptCode | 802e69ac4cfba56c64e4de2c2b1f2093a8762cfe | [
"Apache-2.0"
] | null | null | null | # JavaScriptCode
A Complete JavaScript Course
| 15.333333 | 28 | 0.847826 | deu_Latn | 0.27772 |
2f82d5c6147d5cbb4ee33b76f89e8673b0f90f04 | 669 | md | Markdown | README.md | FunWithPythonProgramming/hangman | b235eccba1ffb3a661754312d723193316caa005 | [
"MIT"
] | null | null | null | README.md | FunWithPythonProgramming/hangman | b235eccba1ffb3a661754312d723193316caa005 | [
"MIT"
] | null | null | null | README.md | FunWithPythonProgramming/hangman | b235eccba1ffb3a661754312d723193316caa005 | [
"MIT"
] | null | null | null | The code in this repository will allow us to play a simple game of hangman.
Goal:
With the given list of words, we want to pick a random word and have the user guess what the word will be. The user can win if and only if they guess all the letters in the word before hitting the threshhold. We must fulfill the following requirements:
* Randomly select word from list
* Repeatedly ask user for input until word is solved or they have used up all their guesses
* User Input must be validated (can only be a single letter)
* User must receive output each guess:
* How many guesses are left
* What letters have already been guessed
* Current status of guessed word
| 47.785714 | 252 | 0.775785 | eng_Latn | 0.999978 |
2f845b1f7cd25dce06b207439a46dcec90e1ba82 | 15,921 | md | Markdown | articles/quickstart/webapp/aspnet-core-3/_includes/_login.md | ryanparrishux/docs | 64fc5effac6a772e495c78e1ffbc3e7622cca5ea | [
"MIT"
] | null | null | null | articles/quickstart/webapp/aspnet-core-3/_includes/_login.md | ryanparrishux/docs | 64fc5effac6a772e495c78e1ffbc3e7622cca5ea | [
"MIT"
] | null | null | null | articles/quickstart/webapp/aspnet-core-3/_includes/_login.md | ryanparrishux/docs | 64fc5effac6a772e495c78e1ffbc3e7622cca5ea | [
"MIT"
] | null | null | null | <!-- markdownlint-disable MD002 MD041 -->
## Configure Your Application to Use Auth0
[Universal Login](/hosted-pages/login) is the easiest way to set up authentication in your application. We recommend using it for the best experience, best security and the fullest array of features. This guide will use it to provide a way for your users to log in to your ASP.NET Core application.
::: note
You can also create a custom login for prompting the user for their username and password. To learn how to do this in your application, follow the [Custom Login sample](https://github.com/auth0-samples/auth0-aspnetcore-mvc-samples/tree/master/Samples/custom-login).
:::
### Install dependencies
To integrate Auth0 with ASP.NET Core you will use the Cookie and OpenID Connect (OIDC) authentication handlers.
If you are adding this to your own existing project, then please make sure that you add the `Microsoft.AspNetCore.Authentication.Cookies` and `Microsoft.AspNetCore.Authentication.OpenIdConnect` packages to your application.
```bash
Install-Package Microsoft.AspNetCore.Authentication.Cookies
Install-Package Microsoft.AspNetCore.Authentication.OpenIdConnect
```
### Install and configure OpenID Connect middleware
To enable authentication in your ASP.NET Core application, use the OpenID Connect (OIDC) middleware.
Go to the `ConfigureServices` method of your `Startup` class. To add the authentication services, call the `AddAuthentication` method. To enable cookie authentication, call the `AddCookie` method.
Next, configure the OIDC authentication handler. Add a call to `AddOpenIdConnect`. To configure the authentication scheme, pass "Auth0" as the `authenticationScheme` parameter. You will use this value later to challenge the OIDC middleware.
Configure other parameters, such as `ClientId`, `ClientSecret` and `ResponseType`.
By default, the OIDC middleware requests both the `openid` and `profile` scopes. Because of that, you may get a large ID Token in return. We suggest that you ask only for the scopes you need. You can read more about requesting additional scopes in the [User Profile step](/quickstart/webapp/aspnet-core/02-user-profile).
::: note
In the code sample below, only the `openid` scope is requested.
:::
```cs
// Startup.cs
public void ConfigureServices(IServiceCollection services)
{
// Cookie configuration for HTTP to support cookies with SameSite=None
services.ConfigureSameSiteNoneCookies();
// Cookie configuration for HTTPS
// services.Configure<CookiePolicyOptions>(options =>
// {
// options.MinimumSameSitePolicy = SameSiteMode.None
// });
// Add authentication services
services.AddAuthentication(options => {
options.DefaultAuthenticateScheme = CookieAuthenticationDefaults.AuthenticationScheme;
options.DefaultSignInScheme = CookieAuthenticationDefaults.AuthenticationScheme;
options.DefaultChallengeScheme = CookieAuthenticationDefaults.AuthenticationScheme;
})
.AddCookie()
.AddOpenIdConnect("Auth0", options => {
// Set the authority to your Auth0 domain
options.Authority = $"https://{Configuration["Auth0:Domain"]}";
// Configure the Auth0 Client ID and Client Secret
options.ClientId = Configuration["Auth0:ClientId"];
options.ClientSecret = Configuration["Auth0:ClientSecret"];
// Set response type to code
options.ResponseType = OpenIdConnectResponseType.Code;
// Configure the scope
options.Scope.Clear();
options.Scope.Add("openid");
// Set the callback path, so Auth0 will call back to http://localhost:3000/callback
// Also ensure that you have added the URL as an Allowed Callback URL in your Auth0 dashboard
options.CallbackPath = new PathString("/callback");
// Configure the Claims Issuer to be Auth0
options.ClaimsIssuer = "Auth0";
});
// Add framework services.
services.AddControllersWithViews();
}
```
::: note
The `ConfigureSameSiteNoneCookies` method used above was added as part of the [sample application](https://github.com/auth0-samples/auth0-aspnetcore-mvc-samples/blob/master/Quickstart/01-Login/Support/SameSiteServiceCollectionExtensions.cs) in order to make cookies with SameSite=None work over HTTP when using Chrome ([read more here](https://blog.chromium.org/2019/10/developers-get-ready-for-new.html)). We recommend using HTTPS instead of HTTP, which removes the need for the `ConfigureSameSiteNoneCookies` method.
:::
Next, add the authentication middleware. In the `Configure` method of the `Startup` class, call the `UseAuthentication` and `UseAuthorization` methods.
```csharp
// Startup.cs
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
if (env.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
else
{
app.UseExceptionHandler("/Home/Error");
// The default HSTS value is 30 days. You may want to change this for production scenarios, see https://aka.ms/aspnetcore-hsts.
app.UseHsts();
}
app.UseStaticFiles();
app.UseCookiePolicy();
app.UseRouting();
app.UseAuthentication();
app.UseAuthorization();
app.UseEndpoints(endpoints =>
{
endpoints.MapControllerRoute(
name: "default",
pattern: "{controller=Home}/{action=Index}/{id?}");
});
}
```
## Trigger Authentication
### Add the Login and Logout methods
Add the `Login` and `Logout` actions to `AccountController`.
To add the `Login` action, call `ChallengeAsync` and pass "Auth0" as the authentication scheme. This will invoke the OIDC authentication handler you registered in the `ConfigureServices` method.
After the OIDC middleware signs the user in, the user is also automatically signed in to the cookie middleware. This allows the user to be authenticated on subsequent requests.
For the `Logout` action, you need to sign the user out of both middlewares.
The `RedirectUri` passed in both instances indicates where the user is redirected after they log in or fail to log in.
```cs
// Controllers/AccountController.cs
using Microsoft.AspNetCore.Authentication;
using Microsoft.AspNetCore.Authentication.Cookies;
public class AccountController : Controller
{
public async Task Login(string returnUrl = "/")
{
await HttpContext.ChallengeAsync("Auth0", new AuthenticationProperties() { RedirectUri = returnUrl });
}
[Authorize]
public async Task Logout()
{
await HttpContext.SignOutAsync("Auth0", new AuthenticationProperties
{
// Indicate here where Auth0 should redirect the user after a logout.
// Note that the resulting absolute Uri must be added to the
// **Allowed Logout URLs** settings for the app.
RedirectUri = Url.Action("Index", "Home")
});
await HttpContext.SignOutAsync(CookieAuthenticationDefaults.AuthenticationScheme);
}
}
```
ASP.NET Core calls `SignOutAsync` for the "Auth0" authentication scheme. You need to provide the OIDC middleware with the URL for logging the user out of Auth0. To set the URL, handle the `OnRedirectToIdentityProviderForSignOut` event when you register the OIDC authentication handler.
When the application calls `SignOutAsync` for the OIDC middleware, it also calls the `/v2/logout` endpoint of the Auth0 Authentication API, which will ensure the user is logged out of Auth0.
If you specify the `returnTo` parameter, the users will be redirected there after they are logged out. Specify the URL for redirecting users in the **Allowed Logout URLs** field in your [Application Settings](${manage_url}/#/applications/${account.clientId}/settings).
In the `Startup.cs` file, update the call to `AddOpenIdConnect` with the following code:
```csharp
// Startup.cs
public void ConfigureServices(IServiceCollection services)
{
// Some code omitted for brevity...
// Add authentication services
services.AddAuthentication(options => {
//...
})
.AddCookie()
.AddOpenIdConnect("Auth0", options => {
// ...
options.Events = new OpenIdConnectEvents
{
// handle the logout redirection
OnRedirectToIdentityProviderForSignOut = (context) =>
{
var logoutUri = $"https://{Configuration["Auth0:Domain"]}/v2/logout?client_id={Configuration["Auth0:ClientId"]}";
var postLogoutUri = context.Properties.RedirectUri;
if (!string.IsNullOrEmpty(postLogoutUri))
{
if (postLogoutUri.StartsWith("/"))
{
// transform to absolute
var request = context.Request;
postLogoutUri = request.Scheme + "://" + request.Host + request.PathBase + postLogoutUri;
}
logoutUri += $"&returnTo={ Uri.EscapeDataString(postLogoutUri)}";
}
context.Response.Redirect(logoutUri);
context.HandleResponse();
return Task.CompletedTask;
}
};
});
}
```
### Add the Login and Logout buttons
Add the **Log In** and **Log Out** buttons to the navigation bar. In the `/Views/Shared/_Layout.cshtml` file, in the navigation bar section, add code that displays the **Log Out** button when the user is authenticated and the **Log In** button if not. The buttons link to the `Logout` and `Login` actions in the `AccountController`:
```html
<!-- Views/Shared/_Layout.cshtml -->
<div class="navbar-collapse collapse d-sm-inline-flex flex-sm-row-reverse">
<ul class="nav navbar-nav">
<li><a asp-area="" asp-controller="Home" asp-action="Index">Home</a></li>
</ul>
<ul class="nav navbar-nav navbar-right">
@if (User.Identity.IsAuthenticated)
{
<li><a id="qsLogoutBtn" asp-controller="Account" asp-action="Logout">Logout</a></li>
}
else
{
<li><a id="qsLoginBtn" asp-controller="Account" asp-action="Login">Login</a></li>
}
</ul>
</div>
```
### Run the application
When the user selects the **Log In** button, the OIDC middleware redirects them to the hosted version of the [Lock](/libraries/lock/v10/customization) widget in your Auth0 domain.
#### About the login flow
1. The user clicks on the **Log In** button and is directed to the `Login` route.
2. The `ChallengeAsync` tells the ASP.NET authentication middleware to issue a challenge to the authentication handler registered with the Auth0 `authenticationScheme` parameter. The parameter uses the "Auth0" value you passed in the call to `AddOpenIdConnect` in the `Startup` class.
3. The OIDC handler redirects the user to the Auth0 `/authorize` endpoint, which displays the Lock widget. The user can log in with their username and password, social provider or any other identity provider.
4. Once the user has logged in, Auth0 calls back to the `/callback` endpoint in your application and passes along an authorization code.
5. The OIDC handler intercepts requests made to the `/callback` path.
6. The handler looks for the authorization code, which Auth0 sent in the query string.
7. The OIDC handler calls the `/oauth/token` endpoint to exchange the authorization code for the user's ID and Access Tokens.
8. The OIDC middleware extracts the user information from the claims on the ID Token.
9. The OIDC middleware returns a successful authentication response and a cookie which indicates that the user is authenticated. The cookie contains claims with the user's information. The cookie is stored, so that the cookie middleware will automatically authenticate the user on any future requests. The OIDC middleware receives no more requests, unless it is explicitly challenged.
## Obtain an Access Token for Calling an API
If you want to call an API from your MVC application, you need to obtain an Access Token issued for the API you want to call. To obtain the token, pass an additional `audience` parameter containing the API identifier to the Auth0 authorization endpoint, which you can get from the API's [Application Settings](${manage_url}/#/applications).
In the configuration for the `OpenIdConnectOptions` object, handle the `OnRedirectToIdentityProvider` event and add the `audience` parameter to `ProtocolMessage`.
```csharp
// Startup.cs
public void ConfigureServices(IServiceCollection services)
{
// Some code omitted for brevity...
services.AddAuthentication(options => {
//...
})
.AddCookie()
.AddOpenIdConnect("Auth0", options => {
// ...
options.Events = new OpenIdConnectEvents
{
OnRedirectToIdentityProvider = context =>
{
// The context's ProtocolMessage can be used to pass along additional query parameters
// to Auth0's /authorize endpoint.
//
// Set the audience query parameter to the API identifier to ensure the returned Access Tokens can be used
// to call protected endpoints on the corresponding API.
context.ProtocolMessage.SetParameter("audience", Configuration["Auth0:Audience"]);
return Task.FromResult(0);
}
};
});
}
```
Be sure to also update your application's `appsettings.json` file to include the Audience configuration:
``` xml
"Auth0": {
...
"Audience": "${apiIdentifier}"
}
```
### Store and retrieve the tokens
The OIDC middleware in ASP.NET Core automatically decodes the ID Token returned from Auth0 and adds the claims from the ID Token as claims in the `ClaimsIdentity`. This means that you can use `User.Claims.FirstOrDefault("<claim type>").Value` to obtain the value of any claim inside any action in your controllers.
The seed project contains a controller action and view that display the claims associated with a user. Once a user has logged in, you can go to `/Account/Claims` to see these claims.
In order to be able to retrieve the Access Token to authenticate the user in calls to your API, update the Startup.cs file so that, when calling `AddOpenIdConnect`, the `SaveTokens` property is set to `true`.
```csharp
// Startup.cs
public void ConfigureServices(IServiceCollection services)
{
// Some code omitted for brevity...
// Add authentication services
services.AddAuthentication(options => {
//...
})
.AddCookie()
.AddOpenIdConnect("Auth0", options => {
// ...
// Saves tokens to the AuthenticationProperties
options.SaveTokens = true;
options.Events = new OpenIdConnectEvents
{
// handle the logout redirection
OnRedirectToIdentityProviderForSignOut = (context) =>
{
//...
}
};
});
}
```
To retrieve the tokens, you can call `HttpContext.GetTokenAsync` and use it as needed:
```csharp
// Inside one of your controller actions
if (User.Identity.IsAuthenticated)
{
string accessToken = await HttpContext.GetTokenAsync("access_token");
// if you need to check the Access Token expiration time, use this value
// provided on the authorization response and stored.
// do not attempt to inspect/decode the access token
DateTime accessTokenExpiresAt = DateTime.Parse(
await HttpContext.GetTokenAsync("expires_at"),
CultureInfo.InvariantCulture,
DateTimeStyles.RoundtripKind);
string idToken = await HttpContext.GetTokenAsync("id_token");
// Now you can use them. For more info on when and how to use the
// Access Token and ID Token, see https://auth0.com/docs/tokens
}
```
For general information on using APIs with web applications, see the [Authorization Code Flow](/flows/concepts/auth-code) article.
| 43.381471 | 518 | 0.706551 | eng_Latn | 0.90961 |
2f849118a07fcb6ea0b0623dd5da9a795b1d5f9f | 3,861 | md | Markdown | BooksApp/README.md | Android-Student-Club-Turkey/-rnek-Android-Projeleri | ea92fd2c051d98329680a12f1afa95857346d5b8 | [
"MIT"
] | 6 | 2021-12-05T12:43:03.000Z | 2022-01-19T17:53:56.000Z | BooksApp/README.md | Android-Student-Club-Turkey/-rnek-Android-Projeleri | ea92fd2c051d98329680a12f1afa95857346d5b8 | [
"MIT"
] | null | null | null | BooksApp/README.md | Android-Student-Club-Turkey/-rnek-Android-Projeleri | ea92fd2c051d98329680a12f1afa95857346d5b8 | [
"MIT"
] | null | null | null | <h1 align="center">
BooksApp
</h1>
<h2 align="center">
Project Features
</h2>
<h3 align="left">
- MVVM (Model, View, ViewModel) <br>
- LiveData <br>
- DataBinding <br>
- Retrofit <br>
- Room Database <br>
- Navigation Component(NavGraph, BottomNav) <br>
- ViewPager2 in TabLayout <br>
- SearchView, Vertical Adapter(BestSellers) and Horizontal Adapter(All Books) with ConcatAdapter for Main Screen <br>
- Firebase Auth (<a href="https://firebase.google.com/docs/auth?authuser=0">Source</a>) <br>
- SearchView in Adapter (<a href="https://www.tugbaustundag.com/android-recyclerviewa-search-filter-ekleme/">Source</a>) <br>
- Picasso (<a href="https://square.github.io/picasso/">Source</a>) <br>
- Lottie (<a href="https://github.com/LottieFiles/lottie-android">Source</a>) <br>
- Animated Svg for Splash (<a href="https://github.com/jaredrummler/AnimatedSvgView">Source</a>)
</h3><br>
<p align="left">
<img align="left" src="https://github.com/cnrture/BooksApp/blob/main/Screenshots/sign_in.png" width="250" height="530"/>
<img align="left" src="https://github.com/cnrture/BooksApp/blob/main/Screenshots/sign_up.png" width="250" height="530"/>
</p>
<h2 align="center">
Login Screen
</h2>
<h3 align="center"><br><br><br><br><br><br>TabLayout and ViewPager2 used for Login and Sign up screens. Login and Sign up operations are provided with Firebase Authorization</h3><br><br><br><br><br><br><br><br><br><br>
<h2 align="center">
Main Screen
</h2>
<h3 align="left">
- Books listed using RecyclerView + DataBinding. <br>
- For the main screen, I utilized the searchView, horizontal adapter and vertical adapter in a single recyclerView by combining the ConcatAdapter structure. <br>
- Book search feature works with author, book name and publisher name. Search can be made with the SearchView in the RecyclerView.<br>
- When the book image is pressed, the BottomShhet opens and details are displayed. The book is sent to the basket with the Add to Basket button. <br>
- The "+" button in the CardView is used to add book to basket. (Note: Images are added with url.) <br>
</h3>
<p align="center">
<img align="center" src="https://github.com/cnrture/BooksApp/blob/main/Screenshots/books.png" width="250" height="530"/>
<img align="center" src="https://github.com/cnrture/BooksApp/blob/main/Screenshots/books_2.png" width="250" height="530"/>
</p>
<p align="center">
<img align="center" src="https://github.com/cnrture/BooksApp/blob/main/Screenshots/book_detail_bottom.png" width="250" height="530"/>
</p>
<br><br>
<img align="right" src="https://github.com/cnrture/BooksApp/blob/main/Screenshots/books_basket.png" width="250" height="530"/>
<h2 align="center">
Basket Screen
</h2>
<h3 align="center"><br><br><br><br><br><br>
Books are added to basket with Room Database, printed with RecyclerView. It is deleted from the Room Database again with the Delete button.
</h3>
<br><br><br><br><br><br><br><br><br><br>
<img align="left" src="https://github.com/cnrture/BooksApp/blob/main/Screenshots/payment.png" width="250" height="530"/>
<img align="left" src="https://github.com/cnrture/BooksApp/blob/main/Screenshots/order_alert.png" width="250" height="530"/>
<br>
<h2 align="center">
Payment Screen
</h2>
<h3 align="center"><br><br><br><br><br>
When one of the 4 payment methods is selected, the relevant information is uploaded to the card below. It can be edited with the edit address button. With the Order Now button, an alert appears and the order is placed.
</h3>
<br><br><br><br><br><br><br><br><br><br><br>
<img align="left" src="https://github.com/cnrture/BooksApp/blob/main/Screenshots/profile.png" width="250" height="530"/>
<br>
<h2 align="center">
Profile Screen
</h2>
<h3 align="center"><br><br><br><br><br>
User information is retrieved with Firebase Auth. Log out the account by clicking the Sign Out button.
</h3>
| 41.967391 | 218 | 0.719244 | eng_Latn | 0.548371 |
2f84f76e755220681d8073a377efefe72bbdca19 | 21,477 | md | Markdown | windows-apps-src/cpp-and-winrt-apis/weak-references.md | hyoshioka0128/windows-uwp | 7585bf66405b307d7ed7788d49003dc4ddba65e6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | windows-apps-src/cpp-and-winrt-apis/weak-references.md | hyoshioka0128/windows-uwp | 7585bf66405b307d7ed7788d49003dc4ddba65e6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | windows-apps-src/cpp-and-winrt-apis/weak-references.md | hyoshioka0128/windows-uwp | 7585bf66405b307d7ed7788d49003dc4ddba65e6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
description: The Windows Runtime is a reference-counted system; and in such a system it's important for you to know about the significance of, and distinction between, strong and weak references.
title: Weak references in C++/WinRT
ms.date: 05/16/2019
ms.topic: article
keywords: windows 10, uwp, standard, c++, cpp, winrt, projection, strong, weak, reference
ms.localizationpriority: medium
ms.custom: RS5
---
# Strong and weak references in C++/WinRT
The Windows Runtime is a reference-counted system; and in such a system it's important for you to know about the significance of, and distinction between, strong and weak references (and references that are neither, such as the implicit *this* pointer). As you'll see in this topic, knowing how to manage these references correctly can mean the difference between a reliable system that runs smoothly, and one that crashes unpredictably. By providing helper functions that have deep support in the language projection, [C++/WinRT](/windows/uwp/cpp-and-winrt-apis/intro-to-using-cpp-with-winrt) meets you halfway in your work of building more complex systems simply and correctly.
## Safely accessing the *this* pointer in a class-member coroutine
For more info about coroutines, and code examples, see [Concurrency and asynchronous operations with C++/WinRT](/windows/uwp/cpp-and-winrt-apis/concurrency).
The code listing below shows a typical example of a coroutine that's a member function of a class. You can copy-paste this example into the specified files in a new **Windows Console Application (C++/WinRT)** project.
```cppwinrt
// pch.h
#pragma once
#include <iostream>
#include <winrt/Windows.Foundation.h>
// main.cpp : Defines the entry point for the console application.
#include "pch.h"
using namespace winrt;
using namespace Windows::Foundation;
using namespace std::chrono_literals;
struct MyClass : winrt::implements<MyClass, IInspectable>
{
winrt::hstring m_value{ L"Hello, World!" };
IAsyncOperation<winrt::hstring> RetrieveValueAsync()
{
co_await 5s;
co_return m_value;
}
};
int main()
{
winrt::init_apartment();
auto myclass_instance{ winrt::make_self<MyClass>() };
auto async{ myclass_instance->RetrieveValueAsync() };
winrt::hstring result{ async.get() };
std::wcout << result.c_str() << std::endl;
}
```
**MyClass::RetrieveValueAsync** spends some time working, and eventually it returns a copy of the `MyClass::m_value` data member. Calling **RetrieveValueAsync** causes an asynchronous object to be created, and that object has an implicit *this* pointer (through which, eventually, `m_value` is accessed).
Remember that, in a coroutine, execution is synchronous up until the first suspension point, where control is returned to the caller. In **RetrieveValueAsync**, the first `co_await` is the first suspension point. By the time the coroutine resumes (around five seconds later, in this case), anything might have happened to the implicit *this* pointer through which we access `m_value`.
Here's the full sequence of events.
1. In **main**, an instance of **MyClass** is created (`myclass_instance`).
2. The `async` object is created, pointing (via its *this*) to `myclass_instance`.
3. The **winrt::Windows::Foundation::IAsyncAction::get** function hits its first suspension point, blocks for a few seconds, and then returns the result of **RetrieveValueAsync**.
4. **RetrieveValueAsync** returns the value of `this->m_value`.
Step 4 is safe only as long as *this* remains valid.
But what if the class instance is destroyed before the async operation completes? There are all kinds of ways the class instance could go out of scope before the asynchronous method has completed. But we can simulate it by setting the class instance to `nullptr`.
```cppwinrt
int main()
{
winrt::init_apartment();
auto myclass_instance{ winrt::make_self<MyClass>() };
auto async{ myclass_instance->RetrieveValueAsync() };
myclass_instance = nullptr; // Simulate the class instance going out of scope.
winrt::hstring result{ async.get() }; // Behavior is now undefined; crashing is likely.
std::wcout << result.c_str() << std::endl;
}
```
After the point where we destroy the class instance, it looks like we don't directly refer to it again. But of course the asynchronous object has a *this* pointer to it, and tries to use that to copy the value stored inside the class instance. The coroutine is a member function, and it expects to be able to use its *this* pointer with impunity.
With this change to the code, we run into a problem in step 4, because the class instance has been destroyed, and *this* is no longer valid. As soon as the asynchronous object attempts to access the variable inside the class instance, it will crash (or do something entirely undefined).
The solution is to give the asynchronous operation—the coroutine—its own strong reference to the class instance. As currently written, the coroutine effectively holds a raw *this* pointer to the class instance; but that's not enough to keep the class instance alive.
To keep the class instance alive, change the implementation of **RetrieveValueAsync** to that shown below.
```cppwinrt
IAsyncOperation<winrt::hstring> RetrieveValueAsync()
{
auto strong_this{ get_strong() }; // Keep *this* alive.
co_await 5s;
co_return m_value;
}
```
A C++/WinRT class directly or indirectly derives from the [**winrt::implements**](/uwp/cpp-ref-for-winrt/implements) template. Because of that, the C++/WinRT object can call its [**implements.get_strong**](/uwp/cpp-ref-for-winrt/implements#implementsget_strong-function) protected member function to retrieve a strong reference to its *this* pointer. Note that there's no need to actually use the `strong_this` variable in the code example above; simply calling **get_strong** increments the C++/WinRT object's reference count, and keeps its implicit *this* pointer valid.
> [!IMPORTANT]
> Because **get_strong** is a member function of the **winrt::implements** struct template, you can call it only from a class that directly or indirectly derives from **winrt::implements**, such as a C++/WinRT class. For more info about deriving from **winrt::implements**, and examples, see [Author APIs with C++/WinRT](/windows/uwp/cpp-and-winrt-apis/author-apis).
This resolves the problem that we previously had when we got to step 4. Even if all other references to the class instance disappear, the coroutine has taken the precaution of guaranteeing that its dependencies are stable.
If a strong reference isn't appropriate, then you can instead call [**implements::get_weak**](/uwp/cpp-ref-for-winrt/implements#implementsget_weak-function) to retrieve a weak reference to *this*. Just confirm that you can retrieve a strong reference before accessing *this*. Again, **get_weak** is a member function of the **winrt::implements** struct template.
```cppwinrt
IAsyncOperation<winrt::hstring> RetrieveValueAsync()
{
auto weak_this{ get_weak() }; // Maybe keep *this* alive.
co_await 5s;
if (auto strong_this{ weak_this.get() })
{
co_return m_value;
}
else
{
co_return L"";
}
}
```
In the example above, the weak reference doesn't keep the class instance from being destroyed when no strong references remain. But it gives you a way of checking whether a strong reference can be acquired before accessing the member variable.
## Safely accessing the *this* pointer with an event-handling delegate
### The scenario
For general info about event-handling, see [Handle events by using delegates in C++/WinRT](handle-events.md).
The previous section highlighted potential lifetime issues in the areas of coroutines and concurrency. But, if you handle an event with an object's member function, or from within a lambda function inside an object's member function, then you need to think about the relative lifetimes of the event recipient (the object handling the event) and the event source (the object raising the event). Let's look at some code examples.
The code listing below first defines a simple **EventSource** class, which raises a generic event that's handled by any delegates that have been added to it. This example event happens to use the [**Windows::Foundation::EventHandler**](/uwp/api/windows.foundation.eventhandler) delegate type, but the issues and remedies here apply to any and all delegate types.
Then, the **EventRecipient** class provides a handler for the **EventSource::Event** event in the form of a lambda function.
```cppwinrt
// pch.h
#pragma once
#include <iostream>
#include <winrt/Windows.Foundation.h>
// main.cpp : Defines the entry point for the console application.
#include "pch.h"
using namespace winrt;
using namespace Windows::Foundation;
struct EventSource
{
winrt::event<EventHandler<int>> m_event;
void Event(EventHandler<int> const& handler)
{
m_event.add(handler);
}
void RaiseEvent()
{
m_event(nullptr, 0);
}
};
struct EventRecipient : winrt::implements<EventRecipient, IInspectable>
{
winrt::hstring m_value{ L"Hello, World!" };
void Register(EventSource& event_source)
{
event_source.Event([&](auto&& ...)
{
std::wcout << m_value.c_str() << std::endl;
});
}
};
int main()
{
winrt::init_apartment();
EventSource event_source;
auto event_recipient{ winrt::make_self<EventRecipient>() };
event_recipient->Register(event_source);
event_source.RaiseEvent();
}
```
The pattern is that the event recipient has a lambda event handler with dependencies on its *this* pointer. Whenever the event recipient outlives the event source, it outlives those dependencies. And in those cases, which are common, the pattern works well. Some of these cases are obvious, such as when a UI page handles an event raised by a control that's on the page. The page outlives the button—so, the handler also outlives the button. This holds true any time the recipient owns the source (as a data member, for example), or any time the recipient and the source are siblings and directly owned by some other object. If you're sure you have a case where the handler won't outlive the *this* that it depends on, then you can capture *this* normally, without consideration for strong or weak lifetime.
But there are still cases where *this* doesn't outlive its use in a handler (including handlers for completion and progress events raised by asynchronous actions and operations), and it's important to know how to deal with them.
- If you're authoring a coroutine to implement an asynchronous method, then it's possible.
- In rare cases with certain XAML UI framework objects ([**SwapChainPanel**](/uwp/api/windows.ui.xaml.controls.swapchainpanel), for example), then it's possible, if the recipient is finalized without unregistering from the event source.
### The issue
This next version of the **main** function simulates what happens when the event recipient is destroyed (perhaps it goes out of scope) while the event source is still raising events.
```cppwinrt
int main()
{
winrt::init_apartment();
EventSource event_source;
auto event_recipient{ winrt::make_self<EventRecipient>() };
event_recipient->Register(event_source);
event_recipient = nullptr; // Simulate the event recipient going out of scope.
event_source.RaiseEvent(); // Behavior is now undefined within the lambda event handler; crashing is likely.
}
```
The event recipient is destroyed, but the lambda event handler within it is still subscribed to the **Event** event. When that event is raised, the lambda attempts to dereference the *this* pointer, which is at that point invalid. So, an access violation results from code in the handler (or in a coroutine's continuation) attempting to use it.
> [!IMPORTANT]
> If you encounter a situation like this, then you'll need to think about the lifetime of the *this* object; and whether or not the captured *this* object outlives the capture. If it doesn't, then capture it with a strong or a weak reference, as we'll demonstrate below.
>
> Or—if it makes sense for your scenario, and if threading considerations make it even possible—then another option is to revoke the handler after the recipient is done with the event, or in the recipient's destructor. See [Revoke a registered delegate](handle-events.md#revoke-a-registered-delegate).
This is how we're registering the handler.
```cppwinrt
event_source.Event([&](auto&& ...)
{
std::wcout << m_value.c_str() << std::endl;
});
```
The lambda automatically captures any local variables by reference. So, for this example, we could equivalently have written this.
```cppwinrt
event_source.Event([this](auto&& ...)
{
std::wcout << m_value.c_str() << std::endl;
});
```
In both cases, we're just capturing the raw *this* pointer. And that has no effect on reference-counting, so nothing is preventing the current object from being destroyed.
### The solution
The solution is to capture a strong reference. A strong reference *does* increment the reference count, and it *does* keep the current object alive. You just declare a capture variable (called `strong_this` in this example), and initialize it with a call to [**implements.get_strong**](/uwp/cpp-ref-for-winrt/implements#implementsget_strong-function), which retrieves a strong reference to our *this* pointer.
> [!IMPORTANT]
> Because **get_strong** is a member function of the **winrt::implements** struct template, you can call it only from a class that directly or indirectly derives from **winrt::implements**, such as a C++/WinRT class. For more info about deriving from **winrt::implements**, and examples, see [Author APIs with C++/WinRT](/windows/uwp/cpp-and-winrt-apis/author-apis).
```cppwinrt
event_source.Event([this, strong_this { get_strong()}](auto&& ...)
{
std::wcout << m_value.c_str() << std::endl;
});
```
You can even omit the automatic capture of the current object, and access the data member through the capture variable instead of via the implicit *this*.
```cppwinrt
event_source.Event([strong_this { get_strong()}](auto&& ...)
{
std::wcout << strong_this->m_value.c_str() << std::endl;
});
```
If a strong reference isn't appropriate, then you can instead call [**implements::get_weak**](/uwp/cpp-ref-for-winrt/implements#implementsget_weak-function) to retrieve a weak reference to *this*. Just confirm that you can still retrieve a strong reference from it before accessing members.
```cppwinrt
event_source.Event([weak_this{ get_weak() }](auto&& ...)
{
if (auto strong_this{ weak_this.get() })
{
std::wcout << strong_this->m_value.c_str() << std::endl;
}
});
```
### If you use a member function as a delegate
As well as lambda functions, these principles also apply to using a member function as your delegate. The syntax is different, so let's look at some code. First, here's the potentially unsafe member function event handler, using a raw *this* pointer.
```cppwinrt
struct EventRecipient : winrt::implements<EventRecipient, IInspectable>
{
winrt::hstring m_value{ L"Hello, World!" };
void Register(EventSource& event_source)
{
event_source.Event({ this, &EventRecipient::OnEvent });
}
void OnEvent(IInspectable const& /* sender */, int /* args */)
{
std::wcout << m_value.c_str() << std::endl;
}
};
```
This is the standard, conventional way to refer to an object and its member function. To make this safe, you can—as of version 10.0.17763.0 (Windows 10, version 1809) of the Windows SDK—establish a strong or a weak reference at the point where the handler is registered. At that point, the event recipient object is known to be still alive.
For a strong reference, just call [**get_strong**](/uwp/cpp-ref-for-winrt/implements#implementsget_strong-function) in place of the raw *this* pointer. C++/WinRT ensures that the resulting delegate holds a strong reference to the current object.
```cppwinrt
event_source.Event({ get_strong(), &EventRecipient::OnEvent });
```
For a weak reference, call [**get_weak**](/uwp/cpp-ref-for-winrt/implements#implementsget_weak-function). C++/WinRT ensures that the resulting delegate holds a weak reference. At the last minute, and behind the scenes, the delegate attempts to resolve the weak reference to a strong one, and only calls the member function if it's successful.
```cppwinrt
event_source.Event({ get_weak(), &EventRecipient::OnEvent });
```
### A weak reference example using **SwapChainPanel::CompositionScaleChanged**
In this code example, we use the [**SwapChainPanel::CompositionScaleChanged**](/uwp/api/windows.ui.xaml.controls.swapchainpanel.compositionscalechanged) event by way of another illustration of weak references. The code registers an event handler using a lambda that captures a weak reference to the recipient.
```cppwinrt
winrt::Windows::UI::Xaml::Controls::SwapChainPanel m_swapChainPanel;
winrt::event_token m_compositionScaleChangedEventToken;
void RegisterEventHandler()
{
m_compositionScaleChangedEventToken = m_swapChainPanel.CompositionScaleChanged([weak_this{ get_weak() }]
(Windows::UI::Xaml::Controls::SwapChainPanel const& sender,
Windows::Foundation::IInspectable const& object)
{
if (auto strong_this{ weak_this.get() })
{
strong_this->OnCompositionScaleChanged(sender, object);
}
});
}
void OnCompositionScaleChanged(Windows::UI::Xaml::Controls::SwapChainPanel const& sender,
Windows::Foundation::IInspectable const& object)
{
// Here, we know that the "this" object is valid.
}
```
In the lamba capture clause, a temporary variable is created, representing a weak reference to *this*. In the body of the lambda, if a strong reference to *this* can be obtained, then the **OnCompositionScaleChanged** function is called. That way, inside **OnCompositionScaleChanged**, *this* can safely be used.
## Weak references in C++/WinRT
Above, we saw weak references being used. In general, they're good for breaking cyclic references. For example, for the native implementation of the XAML-based UI framework—because of the historic design of the framework—the weak reference mechanism in C++/WinRT is necessary to handle cyclic references. Outside of XAML, though, you likely won't need to use weak references (not that there's anything inherently XAML-specific about them). Rather you should, more often than not, be able to design your own C++/WinRT APIs in such a way as to avoid the need for cyclic references and weak references.
For any given type that you declare, it's not immediately obvious to C++/WinRT whether or when weak references are needed. So, C++/WinRT provides weak reference support automatically on the struct template [**winrt::implements**](/uwp/cpp-ref-for-winrt/implements), from which your own C++/WinRT types directly or indirectly derive. It's pay-for-play, in that it doesn't cost you anything unless your object is actually queried for [**IWeakReferenceSource**](/windows/desktop/api/weakreference/nn-weakreference-iweakreferencesource). And you can choose explicitly to [opt out of that support](#opting-out-of-weak-reference-support).
### Code examples
The [**winrt::weak_ref**](/uwp/cpp-ref-for-winrt/weak-ref) struct template is one option for getting a weak reference to a class instance.
```cppwinrt
Class c;
winrt::weak_ref<Class> weak{ c };
```
Or, you can use the use the [**winrt::make_weak**](/uwp/cpp-ref-for-winrt/make-weak) helper function.
```cppwinrt
Class c;
auto weak = winrt::make_weak(c);
```
Creating a weak reference doesn't affect the reference count on the object itself; it just causes a control block to be allocated. That control block takes care of implementing the weak reference semantics. You can then try to promote the weak reference to a strong reference and, if successful, use it.
```cppwinrt
if (Class strong = weak.get())
{
// use strong, for example strong.DoWork();
}
```
Provided that some other strong reference still exists, the [**weak_ref::get**](/uwp/cpp-ref-for-winrt/weak-ref#weak_refget-function) call increments the reference count and returns the strong reference to the caller.
### Opting out of weak reference support
Weak reference support is automatic. But you can choose explicitly to opt out of that support by passing the [**winrt::no_weak_ref**](/uwp/cpp-ref-for-winrt/no-weak-ref) marker struct as a template argument to your base class.
If you derive directly from **winrt::implements**.
```cppwinrt
struct MyImplementation: implements<MyImplementation, IStringable, no_weak_ref>
{
...
}
```
If you're authoring a runtime class.
```cppwinrt
struct MyRuntimeClass: MyRuntimeClassT<MyRuntimeClass, no_weak_ref>
{
...
}
```
It doesn't matter where in the variadic parameter pack the marker struct appears. If you request a weak reference for an opted-out type, then the compiler will help you out with "*This is only for weak ref support*".
## Important APIs
* [implements::get_weak function](/uwp/cpp-ref-for-winrt/implements#implementsget_weak-function)
* [winrt::make_weak function template](/uwp/cpp-ref-for-winrt/make-weak)
* [winrt::no_weak_ref marker struct](/uwp/cpp-ref-for-winrt/no-weak-ref)
* [winrt::weak_ref struct template](/uwp/cpp-ref-for-winrt/weak-ref)
| 52.899015 | 813 | 0.750803 | eng_Latn | 0.992102 |
2f85df0104b29c995b5437b27734a04294d1e546 | 138 | md | Markdown | docs/libui/ui-attribute-type-family.md | illiapoplawski/kotlin-libui | 2424f1b9a0cc78bc619eb79ceca05dd956d925c5 | [
"MIT"
] | null | null | null | docs/libui/ui-attribute-type-family.md | illiapoplawski/kotlin-libui | 2424f1b9a0cc78bc619eb79ceca05dd956d925c5 | [
"MIT"
] | null | null | null | docs/libui/ui-attribute-type-family.md | illiapoplawski/kotlin-libui | 2424f1b9a0cc78bc619eb79ceca05dd956d925c5 | [
"MIT"
] | 1 | 2020-09-08T07:45:38.000Z | 2020-09-08T07:45:38.000Z | [libui](index.md) / [uiAttributeTypeFamily](./ui-attribute-type-family.md)
# uiAttributeTypeFamily
`val uiAttributeTypeFamily: UInt` | 27.6 | 75 | 0.76087 | yue_Hant | 0.121814 |
2f85fcc060549d9413f64f09d08b14008d3db932 | 2,110 | md | Markdown | articles/managed-applications/microsoft-common-passwordbox.md | Nike1016/azure-docs.hu-hu | eaca0faf37d4e64d5d6222ae8fd9c90222634341 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-09-29T16:59:33.000Z | 2019-09-29T16:59:33.000Z | articles/managed-applications/microsoft-common-passwordbox.md | Nike1016/azure-docs.hu-hu | eaca0faf37d4e64d5d6222ae8fd9c90222634341 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/managed-applications/microsoft-common-passwordbox.md | Nike1016/azure-docs.hu-hu | eaca0faf37d4e64d5d6222ae8fd9c90222634341 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Az Azure PasswordBox felhasználói felületi elemben |} A Microsoft Docs
description: Az Azure portal a Microsoft.Common.PasswordBox felhasználói felületi elem ismerteti.
services: managed-applications
documentationcenter: na
author: tfitzmac
manager: timlt
editor: tysonn
ms.service: managed-applications
ms.devlang: na
ms.topic: reference
ms.tgt_pltfrm: na
ms.workload: na
ms.date: 06/27/2018
ms.author: tomfitz
ms.openlocfilehash: 944f59da680c3a058a3cd245cca48d903e44ab87
ms.sourcegitcommit: d4dfbc34a1f03488e1b7bc5e711a11b72c717ada
ms.translationtype: MT
ms.contentlocale: hu-HU
ms.lasthandoff: 06/13/2019
ms.locfileid: "64710939"
---
# <a name="microsoftcommonpasswordbox-ui-element"></a>Microsoft.Common.PasswordBox UI element
Egy olyan vezérlőelem, adja meg és erősítsen meg egy jelszót is lehet.
## <a name="ui-sample"></a>Felhasználói felület minta
## <a name="schema"></a>Séma
```json
{
"name": "element1",
"type": "Microsoft.Common.PasswordBox",
"label": {
"password": "Password",
"confirmPassword": "Confirm password"
},
"toolTip": "",
"constraints": {
"required": true,
"regex": "",
"validationMessage": ""
},
"options": {
"hideConfirmation": false
},
"visible": true
}
```
## <a name="remarks"></a>Megjegyzések
- Ez az elem nem támogatja a `defaultValue` tulajdonság.
- A megvalósítás részleteit, `constraints`, lásd: [Microsoft.Common.TextBox](microsoft-common-textbox.md).
- Ha `options.hideConfirmation` értékre van állítva **igaz**, rejtett szöveget a másodikba általában a felhasználó jelszavát. Az alapértelmezett érték **hamis**.
## <a name="sample-output"></a>Példa kimenet
```json
"p4ssw0rd"
```
## <a name="next-steps"></a>További lépések
* Felhasználóifelület-definíciók létrehozása bevezetésért lásd: [CreateUiDefinition használatának első lépései](create-uidefinition-overview.md).
* Egy felhasználói felületi elemeket általános tulajdonságok leírásáért lásd: [CreateUiDefinition elemek](create-uidefinition-elements.md).
| 32.96875 | 161 | 0.75545 | hun_Latn | 0.982609 |
2f862467a58179b249f687c208bfb091dedaead9 | 431 | md | Markdown | powerbi-docs/includes/consumer-appliesto-nyyn.md | RaulSarachaga/powerbi-docs | 6d7d5e6b19e11d557dfa1b79b745728b4ee02b4e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | powerbi-docs/includes/consumer-appliesto-nyyn.md | RaulSarachaga/powerbi-docs | 6d7d5e6b19e11d557dfa1b79b745728b4ee02b4e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | powerbi-docs/includes/consumer-appliesto-nyyn.md | RaulSarachaga/powerbi-docs | 6d7d5e6b19e11d557dfa1b79b745728b4ee02b4e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: include file
description: include file
services:
author: mihart
ms.service: powerbi
ms.topic: include
ms.date: 08/17/2020
ms.author: mihart
ms.custom: include file
---
<Token>**APPLIES TO:** Power BI service for ***consumers*** Power BI service for designers & developers Power BI Desktop Requires Pro or Premium license </Token> | 33.153846 | 241 | 0.716937 | eng_Latn | 0.881878 |
2f866389d690d803e45dcb5652c3f06789d9cfad | 2,138 | md | Markdown | docs/testaus.md | inkeriV/lazy-route | 7149a81215870362247c525804fb9b5d88c68ae3 | [
"MIT"
] | null | null | null | docs/testaus.md | inkeriV/lazy-route | 7149a81215870362247c525804fb9b5d88c68ae3 | [
"MIT"
] | 2 | 2018-08-20T20:33:18.000Z | 2018-08-31T07:52:34.000Z | docs/testaus.md | inkeriV/lazy-route | 7149a81215870362247c525804fb9b5d88c68ae3 | [
"MIT"
] | null | null | null | ### Testausdokumentti
#### Yksikkötestaus
Ohjelman testauksessa on käytetty javan JUnit:ia yksikkötestaukseen ja JaCoCo:a testikattavuuden tarkasteluun. Lopullinen koodikattavuus on 93.10% Suurin osa puuttuvista testeistä koskee luokkan [PerformanceTesting](https://github.com/inkeriV/lazy-route/blob/master/lazy-route/src/main/java/lazyroute/main/PerformanceTesting.java) main metodia. Jätin sen testaamatta, sillä se ei ole olennaista. Metodi tulostaa algoritmien suoritusaikoja.
#### Suorituskykytestaus
Testauskoodi [täällä](https://github.com/inkeriV/lazy-route/blob/master/lazy-route/src/main/java/lazyroute/main/PerformanceTesting.java).
Dijkstralle ja A-Starille molemmille kutsutaan samaa 1000 x 1000 verkkoa, jossa solmujen painot on generoitu satunnaisesti väliltä 1-99. Suorituskykyä voi testata komennolla
```
mvn compile exec:java -Dexec.mainClass=lazyroute.main.PerformanceTesting -Dexec.args="1"
```
Halutut testauskerrat voi antaa argumenttina (esimerkkikäskyssä kutsutaan kerran). Jokaiselle testauskerralle luodaan uusi verkko.
Tiralabran [ohjeiden](https://github.com/TiraLabra/2018_loppu/wiki/Suorituskykytestauksesta) mukaan nykyhetken aika tallennetaan ennen ohjelman kutsumista ja sen jälkeen ja tulostetaan näiden erotus.
Outputtina on tuloste siitä, kuinka kauan kummallakin algoritmilla kesti millisekunteina.
Testasin suorituskykyä kolmeen otteeseen testaavalla metodilla, jolla joka kerralla kumpaakin algoritmia testattiin 10 kertaa. Kuvissa joka suorituskerran kohdalla (1-10) on eri verkko, mutta molemmat algoritmit käyttivät samalla kohtaa samaa verkkoa. A-star on lähes aina nopeampi. Alla tuloksia.
#### 1. kerta
* A-star mediaani: 683.5 ms.
* Dijkstra mediaani: 734.5 ms.
#### 2. kerta
* A-star mediaani: 682 ms.
* Dijkstra mediaani: 727 ms.
#### 3. kerta
* A-star mediaani: 691.5 ms.
* Dijkstra mediaani: 733 ms.
| 46.478261 | 439 | 0.802619 | fin_Latn | 0.99536 |
2f868b2756cc60f7a0bc89c530e231af3b1bf00f | 14 | md | Markdown | README.md | oleksiib/scrum-board | 8fc460ad85f4248b8270badf6c9797d5f10eae63 | [
"Apache-2.0"
] | null | null | null | README.md | oleksiib/scrum-board | 8fc460ad85f4248b8270badf6c9797d5f10eae63 | [
"Apache-2.0"
] | null | null | null | README.md | oleksiib/scrum-board | 8fc460ad85f4248b8270badf6c9797d5f10eae63 | [
"Apache-2.0"
] | null | null | null | # scrum-board
| 7 | 13 | 0.714286 | eng_Latn | 0.477888 |
2f86dc7f8dd9f23b4903c08e5a90fd156a0c5d75 | 2,834 | md | Markdown | windows-driver-docs-pr/network/extending-wireless-connection-properties.md | i35010u/windows-driver-docs.zh-cn | e97bfd9ab066a578d9178313f802653570e21e7d | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-02-04T01:49:58.000Z | 2021-02-04T01:49:58.000Z | windows-driver-docs-pr/network/extending-wireless-connection-properties.md | i35010u/windows-driver-docs.zh-cn | e97bfd9ab066a578d9178313f802653570e21e7d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | windows-driver-docs-pr/network/extending-wireless-connection-properties.md | i35010u/windows-driver-docs.zh-cn | e97bfd9ab066a578d9178313f802653570e21e7d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 扩展无线连接属性
description: 扩展无线连接属性
keywords:
- IHV UI 扩展 DLL WDK 本机802.11，无线连接属性
- 无线连接属性 WDK 本机 802.11 IHV UI 扩展 DLL
ms.date: 04/20/2017
ms.localizationpriority: medium
ms.openlocfilehash: cac6f66132f4630b8437f40a37cfc4d0fe43bb89
ms.sourcegitcommit: 418e6617e2a695c9cb4b37b5b60e264760858acd
ms.translationtype: MT
ms.contentlocale: zh-CN
ms.lasthandoff: 12/07/2020
ms.locfileid: "96788376"
---
# <a name="extending-wireless-connection-properties"></a>扩展无线连接属性
本主题介绍本机 802.11 IHV UI 扩展 DLL 如何扩展通过网络配置用户界面 (UI) 显示的 " **连接** " 选项卡的属性。 在这种情况下，本机 802.11 IHV UI 扩展 DLL 会将属性添加到专用连接设置的 " **连接** " 选项卡中。
有关网络配置 UI 和其他本机802.11 组件的详细信息，请参阅 [本机802.11 软件体系结构](/previous-versions/windows/hardware/wireless/native-802-11-software-architecture)。
在显示 " **连接** " 选项卡之前，操作系统执行以下操作：
1. 通过对 [**IDot11ExtUI：： GetDot11ExtUIProperties**](/previous-versions/windows/hardware/wireless/ff553776(v=vs.85)) 方法的调用，在本机 802.11 IHV UI 扩展 DLL 中查询其连接属性。 操作系统将 **DOT11 \_ EXT \_ UI \_ 连接** 值传递到该方法的 *ExtType* 参数。
如果本机 802.11 IHV UI 扩展 DLL 支持类型为 **DOT11 \_ EXT \_ ui \_ 连接** 的属性，则 DLL 将通过方法的 *ppDot11ExtUIProperty* 参数) 返回 [ (，该参数将实现](/previous-versions/windows/hardware/wireless/ff553746(v=vs.85))连接属性扩展。 有关用于扩展连接属性的 COM 接口的详细信息，请参阅 [本机 802.11 IHV UI 扩展 Com 接口](native-802-11-ihv-ui-extensions-com-interfaces.md)。
**注意** 对于 Windows Vista，本机 802.11 IHV UI 扩展 DLL 不得为连接属性扩展返回多个 [IDOT11EXTUI COM 接口](/previous-versions/windows/hardware/wireless/ff553769(v=vs.85)) 。
2. 如果本机 802.11 IHV UI 扩展 DLL 支持连接属性，则操作系统将通过调用扩展的 [**IDot11ExtUIProperty：： GetDot11ExtUIPropertyFriendlyName**](/previous-versions/windows/hardware/wireless/ff553768(v=vs.85)) 方法来查询属性扩展的友好名称。 操作系统在文本 "启用 *xxx* 连接设置" 中插入友好名称，其中 "*xxx*" 是属性扩展的友好名称。 操作系统在 " **连接** " 选项卡上显示此文本以及一个复选框。
3. 查询扩展，以确定它是否有可显示的自定义 UI 属性。 操作系统通过调用扩展的 [**IDot11ExtUIProperty：:D ot11extuipropertyhasconfigurationui**](/previous-versions/windows/hardware/wireless/ff553756(v=vs.85)) 方法来执行此操作。 如果连接属性扩展支持自定义 UI 属性，则操作系统会在该属性的复选框下方添加一个 " **配置** " 按钮。
如果所选专用连接设置支持配置 UI，而最终用户在 "**连接**" 选项卡中单击 "**配置**" 按钮，操作系统将调用连接属性扩展的 [**IDot11ExtUIProperty：:D isplaydot11extuiproperty**](/previous-versions/windows/hardware/wireless/ff553749(v=vs.85))方法来启动自定义 UI。 操作系统通过方法的 *bstrIHVProfile* 参数传递扩展插件的当前配置文件数据。
配置文件数据的格式为由 < IHV > < /IHV > XML 标记界定的 xml 片段。 这些标记中的 XML 数据特定于 IHV 的实现，对操作系统不透明。 有关本机802.11 配置文件数据格式的详细信息，请参阅 Microsoft Windows SDK 中的文档。
如果通过自定义 UI 更改了配置文件数据，则扩展的 [**IDot11ExtUIProperty：:D isplaydot11extuiproperty**](/previous-versions/windows/hardware/wireless/ff553749(v=vs.85)) 方法必须在返回前执行以下操作：
- 为修改后的配置文件数据分配字符串缓冲区，并通过方法的 *bstrModifiedIHVProfile* 参数返回指向缓冲区的指针。
**注意** 扩展的 [**IDot11ExtUIProperty：:D isplaydot11extuiproperty**](/previous-versions/windows/hardware/wireless/ff553749(v=vs.85)) 方法不能修改 *bstrIHVProfile* 参数所引用的数据。
- 将 *pbIsModified* 参数设置为 **TRUE**。
| 49.719298 | 303 | 0.760056 | yue_Hant | 0.609471 |
2f876db9c9d204131dad0c0c1f19872195d91f8b | 34,992 | md | Markdown | README.md | clfsoft/gnet | fe509e63ad8d42a8dd5bbda094ac0dbcad017ae0 | [
"MIT"
] | 1 | 2020-04-10T06:08:54.000Z | 2020-04-10T06:08:54.000Z | README.md | louhongfei123/gnet | dda5ccf5d80013ad9d88e4787eda9f672f2a71e7 | [
"MIT"
] | null | null | null | README.md | louhongfei123/gnet | dda5ccf5d80013ad9d88e4787eda9f672f2a71e7 | [
"MIT"
] | null | null | null | <p align="center">
<img src="https://raw.githubusercontent.com/panjf2000/logos/master/gnet/logo.png" alt="gnet">
<br />
<a title="Build Status" target="_blank" href="https://travis-ci.com/panjf2000/gnet"><img src="https://img.shields.io/travis/com/panjf2000/gnet?style=flat-square&logo=travis-ci&logoColor=white"></a>
<a title="Codecov" target="_blank" href="https://codecov.io/gh/panjf2000/gnet"><img src="https://img.shields.io/codecov/c/github/panjf2000/gnet?style=flat-square&logo=codecov"></a>
<a title="Supported Platforms" target="_blank" href="https://github.com/panjf2000/gnet"><img src="https://img.shields.io/badge/platform-Linux%20%7C%20macOS%20%7C%20Windows-549688?style=flat-square&logo=dlna"></a>
<a title="Require Go Version" target="_blank" href="https://github.com/panjf2000/gnet"><img src="https://img.shields.io/badge/go-%3E%3D1.9-30dff3?style=flat-square&logo=go"></a>
<a title="Release" target="_blank" href="https://github.com/panjf2000/gnet/releases"><img src="https://img.shields.io/github/v/release/panjf2000/gnet.svg?color=161823&style=flat-square&logo=smartthings"></a>
<br/>
<a title="Go Report Card" target="_blank" href="https://goreportcard.com/report/github.com/panjf2000/gnet"><img src="https://goreportcard.com/badge/github.com/panjf2000/gnet?style=flat-square"></a>
<a title="Doc for gnet" target="_blank" href="https://pkg.go.dev/github.com/panjf2000/gnet?tab=doc"><img src="https://img.shields.io/badge/go.dev-doc-007d9c?style=flat-square&logo=read-the-docs"></a>
<a title="gnet on Sourcegraph" target="_blank" href="https://sourcegraph.com/github.com/panjf2000/gnet?badge"><img src="https://sourcegraph.com/github.com/panjf2000/gnet/-/badge.svg?style=flat-square"></a>
<a title="Mentioned in Awesome Go" target="_blank" href="https://github.com/avelino/awesome-go#networking"><img src="https://awesome.re/mentioned-badge-flat.svg"></a>
</p>
English | [🇨🇳中文](README_ZH.md)
# 📖 Introduction
`gnet` is an event-driven networking framework that is fast and lightweight. It makes direct [epoll](https://en.wikipedia.org/wiki/Epoll) and [kqueue](https://en.wikipedia.org/wiki/Kqueue) syscalls rather than using the standard Go [net](https://golang.org/pkg/net/) package, and works in a similar manner as [netty](https://github.com/netty/netty) and [libuv](https://github.com/libuv/libuv).
`gnet` is not designed to displace the standard Go [net](https://golang.org/pkg/net/) package, but to create a networking server framework for Go that performs on par with [Redis](http://redis.io) and [Haproxy](http://www.haproxy.org) for networking packets handling.
`gnet` sells itself as a high-performance, lightweight, non-blocking, event-driven networking framework written in pure Go which works on transport layer with TCP/UDP protocols and Unix Domain Socket , so it allows developers to implement their own protocols(HTTP, RPC, WebSocket, Redis, etc.) of application layer upon `gnet` for building diversified network applications, for instance, you get an HTTP Server or Web Framework if you implement HTTP protocol upon `gnet` while you have a Redis Server done with the implementation of Redis protocol upon `gnet` and so on.
**`gnet` derives from the project: `evio` while having a much higher performance and more features.**
# 🚀 Features
- [x] [High-performance](#-performance) event-loop under networking model of multiple threads/goroutines
- [x] Built-in goroutine pool powered by the library [ants](https://github.com/panjf2000/ants)
- [x] Built-in memory pool with bytes powered by the library [bytebufferpool](https://github.com/valyala/bytebufferpool)
- [x] Concise APIs
- [x] Efficient memory usage: Ring-Buffer
- [x] Supporting multiple protocols/IPC mechanism: `TCP,` `UDP` and `Unix Domain Socket`
- [x] Supporting multiple load-balancing algorithms: `Round-Robin`, `Source Addr Hash` and `Least-Connections`
- [x] Supporting two event-driven mechanisms: `epoll` on Linux and `kqueue` on FreeBSD
- [x] Supporting asynchronous write operation
- [x] Flexible ticker event
- [x] SO_REUSEPORT socket option
- [x] Built-in multiple codecs to encode/decode network frames into/from TCP stream: LineBasedFrameCodec, DelimiterBasedFrameCodec, FixedLengthFrameCodec and LengthFieldBasedFrameCodec, referencing [netty codec](https://netty.io/4.1/api/io/netty/handler/codec/package-summary.html), also supporting customized codecs
- [x] Supporting Windows platform with ~~event-driven mechanism of IOCP~~ Go stdlib: net
- [ ] Implementation of `gnet` Client
# 💡 Key Designs
## Networking Model of Multiple Threads/Goroutines
### Multiple Reactors
`gnet` redesigns and implements a new built-in networking model of multiple threads/goroutines: 『multiple reactors』 which is also the default networking model of multiple threads in `netty`, Here's the schematic diagram:
<p align="center">
<img alt="multi_reactor" src="https://raw.githubusercontent.com/panjf2000/illustrations/master/go/multi-reactors.png">
</p>
and it works as the following sequence diagram:
<p align="center">
<img alt="reactor" src="https://raw.githubusercontent.com/panjf2000/illustrations/master/go/multi-reactors-sequence-diagram.png">
</p>
### Multiple Reactors + Goroutine-Pool
You may ask me a question: what if my business logic in `EventHandler.React` contains some blocking code which leads to blocking in event-loop of `gnet`, what is the solution for this kind of situation？
As you know, there is a most important tenet when writing code under `gnet`: you should never block the event-loop goroutine in the `EventHandler.React`, which is also the most important tenet in `netty`, otherwise, it will result in a low throughput in your `gnet` server.
And the solution to that could be found in the subsequent networking model of multiple threads/goroutines in `gnet`: 『multiple reactors with thread/goroutine pool』which pulls you out from the blocking mire, it will construct a worker-pool with fixed capacity and put those blocking jobs in `EventHandler.React` into the worker-pool to make the event-loop goroutines non-blocking.
The networking model:『multiple reactors with thread/goroutine pool』dissolves the blocking jobs by introducing a goroutine pool, as shown below:
<p align="center">
<img alt="multi_reactor_thread_pool" src="https://raw.githubusercontent.com/panjf2000/illustrations/master/go/multi-reactors%2Bthread-pool.png">
</p>
and it works as the following sequence diagram:
<p align="center">
<img alt="multi-reactors" src="https://raw.githubusercontent.com/panjf2000/illustrations/master/go/multi-reactors%2Bthread-pool-sequence-diagram.png">
</p>
`gnet` implements the networking model:『multiple reactors with thread/goroutine pool』by the aid of a high-performance goroutine pool called [ants](https://github.com/panjf2000/ants) that allows you to manage and recycle a massive number of goroutines in your concurrent programs, the full features and usages in `ants` are documented [here](https://pkg.go.dev/github.com/panjf2000/ants/v2?tab=doc).
`gnet` integrates `ants` and provides the `pool.goroutine.Default()` method that you can call to instantiate a `ants` pool where you are able to put your blocking code logic and call the function `gnet.Conn.AsyncWrite([]byte)` to send out data asynchronously after you finish the blocking process and get the output data, which makes the goroutine of event-loop non-blocking.
The details about integrating `gnet` with `ants` are shown [here](#echo-server-with-blocking-logic).
## Auto-scaling Ring Buffer
There are two ring-buffers inside `gnet`: inbound buffer and outbound buffer to buffer and manage inbound/outbound network data.
The purpose of implementing inbound and outbound ring-buffers in `gnet` is to transfer the logic of buffering and managing network data based on application protocol upon TCP stream from business server to framework and unify the network data buffer, which minimizes the complexity of business code so that developers are able to concentrate on business logic instead of the underlying implementation.
<p align="center">
<img src="https://raw.githubusercontent.com/panjf2000/illustrations/master/go/ring-buffer.gif">
</p>
# 🎉 Getting Started
## Prerequisites
`gnet` requires Go 1.9 or later.
## Installation
```powershell
go get -u github.com/panjf2000/gnet
```
`gnet` is available as a Go module, with [Go 1.11 Modules](https://github.com/golang/go/wiki/Modules) support (Go 1.11+), just simply `import "github.com/panjf2000/gnet"` in your source code and `go [build|run|test]` will download the necessary dependencies automatically.
## Usage Examples
**The detailed documentation is located in here: [docs of gnet](https://pkg.go.dev/github.com/panjf2000/gnet?tab=doc), but let's pass through the brief instructions first.**
It is easy to create a network server with `gnet`. All you have to do is just to make your implementation of `gnet.EventHandler` interface and register your event-handler functions to it, then pass it to the `gnet.Serve` function along with the binding address(es). Each connection is represented as a `gnet.Conn` interface that is passed to various events to differentiate the clients. At any point you can close a connection or shutdown the server by return a `Close` or `Shutdown` action from an event function.
The simplest example to get you started playing with `gnet` would be the echo server. So here you are, a simplest echo server upon `gnet` that is listening on port 9000:
### Echo server without blocking logic
<details>
<summary> Old version(<=v1.0.0-rc.4) </summary>
```go
package main
import (
"log"
"github.com/panjf2000/gnet"
)
type echoServer struct {
*gnet.EventServer
}
func (es *echoServer) React(c gnet.Conn) (out []byte, action gnet.Action) {
out = c.Read()
c.ResetBuffer()
return
}
func main() {
echo := new(echoServer)
log.Fatal(gnet.Serve(echo, "tcp://:9000", gnet.WithMulticore(true)))
}
```
</details>
```go
package main
import (
"log"
"github.com/panjf2000/gnet"
)
type echoServer struct {
*gnet.EventServer
}
func (es *echoServer) React(frame []byte, c gnet.Conn) (out []byte, action gnet.Action) {
out = frame
return
}
func main() {
echo := new(echoServer)
log.Fatal(gnet.Serve(echo, "tcp://:9000", gnet.WithMulticore(true)))
}
```
As you can see, this example of echo server only sets up the `EventHandler.React` function where you commonly write your main business code and it will be called once the server receives input data from a client. What you should know is that the input parameter: `frame` is a complete packet which has been decoded by the codec, as a general rule, you should implement the `gnet` [codec interface](https://github.com/panjf2000/gnet/blob/master/codec.go#L18-L24) as the business codec to packet and unpacket TCP stream, but if you don't, your `gnet` server is going to work with the [default codec](https://github.com/panjf2000/gnet/blob/master/codec.go#L53-L63) under the acquiescence, which means all data inculding latest data and previous data in buffer will be stored in the input parameter: `frame` when `EventHandler.React` is being triggered. The output data will be then encoded and sent back to that client by assigning the `out` variable and returning it after your business code finish processing data(in this case, it just echo the data back).
### Echo server with blocking logic
<details>
<summary> Old version(<=v1.0.0-rc.4) </summary>
```go
package main
import (
"log"
"time"
"github.com/panjf2000/gnet"
"github.com/panjf2000/gnet/pool/goroutine"
)
type echoServer struct {
*gnet.EventServer
pool *goroutine.Pool
}
func (es *echoServer) React(c gnet.Conn) (out []byte, action gnet.Action) {
data := append([]byte{}, c.Read()...)
c.ResetBuffer()
// Use ants pool to unblock the event-loop.
_ = es.pool.Submit(func() {
time.Sleep(1 * time.Second)
c.AsyncWrite(data)
})
return
}
func main() {
p := goroutine.Default()
defer p.Release()
echo := &echoServer{pool: p}
log.Fatal(gnet.Serve(echo, "tcp://:9000", gnet.WithMulticore(true)))
}
```
</details>
```go
package main
import (
"log"
"time"
"github.com/panjf2000/gnet"
"github.com/panjf2000/gnet/pool/goroutine"
)
type echoServer struct {
*gnet.EventServer
pool *goroutine.Pool
}
func (es *echoServer) React(frame []byte, c gnet.Conn) (out []byte, action gnet.Action) {
data := append([]byte{}, frame...)
// Use ants pool to unblock the event-loop.
_ = es.pool.Submit(func() {
time.Sleep(1 * time.Second)
c.AsyncWrite(data)
})
return
}
func main() {
p := goroutine.Default()
defer p.Release()
echo := &echoServer{pool: p}
log.Fatal(gnet.Serve(echo, "tcp://:9000", gnet.WithMulticore(true)))
}
```
Like I said in the 『Multiple Reactors + Goroutine-Pool』section, if there are blocking code in your business logic, then you ought to turn them into non-blocking code in any way, for instance you can wrap them into a goroutine, but it will result in a massive amount of goroutines if massive traffic is passing through your server so I would suggest you utilize a goroutine pool like [ants](https://github.com/panjf2000/ants) to manage those goroutines and reduce the cost of system resources.
**All gnet examples:**
<details>
<summary> TCP Echo Server </summary>
```go
package main
import (
"flag"
"fmt"
"log"
"github.com/panjf2000/gnet"
)
type echoServer struct {
*gnet.EventServer
}
func (es *echoServer) OnInitComplete(srv gnet.Server) (action gnet.Action) {
log.Printf("Echo server is listening on %s (multi-cores: %t, loops: %d)\n",
srv.Addr.String(), srv.Multicore, srv.NumEventLoop)
return
}
func (es *echoServer) React(frame []byte, c gnet.Conn) (out []byte, action gnet.Action) {
// Echo synchronously.
out = frame
return
/*
// Echo asynchronously.
data := append([]byte{}, frame...)
go func() {
time.Sleep(time.Second)
c.AsyncWrite(data)
}()
return
*/
}
func main() {
var port int
var multicore bool
// Example command: go run echo.go --port 9000 --multicore=true
flag.IntVar(&port, "port", 9000, "--port 9000")
flag.BoolVar(&multicore, "multicore", false, "--multicore true")
flag.Parse()
echo := new(echoServer)
log.Fatal(gnet.Serve(echo, fmt.Sprintf("tcp://:%d", port), gnet.WithMulticore(multicore)))
}
```
</details>
<details>
<summary> UDP Echo Server </summary>
```go
package main
import (
"flag"
"fmt"
"log"
"github.com/panjf2000/gnet"
)
type echoServer struct {
*gnet.EventServer
}
func (es *echoServer) OnInitComplete(srv gnet.Server) (action gnet.Action) {
log.Printf("UDP Echo server is listening on %s (multi-cores: %t, loops: %d)\n",
srv.Addr.String(), srv.Multicore, srv.NumEventLoop)
return
}
func (es *echoServer) React(frame []byte, c gnet.Conn) (out []byte, action gnet.Action) {
// Echo synchronously.
out = frame
return
/*
// Echo asynchronously.
data := append([]byte{}, frame...)
go func() {
time.Sleep(time.Second)
c.SendTo(data)
}()
return
*/
}
func main() {
var port int
var multicore, reuseport bool
// Example command: go run echo.go --port 9000 --multicore=true --reuseport=true
flag.IntVar(&port, "port", 9000, "--port 9000")
flag.BoolVar(&multicore, "multicore", false, "--multicore true")
flag.BoolVar(&reuseport, "reuseport", false, "--reuseport true")
flag.Parse()
echo := new(echoServer)
log.Fatal(gnet.Serve(echo, fmt.Sprintf("udp://:%d", port), gnet.WithMulticore(multicore), gnet.WithReusePort(reuseport)))
}
```
</details>
<details>
<summary> UDS Echo Server </summary>
```go
package main
import (
"flag"
"fmt"
"log"
"github.com/panjf2000/gnet"
)
type echoServer struct {
*gnet.EventServer
}
func (es *echoServer) OnInitComplete(srv gnet.Server) (action gnet.Action) {
log.Printf("Echo server is listening on %s (multi-cores: %t, loops: %d)\n",
srv.Addr.String(), srv.Multicore, srv.NumEventLoop)
return
}
func (es *echoServer) React(frame []byte, c gnet.Conn) (out []byte, action gnet.Action) {
// Echo synchronously.
out = frame
return
/*
// Echo asynchronously.
data := append([]byte{}, frame...)
go func() {
time.Sleep(time.Second)
c.AsyncWrite(data)
}()
return
*/
}
func main() {
var addr string
var multicore bool
// Example command: go run echo.go --sock echo.sock --multicore=true
flag.StringVar(&addr, "sock", "echo.sock", "--port 9000")
flag.BoolVar(&multicore, "multicore", false, "--multicore true")
flag.Parse()
echo := new(echoServer)
log.Fatal(gnet.Serve(echo, fmt.Sprintf("unix://%s", addr), gnet.WithMulticore(multicore)))
}
```
</details>
<details>
<summary> HTTP Server </summary>
```go
package main
import (
"flag"
"fmt"
"log"
"strconv"
"strings"
"time"
"unsafe"
"github.com/panjf2000/gnet"
)
var res string
type request struct {
proto, method string
path, query string
head, body string
remoteAddr string
}
type httpServer struct {
*gnet.EventServer
}
var errMsg = "Internal Server Error"
var errMsgBytes = []byte(errMsg)
type httpCodec struct {
req request
}
func (hc *httpCodec) Encode(c gnet.Conn, buf []byte) (out []byte, err error) {
if c.Context() == nil {
return buf, nil
}
return appendResp(out, "500 Error", "", errMsg+"\n"), nil
}
func (hc *httpCodec) Decode(c gnet.Conn) (out []byte, err error) {
buf := c.Read()
c.ResetBuffer()
// process the pipeline
var leftover []byte
pipeline:
leftover, err = parseReq(buf, &hc.req)
// bad thing happened
if err != nil {
c.SetContext(err)
return nil, err
} else if len(leftover) == len(buf) {
// request not ready, yet
return
}
out = appendHandle(out, res)
buf = leftover
goto pipeline
}
func (hs *httpServer) OnInitComplete(srv gnet.Server) (action gnet.Action) {
log.Printf("HTTP server is listening on %s (multi-cores: %t, loops: %d)\n",
srv.Addr.String(), srv.Multicore, srv.NumEventLoop)
return
}
func (hs *httpServer) React(frame []byte, c gnet.Conn) (out []byte, action gnet.Action) {
if c.Context() != nil {
// bad thing happened
out = errMsgBytes
action = gnet.Close
return
}
// handle the request
out = frame
return
}
func main() {
var port int
var multicore bool
// Example command: go run http.go --port 8080 --multicore=true
flag.IntVar(&port, "port", 8080, "server port")
flag.BoolVar(&multicore, "multicore", true, "multicore")
flag.Parse()
res = "Hello World!\r\n"
http := new(httpServer)
hc := new(httpCodec)
// Start serving!
log.Fatal(gnet.Serve(http, fmt.Sprintf("tcp://:%d", port), gnet.WithMulticore(multicore), gnet.WithCodec(hc)))
}
// appendHandle handles the incoming request and appends the response to
// the provided bytes, which is then returned to the caller.
func appendHandle(b []byte, res string) []byte {
return appendResp(b, "200 OK", "", res)
}
// appendResp will append a valid http response to the provide bytes.
// The status param should be the code plus text such as "200 OK".
// The head parameter should be a series of lines ending with "\r\n" or empty.
func appendResp(b []byte, status, head, body string) []byte {
b = append(b, "HTTP/1.1"...)
b = append(b, ' ')
b = append(b, status...)
b = append(b, '\r', '\n')
b = append(b, "Server: gnet\r\n"...)
b = append(b, "Date: "...)
b = time.Now().AppendFormat(b, "Mon, 02 Jan 2006 15:04:05 GMT")
b = append(b, '\r', '\n')
if len(body) > 0 {
b = append(b, "Content-Length: "...)
b = strconv.AppendInt(b, int64(len(body)), 10)
b = append(b, '\r', '\n')
}
b = append(b, head...)
b = append(b, '\r', '\n')
if len(body) > 0 {
b = append(b, body...)
}
return b
}
func b2s(b []byte) string {
return *(*string)(unsafe.Pointer(&b))
}
// parseReq is a very simple http request parser. This operation
// waits for the entire payload to be buffered before returning a
// valid request.
func parseReq(data []byte, req *request) (leftover []byte, err error) {
sdata := b2s(data)
var i, s int
var head string
var clen int
var q = -1
// method, path, proto line
for ; i < len(sdata); i++ {
if sdata[i] == ' ' {
req.method = sdata[s:i]
for i, s = i+1, i+1; i < len(sdata); i++ {
if sdata[i] == '?' && q == -1 {
q = i - s
} else if sdata[i] == ' ' {
if q != -1 {
req.path = sdata[s:q]
req.query = req.path[q+1 : i]
} else {
req.path = sdata[s:i]
}
for i, s = i+1, i+1; i < len(sdata); i++ {
if sdata[i] == '\n' && sdata[i-1] == '\r' {
req.proto = sdata[s:i]
i, s = i+1, i+1
break
}
}
break
}
}
break
}
}
if req.proto == "" {
return data, fmt.Errorf("malformed request")
}
head = sdata[:s]
for ; i < len(sdata); i++ {
if i > 1 && sdata[i] == '\n' && sdata[i-1] == '\r' {
line := sdata[s : i-1]
s = i + 1
if line == "" {
req.head = sdata[len(head)+2 : i+1]
i++
if clen > 0 {
if len(sdata[i:]) < clen {
break
}
req.body = sdata[i : i+clen]
i += clen
}
return data[i:], nil
}
if strings.HasPrefix(line, "Content-Length:") {
n, err := strconv.ParseInt(strings.TrimSpace(line[len("Content-Length:"):]), 10, 64)
if err == nil {
clen = int(n)
}
}
}
}
// not enough data
return data, nil
}
```
</details>
<details>
<summary> Push Server </summary>
```go
package main
import (
"flag"
"fmt"
"log"
"sync"
"time"
"github.com/panjf2000/gnet"
)
type pushServer struct {
*gnet.EventServer
tick time.Duration
connectedSockets sync.Map
}
func (ps *pushServer) OnInitComplete(srv gnet.Server) (action gnet.Action) {
log.Printf("Push server is listening on %s (multi-cores: %t, loops: %d), "+
"pushing data every %s ...\n", srv.Addr.String(), srv.Multicore, srv.NumEventLoop, ps.tick.String())
return
}
func (ps *pushServer) OnOpened(c gnet.Conn) (out []byte, action gnet.Action) {
log.Printf("Socket with addr: %s has been opened...\n", c.RemoteAddr().String())
ps.connectedSockets.Store(c.RemoteAddr().String(), c)
return
}
func (ps *pushServer) OnClosed(c gnet.Conn, err error) (action gnet.Action) {
log.Printf("Socket with addr: %s is closing...\n", c.RemoteAddr().String())
ps.connectedSockets.Delete(c.RemoteAddr().String())
return
}
func (ps *pushServer) Tick() (delay time.Duration, action gnet.Action) {
log.Println("It's time to push data to clients!!!")
ps.connectedSockets.Range(func(key, value interface{}) bool {
addr := key.(string)
c := value.(gnet.Conn)
c.AsyncWrite([]byte(fmt.Sprintf("heart beating to %s\n", addr)))
return true
})
delay = ps.tick
return
}
func (ps *pushServer) React(frame []byte, c gnet.Conn) (out []byte, action gnet.Action) {
out = frame
return
}
func main() {
var port int
var multicore bool
var interval time.Duration
var ticker bool
// Example command: go run push.go --port 9000 --tick 1s --multicore=true
flag.IntVar(&port, "port", 9000, "server port")
flag.BoolVar(&multicore, "multicore", true, "multicore")
flag.DurationVar(&interval, "tick", 0, "pushing tick")
flag.Parse()
if interval > 0 {
ticker = true
}
push := &pushServer{tick: interval}
log.Fatal(gnet.Serve(push, fmt.Sprintf("tcp://:%d", port), gnet.WithMulticore(multicore), gnet.WithTicker(ticker)))
}
```
</details>
<details>
<summary> Codec Client/Server </summary>
**Client:**
```go
// Reference https://github.com/smallnest/goframe/blob/master/_examples/goclient/client.go
package main
import (
"encoding/binary"
"fmt"
"net"
"github.com/smallnest/goframe"
)
func main() {
conn, err := net.Dial("tcp", "127.0.0.1:9000")
if err != nil {
panic(err)
}
defer conn.Close()
encoderConfig := goframe.EncoderConfig{
ByteOrder: binary.BigEndian,
LengthFieldLength: 4,
LengthAdjustment: 0,
LengthIncludesLengthFieldLength: false,
}
decoderConfig := goframe.DecoderConfig{
ByteOrder: binary.BigEndian,
LengthFieldOffset: 0,
LengthFieldLength: 4,
LengthAdjustment: 0,
InitialBytesToStrip: 4,
}
fc := goframe.NewLengthFieldBasedFrameConn(encoderConfig, decoderConfig, conn)
err = fc.WriteFrame([]byte("hello"))
if err != nil {
panic(err)
}
err = fc.WriteFrame([]byte("world"))
if err != nil {
panic(err)
}
buf, err := fc.ReadFrame()
if err != nil {
panic(err)
}
fmt.Println("received: ", string(buf))
buf, err = fc.ReadFrame()
if err != nil {
panic(err)
}
fmt.Println("received: ", string(buf))
}
```
**Server:**
```go
package main
import (
"encoding/binary"
"flag"
"fmt"
"log"
"time"
"github.com/panjf2000/gnet"
"github.com/panjf2000/gnet/pool/goroutine"
)
type codecServer struct {
*gnet.EventServer
addr string
multicore bool
async bool
codec gnet.ICodec
workerPool *goroutine.Pool
}
func (cs *codecServer) OnInitComplete(srv gnet.Server) (action gnet.Action) {
log.Printf("Test codec server is listening on %s (multi-cores: %t, loops: %d)\n",
srv.Addr.String(), srv.Multicore, srv.NumEventLoop)
return
}
func (cs *codecServer) React(frame []byte, c gnet.Conn) (out []byte, action gnet.Action) {
if cs.async {
data := append([]byte{}, frame...)
_ = cs.workerPool.Submit(func() {
c.AsyncWrite(data)
})
return
}
out = frame
return
}
func testCodecServe(addr string, multicore, async bool, codec gnet.ICodec) {
var err error
if codec == nil {
encoderConfig := gnet.EncoderConfig{
ByteOrder: binary.BigEndian,
LengthFieldLength: 4,
LengthAdjustment: 0,
LengthIncludesLengthFieldLength: false,
}
decoderConfig := gnet.DecoderConfig{
ByteOrder: binary.BigEndian,
LengthFieldOffset: 0,
LengthFieldLength: 4,
LengthAdjustment: 0,
InitialBytesToStrip: 4,
}
codec = gnet.NewLengthFieldBasedFrameCodec(encoderConfig, decoderConfig)
}
cs := &codecServer{addr: addr, multicore: multicore, async: async, codec: codec, workerPool: goroutine.Default()}
err = gnet.Serve(cs, addr, gnet.WithMulticore(multicore), gnet.WithTCPKeepAlive(time.Minute*5), gnet.WithCodec(codec))
if err != nil {
panic(err)
}
}
func main() {
var port int
var multicore bool
// Example command: go run server.go --port 9000 --multicore=true
flag.IntVar(&port, "port", 9000, "server port")
flag.BoolVar(&multicore, "multicore", true, "multicore")
flag.Parse()
addr := fmt.Sprintf("tcp://:%d", port)
testCodecServe(addr, multicore, false, nil)
}
```
</details>
**For more details, check out here: [examples of gnet](https://github.com/panjf2000/gnet/tree/master/examples).**
## I/O Events
Current supported I/O events in `gnet`:
- `EventHandler.OnInitComplete` fires when the server has been initialized and ready to accept new connections.
- `EventHandler.OnOpened` fires once a connection has been opened.
- `EventHandler.OnClosed` fires after a connection has been closed.
- `EventHandler.React` fires when the server receives inbound data from a socket/connection. (usually it is where you write the code of business logic)
- `EventHandler.Tick` fires right after the server starts and then fires every specified interval.
- `EventHandler.PreWrite` fires just before any data has been written to client.
## Ticker
The `EventHandler.Tick` event fires ticks at a specified interval.
The first tick fires right after the gnet server starts up and if you intend to set up a ticker event, don't forget to pass an option: `gnet.WithTicker(true)` to `gnet.Serve`.
```go
events.Tick = func() (delay time.Duration, action Action){
log.Printf("tick")
delay = time.Second
return
}
```
## UDP
`gnet` supports UDP protocol so the `gnet.Serve` method can bind to UDP addresses.
- All incoming and outgoing packets will not be buffered but read and sent directly.
- The `EventHandler.OnOpened` and `EventHandler.OnClosed` events are not available for UDP sockets, only the `React` event.
- The UDP equivalents of `AsyncWrite([]byte)` in TCP is `SendTo([]byte)`.
## Unix Domain Socket
`gnet` also supports UDS(Unix Domain Socket), just pass the UDS addresses like "unix://xxx" to the `gnet.Serve` method and you could play with it.
It is nothing different from making use of TCP when doing stuff with UDS, so the `gnet` UDS servers are able to leverage all event functions which are available under TCP protocol.
## Multi-threads
The `gnet.WithMulticore(true)` indicates whether the server will be effectively created with multi-cores, if so, then you must take care of synchronizing memory between all event callbacks, otherwise, it will run the server with a single thread. The number of threads in the server will be automatically assigned to the value of `runtime.NumCPU()`.
## Load Balancing
`gnet` currently supports three load balancing algorithms: `Round-Robin`, `Source Addr Hash` and `Least-Connections`, you are able to decide which algorithm to use by passing the functional option `LB` (RoundRobin/LeastConnections/SourceAddrHash) to `gnet.Serve`.
If the load balancing algorithm is not specified explicitly, `gnet` will use `Round-Robin` by default.
## SO_REUSEPORT
`gnet` server is able to utilize the [SO_REUSEPORT](https://lwn.net/Articles/542629/) option which allows multiple sockets on the same host to bind to the same port and the OS kernel takes care of the load balancing for you, it wakes one socket per `connect` event coming to resolved the `thundering herd`.
By default, `gnet` is not going to be haunted by the `thundering herd` under its networking model:『multiple reactors』which gets only **one** main reactor to listen on "address:port" and accept new sockets. So this `SO_REUSEPORT` option is trivial in `gnet` but note that it will fall back to the old networking model of `evio` when you enable the `SO_REUSEPORT` option.
Just use functional options to set up `SO_REUSEPORT` and you can enjoy this feature:
```go
gnet.Serve(events, "tcp://:9000", gnet.WithMulticore(true), gnet.WithReusePort(true)))
```
## Multiple built-in codecs for TCP stream
There are multiple built-in codecs in `gnet` which allow you to encode/decode frames into/from TCP stream.
So far `gnet` has four kinds of built-in codecs: LineBasedFrameCodec, DelimiterBasedFrameCodec, FixedLengthFrameCodec and LengthFieldBasedFrameCodec, which generally meets most scenarios, but still `gnet` allows users to customize their own codecs in their `gnet` servers by implementing the interface [gnet.ICodec](https://github.com/panjf2000/gnet/blob/master/codec.go#L17) and replacing the default codec in `gnet` with customized codec via functional options.
Here is an [example](https://github.com/panjf2000/gnet/blob/master/examples/codec/server/server.go) with codec, showing you how to leverage codec to encode/decode network frames into/from TCP stream.
# 📊 Performance
## Benchmarks on TechEmpower
```powershell
# Hardware
CPU: 28 HT Cores Intel(R) Xeon(R) Gold 5120 CPU @ 2.20GHz
Mem: 32GB RAM
OS : Ubuntu 18.04.3 4.15.0-88-generic #88-Ubuntu
Net: Switched 10-gigabit ethernet
Go : go1.14.x linux/amd64
```
This is the top 50 on the framework ranking of all programming languages consists of a total of 382 frameworks from all over the world.
This is the full framework ranking of Golang.
To see the full ranking list, visit [Full ranking list of Plaintext](https://www.techempower.com/benchmarks/#section=test&runid=c7152e8f-5b33-4ae7-9e89-630af44bc8de&hw=ph&test=plaintext).
## Contrasts to the similar networking libraries
## On Linux (epoll)
### Test Environment
```powershell
# Machine information
OS : Ubuntu 18.04/x86_64
CPU : 8 Virtual CPUs
Memory : 16.0 GiB
# Go version and configurations
Go Version : go1.12.9 linux/amd64
GOMAXPROCS=8
```
#### Echo Server
#### HTTP Server
## On FreeBSD (kqueue)
### Test Environment
```powershell
# Machine information
OS : macOS Mojave 10.14.6/x86_64
CPU : 4 CPUs
Memory : 8.0 GiB
# Go version and configurations
Go Version : go version go1.12.9 darwin/amd64
GOMAXPROCS=4
```
#### Echo Server
#### HTTP Server
# 📄 License
Source code in `gnet` is available under the MIT [License](/LICENSE).
# 👏 Contributors
Please read our [Contributing Guidelines](CONTRIBUTING.md) before opening a PR and thank you to all the developers who already made contributions to `gnet`!
[](https://github.com/panjf2000/gnet/graphs/contributors)
# 🙏 Acknowledgments
- [evio](https://github.com/tidwall/evio)
- [netty](https://github.com/netty/netty)
- [ants](https://github.com/panjf2000/ants)
- [bytebufferpool](https://github.com/valyala/bytebufferpool)
- [goframe](https://github.com/smallnest/goframe)
# 📚 Relevant Articles
- [A Million WebSockets and Go](https://www.freecodecamp.org/news/million-websockets-and-go-cc58418460bb/)
- [Going Infinite, handling 1M websockets connections in Go](https://speakerdeck.com/eranyanay/going-infinite-handling-1m-websockets-connections-in-go)
- [Go netpoll I/O 多路复用构建原生网络模型之源码深度解析](https://taohuawu.club/go-netpoll-io-multiplexing-reactor)
- [gnet: 一个轻量级且高性能的 Golang 网络库](https://taohuawu.club/go-event-loop-networking-library-gnet)
## JetBrains OS licenses
`gnet` had been being developed with `GoLand` IDE under the **free JetBrains Open Source license(s)** granted by JetBrains s.r.o., hence I would like to express my thanks here.
<a href="https://www.jetbrains.com/?from=gnet" target="_blank"><img src="https://raw.githubusercontent.com/panjf2000/illustrations/master/jetbrains/jetbrains-variant-4.png" width="250" align="middle"/></a>
# 💰 Backers
Support us with a monthly donation and help us continue our activities.
<a href="https://opencollective.com/gnet#backers" target="_blank"><img src="https://opencollective.com/gnet/backers.svg"></a>
# 💎 Sponsors
Become a bronze sponsor with a monthly donation of $10 and get your logo on our README on Github.
<a href="https://opencollective.com/gnet#sponsors" target="_blank"><img src="https://opencollective.com/gnet/sponsors.svg"></a>
# ☕️ Buy me a coffee
<img src="https://raw.githubusercontent.com/panjf2000/illustrations/master/payments/WeChatPay.JPG" width="250" align="middle"/>
<img src="https://raw.githubusercontent.com/panjf2000/illustrations/master/payments/AliPay.JPG" width="250" align="middle"/>
<a href="https://www.paypal.me/R136a1X" target="_blank"><img src="https://raw.githubusercontent.com/panjf2000/illustrations/master/payments/PayPal.JPG" width="250" align="middle"/></a> | 33.743491 | 1,055 | 0.715192 | eng_Latn | 0.764409 |
2f88770e2aa2443d239d255a4257a2d044e5b96e | 4,413 | md | Markdown | sources/news/20190926 MG Motor Announces Developer Program and Grant in India.md | singledo/TranslateProject | 47c47e8fde3e975fa9cb399a290a7bfae81f378c | [
"Apache-2.0"
] | null | null | null | sources/news/20190926 MG Motor Announces Developer Program and Grant in India.md | singledo/TranslateProject | 47c47e8fde3e975fa9cb399a290a7bfae81f378c | [
"Apache-2.0"
] | null | null | null | sources/news/20190926 MG Motor Announces Developer Program and Grant in India.md | singledo/TranslateProject | 47c47e8fde3e975fa9cb399a290a7bfae81f378c | [
"Apache-2.0"
] | null | null | null | [#]: collector: (lujun9972)
[#]: translator: ( )
[#]: reviewer: ( )
[#]: publisher: ( )
[#]: url: ( )
[#]: subject: (MG Motor Announces Developer Program and Grant in India)
[#]: via: (https://opensourceforu.com/2019/09/mg-motor-announces-developer-program-and-grant-in-india/)
[#]: author: (Mukul Yudhveer Singh https://opensourceforu.com/author/mukul-kumar/)
MG Motor Announces Developer Program and Grant in India
======
[![][1]][2]
* _**Launched in partnership with Adobe, Cognizant, SAP, Airtel, TomTom and Unlimit**_
* _**Initiative provides developers to build innovative mobility applications and experiences**_
![][3]MG Motor India has today announced the introduction of its MG Developer Program and Grant. Launched in collaboration with leading technology companies such as SAP, Cognizant, Adobe, Airtel, TomTom and Unlimit, the initiative is aimed at incentivizing Indian innovators and developers to build futuristic mobility applications and experiences. The program also brings in TiE Delhi NCR as the ecosystem partner.
Rajeev Chaba, president & MD, MG Motor India said, “The automobile industry is currently witnessing sweeping transformations in the space of connected, electric and shared mobility. MG aims to take this revolution forward with its focus on attaining technological leadership in the automotive industry. We have partnered with leading tech giants to enable start-ups to build innovative applications that would enable unique experiences for customers across the entire automotive ecosystem. More partners are likely to join the program in due course.”
The company is encouraging developers to send in their ideas to the MG India Team. During the program, selected ideas will get access to resources from the likes of Airtel, SAP, Adobe, Unlimit and Cognizant.
**Grants ranging up to Rs 25 lakhs (2.5 million) for start-ups and innovators**
As part of the MG Developer Program & Grant, MG Motor India will provide innovators with an unparalleled opportunity to secure mentorship and funding from industry leaders. Shortlisted ideas will receive specialized, high-level mentoring and networking opportunities to assist with the practical development of the solution, business plan and modelling, testing facilities, go-to-market strategy, etc. Winning ideas will also have access to a grant, the amount of which will be decided by the jury, on a case-to-case basis.
The MG Developer Program & Grant will initially focus on driving innovation in the following verticals: electric vehicles and components, batteries and management, harging infrastructure, connected mobility, voice recognition, AI & ML, navigation technologies, customer experiences, car buying experiences, and autonomous vehicles.
“The MG Developer & Grant Program is the latest in a series of initiatives as part of our commitment to innovation as a core organizational pillar. The program will ensure proper mentoring from over 20 industry leaders for start-ups, laying a foundation for them to excel in the future and trigger a stream of newer Internet Car use-cases that will, in turn, drive adoption of new technologies within the Indian automotive ecosystem. It has been our commitment in the market and Innovation is our key pillar,” added Chaba.
The program will award grants ranging from INR5 lakhs to INR25 Lakhs. The program will be open to both external developers – including students, innovators, inventors, startups and other tech companies – and internal employee teams at MG Motor and its program partners.
--------------------------------------------------------------------------------
via: https://opensourceforu.com/2019/09/mg-motor-announces-developer-program-and-grant-in-india/
作者：[Mukul Yudhveer Singh][a]
选题：[lujun9972][b]
译者：[译者ID](https://github.com/译者ID)
校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://opensourceforu.com/author/mukul-kumar/
[b]: https://github.com/lujun9972
[1]: https://i0.wp.com/opensourceforu.com/wp-content/uploads/2019/09/MG-Developer-program.png?resize=660%2C440&ssl=1 (MG Developer program)
[2]: https://i0.wp.com/opensourceforu.com/wp-content/uploads/2019/09/MG-Developer-program.png?fit=660%2C440&ssl=1
[3]: https://i0.wp.com/opensourceforu.com/wp-content/uploads/2019/09/MG-Developer-program.png?resize=350%2C233&ssl=1
| 84.865385 | 554 | 0.77249 | eng_Latn | 0.978563 |
2f8882389d9cc00abf7ba7543f8e7c2c8f8096e0 | 4,404 | md | Markdown | docs/sequel/README.md | jclusso/flipper | f0f5b3004ba92391d6252bb4c73c4d9d08df9119 | [
"MIT"
] | null | null | null | docs/sequel/README.md | jclusso/flipper | f0f5b3004ba92391d6252bb4c73c4d9d08df9119 | [
"MIT"
] | null | null | null | docs/sequel/README.md | jclusso/flipper | f0f5b3004ba92391d6252bb4c73c4d9d08df9119 | [
"MIT"
] | null | null | null | # Flipper Sequel
A [Sequel](https://github.com/jeremyevans/sequel) adapter for [Flipper](https://github.com/jnunemaker/flipper).
## Installation
Add this line to your application's Gemfile:
gem 'flipper-sequel'
And then execute:
$ bundle
Or install it yourself with:
$ gem install flipper-sequel
## Usage
For your convenience, a sequel migration is provided to create the necessary tables. This migration will create two database tables - flipper_features and flipper_gates.
```ruby
require 'generators/flipper/templates/sequel_migration'
CreateFlipperTablesSequel.new(Sequel::Model.db).up
```
Once you have created and executed the migration, you can use the sequel adapter by simply requiring it:
```ruby
require 'flipper-sequel`
```
**If you need to customize the adapter**, you can add this to an initializer:
```ruby
Flipper.configure do |config|
config.adapter { Flipper::Adapters::Sequel.new }
end
```
## Internals
Each feature is stored as a row in a features table. Each gate is stored as a row in a gates table, related to the feature by the feature's key.
```ruby
require 'flipper/adapters/sequel'
adapter = Flipper::Adapters::Sequel.new
flipper = Flipper.new(adapter)
# Register a few groups.
Flipper.register(:admins) { |thing| thing.admin? }
Flipper.register(:early_access) { |thing| thing.early_access? }
# Create a user class that has flipper_id instance method.
User = Struct.new(:flipper_id)
flipper[:stats].enable
flipper[:stats].enable_group :admins
flipper[:stats].enable_group :early_access
flipper[:stats].enable_actor User.new('25')
flipper[:stats].enable_actor User.new('90')
flipper[:stats].enable_actor User.new('180')
flipper[:stats].enable_percentage_of_time 15
flipper[:stats].enable_percentage_of_actors 45
flipper[:search].enable
puts 'all rows in features table'
pp Flipper::Adapters::Sequel::Feature.all
#[#<Flipper::Adapters::Sequel::Feature @values={:key=>"stats", :created_at=>2016-11-19 13:57:48 -0500, :updated_at=>2016-11-19 13:57:48 -0500}>,
# #<Flipper::Adapters::Sequel::Feature @values={:key=>"search", :created_at=>2016-11-19 13:57:48 -0500, :updated_at=>2016-11-19 13:57:48 -0500}>]
puts
puts 'all rows in gates table'
pp Flipper::Adapters::Sequel::Gate.all
# [#<Flipper::Adapters::Sequel::Gate @values={:feature_key=>"stats", :key=>"boolean", :value=>"true", :created_at=>2016-11-19 13:57:48 -0500, :updated_at=>2016-11-19 13:57:48 -0500}>,
# #<Flipper::Adapters::Sequel::Gate @values={:feature_key=>"stats", :key=>"groups", :value=>"admins", :created_at=>2016-11-19 13:57:48 -0500, :updated_at=>2016-11-19 13:57:48 -0500}>,
# #<Flipper::Adapters::Sequel::Gate @values={:feature_key=>"stats", :key=>"groups", :value=>"early_access", :created_at=>2016-11-19 13:57:48 -0500, :updated_at=>2016-11-19 13:57:48 -0500}>,
# #<Flipper::Adapters::Sequel::Gate @values={:feature_key=>"stats", :key=>"actors", :value=>"25", :created_at=>2016-11-19 13:57:48 -0500, :updated_at=>2016-11-19 13:57:48 -0500}>,
# #<Flipper::Adapters::Sequel::Gate @values={:feature_key=>"stats", :key=>"actors", :value=>"90", :created_at=>2016-11-19 13:57:48 -0500, :updated_at=>2016-11-19 13:57:48 -0500}>,
# #<Flipper::Adapters::Sequel::Gate @values={:feature_key=>"stats", :key=>"actors", :value=>"180", :created_at=>2016-11-19 13:57:48 -0500, :updated_at=>2016-11-19 13:57:48 -0500}>,
# #<Flipper::Adapters::Sequel::Gate @values={:feature_key=>"stats", :key=>"percentage_of_time", :value=>"15", :created_at=>2016-11-19 13:57:48 -0500, :updated_at=>2016-11-19 13:57:48 -0500}>,
# #<Flipper::Adapters::Sequel::Gate @values={:feature_key=>"stats", :key=>"percentage_of_actors", :value=>"45", :created_at=>2016-11-19 13:57:48 -0500, :updated_at=>2016-11-19 13:57:48 -0500}>,
# #<Flipper::Adapters::Sequel::Gate @values={:feature_key=>"search", :key=>"boolean", :value=>"true", :created_at=>2016-11-19 13:57:48 -0500, :updated_at=>2016-11-19 13:57:48 -0500}>]
puts
puts 'flipper get of feature'
pp adapter.get(flipper[:stats])
# {:boolean=>"true",
# :groups=>#<Set: {"admins", "early_access"}>,
# :actors=>#<Set: {"180", "25", "90"}>,
# :percentage_of_actors=>"45",
# :percentage_of_time=>"15"}
```
## Contributing
1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Added some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request
| 42.346154 | 194 | 0.709128 | eng_Latn | 0.313326 |
2f89fa57a826942e507011e849e612a924b3e271 | 1,733 | md | Markdown | packages/zeplin-sass-extension/README.md | AirStair/stylesheet-extensions | 2e359c1eff704f8dbe19e721d945c9e40db4f05d | [
"MIT"
] | 29 | 2018-10-09T16:37:23.000Z | 2021-05-24T20:20:25.000Z | packages/zeplin-sass-extension/README.md | AirStair/stylesheet-extensions | 2e359c1eff704f8dbe19e721d945c9e40db4f05d | [
"MIT"
] | 10 | 2019-06-19T01:47:43.000Z | 2021-04-21T19:59:23.000Z | packages/zeplin-sass-extension/README.md | AirStair/stylesheet-extensions | 2e359c1eff704f8dbe19e721d945c9e40db4f05d | [
"MIT"
] | 19 | 2018-10-16T23:34:38.000Z | 2022-03-23T06:26:33.000Z | # Zeplin Sass Extension
Generates Sass snippets from colors, text styles and layers. ⚛️📱
## Output
Sample colors output:
```sass
$blue: #0000ff
$yellow: #ffff00
$green: #00ff00
$black: #000000
$black50: rgba(0, 0, 0, 0.5)
$white: #ffffff
$red: #ff0000
```
Sample text style output:
```sass
=Sample-text-style-with-color()
font-family: SFProText
font-size: 20px
text-align: left
color: $red
=Sample-text-style()
font-family: SFProText
font-size: 20px
text-align: left
```
Sample layer output:
```sass
.Layer-with-shadow
width: 100px
height: 100px
box-shadow: 0 2px 4px 6px $black50
```
## Options
#### Color format
Supports HEX, RGB or HSL. Sample colors output as HSL:
```sass
$blue: hsl(240, 100%, 50%)
$black50: hsla(0, 0%, 0%, 0.5)
```
#### Dimensions
Toggles generating `width` and `height` properties from layers.
#### Unitless line-height
Toggles generating unitless value for `line-height` property.
#### Text styles as mixins
Toggles using project text styles as mixins while generating code for text layers.
Sample output when this options disabled:
```sass
.Text-layer
width: 220px
height: 24px
font-family: SFProText
font-size: 20px
text-align: left
color: $black
```
When enabled:
```sass
.Text-layer
width: 220px
height: 24px
color: $black
+Sample-text-style()
```
#### Default values
Toggles always generating default values from layers or text styles, such as `fontWeight` and `fontStyle`.
## Development
Sass extension is developed using [zem](https://github.com/zeplin/zem), Zeplin Extension Manager. zem is a command line tool that lets you quickly create and test extensions.
To learn more about zem, [see documentation](https://github.com/zeplin/zem).
| 19.255556 | 174 | 0.709752 | eng_Latn | 0.886195 |
2f8a152dd2dd2846426bff1f83f1cd057d404dfc | 233 | md | Markdown | docs/sdk/com.robotemi.sdk.activitystream/-activity-stream-list-item/-builder/build.md | EddyJeon/temisdkTest | d787ae5461f997879dd11ba821df53cf029cca67 | [
"Apache-2.0"
] | 167 | 2019-06-14T15:28:02.000Z | 2022-03-17T10:06:22.000Z | docs/sdk/com.robotemi.sdk.activitystream/-activity-stream-list-item/-builder/build.md | EddyJeon/temisdkTest | d787ae5461f997879dd11ba821df53cf029cca67 | [
"Apache-2.0"
] | 231 | 2019-06-21T08:10:30.000Z | 2022-03-31T08:27:51.000Z | docs/sdk/com.robotemi.sdk.activitystream/-activity-stream-list-item/-builder/build.md | EddyJeon/temisdkTest | d787ae5461f997879dd11ba821df53cf029cca67 | [
"Apache-2.0"
] | 75 | 2019-08-14T07:20:10.000Z | 2022-03-07T12:34:51.000Z | [sdk](../../../index.md) / [com.robotemi.sdk.activitystream](../../index.md) / [ActivityStreamListItem](../index.md) / [Builder](index.md) / [build](./build.md)
# build
`open fun build(): `[`ActivityStreamListItem`](../index.md)`!` | 46.6 | 160 | 0.626609 | yue_Hant | 0.468448 |
2f8a39d077b80dc39dd8565da824ac39cfcf4313 | 85 | md | Markdown | README.md | oletizi/cosampler | 299b07bbb2a191ed0040ea8275a862de70d5b076 | [
"Apache-2.0"
] | null | null | null | README.md | oletizi/cosampler | 299b07bbb2a191ed0040ea8275a862de70d5b076 | [
"Apache-2.0"
] | null | null | null | README.md | oletizi/cosampler | 299b07bbb2a191ed0040ea8275a862de70d5b076 | [
"Apache-2.0"
] | null | null | null | # cosampler
Maybe a sampler written in C/C++ if it gets that far. A sandbox for now.
| 28.333333 | 72 | 0.729412 | eng_Latn | 0.997662 |
2f8aa2d8e138f1b9e0ea5a82a760a3710fb8bdab | 111 | md | Markdown | README.md | neoreeprast/vue-download-file | 936ca7f6446b9e1d48d224815cb2e3faa121c595 | [
"MIT"
] | null | null | null | README.md | neoreeprast/vue-download-file | 936ca7f6446b9e1d48d224815cb2e3faa121c595 | [
"MIT"
] | 2 | 2021-03-10T21:31:22.000Z | 2021-05-11T16:57:39.000Z | README.md | neoreeprast/vue-download-file | 936ca7f6446b9e1d48d224815cb2e3faa121c595 | [
"MIT"
] | null | null | null | # vue-download-file
Sample code on how to download file from server using axios library.
Code is in index.html
| 27.75 | 68 | 0.792793 | eng_Latn | 0.975674 |
2f8af62be031ab15f1b0546781126549ee88745d | 46 | md | Markdown | README.md | varunchenna1234/ass1day7-b7 | 1b9ccd83466fb0c35f0f682a820aea0cbd2115a4 | [
"Apache-2.0"
] | null | null | null | README.md | varunchenna1234/ass1day7-b7 | 1b9ccd83466fb0c35f0f682a820aea0cbd2115a4 | [
"Apache-2.0"
] | null | null | null | README.md | varunchenna1234/ass1day7-b7 | 1b9ccd83466fb0c35f0f682a820aea0cbd2115a4 | [
"Apache-2.0"
] | null | null | null | # ass1day7-b7
assignmnet1 of day7 from batch7
| 15.333333 | 31 | 0.804348 | eng_Latn | 0.993273 |
2f8afe3d0b28184e89040e8dba299ffb2c030dad | 2,691 | md | Markdown | readme.md | tpatel0107/School_District_Analysis- | 03367e7163faa65296eb82bcb5b88e7ca31c0f8c | [
"MIT"
] | null | null | null | readme.md | tpatel0107/School_District_Analysis- | 03367e7163faa65296eb82bcb5b88e7ca31c0f8c | [
"MIT"
] | null | null | null | readme.md | tpatel0107/School_District_Analysis- | 03367e7163faa65296eb82bcb5b88e7ca31c0f8c | [
"MIT"
] | null | null | null | # **School District Analysis**
# Purpose of the Analysis: Purpose of the analysis to clean up data for the school board and the supervisor. Thomas High School scores for math and reading seem to have been altered, we will need to remove these scores and run our analysis to create values that can be used and so our data is clean.
# Results:Analysis show that district summary was affected -
1) District Summary
**Was affected because due to removing the scores for Thomas High School caused the overall district scores to be skewed.
**Overall School averages were changed causing some to be zeros.
2) School Summary-
**School summary shows some schools that were not previously showing with good scores, ended up having higher scores. Budget per school shows these schools with higher budget.
3)Replacing the ninth graders math and reading scores affect Thomas High School's performance relative to the other schools, they dropped in scoring and budget due to the changes to the scores to nan
4)Math and reading scores by grade-passing math scores and reading scores went down
5)Schools with not such great scores, ended up with more school spending versus schools with higher scores
6)Scores by school size-Overall passing averages by schools were not changed
7)Scores by school type-Charter schools ended up with higher average reading passing score over district
## Summary-Four changes that happened were:
1) Scoring was affected for Thomas High School
2) Other schools came up in scoring due to changes to scoring for Thomas High School
3) School spending was effected
4) Score averages changed due to the changes
| 69 | 301 | 0.781122 | eng_Latn | 0.991171 |
2f8afedb0e23228e9b82b17d76a7c2ea8aa8bc5b | 463 | md | Markdown | 04-my_first_async_io/README.md | rickycodes/learnyounode-golf | 2dbdfe6aca2b236be948b99c18b8f2d211937390 | [
"MIT"
] | 9 | 2018-02-26T14:35:13.000Z | 2019-05-05T14:23:47.000Z | 04-my_first_async_io/README.md | rickycodes/learnyounode-golf | 2dbdfe6aca2b236be948b99c18b8f2d211937390 | [
"MIT"
] | 5 | 2018-02-26T15:02:57.000Z | 2020-05-11T17:14:08.000Z | 04-my_first_async_io/README.md | rickycodes/learnyounode-golf | 2dbdfe6aca2b236be948b99c18b8f2d211937390 | [
"MIT"
] | 6 | 2018-02-26T14:08:42.000Z | 2018-03-13T20:31:42.000Z | ### MY FIRST ASYNC I/O! (Exercise 4 of 13)
#### Problem:
Write a program that uses a single **asynchronous** filesystem operation to read a file and print the number of newlines it contains to the console (stdout), similar to running `cat file | wc -l`.
The full path to the file to read will be provided as the first command-line argument.
#### Solution:
index.js
```js
require('fs')
.readFile(process.argv[2],(_,d)=>console.log(--(''+d).split`
`.length))
```
| 33.071429 | 196 | 0.699784 | eng_Latn | 0.989521 |
2f8ca1cb5a3f97d55f8489e075080b4b9724d036 | 716 | md | Markdown | README.md | bclnet/DroidUIJson | 6848efb75572653559f338dfc14e61f28fe50eb2 | [
"MIT"
] | null | null | null | README.md | bclnet/DroidUIJson | 6848efb75572653559f338dfc14e61f28fe50eb2 | [
"MIT"
] | null | null | null | README.md | bclnet/DroidUIJson | 6848efb75572653559f338dfc14e61f28fe50eb2 | [
"MIT"
] | null | null | null | # DroidUIJson
A Json representation of DroidUI enabling runtime defined views
## Example
JsonPreview will provide json output with a before, and after representation.
```java
import com.DroidUI;
class SampleView implements View {
View getBody() { return
new VStack(() ->
new Text("Hello World");
)
.padding();
}
}
class SampleView_Previews implements PreviewProvider {
static View getPreviews() { returns
new JsonPreview(() ->
new SampleView();
);
}
}
```
## References
The extension method `var` will let DroidUIJson know this is intended to be a variable.
```java
new VStack(() ->
new Text("Title Here".var(self));
)
```
| 18.358974 | 87 | 0.638268 | eng_Latn | 0.618989 |
2f8cd951281baf3d8be956bbb2671a5219dd50c5 | 878 | md | Markdown | content/events/2019-tel-aviv/speakers/robert-barron.md | adzuci/devopsdays-web | aac92777aa15fafb77df084a57c08d1ac559ed30 | [
"Apache-2.0",
"MIT"
] | 149 | 2015-11-10T22:23:49.000Z | 2022-03-09T20:48:22.000Z | content/events/2019-tel-aviv/speakers/robert-barron.md | manicminer/devopsdays-web | db13681175f4e850f1033043d2113c9d64b2329f | [
"Apache-2.0",
"MIT"
] | 2,534 | 2015-11-10T21:56:39.000Z | 2022-03-31T20:26:29.000Z | content/events/2019-tel-aviv/speakers/robert-barron.md | manicminer/devopsdays-web | db13681175f4e850f1033043d2113c9d64b2329f | [
"Apache-2.0",
"MIT"
] | 1,014 | 2016-02-12T02:20:38.000Z | 2022-03-31T17:38:48.000Z | +++
Title = "Robert Barron"
Twitter = "flyingbarron"
image = "robert-barron.jpg"
type = "speaker"
linktitle = "robert-barron"
+++
Robert is a Senior Managing Consultant and member of the IBM Garage Solution Engineering group. Within the worldwide Garage Solution Engineering group, he is part of the Cloud Service Management and Operations (CSMO) team, working in all fields of CSMO and specializing in Site Reliability Engineering (SRE) and Chat Operations (ChatOps).
Robert joined IBM in 2007 and has held various positions in IBM, all in the field of Service Management. In total, he has over twenty years of experience in enterprise systems in multiple domains spanning development, technical leadership, project management and offering management.
Robert speaks at global conferences for IBM and creates assets that range from internal documentation to published books. | 62.714286 | 338 | 0.801822 | eng_Latn | 0.997269 |
2f8da6e894faa2033191c8a8b6155f03194e255c | 1,089 | md | Markdown | AlchemyInsights/commercial-dialogues/find-email-in-autoarchive.md | isabella232/OfficeDocs-AlchemyInsights-pr.sv-SE | f65a29c0e7e545e9826e9af01b9a5d4fe8a977d6 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-05-19T19:08:09.000Z | 2021-04-21T00:13:49.000Z | AlchemyInsights/commercial-dialogues/find-email-in-autoarchive.md | isabella232/OfficeDocs-AlchemyInsights-pr.sv-SE | f65a29c0e7e545e9826e9af01b9a5d4fe8a977d6 | [
"CC-BY-4.0",
"MIT"
] | 3 | 2020-06-02T23:25:58.000Z | 2022-02-09T06:54:54.000Z | AlchemyInsights/commercial-dialogues/find-email-in-autoarchive.md | isabella232/OfficeDocs-AlchemyInsights-pr.sv-SE | f65a29c0e7e545e9826e9af01b9a5d4fe8a977d6 | [
"CC-BY-4.0",
"MIT"
] | 3 | 2019-10-09T20:31:36.000Z | 2021-10-09T10:38:14.000Z | ---
title: Hitta e-post i Arkivera automatiskt
ms.author: v-jmathew
author: v-jmathew
manager: dansimp
ms.audience: Admin
ms.topic: article
ms.service: o365-administration
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Normal
ms.collection: Adm_O365
ms.custom:
- "3100008"
- "7255"
ms.openlocfilehash: a6a6a311708fc23a63656f5b8ccf572e30bc13dab1728bc3be48ad36aeb35077
ms.sourcegitcommit: b5f7da89a650d2915dc652449623c78be6247175
ms.translationtype: MT
ms.contentlocale: sv-SE
ms.lasthandoff: 08/05/2021
ms.locfileid: "54017294"
---
# <a name="find-email-in-autoarchive"></a>Hitta e-post i Arkivera automatiskt
Arkivfilen är en typ av Outlook (.pst). Första gången som Arkivera automatiskt körs skapas arkivfilen automatiskt i: C:\Användare\DittAnvändarnamn\Dokument\Outlook Files\archive.pst.
Så här visar du den automatiska arkivering:
1. I Outlook väljer du **fliken Arkiv och** > **till Outlook** > **datafil**.
2. Bläddra till PST-filens plats och öppna den. När du gör det kommer PST-filen att läggas till i mapplistan.
3. Du kan söka i mappen efter tidigare e-postmeddelanden.
| 35.129032 | 182 | 0.793388 | swe_Latn | 0.928906 |
2f8de17227eeebe120246d9c5e661a144c5d252c | 756 | md | Markdown | Readme.md | little-arhat/rust-chainbuf | 970424dfb4f931ea09fa75469e752a9fef988ef6 | [
"MIT"
] | 8 | 2015-01-23T10:51:13.000Z | 2020-02-16T20:46:34.000Z | Readme.md | little-arhat/rust-chainbuf | 970424dfb4f931ea09fa75469e752a9fef988ef6 | [
"MIT"
] | null | null | null | Readme.md | little-arhat/rust-chainbuf | 970424dfb4f931ea09fa75469e752a9fef988ef6 | [
"MIT"
] | null | null | null |
# Chainbuf
[](https://travis-ci.org/little-arhat/rust-chainbuf)
Chained buffer of contigious byte chunks.
# Simple usage
Plug the package into your app via Cargo:
```toml
[dependencies]
chainbuf = "0.0.4"
```
then use it:
```rust
extern crate chainbuf;
use chainbuf::Chain;
let mut chain = Chain::new();
chain.append_bytes("helloworld".as_bytes());
let some_bytes = chain.pullup(2);
```
# Details of implementation
Chainbuf consists of linked list of nodes, with `start` and `end`
offsets and a reference counted pointer to DataHolder. DataHolders can be
shared across different chains, so for mutation new nodes and data holders
are created (as in Copy-On-Write).
| 24.387097 | 135 | 0.75 | eng_Latn | 0.934036 |
2f8e5680adfdbd20802c4b9f60597b228abc4d55 | 12,023 | md | Markdown | Docs/Packaging/content-packaging-and-delivery.md | isharma-msft/PlayReady | 0db464722d9b372ba80547e4e7af80d6a4348b60 | [
"CC-BY-4.0",
"MIT"
] | 17 | 2018-02-08T09:24:53.000Z | 2021-11-19T17:10:36.000Z | Docs/Packaging/content-packaging-and-delivery.md | isharma-msft/PlayReady | 0db464722d9b372ba80547e4e7af80d6a4348b60 | [
"CC-BY-4.0",
"MIT"
] | 105 | 2017-12-14T19:54:40.000Z | 2022-03-28T17:17:38.000Z | Docs/Packaging/content-packaging-and-delivery.md | isharma-msft/PlayReady | 0db464722d9b372ba80547e4e7af80d6a4348b60 | [
"CC-BY-4.0",
"MIT"
] | 27 | 2017-11-30T23:03:11.000Z | 2021-11-05T06:13:12.000Z | ---
title: Content Packaging and Delivery
description: The basic capability of PlayReady is to protect content from unauthorized use.
ms.assetid: "7E87CB5D-59E1-4E25-8271-82FB97998ECD"
keywords: playready content encryption, encryption and delivery
ms.date: 02/01/2018
ms.topic: conceptual
---
# Content Packaging and Delivery
The basic capability of PlayReady is to protect content from unauthorized use. To do this, your content must first be encrypted, and an associated PlayReady Header be inserted in the content. The system that does this operation is the packager, also known as the encryptor, which is sometimes integrated with the encoder.
This topic describes various ways to encrypt and deliver your content using PlayReady.
## Packaging PlayReady content — Encrypting and inserting the DRM header
The process of encrypting clear content consists of defining one or several encryption keys, using these keys to encrypt the bytes that constitute the content itself, and inserting a DRM header in the content (in the files of the content, or in the manifest if the content has one).
All encrypted content protected by PlayReady must have a PlayReady Header inserted in the encrypted file. This PlayReady Header is used by a PlayReady Client to locate or acquire a license for that particular piece of content. A PlayReady Header is composed of XML that is encoded in UTF-16. It includes the key identifiers (KIDs) that are used to encrypt the content, a default URL that the client will use to acquire a license from if no other is provided, and any custom attributes.
Any packager that packages clear content needs to implement a PlayReady Header generator to build the header and embed it in the encrypted content. The PlayReady Header must be implemented according to the [PlayReady Header Specification](../Specifications/playready-header-specification.md). There are multiple ways to create a PlayReady Header generator in your packager:
* Develop it yourself based on the *PlayReady Header Specification*.
* Use the PlayReady Server SDK API that generates a PlayReady Header.
* Use the Windows 10 API that generates a PlayReady Header.
Your encrypted content can contain multiple DRM headers, including PlayReady Headers along with third-party DRM headers. For more information on how this works, see [Using encryption tools](#encryptiontools).
### Content Type
PlayReady can be used to protect audio and video content. The most common types of encoding used with PlayReady are MPEG-4 AVC (H.264), High Efficiency Video Coding (HEVC) H.265 standards, and the AV1 standard. PlayReady is not limited to these standards and can be used with any audio and video format that is supported on the client device.
PlayReady version 1 and 2 allows you to create a protected package containing content that is not limited to audio or video payloads. These packages, referred to as envelopes, can contain files such as a collection of data files and executables (for example, an application distributed by an application store), pictures (for example, screen wallpaper), or ebooks. This content is packaged by encapsulating the files into an envelope file, which can be decrypted in a manner similar to audio/video content.
These non audio/video content types are no longer supported in PlayReady 3.0 and later.
## Encryption tools
Microsoft does not include a packager as part of the PlayReady deliverables. PlayReady instead provides specifications based on common encryption standards for use by encoders. Therefore the encryption format is not PlayReady specific, rather it's a function of the file format. The most widely used encryption format today is the Common Encryption ISO Standard format, **ISO/IEC 23001-7**.
Basically, you could either create your own packager, or you could work with any type of open source encryptor (such as ffmpeg). In addition, you could work with a professional encoder company if you want to encrypt content with PlayReady (such as Harmonic, Elemental, Ericsson, Wowza, Allegro). Azure Media Services also provides a packaging functionality for clear content.
<a id="encryptiontools"></a>
## Using encryption tools
PlayReady supports the ISO IEC common encryption standard. This process is the same as described in [Basic encryption and licensing process](../Overview/simple-end-to-end-system.md#basicprocess), except headers will be included for other DRMs — each as the payload of the Protection System Specific Header (‘pssh’) box, identified by that DRM’s SystemID. All those headers will have their own syntax that designates the KIDs or the information required to ultimately access the content keys. And the content keys for this asset are going to be the same for all the DRMs.
## Using encryption keys
There are many different ways to encrypt your assets. The simplest one to the most sophisticated one depends on how much complexity you want to design in the system and what the needs of the service are.
Let's take for example, an adaptive streaming asset, as shown in the figure below. It has four different video qualities, one audio track, and one subtitle track. It is encoded in segmented MP4 files, with segments of 2.0 seconds each. It is one asset that is served in multiple formats depending on what the client would prefer to play back. Smooth Streaming, HLS, and DASH are the most common variants. During playback, the client (the video player) is going to successively download the segments of the asset over the network, selecting for each playback time the video segment from the adequate video track, in order to keep playback quality as high as possible, given the constraints of the network bandwidth, the playback speed, and other limited resources like the player capabilities. This logic is known as adaptive streaming playback, governed by some heuristics rules implemented in the player.
### Encrypting the asset with just one key
The simplest way to encrypt these assets would be to use a single content key to encrypt everything (typically subtitles are not encrypted — it's not against any rule, but they are usually kept in the clear). Using one content key makes life easy for the License Server because the License Server has to deliver one key {KID, CK}. This key would typically be acquired by the client before playback occurred.
>[!NOTE]
>PlayReady Clients can acquire licenses proactively or reactively. See the [License Acquisition](../Overview/license-acquisition.md#proactivereactive) page for a description of these two modes.
### Encrypting the asset with two keys, dedicating one to the highest quality
There have been some enhancements in the past years to use multiple keys per asset, mostly driven by the requirement to allow only certain highest-robustness clients to consume the highest quality content. With the arrival of Ultra HD (4K) content, and with the addition of high dynamic range (HDR) for higher color content, there was a need by studios and services to allow the highest quality only on certain clients, which typically have hardware DRM built in. In this scenario, the asset is encrypted using one content key {kid1, ck1} for all the tracks, except for the 4K track that is encrypted using a different content key {kid2, ck2}. That is:
* A client that is allowed to play only up to Full HD (not the 4K track) will be delivered a PlayReady license including only {kid1, ck1}.
* A client that is allowed to play up to 4K will be delivered a PlayReady license including {kid1, ck1} and {kid2, ck2}.
Using this additional complexity, the service can ensure that some clients will not be able to decrypt the 4K track, and that 4K track can be reserved to only the clients that the service most trusts.
### Encrypting the asset with one key per track
The service may have a more complex map of rights to enforce. Some clients, depending on their screen size, their robustness, their outputs, and their location, may be allowed to access only some video tracks, some video qualities, and some audio tracks. To ensure the service has full flexibility in enforcing an arbitrary set of restrictions in the future, it may encrypt an asset with a content key specific to each track. For example:
* A client that is allowed to play only 720p will be delivered a PlayReady license including {kid1, ck1}, {kid2, ck2}, and {kidA, ckA}.
* A client that is allowed to play up to 4K will be delivered a PlayReady license including {kid1, ck1}, {kid2, ck2}, {kid3, ck3}, {kid4, ck4}, and {kidA, ckA}.
* A client playing offline the 4K version of the asset (previously downloaded) will be delivered a PlayReady license including {kid4, ck4} and {kidA, ckA}.
### Changing the encryption keys periodically (multi-period asset)—license rotation
In some scenarios, the service wants to change the encryption keys occasionally, typically at program boundaries. For example, a live linear stream has multiple periods with free to air content that you want everyone to have access to, followed by some content that is restricted to subscribers. Changing the encryption keys at program boundaries allows the service to deliver the free to air keys {KIDi1, CKi1} to all users without any restrictions, and deliver the content keys {kidi2, cki2} only to the subscribers that have successfully logged in the service.
Note that this license rotation is not very scalable: every time the encryption keys change, all clients request the new encryption keys using their own license request. This can result in a high peak of license requests in systems with a large number of clients.
### Changing the encryption keys frequently—scalable key rotation
There is an advanced mechanism in PlayReady called scalable key rotation (as opposed to license rotation). This method stores an Embedded License Store (ELS) in the stream of the actual content. In this mechanism, the key used to encrypt the A2 segment itself is called the leaf key {kidA2, ckA2}, and is delivered in the ELS of the segment A2, being itself encrypted with a separate key that is the same for all the segments of track A, called the root key {kidRA, ckRA}. If you are familiar with MPEG-2 TS and the Control Word encryption, this is a similar mechanism except for the encryption is much stronger and is also more flexible.
Let's say this asset is live linear TV. When the client attempts playback, it finds kidRA in the PlayReady Header of the stream manifest, and requests a license for kidRA. The License Server returns a root license for the root key {kidRA, ckRA}. Then the client parses segment A1 and discovers the ELS in the header of the segment. Parsing this ELS, it finds the leaf license {kidA1, ckA1} in this ELS. Using the root key {kidRA, ckRA} and the leaf license {kidA1, ckA1}, it can get the value of ckA1, and decrypt and render the segment A1.
The PlayReady scalable key rotation feature is extremely scalable because it does not require clients to contact the License Server every time the encryption keys are changed. It keeps the volume of license requests to the lowest possible, as a client only needs one root license from the License Server per stream, or track. It allows encryption keys to rotate as frequently as every segment, typically every two seconds if necessary.
## See also
[Key and Key IDs (KIDs)](../Overview/key-and-key-ids-kids.md)
| 103.646552 | 906 | 0.793396 | eng_Latn | 0.999672 |
2f8ea0650c04ad3e86a2d60373ed85b89cf69515 | 119 | md | Markdown | README.md | softkr/IOT_Server | e14fceca62e68419f28ea2752e1f70e9e0ef3ffa | [
"Apache-2.0"
] | null | null | null | README.md | softkr/IOT_Server | e14fceca62e68419f28ea2752e1f70e9e0ef3ffa | [
"Apache-2.0"
] | null | null | null | README.md | softkr/IOT_Server | e14fceca62e68419f28ea2752e1f70e9e0ef3ffa | [
"Apache-2.0"
] | null | null | null | # IOTServer
인핸드플러스 iot 서버이며 인핸드워치에 마춰 개발된 서버입니다.
다른 용도로 사용이 불가능합니다.
개발자 활용위한 설명서는 [메뉴얼](./manual/manual.md) 확인 하십시오
| 19.833333 | 47 | 0.722689 | kor_Hang | 1.00001 |
2f8ec530256c3dbe3843a366d1eacad33b8e1975 | 76 | md | Markdown | README.md | LightSun/common-view | bba23a61f609a41ed8ab13471b6fc63c06edeb8d | [
"Apache-2.0"
] | null | null | null | README.md | LightSun/common-view | bba23a61f609a41ed8ab13471b6fc63c06edeb8d | [
"Apache-2.0"
] | null | null | null | README.md | LightSun/common-view | bba23a61f609a41ed8ab13471b6fc63c06edeb8d | [
"Apache-2.0"
] | null | null | null | # common-view
move old common view lib on android to here .just for jitpack
| 25.333333 | 61 | 0.776316 | eng_Latn | 0.995353 |
2f8f11cb98186c27aeea3a0de90d4e5f9fadcd02 | 1,791 | md | Markdown | gateways/core/artifact/README.md | locona/argo-events | 9122d50783511e7d08e9020f27249899fa015fe2 | [
"Apache-2.0"
] | 1 | 2019-04-17T23:10:21.000Z | 2019-04-17T23:10:21.000Z | gateways/core/artifact/README.md | locona/argo-events | 9122d50783511e7d08e9020f27249899fa015fe2 | [
"Apache-2.0"
] | null | null | null | gateways/core/artifact/README.md | locona/argo-events | 9122d50783511e7d08e9020f27249899fa015fe2 | [
"Apache-2.0"
] | 1 | 2020-09-02T06:33:20.000Z | 2020-09-02T06:33:20.000Z | <p align="center">
<img src="https://github.com/argoproj/argo-events/blob/ebdbdd4a2a8ce47a0fc6e9a6a63531be2c26148a/docs/assets/s3.png?raw=true" alt="Minio S3"/>
</p>
<br/>
# Minio S3
Artifact gateway listens to bucket notifications from Minio S3 server. If you are interested in AWS S3 then
read [AWS SNS Gateway](../../community/aws-sns/README.md)
## What types of bucket notifications minio offers?
Read about [notifications](https://docs.minio.io/docs/minio-bucket-notification-guide.html)
## How to define an event source in confimap?
An entry in the gateway configmap corresponds to [this](https://github.com/argoproj/argo-events/blob/a913dafbf000eb05401ef2c847b29152af82977f/pkg/apis/common/s3.go#L26-L33).
Most of the things declared are straightforward but `SecretKeySelector`.
`SecretKeySelector` basically contains the information about the Kubernetes secret that
contains the `access` and `secret` keys required to authenticate the user.
### Event Payload Structure
Refer AWS S3 Notitification - https://docs.aws.amazon.com/AmazonS3/latest/dev/notification-content-structure.html
## Setup
**Pre-requisite** - Create necessary bucket/s in Minio.
**1. Install [Gateway Configmap](../../../examples/gateways/artifact-gateway-configmap.yaml)**
**2. Install [Gateway](../../../examples/gateways/artifact-http.yaml)**
Make sure the gateway pod is created
**3. Install [Sensor](../../../examples/sensors/artifact.yaml)**
**4. Trigger workflow**
Drop a file onto `input` bucket and monitor workflows
## How to listen to notifications from different bucket
Simply edit the gateway configmap and add new entry that contains the configuration required to listen to new bucket, save
the configmap. The gateway will now start listening to both old and new buckets.
| 38.934783 | 173 | 0.766052 | eng_Latn | 0.861644 |
2f8f62349420633e43c6dcba4992cfc88cac08c5 | 17,157 | md | Markdown | packages/color/tpl.readme.md | chancyk/umbrella | f24e2605b493db10a1e760ad7a358bf0ef55d437 | [
"Apache-2.0"
] | null | null | null | packages/color/tpl.readme.md | chancyk/umbrella | f24e2605b493db10a1e760ad7a358bf0ef55d437 | [
"Apache-2.0"
] | null | null | null | packages/color/tpl.readme.md | chancyk/umbrella | f24e2605b493db10a1e760ad7a358bf0ef55d437 | [
"Apache-2.0"
] | null | null | null | # ${pkg.banner}
[](https://www.npmjs.com/package/${pkg.name})
[](https://twitter.com/thing_umbrella)
This project is part of the
[@thi.ng/umbrella](https://github.com/thi-ng/umbrella/) monorepo.
For the Clojure version, please visit: [thi.ng/color-clj](https://thi.ng/color-clj)
<!-- TOC -->
## About
${pkg.description}
### Color spaces / modes
Fast color space conversions (any direction) between:
- CSS (string, hex3/hex4/hex6/hex8, rgba(), hsla(), named colors)
- HCYA (float4)
- HSIA (float4)
- HSLA (float4)
- HSVA (float4)
- Int32 (uint32, `0xaarrggbb`)
- RGBA (float4)
- XYZA (float4, aka CIE 1931)
- YCbCr (float4)
Apart from `CSS` and `Int32` colors, all others can be stored as plain
arrays, typed array or custom array-like types of (mostly) normalized
values (`[0,1]` interval). Where applicable, the hue too is stored in
that range, NOT in degrees.
Apart from conversions, most other operations provided by this package
are currently only supporting RGBA colors. These can also be converted
to / from sRGB (i.e. linear vs gamma corrected).
#### Class wrappers
The package provides lightweight class wrappers for each color mode /
space. These wrappers act similarly to the `Vec2/3/4` wrappers in
[@thi.ng/vectors](https://github.com/thi-ng/umbrella/tree/develop/packages/vectors),
support striding (for mapped memory views), named channel accessor
aliases (in addition to array indexing) and are fully compatible with
all functions (and act as syntax sugar for generic conversion
functions). Wrapper factory functions are provided for convenience.
### Color theme generation
The package provides several methods for procedural & declarative color theme
generations. The latter relies on the concept of HSV color ranges, which can be
sampled directly and/or mixed with a base color to produce randomized
variations. Furthermore, multiple such ranges can be combined into a weighted
set to define probabilistic color themes.
```ts
// single random color drawn from the "bright" color range preset
colorFromRange(RANGES.bright);
// [ 0.7302125322518669, 0.8519945301256682, 0.8134374983367859, 1 ]
// single random color based on given HSV base color and preset
colorFromRange(RANGES.warm, [0.33, 1, 1])
// [ 0.3065587375218628, 0.8651353734302525, 0.748781892650323, 1 ]
// infinite iterator of colors sampled from the preset
// (see table below)
const colors = colorsFromRange(RANGES.bright);
colors.next();
// {
// value: [ 0.006959075656347791, 0.8760165887192115, 0.912149937028727, 1 ],
// done: false
// }
// 10 cool reds, w/ 10% hue variance
[...colorsFromRange(RANGES.cool, [0, 0.8, 1], { num: 10, variance: 0.1 })]
// generate colors based on given weighted textual description(s)
[...colorsFromTheme(
["warm goldenrod 1.0", "cool springgreen 0.1"],
{ num: 100, variance: 0.05 }
)]
// theme parts can also be given in this format
// note: base colors are always in HSV
// all keys are optional (range, base, weight),
// but at least `range` or `base` must be given...
[...colorsFromTheme(
[
{ range: "warm", base: "goldenrod", weight: 1 },
{ range: RANGES.cool, base: [0, 1, 0.5], weight: 0.1 }
],
{ num: 100, variance: 0.05 }
)]
```
| ID | 100 colors drawn from color range preset only, sorted by hue |
|-----------|--------------------------------------------------------------------------------------------------------------------|
| `bright` |  |
| `cool` |  |
| `dark` |  |
| `fresh` |  |
| `hard` |  |
| `intense` |  |
| `light` |  |
| `neutral` |  |
| `soft` |  |
| `warm` |  |
| `weak` |  |
| ID | 100 colors, single base color w/ color range preset, sorted by brightness |
|-----------|--------------------------------------------------------------------------------------------------------------------|
| `bright` |  |
| `cool` |  |
| `dark` |  |
| `fresh` |  |
| `hard` |  |
| `intense` |  |
| `light` |  |
| `neutral` |  |
| `soft` |  |
| `warm` |  |
| `weak` |  |
| ID | 100 colors, 2 base colors w/ color range preset, sorted by brightness |
|-----------|------------------------------------------------------------------------------------------------------------------|
| `bright` |  |
| `cool` |  |
| `dark` |  |
| `fresh` |  |
| `hard` |  |
| `intense` |  |
| `light` |  |
| `neutral` |  |
| `soft` |  |
| `warm` |  |
| `weak` |  |
Full example:
```ts
import { colorsFromTheme, hsva, swatchesH } from "@thi.ng/color";
import { serialize } from "@thi.ng/hiccup";
import { svg } from "@thi.ng/hiccup-svg";
import { writeFileSync } from "fs";
// color theme definition using:
// color range preset names, CSS colors and weights
const theme = <ColorThemePartString[]>[
"fresh hotpink 0.1",
"cool goldenrod 1",
"light springgreen 0.1",
];
// generate 200 HSV colors based on above description
const colors = [...colorsFromTheme(theme, { num: 200, variance: 0.05 })];
// create SVG doc of color swatches (hiccup format)
// (convert colors to RGB for smaller file size)
const doc = svg(
{ width: 1000, height: 50, convert: true },
swatchesH(colors.map((x) => hsvaRgba([], x)), 5, 50)
);
// serialize to SVG file
writeFileSync("export/swatches-ex01.svg", serialize(doc));
```
### RGBA transformations
RGBA [color matrix
transformations](https://github.com/thi-ng/umbrella/tree/develop/packages/color/src/transform.ts),
including parametric preset transforms:
- brightness
- contrast
- exposure
- saturation (luminance aware)
- hue rotation
- color temperature (warm / cold)
- sepia (w/ fade amount)
- tint (green / magenta)
- grayscale (luminance aware)
- subtraction/inversion (also available as non-matrix op)
- luminance to alpha
Transformation matrices can be combined using matrix multiplication /
concatenation (see `concat()`) for more efficient application.
### RGBA Porter-Duff compositing
This feature has been moved to the separate
[@thi.ng/porter-duff](https://github.com/thi-ng/umbrella/tree/develop/packages/porter-duff)
package.
### Cosine gradients
- [Original article](http://www.iquilezles.org/www/articles/palettes/palettes.htm)
- [Gradient generator](http://dev.thi.ng/gradients/)
The following presets are bundled (in [`cosine-gradients.ts`](https://github.com/thi-ng/umbrella/tree/develop/packages/color/src/cosine-gradients.ts)):
| Preview | Gradient ID |
|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|
|  | `blue-cyan` |
|  | `blue-magenta-orange` |
|  | `blue-white-red` |
|  | `cyan-magenta` |
|  | `green-blue-orange` |
|  | `green-cyan` |
|  | `green-magenta` |
|  | `green-red` |
|  | `heat1` |
|  | `magenta-green` |
|  | `orange-blue` |
|  | `orange-magenta-blue` |
|  | `purple-orange-cyan` |
|  | `rainbow1` |
|  | `rainbow2` |
|  | `rainbow3` |
|  | `rainbow4` |
|  | `red-blue` |
|  | `yellow-green-blue` |
|  | `yellow-magenta-cyan` |
|  | `yellow-purple-magenta` |
|  | `yellow-red` |
### Two-color gradients
The `cosineCoeffs()` function can be used to compute the cosine gradient
coefficients between 2 start/end colors:
```ts
// compute gradient coeffs between red / green
cosineGradient(10, cosineCoeffs([1,0,0,1], [0,1,0,1])).map(rgbaCss)
// #ff0000
// #f70800
// #e11e00
// #bf4000
// #966900
// #699600
// #40bf00
// #1ee100
// #08f700
// #00ff00
```
### Multi-stop gradients
The `multiCosineGradient()` function returns an iterator of raw RGBA
colors based on given gradient stops. This iterator computes a cosine
gradient between each color stop and yields a sequence of RGBA values.
```ts
col.multiCosineGradient(
// num colors to produce
10,
// gradient stops (normalized positions, only RGBA colors supported)
[0.1, col.RED], [0.5, col.GREEN], [0.9, col.BLUE]
)
// convert to CSS
.map(col.rgbaCss)
// [
// "#ff0000",
// "#ff0000",
// "#da2500",
// "#807f00",
// "#25da00",
// "#00ff00",
// "#00da25",
// "#00807f",
// "#0025da",
// "#0000ff",
// "#0000ff",
// ]
```
${status}
${supportPackages}
${relatedPackages}
${blogPosts}
## Installation
${pkg.install}
${pkg.size}
## Dependencies
${pkg.deps}
${examples}
## API
${docLink}
```ts
import * as col from "@thi.ng/color";
// route #1: asXXX() converters: string -> CSS -> ARGB (int) -> RGBA
const a = col.asRGBA(col.css("#3cf"));
// [0.2, 0.8, 1, 1]
// route #2: parseCSS(): string -> RGBA
const b = col.parseCss("hsla(30,100%,50%,0.75)");
// [ 1, 0.5, 0, 0.75 ]
// route #3: convert() multi-method: CSS -> RGBA -> HSVA
// (see convert.ts)
const c = col.convert("rgb(0,255,255)", "hsv", "css");
// [ 0.4999999722222268, 0.9999990000010001, 1, 1 ]
// route #4: direct conversion RGBA -> HSLA -> CSS
// first arg is output color (same calling convention as @thi.ng/vectors)
// (use `null` to mutate the input color)
col.hslaCss(col.rgbaHsla([], [1, 0.5, 0.5, 1]))
// "hsl(0.00,100.00%,75.00%)"
col.luminance(col.css("white"))
col.luminance(0xffffff, "int")
// 1
// apply color matrix (RGBA only)
col.transform([], col.saturation(1.25), a)
// [ 0.07835000000000002, 0.82835, 1, 1 ]
// combine matrix transformations
filter = col.concat(
col.saturation(0.5), // 50% saturation
col.brightness(0.1), // +10% brightness
);
col.transform([], filter, col.RED);
// [ 0.7065, 0.2065, 0.2065, 1 ]
```
## Authors
${authors}
${pkg.cite}
## License
© ${copyright} // ${license}
| 48.19382 | 171 | 0.659672 | eng_Latn | 0.39601 |
2f8fbcef97bf184f20a60d163138d62fc9433bba | 502 | md | Markdown | doc/Examples.md | olivier-stasse/sot-doc | e09384437066f8184fee571d17f16a17312a378c | [
"MIT"
] | null | null | null | doc/Examples.md | olivier-stasse/sot-doc | e09384437066f8184fee571d17f16a17312a378c | [
"MIT"
] | null | null | null | doc/Examples.md | olivier-stasse/sot-doc | e09384437066f8184fee571d17f16a17312a378c | [
"MIT"
] | null | null | null | # Examples of control infra structure using the SoT {#examples_using_sot}
\section ex_usage_mpi Max-Planck-Institute
* Documentation entry point of the machines-in-motion organization
https://machines-in-motion.github.io/
* Documentation of the tutorial (all in the Readme)
https://github.com/machines-in-motion/dg_tutorial_with_turtlesim
* Documentation of the dynamic_graph_manager
https://machines-in-motion.github.io/code_documentation/dynamic_graph_manager/docs/doxygen/html/index.html | 41.833333 | 107 | 0.814741 | yue_Hant | 0.42548 |
2f90019e6f3f6260501567588281bdc45569b5b4 | 749 | md | Markdown | api/client/args/Telerik.Web.UI.RibbonBarDropDownSelectedIndexChangedEventArgs.md | PaulSorauer/ajax-docs | e7e10ece5fd22eddcf8db12bc6b8405d7aae16ac | [
"Apache-2.0"
] | null | null | null | api/client/args/Telerik.Web.UI.RibbonBarDropDownSelectedIndexChangedEventArgs.md | PaulSorauer/ajax-docs | e7e10ece5fd22eddcf8db12bc6b8405d7aae16ac | [
"Apache-2.0"
] | null | null | null | api/client/args/Telerik.Web.UI.RibbonBarDropDownSelectedIndexChangedEventArgs.md | PaulSorauer/ajax-docs | e7e10ece5fd22eddcf8db12bc6b8405d7aae16ac | [
"Apache-2.0"
] | null | null | null | ---
title: Telerik.Web.UI.RibbonBarDropDownSelectedIndexChangedEventArgs
title_prefix: Client-side API Reference
description: Telerik.Web.UI.RibbonBarDropDownSelectedIndexChangedEventArgs
slug: Telerik.Web.UI.RibbonBarDropDownSelectedIndexChangedEventArgs
---
# Telerik.Web.UI.RibbonBarDropDownSelectedIndexChangedEventArgs
## Inheritance Hierarchy
* *[Telerik.Web.UI.RibbonBarDropDownSelectedIndexChangedEventArgs]({%slug Telerik.Web.UI.RibbonBarDropDownSelectedIndexChangedEventArgs%})*
## Methods
### get_dropDown
Returns a reference to the ribbonbar dropdown that was clicked.
#### Parameters
#### Returns
`Telerik.Web.UI.RibbonBarDropDown`
### get_index
Returns dropdown's selected index.
#### Parameters
#### Returns
`Number`
| 20.243243 | 139 | 0.807744 | yue_Hant | 0.596824 |
2f90afc1c527c1635037f7818b09ac284a243155 | 2,092 | md | Markdown | docs/getting-started.md | nchamsi/vuse | e6678f2f6ba86e36aea5c9ba76cce04a0a3c0bf1 | [
"MIT"
] | 458 | 2018-01-09T21:16:01.000Z | 2022-03-31T01:59:08.000Z | docs/getting-started.md | nchamsi/vuse | e6678f2f6ba86e36aea5c9ba76cce04a0a3c0bf1 | [
"MIT"
] | 32 | 2018-06-12T06:03:04.000Z | 2022-02-26T01:35:26.000Z | docs/getting-started.md | nchamsi/vuse | e6678f2f6ba86e36aea5c9ba76cce04a0a3c0bf1 | [
"MIT"
] | 146 | 2018-01-24T11:06:38.000Z | 2022-03-12T05:57:04.000Z | # getting-started
## What is this
This builder (sections builder) reuses your Vue components as **editable sections** to produce an interactive page builder to the end user, you can use it as a prototyping tool as well as it is sort-of a block builder.
The user/developer can then export the builder for usability in multiple formats, the following are the officially supported ones:
- `json` A json object which can be later used to re-render a page, particularly useful if you plan to have dynamic pages or want to store them in a Database.
- `preview` opens a new page without the editable logic in new tab to see the end result.
- `pwa` produces a zip file which contains all the page files and images neatly packed, this is probably the format you will use for page/prototype landing page builder, The project is augmented by default with service workers to support offline viewing.
The builder is just a Vue plugin, so you can integrate this into your own projects without needing to create separate bundles for it.
## Installation
### Package managers
First step is to install it using `yarn` or `npm`:
```bash
npm install vuse
# or use yarn
yarn add vuse
```
### CDNs
Or add it as a script tag in your projects.
- [unpkg](https://unpkg.com/vuse)
```html
<script src="https://unpkg.com/vue@2.4.2"></script>
<script src="https://unpkg.com/vuse"></script>
```
### Usage
::: tip
If you added it using a script tag, you can skip this section. as it will be auto-installed for you
:::
```js
import Builder from 'vuse';
Vue.use(Builder);
```
You can start using the `b-builder` component to build things now.
This package does not include any sections. The builder is just a system of helpers for managing customizable sections, seeding fake data, exporting views and re-rendering them. The logic for your components/sections is written by you eventually. **we will be adding a huge number of sections soon to be used with this one**. You can use the included examples after reading the API to build your own for now. | 39.471698 | 408 | 0.73566 | eng_Latn | 0.999418 |
2f914f01ee35fa3392648e6d262c46a34d5dd1cd | 3,199 | md | Markdown | source/_posts/macOS.set.mouse.md | DevStarSJ/hexo-src | 016ab30eb80f23a586e61b569d2bd3fedd9fc486 | [
"MIT"
] | null | null | null | source/_posts/macOS.set.mouse.md | DevStarSJ/hexo-src | 016ab30eb80f23a586e61b569d2bd3fedd9fc486 | [
"MIT"
] | null | null | null | source/_posts/macOS.set.mouse.md | DevStarSJ/hexo-src | 016ab30eb80f23a586e61b569d2bd3fedd9fc486 | [
"MIT"
] | null | null | null | ---
title: Using the gesture function with a common mouse in macOS
date: 2016-05-07 00:00:00
categories:
- Tips
- macOS
tags:
- macOS
---
## macOS(OSX)에서 일반 마우스로 매직마우스의 제스쳐(gesture) 기능 사용하기
맥북프로나 맥북에어의 경우 마우스없이 매직패드만으로도 사용이 편리하다는 분들이 많긴하지만,
그래도 마우스를 사용하는게 익숙하신 분들은 마우스 사용을 선호합니다.
이 경우 매직패드에서 제스쳐로 제공하는 기능이 편리하기 때문에 해당 기능을 사용하기 위해서 매직마우스를 구입하는 경우가 많습니다.
하지만 매직마우스 가격이 좀 후덜덜하죠. (99,000원)
오픈마켓에서 조금 저렴하게 구입하더라도 8만원이 넘습니다.
### 키보드 단축키 확인 및 재할당
사실 매직마우스에서 주로 사용하는 제스쳐 중 `Mission Control`, `왼쪽 Space`, `오른쪽 Space` 이 3가지만 사용하더라도 작업이 편리해 집니다.
기본적으로 이 기능을 굳이 매직마우스를 사용하지 않고 `키보드 단축키`를 사용하는 것도 가능합니다.
<img src="https://github.com/DevStarSJ/Study/raw/master/Blog/Apple/image/macOS.set.mouse.01.png?raw=true">
`^`는 `control`키를 뜻합니다.
`control`키와 방향키 4개를 이용해서 해당 기능들이 기본으로 할당되어 있습니다.
### Mission Control 기능을 마우스에 할당
이 기능들을 마우스 버튼에 할당하려면 `시스템 환경설정` 에서 `Mission Control`에서 가능합니다.
<img src="https://github.com/DevStarSJ/Study/raw/master/Blog/Apple/image/macOS.set.mouse.02.png?raw=true">
아래쪽에보면 키보드로는 기본 단축키들이 할당되어 있습니다.
<img src="https://github.com/DevStarSJ/Study/raw/master/Blog/Apple/image/macOS.set.mouse.03.png?raw=true">
그 오른쪽을 클릭하면 마우스버튼 또는 마우스 버튼 + 특수키(`control` , `alt`, `command`, `shift`) 조합을 이용해서도 가능합니다.
여기에서 마우스버튼을 할당하려고 눌러보면 마우스 버튼이 32번까지 할당이 가능합니다.
하지만, 일반 마우스의 경우 마우스 버튼을 *macOS* 에서 인식하기 위해서는 전용 드라이버를 설치하거나, 별도의 프로그램을 사용해야 합니다.
그리고 결정적으로 여기에서는 **Space** 간 이용에 대해서는 할당이 안됩니다.
### BetterTouchTool
예전에는 무료 프로그램도 많았지만 요즘 대부분 유료화 되었으며 그래도 그 중 가장 기능이 많고 사용하기 편한 것으로는 `BetterTouchTool`가 있습니다.
<https://www.boastr.net/downloads>에서 45일 *Trial* 로 사용이 가능하며 4,500원에서 50,000원 정도의 가격으로 구매가 가능합니다.
제작사는 7,000원 정도의 가격으로 구매해주기를 추천한다고 되어 있습니다.
가격별로 기능적 차이는 없습니다.
그냥 *donation* 적인 측면이라 생각하시면 될 것입니다.
`BetterTouchTool` 의 원래 목적은 *macOS* 및 개별 Application 별로 키보드, 매직마우스, 일반마우스 의 특정 버튼 및 제스쳐에 기능들을 할당하는 것이므로 매직마우스 사용자라도 구매하시면 편리하게 사용이 가능합니다.
일반마우스 사용자는 이 툴을 이용해서 기본적으로 *macOS* 에서 할당되지 않은 버튼이나 버튼 + 특수키(`control` , `alt`, `command`, `shift`)의 조합으로 `Mission Control`, `왼쪽 Space`, `오른쪽 Space` 등의 기능을 할당 할 수 있습니다.
### 제조사 제공 마우스 드라이버
필자는 **Logitech** 사의 `MX Anywhere 2` 마우스를 사용중인데, 제조사에서 *macOS* 용 드라이버를 따로 제공해 줍니다.
이렇게 별도의 드라이버를 제공하는 마우스의 경우에는 거기서 설정이 가능한 경우가 많습니다.
<img src="https://github.com/DevStarSJ/Study/raw/master/Blog/Apple/image/macOS.set.mouse.04.png?raw=true">
`MX Anywhere 2`는 가운데 버튼에 `Mission Control`, `왼쪽 Space`, `오른쪽 Space` 이 기본적으로 할당되어 있습니다.
<img src="https://github.com/DevStarSJ/Study/raw/master/Blog/Apple/image/macOS.set.mouse.05.png?raw=true">
- `Mission Control` : 가운데 버튼 클릭 또는 누른체 위로 이동
- `왼쪽 Space` : 가운데 버튼 누른체 좌로 이동
- `오른쪽 Space` : 가운데 버튼 누른체 우로 이동
- `응용 프로그램 윈도우` : 가운데 버튼 누른체 아래로 이동
`Space 이동`의 경우는 비교적 자주 사용하는 기능이므로 좀 더 빨리 사용하기 위해 마우스 휠을 좌, 우로 클릭하는 것이 더 편리할 것으로 판단되어 그렇게 할당을 하였습니다.
<img src="https://github.com/DevStarSJ/Study/raw/master/Blog/Apple/image/macOS.set.mouse.06.png?raw=true">
### 마치며...
해당 제품이 아닌 다른 마우스를 구입할 경우 제조사에서 드라이버를 제공해주지 않는다 하더라도 `BetterTouchTool` 툴을 이용해서 할당이 가능합니다.
단, 마우스의 별도 버튼이 있거나, 휠을 좌,우 클릭으로 누르는게 가능한 마우스를 구매하셔야 좀 더 편리하게 사용이 가능하리라 생각됩니다.
조금 저렴한 버튼이 많은 마우스(휠 좌,우 클릭 지원)와 `BetterTouchTool` 구매를 하더라도 매직마우스 보다는 확실히 더 저렴하니깐요.
매직마우스 + `BetterTouchTool` 의 조합의 경우는 더 많은 작업이 가능하겠지만요.
세손가락 클릭, 네손가락 클릭 등 매직마우스 상의 제스쳐를 이용해서 벼나별 기능의 할당이 가능합니다.
| 35.94382 | 167 | 0.72085 | kor_Hang | 1.00001 |
08b127fa1e7e17184ed2369540ed556eb8fe347e | 1,118 | md | Markdown | src/uk/2016-04/01/03.md | PrJared/sabbath-school-lessons | 94a27f5bcba987a11a698e5e0d4279b81a68bc9a | [
"MIT"
] | 68 | 2016-10-30T23:17:56.000Z | 2022-03-27T11:58:16.000Z | src/uk/2016-04/01/03.md | PrJared/sabbath-school-lessons | 94a27f5bcba987a11a698e5e0d4279b81a68bc9a | [
"MIT"
] | 367 | 2016-10-21T03:50:22.000Z | 2022-03-28T23:35:25.000Z | src/uk/2016-04/01/03.md | OsArts/Bible-study | cfcefde42e21795e217d192a8b7a703ebb7a6c01 | [
"MIT"
] | 109 | 2016-08-02T14:32:13.000Z | 2022-03-31T10:18:41.000Z | ---
title: НЕЩАСЛИВІ ЗАВЕРШЕННЯ
date: 26/09/2016
---
### НЕЩАСЛИВІ ЗАВЕРШЕННЯ
Книга Йова наголошує, що все закінчується добре для патріарха, котрий помер «старим та насиченим днями». Однак усі ми знаємо, що далеко не в усіх людей життєвий шлях закінчується настільки благополучно. Навіть ті, хто був вірний, чесний і порядний, не завжди завершували своє життя так, як Йов.
Як склалася доля наступних біблійних персонажів?
```Авель (Бут. 4:8)```
```Урія (2 Сам. 11:17)```
```Ілій (1 Сам. 4:18)```
```Цар Йосія (2 Хронік 35:22-24)```
```Іван Хреститель (Матв. 14:10)```
```Степан (Дії 7:59, 60)```
Як бачимо, Біблія рясніє історіями з нещасливими завершеннями. І це тому, що саме життя сповнене таких історій. Один приймає мученицьку смерть за добру справу, інший помирає від страшної хвороби, а ще інший проводить решту своїх днів у стражданнях. Мало людей проходить через свої випробування так тріумфально, як Йов. Нечасто в людей життя закінчується так добре, як у Йова. І, звичайно ж, про це говорить не тільки Біблія.
```Які історії з нещасливим завершенням знаєте ви? Чого навчилися з них?``` | 43 | 424 | 0.737925 | ukr_Cyrl | 0.999992 |
08b208ba1452e7fff6fc4f0767bcb395cc4f1fd6 | 30 | md | Markdown | README.md | arthur-barbosa18/aulaGabriel | 0b1998f7153fe18a57e48c53bbfd15e1faac8476 | [
"MIT"
] | null | null | null | README.md | arthur-barbosa18/aulaGabriel | 0b1998f7153fe18a57e48c53bbfd15e1faac8476 | [
"MIT"
] | null | null | null | README.md | arthur-barbosa18/aulaGabriel | 0b1998f7153fe18a57e48c53bbfd15e1faac8476 | [
"MIT"
] | null | null | null | # aulaGabriel
aula ao gabriel
| 10 | 15 | 0.8 | por_Latn | 0.971697 |
08b20c421d233d84351de829bc3f446706ef4085 | 119 | md | Markdown | README.md | MaksimPuzyrkov/cheatsheet-helper | a1f524cf719bf39c8655b598ddd8e256302b2679 | [
"MIT"
] | null | null | null | README.md | MaksimPuzyrkov/cheatsheet-helper | a1f524cf719bf39c8655b598ddd8e256302b2679 | [
"MIT"
] | null | null | null | README.md | MaksimPuzyrkov/cheatsheet-helper | a1f524cf719bf39c8655b598ddd8e256302b2679 | [
"MIT"
] | null | null | null | # cheatsheet-helper
Small program to display cheat sheets (or other quick help information) for foreground application
| 39.666667 | 98 | 0.831933 | eng_Latn | 0.98713 |
08b26085eeb06c84cddfca046ee4c89337cf4008 | 1,591 | md | Markdown | creator/ScriptAPI/Minecraft/Rideable.md | mooremg/minecraft-creator | 23c5dfb1f6f69c077f3a22cf8a5b07808a3db45e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | creator/ScriptAPI/Minecraft/Rideable.md | mooremg/minecraft-creator | 23c5dfb1f6f69c077f3a22cf8a5b07808a3db45e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | creator/ScriptAPI/Minecraft/Rideable.md | mooremg/minecraft-creator | 23c5dfb1f6f69c077f3a22cf8a5b07808a3db45e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
# DO NOT TOUCH — This file was automatically generated. See https://github.com/Mojang/MinecraftScriptingApiDocsGenerator to modify descriptions, examples, etc.
author: jakeshirley
ms.author: jashir
ms.prod: gaming
title: Minecraft.Rideable Class
description: Contents of the Minecraft.Rideable class.
---
# Rideable Class
>[!IMPORTANT]
>These APIs are experimental as part of GameTest Framework. As with all experiments, you may see changes in functionality in updated Minecraft versions. Check the Minecraft Changelog for details on any changes to GameTest Framework APIs.
## Properties
### **id** - `string`
### **seatCount** - `number`
### **crouchingSkipInteract** - `boolean`
### **interactText** - `string`
### **familyTypes** - `array`
### **controllingSeat** - `number`
### **pullInEntities** - `boolean`
### **riderCanInteract** - `boolean`
### **seats** - `array`
## Methods
- [addRider](#addrider)
- [ejectRider](#ejectrider)
- [ejectRiders](#ejectriders)
### **addRider**
`
addRider(rider: Entity): boolean
`
#### Arguments
| Param | Type | Description |
| :--- | :--- | :---: |
| **rider** | [*Entity*](Entity.md) | - |
Returns *boolean*
> [!WARNING]
> This function can throw errors.
### **ejectRider**
`
ejectRider(rider: Entity): void
`
#### Arguments
| Param | Type | Description |
| :--- | :--- | :---: |
| **rider** | [*Entity*](Entity.md) | - |
Returns *undefined*
> [!WARNING]
> This function can throw errors.
### **ejectRiders**
`
ejectRiders(): void
`
Returns *undefined*
> [!WARNING]
> This function can throw errors.
| 16.572917 | 237 | 0.651791 | eng_Latn | 0.499174 |
08b2f7aa53d6a9b9db4c009236050a30f8ba574e | 870 | md | Markdown | README.md | inage782/freee-gem | 288bc5bce0907b31322762d9ee2d2159f48f1a9d | [
"MIT"
] | null | null | null | README.md | inage782/freee-gem | 288bc5bce0907b31322762d9ee2d2159f48f1a9d | [
"MIT"
] | null | null | null | README.md | inage782/freee-gem | 288bc5bce0907b31322762d9ee2d2159f48f1a9d | [
"MIT"
] | 1 | 2018-10-15T14:39:41.000Z | 2018-10-15T14:39:41.000Z | # Freee
Ruby implementation of the freee API.
## Installation
Add this line to your application's Gemfile:
gem 'freee'
And then execute:
$ bundle
Or install it yourself as:
$ gem install freee
## Usage
```sh
> export FREEE_CLIENT_ID=XXXXX
> export FREEE_SECRET_KEY=XXXXX
> export FREEE_APPLICATION_TOKEN=XXXXX
> irb
> require 'freee'
> Freee::Base.set_env
> Freee::User.me
{"user"=>{"email"=>"hoge@example.com", "display_name"=>nil, "first_name"=>nil, "last_name"=>nil, "first_name_kana"=>nil, "last_name_kana"=>nil}}
```
### Generate token
```
> freee token
```
## Contributing
1. Fork it ( https://github.com/futoase/freee/fork )
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create a new Pull Request
| 19.333333 | 144 | 0.698851 | eng_Latn | 0.478325 |
08b308c24c13f8abba2d52b363e4ad8abf15f003 | 504 | md | Markdown | openbanking-api-docs/docu/docs/CreditCheckEligibility2.md | thlaegler/openbanking | 924a29ac8c0638622fba7a5674c21c803d6dc5a9 | [
"MIT"
] | null | null | null | openbanking-api-docs/docu/docs/CreditCheckEligibility2.md | thlaegler/openbanking | 924a29ac8c0638622fba7a5674c21c803d6dc5a9 | [
"MIT"
] | 6 | 2019-10-20T18:56:35.000Z | 2021-12-09T21:41:46.000Z | openbanking-api-docs/docu/docs/CreditCheckEligibility2.md | thlaegler/openbanking | 924a29ac8c0638622fba7a5674c21c803d6dc5a9 | [
"MIT"
] | null | null | null |
# CreditCheckEligibility2
## Properties
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**notes** | **List<String>** | Optional additional notes to supplement the CreditCheck details | [optional]
**scoringType** | [**ScoringTypeEnum**](#ScoringTypeEnum) | Opening Credit Scoring Type (Hard or Soft) | [optional]
<a name="ScoringTypeEnum"></a>
## Enum: ScoringTypeEnum
Name | Value
---- | -----
HARD | "Hard"
SOFT | "Soft"
| 25.2 | 116 | 0.603175 | kor_Hang | 0.295342 |
08b39c887d0b4c4093b8ca07aea0f3abe9b54f2e | 2,223 | md | Markdown | docs/parallel/openmp/2-6-4-atomic-construct.md | svick/cpp-docs | 76fd30ff3e0352e2206460503b61f45897e60e4f | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-04-18T12:54:41.000Z | 2021-04-18T12:54:41.000Z | docs/parallel/openmp/2-6-4-atomic-construct.md | Mikejo5000/cpp-docs | 4b2c3b0c720aef42bce7e1e5566723b0fec5ec7f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/parallel/openmp/2-6-4-atomic-construct.md | Mikejo5000/cpp-docs | 4b2c3b0c720aef42bce7e1e5566723b0fec5ec7f | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-07-11T13:20:45.000Z | 2020-07-11T13:20:45.000Z | ---
title: "2.6.4 atomic Construct | Microsoft Docs"
ms.custom: ""
ms.date: "11/04/2016"
ms.technology: ["cpp-parallel"]
ms.topic: "conceptual"
dev_langs: ["C++"]
ms.assetid: e4232ef1-4058-42ce-9de0-0ca788312aba
author: "mikeblome"
ms.author: "mblome"
ms.workload: ["cplusplus"]
---
# 2.6.4 atomic Construct
The `atomic` directive ensures that a specific memory location is updated atomically, rather than exposing it to the possibility of multiple, simultaneous writing threads. The syntax of the `atomic` directive is as follows:
```
#pragma omp atomic new-lineexpression-stmt
```
The expression statement must have one of the following forms:
*x binop*= *expr*
x++
++x
x--
--x
In the preceding expressions:
- *x* is an lvalue expression with scalar type.
- *expr* is an expression with scalar type, and it does not reference the object designated by *x*.
- `binop` is not an overloaded operator and is one of +, *, -, /, &, ^, |, <\<, or >>.
Although it is implementation-defined whether an implementation replaces all `atomic` directives with **critical** directives that have the same unique *name*, the `atomic` directive permits better optimization. Often hardware instructions are available that can perform the atomic update with the least overhead.
Only the load and store of the object designated by *x* are atomic; the evaluation of *expr* is not atomic. To avoid race conditions, all updates of the location in parallel should be protected with the `atomic` directive, except those that are known to be free of race conditions.
Restrictions to the `atomic` directive are as follows:
- All atomic references to the storage location x throughout the program are required to have a compatible type.
## Examples:
```
extern float a[], *p = a, b;
/* Protect against races among multiple updates. */
#pragma omp atomic
a[index[i]] += b;
/* Protect against races with updates through a. */
#pragma omp atomic
p[i] -= 1.0f;
extern union {int n; float x;} u;
/* ERROR - References through incompatible types. */
#pragma omp atomic
u.n++;
#pragma omp atomic
u.x -= 1.0f;
``` | 34.2 | 316 | 0.691858 | eng_Latn | 0.997221 |
08b40047c4470b558b1aa76eb71633187f54b388 | 3,293 | md | Markdown | README.md | fetis/react-input-range | 9e653881e84b90090ce7d8c598ea0d261149e5a9 | [
"MIT"
] | 1 | 2021-04-29T19:19:23.000Z | 2021-04-29T19:19:23.000Z | README.md | jedwards1211/react-input-range | 9e653881e84b90090ce7d8c598ea0d261149e5a9 | [
"MIT"
] | null | null | null | README.md | jedwards1211/react-input-range | 9e653881e84b90090ce7d8c598ea0d261149e5a9 | [
"MIT"
] | 1 | 2017-12-27T18:22:56.000Z | 2017-12-27T18:22:56.000Z | # react-input-range
`InputRange` is a React component allowing users to input a numeric value within a predefined range. It can accept a single value, or a range of values (start/end). By default, basic styles are applied, but can be overridden depending on your design requirements.
## Demo
A CodePen demo is available [here](http://codepen.io/davidchin/full/GpNvqw/).
## Installation
1. Install `react-input-range` using npm. `npm install react-input-range`
2. Import `react-input-range` to use `InputRange` component.
3. Optionally, import `react-input-range.css` if you want to apply the default styling.
4. Depending on your browser support requirement, `babel-core/polyfill` or `core-js/es6` polyfill might be needed.
## Usage
If accepting a range of values:
```{js}
import React from 'react';
import ReactDOM from 'react-dom';
import InputRange from 'react-input-range';
class App extends React.Component {
constructor(props) {
super(props);
this.state = {
values: {
min: 2,
max: 10,
},
};
}
handleValuesChange(component, values) {
this.setState({
values: values,
});
}
render() {
return (
<InputRange
maxValue={20}
minValue={0}
value={this.state.values}
onChange={this.handleValuesChange.bind(this)}
/>
);
}
}
ReactDOM.render(
<App />,
document.getElementById('app')
);
```
If accepting a single value, pass a number to `value` prop, i.e.:
```{js}
<InputRange
maxValue={20}
minValue={0}
value={this.state.value}
onChange={this.handleValueChange.bind(this)}
/>
```
### Options
Property | Type | Description
:-----------------------|:-----------------------------------|:----------------------------------
ariaLabelledby |string |`aria-labelledby` attribute
ariaControls |string |`aria-controls` attribute
classNames |Object.<string> |CSS class names
defaultValue |number | Object.<number> |Default value(s)
disabled |boolean |Disabled or not
formatLabel |Function |Label formatter
labelPrefix |string |Label prefix
labelSuffix |string |Label suffix
maxValue |number |Maximum value it can accept
minValue |number |Minimum value it can accept
name |string |Name of `form` input
onChange |Function |`onChange` callback (required)
onChangeComplete |Function |`onChangeComplete` callback
step |number |Increment/decrement value
value |number | Object.<number> |Current value(s) (required)
## Development
If you want to work on this project locally, you need to grab all of its dependencies.
```
npm install && bundle install
```
After that, you should be able run
```
npm start
```
Contributions are welcome. :)
| 32.284314 | 263 | 0.557243 | eng_Latn | 0.8707 |
08b40be8320e4a88cf1695c0378d64cf74009ada | 548 | md | Markdown | README.md | derui/org-roam-protocol-installer | 4664b902f9762571ac22f7df96cd0f94b13051c0 | [
"MIT"
] | null | null | null | README.md | derui/org-roam-protocol-installer | 4664b902f9762571ac22f7df96cd0f94b13051c0 | [
"MIT"
] | null | null | null | README.md | derui/org-roam-protocol-installer | 4664b902f9762571ac22f7df96cd0f94b13051c0 | [
"MIT"
] | null | null | null | # Org Roam protocol installer #
The deadly simple program to install org-protocol for [org-roam](https://www.orgroam.com/manual.html#Roam-Protocol) .
# Usage #
```shell
# install for linux
$ org-roam-protocol-install linux install
# uninstall configuration for linux
$ org-roam-protocol-install linux uninstall
# install for linux
$ org-roam-protocol-install macos install --emacsclient-path <full path of emacsclient path>
```
# Contribute #
## Development ##
```shell
# build
$ cargo build
# test
$ cargo test
```
# License #
MIT License
| 18.266667 | 117 | 0.731752 | eng_Latn | 0.365343 |
08b4cc9c2d97616746a7a44fdd4457ddfc4f750a | 72 | md | Markdown | README.md | Subr1ata/DMDW-Lab | 9543f1167a93df0d1cc18c1eca27bff7843e91f5 | [
"Apache-2.0"
] | null | null | null | README.md | Subr1ata/DMDW-Lab | 9543f1167a93df0d1cc18c1eca27bff7843e91f5 | [
"Apache-2.0"
] | null | null | null | README.md | Subr1ata/DMDW-Lab | 9543f1167a93df0d1cc18c1eca27bff7843e91f5 | [
"Apache-2.0"
] | null | null | null | # Name:-Subrata Mukherjee
# Roll no:-18cse042
# Online class:- Group C1
| 18 | 25 | 0.722222 | hun_Latn | 0.318774 |
08b5a962173d3781840769cb659a68320d2808df | 445 | md | Markdown | waveformview/build/markdown/space.siy.waveformview/-r/color/abc_hint_foreground_material_dark.md | AnwarShahriar/WaveFormViewDemo | c710b2d2e592ea2dae04b8793b4e625b8b2b7acc | [
"Apache-2.0"
] | 42 | 2018-04-01T04:53:16.000Z | 2022-03-25T13:26:39.000Z | waveformview/build/markdown/space.siy.waveformview/-r/color/abc_hint_foreground_material_dark.md | AnwarShahriar/WaveFormViewDemo | c710b2d2e592ea2dae04b8793b4e625b8b2b7acc | [
"Apache-2.0"
] | 13 | 2019-05-27T15:54:24.000Z | 2021-02-23T20:46:28.000Z | waveformview/build/markdown/space.siy.waveformview/-r/color/abc_hint_foreground_material_dark.md | mo3rfan/WaveFormViewDemo | 0a27395c8b59d7d33c3cf909ca0e3e3a542017a4 | [
"Apache-2.0"
] | 13 | 2018-05-12T07:33:04.000Z | 2022-03-07T23:46:11.000Z | [space.siy.waveformview](../../index.md) / [R](../index.md) / [color](index.md) / [abc_hint_foreground_material_dark](./abc_hint_foreground_material_dark.md)
# abc_hint_foreground_material_dark
`static var abc_hint_foreground_material_dark: `[`Int`](https://kotlinlang.org/api/latest/jvm/stdlib/kotlin/-int/index.html)
`static var abc_hint_foreground_material_dark: `[`Int`](https://kotlinlang.org/api/latest/jvm/stdlib/kotlin/-int/index.html) | 74.166667 | 157 | 0.777528 | deu_Latn | 0.097423 |
08b6a8a401b4555f64ea8a013a7c14e00469d4da | 930 | md | Markdown | packages/dpctrl-fguicc/CHANGELOG.md | gamlittle/EasyGameFrameworkOpen | 9f99c2cc03e67daec4039fdf0e25acbd45dd1bd3 | [
"MIT"
] | 187 | 2020-11-30T02:24:43.000Z | 2022-03-28T12:16:29.000Z | packages/dpctrl-fguicc/CHANGELOG.md | gamlittle/EasyGameFrameworkOpen | 9f99c2cc03e67daec4039fdf0e25acbd45dd1bd3 | [
"MIT"
] | 4 | 2021-01-11T08:11:30.000Z | 2022-03-01T07:45:22.000Z | packages/dpctrl-fguicc/CHANGELOG.md | gamlittle/EasyGameFrameworkOpen | 9f99c2cc03e67daec4039fdf0e25acbd45dd1bd3 | [
"MIT"
] | 58 | 2020-11-30T14:28:45.000Z | 2022-03-16T13:17:24.000Z | # Change Log
All notable changes to this project will be documented in this file.
See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
## [0.3.2](https://github.com/AILHC/EasyGameFrameworkOpen/compare/@ailhc/dpctrl-fguicc@0.3.1...@ailhc/dpctrl-fguicc@0.3.2) (2021-06-20)
**Note:** Version bump only for package @ailhc/dpctrl-fguicc
## [0.3.1](https://github.com/AILHC/EasyGameFrameworkOpen/compare/@ailhc/dpctrl-fguicc@0.2.0...@ailhc/dpctrl-fguicc@0.3.1) (2021-06-10)
**Note:** Version bump only for package @ailhc/dpctrl-fguicc
# 0.3.0 (2021-06-02)
### Features
* 增加creator3.0demo以及3.0的fgui适配 ([40f126d](https://github.com/AILHC/EasyGameFrameworkOpen/commit/40f126d5edf7624f3be70fcd119030d62de06112))
# 0.2.0 (2021-05-31)
### Features
* 增加creator3.0demo以及3.0的fgui适配 ([40f126d](https://github.com/AILHC/EasyGameFrameworkOpen/commit/40f126d5edf7624f3be70fcd119030d62de06112))
| 23.846154 | 138 | 0.749462 | kor_Hang | 0.192798 |