Path: utzoo!attcan!uunet!mcvax!kth!draken!tut!tucos!abo.fi!rosenbergr From: rosenbergr@abo.fi (Robin Rosenberg, Computer Science, ]bo Akademi) Newsgroups: comp.sys.amiga Subject: Re: More 1.4 whishes (and sw-installation procedure) Message-ID: <5970@abo.fi> Date: 3 Mar 89 11:54:49 GMT References: <5442@abo.fi> <413@antares.UUCP> <5899@abo.fi> Organization: Abo Academy, Finland Lines: 65 In article <5899@abo.fi>, vinsci@abo.fi (Leonard Norrgard) writes: > In article <413@antares.UUCP>, jms@antares.UUCP (Joe Smith) writes: >> In article <5442@abo.fi> rosenbergr@abo.fi (Robin Rosenberg, Computer Science, ]bo Akademi) writes: >>>Maybe now is the time to say what I want in 1.4 instead of asking why the >>>things aren't there when it comes. >>> ... >>>- An autoexec-directory: execute all programs and scripts in this >>> drawer on startup. Then I would only have to drag icons into this >>> directory to make them part of my startup. >> >> If this is implemented, make sure it doesn't have the same problems as the >> AUTO folder on the Atari ST. Several initialization programs will not work >> unless they are executed in a particular order. >>... > So what would the directives look like? Well, how about: > > ANYTIME -- Execute me at any point relative to the other startup > scripts in this directory, except for the FIRST script > which will always be the first. If no other type is > specified, ANYTIME is the default. > AFTER name_of_other_script -- Execute me sometime after `name_of_- > other_script' has been executed, not necessarily directly > after it. AFTER FIRST isn't needed as ANYTIME already > specifies this. > FIRST -- Obvious meaning. Only one of these in the directory though. > ANYTIME scripts will be executed after this. > SLAVE master -- This is a slave script of the `master' script. As > such, it is the `master' script's job to execute this > in a way chosen by the master script. > This is one possibe approach. Another simpler would be that the arrangement of icons would determine the order of execution. Arrange the icons in pretty rows and columns. Then execute first on first row,secons on first row... first on second row... and so on. This scheme obviously has some problems connected to it: how do we determine if an icon is on the same row or the row under it or above. A single pixel could make the difference. Is there a reasonable solution? Another would be a special program to set startup priorities. Continuing this autodrawer story. This would be a very simple solution to the problem of software installation that was discused earlier on News. An application startup icons would represent the program and when executed (in the AutoDrawer) it would do necessary assign. The user should ofcourse set these by the means of entries in the tooltypes array. Or since we have environment variables it might be better to set these than assigning everything. > While at it, please enhance the "tool types" gadget of the info program > to a couple of lines, it seems more and more programs get configured this > way, with more and more parameters to set. Yes. And let me bring up more than one info-window at once and make workbench work in parallel with the info program. And make it tell me how much files/bytes/directories there is in folders and... > Leonard Norrgaard, vinsci@abo.fi, vinsci@finabo.bitnet, +358-21-654474, EET. At least I started a discussion, didn't I? Since 1.4 isn't out we should tell CBM what we want there. They just have to pick the best ideas FOR FREE! ---- Robin Rosenberg, ]bo Akademi, FINLAND Address: Finn|, 22340 Geta, ]LAND - FINLAND or Studentbyn 40A3, 20510 ]BO, FINLAND Translation: ']' is an 'A' with a ring on top, '|' is an 'o' with two dots.