Martin_Head wrote:While I think the idea of predefined 'levels' is nice. Somehow I can't see it working in practise.
On one hand your basically dictating to uses what software they must run on their systems. I personally mainly use QPC2, and half of the software you put as 'must have' I don't have installed, and I don't want to. If I try to use some software that needs a particular extension/tooolkit, then I will load it .
I dont want to dictate, simply to get some kind of sanity. The extensions I list are my
basic assumptions for a minimally, functional system, and my plea is for yall to discuss, and see if we can arrive at some common assumptions.
So you mainly use QPC2. Whats not to like about my Level 3: (SMSQ/E), QLib_run, Turbo_sms_Toolkit, FileInfo2, ENV_bin, ptrmen, Qptr, menu_rext, sound4_bin, sound_bin? With those toolkits loaded it should be possible to test and run most recent software without rebooting between sessions. (A number of these extensions are "systems extensions", ie they cant be compiled into a program, but must or should be loaded at boot time.)
On the other hand, I can see programmers inventing new levels, just to suit what ever program they are writing. Or just ignoring the levels entirely.
Thats pretty much what the world looked like before M$ became dictatorial, in about 1994, and imposed a semblance of sanity.
This helped the computer revolution to take off! (And weve hated them ever since..)
The "QL" isnt so much a platform as a number of splatforms! When preparing some program for distribution, do I target those four people, or the two people in the other camp, or the solipsist in the middle?
I'm more inclined to having a Minimum or Recommended system specification, in the programs documentation. Like PC software.
I rest my case.