Re: [Fxruby-users] New to list - general questions...
Status: Inactive
Brought to you by:
lyle
From: Hugh S. S. E. E. <hg...@dm...> - 2003-06-05 15:42:31
|
On Thu, 5 Jun 2003, ly...@kn... wrote: > Yes. The list was only created the day before yesterday ;) Oh! Thanks. > [...] Thanks for the Faq links. > but you are correct that we don't have a FAQ list dedicated specifically to > FXRuby. I guess part of the challenge will be figuring out which questions > are FXRuby-specific and which questions are more in the domain of FOX Yes, but then metaquestions can go in as well, "where should I look for questions about ..." > programming in general. For example, the FAQ about calling create() on > windows, icons, etc. after the application's already running is a problem > that any FOX programmer will confront at some point, whether he's using > FXRuby, FXPy, EiffelFOX or, worst case, C++ ;) Could one apply the Mediator Pattern to this, and provide direct links to where people need to go, rather than telling them to poke around such and such websites? I think that would be useful provided we can frame the questions so they are not brittle WRT version changes in FOX. I think there may well be FXRubyists who never program FOX directly w/o ruby, so this would seem to be sensible from this viewpoint. > > > And onto FXRuby itself: Most of the API calls wrap C++ pretty [...] > > FXinteger, or does one have to create the objects explicitly? I > > don't think I'd be able to infer this from looking at C++ docs. > > Yes, for the most part it should be a very obvious mapping from C++ to Ruby. > If the C++ function expects a signed or unsigned integer type (i.e. FXshort, > FXushort, FXint or FXuint) the Ruby method probably expects an Integer. If Thank you. I think this is something worth adding to a FAQ, since it is implementation dependent (you *could* have chosen to make FXushort construction explicit; I'm glad you didn't). [...] > well, such as how arrays of values are passed back and forth. For a good > summary of the kinds of differences to expect, see this chapter from the > FXRuby documentation: > > http://www.fxruby.org/doc/differences.html Thanks, hadn't found that. > > Also, your first stop for reference documentation on the Ruby API should be > the docs found here: > > http://www.fxruby.org/doc/api Yes, that's a nice job, coming along well. Thanks. Can this be downloaded as a tgz, or zip file for browsing off-line please? When I tried to run Rdoc on the FXRuby I'd downloaded I didn't get so much documentation embedded. If your using different/newer sources it would be nice to get hold of those so I can send you patches when I feel able to contribute. [I'd actually rather not have write access to cvs, because I'm not confident about using it, and would hate to trash your CVS tree!] > > The problem is that those are still under construction (although I'm getting > closer!). Use the C++ library's reference documentation as a fallback. > > Hope this helps, > > Lyle > Thank you. Hugh |