Date: Mon, 14 May 2001 13:15:10 +0200 To: Jacques Garrigue Cc: Benjamin.Monate at lri.fr, lablgtk at kaba.or.jp Subject: Re: Accessing labels of GTree.tree_item Message-ID: <20010514131510.A3295 at lambda.u-strasbg.fr> References: <20010511135448.43d7e413.Benjamin.Monate at lri.fr> <20010511232023F.garrigue at kurims.kyoto-u.ac.jp> <20010511210045.3144e5bb.Benjamin.Monate at lri.fr> <20010514120202Z.garrigue at kurims.kyoto-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010514120202Z.garrigue at kurims.kyoto-u.ac.jp>; from garrigue at kurims.kyoto-u.ac.jp on Mon, May 14, 2001 at 12:02:02PM +0900 From: Sven LUTHER Sender: Sven LUTHER On Mon, May 14, 2001 at 12:02:02PM +0900, Jacques Garrigue wrote: > > You refer to Gtk 2. > > Do you have started to port lablgtk to the latest version of Gtk (the > > "feature freeze" ) ? > > You can see it from two sides. > One is to make LablGTK compile with the current version of Gtk. > I think this is almost already the case: since the Win32 port of Gtk > is already on the 1.3 branch, I added a few ifdefs to provide > compatibility. > > But what you want is probably the other way round: access to Gtk2 > functionality. > And there we enter the dark country of multiple version support. > This is why LablTk does only support features in Tk4.2, while the > current version is 8.3: I found no clean way to provide multiple > versions at the Caml level, and this would be too much work to > maintain multiple versions simultaneously. mmm, What about starting a gtk2.0 or whatever cvs branch, that people who are ready for it could test and contribute code to. You would still maintain the gtk1.2 branch as the head branch. Once gtk2 ships, then you would just start to make the gtk2.0 branch the head branch, and still people could have access to the older gtk1.2 branch if they need it. Anyway, you told yourself that the 1.2 support was almost fully there. > So, my plan is just to wait for the release of Gtk2, and start the > port at that time, so that I can work on one standard version. But then how long would it take you to have it ported to gtk2.0 ? Will this be longer than the time it will need to become 'popular' ? And if yes, by how much. > All LablGTK versions after that point will require Gtk2, so this > should not happen before Gtk2 is popular enough. I don't think i agree with you much, especially as i don't know what you call being 'popular'. If it is until it comes standard with all the major linux distros, then this may be a pain for all those people using/developping more recent versions of gtk+, don't you think. I remember this being the case with mlgtk when 1.2 was released. Also i feel that the 2.0 deployement will be much faster than the 1.2 one was, as it include lots of features that people have been waiting for since a long time, not sure though. All in all, it would be nice to have access to a 2.0 branch, so people playing with gtk1.3 already can give it a try. Also do you know how much did really change between 1.2 and future 2.0 ? > Of course anybody is free to start interfacing widgets before that... Sure, but making a 2.0 cvs branch available would make things easier ... Friendly, Sven Luther