Re: [Vimprobable-users] Features for next version
Vimprobable is a lean web browser optimised for full keyboard control
Brought to you by:
hanness
From: Hannes S. <ha...@yl...> - 2011-08-14 20:26:07
|
Hi! Daniel Carl <dan...@gm...> wrote: > On Sat, Aug 13, 2011 at 09:14:25PM +0200, Hannes Schüller wrote: > > As announced already, I would put the version 1 branch into > > bug-fixing mode. The question is: Should we do the same for the > > version 2 branch and make future development on a completely new > > one? > > I'm not even sure if it's a good idea to separate vimprobable1 and > vimprobable2 into different branches. It make the maintaining a > little easier, but I think to apply bugfixex also to the version 1 > could be forgotten. I'm not using version 1 and so I apply patches > only for version 2. I'm not familar with the version 1, but could we > use precompiler flags to let the user decide which version to > compile, or would this make the sources to complicate to understand? For once, yes, it would increase source code complexity, yes. Concerning bugfixes, the opposite of what you assume is the case I'd say: different branches make more work. > > On a related note, there is the question of version numbering. > > Should we have: > > - Vimprobable1 1.0 and Vimprobable2 1.0 or > > - Vimprobable 1.0 and Vimprobable 2.0? > > Could we abandon the deviding of version 1 and 2 and have only one > flexible to compile vimprobable? Vimprobable1 could be a vimprobable > compiled with tiny option, vimprobable2 compiled with the huge > option, or so. See above, this would still increase code complexity, making it much less readable, less reliable, more prone to errors and race conditions etc. Hannes |