hexsha
stringlengths 40
40
| size
int64 5
1.04M
| ext
stringclasses 6
values | lang
stringclasses 1
value | max_stars_repo_path
stringlengths 3
344
| max_stars_repo_name
stringlengths 5
125
| max_stars_repo_head_hexsha
stringlengths 40
78
| max_stars_repo_licenses
sequencelengths 1
11
| max_stars_count
int64 1
368k
⌀ | max_stars_repo_stars_event_min_datetime
stringlengths 24
24
⌀ | max_stars_repo_stars_event_max_datetime
stringlengths 24
24
⌀ | max_issues_repo_path
stringlengths 3
344
| max_issues_repo_name
stringlengths 5
125
| max_issues_repo_head_hexsha
stringlengths 40
78
| max_issues_repo_licenses
sequencelengths 1
11
| max_issues_count
int64 1
116k
⌀ | max_issues_repo_issues_event_min_datetime
stringlengths 24
24
⌀ | max_issues_repo_issues_event_max_datetime
stringlengths 24
24
⌀ | max_forks_repo_path
stringlengths 3
344
| max_forks_repo_name
stringlengths 5
125
| max_forks_repo_head_hexsha
stringlengths 40
78
| max_forks_repo_licenses
sequencelengths 1
11
| max_forks_count
int64 1
105k
⌀ | max_forks_repo_forks_event_min_datetime
stringlengths 24
24
⌀ | max_forks_repo_forks_event_max_datetime
stringlengths 24
24
⌀ | content
stringlengths 5
1.04M
| avg_line_length
float64 1.14
851k
| max_line_length
int64 1
1.03M
| alphanum_fraction
float64 0
1
| lid
stringclasses 191
values | lid_prob
float64 0.01
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
05529e32c81ab13e712e6c5e50cf0e0562b2e216 | 839 | md | Markdown | README.md | drayanaindra/lite-api-dir | c1a997667d9faee4153da51f860bdd41d7b31b03 | [
"CC0-1.0"
] | 3 | 2015-11-05T03:42:05.000Z | 2016-02-23T14:16:26.000Z | README.md | drayanaindra/falcon-bootstrap | c1a997667d9faee4153da51f860bdd41d7b31b03 | [
"CC0-1.0"
] | null | null | null | README.md | drayanaindra/falcon-bootstrap | c1a997667d9faee4153da51f860bdd41d7b31b03 | [
"CC0-1.0"
] | null | null | null | # Falcon Bootstrap
**Falcon Bootstrap** is bootstrapping project directory for micro framework [falcon](http://falconframework.org/), everybody can develop simple API. And what you need for this ? Just basic skill of Python, and read more documentation. In this project, i create simple CRUD apps **contact**. Let's see what will you can do with this project.
preparing to using this project
- clone this project
- create virtual environment
- install requirements.txt
- do chmod +x for file `run.py`
- run `./run.py`
this project using database [mongodb](https://www.mongodb.org/) with [mongoengine](mongoengine-odm.readthedocs.or) for Object-Document Mapper. And if you prefer using relational database, you can using [SQL Alchemy](http://docs.sqlalchemy.org/en/rel_0_9/orm/tutorial.html) for SQL Toolkit & Object Relational Mapper.
| 59.928571 | 340 | 0.77354 | eng_Latn | 0.963049 |
0552af9912763d75359eb71d6c2778faa1ed793b | 1,767 | md | Markdown | content/post/code/2018-02-04-testing-with-jest.md | thomasphillips3/blogstrathomas | 37a61926867c11db838937571f87b2eb370629d8 | [
"MIT"
] | null | null | null | content/post/code/2018-02-04-testing-with-jest.md | thomasphillips3/blogstrathomas | 37a61926867c11db838937571f87b2eb370629d8 | [
"MIT"
] | 1 | 2018-01-19T18:16:33.000Z | 2018-01-19T18:16:33.000Z | content/post/code/2018-02-04-testing-with-jest.md | thomasphillips3/blogstrathomas | 37a61926867c11db838937571f87b2eb370629d8 | [
"MIT"
] | null | null | null | ---
day: '114'
title: Testing with Jest
date: 2018-02-04T21:52:29.893Z
tags:
- 100daysofcode
- jest
- javascript
- react-native
- testing
- automation
categories: code
weight: 0
---
# Day 114
## Today's Progress
Created automated tests with Jest
## Thoughts
I have been working on the Android portion of automated tests for the past couple of weeks. I think Jest is the cross-platform way of validating the app from the jump, instead of depending on Espresso for Android, and UI Automation for iOS.
Building the test projects from scratch gave me some insight on how to better use **`npm`** and **`nvm`**. I had initially tried to run my js from the Terminal, and kept getting permission denied errors. After changing permissions on the files, I realized...I NEVER run JS from Terminal, always in a browser. So I came across [this question on SO](https://stackoverflow.com/a/28756251/270847), which told me to use Node (duh).
The first test was just verifying a sum. For the next one, I was trying to do UI testing with Snapshots. I added a new test, but realized I hadn't added React-Native to the project. I used npm to install it, but I had an old version of node, so the install failed. I used nvm to install the right version of node.
## Links
* [Is it possible to run JavaScript files from the command line?](https://stackoverflow.com/a/28756251/270847)
* [Integration with Existing Apps (React Native)](https://facebook.github.io/react-native/docs/integration-with-existing-apps.html)
* [Jest Getting Started](https://facebook.github.io/jest/docs/en/getting-started.html)
* [Testing React Native with the \*new\* Jest — Part I](https://blog.callstack.io/unit-testing-react-native-with-the-new-jest-i-snapshots-come-into-play-68ba19b1b9fe)
| 50.485714 | 426 | 0.754386 | eng_Latn | 0.98216 |
0552e3ec284dce4db11044cf59e86708a6607b4b | 60 | md | Markdown | README.md | ringor/screeps | b6b27e7396e064d41a5875a9f544141a23a4f2c7 | [
"MIT"
] | null | null | null | README.md | ringor/screeps | b6b27e7396e064d41a5875a9f544141a23a4f2c7 | [
"MIT"
] | null | null | null | README.md | ringor/screeps | b6b27e7396e064d41a5875a9f544141a23a4f2c7 | [
"MIT"
] | null | null | null | # screeps
My first little steps in the world of 'screeps'.
| 20 | 49 | 0.733333 | eng_Latn | 0.999195 |
05558548b2fe1faaec829601631893f0a927020e | 55 | md | Markdown | README.md | phated/gitkit-example | 50df134060de1bf1d13c2ac8100464213e28bd97 | [
"MIT"
] | null | null | null | README.md | phated/gitkit-example | 50df134060de1bf1d13c2ac8100464213e28bd97 | [
"MIT"
] | null | null | null | README.md | phated/gitkit-example | 50df134060de1bf1d13c2ac8100464213e28bd97 | [
"MIT"
] | null | null | null | # gitkit-example
WIP gitkit experiments and playground
| 18.333333 | 37 | 0.836364 | eng_Latn | 0.984091 |
05559b2250e33996a8aaa15c98c5335bb8393123 | 2,534 | md | Markdown | _posts/2018-01-22-Quizzes.md | Archlad/Archlad.github.io | 92f5cf78cdb6110313d7e263b33e876fb87e8375 | [
"MIT"
] | null | null | null | _posts/2018-01-22-Quizzes.md | Archlad/Archlad.github.io | 92f5cf78cdb6110313d7e263b33e876fb87e8375 | [
"MIT"
] | null | null | null | _posts/2018-01-22-Quizzes.md | Archlad/Archlad.github.io | 92f5cf78cdb6110313d7e263b33e876fb87e8375 | [
"MIT"
] | null | null | null | ---
title: Quizzes
layout: post
author: archit.rakhade
permalink: /quizzes/
source-id: 10LZbpbPQegzZTmsSp2xZk1O8buF9J4CUPvmO1eC3ThU
published: true
---
<table>
<tr>
<td>Title</td>
<td>Making Quizzes</td>
<td>Date</td>
<td>20/01/18</td>
</tr>
</table>
<table>
<tr>
<td>Starting point:</td>
<td>A blank page on google docs </td>
</tr>
<tr>
<td>Target for this lesson?</td>
<td>To make 6 questions and answers for a quiz similar to a Buzzfeed Quiz</td>
</tr>
<tr>
<td>Did I reach my target?
(add details to "Lesson Review")</td>
<td>No I only managed to complete 3 questions.</td>
</tr>
</table>
<table>
<tr>
<td>Lesson Review</td>
</tr>
<tr>
<td>How did I learn? What strategies were effective? </td>
</tr>
<tr>
<td>At the start of the lesson we were doing quizzes on Buzzfeed and that was very fun and also helpful. It helped me to comprehend how the quizzes worked and how they figured out what type of friend we are for example or how much we like animals. It also made me think about how it has been coded to take in our answers and input and figure out the best suitable option for us. I listened to best and perfect teacher in the world to ever exist in eternity of the intergalactic galaxy and the cosmos (aka Mr Keen) and used it to help me work out what to do and what the questions should be. </td>
</tr>
<tr>
<td>What limited my learning? Which habits do I need to work on? </td>
</tr>
<tr>
<td>What limited my learning was the amount of times I was distracted by the people sitting next to me. One of my friends needed help on the quiz he was doing which was about cricket so I did not manage to get as much work done as I wanted to. Nevertheless, I did struggle thinking of questions that the majority of people would be able to relate to and understood. Most of time I was just trying to think of the questions and also 5 possible answers for them.</td>
</tr>
<tr>
<td>What will I change for next time? How will I improve my learning?</td>
</tr>
<tr>
<td>Next time I will try to solely focus on my work and not pay attention to the problems of others not to say that I won't try to help slightly. This will maximise my efficiency of work completion and minimise the quantity of homework that I would be receiving thus saving time. Also I would hope to think quick and also not overthink the topic and just pick the first suitable idea that comes to mind and not the most perfect.</td>
</tr>
</table>
| 41.540984 | 601 | 0.707577 | eng_Latn | 0.99926 |
05559d59d39d0539511ae3042abe56765b54bac7 | 1,894 | md | Markdown | OVERDUE.md | Theodeus/www.html5rocks.com | df153ceca613213205e78d3f077019d8715779f4 | [
"Apache-2.0"
] | 4 | 2020-07-15T16:28:57.000Z | 2020-09-14T17:38:31.000Z | OVERDUE.md | Theodeus/www.html5rocks.com | df153ceca613213205e78d3f077019d8715779f4 | [
"Apache-2.0"
] | null | null | null | OVERDUE.md | Theodeus/www.html5rocks.com | df153ceca613213205e78d3f077019d8715779f4 | [
"Apache-2.0"
] | null | null | null | HTML5 Rocks Quarter Report for 2014-01-07
=========================================
Articles due this quater
------------------------
|Author|Article|Delivery date|Tech Writer|State|
|------|-------|-------------|-----------|-----|
|Paul Irish|[Mobile development with Chrome DevTools](https://github.com/html5rocks/www.html5rocks.com/issues/526)|2013-09-10||open
|Paul Irish|[Migrating a project to Grunt.js](https://github.com/html5rocks/www.html5rocks.com/issues/532)|2013-09-20||open
|Ilya Grigorik|[Optimizing Mobile Sites with TCP in mind](https://github.com/html5rocks/www.html5rocks.com/issues/496)|2013-09-30||open
|Paul Irish|[Guide to Remote Debugging](https://github.com/html5rocks/www.html5rocks.com/issues/643)|2013-11-16|@dr4b|open
|Matthew Gaunt|[Tooling for mobile web testing](https://github.com/html5rocks/www.html5rocks.com/issues/645)|2013-11-27|@dr4b|open
|Sam Dutton|[EME 101](https://github.com/html5rocks/www.html5rocks.com/issues/512)|2013-12-09|@scottrowe|open
|Alex Danilo|[Stopping the blocking: Eliminate render blocking resources](https://github.com/html5rocks/www.html5rocks.com/issues/509)|2013-12-11|@arthurevans|open
|Chris Wilson|[Understanding the viewport](https://github.com/html5rocks/www.html5rocks.com/issues/488)|2013-12-11|@arthurevans|open
|Paul Kinlan|[How to prioritize your page for visible content](https://github.com/html5rocks/www.html5rocks.com/issues/508)|2013-12-15|@arthurevans|open
|Pete LePage|[Update HTML5 Video Tutorial - http://www.html5rocks.com/en/tutorials/video/basics/](https://github.com/html5rocks/www.html5rocks.com/issues/771)|2013-12-18||open
|Chris Wilson|[Viewport units - a full width experience](https://github.com/html5rocks/www.html5rocks.com/issues/480)|2013-12-18|@arthurevans|open
|Eiji Kitamura|[Quota Management on browsers](https://github.com/html5rocks/www.html5rocks.com/issues/514)|2013-12-20|@dr4b|open
| 86.090909 | 175 | 0.741288 | yue_Hant | 0.731838 |
05564970c7a2697c55e152f83fea17352e0c1fe5 | 713 | md | Markdown | Web Application - Chatbot/README.md | rammya29/Hands-on-ML-Basic-to-Advance- | 2a408de70068e51f673389bca364e331a1574d8e | [
"MIT"
] | null | null | null | Web Application - Chatbot/README.md | rammya29/Hands-on-ML-Basic-to-Advance- | 2a408de70068e51f673389bca364e331a1574d8e | [
"MIT"
] | null | null | null | Web Application - Chatbot/README.md | rammya29/Hands-on-ML-Basic-to-Advance- | 2a408de70068e51f673389bca364e331a1574d8e | [
"MIT"
] | null | null | null | # Chatbot for Web Application
## Short Description
It is a Python web-based project, I am going to build a chatbot using deep learning and flask techniques.
The chatbot will be trained on the dataset which contains categories (intents), pattern and responses. We use a special artificial neural network (ANN)
to classify which category the user’s message belongs to and then we will give a random response from the list of responses.
chatbot using Flask, NLTK, Keras, Python, etc.
## File link
- Template - [Link]()
- Static - [Link]()
- data.json – [Link]()
- trainning.py – [Link]()
- Texts.pkl – [Link]()
- Labels.pkl – [Link]()
- model.h5 – [Link]()
- app.py - [Link]()
# Author
Rammya DharshiniK
| 26.407407 | 152 | 0.71108 | eng_Latn | 0.982232 |
05579ae6ca7ead41f0ef59330e2ba8857818076a | 2,774 | md | Markdown | _posts/2019-05-09-Download-strategic-management-of-professional-service-firms-theory-and-practice.md | Kirsten-Krick/Kirsten-Krick | 58994392de08fb245c4163dd2e5566de8dd45a7a | [
"MIT"
] | null | null | null | _posts/2019-05-09-Download-strategic-management-of-professional-service-firms-theory-and-practice.md | Kirsten-Krick/Kirsten-Krick | 58994392de08fb245c4163dd2e5566de8dd45a7a | [
"MIT"
] | null | null | null | _posts/2019-05-09-Download-strategic-management-of-professional-service-firms-theory-and-practice.md | Kirsten-Krick/Kirsten-Krick | 58994392de08fb245c4163dd2e5566de8dd45a7a | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
categories: Other
---
## Download Strategic management of professional service firms theory and practice book
He made the spell the old Changer had taught him long ago, and the other by a piece of iron pyrites fixed in the same way. but sometimes one can get into the reals. Negroes, being over and done with, while he was being carried from his bed up is no European inn there, the second-worst of the unknown lands in which her roaming spirit other species of the whale which still in pretty large numbers "Why don't you sit down?" As Preston rose from the chair, in places, Crawford could see no reason why it should have happened want to tell anyone what he had done to her. Junior's body betrayed him as before, "I'll know. Thanks for trying anyway. As the diameter of the tower shrank, wise men, snap. Mary's upon her arrival from Oregon. " of the position of these luminous arcs, he seizes the opportunity and runs from Here was the final knave of spades, and laughed. "I can't let you ruin my dancing career? I was hoping. Chukches here it may be mentioned in the last place that they were gas-flame bright, in those long ago days. The inner door opened and Lang pushed forwardвand right back into the airlock. meaningful look, seeking the source. He could also leave the car and follow Celestina on foot if she chose to stroll home from here. His head appeared too large for his body, but suddenly she was loath to have the facts put before her. YOU struck a Nina He had noted all seven names on the bassinets, mystic silvery runes on high branching strategic management of professional service firms theory and practice. "I guess I'm not in Kansas anymore. We're always on the move, this is useful, and services, which was now rare since the monkeats invariably got the worst of it. seriously his suggestion of dishonesty. Preston was denied his dramatic moment when she made only a strangled sound of as modeled here in trash and mold and mouse droppings. They enslave all planets in their path. ah, [intending] for certain of the lands, right. you can bet it's not warm, Dr, having stopped by for a quick refresher on his way home some two hours previously. The state troopers got there hi fifteen minutes, then row furiously for some minutes rest themselves again, the past who had been taken prisoner after being shipwrecked on strategic management of professional service firms theory and practice coast of great swallow's nest from the little ledge to which it is fixed, lifted the lid. Number. JOANNA RUSS He took the word with strategic management of professional service firms theory and practice visible shock, F. When the early-winter twilight gave way to night, Mickey Mouseв they all drew Sinsemilla into their light. | 308.222222 | 2,630 | 0.79416 | eng_Latn | 0.999969 |
0558476331a9140f895d36e879751c3b4f28651c | 858 | md | Markdown | docs/markdown/zh/icon.md | neoliu6/at-ui | e1da40623675cb22a48aa6291804a871d887a2ee | [
"MIT"
] | 2,511 | 2017-08-15T04:09:15.000Z | 2022-03-29T03:24:21.000Z | docs/markdown/zh/icon.md | neoliu6/at-ui | e1da40623675cb22a48aa6291804a871d887a2ee | [
"MIT"
] | 116 | 2017-08-22T10:51:19.000Z | 2022-02-20T16:14:09.000Z | docs/markdown/zh/icon.md | neoliu6/at-ui | e1da40623675cb22a48aa6291804a871d887a2ee | [
"MIT"
] | 305 | 2017-08-29T11:38:09.000Z | 2022-03-03T15:31:33.000Z | # Icon 图标
----
语义化的矢量图形，`AT-UI` 使用开源的 [Feather](https://feathericons.com/) 作为图标库，并制作成了 `icon font`。`Feather` 使用的是 `24x24` 的尺寸，拥有一致的圆角，一致的笔画宽度，确保整个图标系统保持视觉上的统一性。
## 如何使用
使用 `class="icon"` 来声明图标，具体图标的名称请 `copy` 相应的标签
:::demo
```html
<i class="icon icon-zoom-in"></i>
<i class="icon icon-zoom-out"></i>
<i class="icon icon-check"></i>
<i class="icon icon-x"></i>
```
:::
## 图标示例
### 主要
<icon-list type="core"></icon-list>
### 媒体控制
<icon-list type="media"></icon-list>
### 通信
<icon-list type="communication"></icon-list>
### 照片
<icon-list type="photo"></icon-list>
### 地理位置
<icon-list type="location"></icon-list>
### 天气
<icon-list type="weather"></icon-list>
### 箭头
<icon-list type="arrows"></icon-list>
### LOGO
<icon-list type="logos"></icon-list>
<style lang="scss" scoped>
.icon {
font-size: 20px;
margin-right: 10px;
}
</style>
| 14.065574 | 145 | 0.624709 | yue_Hant | 0.164396 |
0558699abc89bf0b3a678a05fab1a4998cc12766 | 1,923 | md | Markdown | doc/src/js/dom/querySelectorLive.md | nikclayton/sugar | bd21c69b6c227874291221afcf7d0f5f03ea409e | [
"MIT"
] | null | null | null | doc/src/js/dom/querySelectorLive.md | nikclayton/sugar | bd21c69b6c227874291221afcf7d0f5f03ea409e | [
"MIT"
] | null | null | null | doc/src/js/dom/querySelectorLive.md | nikclayton/sugar | bd21c69b6c227874291221afcf7d0f5f03ea409e | [
"MIT"
] | null | null | null | # querySelectorLive
Observe the dom to get all the elements that matches a passed css selector at any point in time.
Be warned that this use the mutation observer API and will monitor all the document for new nodes. Make sure to use it
when you don't have the chance to use the custom elements API instead
### Parameters
Name | Type | Description | Status | Default
------------ | ------------ | ------------ | ------------ | ------------
selector | **{ [String](https://developer.mozilla.org/fr/docs/Web/JavaScript/Reference/Objets_globaux/String) }** | The css selector that we are interested in | required |
cb | **{ [Function](https://developer.mozilla.org/fr/docs/Web/JavaScript/Reference/Objets_globaux/Function) }** | The function to call with the newly added node | required |
settings | **{ [Object](https://developer.mozilla.org/fr/docs/Web/JavaScript/Reference/Objets_globaux/Object) }** | An optional settings object to specify things like the rootNode to monitor, etc... | optional | {}
### Example
```js
import querySelectorLive from 'coffeekraken-sugar/js/dom/querySelectorLive'
querySelectorLive('.my-cool-item', (node) => {
// do something here with the detected node
});
```
Author : Olivier Bossel [[email protected]](mailto:[email protected]) [https://olivierbossel.com](https://olivierbossel.com)
## Attributes
Here's the list of available attribute(s).
### settings.rootNode
The root node used to detect newly added nodes within
Type : **{ [HTMLElement](https://developer.mozilla.org/fr/docs/Web/API/HTMLElement) }**
Default : **document**
### settings.once
Specify if want to detect the node only once. Mean that if the node is removed from the dom and added again, it will not be detected again.
Type : **{ [Boolean](https://developer.mozilla.org/fr/docs/Web/JavaScript/Reference/Objets_globaux/Boolean) }**
Default : **true** | 40.914894 | 222 | 0.702548 | eng_Latn | 0.80133 |
05599011fd19b72766c8060c77c10dd9ff36cf2a | 793 | md | Markdown | README.md | jclark017/applehealthdata | da825124011fa46f8309203b8a25b80ab5f062e8 | [
"MIT"
] | 56 | 2016-06-05T15:41:02.000Z | 2022-03-02T21:51:50.000Z | README.md | jclark017/applehealthdata | da825124011fa46f8309203b8a25b80ab5f062e8 | [
"MIT"
] | 1 | 2021-12-30T14:06:18.000Z | 2021-12-30T14:06:18.000Z | README.md | jclark017/applehealthdata | da825124011fa46f8309203b8a25b80ab5f062e8 | [
"MIT"
] | 21 | 2017-02-04T13:06:20.000Z | 2021-12-29T18:56:42.000Z | # applehealthdata
Extract Data from Apple Health App's XML Export
Discussed in blog posts at http://tdda.info, including:
* v1.0: http://www.tdda.info/in-defence-of-xml-exporting-and-analysing-apple-health-data
* v1.1: http://www.tdda.info/first-test
* v1.2: http://www.tdda.info/unit-tests (pending)
* v1.3: http://www.tdda.info/extracting-more-apple-health-data (pending)
Various commits are tagged with version numbers of the form v1.0 etc,
so you can check out a particular version with
$ git checkout v1.0
etc., provided you pull the tags
$ git pull --tags
if your copy of git isn't set up to do this by default.
NOTE: this will leave you in a "detached HEAD" state in git.
You can get back to HEAD when you're finished by saying:
$ git checkout master
| 24.78125 | 90 | 0.72005 | eng_Latn | 0.87983 |
0559a70cbfd79b482ce7396169d4e2b42c9be06c | 236 | md | Markdown | .github/pull_request_template.md | google/horologist | 709007ccb1e77f89fd7e25dc50910bc41df70aa0 | [
"Apache-2.0"
] | 3 | 2022-03-22T19:50:25.000Z | 2022-03-25T08:29:52.000Z | .github/pull_request_template.md | google/horologist | 709007ccb1e77f89fd7e25dc50910bc41df70aa0 | [
"Apache-2.0"
] | 14 | 2022-03-18T17:46:29.000Z | 2022-03-31T09:14:41.000Z | .github/pull_request_template.md | google/horologist | 709007ccb1e77f89fd7e25dc50910bc41df70aa0 | [
"Apache-2.0"
] | 2 | 2022-03-18T17:43:38.000Z | 2022-03-22T19:50:26.000Z | #### WHAT
#### WHY
#### HOW
#### Checklist :clipboard:
- [ ] Add explicit visibility modifier and explicit return types for public declarations
- [ ] Run spotless check
- [ ] Run tests
- [ ] Update metalava's signature text files
| 15.733333 | 88 | 0.665254 | eng_Latn | 0.658908 |
055ab37cca3d474ee58f6da8649157f03c789c49 | 4,167 | md | Markdown | tests/dummy/app/templates/docs/components/vega-vis-container.md | aeroberts/ember-vega | 2b9d19ab60e102a1f2f963e0b7e8b87e4f290c85 | [
"MIT"
] | 8 | 2018-06-13T19:21:52.000Z | 2021-02-23T07:51:19.000Z | tests/dummy/app/templates/docs/components/vega-vis-container.md | aeroberts/ember-vega | 2b9d19ab60e102a1f2f963e0b7e8b87e4f290c85 | [
"MIT"
] | 11 | 2017-07-24T17:39:01.000Z | 2022-01-22T05:25:39.000Z | tests/dummy/app/templates/docs/components/vega-vis-container.md | aeroberts/ember-vega | 2b9d19ab60e102a1f2f963e0b7e8b87e4f290c85 | [
"MIT"
] | 2 | 2017-07-24T13:37:10.000Z | 2020-03-23T20:32:26.000Z | # Vega Vis Container
This component yields an object that contains three properties:
* `element` - the component's element.
* `dimensions` - component element's [`getBoundingClientRect`](https://developer.mozilla.org/en-US/docs/Web/API/Element/getBoundingClientRect).
* `vis` - a composed `vega-vis` component
## Dimensions Property
The `dimensions` is bound to the `window` `resize` event, so whenever the window resizes, the `dimensions` will be updated.
It's useful for computing aspect ratios making `vega-vis` responsive.
By default, `ui.vis` will have its `height` and `width` properties set to `dimensions.height` and `dimensions.width`, respectively.
{{#docs-demo as |demo|}}
{{#vega-vis-demo-basic as |spec|}}
{{#demo.example name="vega-vis-container-demo.hbs"}}
{{#vega-vis-container as |ui|}}
{{ui.vis
spec=spec
height=(div ui.dimensions.width 3)
}}
{{/vega-vis-container}}
{{/demo.example}}
{{/vega-vis-demo-basic}}
{{demo.snippet name="vega-vis-container-demo.hbs"}}
{{/docs-demo}}
Alternatively, a spec can have use the [`containerSize` expression](https://vega.github.io/vega/docs/expressions/#containerSize) to make the visualization responsive.
The example below show's width and height signals that update the when the windows resize event is triggered. If you have a `spec` that makes use of this feature, there is no need to use `vega-vis-container` component in this scenario.
```json
{
"signals": [
{
"name": "width",
"update": "(containerSize()[0] || 400)",
"on": [{
"events": {"source": "window", "type": "resize"},
"update": "containerSize()[0]"
}]
},
{
"name": "height",
"update": "(containerSize()[1] || 200)",
"on": [{
"events": {"source": "window", "type": "resize"},
"update": "containerSize()[1]"
}]
}
]
}
```
## Element Property
With the `element` property, the `vega-vis` can render the visualization in a different element from it's own. This helps with reducing the number of elements in the DOM and can help with debugging.
Note that a `tagName` property is passed to `vega-vis`, along with the `visContainer`. Since `vega-vis` will be rendering the visualization in a different element, setting the `tagName` to an empty string will prevent `vega-vis` from creating an element of its own.
By default, the yielded `ui.vis` will have `visContainer` set to `ui.element` and `tagName` set to an empty string.
{{#docs-demo as |demo|}}
{{#vega-vis-demo-basic as |spec|}}
{{#demo.example name="vega-vis-container-element-demo.hbs"}}
{{#vega-vis-container as |ui|}}
{{ui.vis
spec=spec
visContainer=ui.element
height=spec.height
tagName=""
}}
{{/vega-vis-container}}
{{/demo.example}}
{{/vega-vis-demo-basic}}
{{demo.snippet name="vega-vis-container-element-demo.hbs"}}
{{/docs-demo}}
## Vis Property
The `vis` property is a composed `vega-vis` component with some defaults set:
* The height and width is the yielded `dimensions.height` and `dimensions.width`. This will automatically make `vega-vis` responsive.
* The `vega-vis` `tagName` property is an empty string and `visContainer` property is the yielded `element`. This automatically reduces the number of elements.
Since `vis` is a composed component, any of the defaults can be overriden.
{{#docs-demo as |demo|}}
{{#vega-vis-demo-basic as |spec|}}
{{#demo.example name="vega-vis-container-vis-demo.hbs"}}
{{#vega-vis-container as |ui|}}
{{ui.vis
spec=spec
height=spec.height
}}
{{/vega-vis-container}}
{{/demo.example}}
{{/vega-vis-demo-basic}}
{{demo.snippet name="vega-vis-container-vis-demo.hbs"}}
{{/docs-demo}}
| 38.583333 | 265 | 0.605232 | eng_Latn | 0.942553 |
055af09d4356172ca397f33db3a64abee6ec3dfd | 29,009 | md | Markdown | _posts/2019-5-6-业务层框架spring(1).md | BaiWeiJieKu/BaiWeiJieKu.github.io | ac26b603442e84baee577f1328060a3e4369a778 | [
"MIT"
] | 1 | 2019-07-30T12:35:01.000Z | 2019-07-30T12:35:01.000Z | _posts/2019-5-6-业务层框架spring(1).md | BaiWeiJieKu/BaiWeiJieKu.github.io | ac26b603442e84baee577f1328060a3e4369a778 | [
"MIT"
] | null | null | null | _posts/2019-5-6-业务层框架spring(1).md | BaiWeiJieKu/BaiWeiJieKu.github.io | ac26b603442e84baee577f1328060a3e4369a778 | [
"MIT"
] | 7 | 2019-02-28T02:11:16.000Z | 2019-10-11T02:51:04.000Z | ---
layout: post
title: "业务层框架spring(1)"
categories: spring
tags: spring
author: 百味皆苦
music-id: 2602106546
---
* content
{:toc}
### HelloWorld
#### 概念
- Spring 是一个开源框架，Spring 是一个 IOC(DI) 和 AOP 容器框架
#### 优势
- spring框架有效的组织中间层对象（整合Struts，hibernate），实际上 Spring 自身也提供了展现层的 SpringMVC 和 持久层的 Spring JDBC
- spring实现了真正意义上的面向接口编程，可以实现组件之间的高度解耦
- spring提高了代码的可重用性
- spring为数据存储提供了一个一致的框架，简化了底层数据库的访问方式
- **轻量非侵入性的**：基于 Spring 开发的应用中的对象可以不依赖于 Spring 的 API
- **依赖注入**：IOC（inversion of control）和DI（dependency injection）是同一个概念。调用者不负责被调用者的实例创建工作，该工作由spring框架中的容器来负责。由于spring容器负责创建被调用者实例，实例创建后又负责将该实例注入调用者，因此称为依赖注入
```properties
调用者--->想调用一个对象实例--->spring容器创建所需要的实例对象--->把对象实例注入给调用者
```
- **AOP（aspect oriented programming）**：面向切面编程，他是OOP（面向对象编程）的补充和完善。在OOP中通过**封装，继承，多态**建立起多个对象之间的层次结构。但如果想为这些分散对象添加一些公共行为，OOP就很难实现了，因为OOP擅长的是定义从上到下的关系。恰巧，AOP解决了这个问题，它适合定义从左到右的关系。
- **容器**: Spring 是一个容器, 因为它包含并且管理应用对象的生命周期
- **框架**: Spring 实现了使用简单的组件配置组合成一个复杂的应用. 在 Spring 中可以使用 XML 和 Java 注解组合这些对象
#### 模块
- 核心容器（core container）
- 1）spring核心容器由**beans，core，context，expression language**模块组成
- 2）beans和core模块实现了spring框架的最基本功能，**规定了创建、配置和管理bean的方式**，提供了DI和IOC的特性
- 3）核心容器主要组件是BeanFactory类，他是**工厂模式**的实现，javabean的管理就由他负责。BeanFactory类通过IOC将应用程序的配置和依赖性规范与实际的应用程序代码相分离。
- 4）context模块建立在 core和beans模块之上，**该模块向spring框架提供了上下文信息**
- 5）expression language模块提供了一种强大的表达式语言来**访问和操纵运行时的对象**。支持设置和获取属性值、方法调用、访问数组、集合和索引、逻辑和算术运算、命名变量、根据名称从IOC容器中获取对象等功能。
- 数据访问/集成
- 1）数据访问/集成模块由JDBC、ORM、OXM、JMS和transaction几个模块组成
- 2）spring的JDBC模块对程式化的代码进行抽象，**提供了一个JDBC抽象层**，避免了开发者去面对复杂的API以及因释放数据库资源失败而引起的一系列问题
- 3）ORM模块为**对象关系映射**（object relative mapping）提供了集成层，这些API包括JPA、hibernate、mybatis，该模块可以将O/R映射框架与spring提供的特性进行组合来使用
- 4）transaction模块**提供了对声明式事务和编程事务的支持**，这些事务必须实现特定接口，并且对所有的POJO都适用
- Web模块
- 1）web模块包括web，servlet，Struts和portlet几个模块
- AOP模块
- 使用该模块可以定义方法拦截器和切点，**将代码按功能进行分离**，降低他们之间的耦合性
- Test模块
- 提供一致的ApplicationContexts并缓存这些上下文
#### 开发实例
- javabean（包含了getter和setter方法的java类）
```java
package com.atguigu.spring.helloworld;
public class HelloWorld {
private String user;
public HelloWorld() {
System.out.println("HelloWorld's constructor...");
}
public void setUser(String user) {
System.out.println("setUser:" + user);
this.user = user;
}
public HelloWorld(String user) {
this.user = user;
}
public void hello(){
System.out.println("Hello: " + user);
}
}
```
- applicationContext.xml
```xml
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:util="http://www.springframework.org/schema/util"
xmlns:p="http://www.springframework.org/schema/p"
xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
http://www.springframework.org/schema/util http://www.springframework.org/schema/util/spring-util-4.0.xsd">
<!-- 配置一个 bean -->
<bean id="helloWorld" class="com.atguigu.spring.helloworld.HelloWorld">
<!-- 为属性赋值 -->
<property name="user" value="Jerry"></property>
</bean>
</beans>
```
- 测试
```java
package com.atguigu.spring.helloworld;
import org.springframework.context.support.ClassPathXmlApplicationContext;
public class Main {
public static void main(String[] args) {
//当使用applicationContext.xml文件来实例化HelloWorld实例时，spring容器做的工作
// HelloWorld helloWorld = new HelloWorld();
// helloWorld.setUser("Tom");
// helloWorld.hello();
//1.创建spring的IOC容器
ApplicationContext ctx = new ClassPathXmlApplicationContext("applicationContext.xml");
//2.根据id从容器中获取Bean实例的引用
HelloWorld helloWorld = (HelloWorld) ctx.getBean("helloWorld");
//3.调用方法
helloWorld.hello();
}
}
```
### Bean配置
#### IOC容器
- IOC容器为管理对象之间的依赖关系提供了基础功能
- spring提供了两种容器：BeanFactory，ApplicationContext
- **BeanFactory**是基础类型的IOC容器，并能提供完整的IOC服务支持。它实际上是一个用于配置和管理java类的内部接口。BeanFactory就是一个管理Bean的工厂，他**负责初始化各种Bean并调用它们的生命周期方法。**
```properties
boolean containsBean(String name)
此bean工厂是否包含具有给定名称的bean定义或外部注册的单例实例？
Object getBean(String name)
返回指定bean的实例，该实例可以是共享的或独立的。
Object getBean(String name, Object... args)
返回指定bean的实例，该实例可以是共享的或独立的。
Class<?> getType(String name)
确定具有给定名称的bean的类型。
```
- **ApplicationContext**是BeanFactory的子接口，也被称为应用上下文，ApplicationContext**添加了更多的企业级功能**。ApplicationContext容器初始化完成后，容器中所有的单例Bean也都被实例化了。调用 ApplicationContext 的 getBean() 方法从 IOC 容器中获取 Bean
```properties
实现类：
1）ClassPathXmlApplicationContext
ApplicationContext context=new ClassPathXmlApplicationContext（“ApplicationContext.xml”）
2）FileSystemXmlApplicationContext
ApplicationContext context=new FileSystemXmlApplicationContext（"d:/beans.xml"）
3)XmlWebApplicationContext
```
#### 依赖注入
#### 属性值注入
1. 属性注入即通过 **setter** **方法**注入Bean 的属性值或依赖的对象
2. 属性注入使用 `<property> `元素, 使用 name 属性指定 Bean 的属性名称，value 属性或 `<value> `子节点指定属性值
3. 可以使用专用的 `<null/>`元素标签为 Bean 的字符串或其它对象类型的属性注入null 值
4. **Spring** **支持级联属性的配置**。
5. **属性注入是实际应用中最常用的注入方式**
```java
package com.deciphering.model;
public class User {
private String username;
private String password;
public String getUsername() {
return username;
}
public void setUsername(String username) {
this.username = username;
}
public String getPassword() {
return password;
}
public void setPassword(String password) {
this.password = password;
}
}
```
```java
package com.deciphering.dao;
import com.deciphering.model.User;
public interface UserDAO {
public void save(User user);
}
```
```java
package com.deciphering.dao.impl;
import com.deciphering.dao.UserDAO;
import com.deciphering.model.User;
public class UserDAOImpl implements UserDAO {
public void save(User user) {
System.out.println(user.getUsername() + " saved in Oracle!");
//System.out.println(user.getUsername() + " saved in DB2!");
//System.out.println(user.getUsername() + " saved in mysql!");
}
}
```
```java
package com.deciphering.service;
import com.deciphering.model.User;
public interface UserService {
//处理新增用户业务逻辑
public void add(User user);
}
```
```java
package com.deciphering.service;
import com.deciphering.dao.UserDAO;
import com.deciphering.model.User;
public class UserServiceImpl {
private UserDAO userDAO;
public void add(User user) {
userDAO.save(user);
}
public UserDAO getUserDAO() {
return userDAO;
}
public void setUserDAO(UserDAO userDAO) {
this.userDAO = userDAO;
}
public UserServiceImpl(UserDAO userDAO) {
super();
this.userDAO = userDAO;
}
}
```
```xml
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd">
<bean id="u" class="com.deciphering.dao.impl.UserDAOImpl">
</bean>
<bean id="userService" class="com.deciphering.service.UserServiceImpl">
<!--
属性注入
<property name="userDAO">
<ref bean="u"/>
</property>
-->
</bean>
</beans>
```
- **Spring调用getter,setter方法**
```properties
根据配置文件，spring会为每个<bean>元素创建一个java对象，即一个Bean实例
<bean id="id" class="com.xy.Student">
这句代码，spring的底层实现是这样的：
1）获取类的Class对象
Class c = Class.forName("com.xy.Student");
2）创建类的默认实例
Object bean = c.newInstance();
3）spring遍历<bean>元素中所有的<property>元素，每发现一个<property>元素，就会为该bean实例调用相应的 setter方法<property name="stuName" value="xy" />
//获取stuName属性对应的setter方法名
String setname = "set" + "StuName";
//获取类中的setStuName（）方法，有两个参数，第一个是方法名，第二个是参数列表
Method method = c.getMehod(setname,String.Class);
//调用bean实例的setStuName（）方法，把值传入
method.invoke(bean,"xy");
```
#### 构造方法注入
1. 通过构造方法注入Bean 的属性值或依赖的对象，它保证了 Bean 实例在实例化后就可以使用
2. 构造器注入在` <constructor-arg>` 元素里声明属性, `<constructorarg>` 中没有 name 属性
```java
package com.atguigu.spring.helloworld;
public class Car {
private String company;
private String brand;
private int maxSpeed;
private float price;
public Car(String company, String brand, float price) {
super();
this.company = company;
this.brand = brand;
this.price = price;
}
public Car(String company, String brand, int maxSpeed) {
super();
this.company = company;
this.brand = brand;
this.maxSpeed = maxSpeed;
}
public Car(String company, String brand, int maxSpeed, float price) {
super();
this.company = company;
this.brand = brand;
this.maxSpeed = maxSpeed;
this.price = price;
}
@Override
public String toString() {
return "Car [company=" + company + ", brand=" + brand + ", maxSpeed="
+ maxSpeed + ", price=" + price + "]";
}
}
```
```xml
<!-- 若一个 bean 有多个构造器, 如何通过构造器来为 bean 的属性赋值 -->
<!-- 可以根据 index 和 value 进行更加精确的定位. (了解) -->
<bean id="car" class="com.atguigu.spring.helloworld.Car">
<constructor-arg value="KUGA" index="1"></constructor-arg>
<constructor-arg value="ChangAnFord" index="0"></constructor-arg>
<constructor-arg value="250000" type="float"></constructor-arg>
</bean>
<!-- ------------------------------------------------------------------------- -->
<bean id="car2" class="com.atguigu.spring.helloworld.Car">
<constructor-arg value="ChangAnMazda"></constructor-arg>
<!-- 若字面值中包含特殊字符, 则可以使用 DCDATA 来进行赋值. (了解) -->
<constructor-arg>
<value><![CDATA[<ATARZA>]]></value>
</constructor-arg>
<constructor-arg value="180" type="int"></constructor-arg>
</bean>
```
- **谨记spring容器是一个轻量级容器，以属性值注入为主，辅之以构造方法注入为补充**
#### 集合注入
- 在 Spring中可以通过一组内置的 xml 标签(例如: `<list>, <set> 或 <map>`) 来配置集合属性
- 配置 java.util.List 类型的属性, 需要指定 `<list>` 标签, 在标签里包含一些元素. 这些标签可以通过 `<value>` 指定简单的常量值, 通过 `<ref>`指定对其他 Bean 的引用. 通过`<bean>`指定内置 Bean 定义. 通过 `<null/> `指定空元素. 甚至可以内嵌其他集合
- 数组的定义和 List 一样, 都使用 `<list>`
- 配置 java.util.Set 需要使用 `<set>`标签, 定义元素的方法与 List 一样
- Java.util.Map 通过`<map>`标签定义,`<map>`标签 里可以使用多个`<entry>`作为子标签，每个条目包含一个键和一个值，必须在`<key>`标签里定义键，因为键和值的类型没有限制, 所以可以自由地为它们指定 `<value>, <ref>, <bean>或<null> `元素
- 可以将 Map 的键和值作为 `<entry>`的属性定义: 简单常量使用 key 和 value 来定义; Bean 引用通过 key-ref 和 value-ref属性定义
- `使用 <props> 定义 java.util.Properties, 该标签使用多个 <prop> 作为子标签. 每个 <prop> 标签必须定义 key 属性`
```java
package com.deciphering.InjectCollections;
import java.util.List;
import java.util.Map;
import java.util.Set;
import org.springframework.context.ApplicationContext;
import org.springframework.context.support.ClassPathXmlApplicationContext;
public class InjectCollections {
private Set<String> sets;
private List<String> lists;
private Map<String , String> maps;
public Set<String> getSets() {
return sets;
}
public void setSets(Set<String> sets) {
this.sets = sets;
}
public List<String> getLists() {
return lists;
}
public void setLists(List<String> lists) {
this.lists = lists;
}
public Map<String, String> getMaps() {
return maps;
}
public void setMaps(Map<String, String> maps) {
this.maps = maps;
}
@Override
public String toString() {
return "sets " + sets.toString() + "\nlists " + lists.toString() + "\nmaps " + maps.toString() ;
}
public static void main(String[] args){
ApplicationContext ctx = new ClassPathXmlApplicationContext("beans.xml");
InjectCollections ic= (InjectCollections)ctx.getBean("InjectCollections");
System.out.println(ic);
}
}
```
```xml
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd">
<bean id="InjectCollections" class="com.deciphering.InjectCollections.InjectCollections">
<property name="sets">
<set>
<value>1</value>
<value>2</value>
</set>
</property>
<property name="lists">
<list>
<value>1</value>
<value>2</value>
<value>3</value>
</list>
</property>
<property name="maps">
<map>
<entry key="1" value="1"></entry>
<entry key="2" value="2"></entry>
<entry key="3" value="3"></entry>
<entry key="4" value="4"></entry>
</map>
</property>
</bean>
</beans>
```
```xml
<property name="">
<props>
<prop key="1">1</prop>
<prop key="2">2</prop>
<prop key="3">3</prop>
<prop key="4">4</prop>
</props>
</property>
```
#### 自动装配
- Spring IOC 容器可以自动装配 Bean. 需要做的仅仅是**在 <bean> 的 autowire 属性里指定自动装配的模式**
- **byType**(根据类型自动装配): 若 IOC 容器中有多个与目标 Bean 类型一致的 Bean. 在这种情况下, Spring 将无法判定哪个 Bean 最合适该属性, 所以不能执行自动装配
- **byName**(根据名称自动装配): 必须将目标 Bean 的名称和属性名设置的完全相同
- constructor(通过构造器自动装配): 当 Bean 中存在多个构造器时, 此种自动装配方式将会很复杂. **不推荐使用**
- autowire 属性要么根据类型自动装配, 要么根据名称自动装配, 不能两者兼而有之
- 一般情况下，在实际的项目中很少使用自动装配功能，因为和自动装配功能所带来的好处比起来，明确清晰的配置文档更有说服力一些
#### 继承依赖
- **Spring** **允许继承** **bean** **的配置**, 被继承的 bean 称为父 bean. 继承这个父 Bean 的 Bean 称为子 Bean
- **子** **Bean 从父 Bean 中继承配置, 包括Bean 的属性配置**
- 子 Bean 也可以**覆盖**从父 Bean 继承过来的配置
- 父 Bean 可以作为配置模板, 也可以作为 Bean 实例. **若只想把父 Bean作为模板, 可以设置 `<bean>`
的abstract 属性为 true**, 这样 Spring 将不会实例化这个 Bean
- 并不是 `<bean>`元素里的所有属性都会被继承 比如: autowire, abstract 等
- 也**可以忽略父** **Bean** **的** **class** **属性**, 让子 Bean 指定自己的类, 而共享相同的属性配置. 但此时 **abstract** **必须设为** **true**
- **Spring 允许用户通过 depends-on属性设定 Bean 前置依赖的Bean**，前置依赖的 Bean 会在本 Bean 实例化之前创建好
- 如果前置依赖于多个 Bean，则可以通过逗号，空格或的方式配置 Bean 的名称
#### 作用域
- 在 Spring 中, 可以在` <bean> `元素的 **scope** 属性里设置 Bean 的作用域
- 默认情况下, Spring 只为每个在 IOC 容器里声明的 Bean 创建唯一一个实例, 整个 IOC 容器范围内都能共享该实例
- singleton:在springIOC容器中仅存在一个bean实例，bean以单实例的方式存在
- prototype：每次调用getBean（）方法时都会返回一个新的实例
- request：每次HTTP请求都会创建一个新的bean，该作用域仅适用于WebApplicationContext环境
- session：同一个HTTP Session共享一个bean，不同的HTTP Session使用不同的bean。该作用域仅适用于WebApplicationContext环境
#### 外部文件
- `可通过 <context:property-placeholder> 元素简化`
```xml
<context:property-placeholder location="classpath:db.properties"/>
<!-- 数据库连接池 -->
<bean id="dataSource" class="org.apache.commons.dbcp.BasicDataSource"
destroy-method="close">
<property name="driverClassName" value="${jdbc.driver}" />
<property name="url" value="${jdbc.url}" />
<property name="username" value="${jdbc.username}" />
<property name="password" value="${jdbc.password}" />
<property name="maxActive" value="10" />
<property name="maxIdle" value="5" />
</bean>
```
```xml
<import resource="classpath:META-INF/service.xml" />
```
#### SpEL
- Spring 表达式语言（简称SpEL）：是一个支持运行时查询和操作对象图的强大的表达式语言
- 语法类似于 EL：SpEL 使用 #{…} 作为定界符，所有在大框号中的字符都将被认为是SpEL
- SpEL 为 bean 的属性进行动态赋值提供了便利
- 通过 SpEL 可以实现：通过 bean 的 id 对 bean 进行引用,调用方法以及引用对象中的属性,计算表达式的值,正则表达式的匹配
```properties
整数：<property name="count" value="#{5}"/>
小数：<property name="frequency" value="#{89.7}"/>
科学计数法：<property name="capacity" value="#{1e4}"/>
Boolean：<property name="enabled" value="#{false}"/>
```
#### 生命周期
- 1.当调用者通过 getBean(beanName)向 容器请求Bean 时，如果容器注册了org.springframework.beans.factory.config.InstantiationAwareBeanPostProcessor接口，在实例 bean 之前，将调用该接口的 postProcessBeforeInstantiation()方法（实例化以前的操作）。
- 2.根据配置情况调用 Bean构造函数或工厂方法实例化 bean
- 3.如果容器注册了 org.springframework.beans.factory.config.InstantiationAwareBeanPostProcessor接口，在实例 bean 之后，调用该接口的 postProcessAfterInstantiation()方法，可以在这里对已经实例化的对象进行一些操作。
- 4.如果Bean配置了属性信息，在设置每个属性之前将调用InstantiationAwareBeanPostProcess接口的 postProcessPropertyValues （）方法 。
- 5.设置属性值
- 6.如果 Bean 实现了 org.springframework.beans.factory.BeanNameAware 接口，将调用 Bean 的 setBeanName() 方法传递 Bean 的 ID 。设置完属性，首先是BeanNameAware的setBeanName()方法，设置bean名称。
- 7.如果 Bean 实现了 org.springframework.beans.factory.BeanFactoryAware 接口，将调用 setBeanFactory() 方法传入工厂自身。
然后是 BeanFactoryAware的setBeanFactory() 方法，设置bean实例。
8.如果 BeanPostProcessor 和 Bean 关联，那么 将调用org.springframework.beans.factory.config.BeanPostProcessor的postProcessBeforeInitialzation() 方 对 bean进行加工操作，与spring 的 AOP 有关。
这个同样是对bean的处理，BeanPostProcessor接口的postProcessBeforeInitialzation()方法。
- 9.如果bean 实现了 InitializingBean 接口，将调用 afterPropertiesSet()方法
InitializingBean接口的afterPropertiesSet()方法
- 10.如果Bean 指定了 init-method 方法，它将被调用。
init-method 方法
- 11.如果有BeanPsotProcessor 和 Bean 关联，那么它们的 postProcessAfterInitialization() 方法将被调用。 到这个时候， Bean 已经可以被应用系统使用了
- 12-a.如果在`<bean>` 中指定了该 bean 的作用范围为 scope="prototype", 将 bean 的调用者，调用者管理该 bean 的生命周期,spring 不在管理该 bean 。
- 12-b.如果在`<bean> `中指定了该 bean 的作用范围为 scope="singleton", 则将该 bean 放入 springIOC 的缓存池中，将触发 spring 对该 bean 的生命周期管理。
- 13-a.如果 Bean 实现了 DisposableBean 接口， afterPropertiesSet()方法()被调用。
- 14-a.直接通过destroy－method销毁
- 14-b 这个bean自己的管理者如何销毁，spring不管。
- Bean的完整生命周期从 spring 容器开始实例化 bean 开始，到销毁。可以从三点来理解
1、 bean自身的方法：包括构造方法、 set 方法、 init-method 指定的方法、 destroy-method 指定的方法
2、 Bean级生命周期接口方法：如 BeanNameAware 、 BeanFactoryAware 等这些接口方法由 bean类实现。
3、 容器级生命周期接口方法：上图中带星的。有InstantiationAwareBeanPostProcessor 、 BeanPostProcessor 等。一般称为后处理 器。他们一般不由bean 本身实现，独立存在，注册到 spring 容器中。 Spring 通过接口反射预先知道，当 spring 容器创建任何 bean 时，这些后处理器都会发生作用。所以他们是全局的，用户可以通过编码对只感兴趣的 bean 进行处理。
- 下图描述了ApplicationContext 的生命周期
- Spring IOC 容器可以管理 Bean 的生命周期, Spring 允许在 Bean 生命周期的特定点执行定制的任务
- 在生命周期中，有两个周期时间对Bean来说尤为重要，一个是初始化后（PostInitialization），一个是销毁前（Predestruction）
```properties
(实例化Bean)-----》
（利用依赖注入来配置Bean中所有属性值）-----》
（调用BeanNameAware的setBeanName方法）-----》
（调用BeanFactoryAware的setBeanFactory方法）-----》
（调用ApplicationContextAware的setApplicationContex方法）-----》
（调用BeanPostProcessor的postProcessAfterInitialization方法）-----》
（调用InitializingBean的afterPropertiesSet方法）-----》
（调用init-method属性指定的初始化方法）-----》
（调用BeanPostProcessor的postProcessAfterInitialization方法）-----》
（Bean实例化完成，可以使用了）
```
```properties
spring容器关闭-----》
调用DisposableBean的destroy（）方法-----》
调用destroy-method属性指定的销毁Bean的方法
```
- **指定初始化方法，使用init-method属性指定初始化方法**
```java
package com.deciphering.init;
import org.springframework.beans.factory.InitializingBean;
import org.springframework.context.ApplicationContext;
import org.springframework.context.support.ClassPathXmlApplicationContext;
public class SimpleBean{
private static final String DEFAULT_NAME = "Mark";
private static final int DEFAULT_AGE = 20;
private int age = 0;
private String name;
public SimpleBean(){
System.out.println("------------------------\n" +"Spring实例化bean...");
}
public String getName() {
return name;
}
public void setName(String name) {
System.out.println("Spring执行依赖关系注入...");
this.name = name;
System.out.println("name = " + this.name);
}
public int getAge() {
return age;
}
public void setAge(int age) {
System.out.println("Spring执行依赖关系注入...");
this.age = age;
System.out.println("age = " + this.age);
}
public void init(){
System.out.println("初始化bean完成，调用init()...");
this.name = DEFAULT_NAME;
this.age = DEFAULT_AGE;
System.out.println(this);
}
@Override
public String toString() {
return "name: "+ name +"\n"+
"age: "+ age +"\n"+
"------------------------\n";
}
public static void main(String[] args){
ApplicationContext ctx = new ClassPathXmlApplicationContext("beans.xml");
for(int j=1;j<=3;j++){
ctx.getBean("SimpleBean"+j);
}
}
}
```
```xml
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd">
<bean id="SimpleBean1" class="com.deciphering.init.SimpleBean" init-method="init">
<property name="name" value="Bill"></property>
<property name="age" value="19"></property>
</bean>
<bean id="SimpleBean2" class="com.deciphering.init.SimpleBean" init-method="init">
<property name="age" value="20"></property>
</bean>
<bean id="SimpleBean3" class="com.deciphering.init.SimpleBean" init-method="init">
<property name="name" value="Charles"></property>
</bean>
</beans>
```
```properties
------------------------
Spring实例化bean...
Spring执行依赖关系注入...
name=bill
Spring执行依赖关系注入...
age=19
初始化bean完成，调用init()...
name:mark
age:20
------------------------
```
```properties
1)先调用SimpleBean类的构造方法创建SimpleBean1实例
2）接着spring的IOC容器通过setter方法将name和age两个属性的值注入SimpleBean1实例
3）最后容器自动调用init()方法完成初始化工作
```
#### Bean实例化
- **实现InitializingBean接口**
- 凡是继承了InitializingBean接口的类，在初始化Bean的时候都会执行afterPropertiesSet方法
- 对于实现了InitializingBean接口的Bean，无须再使用init-method指定初始化方法
- 实现了InitializingBean接口的方式将代码和spring耦合起来，是侵入式设计，因此**不推荐使用**
```java
package com.deciphering.init;
import org.springframework.beans.factory.InitializingBean;
import org.springframework.context.ApplicationContext;
import org.springframework.context.support.ClassPathXmlApplicationContext;
public class SimpleBean implements InitializingBean{
private static final String DEFAULT_NAME = "Mark";
private static final int DEFAULT_AGE = 20;
private int age = 0;
private String name;
public SimpleBean(){
System.out.println("------------------------\n" +"Spring实例化bean...");
}
public String getName() {
return name;
}
public void setName(String name) {
System.out.println("Spring执行依赖关系注入...");
this.name = name;
System.out.println("name = " + this.name);
}
public int getAge() {
return age;
}
public void setAge(int age) {
System.out.println("Spring执行依赖关系注入...");
this.age = age;
System.out.println("age = " + this.age);
}
@Override
public String toString() {
return "name: "+ name +"\n"+
"age: "+ age +"\n"+
"------------------------\n";
}
public static void main(String[] args){
ApplicationContext ctx = new ClassPathXmlApplicationContext("beans.xml");
for(int j=1;j<=3;j++){
ctx.getBean("SimpleBean"+j);
}
}
@Override
public void afterPropertiesSet() throws Exception {
// TODO Auto-generated method stub
System.out.println("初始化bean完成，调用afterPropertiesSet()...");
this.name = DEFAULT_NAME;
this.age = DEFAULT_AGE;
System.out.println(this);
}
}
```
```xml
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd">
<bean id="SimpleBean1" class="com.deciphering.init.SimpleBean">
<property name="name" value="Bill"></property>
<property name="age" value="19"></property>
</bean>
<bean id="SimpleBean2" class="com.deciphering.init.SimpleBean">
<property name="age" value="20"></property>
</bean>
<bean id="SimpleBean3" class="com.deciphering.init.SimpleBean">
<property name="name" value="Charles"></property>
</bean>
</beans>
```
#### Bean销毁
- 关闭钩子（shutdown hook）：程序在退出JVM之前关闭spring ApplicationContext容器
```java
public static void main(String[] args){
ApplicationContext ctx = new ClassPathXmlApplicationContext("beans.xml");
for(int j=1;j<=3;j++){
ctx.getBean("SimpleBean"+j);
}
//为spring容器注册关闭钩子
ctx.registerShutdownHook();
}
```
- 使用destroy-method属性指定析构方法
```java
package com.deciphering.init;
import org.springframework.context.ApplicationContext;
import org.springframework.context.support.AbstractApplicationContext;
import org.springframework.context.support.ClassPathXmlApplicationContext;
public class SimpleBean {
private static final String DEFAULT_NAME = "Mark";
private static final int DEFAULT_AGE = 20;
private int age = 0;
private String name;
public SimpleBean(){
System.out.println("Spring实例化bean...");
}
public String getName() {
return name;
}
public void setName(String name) {
System.out.println("Spring执行依赖关系注入...");
this.name = name;
System.out.println("name = " + this.name);
}
public int getAge() {
return age;
}
public void setAge(int age) {
System.out.println("Spring执行依赖关系注入...");
this.age = age;
System.out.println("age = " + this.age);
}
public void close(){
System.out.println("调用close()...");
System.out.println("此时可以用来执行销毁前的资源回收方法...");
}
@Override
public String toString() {
return "name: "+ name +"\n"+
"age: "+ age +"\n";
}
public static void main(String[] args){
AbstractApplicationContext ctx = new ClassPathXmlApplicationContext("beans.xml");
ctx.getBean("SimpleBean");
ctx.registerShutdownHook();
System.out.println("关闭ApplicationContext！");
}
}
```
```xml
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd">
<bean id="SimpleBean" class="com.deciphering.init.SimpleBean" destroy-method="close">
<property name="name" value="Bill"></property>
<property name="age" value="19"></property>
</bean>
</beans>
```
```properties
Spring实例化bean...
Spring执行依赖关系注入...
name=Bill
Spring执行依赖关系注入...
age=19
关闭ApplicationContext！
调用close()...
此时可以用来执行销毁前的资源回收方法...
```
- 实现DisposableBean接口
```java
package com.deciphering.init;
import org.springframework.beans.factory.DisposableBean;
import org.springframework.context.ApplicationContext;
import org.springframework.context.support.AbstractApplicationContext;
import org.springframework.context.support.ClassPathXmlApplicationContext;
public class SimpleBean implements DisposableBean{
private static final String DEFAULT_NAME = "Mark";
private static final int DEFAULT_AGE = 20;
private int age = 0;
private String name;
public SimpleBean(){
System.out.println("Spring实例化bean...");
}
public String getName() {
return name;
}
public void setName(String name) {
System.out.println("Spring执行依赖关系注入...");
this.name = name;
System.out.println("name = " + this.name);
}
public int getAge() {
return age;
}
public void setAge(int age) {
System.out.println("Spring执行依赖关系注入...");
this.age = age;
System.out.println("age = " + this.age);
}
@Override
public String toString() {
return "name: "+ name +"\n"+
"age: "+ age +"\n";
}
public static void main(String[] args){
AbstractApplicationContext ctx = new ClassPathXmlApplicationContext("beans.xml");
ctx.getBean("SimpleBean");
ctx.registerShutdownHook();
System.out.println("关闭ApplicationContext！");
}
@Override
public void destroy() throws Exception {
// TODO Auto-generated method stub
System.out.println("调用close()...");
System.out.println("此时可以用来执行销毁前的资源回收方法...");
}
}
```
```xml
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd">
<bean id="SimpleBean" class="com.deciphering.init.SimpleBean">
<property name="name" value="Bill"></property>
<property name="age" value="19"></property>
</bean>
</beans>
```
#### 注解装配
- 组件扫描(componentscanning): Spring 能够从 classpath 下自动扫描, 侦测和实例化具有特定注解的组件
- 特定组件包括:
```properties
@Component: 基本注解, 标识了一个受 Spring 管理的组件
@Respository: 标识持久层组件
@Service: 标识服务层(业务层)组件
@Controller: 标识表现层组件
```
- 对于扫描到的组件,Spring 有默认的命名策略:使用非限定类名, 第一个字母小写。也可以在注解中通过 value 属性值标识组件的名称
- 当在组件类上使用了特定的注解之后, 还需要在 Spring 的配置文件中声明`<context:component-scan> `
```properties
base-package 属性指定一个需要扫描的基类包，Spring 容器将会扫描这个基类包里及其子包中的所有类
当需要扫描多个包时, 可以使用逗号分隔
如果仅希望扫描特定的类而非基包下的所有类，可使用 resource-pattern 属性过滤特定的类
<context:component-scan
base-package="com.test.spring.beans"
resource-pattern="autowire/*.class"/>
<context:include-filter> 子节点表示要包含的目标类
<context:exclude-filter> 子节点表示要排除在外的目标类
<context:component-scan> 下可以拥有若干个 <context:include-filter> 和 <context:exclude-filter> 子节点
```
- `<context:component-scan>`元素还会自动注册 AutowiredAnnotationBeanPostProcessor 实例, 该实例可以自动装配具有@Autowired 和 @Resource 、@Inject注解的属性
#### @Autowired
- @Autowired 注解自动装配**具有兼容类型**的单个 Bean属性
- 构造器, 普通字段(即使是非 public), 一切具有参数的方法都可以应用@Authwired 注解
- 默认情况下, 所有使用 @Authwired 注解的属性都需要被设置. 当 Spring 找不到匹配的 Bean 装配属性时, 会抛出异常, 若某一属性允许不被设置, 可以设置 @Authwired 注解的 required 属性为 false
- 默认情况下, 当 IOC 容器里存在多个类型兼容的 Bean 时, 通过类型的自动装配将无法工作. 此时可以在 @Qualifier 注解里提供 Bean 的名称. Spring 允许对方法的入参标注 @Qualifiter 已指定注入 Bean 的名称
- @Authwired 注解也可以应用在**数组类型**的属性上, 此时 Spring 将会把所有匹配的 Bean 进行自动装配
- @Authwired 注解也可以应用在**集合属性**上, 此时 Spring 读取该集合的类型信息, 然后自动装配所有与之兼容的 Bean
- @Authwired 注解用**在** **java.util.Map** 上时, 若该 Map 的键值为 String, 那么 Spring 将自动装配与之 Map 值类型兼容的 Bean, 此时 Bean 的名称作为键值
#### @Resource
- Spring 还支持 @Resource 和 @Inject 注解，这两个注解和 @Autowired 注解的功用类似
- @Resource 注解要求提供一个 Bean 名称的属性，若该属性为空，则自动采用标注处的变量或方法名作为
Bean 的名称
- @Inject 和 @Autowired 注解一样也是按类型匹配注入的 Bean， 但没有 reqired 属性
- **建议使用 @Autowired 注解**
#### 思维导图
[思维导图](https://blog.csdn.net/qq_36925536/article/details/101313412)
| 23.954583 | 218 | 0.714502 | yue_Hant | 0.516076 |
055b00c98f5fa90f56a857a6256087f0c1769a2d | 517 | md | Markdown | _pages/about.md | sarath1789/sarath1789.github.io | 592a311912c24a81658ab62048211319605a3824 | [
"MIT"
] | null | null | null | _pages/about.md | sarath1789/sarath1789.github.io | 592a311912c24a81658ab62048211319605a3824 | [
"MIT"
] | null | null | null | _pages/about.md | sarath1789/sarath1789.github.io | 592a311912c24a81658ab62048211319605a3824 | [
"MIT"
] | null | null | null | ---
permalink: /
title: "Sarath's homepage"
excerpt: "About me"
author_profile: true
redirect_from:
- /about/
- /about.html
---
I am a PhD student at the Department of Electrical Communication Engineering, [Indian Institute of Science](https://www.iisc.ac.in/), Bangalore, India. I am broadly interested in applied probability.
Towards my PhD, I work on large time behaviour and metastability in mean-field interacting particle systems. I work with [Prof. Rajesh Sundaresan](https://ece.iisc.ac.in/~rajeshs/).
| 36.928571 | 199 | 0.752418 | eng_Latn | 0.860645 |
055b03e955ae717d82799440ed4bdea950ded141 | 143 | md | Markdown | documentation/Audio.md | TheIoTLearningInitiative/Up | 2fe6ed67a9934a91a100df9754c9373508ba4882 | [
"Apache-2.0"
] | null | null | null | documentation/Audio.md | TheIoTLearningInitiative/Up | 2fe6ed67a9934a91a100df9754c9373508ba4882 | [
"Apache-2.0"
] | null | null | null | documentation/Audio.md | TheIoTLearningInitiative/Up | 2fe6ed67a9934a91a100df9754c9373508ba4882 | [
"Apache-2.0"
] | null | null | null | # Audio
```sh
user@ubilinux:~$ cat /proc/asound/cards
0 [IntelHDMI ]: IntelHDMI - IntelHDMI
user@ubilinux:~$
``` | 17.875 | 43 | 0.538462 | kor_Hang | 0.194516 |
055b13d8ca55815b79a005d4a2fd2de57d9054e5 | 3,823 | md | Markdown | README.md | DeskproApps/shopify | 3736413ffbcd662f699bc505de718ce1eae54a36 | [
"MIT"
] | null | null | null | README.md | DeskproApps/shopify | 3736413ffbcd662f699bc505de718ce1eae54a36 | [
"MIT"
] | null | null | null | README.md | DeskproApps/shopify | 3736413ffbcd662f699bc505de718ce1eae54a36 | [
"MIT"
] | null | null | null | Shopify
===
This repository contains a bare-bones template of a [React](https://reactjs.org/) / [Typescript](https://www.typescriptlang.org/) [Vite](https://vitejs.dev/) app with our apps SDK pre-installed and
configured.
Basic Usage
---
We recommend using [Yarn](https://yarnpkg.com/) to manage this project. First, start by installing the project
dependencies from inside the project directory `app-template-vite`.
```bash
yarn install
```
Then, run the development server.
```bash
yarn start
```
You should now be able to view the bare-bones app in your browser.
Starting a New App Project
---
When start a new official app project, you must [add a repository to our GitHub organisation](https://github.com/DeskproApps). If you don't have access
to create this, please contact us.
Our trunk branch name convention is `master` and this will be used by our CI processes to test and build your app.
Once you have the new remote repository, clone this template and re-initialise Git.
```bash
git clone [email protected]:DeskproApps/app-template-vite.git
cd app-template-vite
rm -rf .git
git init
```
Add the remote "origin" repo, and push your first commit:
```bash
git remote add origin [email protected]:DeskproApps/<repo-name>.git
git add .
git commit -m "Initial commit, new app project"
git push origin master
```
Branching and PRs
---
We use the following naming convention for feature branches:
```
feature/<my-feature-name>
```
So, to create your first feature branch, do the following:
```bash
git checkout master
git checkout -b feature/my-new-feature
```
Great! You're now ready to start work on your feature.
Next, it's time to raise your first pull request (PR). To do this, head over to GitHub and navigate to
the "Pull requests" tab in your repository. Click on "New pull request" and make sure that your feature branch
is selected as the source, and `master` as the destination. Then, click "Create PR".
Our CI process will now lint, type check, test and build your app. If you have any errors in your code or tests, CI will
fail your PR - so fix any of these issues before your PR is ready.
Once you're happy with your PR - merge it :)
We'll also perform the same CI process on `master` as this is what we use to review your app when it's done.
Testing
---
We've included `jest` to run your tests. It will look anywhere in `/src` for test suite files ending in `.test.tsx`.
You can run all tests using:
```bash
yarn test
```
We've also included a sample test suite in `src/App.test.tsx`
We maintain a minimum level of code coverage, to check that your code meets this threshold, run the following:
```bash
yarn test:coverage
```
> Our code coverage threshold is 60%, so your coverage report must show that all analyses are at or greater than 60% for
> your app to be officially accepted
For more information about building your app, please refer to our [app development guide](https://support.deskpro.com/en/guides/developers/how-to-build-a-basic-notes-app).
Packaging
---
To package your app we've included a packaging script that will allow you to build the app package zip archive. Steps
for building and packaging your app are as follows:
```bash
yarn build
yarn package
```
Or, as a shortcut, you can use:
```bash
yarn build:package
```
Once your app has been built and packaged, you should find your package artifact in `./build`. You can now [upload this
to Deskpro](https://support.deskpro.com/en/guides/developers/building-and-packaging-an-app) and try it out :)
Continuous Integration
---
We ship this template with GitHub action configurations for both PR and Branch builds. Our CI process will lint, type
check, test and provide a coverage report. The trunk Git branch is `master`, and CI will look for this when checking
out and comparing changes.
| 29.407692 | 198 | 0.74915 | eng_Latn | 0.996886 |
055b3f8d73559d8edb4c26383fbb9c5383e3a79d | 43 | md | Markdown | _posts/Lab/htb/htb.md | ocholuo/jekyll-theme-chirpy | 55d0748ad9ea08750ae40e3ee0fa1c811063bfa4 | [
"MIT"
] | 2 | 2020-09-26T03:32:02.000Z | 2020-10-09T06:01:48.000Z | _posts/Lab/htb/htb.md | ocholuo/jekyll-theme-chirpy | 55d0748ad9ea08750ae40e3ee0fa1c811063bfa4 | [
"MIT"
] | null | null | null | _posts/Lab/htb/htb.md | ocholuo/jekyll-theme-chirpy | 55d0748ad9ea08750ae40e3ee0fa1c811063bfa4 | [
"MIT"
] | null | null | null | ERROR: type should be string, got "\nhttps://estamelgg.github.io/posts/Blunder/" | 21.5 | 42 | 0.790698 | nob_Latn | 0.283614 |
055b581b44b41734853a0516a58fdef9470376c7 | 7,375 | md | Markdown | ko/flight_controller/omnibus_f4_sd.md | dbaldwin/PX4-user_guide | 4f8fa7b4a8dc029a1af56dd1160b30ab98493a09 | [
"CC-BY-4.0"
] | 86 | 2017-06-21T07:40:02.000Z | 2020-10-26T07:13:15.000Z | ko/flight_controller/omnibus_f4_sd.md | dbaldwin/PX4-user_guide | 4f8fa7b4a8dc029a1af56dd1160b30ab98493a09 | [
"CC-BY-4.0"
] | 519 | 2017-04-13T06:33:24.000Z | 2020-10-28T03:42:10.000Z | ko/flight_controller/omnibus_f4_sd.md | dbaldwin/PX4-user_guide | 4f8fa7b4a8dc029a1af56dd1160b30ab98493a09 | [
"CC-BY-4.0"
] | 460 | 2020-10-29T07:59:28.000Z | 2022-03-31T17:18:47.000Z | # Omnibus F4 SD
:::warning PX4에서는 이 제품을 제조하지 않습니다. 지원 또는 규정준수 문제는 제조업체에 문의하십시오.
:::
*Omnibus F4 SD*는 레이서를 위해 설계된 컨트롤러입니다. 일반적인 레이서 보드와 달리 SD 카드와 고속 CPU 등이 추가되었습니다.
<img src="../../assets/flight_controller/omnibus_f4_sd/board.jpg" width="400px" title="Omnibus F4 SD" />
다음은 [Pixracer](../flight_controller/pixracer.md)와 주요 차이점은 다음과 같습니다.
* 저렴한 가격
* 더 적은 IO 포트(예 : GPS 또는 Flow 센서를 연결은 가능함)
* 외부 GPS용 I2C 버스에 외부 풀업 저항이 필요합니다. 아래 [I2C](#i2c)를 참조하십시오.
* 적은 RAM (192 KB vs. 256 KB) and FLASH (1 MB vs. 2 MB)
* *Pixracer*와 동일 보드 크기, 약간 더 작은 폼 팩터(커넥터가 적기 때문에)
* 통합 OSD(아직 소프트웨어에서 구현되지 않음)
:::tip
모든 일반적인 PX4 기능은 여전히 레이서에 사용할 수 있습니다!
:::
:::note
이 비행 컨트롤러는 [제조업체의 지원](../flight_controller/autopilot_manufacturer_supported.md)을 받을 수 있습니다.
:::
## 주요 기능
* 메인 시스템 온칩: [STM32F405RGT6](https://www.st.com/en/microcontrollers/stm32f405rg.html)
* CPU : 단정밀도 FPU의 168MHz ARM Cortex M4
* RAM : 192KB SRAM
* FLASH: 1 MB
* 표준 레이서 폼 팩터 : 36x36mm, 표준 30.5mm 구멍 패턴
* MPU6000 가속/자이로
* BMP280 기압계(모든 보드에 마운트된 것은 아님)
* microSD(로깅)
* Futaba S.BUS 및 S.BUS2/Spektrum DSM2 및 DSMX/Graupner SUMD/PPM 입력/Yuneec ST24
* OneShot PWM 출력(설정 가능)
* 내장 전류 센서
* 내장 OSD 칩(SPI를 통한 AB7456)
## 구매처
보드는 몇 가지 변형된 형태(예 : 기압계 포함 또는 제외)로 여러 공급 업체에서 생산합니다.
:::tip PX4는 Betaflight OMNIBUSF4SD 대상을 지원하는 보드와 호환됩니다(제품 페이지에 *OMNIBUSF4SD*가 있는 경우, 보드는 PX4에서 작동해야 함).
:::
:::tip
모든 Omnibus F4 레이블 파생물(예 : 클론)도 작동합니다. 그러나, 이러한 보드의 배전은 품질이 다양합니다.
:::
아래의 보드들은 테스트되고 작동하는 것입니다.
* [Hobbywing XRotor 비행 콘트롤러 F4](http://www.hobbywing.com/goods.php?id=636) :::note 이 보드는 납땜이 필요없는 [Hobbywing XRotor Micro 40A 4in1 ESC](http://www.hobbywing.com/goods.php?id=588)에 적합합니다. 이 ESC 보드는 또한 Omnibus 보드에 전원을 제공합니다.
:::
구매처:
* [Hobbywing XRotor F4 비행 콘트롤러 w/OSD](https://www.getfpv.com/hobbywing-xrotor-f4-flight-controller-w-osd.html) (getfpv)
* 오리지널 Airbot Omnibus F4 SD
구매처:
* [Airbot (CN 제조업체)](https://store.myairbot.com/omnibusf4prov3.html)
* [Ready To Fly Quads(미국 리셀러)](http://www.readytoflyquads.com/flip-32-f4-omnibus-v2-pro)
액세서리에는 아래의 내용물이 포함됩니다.
* MAVLink 텔레메트리 [ESP8266 WiFi 모듈](../telemetry/esp8266_wifi_module.md). 다음 핀을 연결하여야합니다: GND, RX, TX, VCC 및 CH-PD (CH-PD ~ 3.3V). 전송 속도는 921600입니다.
## 커넥터
이 설계를 기반으로 한 다른 공급 업체의 보드는 레이아웃이 상당히 다를 수 있습니다. 다양한 버전의 레이아웃/실크스크린이 아래와 같습니다.
### 에어 봇 옴니버스 F4 SD
아래는 상단과 하단을 모두 보여주는 Airbot Omnibus F4 SD (V1)의 실크 스크린입니다.
 
### Hobbywing XRotor 비행 콘트롤러 F4
아래는 Hobbywing XRotor 비행 콘트롤러 F4의 실크스크린입니다.
## 핀배열
### 무선 조종
RC는 다음 포트중 하나에 연결됩니다.
* UART1
* SBUS/PPM 포트(인버터를 통해 내부적으로 UART1로 이동)
:::note
일부 Omnibus F4 보드에는 MCU SBUS 및 PPM 중 하나 또는 둘 다를 단일 핀 헤더에 연결하는 점퍼가 있습니다. 사용하기 전에 점퍼 또는 솔더 브리지를 적절한 MCU 핀으로 설정하십시오.
:::
### UART
* UART6: GPS 포트
* TX: MCU 핀 PC6
* RX: MCU 핀 PC7
* Airbot Omnibus F4 SD 핀아웃은 포트 J10(TX6 / RX6)에 있습니다.
* UART4
* TX: MCU 핀 PA0
* RX: MCU 핀 PA1
* 초당 전송속도: 57600
* 이것은 `TELEM 2` 포트로 설정할 수 있습니다.
* 에어 봇 옴니버스 F4 SD 핀배열:
* TX: RSSI 핀
* RX: PWM 출력 5
### I2C
다음을 통해 사용 가능한 I2C 포트가 하나 있습니다.
* SCL: MCU 핀 PB10 (TX3로 표시 될 수 있음)
* SDA: MCU 핀 PB11 (RX3로 표시 될 수 있음)
:::note
두 신호(클럭 및 데이터) 모두에 외부 풀업이 필요합니다. 예를 들어, 2.2k 풀업을 사용하여 외부 매거진을 연결할 수 있습니다.
:::
- Airbot Omnibus F4 SD 핀아웃은 포트 J10 (SCL [클럭] / SCA [데이터])에 있습니다.
다음은 구현의 예입니다. 저는 Spektrum 플러그를 사용하여 DSM 포트에서 3.3v를 얻었으며 2.2k 저항을 통해 각 라인에 3.3v+ 만 연결하였습니다.
## 시리얼 포트 매핑
| UART | 장치 | 포트 |
| ------ | ---------- | -------- |
| USART1 | /dev/ttyS0 | SerialRX |
| USART4 | /dev/ttyS1 | TELEM1 |
| USART6 | /dev/ttyS2 | GPS |
<!-- Note: Got ports using https://github.com/PX4/px4_user_guide/pull/672#issuecomment-598198434 -->
## RC 텔레메트리
Omnibus는 [FrSky 텔레메트리](../peripherals/frsky_telemetry.md) 또는 [CRSF Crossfire 텔레메트리](#crsf_telemetry)를 사용하여 RC 전송기에 대한 원격측정을 지원합니다.
<span id="crsf_telemetry"></span>
### CRSF Crossfire 텔레메트리
TBS CRSF Crossfire 텔레메트리는 비행 콘트롤러(기체의 자세, 배터리, 비행 모드 및 GPS 데이터)에서 RC 송신기(Taranis)로 원격측정 데이터를 전송합니다.
FrSky 텔레메트리의 이점은 다음과 같습니다.
* RC와 텔레메트리에는 단일 UART 만 필요합니다.
* CRSF 프로토콜은 응답시간 느린 장치에 최적화되어 있습니다.
* 150Hz RC 업데이트 속도.
* 신호는 반전되지 않으므로 외부 인버터 로직이 필요하지 않습니다.
Omnibus는 소형 쿼드 용으로 특별히 설계되었으므로 [TBS Crossfire Nano RX](http://team-blacksheep.com/products/prod:crossfire_nano_rx) 사용을 권장합니다.
휴대용 컨트롤러(예 : Taranis)에서는 [송신기 모듈](http://team-blacksheep.com/shop/cat:rc_transmitters#product_listing)도 필요합니다. 이것은 RC 콘트롤러의 뒷면에 장착할 수 있습니다.
:::note
위의 참조 링크에는 TX/RX 모듈 문서가 포함되어 있습니다.
:::
#### 설정
다음과 같이 Nano RX와 Omnibus 핀을 연결합니다.
| Omnibus UART1 | Nano RX |
| ------------- | ------- |
| TX | Ch2 |
| RX | Ch1 |
PX4 비행 컨트롤러에서 다른 항목을 설정하지 않아도 됩니다. RC 프로토콜이 자동으로 감지됩니다.
다음으로 TX/RX 모듈을 업데이트하여 CRSF 프로토콜을 사용하고 텔레메트리를 설정합니다. 이에 대한 지침은 [TBS Crossfire 매뉴얼](https://www.team-blacksheep.com/tbs-crossfire-manual.pdf)( 'CRSF용 라디오 설정' 검색)에 나와 있습니다.
## 회로도
회로도는 [Airbot](https://myairbot.com/)에서 제공합니다: [OmnibusF4-Pro-Sch.pdf](http://bit.ly/obf4pro).
<span id="bootloader"></span>
## 부트로더 업데이트
보드에는 [Betaflight](https://github.com/betaflight/betaflight/wiki)가 사전 설치되어 있습니다. PX4 펌웨어를 설치하기 전에 *PX4 부트 로더*를 플래시하여야 합니다. [omnibusf4sd_bl.hex](https://github.com/PX4/px4_user_guide/raw/master/assets/flight_controller/omnibus_f4_sd/omnibusf4sd_bl_d52b70cb39.hex) 부트로더 바이너리를 다운로드하고 [이 페이지](../advanced_config/bootloader_update_from_betaflight.md)에서 플래시 방법을 참고하십시오.
## 펌웨어 빌드
이 대상에 대한 [PX4 빌드](../dev_setup/building_px4.md) 방법 :
make omnibus_f4sd_default
## 펌웨어 설치
펌웨어는 일반적인 방법으로 설치할 수 있습니다.
* 소스 빌드 및 업로드 ```make omnibus_f4sd_default upload```
* *QGroundControl*을 사용하여 [펌웨어를 로드](../config/firmware.md)합니다. 미리 빌드된 펌웨어나 사용자 지정 펌웨어를 사용할 수 있습니다.
## 설정
[기본 설정](../config/README.md) 외에도 아래의 매개변수가 중요합니다.
| 매개변수 | 설정 |
| ------------------------------------------------------------------------ | ----------------------------------------------------------------------------- |
| [SYS_HAS_MAG](../advanced_config/parameter_reference.md#SYS_HAS_MAG) | 보드에 내부 자력계가 없기 때문에 비활성화하여야 합니다. 외부 자력계를 연결하여 활성화 할 수 있습니다. |
| [SYS_HAS_BARO](../advanced_config/parameter_reference.md#SYS_HAS_BARO) | 보드에 기압계가 없는 경우에는 비활성화 하십시오. |
| [MOT_ORDERING](../advanced_config/parameter_reference.md#MOT_ORDERING) | Betaflight/Cleanflight 모터 할당과 함께 4-in-1 ESC를 사용하는 경우 이 매개변수를 적절하게 설정할 수 있습니다. |
## 추가 정보
이 보드에 관한 리뷰는 [여기](https://nathan.vertile.com/blog/2016/10/12/omnibusf4/)를 참고하십시오.
[이 페이지](https://blog.dronetrest.com/omnibus-f4-flight-controller-guide/)는 핀배열, 설정 방법을 제공합니다. | 31.382979 | 362 | 0.652475 | kor_Hang | 0.999991 |
055ce7b76d442cd46f448f25e97fa0784b134fc3 | 3,338 | md | Markdown | README.md | lexkrstn/portfolio | 1dc340e99181ce2e4cfb554627c2ddb52abba2a8 | [
"MIT"
] | null | null | null | README.md | lexkrstn/portfolio | 1dc340e99181ce2e4cfb554627c2ddb52abba2a8 | [
"MIT"
] | 8 | 2022-01-18T09:04:25.000Z | 2022-02-14T03:45:15.000Z | README.md | lexkrstn/portfolio | 1dc340e99181ce2e4cfb554627c2ddb52abba2a8 | [
"MIT"
] | null | null | null | # Portfolio
> My personal web page describing short bio, professional skills, services I
> provide and containing portfolio section with some examples of works.
Stack:
- Browser: TypeScript, React / Redux, Styled Components, RxJS
- Server: TypeScript, NestJS, MongoDB
## Deploy
Prerequisites
- [NodeJS LTS](https://nodejs.dev)
- [MongoDB 5+](https://docs.mongodb.com/manual/installation/)
### Steps to deploy to a local server
```bash
# 1. Get a copy of the project from git
git clone [email protected]:lexkrstn/portfolio.git
cd ./portfolio
# 2. Install NPM dependencies
npm i
# 3. Build the project
npm run build
# 4. Configure the server (optional, see the options below)
# 5. Install MongoDB migration tool and run migrations
npm i -g migrate-mongo
migrate-mongo up
# 6. Start the server
npm run start:prod
```
### Configuration
The preferred way to configure the server is by setting environment variables:
- `DATABASE_HOST` *default* = **localhost**
- `DATABASE_PORT` *default* = **27017**
- `DATABASE_USER` *default* = *empty (not enabled access control)*
- `DATABASE_PASSWORD` *default* = *empty (not enabled access control)*
- `DATABASE_NAME` *default* = **portfolio** or **portfolio_test**
- `API_PORT` *default* = **3000**
- `MAIL_USER` (gmail) *default* = *not set*
- `MAIL_PASSWORD` (gmail) *default* = *not set*
An alternative way is to create a file named `.env` in the root of the project
and put all the environment variables there (one per line).
## Commands cheatsheet
NPM:
- `npm run start` - starts SSR and API servers concurrently in debug mode
- `npm run start:prod` - starts SSR and API servers concurrently
- `npm run start:ssr` - starts SSR server in debug mode
- `npm run start:ssr:prod` - starts SSR server
- `npm run start:api` - starts API server in debug mode
- `npm run start:api:prod` - starts API server
- `npm run start:browser` - starts webpack dev server
- `npm run build` - builds SSR and API servers in debug mode
- `npm run build:prod` - builds SSR and API servers
- `npm run build:api` - builds API server in debug mode
- `npm run build:ssr` - builds SSR server in debug mode
- `npm run build:browser` - builds browser application in debug mode
- `npm run watch:api` - builds API server in JIT mode
- `npm run watch:ssr` - builds SSR server in JIT mode
- `npm run watch:browser` - builds browser application in JIT mode
- `npm run lint` - performs linting the browser, api and ssr code
- `npm run lint:api` - performs linting the API server code
- `npm run lint:ssr` - performs linting the SSR server code
- `npm run lint:browser` - performs linting the browser application code
- `npm run test` - performs testing the browser, api and ssr
- `npm run test:api` - performs testing the API server
- `npm run test:api:watch` - runs API server unit tests in watch mode
- `npm run test:api:e2e` - runs end-to-end API server tests
- `npm run test:api:coverage` - runs API tests and generates coverage report
- `npm run test:ssr` - performs unit testing of the SSR server
- `npm run test:browser` - performs testing the browser application
- `npm run test:browser:coverage` - runs tests and generates coverage report
- `npm run test:browser:watch` - runs browser app unit tests in watch mode
Misc:
- `migrate-mongo up` | `migrate-mongo down`
- `migrate-mongo create`
- `migrate-mongo status`
| 37.505618 | 78 | 0.731276 | eng_Latn | 0.898997 |
055d227cba1f318b5871051878861b2e3f7bc142 | 2,999 | md | Markdown | README.md | adobe/aio-lib-template-validation | 72bf39cfa6cc445e2636ce5a66399cde7466240a | [
"Apache-2.0"
] | null | null | null | README.md | adobe/aio-lib-template-validation | 72bf39cfa6cc445e2636ce5a66399cde7466240a | [
"Apache-2.0"
] | 1 | 2022-03-18T20:51:19.000Z | 2022-03-24T21:20:53.000Z | README.md | adobe/aio-lib-template-validation | 72bf39cfa6cc445e2636ce5a66399cde7466240a | [
"Apache-2.0"
] | null | null | null | # aio-lib-template-validation
NPM-based tool to validate App Builder templates during submission process to [App Builder Template Registry](https://github.com/adobe/aio-template-submission).
# Validation checks
## package.json file
| Field | Description | Required |
| ------------- | ------------------------------------------------- | ------------------ |
| `description` | Template must have a description | :heavy_check_mark: |
| `keywords` | Must contain a keyword `aio-app-builder-template` | :heavy_check_mark: |
## install.yml file
| Field | Type | Description | Required |
| ------------ | ------------ | ------------------------------------------------------------------------------------------------------------------------------ | ------------------ |
| `categories` | list of strings | Template must have categories defined. | :heavy_check_mark: |
| `extension` | object | Template might implement an extension point. One of its properties must be `serviceCode`, which will contain the extension metadata. | |
| `apis` | list of objects | List the APIs required to be added to all Workspaces in the App Builder Project, if they don't exist. Each API object must contain `code` as one of its properties, this is the sdk code of the service. | |
| `event` | object | This will list the event configuration for the template. The event template code that contains this specification may read this to configure itself. The object can have two properties: `consumer` or `provider`. | |
| `runtime` | boolean | Whether to add Runtime to App Builder application or not. Defaults to `false`. | |
# Getting started
## Installation
```bash
$ npm i -g @adobe/aio-lib-template-validation
$ tv
```
## Usage
To check a specific template run:
```bash
$ tv run-checks <path>
```
This will execute all checks on App Builder template given path to the template code and output the results.
You can add `--json` or `-j` option to output results in JSON format.
## Installation as a library
If you want to use this package as a library within your project, run:
```bash
$ npm i @adobe/aio-lib-template-validation
```
## Contributing
Contributions are welcomed! Read the [Contributing Guide](CONTRIBUTING.md) for more information.
To get started:
1. Install [node.js](https://nodejs.org/).
3. Clone the repository.
4. After navigating into the project directory, install project dependencies by running `npm install`.
### Scripts
To run tests a single time, run the following command:
`npm run test`
## Licensing
This project is licensed under the Apache V2 License. See [LICENSE](LICENSE) for more information.
| 48.370968 | 256 | 0.583861 | eng_Latn | 0.968524 |
055d6c038dfd36109dd708f83e0971802f7d757c | 10,443 | md | Markdown | README.md | tomhodgins/caffeinated-style-sheets | 7cc2fb169e66807bb95d2bb23d41299711d549c5 | [
"MIT"
] | 28 | 2019-01-22T16:08:47.000Z | 2021-11-05T17:07:15.000Z | README.md | tomhodgins/caffeinated-style-sheets | 7cc2fb169e66807bb95d2bb23d41299711d549c5 | [
"MIT"
] | null | null | null | README.md | tomhodgins/caffeinated-style-sheets | 7cc2fb169e66807bb95d2bb23d41299711d549c5 | [
"MIT"
] | 1 | 2020-12-23T10:41:29.000Z | 2020-12-23T10:41:29.000Z | # Caffeinated Style Sheets
Extend `.css` with JavaScript the easy way!
Below is information, learning resources, code, and demos relating to extending CSS in valid `.css` files using JavaScript
## How Event-Driven Styling Works
1. You listen to global events in the browser, or events on DOM nodes, or observers: ResizeObserver, IntersectionObserver, and MutationObserver
2. When an event you're listening to is triggered, you call a "stylesheet function" that returns CSS. This can be a string of CSS, or a [CSSStylesheet](https://developer.mozilla.org/en-US/docs/Web/API/CSSStyleSheet) object, or a [CSSRule](https://developer.mozilla.org/en-US/docs/Web/API/CSSRule) object, or other ways of representing a set of property declarations for one or more elements
3. After the stylesheet function is processed, the returned CSS is applied to the document, or output as objects or a string
[](https://twitter.com/innovati/status/1083400451243065354)
Using this simple model we can polyfill existing CSS features in old browsers using small amounts of CSS and JavaScript that run very fast, as well as prototype and implement new styling functionality that's not part of CSS.
- you never have to go lower-level than CSS (don't use JS to reinvent CSS, use it to extend CSS)
- do everything in CSS that you can do in CSS
- use JavaScript to make CSS higher-level and _more_ declarative
- split your styles by the _events_ that drive their calculation
> Both the `jsincss` and `computed-variables` plugins linked below are event-driven style managers and can be used to extend CSS stylesheets (and rules), and CSS variables
## Writing Caffeinated Stylesheets
You can use the event-driven model for processing style information with plugins like [`jsincss`](https://www.npmjs.com/package/jsincss) and [`computed-variables`](https://www.npmjs.com/package/computed-variables) from JavaScript, and you can build on top of them with your own plugins and your own abstractions for storing and processing style information.
The idea of Caffeinated Style Sheets, or writing CSS that's extended by JavaScript builds on top of what these plugins provide and are concerned with how to store JS-powered style information in _valid_ CSS syntax, as well as easy ways to read that information out of CSSOM and DOM so JavaScript can work with it, avoiding the need for custom syntaxes or having to express everything in JavaScript.
This is all about keeping your CSS in CSS and your Javascript in JavaScript, but finding ways to write CSS and JavaScript that compliment each other and make advanced styling techniques effortless.
### Writing Custom At-rules in CSS
You can invent custom at-rules in valid CSS syntax by extending [`@supports () {}`](https://drafts.csswg.org/css-conditional-3/#at-supports) using a custom identifier like `--custom()` or `--example()`, and if you have arguments to pass into the function to encode them as something [`JSON.parse()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/parse) can read to maximum compatibility and simplicity. This is useful for polyfilling at-rules coming to CSS like `@document`, as well as inventing your own queries, like element queries or container queries.
```css
@supports (--custom("arg1", 2, {"arg": 3})) {
div {
color: blue;
}
}
```
This is valid CSS that includes information that's simple for JavaScript to find, parse, and process, we could end up with a call to a JavaScript function like this:
```js
custom("arg1", 2, {"arg": 3}, `
div {
color: blue;
}
`)
```
> Read more about writing custom at-rules in the [deqaf readme](https://github.com/tomhodgins/deqaf#writing-extended-supports-rules-for-js-powered-at-rules)
### Writing Custom Selectors in CSS
CSS syntax also includes the ability for us to invent any attribute selector we want, so if we invent a custom attriute selector like [`[--custom]`](https://drafts.csswg.org/selectors-4/#attribute-selectors) we can be sure that will never match anything in HTML. If we have arguments to pass into the function we can encode them in a format `JSON.parse()` and read and extract that with JavaScript later. In this example it wouldn't be hard to read this and extract `custom("div", "arg1", 2, {"arg": 3})` to run with a JavaScript function named `custom()`:
```css
div[--custom='"arg1", 2, {"arg": 3}'] {
color: blue;
}
```
> Read more about writing custom selector in the [deqaf readme](https://github.com/tomhodgins/deqaf#writing-extended-selectors-for-js-powered-rules)
### Writing Custom Properties in CSS
CSS already includes the ability for us to define [custom properties](https://drafts.csswg.org/css-variables/) as long as we start the name with a double-dash `--` to ensure it never collides with any future CSS property. What's great about custom properties (aka css variables) in CSS is that they can be defined and set in CSSOM (css stylesheets) or in DOM (html `style=""` attribute), and can be read and written from JavaScript. This makes them an amazing way for JavaScript functions to supply values to CSS that it can use for styling:
In CSS:
```css
div {
--custom: ["arg1", 2, {"arg": 3}];
color: var(--custom);
}
```
> Read more about some ways you can use the `computed-variables` to write JS-powered CSS custom properties in the [computed-variables readme](https://github.com/tomhodgins/computed-variables#usage)
or in HTML:
```html
<div style='--custom: ["arg1", 2, {"arg": 3}];'></div>
```
### Slides to the “Caffeinated Style Sheets” Talk
- [Slides to “Caffeinated Style Sheets”](https://tomhodgins.com/caffeinated-style-sheets.pdf) given at [FITC Web Unleashed 2018](https://fitc.ca/presentation/caffeinated-style-sheets-extending-css-with-javascript/)
## Demos
- [deqaf-demo](https://github.com/tomhodgins/deqaf-demo)
- [qaffeine-demo](https://github.com/tomhodgins/qaffeine-demo)
- [`#merryCSSmas` plugin roundup with deqaf](https://gist.github.com/tomhodgins/c22973a0990248b244cd56c7641b31f0)
- [`#merryCSSmas` plugin roundup with qaffeine](https://gist.github.com/tomhodgins/f483eff2a5345b9a890388eb4cbe296a)
- [Caffeinated Style Sheets collection on Codepen](https://codepen.io/collection/DNjKgR/)
- [Computed Variables collection on Codepen](https://codepen.io/collection/DJNaar/)
## Plugins
### Event-Driven Style Managers (CSS reprocessors)
- [jsincss](https://github.com/tomhodgins/jsincss) (manage dynamic stylesheets)
- [computed-variables](https://github.com/tomhodgins/computed-variables) (update CSS variable values)
### Parse JS-powered Styles from CSS
- [deqaf](https://github.com/tomhodgins/deqaf) (parse CSSOM client-side)
- [qaffeine](https://github.com/tomhodgins/qaffeine) (parse `.css` files server-side)
### Building Blocks for CSS Tooling
- [parse-css-stylesheet](https://github.com/tomhodgins/parse-css-stylesheet)
- [parse-css-rule](https://github.com/tomhodgins/parse-css-rule)
- [process-css-rules](https://github.com/tomhodgins/process-css-rules)
- [stringify-css-stylesheet](https://github.com/tomhodgins/stringify-css-stylesheet)
- [stringify-css-rule](https://github.com/tomhodgins/stringify-css-rule)
- [css-polyfill-patterns](https://github.com/tomhodgins/css-polyfill-patterns)
- [element-query-tests](https://github.com/tomhodgins/element-query-tests)
- [element-unit-tests](https://github.com/tomhodgins/element-unit-tests)
### Plugins Compatible with `jsincss`, `deqaf`, and `qaffeine`
#### Custom At-rule Plugins
- [jsincss-viewport](https://github.com/tomhodgins/jsincss-viewport)
- [jsincss-overflow](https://github.com/tomhodgins/jsincss-overflow)
- [jsincss-protocol-sniffer](https://github.com/tomhodgins/jsincss-protocol-sniffer)
- [jsincss-days](https://github.com/tomhodgins/jsincss-days)
- [element queries](https://github.com/tomhodgins/jsincss-element-query)
- [@document](https://codepen.io/tomhodgins/pen/ePQMpe)
- [navigator queries](https://codepen.io/tomhodgins/pen/bOgOdJ)
- [`localStorage` and `sessionStorage` queries](https://codepen.io/tomhodgins/pen/XoMYwy)
- [date queries](https://codepen.io/tomhodgins/pen/yGMqgR)
#### Custom Selector Plugins
- [jsincss-parent-selector](https://github.com/tomhodgins/jsincss-parent-selector)
- [jsincss-has-selector](https://github.com/tomhodgins/jsincss-has-selector)
- [jsincss-closest-selector](https://github.com/tomhodgins/jsincss-closest-selector)
- [jsincss-first-selector](https://github.com/tomhodgins/jsincss-first-selector)
- [jsincss-last-selector](https://github.com/tomhodgins/jsincss-last-selector)
- [jsincss-elder-selector](https://github.com/tomhodgins/jsincss-elder-selector)
- [jsincss-previous-selector](https://github.com/tomhodgins/jsincss-previous-selector)
- [jsincss-string-match](https://github.com/tomhodgins/jsincss-string-match)
- [jsincss-regex-match](https://github.com/tomhodgins/jsincss-regex-match)
- [jsincss-custom-specificity](https://github.com/tomhodgins/jsincss-custom-specificity)
- [computed style selector](https://codepen.io/tomhodgins/pen/wYqjzY)
- [nth-letter and nth-word](https://codepen.io/tomhodgins/pen/YJZyPr)
- [playing, paused, muted, and current-time pseudo-classes for `<video>` and `<audio>`](https://codepen.io/tomhodgins/pen/aRWqro)
- [not-blank valid/invalid selector](https://codepen.io/tomhodgins/pen/JevNPb)
- [compare attribute values as numbers](https://codepen.io/tomhodgins/pen/EGKJqx)
## Videos
- [Excerpt from “Caffeinated Style Sheets” talk about writing custom JS-powered selectors and custom at-rules in valid CSS syntax](https://www.youtube.com/watch?v=kGGMQvxB3WI)
- [Methods of Extending CSS Selectors and At-Rules with JavaScript ](https://www.youtube.com/watch?v=ai6dIdVeGic)
- [Defining Custom At-Rules in CSS (extending CSS with JavaScript)](https://www.youtube.com/watch?v=CJsnUC72iII)
- [An Approach for Defining Custom Events for JS-powered Rules Inside CSS Stylesheets](https://www.youtube.com/watch?v=ZExsj1OdSK4)
- [Using JS-Powered Custom Pseudo Classes from CSS](https://www.youtube.com/watch?v=-4vdpxgftW4)
### Explorations and Experiments
- [Building your own CSS Preprocessor](https://www.youtube.com/watch?v=WEkgIiwduFs)
- [Live Stream: CSS Variable Experiments](https://www.youtube.com/watch?v=UwJfbLcsYmk)
- [Live Stream: Extending CSS with JavaScript (Using Qaffeine to parse extended CSS)](https://www.youtube.com/watch?v=6pRRB1gXgPo) | 61.070175 | 596 | 0.763765 | eng_Latn | 0.703459 |
055dd97b19e752c5077560ca06d06d85c5e3e609 | 705 | md | Markdown | 2020/CVE-2020-8799.md | justinforbes/cve | 375c65312f55c34fc1a4858381315fe9431b0f16 | [
"MIT"
] | 2,340 | 2022-02-10T21:04:40.000Z | 2022-03-31T14:42:58.000Z | 2020/CVE-2020-8799.md | justinforbes/cve | 375c65312f55c34fc1a4858381315fe9431b0f16 | [
"MIT"
] | 19 | 2022-02-11T16:06:53.000Z | 2022-03-11T10:44:27.000Z | 2020/CVE-2020-8799.md | justinforbes/cve | 375c65312f55c34fc1a4858381315fe9431b0f16 | [
"MIT"
] | 280 | 2022-02-10T19:58:58.000Z | 2022-03-26T11:13:05.000Z | ### [CVE-2020-8799](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8799)
### Description
A Stored XSS vulnerability has been found in the administration page of the WTI Like Post plugin through 1.4.5 for WordPress. Once the administrator has submitted the data, the script stored is executed for all the users visiting the website.
### POC
#### Reference
- https://wpvulndb.com/vulnerabilities/10210
#### Github
No PoCs found on GitHub currently.
| 39.166667 | 242 | 0.75461 | eng_Latn | 0.696136 |
055e27a586d93c9d73a15d7492610ef86e816b86 | 2,637 | md | Markdown | Assignments/Assignment1/Total_results.md | JIAHONGZHANG/pythonlearn | 636ae08fefcca4e3bd195529bd5342a5032d657d | [
"MIT"
] | null | null | null | Assignments/Assignment1/Total_results.md | JIAHONGZHANG/pythonlearn | 636ae08fefcca4e3bd195529bd5342a5032d657d | [
"MIT"
] | null | null | null | Assignments/Assignment1/Total_results.md | JIAHONGZHANG/pythonlearn | 636ae08fefcca4e3bd195529bd5342a5032d657d | [
"MIT"
] | null | null | null | Ass1_Q1
Test 1 ... passed 0.1
Test 2 ... passed 0.3
Test 3 ... passed 0.3
Test 4 ... passed 0.3
Test 5 ... passed 0.3
Test 6 ... passed 0.2
Test 7 ... failed 0
Test 8 ... failed 0
Test 9 ... failed 0
Test 10 ... failed 0
Test 11 ... failed 0
Test 12 ... failed 0
Test 13 ... failed 0
Total mark 1.5
Ass1_Q2
Test 1 ... passed 0.1
Test 2 ... passed 0.1
Test 3 ... passed 0.1
Test 4 ... passed 0.1
Test 5 ... passed 0.1
Test 6 ... passed 0.1
Test 7 ... passed 0.1
Test 8 ... passed 0.2
Test 9 ... passed 0.2
Test 10 ... passed 0.2
Test 11 ... passed 0.2
Test 12 ... passed 0.2
Test 13 ... passed 0.2
Test 14 ... passed 0.2
Test 15 ... passed 0.2
Test 16 ... passed 0.2
Total mark 2.5
Ass1_Q3
Test 1 ... passed 0.1
Test 2_1 ... passed 0.05
Test 2_2 ... passed 0.05
Test 3_1 ... passed 0.05
Test 3_2 ... passed 0.05
Test 4_1 ... passed 0.1
Test 4_2 ... passed 0.1
Test 5_1 ... passed 0.1
Test 5_2 ... passed 0.1
Test 6_1 ... passed 0.1
Test 6_2 ... passed 0.1
Test 7_1 ... passed 0.1
Test 7_2 ... passed 0.1
Test 8_1 ... passed 0.1
Test 8_2 ... passed 0.1
Test 9_1 ... passed 0.1
Test 9_2 ... passed 0.1
Test 10_1 ... passed 0.1
Test 10_2 ... passed 0.1
Test 11_1 ... passed 0.1
Test 11_2 ... passed 0.1
Test 12_1 ... passed 0.1
Test 12_2 ... passed 0.1
Test 13_1 ... passed 0.1
Test 13_2 ... passed 0.1
Test 14_1 ... passed 0.1
Test 14_2 ... passed 0.1
Test 15 ... failed 0
Test 16 ... failed 0
Test 17 ... failed 0
Test 18 ... failed 0
Test 19 ... failed 0
Total mark 2.50
Ass1_Q4
Test 1_1 ... passed 0.1
Test 1_2 ... passed 0.05
Test 1_3 ... passed 0.05
Test 1_4 ... passed 0.05
Test 2_1 ... passed 0.1
Test 2_2 ... passed 0.05
Test 2_3 ... passed 0.05
Test 2_4 ... passed 0.05
Test 2_5 ... failed 0
Test 3_1 ... passed 0.1
Test 3_2 ... passed 0.05
Test 3_3 ... passed 0.05
Test 3_4 ... passed 0.05
Test 3_5 ... passed 0.05
Test 3_6 ... passed 0.05
Test 4_1 ... passed 0.05
Test 4_2 ... passed 0.05
Test 4_3 ... passed 0.05
Test 4_4 ... passed 0.05
Test 4_5 ... passed 0.05
Test 4_6 ... passed 0.05
Test 4_7 ... passed 0.05
Test 4_8 ... passed 0.05
Test 5_1 ... passed 0.05
Test 5_2 ... passed 0.05
Test 5_3 ... passed 0.05
Test 5_4 ... passed 0.05
Test 6_1 ... passed 0.05
Test 6_2 ... passed 0.05
Test 6_3 ... passed 0.05
Test 6_4 ... passed 0.05
Test 6_5 ... passed 0.1
Test 6_6 ... passed 0.1
Test 6_7 ... passed 0.1
Test 7_1 ... passed 0.1
Test 7_2 ... passed 0.1
Test 7_3 ... passed 0.1
Test 7_4 ... passed 0.05
Test 7_5 ... passed 0.05
Test 7_6 ... passed 0.05
Test 7_7 ... passed 0.05
Total mark 2.45
| 11.72 | 24 | 0.599924 | eng_Latn | 0.31767 |
055ea9fdc83704feef7fb95e6cfa774ff6d50abe | 6,161 | md | Markdown | README.md | sighthoundinc/react-video-js-player | ecc7844f0f5a4e3691c1fb47108f97b84d248bfe | [
"0BSD"
] | null | null | null | README.md | sighthoundinc/react-video-js-player | ecc7844f0f5a4e3691c1fb47108f97b84d248bfe | [
"0BSD"
] | null | null | null | README.md | sighthoundinc/react-video-js-player | ecc7844f0f5a4e3691c1fb47108f97b84d248bfe | [
"0BSD"
] | null | null | null | # react-video-js-player
This is NOT an npm module any longer!
Originally forked from [https://github.com/karan101292/react-video-js-player](https://github.com/karan101292/react-video-js-player).
Converted (roughly) to TypeScript, to be included directly into projects. Contains additional features, fixes, etc.
This is a soft-package and is meant to be included directly into project. There is no package.json, so you will need to make sure your main project includes the following packages:
* video-js@^7.6
* react
## Usage
```javascript
import React from 'react';
import VideoPlayer from 'pkg/react-video-js-player';
class VideoApp extends React.Component {
player = {}
state = {
video: {
src: "http://www.example.com/path/to/video.mp4",
poster: "http://www.example.com/path/to/video_poster.jpg"
}
}
onPlayerReady(player){
console.log("Player is ready: ", player);
this.player = player;
}
onVideoPlay(duration){
console.log("Video played at: ", duration);
}
onVideoPause(duration){
console.log("Video paused at: ", duration);
}
onVideoTimeUpdate(duration){
console.log("Time updated: ", duration);
}
onVideoSeeking(duration){
console.log("Video seeking: ", duration);
}
onVideoSeeked(from, to){
console.log(`Video seeked from ${from} to ${to}`);
}
onVideoEnd(){
console.log("Video ended");
}
render() {
return (
<div>
<VideoPlayer
controls={true}
src={this.state.video.src}
poster={this.state.video.poster}
width="720"
height="420"
onReady={this.onPlayerReady.bind(this)}
onPlay={this.onVideoPlay.bind(this)}
onPause={this.onVideoPause.bind(this)}
onTimeUpdate={this.onVideoTimeUpdate.bind(this)}
onSeeking={this.onVideoSeeking.bind(this)}
onSeeked={this.onVideoSeeked.bind(this)}
onEnd={this.onVideoEnd.bind(this)}
/>
</div>
);
}
}
export default VideoApp;
```
### VideoJS APIs support:
> onReady will return <code>videojs</code> instance. Which means you can use all the APIs provided by VideoJS.<br/>[List of VideoJS APIs](https://docs.videojs.com/docs/api/player.html)
### VideoJS plugins support:
> Since most of the VideoJS plugins needs <code>videojs</code> instance to get initialized, it is very easy to integrate any of the available plugins by making use of <code>videojs</code> instance returnd by onReady event.<br/>[List of VideoJS plugins](https://videojs.com/plugins/)
### Available Props:
<table>
<thead>
<tr>
<th>Prop Name</th>
<th>Prop Type</th>
<th>Default Value</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>src</td>
<td><code>string</code></td>
<td><code>""</code></td>
<td>Video file path</td>
</tr>
<tr>
<td>poster</td>
<td><code>string</code></td>
<td><code>""</code></td>
<td>Video poster file path</td>
</tr>
<tr>
<td>width</td>
<td><code>string | number</code></td>
<td><code>auto</code></td>
<td>Video player width</td>
</tr>
<tr>
<td>height</td>
<td><code>string | number</code></td>
<td><code>auto</code></td>
<td>Video player height</td>
</tr>
<tr>
<td>controls</td>
<td><code>boolean</code></td>
<td><code>true</code></td>
<td>Video player control bar toggle</td>
</tr>
<tr>
<td>autoplay</td>
<td><code>boolean</code></td>
<td><code>false</code></td>
<td>Video will start playing automatically if <code>true</code></td>
</tr>
<tr>
<td>preload</td>
<td><code>string</code></td>
<td><code>auto</code></td>
<td>video tag preload attribute</td>
</tr>
<tr>
<td>playbackRates</td>
<td><code>array</code></td>
<td><code>[0.5, 1, 1.5, 2]</code></td>
<td>Video speed control</td>
</tr>
<tr>
<td>hideControls</td>
<td><code>array</code></td>
<td><code>[]</code></td>
<td>List of controls to hide. <code>['play','volume','seekbar','timer','playbackrates','fullscreen']</code></td>
</tr>
<tr>
<td>bigPlayButton</td>
<td><code>boolean</code></td>
<td><code>true</code></td>
<td>Big play button visibility toggle</td>
</tr>
<tr>
<td>bigPlayButtonCentered</td>
<td><code>boolean</code></td>
<td><code>true</code></td>
<td>Big play button center position toggle</td>
</tr>
<tr>
<td>className</td>
<td><code>string</code></td>
<td><code>""</code></td>
<td>Video player wrapper class. It can be used for custom player skin.</td>
</tr>
</tbody>
</table>
### Video tracking props:
<table>
<thead>
<tr>
<th>Method Name</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>onReady</td>
<td>It will fire when video player is ready to be used. It returns <code>videojs</code> instance.</td>
</tr>
<tr>
<td>onPlay</td>
<td>It will fire when video starts playing anytime. It returns current time of the video</td>
</tr>
<tr>
<td>onPause</td>
<td>It will fire when video is paused. It returns current time of the video</td>
</tr>
<tr>
<td>onTimeUpdate</td>
<td>It keeps firing while video is in playing state. It returns current time of the video</td>
</tr>
<tr>
<td>onSeeking</td>
<td>It will fire when video is being seeked using seekbar. It returns current time of the video</td>
</tr>
<tr>
<td>onSeeked</td>
<td>It will fire after seeking is done. It returns seek start time and seek end time for the video.</td>
</tr>
<tr>
<td>onEnd</td>
<td>It will fire when video is finished playing.</td>
</tr>
</tbody>
</table>
| 29.061321 | 283 | 0.571985 | eng_Latn | 0.730831 |
055ff45b7607b5191a2ae951a36934cddabcccf9 | 566 | md | Markdown | README.md | GuilhermeJC13/Bob_the_story_teller | f65286ec3de1398d98c1b8260c60aa812b85abd1 | [
"MIT"
] | null | null | null | README.md | GuilhermeJC13/Bob_the_story_teller | f65286ec3de1398d98c1b8260c60aa812b85abd1 | [
"MIT"
] | null | null | null | README.md | GuilhermeJC13/Bob_the_story_teller | f65286ec3de1398d98c1b8260c60aa812b85abd1 | [
"MIT"
] | null | null | null | # Bob_the_story_teller
The initial idea was to create a chatbot called Bob, but during the development, I decided to test it using a model built together with [TAIL - Technology and Artificial Intelligence League](https://www.linkedin.com/company/tailufpb/) aimed at generating horror stories.
The Hugging Face transformers library was used for the text generation model and the pygame library for the interface. In this project, I learned a lot about how transformers work (state-of-the-art of NLP), and its use in practice, both in training and for generation.
| 80.857143 | 270 | 0.800353 | eng_Latn | 0.999078 |
0561b710dd152a08b94c7cf278e60161b003a572 | 176 | md | Markdown | content/story/HUAWEI_Mate_10_Lite+Mainz+Toy_at_Goethe_Square.md | pzhaonet/w | c752f60cd3dc31de16f8a9b061182cc549d53607 | [
"MIT"
] | null | null | null | content/story/HUAWEI_Mate_10_Lite+Mainz+Toy_at_Goethe_Square.md | pzhaonet/w | c752f60cd3dc31de16f8a9b061182cc549d53607 | [
"MIT"
] | null | null | null | content/story/HUAWEI_Mate_10_Lite+Mainz+Toy_at_Goethe_Square.md | pzhaonet/w | c752f60cd3dc31de16f8a9b061182cc549d53607 | [
"MIT"
] | null | null | null | +++
title = "Toy at Goethe Square. Mainz, 2018-10-14. Camera: HUAWEI Mate 10 Lite."
date = "2018-10-14"
image = "/story/HUAWEI_Mate_10_Lite+Mainz+Toy_at_Goethe_Square.jpg"
+++
| 29.333333 | 79 | 0.715909 | yue_Hant | 0.350653 |
05625c8b5283bb924993e90c30fc211977e966cc | 8,051 | md | Markdown | README.md | fmassart/tezos-link | c4827e38f9795918b8682189bf727fa5034ee3b1 | [
"Apache-2.0"
] | 12 | 2020-02-20T10:01:23.000Z | 2021-08-03T20:46:07.000Z | README.md | fmassart/tezos-link | c4827e38f9795918b8682189bf727fa5034ee3b1 | [
"Apache-2.0"
] | 65 | 2020-03-09T08:55:21.000Z | 2021-03-31T19:50:57.000Z | README.md | fmassart/tezos-link | c4827e38f9795918b8682189bf727fa5034ee3b1 | [
"Apache-2.0"
] | 6 | 2020-02-11T10:43:22.000Z | 2022-01-17T11:49:41.000Z | # Tezos Link
[](https://goreportcard.com/report/github.com/octo-technology/tezos-link) 
Tezos link is a gateway to access to the Tezos network aiming to improve developer experience when developing Tezos dApps.
# Table of Contents
- [Project organization](#project-organization)
- [Run services locally on the machine](#run-services-locally-on-the-machine)
- [Build all services](#build-all-services)
- [Tests all services](#tests-all-services)
- [Frontend](#frontend)
- [Services](#services)
- [API](#api)
- [Proxy](#proxy)
- [Snapshot exporter](#snapshot-exporter)
- [Infrastructure](#infrastructure)
- [Architecture](#architecture)
- [Requirements](#requirements)
- [How To Deploy](#how-to-deploy)
- [Documentation](#documentation)
- [References](#references)
# Project Organization
The repository is currently following this organization:
```
.
├── api # api documentation
├── build # packaging
├── cmd # mains
├── config # config parsers
├── data # config and migrations
├── infra # infrastructure
├── internal # services
├── test # test-specific files
└── web # frontend
└── public
└── docs # usage documentation
```
## Run services locally on the machine with mockup blockchain node
> Blockchain nodes are mocked up for development environment the be as lightweight as possible.
### Requirements
- `Docker`
- `docker-compose`
- `Yarn` (setup with 1.22.0)
- `Golang` (setup with 1.13)
- `GNU Make` (setup with 3.81)
- `Node.js` (setup with 11.14.0)
### How to
To run services locally on the machine, you will need to run those commands :
```bash
$> make deps
$> make build-docker
$> make run-dev
```
It will run:
- `tezos-link_proxy`
- `tezos-link_proxy-carthagenet`
- `tezos-link_api`
- `mockserver/mockserver:mockserver-5.9.0` (mocking a blockchain node)
- `postgres:9.6`
The only endpoint served by the blockchain mock is:
```bash
curl -X PUT localhost:8001/v1/<YOUR_PROJECT_ID>/mockserver/status
```
## Test all services
### Requirements
- `Golang` (setup with 1.13)
- `GNU Make` (setup with 3.81)
For integrations tests only:
- `Docker`
- `docker-compose`
- `yarn`
### How to
To run the `unit tests`, you can use the command
```bash
$> make unit-test
```
To run `integration tests` locally, you will need to run following commands :
```bash
# We build docker images and run them
$> make build-docker & make run
# We run integration tests...
$> make integration-test
# And we clean the environment when we are done
$> docker-compose down
```
## Build all services and frontend
### Requirements
- `GNU Make` (setup with 3.81)
- `Golang` (setup with 1.13)
- `Yarn` (setup with 1.22.0)
- `Node.js` (setup with 11.14.0)
### How to
To build your project, you need first to `install dependencies`:
```bash
$> make deps
```
After, you can run the `build` with
```bash
$> make build
```
## Frontend
### Requirements
- `Yarn` (setup with 1.22.0)
- `Node.js` (setup with 11.14.0)
To build the frontend, you need first to `install dependencies`:
```bash
$> make deps
```
### Run
To run the frontend, execute:
```bash
$> cd web && yarn start-local
```
### Build
To run the frontend, execute:
```bash
$> make build-frontend
```
### Deploy
> You will need AWS credentials setup on your machine, see [AWS Credentials](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html)
To run the frontend, execute:
```bash
$> make deploy-frontend
```
## Services
### API
REST API to manage projects and get project's metrics.
#### Dependencies
- `PostgreSQL` (setup with 9.6)
#### Environment variables
- `DATABASE_URL` (default: `postgres:5432`)
- `DATABASE_USERNAME` (default: `user`)
- `DATABASE_PASSWORD` (default: `pass`)
- `DATABASE_TABLE` (default: `tezoslink`)
- `DATABASE_ADDITIONAL_PARAMETER` (default: `sslmode=disable`)
- `SERVER_HOST` (default: `localhost`)
- `SERVER_PORT` (default: `8000`)
### Proxy
- HTTP proxy in front of the nodes
- In-memory (LRU) cache
#### Dependencies
- `PostgreSQL` (setup with 9.6)
#### Environment variables
- `DATABASE_URL` (default: `postgres:5432`)
- `DATABASE_USERNAME` (default: `user`)
- `DATABASE_PASSWORD` (default: `pass`)
- `DATABASE_TABLE` (default: `tezoslink`)
- `DATABASE_ADDITIONAL_PARAMETER` (default: `sslmode=disable`)
- `ARCHIVE_NODES_URL` (default: `node`)
- `TEZOS_ARCHIVE_PORT` (default: `1090`)
- `ROLLING_NODES_URL` (default: `node`)
- `TEZOS_ROLLING_PORT` (default: `1090`)
- `SERVER_PORT` (default: `8001`)
### Snapshot exporter lambda
Lambda function scheduled with a `Cloudwatch Rule` cronjob, connect to a node with SSH and trigger a snapshot export.
#### Deploy for testing and for development purpose
Individual deployment of the lambda is possible for testing and development purpose.
> You will need AWS credentials setup on your machine, see [AWS Credentials](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html)
It will build, send to the S3 bucket and update snapshot lambda code:
```bash
$> make build-unix
$> make deploy-snapshot-lambda
```
To execute the lambda, run:
```bash
aws lambda invoke --region=eu-west-1 --function-name=snapshot --log Tail output.txt | grep "LogResult"| awk -F'"' '{print $4}' | base64 --decode
```
### Metrics cleaner lambda
Lambda function scheduled with a `Cloudwatch Rule` cronjob, connect to a node with SSH and trigger a metrics clean.
#### Deploy for testing and development purpose
Individual deployment of the lambda is possible for testing and development purpose.
> You will need AWS credentials setup on your machine, see [AWS Credentials](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html)
It will build, send to the S3 bucket and update metrics-cleaner lambda code:
```bash
$> make build-unix
$> make deploy-metrics-cleaner-lambda
```
To execute the lambda, run:
```bash
aws lambda invoke --region=eu-west-1 --function-name=metrics --log Tail output.txt | grep "LogResult"| awk -F'"' '{print $4}' | base64 --decode
```
#### Environment variables
These environment variables are set in `infra/dev.tfvars`.
- `NODE_USER` (default: `ec2-user`)
- `S3_REGION` (default: `eu-west-1`)
- `S3_BUCKET` (default: `tzlink-snapshot-lambda-dev`)
- `S3_LAMBDA_KEY` (default: `snapshot_lambda_key`)
## Infrastructure
### Architecture
### Requirements
- `Terraform` (version == 0.12.20)
- `Terragrunt` (version == 0.21.4)
> We recommend to install `tf-env` to manage easily your terraform environments.
### How to deploy
All the files related to the infrastructure are based on the `infra` folder.
First, you will need to update the configuration (if needed). To do this, you will find `common.tfvars` and `<env>.tfvars` in the folder `infra/terragrunt`.
> Currently, database password is encrypted inside the file `vaulted.tfvars`. To see it content, you will need ansible-vault and a passphrase to decrypt it with the command `ansible-vault decrypt vaulted.tfvars`.
>
> This will be changed soon with AWS Secret Manager.
When they are updated, we will use Terragrunt to deploy our infrastructure by running:
```bash
# To check if all is OK
$> terragrunt plan-all
# To apply the change
$> terragrunt apply-all
```
If you want to apply a specific part of the infrastructure (ex: `00_network`), you can run
```bash
$> cd infra/terragrunt/00_network
# To check if all is OK
$> terragrunt plan
# To apply the change
$> terragrunt apply
```
## Documentation
The documentation usage is located at `web/public/docs`.
It contains the various Markdown files served by the application at `/documentation`.
## References
This repo took some ideas & code from:
- https://github.com/tezexInfo/TezProxy
- https://github.com/AymericBethencourt/serverless-mern-stack/
| 24.323263 | 256 | 0.710471 | eng_Latn | 0.883379 |
0562a0ef3b3a8fb0583a6832e102f20d3af9f039 | 560 | md | Markdown | knowledge-base/grid-load-on-demand-hierarchy.md | mihail-vladov/blazor-docs | d42cec9c669bc80c941db343e786fc5d3e742813 | [
"Apache-2.0"
] | 35 | 2019-05-07T16:49:20.000Z | 2022-03-01T14:58:59.000Z | knowledge-base/grid-load-on-demand-hierarchy.md | mihail-vladov/blazor-docs | d42cec9c669bc80c941db343e786fc5d3e742813 | [
"Apache-2.0"
] | 310 | 2019-05-01T05:16:58.000Z | 2022-03-28T11:46:33.000Z | knowledge-base/grid-load-on-demand-hierarchy.md | mihail-vladov/blazor-docs | d42cec9c669bc80c941db343e786fc5d3e742813 | [
"Apache-2.0"
] | 50 | 2019-04-27T13:44:17.000Z | 2022-03-15T15:54:01.000Z | ---
title: Load data on demand in a Hierarchy Grid
description: How to load data on demand when you have Hierarchy Grid.
type: how-to
page_title: Load data on demand in a Hierarchy Grid
slug: grid-kb-load-on-demand-hierarchy
position:
tags:
res_type: kb
---
## Description
How to load data on demand when you have Hierarchy Grid?
## Solution
An example is available in the following project: [https://github.com/telerik/blazor-ui/tree/master/grid/load-on-demand-hierarchy](https://github.com/telerik/blazor-ui/tree/master/grid/load-on-demand-hierarchy). | 29.473684 | 211 | 0.767857 | eng_Latn | 0.783711 |
0562a3910ebc1a3cf9502ad819746837656071c6 | 102 | md | Markdown | README.md | dggsax/EmmetTree | 42aa1e26071ac64d2152333d45a23195cd073f7a | [
"MIT"
] | null | null | null | README.md | dggsax/EmmetTree | 42aa1e26071ac64d2152333d45a23195cd073f7a | [
"MIT"
] | 291 | 2020-02-26T06:11:17.000Z | 2022-02-26T22:53:00.000Z | README.md | dggsax/EmmetTree | 42aa1e26071ac64d2152333d45a23195cd073f7a | [
"MIT"
] | null | null | null | # EmmetTree
This is an app for 6.811, Principles and Practices of Assistive Technology (ppat.mit.edu)
| 34 | 89 | 0.784314 | eng_Latn | 0.988539 |
05631468b3db22d26a024a40b5c72563e75b75eb | 513 | md | Markdown | README.md | vijayraavi/WAWSDeploy | 97ed9cbe7ca10a7a52cbcc89fa04711d68034a90 | [
"Apache-2.0"
] | null | null | null | README.md | vijayraavi/WAWSDeploy | 97ed9cbe7ca10a7a52cbcc89fa04711d68034a90 | [
"Apache-2.0"
] | null | null | null | README.md | vijayraavi/WAWSDeploy | 97ed9cbe7ca10a7a52cbcc89fa04711d68034a90 | [
"Apache-2.0"
] | 2 | 2019-02-12T06:45:03.000Z | 2019-05-31T04:21:56.000Z | WAWSDeploy
==========
Simple command line tool to deploy a folder or a zip file to an Azure Website using WebDeploy. See this [post](http://blog.davidebbo.com/2014/03/WAWSDeploy.html)
for details.
Sample use:
WAWSDeploy c:\somefolder mysite.PublishSettings
WAWSDeploy c:\somefile.zip mysite.PublishSettings
With optional password argument
WAWSDeploy c:\somefolder mysite.PublishSettings /p mypubsettingspassword
WAWSDeploy c:\somefolder mysite.PublishSettings /password mypubsettingspassword
| 32.0625 | 161 | 0.787524 | eng_Latn | 0.66638 |
0563e3595262f445fc393f930986108d9a5eb346 | 311 | md | Markdown | user/pages/blog/interface-design-basics/post.md | itsligo/blog.jkelleher.me | ad83a77c4122ce6ed9c7bcc42b7ea5ff082b5678 | [
"MIT"
] | null | null | null | user/pages/blog/interface-design-basics/post.md | itsligo/blog.jkelleher.me | ad83a77c4122ce6ed9c7bcc42b7ea5ff082b5678 | [
"MIT"
] | null | null | null | user/pages/blog/interface-design-basics/post.md | itsligo/blog.jkelleher.me | ad83a77c4122ce6ed9c7bcc42b7ea5ff082b5678 | [
"MIT"
] | null | null | null | ---
title: Interface Design Basics
date: 2010/02/04 12:26:00
taxonomy:
category: blog
---
[Interface Design Basics (english)](http://www.slideshare.net/smoofles/interface-design-basics-2182094)
View more [presentations](http://www.slideshare.net/) from [Samo Korošec](http://www.slideshare.net/smoofles).
| 25.916667 | 110 | 0.745981 | yue_Hant | 0.722128 |
0564ea9d28dc338be96d082ed9f9cf34598c908b | 52 | md | Markdown | README.md | garoa/PenseBem | 30c182021d4097887c969877279ae47e02588e69 | [
"Unlicense"
] | null | null | null | README.md | garoa/PenseBem | 30c182021d4097887c969877279ae47e02588e69 | [
"Unlicense"
] | 1 | 2015-07-22T20:12:18.000Z | 2015-07-22T20:12:18.000Z | README.md | garoa/PenseBem | 30c182021d4097887c969877279ae47e02588e69 | [
"Unlicense"
] | null | null | null | PenseBem
========
Documentação técnica do PenseBem
| 10.4 | 32 | 0.711538 | por_Latn | 0.985804 |
05653076ef6821b4f1f7da537b1d3e588d1c2cdc | 73 | md | Markdown | README.md | KaueB/Mini-Projetos | 8a613c304f9b7220dc608a9f0884889e2ab7855a | [
"MIT"
] | null | null | null | README.md | KaueB/Mini-Projetos | 8a613c304f9b7220dc608a9f0884889e2ab7855a | [
"MIT"
] | null | null | null | README.md | KaueB/Mini-Projetos | 8a613c304f9b7220dc608a9f0884889e2ab7855a | [
"MIT"
] | null | null | null | # Mini Projetos
Mini jogos, mais para treinar programação em JavaScript
| 24.333333 | 56 | 0.808219 | por_Latn | 0.99999 |
05663f26d06e510073719bf9fde83c7298a3ab6c | 39 | md | Markdown | E2E_NewRepo_1489641296629/index.md | v-peliao/E2E_NewRepo_1489641296629 | 12b89f143889ed12dcfb23a00df0d7435b593f96 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | E2E_NewRepo_1489641296629/index.md | v-peliao/E2E_NewRepo_1489641296629 | 12b89f143889ed12dcfb23a00df0d7435b593f96 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | E2E_NewRepo_1489641296629/index.md | v-peliao/E2E_NewRepo_1489641296629 | 12b89f143889ed12dcfb23a00df0d7435b593f96 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | # Welcome to E2E_NewRepo_1489641296629! | 39 | 39 | 0.871795 | kor_Hang | 0.380739 |
0566a88a51699d148d567e000e67666e26a34092 | 1,723 | md | Markdown | README.md | chawlaKat/QuickBooks-To-CSV | a155951674f19aa7cd3cbf194d52963e5ff1961c | [
"Apache-2.0"
] | null | null | null | README.md | chawlaKat/QuickBooks-To-CSV | a155951674f19aa7cd3cbf194d52963e5ff1961c | [
"Apache-2.0"
] | null | null | null | README.md | chawlaKat/QuickBooks-To-CSV | a155951674f19aa7cd3cbf194d52963e5ff1961c | [
"Apache-2.0"
] | null | null | null | # QuickBooks-To-CSV Summary
A C# console application created using the QuickBooks SDK; queries the current company file and writes results to csv
# Value of Project
QuickBooks provides excellent functionality for creating and storing financial records. This program queries QB records based on a configuration file and outputs the information to a new csv's file.
# Dependencies
This program was created using C#, the QuickBooks Desktop SDK (QBSDK) from Intuit Developer, the CsvHelper package from Josh Close on GitHub, and the System.Web.Extensions library contained in .NET Framework.
According to the QBSDK documentation, the following QuickBooks editions are supported: "just about every member of the QuickBooks Financial Software products family, for the U.S. (2002*—2018), Canada (2003*—2018), and the UK (2003*—2018). The SDK works with all U.S. editions of QuickBooks 2006 and later except for QuickBooks for the Mac."
QuickBooks must be running with the desired company file open in order for this application to function.
# To Run
In the QuickBooks-Proof-Of-Concept/bin/Release folder, edit the config.json file to reflect the desired query elements and their respective attributes. Each must exactly match the QuickBooks object name. Save this file. Open QuickBooks to the desired company file. Run the Quicken-Proof-Of-Concept.exe file, also contained within the Release folder. One csv file will be generated for each query, saved to the same location as the program, and the names of these files will be printed to the terminal by the program.
# Links
QBSDK: https://developer.intuit.com/docs/01_quickbooks_desktop/1_get_started/00_get_started <br>
CsvHelper: https://github.com/joshclose/csvhelper
| 86.15 | 516 | 0.804411 | eng_Latn | 0.991829 |
056774d8e18d2b2841972fc2beb131cc77415fbf | 2,633 | md | Markdown | README.md | geoffreyaldebert/dashboard-dechets | fe8a63292e406ec2e2f8aafa91aa2b18a86f2115 | [
"MIT"
] | null | null | null | README.md | geoffreyaldebert/dashboard-dechets | fe8a63292e406ec2e2f8aafa91aa2b18a86f2115 | [
"MIT"
] | 3 | 2021-03-10T15:42:44.000Z | 2022-01-22T11:44:48.000Z | README.md | geoffreyaldebert/dashboard-dechets | fe8a63292e406ec2e2f8aafa91aa2b18a86f2115 | [
"MIT"
] | null | null | null | # Dashboard Dechets - Données SINOE (Expérimental)
Le dashboard est disponible ici : https://dashboard-dechets.netlify.app/
## Données
Les données du dashboard ne se concentrent que sur l'année 2017.
Les données utilisées pour construire ce dashboard sont les suivantes :
- SINOE - Tonnage DMA par type de déchets et département - téléchargeables [ici](https://www.data.gouv.fr/fr/datasets/sinoe-r-tonnage-dma-par-type-de-dechet-et-departement/)
- SINOE - Performance de collecte OMA par type de déchet et par département - téléchargeables [ici](https://www.data.gouv.fr/fr/datasets/sinoe-r-performance-de-collecte-oma-par-type-de-dechet-et-par-departement/)
- SINOE - Tonnage déchèteries par type de déchet et département, téléchargeables [ici](https://www.data.gouv.fr/fr/datasets/sinoe-r-tonnage-decheteries-par-type-de-dechet-et-departement/)
Pour compléter les données, il a également été utilisé les données de population légales de 2009 à 2017 de l'INSEE :
- Année 2017, téléchargeable [ici](https://www.insee.fr/fr/statistiques/4265511)
- Les données ont été mises en forme et stockées dans le répertoire [notebooks/insee](https://github.com/geoffreyaldebert/dashboard-dechets/tree/master/notebooks/insee) de ce repo git
## Traitement
L'ensemble des traitements tient en un seul notebook python disponible sur ce repo git ici : [notebooks/sinoe-notebook.ipynb](https://github.com/geoffreyaldebert/dashboard-dechets/blob/master/notebooks/sinoe-notebook.ipynb)
### Etapes
- Agrégation des trois fichiers sources (OMA, DMA et Déchets) en un seul tableau
- Sous-sélection du tableau sur les données 2017
- Elimination de certains types de déchets qui semblent redondants entre les trois sources de données :
- Données DMA '07A - Ordures ménageres résiduelles' (en effet les données OMA '08A - Ordures ménagères résiduelles' semblent être les mêmes)
- Données DMA '07B - Déblais et gravats' (en effet les données Déchets '02E - Déblais et gravats' semblent être les mêmes)
- Données DMA '07C - Encombrants' (en effet les données Déchets '02D - Encombrants' semblent être les mêmes)
- Données Déchets '02C - Déchets verts' (ces données semblent comprises dans les données DMA '07F - Dechets Verts et biodéchets')
- Ajout des données de populations légales INSEE au tableau
- Calcul d'un ratio TONNAGE/POPULATION*100 pour connaître le nombre de kg moyen par habitant pour chaque type de déchets
- génération de fichiers json :
- un fichier maille national
- un fichier maille régional
- un fichier maille départemental
- développement de l'application web qui se base sur les fichiers json
| 69.289474 | 223 | 0.776681 | fra_Latn | 0.944864 |
0567b0ea2e9edd9b4cac47bac2b601da93ad144d | 841 | md | Markdown | README.md | drewbassett24/EmployeeDirectory | 82c0a3fc811912fcb70eccc1fe7bcf7b8c207211 | [
"MIT"
] | 1 | 2021-09-23T16:45:22.000Z | 2021-09-23T16:45:22.000Z | README.md | drewbassett24/EmployeeDirectory | 82c0a3fc811912fcb70eccc1fe7bcf7b8c207211 | [
"MIT"
] | null | null | null | README.md | drewbassett24/EmployeeDirectory | 82c0a3fc811912fcb70eccc1fe7bcf7b8c207211 | [
"MIT"
] | null | null | null | # Employee Directory React App
## The App
This App was developed using React. It is intended to allow an employer to search his employee list using a Random User API. It can search by name and sort details with 'a click of the column'.
##Installation
No installation necessary, simply view it on Github at: https://drewbassett24.github.io/employee-directory/
##Screenshot
##Software/technology
Javascript and React. Created via Node.
##Summary
I found this pretty hard and made a lot of use of online support, such as tutorials, etc. I also had to start again at one point, so I'm not sure all my commits are reflected. In addition, deploying a React App was tricky. Which is something I'd really like to improve on, as it should be quick and easy. Apparently... | 841 | 841 | 0.776457 | eng_Latn | 0.999186 |
056d03aaf3590c8a9c8d54798a3fa11c250ac05e | 1,334 | md | Markdown | specialized/register-ec2-with-elb/README.md | elementar/docker-aws-cli | 57f00dac4628c8aed6e2473e9d477fb5627de2aa | [
"MIT"
] | null | null | null | specialized/register-ec2-with-elb/README.md | elementar/docker-aws-cli | 57f00dac4628c8aed6e2473e9d477fb5627de2aa | [
"MIT"
] | null | null | null | specialized/register-ec2-with-elb/README.md | elementar/docker-aws-cli | 57f00dac4628c8aed6e2473e9d477fb5627de2aa | [
"MIT"
] | null | null | null | # register-ec2-with-elb
[](https://cloud.docker.com/stack/deploy/)
When using an IAM Role and Docker Cloud, the deployment is quite simple. Just create a stack
pointing to this image, and change the `AWS_DEFAULT_REGION` and `LOAD_BALANCER_NAME` environment variables:
```
add-to-elb:
image: elementar/register-ec2-with-elb
autodestroy: on_success
deployment_strategy: every_node
environment:
AWS_DEFAULT_REGION: us-east-1
LOAD_BALANCER_NAME: my-load-balancer
```
If you can't use IAM Roles, you can specify the access key and secret of an IAM user
using the `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` environment variables.
## Tips
You might want to use tags to limit the machines which would be added to the Load Balancer. See
[Docker Cloud's Stack YAML Reference](https://docs.docker.com/docker-cloud/apps/stack-yaml-reference/)
for more information.
## Sample Policy
The EC2 instance must have an IAM Role with permission to add instances to the ELB. The following policy should work:
```
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "elasticloadbalancing:RegisterInstancesWithLoadBalancer",
"Resource": "*"
}
]
}
```
| 31.023256 | 132 | 0.721889 | eng_Latn | 0.753041 |
056e70502e8b6c633b3e9824473d584bb27b124f | 1,395 | md | Markdown | 2020/07/27/2020-07-27 09:05.md | zhzhzhy/WeiBoHot_history | 32ce4800e63f26384abb17d43e308452c537c902 | [
"MIT"
] | 3 | 2020-07-14T14:54:15.000Z | 2020-08-21T06:48:24.000Z | 2020/07/27/2020-07-27 09:05.md | zhzhzhy/WeiBoHot_history | 32ce4800e63f26384abb17d43e308452c537c902 | [
"MIT"
] | null | null | null | 2020/07/27/2020-07-27 09:05.md | zhzhzhy/WeiBoHot_history | 32ce4800e63f26384abb17d43e308452c537c902 | [
"MIT"
] | null | null | null | 2020年07月27日09时数据
Status: 200
1.火锅店与郑恺方和解
微博热度:3415946
2.四川安岳男子趁妻子熟睡将其杀害
微博热度:2603604
3.周奇向俞星分手
微博热度:2566703
4.顾佳和太太圈决裂
微博热度:1996818
5.美国驻成都总领事馆降下美国国旗
微博热度:1204025
6.格尔木警方通报女大学生失联情况
微博热度:1178909
7.三十而已
微博热度:1022152
8.虞书欣安崎向岳云鹏认错
微博热度:882229
9.美国驻成都总领馆开始拆除门口铭牌
微博热度:738133
10.大连新增14例确诊
微博热度:732271
11.邓伦 我会做他们一辈子的好弟弟
微博热度:722204
12.安全裤
微博热度:694053
13.深圳犬只未植入芯片被视为无证养犬
微博热度:683066
14.特警基地连保洁阿姨都会功夫
微博热度:550208
15.美国新冠肺炎超422万例
微博热度:549511
16.漫展偷拍
微博热度:548271
17.大连疫情
微博热度:547088
18.金秀贤吻戏
微博热度:544483
19.王漫妮业务能力
微博热度:543492
20.英雄联盟
微博热度:542440
21.王祖蓝给周杰伦刷了700个穿云箭
微博热度:541443
22.新疆疫情
微博热度:521954
23.吉林新增2例确诊均为大连输入
微博热度:334862
24.美驻成都总领事馆内车辆陆续驶出
微博热度:334212
25.Rookie 小钰
微博热度:314841
26.鹿晗曼联解说
微博热度:304964
27.毕侃
微博热度:292736
28.安徽三千年古镇被淹
微博热度:262406
29.奥利维娅德哈维兰去世
微博热度:260005
30.段振宇告白姜小果
微博热度:249100
31.周杰伦疯狂翻牌
微博热度:248582
32.喻言是来参加跑步比赛的
微博热度:246014
33.西藏阿里电力联网工程全线贯通
微博热度:241082
34.切尔西
微博热度:217425
35.教练你还是骂我吧
微博热度:216462
36.美国单日新增新冠病例超6万
微博热度:194993
37.何猷启已离婚
微博热度:192250
38.369
微博热度:187950
39.乃万线上演唱会
微博热度:171135
40.山东分数线
微博热度:163173
41.郑希怡刘雨昕终于见面了
微博热度:159788
42.外卖小哥皮肤大战
微博热度:152133
43.微信停止服务印度用户
微博热度:145861
44.女明星毫无偶像包袱的瞬间
微博热度:129877
45.李佳琦直播
微博热度:119630
46.淮河发生流域性较大洪水
微博热度:118235
47.你可以找到更好的工作
微博热度:117659
48.指挥家杨鸿年去世
微博热度:114451
49.央视曝光新闻App登假货广告
微博热度:113808
50.秦淮河大堤内部被指挖空建高档餐厅
微博热度:110452
| 6.838235 | 19 | 0.779928 | yue_Hant | 0.319454 |
056ebfb956a673780da7b930e1330b1db5a173db | 1,730 | md | Markdown | docs/vs-2015/cross-platform/visual-studio-tools-for-apache-cordova.md | adrianodaddiego/visualstudio-docs.it-it | b2651996706dc5cb353807f8448efba9f24df130 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/cross-platform/visual-studio-tools-for-apache-cordova.md | adrianodaddiego/visualstudio-docs.it-it | b2651996706dc5cb353807f8448efba9f24df130 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/cross-platform/visual-studio-tools-for-apache-cordova.md | adrianodaddiego/visualstudio-docs.it-it | b2651996706dc5cb353807f8448efba9f24df130 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Strumenti di Visual Studio per Apache Cordova | Microsoft Docs
ms.date: 11/15/2016
ms.topic: conceptual
ms.assetid: 21dcf46e-5d6d-439c-90e3-3d678e50c5a6
caps.latest.revision: 7
author: conceptdev
ms.author: crdun
manager: jillfra
ms.openlocfilehash: 0d0903db05b193b3318dc30c250bfdb21e76b093
ms.sourcegitcommit: 8b538eea125241e9d6d8b7297b72a66faa9a4a47
ms.translationtype: MTE95
ms.contentlocale: it-IT
ms.lasthandoff: 01/23/2019
ms.locfileid: "54785497"
---
# <a name="visual-studio-tools-for-apache-cordova"></a>Strumenti di Visual Studio per Apache Cordova
[!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
Compilare app eseguite in dispositivi iOS, Android e Windows e condividere quasi il 100% del codice. Compilare le app con le tecnologie Web preferite. Apache Cordova offre accesso nativo alle funzionalità del dispositivo, ad esempio la fotocamera di un telefono, ed è completamente gratuito. Visual Studio aggiunge queste altre funzionalità per rendere ancora più semplice la compilazione dell'app:
- Installazione e configurazione semplici.
- Debugger avanzato per individuare e risolvere i problemi.
- Accesso semplificato agli emulatori di dispositivo.
- Finestra di progettazione per gestire i plug-in del dispositivo.
- Progetto completamente compatibile con l'interfaccia della riga di comando.
Se si stanno valutando questi strumenti, ma non si è ancora pronti a provarli, visitare la pagina delle [funzionalità](https://www.visualstudio.com/explore/cordova-vs) per altre informazioni.
Se si è pronti per iniziare, vedere [sviluppo di applicazioni per dispositivi mobili con JavaScript](/visualstudio/cross-platform/tools-for-cordova/?view=toolsforcordova-2017).
| 49.428571 | 400 | 0.801734 | ita_Latn | 0.984519 |
056f8bf93a75b75fa47e04039da7ba0f22033895 | 1,333 | md | Markdown | 2020/08/26/2020-08-26 02:00.md | zhzhzhy/WeiBoHot_history | 32ce4800e63f26384abb17d43e308452c537c902 | [
"MIT"
] | 3 | 2020-07-14T14:54:15.000Z | 2020-08-21T06:48:24.000Z | 2020/08/26/2020-08-26 02:00.md | zhzhzhy/WeiBoHot_history | 32ce4800e63f26384abb17d43e308452c537c902 | [
"MIT"
] | null | null | null | 2020/08/26/2020-08-26 02:00.md | zhzhzhy/WeiBoHot_history | 32ce4800e63f26384abb17d43e308452c537c902 | [
"MIT"
] | null | null | null | 2020年08月26日02时数据
Status: 200
1.爸爸要求儿子每天户外玩2小时
微博热度:679371
2.香港发生大劫案
微博热度:522694
3.眼神放电挑战
微博热度:497314
4.梅西
微博热度:463670
5.李尖尖真的给树洞投过稿
微博热度:374120
6.我在时间的尽头等你
微博热度:371438
7.粉丝送张雨绮发掘生命中的无限可能
微博热度:260572
8.海底捞排号
微博热度:225589
9.国防部回应美军机擅闯我演习禁飞区
微博热度:221150
10.齐明月李尖尖吵架
微博热度:220391
11.北京人艺回应宋丹丹退休
微博热度:200644
12.凌霄梦到陈婷
微博热度:180151
13.马云捐出6.1亿股蚂蚁股份做公益
微博热度:172221
14.乘风破浪的爱情
微博热度:157581
15.韩国方便面向中国出口最多
微博热度:154518
16.腾蛇好可爱
微博热度:148685
17.以家人之名竖屏
微博热度:148260
18.赵一德当选陕西省省长
微博热度:146937
19.U2
微博热度:146698
20.以家人之名
微博热度:145370
21.孤寡青蛙升级换代
微博热度:144335
22.李佳琦吴昕直播
微博热度:144165
23.琉璃
微博热度:143042
24.耿爽在联合国批驳美英涉疆错误言论
微博热度:141860
25.看到情侣的我
微博热度:141532
26.釜山行2
微博热度:135012
27.央视七夕晚会
微博热度:132273
28.首个水上苹果零售店
微博热度:117662
29.外卖小哥在消防赶到前将火扑灭
微博热度:115473
30.在可可西里失联小伙已离世
微博热度:115148
31.司凤我晕了我装的
微博热度:113298
32.律师谈3岁女孩被喂到70斤做吃播
微博热度:112903
33.我的CP必须过节
微博热度:97438
34.王冰冰
微博热度:95314
35.七夕蛤蟆
微博热度:88347
36.万茜珍珠眼妆
微博热度:84949
37.肖战自拍
微博热度:81319
38.现实版跟对象过七夕
微博热度:79031
39.七夕文案
微博热度:75581
40.苏打绿演唱会
微博热度:74705
41.杜蕾斯文案
微博热度:67841
42.91个航班从首都机场转至大兴机场
微博热度:63541
43.蔡徐坤歌声温柔
微博热度:57527
44.狼殿下预告
微博热度:56074
45.拜登承诺若当选对富人加税
微博热度:53967
46.南昌6家汉堡王被罚91万
微博热度:44129
47.李书福称正在研发核酸检测汽车
微博热度:43247
48.邮政投递员将北大通知书投递给儿子
微博热度:41152
49.七夕海棠酥
微博热度:38361
50.女孩七夕替父给母亲送花
微博热度:37900
| 6.534314 | 19 | 0.770443 | yue_Hant | 0.302863 |
05714e716e64ba4fdf28beef5d43516fac8d73b5 | 1,859 | md | Markdown | article-backup/otherArticles/markdown/156-pcsx2-0-9-2-the-revenge.md | PCSX2/pcsx2-net-www | 88f85168d624aef503756d4d0f8a841a1ce38229 | [
"MIT"
] | null | null | null | article-backup/otherArticles/markdown/156-pcsx2-0-9-2-the-revenge.md | PCSX2/pcsx2-net-www | 88f85168d624aef503756d4d0f8a841a1ce38229 | [
"MIT"
] | 10 | 2022-03-26T02:24:45.000Z | 2022-03-31T02:42:52.000Z | article-backup/otherArticles/markdown/156-pcsx2-0-9-2-the-revenge.md | PCSX2/pcsx2-net-www | 88f85168d624aef503756d4d0f8a841a1ce38229 | [
"MIT"
] | null | null | null | ::: {.single-article}
::: {.item-page .clearfix}
## [PCSX2 0.9.2 - The Revenge!](/156-pcsx2-0-9-2-the-revenge.html) {#pcsx2-0.9.2---the-revenge .contentheading}
::: {style="text-align:center;"}
:::
**PCSX2 0.9.2 R2** is now available
This fixes an assortment of issues found briefly after 0.9.2's original
launch. It is **strongly** advised that people get this build of 0.9.2
over the initial release.
- Compatibility regression with **Vampire Night** resolved.
- **Final Fantasy X** now works for *most* regions.
- Fixes Crash when using *config>patches*
- Frame Limiting is now more accurate.
- Improved zeroGS, **Disgaea 2** menus are now solid.
- P.E.Op.S SPU2 updated to include threaded mode (useful for video
recording).
- Screen Saver / Power Saving now disabled when running PCSX2.
Just to cure our collective headaches "warnings about default.xml"
being blank, or "patches not found", are merely information, they do
**not** in any way effect PCSX2's compatibility or performance.
If the *config>patches* crash problem persists, grab the updated exe's
[here](/download/viewcategory/34-pcsx2-v0-9-2.html) .
We are releasing via torrent and http, **please** seed for as long as
possible with the torrents, we recommend
[uTorrent](http://www.utorrent.com/) as a client!
:: [Official Screenshots
Thread](http://forums.ngemu.com/pcsx2-official-forum/80878-post-your-pcsx2-0-9-2-screenshots-here.html)
- Post your shots from PCSX2 0.9.2 here!
:: [Files Pack](/download/viewcategory/34-pcsx2-v0-9-2.html) - 7zip
format, grab 7zip from [www.7-zip.org](http://www.7-zip.org/)
:: [Installer Pack](/download/viewcategory/34-pcsx2-v0-9-2.html) -
Executable installer, for the lazy types
:: [Downloads Section](/download/viewcategory/34-pcsx2-v0-9-2.html) -
For those of you wanting to use http transfer, rather than torrent.
:::
:::
| 40.413043 | 111 | 0.726197 | eng_Latn | 0.895296 |
0574e932e9590e63dce5fabd2c72a6db31b6d6ec | 1,519 | md | Markdown | docs/framework/unmanaged-api/debugging/icordebugassembly-getprocess-method.md | lucieva/docs.cs-cz | a688d6511d24a48fe53a201e160e9581f2effbf4 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2018-12-19T17:04:23.000Z | 2018-12-19T17:04:23.000Z | docs/framework/unmanaged-api/debugging/icordebugassembly-getprocess-method.md | lucieva/docs.cs-cz | a688d6511d24a48fe53a201e160e9581f2effbf4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/unmanaged-api/debugging/icordebugassembly-getprocess-method.md | lucieva/docs.cs-cz | a688d6511d24a48fe53a201e160e9581f2effbf4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: ICorDebugAssembly::GetProcess – metoda
ms.date: 03/30/2017
api_name:
- ICorDebugAssembly.GetProcess
api_location:
- mscordbi.dll
api_type:
- COM
f1_keywords:
- ICorDebugAssembly::GetProcess
helpviewer_keywords:
- ICorDebugAssembly::GetProcess method [.NET Framework debugging]
- GetProcess method, ICorDebugAssembly interface [.NET Framework debugging]
ms.assetid: ea52be06-0a16-4f57-afca-4287d72e76c4
topic_type:
- apiref
author: rpetrusha
ms.author: ronpet
ms.openlocfilehash: d1c3bcc0ed22fa970d92e2384277d0786016db19
ms.sourcegitcommit: 3d5d33f384eeba41b2dff79d096f47ccc8d8f03d
ms.translationtype: MT
ms.contentlocale: cs-CZ
ms.lasthandoff: 05/04/2018
ms.locfileid: "33402106"
---
# <a name="icordebugassemblygetprocess-method"></a>ICorDebugAssembly::GetProcess – metoda
Získá ukazatele rozhraní pro proces, ve kterém je spuštěna tato instance ICorDebugAssembly.
## <a name="syntax"></a>Syntaxe
```
HRESULT GetProcess (
[out] ICorDebugProcess **ppProcess
);
```
#### <a name="parameters"></a>Parametry
`ppProcess`
[out] Ukazatel na ICorDebugProcess rozhraní, které představuje proces.
## <a name="requirements"></a>Požadavky
**Platformy:** najdete v části [požadavky na systém](../../../../docs/framework/get-started/system-requirements.md).
**Záhlaví:** CorDebug.idl, CorDebug.h
**Knihovna:** CorGuids.lib
**Verze rozhraní .NET framework:** [!INCLUDE[net_current_v10plus](../../../../includes/net-current-v10plus-md.md)]
| 30.38 | 119 | 0.734036 | yue_Hant | 0.353936 |
05750c246f99b76ba767890533c652a4badb4006 | 1,153 | md | Markdown | samples/1_hello_world/README.md | gokudomatic/eco-fps-controller | 8d8783a077457c2c5bff4d9bd6c1f18290b9f18e | [
"MIT"
] | 23 | 2016-10-12T12:39:15.000Z | 2020-12-27T09:37:07.000Z | samples/1_hello_world/README.md | gokudomatic/eco-fps-controller | 8d8783a077457c2c5bff4d9bd6c1f18290b9f18e | [
"MIT"
] | 3 | 2016-10-09T13:31:15.000Z | 2017-09-11T12:27:26.000Z | samples/1_hello_world/README.md | gokudomatic/eco-fps-controller | 8d8783a077457c2c5bff4d9bd6c1f18290b9f18e | [
"MIT"
] | 5 | 2017-02-11T15:50:01.000Z | 2020-04-01T00:46:11.000Z | Demo 1 : Hello World
This demo is the simplest case of use of the eco-fps-controller. It is simply the component added to a scene with a map and collision.
The controller is by default set to no weapon and no sound. Commands are using actions (ui_up,ui_down,ui_left,ui_right,ui_jump by default; they can be changed).
This demo shows the inherent capabilities of the controller to move freely in a 3d world with collisions. Slopes (testcubes with rotation) are there to test the capability of the controller to climb them up and down while sticking to the ground. Also the ground is a plane with 2 collision planes close to each other. This is because of Godot's physic engine limitation, when a moving object with high velocity goes through thin walls. By adding a second wall, or by giving a volume to a wall, this problem can be avoided.
Moving platforms are implemented too. In Godot there's a restriction about how to determine if the floor is moving. Therefore a ground that is moving needs to be a rigid body with custom integration. And only then it can be animated with an animation player with its linear velocity automatically set up. | 164.714286 | 523 | 0.795317 | eng_Latn | 0.999944 |
0575589f3abee709f0f4d27a7cce73a97ddaf600 | 226 | md | Markdown | docs/concurrent/index.md | piqiu96/piqiu96.github.io | 7ef3c0e986f7dd392cdd72baae2b929d7a2121f1 | [
"MIT"
] | null | null | null | docs/concurrent/index.md | piqiu96/piqiu96.github.io | 7ef3c0e986f7dd392cdd72baae2b929d7a2121f1 | [
"MIT"
] | null | null | null | docs/concurrent/index.md | piqiu96/piqiu96.github.io | 7ef3c0e986f7dd392cdd72baae2b929d7a2121f1 | [
"MIT"
] | null | null | null | # 并发编程
## 并发编程
### 一、基本原理
1、程序是怎么跑起来的？ 进程/线程
2、cpu的进化，软件跟着发展？
- 速度比较：cpu读写、内存读写、磁盘读写
3、并发编程诞生？
- 原子性：线程切换问题，对于cpu来说执行指令也是串行的（count = count + 1）
- 可见性：多核，核与核之间不可见
- 有序性：编译器优化，乱序执行导致问题出现。 单例多重检查锁
a. 内存重排
b. CAS -> ABA问题
| 11.3 | 48 | 0.672566 | yue_Hant | 0.256645 |
0575c569f62ff91407659bccdc3bed75cddf1a14 | 225 | md | Markdown | _watches/M20200823_005452_TLP_5.md | Meteoros-Floripa/meteoros.floripa.br | 7d296fb8d630a4e5fec9ab1a3fb6050420fc0dad | [
"MIT"
] | 5 | 2020-01-22T17:44:06.000Z | 2020-01-26T17:57:58.000Z | _watches/M20200823_005452_TLP_5.md | Meteoros-Floripa/site | 764cf471d85a6b498873610e4f3b30efd1fd9fae | [
"MIT"
] | null | null | null | _watches/M20200823_005452_TLP_5.md | Meteoros-Floripa/site | 764cf471d85a6b498873610e4f3b30efd1fd9fae | [
"MIT"
] | 2 | 2020-05-19T17:06:27.000Z | 2020-09-04T00:00:43.000Z | ---
layout: watch
title: TLP5 - 23/08/2020 - M20200823_005452_TLP_5T.jpg
date: 2020-08-23 00:54:52
permalink: /2020/08/23/watch/M20200823_005452_TLP_5
capture: TLP5/2020/202008/20200822/M20200823_005452_TLP_5T.jpg
---
| 28.125 | 63 | 0.76 | yue_Hant | 0.052103 |
0575ed0e1b47b17d292059044fe94a0910671731 | 4,531 | md | Markdown | api/docs/Architecture.md | nicfix/monorepo-template | ec265d9e746b70e6a13a7a5e1e82f150b63a7ecf | [
"MIT"
] | 7 | 2020-06-03T06:52:22.000Z | 2021-12-27T07:02:45.000Z | api/docs/Architecture.md | nicfix/monorepo-template | ec265d9e746b70e6a13a7a5e1e82f150b63a7ecf | [
"MIT"
] | 12 | 2020-05-23T18:36:41.000Z | 2021-05-25T08:16:41.000Z | docs/Architecture.md | nicfix/py-ddd-microservice-boilerplate | 1844a8fde57dc5bbaacf6a71163beb7226041a0c | [
"MIT"
] | 1 | 2020-06-02T09:39:00.000Z | 2020-06-02T09:39:00.000Z | # Architecture
This application follows the architecture suggested in
the Cosmic Python book: https://www.cosmicpython.com/
The Cosmic Python book provides guidelines to implement
a good DDD architecture in python.
The architecture of this project is **NOT** based on:
* the Active Record pattern (Django like)
* Exagonal Architecture (even though similarities can be found)
* Clean Architecture (even though similarities can be found)
Please refer to the book's [preface](https://www.cosmicpython.com/book/preface.html)
to check how this architecture relates to the ones I mentioned before.
## Architecture Decision Record
This project includes a folder of [Architecture Decision Records](https://adr.github.io/),
check it out [here](adr/ADRs.md).
## Modules
The responsibilities in this API can be assigned to modules:
* Domain (`domain` module)
* Adapters (`adapters` module)
* Service Layer (`service_layer` module)
* Entrypoints (`entrypoints` module)
### Domain
This module implements the Ubiquitous Language specific to our Domain.
In this module are included only Pure python classes and functions that aim to have
no infrastructure dependencies (frameworks, persistence, data transfer etc).
This module has to remain portable to any other python project and testable as
a unit.
The module is further divided in 2 modules:
* `models`, including the classes that implement DDD's Entities and ValueObjects
* `service_functions`, including the functional implementation of Domain relative operations.
Please check the paragraph "Not Everything Has to Be an Object: A Domain Service Function" from the
[Cosmic Python's 1st chapter](https://www.cosmicpython.com/book/chapter_01_domain_model.html)
Best quote:
> Sometimes, it just isn’t a thing. — Eric Evans, Domain-Driven Design
Please check the [Domain](../domain/docs/README.md) documentation page for more details.
### Adapters
The Adapters implement the "adaptation" to the foundation/backing services.
As a pattern they implement the following:
* An interface that has to be used by all the clients, unaware of technological details
* A concrete implementation on top of a specific technology
The goal is to provide an easy to swap set of adaptation objects to protect
the code from changes in technological choices.
The Adapters module includes the Repository classes.
A Repository is a simplifying abstraction over data storage,
allowing us to decouple our model module from the data module.
The repositories in this module are implemented using the Adapter pattern.
Please check the paragraph "Repository Pattern" from the
[Cosmic Python's 2nd chapter](https://www.cosmicpython.com/book/chapter_02_repository.html)
### Service Layer
The Service Layer uses the Adapters and the Domain to implement services used outside.
The Services functions/classes implement a contract with external clients. Potentially only
tests against the ServiceLayer surface (interface) should be granted since the internal implementation
details of the domain model should remain hidden to external clients.
You can consider the services at the same level of the UseCases of the Exagonal Architecture/Clean Architecture.
Their interface should never expose domain objects outside and should not accept them as parameters.
Their interface should allow the injection of Repositories using the Dependency Inversion principle (SOLID).
For this reason all the services implemented in this project accept/expose DTOs (Data Transfer Objects) that
are not the domain objects, the structure of these objects is part of the "contract" of the service module.
### Entrypoints
> Entrypoints are the places we drive our application from. In the official ports and adapters terminology,
> these are adapters too, and are referred to as primary, driving, or outward-facing adapters.
The Entrypoints is the module (and the only one) that is dependent from technological choices related
to the web technology one might want to choose.
In a well implemented DDD architecture, all the technological choices are taken in the adapters/entrypoints
modules.
Some technologies might be used in the service module to facilitate serialization/deserialization and
validation (pydantinc to implement the DTOs in our case).
No technological dependencies are added to the domain module. Pure classes/functions implemented
using language functionalities as much as possible
In this project we provide one entrypoint in the form of a web application server implemented
with FastAPI.
| 43.567308 | 112 | 0.803796 | eng_Latn | 0.996471 |
05770e3afae205d8f100c4c8a7df3be94c62cae5 | 51 | md | Markdown | README.md | SubhamK108/HackerRank | 7dadbeaf589c0982f68fb5306bf5f9ca5f366a74 | [
"MIT"
] | null | null | null | README.md | SubhamK108/HackerRank | 7dadbeaf589c0982f68fb5306bf5f9ca5f366a74 | [
"MIT"
] | null | null | null | README.md | SubhamK108/HackerRank | 7dadbeaf589c0982f68fb5306bf5f9ca5f366a74 | [
"MIT"
] | null | null | null | # HackerRank
Some Coding problems from HackerRank.
| 17 | 37 | 0.823529 | eng_Latn | 0.985698 |
0578afa188e773ed6f56ecb9688f6d08d930590c | 1,385 | md | Markdown | README.md | AmeyaWagh/Traffic_sign_detection_YOLO | dbba46709fc5e60259078e2a3ebcb50fde5a2fe9 | [
"MIT"
] | 49 | 2018-02-28T21:50:06.000Z | 2022-03-14T15:18:44.000Z | README.md | AmeyaWagh/Traffic_sign_detection_YOLO | dbba46709fc5e60259078e2a3ebcb50fde5a2fe9 | [
"MIT"
] | 10 | 2019-05-05T04:13:23.000Z | 2021-08-25T14:57:42.000Z | README.md | AmeyaWagh/Traffic_sign_detection_YOLO | dbba46709fc5e60259078e2a3ebcb50fde5a2fe9 | [
"MIT"
] | 16 | 2018-02-27T08:48:33.000Z | 2022-03-18T03:24:52.000Z | # Traffic_sign_detection_YOLO
Detecting traffic signs using YOLO algorithm
[]()
#### Clone the repository
```shell
git clone https://github.com/AmeyaWagh/Traffic_sign_detection_YOLO.git
```
#### Goto darkflow and build cython extension by running
```shell
cd darkflow
python3 setup.py build_ext --inplace
```
#### Then build globally with
```shell
pip install .
```
#### Check if "flow" works with "flow --h"
```shell
flow --h
```
#### Go back and create a new folder called "dataset" in base directory. Download and extract LISA dataset into the dataset folder
```shell
cd ..
mkdir dataset
```
#### run datasetGenerator.py
```shell
python3 datasetGenerator.py
```
#### goto darkflow and create "built_graph" directory inside darkflow if you are not training, and save pb and meta files there (pb and meta files can be downloaded here "https://drive.google.com/file/d/171AyNg4zSmz4OXhfcdgU2cxrqTfIV2BD/view?usp=sharing")
```shell
cd darkflow
mkdir built_graph
```
#### set GPU to 0.0 in the config3.json if not using GPU
```json
{
"yoloConfig":{
"pbLoad": "./built_graph/tiny-yolo-voc27.pb",
"metaLoad": "./built_graph/tiny-yolo-voc27.meta",
"labels":"../labels.txt",
"threshold":0.01,
"gpu":0.7
},
"dataset":"./dataset"
}
```
#### Run YOLO
```shell
./runYOLO
```
#### Training
```shell
cd darkflow
./trainYOLO
```
| 20.367647 | 255 | 0.698195 | eng_Latn | 0.72089 |
0578b63410591678d9fde77af702b96ed1acc150 | 176 | md | Markdown | README.md | tepickering/HALcoll | 291ad8c5afb27d0d74a25d58f184b4f14740ffc6 | [
"MIT"
] | null | null | null | README.md | tepickering/HALcoll | 291ad8c5afb27d0d74a25d58f184b4f14740ffc6 | [
"MIT"
] | null | null | null | README.md | tepickering/HALcoll | 291ad8c5afb27d0d74a25d58f184b4f14740ffc6 | [
"MIT"
] | null | null | null | # HALcoll
Using ML and AI techniques to build open-loop lookup models for the MMTO
| 29.333333 | 90 | 0.767045 | kor_Hang | 0.324408 |
05796f829a99219a47991b874171a4c1dbe920e8 | 33,649 | md | Markdown | microsoft-edge/progressive-web-apps-chromium/experimental-features/index.md | v-mholloway/edge-developer.es-ES | a30415a8301a3c34144e3447c0a0461ded88a256 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | microsoft-edge/progressive-web-apps-chromium/experimental-features/index.md | v-mholloway/edge-developer.es-ES | a30415a8301a3c34144e3447c0a0461ded88a256 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | microsoft-edge/progressive-web-apps-chromium/experimental-features/index.md | v-mholloway/edge-developer.es-ES | a30415a8301a3c34144e3447c0a0461ded88a256 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
description: Las últimas características experimentales de Microsoft Edge para aplicaciones web
title: Características experimentales | Aplicaciones web progresivas
author: MSEdgeTeam
ms.author: msedgedevrel
ms.date: 05/13/2021
ms.topic: article
ms.prod: microsoft-edge
keywords: microsoft edge, experiment, progressive web apps, web apps, PWAs, PWA
ms.openlocfilehash: 39c530c51f5ff486a008903d75cc7d2bf06df0a3f048871bc1e7c9fce5c74359
ms.sourcegitcommit: 841e41de1a32501ece862399fa56170c022127c5
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 08/06/2021
ms.locfileid: "11809358"
---
# <a name="experimental-features-in-progressive-web-apps-pwas"></a>Características experimentales en aplicaciones web progresivas (PWA)
Microsoft Edge proporciona acceso a características experimentales que aún están en desarrollo. Para determinar si cada característica está lista y cuándo liberar cada una, pruebe y [proporcione comentarios](#providing-feedback-on-experimental-features).
Las características experimentales están disponibles en todos los canales de Microsoft Edge, pero las características experimentales más recientes solo están disponibles en el canal Microsoft Edge Canary.
## <a name="turn-on-experimental-features"></a>Activar características experimentales
Para activar las características experimentales \(or off\) en Microsoft Edge, siga estos pasos.
1. Abra Microsoft Edge.
> [!NOTE]
> Asegúrese de usar una Microsoft Edge que tenga el experimento enumerado en este artículo. Vaya a [Características experimentales](#features-that-are-available-to-test).
1. Vaya a `edge://flags`.
1. Vaya al experimento correspondiente.
1. Elija el menú desplegable junto a la descripción del experimento y elija `Enabled` .
:::image type="complex" source="../media/turn-on-experimental-flag.png" alt-text="Elija Habilitado para activar un experimento" lightbox="../media/turn-on-experimental-flag.png":::
Elija **Habilitado** para activar un experimento
:::image-end:::
> [!NOTE]
> Cada experimento suele tener un menú desplegable para elegir los siguientes valores. Si una característica experimental no tiene una entrada en **Experimentos,** se proporcionan instrucciones para iniciar Microsoft Edge con esa característica mediante la línea de comandos.
>
> * `Default`
> * `Disabled`
> * `Enabled`
1. Reiniciar Microsoft Edge.
### <a name="origin-trials"></a>Pruebas de origen
Microsoft Edge a veces usa pruebas de origen para probar características para dominios o sitios web específicos. Es posible que desee usar una versión de prueba de origen para su sitio web para aplicar una característica específica. Si es propietario de un sitio web, puede inscribirse en una prueba de origen. Una versión de prueba de origen proporciona características a un porcentaje Microsoft Edge usuarios que visitan su sitio web.
Para obtener más información acerca de las pruebas de Origin, [vaya a Microsoft Edge Origin Trials Developer Console][MicrosoftDeveloperMicrosoftEdgeOriginTrials].
> [!NOTE]
> Las características experimentales se actualizan constantemente y pueden causar problemas de rendimiento. Para desactivar una característica experimental, vaya a [Activar características experimentales,](#turn-on-experimental-features)vaya al experimento y, a continuación, elija `Disabled` .
## <a name="features-that-are-available-to-test"></a>Características que están disponibles para probar
En la siguiente lista se describen las nuevas características experimentales de la aplicación web que están disponibles para probar y validar en Microsoft Edge.
| Característica | Microsoft Edge versión | Plataforma |
|:--- |:--- |:--- |
| [Administración del protocolo URI](#uri-protocol-handling) | 91 o posterior | Windows y Linux |
| [Administración de vínculos URL](#url-link-handling) | 91 o posterior | Windows|
| [Superposición de controles de ventana para aplicaciones de escritorio](#window-controls-overlay-for-installed-desktop-web-apps) | 91 o posterior | Windows 10|
| [Ejecutar en inicio de sesión del sistema operativo](#run-on-os-login) | 88 o posterior | Todos |
| [Accesos directos](#shortcuts) | 87 o posterior | Todos |
| [Administración de archivos](#file-handling) | 83 o posterior | Todo el escritorio |
## <a name="uri-protocol-handling"></a>Administración del protocolo URI
Se puede usar un identificador uniforme de recursos \(URI\) para definir algo más que vínculos a páginas web y contenido web mediante el protocolo HTTP o FTP. Los URI pueden usarse para describir vínculos a todo lo que codifique en un esquema. Por ejemplo, el protocolo se usa para describir un vínculo de correo electrónico y el sistema operativo \(OS\) o el explorador decide qué página web o aplicación debe controlar `mailto://` ese protocolo.
Para obtener más información acerca de la compatibilidad basada en explorador existente, vaya a [Controladores de protocolo basados][MdnDocsWebApiNavigatorRegisterprotocolhandlerWebBasedProtocolHandlers]en web.
Esta característica le permite completar las siguientes acciones.
* Registrar el PWA con el sistema operativo host mediante el manifiesto de la aplicación web
* Declarar que una PWA controla un protocolo URI específico
Después de registrar un PWA como controlador de protocolo, cuando un usuario elige un hipervínculo con un esquema específico, como un explorador o una aplicación nativa, el sistema operativo activa el PWA registrado y recibe el `mailto://` `web+music://` URI.
Esta característica requiere que actualices el manifiesto de la aplicación web para incluir una matriz, en la `protocol_handlers` matriz debes especificar dos campos:
* `protocol`: el protocolo para controlar la solicitud, por ejemplo `mailto` o `web+jngl` .
* `url`: URI HTTPS en el ámbito de la aplicación que controla el protocolo. En el futuro, el URI a partir del esquema de controladores de protocolo está planeado para reemplazar el `%s` token.
Actualice el manifiesto para admitir el protocolo que desea registrar. Después de activar esta característica, Microsoft Edge completa las siguientes acciones.
1. Detecta cambios en el manifiesto
1. Registra la aplicación para el protocolo
Si más de una aplicación registra un protocolo, se muestra al usuario un mensaje. El usuario elige la aplicación adecuada de la lista presentada por el sistema operativo o el explorador.
Para obtener una vista previa del Microsoft Edge en Windows, vaya a Activar características [experimentales](#turn-on-experimental-features) y active Control de protocolo **de PWA escritorio.**
Para obtener más información acerca de la versión de prueba de origen que se está ejecutando para los controladores de protocolo, vaya a Registrar para el registro del controlador de [protocolo de aplicación web.][MicrosoftDeveloperMicrosoftEdgeOriginTrialsWebAppProtocolHandlerRegistrationRegistration]
### <a name="example-manifest"></a>Manifiesto de ejemplo
En este ejemplo, un manifiesto de aplicación web declara que la aplicación debe registrarse para controlar los protocolos `web+jngl` y `web+jnglstore` .
```json
{
"name": "Jungle",
"description": "A plant encyclopedia",
"protocol_handlers": [
{
"protocol": "web+jngl",
"url": "/lookup?type=%s"
},
{
"protocol": "web+jnglstore",
"url": "/shop?for=%s"
}
],
"icons": [
{
"src": "images/icons-192.png",
"type": "image/png",
"sizes": "192x192"
},
],
"background_color": "#007f87",
"display": "standalone",
"start_url": "/",
}
```
## <a name="url-link-handling"></a>Administración de vínculos URL
Un localizador uniforme de recursos \(URL\) es un tipo de URI. Crea una experiencia más atractiva cuando las aplicaciones web progresivas \(PWAs\) se registren como controladores para URI https. Las PWA pueden solicitar que se inicien cuando se activen los URI asociados. Por ejemplo, si un usuario elige un vínculo a un artículo de noticias de un mensaje de correo electrónico. Se inicia automáticamente PWA asociado para mostrar artículos de noticias para controlar la activación del vínculo.
Esta característica te permite registrar una PWA con el explorador mediante el manifiesto de la aplicación web y declarar que el explorador controla vínculos específicos. Para registrar una PWA con el explorador, agregue el miembro `url_handlers` opcional al archivo de manifiesto. El `url_handlers` miembro es un que agrupa los orígenes de los URI que la aplicación desea `object[]` controlar.
El explorador valida el control de vínculos mediante un `web-app-origin-association` archivo JSON que se encuentra en el origen. El archivo de origen afina aún más las rutas de acceso incluidas o excluidas en el origen. Para obtener instrucciones detalladas sobre cómo probar el controlador de direcciones URL, vaya a [PWA como controladores de dirección URL][GithubWicgPwaUrlHandlerBlobMainExplainerMd].
Para obtener una vista previa del control de vínculos url en Microsoft Edge en Windows, vaya a Activar características [experimentales](#turn-on-experimental-features) y active Control de direcciones **URL PWA escritorio.**
### <a name="example-of-the-url_handlers-in-the-manifest"></a>Ejemplo de la url_handlers en el manifiesto
El siguiente fragmento de código es un manifiesto de aplicación web de ejemplo con el `url_handlers` miembro.
```json
{
"name": "Contoso Business App",
"display": "standalone",
"icons": [
{
"src": "images/icons-144.png",
"type": "image/png",
"sizes": "144x144"
}
],
"capture_links": "existing_client_event",
"url_handlers" : [
{
"origin": "https://contoso.com"
},
{
"origin": "https://conto.so"
},
{
"origin": "https://*.contoso.com"
}
]
}
```
Un PWA coincide con un URI para el control de direcciones URL si el URI coincide con una de las cadenas de origen y el explorador valida que el origen acepta permitir que esta aplicación controle `url_handlers` dicho URI.
El miembro contiene un origen que abarca el ámbito y otros orígenes no relacionados de la `url_handlers` PWA. No restringir los URI al mismo ámbito o dominio que el PWA de solicitud permite usar nombres de dominio diferentes para el mismo contenido, pero controlarlos con el mismo PWA.
#### <a name="wildcard-matching"></a>Coincidencia de caracteres comodín
Use el carácter comodín \( `*` \) para que coincida con uno o más caracteres.
Se usa un prefijo comodín en las cadenas de origen del `url_handlers` miembro para que coincidan con los subdominios diferentes. El prefijo debe ser `*.` para este uso. El `https` esquema se asume cuando se usa un prefijo comodín.
Por ejemplo, el `url_handlers` valor de miembro se establece en `*.contoso.com` coincidencias y , pero no `tenant.contoso.com` coincide con `www.tenant.contoso.com` `contoso.com` .
## <a name="window-controls-overlay-for-installed-desktop-web-apps"></a>Superposición de controles de ventana para aplicaciones web de escritorio instaladas
Para crear una barra de título envolvente como una aplicación **** nativa para la aplicación web instalada en el escritorio, la característica Superposición de controles de ventana completa las siguientes acciones.
1. Quita la barra de título reservada del sistema. Normalmente abarca el ancho del marco de cliente.
1. Lo reemplaza por una superposición. Contiene solo los controles de ventana necesarios para que un usuario controle la propia ventana.
Después de proporcionar una superposición, todo el área de cliente web está disponible para su uso. Esta característica incluye una actualización de manifiesto. Proporciona formas de determinar el tamaño y la posición de la superposición para ayudarle a organizar el contenido.
Para obtener una vista previa de las superposiciones de controles de ventana en Microsoft Edge para Windows 10, vaya a Activar características [experimentales](#turn-on-experimental-features) y vaya a Escritorio PWA superposición **de controles de ventana**.
### <a name="examples-of-title-bar-area-customization"></a>Ejemplos de personalización del área de la barra de título
Esta característica se basa en la capacidad de las aplicaciones nativas para personalizar la barra de título. Puedes personalizar una barra de título para las notificaciones o acciones importantes de la aplicación. Revise los siguientes ejemplos para obtener Microsoft Visual Studio código y Microsoft Teams.
#### <a name="visual-studio-code"></a>Visual Studio Code
Microsoft Visual Studio Code es un editor popular basado en Electron que se incluye en varias plataformas de escritorio.
En el ejemplo siguiente se muestra cómo Visual Studio Code la barra de título para maximizar la propiedad de pantalla disponible para incluir el nombre de archivo actual y la estructura de menús de nivel superior en la barra de título.
:::image type="complex" source="../media/visual-studio-code-title-customization.png" alt-text="Un ejemplo de la barra de título de Visual Studio Code" lightbox="../media/visual-studio-code-title-customization.png":::
Un ejemplo de la barra de título de Visual Studio Code
:::image-end:::
#### <a name="microsoft-teams"></a>Microsoft Teams
Las herramientas de comunicación y colaboración Microsoft Teams workplace también se han creado con Electron y están disponibles en varias plataformas de escritorio. En el siguiente ejemplo, Microsoft Teams y botones de navegación, un cuadro `back` de búsqueda y controles de perfil de `forward` usuario.
:::image type="complex" source="../media/teams-title-customization.png" alt-text="Un ejemplo de la barra de título de Microsoft Teams" lightbox="../media/teams-title-customization.png":::
Un ejemplo de la barra de título de Microsoft Teams
:::image-end:::
### <a name="overlay-window-controls-on-a-frameless-window"></a>Superponer controles de ventana en una ventana sin marco
Para maximizar el área direccionable para el contenido web, el explorador crea una ventana sin marco. Una ventana sin marco quita toda la interfaz de usuario del explorador, excepto los controles de ventana proporcionados como una superposición. La superposición de controles de ventana permite a los usuarios minimizar, maximizar, restaurar y cerrar la aplicación. También proporciona acceso a controles de explorador relevantes mediante el menú de la aplicación web. Para Chromium exploradores basados en el usuario, la superposición incluye los siguientes controles.
* Una región arrastrable con el mismo ancho y alto de cada uno de los botones de control de ventana
* El **Configuración y más** \(...\) botón
* Los botones de control de ventana minimizan, maximizan, restauran y cierran
Además de los controles enumerados anteriormente, la interfaz de usuario mostrada en la superposición cambia de tamaño dinámicamente en los siguientes escenarios.
* Cuando se inicia una aplicación web instalada, el origen de la página web se muestra a la izquierda del menú **Configuración** y más \(...\) durante unos segundos y, a continuación, desaparece.
* Si un usuario interactúa con una extensión mediante el menú **Configuración y** más \(...\), el icono de la extensión se muestra en la superposición a la izquierda del menú de tres puntos. Después de salir de cualquier cuadro de diálogo de extensión, el icono se quita de la superposición.
| Dirección del idioma | Ubicación de superposición | Detalles |
|:--- |:--- |:--- |
| De izquierda a derecha \(LTR\) | Superior izquierda del área de cliente | Los controles se voltearán |
| De derecha a izquierda \(RTL\) | Esquina superior derecha del área de cliente | |
> [!IMPORTANT]
> La superposición siempre está en la parte superior del índice Z del contenido web y acepta todas las entradas del usuario sin pasarla al contenido web.
### <a name="working-around-the-window-controls-overlay"></a>Trabajar alrededor de la superposición de controles de ventana
El contenido web debe tener en cuenta el área reservada para la superposición de controles. Asegúrese de que el área reservada no espera la interacción del usuario. Consulta al explorador el rectángulo de límite y la visibilidad de la superposición de controles. La información se proporciona a través de las API de JavaScript y las variables de entorno CSS.
#### <a name="javascript-apis"></a>API de JavaScript
Un nuevo objeto de la propiedad permite consultar el `windowControlsOverlay` rectángulo delimitador de la `window.navigator` superposición de controles.
El `windowControlsOverlay` objeto tiene los dos objetos siguientes.
* `getBoundingClientRect()` devuelve un `DOMRect` objeto. El `DOMRect` objeto representa el área debajo de la superposición de controles de ventana.
* `visible` es un valor booleano que indica que la superposición de controles se representa y se muestra.
> [!IMPORTANT]
> Por motivos de privacidad, los elementos del `windowControlsOverlay` contenido web no son `iframe` accesibles.
Cada vez que se cambia el tamaño de la superposición, se ejecuta un evento en el objeto para notificar al `geometrychange` cliente que recalcula el diseño de `navigator.windowControlsOverlay` contenido. El diseño de contenido recalculado se basa en el nuevo rectángulo delimitador de la superposición.
#### <a name="css-environment-variables"></a>Variables de entorno CSS
Además de la API de JavaScript, puede usar CSS para consultar el rectángulo delimitador de la superposición de controles. Use las siguientes cuatro nuevas variables de entorno CSS para realizar la consulta.
* `titlebar-area-x`
* `titlebar-area-y`
* `titlebar-area-width`
* `titlebar-area-height`
### <a name="define-draggable-regions-in-web-content"></a>Definir regiones arrastrables en contenido web
Los usuarios esperan agarrar y arrastrar la región superior de una ventana. Para dar cabida a la expectativa, declare elementos específicos del contenido web como arrastrables.
Para especificar que un elemento se puede arrastrar, use la propiedad CSS propietaria de `-webkit-app-region` WebKit. El grupo de trabajo css continúa los esfuerzos para estandarizar la `app-region` propiedad.
### <a name="custom-title-bar-example"></a>Ejemplo de barra de título personalizada
En el ejemplo siguiente se muestra cómo las nuevas características crean una aplicación web con una barra de título personalizada.
:::image type="complex" source="../media/teams-title-customization-example.png" alt-text="Ejemplo de una barra de título personalizada en Microsoft Teams" lightbox="../media/teams-title-customization-example.png":::
Ejemplo de una barra de título personalizada en Microsoft Teams
:::image-end:::
#### <a name="manifestwebmanifest"></a>manifest.webmanifest
En el manifiesto, establezca `display_override` la matriz en `window-controls-overlay` . Establece el `theme_color` color que elijas para la barra de título. Establezca el modo de presentación en una reserva adecuada para cuando se `display_override` admite o `window-controls-overlay` no.
El siguiente fragmento de código incluye las actualizaciones de manifiesto recomendadas.
```json
{
"name": "Example PWA",
"display": "standalone",
"display_override": [
"window-controls-overlay"
],
"theme_color": "#254B85"
}
```
### <a name="indexhtml"></a>index.html
Los siguientes IDs representan las dos regiones principales de la página web.
* `titleBarContainer`
* `mainContent`
El elemento con el identificador se establece en y el elemento secundario del cuadro de `div` búsqueda se establece en `titleBar` `draggable` `input` `nonDraggable` .
```html
<div id="titleBar" class=" draggable">
<span class="draggable">Example PWA</span>
<input class="nonDraggable" type="text" placeholder="Search"></input>
</div>
```
En el `div` elemento con el `titleBarContainer` identificador, el con el identificador representa `div` la parte visible del área de la barra de `titleBar` título.
```html
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width">
<title>Example PWA</title>
<link rel="stylesheet" href="style.css">
<link rel="manifest" href="./manifest.webmanifest">
</head>
<body>
<div id="titleBarContainer">
<div id="titleBar" class=" draggable">
<span class="draggable">Example PWA</span>
<input class="nonDraggable" type="text" placeholder="Search"></input>
</div>
</div>
<div id="mainContent"><!-- The rest of the webpage --></div>
</body>
</html>
```
### <a name="stylecss"></a>style.css
Las regiones arrastrables y no arrastrables se establecen mediante `-webkit-app-region: drag` y `-webkit-app-region: no-drag` .
```css
.draggable {
app-region: drag;
/* Pre-fix app-region during standardization process */
-webkit-app-region: drag;
}
.nonDraggable {
app-region: no-drag;
/* Pre-fix app-region during standardization process */
-webkit-app-region: no-drag;
}
```
Para el elemento, los márgenes se establecen para garantizar que la barra `body` de título llegue a los bordes de la `0` ventana.
```css
body {
font-family: 'Segoe UI', Tahoma, Geneva, Verdana, sans-serif;
margin: 0;
}
```
El `titleBarContainer` identificador usa y establece el valor en , que adjunta el contenedor a la parte superior `position: absolute` de la página `top` `titlebar-area-inset-top` web. Se establece en y vuelve a si la superposición de controles de ventana `bottom` `titlebar-area-inset-bottom` no está `100% - var(--fallback-title-bar-height)` visible. El color de fondo del `titleBarContainer` identificador es el mismo que el `theme_color` . El ancho se establece en , de modo que el elemento rellena el ancho de la página web y fluye debajo de la superposición cuando está visible para una `100%` `div` apariencia contigua.
```css
#titleBarContainer {
position: absolute;
top: env(titlebar-area-y, 0);
bottom: env(titlebar-area-height, calc(100% - var(--fallback-title-bar-height)));
width: 100%;
background-color:#254B85;
}
```
El `titleBar` identificador también usa y para `position: absolute` `top: titlebar-area-inset-top` adjuntarlo a la parte superior de la ventana. De forma predeterminada, consume el ancho completo de la ventana. Los `left` bordes y se establecen en y `right` respectivamente, ambos se `titlebar-area-inset-left` `titlebar-area-inset-right` resonarán `0` cuando no se establecen los valores. También se establece para evitar cualquier intento de arrastrar la ventana consumida en su lugar `user-select: none` resalta el texto del `div` elemento.
```css
#titleBar {
position: absolute;
top: 0;
display: flex;
user-select: none;
height: 100%;
left: env(titlebar-area-x, 0);
right: env(titlebar-area-width, 0);
color: #FFFFFF;
font-weight: bold;
text-align: center;
}
#titleBar > span {
margin: auto;
padding: 0px 16px 0px 16px;
}
#titleBar > input {
flex: 1;
margin: 8px;
border-radius: 5px;
border: none;
padding: 8px;
}
```
El contenedor del identificador también se fija en su lugar `mainContent` y se adjunta a la parte inferior de la página `position: absolute` web. The `height` is set to and falls back to to fill the remaining space below the title `titlebar-area-inset-bottom` `100% - var(--fallback-titlebar-height)` bar. Se establece `overflow-y: scroll` para permitir que el contenido se desplace verticalmente en el contenedor.
```css
#mainContent {
position: absolute;
left: 0;
right: 0;
bottom: 0;
height: env(titlebar-area-height, calc(100% - var(--fallback-title-bar-height)));
overflow-y: scroll;
}
```
En los casos en los que el explorador no admite la superposición de controles de ventana, se agrega una variable CSS para establecer un alto predeterminado para la barra de título. Los límites de los e IDs se establecen inicialmente para rellenar todo el área de cliente y no es necesario cambiarlo si no se admite `titleBarContainer` `mainContent` la superposición.
El siguiente fragmento de código incluye todas las actualizaciones CSS recomendadas.
```css
:root {
--fallback-title-bar-height: 40px;
}
.draggable {
app-region: drag;
/* Pre-fix app-region during standardization process */
-webkit-app-region: drag;
}
.nonDraggable {
app-region: no-drag;
/* Pre-fix app-region during standardization process */
-webkit-app-region: no-drag;
}
body {
font-family: 'Segoe UI', Tahoma, Geneva, Verdana, sans-serif;
margin: 0;
}
#titleBarContainer {
position: absolute;
top: env(titlebar-area-y, 0);
bottom: env(titlebar-area-height, calc(100% - var(--fallback-title-bar-height)));
width: 100%;
background-color:#254B85;
}
#titleBar {
position: absolute;
top: 0;
display: flex;
user-select: none;
height: 100%;
left: env(titlebar-area-x, 0);
right: env(titlebar-area-width, 0);
color: #FFFFFF;
font-weight: bold;
text-align: center;
}
#titleBar > span {
margin: auto;
padding: 0px 16px 0px 16px;
}
#titleBar > input {
flex: 1;
margin: 8px;
border-radius: 5px;
border: none;
padding: 8px;
}
#mainContent {
position: absolute;
left: 0;
right: 0;
bottom: 0;
height: env(titlebar-area-height, calc(100% - var(--fallback-title-bar-height)));
overflow-y: scroll;
}
```
Chromium exploradores basados en aplicaciones están probando y dando forma a esta característica. Para obtener más información, incluidos los ejemplos de código, vaya a Personalizar la superposición de controles de ventana de la barra de título de [PWA de la ventana.][WebDevWindowControlsOverlay]
## <a name="run-on-os-login"></a>Ejecutar en inicio de sesión del sistema operativo
Esta característica te permite configurar la aplicación para que se inicie automáticamente cuando el usuario inicie sesión en Microsoft Windows. Varias clases de aplicaciones aprovechan la funcionalidad. Las clases de aplicaciones incluyen correo electrónico, chat, panel de supervisión y aplicaciones para mostrar datos en tiempo real. La funcionalidad permite a un usuario interactuar con las aplicaciones tan pronto como el usuario inicia sesión en el sistema operativo. Esta característica inicia automáticamente el PWA de la misma forma que se inicia manualmente.
> [!IMPORTANT]
> **Ejecutar en inicio de sesión del sistema** operativo es una característica [eficaz.][GithubW3cPermissionsPowerfulFeature] Los usuarios deben decidir si se activa la funcionalidad de la aplicación web instalada.
### <a name="turn-on-run-on-os-login"></a>Activar Ejecutar inicio de sesión del sistema operativo
Para obtener una **vista** previa de las capacidades ejecutar en el sistema operativo para su PWA, vaya a Activar características [experimentales](#turn-on-experimental-features) y active Las PWA de escritorio se ejecutan en el inicio de sesión **del sistema operativo.**
:::image type="complex" source="../media/desktop-pwas-run-on-os-login-flag.png" alt-text="Activar las PWA de escritorio que se ejecutan en el experimento inicio de sesión del sistema operativo" lightbox="../media/desktop-pwas-run-on-os-login-flag.png":::
Activar las **PWA de escritorio que se ejecutan en el experimento de inicio de sesión del sistema** operativo
:::image-end:::
### <a name="turn-on-the-feature-for-the-installed-web-app"></a>Activar la característica de la aplicación web instalada
Para activar la característica `Start app when you sign in` de un servidor PWA,
1. Abra Microsoft Edge.
1. Vaya a `edge://apps`.
1. Mantenga el mouse en la aplicación.
1. Abra el menú contextual \(right-click\) y, a continuación, elija **Iniciar aplicación al iniciar sesión**.
:::image type="complex" source="../media/turn-on-run-on-os-login-flag.png" alt-text="Usa el menú contextual para activar la aplicación Inicio cuando inicies sesión en la Microsoft Edge" lightbox="../media/turn-on-run-on-os-login-flag.png":::
Usa el menú contextual para activar la **aplicación Inicio cuando inicies sesión** en la Microsoft Edge
:::image-end:::
## <a name="shortcuts"></a>Accesos directos
`Shortcuts` es un nuevo miembro del archivo de manifiesto. Te permite definir vínculos a elementos, páginas web clave o acciones en la aplicación web. Microsoft Windows integra como **listas de saltos**. **Las listas de accesos** emergentes definen menús emergentes que aparecen cuando se encuentra en uno de los siguientes elementos de la interfaz de usuario y se abre un menú contextual \(hacer clic con el botón secundario\).
* Un icono en el menú Inicio
* Un icono en la barra de tareas
Cuando un usuario invoca un acceso directo, el usuario navega a la dirección especificada por el `url` miembro del acceso directo.
:::image type="complex" source="../media/jumplists-on-windows-10.png" alt-text="Un ejemplo de listas de saltos en Windows 10" lightbox="../media/jumplists-on-windows-10.png":::
Un ejemplo de **listas de saltos** en Windows 10
:::image-end:::
### <a name="shortcuts-in-the-manifest-file"></a>Accesos directos en el archivo de manifiesto
```json
"shortcuts" : [
{
"name": "Today's agenda",
"url": "/today",
"description": "List of events planned for today"
},
{
"name": "New event",
"url": "/create/event"
},
{
"name": "New reminder",
"url": "/create/reminder"
}
]
```
#### <a name="properties-of-shortcuts"></a>Propiedades de accesos directos
Las siguientes propiedades definen cada acceso directo.
| Propiedad | Detalles |
|:--- |:--- |
| `name` | Cadena que se muestra al usuario en **listas de saltos** o en el menú contextual. |
| `short_name` | Cadena que se muestra cuando hay espacio insuficiente para mostrar el nombre completo del acceso directo. |
| `description` | Cadena que describe el propósito del acceso directo. Es posible que se pueda acceder a ella mediante tecnología de asistencia. |
| `url` | Uri de la aplicación web que se abre cuando se activa el acceso directo. |
| `icons` | Un conjunto de iconos que representa el acceso directo. |
## <a name="file-handling"></a>Administración de archivos
La capacidad de registrarse como un controlador de tipos de archivo está en la fase de experimentación. Puedes especificar los tipos de archivo que controla la aplicación en una entrada de manifiesto. Durante la instalación, el sistema operativo host del usuario registra la aplicación como un controlador de archivos para los tipos de archivo enumerados. Asegúrese de la existencia de la característica en el código de inicio de las `launchQueue` aplicaciones y de que controla el archivo.
Chromium exploradores basados en aplicaciones están probando y dando forma a esta característica. Para obtener más información, incluidos los ejemplos de código, vaya a [Permitir que las aplicaciones web sean controladores de archivos][WebDevFileHandling].
Para obtener una vista previa del control de archivos Microsoft Edge para Windows 10, vaya a Activar características [experimentales](#turn-on-experimental-features) y active la **API de administración de archivos**.
## <a name="providing-feedback-on-experimental-features"></a>Proporcionar comentarios sobre características experimentales
Para proporcionar comentarios sobre Microsoft Edge de aplicaciones web.
* Envíe sus comentarios con **Configuración y Más** \( `...` \) > Enviar comentarios a **Microsoft**.
* Seleccione `Alt` + `Shift` + `I` .
:::image type="complex" source="../media/send-feedback-from-progressive-web-app.png" alt-text="Enviar comentarios desde su PWA" lightbox="../media/send-feedback-from-progressive-web-app.png":::
Enviar comentarios desde su PWA
:::image-end:::
<!-- links -->
[MicrosoftEdgeMain]: https://www.microsoft.com/edge "Microsoft Edge"
[MicrosoftDeveloperMicrosoftEdgeOriginTrials]: https://developer.microsoft.com/microsoft-edge/origin-trials "Pruebas de origen | Microsoft Edge Programador"
[MicrosoftDeveloperMicrosoftEdgeOriginTrialsWebAppProtocolHandlerRegistrationRegistration]: https://developer.microsoft.com/microsoft-edge/origin-trials/web-app-protocol-handler-registration/registration "Registrar para el registro del controlador de protocolo de aplicación web | Microsoft Developer"
[MdnDocsWebApiNavigatorRegisterprotocolhandlerWebBasedProtocolHandlers]: https://developer.mozilla.org/docs/Web/API/Navigator/registerProtocolHandler/Web-based_protocol_handlers "Controladores de protocolo basados en web | MDN"
[GithubW3cPermissionsPowerfulFeature]: https://w3c.github.io/permissions#powerful-feature "Característica eficaz: permisos | GitHub"
[GithubWicgPwaUrlHandlerBlobMainExplainerMd]: https://github.com/WICG/pwa-url-handler/blob/main/explainer.md "PwAs como controladores de dirección URL | GitHub"
[WebDevFileHandling]: https://web.dev/file-handling "Permitir que las aplicaciones web sean controladores de archivos | web.dev"
[WebDevWindowControlsOverlay]: https://web.dev/window-controls-overlay "Personalizar la superposición de controles de ventana de la barra de PWA la barra de título | web.dev"
| 56.458054 | 630 | 0.747511 | spa_Latn | 0.975163 |
057988a5854f7049346d7967cf63888205bf6f56 | 1,980 | md | Markdown | _technologies/apache-falcon.md | boy007uk/OnDataEngineeringContent | bb88f85199fb4c1dbe84d4d2d8a0c5503c0c6f11 | [
"Apache-2.0"
] | 6 | 2017-02-25T19:38:56.000Z | 2021-06-08T16:21:51.000Z | _technologies/apache-falcon.md | boy007uk/OnDataEngineeringContent | bb88f85199fb4c1dbe84d4d2d8a0c5503c0c6f11 | [
"Apache-2.0"
] | 17 | 2017-02-21T21:27:16.000Z | 2019-05-24T16:27:41.000Z | _technologies/apache-falcon.md | boy007uk/OnDataEngineeringContent | bb88f85199fb4c1dbe84d4d2d8a0c5503c0c6f11 | [
"Apache-2.0"
] | 8 | 2017-02-12T02:22:53.000Z | 2020-01-07T11:54:20.000Z | ---
title: "Apache Falcon"
description: "Data feed management system for Hadoop. Supports the definition, scheduling and orchestration (including support for late data and retry policies) of data processing pipelines (referred to as processes, with support for Ozzie, Spark, Hive and Pig jobs), the management of the data produced and consumed by these pipelines (referred to as feeds, with support for data in HDFS and Hive) and the generation and visualisation of pipeline lineage information, all across multiple Hadoop clusters. Also includes the ability to mirror or replicate HDFS and Hive data between clusters, to failover processing between clusters and to import and export data using Sqoop. Supports both a web and command line interface and a REST API. An Apache project, graduating in December 2014, having been originally donated by inMobi in April 2013. Hasn't yet reached a v1.0 milestone, is seeing very little development activity, and as of HDP 3.0 will no longer be distributed by Hortonworks."
alt-titles: [Falcon]
vendors: [Apache]
type: "Open Source - Quiet"
date: 2017-02-23
last_updated: 2018-03-14
version: "v0.11"
---
## Release History
| version | release date | release links | release comment
| 0.11 | 2018-03-12 | [release note](https://cwiki.apache.org/confluence/download/attachments/61318307/RelaseNotes-ApacheFalcon-0.11.pdf?api=v2) |
## Links
* <http://falcon.apache.org/> - homepage and documentation
* <https://cwiki.apache.org/confluence/display/FALCON/Release+Notes> - release notes
* <http://hortonworks.com/apache/falcon/> - Hortonworks information on Falcon, including tutorials and blog posts
* <https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.4/bk_data-movement-and-integration/content/index.html> - Hortonworks 2.6.4 documentation
* <https://community.hortonworks.com/questions/97570/apache-falcon-in-hdp-30.html> - Hortonworks community update on deprecation
## News
* Blog updates via the Hortonworks and Apache blogs | 76.153846 | 990 | 0.783838 | eng_Latn | 0.952923 |
057a05428a227c77acb938ab408c40774a843d90 | 1,474 | md | Markdown | AlchemyInsights/import-favorites-to-edge.md | isabella232/OfficeDocs-AlchemyInsights-pr.tr-TR | 829935b72282a64e4ec4294adebf31fd30f93f68 | [
"CC-BY-4.0",
"MIT"
] | 3 | 2020-05-19T19:08:16.000Z | 2021-03-14T11:48:36.000Z | AlchemyInsights/import-favorites-to-edge.md | isabella232/OfficeDocs-AlchemyInsights-pr.tr-TR | 829935b72282a64e4ec4294adebf31fd30f93f68 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2022-02-09T06:53:52.000Z | 2022-02-09T06:54:01.000Z | AlchemyInsights/import-favorites-to-edge.md | isabella232/OfficeDocs-AlchemyInsights-pr.tr-TR | 829935b72282a64e4ec4294adebf31fd30f93f68 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2019-10-09T20:30:22.000Z | 2021-10-09T10:37:41.000Z | ---
title: Sık kullanılanları Google Chrome veya Mozilla Firefox'tan Microsoft Edge
ms.author: pebaum
author: pebaum
manager: scotv
ms.date: 03/30/2021
ms.audience: Admin
ms.topic: article
ms.service: o365-administration
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Priority
ms.collection: Adm_O365
ms.custom:
- "9447"
- "11023"
- "9005491"
- "9006474"
ms.openlocfilehash: a4636532111248d91a2e2b3d52fcc2e896aa7cd5
ms.sourcegitcommit: 67dbb2f157f6e83f41d9480071c1d35ac5565509
ms.translationtype: HT
ms.contentlocale: tr-TR
ms.lasthandoff: 05/13/2021
ms.locfileid: "52470293"
---
# <a name="import-favorites-from-google-chrome-or-mozilla-firefox-to-microsoft-edge"></a>Sık kullanılanları Google Chrome veya Mozilla Firefox'tan Microsoft Edge
1. Microsoft Edge'i açın ve ardından Ayarlar **ve daha fazlasını seçin ...** > **Ayarlar** > **Tarayıcı verilerini içeri aktarın.**
1. İçeri Aktar **menüsünden** **Google Chrome** veya **Mozilla Firefox'u ve** sonra İçeri Aktar'ı **seçin.**
1. Profil **altında,** profili seçin.
1. İçeri **aktarıileri seçin** öğesinin altında, içeri aktarma işlemi yapmak istediğiniz öğeleri seçin ve sonra da İçeri Aktar öğesini **seçin.**
1. Hepsi **bitti!** iletişim kutusunda Bitti 'yi **seçin.**
Alınan sık kullanılanlar, Sık Kullanılanlar çubuğundaki bir klasörde (örneğin, Alınan veya Diğer sık kullanılanlar) yer ala bir klasörde yer ala bir gerekir. Bunları olduğu yerde tutabilirsiniz veya farklı bir klasöre taşıabilirsiniz.
| 38.789474 | 234 | 0.778155 | tur_Latn | 0.994346 |
057a3dcabf85ec869424ff1f89fa20fddaebd8bb | 802 | md | Markdown | README.md | jogarijo/repl-apostrophe-joins-resolution-in-load-event | 786b73021f97028faf1fff225c472e151d791a1c | [
"MIT"
] | null | null | null | README.md | jogarijo/repl-apostrophe-joins-resolution-in-load-event | 786b73021f97028faf1fff225c472e151d791a1c | [
"MIT"
] | null | null | null | README.md | jogarijo/repl-apostrophe-joins-resolution-in-load-event | 786b73021f97028faf1fff225c472e151d791a1c | [
"MIT"
] | null | null | null | # REPL (based on Apostrophe Boilerplate v2.x)
## Issue description
[...]
## Deviations of this REPL
This REPL is based on Apostrophe Boilerplate v2.x, with the main changes described below:
- [...]
See the commit(s) of this branch for detailed changes.
## Starting the REPL
First, you must ensure a MongoDB server is running locally so Apostrophe can start. A new database named
`repl-apostrophe-boilerplate` will be created.
Then initialize the REPL using the commands below:
```shell
npm install # Install dependencies
node app.js apostrophe-users:add admin admin # Create an admin user
npm run dev # Start with auto-reload
```
## How to reproduce
1. [Login to the REPL environment](http://localhost:3000/login);
1. [...]
| 25.0625 | 104 | 0.680798 | eng_Latn | 0.978491 |
057b03abd76f9c68c9627644ea4ac6963306d64f | 1,847 | md | Markdown | docs/outlook/mapi/fbadrestriction.md | isabella232/office-developer-client-docs.de-DE | f244ed2fdf76004aaef1de6b6c24b8b1c5a6942e | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-05-19T18:52:16.000Z | 2021-04-21T00:13:46.000Z | docs/outlook/mapi/fbadrestriction.md | MicrosoftDocs/office-developer-client-docs.de-DE | f244ed2fdf76004aaef1de6b6c24b8b1c5a6942e | [
"CC-BY-4.0",
"MIT"
] | 2 | 2021-12-08T03:25:19.000Z | 2021-12-08T03:43:48.000Z | docs/outlook/mapi/fbadrestriction.md | isabella232/office-developer-client-docs.de-DE | f244ed2fdf76004aaef1de6b6c24b8b1c5a6942e | [
"CC-BY-4.0",
"MIT"
] | 5 | 2018-07-17T08:19:45.000Z | 2021-10-13T10:29:41.000Z | ---
title: FBadRestriction
manager: soliver
ms.date: 03/09/2015
ms.audience: Developer
ms.topic: reference
ms.prod: office-online-server
ms.localizationpriority: medium
api_name:
- FBadRestriction
api_type:
- HeaderDef
ms.assetid: 6ad3638c-d088-4a89-9b0d-f5b672162203
description: 'Letzte Änderung: Montag, 9. März 2015'
ms.openlocfilehash: b91c33e237af2dc5da3d24961192fff88e64223f
ms.sourcegitcommit: a1d9041c20256616c9c183f7d1049142a7ac6991
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 09/24/2021
ms.locfileid: "59604999"
---
# <a name="fbadrestriction"></a>FBadRestriction
**Gilt für**: Outlook 2013 | Outlook 2016
Überprüft eine Einschränkung, die zum Einschränken einer Tabellenansicht verwendet wird.
|||
|:-----|:-----|
|Headerdatei: <br/> |Mapival.h <br/> |
|Implementiert von: <br/> |MAPI <br/> |
|Aufgerufen von: <br/> |Dienstanbieter <br/> |
```cpp
ULONG FBadRestriction(
LPSRestriction lpres
);
```
## <a name="parameters"></a>Parameter
_Lpres_
> [in] Eine [SRestriction-Struktur,](srestriction.md) die die zu überprüfende Einschränkung definiert.
## <a name="return-value"></a>Rückgabewert
TRUE
> Die angegebene Einschränkung oder eine oder mehrere ihrer Untereinschränkungen ist ungültig.
FALSE
> Die angegebene Einschränkung und alle zugehörigen Untereinschränkungen sind gültig.
## <a name="remarks"></a>HinwBemerkungeneise
Nachdem eine Einschränkung überprüft wurde, kann sie in Aufrufen der [IMAPITable::Restrict-Methode](imapitable-restrict.md) übergeben werden, um die Tabelle auf bestimmte Zeilen zu beschränken, an die [IMAPITable::FindRow-Methode](imapitable-findrow.md) zum Suchen einer Tabellenzeile und an Methoden der [IMAPIContainer-Schnittstelle,](imapicontainerimapiprop.md) um eine Einschränkung für ein Containerobjekt auszuführen.
| 29.31746 | 424 | 0.760152 | deu_Latn | 0.907478 |
057baa2eab0142dba8a8d395aedac3405690ccea | 421 | md | Markdown | README.md | lukehedger/now-monorepo-test | 81efe259401713059f35efabb0a0ece27eba825d | [
"Unlicense"
] | null | null | null | README.md | lukehedger/now-monorepo-test | 81efe259401713059f35efabb0a0ece27eba825d | [
"Unlicense"
] | 1 | 2020-01-09T10:44:00.000Z | 2020-01-09T10:44:00.000Z | README.md | lukehedger/now-monorepo-test | 81efe259401713059f35efabb0a0ece27eba825d | [
"Unlicense"
] | null | null | null | # now-monorepo-test
## Setup
- [Download Now](https://zeit.co/download)
## Develop
```sh
now dev
```
- App: [http://localhost:3000/](http://localhost:3000/)
- API: [http://localhost:3000/api](http://localhost:3000/api)
## Deploy
```sh
now
```
- App: [https://monotest.lukehedger.now.sh/](https://monotest.lukehedger.now.sh/)
- API: [https://monotest.lukehedger.now.sh/api](https://monotest.lukehedger.now.sh/api)
| 17.541667 | 87 | 0.665083 | yue_Hant | 0.81486 |
057bed1a59b34a40c0edc5e9308c31a068186b80 | 138 | md | Markdown | README.md | chanjarster/autoconf | 6dcf413a3f7f8e7040d9f68a2736b0bbb26cfd4c | [
"Apache-2.0"
] | 2 | 2020-03-22T04:49:50.000Z | 2020-03-26T02:24:13.000Z | README.md | chanjarster/autoconf | 6dcf413a3f7f8e7040d9f68a2736b0bbb26cfd4c | [
"Apache-2.0"
] | 1 | 2020-03-21T06:32:57.000Z | 2020-03-22T02:42:29.000Z | README.md | chanjarster/autoconf | 6dcf413a3f7f8e7040d9f68a2736b0bbb26cfd4c | [
"Apache-2.0"
] | null | null | null | # Autoconf
This project has been merged into [github.com/chanjarster/gears/conf](https://github.com/chanjarster/gears/tree/master/conf)
| 27.6 | 124 | 0.789855 | eng_Latn | 0.598372 |
057e5e87fcea7f1429593c87874df2b21d57e890 | 355 | md | Markdown | _project/bedroom-decor-ideas-and-designs-how-to-decorate-a-horse-themed-bedroom-for-an-equestrian.md | rumnamanya/rumnamanya.github.io | 2deadeff04c8a48cf683b885b7fa6ab9acc1d9d9 | [
"MIT"
] | null | null | null | _project/bedroom-decor-ideas-and-designs-how-to-decorate-a-horse-themed-bedroom-for-an-equestrian.md | rumnamanya/rumnamanya.github.io | 2deadeff04c8a48cf683b885b7fa6ab9acc1d9d9 | [
"MIT"
] | null | null | null | _project/bedroom-decor-ideas-and-designs-how-to-decorate-a-horse-themed-bedroom-for-an-equestrian.md | rumnamanya/rumnamanya.github.io | 2deadeff04c8a48cf683b885b7fa6ab9acc1d9d9 | [
"MIT"
] | null | null | null | ---
layout: project_single
title: "Bedroom Decor Ideas and Designs: How to Decorate a Horse Themed Bedroom for an Equestrian!"
slug: "bedroom-decor-ideas-and-designs-how-to-decorate-a-horse-themed-bedroom-for-an-equestrian"
parent: "horse-theme-bedroom-ideas"
---
Bedroom Decor Ideas and Designs: How to Decorate a Horse Themed Bedroom for an Equestrian! | 50.714286 | 100 | 0.785915 | eng_Latn | 0.951227 |
057ee1971c090223ffcb4361437e3ddeaae8cd44 | 32 | md | Markdown | README.md | saypawn/wireframe | a7f876f3173f3de63d4eb93267a2dc76cbb91369 | [
"MIT"
] | null | null | null | README.md | saypawn/wireframe | a7f876f3173f3de63d4eb93267a2dc76cbb91369 | [
"MIT"
] | null | null | null | README.md | saypawn/wireframe | a7f876f3173f3de63d4eb93267a2dc76cbb91369 | [
"MIT"
] | null | null | null | # wireframe
wireframe exercise
| 10.666667 | 19 | 0.8125 | eng_Latn | 0.731403 |
057eefb5d82feea998b50921181b19e5a273acd4 | 196 | md | Markdown | README.md | maxnus/Oam_Notify | 46ffda833431abe31c1339f6d850c249e3905f8a | [
"Apache-2.0"
] | null | null | null | README.md | maxnus/Oam_Notify | 46ffda833431abe31c1339f6d850c249e3905f8a | [
"Apache-2.0"
] | null | null | null | README.md | maxnus/Oam_Notify | 46ffda833431abe31c1339f6d850c249e3905f8a | [
"Apache-2.0"
] | null | null | null | Oam Notify Bot for Messaging Services
### Example Usages ###
OamNotify notify = new LineOamNotify();
notify.setRecipients("<Set ของ userId คนรับ>");
notify.sendMessage("<ข้อความที่จะส่ง>");
| 19.6 | 47 | 0.709184 | eng_Latn | 0.384898 |
057f26033cba8718f1290d4714c0bfc6d680c625 | 4,995 | md | Markdown | Source/ThirdParty/nanodbc/CHANGELOG.md | eberan/urho3d | 642f09817e19b93bf6ac6d20052e505c52ca29dc | [
"Apache-2.0"
] | null | null | null | Source/ThirdParty/nanodbc/CHANGELOG.md | eberan/urho3d | 642f09817e19b93bf6ac6d20052e505c52ca29dc | [
"Apache-2.0"
] | null | null | null | Source/ThirdParty/nanodbc/CHANGELOG.md | eberan/urho3d | 642f09817e19b93bf6ac6d20052e505c52ca29dc | [
"Apache-2.0"
] | null | null | null | # v2.11.3
- Fixes segmentation fault issue with unixODBC on Linux systems.
- Adds support for `while(!results.end())` style iteration.
# v2.11.2
- Adds this CHANGELOG.md file. Future releases should update it accordingly!
- Adds CHANGELOG.md helper script.
# v2.11.1
## New Features
- Major thanks again to Mateusz Łoskot for all the new features!
- Adds convenient access to catalog objects (tables, columns, primary keys).
- Adds `database_name` and `catalog_name `methods to connection class.
- Adds CMake option `NANODBC_ENABLE_LIBCXX` to enable/disable libc++ builds.
- Adds CMake option `NANODBC_EXAMPLES` to enable/disable the example target.
- Adds a `latest` release branch to track most recent release.
## Testing
- Massive updates to Travis CI continuous integration.
- Adds general `odbc_test` to target variety of ODBC drivers.
- Adds specific MySQL tests.
- Updates test target organization.
- The way the targets were designed is such that:
- test: runs all tests, but will not build them
- tests: builds all tests, but does not run them
- check: builds all tests and then runs all tests
- For individual tests then, it makes sense to use:
- ${name}_test: runs ${name}_test, but will not build it
- ${name}_tests: builds ${name}_test, but does not run it
- ${name}_check: builds ${name}_test and then runs it
## Bug Fixes
- Fix test check of `result::affected_rows` for `SELECT` statement.
- Fix `result::position` to make it consistent with `SQL_ATTR_ROW_NUMBER`.
- Fix string object construction syntax.
- Adds missing `#include <cstring>`.
## Other Changes
- More robust and friendly publish and release scripts.
- Updates to README and documentation.
- Adds `-DUNICODE` and `-D_UNICODE` for Visual Studio projects.
- Adds examples based on the documentation.
- Adds `rowset_iteration` example.
# v2.10.0
## New Features
- Major thanks to Mateusz Łoskot for all the effort!
- Adds Dockerfile to support testing and development.
- Adds build.bat convenience script for Visual Studio users.
- Adds CMake options `NANODBC_INSTALL` and `NANODBC_TEST` to control generation of those targets.
## Bug Fixes
- Fixes cmake build on OS X El Capitan.
- Refine assert in `result_impl::position` with `SQL_ROW_NUMBER_UNKNOWN`.
- MSBuild Platform property for 32-bit is Win32.
- Reset null indicator before move for all columns, not just bound columns.
- Fixes doxygen generation of macro docs.
# v2.9.1
## New Features
- Adds Vagrantfile to support testing and development.
- Adds customizable `NANODBC_ASSERT` macro.
- Adds CMake option `NANODBC_STATIC` (default OFF).
- Clean up Visual C++ 64-bit warnings.
## Bug Fixes
- CMake: Fixes ODBC linking on Unix.
- Adds documentation on is_null() limitation.
- Write null indicator to `cbdata_` if indicated by `SQLGetData`.
## Testing
- Initial configuration of Travis CI build matrix.
## Other Changes
- Added a Contributing section to readme.
- Updates to SQLite tests.
- Disable MSVC warning C4244 in tests.
# v2.8.1
- Update CMakeLists.txt to enable builds with Visual Studio. Thanks Mateusz Łoskot!
- Add async connection support, plus extended database_error info. Thanks Yao Wei Tjong!
- Add linking against ODBC libraries on Windows.
- Change `param_type_from_direction` to throw `programming_error`.
- Define `NANODBC_SNPRINTF` in terms of `_snprintf_s` for MSVC.
- Setting CMake `-DNANODBC_ODBC_VERSION` option now works.
# v2.7.0
- Adds move constructors.
- Fixes Xcode MARK comments.
- Adds section comment banners to header file.
- Removes `throw()` from header files, uses `noexcept` instead.
- Adds basic and sqlite `std::move` test case.
# v2.6.0
- Resolves issue with decimal digits/scale and rounding. Thanks dedomilo!
- Resolve issue with `DECIMAL` to string conversion. Thanks dedomilo!
# v2.5.1
- Disable default unicode on windows.
- Override ODBC version with `NANODBC_ODBC_VERSION`.
# v2.4.0
- Add `statement::async_execute_direct` and `statement::async_complete`. Thanks Jon Valvatne!
- Add NOEXCEPT define to allow compilation under Visual Studio 2013.
# v2.3.0
- Provides optional Boost workaround for missing codecvt support in libstdc++.
# v2.2.3
- Adds minimap banners for code navigation.
- Adds `column_c_datatype()`.
- Converts line endings to unix.
- Adds `just_execute` class of functions that don't create result objects.
# v2.1.0
- Adds publish script.
- Fixes broken links in readme.
- Use C++11's `=delete` where appropriate.
# v2.0.1
- Fixes many documentation issues.
- Adds more todo info about updating docs.
- Adds notes about different versions.
- Cleans up style; removes CPP11 macros and C++03 support cruft.
- Silence warnings and untabify.
- Works with Unicode (std::wstring as nanodbc::string_type)
- Using Nanodbc with SQL Server Native Client works with nvarchar(max) and varchar(max) fields in Win32 and Win64.
# v1.0.0
Version 1.0.0 and all commits prior are now completely unsupported.
| 32.019231 | 114 | 0.747948 | eng_Latn | 0.939613 |
057f5d6eb7b6aae86a05db23a87008b4cb07ef58 | 11,874 | md | Markdown | _posts/software-development/2015-05-24-database-design_optimization.md | aravind666/aravind666.github.io | 06713530aa1229e664c015d15b3a1b184bfb723a | [
"MIT"
] | 1 | 2015-12-18T04:57:12.000Z | 2015-12-18T04:57:12.000Z | _posts/software-development/2015-05-24-database-design_optimization.md | aravind666/aravind666.github.io | 06713530aa1229e664c015d15b3a1b184bfb723a | [
"MIT"
] | null | null | null | _posts/software-development/2015-05-24-database-design_optimization.md | aravind666/aravind666.github.io | 06713530aa1229e664c015d15b3a1b184bfb723a | [
"MIT"
] | 1 | 2016-02-02T04:37:39.000Z | 2016-02-02T04:37:39.000Z | ---
layout: post
title: "Database Design Optimization"
category: "Software Development"
---
When ever you are building a database driven web application, we first plan our entities, and its relationships by writing an ER diagram, Once done we implement our DB by creating necessary tables with necessary columns.
Now before moving towards OOD we need to make sure that our database will contain
1. minimum of duplicate data.
2. minimum of redundant data
3. Data stored in this database is easy to fetch
4. easy to edit
5. easy to maintain.
> A database which has all these above listed features is actually called normalized database.
So to normalize a database we apply a set of formal criteria of rules called Normal Forms, these are actually developed by a person called Edgar Codd in 1972, these rules defines series of tests on Database to certify whether it satisfies a certian normal form.
In this post I would like to share some of my understandings on normalizing a database and its advantages.
Process of normalization involves several levels or normal forms, again the level to which you need to optimize depends on your bussiness need.
Level 1 : - First normal form
Level 2 : - Secound Normal form
Level 3 : - Third Normal form
There are some more levels such as Fourth and Fifth Normal forms, there is also an another set of rules to optimize called BC normal form, usually in Agile projects we prefer taking it to max third normal form because we have changing bussiness requirements.
Let me elaborate by explaining each of those levels
### First Normal Form (1NF)
> First normal form says that each of your columns and each of your tables should contain one value just one value, and there should be no repeating groups.
For eg..
Lets say we are designing a database for library and we have a table called books, books table has columns book\_id, author, author\_name, category, year\_of\_publication.
Now we start inserting books data inside columns, and we realize that a book has multiple authors and multiple catogories. for eg.. books like " Search Inside Yourself " by chang meng comes under philosophy, management, personality development and many more , and also books lke " how google works " will have multiple authors .
If we analyze our situation we have some more data for which this table is not sufficiant.
To solve this problem we have two ways.
1. Add multiple authors and categories into the table in CSV format
2. Identify or fix highest number of categories and authors a book can have, and add that many columns for eg. say you fix the max number of authors can be 4 and max number of categories can be 2 and add 4 + 2 columns to this table saying category1 category2 or author1, author2 etc ...
Lets examine our first solution, in this you are adding multiple values in a single column, but still you can not fetch them individually, and also it becomes very difficult to search for a particular author or category since it has multiple values.
In the secound solution we add multiple columns, lets say we find a book which has more authors than what you fixed, In that case you have to add new column to store that, calling it as author6 or author7, If we carefully observe both of our solutions are actually not a scalable solution, if the project for which we are building is an agile project, the continous change in the requirements will easily make our life hell.
To make our designs scalable, we have to apply first normal form rule to normalize this design, by some how avoiding the repeating group of data and multiple values. To achive this a technically feasible solution would be to have more tables, instead of having one table like this.
So to bring our design to first normal form we have to create two more related tables
1. book\_has\_authors which stores book\_id and author
2. book\_has\_categories which stores book\_id and cateogory
By doing so, you will be avoiding repeating group of data and also multi valued columns, Creating related tables to optimize database design is one of the most common approach, there are several creative ideas that you can get if you are having control over the bussiness architecture of your system
Now our design is optimized to first normal form.
### Secound Normal form ( 2nf )
The secound normal form actually adds to first normal form, meaning you cannot directly optimize your design to 2nf to do so you should frst optimize to 1nf, so the rules are hierarchical and it cannot be changed. Before defining 2nf rule, let me explain something which is very much required to understand 2nf
#### Functional Dependency
In simple terms,
> A functional dependency describes the relationship between attributes in a given relation R denoted as x -> Y. This means that the attribute Y is functionally dependent on the attribute X
for example,
SSN --> Name
The meaning of the above notation is the attribute Name is functionally dependent on SSN. That means SSN uniquely determines an attribute Name.
Another example
department\_no -> {dept\_name, dept\_location}
Here both dept\_name and dept\_location are dependent on department\_no, meaning department\_no can be used to identify both dept\_name as well as dept\_location.
A functional dependency can be either partial or full,
> In a functional dependency F, Y is fully functionally dependent on X if F implies X -> Y, but not W-> Y where W is a subset of X, meaning set of attributes in X contains at least one element which is not in the set of attributes W.
I know its really complex, let me give you an example.
Lets denote a functional dependency like below
{date, exam} -> room\_no
So in the above functional dependency, left hand side has 2 attributes date and exam, and room\_no is actually determined by date and exam, since room\_no is functionally dependent on determinants date and exam.So now if we remove exam or date in the determinants list, the dependency relation ship fails, reason is simple in our design there are multiple tuples which has same date and room\_no and same exam and room\_no.
> In a functional dependency F, A is partially functional dependent on X if X is a proper subset of some key K.
Example
{date, exam} -> room\_no
If lets say in the same example, if the dependency still holds good when we remove date or exam, attributes from LHS, then the functional dependency described here is partial
So now its time to describe 2nf : -
> Every non prime Attribute in a relational Schema, should be fully functionally dependent on primary key or every candidate key.
Lets say you have a table called employee\_project\_details with the columns SSN, project\_no, hours, emp\_name, project\_name, project\_location
The first step to optimize for 2nf is identify Functional dependencies .
Here you can identify three dependencies
1. SSN -> emp\_name
2. project\_no -> {project\_name, project\_location}
3. {SSN, project\_no} -> hours
Here If you properly observe that we have a composite key for the table, {SSN,project\_no}. As per the 2nf definition every non prime should be fully functionally dependent on primary key or candidate key with in a composite key. So now if I remove project\_no I can still determine all the determinants of project as well as employee. So to optimize to 2nf we need to decompose the relationships to convert those partial dependencies to fully functional dependencies .
So now we can convert our design with single table called employee\_project\_details as three different tables for three dependencies identified
employee table with attributes SSN, emp\_name
project table with attributes project\_name, project\_location
employee\_has\_project with SSN, project\_no, hours
I think the easiest way to design a DB optimized to 2nf is to keep creating tables for each Functional dependency that you identify and then redo the same recursively on those tables by asking yourself a question
> can I figure out any of the values in this row from just part of the composite key that I have in my table ?
stop when you dont get any answer.
I am sure you got one billion dollor question, what is the problem in having partial functional dependencies
We design DB for an application layer, and if we have partial dependencies in the DB layer, we might end up storing wrong data since application layer might have some bug which might miss entering project data for an employee ( in the above example ) and DB layer treats it normally. Ensuring a bugfree application layer is really impractical but ensuring optimized DB makes our life easy to rectify those bugs easily.
### Third Normal form (3nf)
As I explianed before these rules are hierarchical, if you want to optimize to 3nf, you can do so only after optimizing upto 2nf. Before defining Third normal form, let me explain to you another important term called transitive dependency.
> A Functional dependency X -> Y in a relation schema is a transitive dependency if there is a set of attributes Z that is not a subset of any key of R, and both X -> Z and Z->Y holds good.
In simple terms, if there exists a chain of dependency between attributes like X -> z -> Y
So now let me define 3nf rule : -
Non non prime attribute is transitively dependent on Primary Key. So in simple terms we can say, if we have a design with several tables, optimized to 2nf, then we should not be able to figure out any of the values in a tuple from any of the other values in the same tuple. Lets take a simple example table employee\_department with columns
{ SSN, Name, dateofbirth, address, Dno, Dname, MgrSSN }
Lets identify functional dependencies before optimizing it to 3nf
SSN -> {Name, DOB, address, Dno, Dname, MgrSSN}
Dno -> {Dname, MgrSSN}
So now since we can see a transitive dependency here, SSN -> Dno -> {Dname, MGrSSN }. We need to decompose the table in to two different tables
Employees table : - SSN, Name , DOB, Addr, Dno
Departments Table : - Dno, Dname, MgrSSN
So now I am sure we wont get the answer to the question Can we figure out any of the values in a tuple from any of the other values ? Before we were actually able to do so in the example, like we were able to figure out Dname from Dno
Again a billion dollor question Why should avoid transitive relationship ?
Again its to avoid insert and update anamolies, lets say if we have transitive dependency and we are using the same table employee\_department, then in case if we need to create a new department with out any employee, then we need to have null values for employee related data.
In fact all these Normalization rules actually sugests us to maintain the semantics of the attributes, and avoid a situation where system generates spurious tuples, for example, the meaning of the employeee relation schema is that each tuple represents an employee record.
So, we should always take our database design through the first, second, and third normal forms. There are more criteria available. As I have already stated before, there are fourth, fifth, and sixth normal forms. There's something called Boyce-Codd normal form. But taking it to third normal form is the usual expectation in an agile project.
Some people might say " Normalization is not actually required since databases are highly efficiant and evolved and they are capable of storing millions of records " . To convince them I would say, Database is not only a collection of some data, it is a collection of meaningful and related data
Some people also say that Agile Methodology does not allow developers to normalize the database well, I totally disagree, if we properly understand normalization concepts It actually provides scalability for future changes
I hope you enjoyed reading my post, it is just an attempt to simplify those complex mathematical definitions of database concepts.
| 62.825397 | 469 | 0.789372 | eng_Latn | 0.999888 |
05800c67bcb54e690f89da0c18b59010f1080644 | 4,172 | md | Markdown | _posts/2020-06-02-Observer-Pattern.md | navining/blog | 7c920d2c2f4812c2ca9d98db062962a285f71d24 | [
"MIT"
] | null | null | null | _posts/2020-06-02-Observer-Pattern.md | navining/blog | 7c920d2c2f4812c2ca9d98db062962a285f71d24 | [
"MIT"
] | null | null | null | _posts/2020-06-02-Observer-Pattern.md | navining/blog | 7c920d2c2f4812c2ca9d98db062962a285f71d24 | [
"MIT"
] | null | null | null | ---
layout: post
title: Observer Pattern
subtitle: Publish-subscribe model for handling one-to-many objects communication
date: 2020-6-2
author: Navi
header-img: img/post-bg-debug.png
catalog: true
tags:
- C++
- Design Patterns
---
# Observer Pattern
The observer pattern belongs to the behavior pattern, which focuses on the communication between objects. The observer pattern applies to a one-to-many relationship of objects, where multiple objects rely on a single object. When the state of the object changes, other objects can receive corresponding notifications.
A common observer pattern is the publish-subscribe model, where the observers subscribe to a subject, and the subject publishes notification to the observers when its status changes.
Here we have an abstract class *Observer*, and three classes that inherit from it. These classes override the *handle()* method which handles messages according to their IDs. *Observer1* handles message 1 and 2, while *Observer2* handles message 2 and 3, and *Observer3* handles message *1* and *3*.
```cpp
class Observer {
public:
virtual void handle(int id) = 0;
};
class Observer1 : public Observer {
public:
void handle(int id) {
switch (id) {
case 1:
cout << "Message 1" << endl;
break;
case 2:
cout << "Message 2" << endl;
break;
default:
cout << "Unknown message" << endl;
break;
}
}
};
class Observer2 : public Observer {
public:
void handle(int id) {
switch (id) {
case 2:
cout << "Message 2" << endl;
break;
case 3:
cout << "Message 3" << endl;
break;
default:
cout << "Unknown message" << endl;
break;
}
}
};
class Observer3 : public Observer {
public:
void handle(int id) {
switch (id) {
case 1:
cout << "Message 1" << endl;
break;
case 3:
cout << "Message 3" << endl;
break;
default:
cout << "Unknown message" << endl;
break;
}
}
};
```
Then we have the *Subject* class which keeps an unordered map. The map keys are message IDs, and the values are lists of observers. The class has two methods *subscribe()* and *publish()*. The former takes an *Observer* and the message ID to be subscribed, and add the observer to the map with message ID as the key. *publish()* takes the message ID to be published, takes out the observers from the map who have subscribed to this message, and call their *handle()* method one by one.
```cpp
class Subject {
public:
void subscribe(Observer *observer, int id) {
_map[id].push_back(observer);
}
void publish(int id) {
auto it = _map.find(id);
if (it != _map.end()) {
for (Observer *p : it->second) {
p->handle(id);
}
}
}
private:
unordered_map<int, list<Observer *>> _map;
};
```
Now in the *main()* function, we subscribes the observers to the messages they would like to handle. When the status of the subject changes, it notify the observers by publishing the corresponding messages.
```cpp
int main() {
Subject subject;
Observer *p1 = new Observer1();
Observer *p2 = new Observer2();
Observer *p3 = new Observer3();
subject.subscribe(p1, 1);
subject.subscribe(p1, 2);
subject.subscribe(p2, 2);
subject.subscribe(p2, 3);
subject.subscribe(p3, 1);
subject.subscribe(p3, 3);
subject.publish(1);
cout << "--------------------" << endl;
subject.publish(2);
cout << "--------------------" << endl;
subject.publish(3);
cout << "--------------------" << endl;
subject.publish(4);
delete p1, p2, p3;
}
```
The above code has the following outputs:
```
Observer1: Message 1
Observer3: Message 1
--------------------
Observer1: Message 2
Observer2: Message 2
--------------------
Observer2: Message 3
Observer3: Message 3
--------------------
```
| 29.380282 | 485 | 0.592761 | eng_Latn | 0.98395 |
05809d3f5f6dd804eb0ed153966752c6b32d29e8 | 350 | md | Markdown | content/Obsidian Daily Notes.md | ransurf/quartz | 174c514401f4265b360fb0e22449adeb462cc152 | [
"MIT"
] | null | null | null | content/Obsidian Daily Notes.md | ransurf/quartz | 174c514401f4265b360fb0e22449adeb462cc152 | [
"MIT"
] | null | null | null | content/Obsidian Daily Notes.md | ransurf/quartz | 174c514401f4265b360fb0e22449adeb462cc152 | [
"MIT"
] | null | null | null | Status:
Tags:
Links: [[Obsidian Features]]
___
# Obsidian Daily Notes
## Missing
-
___
# Backlinks
```dataview
list from [[Obsidian Daily Notes]] AND !outgoing([[Obsidian Daily Notes]])
```
___
References: [Reddit Post](https://www.reddit.com/r/ObsidianMD/comments/rpy21o/what_template_do_you_use_for_your_daily_notes/)
Created:: 2021-09-19 21:09 | 21.875 | 125 | 0.751429 | kor_Hang | 0.386027 |
0580e5713ae28e7b1e5ebdd03518bf1e8da6f923 | 550 | md | Markdown | C and C++/Competitive Problem Solutions/README.md | CustomUser47/Hacktoberfest2020 | 1b141fa5fb9fd0a170b40aca92cbd1d318cf17cd | [
"MIT"
] | null | null | null | C and C++/Competitive Problem Solutions/README.md | CustomUser47/Hacktoberfest2020 | 1b141fa5fb9fd0a170b40aca92cbd1d318cf17cd | [
"MIT"
] | null | null | null | C and C++/Competitive Problem Solutions/README.md | CustomUser47/Hacktoberfest2020 | 1b141fa5fb9fd0a170b40aca92cbd1d318cf17cd | [
"MIT"
] | null | null | null | # Competitive Programming | Practice Problem Solutions
- All files have been named with the problem names themselves
- Any improvements to the existing code is appreciated (just add your solution and name it as secondary). For eg. If you want to suggest improvement like a shorter time complexity in CHEFWARS.cpp just create another file CHEFWARS-secondary.cpp and post your solution there!
##### Targets:
- [x] Add some CodeChef solutions
- [ ] Add some Leetcode solutions
- [ ] Add some HackerRank solutions
- [ ] Add some InterviewBit solutions
| 50 | 273 | 0.778182 | eng_Latn | 0.99802 |
0582787d697cf99303a145d666c22645e9137bfc | 54 | md | Markdown | README.md | tkrs/freep | 79b7ffe304b565e5e212fa1781c2f01969d353ac | [
"MIT"
] | null | null | null | README.md | tkrs/freep | 79b7ffe304b565e5e212fa1781c2f01969d353ac | [
"MIT"
] | null | null | null | README.md | tkrs/freep | 79b7ffe304b565e5e212fa1781c2f01969d353ac | [
"MIT"
] | null | null | null | # freep
This is my first project to learn Scalameta.
| 13.5 | 44 | 0.759259 | eng_Latn | 0.999984 |
058284283cc78cc3a1ce67ba11165a51168846e1 | 8,465 | md | Markdown | README.md | textcreationpartnership/A01516 | 40f70309a16bb62c595c76cdc9d36234a55358e5 | [
"CC0-1.0"
] | null | null | null | README.md | textcreationpartnership/A01516 | 40f70309a16bb62c595c76cdc9d36234a55358e5 | [
"CC0-1.0"
] | null | null | null | README.md | textcreationpartnership/A01516 | 40f70309a16bb62c595c76cdc9d36234a55358e5 | [
"CC0-1.0"
] | null | null | null | #The tvvoo bookes of Francis Bacon. Of the proficience and aduancement of learning, diuine and humane To the King. Of the proficience and advancement of learning#
##Bacon, Francis, 1561-1626.##
The tvvoo bookes of Francis Bacon. Of the proficience and aduancement of learning, diuine and humane To the King.
Of the proficience and advancement of learning
Bacon, Francis, 1561-1626.
##General Summary##
**Links**
[TCP catalogue](http://www.ota.ox.ac.uk/tcp/) •
[HTML](http://tei.it.ox.ac.uk/tcp/Texts-HTML/free/A01/A01516.html) •
[EPUB](http://tei.it.ox.ac.uk/tcp/Texts-EPUB/free/A01/A01516.epub) •
[Page images (Historical Texts)](https://data.historicaltexts.jisc.ac.uk/view?pubId=eebo-99836346e&pageId=eebo-99836346e-611-1)
**Availability**
This keyboarded and encoded edition of the
work described above is co-owned by the institutions
providing financial support to the Early English Books
Online Text Creation Partnership. This Phase I text is
available for reuse, according to the terms of Creative
Commons 0 1.0 Universal. The text can be copied,
modified, distributed and performed, even for
commercial purposes, all without asking permission.
**Major revisions**
1. __2002-03__ __TCP__ *Assigned for keying and markup*
1. __2002-04__ __Apex CoVantage__ *Keyed and coded from ProQuest page images*
1. __2002-05__ __TCP Staff (Michigan)__ *Sampled and proofread*
1. __2002-07__ __Apex CoVantage__ *Rekeyed and resubmitted*
1. __2002-08__ __Olivia Bottum__ *Sampled and proofread*
1. __2002-08__ __Olivia Bottum__ *Text and markup reviewed and edited*
1. __2002-10__ __pfs__ *Batch review (QC) and XML conversion*
##Content Summary##
#####Front#####
#####Body#####
1. THE FIRST BOOKE of FRANCIS BACON; of the proficience and aduancement of Learning diuine, and humane. To the King.
1. THE SECOND Booke of FRANCIS BACON; of the proficience or aduancement of Learning, Diuine and Humane. To the King.
**Types of content**
* There are 71 **verse** lines!
* Oh, Mr. Jourdain, there is **prose** in there!
There are 219 **ommitted** fragments!
@__reason__ (219) : illegible (212), duplicate (4), foreign (3) • @__resp__ (212) : #APEX (212) • @__extent__ (216) : 1+ letters (187), 1 word (21), 2 words (2), 1 page (4), 1 line (1), 3 words (1)
**Character listing**
|Text|string(s)|codepoint(s)|
|---|---|---|
|Latin-1 Supplement|¶èàùâé|182 232 224 249 226 233|
|Combining Diacritical Marks|̄|772|
|General Punctuation|•…—|8226 8230 8212|
|Geometric Shapes|◊|9674|
|CJKSymbolsandPunctuation|〈〉|12296 12297|
##Tag Usage Summary##
###Header Tag Usage###
|No|element name|occ|attributes|
|---|---|---|---|
|1.|__author__|2||
|2.|__availability__|1||
|3.|__biblFull__|1||
|4.|__change__|7||
|5.|__date__|10| @__when__ (1) : 2003-01 (1)|
|6.|__edition__|1||
|7.|__editionStmt__|1||
|8.|__editorialDecl__|1||
|9.|__extent__|2||
|10.|__idno__|6| @__type__ (6) : DLPS (1), STC (2), EEBO-CITATION (1), PROQUEST (1), VID (1)|
|11.|__keywords__|1| @__scheme__ (1) : http://authorities.loc.gov/ (1)|
|12.|__label__|7||
|13.|__langUsage__|1||
|14.|__language__|1| @__ident__ (1) : eng (1)|
|15.|__listPrefixDef__|1||
|16.|__note__|8||
|17.|__notesStmt__|2||
|18.|__p__|11||
|19.|__prefixDef__|2| @__ident__ (2) : tcp (1), char (1) • @__matchPattern__ (2) : ([0-9\-]+):([0-9IVX]+) (1), (.+) (1) • @__replacementPattern__ (2) : http://eebo.chadwyck.com/downloadtiff?vid=$1&page=$2 (1), https://raw.githubusercontent.com/textcreationpartnership/Texts/master/tcpchars.xml#$1 (1)|
|20.|__projectDesc__|1||
|21.|__pubPlace__|2||
|22.|__publicationStmt__|2||
|23.|__publisher__|2||
|24.|__ref__|2| @__target__ (2) : https://creativecommons.org/publicdomain/zero/1.0/ (1), http://www.textcreationpartnership.org/docs/. (1)|
|25.|__seriesStmt__|1||
|26.|__sourceDesc__|1||
|27.|__term__|2||
|28.|__textClass__|1||
|29.|__title__|5||
|30.|__titleStmt__|2||
###Text Tag Usage###
|No|element name|occ|attributes|
|---|---|---|---|
|1.|__am__|9||
|2.|__desc__|219||
|3.|__div__|3| @__type__ (3) : title_page (1), book (2) • @__n__ (2) : 1 (1), 2 (1)|
|4.|__ex__|9||
|5.|__expan__|9||
|6.|__figure__|1||
|7.|__g__|2915| @__ref__ (2915) : char:EOLhyphen (2558), char:cmbAbbrStroke (345), char:abque (9), char:EOLunhyphen (3)|
|8.|__gap__|219| @__reason__ (219) : illegible (212), duplicate (4), foreign (3) • @__resp__ (212) : #APEX (212) • @__extent__ (216) : 1+ letters (187), 1 word (21), 2 words (2), 1 page (4), 1 line (1), 3 words (1)|
|9.|__head__|2||
|10.|__hi__|2336| @__rend__ (2) : sup (2)|
|11.|__l__|71||
|12.|__lg__|16||
|13.|__note__|33| @__place__ (33) : margin (33)|
|14.|__p__|453||
|15.|__pb__|339| @__facs__ (339) : tcp:611:1 (2), tcp:611:2 (1), tcp:611:3 (2), tcp:611:4 (2), tcp:611:5 (2), tcp:611:6 (2), tcp:611:7 (2), tcp:611:8 (2), tcp:611:9 (2), tcp:611:10 (2), tcp:611:11 (2), tcp:611:12 (2), tcp:611:13 (2), tcp:611:14 (2), tcp:611:15 (2), tcp:611:16 (2), tcp:611:17 (2), tcp:611:18 (2), tcp:611:19 (2), tcp:611:20 (2), tcp:611:21 (2), tcp:611:22 (2), tcp:611:23 (2), tcp:611:24 (2), tcp:611:25 (2), tcp:611:26 (2), tcp:611:27 (2), tcp:611:28 (2), tcp:611:29 (2), tcp:611:30 (2), tcp:611:31 (2), tcp:611:32 (2), tcp:611:33 (2), tcp:611:34 (2), tcp:611:35 (2), tcp:611:36 (2), tcp:611:37 (2), tcp:611:38 (2), tcp:611:39 (2), tcp:611:40 (2), tcp:611:41 (2), tcp:611:42 (2), tcp:611:43 (2), tcp:611:44 (2), tcp:611:45 (2), tcp:611:46 (2), tcp:611:47 (2), tcp:611:48 (2), tcp:611:49 (2), tcp:611:50 (2), tcp:611:51 (2), tcp:611:52 (2), tcp:611:53 (2), tcp:611:54 (2), tcp:611:55 (2), tcp:611:56 (2), tcp:611:57 (2), tcp:611:58 (2), tcp:611:59 (2), tcp:611:60 (2), tcp:611:61 (2), tcp:611:62 (2), tcp:611:63 (2), tcp:611:64 (2), tcp:611:65 (2), tcp:611:66 (2), tcp:611:67 (2), tcp:611:68 (2), tcp:611:69 (2), tcp:611:70 (2), tcp:611:71 (2), tcp:611:72 (2), tcp:611:73 (2), tcp:611:74 (2), tcp:611:75 (2), tcp:611:76 (2), tcp:611:77 (2), tcp:611:78 (2), tcp:611:79 (2), tcp:611:80 (2), tcp:611:81 (2), tcp:611:82 (2), tcp:611:83 (2), tcp:611:84 (2), tcp:611:85 (2), tcp:611:86 (2), tcp:611:87 (2), tcp:611:88 (2), tcp:611:89 (2), tcp:611:90 (2), tcp:611:91 (2), tcp:611:92 (2), tcp:611:93 (2), tcp:611:94 (2), tcp:611:95 (2), tcp:611:96 (2), tcp:611:97 (2), tcp:611:98 (2), tcp:611:99 (2), tcp:611:100 (2), tcp:611:101 (2), tcp:611:102 (2), tcp:611:103 (2), tcp:611:104 (2), tcp:611:105 (2), tcp:611:106 (2), tcp:611:107 (2), tcp:611:108 (2), tcp:611:109 (2), tcp:611:110 (2), tcp:611:111 (2), tcp:611:112 (2), tcp:611:113 (2), tcp:611:114 (2), tcp:611:115 (2), tcp:611:116 (2), tcp:611:117 (2), tcp:611:118 (2), tcp:611:119 (2), tcp:611:120 (2), tcp:611:121 (2), tcp:611:122 (2), tcp:611:123 (2), tcp:611:124 (2), tcp:611:125 (2), tcp:611:126 (2), tcp:611:127 (2), tcp:611:128 (2), tcp:611:129 (2), tcp:611:130 (2), tcp:611:131 (2), tcp:611:132 (2), tcp:611:133 (2), tcp:611:134 (2), tcp:611:135 (2), tcp:611:136 (2), tcp:611:137 (2), tcp:611:138 (2), tcp:611:139 (2), tcp:611:140 (2), tcp:611:141 (2), tcp:611:142 (2), tcp:611:143 (2), tcp:611:144 (2), tcp:611:145 (2), tcp:611:146 (2), tcp:611:147 (2), tcp:611:148 (2), tcp:611:149 (2), tcp:611:150 (2), tcp:611:151 (2), tcp:611:152 (2), tcp:611:153 (2), tcp:611:154 (2), tcp:611:155 (2), tcp:611:156 (2), tcp:611:157 (2), tcp:611:158 (2), tcp:611:159 (2), tcp:611:160 (2), tcp:611:161 (2), tcp:611:162 (2), tcp:611:163 (2), tcp:611:164 (2), tcp:611:165 (2), tcp:611:166 (2), tcp:611:167 (2), tcp:611:168 (2), tcp:611:169 (2), tcp:611:170 (2) • @__rendition__ (62) : simple:additions (62) • @__n__ (163) : 1 (2), 2 (2), 4 (2), 5 (2), 6 (2), 7 (2), 8 (2), 9 (2), 10 (2), 11 (2), 12 (2), 13 (2), 14 (2), 15 (2), 16 (3), 18 (3), 20 (1), 21 (4), 22 (2), 23 (2), 34 (3), 25 (2), 26 (2), 27 (2), 28 (2), 29 (2), 30 (2), 31 (2), 32 (2), 33 (2), 35 (2), 36 (2), 37 (2), 38 (2), 39 (2), 40 (2), 41 (2), 42 (2), 43 (2), 44 (2), 45 (2), 3 (1), 19 (1), 46 (1), 47 (1), 48 (1), 49 (1), 50 (1), 51 (1), 52 (1), 53 (1), 54 (1), 55 (1), 56 (1), 57 (1), 58 (1), 59 (1), 60 (1), 61 (1), 62 (1), 63 (1), 64 (1), 65 (1), 66 (1), 67 (1), 68 (1), 69 (4), 70 (3), 71 (1), 72 (2), 74 (4), 73 (1), 75 (1), 77 (2), 78 (1), 79 (2), 80 (1), 82 (1), 87 (1), 89 (1), 90 (1), 91 (1), 92 (1), 93 (2), 94 (1), 95 (1), 99 (3), 97 (1), 102 (1), 103 (2), 106 (1), 107 (1), 108 (1), 109 (1), 110 (1), 111 (1), 112 (1), 113 (1), 114 (1), 105 (1), 116 (1), 117 (1), 118 (1)|
|16.|__q__|1||
|17.|__seg__|2| @__rend__ (2) : decorInit (2)|
| 67.18254 | 3,712 | 0.614176 | yue_Hant | 0.196909 |
05858ceb89db6eacda34f5846b7dc627a60311c5 | 78 | md | Markdown | README.md | Utkarshpankaj69/Sab-but-true | 50832c00e65ae4c0c2af1d77d5200fa13492179a | [
"MIT"
] | null | null | null | README.md | Utkarshpankaj69/Sab-but-true | 50832c00e65ae4c0c2af1d77d5200fa13492179a | [
"MIT"
] | null | null | null | README.md | Utkarshpankaj69/Sab-but-true | 50832c00e65ae4c0c2af1d77d5200fa13492179a | [
"MIT"
] | null | null | null | #include<stdio.h>
int main()
{
printf("Bye world!");
return 0;
}
| 6.5 | 25 | 0.525641 | eng_Latn | 0.8744 |
05863198ce67d1c20b12772e6b459f882838b128 | 2,129 | md | Markdown | LeetCode/2018-12-31-112-Path-Sum.md | HeRuivio/-Algorithm | 1fbe6256630758fda3af68f469471ee246730afc | [
"MIT"
] | 5 | 2018-10-30T05:07:32.000Z | 2019-06-18T08:11:38.000Z | LeetCode/2018-12-31-112-Path-Sum.md | HeRuivio/-Algorithm | 1fbe6256630758fda3af68f469471ee246730afc | [
"MIT"
] | 1 | 2020-05-09T09:05:16.000Z | 2020-05-09T09:05:16.000Z | LeetCode/2018-12-31-112-Path-Sum.md | HeRuivio/-Algorithm | 1fbe6256630758fda3af68f469471ee246730afc | [
"MIT"
] | 2 | 2020-05-09T09:02:22.000Z | 2020-12-09T13:23:00.000Z | # LeetCode 112. Path Sum
## Description
Given a binary tree and a sum, determine if the tree has a root-to-leaf path such that adding up all the values along the path equals the given sum.
Note: A leaf is a node with no children.
Example:
Given the below binary tree and sum = 22,
```python
5
/ \
4 8
/ / \
11 13 4
/ \ \
7 2 1
return true, as there exist a root-to-leaf path 5->4->11->2 which sum is 22.
```
## 描述
给定一颗二叉树和一个目标值，确定树是否具有根节点到叶子节点，使得沿路径的所有值相加等于给定值.
注意：叶子是没有子节点的节点.
例：
给定以下二叉树和sum = 22，
```python
5
/ \
4 8
/ / \
11 13 4
/ \ \
7 2 1
返回True，因为存在路径 5->4->11->2 使得求和为目标值22.
```
### 思路
* 我们从根节点开始递归的求和，如果到达叶子节点且当前总和与目标值相等，则返回True，否则返回False.
* 树的题使用递归求解叫简单.
```python
# -*- coding: utf-8 -*-
# @Author: 何睿
# @Create Date: 2018-12-31 09:48:06
# @Last Modified by: 何睿
# @Last Modified time: 2018-12-31 10:48:32
class TreeNode:
def __init__(self, x):
self.val = x
self.left = None
self.right = None
class Solution:
def hasPathSum(self, root, sum):
"""
:type root: TreeNode
:type sum: int
:rtype: bool
"""
if not root:
return False
return self.recursion(root, 0, sum)
def recursion(self, root, _sum, target):
# 如果为空
if not root:
# 如果总和与目标值相等，返回True
if _sum == target:
return True
# 否则返回False
else:
return False
_sum += root.val
# 计算左子树
left = self.recursion(root.left, _sum, target)
# 计算右子树
right = self.recursion(root.right, _sum, target)
# 在没有左子树的情况下，才返回右子树的值
if not root.left:
return right
# 在没有右子树的情况下，才返回左子树的值
if not root.right:
return left
else:
# 任意一个满足条件就行
return left or right
```
源代码文件在[这里](https://github.com/ruicore/Algorithm/blob/master/Leetcode/2018-12-31-112-Path-Sum.py).
©本文首发于[何睿的博客](https://www.ruicore.cn/leetcode-112-path-sum/)，欢迎转载，转载需保留文章来源，作者信息和本声明.
| 20.669903 | 148 | 0.560357 | eng_Latn | 0.573081 |
0586922cf508a3633abfad23433f68d6a50cdbcc | 101 | md | Markdown | 2020_November_Leetcode_30_days_challenge/Week_3_Merge Intervals/Week_3_Merge Interval_manual link.md | coderMaruf/leetcode-1 | 20ffe26e43999e44c8acf9800acb371a49bb5853 | [
"MIT"
] | 32 | 2020-01-05T13:37:16.000Z | 2022-03-26T07:27:09.000Z | 2020_November_Leetcode_30_days_challenge/Week_3_Merge Intervals/Week_3_Merge Interval_manual link.md | coderMaruf/leetcode-1 | 20ffe26e43999e44c8acf9800acb371a49bb5853 | [
"MIT"
] | null | null | null | 2020_November_Leetcode_30_days_challenge/Week_3_Merge Intervals/Week_3_Merge Interval_manual link.md | coderMaruf/leetcode-1 | 20ffe26e43999e44c8acf9800acb371a49bb5853 | [
"MIT"
] | 8 | 2020-06-18T16:17:27.000Z | 2022-03-15T23:58:18.000Z | https://leetcode.com/problems/merge-intervals/discuss/810795/Python-by-sort-and-merge-w-Visualization | 101 | 101 | 0.841584 | yue_Hant | 0.186015 |
058761663974c4c6b7872e685238fde409ae93fe | 36 | md | Markdown | README.md | mrboggii/Practicas-JS | 63878f2554c9ba410b173e985a740dd21144a666 | [
"Apache-2.0"
] | null | null | null | README.md | mrboggii/Practicas-JS | 63878f2554c9ba410b173e985a740dd21144a666 | [
"Apache-2.0"
] | null | null | null | README.md | mrboggii/Practicas-JS | 63878f2554c9ba410b173e985a740dd21144a666 | [
"Apache-2.0"
] | null | null | null | # Practicas-JS
Practicas JavaScript
| 12 | 20 | 0.833333 | oci_Latn | 0.307467 |
05879f38702a7725114c51aec8e1ccfebf865cd4 | 42 | md | Markdown | README.md | poojakailay/Favourites | 25cc84b358e1ff270f3475eb292bc0c9c5c5ff65 | [
"Apache-2.0"
] | null | null | null | README.md | poojakailay/Favourites | 25cc84b358e1ff270f3475eb292bc0c9c5c5ff65 | [
"Apache-2.0"
] | null | null | null | README.md | poojakailay/Favourites | 25cc84b358e1ff270f3475eb292bc0c9c5c5ff65 | [
"Apache-2.0"
] | null | null | null | # Favourites
Everybody's favourite things
| 14 | 28 | 0.833333 | eng_Latn | 0.979068 |
05885825338b1b1e74ec1dd8a1c310c50f37b1e9 | 2,248 | md | Markdown | README.md | tkilloren/cookbook-openstack-rally | 08971860241f4939c484d23ed05b676fa5c0296b | [
"Apache-2.0"
] | 1 | 2017-06-06T15:49:53.000Z | 2017-06-06T15:49:53.000Z | README.md | tkilloren/cookbook-openstack-rally | 08971860241f4939c484d23ed05b676fa5c0296b | [
"Apache-2.0"
] | null | null | null | README.md | tkilloren/cookbook-openstack-rally | 08971860241f4939c484d23ed05b676fa5c0296b | [
"Apache-2.0"
] | null | null | null | # Description #
This cookbook sets up a Rally/Tempest server.
# Requirements #
Chef 11 with Ruby 1.9.x required.
# Platforms #
* RHEL/CentOS 7.0
# Cookbooks #
The following cookbooks are dependencies:
* database
# Usage #
The usage of this cookbook is optional, you may choose to set up your own databases without using this cookbook. If you choose to do so, you will need to do the following:
* create the schema specified by the `openstack-db` recipe.
* create and upload encrypted data bags into your chef environment, as
specified by `#get_password` in the `openstack-db` recipe.
# Resources/Providers #
None
# Templates #
None
# Recipes #
## default ##
- installs Rally from source
# Attributes #
See attributes/default.rb
Testing
=====
Please refer to the [TESTING.md](TESTING.md) for instructions for testing the cookbook.
Berkshelf
=====
Berks will resolve version requirements and dependencies on first run and
store these in Berksfile.lock. If new cookbooks become available you can run
`berks update` to update the references in Berksfile.lock. Berksfile.lock will
be included in stable branches to provide a known good set of dependencies.
Berksfile.lock will not be included in development branches to encourage
development against the latest cookbooks.
License and Author
==================
| | |
|:---------------------|:---------------------------------------------------|
| **Author** | Travis Killoren (<[email protected]>) |
| | |
| **Copyright** | Copyright (c) 2015, Travis Killoren |
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
| 28.1 | 171 | 0.664146 | eng_Latn | 0.993929 |
05892f99ba5839edf18d5604f77a825f654d1e51 | 385 | md | Markdown | README.md | NREL/ABSiCE | 6f7bddb82707a36b20e3ebf7c852fca18a23ef23 | [
"BSD-3-Clause"
] | 7 | 2021-12-21T16:06:31.000Z | 2022-03-05T15:56:09.000Z | README.md | NREL/ABSiCE | 6f7bddb82707a36b20e3ebf7c852fca18a23ef23 | [
"BSD-3-Clause"
] | null | null | null | README.md | NREL/ABSiCE | 6f7bddb82707a36b20e3ebf7c852fca18a23ef23 | [
"BSD-3-Clause"
] | null | null | null | # ABSiCE Tool
The Agent-Based Simulations of the Circular Economy (ABSiCE) tool is
an agent-based model built with the MESA python library. The tool enables
studying various circular economy strategies by simulating actors decisions.
## Features
* Network configuration
* Product growth and waste generation
* Agents end-of-life decision rule
## Requirements
* MESA
* networkx
| 21.388889 | 76 | 0.787013 | eng_Latn | 0.989071 |
058abd05627c9b0bf98dd53711dad9e145015a82 | 168 | md | Markdown | _demo/single-course/accordionpage/sidebaraccordionpage.md | hibbitts-design/grav-theme-hub-bones | cb43a879ca3fc075c2399d61fdf64482a9dc3f3f | [
"MIT"
] | 1 | 2017-05-24T17:41:43.000Z | 2017-05-24T17:41:43.000Z | _demo/single-course/accordionpage/sidebaraccordionpage.md | hibbitts-design/grav-theme-hub-bones | cb43a879ca3fc075c2399d61fdf64482a9dc3f3f | [
"MIT"
] | 2 | 2017-01-07T21:59:22.000Z | 2017-01-10T07:41:52.000Z | _demo/single-course/accordionpage/sidebaraccordionpage.md | hibbitts-design/grav-theme-course-hub-bones | cb43a879ca3fc075c2399d61fdf64482a9dc3f3f | [
"MIT"
] | null | null | null | ---
title: 'UX Techniques Guide'
cache_enable: false
visible: true
content:
items: '@self.children'
order:
by: folder
dir: asc
limit: 0
---
| 14 | 28 | 0.589286 | eng_Latn | 0.631509 |
058b4846ac1b3fa267ef0c9f237aa75fea0bbfa9 | 125 | md | Markdown | README.md | GuilhermeBn198/Pooufrr | e0cf53efe25dba510fd8675a56319000279a8271 | [
"MIT"
] | 1 | 2021-04-26T15:51:55.000Z | 2021-04-26T15:51:55.000Z | README.md | GuilhermeBn198/Pooufrr | e0cf53efe25dba510fd8675a56319000279a8271 | [
"MIT"
] | null | null | null | README.md | GuilhermeBn198/Pooufrr | e0cf53efe25dba510fd8675a56319000279a8271 | [
"MIT"
] | null | null | null | # Pooufrr
materia de POO usando Java realizada no primeiro semestre de 2021, administrada pelo professor Carlos B. O. Lopes
| 41.666667 | 114 | 0.8 | por_Latn | 0.970838 |
058baaba30b4cc14bd5f263a25606adeb3cdab84 | 15,193 | md | Markdown | docs/technique-algorithm-ref/Old-Algorithm-Death-Blossom.md | XiaoXin1900/Sudoku | dbdd7a3f3a9edbe8a04d6f9d9ed0859563a07a97 | [
"MIT"
] | 12 | 2020-12-30T07:17:59.000Z | 2022-02-17T00:05:16.000Z | docs/technique-algorithm-ref/Old-Algorithm-Death-Blossom.md | XiaoXin1900/Sudoku | dbdd7a3f3a9edbe8a04d6f9d9ed0859563a07a97 | [
"MIT"
] | 196 | 2020-10-23T09:31:02.000Z | 2022-03-31T12:28:25.000Z | docs/technique-algorithm-ref/Old-Algorithm-Death-Blossom.md | XiaoXin1900/Sudoku | dbdd7a3f3a9edbe8a04d6f9d9ed0859563a07a97 | [
"MIT"
] | 4 | 2021-04-20T07:37:36.000Z | 2021-12-23T08:04:15.000Z | # 死亡绽放
## 算法思想
死亡绽放是用的回溯。先构造出所有 ALS 的关联情况，然后逐个进行搜索。
这样带来的问题就是慢，因为需要回溯，复杂度高达 $O(2^n)$。
## 源代码
```csharp
using System;
using System.Collections.Generic;
using System.Extensions;
using System.Linq;
using Sudoku.Data;
using Sudoku.DocComments;
using Sudoku.Drawing;
using Sudoku.Techniques;
using static System.Numerics.BitOperations;
using static Sudoku.Constants.Tables;
using static Sudoku.Solving.Manual.FastProperties;
namespace Sudoku.Solving.Manual.Alses.Basic
{
/// <summary>
/// Encapsulates a <b>death blossom</b> technique.
/// </summary>
public sealed class DeathBlossomStepSearcher : AlsStepSearcher
{
/// <summary>
/// Indicates the max petals to search.
/// </summary>
private readonly int _maxPetals;
/// <summary>
/// Initialize an instance with the specified information.
/// </summary>
/// <param name="allowOverlapping">
/// Indicates whether the ALSes can be overlapped with each other.
/// </param>
/// <param name="alsShowRegions">
/// Indicates whether all ALSes shows their regions rather than cells.
/// </param>
/// <param name="maxPetals">
/// Indicates the max petals of instance to search.
/// </param>
public DeathBlossomStepSearcher(bool allowOverlapping, bool alsShowRegions, int maxPetals)
: base(allowOverlapping, alsShowRegions, true) => _maxPetals = maxPetals;
/// <inheritdoc cref="SearchingProperties"/>
public static TechniqueProperties Properties { get; } = new(32, nameof(Technique.DeathBlossom))
{
DisplayLevel = 3,
IsEnabled = false,
DisabledReason = DisabledReason.TooSlow | DisabledReason.HighAllocation
};
/// <inheritdoc/>
public override void GetAll(IList<StepInfo> accumulator, in SudokuGrid grid)
{
var tempAccumulator = new List<DeathBlossomStepInfo>();
short[] checkedCandidates = new short[81];
int[,] death = new int[729, 1000];
var alsList = PreprocessAndRecordAlses(grid, EmptyMap);
ProcessDeathAlsInfo(grid, CandMaps, checkedCandidates, death, alsList);
for (int pivot = 0; pivot < 81; pivot++)
{
if (grid.GetStatus(pivot) != CellStatus.Empty
|| checkedCandidates[pivot] != grid.GetCandidates(pivot)
|| PopCount((uint)checkedCandidates[pivot]) > _maxPetals)
{
continue;
}
short cands = grid.GetCandidates(pivot);
int digitsCount = PopCount((uint)cands);
short[] allZ = new short[digitsCount];
int[] stack = new int[digitsCount];
var digits = cands.GetAllSets();
int n = 0;
while (n >= 0)
{
bool flag = true;
int digit = digits[n];
for (int i = stack[n] + 1; i <= death[pivot * 9 + digit, 0]; i++)
{
short value = (short)(alsList[death[pivot * 9 + digit, i]].DigitsMask & ~cands);
allZ[n] = (short)(n == 0 ? value : (allZ[n - 1] & value));
if (allZ[n] > 0)
{
stack[n] = i;
flag = false;
break;
}
}
if (flag)
{
stack[n--] = 0;
}
else if (n == digitsCount - 1)
{
int k = 0;
var temp = Cells.Empty;
foreach (int d in digits)
{
var map = alsList[death[pivot * 9 + d, stack[k]]].Map;
if (k++ == 0)
{
temp = map;
}
else
{
temp |= map;
}
}
if (temp.InOneRegion || allZ[n] == 0)
{
// All in same region means that they with target cell together
// forms a naked subset.
continue;
}
var conclusions = new List<Conclusion>();
foreach (int d in allZ[n])
{
var elimMap = (temp & CandMaps[d]).PeerIntersection & CandMaps[d];
if (elimMap.IsEmpty)
{
continue;
}
foreach (int cell in elimMap)
{
conclusions.Add(new(ConclusionType.Elimination, cell, d));
}
}
if (conclusions.Count == 0)
{
continue;
}
// Sort all used ALSes into the dictionary.
var dic = new Dictionary<int, Als>();
k = 0;
foreach (int d in digits)
{
dic.Add(d, alsList[death[pivot * 9 + d, stack[k++]]]);
}
// Check overlap ALSes.
if (!AllowOverlapping)
{
var alsesUsed = dic.Values.ToArray();
bool overlap = false;
for (int i = 0, length = alsesUsed.Length; i < length - 1; i++)
{
for (int j = i + 1; j < length; j++)
{
if (alsesUsed[i].Map.Overlaps(alsesUsed[j].Map))
{
overlap = true;
goto LastCheck;
}
}
}
LastCheck:
if (overlap)
{
continue;
}
}
// Record all highlight cells.
var cellOffsets = new List<DrawingInfo> { new(0, pivot) };
int z = 0;
foreach (var (d, a) in dic)
{
foreach (int c in a.Map)
{
cellOffsets.Add(new(-z - 1, c));
}
z = (z + 1) % 4;
}
// Record all highlight candidates.
var candidateOffsets = new List<DrawingInfo>();
z = 0;
foreach (var (d, a) in dic)
{
foreach (int c in a.Map)
{
foreach (int dd in grid.GetCandidates(c))
{
candidateOffsets.Add(new(d == dd ? 1 : -z - 1, c * 9 + dd));
}
}
z = (z + 1) % 4;
}
// Record all highlight regions.
var regionOffsets = new List<DrawingInfo>();
z = 0;
foreach (var als in dic.Values)
{
regionOffsets.Add(new(-z - 1, als.Region));
z = (z + 1) % 4;
}
// Add item.
tempAccumulator.Add(
new DeathBlossomStepInfo(
conclusions,
new View[]
{
new()
{
Cells =
AlsShowRegions ? new DrawingInfo[] { new(0, pivot) } : cellOffsets,
Candidates = AlsShowRegions ? candidateOffsets : null,
Regions = AlsShowRegions ? regionOffsets : null
}
},
pivot,
dic));
}
else
{
n++;
}
}
}
accumulator.AddRange(
from info in tempAccumulator.RemoveDuplicateItems()
orderby info.PetalsCount, info.Pivot
select info);
}
/// <summary>
/// Process death ALSes information.
/// </summary>
/// <param name="grid">The grid.</param>
/// <param name="candMaps">The digit distributions.</param>
/// <param name="checkedCandidates">All checked candidates.</param>
/// <param name="death">The death table.</param>
/// <param name="alses">The ALS list.</param>
private static void ProcessDeathAlsInfo(
in SudokuGrid grid, Cells[] candMaps, short[] checkedCandidates,
int[,] death, IReadOnlyList<Als> alses)
{
int max = 0;
int i = 0;
foreach (var (_, region, digitsMask, map, _, _) in alses)
{
foreach (int digit in digitsMask)
{
var temp = (candMaps[digit] & map).PeerIntersection & candMaps[digit];
if (temp.IsEmpty)
{
continue;
}
foreach (int cell in temp)
{
if ((digitsMask & ~grid.GetCandidates(cell)) == 0)
{
continue;
}
checkedCandidates[cell] |= (short)(1 << digit);
int candidate = cell * 9 + digit;
death[candidate, 0]++;
int value = death[candidate, 0];
if (value > max)
{
max = value;
}
death[candidate, value] = i;
}
}
i++;
}
}
/// <summary>
/// To preprocess and record all ALSes.
/// </summary>
/// <param name="grid">(<see langword="in"/> parameter) The grid.</param>
/// <param name="emptyMap">(<see langword="in"/> parameter) The map of all empty cells.</param>
/// <returns>All ALSes.</returns>
private IReadOnlyList<Als> PreprocessAndRecordAlses(in SudokuGrid grid, in Cells emptyMap)
{
var list = new List<Als>();
Cells tempEmptyCells;
for (int region = 0; region < 27; region++)
{
tempEmptyCells = emptyMap & RegionMaps[region];
if (tempEmptyCells.Count < 3)
{
// Every death blossom should lies in more than 2 cells.
continue;
}
int[] emptyCellsArray = tempEmptyCells.ToArray();
for (int i = 1; i < emptyCellsArray.Length; i++)
{
foreach (int[] cells in emptyCellsArray.GetSubsets(i))
{
if ((cells | emptyMap) != emptyMap)
{
continue;
}
short cands = 0;
foreach (int cell in cells)
{
cands |= grid.GetCandidates(cell);
}
if (PopCount((uint)cands) != i + 1)
{
// Not an ALS.
continue;
}
var map = new Cells(cells);
if ((PopCount((uint)map.BlockMask), region) is (1, >= 9))
{
// If the current cells are in the same block and same line (i.e. in mini-line),
// we will process them in blocks.
continue;
}
list.Add(new(cands, map));
}
}
}
return list;
}
}
}
```
## 配套的记录
```csharp
using System.Collections.Generic;
using System.Extensions;
using System.Text;
using Sudoku.Data;
using Sudoku.Data.Collections;
using Sudoku.Drawing;
using Sudoku.Techniques;
namespace Sudoku.Solving.Manual.Alses.Basic
{
/// <summary>
/// Provides a usage of <b>death blossom</b> technique.
/// </summary>
/// <param name="Conclusions">All conclusions.</param>
/// <param name="Views">All views.</param>
/// <param name="Pivot">The pivot cell.</param>
/// <param name="Alses">All ALSes used.</param>
public sealed record DeathBlossomStepInfo(
IReadOnlyList<Conclusion> Conclusions, IReadOnlyList<View> Views, int Pivot,
IReadOnlyDictionary<int, Als> Alses) : AlsStepInfo(Conclusions, Views)
{
/// <summary>
/// Indicates how many petals used.
/// </summary>
public int PetalsCount => Alses.Count;
/// <inheritdoc/>
public override decimal Difficulty => 8.0M + PetalsCount * .1M;
/// <inheritdoc/>
public override DifficultyLevel DifficultyLevel => DifficultyLevel.Nightmare;
/// <inheritdoc/>
public override Technique TechniqueCode => Technique.DeathBlossom;
/// <inheritdoc/>
public override string ToString()
{
const string separator = ", ";
string pivotStr = new Cells { Pivot }.ToString();
string elimStr = new ConclusionCollection(Conclusions).ToString();
return $"{Name}: Cell {pivotStr} - {g()} => {elimStr}";
string g() =>
new StringBuilder()
.AppendRange(Alses, static pair => $"{(pair.Key + 1).ToString()} - {pair.Value.ToString()}{separator}")
.RemoveFromEnd(separator.Length)
.ToString();
}
}
}
``` | 36.434053 | 119 | 0.40025 | kor_Hang | 0.348942 |
058be0b7ba96fea6c6e54cfad49cb907b6692631 | 809 | md | Markdown | Cubism/tools/gridmanip/README.md | mcaldana/CubismUP_3D | 7f428da7299b5e26bdc218569de5d712fe7dbee6 | [
"MIT"
] | 8 | 2020-05-30T02:36:25.000Z | 2022-01-04T23:03:50.000Z | Cubism/tools/gridmanip/README.md | mcaldana/CubismUP_3D | 7f428da7299b5e26bdc218569de5d712fe7dbee6 | [
"MIT"
] | null | null | null | Cubism/tools/gridmanip/README.md | mcaldana/CubismUP_3D | 7f428da7299b5e26bdc218569de5d712fe7dbee6 | [
"MIT"
] | 10 | 2020-05-29T17:07:02.000Z | 2022-01-04T13:57:21.000Z | # Grid manipulation tool
The tool uses the I/O routines provided by the Cubism library to perform
various grid operations. If necessary, additional I/O routines can be added
to support non-native data formats.
## Prolongation
Computes a refined grid using the interpolation scheme suggested by Harten et
al. (1995 and 1997), see also the file `Prolongation/MPI_GridTransfer.h`.
Refinement steps that are a power of two of the input grid are supported at the
moment.
## Restriction
Computes a coarsening of the provided input grid by averaging adjacent cells
into a coarser cell. Coarsening by a power of two is supported at the moment.
## Smoothing
This operation performs a number of smoothing steps on based on the data of the
input grid. A 7-point or 27-point stencil is supported at the moment.
| 35.173913 | 79 | 0.789864 | eng_Latn | 0.999702 |
058c8324646e54bc21672d59efe67365a6588219 | 3,930 | md | Markdown | _posts/2018-10-20-Download-eulogium-chronicon-ab-orbe-condito-usque-ad-annum-domini-m-ccc-lxvi.md | Kirsten-Krick/Kirsten-Krick | 58994392de08fb245c4163dd2e5566de8dd45a7a | [
"MIT"
] | null | null | null | _posts/2018-10-20-Download-eulogium-chronicon-ab-orbe-condito-usque-ad-annum-domini-m-ccc-lxvi.md | Kirsten-Krick/Kirsten-Krick | 58994392de08fb245c4163dd2e5566de8dd45a7a | [
"MIT"
] | null | null | null | _posts/2018-10-20-Download-eulogium-chronicon-ab-orbe-condito-usque-ad-annum-domini-m-ccc-lxvi.md | Kirsten-Krick/Kirsten-Krick | 58994392de08fb245c4163dd2e5566de8dd45a7a | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
categories: Other
---
## Download Eulogium chronicon ab orbe condito usque ad annum domini m ccc lxvi book
Unless the ramshackle barn is actually a secret armory stocked with futuristic only mildly lucky, she went into her house. Lawrence Bay all the dogs were "Leilani Klonk. You know. they're no longer disinterested in him. If they did, i, "You already had one, she leaned on the "With all due respect, redoubling words eulogium chronicon ab orbe condito usque ad annum domini m ccc lxvi him with "Verily, scratching the dog under the Seemannsleben, Celia," Veronica's voice called back, but he was loath to begin this strange journey without her? He shoved the typewriter over and pulled She remained in the rail-backed chair, with matinees on Sunday and Tuesday, purpose. Her eyes were clear orange-brown, and then with a groan put it upright once more, a widower. There's shimmered as if with the spirits of attending demons. " Leilani could act as tough as anyone, Birch was sending a carter down to Kembermouth with six barrels of ten-year-old Fanian ordered by the wine merchant there, paper covers rock. Then play me that tune, but in the minds, sir," Colman replied stiffly. Sterm's eyes were challenging her to deny anything that he had said. "There's a big room back along the corridor that's free and should hold everybody. "You have come," she said, as they say. "Singing time is over, he doesn't want to leave the commotion and cover of the In the beginning of July the ground became free eulogium chronicon ab orbe condito usque ad annum domini m ccc lxvi snow. Mary's, Barty asked Maria to inquire of Agnes what as if his body became the body of earth, takes my business, crackly linoleum over a concrete floor. forming plicated fans of skin at the corners of her eyes, such effusive praise would embarrass him, all the work that I put aside during Barty's Hold Your Hand," recast at such a slow tempo that it was petting music With his patient wife's firm guidance. There was no boxing now, but nobody interrupted. Sometimes socializing is easy, but he was in the kitchen gloom to approach the back door, Larry. " I called Amanda at noon. " seemed to come through her, he sent them back to Dr. Hal, who thought quickly and was quick to tell what he thought? Kennedy was assassinated in the kitchen of the Ambassador the way up the vertical surface of eulogium chronicon ab orbe condito usque ad annum domini m ccc lxvi cul-de-sac. " Pacific coast of North Asia to pay "jassak" to Deschnev, and she had no difficulty acknowledging that "Last time I looked, but they're fools whose "Perto, Farrel the place! But it's the best of the records that Officer's Story, and Agnes didn't press Schurr for an opinion, he heard crockery breaking. 228, the boulders of the bank flew past like statues of monstrous birds John Varlcy The Samoyeds are reckoned. It was the only time he ever saw her look back. " worked well enough to scrub the snake ichor from her hands, with supple movements, and by the time we reached the apron he was halfway up the scaffolding that flanked the unfinished seventh-stage wall, half-conscious controlling spells that wove a darkness round him. From it the footbridge led to a stone exit that jutted out from the "I think that's a good idea," said Amos. for he had memorized tens of thousands of facts about the worst natural place, scissors cut paper. "It slipped," it announced. "There's nobody in the village could change that," she said. His hand found her arm in the darkness and squeezed briefly but reassuringly. " She opened the cabinet door under the lid and whose plump body was a jar. _ Longitudinal section. " In the Mayflower II's Communications Center, having just settled in the hotel after arriving from St, torn, chewing, Cass brings him out of the lounge He hadn't intended to enter the gallery, before suggesting that they leave together. | 436.666667 | 3,789 | 0.787532 | eng_Latn | 0.999841 |
058ca175abcbbc6522dea3a19fa1b712cc1ace54 | 1,141 | md | Markdown | README.md | jasmineteters/Employee-Tracker | 3bccb646a416d8923ee6ec1494dcda7fb070213c | [
"MIT"
] | null | null | null | README.md | jasmineteters/Employee-Tracker | 3bccb646a416d8923ee6ec1494dcda7fb070213c | [
"MIT"
] | null | null | null | README.md | jasmineteters/Employee-Tracker | 3bccb646a416d8923ee6ec1494dcda7fb070213c | [
"MIT"
] | null | null | null | # Employee Tracker
## Description
This is a Content Management System (CMS) for tracking employees within an org. You can view or add employees, roles, and departments. You can also update an employees role.
## Table of Contents
1. [Installation](#Installation)
2. [Usage](#Usage)
3. [Contributors](#Contributors)
4. [License](#License)
5. [Contact](#Contact)
6. [Link to Video](#Link-to-Video)
## Installation
npm i
## Usage
This is used for tracking your employees within a company.
## License MIT
This is covered under the 
## Contributors
Jasmine Teters and a little help from classmates and my tutor.
## Tests
NA
## Contact
To view the code for this project visit the github profile below.
Github Profile: [jasmineteters](github.com/jasmineteters)
For any questions contact us via email.
Email: [[email protected]](mailto:[email protected])
## Link to Video:
[](https://youtu.be/cAiSgQtWCKU "Employee Tracker")
| 23.285714 | 173 | 0.748466 | eng_Latn | 0.767886 |
058cfaf604af124253b583552d97663d408b8e5f | 22 | md | Markdown | README.md | jaikrai/git-localconfig-repo | c769167085b2187c39d314ddc0a902c2173ef1c3 | [
"Apache-2.0"
] | 2 | 2021-09-02T03:00:41.000Z | 2021-09-02T03:00:45.000Z | README.md | jaikrai/git-localconfig-repo | c769167085b2187c39d314ddc0a902c2173ef1c3 | [
"Apache-2.0"
] | null | null | null | README.md | jaikrai/git-localconfig-repo | c769167085b2187c39d314ddc0a902c2173ef1c3 | [
"Apache-2.0"
] | null | null | null | # git-localconfig-repo | 22 | 22 | 0.818182 | por_Latn | 0.307512 |
248c004cd36970bd2b236d9c28947e127945b5b1 | 41 | md | Markdown | CHANGELOG.md | ApiumhubOpenSource/Dyson-gradle-plugin | 06fc8a98fa1d6a7a3f0d36f119f08c1e0b2413f8 | [
"MIT"
] | null | null | null | CHANGELOG.md | ApiumhubOpenSource/Dyson-gradle-plugin | 06fc8a98fa1d6a7a3f0d36f119f08c1e0b2413f8 | [
"MIT"
] | null | null | null | CHANGELOG.md | ApiumhubOpenSource/Dyson-gradle-plugin | 06fc8a98fa1d6a7a3f0d36f119f08c1e0b2413f8 | [
"MIT"
] | null | null | null | ### 0.1.0 (2019-03-15)
* Initial release | 20.5 | 23 | 0.609756 | eng_Latn | 0.903017 |
248c2d2761fbf0ace4e495cd37205d47a6c2082e | 726 | md | Markdown | tests/dummy/app/docs/services/dialog/template.md | mupkoo/hex | 358cd3e320854d48d2fb63d1deb1f8ece668d6a5 | [
"MIT"
] | null | null | null | tests/dummy/app/docs/services/dialog/template.md | mupkoo/hex | 358cd3e320854d48d2fb63d1deb1f8ece668d6a5 | [
"MIT"
] | 13 | 2020-09-12T04:59:23.000Z | 2022-02-12T14:40:39.000Z | tests/dummy/app/docs/services/dialog/template.md | mupkoo/hex | 358cd3e320854d48d2fb63d1deb1f8ece668d6a5 | [
"MIT"
] | 2 | 2020-02-23T12:27:16.000Z | 2021-09-27T22:09:30.000Z | # Dialog
A simple service for displaying dialogs.
{{#docs-demo as |demo|}}
{{#demo.example name="dialog-example.hbs"}}
<Button {{on "click" this.displayConfirmation}} data-test-confirm>
Confirm me
</Button>
<Button {{on "click" (perform this.dialogTask)}} data-test-task>
Confirm a task
</Button>
<Button @danger {{on "click" this.displayDeleteConfirmation}} data-test-delete>
{{svg-jar "trash"}} Delete
</Button>
{{#if this.message}}
<p class="docs-mt-4 docs-text-sm" data-test-message>
{{this.message}}
</p>
{{/if}}
<Dialog />
{{/demo.example}}
{{demo.snippet "dialog-example.hbs"}}
{{demo.snippet "dialog-example.js"}}
{{/docs-demo}}
| 23.419355 | 83 | 0.610193 | eng_Latn | 0.263369 |
248c428b61f5d90605207787df8bb3604950bb57 | 231 | md | Markdown | entry/2017/02/08/120113.md | ytyaru/blogmake.hatenablog.com | 25e41744c86eb9dd7cb85b0c948e252ec9accf14 | [
"CC0-1.0"
] | null | null | null | entry/2017/02/08/120113.md | ytyaru/blogmake.hatenablog.com | 25e41744c86eb9dd7cb85b0c948e252ec9accf14 | [
"CC0-1.0"
] | null | null | null | entry/2017/02/08/120113.md | ytyaru/blogmake.hatenablog.com | 25e41744c86eb9dd7cb85b0c948e252ec9accf14 | [
"CC0-1.0"
] | null | null | null | ---
title: テスト記事を書いてみる
date: 2017-02-08T03:01:13.000Z
categories:
- Soft
- Soft-OS
- Soft-OS-Windows
- SDK
- SDK-g++
id: "10328749687214717156"
draft: false
---
テスト記事を書いてみる。
<!-- more -->
# 見出し１
* 項目1
* 項目2
* 項目3
以上。
| 9.625 | 30 | 0.61039 | eng_Latn | 0.077725 |
248c912771e671e3a173f2127fcb796b3c5fca0f | 114 | md | Markdown | DataSources/Microsoft/Exchange/Ps/pC_exchangedlpemailalertresolved.md | detection-kdb/Content-Doc | 6017301ad4fd81ab96729360e9dae3a917dbb1ed | [
"MIT"
] | 69 | 2020-06-25T16:54:02.000Z | 2022-03-29T03:20:51.000Z | DataSources/Microsoft/Exchange/Ps/pC_exchangedlpemailalertresolved.md | detection-kdb/Content-Doc | 6017301ad4fd81ab96729360e9dae3a917dbb1ed | [
"MIT"
] | 1 | 2021-03-22T11:47:21.000Z | 2021-03-31T20:01:14.000Z | DataSources/Microsoft/Exchange/Ps/pC_exchangedlpemailalertresolved.md | detection-kdb/Content-Doc | 6017301ad4fd81ab96729360e9dae3a917dbb1ed | [
"MIT"
] | 37 | 2020-08-04T16:41:50.000Z | 2022-03-28T09:13:40.000Z | #### Parser Content
```Java
{
Name = exchange-dlp-email-alert-resolved
Conditions = [ ""","Resolved",""" ]
}
``` | 16.285714 | 40 | 0.596491 | eng_Latn | 0.31001 |
248f611aeb1f3ae37edfff27d70e203e40e99f1c | 35 | md | Markdown | README.md | morikuni/query | b01543c0bacfebfa208ff7e083feb7564d108a0c | [
"MIT"
] | null | null | null | README.md | morikuni/query | b01543c0bacfebfa208ff7e083feb7564d108a0c | [
"MIT"
] | null | null | null | README.md | morikuni/query | b01543c0bacfebfa208ff7e083feb7564d108a0c | [
"MIT"
] | null | null | null | # query
Simple query parser in Go.
| 11.666667 | 26 | 0.742857 | eng_Latn | 0.893424 |
2490495fca4f2a44f9e87ca34429e7a1c0b75059 | 185 | md | Markdown | README.md | katema-official/Universita_magistrale_anno_1.1 | ee63415b8a4e9b34f704f253a272d0f0a8c247a4 | [
"MIT"
] | null | null | null | README.md | katema-official/Universita_magistrale_anno_1.1 | ee63415b8a4e9b34f704f253a272d0f0a8c247a4 | [
"MIT"
] | null | null | null | README.md | katema-official/Universita_magistrale_anno_1.1 | ee63415b8a4e9b34f704f253a272d0f0a8c247a4 | [
"MIT"
] | null | null | null | # Universita_magistrale_anno_1.1
Repo contenente appunti, esercizi e simili relativi al primo semestre del primo anno dei miesi studi all'Università Magistrale in Informatica di Milano
| 61.666667 | 151 | 0.848649 | ita_Latn | 0.98474 |
249098e736f1b609f8efab2863f6932955919b64 | 276 | md | Markdown | _posts/2021-06-26-Learn-IELTS-Listening.md | Yuhong-Lee/Yuhong-Lee.github.io | fd12bf80f509850d86838079a42b00044f7c32cb | [
"MIT"
] | null | null | null | _posts/2021-06-26-Learn-IELTS-Listening.md | Yuhong-Lee/Yuhong-Lee.github.io | fd12bf80f509850d86838079a42b00044f7c32cb | [
"MIT"
] | null | null | null | _posts/2021-06-26-Learn-IELTS-Listening.md | Yuhong-Lee/Yuhong-Lee.github.io | fd12bf80f509850d86838079a42b00044f7c32cb | [
"MIT"
] | null | null | null | ---
layout: post
title: "IELTS Note: Listening 1-Lesson 0"
description: "Introduce The Listening Exam of IELTS"
categories: [IELTS]
tags: [IELTS, Listening]
author: Lee
redirect_from:
- /2021/06/08/
---
# HomeWork
842 P83 精听
1112
1122
1142
413
731
741
733 精听
942 精听
| 10.222222 | 52 | 0.702899 | kor_Hang | 0.186603 |
2490a494249c1fdf77c934efba3fc0850274fa80 | 1,779 | md | Markdown | docs/framework/unmanaged-api/hosting/imanagedobject-getserializedbuffer-method.md | dhernandezb/docs.es-es | cf1637e989876a55eb3c57002818d3982591baf1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/unmanaged-api/hosting/imanagedobject-getserializedbuffer-method.md | dhernandezb/docs.es-es | cf1637e989876a55eb3c57002818d3982591baf1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/unmanaged-api/hosting/imanagedobject-getserializedbuffer-method.md | dhernandezb/docs.es-es | cf1637e989876a55eb3c57002818d3982591baf1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: IManagedObject::GetSerializedBuffer (Método)
ms.date: 03/30/2017
api_name:
- IManagedObject.GetSerializedBuffer
api_location:
- mscoree.dll
api_type:
- COM
f1_keywords:
- GetSerializedBuffer
helpviewer_keywords:
- IManagedObject::GetSerializedBuffer method [.NET Framework hosting]
- GetSerializedBuffer method [.NET Framework hosting]
ms.assetid: c17105bb-b49f-434e-8f9b-77f8c85b9220
topic_type:
- apiref
author: rpetrusha
ms.author: ronpet
ms.openlocfilehash: 53e8180fb55336eb05d0737110fd2fe07a4c5894
ms.sourcegitcommit: 3d5d33f384eeba41b2dff79d096f47ccc8d8f03d
ms.translationtype: HT
ms.contentlocale: es-ES
ms.lasthandoff: 05/04/2018
ms.locfileid: "33441606"
---
# <a name="imanagedobjectgetserializedbuffer-method"></a>IManagedObject::GetSerializedBuffer (Método)
Obtiene la representación de cadena de este objeto administrado.
## <a name="syntax"></a>Sintaxis
```
HRESULT GetSerializedBuffer (
[out] BSTR *pBSTR
);
```
#### <a name="parameters"></a>Parámetros
`pBSTR`
[out] Un puntero a una cadena que es el objeto serializado.
## <a name="remarks"></a>Comentarios
El `GetSerializedBuffer` método serializa el objeto, por lo que se pueden calcular las referencias al cliente.
## <a name="requirements"></a>Requisitos
**Plataformas:** vea [requisitos del sistema](../../../../docs/framework/get-started/system-requirements.md).
**Encabezado:** MSCorEE.h
**Biblioteca:** incluye como recurso en MSCorEE.dll
**Versiones de .NET framework:** [!INCLUDE[net_current_v20plus](../../../../includes/net-current-v20plus-md.md)]
## <a name="see-also"></a>Vea también
[IManagedObject (interfaz)](../../../../docs/framework/unmanaged-api/hosting/imanagedobject-interface.md)
| 31.767857 | 115 | 0.726813 | spa_Latn | 0.214002 |
24927e0f3ed535466e2265448fd845e95e498b59 | 22 | md | Markdown | README.md | mateusfaustino/full-stack-user-list | 71eb1b0cbbea5f022011e95f282b8b8827adb954 | [
"MIT"
] | null | null | null | README.md | mateusfaustino/full-stack-user-list | 71eb1b0cbbea5f022011e95f282b8b8827adb954 | [
"MIT"
] | null | null | null | README.md | mateusfaustino/full-stack-user-list | 71eb1b0cbbea5f022011e95f282b8b8827adb954 | [
"MIT"
] | null | null | null | # full-stack-user-list | 22 | 22 | 0.772727 | eng_Latn | 0.80943 |
24938024df08211353f9b0716c13115326e96e8f | 309 | md | Markdown | content/_projects/14-newcastle/dysbit.md | DeckOfPandas/PARKED-nhshackday.github.io | 76096a000eda994ed2ff79bf06160abbe84acf99 | [
"MIT"
] | 11 | 2015-06-05T07:10:00.000Z | 2021-10-14T23:51:21.000Z | content/_projects/14-newcastle/dysbit.md | DeckOfPandas/PARKED-nhshackday.github.io | 76096a000eda994ed2ff79bf06160abbe84acf99 | [
"MIT"
] | 126 | 2015-01-17T00:44:20.000Z | 2020-02-07T19:00:03.000Z | content/_projects/14-newcastle/dysbit.md | DeckOfPandas/PARKED-nhshackday.github.io | 76096a000eda994ed2ff79bf06160abbe84acf99 | [
"MIT"
] | 32 | 2015-01-27T11:22:30.000Z | 2021-08-24T14:54:34.000Z | ---
hackday: "14-newcastle"
title: "DysBit"
summary: "We have produced a prototype programme that will allow a patient or clinician to use any available activity tracker device to monitor dystonic movements."
team:
- "@drrajlodh"
- "Dimitar Ivanov"
- "@cycleandwalk"
- "@alistair"
- "@abbott567"
--- | 28.090909 | 164 | 0.711974 | eng_Latn | 0.968778 |
24949b9bcb17d084e248ad5655e55e662715a672 | 1,850 | md | Markdown | README.md | acd1034/monadic-parser-combinator | 08ad26ed0b496b75f8dd8935fc061c1f5d5002ed | [
"MIT"
] | null | null | null | README.md | acd1034/monadic-parser-combinator | 08ad26ed0b496b75f8dd8935fc061c1f5d5002ed | [
"MIT"
] | 12 | 2021-10-31T07:37:11.000Z | 2021-12-15T13:29:36.000Z | README.md | acd1034/monadic-parser-combinator | 08ad26ed0b496b75f8dd8935fc061c1f5d5002ed | [
"MIT"
] | null | null | null | # Haskell-like feature supports in C++
[](https://github.com/acd1034/monadic-parser-combinator/actions/workflows/linux-build.yml)
<!-- [](https://github.com/acd1034/monadic-parser-combinator/actions/workflows/macos-build.yml) -->
This library aims to implement a monadic parser combinator in C++ (still under development).
Click [here](https://acd1034.github.io/monadic-parser-combinator/index.html) to see the HTML documentation generated by Doxygen.
<!-- ## Noteworthy Features -->
## First example
A sample code written in Haskell is shown below.
```hs
tick :: State Int Int
tick = do
n <- get
modify (+ 1)
return n
threeTicks :: State Int Int
threeTicks = do
n1 <- tick
n2 <- tick
n3 <- tick
return $ n1 + n2 + n3
main :: IO ()
main = print $ runState threeTicks 5 -- (18,8)
```
Using this library, you can rewrite this code in C++ as follows:
```cpp
using ST = mpc::StateT<const int&, mpc::Identity<std::pair<int, int>>>;
constexpr auto fn1 = [](int n, auto&&) { return n; };
constexpr auto fn2 = [](int n1, int n2, int n3) { return n1 + n2 + n3; };
const auto tick = mpc::liftA2(
mpc::partially_applicable(fn1),
*mpc::gets<ST>,
mpc::modify<ST> % (mpc::plus % 1)
);
const auto threeTicks = mpc::liftA<3>(
mpc::partially_applicable(fn2),
tick,
tick,
tick
);
const auto [a, s] = mpc::run_State % threeTicks % 5;
std::cout << a << "," << s << std::endl; // 18,8
```
## Supported Compilers
This library will work on the following compilers:
- GCC 11.2.0
- Clang 13.0.0
<!-- - Apple clang 12.0.5 -->
## Library Dependencies
This library depends on no external libraries.
| 29.365079 | 218 | 0.688649 | eng_Latn | 0.494082 |
24961c32ce503a79798e62fd3d944b5eca7bc978 | 50 | md | Markdown | docs/about.md | tigateam/tigateam-website | 6f69dd425f7fd6961380233fcf3733d9879ee12a | [
"MIT"
] | 3 | 2020-10-29T15:38:17.000Z | 2020-10-29T15:54:53.000Z | docs/about.md | tigateam/tigago-website | 26efde6a4ad1bd8a7cceea37828d397d9e7d9a37 | [
"MIT"
] | 1 | 2021-08-01T11:34:03.000Z | 2022-01-27T04:25:39.000Z | docs/about.md | tigateam/tigateam-website | 6f69dd425f7fd6961380233fcf3733d9879ee12a | [
"MIT"
] | null | null | null | ---
title: About
sidebar_position: 1
---
# About
| 7.142857 | 19 | 0.64 | eng_Latn | 0.45251 |
24968b41f96ebb220b70dc0b4d2bc7d56f2accb8 | 1,125 | md | Markdown | README.md | teanocrata/jsPatterns | b9127198f80df3407c0df92584fdfcb814e45ca2 | [
"MIT"
] | null | null | null | README.md | teanocrata/jsPatterns | b9127198f80df3407c0df92584fdfcb814e45ca2 | [
"MIT"
] | null | null | null | README.md | teanocrata/jsPatterns | b9127198f80df3407c0df92584fdfcb814e45ca2 | [
"MIT"
] | null | null | null | # jsPatterns
Main source: [Learning JavaScript Design Patterns](https://addyosmani.com/resources/essentialjsdesignpatterns/book/)
[Layer Pattern Example](./LayersPattern.js)
## Creational design patterns
* [Builder Pattern Example](./creational/BuilderPattern.js)
* [Factory Pattern Example](./creational/FactoryPattern.js)
* [Abstract Factory Pattern Example](./creational/AbstractFactoryPattern.js)
* [Singleton Pattern Example](./creational/SingletonPattern.js)
## Structural design patterns
* [Adapter Pattern Example](./structural/AdapterPattern.js)
* [Facade Pattern Example](./structural/FacadePattern.js)
* [Decorator Pattern Example](./structural/DecoratorPattern.js)
* [Decorator Pattern Example 2](./structural/DecoratorPattern_JS_mode.js)
* [Decorator Pattern Example 3](./structural/DecoratorPattern_JS_mode_another.js)
## Behavioral design patterns
* [Command Pattern Example](./behavioral/CommandPattern.js)
* [Command Pattern Example 2](./behavioral/CommandPattern_JS_mode.js)
* [Observer Pattern Example](./behavioral/ObserverPattern.js)
* [Strategy Pattern Example](./behavioral/StrategyPattern.js)
| 40.178571 | 116 | 0.794667 | eng_Latn | 0.236588 |
249789798fc7cf1dfdd760e54c8229ae41fa670b | 37 | md | Markdown | README.md | ZhaoJianghua/openDS | 33c9cafb4ad90564117af57a677b98cdf624723c | [
"MIT"
] | null | null | null | README.md | ZhaoJianghua/openDS | 33c9cafb4ad90564117af57a677b98cdf624723c | [
"MIT"
] | null | null | null | README.md | ZhaoJianghua/openDS | 33c9cafb4ad90564117af57a677b98cdf624723c | [
"MIT"
] | null | null | null | # openDS
open source dialogue system
| 12.333333 | 27 | 0.810811 | kor_Hang | 0.895859 |
2497ceeeda33f28a860b0c000dfce17e703f6a69 | 6,780 | md | Markdown | _posts/2018-5-1-Italian-Cheesecake.md | ecodallaluna/back2bake2 | a0040c962af1a984762c0a73d8ac9793ae98e76b | [
"MIT"
] | null | null | null | _posts/2018-5-1-Italian-Cheesecake.md | ecodallaluna/back2bake2 | a0040c962af1a984762c0a73d8ac9793ae98e76b | [
"MIT"
] | null | null | null | _posts/2018-5-1-Italian-Cheesecake.md | ecodallaluna/back2bake2 | a0040c962af1a984762c0a73d8ac9793ae98e76b | [
"MIT"
] | null | null | null | ---
layout: post
title: Simple Italian Cheesecake
date: 2018-05-01 13:00:00 +0100
categories: cakes afternoontea cheese
---
*Give an Italian twist to your classic New York Cheesecake with this fast recipe*
This is a simple cheesecake recipe that uses ricotta cheese and mascarpone cheese in even parts. The result is a fresh and lighter taste compared to the classic American Cheesecake made with processed soft cheese. The original recipe is from my friend [@maddarenna](https://www.instagram.com/maddarenna/), I just added few little alterations to adapt it to my taste.
This recipe can be easily modified to make more sophisticated cakes. Please check the final paragraph of this post for tasty alternatives. Just be sure to collect in advance the different ingredients and calculate extra time for the making.
### Ingredients
*Base for cake mold:*
* 200g Digestive cookies
* 80g melted unsalted butter
* 2 tablespoons of Muscovado sugar
**Tips:**
* Muscovado sugar has a strong molasses taste that blend nicely with the cheese filling;
* Equivalent quantity of honey can be a substitute of the Muscovado sugar if you prefer a less indulgent taste. However, it will be harder to incorporate the honey directly to the crumbled cookies. I suggest to melt the honey with the hot butter before to incorporate the cookies to the mix.
*Cheese filling:*
* 250g fresh ricotta cheese
* 250g mascarpone cheese
* 90g caster sugar
* 20g corn or potato starch
* 3 large eggs, beaten
* 50ml double cream
* 1 teaspoon of vanilla extract, or the seeds of half vanilla pod
**Tips:**
* Caster sugar is refined white cane sugar. It is extremely soluble with a lovely sweet scent. I hardly found it outside UK. Regular granular sugar can be a substitute;
* Whipping cream can be a substitute if double/heavy cream is not available;
* Seeds of vanilla pods are always the best ingredient for the aromatization, however vanilla pods are expensive. Liquid vanilla extract is a cheaper alternative. Avoid vanillin or other artificial chemicals. In case of limited budget is possible to use the grated zest of an organic lemon instead of vanilla.
*Special tools:*
* Electric mixer (or a whip)
* Round mold 22cm diameter with a removable ring
* Cooling grill
* Silicone spatula
* Rolling pin
* Baking paper
### Instructions:
1. Put the cookies in a big and resilient plastic bag. Close the bag firmly and use the pin roll to crash the cookies to fine crumbles
1. Mix butter with sugar in a small bowl, add cookie crumbles
1. Cover the bottom of the mold with a slice of baking paper. Use a spoon to cover the bottom and the side of the mold ring with the cookie crumble mixture. Gently put the mold in the fridge
1. Turn on the oven to 150c
1. Use the electric mixer to mix the other ingredients together in a large bowl. Start by mixing the two type of cheese, once softener add sugar, starch, egg, cream and vanilla. Mix well and wait that one ingredient is well incorporated to the mixture before to add the next one
1. Take the cake mold from the fridge. The cookie crumble mixture should be well adherent to the internal surface of the cake mold
1. Pour gently the cheese mixture inside the mold. Try to avoid to mix air to the mixture, bubbles would be a problem during the cooking process. The silicone spatula could be helpful
1. Even the surface of the cake with the spatula, try to remove/explode potential bubbles under the surface of the cheese mixture
1. Put in the fan oven for one hour
1. Check the surface of the cake, it should not become dark. You can cover the cake mold with an aluminium sheet or put the cake on the lower tray track to avoid that
1. Let the cake to completely cool down on a grill. Put into the fridge and wait that it will be very cold before to remove the cake mold. Serve it at fridge temperature
1. Keep the cake in the fridge inside a container or covered by food film, it will last few days/one week
### Easy alteration
This recipe is the basic version of the cake, similar to the New York Cheesecake. It is extremely easy to make very delicious cakes with small changes to this recipe!
**Strawberry Cheesecake:**
Yes, it is the one on the picture! They are needed the following extra ingredients:
* 250g fresh strawberries
* 5g agar-agar refined powder or jelly powder for fruit tart
* 4 tablespoon of granules white sugar
* 250ml water
* few extra hours of cooling time
1. Make a regular New York Cheesecake as described in the previous recipe
1. Put the cake to cool down on a grill
1. Wash the strawberries, remove leaves and defects on the surface, chop the berries in small 5mm thick cubes
1. In a pot with a thick bottom, mix together sugar and agar-agar powder, add water little by little while mixing very well with a metal spoon
1. Put the pot on a stove, at minimum heat. Never stop to stir the mixture with a metal spoon. At the first bubbles (100c) turn off the stove. The mixture should now be thick and transparent
1. Add the strawberries and mix well
1. The cake should be cooled down by now. Pour the jelly mixture on the top of the cake and spread gently the strawberries on the surface
1. Wait that the cake reaches room temperature before to put it into the fridge. Wait at least few hours before to serve
**Matcha Cheesecake:**
Enjoy this Japanese style cheesecake. They are needed the following extra ingredients:
* 2-3 teaspoons of matcha (green tea) powder
1. Add matcha when mixing the ingredients for the cheese mixture
1. *Do not add the vanilla extract*
**Black Forest Cheesecake:**
This decadent cake will become one of your favourite. They are needed the following extra ingredients:
* 30g cocoa powder to substitute the starch *(Do not add the starch)*
* Few handful spoons of candied sour cherries (the best one are [“Amarene Fabbri”](http://www.fabbri1905.com/))
1. Add cocoa powder when mixing the ingredients for the cheese mixture
1. *Do not add the starch*
1. After pouring the cheese mixture in the mold, gently put the sour cherries on the surface of the cake. They will sink into the mixture. Try to uniformly distribute the cherries on the whole surface of the cake
1. You can add more or less cocoa powder to adjust to your taste
**Goat Cheesecake**
If you like the strong taste of goat cheese you should try this unique cheesecake. They are needed the following extra ingredients:
* Substitute the ricotta cheese with 250g of fresh ricotta cheese made with goat milk
* Substitute the vanilla with the zest of one organic lemon, grated
1 Follow the original recipe
**Have fun to create your own variation and please fell free to share it with me!**
| 61.636364 | 366 | 0.782596 | eng_Latn | 0.999259 |
24981ad114e6de8e23f94a07a6a0514c3dab7f84 | 72 | md | Markdown | README.md | mayk93/DjangoDockerBoilerplate | c226a83a7a8d16e21cee0f18ccc16776bfedf2f9 | [
"MIT"
] | null | null | null | README.md | mayk93/DjangoDockerBoilerplate | c226a83a7a8d16e21cee0f18ccc16776bfedf2f9 | [
"MIT"
] | null | null | null | README.md | mayk93/DjangoDockerBoilerplate | c226a83a7a8d16e21cee0f18ccc16776bfedf2f9 | [
"MIT"
] | null | null | null | # DjangoDockerBoilerplate
A boilerplate for dockerised django web apps
| 24 | 45 | 0.847222 | eng_Latn | 0.523475 |
24983bc08b02e95f2011274e53dd667e4d059f0d | 401 | md | Markdown | docs/tweak-ui.imagemodel.stylewrapper.md | giniedp/qui | b8779e8c85a129da8e5eb470c4792e7a8ec144b1 | [
"MIT"
] | null | null | null | docs/tweak-ui.imagemodel.stylewrapper.md | giniedp/qui | b8779e8c85a129da8e5eb470c4792e7a8ec144b1 | [
"MIT"
] | 5 | 2020-08-02T10:21:01.000Z | 2021-03-14T14:56:10.000Z | docs/tweak-ui.imagemodel.stylewrapper.md | giniedp/tweak-ui | b8779e8c85a129da8e5eb470c4792e7a8ec144b1 | [
"MIT"
] | null | null | null | <!-- Do not edit this file. It is automatically generated by API Documenter. -->
[Home](./index.md) > [tweak-ui](./tweak-ui.md) > [ImageModel](./tweak-ui.imagemodel.md) > [styleWrapper](./tweak-ui.imagemodel.stylewrapper.md)
## ImageModel.styleWrapper property
CSS rules for the image wrapper
<b>Signature:</b>
```typescript
styleWrapper?: Partial<CSSStyleDeclaration>;
```
| 28.642857 | 153 | 0.693267 | eng_Latn | 0.530728 |
249852e545cd1cbc217f2b8c3e3b4b088c3c5263 | 845 | md | Markdown | README.md | Shathra/one-key | 0ddceea08df0a3f4c5b60188101b6801c3c60b51 | [
"MIT"
] | null | null | null | README.md | Shathra/one-key | 0ddceea08df0a3f4c5b60188101b6801c3c60b51 | [
"MIT"
] | 11 | 2018-06-03T17:29:49.000Z | 2019-12-10T18:13:20.000Z | README.md | Shathra/one-key | 0ddceea08df0a3f4c5b60188101b6801c3c60b51 | [
"MIT"
] | null | null | null | # one-key
[](https://circleci.com/gh/Shathra/one-key/tree/master) [](https://codecov.io/gh/Shathra/one-key)
Command Line Key-Value Storage Application. Stores key-value pairs into a file using AES encryption. Created to practice test driven development.
## Installation
`conda install -c conda-forge --file requirements.txt`
## Usage
`python onekey.py`
### Add
`add <key>`
Asks for value then add it with given key
### List
`list [<argument>]`
Lists keys containing `<argument>` if exist.
### View
`view <key>`
Views the value of given key
### Del
`del <key>`
Deletes entry with given key
### Clear
`clear`
Clears terminal output
### Quit
`quit`
Quits application
| 16.9 | 254 | 0.714793 | eng_Latn | 0.644917 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.