Is anyone using this list?

[Chris]

Since we've moved to groups.google.com, I have yet to see anyone post
anything. Did we lose the whole wxPython community in this shift?

[David Goldsmith]

I'm still here.

DG

--- On Sat, 6/13/09, Chris <cspe...@cinci.rr.com> wrote:

[David Lyon]

Test....

is anybody interested if I translate the C++ code to python?

http://docs.wxwidgets.org/stable/wx_dialogfunctions.html#dialogfunctions

[Leigh Morresi]

test test


im on it

-- Leigh Morresi +61401883741 dgtl...@gmail.com http://dgtlmoon.com skype: dgtlmoon

[Robin Dunn]

Most of those functions already have wrappers in a wxPython module.

--
Robin Dunn
Software Craftsman
http://wxPython.org

[David Lyon]

Yes, but no documentation suited to a python programmer.

My brain is not native to python... I'm a visitor.....

        dlg = wx.MessageBox("To proceed, we need to install EasyInstall from the Internet. May we do this?",
                                   "Confirm Download",
                                   wx.ICON_INFORMATION | wx.OK | wx.CANCEL)
        rx = dlg.ShowModal()
        dlg.Destroy()
        if rx != wx.OK:
            print " - Installer download cancelled."
            return

Writing one simple dialog takes 3+ hours because of the poor documentation....

Sure I can read C++ code....

But have no idea how to translate it to python wx.... so totally lost...

[David Goldsmith]

With all due respect, two sincere questions: are you facile w/ C++ wxWidgets? Have you read/done any of the tutorials? Because, based on your comments, it sounds more like you need a more basic understanding of the underlying C++ library and of just how any basics are done in Python, as opposed to better/clearer documentation of the Python wrappers (which, having initially cut my wxWidgets teeth on the C++ library, I found to be a comparatively easy pleasure to use). But if I'm wrong, my apologies.

DG

--- On Mon, 6/15/09, David Lyon <david.lyon...@gmail.com> wrote:

[Robin Dunn]

David Lyon wrote:

> Sure I can read C++ code....
>
> But have no idea how to translate it to python wx.... so totally lost...

It's not perfect, but there's this doc in the wiki:

http://wiki.wxpython.org/C%2B%2BGuideForwxPythoneers

"How to Interpret the wxWindows Documentation: a Guide for Python Users"

[Kevin Ollivier]

Hi David,

Have you checked the wxPython demo? It has working code examples for almost every class available to wxPython users, and the demos can even be edited in real-time.

There is also the wxPython in Action book. Granted, I'd love for such good docs to be free, but Robin has already done lots of work for free and his and Neil's book offer a lot of valuable information on not just how to write wxPython apps, but how to write good Python apps in general, so the book is worth every penny in my opinion.

Regards,

Kevin

[David Lyon]

oh - ok

The demos don't show how to read a return code from a dialog...

Sorry - I didn't realise it was about money...

In any case it isn't. Why don't you guys do what normal open
source projects do and collect donations to do the documentation.

Heck.... pay me half of what you collect.... or pay Andrea..

Then you're doing very little work for the money...

TIME IS MONEY - you guys are wasting both....

that's my whole point....

so far my dialog box has cost me $300...

[David Lyon]

On Tue, Jun 16, 2009 at 8:50 AM, David Goldsmith <d_l_go...@yahoo.com> wrote:

With all due respect, two sincere questions: are you facile w/ C++ wxWidgets?  Have you read/done any of the tutorials?  Because, based on your comments, it sounds more like you need a more basic understanding of the underlying C++ library and of just how any basics are done in Python, as opposed to better/clearer documentation of the Python wrappers (which, having initially cut my wxWidgets teeth on the C++ library, I found to be a comparatively easy pleasure to use).  But if I'm wrong, my apologies.

Why should I have to learn C++ to write Python?

that's ridiculous...

When C++ code is left in the documentaion.. it just says that the job is half done...

What is wrong with me asking that the documentation be completed?

Yes, I read the tutorials... and forgot half of it....

Now I want to look something up quickly....

In Java documentation they don't include the C code.... find me any language that does this...

"Wrapper" means "Wrap". ie Cover....

If you are not "covering" the C++ code you don't have a proper wrapper...

right?

[David Lyon]

http://bioinf.wehi.edu.au/folders/james/wxPython/R/library/wxPython/doc/usermanual.html#MessageBox

I did more searching on the internet...

Robin answered the same question perphaps 400+ times on different
mailing lists.....

:-)

His VALUABLE time got wasted again..

I'm offering to make patches to the documentation....

I can patch the documentation at the same time as I work.....

This is a dictionary .com definition of wrapper...

1. to enclose in something wound or folded about (often fol. by up):
She wrapped her head in a scarf.
2. to enclose and make fast (an article, bundle, etc.) within a
covering of paper or the like (often fol. by up): He wrapped the
package up in brown paper.
3. to wind, fold, or bind (something) about as a covering.
4. to protect with coverings, outer garments, etc. (usually fol. by
up).
5. to cover (fingernails) with a sheer silk or linen fabric, as to
repair or strengthen them.
====================================================
6. to surround, envelop, shroud, or hide.
====================================================
7. to fold or roll up.

We shouldn't call wxPython a "wrapper".... if it doesn't intend to
hide...
surround.... envelope..... or shroud the C++ code.....

Forgive me... but I am just being logical and reasonable here...

Nothing else...

[Stephen M. Gava]

