Deliver user-friendly error messages for certain publishing errors
adjust formatting to match surrounding code
TexturePacker optimized by using BitmapData to implement _mask
SwfTexture - renders to target size directly from vector renderer (Issue #32), unless dObj contains filters.  If dObj contains filters, uses full visual bounds to avoid cropping of filter pixels, and scales to target size from bitmapdata of scale 1 vector render.
Exposed the previously Movie-internal class Layer.

Useful for doing things like modifying the hierarchy of a given layer at runtime in a Movie
subclass. I'm using this to add text fields to animated UI bits.
Error messages display keyframe number as Flash CS displays them (first frame displayed as frame 1, rather than 0)
Merge pull request #69 from kpatelPro/artist-friendly-keyframes-good

Display artist friendly keyframe number in error log "location" column
Merge pull request #63 from kpatelPro/publish-error-msgs

Publish error msgs
Merge pull request #64 from kpatelPro/texturepacker-optimization

TexturePacker optimized by using BitmapData to implement _mask
conform to coding standards, removing this. and using _s_ prefix for static members
conform to coding standards, removing this. and using _s_ prefix for static members
use and show texture padding setting in preview texture atlas
Internalize a bunch of exposed classes.

These classes are not meant to be part of the public API. With this change, it is still possible,
through a bit of backbending, for an external library user to play with these bits and extend them,
but they will not show up in the public API docs.

It turns out that you can't apply a user-created namespace to an entire class (only to methods and
member variables), so this had to be done with internal instead.
Fix doc comments.
Make these three public again.

There is a method on LibrarlyLoader to set the CreatorFactory, which in turn exposes ImageCreator
and MovieCreator.  Either that method on LibraryLoader should be made internal, or these three
should be public again, which is the side I'm erring on here. I could go either way though.
Merge pull request #71 from roguenet/internalize-dirty-bits

Internalize dirty bits
LayerMold.frames does not crash if numFrames is zero
ignore layers of type folder, which inherently have no keyframes
Merge pull request #72 from kpatelPro/handle-no-frames-in-layer-safely

Handle "No keyframes in Layer" safely
Merge branch 'ignore-layer-folders-silently' of github.com:kpatelPro/flump