MovieClip not included in createjs-2013.02.12.min.js

[Benjamin Taylor]

This is correct? Or is there a new reference or Toolkit for CreateJS?

TypeError: 'undefined' is not a constructor (evaluating 'new cjs.MovieClip()')

[Grant Skinner]

Correct, MovieClip is not included in the createjs file. There are a couple of reasons for this:

1. MovieClip is not used much at all except with Toolkit, and we didn't want to pad out the core library with tool specific code.

2. More importantly, MovieClip registers a plugin with Tween. Having any plugin registered with Tween has a small impact on performance (minor, but measurable), and we didn't want to force that on developers who weren't using MovieClip, especially given #1.

We're always open to feedback on these types of things, but at present the workflow requires that you include createjs & the movieclip libraries separately.

Cheers,

Grant.

On 2013-03-08, at 15:53 , Benjamin Taylor <infinit...@gmail.com> wrote:

This is correct? Or is there a new reference or Toolkit for CreateJS?

TypeError: 'undefined' is not a constructor (evaluating 'new cjs.MovieClip()')

--
You received this message because you are subscribed to the Google Groups "CreateJS Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to createjs-discus...@googlegroups.com.
To post to this group, send email to createjs-...@googlegroups.com.
Visit this group at http://groups.google.com/group/createjs-discussion?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Benjamin Taylor]

Thank you Grant!

I've also noticed that it seems to not include PreloadJS.

TypeError: 'undefined' is not a constructor (evaluating 'new createjs.PreloadJS(false)') 

On Friday, March 8, 2013 3:01:35 PM UTC-8, gskinner wrote:

Correct, MovieClip is not included in the createjs file. There are a couple of reasons for this:

1. MovieClip is not used much at all except with Toolkit, and we didn't want to pad out the core library with tool specific code.

2. More importantly, MovieClip registers a plugin with Tween. Having any plugin registered with Tween has a small impact on performance (minor, but measurable), and we didn't want to force that on developers who weren't using MovieClip, especially given #1.

We're always open to feedback on these types of things, but at present the workflow requires that you include createjs & the movieclip libraries separately.

Cheers,

Grant.

On 2013-03-08, at 15:53 , Benjamin Taylor <infinit...@gmail.com> wrote:

This is correct? Or is there a new reference or Toolkit for CreateJS?

TypeError: 'undefined' is not a constructor (evaluating 'new cjs.MovieClip()')

--
You received this message because you are subscribed to the Google Groups "CreateJS Discussion" group.

To unsubscribe from this group and stop receiving emails from it, send an email to createjs-discussion+unsub...@googlegroups.com.

[Grant Skinner]

This is an API change. We did a major overhaul of PreloadJS, that included renaming the instantiable class in PreloadJS to LoadQueue. This better reflects the other libraries (ex. you don't create an "EaselJS" instance, or a "TweenJS" instance).

Best,

Grant.

To unsubscribe from this group and stop receiving emails from it, send an email to createjs-discus...@googlegroups.com.

[Benjamin Taylor]

Tried to follow the new LoadQueue instructions found here http://www.createjs.com/Docs/PreloadJS/classes/LoadQueue.html, but my images are not loading properly. Here were my changes using the new calls:

Before:

        var loader = new createjs.PreloadJS(false);
loader.installPlugin(createjs.SoundJS);
loader.onFileLoad = handleFileLoad;
loader.onComplete = handleComplete;
//Add HUD assets to manifest
for(object in mHUD.manifest){ 
manifest.push(mHUD.manifest[object]); 
}
loader.loadManifest(manifest);

After:

        var loader = new createjs.LoadQueue(false);

loader.installPlugin(createjs.Sound);

loader.addEventListener("fileload", handleFileLoad);

loader.addEventListener("complete", handleComplete);

//Add HUD assets to manifest

for(object in mHUD.manifest){ 

manifest.push(mHUD.manifest[object]); 

}

loader.loadManifest(manifest);

The result is a blank canvas, with no errors thrown. Any idea what's going on?