I was talking with G about a fork a while ago. Honestly, I think a fork is a good idea. I only ask two things.
1) I would like you to change the name a little. Even though the code is derived from the Q-gears base, they are two programs going in different directions. I don't want them to be confused with each other. Calling it QRPG Studio or Q-RPG Studio is fine. "Gears" was originally my reference doc for FF7.
2) As Q-gears is GPL, and by extention your RPG Studio, you need to release your changes so we can work on them. I can give you Shell/FTP access to the Q-Gears project Sourceforge so you can upload your work via FTP and we can take it from there. I can do several things for you. I can create a new sourceforge project for you, and make you an admin. I can manage the SVN imports if you just want to upload your code via FTP. This will also give you a FTP spot for your own project and a website. I think you are making out like a bandit in this deal. ^_^
To the other programmers:
Forks are a healthy part of the Open Source ecosystem. It is by that way code can evolve down different branches, and create better code for all.There is no reason to fear the the code is fragmenting. If anything forks often fold back as good ideas are created and bad ones are discarded. One branch will only damage the system when it does not participate in the ecosystem (i.e. code becomes closed).
I have anticipated this for a while. Akari has done so much for the Q-gears project. In the beginning, Q-gears was just a simple summer project of mine. I just wanted to make a simple script parser and see what would happen from there. (My script dumper, by the way, is in SVN under the /util directory) Akari took the idea and made it really shine. For that I'm am eternally grateful.
To G:
I know you are most likely disappointed with this and this most likely came about because of the Linux/Windows cultural gap and the AKAO support. We have a treasure, and we can watch with interest as Akari polishes the work further.
If anyone has any questions, PM, email, or post in the thread. I'll be around.