(no subject)

[John R. <jh...@ma...>]

For my own learning, I made a sample set of files for a library that
* would be fully compatible with the Loader
* follow the general conventions for naming and documentation that I  
observe
* do limited things that I need, like a Components subfolder.

I also noticed this in the FAQ:
Q: Can I make my/other libraries Loader-compatible?
A: Currently, developer documentation for general use is crude and  
limited. It is not difficult to add the required information to your  
library scripts to make them Loader-compatible. However, since most  
library authors are "serious" scripters, there has been little need  
to write general-purpose documentation. We are working on a basic  
"Loader Compatibility Guide".

Attached is a sit file with the resulting "SampleLib" folder that  
might be useful towards such a "Loader Compatibility Guide", simply  
as a starting point for someone to do what I am doing: re-organized  
existing AS code into the Loader model.

(1) Could someone please look it over and assure me that I am on the  
right track?
(2) Is it actually useful to anyone else?

Thanks!

- John R