defaults
Posted: Tue May 20, 2008 6:22 pm
It would be nice if the commandline version did not require so many arguments to be routinely supplied.
I mention the commandline version specifically because I don't think one should need a GUI or other support script just for more convenient defaults.
maxshapes
It seems better to have a moderate default for frequent/casual experimentation and reserve potentially enormous numbers for when one really means it.
I know it involves an arbitrary choice, but pretty much anything is better than a 20 tempfile surprize. I favour a low starting value of 10,000, which I can later raise when useful.
There's always the old "-m 0" convention for "No, really. I don't care how big it gets."
border
25% is just silly. That's 75% of the total area.
Besides which, it's a flat colour; cfdg is not really needed for that.
I almost always use 0.
Actually, the options are rather strange: -8px,0,8px,25%.
I probably would have gone with <signed-byte>px, maybe using the higher magnitudes for percentages, say sign(N)(|N|-100)%, i.e.+/- [1,27]%
hmm
It's probably not warranted at this stage, but user prefs/config files can be useful for supplying arbitrary defaults.
I don't actually know whether you think of cfdg as a complete application or just an engine to be used by a separate interface. Obviously, I regard it as the former.
I mention the commandline version specifically because I don't think one should need a GUI or other support script just for more convenient defaults.
maxshapes
It seems better to have a moderate default for frequent/casual experimentation and reserve potentially enormous numbers for when one really means it.
I know it involves an arbitrary choice, but pretty much anything is better than a 20 tempfile surprize. I favour a low starting value of 10,000, which I can later raise when useful.
There's always the old "-m 0" convention for "No, really. I don't care how big it gets."
border
25% is just silly. That's 75% of the total area.
Besides which, it's a flat colour; cfdg is not really needed for that.
I almost always use 0.
Actually, the options are rather strange: -8px,0,8px,25%.
I probably would have gone with <signed-byte>px, maybe using the higher magnitudes for percentages, say sign(N)(|N|-100)%, i.e.+/- [1,27]%
hmm
It's probably not warranted at this stage, but user prefs/config files can be useful for supplying arbitrary defaults.
I don't actually know whether you think of cfdg as a complete application or just an engine to be used by a separate interface. Obviously, I regard it as the former.