[lgtk-devel] [PATCH:] A few more button functions

[Sverker Wiberg]

On Mon, 2004-03-01 at 18:43, Mario S.Mommer wrote:
> Hi,
> 
> Sverker Wiberg <sverkerw at swipnet.se> writes:
> > Here's a patch to add gtk-button-new-from-stock as well as functions to
> > handle a buttons label and relief state.
> 
> Commited. Thanks!
> 
> > These functions (except for gtk-button-set-label) are showcased in
> > 'button-flavours.lisp', which also contains a very first sketch (done in
> > five minutes) on a somewhat thicker and more Lispy binding for GTK.
> 
> Added button-flavors as an example.

Thanks.

> I think that I should add an
> utility package for the kind of lispy extensions you mention.

Sounds fine.

> > Right now I'm thinking on adding docstring support to def-binding and
> > friends. Any thoughts?
> 
> It would not hurt, I guess. Where do you propose to put the docstrings?

In the syntax? In the usual place, after the name (&optional of course),
as in

   (def-binding "bogo_sort"
      "Sorts the characters in STR an incredibly stupid manner; i.e. by
doing random shuffles until it is sorted. It is not guaranteed to
terminate."
      (void (c-string)))

Under the hood, I'll put the string wherever DESCRIBE and APROPOS
expects to pick it up. Looking in CLtL2, that would be DOCUMENTATION
function.

> As far as lgtk is concerned, adding functionality by hand is only a
> temporary solution. I would much prefer to machine-generate bindings
> by the ton. I think I have a solution, but I'm not sure that it makes
> much sense to add doctrings to that.

Unless there's a way to autogenerate the docstrings too (HHOS, maybe we
could snarf the Doxygen comments...)
[...]

> On the other hand, I always thought of defbinding & friends as a
> facility that would grow beside lgtk until it was mature enough to
> stand by itself, and then would get its own project. From that point
> of view, docstrings make a lot of sense.

Anyway, I'll start with the easy stuff, just adding docstrings to the
macros themselves.

/Sverker