fltk/ide
Greg Ercolano a8d019d60a Added Fl_Table, Fl_Native_File_Chooser, Fl_Tree and related test programs
to ide/visualc/.

These files were /hand edited/ to make the changes.

    TO BE DONE: Someone (other than me) needs to add these to the ide/vs2005
		dir as well. I don't think these can be hand edited; 
		too much human unreadable GUID/hex code stuff..



git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3@7018 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
2010-01-18 18:59:51 +00:00
..
unsupported STR#2030 increment 3: moved not up-to-date ms vc 2003 project filesto ide/unsupported subdir, added a README.MS file explaining what to do if we find a developer to update them. 2008-12-06 11:32:32 +00:00
vc2005 vc2005 update: 2009-03-27 00:02:20 +00:00
visualc Added Fl_Table, Fl_Native_File_Chooser, Fl_Tree and related test programs 2010-01-18 18:59:51 +00:00
Xcode3.1 Applied Manolo's patches from STR #2298: 2010-01-17 17:21:44 +00:00
README.IDE - Added a README.IDE file under the ide subdirectory describing what project dir to start from depending on the ide product. 2008-12-02 23:52:57 +00:00

-------------------------------------------
   HOW TO USE THE FLTK IDE ENVIRONMENTS
-------------------------------------------

As for today, FLTK 1.3 officially supports 
the following integrated environments (1) :

-------------------------------------------
distrib subdir 	   |   supported products
-------------------------------------------
ide/vc2005	   |   Microsoft Visual C++ 2005, 2008 (2)
ide/visualc	   |   Microsoft Visual C++ 6, 2003 (3)
ide/Xcode3.1 	   |   Apple XCode 3.1

Notes :
-------
(1) For *nix platforms based on the autoconf/configure/make toolchain,
    simply run autoconf, then the configure script on the root dir.
    read the ./README file for more info.
(2) When first using the project file (ide/vc2005/fltk.sln) with vc2008, 
    you will be ask to convert the project for vs2008 use.
(3) When first using the project file (ide/visualc/fltk.dsw) with vc2003, 
    you will be ask to convert the project for vs2003 use.