Hello there,
I fixed it on my side, but the next release will be at nearest on the next week.
Still, this panel:
is just a preview and doesn't affect the actual project. The real animation speed is set by code. You can write this line of code to the 'On Create' tab to set an animation speed for a specific type:
this.imgspd = 15 / ct.speed;
Here '15' is a desired number of frames per second. This field and others may be also found in the docs > ct.types > Copies' parameters.
Good memory! Still better make a screenshot next time ;)
The current JS compressor is indeed old and doesn't support ES6 (shame on UglifyJS) that is quite widely used in ct.js. Anyway I plan to replace it with Google Closure Compiler while adding a packing-to-executables feature. Maybe I'll release GCC integration as a hotfix this week.
there is an alternative to uglify which support/build basically for ES6, its terser. Link => https://github.com/fabiosantoscode/terser
Thanks, will give it a shot! I didn't know about terser. It looks like a small, almost dependency-free solution.
Aaaand it turned out that google-closure-compiler-js has been deprecated/merged into google-closure-compiler just 2 days ago, and after trying to get bundle size of google-closure-compiler on https://bundlephobia.com/ the service went offline, so I think the size of it is really a killer 😳
After thinking about it I removed terser and added google-closure-compiler-js again. It has been packing ct.js itself for a long time, so I think it is quite production-ready. (There is a LOT of JavaScript in ct.js, including 3rd-party libraries.)
My games and ct.js demos also turned out to be fully working if compiled to ES5 and compressed with its tool. It will come out this week, I think. There is still some work with internal game debugger and packing awaiting.
This is an expected behaviour and a part of HTMLCanvas specs. Shadows apply to everything, including strokes or images.
If you need to, say, disable shadow after drawing a filled shape, you can write this:
ct.styles.set('interface');
ct.draw.rectangle(10, 10, 50, 50, false);
ct.x.shadowColor = 'transparent';
ct.draw.rectangle(10, 10, 50, 50, true);
ct.styles.reset();Technically it is just UI not refresing =) Fixed; the release will come in about an hour, I guess
Um, have you installed ct.js in your system in some way? I haven't faced handling such apps on macs before and thought that the app will be just extracted to some folder. And could use some more information to help mitigate this problem in future versions of ct.
And yes, you can copy your project to any directory and open it with a Browse button on the starting screen. As a workaround, here is an empty ct.js project: https://www.dropbox.com/s/clcq0d541t8xa1l/EMPTY.zip?dl=0
Ok, so today I've set up a VM with Mojave, but was able to run a simple project and compile examples on v1.0 (though I don't have any additional video support and what I get is a flickering black screen :D but I can see that game logic runs and can interact with it).
I just downloaded ct.js for mac from the official site and run it from within Downloads folder.
Do you run v1? What else is written if you open the dev tools with the context menu? Any other info you can provide?
1st and 2nd: Thanks for reporting, I fixed it and these changes will come in a nearest update.
3rd, the license: I'm not a lawyer either ¯\_(ツ)_/¯ So creating a license is a way of trial and error for me.
But it is meant that the engine files combined with yours ones are licensed under your own terms:
I will think about how to make this section more clear and readable. Actually, there are four entities: ct.IDE, the Software, the ct.js library (the engine), Your Content and user-made modules (aka catmods). ct.IDE is immutable, the ct.js lib is ok to edit, and your content and user-generated modules should be licensed by their makers.
3rd again, the OSS: the main reason that it is not open-source is that everyone wants money ✨ and I would like to monetize ct.js in some way, but also in a non-restricting (for users) one. I understand that FOSS can be monetized, too, by rewards, pledges, Patreon, donations and stuff, but this all is new to me and I'm unsure on how to do it properly. So it is not actually about licensing, as I can make my own license if I need, or just go with GPL-3.
I will make it FOSS when I will think I'm ready, but not now. Maybe it will be OSS some day, maybe it will never ever be. If you have such experience and have a story to tell, you can speed up this process.
