On 30.10.2010, at 21:38, Matthias Melcher wrote: > VisualC 2008 and VisualC 2010 are free in their Express version and have been > out in the field long enough to be the state of the art. I would like to > suggest to drop support of any IDE files older than two major releases of > that IDE.
+1 on dropping the ide/vc2005 files. Before we had the new ide/VisualC2008 and ide/VisualC2010 files, this was needed at least for VC 2010, but if we can keep the new IDE files, this one is obsolete. > I know that there are still a few VC6 junkies out there ... I'm not so sure about ide/VisualC6 though. I think that there may be commercial FLTK users that have restrictions to use their existing development tools for several reasons, but these are probably older tools that can't open the VC 2008 IDE files. Thus, I'd vote for keeping the ide/VisualC6 files, if we can manage them without too much work. This depends on how we can keep them up-to-date. --- Matt, what are your plans regarding maintenance of IDE files? Although I thought that it is generally not a good idea to edit (fluid) source files to add new files/dependencies to the IDE's, this turned out to be a way that more dev's can manage the IDE files (e.g. I don't have these ancient MS IDE's, but I could add a file to the old IDE by generating it with fluid). Currently I have VC 2008 and VC 2010 installed (on my Win 7 box, side by side), but I don't really like the idea to manage the IDE project files with the IDE - but if only one developer can manage them, this can be problematic... So, what would be the best way to manage the IDE files? Do we keep the fluid IDE generation, or do you intend to remove that again? Do we need to point-n-click each change in all IDE project files? How did you do it with the recent 2008/2010 files? Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
