On the cursor side, I guess this means there's no way to get the current cursor?
On Wed, Jun 25, 2008 at 12:50 AM, matthiasm <[EMAIL PROTECTED]> wrote: > > On 25.06.2008, at 09:25, Craig D wrote: > >>> Is there any interest in general code quality cleanup? >> >> This seems like such a religious issue but a style guideline would be >> useful for community code, especially for us ancients for whom IDE >> means >> emacs. > > > A style guide? Like this one? > > <http://www.fltk.org/cmp.php#CODING_STANDARDS> Ah, there is one. It all looks good to me... except that I've seen an awful lot of fltk that doesn't follow it! It looks like it has more of a fltk2 bent and an assumption that fltk2 was going to "happen" real soon now (e.g. the ".h for headers, .H for compatibility headers" when *all* the headers in fltk1 are .H). As far as the guide, any argument about adding: - remove the bit about tabs, and say "indents are two spaces, tabs are not allowed" - 80 column max for lines > As you may guys may have read in earlier posts, we are currently > discussing how to get fltk 1 and fltk 2 back together again and bundle > forces to streamline the process. Since fltk1 and fltk2 actually did > branch from the same code base quite a while back, if would be useful > to keep the code as is for a while to make diff's easier. > > Once we are back to stable, I won't mind a code and API cleanup at all. I'm all in favor of improving fltk2 rather than fltk1 if it represents the future. But does it really? Is there any kind of timeline for when that's going to happen? My impression is that it's been many years. Maybe I should be asking how I can help with fltk2 then even though I've never used it? I might if I had some confidence that it was going to come out of "testing" any time soon, like I might have used it if I had any such confidence. So what this says to me is "no, don't fix anything, wait until we've got this new thing out, which should be any year now". So that's not very encouraging. Speaking of not very encouraging, I have a STR #1952 which has been open for quite a while now. It's a pretty serious bug, with a pretty easy fix, but there hasn't been any sign that anyone actually reads the reports. I know there's definitely interest in encouraging new contributors, so this seems to be sending mixed messages. Does someone with mac knowledge feel like taking a look? > Which also explains the tabulator chaos. We did agree on two spaces > per indent at least. If we now manage to agree on how amny spaces are > in a tab, we will be fine ;-). Understood, any code base (especially an open source one) needs periodic cleaning. Even if it's easy, if no one does it, it will never happen. And it hasn't happened for many years. I would be willing to do some of it if someone is willing to review and commit it. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
