I was taking a look over the change logs and it looks like a ton of new stuff and bug fixes have been added(or are planned? not sure if that is an evolving list or a wishlist). I wanted to know if I use the existing trunk and make (maybe weekly builds) will the API remain mostly stable for the core stuff like creating cubes and meshes, gui stuff and the like (basic stuffs)? I really want to get access to the hardware cursor code but it looks like lots of other neat features (such as a fixed version of the GUIEditor, and brush entities) have been added in as well. If 1.8 isn't far off I can hold out. I just don't want to get on trunk and have the API ripped from underneath me. I didn't find a good place that lists the planned features for 1.8 (I assume that the trunk will turn into 1.8?)
EDIT: ignore the 1.8 stuff, I missed the huge post about half a page down.
Trunk stability
Re: Trunk stability
The change log is about things that already got changed. And in general the API does not change too fast as we certainly don't break it unless we have to (and even then we often keep the old API around as "deprecated" for a while to give people time updating their code).
I'm working with trunk most of the time and the only part I remember that I had to change since 1.7 was that materials need a little more intialization now when used with alpha-values. Not sure, maybe draw2D-functions did behave a little different in the past because of that (would have to write a test to compare). But I never had to rewrite large parts of code so far because of updates. Same was true for most former updates, usually it's about adding a parameter here and there or maybe changing the interface of derived classes a little bit.
And if you get stuff breaking due to updates you can always report it - if it's accidental we also try to fix it fast.
So go on - use trunk, we are always glad if more people test it. Most likely you can use your existing code just with recompiling.
I'm working with trunk most of the time and the only part I remember that I had to change since 1.7 was that materials need a little more intialization now when used with alpha-values. Not sure, maybe draw2D-functions did behave a little different in the past because of that (would have to write a test to compare). But I never had to rewrite large parts of code so far because of updates. Same was true for most former updates, usually it's about adding a parameter here and there or maybe changing the interface of derived classes a little bit.
And if you get stuff breaking due to updates you can always report it - if it's accidental we also try to fix it fast.
So go on - use trunk, we are always glad if more people test it. Most likely you can use your existing code just with recompiling.
IRC: #irrlicht on irc.libera.chat
Code snippet repository: https://github.com/mzeilfelder/irr-playground-micha
Free racer made with Irrlicht: http://www.irrgheist.com/hcraftsource.htm
Code snippet repository: https://github.com/mzeilfelder/irr-playground-micha
Free racer made with Irrlicht: http://www.irrgheist.com/hcraftsource.htm
-
shadowghost21
- Posts: 56
- Joined: Wed Nov 23, 2011 11:53 pm
Re: Trunk stability
Fantastic, just the kind of news I wanted to hear. I'll jump on the latest version tonight and get it integrated with my project. Thanks CuteAlien