As you can tell, I'm not an experienced programmer. In any case, I've
attached a patch of "backend_wx.py" for the v0_91_maint branch. I didn't
know if I was supposed to do something with the filepaths in the patch
before sending it.
Hey Tony -- thanks for the patch -- it looks like you rapidly are
becoming a developer 
Could I ask you to submit a svn diff of the maintenance branch -- this
will be easier for me to apply. simoply make your changes in the
branch and then do
svn diff > my.patch
and send that.
I think your icons look nice, but I was surprised that they were
grayscale. Is this a minimalist aesthetic?
Also, please keep all replies on list rather than to me personally
because someone else could be the one to ultimately handle the patch.
JDH
路路路
On Fri, May 23, 2008 at 4:59 PM, Tony Yu <tsyu80@...149...> wrote:
I think this is what you're asking for, but I may have done the diff from the wrong directory.
backend_wx.patch (3.26 KB)
路路路
On May 23, 2008, at 7:05 PM, John Hunter wrote:
Could I ask you to submit a svn diff of the maintenance branch -- this
will be easier for me to apply. simoply make your changes in the
branch and then do
svn diff > my.patch
and send that.
I think this is what you're asking for, but I may have done the diff from
the wrong directory.
I think the last one was a plain-ol-diff and this one is a svn diff so
it is better. I have applied it and committed it. FYI, I normally do
the svn diff at the same level that the setup.py resides in, but it is
easy enough to correct for,
One last thing: is there some sort of tutorial for beginners who *may* want
to contribute. Like a "Getting Started" page for developers. I have tons of
questions, but I don't want to spam this list. For example: I checked out
the maintenance version of MPL but the build and install set everything up
in a new/separate directory. This means my subversion working copy is
separate from the installed copy (what actually gets imported).
In the svn trunk, there are a few documents in docs/devel (you need a
fesh checkout to find it) that contain coding style guidelines, but
they are rather incomplete. We are in the process of a documentation
push, so we hope to add to these. Your questions are welcome, just
batch them into just one or a few emails rather than a ton of
individual ones. Perhaps one of your first projects can to write the
"getting_started.rst" for the developer's guide as you learn the
ropes. We can all pitch in with answers to your questions... In my
experience, one of the best time to write introductory documentation
is when you are learning something he first time, because the more
seasoned developers have trouble approaching the subject from the
perspective of a beginner.
JDH
路路路
On Sat, May 24, 2008 at 6:29 PM, Tony Yu <tsyu80@...149...> wrote: