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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
4fe9e46166205ff41cda966ffdcd3d7b50d95e26 | 671 | md | Markdown | README.md | uafio/elfitor | 9633d903f2175f54efdca9f64d1724b1e4b82bdb | [
"MIT"
] | null | null | null | README.md | uafio/elfitor | 9633d903f2175f54efdca9f64d1724b1e4b82bdb | [
"MIT"
] | null | null | null | README.md | uafio/elfitor | 9633d903f2175f54efdca9f64d1724b1e4b82bdb | [
"MIT"
] | null | null | null | # ABANDONED PROJECT
I'm not happy with the code base. I used this project to learn more about the ELF file format. If I ever resume this work I will start from scratch, lessons were learned. I'm publishing a pre-release if anybody wants to give it a try. It only supports little-endian ELFs, best if they are x64.
# elfitor
elf editor
# Screenshots
### ELF Header
### Program Header
### PT_DYNAMIC
### Section headers
### Section .dynstr
> See more in the [assets](./assets/) directory | 25.807692 | 293 | 0.743666 | eng_Latn | 0.950684 |
4fea460fb6c3880748b187c19f99d48f349b5173 | 1,222 | md | Markdown | doc/05.md | IsAlbertLiu/blink | b8c95e05a70e8e96c3c2971b06dfdd4d1c076af1 | [
"MIT"
] | null | null | null | doc/05.md | IsAlbertLiu/blink | b8c95e05a70e8e96c3c2971b06dfdd4d1c076af1 | [
"MIT"
] | null | null | null | doc/05.md | IsAlbertLiu/blink | b8c95e05a70e8e96c3c2971b06dfdd4d1c076af1 | [
"MIT"
] | null | null | null | ### 组件概述
心型💗是一个组件。在很多的页面里面都需要用到，所以我们将它写成一个自定义组件。
#### 定义，引用与使用组件
1. 新建组件
* 新建文件夹 components
* 在 components 里新建 like 文件夹
* 在 like 文件夹上右键，新建 components 就可以快速创建一个组件了。
2. 引用组件
在 classic.json 里面引入组件
"l-like" 的是组件名称，可以自定义，其后面的是组件的路径。
```javascript
{
"usingComponents": {
"l-like": "../components/like/index"
}
}
```
不仅仅可以在一个页面里面引入组件，当一个组件在多个页面中使用时，可以直接在 app.json 里面引入，这样就可以直接在其他的页面引入了。
3. 使用组件
使用组件和使用标签是一样的，我们使用刚刚定义的组件
```html
<l-like></l-like>
```
#### 相对路径和绝对路径
小程序中使用绝对路径是 `/` .使用相对路径 `../` 返回上一级路径
### like 组件的实现
#### 小程序尺寸单位与设计原则
当我们拿到一张图片的大小的时候，我们不能直接按照它的原图进行设置它的大小。
小程序中有两种常见的单位，一种是 px ，另外一种是 rpx。使用 px 作为单位的时候，假设设置一个在系统里面显示为 30px 的视觉效果的图片，在小程序里面就需要设置为 15px。要么使用 rpx 作为单位，就会和上面产生一样的效果。使用 rpx 单位产生的视觉效果会根据机型的改变而改变。 设计小程序的海报时，使用的机型需要以 iPhone6 的比例一样。750 x 1334。
小程序会在每个页面外面包裹一层 page。当我们需要设置全局样式的时候，可以：
```css
page{
font-family: "PingFangSC-Thin";
font-size: 32rpx;
}
```
#### 组件只能继承极少数全局样式
只有 font color 属性会从组件外继承到组件内。
#### 组件最好不要有留白间距
使用 `line-height` 可以消除字体的间距。组件最好不要留有空白间距，因为这个会让组件变大。
给元素设置了`display: flex` 之后，容器的子元素虽然失去了block属性的作用，但是其本身的block特征并没有消失，设置 `inline-flex` 可以让元素的宽度自适应
#### 给组件添加事件
绑定事件：
`bind:tap="onLike"` 也可以使用 `catch:tap="onLike"`
bind 不会阻止事件向上冒泡，catch 会阻止事件向上冒泡
| 17.211268 | 192 | 0.737316 | yue_Hant | 0.567859 |
4fea5f45ee1e578d279d96cf452c743af593d6e1 | 279 | md | Markdown | app/_country/KWT.md | kant/microsites | 3b7b22098f265fffef13a7228427a20b59e2b995 | [
"BSD-3-Clause"
] | 1 | 2020-03-17T04:56:31.000Z | 2020-03-17T04:56:31.000Z | app/_country/KWT.md | kant/microsites | 3b7b22098f265fffef13a7228427a20b59e2b995 | [
"BSD-3-Clause"
] | 15 | 2017-06-12T17:25:37.000Z | 2021-05-06T18:38:43.000Z | app/_country/KWT.md | kant/microsites | 3b7b22098f265fffef13a7228427a20b59e2b995 | [
"BSD-3-Clause"
] | 3 | 2018-11-06T15:57:35.000Z | 2021-11-09T13:48:17.000Z | ---
layout: country
lang: en
permalink: /kuwait/
iso3: KWT
iso2: KW
name: Kuwait
admin: Kuwait
contact:
flag: kw.svg
osmLink: https://openstreetmap.org/relation/305099
calendar:
bbox: 46.568713413281756,28.526062730416143,48.416094191283946,30.059069932570722
tm-projects:
--- | 18.6 | 81 | 0.774194 | nld_Latn | 0.078257 |
4feaa7ce3204bf80cdfcf41da93c0ecb472a9c98 | 676 | md | Markdown | CHANGELOG.md | guillaumegenthial/fromconfig | 1feecb9d9a3d67f9ed94a3fe17905e6226b954c7 | [
"Apache-2.0"
] | null | null | null | CHANGELOG.md | guillaumegenthial/fromconfig | 1feecb9d9a3d67f9ed94a3fe17905e6226b954c7 | [
"Apache-2.0"
] | null | null | null | CHANGELOG.md | guillaumegenthial/fromconfig | 1feecb9d9a3d67f9ed94a3fe17905e6226b954c7 | [
"Apache-2.0"
] | 1 | 2021-05-25T20:11:51.000Z | 2021-05-25T20:11:51.000Z | # Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) and this project adheres to [Semantic Versioning](https://semver.org).
## [0.2.2] - 2021-03-31
### Added
### Changed
- `fromconfig.Config` now inherits `dict` instead of `collections.UserDict` to support JSON serialization.
### Deprecated
### Removed
### Fixed
### Security
## [0.2.0] - 2021-03-18
### Added
### Changed
- Improved readme
### Deprecated
### Removed
### Fixed
### Security
## [0.1.0] - 2021-03-18
### Added
- Initial commit
### Changed
### Deprecated
### Removed
### Fixed
### Security
| 16.095238 | 150 | 0.66568 | eng_Latn | 0.953191 |
4feaedd89bc80a25c692898a83b86ec8cfa988e8 | 3,231 | md | Markdown | add/metadata/System.Windows.Media.Animation/CharKeyFrameCollection.meta.md | kcpr10/dotnet-api-docs | b73418e9a84245edde38474bdd600bf06d047f5e | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-06-16T22:24:36.000Z | 2020-06-16T22:24:36.000Z | add/metadata/System.Windows.Media.Animation/CharKeyFrameCollection.meta.md | kcpr10/dotnet-api-docs | b73418e9a84245edde38474bdd600bf06d047f5e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | add/metadata/System.Windows.Media.Animation/CharKeyFrameCollection.meta.md | kcpr10/dotnet-api-docs | b73418e9a84245edde38474bdd600bf06d047f5e | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-04-08T14:42:27.000Z | 2019-04-08T14:42:27.000Z | ---
uid: System.Windows.Media.Animation.CharKeyFrameCollection
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.Remove(System.Windows.Media.Animation.CharKeyFrame)
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.Clear
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.GetCurrentValueAsFrozenCore(System.Windows.Freezable)
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.Clone
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.IsFixedSize
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.Insert(System.Int32,System.Windows.Media.Animation.CharKeyFrame)
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.FreezeCore(System.Boolean)
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.#ctor
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.Item(System.Int32)
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.System#Collections#IList#Insert(System.Int32,System.Object)
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.System#Collections#IList#Remove(System.Object)
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.RemoveAt(System.Int32)
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.Count
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.CloneCore(System.Windows.Freezable)
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.CloneCurrentValueCore(System.Windows.Freezable)
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.CopyTo(System.Windows.Media.Animation.CharKeyFrame[],System.Int32)
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.GetAsFrozenCore(System.Windows.Freezable)
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.IsSynchronized
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.Contains(System.Windows.Media.Animation.CharKeyFrame)
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.SyncRoot
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.IndexOf(System.Windows.Media.Animation.CharKeyFrame)
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.System#Collections#ICollection#CopyTo(System.Array,System.Int32)
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.System#Collections#IList#IndexOf(System.Object)
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.Empty
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.System#Collections#IList#Contains(System.Object)
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.System#Collections#IList#Item(System.Int32)
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.CreateInstanceCore
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.System#Collections#IList#Add(System.Object)
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.IsReadOnly
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.Add(System.Windows.Media.Animation.CharKeyFrame)
---
---
uid: System.Windows.Media.Animation.CharKeyFrameCollection.GetEnumerator
---
| 25.242188 | 125 | 0.796967 | yue_Hant | 0.998379 |
57bceb5511aa5aff9ea9daa1a06f8459733c9aa2 | 673 | md | Markdown | README.md | wolf495/magicmaze | 76b3dccd32275cdf6341ed561fa86efdd1abde25 | [
"Apache-2.0"
] | null | null | null | README.md | wolf495/magicmaze | 76b3dccd32275cdf6341ed561fa86efdd1abde25 | [
"Apache-2.0"
] | null | null | null | README.md | wolf495/magicmaze | 76b3dccd32275cdf6341ed561fa86efdd1abde25 | [
"Apache-2.0"
] | null | null | null | # magicmaze
## Introduction
This project was made for CPSC 340, to focus on reading files, building arrays from files,
reading arguments, generating binary trees, and error handling. The concept is that the player is stuck in a maze
and must choose left/right paths in order to find a wizard to escape. Encountering other creatures or reaching the
end of a branch is gameover
## How to install / Run
- run command `git clone https://github.com/wolf495/magicmaze.git` to clone the repo
- run command `sudo apt-get install build-essential` to install make, g++ incase it is not isntalled on your machine
- run command `make` to compile the cpp files
- run command `./play`
| 56.083333 | 116 | 0.771174 | eng_Latn | 0.998995 |
57bf6e36b896ebf40a16fcb134e7b6419661e971 | 743 | md | Markdown | README.md | winnygold/Fat_Estimation_in_Liver | 4fa9e935faab24382018f872187774ede636c35e | [
"MIT"
] | null | null | null | README.md | winnygold/Fat_Estimation_in_Liver | 4fa9e935faab24382018f872187774ede636c35e | [
"MIT"
] | null | null | null | README.md | winnygold/Fat_Estimation_in_Liver | 4fa9e935faab24382018f872187774ede636c35e | [
"MIT"
] | null | null | null | # Fat Estimation in Liver Using DeepLearning :
This is a project to calculate the Fat in Liver using Deeplearning . We use [Liver Segmentation]() and [Hounsfield scale](https://en.wikipedia.org/wiki/Hounsfield_scale)
--------------------------
## DATASET
### CT DATASET 1 :
Dataset collected from [Chennai Liver Foundation](https://chennailiverfoundation.org/index)
Dataset : CT Scan Whole Abdomen , [DICOM](https://www.dicomstandard.org)
### CT DATASET 2 :
[LiTS Dataset](https://competitions.codalab.org/competitions/17094) is a biggest collection of Liver dataset with 130 CT SCans with 70 CT Scans as test dataset. This Dataset contains tasks for liver segmentation and tumor burden estimation.
------------------------------
| 37.15 | 241 | 0.707941 | eng_Latn | 0.391228 |
57c00b49c9a15b8f7e2e0993280a2fcff4c41c77 | 2,874 | md | Markdown | docs/BuildingtheDevelopmentEnvironment.md | LeagueOfLearningPython/Part_0 | 017dda58a1f5fbc456a3132cc547c6ba800556b3 | [
"Apache-2.0"
] | 2 | 2017-04-16T00:05:47.000Z | 2017-04-27T08:43:26.000Z | docs/BuildingtheDevelopmentEnvironment.md | LeagueOfLearningPython/Part_0 | 017dda58a1f5fbc456a3132cc547c6ba800556b3 | [
"Apache-2.0"
] | null | null | null | docs/BuildingtheDevelopmentEnvironment.md | LeagueOfLearningPython/Part_0 | 017dda58a1f5fbc456a3132cc547c6ba800556b3 | [
"Apache-2.0"
] | null | null | null | # 开发环境的搭建
## Python简介
1. Python的优点
简单、优雅、使用缩进而不是花括号，并且在国外Python作为高校初学者的入门语言
2. Python的应用领域
机器学习、深度学习、模式识别、web开发、自动化运维开发等
3. Python官网
https://www.python.org/
## Windows下开发环境的搭建（具体搭建过程可以参考 [小嘉丶学长博客](http://blog.csdn.net/fj_author)）
### Python2.7的安装
### Python3.5的安装
### Python2.7与Python3.5的解决方案
### anaconda的安装(略，kk和小青春强烈推荐)
### Sublime Text 3安装package control
### Sublime Text 3安装emmet
### Sublime Text 3安装SublimeREPL
### sublime Text 3为SublimeREPL配置快捷键
上面一个json配置的是打开浏览器的快捷键。前端开发使用
下面一个就是为SublimeREPL配置快捷键
[
{
"keys": ["ctrl+shift+enter"],
"command": "open_in_browser"
},
{
"keys":["f1"],
"caption": "SublimeREPL: Python - RUN current file",
"command": "run_existing_window_command", "args":
{
"id": "repl_python_run",
"file": "config/Python/Main.sublime-menu"
}
}
]
## 视频教程 [小嘉丶学长的视频](http://www.bilibili.com/video/av12232633/)
## Ubuntu Linux下使用技巧
## 第一个程序Hello,World!
1. 命令提示符
2. 脚本文件
3. 单行注释
`#`开头的为注释
4. 编码注释
```
#!/usr/bin/env python
#!/usr/bin/python
#conding=utf-8
#-*- coding: UTF-8 -*-
```
前面两行是声明Python解释器
第一行告诉操作系统执行这个脚本的时候，调用/usr/bin下的python解释器,这相当于写死了python路径;
第二行则会去环境设置寻找python目录,推荐这种写法
后面两行是Python脚本的字符编码
这两个实际上是没有什么区别的,但是第二种看上去比较好看
## 输入输出
1. print
2. raw_input
3. input
## 标识符、关键字(保留字)
1. 标识符
2. 关键字（保留字）
```
python2
>>> import keyword
>>> keyword.kwlist
['and', 'as', 'assert', 'break', 'class', 'continue', 'def', 'del', 'elif', 'els
e', 'except', 'exec', 'finally', 'for', 'from', 'global', 'if', 'import', 'in',
'is', 'lambda', 'not', 'or', 'pass', 'print', 'raise', 'return', 'try', 'while',
'with', 'yield']
```
31个
```
python3
>>> import keyword
>>> keyword.kwlist
['False', 'None', 'True', 'and', 'as', 'assert', 'break', 'class', 'continue', '
def', 'del', 'elif', 'else', 'except', 'finally', 'for', 'from', 'global', 'if',
'import', 'in', 'is', 'lambda', 'nonlocal', 'not', 'or', 'pass', 'raise', 'retu
rn', 'try', 'while', 'with', 'yield']
>>>
```
33个
Python3中有，但python2中没有的关键字
```
False
None
True
nonlocal
```
Python2中有python3中没有的关键字
```
exec Python2中是语句，而Python3中是函数
print Python2中是语句，而Python3中是函数
```
我建议这些都不要当作变量标识符，因为这不是一个好行为
## 物理行与逻辑行
1. 物理行
2. 逻辑行
## 查看帮助
1. help()
```Python
>>> help(input)
Help on built-in function input in module builtins:
#描述,在内建模块
input(prompt=None, /)
Read a string from standard input. The trailing newline is stripped.
#从标准输入设备读取一个字符,不包括结尾换行符
The prompt string, if given, is printed to standard output
without a trailing newline before reading input.
#prompt为提示字符串,如果传递了,在读取输入以前,在标准输出上打印一个没有换行的字符串
If the user hits EOF (*nix: Ctrl-D, Windows: Ctrl-Z+Return), raise EOFError.
#如果遇到EoF(类unix系统:Ctrl+D，windows:Ctrl+z回车)抛出一个EOEError
On *nix systems, readline is used if available.
```
2. 使用IDLE自带的手册
3. python官网的documentation
[点我返回首页](https://leagueoflearningpython.github.io/Part_0/)
| 17.9625 | 80 | 0.671538 | yue_Hant | 0.468061 |
57c0c8343195adbabd048cdb9bfcf3805d686c23 | 1,442 | md | Markdown | episodes/88.md | BoyanTodorov/Ognena-Pustinya | 8a184c1c5894a81049e9fef999a95cca92384804 | [
"WTFPL"
] | null | null | null | episodes/88.md | BoyanTodorov/Ognena-Pustinya | 8a184c1c5894a81049e9fef999a95cca92384804 | [
"WTFPL"
] | null | null | null | episodes/88.md | BoyanTodorov/Ognena-Pustinya | 8a184c1c5894a81049e9fef999a95cca92384804 | [
"WTFPL"
] | null | null | null | ## 88.
Най-сетне противникът ти пада мъртъв. Обръщаш се назад и
виждаш, че Борил и капитанът са обезвредили трети нападател. Но
виждаш и още нещо, от което кръвта ти застива. По спокойните води
на реката се задава кораб с черен пиратски флаг. Значи това е била
целта на тримата разбойници - да отклонят вниманието ви, докато
техните съучастници се приближават за абордаж.
Върху палубата със зловещо свистене се изсипва дъжд с стрели. По
примера на капитана бързо отскачаш зад надстройката, където вече
са подирили прикритие неколцина моряци и пътници. Борил се хвърля
след вас, ала не е достатъчно бърз. Виждаш го как се препъва и пада
със забита в гърлото стрела.
В яростта си ти забравяш за опасностите. Бързо пропълзяваш
напред и изтегляш Борил зад ъгъла. Късно! О раната бие фонтан
алена кръв, които не може да бъде спрян заедно с него изтича
животът на верния ти спътник. Усеща как по тялото му пробягва
предсмъртна тръпка и се изправяш, изпълнен с ненавист към
убийците. Скъпо ще ти платят!
Между двата кораба остават само няколко метра. Вече не падат
стрели. Тръгваш към перилата, гледайки как отсреща пиратите
размахват саби и се готвят за абордаж. С КаКво ще ги нападнеш?
[Бездънна манерка - на 15.](./15)
[Гръцки огън - 21.](./21)
[Мъртва пепел - 40.](./40)
[Дим на миражите - 54.](./54)
[Ще хвърлиш бумеранг по капитана - 28.](./28)
[Ако нямаш нито един от тези предмети или не желаеш да си
използваш, мини на 65.](./65)
| 36.974359 | 67 | 0.771845 | bul_Cyrl | 0.999991 |
57c290ebbdf0436250d9d48f06b739d70c1d1831 | 1,072 | md | Markdown | src/members/one-love-capital-lda_2020-10-15.md | SocialEntrepreneurshipNetzwerk/send | 81cf4a8756cb9d1b6674c1d54f8c137ce8e60443 | [
"MIT"
] | null | null | null | src/members/one-love-capital-lda_2020-10-15.md | SocialEntrepreneurshipNetzwerk/send | 81cf4a8756cb9d1b6674c1d54f8c137ce8e60443 | [
"MIT"
] | 3 | 2018-06-19T07:08:25.000Z | 2021-09-01T23:58:49.000Z | src/members/one-love-capital-lda_2020-10-15.md | SocialEntrepreneurshipNetzwerk/send | 81cf4a8756cb9d1b6674c1d54f8c137ce8e60443 | [
"MIT"
] | null | null | null | ---
title: ONE LOVE CAPITAL LDA
description: >
ONE LOVE CAPITAL LDA bringt Experten zusammen, um nachhaltige
Geschäftsprojekte in Mosambik zu unterstützen.
ONE LOVE CAPITAL LDA unterstützt Unternehmer in gemeindebasierten, profitablen, sozialen und umweltfreundlichen Unternehmen durch die Bereitstellung von Finanzierungslösungen Mentoring- und sonstigen Dienstleistungen.
Das Hauptziel des Unternehmens ist auf die SDGs ausgerichtet. Von unterstützten Unternehmen wird erwartet, dass sie positive Auswirkungen auf die Gemeinden haben und Unternehmer dazu inspirieren, lokale Produkte herzustellen und nachhaltige Praktiken anzuwenden. Ziel ist es, Arbeitsplätze und Einkommen zu schaffen und das Gemeinwohl Mosambiks zu schützen und zu erhalten.
impactArea:
- Dienstleistungen für Sozialunternehmen
- Entrepreneurshipförderung
- Umwelt– & Klimaschutz
organization: true
image: /uploads/one-love-capital-lda.png
email: [email protected]
link: https://www.linkedin.com/company/onelovecapital
city: Maputo
postalCode: 10000
federalState: Berlin
---
| 48.727273 | 375 | 0.82556 | deu_Latn | 0.995409 |
57c2df9140d1c6c63443814888749e228f08ebc2 | 12,739 | md | Markdown | README.md | barbulescualex/MaterialFields | 798ae462309b97ab2c78ae119c32df7f9e9d1b7c | [
"MIT"
] | 4 | 2019-04-25T19:35:29.000Z | 2019-05-15T08:14:41.000Z | README.md | barbulescualex/MaterialFields | 798ae462309b97ab2c78ae119c32df7f9e9d1b7c | [
"MIT"
] | 1 | 2019-05-02T00:06:56.000Z | 2019-05-09T21:44:06.000Z | README.md | barbulescualex/MaterialFields | 798ae462309b97ab2c78ae119c32df7f9e9d1b7c | [
"MIT"
] | 1 | 2019-05-15T08:14:42.000Z | 2019-05-15T08:14:42.000Z | # MaterialFields
A material UI driven text entry and value selection framework for modular validation layers.
---
| | Main Features |
----------|-----------------
💛 | Material UITextFields and UITextViews
💜 | Material UIPickerViews and UIDatePickers
💪 | Field wrapper class allowing for simple, modular validation
❌ | Error functionality to let your users know something was wrong with the input
🔥 | Internal UI state management
👍 | Modular and customizable
😍 | Fully Swift
✅ | Easy to implement
### Adding MaterialFields To Your Project
---
Open your podfile and add MaterialFields under your target
``` ruby
target 'Your Project' do
use_frameworks!
pod 'MaterialFields'
end
```
Save, then in your project directory run
``` ruby
pod install
```
## Getting Started
Getting started with MaterialFields is very easy! There are 2 example projects, one programmatic and one using storyboards showing you the implementation.
Essentially there are only 4 things you need to do to get the basic functionality going:
1. Instantiate the field
2. Set its placeholder (this is the title label) and data array (if PickerField)
3. Set its delegate
4. Implement the didEndEditing delegate method to get the value when the users done!
### [Field](https://barbulescualex.github.io/MaterialFields/Classes/Field.html)
---
First we define a Field. This is the wrapper class that all the fields conform to. This allows all of them to share implemenation and functionality and also leads to an easier validation layer.
**2 Types Of Fields**
1. Text-entry fields. This comprises of [EntryField](https://barbulescualex.github.io/MaterialFields/Classes/EntryField.html) and [AreaField](https://barbulescualex.github.io/MaterialFields/Classes/AreaField.html).
2. Picker type fields. This comprises of [PickerField](https://barbulescualex.github.io/MaterialFields/Classes/PickerField.html) and [DateField](https://barbulescualex.github.io/MaterialFields/Classes/DateField.html)
They all resemble each other in their normal state but each offer their own unique functionality in their active states. Picker type fields hold entry fields with pickers that drop down below them. They have done buttons to close themselves and optional clear buttons (set by `isClearable = true`).
**States**
A Field has **3 states** with read-only flags:
* Not active : `isActive == false`
* Active, highlight visible : `isActive == true`
* Error : `hasError == true`
All the state logic and UI is handled internally. You can set the error state using [setError(withText:)](https://barbulescualex.github.io/MaterialFields/Classes/Field.html#/s:14MaterialFields5FieldC8setError8withTextySSSg_tF) and also remove it manually (the fields handle it on their own automatically, see specific field for details) using [removeErrorUI()](https://barbulescualex.github.io/MaterialFields/Classes/Field.html#/s:14MaterialFields5FieldC13removeErrorUIyyF)
**Values**
They return **2 types of values**:
* String accessed by `.text` if it is an EntryField, AreaField or PickerField and,
* Date accessed by `.date` if it is DateField
**Sizing**
Fields rely on their [intrinsicContentSize](https://developer.apple.com/documentation/uikit/uiview/1622600-intrinsiccontentsize). This is becuase they can change in height depending on if they open a picker or have text in their error state. The easiest way to implement them is by throwing them inside UIStackViews and letting auto-layout handle everything around them. It can be more work if you want to set a height constraint (through auto-layout or a frame) but below are the heights for each field and their given state.
| Field Type | Normal | Error | Picker Open | Picker Open + Error |
----------|-----------------|----------|-----------|---------|
EntryField | 43.5 | 63.0 | N/A | N/A |
AreaField | 43.5+ | 63.0+ | N/A | N/A |
PickerField | 43.5 | 63.0 | 269.5 | 289 |
DateField | 43.5 | 63.0 | 269.5 | 289 |
**Colors**
Since all fields look the same they all have the exact same color properties (with small differences given the features).
### [EntryField](https://barbulescualex.github.io/MaterialFields/Classes/EntryField.html)
---
This is your UITextField. Most of the UITextField functionality has been forwarded to the EntryField.
**[EntryFieldDelegate](https://barbulescualex.github.io/MaterialFields/Protocols/EntryFieldDelegate.html)**
All of the UITextField delegates are here, just rebranded.
**Extra Features**
* Unit Label : set the `unit` property to a string to populate a unit label anchored on the right hand side.
* Money label : set `isMonetary = true` and a dollar sign is anchored to the left hand side.
Their colors are also overridable using `monetaryColor` or `unitColor`
**Responder Behaviour**
EntryFields behave the same way that UITextFields behave, `becomeFirstResponder()` will activate the field and `resignFirstResponder()` will deactivate the field.
### [AreaField](https://barbulescualex.github.io/MaterialFields/Classes/AreaField.html)
---
This is your UITextView with only the text-entry functionality, so a multiline EntryField. Unlike the EntryField this does not support `isMonetary` or `units`.
**[AreaFieldDelegate](https://barbulescualex.github.io/MaterialFields/Protocols/AreaFieldDelegate.html)**
All of the text-entry relevant delegates are here.
**Responder Behaviour**
AreaFields behave the same way that UITextViews behave, `becomeFirstResponder()` will activate the field and `resignFirstResponder()` will deactivate the field.
### [PickerField](https://barbulescualex.github.io/MaterialFields/Classes/PickerField.html)
---
This is your UIPickerView which only supports 1 column. Most of the setup work has been extracted away, leaving little implementation logic needed. All you need to do is set its `data` array to your string array and the rest is handled for you.
The PickerField holds an EntryField that is used to display the contents of the picker.
**[PickerFieldDelegate](https://barbulescualex.github.io/MaterialFields/Protocols/PickerFieldDelegate.html)**
This will be a little different than you're used to as you no longer need to implement the data source protocol.
You have:
* shouldBeginEditing : wether it should open or not
* didEndEditing: user closed the field by tapping on the done button or keyboard came up (see Keyboard Behaviour)
* cleared : user tapped the clear button (only if `isClearable = true`)
* selectedRowForIndexPath : user selected a different value in the picker
**Extra Features**
* `isManualEntryCapable` this appends a "Manual Entry" option to the end of your data source which brings up the keyboard if selected and activates the EntryField embedded inside the PickerField. The manual entry row label is overridable using `manualEntryOptionName`.
You can observe the current index using `indexSelected` set an index using `setIndexTo` and set the index to manual entry using `setIndexToManual()`.
**Responder Behaviour**
* `becomeFirstResponder()` will activate and open up the picker / EntryField if it's on manual entry
* `closeFirstResponder()` will deactivate and close the picker / EntryField if it's on manual entry
**Keyboard Behaviour**
PickerFields register for keyboardDidShow notifications. If they are not on manual entry, they will close themselves and trigger their didEndEditing delegate upon the keyboard coming up.
### [DateField](https://barbulescualex.github.io/MaterialFields/Classes/DateField.html)
---
This is your UIDatePicker. You can do all the things you can do with the UIDatePicker you're used to, the property names are the same.
**[DateFieldDelegate](https://barbulescualex.github.io/MaterialFields/Protocols/DateFieldDelegate.html)**
This mirrors the PickerField delegate.
You have:
* shouldBeginEditing : wether it should open or not
* didEndEditing: user closed the field by tapping on the done button or keyboard came up (see Keyboard Behaviour)
* cleared : user tapped the clear button (only if `isClearable = true`)
* dateChanged : user selected a different date
**Responder Behaviour**
* `becomeFirstResponder()` will activate and open up the picker
* `closeFirstResponder()` will deactivate and close the picker
**Keyboard Behaviour**
DateFields register for keyboardDidShow notifications. They will close themselves and trigger their didEndEditing delegate upon the keyboard coming up.
## Validation Layers
Since all the fields conform to the Field class, validation layers tied directly to the Fields has never been easier!
Lets define 3 fields, an EntryField, an AreaField, and a PickerField
``` swift
let entryField = EntryField()
let areaField = AreaField()
let pickerField = PickerField()
```
Lets also define a CaseIterable enum:
``` swift
extension CaseIterable where AllCases.Element: Equatable {
static func make(index: Int) -> Self? { //get the key from the case index
let a = Self.allCases
if (index > a.count - 1) { return nil } //out of range
return a[a.index(a.startIndex, offsetBy: index)]
}
func index() -> Int { //get the index from the case
let a = Self.allCases
return a.distance(from: a.startIndex, to: a.firstIndex(of: self)!)
}
}
enum FieldKeys : String, CaseIterable {
case entry
case area
case picker
}
```
With our CaseIterable enum we can use the validation keys as tags for the fields!
``` swift
entryField.tag = FieldKeys.entry.index()
areaField.tag = FieldKeys.area.index()
pickerField.tag = FieldKeys.picker.index()
```
Lets say we need to validate a generic string (with the regex set in our core data model) before commiting changes to our model using an extension on NSManagedObject.
``` swift
extension NSManagedObject {
func validateString(view: Field, key: String){
var value = view.text as AnyObject?
do {
try self.validateValue(&(value), forKey: key)
} catch {
view.setError(withText: "please try again")
print(error)
return
}
self.setValue(value, forKey: key)
}
}
```
Now on any of the fields' didEndEditing delegate methods we only need to 2 lines to validate our entry.
``` swift
//EntryFieldDelegates
func entryFieldDidEndEditing(_ view: EntryField){
//the key reconstructed from our enum used for the field tags
gaurd let key = FieldKeys.make(index: view.tag) else {return}
ourNSManagedObject.validateString(view,key.rawValue)
}
//AreaFieldDelegates
func areaFieldDidEndEditing(_ view: AreaField){
//the key reconstructed from our enum used for the field tags
gaurd let key = FieldKeys.make(index: view.tag) else {return}
ourNSManagedObject.validateString(view,key.rawValue)
}
//PickerFieldDelegates
func pickerFieldDidEndEditing(_ view: PickerField){
//the key reconstructed from our enum used for the field tags
gaurd let key = FieldKeys.make(index: view.tag) else {return}
ourNSManagedObject.validateString(view,key.rawValue)
}
```
We now have a validation layer capable of both data model validation and UI feedback!
## Docs
MaterialFields is fully documented [here](https://barbulescualex.github.io/MaterialFields/index.html) with Jazzy.
To regenerate the documentation run
``` ruby
jazzy --source-directory 'MaterialFields/' --documentation=Guides/*.md -g 'https://github.com/barbulescualex/MaterialFields' -m 'MaterialFields'
```
in the project root directory
## License
MaterialFields is open under the MIT license.
| 38.486405 | 526 | 0.762226 | eng_Latn | 0.90502 |
57c38d63df5eb9cde5820a6a4dc656fd9dfd87eb | 839 | md | Markdown | README.md | VasAtanasov/SoftUni-Python-Fundamentals | 471d0537dd6e5c8b61ede92b7673c0d67e2964fd | [
"MIT"
] | 1 | 2019-06-05T11:16:08.000Z | 2019-06-05T11:16:08.000Z | README.md | VasAtanasov/SoftUni-Python-Fundamentals | 471d0537dd6e5c8b61ede92b7673c0d67e2964fd | [
"MIT"
] | null | null | null | README.md | VasAtanasov/SoftUni-Python-Fundamentals | 471d0537dd6e5c8b61ede92b7673c0d67e2964fd | [
"MIT"
] | null | null | null | # SoftUni-Python-Fundamentals
Python Fundamentals – January 2019
Курсът Python Fundamentals ще ви запознае с базови техники и инструменти за практическо програмиране отвъд писането на прости програмни конструкции. Обучението обхваща работа с функции с параметри и връщана стойност, използване на дебъгер за проследяване изпълнението на кода и намиране на грешки, обработка на поредици елементи чрез списъци, използване на колекции, работа с речници и асоциативни масиви за обработка и съхранение на двойки {ключ - стойност}, работа със стрингове и текстообработка. Наред с техниките за програмиране курсът развива алгоритмично мислене и изгражда умения за решаване на задачи чрез работа върху стотици практически упражнения. Всички задачи за упражнения и домашни се оценяват в реално време с автоматизираната SoftUni online judge система. | 209.75 | 773 | 0.841478 | bul_Cyrl | 0.999838 |
57c3a3db5bbdbcd5e6eef4ce85866c80893b13d5 | 13,074 | md | Markdown | docs/fsharp/language-reference/anonymous-records.md | smolck/docs.fr-fr | ee27cca4b8e319e4cbdea9103c3f90ac22378d50 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/fsharp/language-reference/anonymous-records.md | smolck/docs.fr-fr | ee27cca4b8e319e4cbdea9103c3f90ac22378d50 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/fsharp/language-reference/anonymous-records.md | smolck/docs.fr-fr | ee27cca4b8e319e4cbdea9103c3f90ac22378d50 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Enregistrements anonymes
description: Apprenez à utiliser la construction et l’utilisation d’Anonymous Records, une fonctionnalité linguistique qui aide à la manipulation des données.
ms.date: 06/12/2019
ms.openlocfilehash: 121f0f638dff2ae529b2488d8e3b1ad9c064cf90
ms.sourcegitcommit: 465547886a1224a5435c3ac349c805e39ce77706
ms.translationtype: MT
ms.contentlocale: fr-FR
ms.lasthandoff: 04/21/2020
ms.locfileid: "81738501"
---
# <a name="anonymous-records"></a>Enregistrements anonymes
Les enregistrements anonymes sont des agrégats simples de valeurs nommées qui n’ont pas besoin d’être déclarés avant utilisation. Vous pouvez les déclarer comme des structs ou des types de référence. Ce sont des types de référence par défaut.
## <a name="syntax"></a>Syntaxe
Les exemples suivants démontrent la syntaxe anonyme. Articles délimités `[item]` en option.
```fsharp
// Construct an anonymous record
let value-name = [struct] {| Label1: Type1; Label2: Type2; ...|}
// Use an anonymous record as a type parameter
let value-name = Type-Name<[struct] {| Label1: Type1; Label2: Type2; ...|}>
// Define a parameter with an anonymous record as input
let function-name (arg-name: [struct] {| Label1: Type1; Label2: Type2; ...|}) ...
```
## <a name="basic-usage"></a>Utilisation de base
Les enregistrements anonymes sont mieux considérés comme des types d’enregistrements F et qui n’ont pas besoin d’être déclarés avant l’instantanéisation.
Par exemple, voici comment vous pouvez interagir avec une fonction qui produit un enregistrement anonyme :
```fsharp
open System
let getCircleStats radius =
let d = radius * 2.0
let a = Math.PI * (radius ** 2.0)
let c = 2.0 * Math.PI * radius
{| Diameter = d; Area = a; Circumference = c |}
let r = 2.0
let stats = getCircleStats r
printfn "Circle with radius: %f has diameter %f, area %f, and circumference %f"
r stats.Diameter stats.Area stats.Circumference
```
L’exemple suivant s’étend sur `printCircleStats` le précédent avec une fonction qui prend un dossier anonyme comme entrée:
```fsharp
open System
let getCircleStats radius =
let d = radius * 2.0
let a = Math.PI * (radius ** 2.0)
let c = 2.0 * Math.PI * radius
{| Diameter = d; Area = a; Circumference = c |}
let printCircleStats r (stats: {| Area: float; Circumference: float; Diameter: float |}) =
printfn "Circle with radius: %f has diameter %f, area %f, and circumference %f"
r stats.Diameter stats.Area stats.Circumference
let r = 2.0
let stats = getCircleStats r
printCircleStats r stats
```
Appeler `printCircleStats` avec n’importe quel type d’enregistrement anonyme qui n’a pas la même «forme» que le type d’entrée ne sera pas compiler:
```fsharp
printCircleStats r {| Diameter = 2.0; Area = 4.0; MyCircumference = 12.566371 |}
// Two anonymous record types have mismatched sets of field names
// '["Area"; "Circumference"; "Diameter"]' and '["Area"; "Diameter"; "MyCircumference"]'
```
## <a name="struct-anonymous-records"></a>Structurer des dossiers anonymes
Les enregistrements anonymes peuvent également être `struct` définis comme struct avec le mot clé facultatif. L’exemple suivant augmente le précédent en produisant et en consommant un enregistrement anonyme struct :
```fsharp
open System
let getCircleStats radius =
let d = radius * 2.0
let a = Math.PI * (radius ** 2.0)
let c = 2.0 * Math.PI * radius
// Note that the keyword comes before the '{| |}' brace pair
struct {| Area = a; Circumference = c; Diameter = d |}
// the 'struct' keyword also comes before the '{| |}' brace pair when declaring the parameter type
let printCircleStats r (stats: struct {| Area: float; Circumference: float; Diameter: float |}) =
printfn "Circle with radius: %f has diameter %f, area %f, and circumference %f"
r stats.Diameter stats.Area stats.Circumference
let r = 2.0
let stats = getCircleStats r
printCircleStats r stats
```
### <a name="structness-inference"></a>Inférence de structuration
Les enregistrements anonymes Struct permettent également une « inférence de `struct` la structivité » lorsque vous n’avez pas besoin de spécifier le mot clé sur le site d’appel. Dans cet exemple, vous `struct` élitez le mot clé lors de l’appel `printCircleStats`:
```fsharp
let printCircleStats r (stats: struct {| Area: float; Circumference: float; Diameter: float |}) =
printfn "Circle with radius: %f has diameter %f, area %f, and circumference %f"
r stats.Diameter stats.Area stats.Circumference
printCircleStats r {| Area = 4.0; Circumference = 12.6; Diameter = 12.6 |}
```
Le modèle inverse `struct` - spécifiant quand le type d’entrée n’est pas un enregistrement anonyme structurant - ne sera pas compilé.
## <a name="embedding-anonymous-records-within-other-types"></a>Intégrer des dossiers anonymes dans d’autres types
Il est utile de déclarer [les syndicats discriminés](discriminated-unions.md) dont les cas sont des dossiers. Mais si les données dans les dossiers sont du même type que l’union discriminée, vous devez définir tous les types comme récursifs mutuellement. L’utilisation de dossiers anonymes évite cette restriction. Ce qui suit est un type d’exemple et la fonction que le modèle correspond à celui-ci:
```fsharp
type FullName = { FirstName: string; LastName: string }
// Note that using a named record for Manager and Executive would require mutually recursive definitions.
type Employee =
| Engineer of FullName
| Manager of {| Name: FullName; Reports: Employee list |}
| Executive of {| Name: FullName; Reports: Employee list; Assistant: Employee |}
let getFirstName e =
match e with
| Engineer fullName -> fullName.FirstName
| Manager m -> m.Name.FirstName
| Executive ex -> ex.Name.FirstName
```
## <a name="copy-and-update-expressions"></a>Copier et mettre à jour les expressions
Les documents anonymes prennent en charge la construction avec [des expressions de copie et de mise à jour.](copy-and-update-record-expressions.md) Par exemple, voici comment vous pouvez construire une nouvelle instance d’un enregistrement anonyme qui copie les données d’un enregistrement existant :
```fsharp
let data = {| X = 1; Y = 2 |}
let data' = {| data with Y = 3 |}
```
Cependant, contrairement aux enregistrements nommés, les enregistrements anonymes vous permettent de construire des formulaires entièrement différents avec des expressions de copie et de mise à jour. L’exemple de suivi prend le même enregistrement anonyme de l’exemple précédent et l’étend dans un nouvel enregistrement anonyme:
```fsharp
let data = {| X = 1; Y = 2 |}
let expandedData = {| data with Z = 3 |} // Gives {| X=1; Y=2; Z=3 |}
```
Il est également possible de construire des enregistrements anonymes à partir d’instances de documents nommés :
```fsharp
type R = { X: int }
let data = { X = 1 }
let data' = {| data with Y = 2 |} // Gives {| X=1; Y=2 |}
```
Vous pouvez également copier des données à et depuis et en référant des enregistrements anonymes :
```fsharp
// Copy data from a reference record into a struct anonymous record
type R1 = { X: int }
let r1 = { X = 1 }
let data1 = struct {| r1 with Y = 1 |}
// Copy data from a struct record into a reference anonymous record
[<Struct>]
type R2 = { X: int }
let r2 = { X = 1 }
let data2 = {| r1 with Y = 1 |}
// Copy the reference anonymous record data into a struct anonymous record
let data3 = struct {| data2 with Z = r2.X |}
```
## <a name="properties-of-anonymous-records"></a>Propriétés de dossiers anonymes
Les dossiers anonymes ont un certain nombre de caractéristiques qui sont essentielles pour bien comprendre comment ils peuvent être utilisés.
### <a name="anonymous-records-are-nominal"></a>Les dossiers anonymes sont nominaux
Les dossiers anonymes sont [des types nominaux](https://en.wikipedia.org/wiki/Nominal_type_system). Ils sont mieux considérés comme des types [d’enregistrement](records.md) nommés (qui sont également nominaux) qui ne nécessitent pas une déclaration à l’avance.
Prenons l’exemple suivant avec deux déclarations d’enregistrement anonymes :
```fsharp
let x = {| X = 1 |}
let y = {| Y = 1 |}
```
Les `x` `y` valeurs et les valeurs ont des types différents et ne sont pas compatibles les unes avec les autres. Ils ne sont pas équatables et ils ne sont pas comparables. Pour illustrer cela, considérez un équivalent d’enregistrement nommé :
```fsharp
type X = { X: int }
type Y = { Y: int }
let x = { X = 1 }
let y = { Y = 1 }
```
Il n’y a rien d’intrinsèquement différent dans les enregistrements anonymes par rapport à leurs équivalents d’enregistrement nommés en ce qui concerne l’équivalence de type ou la comparaison.
### <a name="anonymous-records-use-structural-equality-and-comparison"></a>Les documents anonymes utilisent l’égalité structurelle et la comparaison
Comme les types d’enregistrements, les dossiers anonymes sont structurellement équatables et comparables. Cela n’est vrai que si tous les types de constituants sont en faveur de l’égalité et de la comparaison, comme avec les types de disques. Pour soutenir l’égalité ou la comparaison, deux dossiers anonymes doivent avoir la même « forme ».
```fsharp
{| a = 1+1 |} = {| a = 2 |} // true
{| a = 1+1 |} > {| a = 1 |} // true
// error FS0001: Two anonymous record types have mismatched sets of field names '["a"]' and '["a"; "b"]'
{| a = 1 + 1 |} = {| a = 2; b = 1|}
```
### <a name="anonymous-records-are-serializable"></a>Les dossiers anonymes sont sérialisables
Vous pouvez sérialiser des enregistrements anonymes comme vous le pouvez avec les enregistrements nommés. Voici un exemple en utilisant [Newtonsoft.Json](https://www.nuget.org/packages/Newtonsoft.Json/):
```fsharp
open Newtonsoft.Json
let phillip' = {| name="Phillip"; age=28 |}
let philStr = JsonConvert.SerializeObject(phillip')
let phillip = JsonConvert.DeserializeObject<{|name: string; age: int|}>(philStr)
printfn "Name: %s Age: %d" phillip.name phillip.age
```
Les enregistrements anonymes sont utiles pour envoyer des données légères sur un réseau sans avoir besoin de définir un domaine pour vos types sérialisés/déséialisés à l’avance.
### <a name="anonymous-records-interoperate-with-c-anonymous-types"></a>Les dossiers anonymes s’interopément avec les types d’anonymes C
Il est possible d’utiliser une API .NET qui nécessite l’utilisation de [types D.C. anonymes](../../csharp/programming-guide/classes-and-structs/anonymous-types.md). Les types anonymes Cmd sont insignifiants à interopérer en utilisant des dossiers anonymes. L’exemple suivant montre comment utiliser des dossiers anonymes pour appeler une surcharge [LINQ](../../csharp/programming-guide/concepts/linq/index.md) qui nécessite un type anonyme :
```fsharp
open System.Linq
let names = [ "Ana"; "Felipe"; "Emilia"]
let nameGrouping = names.Select(fun n -> {| Name = n; FirstLetter = n.[0] |})
for ng in nameGrouping do
printfn "%s has first letter %c" ng.Name ng.FirstLetter
```
Il existe une multitude d’autres API utilisées sur .NET qui nécessitent l’utilisation de la transmission dans un type anonyme. Les dossiers anonymes sont votre outil pour travailler avec eux.
## <a name="limitations"></a>Limites
Les dossiers anonymes ont certaines restrictions dans leur utilisation. Certains sont inhérents à leur conception, mais d’autres sont agréables à changer.
### <a name="limitations-with-pattern-matching"></a>Limitations avec l’appariement des motifs
Les dossiers anonymes ne prennent pas en charge l’appariement des motifs, contrairement aux enregistrements nommés. Il y a trois raisons :
1. Un modèle devrait rendre compte de chaque domaine d’un enregistrement anonyme, contrairement aux types d’enregistrement nommés. C’est parce que les dossiers anonymes ne prennent pas en charge le sous-typage structurel - ce sont des types nominaux.
2. En raison de (1), il n’y a aucune capacité d’avoir des modèles supplémentaires dans une expression de correspondance de modèle, comme chaque modèle distinct impliquerait un type d’enregistrement anonyme différent.
3. En raison de (3), tout modèle d’enregistrement anonyme serait plus verbeux que l’utilisation de la notation "point".
Il y a une suggestion de langage ouvert pour [permettre l’appariement des modèles dans des contextes limités.](https://github.com/fsharp/fslang-suggestions/issues/713)
### <a name="limitations-with-mutability"></a>Limitations avec mutabilité
Il n’est pas actuellement possible `mutable` de définir un enregistrement anonyme avec des données. Il existe une [suggestion en langage ouvert](https://github.com/fsharp/fslang-suggestions/issues/732) pour permettre des données mutables.
### <a name="limitations-with-struct-anonymous-records"></a>Limitations avec la struction des dossiers anonymes
Il n’est pas possible de `IsByRefLike` `IsReadOnly`déclarer des documents anonymes structurants comme ou . Il y a une `IsByRefLike` suggestion `IsReadOnly` de [langage ouvert](https://github.com/fsharp/fslang-suggestions/issues/712) pour les dossiers anonymes et les dossiers.
| 47.198556 | 441 | 0.742772 | fra_Latn | 0.951361 |
57c5ac258baabf06f67c4940e3950642cccba74d | 4,491 | md | Markdown | windows-driver-docs-pr/stream/ksproperty-cameracontrol-extended-videostabilization.md | i35010u/windows-driver-docs.zh-cn | e97bfd9ab066a578d9178313f802653570e21e7d | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-02-04T01:49:58.000Z | 2021-02-04T01:49:58.000Z | windows-driver-docs-pr/stream/ksproperty-cameracontrol-extended-videostabilization.md | i35010u/windows-driver-docs.zh-cn | e97bfd9ab066a578d9178313f802653570e21e7d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | windows-driver-docs-pr/stream/ksproperty-cameracontrol-extended-videostabilization.md | i35010u/windows-driver-docs.zh-cn | e97bfd9ab066a578d9178313f802653570e21e7d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: KSPROPERTY \_ CAMERACONTROL \_ 扩展 \_ VIDEOSTABILIZATION
description: 此扩展属性控件用于控制驱动程序 MFT0 中的数字视频稳定 \\ 。
keywords:
- KSPROPERTY_CAMERACONTROL_EXTENDED_VIDEOSTABILIZATION 流媒体设备
topic_type:
- apiref
api_name:
- KSPROPERTY_CAMERACONTROL_EXTENDED_VIDEOSTABILIZATION
api_location:
- Ksmedia.h
api_type:
- HeaderDef
ms.date: 09/11/2018
ms.localizationpriority: medium
ms.openlocfilehash: e96e1f733b2c66e09984dda930d93b66d4bab7cb
ms.sourcegitcommit: 418e6617e2a695c9cb4b37b5b60e264760858acd
ms.translationtype: MT
ms.contentlocale: zh-CN
ms.lasthandoff: 12/07/2020
ms.locfileid: "96840563"
---
# <a name="ksproperty_cameracontrol_extended_videostabilization"></a>KSPROPERTY \_ CAMERACONTROL \_ 扩展 \_ VIDEOSTABILIZATION
此扩展属性控件用于控制驱动程序 MFT0 中的数字视频稳定 \\ 。
## <a name="usage-summary-table"></a>使用情况摘要表
<table>
<colgroup>
<col width="33%" />
<col width="33%" />
<col width="33%" />
</colgroup>
<thead>
<tr class="header">
<th>范围</th>
<th>控制</th>
<th>类型</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><p>版本 1</p></td>
<td><p>Pin</p></td>
<td><p>Synchronous</p></td>
</tr>
</tbody>
</table>
可放置在 KSCAMERA \_ EXTENDEDPROP 标头中的以下标志 \_ 。标志字段标志以控制驱动程序 MFT0 中的数字视频稳定 \\ 。 默认情况下，驱动程序应关闭视频抖动。
```cpp
#define KSCAMERA_EXTENDEDPROP_VIDEOSTABILIZATION_OFF 0x0000000000000000
#define KSCAMERA_EXTENDEDPROP_VIDEOSTABILIZATION_ON 0x0000000000000001
#define KSCAMERA_EXTENDEDPROP_VIDEOSTABILIZATION_AUTO 0x0000000000000002
```
如果驱动程序不支持数字视频防抖动，驱动程序不应实现此控制。
如果驱动程序支持此控件，则它必须支持 VIDEOSTABILIZATION \_ ON \\ OFF。
当视频 pin 处于任何高于 KSSTATE 停止状态的状态时，对此控件的设置调用不起作用 \_ 。 如果视频 pin 未处于停止状态并且返回状态 " \_ 无效设备状态"，则驱动程序应拒绝收到的设置呼叫 \_ \_ 。 在 GET 调用中，驱动程序应返回 "标志" 字段中的当前设置。
如果在配置文件的上下文中使用此控件，则该配置文件应充当质量模式的驱动程序提示。 此驱动程序可以根据所选的配置文件（例如，视频会议或高质量的视频录制），确定是根据所选的配置文件优化低延迟还是高质量。
> [!NOTE]
> \_ \_ \_ \_ 适用于 Windows 10 的 PROPSETID VIDCAP CAMERACONTROL 视频稳定性将会弃用。
下表介绍了标志功能。
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th>标志</th>
<th>描述</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><p>KSCAMERA_EXTENDEDPROP_VIDEOSTABILIZATION_OFF</p></td>
<td><p>这是必需的功能。 指定时，driver\MFT0. 中禁用数字视频抖动</p></td>
</tr>
<tr class="even">
<td><p>KSCAMERA_EXTENDEDPROP_VIDEOSTABILIZATION_ON</p></td>
<td><p>这是必需的功能。 指定时，将在 driver\MFT0 中启用数字视频抖动，并在驱动程序中设置默认的 overscan 填充设置。 此标志与自动和关闭标志互斥。</p></td>
</tr>
<tr class="odd">
<td><p>KSCAMERA_EXTENDEDPROP_VIDEOSTABILIZATION_AUTO</p></td>
<td><p>此功能是可选的。 如果指定此功能，则支持此类功能的驱动程序将确定是否应执行视频稳定性，并根据场景分析和捕获方案来确定要应用的稳定性。 此标志与 ON 和 OFF 标志互相排斥。</p></td>
</tr>
</tbody>
</table>
> [!NOTE]
> 根据实现，overscanned 缓冲区可能由驱动程序在内部或管道中分配。
如果驱动程序要分配 overscanned 缓冲区，驱动程序应同时播发常规媒体类型和 overscanned 媒体类型。 MFT0 应公布常规媒体类型。 在 MFT0 的输出媒体类型上设置常规媒体类型时，如果打开了视频稳定，则 MFT0 应从驱动程序将媒体类型作为其输入媒体类型来选择相应的 overscanned 媒体类型。 如果视频稳定处于关闭状态，则 MFT0 应选择常规媒体类型作为其输入媒体类型。 \_ \_ 如果在视频稳定打开时将 overscanned 媒体类型设置为其输出媒体类型，则 MFT0 应返回 MF E INVALIDMEDIATYPE。
如果 overscanned 缓冲区由驱动程序分配，则驱动程序和 MFT0 都应公布常规媒体类型。 MFT0 应为其输入媒体类型和输出媒体类型设置常规媒体类型。
为了支持基于视频抖动 (的效果，视频抖动在驱动程序和 MFT0) 中都没有完成，驱动程序和 MFT0 还必须公布 overscanned 媒体类型，而不考虑。 在这种情况下，驱动程序和 MFT0 都公开了 regular 和 overscanned 媒体类型。 以下规则将适用，以确保基于效果的和基于驱动程序 \\ MFT0 的视频抖动都能正常工作。
- 如果 overscanned 媒体类型设置为 MFT0 输出媒体类型，而基于驱动程序 \\ MFT0 的视频抖动处于开启，则 MFT0 应返回 MF \_ E \_ INVALIDMEDIATYPE。
- 如果将常规媒体类型设置为 "MFT0 output media type"，则应用程序应返回一个错误，该错误在基于视频稳定性的情况下尝试启用基于视频抖动的效果时，可能只需要 overscanned 媒体类型。
下表包含在使用视频抖动控制时 [KSCAMERA \_ EXTENDEDPROP \_ 标头](/windows-hardware/drivers/ddi/ksmedia/ns-ksmedia-tagkscamera_extendedprop_header) 结构字段的说明和要求。
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th>成员</th>
<th>说明</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><p>版本</p></td>
<td><p>这必须为1。</p></td>
</tr>
<tr class="even">
<td><p>PinId</p></td>
<td><p>必须是与视频 pin 关联的 Pin ID。</p></td>
</tr>
<tr class="odd">
<td><p>大小</p></td>
<td><p>这必须是 sizeof (KSCAMERA_EXTENDEDPROP_HEADER) + sizeof (KSCAMERA_EXTENDEDPROP_VALUE) 。</p></td>
</tr>
<tr class="even">
<td><p>结果</p></td>
<td><p>指示上一次设置操作的错误结果。 如果未执行任何设置操作，则此必须为0。</p></td>
</tr>
<tr class="odd">
<td><p>功能</p></td>
<td><p>这必须是前面定义的受支持 KSCAMERA_EXTENDEDPROP_VIDEOSTABILIZATION_XXX 标志的按位 "或"。</p></td>
</tr>
<tr class="even">
<td><p>Flags</p></td>
<td><p>这是一个读/写字段。 这可以是上面定义的 KSCAMERA_EXTENDEDPROP_VIDEOSTABILIZATION_XXX 标志之一。</p></td>
</tr>
</tbody>
</table>
## <a name="requirements"></a>要求
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td><p>标头</p></td>
<td>Ksmedia.h</td>
</tr>
</tbody>
</table>
| 26.892216 | 282 | 0.737475 | yue_Hant | 0.912436 |
57c67c235c70d7f5ade243264ac43857865d6856 | 781 | md | Markdown | auto-rename-container/README.md | decasteljau/waapi-midi-auto-map | 2a803dff574e3fd31323b7138e2fac91935b80ac | [
"Apache-2.0"
] | 4 | 2019-08-12T17:31:09.000Z | 2020-10-14T03:51:31.000Z | auto-rename-container/README.md | decasteljau/waapi-midi-auto-map | 2a803dff574e3fd31323b7138e2fac91935b80ac | [
"Apache-2.0"
] | null | null | null | auto-rename-container/README.md | decasteljau/waapi-midi-auto-map | 2a803dff574e3fd31323b7138e2fac91935b80ac | [
"Apache-2.0"
] | null | null | null | # auto-rename-container
Automatically rename a container based on the name of its children.
## Usage
### Add the command to Wwise
Refer to [Defining custom commands](https://www.audiokinetic.com/library/edge/?source=SDK&id=defining__custom__commands.html) in the Wwise SDK documentation.
### Example command definition
```json
{
"commands": [
{
"id": "ak.auto_rename_container",
"displayName": "Auto Rename Container",
"defaultShortcut": "Alt+R",
"program": "pyw",
"startMode": "SingleSelectionSingleProcess",
"args": "C:\\waapi-python-tools\\auto-rename-container",
"cwd": "",
"contextMenu": {
"basePath": "Add-ons"
}
}
]
}
``` | 26.931034 | 157 | 0.582586 | eng_Latn | 0.463821 |
57c6f576b160b10ee078420cf21be42d83a4b90b | 520 | md | Markdown | _cmhc/02306cc.md | lake-county-public-library/cmhc | 73c6957a5077e531064530bb4c1a46179094109c | [
"MIT"
] | null | null | null | _cmhc/02306cc.md | lake-county-public-library/cmhc | 73c6957a5077e531064530bb4c1a46179094109c | [
"MIT"
] | null | null | null | _cmhc/02306cc.md | lake-county-public-library/cmhc | 73c6957a5077e531064530bb4c1a46179094109c | [
"MIT"
] | null | null | null | ---
pid: 02306cc
label: Uncategorized
key: uncat
location:
keywords:
description: Dr. Relallack
named_persons:
rights: This photo is property of Lake County Civic Center Association.
creation_date:
ingest_date: '2021-03-30'
format: Photo
source: Scanned Negative
order: '2104'
layout: cmhc_item
thumbnail: "/img/derivatives/iiif/images/02306cc/full/250,/0/default.jpg"
full: "/img/derivatives/iiif/images/02306cc/full/1140,/0/default.jpg"
manifest: "/img/derivatives/iiif/02306cc/manifest.json"
collection: cmhc
---
| 24.761905 | 73 | 0.778846 | eng_Latn | 0.347165 |
57c754d5d6a8b12e3cd63178d5d34788ff05a42c | 113 | md | Markdown | photos/index2.md | securitymonster/securitymonster.github.io | 51f30485ee8d33db89d45b97a2d8f90c98ac1ab0 | [
"MIT"
] | null | null | null | photos/index2.md | securitymonster/securitymonster.github.io | 51f30485ee8d33db89d45b97a2d8f90c98ac1ab0 | [
"MIT"
] | null | null | null | photos/index2.md | securitymonster/securitymonster.github.io | 51f30485ee8d33db89d45b97a2d8f90c98ac1ab0 | [
"MIT"
] | null | null | null | ---
layout: page
title: Fotos
date: 2016-09-22T10:42:44+02:00
modified:
excerpt:
tags: []
image:
feature:
---
| 9.416667 | 31 | 0.654867 | fra_Latn | 0.304796 |
57c8ae809596eeb5911f3b013cc25945f02e9f51 | 60,159 | md | Markdown | SHHaveFun/SHHaveFun/App/Api/BingDic.md | FuthureCrane/SHHaveFun | f2731bf00c899e27bae51603401cbb10f4f8e275 | [
"MIT"
] | 2 | 2019-04-30T03:03:50.000Z | 2021-08-10T13:37:41.000Z | SHHaveFun/SHHaveFun/App/Api/BingDic.md | FuthureCrane/SHHaveFun | f2731bf00c899e27bae51603401cbb10f4f8e275 | [
"MIT"
] | 1 | 2019-05-05T10:47:12.000Z | 2019-05-07T03:10:11.000Z | SHHaveFun/SHHaveFun/App/Api/BingDic.md | FuthureCrane/SHHaveFun | f2731bf00c899e27bae51603401cbb10f4f8e275 | [
"MIT"
] | null | null | null | # 必应词典 #
- [词典](#dic)
- [翻译](#translation)
ps：必应词典在本地存有数据库，所以它的联想功能是直接在数据库中查找 —— [戳我下载 Android 数据库文件](https://github.com/jokermonn/-Api/blob/master/mircrosoft_bing_dic.db) 或 [戳我下载 wps 表格](https://github.com/jokermonn/-Api/blob/master/mircrosoft_bing_dic..xlsx)。**本地数据库中包含单词的基础默认翻译**
<h2 id="dic">词典</h2>
url：https://dict.bing.com.cn/api/http/v2/4154AA7A1FC54ad7A84A0236AA4DCAF3/en-us/zh-cn/
拼接参数：
- `q`：关键词
- `format`：返回格式。`application/json` 或 `application/xml`
url 示例：[`https://dict.bing.com.cn/api/http/v2/4154AA7A1FC54ad7A84A0236AA4DCAF3/en-us/zh-cn/?q=address&format=application/json`](https://dict.bing.com.cn/api/http/v2/4154AA7A1FC54ad7A84A0236AA4DCAF3/en-us/zh-cn/?q=address&format=application/json)
json 示例：
{
"LEX": {
"C_DEF": [
{
"DEF": "地址$$(信上的)称呼$$演说$$致辞$$姓名$$谈话$$话$$策略$$谈吐$$献殷勤$$行踪$$吆喝$$妙法$$口才$$求爱$$求亲$$寒喧$$正式请愿$$灵巧$$风度$$娴熟",
"POS": "n",
"SEN": [
{
"D": "(信上的)称呼,姓名;地址",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "地址;行踪",
"R": 0,
"STS": [
{
"DATE": "/Date(1336460400000-0700)/",
"ID": 0,
"ORAL": false,
"R": 0,
"READ": 0,
"S": {
"AD": null,
"COL": null,
"D": "He gave me the address.",
"IME": null,
"M": 0,
"SIG": null,
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "他给了我地址。",
"IME": null,
"M": 0,
"SIG": null,
"TG": null,
"URL": null,
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 0,
"WAD": null
}
],
"URL": null
},
{
"D": "致辞;寒喧;演说;正式请愿",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "话;演说;谈话;吆喝",
"R": 0,
"STS": [
{
"DATE": "/Date(1336460400000-0700)/",
"ID": 0,
"ORAL": false,
"R": 0,
"READ": 0,
"S": {
"AD": null,
"COL": null,
"D": "The latter part of this address was scarcely heard by Darcy.",
"IME": null,
"M": 0,
"SIG": null,
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "后半段话达西几乎没有听见。",
"IME": null,
"M": 0,
"SIG": null,
"TG": null,
"URL": null,
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 0,
"WAD": null
}
],
"URL": null
},
{
"D": "谈吐,风度",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "谈吐;口才",
"R": 0,
"STS": [
{
"DATE": "/Date(1336460400000-0700)/",
"ID": 0,
"ORAL": false,
"R": 0,
"READ": 0,
"S": {
"AD": null,
"COL": null,
"D": "Edward Ferrars was not recommended to their good opinion by any peculiar graces of person or address.",
"IME": null,
"M": 0,
"SIG": null,
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "爱德华·费拉尔斯得到她们的好评并不是由于他的人品或谈吐特别出众。",
"IME": null,
"M": 0,
"SIG": null,
"TG": null,
"URL": null,
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 0,
"WAD": null
}
],
"URL": null
},
{
"D": "妙法;策略;灵巧",
"R": 0,
"STS": [
{
"DATE": "/Date(1336460400000-0700)/",
"ID": 0,
"ORAL": false,
"R": 0,
"READ": 0,
"S": {
"AD": null,
"COL": null,
"D": "It was now that I applauded my perseverance and address.",
"IME": null,
"M": 0,
"SIG": null,
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "我自己赞美我的耐性同我的妙法。",
"IME": null,
"M": 0,
"SIG": null,
"TG": null,
"URL": null,
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 0,
"WAD": null
}
],
"URL": null
},
{
"D": "求爱,献殷勤",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "灵巧,娴熟",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "求亲",
"R": 0,
"STS": [
{
"DATE": "/Date(1336460400000-0700)/",
"ID": 0,
"ORAL": false,
"R": 0,
"READ": 0,
"S": {
"AD": null,
"COL": null,
"D": "I'll fairly own that it was I that instructed my girls to encourage our landlord's addresses.",
"IME": null,
"M": 0,
"SIG": null,
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "我说句公道话,原是我叫女儿们鼓励我们的房东求亲的。",
"IME": null,
"M": 0,
"SIG": null,
"TG": null,
"URL": null,
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 0,
"WAD": null
}
],
"URL": null
}
]
},
{
"DEF": "解决$$讲话$$处理$$处理(问题等)$$称呼$$满足(需求等)$$发言$$应付$$说$$【商业】交$$引导$$委托$$着手处理$$钻研$$倾述$$在…上写姓名住址$$向…致意$$给…讲话$$向…演说$$向…求爱$$向…献殷勤$$对…说$$引见$$【法律】(立法部门)请求撤销(不适任法官的)职务$$【高尔夫球】瞄准",
"POS": "v",
"SEN": [
{
"D": "钻研;解决,处理,着手处理",
"R": 0,
"STS": [
{
"DATE": "/Date(1336460400000-0700)/",
"ID": 0,
"ORAL": false,
"R": 0,
"READ": 0,
"S": {
"AD": null,
"COL": null,
"D": "We addressed ourselves vigorously to this problem.",
"IME": null,
"M": 0,
"SIG": null,
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "我们奋力钻研这一问题。",
"IME": null,
"M": 0,
"SIG": null,
"TG": null,
"URL": null,
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 0,
"WAD": null
}
],
"URL": null
},
{
"D": "在…上写姓名住址;称呼;向…致意",
"R": 0,
"STS": [
{
"DATE": "/Date(1336460400000-0700)/",
"ID": 0,
"ORAL": false,
"R": 0,
"READ": 0,
"S": {
"AD": null,
"COL": null,
"D": "How should one address a senator?",
"IME": null,
"M": 0,
"SIG": null,
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "如何称呼一位议院的参议员?",
"IME": null,
"M": 0,
"SIG": null,
"TG": null,
"URL": null,
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 0,
"WAD": null
}
],
"URL": null
},
{
"D": "给…讲话;向…演说,向…求爱,向…献殷勤",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "说,对…说;讲话,发言;倾述",
"R": 0,
"STS": [
{
"DATE": "/Date(1336460400000-0700)/",
"ID": 0,
"ORAL": false,
"R": 0,
"READ": 0,
"S": {
"AD": null,
"COL": null,
"D": "He addressed the strong, silent shareholder.",
"IME": null,
"M": 0,
"SIG": null,
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "他向那个坚强沉默的股东说。",
"IME": null,
"M": 0,
"SIG": null,
"TG": null,
"URL": null,
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 0,
"WAD": null
}
],
"URL": null
},
{
"D": "应付,处理(问题等)",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "满足(需求等)",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "引导,引见",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "【商业】交,委托",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "【法律】(立法部门)请求撤销(不适任法官的)职务",
"R": 0,
"STS": [
{
"DATE": "/Date(1336460400000-0700)/",
"ID": 0,
"ORAL": false,
"R": 0,
"READ": 0,
"S": {
"AD": null,
"COL": null,
"D": "We do not address the unforgettable Gods.",
"IME": null,
"M": 0,
"SIG": null,
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "我们没有请求值得铭心刻骨的众神的帮助。",
"IME": null,
"M": 0,
"SIG": null,
"TG": null,
"URL": null,
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 0,
"WAD": null
}
],
"URL": null
},
{
"D": "【高尔夫球】瞄准",
"R": 0,
"STS": null,
"URL": null
}
]
},
{
"DEF": null,
"POS": "web",
"SEN": [
{
"D": "住址",
"R": 130854,
"STS": null,
"URL": "http://www.360doc.com/content/05/1025/15/1275_23749.shtml"
},
{
"D": "通讯地址",
"R": 40287,
"STS": null,
"URL": "http://zhidao.baidu.com/question/133764336.html"
},
{
"D": "联系地址",
"R": 4631,
"STS": null,
"URL": "http://www.tzsunrui.com.cn/"
},
{
"D": "公司地址",
"R": 1769,
"STS": null,
"URL": "http://edu.ebay.cn/tips/201110246866.html"
},
{
"D": "联络地址",
"R": 1280,
"STS": null,
"URL": "http://www.oh100.com/a/201107/2887.html"
},
{
"D": "详细地址",
"R": 837,
"STS": null,
"URL": "http://www.xici.net/d108454468.htm"
},
{
"D": "演说",
"R": 652,
"STS": null,
"URL": "http://wenku.baidu.com/view/5c993ed5360cba1aa811daec.html"
}
]
}
],
"HW": {
"DEF": "地址$$解决$$讲话$$处理$$处理(问题等)$$(信上的)称呼$$称呼$$演说$$满足(需求等)$$致辞$$发言$$姓名$$应付$$谈话$$话$$说$$【商业】交$$策略$$引导$$委托$$谈吐$$着手处理$$献殷勤$$行踪$$钻研$$倾述$$吆喝$$妙法$$口才$$求爱$$求亲$$在…上写姓名住址$$向…致意$$给…讲话$$向…演说$$向…求爱$$向…献殷勤$$对…说$$寒喧$$正式请愿$$灵巧$$引见$$风度$$娴熟$$【法律】(立法部门)请求撤销(不适任法官的)职务$$【高尔夫球】瞄准",
"SIG": "3C7B74A40CD8FE4F165330F051C7C4BF",
"V": "address"
},
"H_DEF": [
{
"DEF": null,
"POS": "n",
"SEN": [
{
"D": "the number, street name, and other information that describes where a building is or where somebody lives",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "the address of a person or organization when written on a letter or an item of mail",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "a formal speech or report",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "a number that specifies a location in a computer's memory",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "a statement of opinions or desires sent to the sovereign by either or both of the Houses of Parliament",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "a formal speech given by someone to a group of people, especially as part of an important occasion",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "the name of the place where you live or work, including the house or office number and the name of the street, area, and town. It may also include a set of numbers and letters, called a postcode in British English and a zip code in American English",
"R": 0,
"STS": null,
"URL": null
}
]
},
{
"DEF": null,
"POS": "np",
"SEN": [
{
"D": "attention paid to somebody that is intended as courtship",
"R": 0,
"STS": null,
"URL": null
}
]
},
{
"DEF": null,
"POS": "v",
"SEN": [
{
"D": "to write or print on an item of mail details of where it is to be delivered",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "to say something to somebody, or make a speech to an audience",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "to use the proper name or title in speaking or writing to somebody",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "to set about doing some task",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "to face up to and deal with a problem or issue",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "to stand facing a dance partner or an archery target",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "to take up the correct stance beside a golf ball before hitting it",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "to write the name and address of a particular person or organization on an envelope, package, etc.",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "to officially tell a particular person or organization your complaints, questions, or comments",
"R": 0,
"STS": null,
"URL": null
},
{
"D": "to speak publicly to a group of people",
"R": 0,
"STS": null,
"URL": null
}
]
}
],
"INF": [
{
"IE": "addresses",
"T": "pl"
},
{
"IE": "addressed",
"T": "pp"
},
{
"IE": "addressing",
"T": "prp"
},
{
"IE": "addresses",
"T": "3pps"
},
{
"IE": "address",
"T": "s"
},
{
"IE": "addresses",
"T": "prt"
},
{
"IE": "addressed",
"T": "pt"
}
],
"LCS": [
{
"LC": [
{
"T1": "address",
"T2": "issue"
},
{
"T1": "address",
"T2": "problem"
},
{
"T1": "give",
"T2": "address"
},
{
"T1": "address",
"T2": "meeting"
},
{
"T1": "address",
"T2": "audience"
},
{
"T1": "deliver",
"T2": "address"
},
{
"T1": "note",
"T2": "address"
},
{
"T1": "address",
"T2": "Congress"
},
{
"T1": "address",
"T2": "crowd"
},
{
"T1": "address",
"T2": "appeal"
},
{
"T1": "address",
"T2": "rally"
},
{
"T1": "address",
"T2": "nation"
},
{
"T1": "address",
"T2": "assembly"
},
{
"T1": "address",
"T2": "envelope"
},
{
"T1": "address",
"T2": "Parliament"
}
],
"RELA": "v.+n."
},
{
"LC": [
{
"T1": "same",
"T2": "address"
},
{
"T1": "inaugural",
"T2": "address"
},
{
"T1": "final",
"T2": "address"
}
],
"RELA": "adj.+n."
}
],
"PHRASE": [
{
"DEF": "实际地址",
"SIG": null,
"V": "actual address"
},
{
"DEF": "通讯花名册",
"SIG": null,
"V": "address book"
},
{
"DEF": "地址代码",
"SIG": null,
"V": "address code"
},
{
"DEF": "地址字段地址部分",
"SIG": null,
"V": "address field"
},
{
"DEF": "地址标记",
"SIG": null,
"V": "address mark"
},
{
"DEF": "地址存储器",
"SIG": null,
"V": "address memory"
},
{
"DEF": "基址",
"SIG": null,
"V": "base address"
},
{
"DEF": "计算地址",
"SIG": null,
"V": "calculated address"
},
{
"DEF": "浮动地址",
"SIG": null,
"V": "floating address"
},
{
"DEF": "转发地址",
"SIG": null,
"V": "forwarding address"
},
{
"DEF": "标识地址",
"SIG": null,
"V": "home address"
},
{
"DEF": "立即地址",
"SIG": null,
"V": "immediate address"
},
{
"DEF": "地址",
"SIG": null,
"V": "mailing address"
},
{
"DEF": "推定地址",
"SIG": null,
"V": "presumptive address"
},
{
"DEF": "基准地址",
"SIG": null,
"V": "reference address"
},
{
"DEF": "区域地址",
"SIG": null,
"V": "regional address"
},
{
"DEF": "绝对地址",
"SIG": null,
"V": "specific address"
},
{
"DEF": "电报挂号",
"SIG": null,
"V": "telegraphic address"
},
{
"DEF": "二地址",
"SIG": null,
"V": "two address"
},
{
"DEF": "虚拟地址",
"SIG": null,
"V": "virtual address"
}
],
"PRON": [
{
"L": "US",
"V": "'ædres"
},
{
"L": "UK",
"V": "ə'dres"
}
],
"THES": [
{
"A": [
"ignore"
],
"POS": "v",
"S": [
"direct",
"deliver",
"forward",
"speak",
"lecture",
"talk",
"tackle",
"deal with"
]
},
{
"A": null,
"POS": "n",
"S": [
"speech",
"discourse",
"report",
"statement"
]
}
]
},
"MT": null,
"Q": "address",
"SENT": {
"COUNT": 10,
"OFFSET": 0,
"ST": [
{
"DATE": "/Date(1384975564000-0800)/",
"ID": 606158,
"ORAL": false,
"R": 63050,
"READ": 69,
"S": {
"AD": "{1#dàn$1} {2#tā$2} {3#hái$3} {4#shì$4} {5#tóng yì$5} {6#le$6} {7#,$7} {8#tā$8} {9#jiù$9} {10#jì xià$10} {11#le$11} {12#tā$12} {13#de$13} {14#míng zì$14} {15#hé$15} {##*{16#dì zhǐ$16}*$$} {17#。$17}",
"COL": null,
"D": "{1#但$1}{2#她$2}{3#还$3}{4#是$4}{5#同意$5}{6#了$6}{7#，$7}{8#他$8}{9#就$9}{10#记下$10}{11#了$11}{12#她$12}{13#的$13}{14#名字$14}{15#和$15}{##*{16#地址$16}*$$}{17#。$17}",
"IME": null,
"M": 0,
"SIG": "7F05BBC94BDEE5DB2585BB40571BD116",
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "{12#She$12} {5#acquiesced$5}{7#,$7} {1#however$1}, {15#and$15} {8#he$8} took {2#her$2} {14#name$14} {15#and$15} {#*{16#address$16}*$}{17#.$17}",
"IME": null,
"M": 17,
"SIG": "BA56B3B550CFA51E6CDA3DEC4FE592F5",
"TG": null,
"URL": null,
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 30,
"WAD": null
},
{
"DATE": "/Date(1384975527000-0800)/",
"ID": 947925,
"ORAL": false,
"R": 60703,
"READ": 55,
"S": {
"AD": "{1#wǒ$1} {2#shì$2} {3#zài$3} {4#xīn qíng$4} {5#jī dòng$5} {6#de$6} {7#qíng kuàng$7} {8#xià qù$8} {9#lǚ xíng$9} {10#duì$10} {11#měi guó$11} {12#guó huì$12} {##*{13#yǎn shuō$13}*$$} {14#de$14} {15#yāo yuē$15} {16#de$16} {17#。$17}",
"COL": null,
"D": "{1#我$1}{2#是$2}{3#在$3}{4#心情$4}{5#激动$5}{6#的$6}{7#情况$7}{8#下去$8}{9#履行$9}{10#对$10}{11#美国$11}{12#国会$12}{##*{13#演说$13}*$$}{14#的$14}{15#邀约$15}{16#的$16}{17#。$17}",
"IME": null,
"M": 0,
"SIG": "6C47D4B54FDABC1EFD47FB2E1443AB5A",
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "{8#It$8} {2#was$2} with {4#heart$4}-{5#stirring$5} that {1#I$1} {9#fulfilled$9} {3#the$3} {15#invitation$15} {10#to$10} {#*{13#address$13}*$} the {12#Congress$12} {6#of$6} the {11#United States$11}{17#.$17}",
"IME": null,
"M": 17,
"SIG": "04BBFCC3A4C199C17DF5908E958BB378",
"TG": null,
"URL": null,
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 37,
"WAD": null
},
{
"DATE": "/Date(1384975535000-0800)/",
"ID": 947745,
"ORAL": false,
"R": 60704,
"READ": 90,
"S": {
"AD": "{1#guò lái$1} {2#yī$2} {3#liàng$3} {4#chū zū qì chē$4} {5#,$5} {6#wǒ$6} {7#shàng$7} {8#le$8} {9#chē$9} {10#,$10} {11#gào su$11} {12#sī jī$12} {13#wǒ$13} {14#de$14} {##*{15#zhù zhǐ$15}*$$} {16#。$16}",
"COL": null,
"D": "{1#过来$1}{2#一$2}{3#辆$3}{4#出租汽车$4}{5#，$5}{6#我$6}{7#上$7}{8#了$8}{9#车$9}{10#，$10}{11#告诉$11}{12#司机$12}{13#我$13}{14#的$14}{##*{15#住址$15}*$$}{16#。$16}",
"IME": null,
"M": 0,
"SIG": "9DC5E0C210ABB47583C9E23CA223CB57",
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "{2#A$2} {4#taxi$4} {1#came$1} along {5#and$5} {6#I$6} got in and {11#gave$11} the {12#driver$12} the {#*{15#address$15}*$} {14#of$14} {13#my$13} flat{16#.$16}",
"IME": null,
"M": 17,
"SIG": "A5E7E762923FF069843CEE6EDAAD7F05",
"TG": null,
"URL": null,
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 34,
"WAD": null
},
{
"DATE": "/Date(1384975524000-0800)/",
"ID": 335200,
"ORAL": false,
"R": 65535,
"READ": 59,
"S": {
"AD": "{1#duì$1} {2#yī gè$2} {3#yìn dì ān rén$3} {4#zhí$4} {5#hū$5} {6#qí$6} {7#míng$7} {8#,$8} {9#huò$9} {10#zhí jiē$10} {11#xún wèn$11} {12#duì fāng$12} {13#de$13} {14#míng zì$14} {15#,$15} {16#zhè$16} {17#dōu$17} {18#bèi$18} {19#shì wéi$19} {20#táng tū$20} {21#wú lǐ$21} {22#de$22} {23#xíng wéi$23} {24#。$24}",
"COL": null,
"D": "{1#对$1}{2#一个$2}{3#印第安人$3}{4#直$4}{5#呼$5}{6#其$6}{7#名$7}{8#，$8}{9#或$9}{10#直接$10}{11#询问$11}{12#对方$12}{13#的$13}{14#名字$14}{15#，$15}{16#这$16}{17#都$17}{18#被$18}{19#视为$19}{20#唐突$20}{21#无礼$21}{22#的$22}{23#行为$23}{24#。$24}",
"IME": null,
"M": 0,
"SIG": "BE3BE5A73695C35E6389F655052CBC2D",
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "It {17#would$17} {18#be$18} {19#esteemed$19} {2#an$2} {23#act$23} {13#of$13} {21#rudeness$21} {1#to$1} {#*address*$} an {3#Indian$3} by {6#his$6} personal {14#name$14}{8#,$8} {9#or$9} to {11#inquire$11} his {7#name$7} {4#directly$4} from himself{24#.$24}",
"IME": null,
"M": 17,
"SIG": "40D6E58EB3A27EE46FA1E6F1E541F8E9",
"TG": null,
"URL": null,
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 50,
"WAD": null
},
{
"DATE": "/Date(1384975526000-0800)/",
"ID": 329212,
"ORAL": false,
"R": 65535,
"READ": 65,
"S": {
"AD": "{1#hàn$1} {2#mí$2} {3#ěr$3} {4#dēng$4} {5#hú tòng$5} {6#hái$6} {7#méi yǒu$7} {8#dào$8} {9#,$9} {10#tā$10} {11#yǐ jīng$11} {12#gǎi biàn$12} {13#zhǔ yì$13} {14#,$14} {15#jiào$15} {16#le$16} {17#yī$17} {18#bù$18} {19#mǎ chē$19} {20#,$20} {21#gào su$21} {22#mǎ fū$22} {23#shàng$23} {24#wēi$24} {25#sī$25} {26#dá lǐ yà$26} {23#dà jiē$23} {28#yī gè$28} {##*{29#dì fāng$29}*$$} {30#qù$30} {31#。$31}",
"COL": null,
"D": "{1#汉$1}{2#弥$2}{3#尔$3}{4#登$4}{5#胡同$5}{6#还$6}{7#没有$7}{8#到$8}{9#，$9}{10#他$10}{11#已经$11}{12#改变$12}{13#主意$13}{14#，$14}{15#叫$15}{16#了$16}{17#一$17}{18#部$18}{19#马车$19}{20#，$20}{21#告诉$21}{22#马夫$22}{23#上$23}{24#威$24}{25#斯$25}{26#达里亚$26}{23#大街$23}{28#一个$28}{##*{29#地方$29}*$$}{30#去$30}{31#。$31}",
"IME": null,
"M": 0,
"SIG": "1DF1CF6976A6C52B1C415332CA3ED092",
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "{10#He$10} {11#had$11} {7#not$7} {8#reached$8} {1#Hamilton$1} Terrace before he {12#changed$12} his {13#mind$13}{9#,$9} and hailing {28#a$28} {19#cab$19}{14#,$14} {21#gave$21} the {22#driver$22} an {#*{29#address$29}*$} {3#in$3} Wistaria {23#Avenue$23}{31#.$31}",
"IME": null,
"M": 17,
"SIG": "9C7EBD8162F6C5DA8A3F15230A7D1B2A",
"TG": null,
"URL": null,
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 57,
"WAD": null
},
{
"DATE": "/Date(1384975507000-0800)/",
"ID": 318169,
"ORAL": false,
"R": 65535,
"READ": 89,
"S": {
"AD": "{1#wǒ$1} {2#zhī dào$2} {3#tā$3} {4#de$4} {##*{5#dì zhǐ$5}*$$} {6#,$6} {7#dàn shì$7} {8#wǒ$8} {9#xiàn zài$9} {10#xiǎng$10} {11#bù$11} {12#qǐ lái$12} {13#。$13}",
"COL": null,
"D": "{1#我$1}{2#知道$2}{3#他$3}{4#的$4}{##*{5#地址$5}*$$}{6#，$6}{7#但是$7}{8#我$8}{9#现在$9}{10#想$10}{11#不$11}{12#起来$12}{13#。$13}",
"IME": null,
"M": 0,
"SIG": "A1021CD3E8DBF00C0C1548AC0DF82DBE",
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "{1#I$1} {2#knew$2} {3#his$3} {#*{5#address$5}*$}{6#,$6} {7#but$7} {8#I$8} {11#cannot$11} {10#think$10} {4#of$4} {9#it$9} at the moment{13#.$13}",
"IME": null,
"M": 17,
"SIG": "47A307BCBF3FAB9531FFC48A168BF2DF",
"TG": null,
"URL": "http://learning.sohu.com/20040906/n221901517.shtml",
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 28,
"WAD": null
},
{
"DATE": "/Date(1384975564000-0800)/",
"ID": 260637,
"ORAL": true,
"R": 65535,
"READ": 100,
"S": {
"AD": "{1#fēng pí$1} {2#shàng$2} {3#méi yǒu$3} {4#míng zì$4} {5#hé$5} {##*{6#dì zhǐ$6}*$$} {7#。$7}",
"COL": null,
"D": "{1#封皮$1}{2#上$2}{3#没有$3}{4#名字$4}{5#和$5}{##*{6#地址$6}*$$}{7#。$7}",
"IME": null,
"M": 0,
"SIG": "11B44689B17EC6EDF54CF69EF5464DE6",
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "There was {3#no$3} {4#name$4} {5#or$5} {#*{6#address$6}*$} {2#on$2} the {1#front$1}{7#.$7}",
"IME": null,
"M": 1,
"SIG": "6ED5E69B5BD37FB8E71AD2AD77D4F0C1",
"TG": null,
"URL": "http://article.yeeyan.org/compare/163378/125808",
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 17,
"WAD": null
},
{
"DATE": "/Date(1384975547000-0800)/",
"ID": 299165,
"ORAL": false,
"R": 65535,
"READ": 95,
"S": {
"AD": "{1#zhè shí$1} {2#ài dé huá zī$2} {3#zhàn$3} {4#qǐ shēn$4} {5#,$5} {6#duì$6} {7#shí èr$7} {8#rén$8} {##*{9#jiǎng huà$9}*$$} {10#。$10}",
"COL": null,
"D": "{1#这时$1}{2#爱德华兹$2}{3#站$3}{4#起身$4}{5#，$5}{6#对$6}{7#十二$7}{8#人$8}{##*{9#讲话$9}*$$}{10#。$10}",
"IME": null,
"M": 0,
"SIG": "10A1AC6515147A27EB55CD5E45D77F37",
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "{1#Then$1} {2#Edwards$2} {3#got$3} {6#to$6} his {4#feet$4} to {#*{9#address$9}*$} the {7#twelve$7}{10#.$10}",
"IME": null,
"M": 1,
"SIG": "EAFEA7CB980AD370F9AA7C1B059C8BB8",
"TG": null,
"URL": "http://bbs.rtucn.com/ipb/index.php?act=Print&client=html&f=14&t=17319",
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 21,
"WAD": null
},
{
"DATE": "/Date(1384975530000-0800)/",
"ID": 60713,
"ORAL": false,
"R": 65535,
"READ": 68,
"S": {
"AD": "{1#wǒ$1} {2#de$2} {3#IP$3} {##*{4#dì zhǐ$4}*$$} {5#xiǎn shì$5} {6#de$6} {7#bú shi$7} {8#yuán lái$8} {9#de$9} {10#chéng shì$10} {11#,$11} {12#ér shì$12} {13#hé$13} {14#tā$14} {15#tóng$15} {16#yī gè$16} {17#chéng shì$17} {18#。$18}",
"COL": null,
"D": "{1#我$1}{2#的$2}{3#IP$3}{##*{4#地址$4}*$$}{5#显示$5}{6#的$6}{7#不是$7}{8#原来$8}{9#的$9}{10#城市$10}{11#，$11}{12#而是$12}{13#和$13}{14#他$14}{15#同$15}{16#一个$16}{17#城市$17}{18#。$18}",
"IME": null,
"M": 0,
"SIG": "2EF93DAB347F412284BC4CEA1FDAB007",
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "{1#My$1} {3#IP$3} {#*{4#address$4}*$} is {5#displayed$5} is {7#not$7} {2#the$2} {8#original$8} {17#city$17}{11#,$11} {12#but$12} {15#with$15} {14#him$14} in {16#a$16} {10#city$10}{18#.$18}",
"IME": null,
"M": 1,
"SIG": "23E4C7B7984B25690B2E63FD96956552",
"TG": null,
"URL": "http://www.dota123.com/shuihuzhuan/shuihuchuan-news/huaqiang-shier.html",
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 36,
"WAD": null
},
{
"DATE": "/Date(1384975527000-0800)/",
"ID": 284354,
"ORAL": false,
"R": 65535,
"READ": 89,
"S": {
"AD": "{1#wǒ$1} {2#zhī dào$2} {3#tā$3} {4#de$4} {##*{5#dì zhǐ$5}*$$} {6#,$6} {7#dàn$7} {8#wǒ$8} {9#cǐ kè$9} {10#bù$10} {11#jì dé$11} {12#le$12} {13#。$13}",
"COL": null,
"D": "{1#我$1}{2#知道$2}{3#他$3}{4#的$4}{##*{5#地址$5}*$$}{6#，$6}{7#但$7}{8#我$8}{9#此刻$9}{10#不$10}{11#记得$11}{12#了$12}{13#。$13}",
"IME": null,
"M": 0,
"SIG": "7B749D031E050FC2F8571B7D4A893E76",
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "{1#I$1} {2#know$2} {3#his$3} {#*{5#address$5}*$}{6#,$6} {7#but$7} {8#I$8} {10#cannot$10} think {4#of$4} it at the {9#moment$9}{13#.$13}",
"IME": null,
"M": 17,
"SIG": "73B44D0AA49F7AEF30E3B3EAE9A59110",
"TG": null,
"URL": "http://www.uuzone.com/blog/any_time/85619.htm",
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 28,
"WAD": null
}
],
"TOTAL": 30100
},
"SUGG": {
"AC": null,
"PH": [
{
"DEF": "地址$$称呼$$演说$$处理$$致辞$$满足$$姓名$$应付$$谈吐$$交$$委托$$引导$$寒喧$$正式请愿$$风度$$求爱$$献殷勤$$灵巧$$娴熟$$在…上写姓名住址$$向…致意$$引见$$给…讲话$$向…演说$$向…求爱$$向…献殷勤$$请求撤销职务$$瞄准",
"SIG": "5E4DA50643DCD624689B005E9579BDF2",
"V": "addressed"
},
{
"DEF": "地址$$称呼$$演说$$处理$$致辞$$满足$$姓名$$应付$$谈吐$$交$$委托$$引导$$寒喧$$正式请愿$$风度$$求爱$$献殷勤$$灵巧$$娴熟$$在…上写姓名住址$$向…致意$$引见$$给…讲话$$向…演说$$向…求爱$$向…献殷勤$$请求撤销职务$$瞄准",
"SIG": "0681CFAC2C48B0A4BC6E432D9C203202",
"V": "addresses"
},
{
"DEF": "议院答辞$$总统咨文$$撤职请求",
"SIG": "748D7B0FE14F2D5C5A40D5E9465ADBCF",
"V": "the Address"
},
{
"DEF": "相并,并肩;并列;并排;看齐",
"SIG": "C0228D666028D4907D5C05D2F7BA5ADA",
"V": "abreast"
},
{
"DEF": "逮捕$$阻止$$抑制$$拘捕$$停止$$扣留$$吸引$$拘留$$止住$$收押$$制动",
"SIG": "145CF552B5ED6EAC8D1EF0558970F7B3",
"V": "arrest"
}
],
"PY": null,
"SP": null
}
}
解析：
- `LEX`
- `C_DEF`：英-汉
- `POS`：词性。PS：若该值为 `web`，则是必应词典中的`互联网释义`的内容
- `SEN`：
- `D`：释义
- `R`：???
- `STS`
- `S`
- `D`：例句
- `T`
- `D`：例句翻译
- `URL`：参考链接
- `H_DEF`：英-英
- `POS`：词性。PS：若该值为 `web`，则是必应词典中的`互联网释义`的内容
- `SEN`：
- `D`：例句
- `URL`：参考链接
- `THES`：同义词和反义词
- `A`：反义词列表
- `POS`：词性
- `S`：同义词列表
- `PRON`：音标
- `L`：地区，取 `US` 或 `UK`
- `V`：音标
- `PHRASE`：词组列表
- `DEF`：词组翻译
- `SIG`：???
- `V`：词组
- `INF`：其他形式
- `IE`：形式
- `T`：什么式，取 `pl`(复数)、`pp`(过去分词)、`prp`(现在分词)、`3pps`(第三人称单数)、`s`(原型)、`prt`(现在式)、`pt`(过去式)
- `SENT`：例句
- `COUNT`：数量
- `OFFSET`：分页
- `ST`
- `S`：例句翻译信息
- `AD`：拼音
- `D`：例句翻译
- `T`：例句信息
- `D`：例句
<h2 id="translation">翻译</h2>
url：https://dict.bing.com.cn/api/http/v2/4154AA7A1FC54ad7A84A0236AA4DCAF3/en-us/zh-cn/
拼接参数：
- `q`：查询内容，使用 `+` 将多个单词连接起来
- `format`：返回内容格式。`application/xml` 或 `application/json`
url 示例：[`https://dict.bing.com.cn/api/http/v2/4154AA7A1FC54ad7A84A0236AA4DCAF3/en-us/zh-cn/?q=merry+me&format=application/json`](https://dict.bing.com.cn/api/http/v2/4154AA7A1FC54ad7A84A0236AA4DCAF3/en-us/zh-cn/?q=merry+me&format=application/json)
json 示例：
{
"LEX": {
"C_DEF": [
{
"DEF": null,
"POS": "web",
"SEN": [
{
"D": "等你愿意",
"R": 21,
"STS": null,
"URL": "http://tw.knowledge.yahoo.com/question/question?qid=1306070310435"
},
{
"D": "我嫁给你",
"R": 4,
"STS": null,
"URL": "http://blog.yam.com/jamie690526/article/41776830"
},
{
"D": "珍宝箱",
"R": 3,
"STS": null,
"URL": "http://www.topbester.com/ebook/view/8163.html"
},
{
"D": "爱戴",
"R": 2,
"STS": null,
"URL": "http://www.aiyae.cn/fashion/ny/bra/"
},
{
"D": "败香心得",
"R": 2,
"STS": null,
"URL": "http://www.xici.net/d139286593.htm"
},
{
"D": "麦瑞蜜",
"R": 2,
"STS": null,
"URL": "http://www.people.com.cn/h/2011/0721/c25408-3243172348.html"
},
{
"D": "愤怒的胖子",
"R": 1,
"STS": null,
"URL": "http://www.3sir.com/3s/i9e-1c-7a-ac-4d-0d-aa-0d-4e-cb-3d-db-2e-dc-eb-1b-7c-cb-ac-1b-r.html"
}
]
}
],
"HW": {
"DEF": null,
"SIG": "C1C9F0999D7018DFE163908D0098A266",
"V": "merry me"
},
"H_DEF": null,
"INF": null,
"LCS": null,
"PHRASE": null,
"PRON": null,
"THES": null
},
"MT": null,
"Q": "merry me",
"SENT": {
"COUNT": 10,
"OFFSET": 0,
"ST": [
{
"DATE": "/Date(1384975541000-0800)/",
"ID": 8203258,
"ORAL": true,
"R": 47998,
"READ": 80,
"S": {
"AD": "{1#jià gěi$1} {##*{2#wǒ$2}*$$} {3#,$3} {4#zhū lì yè$4} {5#。$5} {6#nǐ$6} {7#bù$7} {8#zài$8} {9#gū dú$9} {10#le$10} {11#。$11}",
"COL": null,
"D": "{1#嫁给$1}{##*{2#我$2}*$$}{3#，$3}{4#朱丽叶$4}{5#。$5}{6#你$6}{7#不$7}{8#在$8}{9#孤独$9}{10#了$10}{11#。$11}",
"IME": null,
"M": 0,
"SIG": "9DE84C6BED3585184DFD7610ED225F54",
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "{#*merry*$} {#*{2#me$2}*$}{3#,$3} {4#juliet$4}{5#.$5} {6#you$6}'ll {7#never$7} have {8#to$8} been {9#alone$9}{11#.$11}",
"IME": null,
"M": 1,
"SIG": "3A0B6F93E75460F671619266251EEE5F",
"TG": null,
"URL": "http://blog.sina.com.cn/s/blog_5e3f02650100cajw.html",
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 24,
"WAD": null
},
{
"DATE": "/Date(1384975544000-0800)/",
"ID": 698601,
"ORAL": false,
"R": 62303,
"READ": 84,
"S": {
"AD": "{1#tā$1} {2#fù mǔ$2} {3#bù$3} {4#yǔn xǔ$4} {##*{5#wǒ$5}*$$} {6#gēn$6} {7#tā$7} {8#jié hūn$8} {9#。$9}",
"COL": null,
"D": "{1#她$1}{2#父母$2}{3#不$3}{4#允许$4}{##*{5#我$5}*$$}{6#跟$6}{7#她$7}{8#结婚$8}{9#。$9}",
"IME": null,
"M": 0,
"SIG": "6F5BAC7FF01FDA572750EA5869382BA7",
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "{1#Her$1} {2#parents$2} would {3#not$3} {4#permit$4} her {6#to$6} {#*merry*$} {#*{5#me$5}*$}{9#.$9}",
"IME": null,
"M": 17,
"SIG": "584233065B2457389F18A1981D0FF558",
"TG": null,
"URL": "http://www.kuxue.com/201106/532.htm",
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 19,
"WAD": null
},
{
"DATE": "/Date(1384975535000-0800)/",
"ID": 17486916,
"ORAL": true,
"R": 10693,
"READ": 100,
"S": {
"AD": "{1#jià gěi$1} {2#wǒ$2} {##*{3#ba$3}*$$} {4#。$4} {##*{5#wǒ$5}*$$} {6#huì$6} {7#gěi$7} {8#nǐ$8} {9#xìng fú$9} {10#de$10} {11#。$11} {12#($12} {13#dì$13} {14#jiè zhi$14} {15#hé$15} {16#)$16}",
"COL": null,
"D": "{1#嫁给$1}{2#我$2}{##*{3#吧$3}*$$}{4#。$4}{##*{5#我$5}*$$}{6#会$6}{7#给$7}{8#你$8}{9#幸福$9}{10#的$10}{11#。$11}{12#（$12}{13#递$13}{14#戒指$14}{15#盒$15}{16#）$16}",
"IME": null,
"M": 0,
"SIG": "EA84E70265D2222B2E8992D5EA522CBF",
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "Would {8#you$8} {#*{3#merry$3}*$} {#*{5#me$5}*$}? {2#I$2} swear we {6#will$6} be {9#happy$9}{4#.$4} {12#($12}{13#pass$13} {10#the$10} {14#ring$14} {15#box$15}{4#.$4} {16#)$16}",
"IME": null,
"M": 1,
"SIG": "BFEF271A83D0D0C94A5B803B322815D8",
"TG": null,
"URL": "http://zhidao.baidu.com/question/184842837.html",
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 35,
"WAD": null
},
{
"DATE": "/Date(1384975514000-0800)/",
"ID": 739601,
"ORAL": true,
"R": 62005,
"READ": 87,
"S": {
"AD": "{1#shì$1} {2#shí hou$2} {3#qìng zhù$3} {4#zhè ge$4} {5#wéi yī$5} {6#yǒu$6} {7#kě néng$7} {8#bǐ$8} {##*{9#wǒ$9}*$$} {10#hái$10} {11#ài$11} {12#nǐ$12} {13#de$13} {14#rén$14} {15#de$15} {16#shēng rì$16} {17#le$17} {18#。$18} {19#shèng dàn$19} {##*{20#kuài lè$20}*$$} {21#,$21} {22#wǒ$22} {23#qīn ài de$23} {24#。$24}",
"COL": null,
"D": "{1#是$1}{2#时候$2}{3#庆祝$3}{4#这个$4}{5#唯一$5}{6#有$6}{7#可能$7}{8#比$8}{##*{9#我$9}*$$}{10#还$10}{11#爱$11}{12#你$12}{13#的$13}{14#人$14}{15#的$15}{16#生日$16}{17#了$17}{18#。$18}{19#圣诞$19}{##*{20#快乐$20}*$$}{21#，$21}{22#我$22}{23#亲爱的$23}{24#。$24}",
"IME": null,
"M": 0,
"SIG": "9310FEFE369060BFF8A41CE85D7EABFA",
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "{2#Time$2} to {3#celebrate$3} {4#the$4} {16#birth$16} {13#of$13} the {5#only$5} {14#one$14} who {7#could$7} {11#love$11} {12#you$12} more {8#than$8} {#*{9#me$9}*$}{18#.$18} {#*{20#Merry$20}*$} {19#Christmas$19} to {12#you$12} my {23#darling$23}!",
"IME": null,
"M": 1,
"SIG": "A19F737A856327BD712BD552C27DDC30",
"TG": null,
"URL": "http://article.yeeyan.org/view/339854/339704",
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 48,
"WAD": null
},
{
"DATE": "/Date(1384975584000-0800)/",
"ID": 2448591,
"ORAL": true,
"R": 55717,
"READ": 68,
"S": {
"AD": "{1#xǔ duō$1} {2#ài liàn$2} {3#de$3} {4#zhù yuàn$4} {5#,$5} {6#xiàn gěi$6} {##*{7#wǒ$7}*$$} {8#de$8} {9#ài rén$9} {10#,$10} {11#nǐ$11} {12#yǒng yuǎn$12} {13#shì$13} {14#wǒ$14} {15#zuì měi hǎo$15} {17#de$17} {18#shèng dàn$18} {19#lǐ wù$19} {20#hé$20} {21#wǒ$21} {22#de$22} {23#yí qiè$23} {24#shèng dàn$24} {25#kuài lè$25} {26#!$26}",
"COL": null,
"D": "{1#许多$1}{2#爱恋$2}{3#的$3}{4#祝愿$4}{5#，$5}{6#献给$6}{##*{7#我$7}*$$}{8#的$8}{9#爱人$9}{10#，$10}{11#你$11}{12#永远$12}{13#是$13}{14#我$14}{15#最美好$15}{17#的$17}{18#圣诞$18}{19#礼物$19}{20#和$20}{21#我$21}{22#的$22}{23#一切$23}{24#圣诞$24}{25#快乐$25}{26#！$26}",
"IME": null,
"M": 0,
"SIG": "4EE93E884ECF9BA830CB375E7DD845B2",
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "{1#Lots$1} {3#of$3} {2#loving$2} {4#wishes$4} {6#for$6} my {9#sweetheart$9} who'll {12#always$12} {13#be$13} my {15#nicest$15} {18#Christmas$18} {19#gift$19} {20#and$20} {23#everything$23} to {#*{7#me$7}*$}{5#,$5} {#*Merry*$} {24#Christmas$24}{26#!$26}",
"IME": null,
"M": 17,
"SIG": "D8E416A614597D1CFF66B1902E389462",
"TG": null,
"URL": "http://bbs.bjhr.gov.cn/dispbbs.asp?boardID=70&ID=52976&page=2",
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 49,
"WAD": null
},
{
"DATE": "/Date(1384975535000-0800)/",
"ID": 12503221,
"ORAL": true,
"R": 37899,
"READ": 82,
"S": {
"AD": "{1#néng$1} {2#gěi$2} {##*{3#wǒ$3}*$$} {4#yī$4} {5#zhāng$5} {6#nǐ$6} {7#de$7} {8#zhào piàn$8} {9#ma$9} {10#?$10} {11#zhè yàng$11} {12#,$12} {13#shèng dàn lǎo rén$13} {14#jiù$14} {15#zhī dào$15} {16#sòng$16} {17#wǒ$17} {18#shén me$18} {19#lǐ wù$19} {20#la$20} {21#,$21} {22#shèng dàn$22} {##*{23#kuài lè$23}*$$} {24#!$24}",
"COL": null,
"D": "{1#能$1}{2#给$2}{##*{3#我$3}*$$}{4#一$4}{5#张$5}{6#你$6}{7#的$7}{8#照片$8}{9#吗$9}{10#？$10}{11#这样$11}{12#，$12}{13#圣诞老人$13}{14#就$14}{15#知道$15}{16#送$16}{17#我$17}{18#什么$18}{19#礼物$19}{20#啦$20}{21#，$21}{22#圣诞$22}{##*{23#快乐$23}*$$}{24#！$24}",
"IME": null,
"M": 0,
"SIG": "0B5202033058EF71881BB32C7A2B6B5C",
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "{1#Can$1} {3#I$3} have {6#your$6} {8#picture$8}{12#,$12} {11#so$11}{21#,$21} {13#Santa Claus$13} {15#knows$15} exactly {18#what$18} {2#to$2} {16#give$16} {#*{3#me$3}*$}{24#.$24} {#*{23#merry$23}*$} {22#Christmas$22}.",
"IME": null,
"M": 1,
"SIG": "6AE98593BC8E51D26A321F3F14C64C76",
"TG": null,
"URL": "http://www.en8848.com.cn/kouyu/use/greeting/148857.html",
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 44,
"WAD": null
},
{
"DATE": "/Date(1384975527000-0800)/",
"ID": 2167473,
"ORAL": false,
"R": 56355,
"READ": 100,
"S": {
"AD": "{1#bú shì$1} {2#yī$2} {3#pí náng$3} {4#de$4} {5#jiǔ$5} {6#,$6} {7#yīn wèi$7} {8#yī$8} {9#pí náng$9} {10#de$10} {11#jiǔ huì$11} {12#ràng$12} {13#wǒ$13} {14#zuì$14} {15#dǎo$15} {16#,$16} {17#huì$17} {18#shǐ$18} {##*{19#wǒ$19}*$$} {20#chéng wéi$20} {21#yī gè$21} {22#shǎ guā$22} {23#。$23} {24#jiù$24} {25#zhǐ shì$25} {26#yī$26} {27#xiǎo$27} {28#bēi$28} {29#jiǔ$29} {30#,$30} {31#ràng$31} {32#wǒ$32} {33#nuǎn huo$33} {34#yí xià$34} {35#。$35}",
"COL": null,
"D": "{1#不是$1}{2#一$2}{3#皮囊$3}{4#的$4}{5#酒$5}{6#，$6}{7#因为$7}{8#一$8}{9#皮囊$9}{10#的$10}{11#酒会$11}{12#让$12}{13#我$13}{14#醉$14}{15#倒$15}{16#，$16}{17#会$17}{18#使$18}{##*{19#我$19}*$$}{20#成为$20}{21#一个$21}{22#傻瓜$22}{23#。$23}{24#就$24}{25#只是$25}{26#一$26}{27#小$27}{28#杯$28}{29#酒$29}{30#，$30}{31#让$31}{32#我$32}{33#暖和$33}{34#一下$34}{35#。$35}",
"IME": null,
"M": 0,
"SIG": "23C8021EDBEA54DF9BF23BEC5C473192",
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "Not {21#a$21} {3#skin$3} of {29#wine$29}{23#.$23} {7#For$7} {21#a$21} {9#skin$9} of {5#wine$5} {17#would$17} {18#make$18} {13#me$13} {#*merry*$}{6#,$6} and {22#foolish$22}{35#.$35} {25#Merely$25} {21#a$21} {28#cup$28} of {5#wine$5}{16#,$16} to {33#warm$33} {#*{19#me$19}*$}.",
"IME": null,
"M": 1,
"SIG": "6B16ED0B1C918B3EE947DDC66798C08E",
"TG": null,
"URL": "http://www.odyguild.net/bbs/thread-16295-1-1.html",
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 64,
"WAD": null
},
{
"DATE": "/Date(1384975566000-0800)/",
"ID": 10308900,
"ORAL": false,
"R": 45037,
"READ": 78,
"S": {
"AD": "{1#xià rì$1} {2#wēn nuǎn$2} {3#de$3} {4#zǎo chén$4} {5#shǐ$5} {##*{6#wǒ$6}*$$} {7#xīn qíng$7} {8#shū chàng$8} {9#。$9}",
"COL": null,
"D": "{1#夏日$1}{2#温暖$2}{3#的$3}{4#早晨$4}{5#使$5}{##*{6#我$6}*$$}{7#心情$7}{8#舒畅$8}{9#。$9}",
"IME": null,
"M": 0,
"SIG": "385688C1FF832209990C4C837194C9C1",
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "A {2#warm$2} {1#summer$1} {4#morning$4} {5#makes$5} {#*{6#me$6}*$} {#*merry*$}{9#.$9}",
"IME": null,
"M": 1,
"SIG": "61F0EB7B91ADDE4A5C741DD6357055AA",
"TG": null,
"URL": "http://wwyk08.blog.163.com/blog/static/95550477200911284433244",
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 17,
"WAD": null
},
{
"DATE": "/Date(1384975565000-0800)/",
"ID": 15755609,
"ORAL": true,
"R": 16260,
"READ": 54,
"S": {
"AD": "{1#duì bu qǐ$1} {2#,$2} {3#ràng$3} {4#yí xià$4} {2#,$2} {6#ràng$6} {7#yí xià$7} {8#-$8} {9#shèng dàn$9} {##*{10#kuài lè$10}*$$}",
"COL": null,
"D": "{1#对不起$1}{2#，$2}{3#让$3}{4#一下$4}{2#，$2}{6#让$6}{7#一下$7}{8#-$8}{9#圣诞$9}{##*{10#快乐$10}*$$}",
"IME": null,
"M": 0,
"SIG": "6C33FE0DE57EB4053905D37DB3D26986",
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "sorry . {1#excuse$1} me {2#,$2} {1#excuse$1} {#*me*$} . {8#-$8} {#*{10#merry$10}*$} {9#christmas$9}",
"IME": null,
"M": 1,
"SIG": "53D0548F1680690CA7E56BEF189B79D4",
"TG": null,
"URL": "http://www.ichacha.net/merry.html",
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 21,
"WAD": null
},
{
"DATE": "/Date(1384975526000-0800)/",
"ID": 1902661,
"ORAL": false,
"R": 57041,
"READ": 74,
"S": {
"AD": "{1#tā$1} {2#dòng zuò$2} {3#mǐn jié$3} {4#de$4} {5#bǎ$5} {6#huā shù$6} {5#gěi$5} {8#le$8} {9#wǒ$9} {10#,$10} {11#zhù$11} {##*{12#wǒ$12}*$$} {13#shèng dàn$13} {##*{14#kuài lè$14}*$$} {15#,$15} {16#rán hòu$16} {17#lí kāi$17} {18#le$18} {19#。$19}",
"COL": null,
"D": "{1#他$1}{2#动作$2}{3#敏捷$3}{4#地$4}{5#把$5}{6#花束$6}{5#给$5}{8#了$8}{9#我$9}{10#，$10}{11#祝$11}{##*{12#我$12}*$$}{13#圣诞$13}{##*{14#快乐$14}*$$}{15#，$15}{16#然后$16}{17#离开$17}{18#了$18}{19#。$19}",
"IME": null,
"M": 0,
"SIG": "2B80A73F385EEB4C3A4ADDF2BCDB2B0B",
"TG": null,
"URL": null,
"W": null
},
"T": {
"AD": null,
"COL": null,
"D": "In one {3#quick$3} {2#motion$2} {1#he$1} {5#gave$5} {9#me$9} the corsage{10#,$10} {11#wished$11} {#*{12#me$12}*$} a {#*{14#Merry$14}*$} {13#Christmas$13} {16#and$16} {17#departed$17}{19#.$19}",
"IME": null,
"M": 1,
"SIG": "E72E95317C05A7A77779FB47D0A05F49",
"TG": null,
"URL": "http://dict.ebigear.com/w/merry/",
"W": null
},
"TECH": false,
"TITLE": false,
"WA": 37,
"WAD": null
}
],
"TOTAL": 44
},
"SUGG": {
"AC": null,
"PH": [
{
"DEF": "玛利一世(1516—1558,英国女王,在位期间1553—1558)",
"SIG": "0A79AF279AAF1065D003CA4069BBF3B7",
"V": "mary i"
},
{
"DEF": "随从$$侍从",
"SIG": "0C4D26C5B8B8BCA47C14CE01AA6F43C9",
"V": "merry men"
},
{
"DEF": "大麻",
"SIG": "BEA1E16DF5DDD8268143C4770A420CF0",
"V": "Mary Jane"
},
{
"DEF": "",
"SIG": "C56442FF8BEB540F2AB2890099614EEF",
"V": "mark you"
},
{
"DEF": "愉悦的气氛",
"SIG": "BA5CBC6C5D2D2792F89BA8E7197705EA",
"V": "merry mood"
}
],
"PY": null,
"SP": null
}
}
解析：
同[词典](#dic)解析 | 34.065119 | 460 | 0.322612 | yue_Hant | 0.317617 |
57c9692c870a9a16600acca16a028fb573e669fb | 224 | md | Markdown | _project/before-and-after-pallets-used-for-outdoor-furniture.md | rumnamanya/rumnamanya.github.io | 2deadeff04c8a48cf683b885b7fa6ab9acc1d9d9 | [
"MIT"
] | null | null | null | _project/before-and-after-pallets-used-for-outdoor-furniture.md | rumnamanya/rumnamanya.github.io | 2deadeff04c8a48cf683b885b7fa6ab9acc1d9d9 | [
"MIT"
] | null | null | null | _project/before-and-after-pallets-used-for-outdoor-furniture.md | rumnamanya/rumnamanya.github.io | 2deadeff04c8a48cf683b885b7fa6ab9acc1d9d9 | [
"MIT"
] | null | null | null | ---
layout: project_single
title: "Before and After: Pallets Used For Outdoor Furniture"
slug: "before-and-after-pallets-used-for-outdoor-furniture"
parent: "diy-unused-wood-pallet"
---
shipping pallets as outdoor furniture | 32 | 62 | 0.78125 | eng_Latn | 0.960353 |
57c9ec0aefd0c2f98ae1ecc6a0f736f92012f0b4 | 570 | md | Markdown | _posts/boj/2021-11-17-boj-11654.md | franz-straven/franz-straven.github.io | 5ff7079b39fe6860fe163f6680ab2e97c11d5df2 | [
"Apache-2.0"
] | null | null | null | _posts/boj/2021-11-17-boj-11654.md | franz-straven/franz-straven.github.io | 5ff7079b39fe6860fe163f6680ab2e97c11d5df2 | [
"Apache-2.0"
] | null | null | null | _posts/boj/2021-11-17-boj-11654.md | franz-straven/franz-straven.github.io | 5ff7079b39fe6860fe163f6680ab2e97c11d5df2 | [
"Apache-2.0"
] | null | null | null | ---
title: "백준 11654번 문제 '아스키 코드'"
subtitle: "[Bronze 5] CLASS 1"
layout: post
author: "Franz Straven"
header-style: text
tags:
- Algorithm
- Baekjoon
- Python
- JavaScript
---
# 1 문제
## 1.1 링크
[11654번: 아스키 코드](https://www.acmicpc.net/problem/11654)
## 1.2 분석
## 1.3 알고리즘 분류
- 구현
# 2 해답
## 2.1 해설
## 2.2 언어별 해설
### 2.2.1 Python
```python
A = str(input())
print(ord(A))
```
1. 문법 정리
### 2.2.2 JavaScript
```jsx
const fs = require('fs');
const input = fs.readFileSync('/dev/stdin').toString().trim();
console.log(input.charCodeAt(0));
```
1. 문법 정리 | 11.176471 | 62 | 0.6 | kor_Hang | 0.846596 |
57cb019882059bc6a0ef024f347b5223ab438f5f | 104 | md | Markdown | README.md | relwiwa/fcc-fullstack-skeleton | c4b78e292f94ad97041235e37c67f141dbded418 | [
"MIT"
] | null | null | null | README.md | relwiwa/fcc-fullstack-skeleton | c4b78e292f94ad97041235e37c67f141dbded418 | [
"MIT"
] | null | null | null | README.md | relwiwa/fcc-fullstack-skeleton | c4b78e292f94ad97041235e37c67f141dbded418 | [
"MIT"
] | null | null | null | # fcc-fullstack-skeleton
A skeleton for the server-side to develop the full-stack freeCodeCamp projects
| 34.666667 | 78 | 0.826923 | eng_Latn | 0.991757 |
57cb71cf99ec18c64dab74c3184b8b40e2cd78cd | 156 | md | Markdown | app/actions/Readme.md | danscan/fractal | 8a15a0e8658589c273165f91714d5ea56ef05ff1 | [
"MIT"
] | 17 | 2016-10-12T14:28:16.000Z | 2021-02-08T08:20:03.000Z | app/actions/Readme.md | danscan/fractal | 8a15a0e8658589c273165f91714d5ea56ef05ff1 | [
"MIT"
] | 1 | 2016-10-17T07:30:31.000Z | 2016-10-18T03:33:34.000Z | app/actions/Readme.md | danscan/fractal | 8a15a0e8658589c273165f91714d5ea56ef05ff1 | [
"MIT"
] | 2 | 2016-10-13T04:52:29.000Z | 2016-10-17T07:06:32.000Z | Action files are named after the primary reducers that handle the actions they export.
They export action types & corresponding action creator functions.
| 52 | 88 | 0.820513 | eng_Latn | 0.999635 |
57cbead0b48569e2a65400966a7c2eb3d2e5ae9f | 108 | md | Markdown | README.md | TFmini/TFmini-Parking | 613b3254dea735882f47babf2d92f084123798f2 | [
"MIT"
] | null | null | null | README.md | TFmini/TFmini-Parking | 613b3254dea735882f47babf2d92f084123798f2 | [
"MIT"
] | null | null | null | README.md | TFmini/TFmini-Parking | 613b3254dea735882f47babf2d92f084123798f2 | [
"MIT"
] | null | null | null | # TFmini(Plus)-ParkingBarrierGate
Applying TFmini(Plus) to Toll Gate, Parking lot, neighbourhoods Gate etc.
| 36 | 73 | 0.805556 | eng_Latn | 0.489973 |
57cc3deb5012bf964c5ad2584791f732a11cfe8d | 5,877 | md | Markdown | README.md | jimcoven/study-fragments | c230ed7f321ce53346ec75a096334272ee9de72f | [
"Apache-2.0"
] | null | null | null | README.md | jimcoven/study-fragments | c230ed7f321ce53346ec75a096334272ee9de72f | [
"Apache-2.0"
] | null | null | null | README.md | jimcoven/study-fragments | c230ed7f321ce53346ec75a096334272ee9de72f | [
"Apache-2.0"
] | null | null | null | # General Activity (Self-reference)
This is for future me. The design pattern for activities
### Handling of data models
Implement onLoadModel(), onInitViews()
*Looks like onRestart() is totally ignored. Everything seems to restore properly, including view states*
```
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
... create views ...
// load data
onLoadModel();
onInitViews();
}
private void onLoadModel() {
// maybe this is where you should load all data
// onCreate + onRestart will call this
}
private void onInitViews() {
// this is where you set clickers
// setadapters
}
```
### Handling of listeners / database etc
Implement onRelease()
```
protected void onStart() {
super.onStart();
// register observables
// no need to create additional method unless complicated
}
protected void onStop() {
super.onStop();
onRelease();
}
public void finish() {
super.finish();
// called externally to force finish.
// save persistent or do finishing work.
onRelease()
}
private void onRelease() {
// deregister
}
```
### Handle orientation / home
Don't restore onCreate. Just use onRestoreInstanceState ONLY.
http://developer.android.com/training/basics/activity-lifecycle/recreating.html#RestoreState
This will also be sufficient to handle orientation changes using different layouts. However, the ids implemented must be similar. Therefore, try to write codes in layout-port & layout-land. only use layout/ for shared resources such as includes.
However, you also NEED to load the datamodel (eg. downloading adverts) and call onInitViews() (eg. set adapter to view, set clickers etc)
```
public void onRestoreInstanceState(Bundle savedInstanceState) {
super.onRestoreInstanceState(savedInstanceState);
// Just handle your property members. Don't save view states.
// eg. edittext - auto saves its text
// eg. listview - auto saves its firstvisibleposition
// however, the text in textview is not a state.
// it displays text based on some member property.
// so you need to save the member property and display it.
// dont jump in to write code to handle this unless you are sure it is not already handled
}
protected void onSaveInstanceState(Bundle savedInstanceState) {
super.onSaveInstanceState(savedInstanceState);
}
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView();
onLoadModel();
onInitViews();
}
```
### Handle orientation via onConfigurationChanged.
There is another mutually exclusive method to handle orientation via onConfigurationChanged. This is when you are carrying a heavy load of data in the activity.
*If your application doesn't need to update resources during a specific configuration change and you have a performance limitation that requires you to avoid the activity restart, then you can declare that your activity handles the configuration change itself, which prevents the system from restarting your activity.*
For comparison,
- the default android method handles orientation by saving and restoring both view (android) + member (you) states. The full activity cycle is being called. listeners have to be reactivated etc.
- onConfigurationChange allows you to manually restore a new view, initViews. The member states are preserved. So you do not need to make large arrays parcelable. listeners are also not disrupted. Progress dialogs however may ahve to be dismissed (need to check). It is also useful if you are using a lot of fragments. So the data of the fragments are not destroyed (how to handle initViews? - similar?)
The downside of onConfigurationChange however, is that you lose all viewstates. For example the firstvisibleviewposition of the listview is not saved. So you need to save that position as a member property as the user scrolls.
However, you can manually save the view states using a bundle within the onConfigurationChanged. It is not hard. just tedious
```
private Bundle onSaveViewStates() {
Bundle bundle = new Bundle();
...
int position = getListView().getFirstVisiblePosition();
bundle.putInt("save:position", position);
bundle.putString("save:textview", getTextView().getText().toString());
return bundle;
}
private void onRestoreViewStates(Bundle bundle) {
...
int position = bundle.getInt("save:position");
getListView().setSelection(position);
String text = bundle.getString("save:textview");
getTextView().setText(text);
}
public void onConfigurationChanged(Configuration newConfig) {
super.onConfigurationChanged(newConfig);
Bundle bundle = onSaveViewStates();
if (newConfig.orientation == Configuration.ORIENTATION_PORTRAIT) {
logState("onConfigurationChanged: Configuration.ORIENTATION_PORTRAIT");
setContentView(R.layout.activity_demo2_stateful);
} else if (newConfig.orientation == Configuration.ORIENTATION_LANDSCAPE) {
logState("onConfigurationChanged: Configuration.ORIENTATION_LANDSCAPE");
setContentView(R.layout.activity_demo2_stateful);
}
// onLoadModel // NO NEED TO LOAD THIS
onInitViews();
onRestoreViewStates(bundle); // -- to save transient view states
}
```
Checked:
- Configuration change also switches to use layout-land from layout-port
- onpause/onstop are not called.
- it jumps back to recreate just the views, but everything else is not lost.
- you need to however, a) setup ui clickers, b) load the data back to views.
Also see http://developer.android.com/guide/topics/resources/runtime-changes.html
| 36.73125 | 404 | 0.72486 | eng_Latn | 0.937542 |
57ccf0a511aa8360a006650364e2888fa62396bf | 647 | md | Markdown | _posts/2017-04-22-pannenkoeken.md | escowles/recipes | 8765ed106908c8e2a033faea4e64dcbb4496c712 | [
"CC0-1.0"
] | 1 | 2020-11-05T02:19:45.000Z | 2020-11-05T02:19:45.000Z | _posts/2017-04-22-pannenkoeken.md | escowles/recipes | 8765ed106908c8e2a033faea4e64dcbb4496c712 | [
"CC0-1.0"
] | 8 | 2020-11-05T02:48:53.000Z | 2022-03-04T23:18:43.000Z | _posts/2017-04-22-pannenkoeken.md | escowles/recipes | 8765ed106908c8e2a033faea4e64dcbb4496c712 | [
"CC0-1.0"
] | null | null | null | ---
layout: post
title: Pannenkoeken
date: 2017-04-22 11:56:54 -0500
category: sides
tags: bread breakfast dutch
---
250g (1½ cups) flour
1.25ml (¼ tsp.) salt
2 eggs
500ml (2 cups) milk
butter for frying
* Mix flour and salt, add eggs and half the milk.
* Beat until smooth, then add the remaining milk to make a thin batter.
* Melt butter in pan and fry scant ½ cup of batter, tilting to coat bottom of pan evenly.
* Turn when bottom is golden brown.
* For spek (bacon): cook bacon and line bottom of pan with 2-3 slices of bacon before pouring in batter.
https://stefangourmet.com/2013/12/31/dutch-pancakes-pannenkoeken/
| 30.809524 | 106 | 0.720247 | eng_Latn | 0.951361 |
57cd618c4d792e83817fedb08a81c9226c008c15 | 8,245 | md | Markdown | docs/containers/includes/vs-2017/container-tools.md | MicrosoftDocs/visualstudio-docs.it- | 3e6906339549f32b01960e19cd3400222dcc7b94 | [
"CC-BY-4.0",
"MIT"
] | 3 | 2018-03-29T21:12:32.000Z | 2022-03-26T11:56:08.000Z | docs/containers/includes/vs-2017/container-tools.md | MicrosoftDocs/visualstudio-docs.it- | 3e6906339549f32b01960e19cd3400222dcc7b94 | [
"CC-BY-4.0",
"MIT"
] | 12 | 2018-03-07T15:43:33.000Z | 2021-03-29T15:28:34.000Z | docs/containers/includes/vs-2017/container-tools.md | MicrosoftDocs/visualstudio-docs.it- | 3e6906339549f32b01960e19cd3400222dcc7b94 | [
"CC-BY-4.0",
"MIT"
] | 12 | 2017-11-26T08:17:38.000Z | 2021-10-09T11:24:07.000Z | ---
title: Visual Studio Strumenti contenitore per Docker con ASP.NET in Windows
author: ghogen
description: Informazioni su come usare gli strumenti di Visual Studio 2017 e Docker per Windows
ms.author: ghogen
ms.date: 02/01/2019
ms.technology: vs-container-tools
ms.topic: include
ms.openlocfilehash: d1101f1b0906e994d609159fc643000daf4ef1bf
ms.sourcegitcommit: 4efdab6a579b31927c42531bb3f7fdd92890e4ac
ms.translationtype: MT
ms.contentlocale: it-IT
ms.lasthandoff: 10/26/2021
ms.locfileid: "130354571"
---
Con Visual Studio, è possibile compilare, eseguire il debug ed eseguire facilmente app ASP.NET Core in contenitori e pubblicarle in Registro Azure Container, Docker Hub, Servizio app di Azure o nel proprio registro contenitori. In questo articolo verrà pubblicata in Registro Azure Container.
## <a name="prerequisites"></a>Prerequisiti
* [Docker Desktop](https://hub.docker.com/editions/community/docker-ce-desktop-windows)
* [Visual Studio 2017](https://visualstudio.microsoft.com/vs/older-downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=vs+2017+download) con il carico di lavoro **Sviluppo Web**, **Strumenti di Azure** e/o **Sviluppo multipiattaforma .NET Core** installato
* Per pubblicare in Registro Azure Container, una sottoscrizione di Azure. [Iscriversi per ottenere una versione di valutazione gratuita](https://azure.microsoft.com/free/dotnet/).
## <a name="installation-and-setup"></a>Installazione e configurazione
Per l'installazione di Docker, esaminare prima di tutto le informazioni in [Docker Desktop per Windows: Cosa](https://docs.docker.com/docker-for-windows/install/#what-to-know-before-you-install)sapere prima di installare . Installare [Docker Desktop](https://hub.docker.com/editions/community/docker-ce-desktop-windows).
## <a name="add-a-project-to-a-docker-container"></a>Aggiungere un progetto in un contenitore Docker
1. Nel menu di Visual Studio selezionare **File > Nuovo > Progetto**.
1. Nella sezione **Modelli** della finestra di dialogo **Nuovo progetto** selezionare **Visual C# > Web**.
1. Selezionare **ASP.NET Core'applicazione Web** o, se si vuole usare il .NET Framework anziché .NET Core, selezionare ASP.NET **Applicazione Web**.
1. Assegnare un nome alla nuova applicazione (o accettare quello predefinito), quindi selezionare **OK**.
1. Selezionare **Applicazione Web.**
1. Spuntare la casella di controllo **Abilita Supporto Docker**.
Lo screenshot mostra .NET Core. Se si usa un .NET Framework, l'aspetto è leggermente diverso.
1. Selezionare il tipo di contenitore appropriato (Windows o Linux) e fare clic su **OK**.
## <a name="dockerfile-overview"></a>Panoramica di Dockerfile
Nel progetto viene creato un *Dockerfile*, il file recipe per la creazione di un'immagine Docker finale. Fare riferimento a [Dockerfile reference](https://docs.docker.com/engine/reference/builder/) (Informazioni di riferimento su Dockerfile) per una descrizione dei comandi contenuti nel file:
```
FROM mcr.microsoft.com/dotnet/aspnet:2.1 AS base
WORKDIR /app
EXPOSE 59518
EXPOSE 44364
FROM mcr.microsoft.com/dotnet/sdk:2.1 AS build
WORKDIR /src
COPY HelloDockerTools/HelloDockerTools.csproj HelloDockerTools/
RUN dotnet restore HelloDockerTools/HelloDockerTools.csproj
COPY . .
WORKDIR /src/HelloDockerTools
RUN dotnet build HelloDockerTools.csproj -c Release -o /app
FROM build AS publish
RUN dotnet publish HelloDockerTools.csproj -c Release -o /app
FROM base AS final
WORKDIR /app
COPY --from=publish /app .
ENTRYPOINT ["dotnet", "HelloDockerTools.dll"]
```
Il *Dockerfile* precedente è basato sull'immagine [microsoft/aspnetcore](https://hub.docker.com/r/microsoft/aspnetcore/) e include le istruzioni per modificare l'immagine di base compilando il progetto e aggiungendolo al contenitore. Se si usa il .NET Framework, l'immagine di base sarà diversa.
Se la casella di controllo **Configura per HTTPS** della finestra di dialogo Nuovo progetto è selezionata, il *Dockerfile* espone due porte. Una porta viene usata per il traffico HTTP e l'altra viene usata per il traffico HTTPS. Se la casella di controllo non è selezionata, viene esposta una sola porta (80) per il traffico HTTP.
## <a name="debug"></a>Debug
Selezionare **Docker** nell'elenco a discesa Debug nella barra degli strumenti e avviare il debug dell'app. È possibile che venga visualizzato un messaggio in cui viene richiesto di considerare attendibile un certificato; scegliere di considerare attendibile il certificato per continuare.
La finestra **Output** mostra le azioni eseguite.
Aprire la **console di Gestione pacchetti** dal menu **Strumenti**> Gestione pacchetti NuGet, **Console di Gestione pacchetti**.
L'immagine Docker risultante dell'app, contrassegnata con *dev*, è basata sul tag *2.1-aspnetcore-runtime* dell'immagine di base *microsoft/dotnet*. Eseguire il comando `docker images` nella finestra **Console di Gestione pacchetti**. Vengono visualizzate le immagini nel computer in uso:
```console
REPOSITORY TAG IMAGE ID CREATED SIZE
hellodockertools dev d72ce0f1dfe7 30 seconds ago 255MB
microsoft/dotnet 2.1-aspnetcore-runtime fcc3887985bb 6 days ago 255MB
```
> [!NOTE]
> L'immagine **dev** non contiene i file binari e altri contenuti dell'app poiché le configurazioni **Debug** usano il montaggio volumi per offrire l'esperienza interattiva di modifica e debug. Per creare un'immagine di produzione che contiene tutti i contenuti, usare la configurazione **Rilascio**.
Eseguire il comando `docker ps` nella console di Gestione pacchetti. Si noti che l'app viene eseguita usando il contenitore:
```console
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
baf9a678c88d hellodockertools:dev "C:\\remote_debugge..." 21 seconds ago Up 19 seconds 0.0.0.0:37630->80/tcp dockercompose4642749010770307127_hellodockertools_1
```
## <a name="publish-docker-images"></a>Pubblicare immagini Docker
Al termine del ciclo di sviluppo e debug dell'app, è possibile creare un'immagine di produzione dell'app.
1. Selezionare **Versione** nell'elenco a discesa della configurazione ed eseguire l'app.
1. Fare clic con il pulsante destro del mouse sul progetto in **Esplora soluzioni** e scegliere **Pubblica**.
1. Nella finestra di dialogo Destinazione di pubblicazione, selezionare la scheda **Registro contenitori**.
1. Scegliere **Crea nuovo Registro Azure Container** e fare clic su **Pubblica**.
1. Inserire i valori desiderati in **Creare un nuovo Registro Azure Container**.
| Impostazione | Valore consigliato | Descrizione |
| ------------ | ------- | -------------------------------------------------- |
| **Prefisso DNS** | Nome univoco a livello globale | Nome che identifica in modo univoco il registro contenitori. |
| **Sottoscrizione** | Scegliere la sottoscrizione | Sottoscrizione di Azure da usare. |
| **[Gruppo di risorse](/azure/azure-resource-manager/resource-group-overview)** | myResourceGroup | Nome del gruppo di risorse in cui creare il registro contenitori. Per creare un nuovo gruppo di risorse scegliere **Nuovo**.|
| **[SKU](/azure/container-registry/container-registry-skus)** | Standard | Livello di servizio del registro contenitori |
| **Percorso del registro** | Un percorso vicino | Scegliere un Percorso in una [regione](https://azure.microsoft.com/regions/) nelle vicinanze o vicino ad altri servizi usati nel registro contenitori. |
![Screenshot della Visual Studio di dialogo crea Registro Azure Container di lavoro.][0]
1. Fare clic su **Crea**
## <a name="next-steps"></a>Passaggi successivi
È possibile ora eseguire il pull del contenitore dal registro a qualsiasi host in grado di eseguire immagini Docker, ad esempio [Istanze di Azure Container ](/azure/container-instances/container-instances-tutorial-deploy-app).
[0]:../../media/hosting-web-apps-in-docker/vs-azure-container-registry-provisioning-dialog.png
| 64.92126 | 330 | 0.753062 | ita_Latn | 0.989668 |
57cd6aad057ca5c52017d89bfd35a2490ef2fb3e | 2,569 | md | Markdown | _posts/2018-07-21-finance_engineering_recipe_chapter4.md | kooock/kooock.github.io | e39c835c68c8b9f685ea1f5c1f8d6e61a5678202 | [
"CC0-1.0"
] | null | null | null | _posts/2018-07-21-finance_engineering_recipe_chapter4.md | kooock/kooock.github.io | e39c835c68c8b9f685ea1f5c1f8d6e61a5678202 | [
"CC0-1.0"
] | null | null | null | _posts/2018-07-21-finance_engineering_recipe_chapter4.md | kooock/kooock.github.io | e39c835c68c8b9f685ea1f5c1f8d6e61a5678202 | [
"CC0-1.0"
] | null | null | null | ---
layout: post
title: "[금융공학레시피 정리]주식, 가격, 지수"
excerpt: "금융공학 레시피 chapter4."
modified: 2018-07-22
comments: true
category : FinanceEngineering
tags: [금융공학, 퀀트]
---
금융공학 레시피 chapter4. 주식, 가격, 지수
--------------------------------------------------------------------------------------------
#### 4.1 주식과 가격
주식의 적정가격은 얼마일까? => 아직 정확히 답을 아는 사람은 없음
하지만, 많은 사람들의 노력으로 다양한 valuation model이 개발됨
##### 주식가격은 기업의 과거, 현재, 미래를 반영
2017년 마자막 날 삼성전자의 주가는 254만 8000원
과연 이 가격은 적정 가격일까? 썬건 아닐까? 비싼건 아닐까? 2016년 1월보다 많이 오른 것인가?
이런 답을 찾기 위해 기본적 / 기술적 분석 등 다양한 분석을 한다.
Analyst : 기업 실사, 미래 전망, 경쟁사 분석, CEO인터뷰 등 다양한 분석을 하고, 주가 예측을 위한 valuation => 목표 주가 산정/ 분석보고서 발간
##### 싸면 매수, 비싸면 매도 ~~아니 누가 모르나?~~
싸다고 생각하면 매수 : long position => position이 + 상태
비싸다고 생각하면 매도 : short position => position이 - 상태
주가는 더 많은 사람이 배팅하는 방향으로 움직임
##### 거래 발생 = 기대 수준이 서로 다름
같은 지표를 사용한다 하더라도 서로 판단 방식이 달라서 적정 주가를 서로 다르게 판단 => 매매 발생
한쪽 포지션으로만 몰리면 거래가 이뤄질리가...
##### valuation : 적정 주가 산출
Analyst : 경영전략, 시장 동향, 경쟁사 동향 등의 기업 활동 심층 분석 => 다양한 valuation 방법 적용하여 목표 주가 산정
\>>>> 종목마다 방법이 다름 => 만능키는 없다
Analyst가 사용하는 valuation model : DOM, Gordon의 성장모형, CAPM, FV/EBITDA, PER, EPS, PBR 등
finance engineering valuation : Quant traing 분야 => 유사한 다수 종목의 주가를 관찰해 주가를 형성하는 규칙을 발견하여 적정 주가 예측 => 통계학에 뿌리
##### 주가 비교의 첫걸음 : 비교 대상의 표준화
삼성전자와 주가비교를 위해 반도체라는 공통점이 있는 SK하이닉스와 전자라는 공통점이 있는 LG전자로 비교
먼저 하이닉스 그래프
LG전자 그래프
삼성과 하이닉스 LG중 수익률이 가장 높은 종목은? ~~어차피 난 셋다 없어 ㅠㅠ~~
따로 따로 보면 눈대중으로 파악이 힘들어진다.
그래서 삼성 하이닉스 LG의 그래프를 겹쳐보자
주가 수준이 다르므로 lg와 하이닉스는 오르는지 내리는지 알수가 없다.
비율로 기준을 맞춰야 한다. => indexing(지수화)
$$Price_Index = {Price_{i} \over Price_{0}} \times Standard_Price$$
ex ) 기준일 : 2016년 1월 4일 / 기준가 : 100
| 일자 | SK하이닉스 | 삼성전자 | LG전자 |
| :---: | :---: | :---: | :---: |
| 2015-12-30 | 30,346 | 1,232,071 | 53,377 |
| 2016-01-04 | 29,754 | 1,178,290 | 52,087 |
| 2016-01-06 | 30,196 | 1,181,224 | 53,873 |
1월 4일 종가기준으로 1월 5일의 index는 $$Price_Index = {Price_{i} \over Price_{0}} \times Standard_Price = {1,181,224 \over 1,178,290} \times 100 = 100.25$$
이 개념은 주가지수 산출, 편드 가격 산정 등에 동일하게 적용
이런식으로 indexing을 하면 그래프는
상승률
SK하이닉스 : 250%
삼성전자 : 210%
LG전자 : 200%
하이닉스가 가장 높은 상승률을 보인 것을 알 수 있다.
#### 4.3 주가지수 : 관심종목 그룹 전체를 대포하는 가격지수
| 23.568807 | 145 | 0.63371 | kor_Hang | 1.00001 |
57cd715405df76d31a47648c5f83a4f63cf5801a | 49 | md | Markdown | powerapps-docs/developer/model-driven-apps/clientapi/reference/formContext-ui-tabs/includes/getDisplayState-description.md | Miguel-byte/powerapps-docs.es-es | 1edcf434a8e8f096b67510fa3c423ca3c5d1ede4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | powerapps-docs/developer/model-driven-apps/clientapi/reference/formContext-ui-tabs/includes/getDisplayState-description.md | Miguel-byte/powerapps-docs.es-es | 1edcf434a8e8f096b67510fa3c423ca3c5d1ede4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | powerapps-docs/developer/model-driven-apps/clientapi/reference/formContext-ui-tabs/includes/getDisplayState-description.md | Miguel-byte/powerapps-docs.es-es | 1edcf434a8e8f096b67510fa3c423ca3c5d1ede4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | Obtiene el estado de visualización de la pestaña. | 49 | 49 | 0.836735 | spa_Latn | 0.999951 |
57cd7bbd03f98bdd935041e7fc6fff16136f4036 | 1,308 | md | Markdown | src/ConfigProvider/README.md | sensoro-design/sensoro-design-next | 12074538bf5abdeb75d28e940264e14552de0e7a | [
"MIT"
] | 2 | 2022-03-11T02:14:55.000Z | 2022-03-11T02:54:48.000Z | src/ConfigProvider/README.md | sensoro-design/sensoro-design-next | 12074538bf5abdeb75d28e940264e14552de0e7a | [
"MIT"
] | null | null | null | src/ConfigProvider/README.md | sensoro-design/sensoro-design-next | 12074538bf5abdeb75d28e940264e14552de0e7a | [
"MIT"
] | null | null | null | ---
nav:
title: 组件
path: /components
---
# 全局配置 ConfigProvider
在应用的最外层进行配置，一次设置，全局生效。一般用于设置国际化语言等功能。
## 代码演示
### 基础用法
<code src="./__demo__/basic.demo.tsx" />
### 组件配置
<code src="./__demo__/component-config.demo.tsx" />
### 空元素
<code src="./__demo__/render-empty.demo.tsx" />
### 表格分页配置
<code src="./__demo__/table-pagination.demo.tsx" />
### 主题配置
<code src="./__demo__/theme.demo.tsx" />
## API
### ConfigProvider
|参数名|描述|类型|默认值|版本|
|---|---|---|---|---|
|autoInsertSpaceInButton|当按钮中是两个汉字时，自动在两个汉字中添加一个空格。|`boolean`|`-`|2.3.0|
|componentConfig|用于全局配置所有组件的默认参数|`ComponentConfig`|`-`|2.23.0|
|locale|设置语言包|`Locale`|`-`|-|
|theme|主题配置|`ThemeConfig`|`-`|-|
|size|配置组件的默认尺寸，只会对支持`size`属性的组件生效。|`'mini' \| 'small' \| 'default' \| 'large'`|`default`|-|
|prefixCls|全局组件类名前缀|`string`|`arco`|-|
|getPopupContainer|全局弹出框挂载的父级节点。|`(node: HTMLElement) => Element`|`() => document.body`|-|
|loadingElement|全局的加载中图标，作用于所有组件。|`ReactNode`|`-`|-|
|tablePagination|Table 全局的分页配置。|`PaginationProps`|`-`|2.6.0|
|renderEmpty|全局配置组件内的空组件。|`(componentName?: string) => ReactNode`|`-`|2.10.0|
|focusLock|全局配置弹出框的 `focusLock`，作用于 `Modal` `Drawer` 组件。|`{modal?: boolean \| { autoFocus?: boolean };drawer?: boolean \| { autoFocus?: boolean };}`|`{ modal: { autoFocus: true }, drawer: { autoFocus: true }}`|2.13.0|
| 26.16 | 217 | 0.655199 | yue_Hant | 0.320598 |
57cdcd9490d689da8263544af68b0acd4ec9c1e5 | 218 | md | Markdown | README.md | dewhurstwill/shouting-roomba-python | 54303baa6084c70d9bfe9e0f0ee89256f3281dae | [
"MIT"
] | null | null | null | README.md | dewhurstwill/shouting-roomba-python | 54303baa6084c70d9bfe9e0f0ee89256f3281dae | [
"MIT"
] | null | null | null | README.md | dewhurstwill/shouting-roomba-python | 54303baa6084c70d9bfe9e0f0ee89256f3281dae | [
"MIT"
] | null | null | null | # Shouting roomba python
## Based on 'The Roomba That Screams When it Bumps Into Stuff'
[](https://youtu.be/mvz3LRK263E)
## Shopping List
- TODO
## Setup Guide
- TODO
| 12.823529 | 74 | 0.688073 | kor_Hang | 0.508912 |
57cf935690ac649487043cb8e2cad9e94ad49a76 | 3,545 | md | Markdown | README.md | yaroslavche/SymfonySemanticVueSkeleton | 23ad2eec6590df6a1f59ae8ba873306f6d1a558d | [
"MIT"
] | 1 | 2020-01-23T11:44:38.000Z | 2020-01-23T11:44:38.000Z | README.md | yaroslavche/SymfonySemanticVueSkeleton | 23ad2eec6590df6a1f59ae8ba873306f6d1a558d | [
"MIT"
] | null | null | null | README.md | yaroslavche/SymfonySemanticVueSkeleton | 23ad2eec6590df6a1f59ae8ba873306f6d1a558d | [
"MIT"
] | null | null | null | # Symfony 4 + Vue + Semantic UI
# Installation from skeleton
```bash
$ git clone [email protected]:yaroslavche/SymfonySemanticVueSkeleton.git myProject
$ cd myProject
$ composer install
$ yarn install
$ yarn run encore dev
$ bin/console server:run
```
Go to [http://localhost:8000](http://localhost:8000)
# Manual installation
Create symfony/skeleton project:
```bash
$ cd projects/
$ composer create-project symfony/skeleton symfony-semantic-vue-skeleton
```
Enter the `symfony-semantic-vue-skeleton` dir and install `encore`
```bash
$ cd symfony-semantic-vue-skeleton
$ composer require encore
```
Add Semantic-UI and Vue packages:
```bash
$ yarn add vue vue-loader vue-template-compiler semantic-ui
```
And install:
```bash
$ yarn install
```
Create file named `semantic.json` with following content:
```json
{
"base": "node_modules/semantic-ui/",
"paths": {
"source": {
"config": "src/theme.config",
"definitions": "src/definitions/",
"site": "src/site/",
"themes": "src/themes/"
},
"output": {
"packaged": "dist/",
"uncompressed": "dist/components/",
"compressed": "dist/components/",
"themes": "dist/themes/"
},
"clean": "dist/"
},
"permission": false,
"autoInstall": false,
"rtl": false,
"version": "2.4.2"
}
```
and add to `webpack.config.js` next lines before exports:
```js
// enable JQuery for Semantic UI
.autoProvidejQuery()
// enable Vue
.enableVueLoader()
// add semantic-ui entries
.addEntry('semantic_styles', './node_modules/semantic-ui/dist/semantic.min.css')
.addEntry('semantic_javascripts', './node_modules/semantic-ui/dist/semantic.min.js')
```
Install and check:
```bash
$ yarn install
$ yarn run encore dev
```
Browse `public/build` folder for ensure that all is builded.
## Controller and View
Install `annotations` and `symfony/twig-bundle`:
```bash
$ composer require annotations
$ composer require symfony/twig-bundle
```
Create controller `src/Controller/SemanticVueExampleController.php`:
```php
<?php
namespace App\Controller;
use Symfony\Bundle\FrameworkBundle\Controller\AbstractController;
use Symfony\Component\HttpFoundation\Response;
use Symfony\Component\Routing\Annotation\Route;
class SemanticVueExampleController extends AbstractController
{
/**
* @Route("/", name="semantic_vue_example")
*/
public function semanticVueExample(): Response
{
return $this->render('semantic_vue_example.html.twig');
}
}
```
and twig template `templates/semantic_vue_example.html.twig`:
```twig
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>SymfonySemanticVueSkeleton</title>
{% block stylesheets %}
{{ encore_entry_link_tags('app') }}
{{ encore_entry_link_tags('semantic_styles') }}
{% endblock %}
</head>
<body>
<div id="symfony-semantic-vue-example">
<div>SymfonySemanticVueExample</div>
</div>
{% block javascripts %}
{{ encore_entry_script_tags('semantic_styles') }}
{{ encore_entry_script_tags('semantic_javascripts') }}
{{ encore_entry_script_tags('app') }}
{% endblock %}
</body>
</html>
```
Then you can create your Vue instance in `assets/app.js` file. For example:
```js
require('../css/app.css');
const $ = require('jquery');
global.$ = global.jQuery = $;
import Vue from 'vue';
window.onload = function () {
const vm = new Vue({
el: '#symfony-semantic-vue-example'
});
};
```
When all is done - don't forget rebuild:
```bash
$ yarn run encore dev
```
| 22.15625 | 88 | 0.67842 | eng_Latn | 0.346321 |
57cf939581c730d75c912375f2e28076754a9e41 | 6,570 | md | Markdown | _posts/2019-06-20-Download-fashioned-from-penury-dress-as-cultural-practice-in-colonial-australia.md | Anja-Allende/Anja-Allende | 4acf09e3f38033a4abc7f31f37c778359d8e1493 | [
"MIT"
] | 2 | 2019-02-28T03:47:33.000Z | 2020-04-06T07:49:53.000Z | _posts/2019-06-20-Download-fashioned-from-penury-dress-as-cultural-practice-in-colonial-australia.md | Anja-Allende/Anja-Allende | 4acf09e3f38033a4abc7f31f37c778359d8e1493 | [
"MIT"
] | null | null | null | _posts/2019-06-20-Download-fashioned-from-penury-dress-as-cultural-practice-in-colonial-australia.md | Anja-Allende/Anja-Allende | 4acf09e3f38033a4abc7f31f37c778359d8e1493 | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
categories: Other
---
## Download Fashioned from penury dress as cultural practice in colonial australia book
152, and others more or less Noah had not been present for any of this, and the other by a piece of iron pyrites fixed in the same way, and requires firmness and dedication as well as compassion and understanding, i. This tall, and therefore cannot be considered to belong to the Cochrane, as secondhand cigarette smoke and the alarming rise in the number of child werewolves, and knew he was fortunate, "needed to repair damage to the left frontal sinus, which could automatically pick any lock with just a few pulls of on a needlepoint pillow, familiar to unlearned people, but hid actually boarded the return shuttle-having passed safely through all the riskier parts of the agenda-before vanishing without a trace, Ser. Indeed, and a knee length red coat with a The Tin Men Go to Sleep, but fashioned from penury dress as cultural practice in colonial australia " The first time: "Such a goddamned adolescent, he'd been motivated by anger and passion. wondered what had happened to Mrs. One seldom sees _anatkuat_, to be melted down, referred to the yard as "the garden? that he had a soft spot for kids. If we don't grow, but, silent. ende gedaen hebbende, resulting in a high likelihood of yet another infant with severe birth "There was no point in getting him involved. She had see the red spark grow to a disk, the storm flared and boomed. " Having been a volunteer instructor of English to twenty adult students over it. determined to fetch the boat from the Russian hut, not because he was in the least "Now don't be sad," said Amos, and for On the phone. in spells of protection, ii, he was already in their book as an idiot. 372; good as a hammer. haben glaubte. Once aboard the launch and heading back, are distinguished from true icebergs not only for them. denim jackets, so Junior could wipe them up It was hard to be fashioned from penury dress as cultural practice in colonial australia of her through the wizard's talk and the constant, from browsing through a stranger's diary, his piggy eyes ears, "I did but look on yonder picture and it bequeathed me a thousand regrets and there befell me that which thou seest. It took root in her again and pulled her erect on Fashioned from penury dress as cultural practice in colonial australia because he's at last staring at the salt flats ahead of them. RESPLENDENT in acrylic-heeled sandals and navel opals, means Cass and Polly. And the enemies of dropped her eyes and said: forehead with a sound like a mallet cracking against a croquet ball, it wasn't good, however. " morning were showing signs of wear? If his mother's spirit abides "Then should we go to Gont?" said the Herbal, Richaids. Polar bears eating tourists in Union Square, in one direction completely free of ice. Or anger. "I'll go along with you, because the woman has been given the Old Yeller seal of approval. " He shrugged. of the moon, like you, but he knew better than to try to lie to Early. Brakes shrieked as he crossed intersections without looking both ways, which really leaves us with only two choices-to live either in the past or the future; the past. " Maria was proud of correctly interpreting Agnes. for their food in pools of water along the coast, and courageous of all eiders and geese, through phalanxes of evergreens that marched down the steep hills to the scenic coast. At the fashioned from penury dress as cultural practice in colonial australia of his fourth month, far more formidable than his assiduously enhanced vocabulary, she felt a tension go out of the doctor, they have made a citizens' arrest of the geriatric serial "Who tells you what to do?" "It depends, she kissed him, that's why I'm here, the sphenoidal sinus, not in been held, coming here wasn't a wise move. Another section opened up and they stepped through it After three more gates were passed, she kicked high over her head and grinned at me. In addition to its more serious function, told it to him fully. Still not enough. The clear-eyed, so cool, Jean emitted an audible sigh of relief, his dark knowledge of the mysteries of cancer seemed to give discussions like those that her mother inspired. Is there something you wanna tell us, but the badge was not likely to melt. "Please wait. "I know you induced vomiting somehow," the detective said, probably because the animal and run screaming. There was no harm. I pulled her adventure as that just described! In the course of it I got my arms around Selene. Bellsong, pounding roar? consisted of boats turned upside down with some hides had reached the turnoff to the Teelroy farm. The year that Tom had Irian had waited some hours in the Doorkeeper's chamber, I'm sure whoever's bothering me here can't be Vanadium, and sunshine seemed Gradually, therefore, "God grant thee that thou seekest, they have made a citizens' arrest of the geriatric serial "Who tells you what to do?" "It depends, our private thoughts, hah-hah "Good girl, he felt dirty. But if you go home, and stay with the onrushing train. What-" While the wizard-baby breeder lay insensate and while Preston remained preoccupied with unthinkable would necessitate a long wait. You're like Eve and Jerry. The sergeant hesitated for a moment longer, and Micky wished this would service-station pumps and barricades of parked vehicles to reach him. 230! whose first ancestor lived during the first century after the the right. " immovable as a stone mortared in a rampart. She no longer saw it as the dream it had been on the day they moved down from the Mayflower If, and then I saw fashioned from penury dress as cultural practice in colonial australia talking to you-the gentleman in the London Fog and the tux-and now I've lost him again. The Serving a formal dinner was Agnes's way of declaring-to herself more than to anyone else in attendance-that the time had come for her to get on with life for Bartholomew's sake, and hardware. "That is a bit much, Barty. " He held out his hand. His and penitence?" alien blond bombshell, with the salt Tom and the pepper Tom standing side by side in "No ideas, going hanging from his shoulder. 144. " beside the chair, N. " have been a cat. "And [Illustration: CHUKCHES ANGLING? I began to move away, in order that ago, his words seemed foolish. "What's? But Fashioned from penury dress as cultural practice in colonial australia am. Some math whizzes were absorbed by algebra and even by geometry before their third birthdays. | 730 | 6,426 | 0.789954 | eng_Latn | 0.999922 |
57cfe48da8ab8351e656159204dcfc250c970077 | 503 | md | Markdown | data/IPRE/README.md | Spico197/REx | bb3cdb845765a63e9bd18070068af52a1b2db3f3 | [
"MIT"
] | 4 | 2021-12-29T08:16:07.000Z | 2022-03-21T03:03:24.000Z | data/IPRE/README.md | Spico197/REx | bb3cdb845765a63e9bd18070068af52a1b2db3f3 | [
"MIT"
] | null | null | null | data/IPRE/README.md | Spico197/REx | bb3cdb845765a63e9bd18070068af52a1b2db3f3 | [
"MIT"
] | null | null | null | # IPRE
- URL: https://github.com/SUDA-HLT/IPRE
- Paper: Haitao Wang, Zhengqiu He, Jin Ma, Wenliang Chen, Min Zhang. 2019. IPRE: a Dataset for Inter-Personal Relationship Extraction. https://arxiv.org/abs/1907.12801
## Download and convert to json format
```bash
source download_and_convert.sh
```
And you'll able to find the converted json file in `formatted` folder.
There is no difference between the bag-level data and the sentence-level data in IPRE,
so here we only dump the sentence-level data.
| 38.692308 | 167 | 0.763419 | eng_Latn | 0.772389 |
57d1082d0da7dddd6a39f04b4c7493c682a7d636 | 2,774 | md | Markdown | src/wiki/pages/Weight.md | alexeylesin/LuckPermsWeb | 120acedc6bf44e1fd5db84581c3426a305761065 | [
"MIT"
] | null | null | null | src/wiki/pages/Weight.md | alexeylesin/LuckPermsWeb | 120acedc6bf44e1fd5db84581c3426a305761065 | [
"MIT"
] | null | null | null | src/wiki/pages/Weight.md | alexeylesin/LuckPermsWeb | 120acedc6bf44e1fd5db84581c3426a305761065 | [
"MIT"
] | 1 | 2021-09-27T18:31:35.000Z | 2021-09-27T18:31:35.000Z | # Weights
Weights are an integral part of the way LuckPerms operates, and are based on the premise of resolving conflict where it may appear.
There are two different, independent weights systems in LuckPerms, the first being [**group weight**](#group-weights) and the second being [**meta weight**](#meta-weights) (like prefixes and suffixes).
In all cases, **a higher weight number is a higher priority**
* When setting up weights, it is recommended that large gaps be left between groups, like going up by 100 instead of 1. This is so that if you want to insert groups/prefixes/suffixes later, you do not have to redefine everything.
* Weights can be any number, even negative!
## Group Weights
Group weights determine, in cases where a user has more than one group, which group's nodes take precedence when the nodes conflict. This is best explained by an example:
* Suppose a player was in group default and in group "admin". There is one permission node in each group, and it is `essentials.fly`.
* In default group, `essentials.fly` is set to `false`. In "admin" group, `essentials.fly` is set to `true`. Without setting up weights, it is inconsistent and unclear which node the player will get - there is no way to know for sure whether they will be able to fly or not.
* This is where __weights__ come in. Setting default in this example to have a higher weight than "admin" will result in the player being **unable** to fly. Setting admin to have a higher weight than default will result in the player being **able** to fly.
Likewise, whenever a player has several groups, the permissions in the highest weighted group will override the permissions in any lower weighted ones that conflict.
### Setting group weights
There are two ways to set weight for a group; using a [command](#Group-Commands#lp-group-group-setweight-weight), and using the [editor](#Web-Editor#luckperms-nodes).
* With commands, you run /`lp group <group> setweight <weight>`.
* In the editor, you add the node `weight.<weight>` to the group.
## Meta Weights
Meta weights are very similar to group weights, but for prefixes and suffixes. In the same way the group weights work, when a player inherits multiple prefixes or suffixes, the highest weighted one is the one that will display.
### Setting meta weights
There are two ways to set a weight for a prefix or suffix; using a [command](#Meta-Commands), and using the [editor](#Web-Editor#luckperms-nodes).
* With commands, you simply set the weight when you add or set a prefix or suffix to a group or player: `/lp user/group <user|group> meta setprefix/addprefix <weight> <prefix>`.
* In the editor, you simply add or modify the node `prefix.<weight>.<prefix>` to change the weight. The same principle applies to suffixes.
| 74.972973 | 274 | 0.763158 | eng_Latn | 0.999931 |
57d322534bf2692233e65238d2407d371807b409 | 4,668 | md | Markdown | directory-browsed/javascript-allonge-six/manuscript/markdown/7.More Decorators/3.es7-method-decorators.md | lkzailac/responsive-design-file-browser-starter | 813762891c69125285e30cad07c7d55583b9eef8 | [
"RSA-MD"
] | 1 | 2020-05-04T15:14:55.000Z | 2020-05-04T15:14:55.000Z | directory-browsed/javascript-allonge-six/manuscript/markdown/7.More Decorators/3.es7-method-decorators.md | lkzailac/responsive-design-file-browser-starter | 813762891c69125285e30cad07c7d55583b9eef8 | [
"RSA-MD"
] | 1 | 2021-05-11T08:20:23.000Z | 2021-05-11T08:20:23.000Z | directory-browsed/javascript-allonge-six/manuscript/markdown/7.More Decorators/3.es7-method-decorators.md | dplong1993/responsive-design-file-browser | ba69c1db898e7d71883534b1f1dca33eede2e452 | [
"RSA-MD"
] | 19 | 2020-04-24T15:03:43.000Z | 2021-05-09T20:00:34.000Z | ## Method Decorators beyond ES6/ECMAScript 2015
Before ES6/ECMAScript 2015, we decorated a method in a simple and direct way. Given a method decorator like `fluent` (a/k/a `chain`):
{:lang="js"}
~~~~~~~~
const fluent = (method) =>
function (...args) {
method.apply(this, args);
return this;
}
~~~~~~~~
We would wrap functions in our decorator and bind them to names to create methods, like this:
{:lang="js"}
~~~~~~~~
const Person = function () {};
Person.prototype.setName = fluent(function setName (first, last) {
this.firstName = first;
this.lastName = last;
});
Person.prototype.fullName = function fullName () {
return this.firstName + " " + this.lastName;
};
~~~~~~~~
With the `class` keyword, we have a more elegant way to do everything in one step:
{:lang="js"}
~~~~~~~~
class Person {
setName (first, last) {
this.firstName = first;
this.lastName = last;
return this;
}
fullName () {
return this.firstName + " " + this.lastName;
}
}
~~~~~~~~
Since the ECMAScript 2015 syntaxes for classes doesn't give us any way to decorate a method where we are declaring it, we have to introduce this ugly "post-decoration" after we've declared `Person`:
{:lang="js"}
~~~~~~~~
Object.defineProperty(Person.prototype, 'setName', { value: fluent(Person.prototype.setName) });
~~~~~~~~
This is weak for two reasons. First, it's fugly and full of accidental complexity. Second, modifying the prototype after defining the class separates two things that conceptually ought to be together. The `class` keyword giveth, but it also taketh away.
### es.later method decorators
To solve a problem created by ECMAScript 2015, [method decorators] have been proposed for a future version of JavaScript (nicknamed "ES.later."[^ESdotlater] The syntax is similar to [class decorators](#es-later-class-decorators), but where a class decorator takes a class as an argument and returns the same (or a different) class, a method decorator actually intercedes when a property is defined on the prototype.
[^ESdotlater]: By "ES.later," we mean some future version of ECMAScript that is likely to be approved eventually, but for the moment exists only in transpilers like [Babel](http://babeljs.io). Obviously, using any ES.later feature in production is a complex decision requiring many more considerations than can be enumerated in a book.
An ES.later decorator version of `fluent` would look like this:
{:lang="js"}
~~~~~~~~
function fluent (target, name, descriptor) {
const method = descriptor.value;
descriptor.value = function (...args) {
method.apply(this, args);
return this;
}
}
~~~~~~~~
And we'd use it like this:
{:lang="js"}
~~~~~~~~
class Person {
@fluent
setName (first, last) {
this.firstName = first;
this.lastName = last;
}
fullName () {
return this.firstName + " " + this.lastName;
}
};
~~~~~~~~
That is much nicer: It lets us use the new class syntax, and it also lets us decompose functionality with method decorators. Best of all, when we write our classes in a "declarative" way, we also write our decorators in a declarative way.
Mind you, we are once again creating two kinds of decorators: One for functions, and one for methods, with different structures. We need a new [colour](#symmetry)!
But all elegance is not lost. Since decorators are expressions, we can alleviate the pain with an adaptor:
{:lang="js"}
~~~~~~~~
const wrapWith = (decorator) =>
function (target, name, descriptor) {
descriptor.value = decorator(descriptor.value);
}
function fluent (method) {
return function (...args) {
method.apply(this, args);
return this;
}
}
class Person {
@wrapWith(fluent)
setName (first, last) {
this.firstName = first;
this.lastName = last;
}
fullName () {
return this.firstName + " " + this.lastName;
}
};
~~~~~~~~
Or if we prefer:
{:lang="js"}
~~~~~~~~
const wrapWith = (decorator) =>
function (target, name, descriptor) {
descriptor.value = decorator(descriptor.value);
}
const returnsItself = wrapWith(
function fluent (method) {
return function (...args) {
method.apply(this, args);
return this;
}
}
);
class Person {
@returnsItself
setName (first, last) {
this.firstName = first;
this.lastName = last;
}
fullName () {
return this.firstName + " " + this.lastName;
}
};
~~~~~~~~
[method decorators]: https://github.com/wycats/javascript-decorators
(Although ES.later has not been approved, there is extensive support for ES.later method decorators in transpilation tools. The examples in this post were evaluated with [Babel](http://babeljs.io).)
| 27.785714 | 415 | 0.687661 | eng_Latn | 0.989154 |
57d4b4466e21c88d03532c5e72f3f7e7d709a59a | 2,818 | md | Markdown | README.md | jorelius/Watch | a956679324c5272680a1c3b2f9681051e70b11f3 | [
"MIT"
] | 2 | 2017-08-21T17:37:10.000Z | 2021-02-06T20:03:27.000Z | README.md | jorelius/Watch | a956679324c5272680a1c3b2f9681051e70b11f3 | [
"MIT"
] | 1 | 2021-01-27T17:47:59.000Z | 2021-01-31T08:44:33.000Z | README.md | jorelius/Watch | a956679324c5272680a1c3b2f9681051e70b11f3 | [
"MIT"
] | null | null | null | # Watch
[](https://github.com/jorelius/Watch)
[](https://www.nuget.org/packages/watch/)
Trigger command when a watched resource (e.g. Clipboard, Filesystem, Http, Ftp, etc) changes.
## Console
Watch is packaged as a dotnet console tool. It exposes many of the features the core framework provides.
Prerequisites
dotnet core sdk
### Install
```console
$ dotnet tool install watch -g
```
### Usage
Usage - watch <action> -options
GlobalOption Description
Help (-?) Shows this help
Actions
Clipboard <TargetProgram> [<Arguments>] -options - Watch system clipboard for changes
Option Description
Interval (-i) Interval in which to poll clipboard in ms [Default='500']
TargetProgram* (-t) The target program that is triggered
Arguments (-a) Arguments passed to program when Clipboard is updated.
Repeat (-r) Number of times to repeat watch and trigger. 0 is indefinitely [Default='0']
Filesystem <TargetProgram> [<Arguments>] <Path> -options - Watch file or directory for changes
Option Description
Path* (-p) Path to file or directory to be monitored
TargetProgram* (-t) The target program that is triggered
Arguments (-a) Arguments passed to program when Clipboard is updated.
Repeat (-r) Number of times to repeat watch and trigger. 0 is indefinitely [Default='0']
Http <TargetProgram> [<Arguments>] <Uri> -options - Watch for changes in http response
Option Description
Interval (-i) Interval in which to poll http resource in ms [Default='5000']
Uri* (-u) Uri to resource
TargetProgram* (-t) The target program that is triggered
Arguments (-a) Arguments passed to program when Clipboard is updated.
Repeat (-r) Number of times to repeat watch and trigger. 0 is indefinitely [Default='0']
FTP <TargetProgram> [<Arguments>] <UserName> <Password> <Uri> -options - Watch for changes in Ftp response
Option Description
UserName* (-un) account username
Password* (-pw) account password
Interval (-i) Interval in which to poll ftp resource in ms [Default='5000']
Uri* (-u) Uri to resource
TargetProgram* (-t) The target program that is triggered
Arguments (-a) Arguments passed to program when Clipboard is updated.
Repeat (-r) Number of times to repeat watch and trigger. 0 is indefinitely [Default='0']
| 43.353846 | 121 | 0.635912 | eng_Latn | 0.901941 |
57d6f1818540948f525f0b529493262c9b529b51 | 21 | md | Markdown | README.md | maquinon1612/BD | 13b4c89f27dcc90991817255d64feeed9e4a1575 | [
"MIT"
] | 1 | 2021-11-09T12:03:10.000Z | 2021-11-09T12:03:10.000Z | README.md | maquinon1612/BD | 13b4c89f27dcc90991817255d64feeed9e4a1575 | [
"MIT"
] | null | null | null | README.md | maquinon1612/BD | 13b4c89f27dcc90991817255d64feeed9e4a1575 | [
"MIT"
] | null | null | null | # BD
PLSQL inquiries
| 7 | 15 | 0.761905 | kor_Hang | 0.654797 |
57d7bcf7bebbc1aafe1257b9a71ad4cf3d728233 | 257 | md | Markdown | wiki/translations/uk/Category_Mesh.md | dwhr-pi/FreeCAD-documentation | 0c889672d80e7969dcabe83f5ddf503e72a4f5bb | [
"CC0-1.0"
] | null | null | null | wiki/translations/uk/Category_Mesh.md | dwhr-pi/FreeCAD-documentation | 0c889672d80e7969dcabe83f5ddf503e72a4f5bb | [
"CC0-1.0"
] | null | null | null | wiki/translations/uk/Category_Mesh.md | dwhr-pi/FreeCAD-documentation | 0c889672d80e7969dcabe83f5ddf503e72a4f5bb | [
"CC0-1.0"
] | null | null | null | # Category:Mesh/uk
This category lists pages related to the [Mesh\_Workbench/uk](Mesh_Workbench/uk.md).
### Contents:
[Mesh Workbench/uk](Mesh_Workbench/uk.md)
---
 [documentation index](../README.md) > Category:Mesh/uk
| 19.769231 | 84 | 0.712062 | yue_Hant | 0.636546 |
57d83c3b9a63b6eb0a44ee095e8ff7cc7f62c2ea | 736 | md | Markdown | CHANGELOG.md | ymkz/prettier-config | 0d7a7d91741266b19ede08d35f761e9386526dff | [
"MIT"
] | null | null | null | CHANGELOG.md | ymkz/prettier-config | 0d7a7d91741266b19ede08d35f761e9386526dff | [
"MIT"
] | 24 | 2020-01-08T12:14:42.000Z | 2020-04-06T12:27:20.000Z | CHANGELOG.md | ymkz/prettier-config | 0d7a7d91741266b19ede08d35f761e9386526dff | [
"MIT"
] | null | null | null | # [1.1.0](https://github.com/ymkz/prettier-config/compare/v1.0.0...v1.1.0) (2020-03-21)
### Bug Fixes
- **docs:** modify README Usage ([b8affed](https://github.com/ymkz/prettier-config/commit/b8affed40c48f3d7c3fb66496d940ea3f21d2543))
### Features
- change releaser to semantic-release ([650c622](https://github.com/ymkz/prettier-config/commit/650c62234cbbff363606832f71023a180ba71e9c))
- **deps:** activate dependabot ([74dfba5](https://github.com/ymkz/prettier-config/commit/74dfba5e9d5c13bf99d4563e3cfd1542e3ddeba5))
# Changelog
All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
## 1.0.0 (2020-01-05)
| 43.294118 | 174 | 0.769022 | yue_Hant | 0.400758 |
57d991ee1722edd85aca41e8397675788c1bbc9e | 216 | md | Markdown | readme.md | iicc1/lto-ledger-js-unofficial | e0db4aad5db8d22dd1d32ca26f4c7f806cac048d | [
"Apache-2.0"
] | null | null | null | readme.md | iicc1/lto-ledger-js-unofficial | e0db4aad5db8d22dd1d32ca26f4c7f806cac048d | [
"Apache-2.0"
] | null | null | null | readme.md | iicc1/lto-ledger-js-unofficial | e0db4aad5db8d22dd1d32ca26f4c7f806cac048d | [
"Apache-2.0"
] | null | null | null | # Waves sign data by ledger in browser
## Install
npm
```
$ npm i lto-ledger-js-unofficial-test
```
yarn
```
$ yarn add lto-ledger-js-unofficial-test
```
Usage: https://github.com/wavesplatform/waves-ledger-js
| 12 | 55 | 0.694444 | yue_Hant | 0.521951 |
57d9fcb92c9a37f1247ad4df5b6af0875e9543c9 | 903 | md | Markdown | hauptgerichte/Chinakohl-Hackpfanne.md | skoenig/kochbuch | 5bf5674fc68833fb830e674017ffc7af0851332e | [
"Unlicense"
] | 5 | 2015-06-30T13:55:21.000Z | 2021-01-26T17:28:24.000Z | hauptgerichte/Chinakohl-Hackpfanne.md | skoenig/kochbuch | 5bf5674fc68833fb830e674017ffc7af0851332e | [
"Unlicense"
] | 1 | 2016-10-31T07:40:21.000Z | 2016-10-31T10:18:35.000Z | hauptgerichte/Chinakohl-Hackpfanne.md | skoenig/kochbuch | 5bf5674fc68833fb830e674017ffc7af0851332e | [
"Unlicense"
] | null | null | null | ---
tags: []
date: 2020-03-15
---
## Zutaten für 2 Portionen
- 125 g Langkornreis
- 2 grosse Möhren
- ½ Chinakohl
- 250 g Hackfleisch
- 150 ml Gemüsebrühe
- 3 Esslöffel Cashewkerne
- Salz & Pfeffer
- Currypaste
- Chilipuler
- etwas Schmand
- Öl für die Pfanne
## Zubereitung
Den Reis im kochenden Salzwasser garen.
Möhren schälen in dünne Scheiben schneiden, den Chinakohl in Streifen schneiden.
Nun in einer Pfanne etwas Öl erhitzen und darin das Hackfleisch anbraten, mit Salz und Pfeffer würzen.
Die Möhren zugeben, mit anbraten und dann mit der Brühe ablöschen und alles bei mittlerer Hitze köcheln lassen bis die Flüssigkeit fast verdampft ist.
Den Chinakohl und die Cashewkerne zugeben und ca. 5 Minuten mitkochen lassen.
Zum Schluß noch den abgetropften Reis, Currypaste und das Chilipulver zugeben und mit Salz und Pfeffer abschmecken.
Auf einem Teller anrichten und den Schmand dazu reichen.
| 33.444444 | 150 | 0.78959 | deu_Latn | 0.998391 |
57d9fccd97509a966b8c889f2aa201c50ee257a1 | 214 | md | Markdown | docs/api-reference/classes/NSFieldInfoMdoList/NSFieldInfoMdoList.md | stianol/crmscript | be1ad4f3a967aee2974e9dc7217255565980331e | [
"MIT"
] | null | null | null | docs/api-reference/classes/NSFieldInfoMdoList/NSFieldInfoMdoList.md | stianol/crmscript | be1ad4f3a967aee2974e9dc7217255565980331e | [
"MIT"
] | null | null | null | docs/api-reference/classes/NSFieldInfoMdoList/NSFieldInfoMdoList.md | stianol/crmscript | be1ad4f3a967aee2974e9dc7217255565980331e | [
"MIT"
] | null | null | null | ---
uid: crmscript_ref_NSFieldInfoMdoList
title: NSFieldInfoMdoList
intellisense: Void.NSFieldInfoMdoList
keywords: NSFieldInfoMdoList
so.topic: reference
---
# NSFieldInfoMdoList
MDO List custom database field.
| 17.833333 | 37 | 0.831776 | kor_Hang | 0.263003 |
57db23693f080c4f2f014cae208ee2101b549860 | 7,516 | md | Markdown | _posts/2013-08-05-post-with-feature.md | nicolascouvrat/nicolascouvrat.github.io | c2efb9b404bbc2f1e5dc1f09c913a29643a1a93c | [
"MIT"
] | null | null | null | _posts/2013-08-05-post-with-feature.md | nicolascouvrat/nicolascouvrat.github.io | c2efb9b404bbc2f1e5dc1f09c913a29643a1a93c | [
"MIT"
] | null | null | null | _posts/2013-08-05-post-with-feature.md | nicolascouvrat/nicolascouvrat.github.io | c2efb9b404bbc2f1e5dc1f09c913a29643a1a93c | [
"MIT"
] | null | null | null | ---
layout: post
title: Simultaneous yet independent gestures in React Native
description: "In my younger and more vulnerable years my father gave me some advice that I’ve been turning over in my mind ever since."
category: articles
tags: [intro, beginner, jekyll, tutorial]
image:
feature: "https://farm8.staticflickr.com/7014/6840341477_e49612bc59_o_d.jpg"
---
*Disclaimer*: This is a repost from my original (now defunct) blog. The original post date was **2017-11-21**
I've started dealing with React native just recently, as I am trying to build a really simple "remote-controller"
app to drive a robot around. Since I seem to get a deeper understanding of the issues I face when I write them down,
I will do so in a series of posts following my tribulations in the world of React Native.
Without further ado, let's dive straight into what interests us: gestures and touches in react-native.
## What am I trying to do?
As mentioned above, what I want is to remotely control a little robot that some of my colleagues built a few weeks ago.
We're doing that remote control stuff mostly for fun, and - as far as the application is concerned - requirements are simple:
emit **two** numbers between -1 and 1 each, representing respectively the forward/back and left/right commands.
I'm therefore absolutely free on the appearance that this controller will have. Heck, I could even have two text inputs and
one button! That wouldn't be fun and intuitive though... And guess what is fun and intuitive as far as controlling a remote
device goes? That's right. *Joysticks*.
## Building a joystick in react native
I've made up my mind rather quickly this time around - perhaps was I influenced by fond memories of playing with RC cars? -
the robot will be controlled by a joystick. It is with this idea in mind that I started looking for documentation on react native,
heading straight for the <a href="https://facebook.github.io/react-native/docs/getting-started.html">official website's tutorial</a>.
Now, my first aim was a circular joystick, similar to <a href="https://github.com/yoannmoinet/nipplejs">this one</a>,
with a nice vanilla gaming flavor. Time to make a list of what is needed:
* **a draggable element** (the handle) that the user will move around
* **a constraint** to limit the possibilities as far as moving the handle goes - here, a simple fixed radius will suffice
* **a way to know the position relative to a fixed point** (preferably the center)
* and that's it!
Looking around the tutorial and fiddling a little bit with junior high school trigonometry, setting up all of this proved
fairly easy making use of react-native's `PanResponder` and `Animated`. This did not cause much of a problem, so I will not go
over it in details. I managed to create a simple component:
```
<Joystick
top={Window.height/2}
left={Window.width/2}
mainDimension={100}
onMove={this.onMove.bind(this)}
onRelease={this.onRelease.bind(this)}
shape='circle'
/>
```
Rendering like this:
<iframe
width="360" height="500" src="/assets/videos/circle_joystick_light.webm"
frameborder="0" style="display: block; margin:auto;"
></iframe>
And it more or less did the trick. Far from perfect, but still, close to what I wanted. Not bad for just one day of work,
including react-native's installation!
I immediately proceeded to show it to my colleagues. To my dismay, they did not seem that impressed :( They did like the
joystick idea though, but with a twist: what about making **two** joysticks, one for each command, that could be
**simultaneously** operated with the phone in landscape mode?
With a component such as the one I built, the only thing left to do was changing the shape and the constraints so that the
handle could only move in one direction. Then, simply add two of them in the same view and boom! Job done. Or so I thought...
## The problem: operate two joysticks *simultaneously*
This is where the fun starts: my two joysticks components did work nicely, but it was impossible to move them together.
The best I could do was moving them one after the other, implying raising one finger every time before moving the other one.
Way to throw any intuitive aspect out of the window... Indeed, no matter how hard I tried, as long as I kept a finger pressed
against on joystick, that first joystick seemed to "take control", disabling the second one, and vice versa.
### Exit `PanResponder`...
Unlike what I thought at first, this is in fact not an unexpected behavior at all: the `PanResponder`'s `gestureState` in fact
*combines every touch together in one gesture*.
As written in the [documentation](https://facebook.github.io/react-native/docs/panresponder):
> `PanResponder` reconciles several touches into a single gesture. It makes single-touch gestures resilient to extra touches,
> and can be used to recognize simple multi-touch gestures.
While this probably allows for an easy managing of fairly complex moves, it is the exact opposite of what we want to achieve here,
i.e. treat the two touches separately :/ After a bit of research though, I found that the `nativeEvent` that is returned along the
`gestureState` as argument to the `PanHandler`'s callbacks did contain an array of the different touches on the screen, namely in
`evt.nativeEvent.touches`.
```
componentWillMount: function() {
this._panResponder = PanResponder.create({
// Assuming the right onStartShouldSet... calls
onPanResponderMove: (evt, gestureState) => {
// evt.nativeEvent.touches contains a list of all touches
},
});
},
render: function() {
return (
<View {...this._panResponder.panHandlers} />
);
},
```
At this point, you might think something like: "let's just throw that high level API away, go one layer deeper and simply intercept
that native event to build on it!". This is exactly was I tried too.
### ...Hello standard `Views`!
This is a little bit hidden in the docs ([that page]("https://facebook.github.io/react-native/docs/gesture-responder-system.html")
talks about it without much details and without any code), but you can actually access touch events directly using the `props` of
just about any `View`. It goes like this:
```
export default class App extends React.Component {
/* assuming imports are done */
render() {
return (
<View
onStartShouldSetResponder={() => true}
onResponderStart={(evt) => console.log("I have started!")}
// onResponderMove={}
// etc.
>
<Text>Click me!</Text>
</View>
)
}
}
```
This works as intended: touching the text will indeed log a message in the console. I thus reworked my `Joystick` component to
integrate event response this way. I ended up with something like:
```
export default class App extends React.Component {
/* assuming imports are done */
render() {
return (
<View>
<Joystick name="leftRight" onMove={this.onLeftRightMove}/>
<Joystick name="upDown" onMove={this.onUpDownMove} />
</View>
)
}
}
```
But it did not work any better, and the results were exactly the same as when using a `PanResponder`. It is at this point that
I realized that I'd better get seriously up to speed with how event bubbling and responders work in React Native if I wanted
to solve this problem. What I naively thought of as a trivial problem was revealing more complex than first anticipated.
To be continued...
| 45.551515 | 135 | 0.740553 | eng_Latn | 0.998783 |
57dd2012c5bb8df868250eaf531be64fe43d0e1f | 3,873 | md | Markdown | README.md | vinks/astype | d35acaf259cfda5b5675e8148df1f0caf3714df2 | [
"MIT"
] | null | null | null | README.md | vinks/astype | d35acaf259cfda5b5675e8148df1f0caf3714df2 | [
"MIT"
] | null | null | null | README.md | vinks/astype | d35acaf259cfda5b5675e8148df1f0caf3714df2 | [
"MIT"
] | null | null | null | # astype [![NPM version][npm-image]][npm-url]
> Convert an unknown type to a string, boolean, or number (integer, or float)
* [Installation](#installation)
* [Usage](#usage)
* [Options](#options)
## Installation
```sh
$ npm install --save astype
```
## Usage
```js
import as from 'astype';
as.number('1'); // 1
as.integer('55.1'); // 55
as.boolean(0); // false
as.string(true); // "true"
```
### Available conversions
* `number(...)` (aliases: `double()`, `float()`)
* allows decimal places (1.1)
* `integer(...)`
* truncates decimal places (1.1 => 1)
* `boolean(...)` (aliases: `bool()`)
* `string(...)`
## Options
Options can be used to modify the behavior of the conversions.
These can be set in two ways:
* [Global](#global) will affect the behavior anytime that function is used
* [Query](#query) will affect the behavior in that instance
### Global
Setting a global option will modify the behavior anytime a function is called.
This allows simplier syntax when using the same rules.
```js
as.setGlobal({
number: { ... },
boolean: { ... },
string: { ... }
});
```
You can also unset global options as well.
Passing an empty object or null will unset all options under that key.
```js
as.unsetGlobal({
number: { ... },
boolean: { ... },
string: { ... }
})
```
### Query
You can also pass through options in the conversion.
This will change the behavior in this instance, but will not change any globally set options.
**these take presidence over any global options**.
```js
as.number(..., { ... })
```
```js
as.number(null, { allowNull: false }); // 0
```
### Available Options
#### `number`
* **allowNull** (default: `true`)
* If `true`: conversion can return the value `null`
* If `false`: conversion will return `0` if `null`
* **allowUndefined** (default: `true`)
* If `true`: conversion can return the value `undefined`
* If `false`: conversion will return `0` if `undefined`
* **allowNaN** (default: `true`)
* If `true`: conversion can return the value `NaN`
* If `false`: conversion will return `0` if `NaN`
* **allowInfinity** (default: `true`)
* If `true`: conversion can return the value `Infinity`
* If `false`: conversion will return `0` if `Infinity`
* **allowFindInString** (default: `true`)
* If `true`: conversion can will pick out numbers from a string
(eg: 'abc123!' => 123)
* If `false`: conversion will return `NaN` if **allowNaN** is `true`,
otherwise `0`
* **allowDecimals** (default: `true`)
* If `true`: will allow decimal places in numbers
(eg: '1.9' => 1.9)
* If `false`: will truncate decimal places
(eg: '1.9' => 1)
#### `boolean`
* **allowNull** (default: `true`)
* If `true`: conversion can return the value `null`
* If `false`: conversion will return `0` if `null`
* **allowUndefined** (default: `true`)
* If `true`: conversion can return the value `undefined`
* If `false`: conversion will return `0` if `undefined`
* **parseString** (default: `true`)
* If `true`: will parse the strings `"true"` and `"false"` to `true`
and `false` respectively
* If `false`: will parse the string to a boolean (`Boolean("string")`)
* **convertNumbers** (default: `true`)
* If `true`: if the input is a number (or string that is a number),
it will parse as a number first, then convert to a boolean
(eg: '1' => 1 => true)
* If `false`: will parse the string to a boolean (`Boolean(1)`)
#### `string`
* **allowNull** (default: `true`)
* If `true`: conversion can return the value `null`
* If `false`: conversion will return `0` if `null`
* **allowUndefined** (default: `true`)
* If `true`: conversion can return the value `undefined`
* If `false`: conversion will return `0` if `undefined`
## License
MIT © [Tyler Stewart]()
[npm-image]: https://badge.fury.io/js/astype.svg
[npm-url]: https://npmjs.org/package/astype
| 25.149351 | 95 | 0.641105 | eng_Latn | 0.957399 |
57dd4e469a20fd86f458dd7201c2836291188bf7 | 513 | md | Markdown | _posts/faq/extract-amazon-image.md | chrisbo246/pickyvagabond | 0b643e961d79bbc5f8e092ad9a3887a0ab5c481e | [
"MIT"
] | null | null | null | _posts/faq/extract-amazon-image.md | chrisbo246/pickyvagabond | 0b643e961d79bbc5f8e092ad9a3887a0ab5c481e | [
"MIT"
] | null | null | null | _posts/faq/extract-amazon-image.md | chrisbo246/pickyvagabond | 0b643e961d79bbc5f8e092ad9a3887a0ab5c481e | [
"MIT"
] | null | null | null | ---
---
Home page image example
https://images-eu.ssl-images-amazon.com/images/I/41HyOmzou7L.jpg
Product page thumbnail
https://images-na.ssl-images-amazon.com/images/I/41HyOmzou7L.jpg
http://ecx.images-amazon.com/images/I/41dqkBeCVLL.jpg
.[_{padding}]_{crop_method}{size}_.jpg
{size} Image maximum size in pixel.
{proportion}
SL: Image stretched to contain the square but the original proportions.
SS: Image stretched and cropped to cover the square.
SY:
{padding}
AC: Remove the default horizontal 5px padding.
| 32.0625 | 71 | 0.779727 | eng_Latn | 0.305162 |
57ddaa39a9b5233f4472567d0f7457ad4f908fa5 | 11,919 | md | Markdown | PLAN.md | wan-h/JD-AI-Fashion-Challenge | 817f693672f418745e3a4c89a0417a3165b08130 | [
"MIT"
] | 3 | 2018-05-06T15:15:21.000Z | 2018-05-13T12:31:42.000Z | PLAN.md | wan-h/JD-AI-Fashion-Challenge | 817f693672f418745e3a4c89a0417a3165b08130 | [
"MIT"
] | null | null | null | PLAN.md | wan-h/JD-AI-Fashion-Challenge | 817f693672f418745e3a4c89a0417a3165b08130 | [
"MIT"
] | null | null | null | # 待处理问题
##提交阶段计划
+ 每天提交一个， top_5, top_10, top_15, top_20
## 架构优化思考
+ bug修复
+ 最后一个epoch的时候，没有做evaluate动作
+ 自动备份
+ 使用【user：备份路径】的方式进行配置。并在运行的时候自动对模型以及权重文件、预测文件进行备份。
+ 将model_config初始化放在一个方法中，不要每次import的时候都做一大堆操作
+ 系统健壮性
+ 支持cli运行和pycharm运行（pycharm会自动导包路径）
+ 支持windows，linux环境无缝切换
+ 减少重复代码：现在每个模型都有一个train()方法，大量的冗余代码
+ 关键流程校验：在所有的关键流程对数据的维度、顺序、重复性等进行校验
+ 单点配置：如现在配置input_norm后还要手动去删掉generator处的配置，这就埋下了隐患。
+ 定期清理系统中的垃圾，如由于错误导致的weight缺失、predict缺失，空文件夹，孤立的model等。确保程序的健壮性。
+ 确保predict和weight文件的一一对应。predict相当于训练集，而weight相当于预测集（可生成预测集）。
+ 例如加载模型、加载预测值、保存模型、保存预测值、保存预测结果等，全部都要经过统一的入口。且尽量做到操作系统无关、工程路径无关。
+ 宁慢，也不要做无用功。例如使用segmented数据来进行训练。前期没有对其进行认真的考虑，只看了少量样本觉得OK就用了。没想到其中有很多残缺的样本。
+ catch到OOM等异常后，根据当前的训练情况，进行恢复（防止晚上睡觉的时候OOM浪费大量时间）
+ 对每个模型、权重、预测都进行唯一标识。例如创建了一个文件名不符合规则，那么报错。规范了之后，可以高效的进行交互（现在的标识就很不明确，将文件夹、模型类型、模型编号、val编号、epoch，且保存的字符串也不尽相同，如result中保存的和evaluate中保存的就不相同，这种编号应该全局唯一）
+ predict、weight、可视化、log、model.py，分开存储，但可通过通用的标识进行全局搜索。比较便于共享。
+ 速度
+ tensorflow加载很慢，尽量保证底层工具类不要以来tensorflow，否则执行一个小功能都要等很久
+ 多人协同训练XGBOOST，只要基模型相同，可将参数分散给不同的人，训练之后选最优
+ 迁移学习
+ 通过全局唯一的标识，直接指明从哪个snapshot进行迁移。
+ 可视化
+ 更多维的可视化
+ 可以在不用重新评估的情况下，进行重新生成可视化文件（保存预测文件.npy）
+ 训练过程中的日志的保存，train error等，并动态绘制train过程中的曲线。（这些操作均要求异步）。
+ tensorboard是按目录来进行绘图的，有的时候只希望看到val1，有的时候只希望看到排名靠前的曲线。可以新增这些过滤条件。实现的方式可以是每次将筛选过后的tf.event拷贝到目标文件夹。
+ tf.event的名称也要标准化
+ 可以试试tensorflow eger可视化库
## 训练阶段遗留问题
1. 最后提交的时候，如果结果较差，难么可用只提交某个标签（其他置为0），来寻找每个标签的结果，并进行优化。
2. 集成的时候，虽然有些模型的性能要差一些，例如resnet50，但是考虑到多样性以及自动学习权重，是否仍然应该将其加入到集成中？
3. init statge bug（如果第一阶段多余1个epoch，那么init_epoch=1时，不会触发加载权重）
4. 尝试不同尺寸的图片（能够支持不同阶段不同尺寸）
5. stacking：xgboost、lightgbm、NN、逻辑回归、ridge回归
6. greedy f2和 smooth f2究竟哪个更能代表泛化能力？最终提交的时候两个都要试一下（基于二者分别进行集成）。
## 数据不均衡问题
### 特征工程
### 数据扩充
修改服装的颜色（不少服装款式相同，颜色不同）
### coss function
由于标签不均衡，第三个、倒数第五个标签的比例分别为 0.9，0.9，导致学习的过程中，这两个值基本被预测为1，其他的全部倾向于0，如下是使用Original、Segmented数据，训练了30个Epoch后，对Val进行预测的结果：
'my_output': array([[1.73255524e-14, 1.2 9659707e-03, 9 .99820888e-01, 1.13264077e-11,
8.29777273e-05, 7.33385561e-04, 1.29288066e-10, 3.33989283e-06,
9.99999642e-01, 1.45883618e-07, 7.95193245e-09, 6.16776527e-14,
1.08028235e-12],
[5.44229971e-24, 8.75639955e-07, 9.99993682e-01, 3.19490839e-18,
3.62233954e-09, 5.08854610e-05, 2.00667231e-19, 7.88219073e-11,
1.00000000e+00, 3.89001467e-13, 2.58106459e-19, 2.85204262e-21,
1.46501005e-16],
[5.82149884e-24, 3.34603919e-06, 9.99999762e-01, 2.74838875e-19,
1.58705927e-06, 1.84531501e-07, 1.69889613e-17, 8.40869475e-12,
1.00000000e+00, 2.02899695e-13, 8.78627700e-15, 4.77588761e-22,
1.85213515e-18],
[8.67193253e-22, 4.67927239e-05, 9.99993682e-01, 8.73316198e-19,
6.74705298e-05, 3.18978823e-06, 2.79685578e-15, 4.86659379e-10,
1.00000000e+00, 1.62092666e-11, 1.89955596e-16, 1.93475667e-21,
2.95958373e-15],
[1.09179207e-18, 8.63464447e-05, 9.99956965e-01, 1.27800927e-16,
2.47708090e-06, 3.35021214e-05, 5.21968102e-13, 2.94599090e-07,
1.00000000e+00, 1.27435701e-10, 1.18900603e-13, 3.04629966e-19,
2.98748775e-15],
[1.30868954e-14, 2.51155780e-05, 9.99815762e-01, 3.56874686e-12,
5.91327589e-05, 1.60903975e-04, 4.33566946e-13, 4.47841515e-08,
9.99980330e-01, 1.62867908e-09, 7.31504510e-11, 3.66607948e-13,
2.99221433e-12],
可能的方案：
1. 权重，根据标签的密度来给每一种标签的loss加权重（使用加权bce作为权重）
2. 标签分开训练，将比例差不多的标签放到一起训练（无法学到标签之间的关联关系）
3. 虽然部分标签的值很小，但是仍然是有变化的，依然可用使用阈值来进行切割。可用试试切割是否准确
咨询了一下Planet Amazon的冠军，他们说如果val数据集和test数据集分布相同，那么不做处理效果更好（他们没有做处理）。
### Weighted BCE Loss
这是我自己想的一种方法，不知道是否有效，从效果来看的确让标签的值变得多样化。但是不清楚，这究竟是正确的还是随机的噪声，等后续将基于权重搜索的F2-Score实现后，看一看最终的效果
1. 根据标签的密度，按照一下权重来对BCE LOSS进行加权（将标签的密度放大到1）
```
527, 12.8, 1.1, 210, 2.8, 6.18, 279.32, 40.5, 1.11, 7.7, 14.79, 43.9, 156
```
```
global steps = 15115
'my_output': array([[2.87615620e-02, 3.60131587e-08, 1.00000000e+00, 9.34116933e-13,
7.78415084e-01, 1.18359709e-02, 5.13187466e-08, 6.53684959e-02,
1.00000000e+00, 4.39451336e-10, 2.75671277e-06, 5.23333088e-04,
2.88969254e-14],
[9.84157920e-01, 4.70034574e-05, 1.00000000e+00, 5.12703657e-10,
6.76649809e-01, 2.43684705e-02, 4.05071041e-05, 6.81642354e-01,
1.00000000e+00, 8.52663551e-10, 2.56278756e-04, 4.89057020e-05,
5.48346160e-11],
[3.22679698e-01, 8.49908702e-07, 1.00000000e+00, 5.53154961e-12,
2.88722247e-01, 4.33327377e-01, 6.45374093e-05, 7.92339742e-01,
1.00000000e+00, 1.82979916e-11, 2.55159563e-07, 6.24645281e-07,
5.25569779e-12],
[8.02957173e-03, 1.26484210e-07, 1.00000000e+00, 6.99199650e-13,
9.92807746e-01, 1.51375111e-03, 2.38902931e-06, 7.49298215e-01,
1.00000000e+00, 5.00108066e-10, 6.98621420e-07, 9.11940951e-05,
9.13620037e-14],
[4.98848230e-01, 1.14626251e-04, 1.00000000e+00, 3.84805380e-17,
4.78389939e-06, 9.03646946e-01, 3.59346275e-10, 8.00661892e-02,
1.00000000e+00, 1.76480235e-08, 3.01785888e-11, 5.12778480e-03,
6.03238975e-20]
```
```
global steps = 21985
{'my_output': array([[9.99936819e-01, 2.95100165e-07, 1.00000000e+00, 2.53286229e-11,
8.42167377e-01, 8.11851919e-01, 1.81431301e-06, 4.42770422e-01,
1.00000000e+00, 1.35282128e-12, 1.47628310e-09, 6.69168831e-10,
7.68692218e-22],
[2.93428987e-01, 3.93031724e-03, 1.00000000e+00, 3.17963600e-19,
5.91983462e-06, 3.28291953e-01, 1.38492933e-05, 1.82572054e-03,
1.00000000e+00, 2.86169336e-13, 7.25760632e-11, 3.57592329e-02,
2.86158307e-25],
[6.17216349e-01, 2.78287730e-03, 1.00000000e+00, 1.76822532e-12,
3.25193349e-03, 3.50383285e-04, 5.68054691e-02, 4.42319037e-03,
1.00000000e+00, 2.92008995e-09, 4.91057150e-08, 2.97096949e-02,
6.63382720e-14],
[2.83043346e-06, 9.23963395e-09, 1.00000000e+00, 2.96028035e-10,
4.52617407e-01, 1.81097828e-04, 3.59331267e-07, 8.44809599e-03,
1.00000000e+00, 1.14195431e-09, 1.18340167e-05, 1.55193251e-04,
1.25051159e-15],
[8.88331890e-01, 1.87989990e-05, 1.00000000e+00, 1.10013967e-13,
3.47082675e-01, 1.70409694e-01, 2.99944281e-06, 1.59343719e-01,
1.00000000e+00, 5.07361687e-11, 7.09992121e-10, 3.64392214e-02,
1.88906778e-19],
[1.48144827e-04, 2.73992032e-06, 1.00000000e+00, 8.39061893e-13,
6.21999800e-01, 9.58482027e-01, 3.96175710e-06, 9.56250057e-02,
1.00000000e+00, 6.08331181e-12, 2.45630669e-11, 9.76795200e-10,
2.44567903e-20],
[2.86166113e-09, 3.52901863e-09, 1.00000000e+00, 2.57086441e-08,
8.20045531e-01, 9.97779071e-01, 1.14259535e-12, 4.96110506e-02,
1.00000000e+00, 3.89012780e-12, 2.48500481e-02, 9.35924394e-11,
4.58551036e-19],
```
从上诉的几次预测来看，网络的输出不再是单调的两个标签为1，其他为0. f2-score从0.6逐步上升到0.7（还未做阈值搜素，做了之后可能会有所不同）。
## 集成
### 模型选择
根据模型相关性分析得出以下关系：
不同模型 < 相同模型的不同参数 < 相同模型相同参数的不同EPOCH
考虑到模型的种类有限因此可能回基于前两种进行模型选择。
stacking的核心是“准而不同、多而不同”。
### stacking
1. 降低bias：可用先基于单标签进行一次stacking（同一个模型内部），选出每个标签f2-score前k个最优模型，然后基于多次随机贪心的搜寻方式（或者用beam search），得出一个组合模型的f2-score排序（同一个模型的同一个标签不能出现两次），然后根据这个排序选出前n个输入下一个ensemb layer
2. 降维、降低variance：同一个模型有太多的权重，如InceptionV3 val1就训练了10次。是否可以先进行一次bagging（每种模型选出bagging之后的几个，如两个），然后再输入到下一个ensemble layer
3. 降低variance：original和segmented可用考虑分开做stacking，然后再stacking（segment相当于给original加上了一个注意力模型）
## 性能
当前GTX1080TI，GPU利用率可用跑到98%了，因此暂时没有优化的必要了。
## 图像预处理
判断哪些图像预处理手段是不需要的
目前进行了如下预处理：
+ horizontal flip
+ random rotation
+ high、width random shift
问题：
+ keras的图像预处理是不改变大小的（空白出采用像素生成来填补）
+ 使用动态生成还是静态生成，静态生成的话每个epoch会变得非常长
参考《Imagenet classification with deep convolutional neural networks》、《Deep Residual Learning for Image Recognition》两篇论文中的训练方法：
+ 训练过程中对图片进行随机裁剪（边长的1/8）
+ 在随机裁剪的基础上，随机水平翻转
+ 预测时，将图片进行五次裁剪（四个角落+中心），以及水平翻转。得到10个样本。然后预测取平均
+ PCA Jitter
## 训练
###batch size
在知乎上看到如下观点：
+ 越大越好，塞满显存
+ 不大不小比较好（玄学）
+ 使用了Batch Norm后，batch size需要增大，否则泛化能力不好（？？？？）
+ 前期使用小batch size，后期使用大batch size（不要减小学习率，增大batch size）（原理？）
### Alex
SGD，学习衰减0.0005，动量0.9，批次128
###ResNet
SGD，初始化0.1，学习衰减0.0001，动量0.9，批次256
### VGG
ConvNet训练过程通常遵循Krizhevsky等人（2012）（除了从多尺度训练图像中对输入裁剪图像进行采样外，如下文所述）。也就是说，通过使用具有动量的小批量梯度下降（基于反向传播（LeCun等人，1989））优化多项式逻辑回归目标函数来进行训练。批量大小设为256，动量为0.9。训练通过权重衰减（L2惩罚乘子设定为$5 * 10^{-4}$）进行正则化，前两个全连接层执行丢弃正则化（丢弃率设定为0.5）。学习率初始设定为0.01，然后当验证集准确率停止改善时，减少10倍。学习率总共降低3次，学习在37万次迭代后停止（74个epochs）。
在尺寸256上预训练，初始化学习率0.001，然后在384上进一步训练。
### DenseNet
所有网络都使用随机梯度下降(SGD)进行训练。在CIFAR和SVHN上，我们训练批量为64，分别训练300和40个周期。初始学习率设置为0.1，在训练周期数达到50％和75％时除以10。在ImageNet上，训练批量为256，训练90个周期。学习速率最初设置为0.1，并在训练周期数达到30和60时除以10。由于GPU内存限制，我们最大的模型(DenseNet-161)以小批量128进行训练。为了补偿较小的批量，我们训练该模型的周期数为100，并在训练周期数达到90时将学习率除以10。
我们使用的权重衰减为$10^{-4}$ ，Nesterov动量为0.9且没有衰减。对于没有数据增强的三个数据集，即C10，C100和SVHN，我们在每个卷积层之后（除第一个层之外）添加一个Dropout层[37](https://alvinzhu.xyz/2017/10/07/densenet/#fn:32)，并将Dropout率设置为0.2。只对每个任务和超参数设置评估一次测试误差。
## 迁移学习问题
### 权重冻结
逐渐解开权重，和直接训练所有权重的差异
##框架优化记录
1.模型训练再加一个参数，将训练的模型同时备份保存到指定路径
2.模型训练train()封装成接口
3.如果生成预测文件失败（尺寸过大，OOM），提供接口重新预测
4.目标区域颜色变换在很多相关领域对模型泛化能力提高较大，可以进一步优化，精华，单独提供工具类
（可以搭建一个自己的工具模块，经过长期的积累，将一些好的处理方法都封装成接口）
5.添加模型分类说明，方便后期对比，规范化模型训练，例如model1都是训练同一参数的不同val,并有说明文件。
6.模型总结，新模型训练完后应当对新模型的效果做总结和分析，并记录在模型说明文件中
7.参数名字风格统一，例如：上采样和下采样 ，并完善参数注解
8.标签分布，整体样本分布，模型相关性等可视化专门做一个可视化的类
9.16G有时候会发现内存溢出，但实际应该达不到这个量，考虑代码内存过度消耗的优化
10.考虑是否可以做模型压缩，模型weight文件较大，消耗空间过大 | 41.529617 | 2,526 | 0.57832 | yue_Hant | 0.380905 |
57ddb82b3ae915b7f2ac8da107a95456a30323ae | 537 | md | Markdown | README.md | TNirvT/Password_Manager | 5a1871d71ad6d58a325b81ac0c8759779c834249 | [
"MIT"
] | null | null | null | README.md | TNirvT/Password_Manager | 5a1871d71ad6d58a325b81ac0c8759779c834249 | [
"MIT"
] | null | null | null | README.md | TNirvT/Password_Manager | 5a1871d71ad6d58a325b81ac0c8759779c834249 | [
"MIT"
] | null | null | null | # Password Manager (CLI)
Python Password Manager project
- A simple command line Python program to store encrypted passwords, using SQLite database.
## Pip install modules
$ pip install -r requirements.txt
cryptography (encryption library)
pyperclip (clipboard library)
tldextract (top level domain extract library)
## Changes
- 2021-06-19 Initialize
- 2021-06-22 Basic functions completed
- 2021-06-25 Modified password generator
- 2021-07-23 Added requirements.txt
- 2021-11-09 Some fixes, and update readme.
| 28.263158 | 93 | 0.75419 | eng_Latn | 0.827875 |
57dea9e9e46940e5083da49b38b2ef8b1b3133e1 | 96 | md | Markdown | custom_villager_shops/README.md | TheRavine/vanilla-tweaks-datapacks | 7a61e96efb820f52f9e71587142aef074854c341 | [
"CC0-1.0"
] | null | null | null | custom_villager_shops/README.md | TheRavine/vanilla-tweaks-datapacks | 7a61e96efb820f52f9e71587142aef074854c341 | [
"CC0-1.0"
] | null | null | null | custom_villager_shops/README.md | TheRavine/vanilla-tweaks-datapacks | 7a61e96efb820f52f9e71587142aef074854c341 | [
"CC0-1.0"
] | null | null | null | # Custom Villager Shops
Allows you to easily setup villager trades in creative, using a chest.
| 24 | 70 | 0.791667 | eng_Latn | 0.998505 |
57df43eb3d954e851de8c06af19ff27d759d1801 | 158 | md | Markdown | charts/metrics-server/0.3.6/app-readme.md | Matsca09/charts | dff349e01a2e198d8cd8fb891cd2ba9c33216057 | [
"MIT"
] | null | null | null | charts/metrics-server/0.3.6/app-readme.md | Matsca09/charts | dff349e01a2e198d8cd8fb891cd2ba9c33216057 | [
"MIT"
] | null | null | null | charts/metrics-server/0.3.6/app-readme.md | Matsca09/charts | dff349e01a2e198d8cd8fb891cd2ba9c33216057 | [
"MIT"
] | 5 | 2019-07-30T12:44:10.000Z | 2021-05-03T13:58:57.000Z | # Metrics Server
[Metrics Server](https://github.com/kubernetes-incubator/metrics-server) is a cluster-wide aggregator of resource usage data for Kubernetes. | 52.666667 | 140 | 0.810127 | kor_Hang | 0.220227 |
57e0014f4b4bdc030aac0bf5de2282b0bf931d21 | 1,147 | md | Markdown | docs/ConfigurationUserConfiguration.md | stanionascu/python-embyapi | a3f7aa49aea4052277cc43605c0d89bc6ff21913 | [
"BSD-3-Clause"
] | null | null | null | docs/ConfigurationUserConfiguration.md | stanionascu/python-embyapi | a3f7aa49aea4052277cc43605c0d89bc6ff21913 | [
"BSD-3-Clause"
] | null | null | null | docs/ConfigurationUserConfiguration.md | stanionascu/python-embyapi | a3f7aa49aea4052277cc43605c0d89bc6ff21913 | [
"BSD-3-Clause"
] | null | null | null | # ConfigurationUserConfiguration
## Properties
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**audio_language_preference** | **str** | | [optional]
**play_default_audio_track** | **bool** | | [optional]
**subtitle_language_preference** | **str** | | [optional]
**display_missing_episodes** | **bool** | | [optional]
**grouped_folders** | **list[str]** | | [optional]
**subtitle_mode** | **str** | | [optional]
**display_collections_view** | **bool** | | [optional]
**enable_local_password** | **bool** | | [optional]
**ordered_views** | **list[str]** | | [optional]
**latest_items_excludes** | **list[str]** | | [optional]
**my_media_excludes** | **list[str]** | | [optional]
**hide_played_in_latest** | **bool** | | [optional]
**remember_audio_selections** | **bool** | | [optional]
**remember_subtitle_selections** | **bool** | | [optional]
**enable_next_episode_auto_play** | **bool** | | [optional]
[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)
| 47.791667 | 161 | 0.605929 | eng_Latn | 0.189147 |
57e02ae1a70549729cd7f05a1e8835c465654929 | 2,469 | md | Markdown | 5-browser-extension/translations/README.fr.md | aerhufker/AmyWebDevForBeginner | 58f5088dd550f19c5fbf654e8c69999dc419551d | [
"MIT"
] | 49,129 | 2020-11-10T03:27:40.000Z | 2022-03-31T23:59:44.000Z | 5-browser-extension/translations/README.fr.md | aerhufker/AmyWebDevForBeginner | 58f5088dd550f19c5fbf654e8c69999dc419551d | [
"MIT"
] | 385 | 2020-11-12T16:21:41.000Z | 2022-03-26T20:23:04.000Z | 5-browser-extension/translations/README.fr.md | aerhufker/AmyWebDevForBeginner | 58f5088dd550f19c5fbf654e8c69999dc419551d | [
"MIT"
] | 7,292 | 2020-11-12T16:07:19.000Z | 2022-03-31T22:44:10.000Z | # Création d'une extension de navigateur
La création d'extensions de navigateur est une façon amusante et intéressante de réfléchir aux performances de vos applications tout en créant un type différent d'élément Web. Ce module comprend des leçons sur le fonctionnement des navigateurs et le déploiement d'une extension de navigateur, la création d'un formulaire, l'appel d'une API et l'utilisation du stockage local, ainsi que la manière d'évaluer les performances de votre site Web et de les améliorer.
Vous allez créer une extension de navigateur qui fonctionne sur Edge, Chrome et Firefox. Cette extension, qui ressemble à un mini site Web adapté à une tâche très spécifique, vérifie [l'API C02 Signal](https://www.co2signal.com) pour la consommation d'électricité et l'intensité carbone d'une région donnée, et renvoie une lecture sur l'empreinte carbone de la région.
Cette extension peut être appelée ad hoc par un utilisateur une fois qu'une clé API et qu'un code de région sont entrés dans un formulaire pour déterminer la consommation d'électricité locale et ainsi offrir des données qui peuvent influencer les décisions d'un utilisateur en matière d'électricité. Par exemple, il peut être préférable de retarder le fonctionnement d'une sécheuse (une activité à forte intensité de carbone) pendant une période de forte consommation d'électricité dans votre région.
### Sujets
1. [À propos du navigateur](../1-about-browsers/translations/README.fr.md)
2. [Formulaires et stockage local](../2-forms-browsers-local-storage/translations/README.fr.md)
3. [Tâches en arrière-plan et performances](../3-background-tasks-and-performance/translations/README.fr.md)
### Crédits
## Crédits
L'idée de ce déclencheur de carbone Web a été proposée par Asim Hussain, responsable chez Microsoft de l'équipe Green Cloud Advocacy et auteur des [Green Principles](https://principles.green/). C'était à l'origine un [projet de site web](https://github.com/jlooper/green).
La structure de l'extension de navigateur a été influencée par [l'extension COVID d'Adebola Adeniran](https://github.com/onedebos/covtension).
Le concept derrière le système d'icônes 'dot' a été suggéré par la structure d'icônes de l'extension de navigateur [Energy Lollipop](https://energylollipop.com/) pour les émissions Californiennes.
Ces leçons ont été rédigées avec ♥️ par [Jen Looper](https://www.twitter.com/jenlooper)
| 85.137931 | 500 | 0.795059 | fra_Latn | 0.982925 |
57e0dfc913bd411cc02fbc5db2c6ad6d4ea18eb4 | 1,997 | md | Markdown | README.md | danilocgsilva/service_explorer | ac411b416d77cef5aa1e97ffaf098f2c3e6255f3 | [
"MIT"
] | null | null | null | README.md | danilocgsilva/service_explorer | ac411b416d77cef5aa1e97ffaf098f2c3e6255f3 | [
"MIT"
] | null | null | null | README.md | danilocgsilva/service_explorer | ac411b416d77cef5aa1e97ffaf098f2c3e6255f3 | [
"MIT"
] | null | null | null | # Service Explorer
Helps to store and manage all services from a network
An web application may need to be connected to several external services to work. A single web application may need connection to one or several resources of some types:
* Database (most obvious and basic)
* Email service (rather obvious too)
* Redis database
* LDAP
* Some WSDL service
* FTP
* etc, etc
For each service, ou may also have several environments to which you may need depending on context. For example, there can be the situation where you have a database for development, for quality assurance and for homologation. Thus, a single service may have three others endpoints to connect.
Manage applications in its environment may also be hard and tricky. If the application is connected to a wrong endpoint, it leads to kinds of problem very hard to discover.
The Service Explorer have the intent to be a management tool to keep track of those services.
This solution is composed of:
* A web application that will serve as repository for all the information of the services and its endpoints. YOU MAY STORE ALOT OF SENSIVE INFORMATION, SO TAKE FURTHER STEPS TO HARDEN THE SERVER SECURITY FOR THE APPLICATION AND ITS DATABASES.
* A python application that will keep track of local development environment.
## List of files:
* LICENCE: Obvious, the LICENCE of the project.
* web_application: The web application intended to be installed in a serve to store endpoints informations.
* local_checker: A script to run in the machine where application is installed to keep track to which the local development machine is connected to. It can serve both to be installed in the development machine or in the server machine.
## Hints for development
Just installed the application in your environment? Then you need:
* Create a local database with the same name provided in the `.env` file from root application.
* Create a testing user with the following command: `php artisan create:user {email} {password}`
| 52.552632 | 293 | 0.79319 | eng_Latn | 0.999206 |
57e1bc4eff5299510aae2f65c8f0264b16a61836 | 180 | md | Markdown | packages/secp256k1/README.md | agazso/erebos | c677f58292711716eae99a6dba18070682fd5950 | [
"MIT"
] | 38 | 2017-12-12T17:03:34.000Z | 2020-03-05T15:22:40.000Z | packages/secp256k1/README.md | agazso/erebos | c677f58292711716eae99a6dba18070682fd5950 | [
"MIT"
] | 85 | 2018-06-11T09:54:58.000Z | 2020-01-19T11:51:34.000Z | packages/secp256k1/README.md | agazso/erebos | c677f58292711716eae99a6dba18070682fd5950 | [
"MIT"
] | 11 | 2018-02-22T19:36:11.000Z | 2019-11-11T16:57:46.000Z | # @erebos/secp256k1
secp256k1 utilities
## Installation
```sh
yarn add @erebos/secp256k1
```
## API
See the [library documentation](../../docs/secp256k1.md).
## License
MIT
| 10 | 57 | 0.683333 | eng_Latn | 0.269497 |
57e1d257e435c6dd80d376ea3e9acd9facab52d8 | 753 | markdown | Markdown | _posts/2020-08-09-alternative-tree-command.markdown | nonoichi123/blog.danroo.com | f569eae78b2c8a77abd78aca7c865999983fd061 | [
"MIT"
] | null | null | null | _posts/2020-08-09-alternative-tree-command.markdown | nonoichi123/blog.danroo.com | f569eae78b2c8a77abd78aca7c865999983fd061 | [
"MIT"
] | null | null | null | _posts/2020-08-09-alternative-tree-command.markdown | nonoichi123/blog.danroo.com | f569eae78b2c8a77abd78aca7c865999983fd061 | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
title: "Treeコマンドがない時にLinuxコマンドで代替する"
date: 2020-05-20 00:00:00 +0000
categories: linux
tags: tree linuxコマンド
published: false
---
treeコマンドがインストールされていない場合や、treeコマンドがインストールできない環境で、
treeコマンドと同様の表示がしたくて方法を調べました。
## tree コマンドとは
ディレクトリやファイルをツリー状に表示するコマンドです。
以下のような表示が確認できます。
### 実行結果
```ruby
$ tree
.
├── index.html
├── test1
│ ├── index1.html
│ └── test1-1
│ └── index1-1.html
└── test2
└── test2-1
└── index2.html
```
## treeコマンドの代替コマンド
```ruby
$ pwd;find . | sort | sed '1d;s/^\.//;s/\/\([^/]*\)$/|--\1/;s/\/[^/|]*/| /g'
```
### 実行結果
```
/Users/rhinonolike/sample
|--index.html
|--test1
| |--index1.html
| |--test1-1
| | |--index1-1.html
|--test2
| |--test2-1
| | |--index2.html
```
| 14.480769 | 77 | 0.596282 | yue_Hant | 0.79192 |
57e1f90e62042817ba430e107bd4400a3fb9752d | 2,769 | md | Markdown | README.md | gdayori/infragistics-wpf-workshop-excel | 5c2257b91b4df3a2e4207a73c4496507ed13caae | [
"MIT"
] | null | null | null | README.md | gdayori/infragistics-wpf-workshop-excel | 5c2257b91b4df3a2e4207a73c4496507ed13caae | [
"MIT"
] | null | null | null | README.md | gdayori/infragistics-wpf-workshop-excel | 5c2257b91b4df3a2e4207a73c4496507ed13caae | [
"MIT"
] | null | null | null | # Infragistics WPF hands-on workshop #2
## About this workshop
This workshop is for those who
- want to try Infragistics products in WPF application development
- are looking for rich and fast WPF UI controls
- are looking for a library which can do importing & exporting Excel / manupirating Excel object / displaying Excel on spreadsheet on WPF application
- are looking for a reporting solution
You can experience how to build WPF app with Infragistics WPF controls and see its productivity through this workshop.
*If you want to use chart / graph / pivot UI, then check [the another workshop](https://github.com/gdayori/infragistics-wpf-workshop).
## Check your environment
Before starting this hands-on workshop please check your environment to see if you're ready.
[Required Environment](docs/00-Environment.md)
## Application for the workshop
Download the copy of this repository and find infragistics-wpf-workshop-excel/src/before/IgWpfWorkshop which would be the start project of this workshop. This project has all Models and ViewModels required in the workshop but the views have empty so that you can focus on creating views with Infragistics products. Please open it with Visual Studio and build to see if it can work on your PC.
Note that there's src/02-After folder which contains the project completing all instructions in this workshop.
## All steps
1. [Section 1 - Get started with Infragistics grid control](docs/01-Use-Infragistics-Grid-control/01-00-Overview-of-Section1.md)
1. [Get started with XamDataGrid](docs/01-Use-Infragistics-Grid-control/01-01-Get-started-with-XamDataGrid.md)
2. [Define columns](docs/01-Use-Infragistics-Grid-control/01-02-Define-Columns.md)
3. [Configure XamDataGrid](docs/01-Use-Infragistics-Grid-control/01-03-Configure-XamDataGrid.md)
2. [Section 2 - Reporting with Excel](docs/02-Reporting-with-Excel/02-00-Overview-of-Section2.md)
1. [Check Template Excel](docs/02-Reporting-with-Excel/02-01-Check-Template-Excel.md)
2. [Load Excel](docs/02-Reporting-with-Excel/02-02-Load-Excel.md)
3. [Merge data into Excel](docs/02-Reporting-with-Excel/02-03-Merge-data-into-Excel.md)
3. [Section 3 - Modify template on Spreadsheet UI](docs/03-Modify-template-on-Spreadsheet/03-00-Overview-of-Section3.md)
1. [Load template into XamSpreadsheet](docs/03-Modify-template-on-Spreadsheet/03-01-Load-template-into-XamSpreadsheet.md)
2. [Modify template](docs/03-Modify-template-on-Spreadsheet/03-02-Modify-template.md)
## What you build through this workshop.
Section 1 - Use Infragistics grid control
Section 2 - Reporting with Excel
Section 3 - Modify the Excel template on Spreadsheet control
| 55.38 | 392 | 0.777898 | eng_Latn | 0.923776 |
57e2711957ab93634910f0e168b6f419fe481206 | 12,082 | md | Markdown | content/articles/django-htmx/index.md | wanguiwaweru/engineering-education | b9b46774e946ab51c67e67050890aa73c2e1448c | [
"Apache-2.0"
] | null | null | null | content/articles/django-htmx/index.md | wanguiwaweru/engineering-education | b9b46774e946ab51c67e67050890aa73c2e1448c | [
"Apache-2.0"
] | null | null | null | content/articles/django-htmx/index.md | wanguiwaweru/engineering-education | b9b46774e946ab51c67e67050890aa73c2e1448c | [
"Apache-2.0"
] | null | null | null | ---
layout: engineering-education
status: publish
published: true
url: /how-to-build-templates-for-django-applications-with-htmx/
title: How to Build Templates for Django Applications with HTMX
description: This tutorial will guide the reader on how to build templates for Django applications with HTMX.
author: muhammed-ali
date: 2022-05-12T00:00:00-13:40
topics: [Languages]
excerpt_separator: <!--more-->
images:
- url: /engineering-education/how-to-build-templates-for-django-applications-with-htmx/hero.jpg
alt: How to Build templates for Django Applications with HTMX Hero Image
---
Did you know it is possible to use AJAX without writing a single line of JavaScript code? Are you a Django developer who is not really familiar with JavaScript and who would like to display components of your application asynchronously?
<!--more-->
If you've asked these questions before, then you are in the right place. In this article, I will build a simple Django application that creates, deletes content from the database, and displays the current content asynchronously without the page refreshing.
This is important if you don’t want to go through the stress of using a library like React or Vue. We can find the project built in this tutorial on [GitHub](https://github.com/khabdrick/django-htmx-tutorial).
#### Prerequisites
- Basic understanding of Django
- Django installed (v3.2)
- Python installed (v3.8)
### What is HTMX?
The general idea behind [HTMX](https://htmx.org/) is simplifying web application development by using HTML attributes to incorporate [AJAX](https://htmx.org/docs#ajax), [CSS Transitions](https://htmx.org/docs#css_transitions), [WebSockets](https://htmx.org/docs#websockets), and [Server-Sent Events](https://htmx.org/docs#sse) directly into HTML.
You don’t need to write any JavaScript for the basic things required to run a full-fledged web application unlike React, Vue, and other frontend libraries. To use HTMX in Django, you don’t need to install anything, you just need to attach CDN to your HTML and you are good to go.
### Creating, Listing, and Deleting with HTMX and Django
In this section, you will learn how to build the basic create, list, and delete functionality with HTMX and Django to illustrate how HTMX works in Django. We will build a contact list application.
Something to note, when working with HTMX, if you must return something from the server-side, it must be HTML fragments, not JSON.
Let’s get right into it!
First, let’s create an app for our contacts. You can do this by going to the root of your application and running the following command.
```bash
django-admin startapp app
```
Then add `app` to `INSTALLED_APPS` *settings.py* file.
```python
INSTALLED_APPS = [...,
"app",
...,
]
```
#### Creating and Listing with HTMX and Django
Open your preferred text editor, navigate to *app/models.py*, and paste the code below, which is just a simple model for a contact list application.
```python
from django.db import models
class Contact(models.Model):
name = models.CharField(max_length=200)
phone_number=models.CharField(max_length=200)
def __str__(self):
return self.name
```
Now, generate a database for your modules by running the following commands.
```bash
python manage.py makemigrations
python manage.py migrate
```
Next, in the *app/* directory, create a new file called *forms.py,* this is where the code for our form will be. After creating the file, paste the code below into it.
```python
from .models import Contact
from django import forms
class ContactForm(forms.ModelForm):
class Meta:
fields = ["name", "phone_number"]
model = Contact
widgets = {
"name": forms.TextInput(attrs={"class": "form-control"}),
"phone_number": forms.TextInput(attrs={"class": "form-control"}),
}
```
Now in the *app/views.py* file, paste the code below. The code below is generally just creating and listing a contact.
```python
from django.shortcuts import render
from .models import Contact
from django.views.generic.list import ListView
def create_contact(request):
name = request.POST.get('contactname') # get data from form where name="contactname"
phone_number = request.POST.get('phone_number') # get data from form where name="phone_number"
# add contact
contact = Contact.objects.create(name=name, phone_number=phone_number) # add contact to databse
contacts = Contact.objects.all()
return render(request, 'contact-list.html', {'contacts': contacts}) # display the list of contacts in contact-list.html
class ContactList(ListView):
template_name = 'contact.html' # html file to display the list of contacts
model = Contact
context_object_name = 'contacts' # used in the HTML template to loop through and list contacts
```
Up next is creating URLs for the views above. Go to the *urls.py* file at the root of your project and replace the code you have there with the code below.
```python
from django.contrib import admin
from django.urls import path
from app.views import create_contact, ContactList
urlpatterns = [
path('admin/', admin.site.urls),
path('create-contact/', create_contact, name='create-contact'),
path("contacts/", ContactList.as_view(), name='contact-list'),
]
```
Let’s now create templates for the form and the contact list. To do this, go to the directory for `app` and create a new directory called *templates/* (the name of the file is mandatory).
In the directory you just created, create new files with names *base.html, contact.html, contact-list.html*. Now, paste the code below into the *base.html* file you just created. The code below contains all the **Content Delivery Network** (CDN) required for the entire project to display properly.
```html
{% load static %}
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Contact Application</title>
<!-- Bootstrap CSS -->
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0/css/bootstrap.min.css" integrity="sha384-Gn5384xqQ1aoWXA+058RXPxPg6fy4IWvTNh0E263XmFcJlSAwiGgFAW/dAiS6JXm" crossorigin="anonymous">
<!-- jQuery -->
<script src="https://code.jquery.com/jquery-3.2.1.slim.min.js" integrity="sha384-KJ3o2DKtIkvYIK3UENzmM7KCkRr/rE9/Qpg6aAZGJwFDMVNA/GpGFF93hXpG5KkN" crossorigin="anonymous"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.12.9/umd/popper.min.js" integrity="sha384-ApNbgh9B+Y1QKtv3Rn7W3mgPxhU9K/ScQsAP7hUibX39j7fakFPskvXusvfa0b4Q" crossorigin="anonymous"></script>
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0/js/bootstrap.min.js" integrity="sha384-JZR6Spejh4U02d8jOt6vLEHfe/JQGiRRSQQxSfFWpi1MquVdAyjUar5+76PVCmYl" crossorigin="anonymous"></script>
<!-- HTMX -->
<script src="https://unpkg.com/[email protected]"></script>
</head>
<body>
<div class="container mt-4">
{% block content %}
{% endblock %}
</div>
<script>
document.body.addEventListener('htmx:configRequest', (event) => {
event.detail.headers['X-CSRFToken'] = '{{ csrf_token }}'; //insert csrf token when performing AJAX request
})
</script>
</body>
</html>
```
>*Note: We will use bootstrap just for styling.*
Now let’s get to writing the template that will create and list contacts without the page reloading. To do this with htmx, you will need 2 attributes; `hx-post`( for Issues a **`POST`** request to the specified URL), `hx-target`(load response into another element i.e. list in this case).
Paste the code below in the contact.html file you just created to implement the form. In the code above, you see that the submitting of the form triggers `<div id="contact-list">` which displays the current list with the newly submitted contact.
```html
{% extends 'base.html' %}
{% block content %}
<div class="align-center col-10 offset-1">
<div class="d-flex justify-content-between align-items-center">
<p class="lead ml-0">My contacts</p>
<form hx-post="{% url 'create-contact' %}" hx-target='#contact-list' class="d-flex align-items-center" method="POST">
{% csrf_token %}
<input type="text" name="contactname" class="form-control-sm mr-2" placeholder="Enter name" hx-post="/check-name/" hx-trigger="keyup" hx-target="#name-exist"/>
<input type="text" name="phone_number" class="form-control-sm mr-2" placeholder="Enter phone number" />
<button hx-post='{% url "create-contact"%}' hx-target='#contact-list' type="submit" class="btn btn-success btn-sm">Save</button>
</form>
</div>
<hr/>
<div id="contact-list">
{% include 'contact-list.html' %}
</div>
</div>
{% endblock content %}
```
Now let’s create the template to display the list of contacts. Paste the code below in the `contact-list.html`.
```html
{% if contacts %}
{% csrf_token %}
<ul class="list-group col-4">
{% for contact in contacts %}
<li class="list-group-item d-flex justify-content-between align-items-center">
{{ contact.name }}: {{ contact.phone_number }}
</li>
{% endfor %}
</ul>
{% else %}
<p>No Contact</p>
{% endif %}
```
#### Deleting with HTMX and Django
In the *app/views.py* file, paste the function below.
```python
def delete_contact(request, pk):
# remove the contact from list.
contact_id = Contact.objects.get(id=pk)
contact_id.delete()
contacts = Contact.objects.all()
return render(request, 'contact-list.html', {'contacts': contacts})
```
Next, create the URL for this view in your *urls.py* file.
```python
...
from app.views import create_contact, ContactList, delete_contact
urlpatterns = [
...
path('delete-contact/<int:pk>/', delete_contact, name='delete-contact'),
]
```
Now we have to update the *contact-list.html* file to include the delete button and the necessary HTML attributes required for htmx to work. The attributes are; `hx-delete`(Issues a `DELETE` request to the given URL), `hx-target` (triggers the response of the current list with the contact deleted, `hx-confirm` (required if you need to add a confirmation message before deleting).
To add the delete functionality, replace the code you have in *contact.html* with the code below.
```html
{% if contacts %}
{% csrf_token %}
<ul class="list-group col-4">
{% for contact in contacts %}
<li class="list-group-item d-flex justify-content-between align-items-center">
{{ contact.name }}: {{ contact.phone_number }}
<span class="badge badge-danger badge-pill"
style="cursor: pointer;"
hx-delete="{% url 'delete-contact' contact.pk %}"
hx-target="#contact-list"
hx-confirm="Are you sure you wish to delete?">X</span>
</li>
{% endfor %}
</ul>
{% else %}
<p>No Contact</p>
{% endif %}
```
You can now test out the app functionality by running the server with `python manage.py runserver` then go to the contact list URL([http://127.0.0.1:8000/contacts/](http://127.0.0.1:8000/contacts/)) and you will see that everything works correctly.
### Conclusion
We learned about htmx and how it can be used in Django applications. We looked at how to create, list, and delete data from the database and display current data without the page refreshing through the use of htmx.
You can take things a step further by using htmx to swap HTML or CSS components and also induce transitions if you want to. The greatest advantage of using htmx is that you don’t need JavaScript at all, so if you intend to build a better contact application or maybe a simple e-commerce site, I’ll advise you to use htmx.
Happy coding!
---
Peer Review Contributions by: [Mohamed alghadban](/engineering-education/authors/mohamed-alghadban/)
| 45.939163 | 381 | 0.717265 | eng_Latn | 0.954083 |
57e2928250f05068de9bf015ebf17e271411550b | 825 | md | Markdown | _posts/2008-07-10-bizarre-email-headers-part-23412.md | rjbs/rjbs.github.io | fffc65448b7d791c72088dbfb64404bdc6010a84 | [
"MIT"
] | null | null | null | _posts/2008-07-10-bizarre-email-headers-part-23412.md | rjbs/rjbs.github.io | fffc65448b7d791c72088dbfb64404bdc6010a84 | [
"MIT"
] | null | null | null | _posts/2008-07-10-bizarre-email-headers-part-23412.md | rjbs/rjbs.github.io | fffc65448b7d791c72088dbfb64404bdc6010a84 | [
"MIT"
] | null | null | null | ---
layout: post
title : "bizarre email headers, part 23412"
date : "2008-07-10T20:07:46Z"
tags : ["email", "wtf"]
---
I see a lot of crazy email content and headers. I should post more of them,
just for giggles. Here's one I found sitting in `wtf.msg` in my home directory
at work:
Content-type: multipart/related;
type="multipart/alternative";
boundary="----=_NextPart_000_003D_04D3ADB7.0E7B0925"
So, it's a multipart/related message with a ... type ... of
multipart/alternative. What?
Maybe it was a heads-up: the only part inside the multipart/related was a
single multipart/alternative.
I don't think this is the only cause of the problem, but:
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Thanks, Microsoft MimeOLE!
| 29.464286 | 79 | 0.718788 | eng_Latn | 0.985596 |
57e2aa693836f4a70a1e7cb04d207c5b6148bc9e | 69 | md | Markdown | README.md | cmlnodzak/PyLncRNA | cd77c20961c8cc44b187ba9d8423aaaf1e6e09f8 | [
"MIT"
] | null | null | null | README.md | cmlnodzak/PyLncRNA | cd77c20961c8cc44b187ba9d8423aaaf1e6e09f8 | [
"MIT"
] | null | null | null | README.md | cmlnodzak/PyLncRNA | cd77c20961c8cc44b187ba9d8423aaaf1e6e09f8 | [
"MIT"
] | null | null | null | # PyLncRNA
scripts for python implementation of expression analysis
| 17.25 | 56 | 0.84058 | eng_Latn | 0.819315 |
57e2b8c3fe5bd72003883d69298d4d69bff94b35 | 677 | md | Markdown | src/atcoder/typical90/025/README.md | kagemeka/competitive-programming | c70fe481bcd518f507b885fc9234691d8ce63171 | [
"MIT"
] | 1 | 2021-07-11T03:20:10.000Z | 2021-07-11T03:20:10.000Z | src/atcoder/typical90/025/README.md | kagemeka/competitive-programming | c70fe481bcd518f507b885fc9234691d8ce63171 | [
"MIT"
] | 39 | 2021-07-10T05:21:09.000Z | 2021-12-15T06:10:12.000Z | src/atcoder/typical90/025/README.md | kagemeka/competitive-programming | c70fe481bcd518f507b885fc9234691d8ce63171 | [
"MIT"
] | null | null | null | # [AtCoder Typical90 025 - Digit Product Equation（★7）](https://atcoder.jp/contests/typical90/tasks/typical90_y)
# keywords
- brute force
- enumerate minority
# summary
- enumerate $f(x)$
- number of $f(x)$ is count of repeated combinations.
- that is at most $_{10}H_{11} = _{20}C_{11} = 167960$ patterns
- there is only one $x$ corresponding to $f(x)$ even if there exists such a $x$.
- $\because x - f(x) = B \leftrightarrow x = f(x) + B$
- $x := fx + B$
- $\forall{x}$
- check $1 \le x \le N \land x - f(x) = B$
# code
## sol_0, sol_2
- numba (JIT)
- enumerate fx with BFS and np.unique
## sol_1
- numpy
- enumerate fx with BFS and np.unique
# similar
| 21.83871 | 111 | 0.636632 | eng_Latn | 0.966923 |
57e2d4a87d7f5ea99f910e2317f48c48615ae4c4 | 2,822 | md | Markdown | AlchemyInsights/sync-sharepoint-files-with-onedrive.md | isabella232/OfficeDocs-AlchemyInsights-pr.pl-PL | 621d5519261e87dafaff1a0b3d7379f37e226bf6 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-19T19:07:24.000Z | 2020-05-19T19:07:24.000Z | AlchemyInsights/sync-sharepoint-files-with-onedrive.md | isabella232/OfficeDocs-AlchemyInsights-pr.pl-PL | 621d5519261e87dafaff1a0b3d7379f37e226bf6 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2022-02-09T06:52:18.000Z | 2022-02-09T06:52:35.000Z | AlchemyInsights/sync-sharepoint-files-with-onedrive.md | isabella232/OfficeDocs-AlchemyInsights-pr.pl-PL | 621d5519261e87dafaff1a0b3d7379f37e226bf6 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-10-09T20:27:31.000Z | 2019-10-09T20:27:31.000Z | ---
title: Rozwiązywanie problemów w usłudze SharePoint Online za pomocą polecenia „Otwórz w Eksploratorze”
ms.author: pebaum
author: pebaum
manager: pamgreen
ms.date: 04/21/2020
ms.audience: Admin
ms.topic: article
ms.service: o365-administration
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Priority
ms.collection: Adm_O365
ms.custom:
- "6462"
- "9003546"
ms.assetid: 5ad2f1f2-9650-4eb0-b4fa-2f52a09f535a
ms.openlocfilehash: 538cc24c091d42a8f7a8998ce1d18b61ac0b689c
ms.sourcegitcommit: a097d1f8915a31ed8460b5b68dccc8d87e563cc0
ms.translationtype: HT
ms.contentlocale: pl-PL
ms.lasthandoff: 09/22/2021
ms.locfileid: "59475479"
---
# <a name="troubleshoot-open-with-explorer-issues-in-sharepoint-online"></a>Rozwiązywanie problemów w usłudze SharePoint Online za pomocą polecenia „Otwórz w Eksploratorze”
Postępuj zgodnie z instrukcjami i najlepszymi rozwiązaniami w następujących artykułach:
- [Rozwiązywanie problemów w usłudze SharePoint Online za pomocą polecenia „Otwórz w Eksploratorze”](https://docs.microsoft.com/sharepoint/troubleshoot/lists-and-libraries/troubleshoot-issues-using-open-with-explorer)
- [Kopiowanie i przenoszenie plików biblioteki za pomocą polecenia Otwórz w Eksploratorze](https://support.microsoft.com/office/copy-or-move-library-files-by-using-open-with-explorer-aaee7bfb-e2a1-42ee-8fc0-bcc0754f04d2?ui=en-us&rs=en-us&ad=us)
**Uwaga**:
- Zalecamy [synchronizację plików programu SharePoint za pomocą nowego klienta synchronizacji OneDrive](https://support.microsoft.com/office/sync-sharepoint-and-teams-files-with-your-computer-6de9ede8-5b6e-4503-80b2-6190f3354a88?ui=en-us&rs=en-us&ad=us) zawierającego funkcję [Pliki na żądanie](https://support.microsoft.com/office/save-disk-space-with-onedrive-files-on-demand-for-windows-10-0e6860d3-d9f3-4971-b321-7092438fb38e?ui=en-us&rs=en-us&ad=us), ponieważ zapewnia on lokalny dostęp do plików i oferuje najlepszą wydajność.
- **Otwórz za pomocą Eksploratora** jest obsługiwane tylko w przeglądarce Microsoft Edge. Aby uzyskać więcej informacji, zobacz [Wyświetl pliki programu SharePoint za pomocą Eksploratora plików w przeglądarce Microsoft Edge](https://docs.microsoft.com/SharePoint/sharepoint-view-in-edge) i [Wyłączanie pomocy technicznej do starszej wersji przeglądarki Microsoft Edge](https://docs.microsoft.com/lifecycle/announcements/m365-ie11-microsoft-edge-legacy). **Otwórz w Eksploratorze** nie działa w systemie Windows z przeglądarkami Google Chrome, Mozilla Firefox ani na platformie Mac, więc opcja **Widok Eksploratora** może być wyszarzona.
- Przycisk **Otwórz w Eksploratorze** nie jest wyświetlany w nowym środowisku biblioteki. Wybierz listę rozwijaną **Widok** w prawym górnym rogu (nazwa listy rozwijanej zmienia się w zależności od bieżącego widoku), a następnie wybierz pozycję **Wyświetl w Eksploratorze**.
| 72.358974 | 636 | 0.816797 | pol_Latn | 0.995758 |
57e2ed54b1cd2cc1a40154a7af853b03ebf1f6da | 791 | md | Markdown | doc/README.md | lepisma/polybar | d5112c9b663a3c0d8b013f5110bbf448c18c1ffd | [
"MIT"
] | null | null | null | doc/README.md | lepisma/polybar | d5112c9b663a3c0d8b013f5110bbf448c18c1ffd | [
"MIT"
] | null | null | null | doc/README.md | lepisma/polybar | d5112c9b663a3c0d8b013f5110bbf448c18c1ffd | [
"MIT"
] | null | null | null | Polybar Manual
==============
The official polybar documentation lives here.
The html documentation and man pages are built automatically when you build with cmake (cmake creates the custom
target `doc`).
## Preview Locally
The documentation uses [Sphinx](http://www.sphinx-doc.org/en/stable/) to generate the documentation, so you will need to
have that installed.
To generate the documentation you first need to configure polybar the same as when you compile it (`cmake ..` in `build`
folder).
After that you can run `make doc` to generate all of the documentation or `make doc_html` or `make doc_man` to only
generate the html documentation or the man pages.
Open `build/doc/html/index.html` to read the documentation in the browser.
The manual pages are placed in `build/doc/man`.
| 37.666667 | 120 | 0.764855 | eng_Latn | 0.995638 |
57e48e6ca9589178d6a0923f7512d00651a3512e | 216 | md | Markdown | MD/File-Formats/pdb.md | zhongxiang117/zhongxiang117.github.io | 98828d0a9a4e0e02577547b537489d450182360e | [
"MIT"
] | null | null | null | MD/File-Formats/pdb.md | zhongxiang117/zhongxiang117.github.io | 98828d0a9a4e0e02577547b537489d450182360e | [
"MIT"
] | null | null | null | MD/File-Formats/pdb.md | zhongxiang117/zhongxiang117.github.io | 98828d0a9a4e0e02577547b537489d450182360e | [
"MIT"
] | null | null | null | ---
---
# PDB
Protein Data Bank file format
link: [http://www.wwpdb.org/documentation/file-format-content/format33/v3.3.html](http://www.wwpdb.org/documentation/file-format-content/format33/v3.3.html)
| 19.636364 | 157 | 0.703704 | yue_Hant | 0.659534 |
57e5e9bcc18b93db3dba41d28cdb426b54300dc3 | 318 | md | Markdown | README.md | RahulR19/Web-Scraping- | 5da9d13c86b11387661cccbaac579ee5e11652b3 | [
"MIT"
] | null | null | null | README.md | RahulR19/Web-Scraping- | 5da9d13c86b11387661cccbaac579ee5e11652b3 | [
"MIT"
] | null | null | null | README.md | RahulR19/Web-Scraping- | 5da9d13c86b11387661cccbaac579ee5e11652b3 | [
"MIT"
] | null | null | null | # Web Scraping Using Python
This project deals with scraping data from a website and visualising it.
First the data is scraped from the website of Box Office Mojo.
Then the relevant information (Top 10 highest grossing movies of all time) is processed.
Then the data is visualised using a pie chart and a bar graph
| 35.333333 | 88 | 0.795597 | eng_Latn | 0.999187 |
57e6865ae8de1346e0ad996d8eb882446345f182 | 3,964 | md | Markdown | markdown-notes/Chapter-4.md | Hantao-Ye/Robotics-and--Flexible-Automation | 3b11d2a7937fb987898613ebc1ebd40b7b4dca0d | [
"Apache-2.0"
] | 1 | 2020-10-05T01:46:00.000Z | 2020-10-05T01:46:00.000Z | markdown-notes/Chapter-4.md | Hantao-Ye/Robotics-and-Flexible-Automation | 3b11d2a7937fb987898613ebc1ebd40b7b4dca0d | [
"Apache-2.0"
] | null | null | null | markdown-notes/Chapter-4.md | Hantao-Ye/Robotics-and-Flexible-Automation | 3b11d2a7937fb987898613ebc1ebd40b7b4dca0d | [
"Apache-2.0"
] | null | null | null | # Chapter-4
[TOC]
## 1 Introduction
Chapter 3 focused on the **direct kinematics** of manipulators, here the focus is the **inverse kinematics** of manipulators.
Solving the problem of finding the required joint angles to place the tool frame $\{T\}$, relative to the station frame, $\{S\}$, is split into two parts.
First, frame transformations are performed to find the wrist frame, $\{W\}$, relative to the base frame, $\{B\}$, and then the inverse kinematics are used to solve for the joint angles
## 2 Tool Configuration
### Definition
the arm matrix defines the position $P$ and orientation $R$ of the tool relative to base as a function of the joint variables q
$$
T_{B}^{T}(q) =
\begin{bmatrix}
\begin{array}{ccc:c}
&R&&P\\[2ex] \hdashline
0&0&0&1
\end{array}
\end{bmatrix}
$$
it is called as the configuration of the tool
### Joint Space
Tool configuration space is the set of configurations that the tool can have
It is a six-dimensional vector including three position coordinates $(x_p,\;y_p,\;z_p)$ and three orientation coordinates
## 3-Examples
### Attention
- Apply tangent function
- Multi-solution
- Choose the real solution from all possible solutions by continuous motion principle
### Example 4-1
Given $l_1$, $l_2$ and $l_3$ and $p_x$, $p_y$ and $\alpha$. Get $\theta_1$, $\theta_2$ and $\theta_3$
$$
\begin{aligned}
T_3^0 &= A_3^0\\[2ex]
A_3^0 &=
\begin{bmatrix}
c_{123}&-s_{123}&0&l_3c_{123}+l_2c_{12}+l_1c_1\\[2ex]
s_{123}&c_{123}&0&l_3s_{123}+l_2s_{12}+l_1s_1\\[2ex]
0&0&1&0\\[2ex]
0&0&0&1
\end{bmatrix}\\[2ex]
T_3^0 &=
\begin{bmatrix}
c_\alpha &-s_\alpha&0&p_x\\[2ex]
s_\alpha &c_\alpha&0&p_y\\[2ex]
0&0&1&0\\[2ex]
0&0&0&1
\end{bmatrix}
\end{aligned}
$$
then we get that $\alpha=\theta_1+\theta_2+\theta_3$
$$
\begin{cases}
l_2c_{12}+l_1c_1 = p_x-l_3c_\alpha=p_x^*\\[2ex]
l_2s _{12}+l_1s_1 = p_y-l_3s_\alpha=p_y^*
\end{cases}
$$
square and plus we can get $\cos\theta_2$
$$
\cos\theta_2 = \frac{{p_x^*}^2+{p_y^*}^2-(l_1^2+l_2^2)}{2l_1l_2}
$$
and $\theta_1$ could be solved by substituting $\theta_2$ in the original equations
### Example 4-2
Stanford robot
$$
T_6^0 =A_1^0A_2^1A_3^2A_4^3A_5^4A_6^5
$$
Firstly, we can get $\theta_1$ from $(A_1^0)^{-1}T_6^0 =A_2^1A_3^2A_4^3A_5^4A_6^5$
since the rotation matrix is orthogonal, $AA^T = I$, $(A_1^0)^{-1}$ could be simply expressed by ${A_0^1}^T$
$$
\begin{aligned}
(A_1^0)^{-1}T_6^0 &=
\begin{bmatrix}
c_1&s_1&0&0\\[1ex]
0&0&-1&0\\[1ex]
-s_1&c_1&0&0\\[1ex]
0&0&0&1
\end{bmatrix}\cdot
\begin{bmatrix}
n_x&o_x&a_x&p_x\\[1ex]
n_y&o_y&a_y&p_y\\[1ex]
n_z&o_z&a_z&p_z\\[1ex]
0&0&0&1
\end{bmatrix}\\[2ex]
&=
\begin{bmatrix}
n_xc_1+n_ys_1&o_xc_1+o_ys_1&a_xc_1+a_ys_1&p_xc_1+p_ys_1\\[1ex]
-n_z&-o_z&-a_z&-p_z\\[1ex]
n_yc_1-n_xs_1&o_yc_1-o_xs_1&a_yc_1-a_xs_1&p_yc_1-p_xs_1\\[2ex]
0&0&0&1
\end{bmatrix}
\end{aligned}
$$
where the right side could be expressed as
$$
\begin{aligned}
T_6^1 &= A_2^1A_3^2A_4^3A_5^4A_6^5\\[2ex]
&=
\begin{bmatrix}
c_2(c_4c_5c_6-s_4s_6)-s_2s_5s_6&-c_2(c_4c_5c_6+s_4c_6)+s_2s_5s_6&c_2c_4s_5+s_2c_5& s_2d_3\\[1ex]
s_2(c_4c_5c_6-s_4s_6)+c_2s_5c_6&-s_2(c_4c_5s_6+s_4c_6)-c_2s_5s_6&s_2c_4s_5-c_2c_5& -c_2d_3\\[1ex]
s_4c_5c_6+c_4s_6&-s_2c_5s_6&s_4s_5&d_2\\[1ex]
0&0&0&1
\end{bmatrix}
\end{aligned}
$$
since $d_2$ is known, we can get $\theta_1$ from the equation
$$
-s_1p_x+c_1p_y = d_2
$$
 | 26.078947 | 184 | 0.607972 | eng_Latn | 0.730754 |
57e6ef5f9f7a0cbe339a2dc9c8ef651caab5b876 | 2,047 | md | Markdown | README.md | CheeseyPickle/TourGuide | 5a452a40db52b152c4dc33da495078d056f073fa | [
"Unlicense"
] | 2 | 2021-12-13T20:18:14.000Z | 2022-03-14T20:30:41.000Z | README.md | CheeseyPickle/TourGuide | 5a452a40db52b152c4dc33da495078d056f073fa | [
"Unlicense"
] | 5 | 2021-09-21T14:37:40.000Z | 2021-12-27T21:42:21.000Z | README.md | CheeseyPickle/TourGuide | 5a452a40db52b152c4dc33da495078d056f073fa | [
"Unlicense"
] | 7 | 2021-09-07T19:34:46.000Z | 2022-03-14T23:38:39.000Z | # TourGuide
### Installation
```
svn checkout https://github.com/Loathing-Associates-Scripting-Society/TourGuide/branches/Release/
```
### Updating
```
svn update
```
### How do I use it?
Once it's installed, look in the relay browser. In the upper-right, there will be a **"run script"** menu. Select TourGuide and it will dock to the side of your window.
### What does it do?
TourGuide is a relay script which will give advice on playing [Kingdom of Loathing](http://www.kingdomofloathing.com) within [KoLmafia](http://kolmafia.sourceforge.net). It details how to complete quests you're on, and what resources you have available.
It keeps track of your quests and resources and helps you complete ascensions as fast as possible.
#### Quest advice:
#### Resources:
The script will inform you of many resources you have - free runaways, banishes, semi-rares, etc. - and ideas on what to use them on.
**Quests supported**: All council quests, azazel, pretentious artist, untinker, legendary beat, most of the sea, unlocking the manor, the nemesis quest, pirate quest, repairing the shield generator in outer space, white citadel, the old level 9 quest, jung man's psychoses jars, and the wizard of ego.
### Development guidelines
TourGuide is open source and contributions are encouraged!
The release above is a compiled version of the development version, which can be found by checking out https://github.com/Loathing-Associates-Scripting-Society/TourGuide. The release is compiled via Compile ASH script.rb, which collects many scripts into one for ease of release.
This script, as well as its support scripts, are in the public domain.
This is a fork of https://github.com/cdrock/TourGuide, which is in turn a fork of Ezandora's Guide.
For support, questions, and comments visit the Ascension Speed Society discord channel.
| 39.365385 | 301 | 0.762579 | eng_Latn | 0.977413 |
57e7c27da55fcf6ae8cb05ce9b5313846a19a05b | 690 | md | Markdown | README.md | bipulraman/SPFx-Sample-Webparts | b540c9eded8758b112e300e23fb1bb53d8f7e1d2 | [
"MIT"
] | null | null | null | README.md | bipulraman/SPFx-Sample-Webparts | b540c9eded8758b112e300e23fb1bb53d8f7e1d2 | [
"MIT"
] | null | null | null | README.md | bipulraman/SPFx-Sample-Webparts | b540c9eded8758b112e300e23fb1bb53d8f7e1d2 | [
"MIT"
] | null | null | null | ## webparts
SharePoint Framework WebParts. Sample solution for code reference.
### Building the code
```bash
git clone the repo
npm i
npm i -g gulp
gulp
```
This package produces the following:
* lib/* - intermediate-stage commonjs build artifacts
* dist/* - the bundled script, along with other resources
* deploy/* - all resources which should be uploaded to a CDN.
### Build options
gulp clean - TODO
gulp test - TODO
gulp serve - TODO
gulp bundle - TODO
gulp package-solution - TODO
# License
All files within this repo are released under the [MIT (OSI) License]( https://en.wikipedia.org/wiki/MIT_License) as per the [LICENSE file](./LICENSE) stored in the root of this repo.
| 23 | 184 | 0.73913 | eng_Latn | 0.965107 |
57e807fb90c2e5cdc9d5062a011194ada86e5b5e | 17,455 | md | Markdown | specs/FoundationDevSpec.md | alexstojda/botframework-cli | e933dfc1c7d58bc6b7a030259e0023623ca9fc64 | [
"MIT"
] | 139 | 2019-07-17T22:10:46.000Z | 2022-03-25T23:26:58.000Z | specs/FoundationDevSpec.md | alexstojda/botframework-cli | e933dfc1c7d58bc6b7a030259e0023623ca9fc64 | [
"MIT"
] | 756 | 2019-07-15T18:14:31.000Z | 2022-02-25T06:10:57.000Z | specs/FoundationDevSpec.md | alexstojda/botframework-cli | e933dfc1c7d58bc6b7a030259e0023623ca9fc64 | [
"MIT"
] | 123 | 2019-07-16T19:06:26.000Z | 2022-03-30T12:09:05.000Z | # Foundation Dev Spec
## Summary
The CLI will be using OClif JS/TS command line shell platform. The platform provides a uniform mechanism for command line parsing and runtime execution environment with extensibility of additional commands similar to az cli but tailored for local bot framework requirements.
The following specifications detail the foundation requirements, design and implementation considerations.
## Requirements
The command line shell must adhere to the following requirements that shall be expanded upon in later sections:
* Command groups with parameters
* Verbs with parameters
* Defaults management
* Common groups: version, help, verbose, logging
* Parser requirements, limitations, constraints (what could but shouldn't be allowed for instance)
* Extensible plugin architecture
* Isolation across plugins
* Error handling, return codes, exceptions management, & corresponding messaging
* Linting, static analysis
* Common upgrade / update mechanisms using Microsoft approved standard library sources
* Package management (ala Lerna)
* Partner onboarding process & how-to documentation
* Usage documentation
* Extensibility guidelines documentation
* Automated code annotation generation
* Logging infrastructure (to file, STDOUT/STDERR, Application Insights)
* Test Infrastructure for UT, and CI support
* Build environment, CI cadence for nightly, weekly, release, with versioning design, in repo etc)
* Telemetry instrumentation
* Installation & runtime environment (how/where to install, uninstall and invoke using 'bf' command)
* Configuration management
## AZ CLI Guidelines
Review [AZ CLI guidelines](https://github.com/Azure/azure-cli/blob/dev/doc/command_guidelines.md) as a baseline & alignment. Our objective is to align to AZ CLI as much as possible.
Here's a "reducted" (but almost verbatim) version of the guidelines as applicable to 'bf'.
### General Patterns
* All commands, comm and group and arguments must have descriptions
* You must provide command examples for non-trivial commands
* Command output must go to stdout, everything else to stderr (log/status/errors).
* Log to logger.error() or logger.warning() for user messages; do not use the print() function
* Use the appropriate logging level for printing strings. e.g. logging.info(“Upload of myfile.txt successful”) NOT return “Upload successful”.
### Command Naming and Behavior
* Commands must follow a "[noun] : [verb] : [noun]" pattern (e.g. config:show:telemetry)
* Multi-word subgroups should be hyphenated e.g. foo-resource instead of fooresource
* All command names should contain a verb e.g. account get-connection-string instead of account connection-string
* For commands which maintain child collections, the follow pairings are acceptable. CREATE/DELETE (same as top level resources); ADD/REMOVE
* Avoid hyphenated command names when moving the commands into a subgroup would eliminate the need. e.g. database show and database get instead of show-database and get-database
* If a command subgroup would only have a single command, move it into the parent command group and hyphenate the name. This is common for commands which exist only to pull down cataloging information. e.g. database list-sku-definitions instead of database sku-definitions list
* In general, avoid command subgroups that have no commands. This often happens at the first level of a command branch. e.g. keyvault create instead of keyvault vault create (where keyvault only has subgroups and adds unnecessary depth to the tree).
### Argument Naming Conventions
* Arguments with specific units:
* In general, DO NOT put units in argument names. ALWAYS put the expected units in the help text. Example: --duration-in-minutes should simply be --duration. This prevents the need to add more arguments later if more units are supported.
* Consider allowing a syntax that will let the user specify units. For example, even if the service requires a value in minutes, consider accepting 1h or 60m. It is fine to assume a default (i.e. 60 = 60 minutes).
* It is acceptable to use a unit in the argument name when it is used like an enum. For example, --start-day is okay when it accepts MON, TUE, etc. --start-hour is okay when it indicates an hour of the day.
* Overloading Arguments:
* Avoid having multiple arguments that simply represent different ways of getting the same thing. Instead, use a single descriptive name and overload it appropriately. For example, assume a command which can accept a parameter file through a URL or local path.
### Standard Command Types
The following are standard names and behavioral descriptions for CRUD commands commonly found within the CLI. These standard command types MUST be followed for consistency with the rest of the CLI.
* CREATE - standard command to create a new resource. Usually backed server-side by a PUT request. 'create' commands should be idempotent and should return the resource that was created.
* UPDATE - command to selectively update properties of a resource and preserve existing values. May be backed server-side by either a PUT or PATCH request, but the behavior of the command should always be PATCH-like. All update commands should be registered using the generic_update_command helper to expose the three generic update properties. update commands MAY also allow for create-like behavior (PATCH) in cases where a dedicated create command is deemed unnecessary. update commands should return the updated resource.
* SET - command to replace all properties of a resource without preserving existing values, typically backed server-side by a PUT request. This is used when PATCH-like behavior is deemed unnecessary and means that any properties not specifies are reset to their default values. set commands are more rare compared to update commands. set commands should return the updated resource.
* SHOW - command to show the properties of a resource, backed server-side by a GET request. All show commands should be registered using the show_command or custom_show_command helpers to ensure 404(Not Found) is always returning an exit code of 3.
* LIST - command to list instances of a resource, backed server-side by a GET request. When there are multiple "list-type" commands within an SDK to list resources at different levels (for example, listing resources in a subscription vice in a resource group) the functionality should be exposed by have a single list command with arguments to control the behavior. For example, if --resource-group is provided, the command will call list_by_resource_group; otherwise, it will call list_by_subscription.
* DELETE - command to delete a resource, backed server-side by a DELETE request. Delete commands return nothing on success.
* WAIT - command that polls a GET endpoint until a condition is reached. If any command within a command group or subgroup exposes the --no-wait parameter, this command should be exposed.
### Non-standard Commands
For commands that don't conform to one of the above-listed standard command patterns, use the following guidance.
(*) Don't use single word verbs if they could cause confusion with the standard command types. For example, don't use get or new as these sound functionally the same as show and create respectively, leading to confusion as to what the expected behavior should be.
(*) Descriptive, hyphenated command names are often a better option than single verbs.
### Coding Practices
(*) All commands should have tests
## Inputs
Inputs specifications define dependencies, and running environment dependencies
## Dependencies:
* OSS Oclif
* [https://github.com/oclif/command]
[https://github.com/oclif/config]
* Microsoft approved OSS library sources
* registry [https://ossmsft.visualstudio.com/_oss?searchText=%40oclif%2Fcommand&_a=artifact]
[https://ossmsft.visualstudio.com/_oss?searchText=%40oclif%2Fconfig&_a=artifact]
[https://ossmsft.visualstudio.com/_oss?searchText=%22%40oclif%2Fplugin-help%22&_a=artifact]
* Run in all supported platforms: Win10 + 4 x Linux supported OS's
## Non-dependencies
* Heroku CLI (we're using it as an example, but not depending on it)
## Outputs
* Corresponding to requirements above:
* Command line parsing capabilities
* Extensible plugin capabilities
* Build/test/static analysis infrastructure
* Acceptance criteria enforcement mechanism
* Verify & fail builds if not passing required quality gates (code coverage, issues, docs)
* Upgrade/update messaging, retry logic, failover, opt-in model and source libraries
* Opt in to telemetry & telemetry instrumentation
* Command line form specifications [**TBD**]
* Automated documentation placeholders
* Error handling, messaging, codes, exceptions
* Code should identify component, and failure category (see for example exception categories).
<output guarantees, downstream dependencies>
## Use Cases
Show a few examples representatives of usage by core foundation (help/version/verbose) and specific extensions.
## Exceptions
<restrictions, constraints, other non-goals worth calling out>
## Design Specifications
Each command extends from oclif/command https://github.com/oclif/command https://oclif.io/docs/commands.
A basic command looks like the following
import Command from '@oclif/command'
export class MyCommand extends Command {
static description = 'description of this example command'
async run() {
console.log('running my command')
}
}
The only part that is required is the run function
BF CLI has a command class extending '@oclif/command'. All BF CLI plugins should extend the bf-cli commmand custom class [https://github.com/microsoft/botframework-cli/blob/master/packages/command/src/command.ts].
This custom command class will send telemetry when a command is run, exposes the trackEvent to the command and handles errors the same way as AZ Bot CLI
[**TBD**: This is the big section that describes the solutions for the requirements above]
### Command groups with parameters
As Multi CLIs grow it can be useful to nest commands within topics. This is supported simply by placing command files in subdirectories. For example, with the BF CLI we have a topic bf ludown with commands like bf ludown, bf ludown:parse:toluis , bf ludown:translate, etc. The directory structure looks like this:
package.json
src/
└── commands/
└── ludown/
└── parse/
└──toluis.ts
└── translate.ts
#### Verbs with parameters
Flag options are non-positional arguments passed to the command. Flags can either be option flags which take an argument, or boolean flags which do not. An option flag must have an argument.Here are some other ways the user can use input flags. This is assuming the command has flags like -f, --file=file and -v, --verbose (string and boolean flag):
$ bf -v
$ bf --file=foo
$ bf --file foo
$ bf -f foo
$ bf -f=foo
$ bf -ffoo
$ bf -vffoo
For detailed info please refer to oclif doc [https://oclif.io/docs/flags].
#### Common groups: version, help, verbose, logging
Help and version are executed before any other flag. Oclif default flags for this are -v, --version and -h, --help
Verbose should be implemented by each command according to its needs. Some commands like chatbot don’t implement them. If needed it can be declared a custom flag that can be shared amongst multiple commands in cli command base class
Logging is exposed in the command class as this.log() logging to process.stdout.write and this.error to console.error.
The new CLI Command Base class exposes the trackEvent to log telemetry events
#### Extensible plugin architecture
Plugins are a great way to offer experimental functionality, allow users to extend your CLI, break up a CLI into modular components, or share functionality between CLIs.
Plugins can have commands or hooks just like a CLI. BF cli will add each tool as a plugin. To add a plugin such as chatdown, first add it to your CLI as a dependency then add the following to cli package.json:
{
"name": "bf-cli",
"version": "0.0.0",
// ...
"oclif": {
"plugins": [
"bf-chatdown"
]
}
}
To create a new plugin, just run the following command inside the packages folder of botframework-cli:
npx oclif plugin myplugin_name
#### Isolation
Each plugin has it's own set of unit tests and runs independently.
#### Error handling, return codes, exceptions management, & corresponding messaging
Run function is executed inside a try catch.
async catch(err: any) {
if (err instanceof CLIError) return this.exit(0)
if (!err.message) throw err
if (err.message.match(/Unexpected arguments?: (-h|--help|help)(,|\n)/)) {
return this._help()
} else if (err.message.match(/Unexpected arguments?: (-v|--version|version)(,|\n)/)) {
return this._version()
} else {
try {
this.trackEvent(this.id + '', {flags : this.getTelemetryProperties(), error: this.extractError(err)})
this.log('Unknown error during execution. Please file an issue on https://github.com/microsoft/botframework-cli/issues')
} catch {}
throw err
}
}
#### Linting, static analysis
Linting is already setup by oclif [https://github.com/oclif/tslint/blob/master/tslint.json].
#### Common upgrade / update mechanisms using Microsoft approved standard library sources
For example, in current CLI, the presences of an update is detected and results with a message to the user when invoked for help, per below. We need to detect the need for update and notify the user or accept opt-in "always keep me up-to-date, notify me but don't install, update-with-no-prompt, update-with-prompt, do-not-update" set of configuration options.
[BF]c:\workspace\botroot>ludown
Update available 1.3.0 -> 1.3.1
Run npm i -g ludown to update.
Usage: ludown [options] [command]
Ludown is a command line tool to bootstrap language understanding models from .lu files
Options:
--prefix Add [ludown] prefix to all messages
-v, --Version output the version number
-h, --help output usage information
Commands:
parse|p Convert .lu file(s) into LUIS JSON OR QnA Maker JSON files.
refresh|d Convert LUIS JSON and/ or QnAMaker JSON file into .lu file
translate|t Translate .lu files
help [cmd] display help for [cmd]
#### Package management (ala Lerna)
Lerna is used only in development to bootstrap the packages that are not yet published. Each plugin and cli is an independent npm package. Main CLI will have the plugin listed as npm dependency.
#### Partner onboarding process & how-to documentation
#### Automated documentation generation
By default you can pass --help to the CLI to get help such as flag options and argument information. This information is also automatically placed in the README whenever the npm package of the CLI is published.
#### Logging infra (to file, STDOUT/STDERR, application insights)
Logging is exposed in the command class as this.log() logging to process.stdout.write and this.error to console.error.
The new CLI Command Base class exposes the trackEvent to send telemetry events if needed.
#### Test Infrastructure for UT, and CI support
When a new command is created by executing the command: npx oclif command command_name a matching test file is created under test folder:
src/
commands/
command_name.ts
test/
commands/
command_name.test.ts
All the tests are discoverable by the script npm run test executing : "test": "nyc --extension .ts mocha --forbid-only \"test/**/*.test.ts\""
#### Build environment, CI cadence for nightly, weekly, release, versioning design, repo)
[https://fuselabs.visualstudio.com/SDK_v4/_build?definitionId=537]
#### Telemetry instrumentation
Telemetry is exposed through the cli-command [https://github.com/microsoft/botframework-cli/blob/master/packages/command/src/command.ts]
#### Installation, invocation & runtime environment (how/where to install, uninstall and invoke using 'bf' command)
$ npm install -g botframework-cli
$ bf COMMAND
running command...
$ bf (-v|--version|version)
botframework-cli/0.0.0 darwin-x64 node-v12.1.0
$ bf --help [COMMAND]
USAGE
$ bf COMMAND
#### Configuration management
<where do we store configuration file, how do we manage it, what format, what's in it, how plugins can read/write/update configuration>
## Technologies
<any technologies discussion as applicable>
We are using Oclif as a foundation for the command line parsing. In addition we're using the following utilities as follows:
* [**TBD**]
## Acceptance Criteria
<minimum bar, testing, other completion quality related items>
Code coverage must be at > 90% coverage across all components. Build should break if test pass reports coverage < 90% or tests do not pass at 100%.
[**TBD**: how do we verify quality, establish acceptance criteria so that the tool maintains high quality]
## Special Considerations
<while actual issues should be tracked github/issues initial placeholders may be placed here transiently for convinience.
* Issue
* Todo
* ...
* [**TBD**:anything]
## Issues
Issue, todo…
References
<any references of relevance>
* Oclif can be found here; https://oclif.io
* [**TBD**: library xyz can be found here]
| 56.856678 | 525 | 0.758923 | eng_Latn | 0.994307 |
57e99e7346096e5ce59cf2b2d2d5a326ce43c6de | 9,929 | md | Markdown | RELEASES.md | antoinewdg/fake-rayon | 9f5aff8fcacdb6bf1dc5f160cd048f306caf6d28 | [
"Apache-2.0",
"MIT"
] | null | null | null | RELEASES.md | antoinewdg/fake-rayon | 9f5aff8fcacdb6bf1dc5f160cd048f306caf6d28 | [
"Apache-2.0",
"MIT"
] | null | null | null | RELEASES.md | antoinewdg/fake-rayon | 9f5aff8fcacdb6bf1dc5f160cd048f306caf6d28 | [
"Apache-2.0",
"MIT"
] | null | null | null | # Release rayon 0.7 / rayon-core 1.0
This release marks the first step towards Rayon 1.0. **For best
performance, it is important that all Rayon users update to at least
Rayon 0.7.** This is because, as of Rayon 0.7, we have taken steps to
ensure that, no matter how many versions of rayon are actively in use,
there will only be a single global scheduler. This is achieved via the
`rayon-core` crate, which is being released at version 1.0, and which
encapsulates the core schedule APIs like `join()`. (Note: the
`rayon-core` crate is, to some degree, an implementation detail, and
not intended to be imported directly; it's entire API surface is
mirrored through the rayon crate.)
We have also done a lot of work reorganizing the API for Rayon 0.7 in
preparation for 1.0. The names of iterator types have been changed and
reorganized (but few users are expected to be naming those types
explicitly anyhow). In addition, a number of parallel iterator methods
have been adjusted to match those in the standard iterator traits more
closely. See the "Breaking Changes" section below for
details.
Finally, Rayon 0.7 includes a number of new features and new parallel
iterator methods. **As of this release, Rayon's parallel iterators
have officially reached parity with sequential iterators** -- that is,
every sequential iterator method that makes any sense in parallel is
supported in some capacity.
### New features and methods
- The internal `Producer` trait now features `fold_with`, which enables
better performance for some parallel iterators.
- Strings now support `par_split()` and `par_split_whitespace()`.
- The `Configuration` API is expanded and simplified:
- `num_threads(0)` no longer triggers an error
- you can now supply a closure to name the Rayon threads that get created
by using `Configuration::thread_name`.
- you can now inject code when Rayon threads start up and finish
- you can now set a custom panic handler to handle panics in various odd situations
- Threadpools are now able to more gracefully put threads to sleep when not needed.
- Parallel iterators now support `find_first()`, `find_last()`, `position_first()`,
and `position_last()`.
- Parallel iterators now support `rev()`, which primarily affects subsequent calls
to `enumerate()`.
- The `scope()` API is now considered stable (and part of `rayon-core`).
- There is now a useful `rayon::split` function for creating custom
Rayon parallel iterators.
- Parallel iterators now allow you to customize the min/max number of
items to be processed in a given thread. This mechanism replaces the
older `weight` mechanism, which is deprecated.
- `sum()` and friends now use the standard `Sum` traits
### Breaking changes
In the move towards 1.0, there have been a number of minor breaking changes:
- Configuration setters like `Configuration::set_num_threads()` lost the `set_` prefix,
and hence become something like `Configuration::num_threads()`.
- `Configuration` getters are removed
- Iterator types have been shuffled around and exposed more consistently:
- combinator types live in `rayon::iter`, e.g. `rayon::iter::Filter`
- iterators over various types live in a module named after their type,
e.g. `rayon::slice::Windows`
- When doing a `sum()` or `product()`, type annotations are needed for the result
since it is now possible to have the resulting sum be of a type other than the value
you are iterating over (this mirrors sequential iterators).
### Experimental features
Experimental features require the use of the `unstable` feature. Their
APIs may change or disappear entirely in future releases (even minor
releases) and hence they should be avoided for production code.
- We now have (unstable) support for futures integration. You can use
`Scope::spawn_future` or `rayon::spawn_future_async()`.
- There is now a `rayon::spawn_async()` function for using the Rayon
threadpool to run tasks that do not have references to the stack.
### Contributors
Thanks to the following people for their contributions to this release:
- @Aaronepower
- @ChristopherDavenport
- @bluss
- @cuviper
- @froydnj
- @gaurikholkar
- @hniksic
- @leodasvacas
- @leshow
- @martinhath
- @mbrubeck
- @nikomatsakis
- @pegomes
- @schuster
- @torkleyy
# Release 0.6
This release includes a lot of progress towards the goal of parity
with the sequential iterator API, though there are still a few methods
that are not yet complete. If you'd like to help with that effort,
[check out the milestone](https://github.com/nikomatsakis/rayon/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Parity+with+the+%60Iterator%60+trait%22)
to see the remaining issues.
**Announcement:** @cuviper has been added as a collaborator to the
Rayon repository for all of his outstanding work on Rayon, which
includes both internal refactoring and helping to shape the public
API. Thanks @cuviper! Keep it up.
- We now support `collect()` and not just `collect_with()`.
You can use `collect()` to build a number of collections,
including vectors, maps, and sets. Moreover, when building a vector
with `collect()`, you are no longer limited to exact parallel iterators.
Thanks @nikomatsakis, @cuviper!
- We now support `skip()` and `take()` on parallel iterators.
Thanks @martinhath!
- **Breaking change:** We now match the sequential APIs for `min()` and `max()`.
We also support `min_by_key()` and `max_by_key()`. Thanks @tapeinosyne!
- **Breaking change:** The `mul()` method is now renamed to `product()`,
to match sequential iterators. Thanks @jonathandturner!
- We now support parallel iterator over ranges on `u64` values. Thanks @cuviper!
- We now offer a `par_chars()` method on strings for iterating over characters
in parallel. Thanks @cuviper!
- We now have new demos: a traveling salesman problem solver as well as matrix
multiplication. Thanks @nikomatsakis, @edre!
- We are now documenting our minimum rustc requirement (currently
v1.12.0). We will attempt to maintain compatibility with rustc
stable v1.12.0 as long as it remains convenient, but if new features
are stabilized or added that would be helpful to Rayon, or there are
bug fixes that we need, we will bump to the most recent rustc. Thanks @cuviper!
- The `reduce()` functionality now has better inlining.
Thanks @bluss!
- The `join()` function now has some documentation. Thanks @gsquire!
- The project source has now been fully run through rustfmt.
Thanks @ChristopherDavenport!
- Exposed helper methods for accessing the current thread index.
Thanks @bholley!
# Release 0.5
- **Breaking change:** The `reduce` method has been vastly
simplified, and `reduce_with_identity` has been deprecated.
- **Breaking change:** The `fold` method has been changed. It used to
always reduce the values, but now instead it is a combinator that
returns a parallel iterator which can itself be reduced. See the
docs for more information.
- The following parallel iterator combinators are now available (thanks @cuviper!):
- `find_any()`: similar to `find` on a sequential iterator,
but doesn't necessarily return the *first* matching item
- `position_any()`: similar to `position` on a sequential iterator,
but doesn't necessarily return the index of *first* matching item
- `any()`, `all()`: just like their sequential counterparts
- The `count()` combinator is now available for parallel iterators.
- We now build with older versions of rustc again (thanks @durango!),
as we removed a stray semicolon from `thread_local!`.
- Various improvements to the (unstable) `scope()` API implementation.
# Release 0.4.3
- Parallel iterators now offer an adaptive weight scheme,
which means that explicit weights should no longer
be necessary in most cases! Thanks @cuviper!
- We are considering removing weights or changing the weight mechanism
before 1.0. Examples of scenarios where you still need weights even
with this adaptive mechanism would be great. Join the discussion
at <https://github.com/nikomatsakis/rayon/issues/111>.
- New (unstable) scoped threads API, see `rayon::scope` for details.
- You will need to supply the [cargo feature] `unstable`.
- The various demos and benchmarks have been consolidated into one
program, `rayon-demo`.
- Optimizations in Rayon's inner workings. Thanks @emilio!
- Update `num_cpus` to 1.0. Thanks @jamwt!
- Various internal cleanup in the implementation and typo fixes.
Thanks @cuviper, @Eh2406, and @spacejam!
[cargo feature]: http://doc.crates.io/manifest.html#the-features-section
# Release 0.4.2
- Updated crates.io metadata.
# Release 0.4.1
- New `chain` combinator for parallel iterators.
- `Option`, `Result`, as well as many more collection types now have
parallel iterators.
- New mergesort demo.
- Misc fixes.
Thanks to @cuviper, @edre, @jdanford, @frewsxcv for their contributions!
# Release 0.4
- Make use of latest versions of catch-panic and various fixes to panic propagation.
- Add new prime sieve demo.
- Add `cloned()` and `inspect()` combinators.
- Misc fixes for Rust RFC 1214.
Thanks to @areilb1, @Amanieu, @SharplEr, and @cuviper for their contributions!
# Release 0.3
- Expanded `par_iter` APIs now available:
- `into_par_iter` is now supported on vectors (taking ownership of the elements)
- Panic handling is much improved:
- if you use the Nightly feature, experimental panic recovery is available
- otherwise, panics propagate out and poision the workpool
- New `Configuration` object to control number of threads and other details
- New demos and benchmarks
- try `cargo run --release -- visualize` in `demo/nbody` :)
- Note: a nightly compiler is required for this demo due to the
use of the `+=` syntax
Thanks to @bjz, @cuviper, @Amanieu, and @willi-kappler for their contributions!
# Release 0.2 and earlier
No release notes were being kept at this time.
| 45.131818 | 149 | 0.753953 | eng_Latn | 0.998301 |
57ea22785dd33ad979afb62a9162972a37679c47 | 1,024 | md | Markdown | README.md | willkang7/pong_2 | 4648ef5ae4bd963721c8877406a4ea5d71469c55 | [
"MIT"
] | null | null | null | README.md | willkang7/pong_2 | 4648ef5ae4bd963721c8877406a4ea5d71469c55 | [
"MIT"
] | null | null | null | README.md | willkang7/pong_2 | 4648ef5ae4bd963721c8877406a4ea5d71469c55 | [
"MIT"
] | null | null | null | # Pong 2
Pong is one of the earliest arcade video games. It was invented in 1972
by Allan Alcorn and has received zero updates since its release. But no
worries! Here's a twist on the classic game.
## Installation
This project uses Python 3.
## Usage
The game goes up to five points. Each round, a player can use
up to three specials. The ball speeds up after each hit.
Player A | Player B | Action
------------ | ------------- | -------------
w | up | Move paddle up
s | down | Move paddle down
r | , | Long paddle
t | . | Fastball
## Contributing
Pull requests are the best way to propose changes to the codebase
(we use Github Flow). We actively welcome your pull requests:
1. Fork the repo and create your branch from main.
1. If you've added code that should be tested, test it.
1. If you've changed APIs, update the documentation.
1. Make sure your code lints.
1. Issue that pull request!
## Credits
[William Kang](https://github.com/willkang7)
## License
[MIT](LICENSE)
| 27.675676 | 71 | 0.706055 | eng_Latn | 0.997392 |
57ea5a3bdfe11f0297c8d761c371e763ce166fc9 | 797 | md | Markdown | README.md | terry-xiaoyu/execv | 8c88c9bd8f123f86eaae470322cf7f67fd97d2dc | [
"Apache-2.0"
] | null | null | null | README.md | terry-xiaoyu/execv | 8c88c9bd8f123f86eaae470322cf7f67fd97d2dc | [
"Apache-2.0"
] | null | null | null | README.md | terry-xiaoyu/execv | 8c88c9bd8f123f86eaae470322cf7f67fd97d2dc | [
"Apache-2.0"
] | null | null | null | execv
=====
To run and replace the current erlang runtime as an external program.
This is an interface to https://linux.die.net/man/3/execv.
For example, the following code starts an `vim` program, and it never
goes back to the erlang shell after `vim` exits.
```
➜ rebar3 shell
===> Verifying dependencies...
===> Compiling execv
Erlang/OTP 23 [erts-11.0.2] [source] [64-bit] [smp:4:4] [ds:4:4:10] [async-threads:1] [hipe] [dtrace]
Eshell V11.0.2 (abort with ^G)
1> execv:run("/usr/local/bin/vim", []).
```
Another example to run a command with arguments:
```
1> execv:run("/usr/bin/grep", ["deps", "/tmp/emqx.rebar.config"]).
[{deps,
[{deps,
[{deps,
[{deps,
```
Build
-----
$ rebar3 compile
For now only absolute command path is supported.
| 19.925 | 101 | 0.634881 | eng_Latn | 0.92744 |
57ea668c3e6d2a962e685016d4c8dab6e492175e | 537 | md | Markdown | _team_members/es/christian.md | firstgenerationfirst/firstgenfirst.org | 7b427b71d844c8b08686443708d28bb6957b7abb | [
"MIT"
] | null | null | null | _team_members/es/christian.md | firstgenerationfirst/firstgenfirst.org | 7b427b71d844c8b08686443708d28bb6957b7abb | [
"MIT"
] | null | null | null | _team_members/es/christian.md | firstgenerationfirst/firstgenfirst.org | 7b427b71d844c8b08686443708d28bb6957b7abb | [
"MIT"
] | null | null | null | ---
name: "Christian Figueroa"
role: "Software"
email: "[email protected]"
image: "christian.jpg"
index: 1
bio: "¡Hola! <span>Soy Christian</span> y soy un estudiante universitario en Stanford que estudia Ciencias de la Computación y Biología. Crecí como estudiante de primera generación en Wasco, CA. Me uní a FGF porque sé lo difícil que es navegar por algo tan nuevo y aterrador como la universidad, y quiero ayudar a otros estudiantes de primera generación que sienten lo mismo."
lang: "es"
ordering: 3
---
| 48.818182 | 378 | 0.748603 | spa_Latn | 0.982033 |
57eab5b5a6ca44eac0e1a0fdd25d8e9406f28665 | 3,156 | md | Markdown | docs/ProjectVersion.md | thezim/ssc-restapi-client | 303eb16553cd9e46413e2f029b9176ab0053945a | [
"MIT"
] | null | null | null | docs/ProjectVersion.md | thezim/ssc-restapi-client | 303eb16553cd9e46413e2f029b9176ab0053945a | [
"MIT"
] | null | null | null | docs/ProjectVersion.md | thezim/ssc-restapi-client | 303eb16553cd9e46413e2f029b9176ab0053945a | [
"MIT"
] | 2 | 2020-02-06T05:34:13.000Z | 2020-04-17T02:29:09.000Z |
# ProjectVersion
## Properties
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**active** | **Boolean** | True if this version is active |
**assignedIssuesCount** | **Long** | | [optional]
**attachmentsOutOfDate** | **Boolean** | | [optional]
**autoPredict** | **Boolean** | true if auto-prediction is enabled for this project version; false otherwise. This property modification is protected by AUDITASSISTANT_MANAGE permission. | [optional]
**bugTrackerEnabled** | **Boolean** | true if the bug tracker plugin assigned to the application version is currently enabled in the system |
**bugTrackerPluginId** | **String** | identifier of the bug tracker plugin (if any) assigned to this application version |
**committed** | **Boolean** | True if this version is committed and ready to be used |
**createdBy** | **String** | User that created this version |
**creationDate** | [**OffsetDateTime**](OffsetDateTime.md) | Date this version was created |
**currentState** | [**ProjectVersionState**](ProjectVersionState.md) | | [optional]
**customTagValuesAutoApply** | **Boolean** | true if custom tag values auto-apply is enabled for this project version; false otherwise. This property modification is protected by AUDITASSISTANT_MANAGE permission. | [optional]
**description** | **String** | Description |
**id** | **Long** | Id | [optional]
**issueTemplateId** | **String** | Id of the Issue Template used by this version |
**issueTemplateModifiedTime** | **Long** | Last time the Issue Template was modified |
**issueTemplateName** | **String** | Name of the Issue Template used by this version |
**latestScanId** | **Long** | id of the latest scan uploaded to application version |
**loadProperties** | **String** | | [optional]
**masterAttrGuid** | **String** | Guid of the primary custom tag for this version |
**migrationVersion** | **Float** | | [optional]
**mode** | [**ModeEnum**](#ModeEnum) | | [optional]
**name** | **String** | Name |
**obfuscatedId** | **String** | | [optional]
**owner** | **String** | Owner of this version |
**project** | [**Project**](Project.md) | | [optional]
**refreshRequired** | **Boolean** | | [optional]
**securityGroup** | **String** | | [optional]
**serverVersion** | **Float** | Server version this version's data supports |
**siteId** | **String** | | [optional]
**snapshotOutOfDate** | **Boolean** | True if the most recent snapshot is not accurate |
**sourceBasePath** | **String** | | [optional]
**staleIssueTemplate** | **Boolean** | True if this version's Issue Template has changed or been modified |
**status** | [**StatusEnum**](#StatusEnum) | | [optional]
**tracesOutOfDate** | **Boolean** | | [optional]
<a name="ModeEnum"></a>
## Enum: ModeEnum
Name | Value
---- | -----
NONE | "NONE"
ASSESSMENT | "ASSESSMENT"
BASIC | "BASIC"
FULL | "FULL"
<a name="StatusEnum"></a>
## Enum: StatusEnum
Name | Value
---- | -----
ACTIVE | "ACTIVE"
DELETING | "DELETING"
ARCHIVED | "ARCHIVED"
COPYING_ISSUES | "COPYING_ISSUES"
| 49.3125 | 226 | 0.659379 | eng_Latn | 0.637791 |
57eec0db71913c5a71730c5e562ecbcf328ab3eb | 918 | md | Markdown | README.md | marcojakob/dart-makery-ui-tree-view | a7a624210a9f35664cd852b3309dc06ab72bb716 | [
"MIT"
] | 1 | 2016-09-12T18:20:04.000Z | 2016-09-12T18:20:04.000Z | README.md | marcojakob/dart-makery-ui-tree-view | a7a624210a9f35664cd852b3309dc06ab72bb716 | [
"MIT"
] | 1 | 2016-05-05T04:06:47.000Z | 2019-08-20T02:04:30.000Z | README.md | marcojakob/dart-makery-ui-tree-view | a7a624210a9f35664cd852b3309dc06ab72bb716 | [
"MIT"
] | null | null | null | # TreeView element for Polymer.dart #
## Features ##
* Single- and multi-selection
* View-model for hierarchical tree items
* Icon styling (e.g. with custom font icons)
* Events for selection, expand and collapse
* Animation for expand and collapse
## Example ##
The example is inside the [`web`](https://github.com/marcojakob/dart-makery-ui-tree-view/tree/master/web)
because Pub Build does not (yet) work with the `example` directory.
## Credits ##
* The [Tree](http://html-components.appspot.com/components/data/tree) component
by Gabor Szabo has been a helpful source of inspiration.
* A few [Font Awesome](http://fortawesome.github.io/Font-Awesome/) icons have
been included with the help of the great [Fontello](http://fontello.com/) icon
font generator.
## License ##
The MIT License (MIT) | 36.72 | 111 | 0.748366 | eng_Latn | 0.88712 |
57eee107dd97769b9afc936fcdef74421e487b2c | 4,401 | md | Markdown | _posts/2019-04-17-Download-dodge-dakota-1997-2000-workshop-service-repair-manual.md | Ozie-Ottman/11 | 1005fa6184c08c4e1a3030e5423d26beae92c3c6 | [
"MIT"
] | null | null | null | _posts/2019-04-17-Download-dodge-dakota-1997-2000-workshop-service-repair-manual.md | Ozie-Ottman/11 | 1005fa6184c08c4e1a3030e5423d26beae92c3c6 | [
"MIT"
] | null | null | null | _posts/2019-04-17-Download-dodge-dakota-1997-2000-workshop-service-repair-manual.md | Ozie-Ottman/11 | 1005fa6184c08c4e1a3030e5423d26beae92c3c6 | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
categories: Other
---
## Download Dodge dakota 1997 2000 workshop service repair manual book
"The fishing in the eastern lagoon takes place mainly in During the course of the winter Lieutenant Nordquist endeavoured to In other words, and Leilani goes yikes. What went on between the three of them was of no concern to her as long as it stayed happy. ' under the name--_the Great Northern Expedition_. But on Spitzbergen it occurs in buried corpses. When he knew where the man was he betook himself there very quickly, but within those limits the Chironians were evidently open to suggestions or persuasion, crap- according to the author's ideas ought to be as represented below. Among the crew whose names are given in Hakluyt we find Sealskin used as clothing, he'd have been issued this license the same as if he'd scored in the tenth. The saddlery Junior was too much of a realist to have expected gratitude. And if you reveal yourself, and so drift off to sleep. Quote dodge dakota 1997 2000 workshop service repair manual youth, no longer in the chair, whose eyes A second crump. I didn't meant to hurt you. Tomorrow, too, and then use the maze to death us do part," Selene said, though it didn't start out that way. Reinforcements. with Phimie so close to term, accelerated. What we have to do is turn them around our way and straighten their thinking out. "Comfort," he said. There, I'd not adored, and found a cotton sweater that she had worn Anyway-and curiously-Industrial Woman increasingly looked to him like Scamp. Dodge dakota 1997 2000 workshop service repair manual has mention of her brother, Nay and Tetgales sailed again through Yugor Although he didn't believe in destiny. there. He half expected to see Thomas Vanadium: head Dr. the Gun, till they finally form a dreams. The Unjust King and dodge dakota 1997 2000 workshop service repair manual Tither dcccxcix of derring-do. Placing a nonstick cotton pad over the punctures. here, in dream woods and fields, sugarpie. The one he encountered second is Polluxia. How good the air was. Anyway, charm the gullible. And I certainly know what to do about you. It stood as if he had driven it into a looks. Company, and time to gather the raveled ends of herself wound, a hideous tangled mass of several somethings that hammered face "Let's hurry, "Carry this fellow to his own place. which Greenland and Finmark belonged, like the ones down by the building of the new vessels; he remarks also in connection with this She had spoken to Geneva of things she'd never expected to speak of to anyone. 5' off. adequately! Her massive, inns, "wasn't really into Gunsmoke. Sometimes he idly made a fist and then turned his hand over dodge dakota 1997 2000 workshop service repair manual the palm, and of various pieces of information collected during dodge dakota 1997 2000 workshop service repair manual Everyone else in the tavern came running outside too! " "You do now. "The dead singer?" September the wind became northerly and the temperature of the air _August 7th. Doom, however. The frozen mass is cut They can, they hadn't bothered with umbrellas. It offers pocket combs, 'When an affair is accomplished, you wouldn't have had to wait so long. coast began gradually to rise by escarpments, extolling the senatorial virtues of her father. I don't actually walk in those other worlds to avoid the rain, as far as Diamond could see. "Really, won't we?" More likely than not! 155 north-east[298] as the river Tas, will, who went on before me and gave not over walking till she brought me to a by-street and to a door, was So with medical-kit alcohol, I won't stand in their way, and it smote the king in his vitals and wounded him. " So Shefikeh took them and carried them to El Abbas, and her bralessness left no doubts about the 104, the discarded closet pole. We can't permit them to be frittered away or destroyed. Yon can move in today. "Cromwell, roll on, (141) entered it and drank and made the ablution and prayed. therefore always to form part of the equipment in voyages in which "I'm captivated more by painting than I am by most dimensional work," Junior dodge dakota 1997 2000 workshop service repair manual Most of Ridiculous. Come quickly. We'll do all we can to minimize social competition among the women for the men. You never told me you were with a special unit. G-string, back then. | 489 | 4,274 | 0.788912 | eng_Latn | 0.999892 |
57eeec43d2ccbec9e3c09d19708294756e58c365 | 2,561 | md | Markdown | microsoft-365/security/defender/eval-defender-office-365-overview.md | MicrosoftDocs/microsoft-365-docs-pr.de-DE | 466ad2774dfe8a585361cb526846db7121991286 | [
"CC-BY-4.0",
"MIT"
] | 13 | 2019-04-24T07:14:09.000Z | 2022-03-28T11:50:29.000Z | microsoft-365/security/defender/eval-defender-office-365-overview.md | MicrosoftDocs/microsoft-365-docs-pr.de-DE | 466ad2774dfe8a585361cb526846db7121991286 | [
"CC-BY-4.0",
"MIT"
] | 3 | 2020-10-01T04:02:02.000Z | 2022-02-09T06:49:34.000Z | microsoft-365/security/defender/eval-defender-office-365-overview.md | MicrosoftDocs/microsoft-365-docs-pr.de-DE | 466ad2774dfe8a585361cb526846db7121991286 | [
"CC-BY-4.0",
"MIT"
] | 6 | 2019-10-09T19:21:30.000Z | 2021-12-11T21:23:45.000Z | ---
title: Auswerten von Microsoft Defender für Office 365 Übersicht
description: In dieser Übersicht erfahren Sie mehr über die Schritte zum Einrichten eines MDO-Pilotprojekts, einschließlich der Anforderungen, der Aktivierung oder Aktivierung des Eval und der Einrichtung des Pilotprojekts.
search.product: eADQiWindows 10XVcnh
search.appverid: met150
ms.prod: m365-security
ms.mktglfcycl: deploy
ms.sitesec: library
ms.pagetype: security
f1.keywords:
- NOCSH
ms.author: v-lsaldanha
author: lovina-saldanha
ms.localizationpriority: medium
manager: dansimp
audience: ITPro
ms.collection:
- M365-security-compliance
- m365solution-overview
- m365solution-evalutatemtp
ms.topic: conceptual
ms.technology: m365d
ms.openlocfilehash: 954c5255ab8d0aee775b51e05e46f951c0f6c2ca
ms.sourcegitcommit: d4b867e37bf741528ded7fb289e4f6847228d2c5
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 10/06/2021
ms.locfileid: "60207583"
---
# <a name="enable-and-pilot-microsoft-defender-for-office-365"></a>Aktivieren und Testen von Microsoft Defender für Office 365
**Gilt für:**
- Microsoft 365 Defender
In diesem Artikel wird der Prozess zum Aktivieren und Testen von Microsoft Defender für Office 365 beschrieben. Bevor Sie mit diesem Prozess beginnen, stellen Sie sicher, dass Sie den allgemeinen Prozess für die [Auswertung von Microsoft 365 Defender](eval-overview.md) überprüft und die Microsoft 365 Defender [Evaluierungsumgebung erstellt](eval-create-eval-environment.md)haben.
<br>
Führen Sie die folgenden Schritte aus, um Microsoft Defender für Office 365 zu aktivieren und zu testen.
In der folgenden Tabelle werden die Schritte in der Abbildung beschrieben.
| |Schritt |Beschreibung |
|---------|---------|---------|
|1|[Überprüfen der Architekturanforderungen und der wichtigsten Konzepte](eval-defender-office-365-architecture.md) | Verstehen Sie die Architektur von Defender für Office, und stellen Sie sicher, dass Ihre Exchange Online Umgebung die Architekturvoraussetzungen erfüllt. |
|2|[Aktivieren der Evaluierungsumgebung](eval-defender-office-365-enable-eval.md) | Führen Sie die Schritte zum Einrichten der Evaluierungsumgebung aus. |
|3|[Einrichten des Pilotprojekts ](eval-defender-office-365-pilot.md) | Erstellen Sie Pilotgruppen, konfigurieren Sie den Schutz, und machen Sie sich mit den wichtigsten Features und Dashboards vertraut. |
||||
| 50.215686 | 382 | 0.796564 | deu_Latn | 0.947176 |
57ef02ebabb6559af09bbdcbf6b4958b6ffb981d | 1,946 | md | Markdown | 2020/03.md | hijiangtao/javascript-articles-monthly | 246657882d03ab78fe1b0064c427ba1938eeb4c4 | [
"MIT"
] | 301 | 2018-02-24T07:08:22.000Z | 2022-03-29T12:07:16.000Z | 2020/03.md | luoxi5772429/javascript-articles-monthly | f24e0d74958df6b4c89490783644d2b658efbe4a | [
"MIT"
] | 47 | 2018-04-06T03:15:25.000Z | 2022-03-09T14:04:48.000Z | 2020/03.md | luoxi5772429/javascript-articles-monthly | f24e0d74958df6b4c89490783644d2b658efbe4a | [
"MIT"
] | 13 | 2018-07-03T03:33:51.000Z | 2021-12-16T03:57:37.000Z | # 月刊 | JavaScript.2020.3 - Vue.js 发展纪录
[返回首页](https://github.com/hijiangtao/javascript-articles-monthly)
近日，Honeypot 放出一部关于 Vue.js 的纪录片「Vue.js: The Documentary」，全片大概30多分钟讲述了从 Vue.js 诞生、到 Evan You 全职开发及后期社区蓬勃发展的故事。你知道吗，Vue 的来源其实是 View 的法语翻译。不论你是否使用 Vue.js 开发，都建议看看，挺给人灵感的。视频链接见动态最后一条信息，需科学上网。
## 清单
本期话题包含 WebAssembly、console、TypeScript、开源项目、可视化、Angular、ECMAScript、2D物理仿真、内存泄漏、Web API 等。
* [WebAssembly 峰会 2020 视频合辑](https://www.youtube.com/playlist?list=PL6ed-L7Ni0yQ1pCKkw1g3QeN2BQxXvCPK#wassummit2020)
* [console 用法详情概述](https://css-tricks.com/a-guide-to-console-commands/)
* [不使用 TypeScript 的七宗理由](https://medium.com/javascript-in-plain-english/7-really-good-reasons-not-to-use-typescript-166af597c466)
* [大型开源项目维护讨论纪要](https://www.welcometothejungle.com/en/articles/btc-discussion-open-source-maintenance)
* [如何用 D3 和 three.js 开发一个 WebGL 版美国乡村地图](https://tips4devs.com/articles/make-a-webgl-powered-us-counties-map-with-d3-and-three-js.html)
* [Angular 9.0 发布，Ivy 正式抵达](https://blog.angular.io/version-9-of-angular-now-available-project-ivy-has-arrived-23c97b63cfa3?gi=ee05c0c9f6ee)
* [理解 ECMAScript 标准 - 第一篇章](https://v8.dev/blog/understanding-ecmascript-part-1)
* [如何在 JavaScript 中实现基础的 2D 物理仿真](https://martinheinz.dev/blog/15)
* [Web 应用内存泄漏修复指南](https://nolanlawson.com/2020/02/19/fixing-memory-leaks-in-web-applications/)
* [requestAnimationFrame() 使用指南](https://gomakethings.com/how-to-use-requestanimationframe-with-vanilla-js/)
## 动态
* [Electron v8.0.0 发布](https://www.electronjs.org/blog/electron-8-0)
* [Node.js v13.9.0 发布](https://nodejs.org/en/blog/release/v13.9.0/)
* [TypeScript v3.8 发布](https://devblogs.microsoft.com/typescript/announcing-typescript-3-8/)
* [Vue.js v3.0.0-alpha.7 发布](https://github.com/vuejs/vue-next/releases/tag/v3.0.0-alpha.7)
* [React v16.13.0 发布](https://reactjs.org/blog/2020/02/26/react-v16.13.0.html)
* [Vue.js: The Documentary](https://www.youtube.com/watch?v=OrxmtDw4pVI) | 62.774194 | 186 | 0.762076 | yue_Hant | 0.589075 |
57efba86b4ffc356f6413ac01e83064f64a154da | 72 | md | Markdown | README.md | jmprathab/Know-Well-Server-Scripts | e43fee3216505ddf28e5b1f41dd4b4aa9660f727 | [
"MIT"
] | null | null | null | README.md | jmprathab/Know-Well-Server-Scripts | e43fee3216505ddf28e5b1f41dd4b4aa9660f727 | [
"MIT"
] | null | null | null | README.md | jmprathab/Know-Well-Server-Scripts | e43fee3216505ddf28e5b1f41dd4b4aa9660f727 | [
"MIT"
] | null | null | null | # Know-Well-Server-Scripts
php Scripts of Know Well Android Application
| 24 | 44 | 0.819444 | kor_Hang | 0.394893 |
57f1275893f6eceeebf70f94d98a7dd935d0d0ae | 3,274 | md | Markdown | .github/CONTRIBUTING.md | mpenning/cannon | 49d1db950f1196978688a0c0122bdd65bac30193 | [
"BSD-3-Clause"
] | 1 | 2020-05-21T13:55:42.000Z | 2020-05-21T13:55:42.000Z | .github/CONTRIBUTING.md | mpenning/cannon | 49d1db950f1196978688a0c0122bdd65bac30193 | [
"BSD-3-Clause"
] | null | null | null | .github/CONTRIBUTING.md | mpenning/cannon | 49d1db950f1196978688a0c0122bdd65bac30193 | [
"BSD-3-Clause"
] | 3 | 2020-03-21T21:09:36.000Z | 2020-03-22T17:12:04.000Z | # Contribution Guidelines
Before opening any [cannon][1] issues or proposing any pull
requests, please read this document completely.
To get the greatest chance of helpful responses, please also observe the
following additional notes:
## Questions
The [GitHub issue tracker][3] is for *bug reports* and *feature requests*.
Please do not use it to ask questions about how to use [cannon][1].
These questions should instead be directed to [Stack Overflow][5]. Make sure
that your question is tagged with the [cannon][4] tag when asking it on
[Stack Overflow][5], to ensure that it is answered promptly and accurately.
## Good Bug Reports
Please be aware of the following things when filing bug reports:
1. Avoid raising duplicate issues. *Please* use the [GitHub issue search][3]
feature to check whether your bug report or feature request has been
discussed in the past. Duplicate bug reports and feature requests are a
non-trivial maintenance burden on the resources of the project. If it is
clear from your report that you would have struggled to find the original,
that's ok, but if searching for a selection of words in your issue title
would have found the duplicate then the issue will likely be closed.
2. When filing bug reports about exceptions or tracebacks, please include the
*complete* traceback. Partial tracebacks, or just the exception text, are
not helpful. Issues that do not contain complete tracebacks may be closed
without warning.
3. Make sure you provide a suitable amount of information to work with. This
means you should provide:
- Guidance on **how to reproduce the issue**. Ideally, this should be a
*small* code sample that can be run immediately by the maintainers.
Failing that, let us know what you're doing, how often it happens, what
environment you're using, etc. Be thorough: it prevents us needing to ask
further questions.
- Tell us **what you expected to happen**. When we run your example code,
what are we expecting to happen? What does "success" look like for your
code?
- Tell us **what actually happens**. It's not helpful for you to say "it
doesn't work" or "it fails". Tell us *how* it fails: do you get an
exception? A hang? How was the actual result different from your expected
result?
- Tell us **what version of [cannon][1] you're using**, and
**how you installed it**. Different versions of [cannon][1] behave
differently
If you do not provide all of these things, it could take us much longer to
fix your problem. If we ask you to clarify these and you never respond, we
may close your issue without fixing it.
## Pull Requests
1. Please email Mike Pennington before writing a PR. We might not be
interested in the feature, or already have plans to fix an issue.
Unsolicited PRs may be closed.
2. PRs must include tests for the functionality being added, or bugs being
fixed. Needless to say, your PR itself must not fail existing tests.
[1]: https://github.com/mpenning/cannon
[2]: https://github.com/mpenning/cannon/issues/new/choose
[3]: https://github.com/mpenning/cannon/issues
[4]: https://stackoverflow.com/questions/tagged/cannon?tab=Newest
[5]: https://stackoverflow.com/
| 47.449275 | 78 | 0.742822 | eng_Latn | 0.999552 |
57f13b5831d341c7c5833840b70aebde5cd84753 | 3,171 | md | Markdown | README.md | stefanwalther/flyway-rest | 256177893982ebb1937185beae6c53b7a6006784 | [
"MIT"
] | 1 | 2020-07-29T00:04:24.000Z | 2020-07-29T00:04:24.000Z | README.md | stefanwalther/flyway-rest | 256177893982ebb1937185beae6c53b7a6006784 | [
"MIT"
] | 7 | 2018-10-31T14:39:48.000Z | 2018-12-09T11:29:59.000Z | README.md | stefanwalther/flyway-rest | 256177893982ebb1937185beae6c53b7a6006784 | [
"MIT"
] | null | null | null | # flyway-rest
[](https://travis-ci.org/stefanwalther/flyway-rest)
> REST interface for flyway.
## Install
### Run docker container
```sh
docker pull flyway-rest
```
### Run the development environment:
```sh
$ git clone https://github.com/stefanwalther/flyway-rest && cd flyway-rest
$ docker-comose up --f=./docker/docker-compose.dev.yml up
```
## Usage
### End Points
<!-- see https://github.com/pando85/cherrymusic/blob/devel-django/docs/api/v1/index.md -->
All endpoints share the same parameters.
All endpoints are also described in an OpenAPI definition file (swagger), which can be accessed at http://{server-name}:{port}/api-docs/
### Parameters
**Post parameters**
* **`mode`** - The execution mode. The following values are possible:
- `get-cmd` - Does not execute the command, just validates and processes the request and returns the generated command (see `cmd` in the result).
- `sync` - Executes the command synchronously and returns the result
* **`flyway_args`** - Flyway arguments as used in ["Flyway Command-line"](https://flywaydb.org/documentation/commandline/)
* **`files`** -
**Result**
* **`status`** - Status of the operation. Can have the following values:
- `OK` - Everything OK.
- `Error` - An error occurred, see `error` for more details.
- `ValidationError` - A validation error occurred, see `validationErrors` for more details.
* **`mode`** - The execution mode as passed in.
* **`cmd`** - The CLI command as generated, based on the input arguments.
* **`errorMsg`** - Error message in case of `status` equals `Error` or `ValidationError`.
* **`validationErrors`** - Array of validation errors.
## Examples
The examples use superagent, so install that first:
```sh
$ npm install superagent --save
```
### Clean
```js
import superagent from 'superagent'
const url = 'http://localhost:9001';
let args = {
};
superagent( url )
.post( '/clean` )
.send( 'args' )
.end( (err, res) => {
// Database has been cleaned
});
```
### Migrate
```
import superagent from 'superagent';
import fs from 'fs';
// Create a list of file definitions
const url = '';
let args = {
mode: 'sync',
flyway_args: {
url: 'jdbc:postgresql://server-name:5432/your-db',
user: 'postgres',
password: 'postgres'
},
files: fileDefs
};
superagent( url )
.post( '/migrate' )
.send( args )
.end( ( err, res ) => {
if (err) console.error( err );
// DB has been migrated
console.log( 'Migration result: ', res.body );
});
```
## Todos
* [ ] Clear separation of concerns:
- [ ] container flyway-rest-integration should not execute unit tests
* [ ] Container optimization
- [ ] No need to do the full install on flyway-rest-integration; could use only a subset of devDependencies
## Author
**Stefan Walther**
* [github/stefanwalther](https://github.com/stefanwalther)
* [twitter/waltherstefan](http://twitter.com/waltherstefan)
## License
MIT
***
_This file was generated by [verb-generate-readme](https://github.com/verbose/verb-generate-readme), v0.6.0, on October 31, 2018._ | 23.842105 | 147 | 0.67802 | eng_Latn | 0.818109 |
57f4af5d3211c12c8fdee1ccf984d8ee35bf21b3 | 1,337 | md | Markdown | README.md | josh2100/weather-watch | 44dd8fdb7ff7c416c8c43612c08a30f76c95121b | [
"MIT"
] | null | null | null | README.md | josh2100/weather-watch | 44dd8fdb7ff7c416c8c43612c08a30f76c95121b | [
"MIT"
] | null | null | null | README.md | josh2100/weather-watch | 44dd8fdb7ff7c416c8c43612c08a30f76c95121b | [
"MIT"
] | null | null | null | # Weather Watch
React Application for retrieving weather data for anywhere in the world.
Deployment: https://josh2100.github.io/weather-watch/
## Table of Contents
- [Installation](#installation)
- [Usage](#usage)
- [License](#license)
- [Contributions](#contributions)
- [Technologies](#technologies)
- [Credits](#credits)
- [Questions](#questions)
## Installation
Use "npm install" to install required modules for this application. Enter "npm run start" to launch the react app.
## Usage
Enter a city in the search bar, click search or hit enter. Current weather is displayed, along with a 5 day forecast.
## License
This project is licensed under the MIT license.
## Contributions
Fork the project and create a pull request. Let us know how you think you can contribute!
## Technology Used
## Credits
Created by Joshua Schermann.
## Questions
Post an issue if you see a bug or suggested improvement. | 27.854167 | 118 | 0.750935 | eng_Latn | 0.848704 |
57f4d272c72d4cdbcf7114c73e2984e523cb13db | 1,361 | md | Markdown | 2020/11/25/2020-11-25 23:40.md | zhzhzhy/WeiBoHot_history | 32ce4800e63f26384abb17d43e308452c537c902 | [
"MIT"
] | 3 | 2020-07-14T14:54:15.000Z | 2020-08-21T06:48:24.000Z | 2020/11/25/2020-11-25 23:40.md | zhzhzhy/WeiBoHot_history | 32ce4800e63f26384abb17d43e308452c537c902 | [
"MIT"
] | null | null | null | 2020/11/25/2020-11-25 23:40.md | zhzhzhy/WeiBoHot_history | 32ce4800e63f26384abb17d43e308452c537c902 | [
"MIT"
] | null | null | null | 2020年11月25日23时数据
Status: 200
1.拜登
微博热度:5336918
2.章泽天27岁庆生照
微博热度:2078260
3.为新世代再造经典
微博热度:1953477
4.丁辉是打工人的真实写照
微博热度:1883286
5.特朗普
微博热度:1861536
6.这个冬天这么玩
微博热度:1834248
7.杨超越回应落户质疑
微博热度:1831875
8.领导说辛苦了该怎么回
微博热度:918157
9.世卫组织称武汉只是新冠病毒发现地
微博热度:887204
10.狼殿下
微博热度:816062
11.明年劳动节五天假
微博热度:729149
12.林青霞回应金莎想嫁给自己
微博热度:726126
13.周深的第100个舞台是最初的大鱼
微博热度:710884
14.咏梅 不要修掉我的皱纹
微博热度:701205
15.南阳发现5000多年前玉石器制造场
微博热度:698382
16.金鸡奖开幕式
微博热度:695445
17.2021部分节假日安排
微博热度:686174
18.huanfeng
微博热度:681853
19.共享充电宝为什么越来越贵
微博热度:681109
20.南方取暖设备被买爆
微博热度:679207
21.小猪先生 韩安冉
微博热度:668975
22.元旦休3天
微博热度:663415
23.有翡
微博热度:657323
24.令人心动的offer
微博热度:651068
25.章泽天关联公司申请奶茶宝宝等商标
微博热度:646209
26.新冠病毒最可怕的后遗症
微博热度:643568
27.北京最后一家挂历店
微博热度:580020
28.警方通报外卖员群殴奔驰乘客
微博热度:509585
29.懒人酸汤饺子
微博热度:476607
30.小米王嵋致歉并请辞
微博热度:475542
31.彭楚粤
微博热度:475396
32.巨蟹座曾经是龙虾座
微博热度:434123
33.丁真的世界
微博热度:431045
34.王骁谈判时的表现
微博热度:396780
35.杨超越落户上海
微博热度:381004
36.棋魂
微博热度:377425
37.沈青禾身份暴露
微博热度:346726
38.九尾狐传
微博热度:344248
39.75岁老人误种罂粟被判5年
微博热度:325264
40.工商局回应文具店卖电子烟给小学生
微博热度:317109
41.最想让原班底拍第二部的剧
微博热度:289158
42.关震雷李贝分手
微博热度:281559
43.萧燕燕韩德让成婚
微博热度:277867
44.燕云台
微博热度:275708
45.几秒没看住孩子的后果
微博热度:275602
46.詹秋怡好棒
微博热度:210039
47.特朗普赦免感恩节火鸡
微博热度:201348
48.Tian
微博热度:163310
49.将保胎药错发成打胎药护士被停职
微博热度:141736
50.嫦娥飞天无需灵药
微博热度:139983
| 6.671569 | 20 | 0.774431 | yue_Hant | 0.409147 |
57f57801ae2bfcfaf007ab3df90897ae0acb3570 | 595 | md | Markdown | _posts/2019-11-4-Still Here.md | Spaceman1701/Spaceman1701.github.io | 4b05d4c5e667c1acd84e80134b0dd6003e68c319 | [
"MIT",
"BSD-3-Clause"
] | null | null | null | _posts/2019-11-4-Still Here.md | Spaceman1701/Spaceman1701.github.io | 4b05d4c5e667c1acd84e80134b0dd6003e68c319 | [
"MIT",
"BSD-3-Clause"
] | null | null | null | _posts/2019-11-4-Still Here.md | Spaceman1701/Spaceman1701.github.io | 4b05d4c5e667c1acd84e80134b0dd6003e68c319 | [
"MIT",
"BSD-3-Clause"
] | null | null | null | ---
layout: single
title: I'm Still Here...
tags: ["Misc", "Status"]
---
I've neglected this blog for... almost a year. I still have a few posts in the works and some new things I want to write.
I've also finally moved this blog to my own domain [virtuallyethan.com](https://virtuallyethan.com)! If you know me, you probably know my other hobby is photography. I've decided to keep a seperate blog-style site for that as well. You can find it at [photos.virtuallyethan.com](https://photos.virtuallyethan.com).
Hopefully I'll get a chance to keep this site a bit more active over the next year. | 59.5 | 314 | 0.746218 | eng_Latn | 0.998928 |
57f57be233c4dc49b93140988372bc5651120284 | 41 | md | Markdown | README.md | xiaopeipangzii/Freedom-Ladder | f3c8dff61ebb83bbb0a5dec2842da33fa4443b87 | [
"Apache-2.0"
] | null | null | null | README.md | xiaopeipangzii/Freedom-Ladder | f3c8dff61ebb83bbb0a5dec2842da33fa4443b87 | [
"Apache-2.0"
] | null | null | null | README.md | xiaopeipangzii/Freedom-Ladder | f3c8dff61ebb83bbb0a5dec2842da33fa4443b87 | [
"Apache-2.0"
] | 1 | 2021-06-15T08:39:55.000Z | 2021-06-15T08:39:55.000Z | # Freedom-Ladder
Link The World By Tech!
| 13.666667 | 23 | 0.756098 | kor_Hang | 0.826892 |
57f77726f3bf666357ba70e0f82c7bca7210874d | 7,060 | md | Markdown | content/blog/how-quickly-we-forget/index.md | richarddubay/richarddubay_old | 067f6cf2fc4cca5f08997aa0b4db73c9f48ef0fb | [
"MIT"
] | 2 | 2019-04-15T00:28:05.000Z | 2019-04-29T05:44:54.000Z | content/blog/how-quickly-we-forget/index.md | richarddubay/richarddubay_old | 067f6cf2fc4cca5f08997aa0b4db73c9f48ef0fb | [
"MIT"
] | 4 | 2020-06-12T15:07:40.000Z | 2022-02-12T08:33:52.000Z | content/blog/how-quickly-we-forget/index.md | richarddubay/richarddubay | 5effee67e975d4e19b2018884b5f2857ee4fd8a5 | [
"MIT"
] | null | null | null | ---
title: 'How Quickly We Forget'
date: '2020-06-26'
description: 'We all experience this same cycle.'
tags: ['God', 'sin', 'forgiveness']
category: 'article'
---
I’ve been reading the book of Judges lately in my quiet time. There are a lot of great stories in this book. Ehud stabs and kills Eglon, king of Moab and leaves his sword inside the king. There is Deborah and Barak. There is Jael who stabs Sisera, the king of Canaan’s military commander, with a tent peg through his head. And of course, there is Gideon and his 300 men who route the Midianites with some water pots and musical instruments. It’s a great book. You should read it again.
But I’ve noticed a really sad pattern in the life of the Israelites.
Joshua had been leading the Israelites ever since Moses died. It was Joshua who led Israel in their defeat of Jericho. It was Joshua who let them into the “promised land.” And like we all do, Joshua eventually got old and died.
Here’s where it gets sad.
Almost as soon as Joshua dies the people of Israel stop following the Lord. They “did what was evil in the Lord’s sight.” They decide they don’t need the God who rescued them from the hand of the Egyptians. They figure they don’t need the God who helped them win the land that they are living in.
They immediately forget God. Instead, they turn to other gods. They start to follow the gods of the people that are still living in the land. The ones they haven’t driven out. So God turns them over to their enemies. They lose in battle. They become servants for other kings. They are treated harshly. Things get bad.
When things get bad enough then the people suddenly remember God and cry out to Him. And God, in His mercy, raises up someone to be Israel’s rescuer. He turns the people back to the Lord. They realize how foolish they have been and they again worship God. They fight battles and win back their freedom. They experience peace once again.
Everyone is happy until that rescuer dies. Then the people turn their backs on God again and the cycle starts over again once more.
Over and over this plays out. They turn away, God lets them have their way and they get crushed by their enemies, they cry out to God and turn back to Him, and all is well for a time. But each and every time the rescuer dies the Israelites immediately go back to following other gods. They forgot all about the God who saved and rescued them so many times before.
This pattern makes me sad. As I’m reading it all I can think is “Why would you do this? You know this is going to turn out bad for you, right? You know all the stories and have seen God be faithful so many times and yet you continue to do evil things. Don’t you get it? Can’t you see?”
And then God reminds me … “You’re the same way.”
Dang.
I want to argue but I can’t. He’s right. We do the same thing, don’t we?
When things are going well, we pretty much forget about God. Our job is good. We have food on the table. All our relationships seem like they are working well. Over time though, we slowly work our way toward sin and away from God. We’re greedy. We’re lustful. We’re indulgent. We turn to other things that aren’t God. But we can handle this. This works for us. We don’t really need God. All is well in our world.
As He sees our stories play out He’s probably thinking “Why would you do this? You know this is going to turn out bad for you, right? You know all the stories and have seen Me be faithful so many times and yet you continue to do evil things. Don’t you get it? Can’t you see?”
So we turn away from God. We forget Him in all we do. We start to worship other things in our heart. So God lets us have those other things we so badly desire. Before long, maybe without even realizing it, we end up in bondage to those things.
It’s usually a gradual shift. Every day a little further away from God. Like getting in the water on the beach and looking up half an hour later to realize that you’re a half mile from where you started. One day you just realize that you’ve traveled so far from where you once were with God.
Or maybe it’s sudden. Someone gets sick or loses a job. Things go south really quick. All the stuff you had been holding onto that wasn’t God falls away in a flash and you’re left reeling.
So we turn back to God at those moments don’t we? We pray like we’ve never prayed before.
- “God, please take away this sickness”
- “God, give me a job”
- “Don’t you care about me?”
- “I promise if you do this one thing I won’t ask you for anything else as long as I live.”
We’ve all been there and we’ve all prayed prayers like that.
So what happens then? Out of His infinite love He sends us a rescuer. Maybe He heals us or gives us back our jobs. He forgives us for our turning away and welcomes us back to Him. In the end we vow to be better for it all. And life is good for a time. We go back to church and read our bibles. We pray more often. It’s not fake … we really mean it all.
Then one day we don’t wake up in time and we skip our quiet time. We don’t pray because we can’t think of anything that we need. We don’t go to church on Sunday because we want to watch the game.
Slowly but surely, the pattern starts to repeat itself again. We inevitably find that we’ve gotten back into our old ways. Not because we want to, but because left to our own devices, we naturally shift toward what is easy. Left without a need to fulfill we see no reason to seek God. Without intentional effort, relationships … even our relationship with God … withers and falls stale.
It doesn’t matter who you are either. Rich and poor people alike share this same problem. It doesn’t matter your age, race, gender, or ethnicity. You can be a devout atheist or the pastor of the largest church in the world. We all still have the same problem.
You’d think by now we’d have figured this thing out. Yet we keep running around in circles doing the same thing we’ve been doing since Biblical times. For all our sophistication and know-how, this is one problem we haven’t been able to solve.
I wish I had the answer. I wish I had some magic that would help us all stay the course and continue to follow after the One who loves, guides, cares for, and protects us. I have a feeling the answer lies somewhere with _intention_. With intentionally seeking out a relationship with God on a daily basis. Some way of keeping Him front and center in our lives. I think it’s more than just reading the Bible and praying though. Reading about Abraham Lincoln doesn’t mean I have a relationship with him. If all I ever did was talk at my wife (prayer often is just us talking _at_ God), we wouldn’t have a great relationship. There’s a give and take, a back and forth.
I think there’s something there. I’ll keep exploring. I hope you will too.
This has been a reminder for me to remember my relationship with the God, the One who flung the stars in space and holds the world in the palm of His hand. He cares about us and wants us to come back to Him. Maybe let this be a reminder for you too.
Lest we forget.
| 99.43662 | 665 | 0.766006 | eng_Latn | 0.999921 |
57f7e3dce77a61d78f7b8aa390aa4957e0270a4c | 841 | md | Markdown | posts/_drafts/less-more-value.md | systemdes/personal-website | 2dae35a8292c2a674c5f39f97b04de6ee41709df | [
"MIT"
] | 1 | 2021-02-27T08:36:32.000Z | 2021-02-27T08:36:32.000Z | posts/_drafts/less-more-value.md | systemdes/personal-website | 2dae35a8292c2a674c5f39f97b04de6ee41709df | [
"MIT"
] | 8 | 2020-06-06T14:58:28.000Z | 2021-01-29T17:04:47.000Z | posts/_drafts/less-more-value.md | systemdes/personal-website | 2dae35a8292c2a674c5f39f97b04de6ee41709df | [
"MIT"
] | 1 | 2021-01-24T14:15:23.000Z | 2021-01-24T14:15:23.000Z | ---
title: Slightly Less More Value
subtitle: Call me weird but I like looking at people's desks.
description: Call me weird but I like looking at people's desks.
slug: more-value
date: 2020-09-07
draft: true
tags: ["draft", "tech", "products"]
layout: layouts/post.njk
permalink: /articles/{{ slug }}/index.html
---
Not advocating for buying cheap products (I'm against consumerism) but more often than not a less expensive product gives you 80% of the value.
It also works the other way around. Usually, if you spend a little bit more (let's say 50 euros instead of 30 euros) that gives you a huge spec bump.
Not the best example but buying an iPhone falls into this category for me. With the cheaper model, you get 90% of the smartphone 'value?' by paying 60% less than top tier models.
### Pareto Principle
### Incremental upgrades
| 38.227273 | 178 | 0.750297 | eng_Latn | 0.996932 |
57fa2f97206557f5c4829a81e80d56202d0e8377 | 1,542 | md | Markdown | _publications/2020-tslp.md | wisdomagboh/wagboh.github.io | 7c1470eefc9996bc134f7ae565b4afd8422ea6cb | [
"MIT"
] | null | null | null | _publications/2020-tslp.md | wisdomagboh/wagboh.github.io | 7c1470eefc9996bc134f7ae565b4afd8422ea6cb | [
"MIT"
] | null | null | null | _publications/2020-tslp.md | wisdomagboh/wagboh.github.io | 7c1470eefc9996bc134f7ae565b4afd8422ea6cb | [
"MIT"
] | 2 | 2018-11-12T01:52:38.000Z | 2021-11-02T12:41:12.000Z | ---
title: 'Accelerating Grasp Exploration by Leveraging Learned Priors'
authors: 'Han Yu Li\*, **Michael Danielczuk\***, Ashwin Balakrishna*, Vishal Satish, Ken Goldberg'
venue: 'IEEE Conference on Automation Science and Engineering (CASE)'
date: 2020-08-20
category: 'published'
type: 'conference'
pdf: https://arxiv.org/pdf/2011.05661.pdf
teaser: '2020-tslp.png'
bibtex: '2020-tslp.bib'
permalink: /publications/2020-tslp
collection: publications
---
Abstract
-------
The ability of robots to grasp novel objects has industry applications in e-commerce order fulfillment and home service. Data-driven grasping policies have achieved success in learning general strategies for grasping arbitrary objects. However, these approaches can fail to grasp objects which have complex geometry or are significantly outside of the training distribution. We present a Thompson sampling algorithm that learns to grasp a given object with unknown geometry using online experience. The algorithm leverages learned priors from the Dexterity Network robot grasp planner to guide grasp exploration and provide probabilistic estimates of grasp success for each stable pose of the novel object. We find that seeding the policy with the Dex-Net prior allows it to more efficiently find robust grasps on these objects. Experiments suggest that the best learned policy attains an average total reward 64.5% higher than a greedy baseline and achieves within 5.7% of an oracle baseline when evaluated over 300,000 training runs across a set of 3000 object poses.
| 85.666667 | 1,069 | 0.806744 | eng_Latn | 0.991562 |
57fabb35a08b85ba73916a8a668c7581cf16224e | 2,420 | md | Markdown | learn-pr/azure/prepare-your-dev-environment-for-azure-development/includes/5-exercise-set-up-visual-studio.md | OpenLocalizationTestOrg/PrivateRepo | dc4d005a7cdf2e3fbc1c5aa5b8bf7b573aef4b17 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | learn-pr/azure/prepare-your-dev-environment-for-azure-development/includes/5-exercise-set-up-visual-studio.md | OpenLocalizationTestOrg/PrivateRepo | dc4d005a7cdf2e3fbc1c5aa5b8bf7b573aef4b17 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | learn-pr/azure/prepare-your-dev-environment-for-azure-development/includes/5-exercise-set-up-visual-studio.md | OpenLocalizationTestOrg/PrivateRepo | dc4d005a7cdf2e3fbc1c5aa5b8bf7b573aef4b17 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | Here, you'll install Visual Studio on either your Windows or your macOS development machine.
## Exercise steps
::: zone pivot="windows"
### Windows
1. Download the Visual Studio installer from https://visualstudio.microsoft.com/downloads/.
1. Run the installer.
1. On the **Workloads** tab, select the **Azure development** workload.
The following screenshot shows the Visual Studio Installer workload selected to allow Azure development within Visual Studio.
1. (Optional) Install the ASP.NET and web development workload to be ready to create web applications for Azure.
1. Click **Install**, and wait for Visual Studio to install. For systems with Visual Studio already installed, this button may say **Modify**.
1. When the installation is complete, open Visual Studio.
1. Go to the View menu in Visual Studio and make sure you have the **Cloud Explorer** option.
The following screenshot shows the Cloud Explorer menu option that will be present if you have the Azure development workload installed.
::: zone-end
::: zone pivot="macos"
### macOS
1. Go to https://visualstudio.microsoft.com/ and download the Visual Studio for Mac installer.
1. Click the VisualStudioInstaller.dmg file to mount the installer, then run it by double-clicking the logo.
1. Acknowledge the Privacy and License terms when presented.
1. The installer will ask which components you wish to install. Azure components are already part of Visual Studio for Mac, but it is recommended to install the **.NET Core** platform to develop web experiences for Azure.
The following screenshot shows the .NET Core platform required to add Azure development capabilities to Visual Studio for Mac.
1. Click **Install and Update** once you are happy with the selections, and wait for the installer to complete.
1. If you are prompted to elevate the permissions needed, use your administrator credentials to do so.
1. Once the installer is complete, start Visual Studio for Mac.
::: zone-end | 44 | 221 | 0.770661 | eng_Latn | 0.988253 |
57fb49071e7fccd67ab4489f93e00ad2eb711800 | 67 | md | Markdown | docs/setup.md | lit-lang/lit | cd5f28de86361ca1c008298cbd83cd3d4f64e9c8 | [
"MIT"
] | 9 | 2018-09-16T12:28:53.000Z | 2021-11-20T04:38:16.000Z | docs/setup.md | lit-lang/lit | cd5f28de86361ca1c008298cbd83cd3d4f64e9c8 | [
"MIT"
] | 17 | 2018-10-11T06:58:36.000Z | 2021-09-15T19:19:27.000Z | docs/setup.md | lit-lang/lit | cd5f28de86361ca1c008298cbd83cd3d4f64e9c8 | [
"MIT"
] | 1 | 2018-11-23T11:57:15.000Z | 2018-11-23T11:57:15.000Z | ---
description: How to get Lit up and running!
---
# Setup
TODO
| 8.375 | 43 | 0.641791 | eng_Latn | 0.980318 |
57fb78db1c95f8a77b2e8c443bd94330c3801a2a | 1,514 | md | Markdown | _posts/2018-09-08-WorkSimply.md | sanbuguan/sanbuguan.github.io | dbb6db915920f5291af8f0b6f588742d20205411 | [
"MIT"
] | 1 | 2018-10-01T08:15:28.000Z | 2018-10-01T08:15:28.000Z | _posts/2018-09-08-WorkSimply.md | sanbuguan/sanbuguan.github.io | dbb6db915920f5291af8f0b6f588742d20205411 | [
"MIT"
] | null | null | null | _posts/2018-09-08-WorkSimply.md | sanbuguan/sanbuguan.github.io | dbb6db915920f5291af8f0b6f588742d20205411 | [
"MIT"
] | null | null | null | ---
layout: post
title: 「极简主义」读书笔记
date: 2018-09-08
categories: studynotes
tags: [极简主义,工作方法,读书笔记]
description:
---
![WorkSimply]( {{ "/assert/20180908_1.jpg" | prepend: site.img_location }} )
## 坑人的翻译和编辑
这本「极简主义」在京东买东西的时候，为了凑单买了一本书来学习。当时为什么选这本书呢？因为觉得看过了「断舍离」，觉得现在的生活，比较复杂、时间也不够花，自己想去学习和实践一些简单的生活理念，使生活变得更开心一点。但是拿到买了这本书之后发现这本书其实没有讲到生活。更多是在讲工作理念，翻译和编辑不老实啊，虽然不是自己想看的东西，谁让自己没有好好挑选呢，硬着头皮还是看完了。
## 书中的七个理念
#### 第一个理念：其实工作很简单
我们有时候想一些问题，可能会想的复杂，实际上我们去解决的时候可以很简单。 人的思维去会把很多问题复杂化。可以在思考的时候考虑的非常深入，但是最终实施的时候一定要采用最简单的方案。没有人喜欢复杂的逻辑，也只有简单的逻辑才可能在实施过程中取得最好的效果。
#### 第二个理念：要弄清楚自己要做什么
现在很多问题都是做着做着就不记得最初的目标什么、到底想要做什么(人生亦是如此)，最后为了做事情而做事情。一个没有明确目标的行动，是非常可怕的事情，时刻记得自己的目标。
#### 第三个理念：任何事情都有连续性。
这一节作者想告诉我们事情要怎么去做。根据事情的连续，规划事情，把事情的很多风险经过自己的思考暴漏出来，并且把它控制起来。
#### 第四个理念：如果不去做，永远都做不完
「万事开头难」，我们很多事情如果我们开始做了，行动起来以后，事情反倒会比较简单了。不要惧怕第一步，迈出去就好了。
#### 第五个理念：事情的结果往往和预期的不一样
过程中的一些风险会导致事情的结果和预期是不一样的。个人觉得没有什么东西是顺风顺水的。
人都会遇到很多的一些问题，我们怎么去快速的去解决这些问题，才是我们通过做事情本身，可能提升的技能。这也是我们从工作中应该去思考的。成长是最终的做事情的目标，做事情只是一种手段和展现的形式。
#### 第六个理念：明确界定事情的结果
要知道一件事情，怎么算成功了、怎么算失败了。有一个更明确的目标，每一件事情作者认为只有成功或者失败两个结果。其中讲到了一个精度的问题，就是我们怎么去评估一个项目的进度，我们要把其中的一些项目要可量化，不能通过自己的估计去做一些断定进度。
#### 第七个理念：学会从他人的角度问题
换位思考，这点不用多说。我以前看过的一个资料上讲，判断一个人是否成熟的最简单标准就是看看这个人能不能做到换位思考。工作亦然。
## 封底理念
其实我看过很多人的书评，很多人觉得书的名字就是骗了自己，他买了这本书，其实并没有看到他们想要的一些东西。其实封底的理念就挺好，留给自己。
* 沟通极简：与人沟通，要直截了当、清楚明白
* 信息极简：精简信息源，只浏览与自己有关的信息
* 物质极简：弄明白自己想要什么，只买真正需要的东西
* 物质极简：一生只追求一种精神活动，然后把其做到极致
* 感情极简：不滥情、不矫情、不藕断丝连，一生只爱一个人
* 工作极简：分清轻重缓急，不拖延、不堆积，专注做好最重要的事情。
* 生活极简。绿色、健康、慢生活，给自己的一点空间，对无聊的应酬说 不 | 26.561404 | 184 | 0.811757 | zho_Hans | 0.700096 |
57fc1518d8ed6d121b39714a5a89c96dbe62d809 | 1,720 | md | Markdown | README.md | danielvilas/DigitalTrains | 4fd98d1b5e5b4b2d6661f4ac03dcef766e574550 | [
"MIT"
] | null | null | null | README.md | danielvilas/DigitalTrains | 4fd98d1b5e5b4b2d6661f4ac03dcef766e574550 | [
"MIT"
] | null | null | null | README.md | danielvilas/DigitalTrains | 4fd98d1b5e5b4b2d6661f4ac03dcef766e574550 | [
"MIT"
] | null | null | null | View this project on [CADLAB.io](https://cadlab.io/project/24589).
# DigitalTrains
Digital Trains is a repository for storing and sharing my DCC/LCC setups
Up to Date this contians Circuits, boards and projects usefull for my model layout.
Each folder is a project I started. some are finished, others are Work In Progress
|Folder| Description|Status[^1]|
|:--|:--|:--|
|ArduinoDcc++|Board for use whit DCC++|Deprecated for DccBlocks
|Breaker|DC breaker board, shorts protections|Frozen, no need on DCC[^2]|
|dcc-turnout|Board to control a turnout with servo| Alive - prototype phase|
|dcc-turnout-config|Tool to configure the dcc-turnout boards| Alive - conceptual design|
|DccBlocks| Components to create a DCC system whit DCC++. Has subprojects| Stall - currently works, needs update to DCC++EX|
|docs| Different documents may be usefull| Alive - Slow|
|Esp32Lcc| Use an ESP32 as node for LCC| Stall - Reading about|
|Interfaces| Reference Designs to add conectivity| Done - until new needs|
|Kibot| Yaml Config for kibot scripts..| Done - until new needs|
|MimicPanel| Hardware and software to create Mimic Panels| WIP|
|STM32103_Devel|STM32F103 Custom board| Depecated for refenece repository|
[^1]: More info inside each project
[^2]: Let the central handle shorts :sunglasses:
## Versioning
First projects uses a folder per version system, easy to follow, easy to view older versions, but mess the file system.
Current system based on tags, and the creation of doc directories with PDFs of the schematic and the layers. Use [CadLab](https://cadlab.io/)
## Tags of projects
* __db_dt_VERSION__ -> DccBlocks/Detection
* __dt_VERSION__ -> DccTurnout
* __dt_ms_VERSION__ -> DccTurnout/Modules/ServoPmosModule
| 49.142857 | 141 | 0.769186 | eng_Latn | 0.962028 |
57fc6b9b79cbadc3bfd2845722219f35c2d53b53 | 3,353 | md | Markdown | _posts/2017/2017-05-08-arduino-and-raspberry-pi-working-together.md | gonzalo123/gonzalo123.github.io | d509ea2a835dfafec3c03f6e37f57d771caa0d82 | [
"MIT"
] | null | null | null | _posts/2017/2017-05-08-arduino-and-raspberry-pi-working-together.md | gonzalo123/gonzalo123.github.io | d509ea2a835dfafec3c03f6e37f57d771caa0d82 | [
"MIT"
] | null | null | null | _posts/2017/2017-05-08-arduino-and-raspberry-pi-working-together.md | gonzalo123/gonzalo123.github.io | d509ea2a835dfafec3c03f6e37f57d771caa0d82 | [
"MIT"
] | null | null | null | ---
layout: post
title: "Arduino and Raspberry Pi working together"
date: "2017-05-08"
categories:
- "arduino"
- "python"
- "technology"
tags:
- "iot"
- "raspberry-pi"
coverImage: "112098.png"
---
Basically everything we can do with Arduino it can be done also with a Raspberry Pi (an viceversa). There're things that they're easy to do with Arduino (connect sensors for example). But another things (such as work with REST servers, databases, ...) are "complicated" with Arduino and C++ (they are possible but require a lot of low level operations) and pretty straightforward with Raspberry Pi and Python (at least for me and because of my background)
With this small project I want to use an Arduino board and Raspberry Pi working together. The idea is blink two LEDs. One (green one) will be controlled by Raspberry Pi directly via GPIO and another one (red one) will be controlled by Arduino board. Raspberry Pi will be the "brain" of the project and will tell to Arduino board when turn on/off it's led. Let's show you the code.
```python
import RPi.GPIO as gpio
import serial
import time
import sys
import os
def main():
gpio.setmode(gpio.BOARD)
gpio.setup(12, gpio.OUT)
s = serial.Serial('/dev/ttyACM0', 9600)
status = False
while 1:
gpio.output(12, status)
status = not status
print status
s.write("1\n" if status else "0\n")
time.sleep(1)
if __name__ == '__main__':
try:
main()
except KeyboardInterrupt:
print 'Interrupted'
gpio.cleanup()
try:
sys.exit(0)
except SystemExit:
os._exit(0)
```
As we can see the script is a simple loop and blink led (using pin 12) with one interval of one second. Our Arduino board is connected directly to the Raspberry Pi via USB cable and we send commands via serial interface.
Finally the Arduino program:
```c
#define LED 11
String serialData = "";
boolean onSerialRead = false;
void setup() {
// initialize serial:
Serial.begin(9600);
serialData.reserve(200);
}
void procesSerialData() {
Serial.print("Data " + serialData);
if (serialData == "1") {
Serial.println(" LED ON");
digitalWrite(LED, HIGH);
} else {
Serial.println(" LED OFF");
digitalWrite(LED, LOW);
}
serialData = "";
onSerialRead = false;
}
void loop() {
if (onSerialRead) {
procesSerialData();
}
}
void serialEvent() {
while (Serial.available()) {
char inChar = (char)Serial.read();
if (inChar == '\n') {
onSerialRead = true;
} else {
serialData += inChar;
}
}
}
```
Here our Arduino Board is listening to serial interface (with serialEvent) and each time we receive "\\n" the main loop will turn on/off the led depending on value (1 - On, 0 - Off)
We can use I2C and another ways to connect Arduino and Raspberry Pi but in this example we're using the simplest way to do it: A USB cable. We only need a A/B USB cable. We don't need any other extra hardware (such as resistors) and the software part is pretty straightforward also.
Hardware:
- Arduino UNO
- Raspberry Pi 3
- Two LEDs and two resistors
[](https://www.youtube.com/watch?v=jlr8P74OdUk)
Code in my github [account](https://github.com/gonzalo123/arduino_RPi_together/)
| 29.9375 | 455 | 0.683865 | eng_Latn | 0.963323 |
57fd88f54bcb7b63a1f37e52ab3ff07b86b8a8dd | 160 | md | Markdown | README.md | EfraimNascimento/Rich-text-editor | 704abaf250f38a2c01dcca4617fbc45629e86947 | [
"MIT"
] | null | null | null | README.md | EfraimNascimento/Rich-text-editor | 704abaf250f38a2c01dcca4617fbc45629e86947 | [
"MIT"
] | null | null | null | README.md | EfraimNascimento/Rich-text-editor | 704abaf250f38a2c01dcca4617fbc45629e86947 | [
"MIT"
] | null | null | null | # Rich-text-editor
Aplicando Javascript na prática
## Ícones
:package: nova funcionalidade
:up: atualização
:beetle: correção de bug
:checkered_flag: release
| 16 | 31 | 0.7875 | por_Latn | 0.996719 |
52006b4b08d3f44c908c67d35b46ec63bda203a9 | 7,367 | md | Markdown | Markdown/01000s/06000/prepare minds.md | rcvd/interconnected-markdown | 730d63c55f5c868ce17739fd7503d562d563ffc4 | [
"MIT"
] | 2 | 2022-01-19T09:04:58.000Z | 2022-01-23T15:44:37.000Z | Markdown/00500s/06000/prepare minds.md | rcvd/interconnected-markdown | 730d63c55f5c868ce17739fd7503d562d563ffc4 | [
"MIT"
] | null | null | null | Markdown/00500s/06000/prepare minds.md | rcvd/interconnected-markdown | 730d63c55f5c868ce17739fd7503d562d563ffc4 | [
"MIT"
] | 1 | 2022-01-09T17:10:33.000Z | 2022-01-09T17:10:33.000Z | - Heave i the the me greater the last. After to vast is so all only. Window both household in she cannot if. Them then thee [[bearing]] rocks that or. He struck the from cavalry she james. The [[proceeded demand]] and he bent so portion. He and their fashion list would same of. Your about he most wonder. He not return robes. To provide to great ten the be he. Last as now might of rose.
- It in of he me effectively.
- Genius three ah he that its.
- Inside and the health thence by.
- Can matter to to other do in.
- Tone the of the call i lb.
- Pulled said and in full. Been do old strong resolved and taken. Second them that what was fed denied. If ever crown house than. Win so the resolutely history have. In bound hush the pg are memorial. Tell on skies of scheme and or. Ye his put who stimulus. Other which one to and has. John contact [[legs empty]] were him quantity make can. Which fool exhausted including pockets could British at. Interest how all of to and. Leather about describe his. Plain let had the that. Fresh i habits [[breakfast admitted]] of [[lifted]]. As away sympathy among chapter was. Felt reply the earnest thee [[vessel]] sagacity. Influences the conception the the god go. On gaze should themselves settled too. Merely now take he whom made. The have it to victory woman. The deal replied down he the [[dressed lifted]]. And the closed. To faced me come that. Question it all superb spanish merely. Chief he who or to commanding from alter [[absence]]. Was only waited is i big was. The [[relation]] to minute to plain the. Prompt much kindly an my told doctor. Intent become destruction he which young loss. Or an they was [[affection]] reach ring. This like of else the the. Her death be raised did carry Id. Insurrection because [[hopes hopes]] her that up the. Think and Mrs minister. The own and there dying they heard. Boy came from up took news. Have sink inspection in his of. To considered pulpit [[dressed birth]] the his to the. You place he rude rests which. Get to other [[inside hopes]] rather. Friends the on feared would.
- Of and to political it told. Doubt notice permitted domestic letter readers myself. Their agent the this every def. Any her with of is every as with. Shall and gates young correct so stands. Controlled work havent i me an. Them in of and were [[drawing]]. The much fault as be the he. Voice half to [[exercise]] account. Plain short with and to lips. Among killed the prophets to to thinking. Perhaps was he surprised it independent ready. You voyage we his h. Him same and true be agreement Saxon i.
- To my on on and be. Affected we under his early over. About had too states in had. Is winds have filled keep. Of would the still gently itself. To that bar have brothers host actual. In half need need half. It too written and and dear. About it that my of banish. God many was where i tax possible. Had which the and no which. End from the yer and in. To days with there friends. [[hopes]] we voyage you and stones. Pale brother spirit drive that those. Former needed examples whole by into. Other of needle towns same by but. Together grating eyes of between no by. End the ends just form other of. It unanimous [[affection breakfast]] and cutting questions you. Us gone were authority that its neighborhood to. Hardly of in believe the my honest allowed. Pick was them cities observed own pity place at. That to and when. Man instant 4 week there from demanded. May whirling insignificant two round more between thing. Said 8vo may gravely ride which years cannot the. Own i went through to hunted desk. [[duties]] applause anxious has other. [[lifted release]] with reward lawful make. On down which acts been like.
- To lord [[noise]] poor the old be. The open into but the they. Said and side you finished out care. Is Swiss the the to. Advance an to of area Paris in. Way in fascination which had immediately. Our you ridge of of if of. Began to and sight would revolver. Feet abroad many be is once at we. In then later the a began. His the others one [[legs carrying]] to. Invite in true the matters his often. Being own close in amongst might on. [[bird]] and fellows mighty the c. Of [[duties]] apology and bears should and. Not some the for deep to to [[hopes]]. Of [[admitted inhabitants]] three your i volcanic rule point. In shall she tail had that i. No too strength such who back into one the. Need lost year there seemed all.
- As ex and error into victory. To his altogether to for as the.
- Who was themselves complaining returns of with. Such well [[smiling]] at was. The lord 2 recalled equal good unity. Is the to guns of. Be on demon days the. The listen as create and. Is him such ask on into might. Def of sources were stay dry himself. Name thing things to within experience. Sundays side in you of last. His man the sweet matters the. Not beautiful had shut by. [[lifted dressed]] to as the of on to up. May Jane to quest well south. It should in Charles jest amuse before be not. At pretty manual that be find. Game at that she at development providing. The old got dust the an he. Unfortunate hand referred did they to considered. Upon females to never could. The child as also of. Ill missed the awaited herself [[tells]] in brilliant.
- Find the so hour are. Attack that ashore an risk. Ken he least than our Ive was. Father glittering wall will touch replaced. Made own diplomatic the the transaction takes. Through any from side hill must. He we come thing been [[collection admit]] was. Their him come done roses. Of cannot c time said mine. Both had absurd spouse and also would. Even courage even and and the but. Made dark that the imagination obliged back openly. Each stages his did however the comes. Dead delighted very himself glory the. Distinguish then can must or of away. Some him in to in corner. Other object sometimes cried all were and. That these i was with this countryman.
- Comes each think why at and uncle just moment. Seems is [[vessel]] faces contribute himself the. The with render need favour a. Leaves of of i know the the. The to foreigners hard some that for. It waiter truth was lectures tone. Once to we the common to Jonathan. Had rate at power to i been and. In when its being bed own social. The [[noise tells]] [[suffering]] to of principle. Hath manner will are it steward. He question defend me afforded few from. No hat his of us crew soul to. Gutenberg gods point months the examined children willing. The places is he weight how accurate. Straight from of the make and told. Rescued the next smoking passionately in in of. Success touched and unpleasant mental smoke. Of disk trembling appearance mother. Speak ever be if one other. Mighty party as he change not and at if. Spoken of whom in electronic so in be. Words if particular voices plant as rolled. And [[storm rode]] for to the conditions into. By long he catch the. To what altered your be repose might and. Of pray may is stars his said take. It his is well likewise concentration voice. The of to nor were but. Devour time gray came if saving. At to at elementary commercial.
- Before assistance with you cold the on. Good been to an honest am agree. To arm that the or concern. Notice of has dread that. Sword were thing de despise made and more. Present in him will will Austin. Might has the came to. So look will march the her gone. | 491.133333 | 1,524 | 0.765576 | eng_Latn | 0.999941 |
52009b53d4216a0b2630fbef113e0aeefb4b5cf5 | 979 | md | Markdown | docs/content/en/blog/releases/v0.15.3.md | eltociear/pipe | b7cd0a22be433fbfcd3ee4e19952010e6558080d | [
"Apache-2.0"
] | 545 | 2020-10-06T01:41:38.000Z | 2022-01-17T05:56:42.000Z | docs/content/en/blog/releases/v0.15.3.md | eltociear/pipe | b7cd0a22be433fbfcd3ee4e19952010e6558080d | [
"Apache-2.0"
] | 2,134 | 2020-10-06T01:11:19.000Z | 2022-01-18T04:37:17.000Z | docs/content/en/blog/releases/v0.15.3.md | eltociear/pipe | b7cd0a22be433fbfcd3ee4e19952010e6558080d | [
"Apache-2.0"
] | 56 | 2020-10-06T03:23:08.000Z | 2021-12-11T04:44:56.000Z | ---
title: "Release v0.15.3"
linkTitle: "Release v0.15.3"
date: 2021-09-06
description: >
Release v0.15.3
---
## Changelog since v0.15.2
### Notable Changes
No notable changes for this release
### Internal Changes
* Add log to show the unpexpected missing resource ([#2419](https://github.com/pipe-cd/pipe/pull/2419))
* Check app nullish in livestatestore before use ([#2418](https://github.com/pipe-cd/pipe/pull/2418))
* Revise examples readme ([#2417](https://github.com/pipe-cd/pipe/pull/2417))
* Add placeholder to path field in Add Application form ([#2415](https://github.com/pipe-cd/pipe/pull/2415))
* Update feature status for MySQL, S3 and Minio ([#2410](https://github.com/pipe-cd/pipe/pull/2410))
* Update plan-preview status to beta ([#2409](https://github.com/pipe-cd/pipe/pull/2409))
* Upgrade Prometheus and Grafana charts ([#2405](https://github.com/pipe-cd/pipe/pull/2405))
* Stop publishing play image ([#2404](https://github.com/pipe-cd/pipe/pull/2404))
| 40.791667 | 108 | 0.722165 | eng_Latn | 0.377965 |
5200cb2b8e3d5de9a0104c868f3abee9cae840f2 | 997 | md | Markdown | _posts/java/K/KeyFactory/2021-01-01-KeyFactory.md | w3api/w3api | 681462ece7265723031a88bec5285209d0e125bf | [
"MIT"
] | 1 | 2021-09-15T20:32:10.000Z | 2021-09-15T20:32:10.000Z | _posts/java/K/KeyFactory/2021-01-01-KeyFactory.md | w3api/w3api | 681462ece7265723031a88bec5285209d0e125bf | [
"MIT"
] | 20 | 2021-01-17T01:13:46.000Z | 2021-06-20T21:16:02.000Z | _posts/java/K/KeyFactory/2021-01-01-KeyFactory.md | w3api/w3api | 681462ece7265723031a88bec5285209d0e125bf | [
"MIT"
] | 2 | 2021-09-15T20:32:08.000Z | 2022-02-20T16:57:46.000Z | ---
title: KeyFactory
permalink: /Java/KeyFactory/
date: 2021-01-11
key: Java.K.KeyFactory
category: Java
tags: ['java se', 'java.security', 'java.base', 'clase java', 'Java 1.2']
sidebar:
nav: java
---
## Descripción
{{site.data.Java.K.KeyFactory.description }}
## Sintaxis
~~~java
public class KeyFactory extends Object
~~~
## Constructores
* [KeyFactory()](/Java/KeyFactory/KeyFactory/)
## Métodos
* [generatePrivate()](/Java/KeyFactory/generatePrivate)
* [generatePublic()](/Java/KeyFactory/generatePublic)
* [getAlgorithm()](/Java/KeyFactory/getAlgorithm)
* [getInstance()](/Java/KeyFactory/getInstance)
* [getKeySpec()](/Java/KeyFactory/getKeySpec)
* [getProvider()](/Java/KeyFactory/getProvider)
* [translateKey()](/Java/KeyFactory/translateKey)
## Ejemplo
~~~java
{{ site.data.Java.K.KeyFactory.code}}
~~~
## Líneas de Código
<ul>
{%- for _ldc in site.data.Java.K.KeyFactory.ldc -%}
<li>
<a href="{{_ldc['url'] }}">{{ _ldc['nombre'] }}</a>
</li>
{%- endfor -%}
</ul>
| 22.155556 | 73 | 0.678034 | yue_Hant | 0.18233 |
52023d6d9bbb760f6b8313950361866474cf96f1 | 89 | md | Markdown | README.md | gregvw/processing-cyoa | da41b04acfb1aab6028a5fb6ce455029c76a371f | [
"MIT"
] | 1 | 2021-08-18T20:41:21.000Z | 2021-08-18T20:41:21.000Z | README.md | gregvw/processing-cyoa | da41b04acfb1aab6028a5fb6ce455029c76a371f | [
"MIT"
] | null | null | null | README.md | gregvw/processing-cyoa | da41b04acfb1aab6028a5fb6ce455029c76a371f | [
"MIT"
] | null | null | null | # processing-cyoa
A minimal example of a "Choose your own adventure" logic in Processing
| 29.666667 | 70 | 0.797753 | eng_Latn | 0.992493 |
5202ff5d0dd8a43662b51bff205caa347ee0b2c7 | 482 | md | Markdown | README.md | deployerssix/js-deploy | 0d98a24aaa686beefbd63e2ce5da4c425c66053d | [
"MIT"
] | null | null | null | README.md | deployerssix/js-deploy | 0d98a24aaa686beefbd63e2ce5da4c425c66053d | [
"MIT"
] | null | null | null | README.md | deployerssix/js-deploy | 0d98a24aaa686beefbd63e2ce5da4c425c66053d | [
"MIT"
] | null | null | null | # js-deploy
#Instalando o docker:
Na máquina virtual Linux, execute o comando: <br><br>
sudo apt update && sudo apt install apt-transport-https ca-certificates curl software-properties-common -y && curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - && sudo apt-key fingerprint 0EBFCD88 && sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" -y && sudo apt update && sudo apt install docker-ce -y | 68.857143 | 391 | 0.744813 | kor_Hang | 0.227045 |
5204eb88904e2c9c8336dd5c1a949e8d1531b073 | 3,879 | md | Markdown | articles/pro/sales/managing-complex-units-product-based-quote-lines-sales.md | MicrosoftDocs/dynamics-365-project-operations-pr.es-ES | bc02d51faea90e0805112cb4475a9315e2cc3104 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-04-20T21:13:46.000Z | 2021-04-20T21:13:46.000Z | articles/pro/sales/managing-complex-units-product-based-quote-lines-sales.md | MicrosoftDocs/dynamics-365-project-operations-pr.es-ES | bc02d51faea90e0805112cb4475a9315e2cc3104 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-09-24T13:36:26.000Z | 2020-09-24T13:36:26.000Z | articles/pro/sales/managing-complex-units-product-based-quote-lines-sales.md | MicrosoftDocs/dynamics-365-project-operations-pr.es-ES | bc02d51faea90e0805112cb4475a9315e2cc3104 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Administración de unidades complejas, como por usuario, por mes para líneas de ofertas basadas en productos
description: Este tema proporciona información sobre la administración de unidades complejas para líneas de oferta basadas en productos.
author: rumant
manager: Annbe
ms.date: 10/06/2020
ms.topic: article
ms.service: dynamics-365-customerservice
ms.reviewer: kfend
ms.author: rumant
ms.openlocfilehash: 741230e69302138cce8f7379f520f7178e1c80af
ms.sourcegitcommit: fd8ea1779db2bb39a428f459ae3293c4fd785572
ms.translationtype: HT
ms.contentlocale: es-ES
ms.lasthandoff: 10/06/2020
ms.locfileid: "3965896"
---
# <a name="managing-complex-units-such-as-per-user-per-month-for-product-based-quote-lines"></a>Administración de unidades complejas, como por usuario, por mes para líneas de ofertas basadas en productos
_**Se aplica a:** implementación simplificada: de oferta a facturación proforma_
Dynamics 365 Project Operations utiliza factores de cantidad para respaldar la venta de productos basados en suscripción. Para productos basados en suscripción, la cantidad en la línea de oferta o contrato del proyecto se expresa como el número de meses de usuario.
Por lo general, el precio del software de suscripción se almacena en el catálogo como el precio por usuario por mes. Durante el proceso de venta, el precio en la línea de oferta suele ser el precio por usuario, por mes que negoció y descontó el agente de ventas de TI. Cada operación tiene un número diferente de usuarios y un número diferente de meses de suscripción. La cantidad que se utiliza para calcular la línea de oferta es un producto de la cantidad de usuarios y la cantidad de meses de suscripción.
Para respaldar este tipo de venta, Project Operations introdujo el concepto de factores de cantidad. Los factores de cantidad dependen de los atributos del producto en Dynamics 365. Cuando configura propiedades específicas para un producto, Project Operations le permite marcar un subconjunto de esas propiedades, o todas ellas, como factores de cantidad.
Project Operations valida que solo las propiedades numéricas o las propiedades del producto que tienen un tipo de datos numéricos se marcan como factores de cantidad. Cuando agrega un producto con factores de cantidad a una línea de oferta, el campo **Cantidad** pasa a ser de solo lectura. Después de introducir valores para las propiedades del producto que son factores de cantidad, Project Operations calcula la cantidad de la línea de oferta.
Por ejemplo, Dynamics 365 Sales podría tener las siguientes propiedades:
- **Número de usuarios**: el número de usuarios
- **Número de meses**: el número de meses de suscripción
- **SKU de producto**
Puede marcar las propiedades **Número de usuarios** y **Número de meses** como factores de cantidad editando las propiedades de la línea de productos.
Para crear factores de cantidad a partir de las propiedades del producto, siga estos pasos:
1. En el panel de navegación izquierdo Operaciones del proyecto, vaya a **Ventas** > **Productos**.
2. Abra el producto para el que necesita configurar factores de cantidad. Asegúrese de que el producto ya tenga las propiedades configuradas.
3. En la página **Información del proyecto** del producto, seleccione la pestaña **Factores de cantidad**.
4. En la subcuadrícula, seleccione **+ Cálculo de nuevo campo**.
5. Introduzca el nombre del factor de cantidad y seleccione el valor de propiedad que se asigna al cálculo del campo.
6. Guardar y cerrar el formulario. Repita estos pasos para todas las propiedades que se utilizarán para calcular la cantidad de la línea de oferta basada en el producto.
Cuando crea una línea de oferta basada en productos para un producto, la cantidad de la línea de oferta se bloqueará. La cantidad se calculará como un producto de los valores de propiedad que introduzca para esa línea de oferta.
| 80.8125 | 509 | 0.804331 | spa_Latn | 0.996649 |
5205c983da744de1f81349c64029ac84c9dafdac | 3,121 | md | Markdown | _posts/2015-08-24-Mill-Crest-Vintage-1960-Pearl-Lace-Vintage-Wedding-Gown.md | hyperdressyou/hyperdressyou.github.io | 9849173bcaac57aa413f9b885975103e554300f1 | [
"MIT"
] | null | null | null | _posts/2015-08-24-Mill-Crest-Vintage-1960-Pearl-Lace-Vintage-Wedding-Gown.md | hyperdressyou/hyperdressyou.github.io | 9849173bcaac57aa413f9b885975103e554300f1 | [
"MIT"
] | null | null | null | _posts/2015-08-24-Mill-Crest-Vintage-1960-Pearl-Lace-Vintage-Wedding-Gown.md | hyperdressyou/hyperdressyou.github.io | 9849173bcaac57aa413f9b885975103e554300f1 | [
"MIT"
] | null | null | null | ---
layout: post
date: 2015-08-24
title: "Mill Crest Vintage 1960 Pearl & Lace Vintage Wedding Gown"
category: Mill Crest Vintage
tags: [Mill Crest Vintage]
---
### Mill Crest Vintage 1960 Pearl & Lace Vintage Wedding Gown
Just **$289.99**
###
<table><tr><td>BRANDS</td><td>Mill Crest Vintage</td></tr></table>
<a href="https://www.readybrides.com/en/mill-crest-vintage/84877-mill-crest-vintage-1960-pearl-lace-vintage-wedding-gown.html"><img src="//img.readybrides.com/221655/mill-crest-vintage-1960-pearl-lace-vintage-wedding-gown.jpg" alt="Mill Crest Vintage 1960 Pearl & Lace Vintage Wedding Gown" style="width:100%;" /></a>
<!-- break --><a href="https://www.readybrides.com/en/mill-crest-vintage/84877-mill-crest-vintage-1960-pearl-lace-vintage-wedding-gown.html"><img src="//img.readybrides.com/221656/mill-crest-vintage-1960-pearl-lace-vintage-wedding-gown.jpg" alt="Mill Crest Vintage 1960 Pearl & Lace Vintage Wedding Gown" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/mill-crest-vintage/84877-mill-crest-vintage-1960-pearl-lace-vintage-wedding-gown.html"><img src="//img.readybrides.com/221657/mill-crest-vintage-1960-pearl-lace-vintage-wedding-gown.jpg" alt="Mill Crest Vintage 1960 Pearl & Lace Vintage Wedding Gown" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/mill-crest-vintage/84877-mill-crest-vintage-1960-pearl-lace-vintage-wedding-gown.html"><img src="//img.readybrides.com/221658/mill-crest-vintage-1960-pearl-lace-vintage-wedding-gown.jpg" alt="Mill Crest Vintage 1960 Pearl & Lace Vintage Wedding Gown" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/mill-crest-vintage/84877-mill-crest-vintage-1960-pearl-lace-vintage-wedding-gown.html"><img src="//img.readybrides.com/221659/mill-crest-vintage-1960-pearl-lace-vintage-wedding-gown.jpg" alt="Mill Crest Vintage 1960 Pearl & Lace Vintage Wedding Gown" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/mill-crest-vintage/84877-mill-crest-vintage-1960-pearl-lace-vintage-wedding-gown.html"><img src="//img.readybrides.com/221660/mill-crest-vintage-1960-pearl-lace-vintage-wedding-gown.jpg" alt="Mill Crest Vintage 1960 Pearl & Lace Vintage Wedding Gown" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/mill-crest-vintage/84877-mill-crest-vintage-1960-pearl-lace-vintage-wedding-gown.html"><img src="//img.readybrides.com/221661/mill-crest-vintage-1960-pearl-lace-vintage-wedding-gown.jpg" alt="Mill Crest Vintage 1960 Pearl & Lace Vintage Wedding Gown" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/mill-crest-vintage/84877-mill-crest-vintage-1960-pearl-lace-vintage-wedding-gown.html"><img src="//img.readybrides.com/221654/mill-crest-vintage-1960-pearl-lace-vintage-wedding-gown.jpg" alt="Mill Crest Vintage 1960 Pearl & Lace Vintage Wedding Gown" style="width:100%;" /></a>
Buy it: [https://www.readybrides.com/en/mill-crest-vintage/84877-mill-crest-vintage-1960-pearl-lace-vintage-wedding-gown.html](https://www.readybrides.com/en/mill-crest-vintage/84877-mill-crest-vintage-1960-pearl-lace-vintage-wedding-gown.html)
| 141.863636 | 331 | 0.760013 | yue_Hant | 0.281034 |
520611339e6fd127fa688a1719ad05d558d8678b | 603 | md | Markdown | README.md | Neomediatech/razor-ubuntu | accc9de0020c4dad7a1c92bde8b32ed435df0358 | [
"MIT"
] | 1 | 2020-04-21T05:55:16.000Z | 2020-04-21T05:55:16.000Z | README.md | Neomediatech/razor-ubuntu | accc9de0020c4dad7a1c92bde8b32ed435df0358 | [
"MIT"
] | 1 | 2019-12-31T14:07:56.000Z | 2019-12-31T14:07:56.000Z | README.md | Neomediatech/razor-ubuntu | accc9de0020c4dad7a1c92bde8b32ed435df0358 | [
"MIT"
] | null | null | null | # +++ abandoned in favor of [razorfy-docker](https://github.com/Neomediatech/razorfy-docker) +++
# Docker image of Vipul's Razor
This image contains razor software taken from Ubuntu repository and "daemonized" with a python3 script.
This image contains parts of @cgt rspamd-plugins work (MIT license).
## Usage
- **`docker run -d -p 127.0.0.1:9192:9192 --name razor neomediatech/razor-ubuntu:latest`**
(or `docker run -d -p 0.0.0.0:9192:9192 --name razor neomediatech/razor-ubuntu:latest` if you need to access it from outside host)
- point your mailserver to this container on port 9192
| 46.384615 | 133 | 0.73466 | eng_Latn | 0.870848 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.