David, if you'd like some kind of wxpython documentation done in some
way different from any of the existing docs then feel free to spend some
time working on that for everyone's benefit, just like all the other
volunteers who spend their time on this project.

the beauty of an open source volunteer project, if you find something
lacking you're absolutely free to volunteer your own time to remedy that
percieved lack.

if that's not an option, using wxpython isn't compulsory. *shrug*

you might find if you post any questions you have on the much higher
volume users list: wxPython-users you'll get plenty of helpful answers
on questions about how to _use_ wxpython. you'll find plenty of other
wxpython users there who are only to willing to help answer any polite
question.

this low volume wxPython-dev list is for messages relating to the
development _of_ of wxpython, not development _with_ wxpython, so there
are far fewer eyes on your questions here and so less chance of getting
and answer to any specific usage question you might have.

greets,
Stephen.

[David Lyon]

On Tue, Jun 16, 2009 at 12:14 PM, Stephen M. Gava <elgu...@python.net> wrote:

David, if you'd like some kind of wxpython documentation done in some
way different from any of the existing docs then feel free to spend some
time working on that for everyone's benefit, just like all the other
volunteers who spend their time on this project.

Happy to...
 

the beauty of an open source volunteer project, if you find something
lacking you're absolutely free to volunteer your own time to remedy that
percieved lack.

Thats all I am talking about..
 

you might find if you post any questions you have on the much higher
volume users list: wxPython-users you'll get plenty of helpful answers
on questions about how to _use_ wxpython. you'll find plenty of other
wxpython users there who are only to willing to help answer any polite
question.

I posted here because it is SUPPOSED to be the development list....

but I keep get told no devel....

this low volume wxPython-dev list is for messages relating to the
development _of_ of wxpython, not development _with_ wxpython, so there
are far fewer eyes on your questions here and so less chance of getting
and answer to any specific usage question you might have.

ok - I'm talking fixing stuff up...

what are you talking about?

:-)

[Stephen M. Gava]

David Lyon wrote:>
> ok - I'm talking fixing stuff up...
>
> what are you talking about?
>
> :-)

david, just trying to be helpful...

thought if you had some particular questions on usage the user list
would be the best place for help. i thought you were originally having
some trouble using the dialog classes, my mistake if that wasn't so.

Stephen.

[David Lyon]

On Tue, Jun 16, 2009 at 1:49 PM, Stephen M. Gava <elgu...@python.net> wrote:

 

thought if you had some particular questions on usage the user list
would be the best place for help.

Seems a waste of everybodies time posting such a trivial question there....

Don't you think?

 

i thought you were originally having
some trouble using the dialog classes, my mistake if that wasn't so.

Yes...

Like a lot of others....

so why not nip it in the bud and let people contribute to the documentation along the way in an open source sort of way?

Every time the word "development" and "documentation" are used.. the subject gets changed...

hence my posting to this thread.....

[Kevin Ollivier]

Hi David,

On Jun 15, 2009, at 11:42 PM, David Lyon wrote:

On Tue, Jun 16, 2009 at 1:49 PM, Stephen M. Gava <elgu...@python.net> wrote:

 

thought if you had some particular questions on usage the user list
would be the best place for help.

Seems a waste of everybodies time posting such a trivial question there....

Don't you think?

No, that's sort of where newbies are supposed to go for help.

 

i thought you were originally having
some trouble using the dialog classes, my mistake if that wasn't so.

Yes...

Like a lot of others....

so why not nip it in the bud and let people contribute to the documentation along the way in an open source sort of way?

Every time the word "development" and "documentation" are used.. the subject gets changed...

No, it doesn't. You know full well that we discussed this in detail the last time you brought this subject up, and the discussion ended with you offering help. Now we've gone full circle, back to you writing emails complaining about it again.

Anyway, Robin or I will deal with this when one of us gets time.

Regards,

Kevin

[Kevin Ollivier]

Hi David,

On Jun 15, 2009, at 6:03 PM, David Lyon wrote:

>
> oh - ok
>
> The demos don't show how to read a return code from a dialog...

They do, actually, and it's pretty hard to miss. From the dialog
sample, around line 110:

# this does not return until the dialog is closed.
val = dlg.ShowModal()

if val == wx.ID_OK:
self.log.WriteText("You pressed OK\n")
else:
self.log.WriteText("You pressed Cancel\n")

It even prints what button you pressed in the bottom log window when
you run the dialog sample.

> Sorry - I didn't realise it was about money...
>
> In any case it isn't. Why don't you guys do what normal open
> source projects do and collect donations to do the documentation.
>
> Heck.... pay me half of what you collect.... or pay Andrea..
>
> Then you're doing very little work for the money...
>
> TIME IS MONEY - you guys are wasting both....
>
> that's my whole point....

Again you've missed something. You've somehow managed to miss the
Support link on wxpython.org, which offers several ways to financially
support the project from donations to paid support, the links to the
book, the link to wxPython t-shirts and goods, AND the donate link on
the project's page on sf.net. Anyway, the reality is that donations
and affiliate programs tend not to make very much money unless the
project is very large. Most large open source projects which pay their
volunteers have some sort of corporate sponsorship.

> so far my dialog box has cost me $300...

To figure out a problem that was clearly shown in the "Dialog" sample
code. I'd say that's a costly lesson on reading example code
carefully...

And BTW, if this is how you respond to people who are taking time out
of their day to help you learn wxPython, soon you'll find that no one
will be very interested in helping you. This isn't the arguments list,
this is the wxPython development list. Arguments is down the hall. :-)

Regards,

Kevin