TIP: Click on subject to list as thread! ANSI
echo: os2
to: Mark Ellis
from: Herbert Rosenau
date: 1999-09-13 23:15:11
subject: Objects

 ME> What is the advantage to creating objects and running things as
 ME> objects as opposed to just making shadows or running with a
 ME> program?

Eh, this is a little complex. Let us show what kind of objects we mean:

shadow is a pointer to its parent. Anythig done with it is really done with
its parent (except location and deletion).

For executeable we have to differ:

a) program file object is the binary data itself. It my be directly started
but any change is made directly on that file (blubber.exe). E.g.: changing the 
name changes the file name on disk of the binary.

b) program object is an abstraction of an executeabele object but has NO file. 
Any change made is don only on this program object but not on the file it is
pointing to. E.g.: Changing the name changes the anme of the program object
the binary file it points to is NOT changed.

To have a program elsewhere on your desktop or in different folder (with or
without differen setting) creat program objects from your program file object
but don't never use shadows from Program file objects.

The most significant visible difference between program and program file
objects is: in settins notebook only program file objects have a page named
file.

Using shadows for data objects is a good idea to have the objects anyway
present you search for. Using shadows for program file objects is not only
ugly it my be risky (change it and your program file is changed! Use program
objects - you can handle them without any risk (move, delete, copy, rename).
Your program file is never touched.

The best way to encapsulate your program files (the binaries/command files)
from your handling is to make program objects of them (you my assign different 
settings to different program objects again without attaching the file on
disk).

 ME> What is the use of the start.cmd as opposed to putting things in
 ME> the startup folder?

The startup.cmd is started while the desktop (WPS) is NOT reday. So no access
to WPS objects is possible.

The startup folder is a special folder class on WPS. It can handle any kind of 
other WPS classes. It will open all objects it contains.

You should only put shadows of your eal objects (folders, program (file)
objects, files (to indirectly oben theiyr associated program (defaultview).
Because the WPS does not directly differ between a view to an object and
starting a program. You can only OPEN vies (a special form of a view is to run 
the program the object points to/visualises it.

 ME> Also, any tips on speeding up warp 4 on a 486dx2/66 with 20megs
 ME> of ram would be appreciated.

- Dont use the WARP Center (disable it in your config sys)
  remove WARPCENTER from AUTOSTART (The WARP Center eats a lot of memory)
  insert LAUNCHPAD instead (less memory intensive)
- disable voice type (deinstall if installed) (it's a true memory monster even 
you don't use your microphone.)

Then if you don't like the WPS change
RUNWORKPLACE to x:\os2\cmd.exe

But the most practicabe way is: inser more RAM (a total of 32 MB is
recommendet, a total of 64MB is sufficient)

If you have more than 1 physical disk drive
set swappath to that physical drive with at least lowest usage and there on
the MOST used logical drive. This will increase the swapping performance
significally.

If you don't use any DOS or Windows programs set
PRTECTONLY=YES

--- Sqed/32 1.14/development
280/801
* Origin: Schont die Umwelt: Vermeidet DOSen (2:2476/493)

SOURCE: echoes via The OS/2 BBS

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.