cocos2d for iPhone

A fast, easy to use, free, and community supported 2D game engine

1. 

   riq
   Key Master

   TMX support is very immature, and probably some class/method's names will be renamed/modified/added/removed.

   That's why I would like your opinions about them:

   • TMXTiledMap: is the main class, the one that you create. it's a subclass of CocosNode.
   • TMXMapInfo: contains the map info from the xml file
   • TMXLayerInfo: contains the layer info from the xml file
   • TMXTilesetInfo: contains the tileset info from the xml file

   These TMXxxxInfo classes contains the xml info. Once the TMXTiledMap is created, these TMXxxxInfo classes might be useful (or not) depending on your game.

   A 5th class might appear.

   • TMXLayer: Right now it is not needed, because each tmx-layer is represented by an AtlasSpriteManager, but I think I would need to extend it

   //
   // TMXLayer (subclass of AtlasSpriteManager)
   //
   // obtain the tile at position x,y
   -(AtlasSprite*) tileAt:(CGPoint)pos;

   So, what's the problem ?
   TMXTiledMap and TMXLayer are cocos nodes, and IMHO, the names are ok.

   but, I don't like these other names:
   * TMXMapInfo
   * TMXLayerInfo
   * TMXTilesetInfo

   because it's not clear what they do, and people might confuse them with the other 2 classes.
   These 3 classes are not that important... but they can't be private classes (hidden) because the information they contain might be useful for some games.

   so, what do you recommend ?
   should these 3 classes be renamed ? which names do you recommend ?
   should they me merged ? how ?
   should they exists ? how to obtain the xml data in case a game needs it ?

   thanks,

   Posted 2 years ago #
2. 

   riq
   Key Master

   probably the classes will be named:

   TMXTiledMap <-- CocosNode
   TMXLayer <-- CocosNode
   TMXTilesetInfo <-- only contains info about the layer.

   and:
   TMXTiledMap will have these properties:
   * name
   * mapSize
   * orientation

   TMXLayer will have these properties:
   * name
   * layer size
   * "map": a pointer to the tiles

   Posted 2 years ago #
3. 

   Clain
   Member

   I'm not familiar with tiled maps. I've just looked at the tiled editor and at the TMX**** classes in the svn repo. I can't really tell you if it'd be better to merge the TMX***Info classes into the 2 others but to me, it makes sense to have these 3 classes for the sake of the "one class, one responsibility" principle.

   And their names seem fine. TMXTilesetInfo holds info about the TMX tileset. If people get confused about the names, it would be their fault because they didn't read the documentation.

   Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.