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

Author:jfiat

Browse Source 
Date:2009-11-19T17:49:07.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@360 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
jfiat
2009-11-19 17:49:07 +00:00
parent cc1f34d518
commit ef95dc14df
2 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
documentation/current/eiffelstudio/eiffelstudio-guided-tour/recompiling-and-editing.wiki
View File

@@ -21,7 +21,7 @@ The Editing Tool hosts a text editor which you can use to change the class text.
io.new_line io.new_line
</code> </code>
They are very similar to the current first two lines of the routine, so you can just use copy-paste: select the first two lines with the mouse, copy them using <code>CTRL-C</code> (or <code>Copy</code> from the <code>Edit</code> menu), then paste them just after the <code>do</code> using <code>CTRL-V</code> (or <code>Paste</code> from the <code>Edit</code> menu). Add or remove tabs to align with the rest of the routine, and change the string to <code lang=text>THIS IS SOME MORE ADDED TEXT</code> so that the result will look like what's shown on the next figure. This is all there is to change; the second line remains untouched. Please check the result and be careful not to introduce any mistakes; in the next section we'll study how EiffelStudio will report syntax and other errors, but right now we want to see what happens when everything is right! They are very similar to the current first two lines of the routine, so you can just use copy-paste: select the two lines with the mouse, copy them using <code>CTRL-C</code> (or <code>Copy</code> from the <code>Edit</code> menu), then paste them just after the <code>do</code> using <code>CTRL-V</code> (or <code>Paste</code> from the <code>Edit</code> menu). Add or remove tabs to align with the rest of the routine, so that the result will look like what's shown on the next figure. This is all there is to change; the second line remains untouched. Please check the result and be careful not to introduce any mistakes; in the next section we'll study how EiffelStudio will report syntax and other errors, but right now we want to see what happens when everything is right!
[[Image:index-67]] [[Image:index-67]]

4
documentation/current/eiffelstudio/eiffelstudio-reference/outputs-tool/external-compilation-pane.wiki
View File

@@ -35,6 +35,8 @@ You can open a file mentioned in the external compiler output in a specified ext
[[Image:External compilation pane file selection|Selecting a file to open]] [[Image:External compilation pane file selection|Selecting a file to open]]
If, as is often the case with C compilation errors, a line number is adjacent to the file name, you can select the line number and the file will be opened in the external editor and the cursor positioned at that line number.
==View external code for a class/feature== ==View external code for a class/feature==
You can view the external code for a particular Eiffel class or feature in an external editor. Pick the class or feature whose generated code you want to see, and drop it onto the [[Image:metrics-tool--command-send-to-external-editor-icon|send to external editor]] button. The external code for the class or feature will be shown in an external editor. You can view the external code for a particular Eiffel class or feature in an external editor. Pick the class or feature whose generated code you want to see, and drop it onto the [[Image:metrics-tool--command-send-to-external-editor-icon|send to external editor]] button. The external code for the class or feature will be shown in an external editor.
@@ -43,6 +45,8 @@ The figure below shows an example of picking the feature <code>make</code> and d
[[Image:External compilation pane edit feature]] [[Image:External compilation pane edit feature]]
You can also drop a class or feature pebble on the '''open folder''' or '''terminal''' icon. This will get you to the folder in which the generated code for the class or feature resides.
===View external code from the finalized folder=== ===View external code from the finalized folder===
By default the code that you see in an external editor is from the workbench (W_code) folder. You can see the corresponding external code from the finalized (F_code) folder by holding the <code>CTRL</code> key while you drop the class or feature pebble. By default the code that you see in an external editor is from the workbench (W_code) folder. You can see the corresponding external code from the finalized (F_code) folder by holding the <code>CTRL</code> key while you drop the class or feature pebble.