On Fri, 2004-02-20 at 10:05, george young wrote: > On Wed, 18 Feb 2004 01:48:38 -0500 > "John (J5) Palmieri" <[EMAIL PROTECTED]> threw this fish to the penguins: > > > Thanks to your help, especially from Gustavo, I am proud to announce > > version 0.1 of my GtkSpell python bindings. This binding forgoes the > > use of pygtk-codegen because GtkSpell isn't GObject based. As always I > > welcome constructive criticism on how I could improve the wrapper. Not > > everything is finished and the test script is pretty ugly but the > > skeleton is there and it is functional. You can attach GtkSpell to a > > TextView and detach it. > > > > Next thing to do is to integrate it into the autotools build framework, > > clean up and implement the rest of the interface and perhaps get it > > included in the next release of PyGTK. > > > > You may obtain the latest code at: > > > > http://martianrock.com/dropzone/pygtkspell-0.1.tar.gz > > The notion of a spellchecker for pygtk is intriguing, but it would > be very helpful if your announcements included a brief description > of what it is, and what it's requirements are. > > I downloaded from your link and typed make and only then found that > it requires something called gtkspell, which I did not know existed > and don't know where to find. I would suggest a brief "README" file > in the distribution, saying what this package does, what version(s) of > python, gtk, and pygtk are needed, and links to source of any > extra packages that it needs.
I'm sorry about that I was just so excited to get it working that night that I wanted to release it to get comments on how I wrapped the library. Being that it was my first attempt at wrapping a library with python from scratch I wanted to find out what I did wrong or could do better :-) Obviously packing it all up better is one of those things. I will be working this weekend on autoolizing the package and making it GNU compliant (README, ChangeLog, Licence, Authors, etc.). For now you can get GtkSpell from http://gtkspell.sourceforge.net/. > I know its hard when you've been up to your eyeballs in code to > keep in mind that lots of people have no idea of your particular > domain of endeavor. I will be more careful in the future. > Please don't mistake my tone for disapproving or complaining: I appreciate > *very much* that you have made something and are contributing to > the community. I just think that it would be better received, and used, > if you gave a bit more helpful info. Not at all. I take your comments as a way to better my software. After all, my goal is to have people use and enjoy my work. Again, usually I'm not in such a rush but it was so exciting when things worked on the first try (I figured it was going to take me weeks to learn how to wrap with python) I sort of just pushed it out the door. -- J5 _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
