On 28.03.2008, at 12:33, MacArthur, Ian (SELEX GALILEO, UK) wrote:
>> * better typing: we can finally break the binary interface,
>> so we will
>> change some types in FLTK 1.3. Widget coordinates will be 32
>> bit, for
>> example. At this time, we will also weed out some other limitations
>> that could not be fixed due to ABI issues.
>
> This will include making some of the base class methods virtual, and
> moving some things around from the public/private domains, etc.?

Absolutely. This refers to all ABI changes that we held back.

>> * Doxygen manuals: only *after* utf-8 is fully implemented and types
>> are changed, we will move all documentation into the FL
>> header files,
>> using the Doxygen syntax. Doxygen is a widely accepted standard for
>> library documentation with an insane ammount of options to create
>> documentation just the way we like it. Please note: Doxygen
>> docs go in
>> the headers. Documentation about the internal workings of
>> FLTK go into
>> the source code. I will provide some sample doxygenization in
>> the next
>> days.
>
> Can this not be started "out of order" too? (If there's someone  
> willing
> to get started on it...)

Not until we merged the UTF-8 code in and have it running. Once the  
Doxygen comments are in, any attempt to "diff" will lead to an  
overwhelming mess.

> As I understand it, the API will be documented using doxygen  
> comments on
> the header files.
> The implementation details and internal workings will be documented in
> the c/cxx files - also using doxygen comments? Or not?

Small hints don't need to use Doxygen. Larger blocks that help  
understand what's going on should be marke @internal, so the comment  
can be added as an option.

>>
> What are we going to call fltk-config and the libs themselves?
> During the transition I (and I guess others) am going to have
> fltk-1.1.8, fltk-2 and fltk-1.3 around... At present, I have the
> following:
>
> Fltk-1.1   : fltk-config, libfltk.a, etc.
> Fltk-2     : fltk2-config, libfltk2.a, etc.
> Fltk-utff8 : fltk-utf8-config, libfltk-utf8.a, etc.
>
> Where will fltk-1.3 fit in?

Good point. I will give this some though.

----
http://robowerk.com/