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

merged from 18.07

Browse Source 
git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@2058 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
eiffel-org
2018-09-03 20:21:22 +00:00
parent 52e6547a13
commit 2b1cecb8c5
3 changed files with 279 additions and 269 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
documentation/trunk/eiffelstudio/Tutorials/customizing-tools-layout-and-toolbars.wiki
View File

@@ -1,3 +1,5 @@
[[Property:modification_date|Tue, 21 Aug 2018 18:55:21 GMT]]
[[Property:publication_date|Tue, 21 Aug 2018 18:55:21 GMT]]
[[Property:title|Customizing the tools layout and toolbars]]
[[Property:weight|-8]]
[[Property:uuid|eb75573e-c653-9290-376a-063cb5fa32d4]]
@@ -7,18 +9,16 @@ We saw in [[Viewing Classes]] how EiffelStudio panes could be resized and how th
Now let's look at some other ways in which you can customize the layout the EiffelStudio tools.
EiffelStudio uses a '''default''' tools layout that generally reflects the preferences of a majority of users. So if you don't change anything in the way that the EiffelStudio interface is originally set up, you should still be able to work well enough. Also, be aware that as new versions of EiffelStudio emerge, it is possible that the layout that "generally reflects the preferences of a majority of users" may change. So, don't be too surprised if things look just a little different after installing a new version.
The first time you use EiffelStudio, it will display a '''default''' tools layout that reflects the preferences of a majority of users. Typical user preferences change, so don't be too surprised if things look just a little different after installing a new version.
After considerable experience using EiffelStudio, you may decide that certain changes to the default make sense for the way that you work. For example, you may always want to have certain tools visible which were not visible by default. Once you make a change like this, EiffelStudio generally remembers that change and it will be in force the next time you open EiffelStudio. But you can also save a complete tools layout and recall it at a later time. For example, you might have two or three different development '''modes''' that you work in, and have a saved tools layout for each.
As you gain more experience with EiffelStudio, you may want to adapt the layout to your personal preferences. For example, you may always want to have certain tools visible which were not visible by default. Once you make a change like this, EiffelStudio generally remembers that change and it will be in force the next time you open EiffelStudio. But you can also save a complete tools layout and recall it at a later time. For example, you might have two or three different development '''modes''' that you work in, and have a saved tools layout for each.
The ways in which the EiffelStudio tools can be arranged are nearly endless. You can make tools visible or hide them. You can make almost any tool a tab in almost any pane. You can re-order the tabs for a pane. You can pull tools completely out of EiffelStudio as free-floating windows. You can create additional panes as needed. Almost any pane can be "pinned" open or "auto hidden".
==Reverting to the default layout==
In view of this, it seems fitting that the first item that we should cover is how to revert back to the default layout in the case in which you get the tool layout in such a state that you just want dismiss the changes that you made and start over.
You can use the menu path:
If you changed the layout and are not pleased with the result, you can revert to the default. Use the menu path:
<code lang="text">
View --> Tools Layout --> Reset Tools Layout
</code>

5
documentation/trunk/eiffelstudio/eiffelstudio-reference/eiffelstudio-release-notes/Release-notes-for-EiffelStudio-18.07.wiki
View File

@@ -1,4 +1,4 @@
[[Property:modification_date|Wed, 04 Jul 2018 09:10:10 GMT]]
[[Property:modification_date|Wed, 25 Jul 2018 07:17:36 GMT]]
[[Property:publication_date|Wed, 27 Jun 2018 08:33:05 GMT]]
[[Property:uuid|73F20392-AB22-4CD6-BFE5-83296B8BD64B]]
[[Property:title|Release notes for EiffelStudio 18.07]]
@@ -21,7 +21,8 @@
* It is now possible to extend a project target from a different project (ECF).
* The rules for '''class''' features were relaxed. Re-declaration into or joining with a class feature is valid as soon as combined assertions satisfy the class feature conditions. A non-static external and constant feature automatically gets a class post-condition if its contracts do not involve constructs that can access Current object .
* Updated the Eiffel grammar to support bracket expressions as bracket targets (such as `table[x][y][z]`)
* Supports detection of '''VHPR(5)''' violations for arbitrary ancestors, not just for immediate parents. This may be a breaking change for classes that inherit different generic derivations of the same class.
* Supported detection of '''VHPR(5)''' violations for arbitrary ancestors, not just for immediate parents. This may be a breaking change for classes that inherit different generic derivations of the same class.
* Added detection of a type mismatch between a manifest array and a target of the reattachment where the manifest array is used for projects created before 18.01 release to facilitate migration to the new typing rules for manifest arrays. A per-library option and a project-wide setting are available to control the checks.
==Libraries==
* EiffelBase:

9
documentation/trunk/solutions/other-languages/eiffel-external-mechanism/interfacing-c-and-c.wiki
View File

@@ -1,3 +1,5 @@
[[Property:modification_date|Mon, 03 Sep 2018 08:31:04 GMT]]
[[Property:publication_date|Mon, 03 Sep 2018 08:28:15 GMT]]
[[Property:title|Interfacing with C and C++]]
[[Property:weight|0]]
[[Property:uuid|dcc4e216-307b-46ec-1bc1-a15da8b99469]]
@@ -119,5 +121,12 @@ The first condition means that user file names must conform to the path and file
Some parts of the validity of external file names may not be able to be determined by an Eiffel compiler and thus ultimately depend upon the evaluation of an external compiler. For example, the Eiffel compiler might not be able to determine whether a particular C file contains valid content.
==Related pages or articles==
{{seealso| <br/>
- [https://www.eiffel.org/doc/solutions/Eiffel_%22external%22_mechanism] <br/>
- [https://www.eiffel.org/article/protecting_objects] <br/>
- [https://www.eiffel.org/article/using_externals_in_multithreaded_applications] <br/>
- [https://www.eiffel.org/article/c_c_calls_and_callbacks] <br/>
}}