On 27.03.2010, at 18:56, Robin Rowe wrote: > Albrecht Schlosser wrote on 01:42 Mar 19: > > << FLTK 2.0 is currently not supported and outdated, many things are > broken. You shouldn't use it if you don't need to (because you > have old code).>> > > Does that mean FLTK2 has been abandoned or no Windows 7 support?
There are currently no developers for FLTK 2, and in the past there were no regular bug fixes for a long time. See the bug list for fltk 2 at <http://www.fltk.org/roadmap.php#2.0> . Thus, abandoned describes it best. But we have plans to integrate the FLTK 2 API and existing widgets into the next generation FLTK 3 project, but this is more a vision than a concrete plan (i.e. there's no roadmap, no time schedule). > Don't use FLTK2 for new projects? Yes. > Is FLTK 1.3 the path forward? Yes, but it's still beta (although some people are using it already). There is no release date yet, but all development efforts are currently going into the FLTK 1.3 development. > > << Currently there are three subdirs in the ide/ directory: > > VisualC6: the newest, should be up-to-date, but needs testing > should work OOTB, but please report any issues. This will > probably be the only supported VS IDE project in the future. > I don't know if the latest updates are already reflected, > you will maybe need to add some files manually, but this is > the VS project you should use. > > vc2005: That's the one you probably used. It's not up-to-date > (missing files) and the project settings are obviously wrong. > You must switch to debug or release mode if you don't have > Cairo installed. > > visualc: the oldest VS version, but the project files are almost > up-to-date. You *will* have to add some new files manually. > >>> > > The above, as you've written, is needed in the README. You were right when > you guessed that I used the vc2005 files because I'd assumed that to be > newest. Yes, you're right. > << BTW.: FLTK 1.3 is in development, and current subversion and/or > the latest snapshots are not always guaranteed to build without > problems, but we're trying to fix any issues.>> > > What is the best version of FLTK to use for multi-platform production code? FLTK 1.1.10 is the only current stable release that can be recommended for production code, but this uses only 8-bit characters (you need to set a non-UTF-8 locale, or use the correct Windows codepage etc.). If you need UTF-8, then you might probably want to try FLTK 1.3, and there is also new printing support and some interesting widgets. FLTK 1.3 uses the same API as 1.1, so that you can switch from 1.1 to 1.3 with only very small code changes (if any). > << [ To build debug-cairo ] You need to install Cairo>> > > Is there a README for that? README.cairo. But don't expect too much. There's only basic support so that you can integrate Cairo rendering, but without FLTK using it by itself. > << I've never heard [of widgets looking ugly in Win7] before. Builds okay > for me...with Cygwin or MinGW...>> > > It's not a build problem. I can build FLTK 1.3 using VC++. The problem seems > to be that the default system colors in Win7 are not pleasing when rendered > by FLTK, that the widgets look like high contrast 2-color B&W, whether gtk+ > or plastic style. Indeed, I can see that on my Win7 system too. The background is very bright, maybe almost white. > How do I get pretty widgets? How do I reset the colors darker so the widgets > draw nicely? FLTK supports setting the background color by a commandline switch, and some more options, e.g. run "test/tabs -bg aaeba0" to see a bright green background color on Windows. Use -fg to set the foreground (text) color. Note: Color syntax is slightly different on other OS's. > Do I write my own theme? How? What function calls do I need to make? There are functions to change the internal colors ("gray ramp"), and you can set colors for all widgets individually, and you can write your own box drawing functions ("theme"), but I can't tell you what to do off the top of my head. RTFM ;-) > Is there an FLTK call that tells me what platform and OS version I'm on so I > know to tweak it when it's Win7? Not a FLTK call, but someone (Ian?) posted such code for all platforms some time ago. Albrecht _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
