Sanel Zukan wrote:
> ...
>> The pre-1.0 FLTK had the same problem, and we just had to draw a line
>> in the sand and focus on putting out a stable release, branch, and
>
> I'm not very good with pre-1.0 history; did 1.1 introduction required
> significant changes in pre-1.0 powered code ?
Pre-1.0 to 1.0 didn't introduce any major changes, we just did a few
months of bug fixes.
1.0 to 1.1 issues are covered here:
http://www.fltk.org/doc-1.1/migration.html
Basically, there was some API renaming (with a define to also use
the old names) and symbol labels became the default, but 1.0.x
code largely worked without changes on 1.1.x.
>> then let Bill and others play in HEAD/trunk while we maintained 1.0
>> (and later 1.1).
>
> I would propose going even further: move next official version in
> trunk and make something like 'future' or 'xyz' branch for next major
> version, that will not be publicly known (but should be accessible),
> where Bill and interested parties can work (with appropriate
> known roadmap, of course) in peace without hate mails about frequent api
> changes and compilation issues.
:) That sounds good to me!
>> Right now 2.0's foundation is cracked and the
>> ground has shifted. Before you move on to 3.0, you need to get 2.0
>> to at least a 1.0 level of stability...
>
> Yes, but IMHO this will work only if current 2.0 does not start to reshifting
> again. Or... maybe it is a good time now to rethink some things, like Bill
> initiated moving Group into Widget, layout design (I am still for keeping
> it fully compatible with 1.x) and etc.
>
> Maybe is too early to speak about the future, but there will be
> even more custom widgets, custom code, complex applications... and at
> some point if potential 3.0 does not be unobtrusive replacement... the
> whole story will be repeated again.
I started work on 1.1 several years ago when it was apparent that 2.0
was not nearing stability any time soon. There were constant battles
over implementation changes, and we spent a lot of time "fixing"
things after back-and-forth commit wars... (Sound familiar? :)
1.1 was basically 1.0 + some of the best things from 2.0 along with
an updated file chooser and various popular third-party widgets.
1.n (n == 2/3/5/whatever) can be another update to 1.x with the
same (limited) goals - add the latest stable/accepted changes from
2.0 and other sources, test the hell out of it, and then release as
a new stable branch.
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike at easysw dot com
Internet Printing and Publishing Software http://www.easysw.com
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
