@DATABASE "MWB_DOpus.guide" @AUTHOR "Trevor Morris (a3nb@unb.ca)" @SMARTWRAP @$VER: MWB_DOpus.guide Release 6 (17-07-95) @REMARK Smartwraping by Nudel! @NODE "MAIN" "MWB_DOpus Guide 17-07-95" @NEXT "MAIN" @{fg shine} @{par} @{bg fill}@{" Magic WorkBench Stuff for Directory Opus 5 " LINK "GPSoft"}@{bg background} @{par} @{bg fill}@{" by " LINK "Author"}@{bg background} @{par} @{bg fill}@{" Trevor Morris & Leo Davidson " LINK "Author"}@{bg background} @{fg text} @{par} @{par} @{" What is this stuff? " LINK "DownLoad" } @{par} @{" System Requirements... " LINK "Requirements"} @{par} @{" Installation... " LINK "Installation"} @{par} @{" Hints & Tips & HELP! " LINK "HintsTips" } @{par} @{" The Authors " LINK "Author" } @{par} @{par} @{" History " LINK "History" } @{par} @{" Thanks to... " LINK "Thanks" } @{par} @{" Nudel speaks... " LINK "Nudel" } @{par} @{" Distribution " LINK "Distribution"} @{par} @{" Disclaimer " LINK "Disclaimer" } @{par} @{par} @{" DOpus 5 Reviewed " LINK "Review" } @{par} @{" How to order DOpus5 " LINK "LeoD5PM_OrderInfo"} @{par} @{par} @{" What is DIF? " LINK "DIF" } @{par} @{" What is PaletteShove " LINK "PS" } @{par} @{par} @{" Children of the Storm " LINK "COTS_Charity"} @{par} @{par} @{par}@{fg fill}This archive is freely distributable, HOWEVER please have the courtesy to distribute this archive with @{b}all of its files and documentation in tact@{ub}, as they are intended to help those who obtain this piece of software. Thanx!@{fg text} @{par} @{par}@{b}SYSOPS@{ub}: Please name this achive MWOpus_6.lha if you post it. Thanx in advance! @ENDNODE @NODE "DownLoad" "What is this stuff?" @{par} @{fg shine}What is this stuff?@{fg text} @{par} @{par}The original archive should contain the following files: @{par} @{par} @{fg fill}@{"ARexx (dir) " LINK "ARexx" } @{par} @{"c (dir) " LINK "c" } @{par} @{"Color&Pointer (dir)" LINK "C&P" } @{par} @{"Drives (dir) " LINK "Drives"} @{par} @{"Fonts (dir) " LINK "Fonts" } @{par} @{"Icons (dir) " LINK "Icons" } @{par} @{"Images (dir) " LINK "Images"} @{par} @{"Patterns (dir) " LINK "Patterns"} @{par} @{"WBStartup (dir) " LINK "WBStartup"}@{fg text} @{par} ARexx.info @{b}Button_Template@{ub} @{par} Button_Template.info C.info @{par} Color&Pointer.info DirectoryOpus.info @{par} @{b}DOpusScreen.pic@{ub} DOpusScreen.pic.info @{par} Drives.info Fonts.info @{par} Icons.info Images.info @{par} @{b}MWB_DOpus.guide@{ub} MWB_DOpus.guide.info @{par} @{b}NudelScreen.pic@{ub} NudelScreen.pic.info @{par} Patterns.info @{b}SYSOPS.README@{ub} @{par} SYSOPS.README.info WBStartup.info @{par} @{par}The @{b}Button_Template@{ub} is just a picture of everything in the @{"images drawer" LINK "Images"} as well as some extra stuff (it's handy as a template for drawing your own, but if you do, make sure you upload them for everyone else to enjoy!) @{par} @{par}@{b}DOpusScreen.pic@{ub} is a snapshot of @{"my" LINK "Author"} DOpus screen which may give you some ideas! @{par} @{par}@{b}NudelScreen.pic@{ub} is a snapshot of @{"Leo Davidson's" LINK "Author"} DOpus screen (even more ideas for you A500 owners ;) @{par} @{par}@{b}MWB_DOpus5.guide@{ub} - you are reading it ;) @{par} @{par}@{b}SYSOPS.README@{ub} is just a notice to BBS sysops regarding the naming convension of this archive to try to avoid the situation where people accidentally download the same archive twice (or more) because it has a different name. @ENDNODE @NODE "ARexx" "ARexx (dir)" @TOC "Download" @{par} @{fg shine}ARexx (dir)@{fg text} @{par} @{par}This dir contains the following ARexx scripts written by @{"Leo Davidson" LINK "Author"}: @{par} @{par} @{b}WinCopy.dopus5@{ub} WinCopy.dopus5.info @{par} @{b}WinSwap.dopus5@{ub} WinSwap.dopus5.info @{par} @{par}Copy them into your @{b}DOpus5:Arexx/@{ub} drawer. Read their headers for configuration information and discription. @ENDNODE @NODE "c" "c" @TOC "Download" @{par} @{fg shine}The "c" directory@{fg text} @{par} @{par}This dir contains the following items: @{par} @{par} @{"DIF" LINK "DIF"} DIF.info @{par} DIF.readme DIF.readme.info @{par} @{"PaletteShove" LINK "PS"} PaletteShove.info @{par} PaletteShove.guide PaletteShove.guide.info @ENDNODE @NODE "C&P" "Color&Pointer" @TOC "Download" @{par} @{fg shine}Color&Pointer@{fg text} @{par} @{par}This drawer contains the following: @{par} @{par} ClickForColors ClickForColors.info @{par} ClickForPointer ClickForPointer.info @{par} @{par}These are just my palette and pointer configs. Clicking on them will change your prefs to emulate mine - but only until you reboot. The palette is quite useful, as most times I draw things to look good using my palette (of course) and it may not necessarily look good with yours!? @ENDNODE @NODE "Drives" "Drives" @TOC "Download" @{par} @{fg shine}Drives@{fg text} @{par} @{par}This archive contains the following drive brushes: @{par} @{par} Plain.brush Plain.info @{par} Work.brush Work.info @{par} System.brush System.info @{par} @{par}I intended to use these to make a drive bank, however DOpus put a significant sized border around them - which defeated the original purpose of making them small! However, you may still find a use for them!? @ENDNODE @NODE "Fonts" "Fonts" @TOC "DownLoad" @{par} @{fg shine}Fonts@{fg text} @{par} @{par}This directory just contains a couple of fonts which some of you might like to use for DOpus? Check out the NOoDLE & P0T fonts by @{"Leo Davidson" LINK "Author"}. @{par} @{par} @{fg fill}P0T-IBM (dir) @{par} P0T-NOoDLE (dir) @{par} P0T-Prop (dir) @{par} PolarSmall-Prop (dir) @{par} PolarSmall (dir)@{fg text} @{par} P0T-IBM.font P0T-NOoDLE.font @{par} P0T-Prop.font PolarSmall-Prop.font @{par} PolarSmall.font @ENDNODE @NODE "Icons" "Icons" @TOC "Download" @{par} @{fg shine}Icons@{fg text} @{par} @{par}This archive contains the following icons: @{par} @{par} AppIcon.info Buttons.info @{par} Environment.info Filetype.info @{par} Group.info Lister.info @{par} Settings.info @{par} @{par}I realize that these may look identical to the ones supplied with DOpus, but they have been fixed. The original icons @{i}swim@{ui} when you click on them - there were gliches in them which I fixed (I don't know why - it just bugged me I guess!?! ;) @ENDNODE @NODE "Images" "Images" @TOC "Download" @{par} @{fg shine}Images@{fg text} @{par} @{par}This archive contains the following images: @{par} @{par} 3D.small AddIcon.small @{par} All.small Assign.small @{par} Balance.small Balls.small @{par} Boot.small Brush.small @{par} C.small Cache.small @{par} Calculator.small CD.small @{par} CheckFit.small CheckFit2.small @{par} CLI.small ClipBoard.small @{par} ClipBoard2.small Clone.small @{par} Comment.small Computer.small @{par} Copy.small CopyAs.small @{par} CopyWin.small Cut.small @{par} DateStamp.small DateStamp2.small @{par} DBase.small Delete.small @{par} Demon.small Device.small @{par} Device2.small Dice.small @{par} Disk.small DiskCopy.small @{par} Disks.small Document.small @{par} DOpus5.small DownArrow.small @{par} Drawer.small DynaShow.small @{par} Edit.small Edit2.small @{par} EditNew.small EditSS.small @{par} Exclamation.small FastView.small @{par} Feather1.small Feather2.small @{par} Feet.small Film.small @{par} FirstAid.small Font.small @{par} Function.small FX.small @{par} Game.small Game2.small @{par} Gears.small GetSizes.small @{par} Globe.small Graphics.small @{par} HamLab.small HardCopy.small @{par} HD.small Hear.small @{par} Help.small Hippo.small @{par} Home.small Humans.small @{par} IBM.small IconInfo.small @{par} Ink.small Ink&Feather.small @{par} LhAadd.small LhAext.small @{par} Mail.small MakeDir.small @{par} Menu.small Modem.small @{par} Monitor.small Mouse.small @{par} Move.small MoveAs.small @{par} Movie.small MUI.small @{par} MultiView.small Music.small @{par} None.small Optimize.small @{par} Opus.small Pack.small @{par} Pack2.small Panther.small @{par} PaperClip.small Parent.small @{par} Pattern.small Pie.small @{par} Piggy.small Play.small @{par} Prefs.small Print.small @{par} Protect.small Protect2.small @{par} Purge.small Relabel.small @{par} RemoveSizes.small Rename.small @{par} ReScan.small Root.small @{par} Sample.small Select.small @{par} Sheep.small Show.small @{par} Sparks.small Stacker.small @{par} Star.small System.small @{par} Toggle.small Tool.small @{par} @{fg fill}ToolBarArrow.image@{fg text} Tut.small @{par} UnPack.small UnPack2.small @{par} Version.small Wand.small @{par} Yield.small @{par} @{par}These images are just a bunch which @{"myself and Leo Davidson" LINK "Author"} made (mostly a cut & paste operation from the @{"many archives" LINK "Thanks"} of beatifully drawn @{"MWB" LINK "MWB"} icons which exist on Aminet), however, some are hand-drawn and all in all this archive still took quite a bit of time to compile. @{par} @{par}@{b}NOTE:@{ub} The @{fg fill}ToolBarArrow.image@{fg text} is a replacement for the cycle gadget in the @{par} lister_toolbarmenu (the name must remain @{b}as is@{ub} in order to work). @ENDNODE @NODE "Patterns" "Patterns" @TOC "Download" @{par} @{fg shine}Patterns@{fg text} @{par} @{par}This archive includes the following patterns: @{par} @{par} ClassicDOpus.pat ClassicMarble.pat @{par} DOpusStone.pat DOpusStone0_LoRes.pat @{par} DOpusStone1_LoRes.pat DOpusStone2_LoRes.pat @{par} DOpusStone4_LoRes.pat DOpusEmboss.pat @{par} Paper.pat PaperDOpus.pat @{par} PaperDOpusBlue.pat PaperDOpusPink.pat @{par} Stone.pat @{par} @{par}The @{b}ClassicMarble@{ub} and @{b}Paper@{ub} were obtained from other archives, however, I fixed them so they repeated properly. The @{b}DOpusStone#_LoRes@{ub} patterns were designed by @{"Leo" LINK "Author"} for all you people with LoRes screens (the # indicates the number of DOpus hedgehogs on the pattern). @ENDNODE @NODE "WBStartup" "WBStartup" @TOC "Download" @{par} @{fg shine}WBStartup@{fg text} @{par} @{par}This archive includes the following items in the WBStartup drawer: @{par} @{par} Opus5_Startup Opus5_Startup.info @{par} @{par}I've just put this here, because I think that the icon I drew for the Opus5_Startup is better than the one which is provided (you may not?). @ENDNODE @NODE "Requirements" "System Requirements..." @{par} @{fg shine}System Requirements...@{fg text} @{par} @{par}Since this archive requires DOpus5, you must have the minimum requirements as stated in the DOpus5 manual: KickStart 2.04 or higher, 1 Meg RAM, and a Hard Drive. However, a recommended configuration@{b}°@{ub} includes 4 Meg RAM and at least a 68030. @{par} @{par}@{b}°@{ub}Recommendation by Amiga Computing's Frank Nord - Issue 88, page 33. @ENDNODE @NODE "Installation" "Installation" @{par} @{fg shine}Installation@{fg text} @{par} @{par}If anyone thinks that this archive requires an installation script then mail me. I think most people would actually prefer to install this stuff themselves. @{par} @{par}All you need to do is copy this stuff where you want it. One recommendation, however would be to rename the images drawer in DOpus5: to something else and then copy the included images drawer into DOpus5: (since this is where DOpus looks for icons be default). @{par} @{par}If the brushes and pictures are not compliant with your palette then you will want to use @{"DIF" LINK "DIF"} (possibly in conjunction with @{"PaletteShove" LINK "PS"}) - both programs and their respective documentation are included in this archive in @{"c (dir)" LINK "C"}). @{par} @{par}As for the @{"pictures and the guide" LINK "DownLoad"}, you can delete them when you're done with them (although you might like to hang on to the @{"Buttons_Template" LINK "DownLoad"} which will serve as a good template for drawing your own icons and an index when you are not sure which icon to pick). @ENDNODE @NODE "HintsTips" "Hints & Tips & HELP!" @NEXT "HintsTips" @{par} @{fg shine}Hints & Tips & HELP!@{fg fill} @{par} @{par} · If you decide to use the included toolbar icons, it is a good idea to delete @{par} or rename the @{b}default images drawer@{ub} in @{b}DOpus5:@{ub}. Then copy the @{"Images" LINK "Images"} drawer @{par} included in this archive into your @{b}DOpus5:@{ub} directory (since this is where @{par} DOpus looks for images by default). @{par} @{par} · If you want to make a drive bank (similar to DOpus4) you can use a button @{par} bank with the @{b}ScanDir@{ub} command (see my @{"DOpusScreen.pic" LINK "DownLoad"}). @{par}@{fg text} @{par} · Is it possible to have drive icons on the DOpus screen which do not @{par} necessarily exist on WorkBench? For instance, for an assign? @{par}@{fg fill} @{par} -> Answered by @{"Leo Davidson" LINK "Author"}: You can @{b}leave out@{ub} any directory, so long as @{par} it has an ICON. Directories left out on the DOpus screen are @{b}NOT@{ub} left @{par} out on the Workbench (unless you also leave them out on the Workbench). @{par} BUT, you can't leave things out which do not have an icon. @{par}@{fg text} @{par} · Is everyone having the same problems I am with snapshoting icons in DOpus.. @{par} wherever you snapshot the windows in DOpus is where they end up on the @{par} workbench? Am I doing something wrong? @{par}@{fg fill} @{par} -> Answered by @{"Leo Davidson" LINK "Author"}: Yes, there is currently no way around this :( @{par}@{fg text} @{par} · What happened to the SWAPDIR and COPYDIR commands? Is there a way to @{par} impliment this through other commands (to operate on the source and the @{par} destination)? @{par}@{fg fill} @{par} -> Answered by @{"Greg Perry" LINK "LeoD5PM_OrderInfo"}: the COPYWIN command may be envoked via ARexx. @{par}@{fg text} @{par} · Does it annoy anyone else that when you click on the button banks that they @{par} remain highlighted and then you have to go back and click on the window? @{par} Once the operation has been preformed, the window in which the action was @{par} preformed should be rehighlighted...right? @{par} @{par} · Can you save the prefs so that the clock remains ON? @{par}@{fg fill} @{par} -> Answered by @{"Leo Davidson" LINK "Author"}: Yes, but you must quit DOpus for the changes to @{par} remain in effect. @{par}@{fg text} @{par} · I wish you could get rid of the borders on the button banks...what a waste @{par} of space (it would nice to have a feature like ToolManager)! @{par} @{par} · How do you replace the cycle gadget in the ToolBarLister? @{par}@{fg fill} @{par} -> Answered by @{"Leo Davidson" LINK "Author"}: See @{"Images" LINK "Images"} - at the bottom of the page, there @{par} is a note on how to replace the cycle gadget. @{par} @{par} · Here are a couple of great tips from @{"Leo Davidson" LINK "Author"}: @{par} @{"How to add an LHA destination-path file-requester to a button (or menu) " LINK "LHADest"} @{par} @{"An LHA button (or menu) which creates seperate directories for each archive" LINK "LHADir"} @{par}@{fg text} @{par} · Why do all screens remap whenever you change resolution (i.e. in paint @{par} programs) whenever DOpus is running? For instance if you change the page @{par} size in OpalPaint while the DOpus window is open then Workbench remaps it's @{par} screen, however if DOpus is iconified this doesn't happen (it is very @{par} annoying and it slows things down!). @{par} @{par} · In order to play @{b}The Settlers@{ub} (© BlueByte), you must kill DOpus or your @{par} machine goes Balistic (WHY, does it have something to do will the PAL mode?) @{par} @{par} · Push this button @{b}->@{ub} @{bg fill}@{" " LINK "GURU"}@{bg background} to see a crash which @{"MCP (© ALiEN DESiGN)" LINK "MCP"} reported: @{par} Can anyone tell me what it mean? @{par}@{fg fill} @{par} -> Answered by @{"Greg Perry" LINK "LeoD5PM_OrderInfo"}: GPSoftware believes these bugs have been fixed @{par} for 5.11 (available on Aminet). @{par}@{fg text} @{par} · When you load DOpus after bootup, one window becomes the source and the @{par} other becomes the destination (that is good); however if you launch DOpus @{par} from the WBStartup, then both windows are off when you deiconify it (is @{par} there someway to fix this...if not what the hell is the good of that... @{par} I mean when I open DOpus I obviously want to use it, so why should I have @{par} to click on both windows to get the source and destination?) @{par} @{par} · Where do you put the PublicScreen name for the {Qs} delimiter? I've tried: @{par} command {@{b}Qs@{ub}Workbench} @{par} command {@{b}Qs@{ub}"Workbench"} @{par} command {@{b}Qs@{ub}}Workbench @{par} command {@{b}Qs@{ub}}"Workbench" @{par} but none of these work...help! @{par}@{fg fill} @{par} -> Answered by @{"Leo Davidson" LINK "Author"}: {Qs} is like the {Qp} command. It inserts @{par} DOpus's public screen name into the command string. It doesn't check if @{par} a named public screen exists or anything like that. @{par} @{par} @{b}NOTE@{ub}: You can't use {} sequenses in "command" type commands. This is a @{par} common misconception. @{par}@{fg text} @{par} · Has anyone ever had any luck installing @{"LhaDir.DOpus5" LINK "EVLhaDir"} and getting it to work @{par} on the first try? I found this utility quite difficult to get going - maybe @{par} it is just me, but for those of you who are having trouble, I've provided @{par} @{"some hints to help you install LhaDir.DOpus5" LINK "InstallLhaDir"}. @{par}@{fg fill} @{par} · DOpus will CRASH if you: select more than one icon (containing tooltypes), @{par} use IconInfo, select but do not edit the first tooltype in the first icon, @{par} select SAVE (even though nothing has been altered) and DOpus will crash - @{par} GURU # 8100 0005. (I accidentally found this out the hard way, but YOU have @{par} been warned). @{par} @{par} · If you have @{"CheckGuide" LINK "CheckGuide"} you can save yourself some time by adding it to DOpus @{par} as either a Button or User-Menu item (@{"click for an example of how to do it" LINK "DCG"}). @{par} @{par} · Check out @{"Jonathon Potter's tip on how to add DIF to DOpus" LINK "DIF"}. @{par} @{par} · Check out this great tip on @{"How to get DOpus to Parse commands" LINK "Parse"}, by @{"Leo" LINK "Author"}. @{par} @{par} · @{"Leo" LINK "Author"} provides an explanation of DOpus5's @{"FileTypes" LINK "Filetype"}. @{par} @{par}@{fg text} @{par} If you have answers for any of these @{"I'd love to hear from you" LINK "Author"}. Or if you have @{par} something which you would like to share with others, contact @{"me" LINK "Author"} and I'll @{par} include it in this section. @{par} @{par}@{fg shine}@{b}All Users of DOpus5@{ub}: The patch for DOpus5.11 is now on Aminet (Dopus511.lha)!!@{fg text} @ENDNODE @NODE "Thanks" "Thanks to..." @NEXT "Thanks" @PREV "Thanks" @{par} @{fg shine}Thanks to...@{fg text} @{par} @{par} · @{"Leo Davidson" LINK "Author"} - for his ideas & efforts and for making this archive possible! @{par} · Jonathan Potter - for writing @{"DIF" LINK "DIF"} for us (and for DOpus of course ;) @{par} Greg Perry - for all your help. @{par} and the rest of the Gang at @{"GPSoftware" LINK "GPSoft"} (Leigh Malpas and Mark Anderson) for @{par} creating the most powerful/useful Amiga Utility! @{par} for creating the most powerful/useful Amiga Utility! @{par} · Cléo Saulnier - for writing @{"PaletteShove" LINK "PS"}! @{par} · PRoToCoL - for the RomanIcons9 DOpus images (listed in @{"History - Revision 4" LINK "History"}) @{par} · Edmund Vermeulen - for his amazing/useful @{"LhaDir.DOpus5" LINK "EVLhaDir"} Arexx scripts! @{par} · Marin "XEN" "Hutti" Huttenloher - for creating the @{"MagicWB" LINK "MWB"} standard! @{par} · Roman Patzner - no MWB credits would be complete without this guy! @{par} · Eddy Carroll - for creating @{"CheckGuide" LINK "CheckGuide"} @{par} · Chad Randall - for Iconian and PictIcon! @{par} · Jan-Tore, Richard "FOXX" Harris, Øyvind Falch, Martin "GASTON" Rolfsmeyer, @{par} Alisdair Walker, Mario Cattaneo, Timo C. Nentwig and all other icon artists @{par} on the globe!! @{par} · Anyone who sent me mail about this archive. @{par} · Hello to :) @ENDNODE @NODE "CheckGuide" "CheckGuide by Eddy Carroll" @NEXT "CheckGuide" @PREV "CheckGuide" @TOC "Thanks" @{par} @{fg shine}CheckGuide 1.0 -- Checks AmigaGuide files for common errors @{par} @{par} by Eddy Carroll, September 1994. Freely distributable.@{fg text} @{par} @{par}Introduction @{par} @{par}If you've ever tried creating even a modestly sized AmigaGuide file by hand, @{par}you'll have discovered that it can be quite difficult to keep track of all the @{par}various links and cross references. As your help file gets larger, it gets @{par}increasingly harder to ensure that you have remembered to reference all the @{par}nodes in the file from at least one place, and haven't left any unresolved @{par}links. @{par} @{par}CheckGuide is a simple utility that can detect several common errors in @{par}AmigaGuide files. The errors it can detect are: @{par} @{par}· Extra plain text between an \@ENDNODE and \@NODE (AmigaGuide won't allow such @{par} text to ever be displayed) @{par} @{par}· Nodes that are defined but not referenced from any other node. Unless your @{par} program directly instructs AmigaGuide to access such nodes, the user won't @{par} easily be able to access them. @{par} @{par}· Links to help nodes that aren't defined within the file. @{par} @{par}· Open braces with no preceding \@ character (usually a simple typo). @{par} @{par}· \@{" Button "} constructs with no LINK command (an easy mistake to make if @{par} you're entering a lot of them). @{par} @{par}All of these options can be selectively enabled or disabled. @{par} @{par} @{fg shine}CheckGuide was used in the creation of @{b}THIS@{ub} document!@{fg text} @ENDNODE @NODE "Distribution" "Distribution" @NEXT "Distribution" @PREV "Distribution" @{par} @{fg shine}Distribution@{fg text} @{par} @{par}I won't bother to put a whole wack of stringent regulations on this archive which I would never be able to enforce, and to which none of you would pay any attention, however I would ask you to please have the courtesy to distribute this archive with @{b}all of its files and documentation in tact@{ub}, as they are intended to help those who obtain this piece of software. Thanx! @{par} @{par}@{b}SYSOPS@{ub}: Please name this achive MWOpus_6.lha if you post it. Thanx in advance! @{par} @{par}Directory Opus 5.0 is ©1995 by @{"GPSoftware" LINK "GPSoft"}. @{par}See @{"How to buy Directory Opus 5" LINK "LeoD5PM_OrderInfo"}. @ENDNODE @NODE "Disclaimer" "Disclaimer" @NEXT "Disclaimer" @PREV "Disclaimer" @{par} @{fg shine}Disclaimer@{fg text} @{par} @{par}THERE IS NO WARRANTY FOR THE SOFTWARE TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHERE OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE SOFTWARE "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE SOFTWARE IS WITH YOU. SHOULD THE SOFTWARE PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. @{par} @{par}IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY REDISTRIBUTE THE SOFTWARE AS PERMITTED BELOW, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE SOFTWARE (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE SOFTWARE TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. @{par} @{par}Please see @{"Nudel Speaks..." LINK "Nudel"} @ENDNODE @NODE "History" "History" @NEXT "Author" @PREV "HintsTips" @{par} @{fg shine}History@{fg text} @{par}@{fg fill}Release 6:@{fg text} @{par} @{par} · Added @{"DIF by Jonathon Potter" LINK "DIF"}. @{par} · Added the following brushes: LHAadd, LHAext, Protect2, Edit2, Feather1, @{par} Feather2, Ink, Ink&Feather. @{par} · Updated the @{"Buttons_Template" LINK "DownLoad"}. @{par} · Fixed the @{"PolarSamll-Prop" LINK "Fonts"} font. @{par} · As always, updated guide (@{b}NOTE@{ub}: @{"Micro R&D" LINK "LeoD5PM_OrderInfo"} phone number typo fixed "1234 @{b}-@{ub}> @{par} 1243"). Also added @{"DOpus5 Review" LINK "Review"} & @{"Children of the Storm" LINK "COTS_Charity"} nodes. Check out @{par} the new @{"Hints" LINK "HintsTips"} as well! @{par} · New @{"NudelScreen.pic" LINK "DownLoad"}. @{par} · Included some @{"patterns" LINK "patterns"} for DOpus' background. @{par} · Renaming archive (MWB_DOpus5#.lha @{b}-@{ub}> MWB_DOpus_#.lha) to avoid confusion for @{par} later releases (ie. MWB_DOpus510..?). @{par} · Renamed PalPatch to PaletteShove (so it is not confused with a PAL (50Hz) @{par} patch :) and included seperate guide for it in the @{"c drawer" LINK "C"}. @{par} · Fixed up the CLI and DOpus drawer icons and added an icon for @{"PaletteShove" LINK "PS"}. @{par} · Added an @{"ARexx drawer" LINK "ARexx"} with two scripts written by @{"Leo Davidson" LINK "Author"}. @{par} @{par}@{fg fill}Release 5:@{fg text} @{par} @{par} · Added the following brushes: CopyWin, Version, Modem, Pack2, UnPack2, Help @{par} and Device2. @{par} · Replaced AddIcon.small. @{par} · Modified the FastView.small image. @{par} · Deleted the Chip image - useless and didn't look good as a cropped image. @{par} · Remodelled and renamed DOpus5Icons (now called Button_Template). Also added @{par} all new buttons (listed above) to the template. @{par} · As always, updated guide (more hints, etc - DOpus5.11 users should note the @{par} change in @{"Nudel's Lha ext routine" LINK "LHADir"} @{fg fill}"_{o}/"@{fg text} @{b}-@{ub}> @{fg fill}"{o-}/"@{fg text}). @{par} · Updated my screen snapshot (woopee!). @{par} @{par}@{fg fill}Release 4:@{fg text} @{par} @{par} · Added PalPatch by Cléo Saulnier. @{par} · Added the following brushes: Balance, Balls, Chip, ClipBoard, ClipBoard2, @{par} Demon, Dice, Drawer, FastView, FX, HamLab, Hippo, Opus, Panther, Pattern, @{par} PaperClip, Star and Tut - Drawn by @{"Roman" LINK "Thanks"}, altered for DOpus by @{"PRoToCoL" LINK "Thanks"}. @{par} · Updated DOpus5Icons Template to include the above images. @{par} · Updated guide (more hints, full SMARTWRAP supported by @{"Nudel" LINK "Author"},...) @{par} @{par}@{fg fill}Release 3:@{fg text} @{par} @{par} · Updated the guide (added some more hints, history, fixed some errors...) @{par} · Added the fonts directory @{par} · Included a better snapshot of my DOpus screen @{par} · Added a snapshot of Nudel's DOpus screen @{par} · Added the ClickMe for color and pointer stuff @{par} · Included Drives icons (in Drives drawer as a request) @{par} @{par}@{fg fill}Release 2:@{fg text} @{par} @{par} · Added a few more button icons (since the History node wasn't added until @{par} release three, I can't remember which ones...sorry). New icons were also @{par} added to the template @{par} · Expanded the Hints&Tips section @{par} · Added the Drives drawer (as a request) @{par} · Fixed some minor details in my DOpus icons and drew one for the DOpus tool @{par} (Only the commodity icon was included in Release one) @{par} · Added better DOpus.guide.info @{par} · New snapshot image included @{par} @{par}@{fg fill}Release 1:@{fg text} @{par} @{par} · First release (everything was new @{fg shine}8@{fg text}@{b})@{ub} @ENDNODE @NODE "Author" "The Authors" @NEXT "Author" @PREV "Author" @{par} @{fg shine}The Authors@{fg text} @{par} @{par} @{fg fill}Trevor Morris@{fg text} A3000 030 25MHz @{par} Comp 4, Site 7 OpalVision @{par} RR#1 Oromocto, NB 14M RAM, 320M HD @{par} E2V 2G2 Canada @{par} @{fg shine}Email: a3nb@unb.ca@{fg text} @{par}@{u} @{uu} @{par} @{par}Thanks a million to @{fg fill}Leo Davidson @{fg shine}(@{b}EMail:@{ub} leo@hampschl.demon.co.uk, @{b}IRC handle: @{ub} NUDEL)@{fg text} who orginally started the enclosed template & developed the @{i}standards @{ui} which I have also decided to use in this archive. Leo has not only granted me full permission to include and alter his material, but has also answered many of my @{"questions" LINK "HintsTips"} related to the operation of DOpus5 (so if I can't answer your questions then bug this guy ;)! @{par}@{u} @{uu} @{par} @{par} @{fg fill}Also check out the following archives by Trevor Morris:@{fg text} @{par} @{par}For lots of pix, icons, and stuff to go with MagicWB, grab up @{b}MagicWBStuff3.lha @{ub} from Aminet in pix/icon! AND @{b}MagicWBStuff4.lha@{ub} has just been uploaded to Aminet in pix/mwb!! @{par} @{par}Check out @{b}Ent1701D.lha@{ub} in gfx/3dobj on Aminet for a gorgeous Imagine model and preview of the StarShip Enterprise! @{par} @{par}If you are running MCP by ALiEN DESiGN then you'll want my @{b}MCPGuide.lha@{ub} in docs/help on Aminet! @{par}@{u} @{uu} @{par} @{par}Directory Opus 5.0 is ©1995 by @{"GPSoftware" LINK "GPSoft"}. See @{"How to buy DOpus 5" LINK "LeoD5PM_OrderInfo"}. @ENDNODE @NODE "MWB" "MagicWB is © by Martin Huttenloher" @NEXT "MWB" @PREV "MWB" @{par} @{fg shine}MagicWB is © by Martin Huttenloher@{fg text} @{par} @{par} @{par} @{b}MagicWB V2.0 @{par} ============@{ub} @{par} @{par} @{par}The definitive WB-Enhancer no Amiga can do without. MagicWB is a full replacement for the graphic user interface of the Workbench and has become the standard on the Amiga. @{par} @{par}MagicWB 2.0 is completely restructured on a new color-allocation scheme which more than doubles the speed of the WB and reduces chip-consumption to only a third compared with all previous versions and also features a highly improved color palette. MWB 2.0 introduces a never-before-seen standard for over four dozen of new image-drawers to achieve a more diversified look on your WB. More icons, dock-brushes, a dozen of new patterns, fonts and a AA-support complete this special product. @{par} @{par}To get the 'real' look and feel of MagicWB, you should make sure that... @{par} @{par} · ...you have set the MagicWB-Palette. Do this by clicking on the 'ClickFor @{par} Colors' icon. @{par} @{par} · ...you have set the resolution of your Workbench to a aspect ratio near 3:4 @{par} like 640x480, 800x600 or 1024x768. @{par} @{par} The demo-version can be found on Aminet biz/demo/MagicWB20d.lha. @{par} @{par} @{b}MagicWB is © by Martin Huttenloher.@{ub} @ENDNODE @NODE "LHADest" "Adding LHA with a destination file requester" @PREV "LHADest" @NEXT "LHADest" @TOC "HintsTips" @{par} @{fg shine}How to add an LHA destination-path file-requester to a button (or menu)@{fg text} @{par} @{par}To add an LHA command to DOpus with a destination file requester use the @{par}following to define either a button, a menu item or a gadget: @{par} @{par} TYPE: COMMAND: @{par} @{b}------------------------------------------------------------------------------@{ub}@{fg fill} @{par} @{b}AmigaDOS@{ub} - FailAt 21 @{par} @{b}AmigaDOS@{ub} - sys:c/RequestFile DRAWER={d} PATTERN=#?.(LHA|LZH) NOICONS @{b}@{fg shine}->@{ub}@{fg fill} @{par} PUBSCREEN=DOPUS.1 SAVEMODE >PIPE:LHA_{Qp} @{par} @{b}AmigaDOS@{ub} - IF FAIL @{par} @{b}AmigaDOS@{ub} - QUIT @{par} @{b}AmigaDOS@{ub} - ENDIF @{par} @{b}AmigaDOS@{ub} - sys:c/LHA -r -x u "`Type PIPE:LHA_{Qp}`" {O}@{fg text} @{par} @{b}------------------------------------------------------------------------------@{ub} @{par} @{par}Check the following flags: @{par} @{par} @{fg fill}· CD source @{par} · Output to window @{par} · Window close button@{fg text} @{par} @{par}@{b}NOTE:@{ub} Make sure you change the @{b}sys:c/@{ub} in the last command line to point to @{par} the path where @{b}Lha@{ub} can be found on @{i}your@{ui} machine. @{par} @{par} the @{fg shine}@{b}->@{fg text}@{ub} means @{b}continued on the next line@{ub}; however, you would @{b}type this @{par} all on one line@{ub}. @{par} @{par} the @{b}RequestFile@{ub} command comes with OS3.x. @ENDNODE @NODE "LHADir" "An LHA button (or menu) which creates seperate dirs for each archive" @PREV "LHADir" @TOC "HintsTips" @NEXT "LHADir" @{par} @{fg shine}An LHA button (or menu) which creates seperate directories for each archive@{fg text} @{par} @{par} TYPE: COMMAND: @{par} @{b}------------------------------------------------------------------------------@{ub}@{fg fill} @{par} @{b}AmigaDOS@{ub} - sys:c/LHA -M x {fu} {o-}/@{fg text} @{par} @{b}------------------------------------------------------------------------------@{ub} @{par} @{par}Check the following flags: @{par} @{par} @{fg fill}· Output to window @{par} · Window close button @{par} · CD destination@{fg text} @{par} @{par}@{b}NOTE:@{ub} Make sure you change the @{b}sys:c/@{ub} to point to where the Lha command @{par} can be found on @{i}your@{ui} machine. @ENDNODE @NODE "GURU" "DOpus GURU Reported by MCP 1.05" @PREV "GURU" @TOC "HintsTips" @NEXT "GURU" @{par} @{fg shine}DOpus GURU Reported by MCP 1.05@{fg text} @{par} @{par}@{fg fill} MCP GuruHistory @{par}@{fg text}@{b}=============================================================================== @{par}@{ub}Date : Tuesday 06-Jun-95 08:59:37 @{par}Task : 075C6008 "dopus_buttons" @{par}Error : 8000000B (DEADEND) @{par}By : System @{par}Cause : Line 1111 Emulator error @{par}@{b}------------------------------------------------------------------------------- @{par}@{ub}Date : Friday 09-Jun-95 19:40:06 @{par}Task : 075747E0 "Dopus5:DirectoryOpus" @{par}Error : 80000004 (DEADEND) @{par}By : System @{par}Cause : Illegal instruction @{par}@{b}------------------------------------------------------------------------------@{ub} @ENDNODE @NODE "MCP" "MCP by ALiEN DESiGN" @PREV "MCP" @TOC "HintsTips" @NEXT "MCP" @{par} @{fg shine}MCP by ALiEN DESiGN@{fg text} @{par} @{par}MCP is a definitive system control program which patches many WB functions to optimize speed and functionality on any Amiga machine - GET IT! @{par} @{par}You can find it on any Aminet site or, @{par} @{par}How to contact the Authors of @{b}MCP@{ub}: @{par} @{par} @{fg shine}Stefan "zerocom" Sommerfeld Michael "Oxygene" Knoke@{fg text} @{par} Kaulbachstr. 3 Berlinerstr. 33 @{par} 14612 Falkensee 14612 Falkensee @{par} Germany Germany @{par} @{par}@{fg fill}Phone: +49-[0]3322-202452 Phone: +49-[0]3322-22440@{fg shine} @{par}EMail: zerocom@cs.tu-berlin.de EMail: knoke@cs.tu-berlin.de @{par} @{par} Vincent "fOX" Schöttke @{par} @{par} @{fg fill}Phone: +49-[0]3322-3202@{fg text} @{par} @{par} @{par}Support BBS: @{fg fill}MagiC P0ti0N!@{fg shine} +49-[0]3322-208768@{fg text} ( 2400-28800 ) Type @{b}update@{ub} on login, and you will be admitted to a part of the BBS where you can report bugs or suggestions, or download the newest version of @{fg fill}MCP@{fg text}. @ENDNODE @NODE "GPSoft" "Directory Opus V5.0 ©1995 by GPSoftware. All rights reserved" @PREV "GPSoft" @NEXT "GPSoft" @{par} @{fg shine}Directory Opus V5.0 ©1995 by GPSoftware. All rights reserved@{fg text} @{par} @{par}Directory Opus 5 and it's manual are © Jonathan Potter and GPSoftware, Brisbane, 1995. All Rights Reserved. The software was written by Jonathan Potter. Graphic design by Leigh Malpas. Manual written by Greg Perry. Help file system written by Mark Anderson and Greg Perry. @{par} @{par}See @{"How to buy Directory Opus 5" LINK "LeoD5PM_OrderInfo"}. @ENDNODE @NODE "Nudel" "Support the Amiga, or use PC's forever!" @PREV "Nudel" @{par} @{fg shine}Support the Amiga, or use PC's forever!@{fg text} @{par} @{par}An open message regarding the future of the Amiga in connection with piracy, and in particular that of Directory Opus 5. @{par} @{par}Written by @{"Leo Davidson" LINK "Author"} (P0T-NOoDLE / Gods'Gift Utilities / Anthrox) @{par} @{par}E-Mail: @{fg fill}leo@hampschl.demon.co.uk@{fg text} (Until around July'95) @{par}IRC: @{fg fill}@{b}Nudel@{ub} in #Amiga@{fg text} @{par} @{par}Contents: @{par} @{par} @{" Main Text " LINK LeoD5PM_Message} @{par} @{" Jonathan Potter's Message to AR " LINK LeoD5PM_JPMSG} @{par} @{" How to order DOpus5 " LINK LeoD5PM_OrderInfo} @{par} @{par}DOpus5 is a work of art: probably the most configurable, versatile, and useful program ever written, but you'll never see anything like it again on the Amiga unless you let the developers know that the Amiga isn't a lost cause. @ENDNODE @NODE "LeoD5PM_JPMSG" "Jonathan Potter speaks" @TOC "Nudel" @{par} @{fg shine}Jonathan Potter speaks@{fg text} @{par} @{par}From Amiga Report, 3.09 @{par}@{b}==============================================================================@{ub} @{par} @{fg fill}POTTER ON PIRACY @{par} By Jonathan Potter@{fg text} @{par}@{b}==============================================================================@{ub} @{par} @{par}Jason, @{par} @{par}I just thought I'd write a quick letter to AReport to express my disappoint- ment with the actions of some members of the Amiga community. As you may be aware, Directory Opus 5 has just been released. This is a significant upgrade; the program has been completely rewritten after more than 6 months of hard work. Less than a week after its release, pirate copies have already spread around the world. @{par} @{par}Software piracy is a problem as old as computers themselves, and of course we would be naive not to expect it. But to have the program appear so quickly on pirate BBS' makes me wonder just exactly how tuned in to reality some people are. The position of the Amiga at the moment is exceptionally precarious, as I would have thought was obvious to anybody, and the only thing keeping it alive are the developers who still believe in the platform. @{par} @{par}Many times in the past six months I've had to ask myself why I was wasting my time programming for a nearly-dead computer. Obviously, I do it because I enjoy it, but the hard truth is that I have to justify it in dollar terms - philanthropy is all well and good, but if I don't make any money I don't eat. The Amiga market is already small enough without the added burden of rampant piracy to contend with. @{par} @{par}I guess all I'm trying to do is to appeal to people; if they really believe in the Amiga, and really want to see it continue, don't contribute to its down- fall by ripping off the hard work of the very people who are keeping it alive. @{par} @{par}Regards, @{par} @{par} Jonathan Potter @{par} @{par} +@{b}------------------------------------------------------------------@{ub}+ @{par} | @{fg shine}Jonathan Potter yeti@adam.com.au +61-412-845-696@{fg text} | @{par} +@{b}------------------------------------------------------------------@{ub}+ @ENDNODE @NODE "LeoD5PM_Message" "They can't keep the faith if they can't eat" @TOC "Nudel" @{par} @{fg shine}They can't keep the faith if they can't eat@{fg text} @{par} @{par}"What pirates must remember is that it takes 12 months of bloody hard work to get a product to market, then more time to get some money in etc. Development of Dopus 5 was actually funded by GPFax. It is quite simple if people keep pirating our Amiga software we will just have to give up and go elsewhere. It would be a pity." @{par} @{par} Dr Greg Perry @{par} @{par} GPSoftware, PO Box 570, Ashgrove, Qld Australia 4060 Ph/fax +61 7 3661402 @{par} Internet: zzgperry@mailbox.uq.oz.au @{par} @{par} @{par}First let me state: I'm not attempting to create any illusions here. I'm no angel, and I haven't bought every piece of software I own. I wish I had the money to, and if I were not a student with zero real-income I would certainly buy a hell of a lot more software. This message is aimed at those who can easily afford to buy software and support their machine but don't. Of course some people are worse than others. Think of those selling pirate copies of other people's software and making so much money that they can afford to buy mega-expensive pieces of hardware and all kinds of stuff through virtually no work of their own (there IS such a thing as a free-lunch). @{par} @{par}Enough moral high-horsing, let's talk. @{par} @{par}The Amiga is in a bad state. It isn't a machine which is in every other house, office, or school. Everyone who has really got past inserting a game at the kickstart screen knows that the Amiga has the best OS on any home computer (sure, AmigaOS has holes in it at the moment, but I'd rather wear a raincoat with holes than one that dissolves in water!). Another thing the Amiga has going for it is the great support by PD and shareware programmers - people who really love the machine and write software for that single reason. Let's face it, if you look at how much software comes out (from MicroSoft alone!) on the PC, commercial software development on the Amiga has all but stopped in comparison. (Of course, bar a few games, there's very little I could do on the PC that I would not do better on an Amiga, despite the vast amounts of releases). I would go as far as to say that if all commercial software development on the Amiga stopped today, I would continue to use the Amiga for a long time to come, using the PD software, and writing my own stuff until I could afford my own SiliconGraphics machine, because I'm used to a REAL computer, without bottlenecks, workarounds, bad standards, and inherently- flawed hardware covered with a paper-thin gloss of leading edge technology. There is some incredible shareware software out there, but none of these people are earning enough from it to support them. Broadly speaking, there is a point where projects become so large that none but the rich-hobbyist can afford to make them just for fun and the love of a machine. Unless you've already made your fortune, you are simply not able to spend a year developing a program, because you won't even be able to pay the bills to keep your machine fed with electricity (well, OK, my SAmiLog3 is taking about 2 years to develop, but so far it could have all been done in 2 weeks!). @{par} @{par}So isn't it easy to understand why so many people have dumped the Amiga? No matter how much you love the machine, you can't make a living out of it if not enough people buy the software. The fact that developers who have experienced the @{b}JOY@{ub} of programming on the Amiga can write software in the @{b}DREADFULL@{ub} PC environment is an indication of just how much piracy has affected the Amiga market. On the PC, so many people own the machine that stupid things like a Screen-Blanker, which would never be a commercial product on the Amiga, have huge price tags slapped on them, and the stupid market buys it. (This is more or less what the PC is based on: a STUPID market who are happy to follow all the trends because they don't know that there is another way of doing things). Because the PC market is so huge now a product will make money even if only a tiny percentage of people buy it. Piracy may be a Robin Hood operation on the PC, but on the Amiga it is suicide for those who love the machine, and a disappearing way to make some quick money for those who don't give a stuff about it (notice how most of the parasites who were in the scene to make money have left the Amiga for the PC (of course, a large number of very talented and great people have also gone that way too, to our loss)). @{par} @{par}It's even worse on the PC, but I still think that the price of games on the Amiga is too high, especially considering many will last two weeks at most for someone like me. But on the Amiga we simply cannot complain about the cost of productivity programs. Let's look at Directory Opus as an example. This is a program which PC users would kill for, (and they would have to) yet it cost about the same price as many PC games! Walk into a software shop some day and have a look at just how much serious software costs on the PC. Of course, just because our (better) software is cheaper than the PC's doesn't mean it is reasonably priced. What is reasonable is an individual's choice, but I personally feel that a program such as Directory Opus is very good value for money. Not everyone likes DOpus, especially the controversial new version (believe me, use it for a week and you won't ever want to go back to DOpus4!), and it's always been a program which has polarized opinions. You either love it or hate it, because a file management program is something that if you use at all, you probably use every single day you turn your computer on. When you use something as good as DOpus every day, and it costs as little as it does, there is very little excuse for not buying it. @{par} @{par}If you're using a pirate copy of Directory Opus 5, just think about this. Is the cost (and I would hardly call it expensive!) really so great, considering how much work has gone (and continues to go) into the program which you use every day and wouldn't be the same without? If you're using DOpus5 it is because you think it's the best, not because there is nothing else to do the job, as there are many, many other file-management programs for the Amiga. It isn't like people using AmiExpress because it's virtually the only option, despite the fact that it is incompetently programmed and designed (if it is designed at all). If I hated DOpus as much as I hated AmiExpress when I used that every day too, I would never have paid a penny for it and certainly wouldn't be urging anyone else to. However, I have a great deal of respect for the people behind DOpus, and I wish that they were getting rich from it (but not so rich that they wouldn't talk to me any more :), because they certainly deserve to. @{par} @{par}I know a lot of people read AmigaReport, so many of you will have seen the message from Jonathan Potter about how damaging the almost instant pirate release of DOpus was, and how upset he was personally. Now it seems that an internal beta copy has even been released (there isn't even honour among thieves). I've been talking to both Jonathan and Greg Perry a great deal during the past few weeks and they have been both helpful with my problems and open to my suggestions, not to mention extremely friendly and willing to take the time to talk to me. You wouldn't get that from a lot of other companies, and I guess it's a little ironic that the smaller companies can often offer better tech-support. Greg and Jonathan have both done a great deal for me, and this is my small way of doing (trying to do) something in return. @{par} @{par}I urge people not to release any more of the updates of DirectoryOpus. Those who would actually want the updates must like the program enough to be able to spend the small amount of money it takes to actually buy the program. You can not even use the excuse that you're doing it for respect, because virtually ANYONE who knows how to use DMS could release a new copy of DOpus. @{par} @{par}For the same reasons, I urge people not to release copies of the manual, as this and tech-support are about the only incentives to buy the program for people who don't even care about the developers and the future of the Amiga. There are many features of DOpus5 that you will probably never find without reading the manual. Incidentally, there will not be an electronic (AmigaGuide) version of the ARexx commands appendix for the sole reason of sales. Think about what that means. (Looks like I'm too late in saying this, someone has already released the manual :( ). @{par} @{par}Come on, if someone with as little money to spend as me at the moment can manage to pay the small cost, surely you can too. @{par} @{par}The only other reason that you should buy your copy of DOpus5 (for those who really just don't care about anyone or thing but themselves) is that Directory Opus has to be the most frequently "faked" program of all time. If I had a pound for ever fake copy (some with a virus attached) of DOpus that I've seen on certain BBS, I would be able to buy myself a second copy. If you want to be able to TRUST your copies, you have to BUY them. (For those of you thinking things are dandy, BOTH of the TWO versions claiming to be Directory Opus v5.1 are BOTH @{b}BETA@{ub} versions, and not the real v5.1!! (YES, even the "German release" one). How does that make you feel about trusting new versions? Next time it could look just as much like an official release but wipe your harddrive). @{par} @{par}DOpus5 is STILL being worked on and updated. Think how many of the great Amiga programs you use on a daily basis are still being updated. We really cannot afford to let any more developers leave our platform if we want our software to continue to be up there with the other machines. @ENDNODE @NODE "LeoD5PM_OrderInfo" "Where to order DOpus5" @{par} @{fg shine}Where to order DOpus5@{fg text} @{par} @{par}To contact @{b}GPSoftware@{ub}, mail/fax Greg Perry: @{par} @{par}@{fg fill} Dr Greg Perry@{fg text} @{par} GPSoftware @{par} PO Box 570 @{par} Ashgrove @{par} Qld @{par} Australia 4060 @{par} @{fg text}Ph/fax:@{fg fill} +61 7 3661402 @{par} @{fg text}Internet:@{fg fill} zzgperry@mailbox.uq.oz.au@{fg text} @{par} @{par} @{par}@{fg shine}To order Directory Opus 5 (GP Software):@{fg text} @{par} @{par} Small-Biz Software Phone: @{fg fill}+61 (74) 919 190@{fg text} @{par} PO Box 24 Fax: @{fg fill}+61 (74) 926 860@{fg text} @{par} Golden Beach @{par} Queensland @{par} AUSTRALIA 4551 @{par} @{par} @{par} Wizard Developments Phone: @{fg fill}+44 (01) 322 272908@{fg text} @{par} PO BOX 490 Fax: @{fg fill}+44 (01) 322 2811311@{fg text} @{par} Dartford @{par} Kent DA1 2UH @{par} ENGLAND @{par} @{par} @{par} Schatztruhe Phone: @{fg fill}+49 201 788778@{fg text} @{par} Veronikastr 33 Fax: @{fg fill}+49 201 798447@{fg text} @{par} 45131 Essen @{par} GERMANY @{par} @{par} @{par} Micro R&D Phone: @{fg fill}+1 308 745 1243@{fg text} @{par} 721 'O' Street Fax: @{fg fill}+1 308 745 1246@{fg text} @{par} Loup City @{par} NE 68853 @{par} USA @{par} @{par} (Taken from the registration card - I hope this information is accurate) @ENDNODE @NODE "EVLhaDir" "LhaDir.DOpus5 1.0" @NEXT "EVLhaDir" @PREV "EVLhaDir" @{par} @{fg shine}LhaDir.DOpus5 1.0@{fg text} @{par} @{par}LhaDir.DOpus5 is an ARexx script for @{"Directory Opus 5" LINK "GPSoft"} that allows you to show the contents of Lha archives in an Opus lister window and operate on the files and directories inside the archive as if it is a normal directory. @{par} @{par}With LhADir.dopus5 you can: @{par} @{par}· Browse through the directory structure of an archive file. @{par}· Double click on files in an archive to read/play/show/etc (any DOpus internal command). @{par}· Delete files and directories with the Delete button. @{par}· Extract/add files and directories with the Copy or Move buttons. @{par}· Double clicking on files and directories works. @{par}· Can be compiled with the Rexx Plus Compiler for optimum speed. @{par}· Works with more than one copy of Directory Opus running. @{par}· View an archive in an archive by extracting it from it's mother archive to the current destination directory. @{par}· Deletes strange filenames like '#?' without a problem. @{par}· Create new (empty) Lha archives with the MakeDir button. @{par}· Copy/move between two archives (via T:) @{par}· Datestamps, attributes and comments are listed and preserved correctly. @{par}· Localized (Dutch catalog provided). @{par} @{par}LhaDir.DOpus5 is Copyright © 1995 by EAV Productions International. Placed in the public domain. No restrictions on distribution or usage. @{par} @{par}Author: @{fg fill}Edmund Vermeulen@{fg text} @{par} Primulastraat 2 @{par} 3202 RN Spijkenisse @{par} The Netherlands @{par} Tel. 01880-13925 @{par} @{par}Fidonet: @{fg fill}2:286/407.48@{fg text} @{par}Internet: @{fg fill}edmundv@grafix.xs4all.nl@{fg text} @{par} @{par}@{fg shine}@{b}NOTE@{ub}: LhaDir.DOpus5 is included with the DOpus511.lha patch on Aminet@{fg text} @ENDNODE @NODE "InstallLhaDir" "Some hints to help you install LhaDir.DOpus5" @TOC "HintsTips" @NEXT "HintsTips" @PREV "HintsTips" @{par} @{fg shine}Some hints to help you install LhaDir.DOpus5@{fg text} @{par}@{fg fill} @{par} -> Make sure you edit the header in each script to suit your own machine (ie @{par} you may have to change the @{b}LhaCommand =@{ub} from sys:c/Lha to Work:Arc/Lha @{par} or something like that). @{par} @{par} -> Make sure you add the following lines to your startup-sequence (or user- @{par} startup): @{par} @{fg shine}sys:system/rexxmast >nil: @{par} c:runback >NIL: sys:rexxc/RX DOpus5:ARexx/LhaHandler.rexx @{par} c:path sys:Rexxc add@{fg fill} @{par} @{par} You may also wish to add @{fg shine}c:resident c:Lha FORCE@{fg fill} to speed things up. @{par} @{par} Remember, however, that your paths may be different! @{par} @{par} -> Make sure that you select the @{b}ARexx@{ub} command Function Editor cycle gadget @{par} and that every command (which you wish to pass to LhaDir.DOpus5) calls @{par} LhaDir.DOpus5 (ie. DOpus5:ARexx/LhaDir.DOpus5 @{b}MakeDir@{ub} {Qp}). @{par} @{par} -> If you still can't get things to work, select the @{b}Output to Reader@{ub} option @{par} in the function editor to find out what is going on (this is useful for @{par} debugging at any time and not just for LhaDir.DOpus5). @{par} @{par} -> As a recommendation, I suggest you make a seperate LHA_COMMANDS button @{par} bank, since LhaDir.DOpus5 slows regular functions down and sometimes it @{par} does some weird things like prompt you for a destination dir when copying @{par} files!? See my @{"DOpusScreen.pic" LINK "DownLoad"} for an example. @{par}@{fg text} @ENDNODE @NODE "DIF" "DIF V1.0 © 1995 Jonathan Potter" @NEXT "DIF" @PREV "DIF" @{par} @{fg shine}DIF V1.0 © 1995 Jonathan Potter@{fg text} @{par} @{par}This is a little program designed to allow easy conversion of images designed for one screen depth to images suitable for another screen depth. For example, the Magic Workbench icons for DOpus 5 (by Trevor Morris & Leo Davidson) are all designed for an eight colour screen. If your DOpus screen (or Workbench screen) is more than eight colours, these images will be displayed with the wrong colours. DIF can remap these images to allow their use on a deeper screen. @{par} @{par}@{fg fill}Usage : DIF FROM/A,TO/A,DEPTH/N/A@{fg text} @{par} @{par} @{b}FROM@{ub} - source image file @{par} @{b}TO@{ub} - destination image file @{par} @{b}DEPTH@{ub} - desired depth of the converted image @{par} @{par}The input file must be an IFF ILBM image. You will normally specify the depth of your Opus (or Workbench) screen for DEPTH - for instance, my Workbench screen is 32 colours, so I would specify a DEPTH of 5 (if you don't understand the term "depth", tough luck @{fg shine}@{b}:@{ub}@{fg text}) @{par} @{par}While this program will work on any depth source image, and produce any depth destination image, it is really designed for converting 8 colour images to work on a screen of more than 8 colours. For that reason, the results when using any other depth input image are undefined (well, they're not undefined, but I've never tried it, so who knows what will happen @{fg shine}@{b}:@{ub}@{fg text}) You can also specify a smaller depth than the original image, in which case the higher bitplanes will simply be tossed away. @{par} @{par}The easiest way to use this program is probably to set up a DOpus button, with a function similar to the following : @{par}@{u} @{uu} @{par} @{par} @{fg fill}AmigaDOS DIF {fu} {d}{o} {RsEnter desired depth:4} @{par} @{par} Flags : Do all files @{par} Output to window @{par} Rescan dest @{par} Window close button@{fg text} @{par}@{u} @{uu} @{par} @{par}DIF works on both RLE-compressed images and non-compressed images (like brushes). @{par} @{par}If you have any problems, you can reach me at: @{fg shine}jpotter@birch.apana.org.au@{fg text} @ENDNODE @NODE "Review" "Directory Opus 5 Reviewed - Amiga Computing Issue # 88, page 33-34" @NEXT "Review" @PREV "Review" @{par} @{fg shine}Directory Opus 5 Reviewed - Amiga Computing Issue # 88, page 33-34@{fg text} @{par} @{par} @{fg fill}MAGNUM OPUS@{fg text} @{par} @{par}Frank Nord closely examines the latest episode in the Directory Opus saga. @{par} @{par}Directory Opus has been long awaited. Since the first murky screenshots appeared in magazines late last year, breath has been baited, wallets clutched, murmurs of concern were heard when Jonathon Potter announced he wasn't going to be using his stablemates of old, Inovatronics, to distribute this muiti-tasking beast. @{par} @{par}But here it finally is, and the metamorphosis has been even greater than could be imagined. We were all ready for a larger amount of configurability, prepared for a new windowing system, we had even set our shoulders in grim determination when we heard you could have more than the standard two directory windows open at the same time. What I certainly wasn't prepared for was the fact that Directory Opus 5 could replace Workbench altogether. That's right, you don't even need to load Workbench at all. @{par} @{par} @{fg fill}ANOTHER WORLD@{fg text} @{par} @{par}If you choose the 'Replace Workbench' option, everything seems perfectly normal, there doesn't seem to be any difference. But as soon as you open a window on your Workbench screen, oh boy, you sure are in a different world. By default, DOpus doesn't fill its windows with icons. Although you do have that option, the default is actually to fill the windows like, well, like a file manager should. A burst of little icons fills the top edge of each window, letting you perform all the essential operations any file manager should be capable of such as copying, renaming and deleting. @{par} @{par}Running DOpus as a Workbench replacement seems like a really neat idea at first. Anyone who has played with Norton Desktop for Windows will know what I mean. It's funky to open your hard drive's window and find everything listed as text, with the ability to copy, move, rename, delete, etc. right at your finger tips in the window itself. @{par} @{par}It's also nice not to have your entire Workbench screen filled with windows as you move through sub-directories. DOpusbench will let you do this if you want, but normally it will only replace the files shown in the window with the sub- directory's contents, as you would expect. But soon you get a bit fed up at the loss of all those customisations you had on Workbench. @{par} @{par}Apart from its looks, things have changed under the bonnet too. Directory Opus 5 is now a fully multi-threaded, multi-tasking package with the ability to perform several operations concurrently. One of the screenshots on these pages shows the contents of a disk being copied to a directory on my hard drive, while another pair of windows are being used to copy some files from another partition into RAM:. This ability is particularly useful for anyone who wants to copy files onto several disks at once, because you would be able to have as many copy operations going as the number of floppy drives you had. @{par} @{par} @{fg fill}SLIGHT CONFUSION@{fg text} @{par} @{par}The manual could stand some improvement. It's very nicely laid out, but the index is fairly poor and there are several typos and things that look like typos, but are, in fact, design elements. They have used the Right Amiga symbol that appears in the menus to show that you are reading about a menu item. But this symbol is usually used in a manual to show the keyboard shortcut for that command, which makes things even more confusing because they don't show the shortcut - they are just in the manual on their own. One of the real disasters comes when you read the information about the internal 'Finish Section' command - it gave an example that sounded very useful indeed. The manual said you could get DOpus to beep when it had finished an operation, and the example given was using LHA. @{par} @{par}I use LHA all the time and thought that given DOpus 5's ability to multi-task, it would be very useful to get it to beep on finishing the LHA compressing or decompressing. I followed the instructions down to the last letter until I came to the internal command 'Beep.' There isn't one. @{par} @{par} @{fg fill}OUTSTANDING@{fg text} @{par} @{par}There are some really nice features with this new version. The ability to perform several operations at once must rank highest on the list, but there are some outstanding tools that vie with multi-tasking for attention. The ability to drag and drop more than one file at a time is a definite bonus, along with filetypes which are saved out with icons. @{par} @{par}I think we will soon be seeing collections of these filetypes uploaded to Aminet, performing such esoteric functions as displaying imagine objects or HTML pages and so on. The fact that the built-in viewer now supports datatypes should be applauded and will certainly cut down on the amount of configuration that needs to be done to show GIF, PCX and Jpeg pictures or play VOC or WAV sounds. I liked the new ability to use the keyboard to navigate DOpus' interface. @{par} @{par}Instead of swapping source and destination windows as it used to do in DOpus 4, the space bar now switches on keyboard mode. To show this you are given a little arrow cursor in the active directory window which you can move up and down with the cursor keys. Selecting files is done with the return key and double-clicking on them can be emulated with the Enter key on the numeric pad. @{par} @{par}The context sensitive on-line help is also useful, although I would have liked to see slightly more index entries. One other thing I liked was that DOpus 5 now caters for the three button mouse owner too. Most buttons can be configured for three different operations depending on the mouse button used, giving even more flexibility (all the same, I think I'll still use my middle mouse button to swap between screens rather than use it in DOpus). @{par} @{par}However, if you've seen the requirements for DOpus at the bottom of this page, you will have noticed that you can no longer take it with you when you go to rescue a friend's hard drive. The price for all these added elements is the increased size of the application. It still comes on one disk - it only takes up about 800k of hard drive space - but that doesn't really leave enough room on the disk to install workbench as well. @{par} @{par}One of the other features which had me slightly confused until I ran DOpusbench is an icon on DOpus's screen called 'Favourites.' This is a 'Program Group.' The reason for it became clear when I realized that running DOpusbench means you lose ToolsDaemon and ToolManager even though DOpus has the ability to show entries added to the Tools menu. @{par} @{par} @{fg fill}IN THE WRONG DIRECTION?@{fg text} @{par} @{par}As you can probably guess from the text on these pages, DOpus 5 has got me really frustrated. It certainly is different from DOpus 4 and pretty much any other file manager, and is a lot more ambitious in its scope. But it is so much of a paradigm shift that it makes me wonder if anyone is going to use it to its full potential. @{par} @{par}I have always plugged DOpus 4 in my various reviews and features, basically telling everyone that if they were to only ever buy one piece of software, then that should be it. So I, possibly more than others, feel disappointed that the clean interface DOpus 4 presented to the world has been swapped for something that could almost have been designed by Macro Systems (no offence, guys). Directory Opus' changes make we wonder about change for change's sake. Progress has once again triumphed over common sense, and what was an incredibly good file manager with only two flaws (not selecting .font files when the font directory was chosen and not being able to discern between two floppies with the same name) has become something that will require more maintenance than your hard drive. @{par} @{par}I think what will happen for the vast majority of people is that they will load their DOpus 4 config file and then not bother with the new configuration abilities of DOpus 5. And guess what? DOpus 5 still can't tell the difference between two floppies with the same name. @{par} @{par} @{fg fill}PROGRAMS@{fg text} @{par} @{par}These program groups are where you are supposed to drag your most-used programs to save you having to click through directories to get at them. You can have as many as you like and they can be called whatever you like, but it reminded me too much of Windoze, so I gave up on the idea of using them almost as quickly as I did on using DOpusbench. @{par} @{par}The default configuration is, unlike DOpus 4's, pretty unusable, so there is no alternative but to configure the program to meet your needs. However, configuration has gone from one button in the bottomright corner of the DOpus 4 interface to not one, not two, but eight separate menu items scattered from one end of the title bar to the other. I understand that each of these preferences tools are discrete, multi-tasking programs in their own right, but couldn't we have had them all in one place? @{par} @{par}One of the really annoying problems with this schizophrenic configuration method is that keyboard short cuts get duplicated. On my DOpus I like to have the Delete key as the shortcut for deleting files, surprisingly enough. When I hit the Del key in DOpus 5, however, I get a Lister Format window appear. Now, I've scoured the manual for a way to stop this from happening so that I can be re-acquainted with my Del key, but all it smugly tells me in the manual is the fact that not only can I use the Lister Status PopUp menu to call up this Lister Format window, I could also double-click with my right mouse button in the lister. @{par} @{par}What it doesn't say is that the Del key also works, nor does it tell me how to stop it from working. Two methods for calling up this window seem ample to me, why (article ends here...really, Trevor Morris). @{par} @{par}Essential: Kickstart 2.04, 1 Mb RAM, Hard drive @{par}Recommended: 4 Mb RAM, 68030 @{par} @{par}@{fg fill}The bottom line@{fg text} @{par}@{b}Product:@{ub} Directory Opus 5 @{par}@{b}Supplier:@{ub} Wizard Developments @{par}@{b}Price:@{ub} £49.99 @{par}@{b}Tel:@{ub} 01322 277908 @{par} @{par}@{fg shine}Ease of use @{b}6@{ub} @{par}Implementation @{b}8@{ub} @{par}Value for money @{b}8@{ub} @{par}Overall @{b}8@{ub}@{fg text} @ENDNODE @NODE "DCG" "How to add CheckGuide to DOpus" @NEXT "DCG" @PREV "DCG" @{par} @{fg shine}How to add CheckGuide to DOpus@{fg text} @{par} @{par} TYPE: COMMAND: @{par} @{b}------------------------------------------------------------------------------@{ub}@{fg fill} @{par} @{b}AmigaDOS@{ub} - Work:Utilities/CheckGuide {F} @{par} @{fg text}@{b}------------------------------------------------------------------------------@{ub} @{par} @{par}Check the following flags: @{par} @{par} @{fg fill}· CD source @{par} · Output to reader @{par} · Do all files@{fg text} @{par} @{par} @{b}NOTE:@{ub} Do not forget to change @{b}Work:Utilities/@{ub} to the proper source on @{b}your@{ub} @{par} drive. @ENDNODE @NODE "COTS_Charity" "Children of the Storm" @NEXT "COTS_Charity" @PREV "COTS_Charity" @{par} @{fg shine}Children of the Storm@{fg text} @{par} @{par}@{u} @{uu} @{par} @{par}@{b}NOTE@{ub}: This information hasn't been updated for a long time, but the ideas are still the same - only more things have been accomplished since it was written. The address at the end IS still correct. @{par} @{par}There is also now an E-Mail address and WWW page for the charity, but I'm afraid I don't have the info with me. If you would like to know more about it or contact any of the people via e-mail instead of snail-mail, please e-mail me (@{fg fill}@{"leo@hampschl.demon.co.uk" LINK "Author"}@{fg text}) and I will get the details. @{par}@{u} @{uu} @{par} @{par}I know that most you out there won't pay anything at all, but I am doing this in the hope that at least a few people donate even a small amount of money, because every little penny can be put to some good! @{par} @{par}Please, at least read about the charity, Children of the Storm. I not going to say that anyone who doesn't send off some money should feel really guilty, just that anyone who does send off some money should feel really great, knowing that they've helped someone out. @{par} @{par}Even if you don't want to send any money (for whatever reasons), you could always send a letter of support, or spread the word to other people. @{par} @{par}I have never asked for any money for all the work I put into these utils, and I do not gain anything from your donations except knowing that I have helped some people out. I know that my work is used by a lot of people and that because of that, I have helped them out in one way or another, so why not help someone else now! Scene members do have hearts, don't they? Make it worth my while typing all of this info! @{par} @{par}@{b}BTW@{ub}: In the case of Next2Active, the amount of work I have done is tiny, please don't think that all my utils are this tiny!) @{par} @{par} @{par} @{fg shine}Who are the CHILDREN OF THE STORM?@{fg text} @{par} @{par}In Britain this year, over a hundred young children will be accepted into the country by the Home Office, seeking political asylum. They may be just eleven or twelve years old. Often they have travelled across continents alone. They may have just lost their parents, seen brothers and sisters brutally murdered, or suffered beatings or torture themselves. Whilst our Government offers them basic shelter and the long-term possibility of war-refugee status in the UK, they can live here for weeks and months under the threat of instand deportation, sometimes forced to live rough without provision for food, clothing and other simple necessities. Far from their home and their culture, hungry, fearful and insecure, these children attempt, often with an astounding dignity and human spirit, to survive and grow despite the weight of unbearable memories they carry deep within... @{par} @{par} @{fg shine}Background@{fg text} @{par} @{par}Since 1989 several members of the staff at Hampstead School have been building up a support network for refugee children attending the school who have little or no family back-up, few resources, and are often in a critical emotional state. @{par} @{par}Achievements to date include: @{par} @{par}· Providing food, shelter and income for regugee children, working with the @{par} Tavistock Clinic which is providing counselling services and advising @{par} teachers, @{par}· Forging links with the local authority (London Borough of Camden) to put @{par} children and carers in touch with any relevant support agencies, @{par}· Establishing a social club in which refugee children are offered additional @{par} tuition and emotional support by their fellow pupils at the school, @{par}· Acting as the children's advocates in relation to housing, social services, @{par} social security etc. @{par} @{par} @{fg shine}Status@{fg text} @{par} @{par}Registered Charity number 1035774 @{par}Consultant: Sheila Kasabova, Refugee Co-ordinator, Camden Council @{par}Consultant Psychologist: Maureen Fox, Consultant Psychotherapist at the @{par} Tavistock Clinic @{par}Legal Consultants: Bindmans (services at no charge) @{par}Accountants: Alan Heywood, Chartered Accountants (services at no charge) @{par} @{par} @{fg shine}Aims and Objectives@{fg text} @{par} @{par}1. To continue to build on the existing project achievements outlined, @{par}2. To extend knowledge acquired by staff and pupils of the school to other @{par} schools and bodies dealing with refugee children through teacher-training @{par} programmes, conferences, booklets etc. @{par} @{par} @{fg shine}Summary of Projects in Progress or Anticipated@{fg text} @{par} @{par}1. Publishing a booklet: the Hampstead Story, by those involved in the @{par} project, outlining the problems Hampstead School itself has encountered @{par} with refugee children and strategies for dealing with them. To be @{par} delivered free of charge to every school in the country. @{par} Cost: £9,000. Project in progress. @{par}2. Expanding the social club outlined above to include students from other @{par} local schools including primary schools. @{par} Cost: £50 per month. Project in progress. @{par}3. Employing a full-time counsellor at Hampstead School to counsel children @{par} and train staff in counselling techniques. @{par} Cost: £38,000 pa. @{par}4. Employing an administrative assistant to manage the charity. @{par} Cost: £20,000 pa. @{par}5. Holding a national conference on problems faced by refugee children in @{par} Britain, and strategies for overcoming them, open to any persons or @{par} organisations working with regugee children (teachers, welfare and social @{par} servicesm volunteer groups etc.) @{par}6. Employing a fundraiser. @{par} Cost: £15,000 pa. @{par} @{par} @{fg shine}Conclusion@{fg text} @{par} @{par}The project originated at Hampstead School is the only one of its kind. Due largely to recent wide coverage and acclaim in local, national and international media, it is increasingly being recognised by local authorities as a role model for other schools. Central to the project's success is teacher Athy Demetriades, who has assisted on training days in schools around the country. Regular requests for her to speak now come from solicitors, educational psychologists, welfare services and radio programmes as well as schools. On average, she fulfils one such engagement per week. She is, in effect, becoming one of few experts on the all-round care of children suffering a unique combination of problems - the destruction of the childhood together with the loss of citizenship and any automatic recourse to law and welfare that citizenship entails. @{par} @{par}Sponsorship for Children of the Storm would ensure that the work originated at Hampstead School can continue. It would also lay the foundations for a training programme enabling teachers and carers right across the country to provide the basics of security and education to refugee children. @{par} @{par} @{fg shine}Further Information@{fg text} @{par} @{par}This is basically what you would find on the letter head: @{par} @{par}@{fg fill}Children Of The Storm @{par}Hampstead School @{par}Westbere Road @{par}London @{par}NW2 3RT @{par}United Kingdom@{fg text} @{par} @{par}There is a telephone and fax number, but I feel that it would be unwise to @{par}include it here, as there are a few idiots out there who might abuse it. @{par} @{par}Charity registration number 1035774 @{par} @{par}Patrons: @{par}@{fg fill} Dame Judi Dench, @{par} Lindsay Duncan, @{par} Geraldine James, @{par} Griff Rhys Jones, @{par} John Gordon Sinclair.@{fg text} @{par} @{par}Trustees: @{par} @{fg fill}A. Demetriades, @{par} A. Berkeley, @{par} M. Janota Bzowski, @{par} S. Pickford, @{par} G. Walker, @{par} M. Johnson, @{par} F. Capone.@{fg text} @{par} @{par}Consultants: @{par} @{fg fill}M. Fox THE TAVISTOCK CLINIC, @{par} M. Martin LEGAL ADVISER, @{par} A. Heywood A.C.A, @{par} S. Kasabova CAMDEN L.E.A.@{fg text} @{par} @{par} The address is up there, so go on, donate! @{par} If you think you can offer something other than money, write! @{par} @{par} I want to say a huge thanks to anyone who does donate some money. @{par} @{par} Thanks for at least reading this... and sorry for any mistakes in @{par} the above text - my typing can go a bit haywire sometimes!! @ENDNODE @NODE "PS" "PaletteShove V1.0 © Cléo Saulnier" @NEXT "DIF" @PREV "DIF" @{par} @{fg shine}PaletteShove V1.0 © Cléo Saulnier@{fg text} @{par} @{par}Please read the @{b}PaletteShove.guide@{ub} in the @{"c drawer" LINK "C"} of this archive. @ENDNODE @NODE "Parse" "Parse Command" @TOC "HintsTips" @NEXT "HintsTips" @PREV "HintsTips" @{par} @{fg shine}"Parse" Command@{fg text} @{par} @{par}This function can be used when you want to run a program for which you have not set up a button, but which requires arguments. It can also be used for running a program on the selected file(s) (ie. basically for when you are too lazy to open a shell window!). @{par} @{par}For example, if you select a file called @{b}Widget.Nad@{ub} and use Parse, you will be asked for a string to go before and after it. This will be built into a command-line which is then executed. Let's say that @{b}Widget.Nad@{ub} was a picture you wanted to show with @{b}ViewTek@{ub}, and you wanted to use ViewTek's @{b}NoBusy@{ub} option, you would enter @{b}Viewtek@{ub} in the first requester and @{b}NoBusy@{ub} in the second one. @{b}Note@{ub} that you are not limited to single word answers - this is just an example: @{par} @{par}@{fg fill}Viewtek Widget.Nad NoBusy@{fg text} @{par} @{par}...would then be executed, and the picture displayed. @{par} @{par}As another example, say that you have downloaded a new program called @{b}NadBuster@{ub} which requires a shell-argument @{b}Config@{ub} to tell it where its config file is. Let us also say you have created and saved this config as @{b}RAM:NadBuster.config@{ub}. All you have to do is select the @{b}NadBuster@{ub} program file, click on Parse, leave the first requester blank (just hit RETURN), and type @{b}Config RAM:NadBuster.config@{ub}. @{par} @{par}@{fg fill}NadBuster RAM:NadBuster.config@{fg text} would then be run. @{par} @{par}OK, I hope you get the idea now. Want to know how many lines the actual function which took so long to describe is?... Just one @{fg shine}@{b}:@{fg text}@{ub}-). @{par}(It is not complicated - just very usefull!). @{par} @{par} TYPE: COMMAND: @{par} @{b}------------------------------------------------------------------------------@{ub}@{fg fill} @{par} @{b}AmigaDOS@{ub} - {RsEnter String To Preceed Filename} {o} {RsEnter String To @{b}@{fg shine}->@{ub}@{fg fill} @{par} Follow Filename}@{fg text} @{par} @{b}------------------------------------------------------------------------------@{ub} @{par} @{par}Check the following flags: @{par} @{par} @{fg fill}· CD source @{par} · Do all files @{par} · No file quote (** Optional, sometimes you'll want this off **) @{par} · Output to window @{par} · Window close button@{fg text} @{par} @{par}@{b}NOTE:@{ub} the @{fg shine}@{b}->@{fg text}@{ub} means @{b}continued on the next line@{ub}; however, you would @{b}type this @{par} all on one line@{ub}. @ENDNODE @NODE "FileType" "FileType" @TOC "HintsTips" @NEXT "HintsTips" @PREV "HintsTips" @{par} @{fg shine}FileType Priorities@{fg text} @{par} @{par}Special thanks to @{"Jonathan Potter" LINK "Thanks"} for helping me out with some of the details used in this section. @{par} @{par}Usually, you will want all of your filetypes to have a priority of zero. However, the filetype priorities become very useful when you have one filetype which is a subset of another. For example, 24-bit IFF-pictures are a subset of regular IFF-pictures, and while only a 24-bit picture will match the first type, ANY type of IFF-picture will match the second. @{par} @{par}I've got about 8 different picture viewers on my harddrive. On my setup, PPShow seems to be the best one for showing 24-bit IFF-pictures, but for other things I prefer to use Viewtek. Obviously I've set the 24-bit IFF-picture filetype to use PPShow, and the IFF-picture datatype to use Viewtek, but this isn't enough. DOpus will act on the first filetype which matches the file, so you have to do something to ensure that a 24-bit IFF-picture isn't matched by the IFF-picture filetype! This is simple to do - just put the 24-bit filetype at a higher priority. My IFF-picture filetype is at priority 0 (zero), so I set the 24-bit filetype to 1 (one), and everything works fine. @{par} @{par}Similarily, I have a filetype which matches ASCII text and extracts binary data from the file in one of two ways: UUEncoded data via drag-n-drop and User2 (which is "Unpack" on my setup). Because a UUEncoded file would match the standard ASCII filetype, I set the UUEncoded filetype to a higher priority. @{par}@{u} @{uu} @{par} @{par} @{b}Undocumented Feature@{ub} @{par} @{par}DOpus5 has some internal filetypes which exist even if you were to delete ALL the @{b}DOpus5:Filetypes/@{ub} files. @{par} @{par}Essentially there are two sets of filetypes: those set at priority -125, which display pictures, play sounds, etc., and the "last-resort" filetype at priority -127, which just calls @{b}SmartRead@{ub} if a file was @{b}Double-Clicked@{ub}, and @{b}Copy@{ub} if it was @{b}Drag-n-Drop@{ub}ped. @{par} @{par}@{b}NOTE@{ub}: The "last-restort" will only get used if NO filetype matches are found @{par} (ie. if none of the -125 filetypes are matched). @{par} @{par}The filetype priority -126 is left unused so that you may create a filetype which will match ALL files (MatchName #?) and define an action (ie. for Double- Click, User1, Drag-n-Drop, etc) you wish preformed if absolutely none of the other filetypes match the slected file. @{par} @{par}@{b}NOTE@{ub}: In order to have an action preformed by the filetype priorities greater @{par} than -126 (ie -125 and up), you must have actions defined for them. @{par} @{par}Since the priority -127 filetype actions for Double-Click and Drag-n-Drop are what most people would want as the "last-resort," your -126 filetype probably won't define anything for those actions. However, the -127 filetype has nothing defined for the @{b}UserX@{ub} actions. This means that if you do @{b}User1@{ub} on a file and none of the filetypes match the file (AND you have a User1 action defined), absolutely nothing will happen. So to MAKE something happen by @{i}default@{ui} on the @{b}UserX@{ub} actions, you may define them in your -126 filetype. @{par} @{par}@{b}FINAL NOTE@{ub}: You DO NOT have to define every action for each filetype. For @{par} example, my @{i}default@{ui} filetype has the Drag-n-Drop action defined as @{par} the internal @{b}Copy@{ub} command. If you are editing a filetype, say for @{par} IFF-pictures, and you want them to be copied when Drag-n-Drop, you @{par} can leave the Drag-n-Drop action blank because the pictures will @{par} drop through the IFF-picture filetype and be caught by your @{i}default @{ui} @{par} filetype (assuming they don't match another filetype on the way, of @{par} course!). @{par}@{u} @{uu} @{par} @{par}I know this stuff sounds complicated (try explaining it @{fg shine}@{b}:@{ub}@{fg text}), but if you require help/clarification then feel free to contact @{"one of us" LINK "Author"}. @ENDNODE