Now I'm using 'labltk' with ocaml-3.09.3, and realized that
some widgets such as 'labelframe', 'spinbox', etc are missing.
I like to using 'labltk' because it's easy to use, but
when I check the tk8.4's demo, I found many functions are
not supported in 'labltk'.
Is there any plan to upgrading 'labltk'?
Should I use 'lablgtk2' or something instead of 'labltk'?
Caml-list mailing list. Subscription management:
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs
> Now I'm using 'labltk' with ocaml-3.09.3, and realized that
> some widgets such as 'labelframe', 'spinbox', etc are missing.
> I like to using 'labltk' because it's easy to use, but
> when I check the tk8.4's demo, I found many functions are
> not supported in 'labltk'.
The widgets supported in camltk/labltk are those of tk8.0.
New widgets were not added to keep compatibility, but since Tcl/Tk
seems to have finally converged on 8.4, this might be a good idea to
add the new widgets now. This is easy to do: mainly editing the
Widgets.src file. But this is time consuming: one has to check by hand
the Tcl/Tk documentation to find all the missing functions and
parameters... So this will probably not be in 3.10.0, but could be
done in a reasonably close future.
> Is there any plan to upgrading 'labltk'?
> Should I use 'lablgtk2' or something instead of 'labltk'?
Use the one that fits your needs. There are more widgets in gtk2, but
they can be harder to use.
Now I see. Thank you for your reply.
Let me ask another question.
# Maybe it's a FAQ...
Why camltk and labltk both exists?
These look like twins for me.
What is the role of these two libraries?
(I think if there is no need to use the camltk...)
The original library was CamlTk, and LablTk was actually created by
hacking the automatic generation tool included in CamlTk.
As a result, for a long time only CamlTk was available, and for
instance the MMM web browser was developped using CamlTk. Many
examples are available, and CamlTk is described in one of the rare
books on OCaml written in English.
For all these reasons, it is necessary to continue supporting it, and
the current implementation does it at a very low cost, by using the