shinkan I thought about your post a bit more and I think you are wrong. Not about the words "sprite sheet" and "tile map" (although the fact that "tiles" are in the sprite sheet is a bit confusing), but more for your unasked-for advice.
While your advice might have been fine more than 50 years ago, the world today is changing way to fast to sit on the sidelines and study until I know enough. Everything is changing and people's terminology is likely to be a bit loose.
Yes, there is a difference between sprite objects and tilemap objects. But the files that are pulled in aren't as clearly defined. The sprite sheet I used was a set of tiles and it looks just like a tile map you might see on the Tiled web site (except that Tiler tile maps also have XML data and the proper name for those tile maps is a TMX file.
I don't think you were helpful in your criticism because you didn't say something like:
[quote:2y6iq5ag]Use the term "sprite sheet" when referring to sprites and use "tile maps" when to the tilemap object. A sprite sheet is a simple art file but a tile map is ....
A glossary would be really helpful. Maybe there is one. Maybe not. But if there is, it would have been helpful to point to it.
Everything is moving very fast and names are changing. Most of the people who are working with Construct 2 seem to be aware of this and try to be helpful if someone doesn't understand some part of something. While I love Construct 2 a lot, I feel like it's isn't completely a finished product (I'm looking at you, Android and iOS) and I don't think it will be for a while because browser adoption of HTML5 is still a bit spotty and because HTML5 is a broad collection of technologies, some of those are baked, some are half-baked, and others are still a dream (MIDI, for example).
The idea of me making one mistake and people laughing at me and not reading my blog is not appropriate in an age where things are changing very fast, and the rate of change is accellerating. People who are successful in cutting-edge technology learn to not be distressed by loose terminology and pay attention to the essentials. My blog post (so far) seems to be accurate and I think will be useful for people who are trying to adapt Construct 2 to a Firefox OS mobile-only UX.
I'm sharing my blog posts with the Construct 2 audience in hopes that I'll find out if I've made any significant mistakes and I will change my post to say "sprite sheet" instead of "tile map". But my main focus is on using HTML5 to make games for the devices that support HTML5 (which so far is Firefox OS, which Amazon recently jumping on the bandwagon, Tizen falling off, and Microsoft marching in the wrong direction). If you read my other blog posts, you'll see that they are covering HTML5 in great detail. Everything I do is tested and works.
I am reminded of a saying I heard many times when I worked for IBM (a long time ago). "There are three names for everything and every name has three meanings."