DM Guide 11 - История изменений

Architect of fates: Откат правок ZLOFENIХ (обсуждение) к версии Michael Shepard

2016-12-12T21:56:45Z

Откат правок ZLOFENIХ (обсуждение) к версии Michael Shepard

Внесённые изменения

ZLOFENIХ: clean up, removed: ''Это 11 глава перевода оригинального руководства по Dream Maker от разработчиков.'' (442)

2016-12-12T21:09:18Z

clean up, removed: ''Это 11 глава перевода оригинального руководства по Dream Maker от разработчиков.'' (442)

Внесённые изменения

Michael Shepard: Откат правок Inaf (обсуждение) к версии IXVI

2016-01-28T17:45:34Z

Откат правок Inaf (обсуждение) к версии IXVI

Inaf: TODO:1. Решить, нужна ли эта страница на вики и выпилить, если не нужна. 2. Актуализировать информацию 3. Поправить стиль и грамматику 3.Добавит…

2016-01-28T14:25:04Z

TODO:1. Решить, нужна ли эта страница на вики и выпилить, если не нужна. 2. Актуализировать информацию 3. Поправить стиль и грамматику 3.Добавит…

Inaf: TODO:1. Решить, нужна ли эта страница на вики и выпилить, если не нужна. 2. Актуализировать информацию 3. Поправить стиль и грамматику 3.Добавит…

2016-01-28T14:18:26Z

IXVI: /* Инструкция ввода */

2015-11-14T20:36:25Z

Инструкция ввода

IXVI: /* Verbs */

2015-11-14T20:31:19Z

Verbs

IXVI: /* Глава 11 */

2015-11-14T20:30:10Z

Глава 11

