>I would go in and delete all unnecessary text, such as tool tips and
>documentation.
Tool tips, yes--but I would never delete documentation. It has no effect on
the code speed, and I'm a strong believer in documenting code. If you
looked through some of my stuff, you'd probably find that a good 25% of the
lines are comments.
> I recommend against them anyway; since they use a lot of
>code so as to be universally customizable
Some of the more complex ones, yes.
>it's more efficient for
>processing speed (fewer lines of code) to just write your own.
There's a tradeoff between processing speed and development cost. In some
cases, good enough *is* good enough.
I would agree that it's a good idea to rewrite some of the behaviors, take
out the over-generalized stuff, optimize it here and there. But I don't
reinvent the wheel every time I need to do something--I'm more than happy
to use somebody else's code as a starting point.
The built-in behaviors are a real blessing to less advanced programmers,
and to non-programmers (designers, artists) who use Director for prototyping.
Kvetch, kvetch--it's Saturday evening. Everybody have a good weekend!
Cordially,
Kerry Thompson
Learning Network
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
