> That looks like more well phrased notes for you to add to the FAQ pages
> and so on...! :-)
>   <snipped clear explanation from Duncan..>

Why, thank you, kind sir!

Seriously though, when I wrote the "What are the versions of FLTK?"
article, I just wanted to provide a paragraph describing the main
features of each release, and a single line showing its status.
IMO, if I add more text it's not really pithy enough for a FAQ entry.

I discovered that as an authorised developer, I appear to have access
to update the web pages via the options on the Web Site tab. Maybe.
So I was looking around to find whether I can add brackets around
the FLTK-2.0 snapshot link, or a Version Info link to the article.
Again, possible, but I'd rather not cock it up and mess up the site.

I also found that I appear to have access to create a new poll! That,
along with Andreas' comment that "fltk2 appears popular" has had me
thinking whether the current poll questions could be re-phrased at
some point in the future to discover why people use a given version.

Why do you [still] use a particular FLTK version?

 - FLTK-1.1.x : for the stability
 - FLTK-1.1.x : too much code to migrate

 - FLTK-1.3.x : for the UTF-8 / printing
 - FLTK-1.3.x : for the online support
 - FLTK-1.3.x : to help with development

 - FLTK-2.0.x : for the UTF-8 / printing
 - FLTK-2.0.x : for the cleaner interface
 - FLTK-2.0.x : too much code to migrate

 - FLTK-other : please provide a comment

I've deliberately left out 1.0.x and 3.x because there is a limit to
the number of options, and maybe then we don't have enough to cover
1.1.x, 1.3.x and 2.0.x in the same poll. I wonder whether are some
more generic questions that could be posed regardless of version?

However, such a poll would be too similar to the current one, so it
probably makes sense to postpone it until after a completely different
poll question. And by then, the landscape might have changed.

D
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to