1
Feature requests / Re: Parent / Child heirachy sprite support
« on: July 16, 2012, 09:35:46 pm »
Funny that both my feature requests would get shot down as 'my job'. I've already written something very much like SFML a couple times for multiple platforms. Ortho mappped GL sprites are not that hard. I'm using SFML because it should hopefully make my life easier. If its 'my job' to manage everything but low level stuff, then whats the point of SFML?
I'm not suggesting you put in path solving, steering behaviors, optimized distance calculations or a physics system. I would agree that all these things, though very helpful, are not the job of the library. But if you're going to make a sprite class, please do make the whole thing. Stopping just short of 'useful' just motivates me to do a total rewrite. Sprites are not only the domain of games btw, the forums obvious disdain for game programmers is misguided in my opinion. Lots of apps use sprites that aren't games. Game coders are enthusiastic programmers and should not be pushed away just because their game probably will never be known of or played widely.
BTW I've already implemented both the features I requested. They've very helpful. You should add them. Tweening and parent/child relationships. 'Thats the programmers job' just sounds like a weak excuse. Referring me off to some other add-on library of 'everythign that doesnt fit in SFML' just pointlessly induces bloat. Making every user reinvent the same wheel just means that wheel is usually going to be made poorly.
This is probably going to be my last post. People seem kinda diminishing and combative here, like I'm some sorta novice because i suggested these things. Be glad i took the 30 seconds to give you some honest feedback, dont try to argue with me about what I want. As the user, what I want should be very, very important to the developer. If its not, then the developer is no good and does not deserve my time and energy.
Thanks again for this fine library and all your hard work. Good luck.
I'm not suggesting you put in path solving, steering behaviors, optimized distance calculations or a physics system. I would agree that all these things, though very helpful, are not the job of the library. But if you're going to make a sprite class, please do make the whole thing. Stopping just short of 'useful' just motivates me to do a total rewrite. Sprites are not only the domain of games btw, the forums obvious disdain for game programmers is misguided in my opinion. Lots of apps use sprites that aren't games. Game coders are enthusiastic programmers and should not be pushed away just because their game probably will never be known of or played widely.
BTW I've already implemented both the features I requested. They've very helpful. You should add them. Tweening and parent/child relationships. 'Thats the programmers job' just sounds like a weak excuse. Referring me off to some other add-on library of 'everythign that doesnt fit in SFML' just pointlessly induces bloat. Making every user reinvent the same wheel just means that wheel is usually going to be made poorly.
This is probably going to be my last post. People seem kinda diminishing and combative here, like I'm some sorta novice because i suggested these things. Be glad i took the 30 seconds to give you some honest feedback, dont try to argue with me about what I want. As the user, what I want should be very, very important to the developer. If its not, then the developer is no good and does not deserve my time and energy.
Thanks again for this fine library and all your hard work. Good luck.