Hey cool, answers... this list is turning into my little
treasure-chest!
Thanks for all the feedback guys... it sure helps. Guess I'll
have to outsource the var to file or reg then. I'll have to
check what serves the purpose best.
/*
It's a bit weezy, 'cause some people (like me) hate registry
accesses, on the other hand I hear from too much themers and
users the modules.ini is the most unwanted thingy around (at
least for what they think). This actually lets arrise another
question and here we go again back to litestep structuring: a
predefinable litestep config dir with all core config files
would be easiest and for what I know a common way of working
around some probs like this. It could also serve as the themer's
var-outsourcing and modules-configuration-file directory and we
would only have to set it up with some core standards so the
user can point out whichever dir he wants to use...
Aaaaarch! Is that me thinking again? Coold someone please hit me
with a baseball bat or something so I shut up?
Good thing I'm not on devteam and have to think about stuff like
that. Hey Devteam-Guys, I'm only beginning to understand what
great job you're doing right now... go devteam, go! And thanks
for keeping up with making the next official lsbuild a stable
little wizzproggy again no matter how crazy some of us get.
Please forgive freaks like me that are hooked on ls like a
junkie and kept nagging about a new shot of litestep. It only
proves what great job you're doing there!
No wonder I find all these cool coders and some helping hands in
here.
(If I would be gay, I'ld kiss you all! <g>)
*/
ttyl
Mike
e-sushi@xxxxxxx
__________________________________________________
Subscription options and archive:
http://www.freelists.org/list/shell-coding
