From the last few posts, it seems to me from what I understand that Lime’s issue is that it tries to support too much. In flexibility comes a performance hit.
Maybe Lime could have 2 code paths, depending on whether you need the bells and whistles, or an optimised route just for displaying a basic tile map?
Just a suggestion. I must admit, I’ve considered re-working and releasing my own tile engine, because it seems from what I’ve read over here that I’ve got if not the fastest, but one of the fastest solutions for just dumping a tile map to the screen, but I think its a bit early for me to go down that route, and in fact I’ve even become hesitant in helping people who suffer from this problem (although I have loosely detailed my method elsewhere in this forum).
For example - because I can handle extremely large maps, loading from XML has proved to be an annoying delay. Result? I wrote a convertor that changes level data structures into formatted Lua code - there’s nothing quicker than native (as it can get) code, right? [import]uid: 46639 topic_id: 8728 reply_id: 34418[/import]