Remove $Id$ tags, update URL's, and more

- remove obsolete svn '$Id$' tags from all source files
- update .fl files and generated files accordingly
- replace 'http://www.fltk.org' URL's with 'https://...'
- replace bug report URL 'str.php' with 'bugs.php'
- remove trailing whitespace
- fix other whitespace errors flagged by Git
- add and/or fix missing or wrong standard headers
- convert tabs to spaces in all source files

The only relevant code changes are in the fluid/ folder where
some .fl files and other source files were used to generate
the '$Id' headers and footers.

1 files changed, 9 insertions, 15 deletions

diff --git a/FL/Fl_Plugin.H b/FL/Fl_Plugin.H
index 6cbd840ad..aca8d4b8b 100644
--- a/FL/Fl_Plugin.H
+++ b/FL/Fl_Plugin.H
@@ -1,6 +1,4 @@
 //
-// "$Id$"
-//
 // A Plugin system for FLTK, implemented in Fl_Preferences.cxx.
 //
 // Copyright 2002-2010 by Matthias Melcher.
@@ -9,11 +7,11 @@
 // the file "COPYING" which should have been included with this file.  If this
 // file is missing or damaged, see the license at:
 //
-//     http://www.fltk.org/COPYING.php
+//     https://www.fltk.org/COPYING.php
 //
-// Please report all bugs and problems on the following page:
+// Please see the following page on how to report bugs and issues:
 //
-//     http://www.fltk.org/str.php
+//     https://www.fltk.org/bugs.php
 //
 
 /* \file
@@ -27,7 +25,7 @@
 
 /**
  \brief Fl_Plugin allows link-time and run-time integration of binary modules.
- 
+
  Fl_Plugin and Fl_Plugin_Manager provide a small and simple solution for
  linking C++ classes at run-time, or optionally linking modules at compile
  time without the need to change the main application.
@@ -35,7 +33,7 @@
  Fl_Plugin_Manager uses static initialisation to create the plugin interface
  early during startup. Plugins are stored in a temporary database, organized
  in classes.
- 
+
  Plugins should derive a new class from Fl_Plugin as a base:
  \code
  class My_Plugin : public Fl_Plugin {
@@ -45,9 +43,9 @@
  };
  My_Plugin blur_plugin();
  \endcode
- 
+
  Plugins can be put into modules and either linked before distribution, or loaded
- from dynamically linkable files. An Fl_Plugin_Manager is used to list and 
+ from dynamically linkable files. An Fl_Plugin_Manager is used to list and
  access all currently loaded plugins.
  \code
  Fl_Plugin_Manager mgr("effects");
@@ -74,14 +72,14 @@ class FL_EXPORT Fl_Plugin_Manager : public Fl_Preferences {
 public:
   Fl_Plugin_Manager(const char *klass);
   ~Fl_Plugin_Manager();
-  
+
   /** \brief Return the number of plugins in the klass.
    */
   int plugins() { return groups(); }
   Fl_Plugin *plugin(int index);
   Fl_Plugin *plugin(const char *name);
   Fl_Preferences::ID addPlugin(const char *name, Fl_Plugin *plugin);
-  
+
   static void removePlugin(Fl_Preferences::ID id);
   static int load(const char *filename);
   static int loadAll(const char *filepath, const char *pattern=0);
@@ -89,7 +87,3 @@ public:
 
 
 #endif // !Fl_Preferences_H
-
-//
-// End of "$Id$".
-//