source: trunk/dll/ipf/tutor.ipf@ 10

Last change on this file since 10 was 10, checked in by root, 23 years ago

Lock in relative dir mods

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
File size: 20.7 KB
Line 
1:h1 res=99800 name=PANEL_TUTORIAL.Tutorials
2:i1 id=aboutTutorial.Tutorials
3:artwork name='bitmaps\tutor.bmp' align=center.
4This tutorial section is provided for the complete novice. If you
5already know how to use OS/2's WPS in general and have used other OS/2
6PM applications, you probably don't need this tutorial. Go forth and be
7productive.
8:p.
9This tutorial addresses the most often used commands in FM/2 -- the only
10commands that most "file managers" provide. There are, of course, many
11more commands available in FM/2. However, once you have the methodology
12for these basic commands mastered, other commands are easy to use. Of
13course, if you're totally new to OS/2 PM and WPS, you should first run
14the OS/2 tutorial. I'm not kidding -- PM programs have similar user
15interfaces, and it all begins with the WPS, so the OS/2 tutorial is a
16must for the new OS/2 user to begin understanding :hp1.all:ehp1. his
17applications.
18:p.
19Plesae pick a topic&colon.
20:p.
21:link reftype=hd res=99810.Rename:elink.
22.br
23:link reftype=hd res=99820.Move:elink.
24.br
25:link reftype=hd res=99830.Copy:elink.
26.br
27:link reftype=hd res=99840.Compare:elink.
28.br
29:link reftype=hd res=99850.View:elink.
30.br
31:link reftype=hd res=99860.Open:elink.
32.br
33:link reftype=hd res=99870.Delete:elink.
34.br
35:link reftype=hd res=99880.Make directory:elink.
36.br
37:link reftype=hd res=99890.Create archive:elink.
38.br
39:link reftype=hd res=99900.Extract from archive:elink.
40.br
41:link reftype=hd res=100060.Double-click actions:elink.
42.br
43:link reftype=hd res=99910.Using context menus:elink.
44
45:h2 res=99910 name=PANEL_TCONTEXT.Context menu tutorial
46:i1 id=aboutContextTutorial.Using Context menus
47To request a context menu, first point the mouse arrow at an object.
48Then click mouse button 2 (B2, usually the right button). A context
49menu will then appear, if available.
50:p.
51The :hp1.Files:ehp1. menu is a "shadow" of the context menu that would
52be shown if one were requested over the :hp1.current object:ehp1..
53Keyboard-only users can use the :hp1.Files:ehp1. menu instead of context
54menus. But stop being unproductively stubborn, get a pointing device.
55&colon.-)
56:p.
57The :hp1.Views:ehp1. menu is a "shadow" of the context menu that would
58be shown if one were requested over whitespace in the current window.
59:p.
60To make things a little clearer to users who haven't used OS/2's WPS
61before, take a look at the following three pictures&colon.
62:artwork name='bitmaps\tcontxt1.bmp' align=left.
63A context menu that applies to one item. The mouse arrow still points at
64the object on which the menu was requested -- that is the object that will
65be affected by the command selected from the menu. You can see the dotted
66outline with rounded corners around the object.
67:artwork name='bitmaps\tcontxt2.bmp' align=left.
68A context menu that applies to several items. The mouse arrow still points
69at the object on which the menu was requested -- since it is highlighted,
70all highlighted objects will be affected by the command selected from the
71menu.
72:artwork name='bitmaps\tcontxt3.bmp' align=left.
73A context menu that applies to a container as a whole. The menu was
74requested over container whitespace (an empty part of the container),
75not over any of the objects that it contains.
76
77:h2 res=99810 name=PANEL_TRENAME.Rename tutorial
78:i1 id=aboutRenameTutorial.Rename Tutorial
79:artwork name='..\..\bitmaps\rename.bmp' align=left.
80Please select a method to learn about&colon.
81:p.
82:link reftype=hd res=99811.Direct editing:elink.
83.br
84:link reftype=hd res=99812.Drag and drop:elink.
85.br
86:link reftype=hd res=99813.Keystrokes:elink.
87
88:h3 res=99811 name=PANEL_TRENAMEDIRECT.Rename by direct editing
89:i1 id=aboutRenameDirectTutorial.Rename by Direct Editing
90:artwork align=left name='bitmaps\direct.bmp'.
91To rename a file system object, hold down the :hp1.Alt:ehp1. key and
92click on the object's name with mouse button 1 (B1, usually the left
93button). The entire pathname of the object appears in a framed control
94known as an :hp1.MLE:ehp1.. You'll initially be located at the start of
95the filename with the filename (excluding the path) highlighted (ready
96to be replaced by whatever you type). The usual editing keys work
97(arrows, home, end, insert, delete, etc.).
98:p.
99Type in the new name, then click the file system object again. FM/2
100renames the object and updates the display.
101:p.
102You can abort the rename by pressing the :hp1.ESCape:ehp1. key.
103:p.
104:link reftype=hd res=99800.Return to Tutorial menu:elink.
105
106:h3 res=99812 name=PANEL_TRENAMEDRAG.Rename by drag and drop
107:i1 id=aboutRenameDragTutorial.Rename by Drag and Drop
108:artwork name='bitmaps\drename.bmp' align=left.
109To invoke a rename using drag and drop, "grab" a file system object with
110the mouse by placing the mouse pointer on top of the object and
111depressing and holding mouse button 2 (B2, usually the right button).
112Still holding B2, "drag" the object to some whitespace (unoccupied space
113in the Directory Container -- a blank area) and then release B2. The
114:link reftype=hd res=91400.Rename dialog:elink. will then appear and you
115can enter a new name for the object.
116:p.
117You can abort a drag and drop action by pressing the :hp1.ESCape:ehp1.
118key.
119:p.
120:link reftype=hd res=99800.Return to Tutorial menu:elink.
121
122:h3 res=99813 name=PANEL_TRENAMEKEY.Rename by keystrokes
123:i1 id=aboutRenameKeyTutorial.Rename by Keystrokes
124Place the dotted cursor on the object you want to rename (make it the
125:hp1.current object:ehp1.). Press Ctrl + r, the accelerator key
126for the Rename command, or pick "Rename" from the :hp1.Files menu:ehp1..
127:p.
128The :link reftype=hd res=91400.Rename dialog:elink. will then appear and
129you can enter a new name for the object.
130:p.
131:link reftype=hd res=99800.Return to Tutorial menu:elink.
132
133:h2 res=99820 name=PANEL_TMOVE.Move tutorial
134:i1 id=aboutMoveTutorial.Move Tutorial
135:artwork name='..\..\bitmaps\mover.bmp' align=left.
136Please select a method to learn about&colon.
137:p.
138:link reftype=hd res=99821.Direct editing:elink.
139.br
140:link reftype=hd res=99822.Drag and drop:elink.
141.br
142:link reftype=hd res=99823.Keystrokes:elink.
143
144:h3 res=99821 name=PANEL_TMOVEDIRECT.Move by direct editing
145:i1 id=aboutMoveDirectTutorial.Move by Direct Editing
146:artwork align=left name='bitmaps\direct.bmp'.
147To move a file system object, hold down the :hp1.Alt:ehp1. key and
148click on the object's name with mouse button 1 (B1, usually the left
149button). The entire pathname of the object appears in a framed control
150known as an :hp1.MLE:ehp1.. You'll initially be located at the start of
151the pathname. Type in the new pathname, then click the file system
152object again. FM/2 moves the object and updates the display.
153:p.
154You can abort the move by pressing the :hp1.ESCape:ehp1. key.
155:p.
156:link reftype=hd res=99800.Return to Tutorial menu:elink.
157
158:h3 res=99822 name=PANEL_TMOVEDRAG.Move by drag and drop
159:i1 id=aboutMoveDragTutorial.Move by Drag and Drop
160:artwork name='bitmaps\tmove.bmp' align=left.
161To move a file system object using drag and drop, "grab" a file system
162object with the mouse by placing the mouse pointer on top of the object
163and depressing and holding mouse button 2 (B2, usually the right
164button). Still holding B2, "drag" the object to its destination (for
165instance, onto a directory in the Drive Tree), and then release B2.
166:p.
167You can abort a drag and drop action by pressing the :hp1.ESCape:ehp1.
168key.
169:p.
170:link reftype=hd res=99800.Return to Tutorial menu:elink.
171
172:h3 res=99823 name=PANEL_TMOVEKEY.Move by keystrokes
173:i1 id=aboutMoveKeyTutorial.Move by Keystrokes
174Place the dotted cursor on the object you want to rename (make it the
175:hp1.current object:ehp1.). Press Ctrl + m, the accelerator key
176for the Move command, or pick "Move" from the :hp1.Files menu:ehp1..
177:p.
178A dialog known as the :link reftype=hd res=91500.Walk Directories:elink.
179dialog appears to allow you to pick or type the destination directory
180for the move operation.
181:link reftype=hd res=99800.Return to Tutorial menu:elink.
182
183:h2 res=99830 name=PANEL_TCOPY.Copy tutorial
184:i1 id=aboutCopyTutorial.Copy Tutorial
185:artwork name='..\..\bitmaps\copier.bmp' align=left.
186Please select a method to learn about&colon.
187:p.
188:link reftype=hd res=99832.Drag and drop:elink.
189.br
190:link reftype=hd res=99833.Keystrokes:elink.
191.br
192:link reftype=hd res=99834.Cloning:elink.
193
194:h3 res=99832 name=PANEL_TCOPYDRAG.Copy by drag and drop
195:i1 id=aboutCopyDragTutorial.Copy by Drag and Drop
196:artwork name='bitmaps\tcopy.bmp' align=left.
197To copy a file system object using drag and drop, press and hold the
198Ctrl key, then "grab" a file system object with the mouse by placing the
199mouse pointer on top of the object and depressing and holding mouse
200button 2 (B2, usually the right button). Still holding B2 and Ctrl,
201"drag" the object to its destination (for instance, onto a directory in
202the Drive Tree), and then release B2. During a copy drag, the dragged
203object is "ghosted" rather than solid as during a move drag.
204:p.
205You can abort a drag and drop action by pressing the :hp1.ESCape:ehp1.
206key.
207:p.
208:link reftype=hd res=99800.Return to Tutorial menu:elink.
209
210:h3 res=99833 name=PANEL_TCOPYKEY.Copy by keystrokes
211:i1 id=aboutCopyKeyTutorial.Copy by Keystrokes
212Place the dotted cursor on the object you want to rename (make it the
213:hp1.current object:ehp1.). Press Ctrl + c, the accelerator key
214for the Copy command, or pick "Copy" from the :hp1.Files menu:ehp1..
215:p.
216A dialog known as the :link reftype=hd res=91500.Walk Directories:elink.
217dialog appears to allow you to pick or type the destination directory
218for the copy operation.
219:p.
220:link reftype=hd res=99800.Return to Tutorial menu:elink.
221
222:h3 res=99834 name=PANEL_TCLONE.Clone tutorial
223:i1 id=aboutCloneTutorial.Clone Tutorial
224You :hp1.clone:ehp1. a file system object by copying it into the same
225directory that already holds it. The :link reftype=hd res=91400.Rename
226dialog:elink. will then appear because of the naming conflict, and allow
227you to specify a new name for the new, "cloned" copy of the object.
228:p.
229:link reftype=hd res=99800.Return to Tutorial menu:elink.
230
231:h2 res=99840 name=PANEL_TCOMPARE.Compare tutorial
232:i1 id=aboutCompareTutorial.Compare Tutorial
233:artwork name='..\..\bitmaps\linkdrag.bmp' align=left.
234To compare file system objects, link-drag one object onto another.
235:p.
236A link drag is initiated by placing the mouse cursor on the object to
237be dragged, holding down the Ctrl and Shift keys, and clicking mouse
238button 2 (B2, usually the right button). While still holding the keys
239and B2, move the mouse to drag the object over the target object, then
240release B2. During a link drag, a rubber-band line appears between the
241source object and the dragged object.
242:p.
243You can change the compare program from FM/2's :link reftype=hd
244res=94600.Internal Settings notebook:elink.. An internal default is
245used if you leave the entry there blank.
246
247:h2 res=99850 name=PANEL_TVIEW.View tutorial
248:i1 id=aboutViewTutorial.View Tutorial
249:artwork name='..\..\bitmaps\view.bmp' align=left.
250Viewing files can be as simple as double-clicking their objects. FM/2
251will attempt to do to the object what should "logically" be done, which,
252in the case of text files, archives and the like, is to view them. If
253you would like different actions taken, FM/2 provides :link reftype=hd
254res=90400.Associations:elink. to allow you to assign special viewer
255programs or actions to different file types.
256:p.
257You can also invoke viewing directly from the :hp1.Files:ehp1. and :link
258reftype=hd res=93700.context:elink. menus, or by pressing the Ctrl + v
259accelerator key. In this case, no other default actions will be taken
260even if one might be "obvious" -- the object will simply be viewed. If,
261for example, you wanted to view an executable, this is the method you'd
262need to use (the default double-click action would be to run the
263executable file, which is usually what you'd want to do).
264:p.
265You can change the viewing program from FM/2's :link reftype=hd
266res=94600.Internal Settings notebook:elink.. An internal default is
267used if you leave the entry there blank.
268:p.
269A good viewing program to try out would be :hp1.Hyperview:ehp1. by
270Michael H. Shacter.
271
272:h2 res=99860 name=PANEL_TOPEN.Open tutorial
273:i1 id=aboutOpenTutorial.Open Tutorial
274"Opening" a file system object is an object-based concept. When you
275open a directory, you get a view of the file system objects (files and
276directories) contained within that object. When you open an executable
277file, you cause it to execute. When you open a data file, you usually
278cause its owning application (if known) to execute with the data file
279being loaded by the application. This is known as a "default" open.
280:p.
281But there are often several types of "open" operation that can be
282performed on an object. For instance, you can open an object's Settings
283notebook. FM/2 provides some variations on WPS open themes. You can
284open either a WPS folder or an FM/2 Directory Container for a directory
285object, for instance (to find out more about opening an FM/2 Directory
286Container for a directory object, see the :link reftype=hd
287res=98900.Opening a Directory Container:elink. topic).
288:p.
289To open an object's default WPS "view," use the F6 accelerator key, or
290press the Ctrl key while double-clicking the object. The same type of
291"open" will be done on the object that would be done if you directly
292double-clicked the object in a WPS folder object (remember, WPS folders
293are just visual representations of directories).
294:p.
295To open a file system object's WPS Settings notebook directly, use the
296F7 accelerator key, or press the Ctrl and Shift keys while
297double-clicking the object.
298:p.
299For directory objects, you have the choice of WPS view type to open, as
300well -- Icon, Details or Tree view. You pick these from the
301:hp1.Open:ehp1. cascade menu on the :hp1.Files:ehp1. menu or a context
302menu requested on the object (you request a context menu on an object by
303placing the mouse pointer on the object and clicking mouse button 2,
304B2). A command to open an FM/2 Directory Container is also on that
305cascade menu, and is the default.
306
307:h2 res=99870 name=PANEL_TDELETE.Delete tutorial
308:i1 id=aboutDeleteTutorial.Delete Tutorial
309:artwork name='..\..\bitmaps\delete.bmp' align=left.
310:artwork name='..\..\bitmaps\permdel.bmp' align=left.
311There are two styles of deleting under FM/2 -- a "regular" delete, that
312leaves the objects capable of being undeleted using OS/2's UNDELETE
313command or FM/2's Undelete Utility, and a "permanent" delete that does
314not leave the object recoverable. "Permanent" deletions are usually
315faster than "recoverable" deletions. You can select which type you want
316to be the default in FM/2's internal :link reftype=hd res=94600.Settings
317notebook:elink..
318:p.
319Note&colon. You have to set up OS/2, using CONFIG.SYS, so that UNDELETE
320is enabled to do non-permanent deletions. See :link reftype=launch
321object='VIEW.EXE' data='CMDREF.INF UNDELETE'.UNDELETE:elink. in the OS/2
322online help.
323:p.
324You can delete objects in many ways&colon.
325:p.
326:hp1.Drag and drop:ehp1. Drag the object(s) to FM/2's toolbar Trashcan
327icon, or to the WPS's Shredder icon. (You might want to pick up a
328replacement for the WPS Shredder like the free :hp1.mshred:ehp1. object
329written by the author of FM/2.)
330:p.
331:hp1.Files or context menu:ehp1. Select the :hp1.Delete:ehp1. command
332or pick the type of delete from the cascade menu.
333:p.
334:hp1.Keyboard:ehp1. The Ctrl + d accelerator key performs a "regular"
335delete, Shift + Ctrl + D (also written as just "Ctrl + D" -- accelerator
336keys are case sensitive) performs a permanent delete.
337
338:h2 res=99880 name=PANEL_TMKDIR.Make directory tutorial
339:i1 id=aboutMkdirTutorial.Make Directory Tutorial
340:artwork name='..\..\bitmaps\mkdir.bmp' align=left.
341To create a directory, use FM/2's Make Directory command.
342:p.
343You can pick this command from the :hp1.Files:ehp1. menu or a
344:hp1.context:ehp1. menu (under the Miscellaneous cascade menu). You can
345click the button on FM/2's toolbar. Or you can use the Shift + Ctrl
346+ "M" accelerator key.
347:p.
348FM/2 presents you with a small dialog box in which you can type the name
349of the directory that you want to create -- FM/2 will try to fill in the
350entry field with a guess at the first part of what you want, but you can
351delete that if desired (:hp1.Shift + Home:ehp1., then touch the
352:hp1.Del:ehp1. key to do it quickly).
353:p.
354The directory created can be many levels deep. FM/2 will create
355intermediate subdirectories as required if they do not already exist.
356For example, if you have a directory \myapps and want to create a
357directory \myapps\games\mygame you can do so without first creating
358\myapps\games -- just enter the full path you want and FM/2 will
359create the intermediate directory \myapps\games.
360:p.
361You can pick :hp1.<New directory>:ehp1. from the Common directories
362:link reftype=hd res=99400.quicklist:elink. to create a new directory
363and open its Directory container simultaneously.
364
365:h2 res=99890 name=PANEL_TARCHIVE.Create archive tutorial
366:i1 id=aboutArchiveTutorial.Create Archive Tutorial
367:artwork name='..\..\bitmaps\archive.bmp' align=left.
368To create a new archive, select the file system objects you want in the
369archive, then select :hp1.Archive:ehp1. from the :hp1.Files:ehp1. menu
370or a :hp1.context:ehp1. menu, or click the Archive toolbar button.
371:p.
372A dialog then appears that lets you select the type of archive to be
373created from the types defined in the :hp1.ARCHIVER.BB2:ehp1. control
374file.
375:p.
376Once you have selected the archive type, the :link reftype=hd
377res=90300.Archive:elink. dialog appears and lets you specify the name of
378the archive to be created and the type of archiving action (move or copy
379to archive, include subdirectories or not, recurse into subdirectories,
380etc.). You can specify additional filemasks or place more obscure
381options on the command line to be executed.
382:p.
383To add to an existing archive, you can go through the same process,
384changing the name of the archive to that of the existing archive, or
385simply drag objects onto the existing archive's object.
386:p.
387You can also add objects to an archive by viewing it (double-click on
388the archive object) and then dragging the objects to be added onto the
389:link reftype=hd res=90200.Archive Container:elink. window.
390
391:h2 res=99900 name=PANEL_TEXTRACT.Extract from archive tutorial
392:i1 id=aboutExtractTutorial.Extract from Archive Tutorial
393:artwork name='..\..\bitmaps\extract.bmp' align=left.
394To extract from an archive, first place the dotted cursor on the file
395(make it the :hp1.current object:ehp1.), then select the
396:hp1.Extract:ehp1. command from the :hp1.Files:ehp1. menu or a context
397menu requested on the archive, or press the Ctrl + x accelerator
398key.
399:p.
400The :link reftype=hd res=91000.Extract:elink. dialog then appears and
401allows you to specify a filemask to be extracted and/or to add more
402esoteric options to the command line to be executed.
403:p.
404You can also extract objects from an archive by viewing it (double-click
405on the archive object) and then dragging objects from the :link
406reftype=hd res=90200.Archive Container:elink. window to FM/2's other
407windows, or by using the :hp1.Files:ehp1. or context menu and selecting
408from various types of :hp1.Extract:ehp1. commands there.
409
410:h2 res=100060 name=PANEL_DBLCLK.Double-click actions
411:i1 id=aboutDoubleClick.Double-click actions
412
413Double-clicking a file system object causes a :hp1.default action:ehp1.
414to be taken. FM/2 has its own set of defaults, but you can override
415those in many cases. Here's a description of the FM/2 defaults and
416how to change them&colon.
417:p.
418If the object is a directory, the Directory Container switches to look
419into that directory. If it's a file, FM/2 first checks to see if you've
420assigned any :link reftype=hd res=90400.Associations:elink. that match
421the filename and signature (if applicable). Next, FM/2 tries to view
422the file as an :link reftype=hd res=90200.archive:elink.. If it's not
423an archive, FM/2 checks to see if the file's an executable and runs it
424if so. Then INI and HLP files are checked by extensions and viewed as
425such. If all else fails, FM/2 views the file using the configured or
426internal viewer.
427:p.
428In the Drive Tree, holding down the Shift key while double-clicking
429causes a new FM/2 Directory Container to be opened, and holding down
430the Ctrl key while double-clicking causes a WPS folder to be opened.
431:p.
432In Directory Containers, holding down the Ctrl key while double-clicking
433causes the default WPS open to be performed on the object (this honors
434WPS associations, runs executables, opens folders in their default view,
435or opens the Settings notebook for the object -- whatever
436double-clicking on the object in the WPS would do), and holding down the
437Shift key while double-clicking causes the file to be directly Viewed,
438bypassing the other steps listed above (for file objects; directory
439objects cause another FM/2 window to be opened).
440:p.
441If you'd like more detail, go to the :link reftype=hd
442res=99850.View:elink. and :link reftype=hd res=99860.Open:elink.
443tutorials.
444:p.
445You can change what FM/2 does on a double-click of a file object by
446using FM/2's :link reftype=hd res=90400.Associations:elink.. This is
447a very powerful tool for customizing FM/2's behavior, so when you're
448ready, be sure to look it over.
Note: See TracBrowser for help on using the repository browser.