@fmsim/fmsim-restful 0.0.97 → 0.0.98

package/dist-app/helps/board-modeller/styles/line-style.zh.md

@@ -1,19 +0,0 @@
-# 线型
-
-  - 厚度：设置线的厚度。
-  - 颜色：设置线的颜色。
-  - 线的样式：设置线的样式。（直线、虚线等）
-  - 线端的样式：设置线端的样式。（square：方形线端，round：圆形线端）
-  - 连接样式：设置线与线相连接的点的样式。  
-    (锐角相交 : ![miter][miter], 弧形 : ![round][round], 斜角相交 : ![bevel][bevel])
-  - 开始形状：设置线的开始形状。
-  - 开始大小：设置线的开始大小。
-  - 结束形状：设置线的结束形状。
-  - 结束大小：设置线的结束大小。
-
-
-[miter]: ../images/join-type-miter.png
-
-[round]: ../images/join-type-round.png
-
-[bevel]: ../images/join-type-bevel.png

package/dist-app/helps/board-modeller/styles/opacity.ko.md

@@ -1,3 +0,0 @@
-# 투명도
-
-컴포넌트의 투명한 정도를 설정한다. (0 ~ 1, 0 : 안보임, 1 : 보임)

package/dist-app/helps/board-modeller/styles/opacity.md

@@ -1,3 +0,0 @@
-# Opacity
-
-- Set the transparency of component. (0 ~ 1, 0: Invisible, 1: Visible)

package/dist-app/helps/board-modeller/styles/opacity.zh.md

@@ -1,3 +0,0 @@
-# 透明度
-
-设置组件的透明度。（0~1, 0: 透明, 1: 不透明）

package/dist-app/helps/board-modeller/styles/text-style.ko.md

@@ -1,8 +0,0 @@
-# 텍스트 스타일
-
-  - 폰트 : 컴포넌트 텍스트의 폰트를 설정한다.  
-  - 크기 : 컴포넌트 텍스트의 크기를 설정한다.  
-  - 줄간격 : 컴포넌트 텍스트의 줄사이 간격을 설정한다.  
-  - 색상 : 컴포넌트 텍스트의 색상을 설정한다.
-  - 굵기 : 컴포넌트 텍스트를 굵게 설정한다.
-  - 기울기 : 컴포넌트 텍스트를 기울임꼴로 설정한다.

package/dist-app/helps/board-modeller/styles/text-style.md

@@ -1,8 +0,0 @@
-# Text Style
-
-  - Font: Set the font of component text.
-  - Font size: Set the size of component text.
-  - Line spacing: Set the line spacing of component text.
-  - Color: Set the color of component text.
-  - Bold: Set the text of component bold.
-  - Italic: Set the text of component italic.

package/dist-app/helps/board-modeller/styles/text-style.zh.md

@@ -1,8 +0,0 @@
-# 文本样式
-
-  - 字体：设置组件文本的字体。
-  - 字体大小：设置组件文本的大小。
-  - 行间隔：设置组件文本的行间隔。
-  - 颜色：设置组件文本的颜色。
-  - 粗体：加粗组件文本。
-  - 斜体：加斜组件文本。

package/dist-app/helps/board-service/board-template.md

