Peter, It's been a few months since I've had a chance to work with GTK-Server. But I had the Flu this last weekend, so I was laid up in the house for a couple of days and I had some time to play around with it and NewLISP. Once again, I would like to thank you for your work on this great tool. I've learned quite a bit of C-Programming since I spoke to you last, and I've set up a Linux box at home, and at work. (I'm using Debian though, not Slackware.) The C Programming language has proved more of a challenge than I thought it would be. I'm am picking it up, but a slower pace than I would like. I really got thrown with the whole subject of pointers, but I'm getting a handle on it now. At any rate, I've got a couple more questions for you. [1] What is the purpose of the "gtk server-callback WAIT" function that is included in the main loop portion of the GTK-Server/NewLISP demo? (I couldn't find any info on this function in the GTK API docs, and I'm guessing by the name that it is a function internal to GTK-Server.) [2] It seems like the GTK-Server simply accepts GTK function calls and arguments as a single string from NewLISP. Is this a correct observation? I am really curious how the GTK-Server works. Do you parse those strings and translate them into actual C calls? If so, how does this work? Are the function calls in C compiled and executed as they are recieved, or are you using some other mechanism? [3] I'm interested in taking a look at the code for GTK-Server. I'd still like to contribute improvements and assist with maintenance as my knowledge of C programming improves. Is there any documentation on how the program works, or should I just take a look at the source code and ask my questions on this mailing list? Thanks Peter, Landon P.S. - I hope to wrap many of the GTK-Server functions in NewLISP functions. This will allow NewLISP users to use GTK GUI's without having to aquire an extensive knowledge of GTK-Server. I'll keep you posted on how things work out. On 2/2/05, Peter van Eerten <administrator@xxxxxxxxxxxxxx> wrote: > > Hi Landon, > > (1) My primary development platform is Slackware Linux (www.slackware.com > ). > First I take care the program compiles on Linux; the GTK-server is > primarily > intended to be used on Linux anyway. If everything works fine there, then > I > switch to Win2000 or XP to make a port. > > (2) The one and only on Linux: gcc (Gnu C Compiler). This has become an > excellent compiler, and has proven to be stable and reliable. Everything > in > Linux is compiled with GCC, including it's kernel. On the Windows > platforms I > use the Windows-port of GCC which is known as "MinGW" (www.mingw.org). It > is > also nice to know that the GCC/MinGW compiler is free (like in "freedom"), > and > the resulting binary's can be used for any purpose. > > (3) Actually yes, I had programmed with GTK before, so for me it was easy > to go > on with the GTK-server since the API already was familiar. You could start > using > MinGW as well since your code might be easier to port to other platforms > (like > many Unix versions, Linux, MacOSX, and so on). Also GTK for Windows was > ported > using MinGW, though you can compile it with VisualC as well. > > The book I learned most from, is called "The C Programming Language" > written by > Kernighan and Ritchie. As I understand it, these 2 men have actually > invented > the C language, and who can explain better than the inventors themselves? > Until > today I lookup issues in this book. > > The GTK-libs hosted at Tor's page are used to develop with GTK. Those libs > are > needed for the GTK-server on the Windows platform as well (except for the > actual > source code of the GTK libraries). So the header files, the extra > libraries, > pkgconfig, etc... are needed - a lot of stuff to download. > > Again, my vision is coloured by my Unix background. Therefore I would > recommend > the GCC compiler. With MinGW on Windows, and also the MSYS shell, you will > have > extremely powerfull tools to develop with C. As IDE I always use VI > Improved > (www.vim.org), which, for first users, will be a very user-unfriendly > interface. > But the original VI is used as default editor in Unix, so I am used to it. > And > besides, VIM is created by a Dutch guy, and I am a little bit of a > patriot... > ;-) > > Bloodshed I've heard of, but never used. > > Regards > > Peter > > > Citeren Sunburned Surveyor <sunburned.surveyor@xxxxxxxxx>: > > > Peter, > > > > I would like to learn some C programming so I can understand how GTK > > Server works, and perhaps contribute to your efforts. > > I purchased Sams "Teach Yourself C in 21 Days", and I'm getting ready > > to dive in. > > > > I had a couple of brief questions for you before I get started. > > > > (1) Do you work on Linux or Windows? Or do you work with both? > > (2) What compiler do you use? > > (3) If I wanted to get set up for some programming with C and GTK on > > Windows, would you be able to give me some pointers, or do you only > > deal with GTK on Linux? > > > > I checked out Tor's page, but it was a little intimidating, and the > > other GTK Page at dropline.net doesn't look like it is being > > maintained anymore. I'm not running on Linux. (Not yet anyways, but > > hopefully soon.) > > > > I was thinking of using Bloodshed Dev C++ for my IDE, or the CDT > > Extension for Eclipse. > > > > What are your thoughts? > > > > Landon > -- > http://www.gtk-server.org > >