MasterOfDmx: Новая страница: «''Это 11 глава перевода оригинального руководства по Dream Maker от разработчиков.'' [http://wiki.ss13.r…»

2015-10-26T20:45:24Z

Новая страница: «''Это 11 глава перевода оригинального руководства по Dream Maker от разработчиков.'' [http://wiki.ss13.r…»

Внесённые изменения

@@ Строка 1: / Строка 1: @@
 ''Это 11 глава перевода оригинального руководства по Dream Maker от разработчиков.''
@@ Строка 30: / Строка 26: @@
 <!--All user input seen so far has come at the initiative of the user. The player may type a command, press a direction key, click an object, etc. These forms of input are all similar because they are ultimately handled by verbs. In the case of the direction keys and mouse clicks, players don't need to actually type any command--the client does it all. However, from the programmer's point of view, these are all the same: The player calls a procedure and possibly passes some arguments to it.-->
-Есть несколько заранее определённых операторов(verbs), принимающих ввод информации от игрока. Это кнопки направления\стрелки (напр. client.North()), щелчок мыши (client.Click() и client.DblClick()) и ссылки топиков (client.Topic()). Все остальные операторы(verbs) задаются программистом.
+Есть несколько заранее определённых операторов(verbs), принимающих ввод информации от игрока. Это кнопки направления\стрелки (напр. client.North()), щелчок мыши ((client.Click() и client.DblClick()) и ссылки топиков (client.Topic()). Все остальные операторы(verbs) задаются программистом.
 <!--The only pre-defined verbs are associated with the client data object. They are the direction keys (e.g. client.North()), mouse clicks (client.Click() and client.DblClick()), and topic links (client.Topic()). All other verbs are defined by the programmer.-->
@@ Строка 138: / Строка 134: @@
 browse	(Doc, Options)
 Doc is the message to display.	Options are various window-specific options. Consult the reference for specifics.
-By default, each message replaces any previous message being displayed but the user can move back to previous messages stored in the client's memory. In many ways, the client terminal behaves like a telnet session and the browse window behaves like a web browser. One displays output sequentially in a continuous stream. The other displays it in discrete chunks—one document after another. The two are each useful in different situations.
+By default, each message replaces any previous message being displayed but the user can move back to previous messages stored in the client's memory. In many ways, the client terminal behaves like a telnet session and the browse window behaves like a web browser. One displays output sequentially in a continuous stream. The other displays it in discrete chunks--one document after another. The two are each useful in different situations.
 The document is often a text string. However, it may be a file instead. The type of file will determine how it is handled. Files may reside in the resource cache or in the file system. As always, cached items may be specified by putting the file name in single quotes. An external file, on the other hand, is indicated using the file instruction described in section 11.2.7.
@@ Строка 195: / Строка 191: @@
        usr.enemy_marker = image('outline.dmi',M)
        usr << usr.enemy_marker
-The code works by first deleting any old enemy marker. A new one is then made and displayed to the user. No one else will see the image—only the player who clicked on the enemy.
+The code works by first deleting any old enemy marker. A new one is then made and displayed to the user. No one else will see the image--only the player who clicked on the enemy.
@@ Строка 378: / Строка 374: @@
 "I am very mad!"
-The start tag ''' turns on bold lettering and ''' turns it off. For a complete list of tags understood by DM, see page 3 in the appendix. The most commonly used ones are listed in figure 11.19 for easy reference.
+The start tag <B> turns on bold lettering and </B> turns it off. For a complete list of tags understood by DM, see page 3 in the appendix. The most commonly used ones are listed in figure 11.19 for easy reference.
 Figure 11.19: Common text tags
@@ Строка 385: / Строка 381: @@
 anchor (for hyperlinks)
-''''''	bold
+<B></B>	bold
 <BIG></BIG>	bigger text
 <BR>	line break
 <FONT></FONT>	font face, size, and color
-''''	italic
+<I></I>	italic
+<P></P>	paragraph
 <S></S>	overstrike
 <SMALL></SMALL>	smaller text
@@ Строка 409: / Строка 401: @@
 Whitespace refers to any spaces, tabs, or newlines. In standard HTML, whitespace serves merely to delimit words. The amount of space and whether it is a tab, space, or newline is irrelevant.
-DM processes whitespace like standard HTML when it is inside of a pair of start and end tags. So, for example, inside of
+DM processes whitespace like standard HTML when it is inside of a pair of start and end tags. So, for example, inside of <P> and </P>, the paragraph markers, standard HTML rules are in effect; newlines, spaces, and tabs serve merely to delimit words. Note that an entire document could be surrounded by <HTML> and </HTML> to mark the whole thing as standard HTML.
 Outside of all HTML tags, DM handles whitespace a little differently. Spaces still delimit words, but newlines (embedded with \n) mark the end of lines. In other words, the newline is automatically converted to <BR>, the linebreak tag. That is convenient for use in messages composed by players when it would be annoying to write formal HTML with paragraph tags and so forth.
@@ Строка 494: / Строка 482: @@
 HTML tags, such as <FONT> may be used to directly format output text. Another approach, however, is to use HTML tags to specify purely structural information and use a style sheet to define how various elements within that structure should be treated. DM uses a subset of the Cascading Style Sheet (CSS) language, which was introduced for this purpose in HTML documents.
-As an example of a style sheet, suppose one wanted combat and conversational messages to appear differently—perhaps using different colors. Instead of using the <FONT> tag to color the text, you could use <SPAN> to mark the beginning and ending of the text and to specify what kind of message it is. The result might be text such as the following:
+As an example of a style sheet, suppose one wanted combat and conversational messages to appear differently--perhaps using different colors. Instead of using the <FONT> tag to color the text, you could use <SPAN> to mark the beginning and ending of the text and to specify what kind of message it is. The result might be text such as the following:
 "[usr] spanks [targ]!"
@@ Строка 581: / Строка 569: @@
 .system {color: red; font-weight: bold}
 .command {color: green}
-In this example, the background color of the terminal will be aqua, normal text from the server will be black, and all output from the client will be bold and red, except echoed commands and expansion lists, which will be bold and green. The more specific .command rule is placed after the general .system rule so that its color takes precedence. This is how style sheets are composed—you write general rules first followed by any exceptions.
+In this example, the background color of the terminal will be aqua, normal text from the server will be black, and all output from the client will be bold and red, except echoed commands and expansion lists, which will be bold and green. The more specific .command rule is placed after the general .system rule so that its color takes precedence. This is how style sheets are composed--you write general rules first followed by any exceptions.
@@ Строка 698: / Строка 686: @@
 The advantage of using icon states in this way is that the code remains very general. All the map designer has to do is plug in different icons with the same states and a variety of doors can be made from the one basic definition.
-If the icon state specified by the flick instruction does not exist, it has no effect. In the above code, for example, a door icon could be used that did not have "opening" and "closing" states defined. Everything would work—only the transition would not be animated.
+If the icon state specified by the flick instruction does not exist, it has no effect. In the above code, for example, a door icon could be used that did not have "opening" and "closing" states defined. Everything would work--only the transition would not be animated.

← Предыдущая версия		Версия от 14:25, 28 января 2016
Строка 1:		Строка 1:
		+	{{Заготовка}}
		+
	{{Заготовка}}		{{Заготовка}}

@@ Строка 1: / Строка 1: @@
 ''Это 11 глава перевода оригинального руководства по Dream Maker от разработчиков.''
@@ Строка 26: / Строка 28: @@
 <!--All user input seen so far has come at the initiative of the user. The player may type a command, press a direction key, click an object, etc. These forms of input are all similar because they are ultimately handled by verbs. In the case of the direction keys and mouse clicks, players don't need to actually type any command--the client does it all. However, from the programmer's point of view, these are all the same: The player calls a procedure and possibly passes some arguments to it.-->
-Есть несколько заранее определённых операторов(verbs), принимающих ввод информации от игрока. Это кнопки направления\стрелки (напр. client.North()), щелчок мыши ((client.Click() и client.DblClick()) и ссылки топиков (client.Topic()). Все остальные операторы(verbs) задаются программистом.
+Есть несколько заранее определённых операторов(verbs), принимающих ввод информации от игрока. Это кнопки направления\стрелки (напр. client.North()), щелчок мыши (client.Click() и client.DblClick()) и ссылки топиков (client.Topic()). Все остальные операторы(verbs) задаются программистом.
 <!--The only pre-defined verbs are associated with the client data object. They are the direction keys (e.g. client.North()), mouse clicks (client.Click() and client.DblClick()), and topic links (client.Topic()). All other verbs are defined by the programmer.-->
@@ Строка 134: / Строка 136: @@
 browse	(Doc, Options)
 Doc is the message to display.	Options are various window-specific options. Consult the reference for specifics.
-By default, each message replaces any previous message being displayed but the user can move back to previous messages stored in the client's memory. In many ways, the client terminal behaves like a telnet session and the browse window behaves like a web browser. One displays output sequentially in a continuous stream. The other displays it in discrete chunks--one document after another. The two are each useful in different situations.
+By default, each message replaces any previous message being displayed but the user can move back to previous messages stored in the client's memory. In many ways, the client terminal behaves like a telnet session and the browse window behaves like a web browser. One displays output sequentially in a continuous stream. The other displays it in discrete chunks—one document after another. The two are each useful in different situations.
 The document is often a text string. However, it may be a file instead. The type of file will determine how it is handled. Files may reside in the resource cache or in the file system. As always, cached items may be specified by putting the file name in single quotes. An external file, on the other hand, is indicated using the file instruction described in section 11.2.7.
@@ Строка 191: / Строка 193: @@
        usr.enemy_marker = image('outline.dmi',M)
        usr << usr.enemy_marker
-The code works by first deleting any old enemy marker. A new one is then made and displayed to the user. No one else will see the image--only the player who clicked on the enemy.
+The code works by first deleting any old enemy marker. A new one is then made and displayed to the user. No one else will see the image—only the player who clicked on the enemy.
@@ Строка 374: / Строка 376: @@
 "I am very mad!"
-The start tag <B> turns on bold lettering and </B> turns it off. For a complete list of tags understood by DM, see page 3 in the appendix. The most commonly used ones are listed in figure 11.19 for easy reference.
+The start tag ''' turns on bold lettering and ''' turns it off. For a complete list of tags understood by DM, see page 3 in the appendix. The most commonly used ones are listed in figure 11.19 for easy reference.
 Figure 11.19: Common text tags
@@ Строка 381: / Строка 383: @@
 anchor (for hyperlinks)
-<B></B>	bold
+''''''	bold
 <BIG></BIG>	bigger text
 <BR>	line break
 <FONT></FONT>	font face, size, and color
-<I></I>	italic
+''''	italic
-<P></P>	paragraph
 <S></S>	overstrike
 <SMALL></SMALL>	smaller text
@@ Строка 401: / Строка 407: @@
 Whitespace refers to any spaces, tabs, or newlines. In standard HTML, whitespace serves merely to delimit words. The amount of space and whether it is a tab, space, or newline is irrelevant.
-DM processes whitespace like standard HTML when it is inside of a pair of start and end tags. So, for example, inside of <P> and </P>, the paragraph markers, standard HTML rules are in effect; newlines, spaces, and tabs serve merely to delimit words. Note that an entire document could be surrounded by <HTML> and </HTML> to mark the whole thing as standard HTML.
+DM processes whitespace like standard HTML when it is inside of a pair of start and end tags. So, for example, inside of
 Outside of all HTML tags, DM handles whitespace a little differently. Spaces still delimit words, but newlines (embedded with \n) mark the end of lines. In other words, the newline is automatically converted to <BR>, the linebreak tag. That is convenient for use in messages composed by players when it would be annoying to write formal HTML with paragraph tags and so forth.
@@ Строка 482: / Строка 492: @@
 HTML tags, such as <FONT> may be used to directly format output text. Another approach, however, is to use HTML tags to specify purely structural information and use a style sheet to define how various elements within that structure should be treated. DM uses a subset of the Cascading Style Sheet (CSS) language, which was introduced for this purpose in HTML documents.
-As an example of a style sheet, suppose one wanted combat and conversational messages to appear differently--perhaps using different colors. Instead of using the <FONT> tag to color the text, you could use <SPAN> to mark the beginning and ending of the text and to specify what kind of message it is. The result might be text such as the following:
+As an example of a style sheet, suppose one wanted combat and conversational messages to appear differently—perhaps using different colors. Instead of using the <FONT> tag to color the text, you could use <SPAN> to mark the beginning and ending of the text and to specify what kind of message it is. The result might be text such as the following:
 "[usr] spanks [targ]!"
@@ Строка 569: / Строка 579: @@
 .system {color: red; font-weight: bold}
 .command {color: green}
-In this example, the background color of the terminal will be aqua, normal text from the server will be black, and all output from the client will be bold and red, except echoed commands and expansion lists, which will be bold and green. The more specific .command rule is placed after the general .system rule so that its color takes precedence. This is how style sheets are composed--you write general rules first followed by any exceptions.
+In this example, the background color of the terminal will be aqua, normal text from the server will be black, and all output from the client will be bold and red, except echoed commands and expansion lists, which will be bold and green. The more specific .command rule is placed after the general .system rule so that its color takes precedence. This is how style sheets are composed—you write general rules first followed by any exceptions.
@@ Строка 686: / Строка 696: @@
 The advantage of using icon states in this way is that the code remains very general. All the map designer has to do is plug in different icons with the same states and a variety of doors can be made from the one basic definition.
-If the icon state specified by the flick instruction does not exist, it has no effect. In the above code, for example, a door icon could be used that did not have "opening" and "closing" states defined. Everything would work--only the transition would not be animated.
+If the icon state specified by the flick instruction does not exist, it has no effect. In the above code, for example, a door icon could be used that did not have "opening" and "closing" states defined. Everything would work—only the transition would not be animated.

@@ Строка 57: / Строка 57: @@
 <!--Note that the input instruction does not return until the user has entered a value. Since the entire multi-user system cannot halt while waiting for this to happen, only the current procedure waits. More will be said on the subject of multi-tasking in chapter 13.-->
-One case in which the input instruction proves useful is when something happens in the game that the player needs to respond to. A verb would be too open-ended for the task, making it difficult for the player to guess what to do next.
+Инструкция ввода для игрока выглядит как запрос ответа на сложившуюся ситуацию. В таком случае простое применение оператора(verb) было бы слишком неточным для определения дальнейших действий игры.
-The following code, for example, handles a rather sad event in the life of a player.
+The following code, for example, handles a rather sad event in the life of a player.-->
+Следующий код показывается пример подобного случая:
 ==Output==

← Предыдущая версия		Версия от 20:31, 14 ноября 2015
Строка 21:		Строка 21:


−	===~~Verbs~~===	+	===Операторы (verbs)===

	До сих пор весь ввод был со стороны пользователя. Игрок может написать команду, нажать кнопку управления, щёлкнуть на объект и т.д. Эти виды ввода информации однородны, так как ими управляют одинаковые операторы(verbs). То есть нажатие на кнопку влево вызывает определённый процесс и задаёт ему значение "кнопка влево".		До сих пор весь ввод был со стороны пользователя. Игрок может написать команду, нажать кнопку управления, щёлкнуть на объект и т.д. Эти виды ввода информации однородны, так как ими управляют одинаковые операторы(verbs). То есть нажатие на кнопку влево вызывает определённый процесс и задаёт ему значение "кнопка влево".

@@ Строка 9: / Строка 9: @@
 =Глава 11=
-User Input/Output
+Ввод\вывод Пользователя <!--User Input/Output-->
-Technology is the camp fire around which we narrate our stories.
+Взаимодействие с пользователем - это главная цель любых программ в Dream Maker и эта глава описывает основы языка, отвечающего за ввод и вывод информации.
---Laurie Anderson
+<!--Interacting with the user is the ultimate purpose of any DM program. This chapter describes the elements of the language which make it possible. To come this far would have been impossible without a casual introduction to some of the input/output instructions, but even those have more power to offer.-->
-==Input==
+==Ввод==
-There are two basic ways of getting information from the player. One is client initiated and the other is server initiated input. The difference is in whether the player sends unsolicited input or whether the game asks for it. These will be discussed in the following sections.
+Есть два основных пути получения информации от игрока. Первый - ввод по запросу клиента(игрока), второй - ввод по запросу сервера(игры). Разница в том, посылает ли игрок информацию на обработку, или игра запрашивает необходимую информацию.
 ===Verbs===
-All user input seen so far has come at the initiative of the user. The player may type a command, press a direction key, click an object, etc. These forms of input are all similar because they are ultimately handled by verbs. In the case of the direction keys and mouse clicks, players don't need to actually type any command--the client does it all. However, from the programmer's point of view, these are all the same: The player calls a procedure and possibly passes some arguments to it.
+До сих пор весь ввод был со стороны пользователя. Игрок может написать команду, нажать кнопку управления, щёлкнуть на объект и т.д. Эти виды ввода информации однородны, так как ими управляют одинаковые операторы(verbs). То есть нажатие на кнопку влево вызывает определённый процесс и задаёт ему значение "кнопка влево".
-The only pre-defined verbs are associated with the client data object. They are the direction keys (e.g. client.North()), mouse clicks (client.Click() and client.DblClick()), and topic links (client.Topic()). All other verbs are defined by the programmer.
+Есть несколько заранее определённых операторов(verbs), принимающих ввод информации от игрока. Это кнопки направления\стрелки (напр. client.North()), щелчок мыши ((client.Click() и client.DblClick()) и ссылки топиков (client.Topic()). Все остальные операторы(verbs) задаются программистом.
-The general format for defining a verb includes any number of arguments. Each one may have a default value, an input type, and a list of possible values.
+Общий вид для определения оператора(verb) следующий:
-verb/Name(Arg1 = Default as input-type in List,...)
+Количество аргументов может быть любым. Каждый из них может иметь значение по умолчанию, тип ввода и список допустимых значений.
-===input instruction===
+===Инструкция ввода===
-The input instruction allows you to ask the player for information. This is how DM provides server-initiated input. It is similar to a single verb argument.
+Инструкция ввода - это то, что позволяет вам(со стороны игры) запросить у игрока информацию ввода. На ней построены все взаимоотношения сервера с клиентом. Она похожа на простой одиночный оператор(verb).
->input(User=usr,Message,Title,Default) input	(User,Query,Title,Default) as input-type in List
+: >input(User=usr,Message,Title,Default) input	(User,Query,Title,Default) as input-type in List
-Note that the input instruction does not return until the user has entered a value. Since the entire multi-user system cannot halt while waiting for this to happen, only the current procedure waits. More will be said on the subject of multi-tasking in chapter 13.
+User - это имя игрока(моба).
 One case in which the input instruction proves useful is when something happens in the game that the player needs to respond to. A verb would be too open-ended for the task, making it difficult for the player to guess what to do next.