wxpython-phoenix pycrust

wxPython Users
1

Hi Philippe,

Hello,

I have translated pycrust (py folder) for phoenix (on xp for python 2.7 and 3.3)
some others samples (samples, wxPIA_book)

wxpython demos (80%) running well on python 2.7.

on my dropbox
Dropbox - Error - Simplify your life

Looks like you did a lot of work.

I am sure Robin will want patches and not the changed files or ZIP archives.

If you are on Windows install something like TortoiseSVN and checkout:
http://svn.wxwidgets.org/svn/wx/wxPython/Phoenix/trunk

Copy your changed files into:
whereeveryouhave put the checkout\wxPhoenix\wx\whatever you have changed

Right click on the wxPhoenix folder and select "create patch" from the TortoiseSVN menu, make a patch for pycrust, one per sample etc etc.

If you haven't already done so also check the following links:
ProjectPhoenix/LibraryMigration - wxPyWiki - add the tags to the changed files as mention in "Phase 2"
Redirecting...

And you should post them to the wxpython-dev list.

Werner

···

On 09/05/2013 17:11, philippe DALET wrote:

2

werner wrote:

I am sure Robin will want patches and not the changed files or ZIP
archives.

Indeed. It really is the best way for me to be able to review what has changed and to figure out what should be double-checked before committing. Also, if you happen to take your snapshot before some other changes are made to the code and then submit the whole changed file(s) then those other changes will be lost. Using a patch makes it possible to merge your changes with others.

If you are on Windows install something like TortoiseSVN and checkout:
http://svn.wxwidgets.org/svn/wx/wxPython/Phoenix/trunk

Also, if you don't want to, or are unable to use Subversion then the code is also mirrored on github at GitHub - RobinD42/Phoenix: wxPython's Project Phoenix. A new implementation of wxPython, better, stronger, faster than he was before.. You can clone the repo locally and use git to make the patch files that you submit, or you can fork it to your own github repository, make the changes and then submit the patches as PRs using github.

···

--
Robin Dunn
Software Craftsman

3

...

Also, if you don't want to, or are unable to use Subversion then the code is also mirrored on github at GitHub - RobinD42/Phoenix: wxPython's Project Phoenix. A new implementation of wxPython, better, stronger, faster than he was before.. You can clone the repo locally and use git to make the patch files that you submit, or you can fork it to your own github repository, make the changes and then submit the patches as PRs using github.

Would you prefer PRs instead of patches?

Werner

···

On 09/05/2013 20:53, Robin Dunn wrote:

4

werner wrote:

...

Also, if you don't want to, or are unable to use Subversion then the
code is also mirrored on github at
GitHub - RobinD42/Phoenix: wxPython's Project Phoenix. A new implementation of wxPython, better, stronger, faster than he was before.. You can clone the repo locally
and use git to make the patch files that you submit, or you can fork
it to your own github repository, make the changes and then submit the
patches as PRs using github.

Would you prefer PRs instead of patches?

I'm not sure. I haven't actually done PRs with these repositories yet, and since they are forks of a mirror of the main SVN repository, and since all change sets have to go up to the svn repo and then back down via the mirror and then back up to my fork, it's a little more complicated than the typical git repo... But I suspect that it will work okay and that overall the process on my end will be a bit more automated and streamlined.

In the end though it really just depends on what the contributor is most comfortable with using to make and submit the changes and either way is okay with me. If somebody is already familiar with how github and PRs work then I expect that submitting contributions that way will be a little more streamlined for them too.

···

On 09/05/2013 20:53, Robin Dunn wrote:

--
Robin Dunn
Software Craftsman