::) sometimes....
:
:> > Ohter thing .... Why you want to hide your VDP handling routines ?
:> > I just don�t know why the good programmers don�t want to show how to do
:> > that incredible VDP tricks to the beginer proggramers ....
:>
:> Ah, a good magician never gives away his tricks ;-)
:> Another thing may be that the code to get the trick is so unclear that
:> even the programmer doesn't know anymore why it works - he's just glad
:> it does ;-)
:
:I'm sure a good programmer knows how his trick works, but I think this
:"hiding" is especially important for demo-programmers (sorry Mark :) but
:I think that's the way it is) because a demo is usually nothing more than
:a technical trick. That's what you're selling, along with some of your ego
::) (oops not to offend anyone) If the tricks are known, the demo isn't that
:much fun anymore. So there are reasons for that. It's up to you to decide
if
:these are good reasons...
Most of the tricks are just a lot of screensplits which change VDP r#23...
:> > I�m sure that if they open that secrets to every one we will have more
:> > good programmers on the MSX ....
:> True fact
:
:I completely disagree. That's like giving a monkey a nuclear reactor and
:saying "hey now you're a good engineer". Coding a bigger project like a
game
:or something requires a lot more than a bag of tricks. If I were to release
:all of my code (which I have considered) I don't believe that it would
:result in more games being made. There is a lot of hard work in completing
a
:complete project, and that requires skills you need to learn, for example
:through practice. The actual code isn't that relevant. It's also very
:difficult to work with the code of someone else, and you learn a lot more
by
:doing it yourself.
I actually think that looking at the code of others is very useful... Then
you can see how they wrote certain routines (and if you are puzzledabout
that, even better!) and which tricks they used... 15xOUTI as a replacement
of OTIR in the "DoCopy"-routine for example... And if you don't get how a
certain thing works you can look it up in someone else's routines... To load
and replay a wave for the MoonSound for example... I have 'loaned' some
parts of the MBWAVE Basic-driver... I've got the documentation of the
MoonSound and I get how it works but doing this the routines will work
sooner and I can see which things of the OPL4 have to be (pre)set in the
case of use on a MSX...
: Good programmers are people who are willing to see a big project through
:over a larger period of time. It has NOTHING to do with VDP tricks. Make a
:fun game, okay?
Yeah, let's do that!
~Grauw
****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put
in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the
quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
****
