Dejan Lekic wrote: > Ok guys, this is just a suggestion and please tell me what You think - > does it make sense or not? > > I would like to have a fltk1 and fltk2 major groups with subgroups that > have the same name as nowadays fltk.* subgroups. > So, to illustrate what I have in mind: > > fltk1.development > fltk1.opengl > fltk1.bugs > fltk1.commit > fltk1.general > > similarly we would have > > fltk2.development > fltk2.opengl > fltk2.bugs > fltk2.commit > fltk2.general
Might be worth thinking about something like this. However, what should be done with the old contents? Let fltk.* as is, and split off fltk1.* or fltk2.* and say "fltk.* is for flkt1 and has all the old contents, and fltk2.* is for fltk2 only". Or vice versa? Or, as you suggested, two new hierarchies, and fltk.* stays and becomes read-only? Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
