Re: [Geeqie-devel] GTK2 GTK3

2016-07-04 Thread Roger
>Currently I tend to keep the ifdef way. But the private function name >space has some potential and some elegances. I don't see a way at all in >different branches. Long term that is not manageable. > >On the other hand, if GTK3 gets to a usable state, I would vote to drop >GTK2. But I don't see t

Re: [Geeqie-devel] GTK2 GTK3

2016-07-03 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Colin, Am So den 3. Jul 2016 um 18:39 schrieb Colin Clark: > I am somewhat lost in understanding how this kind of development works > (I only worked on embedded micros - very different). Well, it works how it is best to archive. :-) If somethi

Re: [Geeqie-devel] GTK2 GTK3

2016-07-03 Thread Greg Troxel
Colin Clark writes: > What is the typical arrangement for development of an application that > compiles on both GTK2 and GTK3? Is it standard to maintain two separate > development trees? Generally, one or the other is enabld via something like autoconf and there are ifdefs when necessary, wi

[Geeqie-devel] GTK2 GTK3

2016-07-03 Thread Colin Clark
Hi Klaus I am somewhat lost in understanding how this kind of development works (I only worked on embedded micros - very different). What is the typical arrangement for development of an application that compiles on both GTK2 and GTK3? Is it standard to maintain two separate development trees?