matthiasm wrote: > > On 29.06.2008, at 18:39, Roman Kantor wrote: > >> matthiasm wrote: >> >>> 2: there is much more to the new API than the new namespace. Widgets are >>> named much more consistently (Fl_Tabs became TabGroup, Fl_Pack became >>> PackGroup to indicate that they are groups, etc. etc.). >> >> Well, if you want to be pedantic, then the names would be >> TabGroupWidget, PackGroupWidget etc and to express more descendant >> classes you would end up with very long names, which can be sometimes >> very confusing (like CheckLightButton, because light button is inherited >> from light button). If you have good documentation (ie generated by >> Doxygen) and/or self-regarding editor or IDE, then it is very easy to >> get the info about base class or inheritance tree. This things remind me >> "Hungarian" notation which I personally hate with passion. > > > Of course I don't want the entire inheritance in the names. A group is > so essentially different from a non-grouping widget that it would make > sense IMHO. > > I always understood and supported that FLTK has to be as stable as > possible. I am quite surprised to see though that even API changes seem > to be unwanted. But that's fine with me, either way.
For me, anyways, I'd like to avoid gratuitous API changes. That said, I have no problem breaking things where needed - I just don't think namespaces are a necessary API change for anything we want to change, and given our limited development bandwidth I'd rather see efforts focused on functional changes. -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
