Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Python Debugger
dmoore:
--- Quote from: Falldog on October 13, 2012, 04:14:09 pm ---Do you mean that I create another my own repo to maintain these code? ???
--- End quote ---
Yes, just because it is any easy way to share the code that you are working on. Of course, I will be happy to merge it into mine when you think its ready. Alternatively, you are welcome to use a branch of my Berlios repo if you have an account there. But repos are cheap. Without too much hassle, you can sign up at github or launchpad and get free repo public space that I and others can pull from.
Falldog:
--- Quote from: dmoore on October 13, 2012, 04:28:11 pm ---Yes, just because it is any easy way to share the code that you are working on. Of course, I will be happy to merge it into mine when you think its ready. Alternatively, you are welcome to use a branch of my Berlios repo if you have an account there. But repos are cheap. Without too much hassle, you can sign up at github or launchpad and get free repo public space that I and others can pull from.
--- End quote ---
It sounds great! I think I will create a github account to do it. :)
And next step, I think I will try to study wizard script, and create PyDebugger project wizard for save PyDebugger own project
Any suggestion?
MortenMacFly:
--- Quote from: Falldog on October 13, 2012, 04:54:54 pm ---It sounds great! I think I will create a github account to do it. :)
--- End quote ---
For the record: I personally prefer SVN repos, because these we can integrate as "external" repo into the C::B repo. This allows the devs to stay independent but us/users to checkout the whole stuff.
At least this is true as long as we stick with SVN.
dmoore:
--- Quote from: MortenMacFly on October 14, 2012, 07:41:03 am ---
--- Quote from: Falldog on October 13, 2012, 04:54:54 pm ---It sounds great! I think I will create a github account to do it. :)
--- End quote ---
For the record: I personally prefer SVN repos, because these we can integrate as "external" repo into the C::B repo. This allows the devs to stay independent but us/users to checkout the whole stuff.
At least this is true as long as we stick with SVN.
--- End quote ---
I plan to merge his stuff when it is ready into my SVN on berlios. In the meantime it is better for him to use *any* repo as opposed to just posting patches here. If you want, Morten, I can setup a python area of my berlios SVN repo (a tidy up of my trunk is long overdue) that C::B can pull from. This would be a combination of several plugins (embedded interpreter, code completion, debugger), but I guess I could combine them into a single C::B project with multiple plugin targets?
dmoore:
--- Quote from: Falldog on October 13, 2012, 03:47:32 pm ---
--- Quote from: dmoore on October 11, 2012, 10:20:39 pm ---Thanks. I'll try to test it out in the next week or so. Why are there two patch files?
--- End quote ---
I had merge local commit in this patch, but file too large(more than maximun attachment), I separate in 2 rar files
--- End quote ---
Ok, I briefly tested this one. You should add a post build step to the project to copy the python files to the right place. You also missed XRC file in your zip command on Linux.
BTW, using wxString rpdb_wrap_path = ConfigManager::GetDataFolder() + _T("/python/PyDebugger/rpdb_wrap.py");, you should test GetDataFolder with true and false. Depending on the setup, the python files could be installed to a global or local place.
I didn't have time to make these fixes myself, but I will take another look later. I did successfully compile the project.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version