From: Daniel H. <dh...@gm...> - 2012-08-17 22:29:45
|
OK, I have a sample code for people to run if they want to. I've dumped all of the interactive manager code and some sample usage (of the mix-in way of doing it) in the following branch: https://github.com/dhyams/matplotlib/tree/MEP9 in the directory examples/user_interfaces/imanager.py Just run that script, and it should give a little demo plot. I do apologize and disclaim all messiness in the code...it's not the prettiest thing anyway, and I cobbled it together very quickly so that you could see what it does. Sort of a straw man to beat on, I guess. On Fri, Aug 17, 2012 at 3:38 PM, Daniel Hyams <dh...@gm...> wrote: > > > On Fri, Aug 17, 2012 at 3:24 PM, Eric Firing <ef...@ha...> wrote: > >> On 2012/08/17 8:45 AM, Daniel Hyams wrote: >> > I was planning to just create my own branch to start putting code in, >> > but would it be better for an admin to create a branch off of master in >> > the main matplotlib repo (say MEP9)? Then whoever wants to help out >> > with MEP9 can branch from that and issue pull requests against it? >> >> People can already do that by forking your repo (which you forked from >> master), and issuing pull requests against your MEP9 branch within it. >> The difference is that in the latter case, you are the only one who can >> merge a pull request. I think this will have some advantages, including >> giving you more freedom to do things like rebase and force-push, which >> we would not want to do in the main repo. >> >> Eric > > > > OK, thanks Eric. I'll try my best not to let my git-ignorance "git" in > the way too much ;) > > -- Daniel Hyams dh...@gm... |