Move new panel to trunk

(Old svn revision: 17863)

.indent.pro

@@ -0,0 +1,7 @@
+-gnu
+-i4
+-bli0
+-cli4
+-hnl
+-bad
+-nut

AUTHORS

@@ -0,0 +1 @@
+Jasper Huijsmans <huysmans@users.sourceforge.net>

COPYING

@@ -0,0 +1,340 @@
+		    GNU GENERAL PUBLIC LICENSE
+		       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+     59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+			    Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+		    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+			    NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+		     END OF TERMS AND CONDITIONS
+
+	    How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program; if not, write to the Free Software
+    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year  name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Library General
+Public License instead of this License.

COPYING_LIBS

@@ -0,0 +1,440 @@
+This license applies to the libraries in this package, but not the
+applications. See header comments in specific source files.
+
+		  GNU LIBRARY GENERAL PUBLIC LICENSE
+		       Version 2, June 1991
+
+ Copyright (C) 1991 Free Software Foundation, Inc.
+    		    59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+[This is the first released version of the library GPL.  It is
+ numbered 2 because it goes with version 2 of the ordinary GPL.]
+
+			    Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software--to make sure the software is free for all its users.
+
+  This license, the Library General Public License, applies to some
+specially designated Free Software Foundation software, and to any
+other libraries whose authors decide to use it.  You can use it for
+your libraries, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if
+you distribute copies of the library, or if you modify it.
+
+  For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you.  You must make sure that they, too, receive or can get the source
+code.  If you link a program with the library, you must provide
+complete object files to the recipients so that they can relink them
+with the library, after making changes to the library and recompiling
+it.  And you must show them these terms so they know their rights.
+
+  Our method of protecting your rights has two steps: (1) copyright
+the library, and (2) offer you this license which gives you legal
+permission to copy, distribute and/or modify the library.
+
+  Also, for each distributor's protection, we want to make certain
+that everyone understands that there is no warranty for this free
+library.  If the library is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original
+version, so that any problems introduced by others will not reflect on
+the original authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that companies distributing free
+software will individually obtain patent licenses, thus in effect
+transforming the program into proprietary software.  To prevent this,
+we have made it clear that any patent must be licensed for everyone's
+free use or not licensed at all.
+
+  Most GNU software, including some libraries, is covered by the ordinary
+GNU General Public License, which was designed for utility programs.  This
+license, the GNU Library General Public License, applies to certain
+designated libraries.  This license is quite different from the ordinary
+one; be sure to read it in full, and don't assume that anything in it is
+the same as in the ordinary license.
+
+  The reason we have a separate public license for some libraries is that
+they blur the distinction we usually make between modifying or adding to a
+program and simply using it.  Linking a program with a library, without
+changing the library, is in some sense simply using the library, and is
+analogous to running a utility program or application program.  However, in
+a textual and legal sense, the linked executable is a combined work, a
+derivative of the original library, and the ordinary General Public License
+treats it as such.
+
+  Because of this blurred distinction, using the ordinary General
+Public License for libraries did not effectively promote software
+sharing, because most developers did not use the libraries.  We
+concluded that weaker conditions might promote sharing better.
+
+  However, unrestricted linking of non-free programs would deprive the
+users of those programs of all benefit from the free status of the
+libraries themselves.  This Library General Public License is intended to
+permit developers of non-free programs to use free libraries, while
+preserving your freedom as a user of such programs to change the free
+libraries that are incorporated in them.  (We have not seen how to achieve
+this as regards changes in header files, but we have achieved it as regards
+changes in the actual functions of the Library.)  The hope is that this
+will lead to faster development of free libraries.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.  Pay close attention to the difference between a
+"work based on the library" and a "work that uses the library".  The
+former contains code derived from the library, while the latter only
+works together with the library.
+
+  Note that it is possible for a library to be covered by the ordinary
+General Public License rather than by this special one.
+
+		  GNU LIBRARY GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License Agreement applies to any software library which
+contains a notice placed by the copyright holder or other authorized
+party saying it may be distributed under the terms of this Library
+General Public License (also called "this License").  Each licensee is
+addressed as "you".
+
+  A "library" means a collection of software functions and/or data
+prepared so as to be conveniently linked with application programs
+(which use some of those functions and data) to form executables.
+
+  The "Library", below, refers to any such software library or work
+which has been distributed under these terms.  A "work based on the
+Library" means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language.  (Hereinafter, translation is
+included without limitation in the term "modification".)
+
+  "Source code" for a work means the preferred form of the work for
+making modifications to it.  For a library, complete source code means
+all the source code for all modules it contains, plus any associated
+interface definition files, plus the scripts used to control compilation
+and installation of the library.
+
+  Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it).  Whether that is true depends on what the Library does
+and what the program that uses the Library does.
+  
+  1. You may copy and distribute verbatim copies of the Library's
+complete source code as you receive it, in any medium, provided that
+you conspicuously and appropriately publish on each copy an
+appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any
+warranty; and distribute a copy of this License along with the
+Library.
+
+  You may charge a fee for the physical act of transferring a copy,
+and you may at your option offer warranty protection in exchange for a
+fee.
+
+  2. You may modify your copy or copies of the Library or any portion
+of it, thus forming a work based on the Library, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) The modified work must itself be a software library.
+
+    b) You must cause the files modified to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    c) You must cause the whole of the work to be licensed at no
+    charge to all third parties under the terms of this License.
+
+    d) If a facility in the modified Library refers to a function or a
+    table of data to be supplied by an application program that uses
+    the facility, other than as an argument passed when the facility
+    is invoked, then you must make a good faith effort to ensure that,
+    in the event an application does not supply such function or
+    table, the facility still operates, and performs whatever part of
+    its purpose remains meaningful.
+
+    (For example, a function in a library to compute square roots has
+    a purpose that is entirely well-defined independent of the
+    application.  Therefore, Subsection 2d requires that any
+    application-supplied function or table used by this function must
+    be optional: if the application does not supply it, the square
+    root function must still compute square roots.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Library,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Library, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote
+it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Library.
+
+In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may opt to apply the terms of the ordinary GNU General Public
+License instead of this License to a given copy of the Library.  To do
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+instead of to this License.  (If a newer version than version 2 of the
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.)  Do not make any other change in
+these notices.
+
+  Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+
+  This option is useful when you wish to copy part of the code of
+the Library into a program that is not a library.
+
+  4. You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form
+under the terms of Sections 1 and 2 above provided that you accompany
+it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a
+medium customarily used for software interchange.
+
+  If distribution of object code is made by offering access to copy
+from a designated place, then offering equivalent access to copy the
+source code from the same place satisfies the requirement to
+distribute the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  5. A program that contains no derivative of any portion of the
+Library, but is designed to work with the Library by being compiled or
+linked with it, is called a "work that uses the Library".  Such a
+work, in isolation, is not a derivative work of the Library, and
+therefore falls outside the scope of this License.
+
+  However, linking a "work that uses the Library" with the Library
+creates an executable that is a derivative of the Library (because it
+contains portions of the Library), rather than a "work that uses the
+library".  The executable is therefore covered by this License.
+Section 6 states terms for distribution of such executables.
+
+  When a "work that uses the Library" uses material from a header file
+that is part of the Library, the object code for the work may be a
+derivative work of the Library even though the source code is not.
+Whether this is true is especially significant if the work can be
+linked without the Library, or if the work is itself a library.  The
+threshold for this to be true is not precisely defined by law.
+
+  If such an object file uses only numerical parameters, data
+structure layouts and accessors, and small macros and small inline
+functions (ten lines or less in length), then the use of the object
+file is unrestricted, regardless of whether it is legally a derivative
+work.  (Executables containing this object code plus portions of the
+Library will still fall under Section 6.)
+
+  Otherwise, if the work is a derivative of the Library, you may
+distribute the object code for the work under the terms of Section 6.
+Any executables containing that work also fall under Section 6,
+whether or not they are linked directly with the Library itself.
+
+  6. As an exception to the Sections above, you may also compile or
+link a "work that uses the Library" with the Library to produce a
+work containing portions of the Library, and distribute that work
+under terms of your choice, provided that the terms permit
+modification of the work for the customer's own use and reverse
+engineering for debugging such modifications.
+
+  You must give prominent notice with each copy of the work that the
+Library is used in it and that the Library and its use are covered by
+this License.  You must supply a copy of this License.  If the work
+during execution displays copyright notices, you must include the
+copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License.  Also, you must do one
+of these things:
+
+    a) Accompany the work with the complete corresponding
+    machine-readable source code for the Library including whatever
+    changes were used in the work (which must be distributed under
+    Sections 1 and 2 above); and, if the work is an executable linked
+    with the Library, with the complete machine-readable "work that
+    uses the Library", as object code and/or source code, so that the
+    user can modify the Library and then relink to produce a modified
+    executable containing the modified Library.  (It is understood
+    that the user who changes the contents of definitions files in the
+    Library will not necessarily be able to recompile the application
+    to use the modified definitions.)
+
+    b) Accompany the work with a written offer, valid for at
+    least three years, to give the same user the materials
+    specified in Subsection 6a, above, for a charge no more
+    than the cost of performing this distribution.
+
+    c) If distribution of the work is made by offering access to copy
+    from a designated place, offer equivalent access to copy the above
+    specified materials from the same place.
+
+    d) Verify that the user has already received a copy of these
+    materials or that you have already sent this user a copy.
+
+  For an executable, the required form of the "work that uses the
+Library" must include any data and utility programs needed for
+reproducing the executable from it.  However, as a special exception,
+the source code distributed need not include anything that is normally
+distributed (in either source or binary form) with the major
+components (compiler, kernel, and so on) of the operating system on
+which the executable runs, unless that component itself accompanies
+the executable.
+
+  It may happen that this requirement contradicts the license
+restrictions of other proprietary libraries that do not normally
+accompany the operating system.  Such a contradiction means you cannot
+use both them and the Library together in an executable that you
+distribute.
+
+  7. You may place library facilities that are a work based on the
+Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on
+the Library and of the other library facilities is otherwise
+permitted, and provided that you do these two things:
+
+    a) Accompany the combined library with a copy of the same work
+    based on the Library, uncombined with any other library
+    facilities.  This must be distributed under the terms of the
+    Sections above.
+
+    b) Give prominent notice with the combined library of the fact
+    that part of it is a work based on the Library, and explaining
+    where to find the accompanying uncombined form of the same work.
+
+  8. You may not copy, modify, sublicense, link with, or distribute
+the Library except as expressly provided under this License.  Any
+attempt otherwise to copy, modify, sublicense, link with, or
+distribute the Library is void, and will automatically terminate your
+rights under this License.  However, parties who have received copies,
+or rights, from you under this License will not have their licenses
+terminated so long as such parties remain in full compliance.
+
+  9. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Library or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Library or works based on it.
+
+  10. Each time you redistribute the Library (or any work based on the
+Library), the recipient automatically receives a license from the
+original licensor to copy, distribute, link with or modify the Library
+subject to these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  11. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Library at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Library by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+If any portion of this section is held invalid or unenforceable under any
+particular circumstance, the balance of the section is intended to apply,
+and the section as a whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  12. If the distribution and/or use of the Library is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Library under this License may add
+an explicit geographical distribution limitation excluding those countries,
+so that distribution is permitted only in or among countries not thus
+excluded.  In such case, this License incorporates the limitation as if
+written in the body of this License.
+
+  13. The Free Software Foundation may publish revised and/or new
+versions of the Library General Public License from time to time.
+Such new versions will be similar in spirit to the present version,
+but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Library
+specifies a version number of this License which applies to it and
+"any later version", you have the option of following the terms and
+conditions either of that version or of any later version published by
+the Free Software Foundation.  If the Library does not specify a
+license version number, you may choose any version ever published by
+the Free Software Foundation.
+
+  14. If you wish to incorporate parts of the Library into other free
+programs whose distribution conditions are incompatible with these,
+write to the author to ask for permission.  For software which is
+copyrighted by the Free Software Foundation, write to the Free
+Software Foundation; we sometimes make exceptions for this.  Our
+decision will be guided by the two goals of preserving the free status
+of all derivatives of our free software and of promoting the sharing
+and reuse of software generally.
+
+			    NO WARRANTY
+
+  15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
+KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
+LIBRARY IS WITH YOU.  SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
+FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
+RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
+FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
+SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGES.
+
+		     END OF TERMS AND CONDITIONS

