[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Wxruby-dev] Summary of naming problems
From: |
Kevin Smith |
Subject: |
Re: [Wxruby-dev] Summary of naming problems |
Date: |
22 Jun 2003 15:40:15 -0700 |
On Sun, 2003-06-22 at 13:26, Richard Kilmer wrote:
> I personally like the Wx::Window.
Me too, generally. But in this case I'm conflicted. Your FreeRIDE
anecdote was very interesting, and moderately compelling.
> > CLASS METHOD
> > GetPosition (same)
>
> I would use get_position
>
> ...folks will expect to see documentation that aligned with this (not
> do the translation themselves) so the docs will have to be emitted in
> this form, but my experience with working with the documentation
> (latex) files this would be pretty easy to do.
But this means that if they grab a wxWindows book off the shelf, or if
they are trying to use a wxPython program as a sample, they will always
have to perform the mental translation themselves.
When working with the RubyGTK library, I really appreciated being able
to use any of the C documents out on the web.
Maybe the best answer is to provide GetPosition and get_position (and
perhaps getPosition), as aliases of each other.
> Wx::Globals.message_box
I don't think the extra level helps. Wx.message_box is better.
Still hoping for more opinions...
Kevin
Re: [Wxruby-dev] Summary of naming problems, Kevin Smith, 2003/06/24
RE: [Wxruby-dev] Summary of naming problems, repeater, 2003/06/24