mirrors/eiffel-org
1
0
Fork 0
mirror of https://github.com/EiffelSoftware/eiffel-org.git synced 2025-12-08 15:52:26 +01:00
Code Issues Packages Projects Releases Wiki Activity

Replace occurrences of ..' by ..` (backtick+text+quote replaced by backtick+text+backtick).

Browse Source 
git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1597 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
eiffel-org
2016-07-01 10:32:39 +00:00
parent 067d834eba
commit 10e39cfb40
68 changed files with 452 additions and 453 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
documentation/trunk/solutions/gui-building/eiffelbuild/eiffelbuild-reference/builder-window.wiki
View File

@@ -21,8 +21,8 @@ Imagine that this was not the case, and each container [[EiffelBuild Notation|ob
In the screenshot above, you can see that there are two [[EiffelBuild Notation|objects]] representing containers in your project, an <eiffel>EV_VERTICAL_BOX</eiffel>, and an <eiffel>EV_HORIZONTAL_BOX</eiffel> (Excluding the <eiffel>EV_TITLED_WINDOW</eiffel> [[EiffelBuild Notation|object]] represented by this window).
The properties of the [[EiffelBuild Notation|objects]] in you system are always reflected in this window, with a few exceptions:
* 'user_can_resize', 'maximum_width', 'maximum_height' and 'title_string' are not reflected in this window.
* 'minimum_width' and `minimum_height' are not reflected in any of the controls representing [[EiffelBuild Notation|objects]] within this window.
* `user_can_resize`, `maximum_width`, `maximum_height` and `title_string` are not reflected in this window.
* `minimum_width` and `minimum_height` are not reflected in any of the controls representing [[EiffelBuild Notation|objects]] within this window.
{{seealso|<br/>
[[Display window|Display window]] <br/>

12
documentation/trunk/solutions/gui-building/eiffelbuild/eiffelbuild-reference/constants.wiki
View File

@@ -54,7 +54,7 @@ As objects are reliant on the constant you are removing, you must confirm that y
==String constant==
A String constant represents an Eiffel STRING, and may be any valid STRING. For example, in the generated constants file, for a String constant named `modify_button_text', the following code is generated:
A String constant represents an Eiffel STRING, and may be any valid STRING. For example, in the generated constants file, for a String constant named `modify_button_text`, the following code is generated:
<code>
modify_button_text: STRING
-- `Result' is STRING constant named modify_button_text.
@@ -66,7 +66,7 @@ A String constant represents an Eiffel STRING, and may be any valid STRING. For
==Integer constant==
A Integer constant represents an Eiffel INTEGER, and may be any valid INTEGER value. For example, in the generated constants file, for an Integer constant named `medium_padding', the following code is generated:
A Integer constant represents an Eiffel INTEGER, and may be any valid INTEGER value. For example, in the generated constants file, for an Integer constant named `medium_padding`, the following code is generated:
<code>
medium_padding: INTEGER
-- `Result' is INTEGER constant named medium_padding.
@@ -76,7 +76,7 @@ A Integer constant represents an Eiffel INTEGER, and may be any valid INTEGER va
==Directory constant==
A Directory constant is an Eiffel representation of a directory, as a STRING value. For example, in the generated constants file, for a Directory constant named `pixmap_location', the following code is generated:
A Directory constant is an Eiffel representation of a directory, as a STRING value. For example, in the generated constants file, for a Directory constant named `pixmap_location`, the following code is generated:
<code>
pixmap_location: STRING
-- `Result' is DIRECTORY constant named pixmap_location.
@@ -115,12 +115,12 @@ A pixmap constant is a representation of a pixmap image, and two types are avail
set_with_named_file(Result, a_file_name)
end</code>
Where `pixmap_location' is the name of the Directory constant to which the pixmap is relative.
Where `pixmap_location` is the name of the Directory constant to which the pixmap is relative.
==Font constant==
A Font constant represents an EV_FONT. For example, in the generated constants file, for a font constant named `times_new_roman', the following code is generated:
A Font constant represents an EV_FONT. For example, in the generated constants file, for a font constant named `times_new_roman`, the following code is generated:
<code>
times_new_roman: EV_FONT
-- `Result' is EV_FONT constant named `times_new_roman'.
@@ -135,7 +135,7 @@ A Font constant represents an EV_FONT. For example, in the generated constants f
==Color constant==
A Color constant represents an EV_COLOR. For example, in the generated constants file, for a color constant named `red', the following code is generated:
A Color constant represents an EV_COLOR. For example, in the generated constants file, for a color constant named `red`, the following code is generated:
<code>
red: EV_COLOR
-- `Result' is EV_COLOR constant named `red'.

2
documentation/trunk/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-project-settings-window/build-tab.wiki
View File

@@ -15,7 +15,7 @@ The options available in this tab are as follows:
* <span id="build_type"></span> '''Build type'''
Select 'Project' if you wish to generate a complete project including an ace file, and an application class, which will launch the GUI you are developing.
Select `Class' if you wish to generate a single class that represents the GUI you are developing. This option is useful if you wish to incorporate your current project into an existing EiffelVision 2 system.
Select `Class` if you wish to generate a single class that represents the GUI you are developing. This option is useful if you wish to incorporate your current project into an existing EiffelVision 2 system.
* '''Always rebuild ace'''
This option causes the ace file to be completely re-generated every time you generate your project. If you do not wish the ace file to be re-generated, then disable this option. This check box is only available if 'build type' is set to 'project'.

2
documentation/trunk/solutions/gui-building/eiffelbuild/eiffelbuild-reference/object-editor/index.wiki
View File

@@ -60,7 +60,7 @@ Clicking this button will cause the following dialog to be displayed:
Looking at the screenshot above, you will see that this dialog contains all the action_sequences available for the <eiffel>EV_BUTTON</eiffel> to which the object editor is targeted.
If you check a button connected with one of the action sequences, you will be then able to enter the name of a feature that you wish to connect to the action sequence. The screenshot above shows the user has connected a feature named `button_pressed' to the `select_actions'. When [[EiffelBuild: Code Generation|code is generated]] , this will cause EiffelBuild to generate an empty feature named `button_pressed' already connected to the `select_actions' of the button.
If you check a button connected with one of the action sequences, you will be then able to enter the name of a feature that you wish to connect to the action sequence. The screenshot above shows the user has connected a feature named `button_pressed` to the `select_actions`. When [[EiffelBuild: Code Generation|code is generated]] , this will cause EiffelBuild to generate an empty feature named `button_pressed` already connected to the `select_actions` of the button.
{{note|You will only be allowed to enter valid and unique Eiffel feature names. If a name is invalid, it will be highlighted in red, and a dialog will warn you when you attempt to close the dialog. }}