HACKING

@@ -0,0 +1,49 @@
+This file describes the coding style I prefer for the panel. If you want to
+help out with panel development, please try to conform to these 'rules'.
+-- Jasper
+
+* 2005-1-3
+
+Somewhere in the past year I decided to expand tabs, to make sure there's no
+misunderstanding in how I want things to look.
+
+
+* 2003-05-17
+
+Updated the .indent.pro to use Olivier's new version. He seems he conformed to
+my standards this time ;-)) (<-- this is a joke, please laugh) Anyway, his new
+version has all the things I find important.
+
+
+* 2003-04-02
+
+If you are interested in working on the panel that is of course enormously
+appreciated. I would like to ask you to follow a small number of rules to ease
+the maintainer's job a little.
+
+- Please use the .indent.pro file provided in this directory to format your
+  files. Since we didn't seem to agree on a common coding style for the entire
+  project I took the liberty to adapt Olivier's file (found in xfwm4/src/) a
+  little to better suit my own taste. The most important aspects are:
+  o indentation is 4 spaces (which does not equal 1 tab!)
+  o braces are on a new line
+  o return type for function definitions on separate line
+
+- If you have CVS access it's alright to commit bugfixes or trivial changes to 
+  CVS directly. But please send a patch to the mailing list for any 
+  non-trivial and/or non-obvious changes for discussion. When in doubt, ask 
+  first. Make patches by running `cvs diff -u > <patchfile>'.
+
+- Patches are always welcome please use `diff -Naur <oldfile> <newfile>' to
+  create them or use the cvs method mentioned above. You can send them to the 
+  mailing list for discussion.
+
+If we all stick to these guidelines I'm sure the code will remain as clean and
+readable as it it today (Ahem ... ;).
+
+Look at the README and TODO for a bit more information, but be careful, it may
+not be entirely up to date.
+
+Thanks,
+	Jasper
+	

