@pepstar If you would like to update my tutorials, making them clearer, easier to understand, or by adding images, PLEASE DO!! I absolutely hate writing tutorials. In fact, if you just want to re-write them in their entirety, I'm completely on board with that as well.

@IngeJones if you know that, why are you making the statements you're making and making implications or accusations that Kuree has no idea of the licenses? If you knew that you wouldn't be making said statements

guys, why is there so much arguing go on in here? To correct a couple statements above no one on the s4s team is irritated with anyone and our plans for s4s are related to using code specifically created for it, a user-interface heavy tool meant for creators, rather than code created for a library like s4pi which is user interface lean (if you look at s4pe as its interface) and meant for coders. The purposes of these two things are very different and the code which works well for one does not suit the other as effectively. Also, we have a new coder on the team who has had a bit of difficulty working with the rather intricate and unique s4pi code. Removing all this will allow this person to be more productive and to have greater familiarity with the code the tool is using. Although Kuree generously offered some code components these sections were already completed using different code sources. There will not be any line of code that is borrowed from s4pi. All code in the tool will be either "homegrown" or taken from other licensed sources. The team is still considering how to license the tool. Certainly, no one wants to discourage other coders from working on this project. Our latest member joined the team after posting in the forum that they wanted to work on S4S. We are actively seeking more coders as a matter of fact. Anyone with a serious interest should not hesitate to speak up.

Seems fair enough to me, OM. I don't know why everyone is trying to see it as a fight. Every tool in the community is another choice for the creators. My only regret is that I think it's a bit of a pity that the s4pe/i project is being run by someone who openly admits they're not that interested in it, when it would benefit so much from a bit more loving attention. That's completely unrelated to s4studio.

Jesus wept I never claimed any such thing. I said the RCOL chain still had some errors and it did. Not in MATD because you fixed that, and I never said you didn't. The remaining problems were MTST and MODL chunks which hopefully are now fixed. It took three of us contributing to CASP wrapper as we each either made a mistake or didn't know how to do something. Between the three of us we got it working I think. Just what the hell is your problem with that? FFS do cheer up!

and even if someone else does the code and gives it to you, you would still get the kudos as the project leader. Where is goes wwrong is when you refuse to accept the code, or delay it so long the other author releases it themself and gets the credit themself