> Though to a new user, a lot of things are important, such as getting > an initial 'feel' for each widget's way of working. Code examples can > help that, and I think consistent form will give the reader the added > "warm and fuzzies" that there's some consistency to the docs; > documentation features they see in one widget they'll probably expect > from others. > > I'm going to try focusing on the widgets that I know have been > historically thin or too terse. Probably going to be a long process > that will reach beyond 1.3.x's release date.. which should be fine.
As I have been working on each *.dox file, I have had the old 1.1.x html page from the web site in another browser tab so that I can check what it used to do before I started tinkering. The other day I had the 1.1.x "html with comments" page, and it struck me that we should also review these comments too. Sorry if I'm being Job's comforter. > I know for 1.3.x to go out, we mainly want to get the code stable, > so I figure that's what you guys are all on top of. One STR burger at a time, but there are some T-bone steaks involving UTF-8 and Mac/Windows that are too big for me :-( Cheers D _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
