To: Benjamin.Monate at lri.fr Cc: lablgtk at kaba.or.jp Subject: Re: Galde support [was: Re: Accessing labels of GTree.tree_item] In-Reply-To: <20010515113847.74211da1.Benjamin.Monate at lri.fr> References: <20010514131510.A3295 at lambda.u-strasbg.fr> <20010515181709D.garrigue@kurims.kyoto-u.ac.jp> <20010515113847.74211da1.Benjamin.Monate@lri.fr> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010515184710E.garrigue at kurims.kyoto-u.ac.jp> Date: Tue, 15 May 2001 18:47:10 +0900 From: Jacques Garrigue Lines: 32 From: Benjamin Monate > > Well, glade support for one thing is still in preliminary stage. > > There is always work to be done... > > By glade support, do you mean interfacing libglade in ocaml ? > > I am currently writing a filter that takes a Glade xml file as input and > outputs a set of ocaml modules where the user just has to write the > callbacks' body. This is what glade does for C. > > What do you think of this approach ? This approach works also, but has a big drawback: you cannot edit your files afterwards. So this is nice to start an application, but after that you have to code by hand. My idea was to both interface to libglade, and generate wrappers to access the widgets build by libglade. To make it even more modular, these wrappers could eventually be compiled indepently, and modified by inheritance. This way you can modify easily details of the layout of your application, without having to change the ML code. By the way, if you have a parser for glade description files, I'm interested. In fact, this is almost the only item I need to complete my scheme. Cheers, Jacques