INSTALL

@@ -0,0 +1,231 @@
+Copyright 1994, 1995, 1996, 1999, 2000, 2001 Free Software Foundation,
+Inc.
+
+   This file is free documentation; the Free Software Foundation gives
+unlimited permission to copy, distribute and modify it.
+
+Basic Installation
+==================
+
+   These are generic installation instructions.
+
+   The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation.  It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions.  Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+
+   It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring.  (Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.)
+
+   If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release.  If you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+   The file `configure.ac' (or `configure.in') is used to create
+`configure' by a program called `autoconf'.  You only need
+`configure.ac' if you want to change it or regenerate `configure' using
+a newer version of `autoconf'.
+
+The simplest way to compile this package is:
+
+  1. `cd' to the directory containing the package's source code and type
+     `./configure' to configure the package for your system.  If you're
+     using `csh' on an old version of System V, you might need to type
+     `sh ./configure' instead to prevent `csh' from trying to execute
+     `configure' itself.
+
+     Running `configure' takes awhile.  While running, it prints some
+     messages telling which features it is checking for.
+
+  2. Type `make' to compile the package.
+
+  3. Optionally, type `make check' to run any self-tests that come with
+     the package.
+
+  4. Type `make install' to install the programs and any data files and
+     documentation.
+
+  5. You can remove the program binaries and object files from the
+     source code directory by typing `make clean'.  To also remove the
+     files that `configure' created (so you can compile the package for
+     a different kind of computer), type `make distclean'.  There is
+     also a `make maintainer-clean' target, but that is intended mainly
+     for the package's developers.  If you use it, you may have to get
+     all sorts of other programs in order to regenerate files that came
+     with the distribution.
+
+Compilers and Options
+=====================
+
+   Some systems require unusual options for compilation or linking that
+the `configure' script does not know about.  Run `./configure --help'
+for details on some of the pertinent environment variables.
+
+   You can give `configure' initial values for variables by setting
+them in the environment.  You can do that on the command line like this:
+
+     ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
+
+   *Note Defining Variables::, for more details.
+
+Compiling For Multiple Architectures
+====================================
+
+   You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory.  To do this, you must use a version of `make' that
+supports the `VPATH' variable, such as GNU `make'.  `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script.  `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.
+
+   If you have to use a `make' that does not support the `VPATH'
+variable, you have to compile the package for one architecture at a
+time in the source code directory.  After you have installed the
+package for one architecture, use `make distclean' before reconfiguring
+for another architecture.
+
+Installation Names
+==================
+
+   By default, `make install' will install the package's files in
+`/usr/local/bin', `/usr/local/man', etc.  You can specify an
+installation prefix other than `/usr/local' by giving `configure' the
+option `--prefix=PATH'.
+
+   You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files.  If you
+give `configure' the option `--exec-prefix=PATH', the package will use
+PATH as the prefix for installing programs and libraries.
+Documentation and other data files will still use the regular prefix.
+
+   In addition, if you use an unusual directory layout you can give
+options like `--bindir=PATH' to specify different values for particular
+kinds of files.  Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.
+
+   If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+
+Optional Features
+=================
+
+   Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System).  The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+
+   For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+
+Specifying the System Type
+==========================
+
+   There may be some features `configure' cannot figure out
+automatically, but needs to determine by the type of host the package
+will run on.  Usually `configure' can figure that out, but if it prints
+a message saying it cannot guess the host type, give it the
+`--build=TYPE' option.  TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name which has the form:
+
+     CPU-COMPANY-SYSTEM
+
+where SYSTEM can have one of these forms:
+
+     OS KERNEL-OS
+
+   See the file `config.sub' for the possible values of each field.  If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the host type.
+
+   If you are _building_ compiler tools for cross-compiling, you should
+use the `--target=TYPE' option to select the type of system they will
+produce code for.
+
+   If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the host
+platform (i.e., that on which the generated programs will eventually be
+run) with `--host=TYPE'.  In this case, you should also specify the
+build platform with `--build=TYPE', because, in this case, it may not
+be possible to guess the build platform (it sometimes involves
+compiling and running simple test programs, and this can't be done if
+the compiler is a cross compiler).
+
+Sharing Defaults
+================
+
+   If you want to set default values for `configure' scripts to share,
+you can create a site shell script called `config.site' that gives
+default values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/config.site' if it exists, then
+`PREFIX/etc/config.site' if it exists.  Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+
+Defining Variables
+==================
+
+   Variables not defined in a site shell script can be set in the
+environment passed to `configure'.  However, some packages may run
+configure again during the build, and the customized values of these
+variables may be lost.  In order to avoid this problem, you should set
+them in the `configure' command line, using `VAR=value'.  For example:
+
+     ./configure CC=/usr/local2/bin/gcc
+
+will cause the specified gcc to be used as the C compiler (unless it is
+overridden in the site shell script).
+
+`configure' Invocation
+======================
+
+   `configure' recognizes the following options to control how it
+operates.
+
+`--help'
+`-h'
+     Print a summary of the options to `configure', and exit.
+
+`--version'
+`-V'
+     Print the version of Autoconf used to generate the `configure'
+     script, and exit.
+
+`--cache-file=FILE'
+     Enable the cache: use and save the results of the tests in FILE,
+     traditionally `config.cache'.  FILE defaults to `/dev/null' to
+     disable caching.
+
+`--config-cache'
+`-C'
+     Alias for `--cache-file=config.cache'.
+
+`--quiet'
+`--silent'
+`-q'
+     Do not print messages saying which checks are being made.  To
+     suppress all normal output, redirect it to `/dev/null' (any error
+     messages will still be shown).
+
+`--srcdir=DIR'
+     Look for the package's source code in directory DIR.  Usually
+     `configure' can determine that directory automatically.
+
+`configure' also accepts some other, not widely useful, options.  Run
+`configure --help' for more details.
+

Makefile.am

@@ -0,0 +1,47 @@
+@SET_MAKE@
+
+EXTRA_DIST = 								\
+	intltool-extract.in						\
+	intltool-merge.in						\
+	intltool-update.in						\
+	AUTHORS								\
+	COPYING								\
+	COPYING_LIBS							\
+	ChangeLog							\
+	HACKING								\
+	INSTALL								\
+	NEWS								\
+	README								\
+	README.Kiosk							\
+	README.Plugins							\
+	.indent.pro
+
+DISTCLEANFILES =							\
+	intltool-extract						\
+	intltool-merge							\
+	intltool-update							\
+	xfce4-panel.spec
+
+# docs should be at the end to make sure the library is build before 
+# scanning it.
+SUBDIRS =								\
+	po								\
+	config								\
+	icons								\
+	libxfce4panel							\
+	panel								\
+	plugins								\
+	docs
+
+distclean-local:
+	rm -rf *.cache *~
+
+rpm: dist
+	rpmbuild -ta $(PACKAGE)-$(VERSION).tar.gz
+	@rm -f $(PACKAGE)-$(VERSION).tar.gz
+
+dist-bz2: dist
+	zcat $(PACKAGE)-$(VERSION).tar.gz | bzip2 --best -c > $(PACKAGE)-$(VERSION).tar.bz2
+
+distcheck-bz2: distcheck
+	zcat $(PACKAGE)-$(VERSION).tar.gz | bzip2 --best -c > $(PACKAGE)-$(VERSION).tar.bz2

NEWS

@@ -0,0 +1,106 @@
+NEWS for xfce4-panel
+====================
+
+4.1.99.3 (4.2-RC3)
+==================
+- Fix type mismatch when writing backup files. Fixes infinite loop on non-x86.
+  Patch by Michele Baldessari <michele@pupazzo.org> (Jasper)
+
+- Fix edge snapping for very big panels (Jasper)
+
+- Properly setting dock type hint (Olivier)
+
+- Translation updates (Jean-Francois)
+
+
+4.1.99.2 (4.2-RC2)
+==================
+- Increase plugin API version. Plugins build against a panel older than RC1
+  need to be rebuild (Jasper)
+
+- Fix two bugs in the graphical pager (Jasper, Olivier)
+
+- Prevent resizing during panel unhide (Jasper)
+
+- Translation updates (Jean-Francois)
+
+
+4.1.99.1 (4.2 RC1)
+==================
+- Updated documentation screenshots (Jasper)
+
+- Fix POP3 mail checking, patch by Piotr Chmura (Jasper)
+
+- Make transparency configurable with a 'hidden' option (Jasper)
+
+- Increase API version, but still support old plugins (Jasper)
+
+- Use new gtk 2.4 file chooser (Jasper)
+
+- Improve focus management (in combination with xfwm4) by setting the dock
+  type hint. Panel will now always be on top; the option is gone. 
+  (Olivier, Jasper)
+
+- Transparency is always on, but toggled off when the mouse is over the panel
+  (Jasper)
+
+
+4.1.91 (4.2 BETA2)
+==================
+- Several translation updates (Jean-Francois)
+
+- Some autohide fixes with open dialogs (Jasper)
+
+- Fix multihead support (Jasper)
+
+- Translucent panel when set on top. Needs xfwm4 with composite support 
+  and XOrg >= 6.8.0 with composite extension enabled. (Olivier)
+
+
+4.1.90 (4.2 BETA1)
+==================
+- Use basedir spec to locate config file. (Jasper)
+
+- Rename xfce4rc to contents.xml. (Jasper)
+
+- Change the fallback (default) icons to the ones from the Rodent theme 
+  by Francois, very pretty. (Jasper)
+
+- Add support for new KIOSK mode. Much better than env variables. (Benedikt)
+
+- Fix autohide and right-click menu interaction. (Jasper)
+
+- Icon theme support : no more panel-specific themes, the panel will now
+  follow the icon theme set in the user interface dialog. (Jasper)
+
+- Set partial struts (Jasper)
+
+- Add multihead support. The user needs to set DISPLAY properly to start a 
+  new panel on another screen. (Jasper)
+
+- Update list of module list when opening dialog: remove uninstalled modules
+  (when not in use) and add newly installed ones. Based on idea of Scott 
+  Barron. (Jasper)
+
+- Use a dialog to add items to the panel, instead of a submenu. (Jasper)
+
+- Reduce handle width to show only one line of dots. (Jasper)
+
+- Split out the code for choosing a command and choosing an icon from
+  item_dialog.c. to make it available for use in other dialogs (plugins). 
+  The mailcheck plugin makes use of it and of course the launcher dialog. 
+  (Jasper)
+
+- Implement module unloading. Add uniqueness setting to plugins. (Jasper)
+
+- Add pop3 email checking: Use 'pop3://username:password@host' as mailbox.
+  (Olivier)
+
+- Properly update arrow direction. Use this info to position the menus. 
+  Much better. (Jasper)
+
+- Add xrandr awareness. (Jasper)
+
+- Add xinerama aware smart positioning. (Jasper)
+
+

README

@@ -0,0 +1,33 @@
+README for xfce version 4.4.x
+=============================
+
+WHAT IS IT ?
+------------
+'xfce4-panel' is the panel of the Xfce Desktop Environment. It is modeled
+slightly after the CDE panel and, of course, previous versions of xfce.
+This version is based on GTK2 and should have all the advantages that come 
+with this new and improved toolkit (see http://www.gtk.org).
+
+The panel provides program lauchersi with optional, non-hierarchical menus 
+(easier to read at a glance), and several panel 'plugins' like a clock and a
+pager. Additional plugins may be installed separately.
+
+
+WHAT'S NEW ?
+------------
+Apart from the toolkit changes the underlying framework of the panel has also
+changed completely. 
+
+All interactions with the window manager take place through the new window
+manager hints as defined on http://www.freedesktop.org. This means that you 
+will need a compliant window manager for xfce to function properly (preferably 
+xfwm4 ;-).
+
+Highlights from the new panel include:
+o vertical and horizontal mode
+o icon themes
+o dynamic modules as well as traditional launcher buttons
+o support for multiple panels
+o plugins can be loadable modules or external programs
+
+

README.Kiosk

@@ -0,0 +1,20 @@
+The Xfce Panel supports the KIOSK mode introduced with libxfce4util 4.1.13. It
+provides the following KIOSK capabilities:
+
+	CustomizePanel		Only users with this capability will be allowed
+				to customize their panel (add panel plugins,
+				configure panel plugins, add launchers, etc.).
+				This is similar to setting the environment va-
+				riable XFCE_DISABLE_USER_CONFIG with the old
+				panel.
+
+
+So a sample xfce4-panel section in your kioskrc might look like this:
+
+--- snip ---
+[xfce4-panel]
+CustomizePanel=%powerusers,foo
+--- snip ---
+
+This allows only users in the group powerusers and the user foo to customize
+their panels.

README.Plugins

@@ -0,0 +1,243 @@
+= Plugin System for Xfce Panel 4.4 =
+
+Starting from version 4.4 the Xfce Panel supports two types of plugins:
+ * Internal plugins. These are loadable modules, using the gmodule interface.
+ * External plugins. These are separate programs that are embedded into the
+   panel using the GtkPlug/GtkSocket mechanism.
+
+In order to handle these plugins the plugin system was entirely rewritten,
+along with the rest of the panel framework. This file describes the way plugin
+writers should interact with this system.
+
+For the impatient, you can have a look at the plugins provided with the panel
+to see how the system is suposed to work.
+
+The API documentation is installed with the panel and also available from 
+http://www.loculus.nl/xfce/documentation/API/
+
+
+== .desktop file ==
+
+New in version 4.4 is the requirement for a so called .desktop file, that is
+'pluginname.desktop', to be installed. It should look like this:
+
+  [Xfce Panel]
+  Name=Plugin
+  Comment=Plugin to solve all your problems
+  Icon=fancy-icon
+  X-XFCE-Exec=/full/path/to/xfce4-fancy-plugin
+
+See the plugins provided with the panel for some tricks for Makefile.am and
+to find out how to get translations in the file using intltool.
+
+For an internal plugin you would use 'X-XFCE-Module' with the full path to the
+loadable module.
+
+If the module should have no more than 1 instance running at the same time,
+you add this line:
+
+  X-XFCE-Unique=true
+
+
+== Library ==
+
+The necessary widgets are provided by libxfce4panel. In your configure.ac you
+should add a line like this:
+
+XDT_CHECK_PACKAGE ([LIBXFCE4PANEL], [libxfce4panel-1.0], [4.4.0])
+
+The above assumes that you are using the xfce4-dev-tools package, which you
+really should, because it makes you life easier. Otherwise, you'd have to
+adjust it to include the relevant PKG_CONFIG macro.
+
+
+== Header File ==
+
+There is only one header file that needs to be included, which will take care
+of including other required headers:
+
+  #include <libxfce4panel/xfce-panel-plugin.h>
+
+
+== Plugin Registration ==
+
+To register a plugin with the plugin system there are two macros available
+that should be used, instead of using the library functions directly; one for
+internal plugins and one for external plugins.
+
+  XFCE_PANEL_PLUGIN_REGISTER_EXTERNAL(construct);
+
+  XFCE_PANEL_PLUGIN_REGISTER_INTERNAL(construct);
+
+The 'construct' argument is the name of a function that may be cast to
+XfcePanelPluginFunc, i.e. it takes a single XfcePanelPlugin pointer as
+argument. In the function all widgets should be created and callbacks
+connected to the appropriate plugin signals (see below).
+
+example usage:
+
+  static void plugin_construct (XfcePanelPlugin *plugin);
+  
+  XFCE_PANEL_PLUGIN_REGISTER_EXTERNAL (plugin_construct);
+
+  /* implement functions */
+  ....
+
+For an internal plugin, only the macro call is different. And of course the
+build files.
+
+
+== Signals ==
+
+There are several signals that plugins may be interested in:
+
+The "orientation-changed" signal
+  void user_function (XfcePanelPlugin *plugin, GtkOrientation orientation,
+  	              gpointer user_data);
+
+The "screen-position-changed" signal
+  void user_function (XfcePanelPlugin *plugin, XfceScreenPosition *position,
+  	              gpointer user_data);
+
+The XfceScreenPosition describes the position of the panel on the screen.
+There are 12 positions, 3 on each side, plus two floating positions.
+
+  typedef enum
+  {
+      XFCE_SCREEN_POSITION_NONE,
+    
+      /* top */
+      XFCE_SCREEN_POSITION_NW_H,          /* North West Horizontal */
+      XFCE_SCREEN_POSITION_N,             /* North                 */
+      XFCE_SCREEN_POSITION_NE_H,          /* North East Horizontal */
+
+      /* left */
+      XFCE_SCREEN_POSITION_NW_V,          /* North West Vertical   */
+      XFCE_SCREEN_POSITION_W,             /* West                  */
+      XFCE_SCREEN_POSITION_SW_V,          /* South West Vertical   */
+    
+      /* right */
+      XFCE_SCREEN_POSITION_NE_V,          /* North East Vertical   */
+      XFCE_SCREEN_POSITION_E,             /* East                  */
+      XFCE_SCREEN_POSITION_SE_V,          /* South East Vertical   */
+
+      /* bottom */
+      XFCE_SCREEN_POSITION_SW_H,          /* South West Horizontal */
+      XFCE_SCREEN_POSITION_S,             /* South                 */
+      XFCE_SCREEN_POSITION_SE_H,          /* South East Horizontal */
+
+      /* floating */
+      XFCE_SCREEN_POSITION_FLOATING_H,    /* Floating Horizontal */
+      XFCE_SCREEN_POSITION_FLOATING_V,    /* Floating Vertical */
+  }
+  XfceScreenPosition;
+
+Several macros are defined to make it easier to work with screen positions:
+
+  xfce_screen_position_is_horizontal(position);
+
+  xfce_screen_position_get_orientation(position);
+
+  xfce_screen_position_is_floating(position);
+
+  xfce_screen_position_is_top(position);
+
+  xfce_screen_position_is_left(position);
+
+  xfce_screen_position_is_right(position);
+
+  xfce_screen_position_is_bottom(position);
+
+The "size-changed" signal (return TRUE when you handle the size change):
+  gboolean user_function (XfcePanelPlugin *plugin, int size,
+  	                  gpointer user_data);
+
+The "free-data" signal, free all allocated resources:
+  void user_function (XfcePanelPlugin *plugin,
+  	              gpointer user_data);
+
+The "save" signal, save configuration, may be called more than once:
+  void user_function (XfcePanelPlugin *plugin,
+  	              gpointer user_data);
+
+The "about" signal, emitted when the 'About' menu item is clicked:
+  void user_function (XfcePanelPlugin *plugin,
+  	              gpointer user_data);
+
+To show the menu item the plugin writer should also call:
+  void xfce_panel_plugin_menu_show_about (XfcePanelPlugin *plugin);
+
+The "configure-plugin" signal, emitted when the 'Configure' menu item is 
+clicked:
+  void user_function (XfcePanelPlugin *plugin,
+  	              gpointer user_data);
+
+To show the menu item the plugin writer should also call:
+  void xfce_panel_plugin_menu_show_configure (XfcePanelPlugin *plugin);
+
+
+== Properties ==
+
+Several functions are available to get more information about the plugin (and
+the panel it is part of). Only one property can also be changed, the 'expand'
+behavior. The plugin API also provides convenience functions to store and
+retrieve a pointer to user data.
+
+  /* identification */
+  G_CONST_RETURN char *
+    xfce_panel_plugin_get_name (XfcePanelPlugin *plugin);
+
+  G_CONST_RETURN char *
+    xfce_panel_plugin_get_id (XfcePanelPlugin *plugin);
+
+  G_CONST_RETURN char *
+    xfce_panel_plugin_get_display_name (XfcePanelPlugin *plugin);
+
+  /* getting properties */
+  int xfce_panel_plugin_get_size (XfcePanelPlugin *plugin);
+
+  XfceScreenPosition 
+    xfce_panel_plugin_get_screen_position (XfcePanelPlugin *plugin);
+
+  gboolean xfce_panel_plugin_get_expand (XfcePanelPlugin *plugin);
+
+  GtkOrientation xfce_panel_plugin_get_orientation (XfcePanelPlugin *plugin);
+
+  /* settings properties */
+  void xfce_panel_plugin_set_expand (XfcePanelPlugin *plugin, 
+                                     gboolean expand);
+
+
+== Menu ==
+
+The plugin has a right-click mouse menu connected to it that allows the user
+to show the about or settings dialog, to remove the plugin, or to show the
+panel settings dialog. Plugin writers have to make sure all widgets in the
+plugin that receive mouse events are connected to the menu by using the
+xfce_panel_plugin_add_action_widget() function. A plugin can also add 
+additional, custom menu items.
+
+  void xfce_panel_plugin_add_action_widget (XfcePanelPlugin *plugin, 
+                                            GtkWidget *widget);
+
+  void xfce_panel_plugin_menu_insert_item (XfcePanelPlugin *plugin,
+                                           GtkMenuItem *item);
+
+
+== Configuration ==
+
+Plugins can save and retrieve their configuration, using simple ini-style
+configuration files, which are handled by the XfceRc interface in
+libxfce4util. During contruction (one of the vtable functions) a plugin can
+open the file read-only to improve efficiency.
+
+  XfceRc *xfce_panel_plugin_get_rc_file (XfcePanelPlugin *plugin, 
+                                         gboolean read_only);
+
+
+== Examples ==
+
+Look at the plugins included with the panel for examples on how to use the
+plugin interface.
+
+

autogen.sh

@@ -0,0 +1,23 @@
+#!/bin/sh
+#
+# $Id: autogen.sh 4312 2005-01-27 10:10:04Z jasper $
+#
+# Copyright (c) 2002-2005
+#         The Xfce development team. All rights reserved.
+#
+# Written for Xfce by Benedikt Meurer <benny@xfce.org>.
+#
+
+(type xdt-autogen) >/dev/null 2>&1 || {
+  cat >&2 <<EOF
+autogen.sh: You don't seem to have the Xfce development tools installed on
+            your system, which are required to build this software.
+            Please install the xfce4-dev-tools package first, it is available
+            from http://www.xfce.org/.
+EOF
+  exit 1
+}
+
+exec xdt-autogen $@
+
+# vi:set ts=2 sw=2 et ai:

config/Makefile.am

@@ -0,0 +1,13 @@
+confdir = $(sysconfdir)/xdg/xfce4/panel
+conf_in_files = 					\
+	panels.xml.in	
+conf_DATA = $(conf_in_files:.xml.in=.xml)
+	
+@INTLTOOL_XML_RULE@
+
+EXTRA_DIST = 					\
+	$(conf_in_files)
+
+DISTCLEANFILES =				\
+	$(conf_DATA)
+

config/panels.xml.in

@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE config SYSTEM "config.dtd">
+<panels>
+	<panel>
+		<properties>
+			<property name="size" value="34"/>
+			<property name="monitor" value="0"/>
+			<property name="screen-position" value="1"/>
+			<property name="xoffset" value="0"/>
+			<property name="yoffset" value="0"/>
+			<property name="autohide" value="0"/>
+			<property name="fullwidth" value="1"/>
+			<property name="transparency" value="20"/>
+		</properties>
+		<items>
+			<item name="tasklist" id="1"/>
+			<item name="pager" id="2"/>
+			<item name="systray" id="3"/>
+			<item name="clock" id="4"/>
+		</items>
+	</panel>
+	<panel>
+		<properties>
+			<property name="size" value="34"/>
+			<property name="monitor" value="0"/>
+			<property name="screen-position" value="11"/>
+			<property name="xoffset" value="0"/>
+			<property name="yoffset" value="0"/>
+			<property name="autohide" value="0"/>
+			<property name="fullwidth" value="0"/>
+			<property name="transparency" value="20"/>
+		</properties>
+		<items>
+			<item name="launcher" id="5"/>
+			<item name="iconbox" id="6"/>
+			<item name="separator" id="7"/>
+			<item name="actions" id="8"/>
+		</items>
+	</panel>
+</panels>

configure.ac

@@ -0,0 +1,100 @@
+dnl configure.ac
+dnl
+dnl xfce4 - panel for the Xfce Desktop environment
+dnl
+dnl 2005 Jasper Huijsmans <jasper@xfce.org>
+dnl
+
+dnl version info
+m4_define([xfce4_panel_version],[4.3.21])
+m4_define([libxfce4panel_verinfo], [1:1:0])
+
+dnl init autoconf
+AC_COPYRIGHT([Copyright (c) 2002-2005
+        The Xfce development team. All rights reserved.
+
+Written for Xfce by Jasper Huijsmans <jasper@xfce.org>.])
+AC_INIT([xfce4-panel], [xfce4_panel_version()], [xfce4-dev@xfce.org])
+
+dnl init automake
+XFCE4_PANEL_VERSION=xfce4_panel_version()
+AM_INIT_AUTOMAKE([xfce4-panel], [$XFCE4_PANEL_VERSION])
+AM_CONFIG_HEADER([config.h])
+AM_MAINTAINER_MODE
+
+dnl Check for UNIX variants
+AC_AIX
+AC_ISC_POSIX
+AC_MINIX
+AM_CONDITIONAL([HAVE_CYGWIN], [test "`uname | grep \"CYGWIN\"`" != ""])
+
+dnl disable static libs
+AC_DISABLE_STATIC
+
+dnl Check for basic programs
+AC_PROG_CC()
+AC_PROG_INSTALL()
+AC_PROG_LN_S()
+AC_PROG_LIBTOOL()
+AC_PROG_INTLTOOL()
+
+LIBXFCE4PANEL_VERINFO=libxfce4panel_verinfo()
+AC_SUBST([LIBXFCE4PANEL_VERINFO])
+
+dnl Check for standard header files
+AC_HEADER_STDC
+AC_CHECK_HEADERS([signal.h stddef.h sys/wait.h time.h])
+AC_CHECK_FUNCS([sigaction])
+
+dnl Check for i18n support
+XDT_I18N([nl])
+
+dnl Check for X11 installed
+XDT_CHECK_LIBX11_REQUIRE
+XDT_CHECK_LIBSM
+
+dnl Check for required packages
+dnl XDT_CHECK_PACKAGE([LIBXFCE4MCS_CLIENT], [libxfce4mcs-client-1.0], [4.2.0])
+XDT_CHECK_PACKAGE([LIBXFCE4UTIL], [libxfce4util-1.0], [4.3.0])
+XDT_CHECK_PACKAGE([LIBXFCEGUI4], [libxfcegui4-1.0], [4.3.5])
+XDT_CHECK_PACKAGE([GTHREAD], [gthread-2.0], [2.4.0])
+
+dnl Check for optional packages
+XDT_CHECK_OPTIONAL_PACKAGE([LIBSTARTUP_NOTIFICATION],
+			   [libstartup-notification-1.0], [0.5],
+			   [startup-notification], 
+			   [startup notification library], [yes])
+
+dnl gtk-doc
+GTK_DOC_CHECK([1.0])
+
+dnl Configure the mcs plugin
+dnl XDT_XFCE_MCS_PLUGIN([XFCE_MCS_MANAGER], [4.2.0])
+
+dnl Check for debugging support
+XDT_FEATURE_DEBUG()
+
+AC_OUTPUT([
+xfce4-panel.spec
+Makefile
+po/Makefile.in
+config/Makefile
+icons/Makefile
+libxfce4panel/Makefile
+libxfce4panel/libxfce4panel-1.0.pc
+panel/Makefile
+plugins/Makefile
+plugins/launcher/Makefile
+plugins/separator/Makefile
+plugins/actions/Makefile
+plugins/tasklist/Makefile
+plugins/pager/Makefile
+plugins/systray/Makefile
+plugins/iconbox/Makefile
+plugins/clock/Makefile
+plugins/testplugin/Makefile
+docs/Makefile
+docs/API/Makefile
+docs/API/version.xml
+])
+

