@database "mConfig - instrukcja uûytkownika" @author "Michaî Durys (Misha/ECS) @$VER: mConfig.guide 1.0 @node main "mConfig - instrukcja uûytkownika" ________.___________________________________________________________________@{fg text} / \ / -\ @{b}EL CONDOR SOFTWARE@{ub} /-----\ presents / -----\ @{fg shine}mConfig@{fg text} /_________\ @{fg highlight}Let your Workbench surprise you!@{fg text} --/ _________\-------------------------------------------------------------@{fg text} /__________ \ email: elcondor@polbox.com /_______________\ web: www.polbox.com/e/elcondor @{b}@{fg shine} .-------------------------------. -------------( Introduction ) `-------------------------------'@{fg text}@{ub} @{" Overview " link description} @{" Requiments " link requiments} @{b}@{fg shine} .-------------------------------. -------------( Usage ) `-------------------------------'@{fg text}@{ub} @{" Instalation " link install} @{" Options description " link usage} @{" Examples " link examples} @{" Preparing configuration " link config} @{b}@{fg shine} .-------------------------------. -------------( Informations ) `-------------------------------'@{fg text}@{ub} @{" Distribution " link distribution} @{" Future plans " link plans} @{" Author " link author} @endnode @node description "Overview" I have my Workbench configured very nice in several versions. The problem was I couldn't choose which configuration to use. So after one day I wrote this program. mConfig is some kind of small configuration manager. It allows to change it at any time and has interesting possibility of choosing random configuration. Thanks to mConfig my Workbench looks different every time. @endnode @node requiments "Requiments" Almost none. Program requires OS 2.0 or better and some small amount of memory. I've got OS 3.0 on my Amiga and with this version program works exellent. @endnode @node install "Instalation" Just in case: copy file mConfig to C: directory. For volunteers: copy this guide somewhere. @endnode @node usage "Options description" Every program below 10KB is easy to use and mConfig isn't an exception. It's run from CLI like this: @{fg highlight}mConfig NAME,RANDOM,COPY/S,USE/S,SAVE/S,FROM/K,TO/K@{fg text} Options description: @{b}NAME@{ub} - configuration name, e.g.: Fast. This option mutualy excludes possibilty to use RANDOM option. @{b}RANDOM@{ub} - list of configuration names to choose from. Individual names have to separated by a | char, e.g.: "Foxa|Rally|Lum levi". In combination with COPY mode it's ment for use in startup-sequence to choose random configuration at startup. In my startup-sequence there's a line like this: @{fg highlight}C:mConfig RANDOM "Rally|Foxa|Lum levi|Shan|Gunbusters|Gokko" COPY@{fg text} Thanks to this after every reboot different girl looks at me from WB :). This option mutualy excludes possibilty to use NAME option. @{b}COPY@{ub} - in this mode mConfig will only copy preferences files to directory specified in TO parameter, without forcing system to use new preferences. In connection with RANDOM option it's specially useful in startup-sequence. It's rather useless after running IPrefs, since then it's equal to USE parameter. This option mutualy excludes possibilty to use USE and SAVE options. @{b}USE@{ub} - forces system to use given configuration. Configuration is saved to ENV: directory and is lost after reset (except someone has ENV: assigned to a directory on hardisk, just as I have ;)). It's default mode. This option mutualy excludes possibilty to use COPY and SAVE options. @{b}SAVE@{ub} - saves given configuration as default one. Configuration is saved in ENVARC: directory and it's kept there until the end of the world. This option mutualy excludes possibilty to use COPY and USE options. @{b}FROM@{ub} - specifies a directory from which preferences files are to be taken from. It's SYS:Prefs/Presets by default. @{b}TO@{ub} - specifies where to copy preferences files in COPY mode. Default is ENV:. @endnode @node examples "Examples" After this load of theory let's have some practice. When I'm working and I need more memory I do something like this: @{fg highlight}mConfig Fast@{fg text} After this command my Workbench turns in 'eco-mode' (8 colour screen, patterns instead of pictures and so on). Sometimes I do something totally sifferent: @{fg highlight}mConfig Dream@{fg text} After this one configuration of my dreaams loads in. Desktop looks really beatiful, but I can't do anything :(. I've mentioned several times about using mConfig in startup-sequence to choose random configuration at startup. To do this add following line to your startup-sequence, before IPrefs: @{fg highlight}C:mConfig RANDOM 'list|your|configurations|here' COPY@{fg text} @endnode @node config "Preparing configuration" Preparing configuration - it only sounds complicated :). In fact it only requires ability to use system preferences programs, and I hope that isn't too much for anyone. In theory configuration is a set of system preferences files with names begining from particular string (which is configuration name) and a suffix which determinates file type added after a '-' sign. This suffix is simply program name that generated that file (e.g. '-wbpattern.pre'). Due to those rules configuration named 'Bla' would consist such files: · Bla-wbpattern.pre · Bla-palette.pre · Bla-pointer.pre · ... Configuration doesn't have to include all possible configuration files, only those which interest you (which are to change). When you want to have configuration called 'X-rated' which only changes mouse pointer to more sexy one all you have to do is to write your pointer preferences somewhere as 'X rated-pointer.pre'. Good place for storage configuration files is 'SYS:Prefs/Presets', where mConfig searches them by default. In my opinion the best task for mConfig is to choose random configuration at boot time. Thanks to this, after every boot up another cute girl looks at me from my desktop! I've got a few these girls configurations and each of them consists of palette preferences and background preferences, e.g.: · Rally (Rally-palette.pre i Rally-wbpattern.pre) · Shan (Shan-palette.pre i Shan-wbpattern.pre) · Gokko (Gokko-palette.pre i Gokko-wbpattern.pre) · Lum (Lum-palette.pre i Lum-wbpattern.pre) In this place I'd like to advertise my collection of anime style backgrounds, which should be avaible as pix/back/AnimeOS.lha on Aminet. They are awesome! @endnode @node distribution This software is subject to the "Standard Amiga FD-Software Copyright Note". It is @{"Giftware" link AFD-copyright/MAIN 96} as defined in paragraph @{"4g" link AFD-copyright/MAIN 96}. For more information please read @{"AFD-COPYRIGHT" link AFD-copyright/MAIN} (Version 1 or higher). @endnode @node plans "Future plans" In current version mConfig does probably all it should do and it does it good. But I still have some ideas to improve it: · make mConfig some kind of complete configuration manager, with gui and other fountains. · gather all modes (COPY, USE, SAVE) in MODE parameter. · exchange RANDOM to RANDOM/M so all configuration names could written one after another, not separated with '|' All ideas for improvements are welcome and I promise to implemet them (as long as they are reasonable). Please send them to me. @endnode @node author "Author" This program was written by me - Michal Durys alias Misha/ECS. It was developed on: A1200T, 6MB RAM, 850 MB HDD, 4x CD, 1084S If you'd like to contact me then write to: @{fg highlight}misha@friko2.onet.pl@{fg text} I'd like to encourage you to visit my homepage: @{fg highlight}www.friko2.onet.pl/wa/misha/index.html@{fg text} And if you are off-line then write at address given below. Note that I guarantee only to answer letters written on disks! @{fg highlight}Michal Durys ul. Konarskiego 48/12 01-355 Warszawa POLAND@{fg text} @endnode