Here is my draft of an update to CLIM tutorial.
http://clemens.endorphin.org/A%20Guided%20Tour%20of%20CLIM%202006-draft.pdf
I plan to put it into the mcclim repository under Doc/, so others can enhance it if desired. I will probably post an other update myself, as I originally planned to write more (incremental updates, accepting- values and a spreadsheet examples are missing). But I rather felt like it's better to release it early than never.
Feedback is appreciated.
Clemens Fruhwirth clemens@endorphin.org writes:
http://clemens.endorphin.org/A%20Guided%20Tour%20of%20CLIM%202006-draft.pdf
Feedback is appreciated.
Hello,
I'm going through the tutorial, and being very much clim-illiterate here are my few comments that I wrote down while doing so:
- The tutorial is pretty cool. The introduction addresses what CLIM is good for, and how it relates to "normal" GUI toolkits, the terminology, etc... Very enlightening.
- There's a typo in page 2: "(...) equally to the _build-in_ gadget types."
- Mentioning the CLIM-USER package (where we can try the examples) might be a good idea.
- I'd suggest restructuring the code in way that doesn't generate warnings about undefined functions. Eg: I was confused about why my McCLIM didn't seem to have this update-draw-pane function used in the draw-frame commands.
- The draw-frame example doesn't work for me (SBCL 0.9.8 and McCLIM HEAD, CLX backend). I get an error saying: "The function (SETF RECTANGLE-EDGES*) is undefined." Hmm, and I get this same error with the file-browser example.
- Another typo: in figure 7, "The second _color_ (...)".
- I'd love to see figure 7's code in action. However, count-package-symbols isn't defined anywhere. (Ah, and in fig. 7 it actually reads _count-package-symbols-package_). Sure, it is trivial to implement, but still. :-)
- Is the source code for the examples available somewhere? That'd be useful.
Hope this helps in some say,
I'm also reading it, but haven't gotten all the way through it yet
Luís Oliveira wrote:
Clemens Fruhwirth clemens@endorphin.org writes:
http://clemens.endorphin.org/A%20Guided%20Tour%20of%20CLIM%202006-draft.pdf
Feedback is appreciated.
Hello,
I'm going through the tutorial, and being very much clim-illiterate here are my few comments that I wrote down while doing so:
The tutorial is pretty cool. The introduction addresses what CLIM is good for, and how it relates to "normal" GUI toolkits, the terminology, etc... Very enlightening.
There's a typo in page 2: "(...) equally to the _build-in_ gadget types."
Mentioning the CLIM-USER package (where we can try the examples) might be a good idea.
I'd suggest restructuring the code in way that doesn't generate warnings about undefined functions. Eg: I was confused about why my McCLIM didn't seem to have this update-draw-pane function used in the draw-frame commands.
The draw-frame example doesn't work for me (SBCL 0.9.8 and McCLIM HEAD, CLX backend). I get an error saying: "The function (SETF RECTANGLE-EDGES*) is undefined." Hmm, and I get this same error with the file-browser example.
Another typo: in figure 7, "The second _color_ (...)".
I'd love to see figure 7's code in action. However, count-package-symbols isn't defined anywhere. (Ah, and in fig. 7 it actually reads _count-package-symbols-package_). Sure, it is trivial to implement, but still. :-)
Is the source code for the examples available somewhere? That'd be useful.
Hope this helps in some say,
Luís Oliveira luismbo@gmail.com wrote:
- I'd suggest restructuring the code in way that doesn't generate warnings about undefined functions. Eg: I was confused about why my McCLIM didn't seem to have this update-draw-pane function used in the draw-frame commands.
The draw-frame example had a missing closing parenthesis. Please retry with the examples checked in CVS. (Doc/Guided-Tour)
- The draw-frame example doesn't work for me (SBCL 0.9.8 and McCLIM HEAD, CLX backend). I get an error saying: "The function (SETF RECTANGLE-EDGES*) is undefined." Hmm, and I get this same error with the file-browser example.
I don't use that function directly. Can you paste a backtrace?
- Is the source code for the examples available somewhere? That'd be useful.
Sure, in the CVS!
Thank you for your feedback.
On Feb 9, 2006, at 2:25 PM, Clemens Fruhwirth wrote:
Luís Oliveira luismbo@gmail.com wrote:
- The draw-frame example doesn't work for me (SBCL 0.9.8 and McCLIM HEAD, CLX backend). I get an error saying: "The function (SETF RECTANGLE-EDGES*) is undefined." Hmm, and I get this same error with the file-browser example.
I don't use that function directly. Can you paste a backtrace?
This is caused by a recent check in of mine. Be sure you recompile all your CLIM files, both in McCLIM and your own stuff.
Tim
Clemens Fruhwirth clemens@endorphin.org writes:
Here is my draft of an update to CLIM tutorial.
http://clemens.endorphin.org/A%20Guided%20Tour%20of%20CLIM%202006-draft.pdf
I plan to put it into the mcclim repository under Doc/, so others can enhance it if desired. I will probably post an other update myself, as I originally planned to write more (incremental updates, accepting- values and a spreadsheet examples are missing). But I rather felt like it's better to release it early than never.
Feedback is appreciated.
I've read it through, and from this first pass have a list of small typos, stylistic changes and the like that I'd like to suggest. I would have sent a diff with the changes, but unfortunately the current source is one-line-per-paragraph, which would make the diff extremely noisy and unclear. Would it be possible to insert line breaks in the source?
The thing I would most like to see in terms of the document as a whole, I think, is a changebar (somewhat like in the second edition of CLtL) indicating the changed material, so that the reader can see what is essentially unchanged from the 1990 version.
Cheers,
Christophe
Christophe Rhodes csr21@cam.ac.uk writes:
Clemens Fruhwirth clemens@endorphin.org writes:
Here is my draft of an update to CLIM tutorial.
I've read it through, and from this first pass have a list of small typos, stylistic changes and the like that I'd like to suggest. I would have sent a diff with the changes, but unfortunately the current source is one-line-per-paragraph, which would make the diff extremely noisy and unclear. Would it be possible to insert line breaks in the source?
Find attached a diff against the linebroken version in Doc/Guided-Tour. These changes are suggestions -- where I've picked up on something, it may be that you can think of a better way to express it than I have.
Cheers,
Christophe
-
Christophe Rhodes -
Clemens Fruhwirth -
Luís Oliveira -
Scott Williams -
Timothy Moore