Removal of App Root on the Dev Trac + a little more.
Posted by sirebral on 2009-07-26 08:29
There is more going into that later on with Traipse. One problem I am noticing is that the OPENRPG_BASE key remains after the program closes, so the idea is to use that object, place the material into a disr_struct path and then delete the object.
In the traipse_dev trac I have also shortened some of the if: else: statements. At first the effect is not very noticeable, but if you run two clients side by side after a time the older client starts to hold unto more RAM bits. This is due mearly to the size of the files being loaded.
I also want you to take a look at the Traipse Stable trac tickets. It is entirely possible to re-use the Updater Window. If you want to help we can get this done a lot faster. The idea I am working on is to pull updates from the trac every time the user starts the software, but then the udpater window provides the user a plethora of update possibilites. They will be able to switch branch names, and from there they will be able to see the revisions. If a user auto updates it will by pass the window and just pull + update. This also lends itself to portability if a user wants to clone a trac and dev with it.
Which leads me to one last thing. Traipse is Distro ready. I would hope that you adopt this feature as I think it is very inviting for developers. If you download a copy of Traipse the main window says Traipse Grumpy Goblin {Build Number}, and I think it would be nice if the OpenRPG trac said OpenRPG Core {Build Number}.
In the traipse_dev trac I have also shortened some of the if: else: statements. At first the effect is not very noticeable, but if you run two clients side by side after a time the older client starts to hold unto more RAM bits. This is due mearly to the size of the files being loaded.
I also want you to take a look at the Traipse Stable trac tickets. It is entirely possible to re-use the Updater Window. If you want to help we can get this done a lot faster. The idea I am working on is to pull updates from the trac every time the user starts the software, but then the udpater window provides the user a plethora of update possibilites. They will be able to switch branch names, and from there they will be able to see the revisions. If a user auto updates it will by pass the window and just pull + update. This also lends itself to portability if a user wants to clone a trac and dev with it.
Which leads me to one last thing. Traipse is Distro ready. I would hope that you adopt this feature as I think it is very inviting for developers. If you download a copy of Traipse the main window says Traipse Grumpy Goblin {Build Number}, and I think it would be nice if the OpenRPG trac said OpenRPG Core {Build Number}.
Home / Developer API / Tour / Get a Project - Solutions for Bug & Issue Tracking, Collaboration Tools, Subversion Hosting, Git Hosting
Openrpg is powered by Assembla.
0 Comments