@@ -1,160 +0,0 @@
-# BoardTemplate
-
-Paragraphs are separated by a blank line.
-
-2nd paragraph. _Italic_, **bold**, and `monospace`. Itemized lists
-look like:
-
-- this one
-- that one
-- the other one
-
-Note that --- not considering the asterisk --- the actual text
-content starts at 4-columns in.
-
-> Block quotes are
-> written like so.
->
-> They can span multiple paragraphs,
-> if you like.
-
-Use 3 dashes for an em-dash. Use 2 dashes for ranges (ex., "it's all
-in chapters 12--14"). Three dots ... will be converted to an ellipsis.
-Unicode is supported. ☺
-
-## An h2 header
-
-Here's a numbered list:
-
-1. first item
-2. second item
-3. third item
-
-Note again how the actual text starts at 4 columns in (4 characters
-from the left side). Here's a code sample:
-
-# Let me re-iterate ...
-
-for i in 1 .. 10 { do-something(i) }
-
-As you probably guessed, indented 4 spaces. By the way, instead of
-indenting the block, you can use delimited blocks, if you like:
-
-```
-define foobar() {
-print "Welcome to flavor country!";
-}
-```
-
-(which makes copying & pasting easier). You can optionally mark the
-delimited block for Pandoc to syntax highlight it:
-
-```python
-import time
-# Quick, count to ten!
-for i in range(10):
-# (but not *too* quick)
-time.sleep(0.5)
-print(i)
-```
-
-### An h3 header
-
-Now a nested list:
-
-1. First, get these ingredients:
-
-- carrots
-- celery
-- lentils
-
-2. Boil some water.
-
-3. Dump everything in the pot and follow
-   this algorithm:
-
-find wooden spoon
-uncover pot
-stir
-cover pot
-balance wooden spoon precariously on pot handle
-wait 10 minutes
-goto first step (or shut off burner when done)
-
-Do not bump wooden spoon or it will fall.
-
-Notice again how text always lines up on 4-space indents (including
-that last line which continues item 3 above).
-
-Here's a link to [a website](http://foo.bar), to a [local
-doc](local-doc.html), and to a [section heading in the current
-doc](#an-h2-header). Here's a footnote [^1].
-
-[^1]: Some footnote text.
-
-Tables can look like this:
-
-Name Size Material Color
-
----
-
-All Business 9 leather brown
-Roundabout 10 hemp canvas natural
-Cinderella 11 glass transparent
-
-Table: Shoes sizes, materials, and colors.
-
-(The above is the caption for the table.) Pandoc also supports
-multi-line tables:
-
----
-
-Keyword Text
-
----
-
-red Sunsets, apples, and
-other red or reddish
-things.
-
-green Leaves, grass, frogs
-and other things it's
-not easy being.
-
----
-
-A horizontal rule follows.
-
----
-
-Here's a definition list:
-
-apples
-: Good for making applesauce.
-
-oranges
-: Citrus!
-
-tomatoes
-: There's no "e" in tomatoe.
-
-Again, text is indented 4 spaces. (Put a blank line between each
-term and its definition to spread things out more.)
-
-Here's a "line block" (note how whitespace is honored):
-
-| Line one
-| Line too
-| Line tree
-
-and images can be specified like so:
-
-![example image](example-image.jpg 'An exemplary image')
-
-Inline math equation: $\omega = d\phi / dt$. Display
-math should get its own line like so:
-
-$$I = \int \rho R^{2} dV$$
-
-And note that you can backslash-escape any punctuation characters
-which you wish to be displayed literally, ex.: \`foo\`, \*bar\*, etc.

package/dist-app/helps/codelingua/codelingua.md

@@ -1,160 +0,0 @@
-# Codelingua
-
-Paragraphs are separated by a blank line.
-
-2nd paragraph. _Italic_, **bold**, and `monospace`. Itemized lists
-look like:
-
-- this one
-- that one
-- the other one
-
-Note that --- not considering the asterisk --- the actual text
-content starts at 4-columns in.
-
-> Block quotes are
-> written like so.
->
-> They can span multiple paragraphs,
-> if you like.
-
-Use 3 dashes for an em-dash. Use 2 dashes for ranges (ex., "it's all
-in chapters 12--14"). Three dots ... will be converted to an ellipsis.
-Unicode is supported. ☺
-
-## An h2 header
-
-Here's a numbered list:
-
-1. first item
-2. second item
-3. third item
-
-Note again how the actual text starts at 4 columns in (4 characters
-from the left side). Here's a code sample:
-
-# Let me re-iterate ...
-
-for i in 1 .. 10 { do-something(i) }
-
-As you probably guessed, indented 4 spaces. By the way, instead of
-indenting the block, you can use delimited blocks, if you like:
-
-```
-define foobar() {
-print "Welcome to flavor country!";
-}
-```
-
-(which makes copying & pasting easier). You can optionally mark the
-delimited block for Pandoc to syntax highlight it:
-
-```python
-import time
-# Quick, count to ten!
-for i in range(10):
-# (but not *too* quick)
-time.sleep(0.5)
-print(i)
-```
-
-### An h3 header
-
-Now a nested list:
-
-1. First, get these ingredients:
-
-- carrots
-- celery
-- lentils
-
-2. Boil some water.
-
-3. Dump everything in the pot and follow
-   this algorithm:
-
-find wooden spoon
-uncover pot
-stir
-cover pot
-balance wooden spoon precariously on pot handle
-wait 10 minutes
-goto first step (or shut off burner when done)
-
-Do not bump wooden spoon or it will fall.
-
-Notice again how text always lines up on 4-space indents (including
-that last line which continues item 3 above).
-
-Here's a link to [a website](http://foo.bar), to a [local
-doc](local-doc.html), and to a [section heading in the current
-doc](#an-h2-header). Here's a footnote [^1].
-
-[^1]: Some footnote text.
-
-Tables can look like this:
-
-Name Size Material Color
-
----
-
-All Business 9 leather brown
-Roundabout 10 hemp canvas natural
-Cinderella 11 glass transparent
-
-Table: Shoes sizes, materials, and colors.
-
-(The above is the caption for the table.) Pandoc also supports
-multi-line tables:
-
----
-
-Keyword Text
-
----
-
-red Sunsets, apples, and
-other red or reddish
-things.
-
-green Leaves, grass, frogs
-and other things it's
-not easy being.
-
----
-
-A horizontal rule follows.
-
----
-
-Here's a definition list:
-
-apples
-: Good for making applesauce.
-
-oranges
-: Citrus!
-
-tomatoes
-: There's no "e" in tomatoe.
-
-Again, text is indented 4 spaces. (Put a blank line between each
-term and its definition to spread things out more.)
-
-Here's a "line block" (note how whitespace is honored):
-
-| Line one
-| Line too
-| Line tree
-
-and images can be specified like so:
-
-![example image](example-image.jpg 'An exemplary image')
-
-Inline math equation: $\omega = d\phi / dt$. Display
-math should get its own line like so:
-
-$$I = \int \rho R^{2} dV$$
-
-And note that you can backslash-escape any punctuation characters
-which you wish to be displayed literally, ex.: \`foo\`, \*bar\*, etc.

package/dist-app/helps/components/oops-progress.md

@@ -1,73 +0,0 @@
-# OOPS Progress 컴포넌트
-
-긴 시간 진행되는 작업의 진행 상황을 표현해주기 위해 서버에 진행율을 Subscribe하는 클라이언트 컴포넌트이다.
-이 컴포넌트는 자체적으로 시각적 요소를 포함하지 않지만, 시각적 표현을 위해서 자식 노드(Light DOM)를 포함할 수는 있다.
-
-## properties
-
-- tag: String 서브스크립션 태그이며, 서버의 'publishProgress'의 tag와 일치시키도록 한다.
-- subscription: String (readonly) 이 속성이 값을 가지고 있으면, 서브스크립션 중임을 의미한다.
-
-## methods
-
-- startSubscribe() 진행율 구독을 시작한다.
-- stopSubscribe() 진행율 구독을 종료한다.(서버쪽 작업의 종료를 의미하지 않으며, 클라이언트에서 구독을 종료한다는 의미임.)
-
-## event
-
-- progress(event) 서버로부터 진행율이 Subscribe 되었을 때 발생한다.
-  - event.detail : progress 값을 갖는다.
-- finish(event) 진행율이 100% 도달하면 발생한다.
-
-## 예시
-
-### 클라이언트 사이드
-
-```
-  <oops-progress
-    .tag='progress-pending-job'
-    @progress=${e => {
-      this.progress = e.detail
-    }}
-    @finish=${() => {
-      console.log('complete')
-    }}
-    ?hidden=${progress < 0 || progress > 100}
-  >
-    <div>
-      <mwc-linear-progress .progress=${progress / 100}></mwc-linear-progress>
-      <span>Progress : ${progress} % (${message})</span>
-    </div>
-  </oops-progress>
-
-```
-
-### 서버사이드
-
-```
-import { sleep } from '@things-factory/utils'
-
-...
-
-@Mutation(returns => String, { description: 'To reference of pending job progress' })
-async referencePendingJob(
-  @Root() _,
-  @Ctx() context: any
-) : Promise<string> {
-
-  const { domain } = context.state
-
-  for(var i = 0;i <= 100;i++) {
-    await sleep(100)
-
-    publishProgress({
-      domain,
-      tag: 'progress-pending-job',
-      progress: i,
-      message: `${i * 10} / 1000`
-    })
-  }
-
-  return 'success'
-}
-```

package/dist-app/helps/contact/contact.md

@@ -1,160 +0,0 @@
-# Contact
-
-Paragraphs are separated by a blank line.
-
-2nd paragraph. _Italic_, **bold**, and `monospace`. Itemized lists
-look like:
-
-- this one
-- that one
-- the other one
-
-Note that --- not considering the asterisk --- the actual text
-content starts at 4-columns in.
-
-> Block quotes are
-> written like so.
->
-> They can span multiple paragraphs,
-> if you like.
-
-Use 3 dashes for an em-dash. Use 2 dashes for ranges (ex., "it's all
-in chapters 12--14"). Three dots ... will be converted to an ellipsis.
-Unicode is supported. ☺
-
-## An h2 header
-
-Here's a numbered list:
-
-1. first item
-2. second item
-3. third item
-
-Note again how the actual text starts at 4 columns in (4 characters
-from the left side). Here's a code sample:
-
-# Let me re-iterate ...
-
-for i in 1 .. 10 { do-something(i) }
-
-As you probably guessed, indented 4 spaces. By the way, instead of
-indenting the block, you can use delimited blocks, if you like:
-
-```
-define foobar() {
-print "Welcome to flavor country!";
-}
-```
-
-(which makes copying & pasting easier). You can optionally mark the
-delimited block for Pandoc to syntax highlight it:
-
-```python
-import time
-# Quick, count to ten!
-for i in range(10):
-# (but not *too* quick)
-time.sleep(0.5)
-print(i)
-```
-
-### An h3 header
-
-Now a nested list:
-
-1. First, get these ingredients:
-
-- carrots
-- celery
-- lentils
-
-2. Boil some water.
-
-3. Dump everything in the pot and follow
-   this algorithm:
-
-find wooden spoon
-uncover pot
-stir
-cover pot
-balance wooden spoon precariously on pot handle
-wait 10 minutes
-goto first step (or shut off burner when done)
-
-Do not bump wooden spoon or it will fall.
-
-Notice again how text always lines up on 4-space indents (including
-that last line which continues item 3 above).
-
-Here's a link to [a website](http://foo.bar), to a [local
-doc](local-doc.html), and to a [section heading in the current
-doc](#an-h2-header). Here's a footnote [^1].
-
-[^1]: Some footnote text.
-
-Tables can look like this:
-
-Name Size Material Color
-
----
-
-All Business 9 leather brown
-Roundabout 10 hemp canvas natural
-Cinderella 11 glass transparent
-
-Table: Shoes sizes, materials, and colors.
-
-(The above is the caption for the table.) Pandoc also supports
-multi-line tables:
-
----
-
-Keyword Text
-
----
-
-red Sunsets, apples, and
-other red or reddish
-things.
-
-green Leaves, grass, frogs
-and other things it's
-not easy being.
-
----
-
-A horizontal rule follows.
-
----
-
-Here's a definition list:
-
-apples
-: Good for making applesauce.
-
-oranges
-: Citrus!
-
-tomatoes
-: There's no "e" in tomatoe.
-
-Again, text is indented 4 spaces. (Put a blank line between each
-term and its definition to spread things out more.)
-
-Here's a "line block" (note how whitespace is honored):
-
-| Line one
-| Line too
-| Line tree
-
-and images can be specified like so:
-
-![example image](example-image.jpg 'An exemplary image')
-
-Inline math equation: $\omega = d\phi / dt$. Display
-math should get its own line like so:
-
-$$I = \int \rho R^{2} dV$$
-
-And note that you can backslash-escape any punctuation characters
-which you wish to be displayed literally, ex.: \`foo\`, \*bar\*, etc.

package/dist-app/helps/integration/concept/connection.md

@@ -1,27 +0,0 @@
-# Connection
-
-외부 시스템을 연결하기 위해 제공되는 기능을 Connector라고 하며, Connector를 작동시키기 위한 설정 정보가 Connection 이다.
-한 종류의 Connector는 여러 Connection을 가질 수 있다.
-
-외부 시스템을 연결하기 위해서는 외부 시스템에 연결하기 위한 연결 정보와 프로토콜을 정의해야 하며,
-커넥션은 외부 시스템 연결 정보를 의미한다.
-
-외부 시스템은 대표적으로 데이타베이스, 메시지 브로커 등의 서비스를 제공하는 네트워크 기반의 시스템이 될 수도 있고,
-때로는 카메라, 프린터, 스캐너 같은 디바이스를 직접 연결하는 USB 포트 등이 될 수 있다.
-그 밖에 가상의 오브젝트가 될 수도 있다.
-
-시나리오는 태스크의 시리즈로 정의된다. 일부 태스크는 커넥션에 기반한 태스크들이 될 수 있다.
-예를 들면, 데이타베이스 커넥션에 기반한 태스크로는 데이타베이스 쿼리가 될 수 있으며,
-메시지 브로커를 기반한 태스크로는 메시지 서브스크라이브나 메시지 퍼블리시 같은 태스크들이 있을 수 있다.
-
-## endpoint
-
-- 외부 시스템의 연결 정보를 설정한다.
-- 네트워크 기반 커넥션의 엔드포인트는 보통 protocol과 host, service port 그리고 path 정보로 구성된다.
-- USB 디바이스에 대한 커넥션의 엔드포인트는 USB 포트번호가 될 수 있다.
-- 각 커넥터별 엔드포인트 설정 방법은 커넥터의 구현에 따른다. 커넥터의 도움말 기능을 통해서 엔드포인트 설정 방법을 가이드한다.
-
-## parameters
-
-- Connector를 동작시키기 위한 속성을 설정한다.
-- Connector 구현에 따라서 속성들은 정의된다.

package/dist-app/helps/integration/concept/data-accessor.ko.md

@@ -1,11 +0,0 @@
-# 데이터 접근자(data accessor)
-
-- 태스크의 속성으로 [시나리오 컨텍스트](./scenario-context.md) 내의 Data 중에서 필요한 value를 한정하고자 할 때 사용된다
-- 컨텍스트의 데이타는 각 스텝의 이름을 Key로 가지며, 스텝의 결과값을 Value로 유지하는 오브젝트이다.
-- 따라서 accessor는 항상 스텝의 이름으로 시작되며, 그 값 아래로도 더 한정하고 싶은 경우에는 자바스크립트 오브젝트의 Value를 지정하는 표현을 사용할 수 있다.
-- 또한, 데이터를 변환한 결과를 사용할 수도 있다.
-- 데이터 접근자(data accessor)를 설정하는 방법은 [JSONATA Document](http://docs.jsonata.org/overview)의 명세를 따른다.
-- 예시
-  - `stepname`
-  - `stepname.property`
-  - `stepname.property.property. ...`

package/dist-app/helps/integration/concept/data-accessor.md

@@ -1,11 +0,0 @@
-# data accessor
-
-- As a property of the task, it is used to limit the required value among the data in [scenario context](./scenario-context.md).
-- Context data is an object that has the name of each step as a Key and maintains the result value of the step as a Value.
-- Therefore, the accessor always starts with the name of the step, and if you want to further limit the value below that value, you can use an expression that specifies the value of the JavaScript object.
-- You can also use the result of data transformation.
-- How to set data accessor follows the specification of [JSONATA Document](http://docs.jsonata.org/overview).
-- example
-  - `stepname`
-  - `stepname.property`
-  - `stepname.property.property. ...`

package/dist-app/helps/integration/concept/data-accessor.zh.md

@@ -1,11 +0,0 @@
-# 数据访问器
-
-- 作为任务的一个属性，用于限制[scenario context](./scenario-context.md) 中数据中所需的值。
-- 上下文数据是将每个步骤的名称作为 Key，并将步骤的结果值作为 Value 来维护的对象。
-- 因此，访问器总是以步骤名称开头，如果您想进一步限制低于该值的值，您可以使用指定 JavaScript 对象值的表达式。
-- 您还可以使用数据转换的结果。
-- 如何设置数据访问器遵循 [JSONATA Document](http://docs.jsonata.org/overview) 的规范。
-- 例子
-  - `stepname`
-  - `stepname.property`
-  - `stepname.property.property。 ...`