[CM] fun with CM + Linux
Tobias Kunze Briseño
t at fictive.com
Fri Dec 6 19:12:56 PST 2002
imho there should be no hardcoded defaults whatsoever, for any output
syntax. instead, output data should be only generated and placed in a
pre-defined location (a file, dac, port, socket, whatever), in some
pre-defined manner (all at once, chunked, ring-bufferd, whatever).
the user should then see to it that a suitable renderer is called upon
that data.
of course, as a matter of convenience, a hook mechanism should also be
provided that allows the user to have his renderer called
automatically. and here is where defaults can make sense, in addition
to direct specification.
likewise, a global preference should be provided to indicate whether
or not external data such as the user's and the system's settings for
specific, pre-defined MIME types (e.g., audio/midi) should be perused
to derive hook definitions.
finally, to assist the user in setting up a hook, sensible, hardcoded
'default' values could be offered as starting points for user
adjustments. this, however, is a user interface issue, not an issue
of functionality.
More information about the Cmdist
mailing list