docs/API/Makefile.am

@@ -0,0 +1,83 @@
+## Process this file with automake to produce Makefile.in
+
+# We require automake 1.6 at least.
+AUTOMAKE_OPTIONS = 1.9
+
+# This is a blank Makefile.am for using gtk-doc.
+# Copy this to your project's API docs directory and modify the variables to
+# suit your project. See the GTK+ Makefiles in gtk+/docs/reference for examples
+# of using the various options.
+
+# The name of the module, e.g. 'glib'.
+DOC_MODULE=libxfce4panel
+
+# The top-level SGML file. You can change this if you want to.
+DOC_MAIN_SGML_FILE=$(DOC_MODULE)-docs.sgml
+
+# The directory containing the source code. Relative to $(srcdir).
+# gtk-doc will search all .c & .h files beneath here for inline comments
+# documenting the functions and macros.
+# e.g. DOC_SOURCE_DIR=../../../gtk
+DOC_SOURCE_DIR=../../libxfce4panel
+
+# Extra options to pass to gtkdoc-scangobj. Not normally needed.
+SCANGOBJ_OPTIONS=
+
+# Extra options to supply to gtkdoc-scan.
+# e.g. SCAN_OPTIONS=--deprecated-guards="GTK_DISABLE_DEPRECATED" 
+SCAN_OPTIONS=
+
+# Extra options to supply to gtkdoc-mkdb.
+# e.g. MKDB_OPTIONS=--sgml-mode --output-format=xml
+MKDB_OPTIONS=--sgml-mode --output-format=xml
+
+# Extra options to supply to gtkdoc-mktmpl
+# e.g. MKTMPL_OPTIONS=--only-section-tmpl
+MKTMPL_OPTIONS=
+
+# Extra options to supply to gtkdoc-fixref. Not normally needed.
+# e.g. FIXXREF_OPTIONS=--extra-dir=../gdk-pixbuf/html --extra-dir=../gdk/html
+FIXXREF_OPTIONS=
+
+# Used for dependencies. The docs will be rebuilt if any of these change.
+# e.g. HFILE_GLOB=$(top_srcdir)/gtk/*.h
+# e.g. CFILE_GLOB=$(top_srcdir)/gtk/*.c
+HFILE_GLOB=$(top_srcdir)/libxfce4panel/*.h
+CFILE_GLOB=$(top_srcdir)/libxfce4panel/*.c
+
+# Header files to ignore when scanning.
+# e.g. IGNORE_HFILES=gtkdebug.h gtkintl.h
+IGNORE_HFILES=					\
+	xfce-marshal.h				\
+	xfce-panel-external-item.h		\
+	xfce-panel-item-iface.h			\
+	xfce-panel-plugin-iface-private.h	\
+	xfce-panel-plugin-messages.h
+
+# Images to copy into HTML directory.
+# e.g. HTML_IMAGES=$(top_srcdir)/gtk/stock-icons/stock_about_24.png
+HTML_IMAGES=
+
+# Extra SGML files that are included by $(DOC_MAIN_SGML_FILE).
+# e.g. content_files=running.sgml building.sgml changes-2.0.sgml
+content_files=version.xml
+
+# SGML files where gtk-doc abbrevations (#GtkWidget) are expanded
+# These files must be listed here *and* in content_files
+# e.g. expand_content_files=running.sgml
+expand_content_files=
+
+# CFLAGS and LDFLAGS for compiling gtkdoc-scangobj with your library.
+# Only needed if you are using gtkdoc-scangobj to dynamically query widget
+# signals and properties.
+# e.g. INCLUDES=-I$(top_srcdir) -I$(top_builddir) $(GTK_DEBUG_FLAGS)
+# e.g. GTKDOC_LIBS=$(top_builddir)/gtk/$(gtktargetlib)
+INCLUDES=-I$(top_srcdir) -I$(top_builddir)/libxfce4panel $(LIBXFCEGUI4_CFLAGS)
+GTKDOC_LIBS=$(top_builddir)/libxfce4panel/libxfce4panel.la $(LIBXFCEGUI4_LIBS)
+
+# This includes the standard gtk-doc make rules, copied by gtkdocize.
+include $(top_srcdir)/gtk-doc.make
+
+# Other files to distribute
+# e.g. EXTRA_DIST += version.xml.in
+EXTRA_DIST += 

docs/API/html/XfceArrowButton.html

@@ -0,0 +1,309 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>XfceArrowButton</title>
+<meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
+<link rel="start" href="index.html" title="libxfce4panel Reference Manual">
+<link rel="up" href="ch01.html" title="API Reference">
+<link rel="prev" href="ch01.html" title="API Reference">
+<link rel="next" href="XfcePanelWindow.html" title="XfcePanelWindow">
+<meta name="generator" content="GTK-Doc V1.4 (XML mode)">
+<link rel="stylesheet" href="style.css" type="text/css">
+<link rel="chapter" href="ch01.html" title="API Reference"