> At the very LEAST, a collaboration should mean that the respective projects > (Loci/GMS/Oveflow) don't continue development in such a way as to incorporate > incompatibilities with VSH. If you're not excited about VSH right now, then > fine, maybe you will be later. But you need to... > > (1) Tell us what features you'll be adding to your program > (2) Consider whether or not features will work in the VSH system > (3) Be prepared to change your program to incorporate a VSH feature > OK to me. It seems gms will get the most changes, but that's no problem. I'm only saying the coming time the VSH project will contains 3 types of code: 1) general code, 2) collaborate code & 3) standalone code I think these dont need any further explanation. bye, jarl