From: Michael Orlitzky Date: Sun, 18 Jan 2009 07:37:24 +0000 (-0500) Subject: Initial commit. X-Git-Tag: v0.0.1 X-Git-Url: http://gitweb.michael.orlitzky.com/?p=xfce4-hdaps.git;a=commitdiff_plain;h=refs%2Ftags%2Fv0.0.1 Initial commit. --- 63eef27ea56fc385cf1eb7af33211e697b384c3e diff --git a/AUTHORS b/AUTHORS new file mode 100644 index 0000000..8f721a0 --- /dev/null +++ b/AUTHORS @@ -0,0 +1 @@ +Michael Orlitzky diff --git a/COPYING b/COPYING new file mode 100644 index 0000000..94a9ed0 --- /dev/null +++ b/COPYING @@ -0,0 +1,674 @@ + GNU GENERAL PUBLIC LICENSE + Version 3, 29 June 2007 + + Copyright (C) 2007 Free Software Foundation, Inc. + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The GNU General Public License is a free, copyleft license for +software and other kinds of works. + + The licenses for most software and other practical works are designed +to take away your freedom to share and change the works. By contrast, +the GNU General Public License is intended to guarantee your freedom to +share and change all versions of a program--to make sure it remains free +software for all its users. We, the Free Software Foundation, use the +GNU General Public License for most of our software; it applies also to +any other work released this way by its authors. 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 +them 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 prevent others from denying you +these rights or asking you to surrender the rights. Therefore, you have +certain responsibilities if you distribute copies of the software, or if +you modify it: responsibilities to respect the freedom of others. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must pass on to the recipients the same +freedoms that you received. 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. + + Developers that use the GNU GPL protect your rights with two steps: +(1) assert copyright on the software, and (2) offer you this License +giving you legal permission to copy, distribute and/or modify it. + + For the developers' and authors' protection, the GPL clearly explains +that there is no warranty for this free software. For both users' and +authors' sake, the GPL requires that modified versions be marked as +changed, so that their problems will not be attributed erroneously to +authors of previous versions. + + Some devices are designed to deny users access to install or run +modified versions of the software inside them, although the manufacturer +can do so. This is fundamentally incompatible with the aim of +protecting users' freedom to change the software. The systematic +pattern of such abuse occurs in the area of products for individuals to +use, which is precisely where it is most unacceptable. Therefore, we +have designed this version of the GPL to prohibit the practice for those +products. If such problems arise substantially in other domains, we +stand ready to extend this provision to those domains in future versions +of the GPL, as needed to protect the freedom of users. + + Finally, every program is threatened constantly by software patents. +States should not allow patents to restrict development and use of +software on general-purpose computers, but in those that do, we wish to +avoid the special danger that patents applied to a free program could +make it effectively proprietary. To prevent this, the GPL assures that +patents cannot be used to render the program non-free. + + The precise terms and conditions for copying, distribution and +modification follow. + + TERMS AND CONDITIONS + + 0. Definitions. + + "This License" refers to version 3 of the GNU General Public License. + + "Copyright" also means copyright-like laws that apply to other kinds of +works, such as semiconductor masks. + + "The Program" refers to any copyrightable work licensed under this +License. Each licensee is addressed as "you". "Licensees" and +"recipients" may be individuals or organizations. + + To "modify" a work means to copy from or adapt all or part of the work +in a fashion requiring copyright permission, other than the making of an +exact copy. The resulting work is called a "modified version" of the +earlier work or a work "based on" the earlier work. + + A "covered work" means either the unmodified Program or a work based +on the Program. + + To "propagate" a work means to do anything with it that, without +permission, would make you directly or secondarily liable for +infringement under applicable copyright law, except executing it on a +computer or modifying a private copy. Propagation includes copying, +distribution (with or without modification), making available to the +public, and in some countries other activities as well. + + To "convey" a work means any kind of propagation that enables other +parties to make or receive copies. Mere interaction with a user through +a computer network, with no transfer of a copy, is not conveying. + + An interactive user interface displays "Appropriate Legal Notices" +to the extent that it includes a convenient and prominently visible +feature that (1) displays an appropriate copyright notice, and (2) +tells the user that there is no warranty for the work (except to the +extent that warranties are provided), that licensees may convey the +work under this License, and how to view a copy of this License. If +the interface presents a list of user commands or options, such as a +menu, a prominent item in the list meets this criterion. + + 1. Source Code. + + The "source code" for a work means the preferred form of the work +for making modifications to it. "Object code" means any non-source +form of a work. + + A "Standard Interface" means an interface that either is an official +standard defined by a recognized standards body, or, in the case of +interfaces specified for a particular programming language, one that +is widely used among developers working in that language. + + The "System Libraries" of an executable work include anything, other +than the work as a whole, that (a) is included in the normal form of +packaging a Major Component, but which is not part of that Major +Component, and (b) serves only to enable use of the work with that +Major Component, or to implement a Standard Interface for which an +implementation is available to the public in source code form. A +"Major Component", in this context, means a major essential component +(kernel, window system, and so on) of the specific operating system +(if any) on which the executable work runs, or a compiler used to +produce the work, or an object code interpreter used to run it. + + The "Corresponding Source" for a work in object code form means all +the source code needed to generate, install, and (for an executable +work) run the object code and to modify the work, including scripts to +control those activities. However, it does not include the work's +System Libraries, or general-purpose tools or generally available free +programs which are used unmodified in performing those activities but +which are not part of the work. For example, Corresponding Source +includes interface definition files associated with source files for +the work, and the source code for shared libraries and dynamically +linked subprograms that the work is specifically designed to require, +such as by intimate data communication or control flow between those +subprograms and other parts of the work. + + The Corresponding Source need not include anything that users +can regenerate automatically from other parts of the Corresponding +Source. + + The Corresponding Source for a work in source code form is that +same work. + + 2. Basic Permissions. + + All rights granted under this License are granted for the term of +copyright on the Program, and are irrevocable provided the stated +conditions are met. This License explicitly affirms your unlimited +permission to run the unmodified Program. The output from running a +covered work is covered by this License only if the output, given its +content, constitutes a covered work. This License acknowledges your +rights of fair use or other equivalent, as provided by copyright law. + + You may make, run and propagate covered works that you do not +convey, without conditions so long as your license otherwise remains +in force. You may convey covered works to others for the sole purpose +of having them make modifications exclusively for you, or provide you +with facilities for running those works, provided that you comply with +the terms of this License in conveying all material for which you do +not control copyright. Those thus making or running the covered works +for you must do so exclusively on your behalf, under your direction +and control, on terms that prohibit them from making any copies of +your copyrighted material outside their relationship with you. + + Conveying under any other circumstances is permitted solely under +the conditions stated below. Sublicensing is not allowed; section 10 +makes it unnecessary. + + 3. Protecting Users' Legal Rights From Anti-Circumvention Law. + + No covered work shall be deemed part of an effective technological +measure under any applicable law fulfilling obligations under article +11 of the WIPO copyright treaty adopted on 20 December 1996, or +similar laws prohibiting or restricting circumvention of such +measures. + + When you convey a covered work, you waive any legal power to forbid +circumvention of technological measures to the extent such circumvention +is effected by exercising rights under this License with respect to +the covered work, and you disclaim any intention to limit operation or +modification of the work as a means of enforcing, against the work's +users, your or third parties' legal rights to forbid circumvention of +technological measures. + + 4. Conveying Verbatim Copies. + + You may convey 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; +keep intact all notices stating that this License and any +non-permissive terms added in accord with section 7 apply to the code; +keep intact all notices of the absence of any warranty; and give all +recipients a copy of this License along with the Program. + + You may charge any price or no price for each copy that you convey, +and you may offer support or warranty protection for a fee. + + 5. Conveying Modified Source Versions. + + You may convey a work based on the Program, or the modifications to +produce it from the Program, in the form of source code under the +terms of section 4, provided that you also meet all of these conditions: + + a) The work must carry prominent notices stating that you modified + it, and giving a relevant date. + + b) The work must carry prominent notices stating that it is + released under this License and any conditions added under section + 7. This requirement modifies the requirement in section 4 to + "keep intact all notices". + + c) You must license the entire work, as a whole, under this + License to anyone who comes into possession of a copy. This + License will therefore apply, along with any applicable section 7 + additional terms, to the whole of the work, and all its parts, + regardless of how they are packaged. This License gives no + permission to license the work in any other way, but it does not + invalidate such permission if you have separately received it. + + d) If the work has interactive user interfaces, each must display + Appropriate Legal Notices; however, if the Program has interactive + interfaces that do not display Appropriate Legal Notices, your + work need not make them do so. + + A compilation of a covered work with other separate and independent +works, which are not by their nature extensions of the covered work, +and which are not combined with it such as to form a larger program, +in or on a volume of a storage or distribution medium, is called an +"aggregate" if the compilation and its resulting copyright are not +used to limit the access or legal rights of the compilation's users +beyond what the individual works permit. Inclusion of a covered work +in an aggregate does not cause this License to apply to the other +parts of the aggregate. + + 6. Conveying Non-Source Forms. + + You may convey a covered work in object code form under the terms +of sections 4 and 5, provided that you also convey the +machine-readable Corresponding Source under the terms of this License, +in one of these ways: + + a) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by the + Corresponding Source fixed on a durable physical medium + customarily used for software interchange. + + b) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by a + written offer, valid for at least three years and valid for as + long as you offer spare parts or customer support for that product + model, to give anyone who possesses the object code either (1) a + copy of the Corresponding Source for all the software in the + product that is covered by this License, on a durable physical + medium customarily used for software interchange, for a price no + more than your reasonable cost of physically performing this + conveying of source, or (2) access to copy the + Corresponding Source from a network server at no charge. + + c) Convey individual copies of the object code with a copy of the + written offer to provide the Corresponding Source. This + alternative is allowed only occasionally and noncommercially, and + only if you received the object code with such an offer, in accord + with subsection 6b. + + d) Convey the object code by offering access from a designated + place (gratis or for a charge), and offer equivalent access to the + Corresponding Source in the same way through the same place at no + further charge. You need not require recipients to copy the + Corresponding Source along with the object code. If the place to + copy the object code is a network server, the Corresponding Source + may be on a different server (operated by you or a third party) + that supports equivalent copying facilities, provided you maintain + clear directions next to the object code saying where to find the + Corresponding Source. Regardless of what server hosts the + Corresponding Source, you remain obligated to ensure that it is + available for as long as needed to satisfy these requirements. + + e) Convey the object code using peer-to-peer transmission, provided + you inform other peers where the object code and Corresponding + Source of the work are being offered to the general public at no + charge under subsection 6d. + + A separable portion of the object code, whose source code is excluded +from the Corresponding Source as a System Library, need not be +included in conveying the object code work. + + A "User Product" is either (1) a "consumer product", which means any +tangible personal property which is normally used for personal, family, +or household purposes, or (2) anything designed or sold for incorporation +into a dwelling. In determining whether a product is a consumer product, +doubtful cases shall be resolved in favor of coverage. For a particular +product received by a particular user, "normally used" refers to a +typical or common use of that class of product, regardless of the status +of the particular user or of the way in which the particular user +actually uses, or expects or is expected to use, the product. A product +is a consumer product regardless of whether the product has substantial +commercial, industrial or non-consumer uses, unless such uses represent +the only significant mode of use of the product. + + "Installation Information" for a User Product means any methods, +procedures, authorization keys, or other information required to install +and execute modified versions of a covered work in that User Product from +a modified version of its Corresponding Source. The information must +suffice to ensure that the continued functioning of the modified object +code is in no case prevented or interfered with solely because +modification has been made. + + If you convey an object code work under this section in, or with, or +specifically for use in, a User Product, and the conveying occurs as +part of a transaction in which the right of possession and use of the +User Product is transferred to the recipient in perpetuity or for a +fixed term (regardless of how the transaction is characterized), the +Corresponding Source conveyed under this section must be accompanied +by the Installation Information. But this requirement does not apply +if neither you nor any third party retains the ability to install +modified object code on the User Product (for example, the work has +been installed in ROM). + + The requirement to provide Installation Information does not include a +requirement to continue to provide support service, warranty, or updates +for a work that has been modified or installed by the recipient, or for +the User Product in which it has been modified or installed. Access to a +network may be denied when the modification itself materially and +adversely affects the operation of the network or violates the rules and +protocols for communication across the network. + + Corresponding Source conveyed, and Installation Information provided, +in accord with this section must be in a format that is publicly +documented (and with an implementation available to the public in +source code form), and must require no special password or key for +unpacking, reading or copying. + + 7. Additional Terms. + + "Additional permissions" are terms that supplement the terms of this +License by making exceptions from one or more of its conditions. +Additional permissions that are applicable to the entire Program shall +be treated as though they were included in this License, to the extent +that they are valid under applicable law. If additional permissions +apply only to part of the Program, that part may be used separately +under those permissions, but the entire Program remains governed by +this License without regard to the additional permissions. + + When you convey a copy of a covered work, you may at your option +remove any additional permissions from that copy, or from any part of +it. (Additional permissions may be written to require their own +removal in certain cases when you modify the work.) You may place +additional permissions on material, added by you to a covered work, +for which you have or can give appropriate copyright permission. + + Notwithstanding any other provision of this License, for material you +add to a covered work, you may (if authorized by the copyright holders of +that material) supplement the terms of this License with terms: + + a) Disclaiming warranty or limiting liability differently from the + terms of sections 15 and 16 of this License; or + + b) Requiring preservation of specified reasonable legal notices or + author attributions in that material or in the Appropriate Legal + Notices displayed by works containing it; or + + c) Prohibiting misrepresentation of the origin of that material, or + requiring that modified versions of such material be marked in + reasonable ways as different from the original version; or + + d) Limiting the use for publicity purposes of names of licensors or + authors of the material; or + + e) Declining to grant rights under trademark law for use of some + trade names, trademarks, or service marks; or + + f) Requiring indemnification of licensors and authors of that + material by anyone who conveys the material (or modified versions of + it) with contractual assumptions of liability to the recipient, for + any liability that these contractual assumptions directly impose on + those licensors and authors. + + All other non-permissive additional terms are considered "further +restrictions" within the meaning of section 10. If the Program as you +received it, or any part of it, contains a notice stating that it is +governed by this License along with a term that is a further +restriction, you may remove that term. If a license document contains +a further restriction but permits relicensing or conveying under this +License, you may add to a covered work material governed by the terms +of that license document, provided that the further restriction does +not survive such relicensing or conveying. + + If you add terms to a covered work in accord with this section, you +must place, in the relevant source files, a statement of the +additional terms that apply to those files, or a notice indicating +where to find the applicable terms. + + Additional terms, permissive or non-permissive, may be stated in the +form of a separately written license, or stated as exceptions; +the above requirements apply either way. + + 8. Termination. + + You may not propagate or modify a covered work except as expressly +provided under this License. Any attempt otherwise to propagate or +modify it is void, and will automatically terminate your rights under +this License (including any patent licenses granted under the third +paragraph of section 11). + + However, if you cease all violation of this License, then your +license from a particular copyright holder is reinstated (a) +provisionally, unless and until the copyright holder explicitly and +finally terminates your license, and (b) permanently, if the copyright +holder fails to notify you of the violation by some reasonable means +prior to 60 days after the cessation. + + Moreover, your license from a particular copyright holder is +reinstated permanently if the copyright holder notifies you of the +violation by some reasonable means, this is the first time you have +received notice of violation of this License (for any work) from that +copyright holder, and you cure the violation prior to 30 days after +your receipt of the notice. + + Termination of your rights under this section does not terminate the +licenses of parties who have received copies or rights from you under +this License. If your rights have been terminated and not permanently +reinstated, you do not qualify to receive new licenses for the same +material under section 10. + + 9. Acceptance Not Required for Having Copies. + + You are not required to accept this License in order to receive or +run a copy of the Program. Ancillary propagation of a covered work +occurring solely as a consequence of using peer-to-peer transmission +to receive a copy likewise does not require acceptance. However, +nothing other than this License grants you permission to propagate or +modify any covered work. These actions infringe copyright if you do +not accept this License. Therefore, by modifying or propagating a +covered work, you indicate your acceptance of this License to do so. + + 10. Automatic Licensing of Downstream Recipients. + + Each time you convey a covered work, the recipient automatically +receives a license from the original licensors, to run, modify and +propagate that work, subject to this License. You are not responsible +for enforcing compliance by third parties with this License. + + An "entity transaction" is a transaction transferring control of an +organization, or substantially all assets of one, or subdividing an +organization, or merging organizations. If propagation of a covered +work results from an entity transaction, each party to that +transaction who receives a copy of the work also receives whatever +licenses to the work the party's predecessor in interest had or could +give under the previous paragraph, plus a right to possession of the +Corresponding Source of the work from the predecessor in interest, if +the predecessor has it or can get it with reasonable efforts. + + You may not impose any further restrictions on the exercise of the +rights granted or affirmed under this License. For example, you may +not impose a license fee, royalty, or other charge for exercise of +rights granted under this License, and you may not initiate litigation +(including a cross-claim or counterclaim in a lawsuit) alleging that +any patent claim is infringed by making, using, selling, offering for +sale, or importing the Program or any portion of it. + + 11. Patents. + + A "contributor" is a copyright holder who authorizes use under this +License of the Program or a work on which the Program is based. The +work thus licensed is called the contributor's "contributor version". + + A contributor's "essential patent claims" are all patent claims +owned or controlled by the contributor, whether already acquired or +hereafter acquired, that would be infringed by some manner, permitted +by this License, of making, using, or selling its contributor version, +but do not include claims that would be infringed only as a +consequence of further modification of the contributor version. For +purposes of this definition, "control" includes the right to grant +patent sublicenses in a manner consistent with the requirements of +this License. + + Each contributor grants you a non-exclusive, worldwide, royalty-free +patent license under the contributor's essential patent claims, to +make, use, sell, offer for sale, import and otherwise run, modify and +propagate the contents of its contributor version. + + In the following three paragraphs, a "patent license" is any express +agreement or commitment, however denominated, not to enforce a patent +(such as an express permission to practice a patent or covenant not to +sue for patent infringement). To "grant" such a patent license to a +party means to make such an agreement or commitment not to enforce a +patent against the party. + + If you convey a covered work, knowingly relying on a patent license, +and the Corresponding Source of the work is not available for anyone +to copy, free of charge and under the terms of this License, through a +publicly available network server or other readily accessible means, +then you must either (1) cause the Corresponding Source to be so +available, or (2) arrange to deprive yourself of the benefit of the +patent license for this particular work, or (3) arrange, in a manner +consistent with the requirements of this License, to extend the patent +license to downstream recipients. "Knowingly relying" means you have +actual knowledge that, but for the patent license, your conveying the +covered work in a country, or your recipient's use of the covered work +in a country, would infringe one or more identifiable patents in that +country that you have reason to believe are valid. + + If, pursuant to or in connection with a single transaction or +arrangement, you convey, or propagate by procuring conveyance of, a +covered work, and grant a patent license to some of the parties +receiving the covered work authorizing them to use, propagate, modify +or convey a specific copy of the covered work, then the patent license +you grant is automatically extended to all recipients of the covered +work and works based on it. + + A patent license is "discriminatory" if it does not include within +the scope of its coverage, prohibits the exercise of, or is +conditioned on the non-exercise of one or more of the rights that are +specifically granted under this License. You may not convey a covered +work if you are a party to an arrangement with a third party that is +in the business of distributing software, under which you make payment +to the third party based on the extent of your activity of conveying +the work, and under which the third party grants, to any of the +parties who would receive the covered work from you, a discriminatory +patent license (a) in connection with copies of the covered work +conveyed by you (or copies made from those copies), or (b) primarily +for and in connection with specific products or compilations that +contain the covered work, unless you entered into that arrangement, +or that patent license was granted, prior to 28 March 2007. + + Nothing in this License shall be construed as excluding or limiting +any implied license or other defenses to infringement that may +otherwise be available to you under applicable patent law. + + 12. No Surrender of Others' Freedom. + + If 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 convey a +covered work so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you may +not convey it at all. For example, if you agree to terms that obligate you +to collect a royalty for further conveying from those to whom you convey +the Program, the only way you could satisfy both those terms and this +License would be to refrain entirely from conveying the Program. + + 13. Use with the GNU Affero General Public License. + + Notwithstanding any other provision of this License, you have +permission to link or combine any covered work with a work licensed +under version 3 of the GNU Affero General Public License into a single +combined work, and to convey the resulting work. The terms of this +License will continue to apply to the part which is the covered work, +but the special requirements of the GNU Affero General Public License, +section 13, concerning interaction through a network will apply to the +combination as such. + + 14. Revised Versions of this License. + + The Free Software Foundation may publish revised and/or new versions of +the GNU 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 that a certain numbered version of the GNU General +Public License "or any later version" applies to it, you have the +option of following the terms and conditions either of that numbered +version or of any later version published by the Free Software +Foundation. If the Program does not specify a version number of the +GNU General Public License, you may choose any version ever published +by the Free Software Foundation. + + If the Program specifies that a proxy can decide which future +versions of the GNU General Public License can be used, that proxy's +public statement of acceptance of a version permanently authorizes you +to choose that version for the Program. + + Later license versions may give you additional or different +permissions. However, no additional obligations are imposed on any +author or copyright holder as a result of your choosing to follow a +later version. + + 15. Disclaimer of Warranty. + + 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. + + 16. Limitation of Liability. + + IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS +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. + + 17. Interpretation of Sections 15 and 16. + + If the disclaimer of warranty and limitation of liability provided +above cannot be given local legal effect according to their terms, +reviewing courts shall apply local law that most closely approximates +an absolute waiver of all civil liability in connection with the +Program, unless a warranty or assumption of liability accompanies a +copy of the Program in return for a fee. + + 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 +state the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + 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 3 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, see . + +Also add information on how to contact you by electronic and paper mail. + + If the program does terminal interaction, make it output a short +notice like this when it starts in an interactive mode: + + Copyright (C) + This program 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, your program's commands +might be different; for a GUI interface, you would use an "about box". + + You should also get your employer (if you work as a programmer) or school, +if any, to sign a "copyright disclaimer" for the program, if necessary. +For more information on this, and how to apply and follow the GNU GPL, see +. + + The GNU 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 Lesser General +Public License instead of this License. But first, please read +. diff --git a/ChangeLog b/ChangeLog new file mode 100644 index 0000000..5f21edd --- /dev/null +++ b/ChangeLog @@ -0,0 +1,4 @@ +2009-01-18 Michael Orlitzky + + * === Released 0.0.1 === + * Initial release. diff --git a/INSTALL b/INSTALL new file mode 100644 index 0000000..8b82ade --- /dev/null +++ b/INSTALL @@ -0,0 +1,291 @@ +Installation Instructions +************************* + +Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005, +2006, 2007, 2008 Free Software Foundation, Inc. + + This file is free documentation; the Free Software Foundation gives +unlimited permission to copy, distribute and modify it. + +Basic Installation +================== + + Briefly, the shell commands `./configure; make; make install' should +configure, build, and install this package. The following +more-detailed instructions are generic; see the `README' file for +instructions specific to this package. + + 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 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. + + Running `configure' might take a while. 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. + + 6. Often, you can also type `make uninstall' to remove the installed + files again. + +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 configuration parameters +by setting variables in the command line or in the environment. Here +is an example: + + ./configure CC=c99 CFLAGS=-g 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 can use 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 `..'. + + With a non-GNU `make', it is safer 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. + + On MacOS X 10.5 and later systems, you can create libraries and +executables that work on multiple system types--known as "fat" or +"universal" binaries--by specifying multiple `-arch' options to the +compiler but only a single `-arch' option to the preprocessor. Like +this: + + ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ + CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ + CPP="gcc -E" CXXCPP="g++ -E" + + This is not guaranteed to produce working output in all cases, you +may have to build one architecture at a time and combine the results +using the `lipo' tool if you have problems. + +Installation Names +================== + + By default, `make install' installs the package's commands under +`/usr/local/bin', include files under `/usr/local/include', etc. You +can specify an installation prefix other than `/usr/local' by giving +`configure' the option `--prefix=PREFIX'. + + You can specify separate installation prefixes for +architecture-specific files and architecture-independent files. If you +pass the option `--exec-prefix=PREFIX' to `configure', the package uses +PREFIX as the prefix for installing programs and libraries. +Documentation and other data files still use the regular prefix. + + In addition, if you use an unusual directory layout you can give +options like `--bindir=DIR' 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. + +Particular systems +================== + + On HP-UX, the default C compiler is not ANSI C compatible. If GNU +CC is not installed, it is recommended to use the following options in +order to use an ANSI C compiler: + + ./configure CC="cc -Ae" + +and if that doesn't work, install pre-built binaries of GCC for HP-UX. + + On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot +parse its `' header file. The option `-nodtk' can be used as +a workaround. If GNU CC is not installed, it is therefore recommended +to try + + ./configure CC="cc" + +and if that doesn't work, try + + ./configure CC="cc -nodtk" + +Specifying the System Type +========================== + + There may be some features `configure' cannot figure out +automatically, but needs to determine by the type of machine the package +will run on. Usually, assuming the package is built to be run on the +_same_ architectures, `configure' can figure that out, but if it prints +a message saying it cannot guess the machine 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 machine type. + + If you are _building_ compiler tools for cross-compiling, you should +use the option `--target=TYPE' 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'. + +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 + +causes the specified `gcc' to be used as the C compiler (unless it is +overridden in the site shell script). + +Unfortunately, this technique does not work for `CONFIG_SHELL' due to +an Autoconf bug. Until the bug is fixed you can use this workaround: + + CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash + +`configure' Invocation +====================== + + `configure' recognizes the following options to control how it +operates. + +`--help' +`-h' + Print a summary of all of the options to `configure', and exit. + +`--help=short' +`--help=recursive' + Print a summary of the options unique to this package's + `configure', and exit. The `short' variant lists options used + only in the top level, while the `recursive' variant lists options + also present in any nested packages. + +`--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. + +`--prefix=DIR' + Use DIR as the installation prefix. *Note Installation Names:: + for more details, including other options available for fine-tuning + the installation locations. + +`--no-create' +`-n' + Run the configure checks, but stop before creating any output + files. + +`configure' also accepts some other, not widely useful, options. Run +`configure --help' for more details. + diff --git a/Makefile.am b/Makefile.am new file mode 100644 index 0000000..de8f5b4 --- /dev/null +++ b/Makefile.am @@ -0,0 +1,25 @@ +# $Id$ + +SUBDIRS = \ + icons \ + panel-plugin \ + po + +distclean-local: + rm -rf *.cache *~ + +rpm: dist + rpmbuild -ta $(PACKAGE)-$(VERSION).tar.gz + @rm -f $(PACKAGE)-$(VERSION).tar.gz + +EXTRA_DIST = \ + intltool-extract.in \ + intltool-merge.in \ + intltool-update.in + +DISTCLEANFILES = \ + intltool-extract \ + intltool-merge \ + intltool-update + +# vi:set ts=8 sw=8 noet ai nocindent syntax=automake: diff --git a/NEWS b/NEWS new file mode 100644 index 0000000..7dedc30 --- /dev/null +++ b/NEWS @@ -0,0 +1,3 @@ +2009-01-18 +---------- +Plugin begins its existence. diff --git a/README b/README new file mode 100644 index 0000000..0dc7dd7 --- /dev/null +++ b/README @@ -0,0 +1,52 @@ +1. What is it? + +A plugin to indicate the status of the IBM Hard Drive Active +Protection System, or HDAPS. + +2. Requirements + +As of Linux kernel 2.6.28, a kernel patch is no longer required to +support the HDAPS functionality. As a result, this plugin will only +(officially) support kernels newer than 2.6.28. + +It will also only (officially) support the hdaps module provided +by the tp_smapi project. The tp_smapi module is currently recommended +by the hdaps devs, so you should be using it. In the future, the +in-tree module will probably be supported as well. + +3. Installation + +I think it builds like most XFCE panel plugins. Run ./autogen.sh in +the project directory, and hopefully it will compile. At that point, +you should have an xfce-hdaps executable in your panel-plugin +directory. + +Now, there should also be an xfce4-hdaps.desktop file in the +panel-plugin directory. You need to copy this to the directory where +XFCE keeps all of those things. For example, the system-wide location +on Gentoo is /usr/share/xfce4/panel-plugins/. + +Finally, modify the X-XFCE-Exec parameter in the desktop file to +reflect the real location of your xfce4-hdaps binary. You should now +be able to add the plugin to your panel. + + +4. Settings + +4a. Poll Frequency + +This is the frequency with which the plugin checks the status of +HDAPS. If you set it to 500ms (the default), it will check every half +second and update the icon according to what it finds. + +4b. Device Name + +The name of the device whose HDAPS status you wish to monitor. This +will almost certainly be a hard drive, and will most likely be "sda". +With any luck, the plugin will auto-detect the supported devices on +your system. If you have more than one supported device, you will +need to select it on the configuration dialog. + +5. How to report bugs + +Email them to me at michael@orlitzky.com. diff --git a/autogen.sh b/autogen.sh new file mode 100755 index 0000000..01373b9 --- /dev/null +++ b/autogen.sh @@ -0,0 +1,35 @@ +#!/bin/sh +# +# $Id$ +# +# Copyright (c) 2002-2007 +# The Xfce development team. All rights reserved. +# + +(type xdt-autogen) >/dev/null 2>&1 || { + cat >&2 </dev/null 2>&1 || { + cat >&2 < "configure.in" + +exec xdt-autogen $@ diff --git a/configure.in.in b/configure.in.in new file mode 100644 index 0000000..cd37134 --- /dev/null +++ b/configure.in.in @@ -0,0 +1,101 @@ +dnl $Id$ +dnl +dnl xfce4-hdaps - An IBM HDAPS plugin for the Xfce panel +dnl +dnl 2009 Michael Orlitzky +dnl + +dnl *************************** +dnl *** Version information *** +dnl *************************** +m4_define([xfce4-hdaps_version], [0.0.1]) + +dnl *************************** +dnl *** Initialize autoconf *** +dnl *************************** +AC_COPYRIGHT([Copyright (c) 2009 + Michael Orlitzky. All rights reserved.]) +AC_INIT([xfce4-hdaps], [xfce4-hdaps_version()], [http://bugzilla.xfce.org/], [xfce4-hdaps]) +AC_PREREQ([2.50]) +AC_CANONICAL_TARGET() +AC_REVISION([$Id]) + +dnl *************************** +dnl *** Initialize automake *** +dnl *************************** +AM_INIT_AUTOMAKE([1.8 dist-bzip2 tar-ustar]) +AM_CONFIG_HEADER([config.h]) +AM_MAINTAINER_MODE() + +dnl ******************************** +dnl *** Check for basic programs *** +dnl ******************************** +AC_PROG_CC() +AC_PROG_LD() +AC_PROG_INSTALL() +AC_PROG_INTLTOOL() + +dnl ********************************** +dnl *** Check for standard headers *** +dnl ********************************** +AC_CHECK_HEADERS([math.h memory.h stdlib.h string.h sys/stat.h \ + sys/time.h time.h]) + +dnl ************************************ +dnl *** Check for standard functions *** +dnl ************************************ +AC_CHECK_FUNCS([]) + +dnl ****************************** +dnl *** Check for i18n support *** +dnl ****************************** +XDT_I18N([@LINGUAS@]) + +dnl ******************************* +dnl *** Check for X11 installed *** +dnl ******************************* +XDT_CHECK_LIBX11_REQUIRE() + +dnl *********************************** +dnl *** Check for required packages *** +dnl *********************************** +XDT_CHECK_PACKAGE([GTK], [gtk+-2.0], [2.6.0]) +XDT_CHECK_PACKAGE([LIBXFCEGUI4], [libxfcegui4-1.0], [4.3.99.2]) +XDT_CHECK_PACKAGE([LIBXFCE4UTIL], [libxfce4util-1.0], [4.3.99.2]) +XDT_CHECK_PACKAGE([LIBXFCE4PANEL], [libxfce4panel-1.0], [4.3.99.2]) + +dnl *********************************** +dnl *** Check for debugging support *** +dnl *********************************** +XDT_FEATURE_DEBUG() + +dnl ********************************* +dnl *** Substitute platform flags *** +dnl ********************************* +AC_MSG_CHECKING([PLATFORM_CPPFLAGS]) +AC_MSG_RESULT([$PLATFORM_CPPFLAGS]) +AC_SUBST([PLATFORM_CPPFLAGS]) +AC_MSG_CHECKING([PLATFORM_CFLAGS]) +AC_MSG_RESULT([$PLATFORM_CFLAGS]) +AC_SUBST([PLATFORM_CFLAGS]) +AC_MSG_CHECKING([PLATFORM_LDFLAGS]) +AC_MSG_RESULT([$PLATFORM_LDFLAGS]) +AC_SUBST([PLATFORM_LDFLAGS]) + +AC_OUTPUT([ +Makefile +icons/Makefile +icons/48x48/Makefile +icons/scalable/Makefile +panel-plugin/Makefile +po/Makefile.in +]) + +dnl *************************** +dnl *** Print configuration *** +dnl *************************** +echo +echo "Build Configuration:" +echo +echo "* Debug Support: $enable_debug" +echo diff --git a/icons/48x48/Makefile.am b/icons/48x48/Makefile.am new file mode 100644 index 0000000..a0b3ad8 --- /dev/null +++ b/icons/48x48/Makefile.am @@ -0,0 +1,10 @@ +# $Id$ + +iconsdir = $(datadir)/icons/hicolor/48x48/apps +icons_DATA = \ + xfce4-hdaps.png + +EXTRA_DIST = \ + $(icons_DATA) + +# vi:set ts=8 sw=8 noet ai nocindent syntax=automake: diff --git a/icons/48x48/xfce4-hdaps.png b/icons/48x48/xfce4-hdaps.png new file mode 100644 index 0000000..4dd436c Binary files /dev/null and b/icons/48x48/xfce4-hdaps.png differ diff --git a/icons/Makefile.am b/icons/Makefile.am new file mode 100644 index 0000000..2caedee --- /dev/null +++ b/icons/Makefile.am @@ -0,0 +1,20 @@ +# $Id$ + +SUBDIRS = \ + 48x48 \ + scalable + +gtk_update_icon_cache = gtk-update-icon-cache -f -t $(datadir)/icons/hicolor + +install-data-hook: + @-if test -z "$(DESTDIR)"; then \ + echo "Updating Gtk icon cache."; \ + $(gtk_update_icon_cache); \ + else \ + echo "*** Icon cache not updated. Remember to run:"; \ + echo "***"; \ + echo "*** $(gtk_update_icon_cache)"; \ + echo "***"; \ + fi + +# vi:set ts=8 sw=8 noet ai nocindent syntax=automake: diff --git a/icons/scalable/Makefile.am b/icons/scalable/Makefile.am new file mode 100644 index 0000000..f5923a8 --- /dev/null +++ b/icons/scalable/Makefile.am @@ -0,0 +1,10 @@ +# $Id$ + +iconsdir = $(datadir)/icons/hicolor/scalable/apps +icons_DATA = \ + xfce4-hdaps.svg + +EXTRA_DIST = \ + $(icons_DATA) + +# vi:set ts=8 sw=8 noet ai nocindent syntax=automake: diff --git a/icons/scalable/xfce4-hdaps.svg b/icons/scalable/xfce4-hdaps.svg new file mode 100644 index 0000000..b359bb1 --- /dev/null +++ b/icons/scalable/xfce4-hdaps.svg @@ -0,0 +1,408 @@ + + + + + + + image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/panel-plugin/Makefile.am b/panel-plugin/Makefile.am new file mode 100644 index 0000000..cf794a0 --- /dev/null +++ b/panel-plugin/Makefile.am @@ -0,0 +1,64 @@ +# $Id$ + +INCLUDES = \ + -I$(top_srcdir) \ + -DG_LOG_DOMAIN=\"xfce4-hdaps\" \ + -DPACKAGE_LOCALE_DIR=\"$(localedir)\" \ + $(PLATFORM_CPPFLAGS) + +# +# HDAPS plugin +# +plugin_PROGRAMS = \ + xfce4-hdaps + +plugindir = \ + $(libexecdir)/xfce4/panel-plugins + +xfce4_hdaps_SOURCES = \ + hdaps.c \ + hdaps.h \ + xfce4-hdaps.c \ + xfce4-hdaps.h \ + xfce4-hdaps-dialogs.c \ + xfcd4-hdaps-dialogs.h + +xfce4_hdaps_CFLAGS = \ + $(LIBXFCE4UTIL_CFLAGS) \ + $(LIBXFCEGUI4_CFLAGS) \ + $(LIBXFCE4PANEL_CFLAGS) \ + $(PLATFORM_CFLAGS) + +xfce4_hdaps_LDADD = \ + $(LIBXFCE4UTIL_LIBS) \ + $(LIBXFCEGUI4_LIBS) \ + $(LIBXFCE4PANEL_LIBS) + +# +# Desktop file +# +desktopdir = \ + $(datadir)/xfce4/panel-plugins + +desktop_in_in_files = \ + xfce4-hdaps.desktop.in.in + +desktop_in_files = \ + $(desktop_in_in_files:.desktop.in.in=.desktop.in) + +%.desktop.in: %.desktop.in.in + sed -e "s,\@libexecdir\@,$(libexecdir),g" < $< > $@ + +desktop_DATA = \ + $(desktop_in_files:.desktop.in=.desktop) + +@INTLTOOL_DESKTOP_RULE@ + +EXTRA_DIST = \ + $(desktop_in_in_files) + +CLEANFILES = \ + $(desktop_in_files) \ + $(desktop_DATA) + +# vi:set ts=8 sw=8 noet ai nocindent syntax=automake: diff --git a/panel-plugin/hdaps.c b/panel-plugin/hdaps.c new file mode 100644 index 0000000..de1476f --- /dev/null +++ b/panel-plugin/hdaps.c @@ -0,0 +1,108 @@ +#ifdef HAVE_CONFIG_H +#include +#endif + +#include +#include +#include +#include +#include +#include +#include "hdaps.h" + +/* The most space we expect to need when reading in + a file using these hdaps functions. To exceed 32 + bytes worth of content in unload_heads you'd have + to throw your laptop hard as a motherfucker. */ +#define MAX_FILE_CONTENTS_SIZE 32 + +/* Where the block device names are located. */ +#define SYSFS_BLOCK_DEVICE_DIR "/sys/block/" + + +static int hdaps_device_exists(const char* device) { + /* Determine whether or not a device (file) exists and has an + unload_heads entry in sysfs. */ + char path[FILENAME_MAX]; + snprintf(path, FILENAME_MAX, UNLOAD_HEADS_FMT, device); + return (access(path, F_OK) == 0); +} + + +int get_hdaps_device_list(char list[MAX_HDAPS_DEVICES][FILENAME_MAX]) { + int list_idx = 0; + DIR *dp; + struct dirent *ep; + + dp = opendir(SYSFS_BLOCK_DEVICE_DIR); + + if (dp != NULL) { + while ((ep = readdir(dp)) && list_idx < MAX_HDAPS_DEVICES) { + /* This next test covers "." and ".." too. */ + if (hdaps_device_exists(ep->d_name)) { + strncpy(list[list_idx], ep->d_name, FILENAME_MAX); + list_idx++; + } + } + + (void)closedir(dp); /* Explicitly ignore this. */ + } + + return list_idx; +} + + +int slurp_file(const char* filename, char* buf, int max_bytes) { + /* This function just reads the contents of filename + * into buf. It is slightly stolen from the hdapsd project. + */ + + /* Return an error value by default. */ + int ret = HDAPS_ERROR; + int fd = open(filename, O_RDONLY); + + if (filename == NULL || buf == NULL) { + return ret; + } + + if (fd < 0) { + fprintf(stderr, "open(%s): %s\n", filename, strerror(errno)); + return fd; + } + + ret = read(fd, buf, max_bytes-1); + + if (ret < 0) { + fprintf(stderr, "read(%s): %s\n", filename, strerror(errno)); + } + else { + buf[ret] = 0; /* Null-terminate buf. */ + } + + if (close(fd)) { + fprintf(stderr, "close(%s): %s\n", filename, strerror(errno)); + } + + return ret; +} + + + + +int parse_int_from_file(const char* filename) { + /* Read an integer from a file. We expect the file + to contain an integer (although in string form). */ + + char buf[MAX_FILE_CONTENTS_SIZE]; + int ret = slurp_file(filename, buf, sizeof(buf)); + + if (ret < 0) { + /* Why did we read fewer than 0 bytes? */ + return ret; + } + else { + /* If we read more than 0 bytes, hopefully we can + count on atoi to succeed. */ + return atoi(buf); + } +} diff --git a/panel-plugin/hdaps.h b/panel-plugin/hdaps.h new file mode 100644 index 0000000..4624dae --- /dev/null +++ b/panel-plugin/hdaps.h @@ -0,0 +1,15 @@ +#ifndef __HDAPS_H__ +#define __HDAPS_H__ + +#define HDAPS_ERROR -1 +#define HDAPS_OFF 0 +#define UNLOAD_HEADS_FMT "/sys/block/%s/device/unload_heads" + +/* The most devices we'll consider. Gotta stop somewhere. */ +#define MAX_HDAPS_DEVICES 12 + +int parse_int_from_file(const char* filename); +int slurp_file(const char* filename, char* buf, int max_bytes); +int get_hdaps_device_list(char list[MAX_HDAPS_DEVICES][FILENAME_MAX]); + +#endif diff --git a/panel-plugin/xfce4-hdaps-dialogs.c b/panel-plugin/xfce4-hdaps-dialogs.c new file mode 100644 index 0000000..80e0bcc --- /dev/null +++ b/panel-plugin/xfce4-hdaps-dialogs.c @@ -0,0 +1,194 @@ +#ifdef HAVE_CONFIG_H +#include +#endif + +#include +#include +#include +#include "xfce4-hdaps-dialogs.h" + +/* Wild guess. Actually borrowed from some code + I copy-and-pasted. Doesn't seem too ugly. */ +#define DEFAULT_BORDER_WIDTH 8 + +/* If people can't read the README, well maybe + * they can do it /online/. + */ +#define PLUGIN_WEBSITE "http://michael.orlitzky.com/code/xfce4-hdaps.php" + + +static void hdaps_configure_response(GtkWidget *dialog, + gint response, + HdapsPlugin *hdaps) { + + if (response == GTK_RESPONSE_HELP) { + /* Launch the user's web browser and direct them to + the plugin's webpage. */ + gboolean spawn_result = g_spawn_command_line_async("exo-open --launch WebBrowser " PLUGIN_WEBSITE, NULL); + + if (G_UNLIKELY(spawn_result == FALSE)) { + g_warning(_("Unable to open the following url: %s"), PLUGIN_WEBSITE); + } + + return; + } + + + if (response == GTK_RESPONSE_OK) { + /* This corresponds to the "Save" button, so we + want to save any settings that may have changed. */ + g_object_set_data(G_OBJECT(hdaps->plugin), "dialog", NULL); + hdaps->poll_frequency = gtk_spin_button_get_value_as_int((GtkSpinButton*)hdaps->sb_poll_frequency); + hdaps->device_name = gtk_combo_box_get_active_text((GtkComboBox*)hdaps->cb_device_name); + snprintf(hdaps->sysfs_file, FILENAME_MAX, UNLOAD_HEADS_FMT, hdaps->device_name); + hdaps_save(hdaps->plugin, hdaps); + hdaps_reset_timeout(hdaps); + } + + + /* Since there is already a "save" button, we should ignore + any changes that were made if the user presses "cancel" + instead. */ + g_object_set_data(G_OBJECT(hdaps->plugin), "dialog", NULL); + xfce_panel_plugin_unblock_menu(hdaps->plugin); + gtk_widget_destroy(dialog); + + return; +} + + + +void hdaps_configure(XfcePanelPlugin *plugin, + HdapsPlugin *hdaps) { + + /* Here comes a bunch of GTK garbage to create the + settings dialog. */ + + GtkWidget *dialog; + GtkWidget *label; + GtkWidget *vbox; + GtkWidget *hbox; + GtkSizeGroup *sg; + + /* Block the plugin menu while the configuration + dialogue is open. Don't forget to unblock it before + we close. */ + xfce_panel_plugin_block_menu(plugin); + + /* Create the dialog */ + dialog = xfce_titled_dialog_new_with_buttons(_("Hdaps Plugin"), + GTK_WINDOW (gtk_widget_get_toplevel (GTK_WIDGET (plugin))), + GTK_DIALOG_DESTROY_WITH_PARENT | GTK_DIALOG_NO_SEPARATOR, + GTK_STOCK_HELP, GTK_RESPONSE_HELP, + GTK_STOCK_SAVE, GTK_RESPONSE_OK, + GTK_STOCK_CANCEL, GTK_RESPONSE_CANCEL, + NULL); + + /* Center the dialog on screen. */ + gtk_window_set_position(GTK_WINDOW(dialog), GTK_WIN_POS_CENTER); + + /* Set dialog icon to a generic settings icon. */ + gtk_window_set_icon_name(GTK_WINDOW(dialog), "xfce4-settings"); + + /* Link the dialog to the plugin, so we can destroy it in case + * the plugin is closed while the dialog is still open. */ + g_object_set_data(G_OBJECT(plugin), "dialog", dialog); + + /* Connect the reponse signal to the dialog. */ + g_signal_connect(G_OBJECT (dialog), "response", + G_CALLBACK(hdaps_configure_response), hdaps); + + + vbox = gtk_vbox_new(FALSE, DEFAULT_BORDER_WIDTH); + gtk_container_set_border_width(GTK_CONTAINER(vbox), DEFAULT_BORDER_WIDTH - 2); + gtk_box_pack_start(GTK_BOX(GTK_DIALOG(dialog)->vbox), vbox, TRUE, TRUE, 0); + + /* Create size group to keep widgets aligned */ + sg = gtk_size_group_new(GTK_SIZE_GROUP_HORIZONTAL); + + hbox = gtk_hbox_new(FALSE, DEFAULT_BORDER_WIDTH); + gtk_box_pack_start(GTK_BOX(vbox), hbox, FALSE, FALSE, 0); + + label = gtk_label_new(_("Poll Frequency:")); + gtk_size_group_add_widget(sg, label); + gtk_misc_set_alignment(GTK_MISC(label), 0, 0.5); + gtk_box_pack_start(GTK_BOX(hbox), label, FALSE, FALSE, 0); + + hdaps->sb_poll_frequency = gtk_spin_button_new_with_range(100, 5000, 100); + gtk_spin_button_set_value((GtkSpinButton*)hdaps->sb_poll_frequency, hdaps->poll_frequency); + + gtk_box_pack_start(GTK_BOX(hbox), + hdaps->sb_poll_frequency, + FALSE, + FALSE, + 0); + + /* Create the device name dropdown. */ + hbox = gtk_hbox_new(FALSE, DEFAULT_BORDER_WIDTH); + gtk_box_pack_start(GTK_BOX(vbox), hbox, FALSE, FALSE, 0); + + label = gtk_label_new(_("Device Name:")); + gtk_size_group_add_widget(sg, label); + gtk_misc_set_alignment(GTK_MISC(label), 0, 0.5); + gtk_box_pack_start(GTK_BOX(hbox), label, FALSE, FALSE, 0); + + hdaps->cb_device_name = gtk_combo_box_new_text(); + /* Add the current device name, it should always be available. + Oh, and it should be the default, too. */ + gtk_combo_box_append_text((GtkComboBox*)hdaps->cb_device_name, hdaps->device_name); + + /* This function takes an index, and 0 should be the first + (only) index at this point. */ + gtk_combo_box_set_active((GtkComboBox*)hdaps->cb_device_name, 0); + + /* Now loop through the list of available devices, adding each + to the list as we go. I believe GTK takes care of the duplicates + for us. */ + char hdaps_devices[MAX_HDAPS_DEVICES][FILENAME_MAX]; + int found_devices = get_hdaps_device_list(hdaps_devices); + int list_idx = 0; + + for (list_idx = 0; list_idx < found_devices; list_idx++) { + gtk_combo_box_append_text((GtkComboBox*)hdaps->cb_device_name, hdaps_devices[list_idx]); + } + + gtk_box_pack_start(GTK_BOX(hbox), hdaps->cb_device_name, FALSE, FALSE, 0); + + /* Show the dialog and all of its widgets. */ + gtk_widget_show_all(dialog); +} + + + +void hdaps_about(XfcePanelPlugin *plugin) { + GdkPixbuf *icon; + GtkWidget *dialog; + XfceAboutInfo *about; + + /* Send NULL as our license, since GPL >= 3 is not + supported yet. I don't particularly care if people + want to re-license under GPL2, but I also don't want + to cause any unnecessary confusion. */ + about = xfce_about_info_new("xfce4-hdaps", + VERSION, + _("An HDAPS Plugin for XFCE4"), + XFCE_COPYRIGHT_TEXT("2009", "Michael Orlitzky"), + NULL); + + xfce_about_info_set_homepage(about, PLUGIN_WEBSITE); + + xfce_about_info_add_credit(about, + "Michael Orlitzky", + "michael@orlitzky.com", + _("A Reasonable Man")); + + icon = gtk_icon_theme_load_icon(gtk_icon_theme_get_default(), + "xfce4-hdaps", + 48, 0, NULL); + + dialog = xfce_about_dialog_new_with_values(NULL, about, icon); + xfce_about_info_free(about); + gtk_dialog_run(GTK_DIALOG(dialog)); + gtk_widget_destroy(dialog); + g_object_unref(G_OBJECT(icon)); +} diff --git a/panel-plugin/xfce4-hdaps-dialogs.h b/panel-plugin/xfce4-hdaps-dialogs.h new file mode 100644 index 0000000..5eb7435 --- /dev/null +++ b/panel-plugin/xfce4-hdaps-dialogs.h @@ -0,0 +1,16 @@ +#ifndef __XFCE4_HDAPS_DIALOGS_H__ +#define __XFCE4_HDAPS_DIALOGS_H__ + +#include "hdaps.h" +#include "xfce4-hdaps.h" + +G_BEGIN_DECLS + +void hdaps_configure(XfcePanelPlugin *plugin, + HdapsPlugin *hdaps); + +void hdaps_about(XfcePanelPlugin *plugin); + +G_END_DECLS + +#endif diff --git a/panel-plugin/xfce4-hdaps.c b/panel-plugin/xfce4-hdaps.c new file mode 100644 index 0000000..6f7bcfc --- /dev/null +++ b/panel-plugin/xfce4-hdaps.c @@ -0,0 +1,358 @@ +#ifdef HAVE_CONFIG_H +#include +#endif + +#include "xfce4-hdaps.h" +#include "xfce4-hdaps-dialogs.h" + +/* We need a default device. Since we require kernels + newer than 2.6.28, it's probably sdX, and I'm guessing + that sda is most likely. */ +#define DEFAULT_DEVICE_NAME "sda" + +/* How often do we poll, in milliseconds? + This should be configured, but we set the default here. */ +#define DEFAULT_POLL_FREQUENCY 500 + + +/* Prototype, needed to register below. */ +static void hdaps_construct(XfcePanelPlugin *plugin); + +/* Register the plugin with the panel. */ +XFCE_PANEL_PLUGIN_REGISTER_EXTERNAL(hdaps_construct); + + +void hdaps_save(XfcePanelPlugin *plugin, HdapsPlugin *hdaps) { + + XfceRc *rc; + gchar *file; + + /* Get the config file location. XFCE should know this. */ + file = xfce_panel_plugin_save_location(plugin, TRUE); + + if (G_UNLIKELY(file == NULL)) { + DBG("Failed to find the configuration file. Bailing."); + return; + } + + /* Open the config file read/write. */ + rc = xfce_rc_simple_open(file, FALSE); + + /* And we can free the file path now that we've + opened the file. */ + g_free(file); + + if (G_UNLIKELY(rc == NULL)) { + DBG("Failed to open the configuration file. Bailing."); + return; + } + + + /* Write any user-configured values to the resource file. */ + if (hdaps->device_name) { + xfce_rc_write_entry(rc, "device_name", hdaps->device_name); + } + + xfce_rc_write_int_entry(rc, "poll_frequency", hdaps->poll_frequency); + + /* close the rc file */ + xfce_rc_close(rc); +} + + + +void hdaps_set_icon(HdapsPlugin *hdaps, int status) { + GdkPixbuf *icon; + gint size; + + /* Panel info magic. */ + size = xfce_panel_plugin_get_size(hdaps->plugin) - 6; + + /* Try to load an icon from the current icon theme. */ + if (status < HDAPS_OFF) { + /* Error */ + icon = gtk_icon_theme_load_icon(gtk_icon_theme_get_default(), + "dialog-error", + size, 0, NULL); + } + else if (status == HDAPS_OFF) { + icon = gtk_icon_theme_load_icon(gtk_icon_theme_get_default(), + "drive-harddisk", + size, 0, NULL); + } + else { + /* status > HDAPS_OFF means it's on. */ + icon = gtk_icon_theme_load_icon(gtk_icon_theme_get_default(), + "emblem-nowrite", + size, 0, NULL); + } + + /* Get rid of the previous icon. */ + if (hdaps->icon) { + gtk_widget_destroy(hdaps->icon); + } + + if (icon) { + hdaps->icon = gtk_image_new_from_pixbuf(icon); + g_object_unref(G_OBJECT(icon)); + } + else { + hdaps->icon = gtk_image_new_from_icon_name("dialog-warning", GTK_ICON_SIZE_BUTTON); + } + + gtk_box_pack_start(GTK_BOX(hdaps->hvbox), GTK_WIDGET(hdaps->icon), FALSE, FALSE, 0); + gtk_widget_show(hdaps->icon); + + return; +} + + +static void hdaps_set_defaults(HdapsPlugin *hdaps) { + DBG("Configuring all settings to defaults."); + hdaps->device_name = g_strdup(DEFAULT_DEVICE_NAME); + snprintf(hdaps->sysfs_file, FILENAME_MAX, UNLOAD_HEADS_FMT, hdaps->device_name); + hdaps->poll_frequency = DEFAULT_POLL_FREQUENCY; +} + + +static void hdaps_read(HdapsPlugin *hdaps) { + + XfceRc *rc; + gchar *file; + const gchar *saved_device_name; + + /* Get the plugin config file location. XFCE should know this. */ + file = xfce_panel_plugin_save_location(hdaps->plugin, TRUE); + + if (G_UNLIKELY(file == NULL)) { + DBG("Something went wrong getting the configuration file location."); + DBG("Retaining default settings."); + return; + } + + /* Open the config file read-only. */ + rc = xfce_rc_simple_open(file, TRUE); + + /* Don't need this anymore if we've got a file handle. */ + g_free(file); + + if (G_UNLIKELY(rc == NULL)) { + DBG("There was an error opening the configuration file."); + DBG("Retaining default settings."); + return; + } + + /* Read the settings, one at a time. */ + + /* We use saved_device_name here because we need + to dupe the string after we read it in from the + config file. */ + saved_device_name = xfce_rc_read_entry(rc, + "device_name", + DEFAULT_DEVICE_NAME); + hdaps->device_name = g_strdup(saved_device_name); + snprintf(hdaps->sysfs_file, FILENAME_MAX, UNLOAD_HEADS_FMT, hdaps->device_name); + + /* Integers are easier. */ + hdaps->poll_frequency = xfce_rc_read_int_entry(rc, + "poll_frequency", + DEFAULT_POLL_FREQUENCY); + + /* And close the config file. */ + xfce_rc_close(rc); +} + + + + +static HdapsPlugin *hdaps_new(XfcePanelPlugin *plugin) { + HdapsPlugin *hdaps; + GtkOrientation orientation; + + /* Allocate memory for the plugin struct, and zero it. */ + hdaps = panel_slice_new0(HdapsPlugin); + + /* The HdapsPlugin gets a copy of the XfcePanelPlugin. */ + hdaps->plugin = plugin; + + /* Set default values right before reading in the user's settings. + This way, hdaps_read() doesn't have to set defaults on error + conditions. */ + hdaps_set_defaults(hdaps); + + /* Read any user settings into the HdapsPlugin. */ + hdaps_read(hdaps); + + /* Get the current orientation. Magic. */ + orientation = xfce_panel_plugin_get_orientation(plugin); + + /* This creates the event box and shows it. This + is necessary to, + + a) See the widget + b) Interact with it via right-click, etc. + */ + hdaps->eventbox = gtk_event_box_new(); + gtk_widget_show(hdaps->eventbox); + + /* Set up the hvbox for the widget, which supports + both horizontal and vertical (hv) orientations. */ + hdaps->hvbox = xfce_hvbox_new(orientation, FALSE, 2); + gtk_widget_show(hdaps->hvbox); + gtk_container_add(GTK_CONTAINER(hdaps->eventbox), hdaps->hvbox); + + /* We only change the icon when the status has changed, + so it's important that they start out n*sync. */ + hdaps->previous_status = HDAPS_OFF; + hdaps_set_icon(hdaps, HDAPS_OFF); + + return hdaps; +} + + + +static void hdaps_free(XfcePanelPlugin *plugin, + HdapsPlugin *hdaps) { + + GtkWidget *dialog; + + /* Destroy the dialog if it's still open. */ + dialog = g_object_get_data(G_OBJECT(plugin), "dialog"); + + if (G_UNLIKELY(dialog != NULL)) { + gtk_widget_destroy(dialog); + } + + /* Destroy the panel widgets. When dumb comments like these + are left over, they're from the sample panel applet, + I swear. */ + gtk_widget_destroy(hdaps->hvbox); + + /* Remove the timeout that was set during creation. */ + if (hdaps->timeout) { + g_source_remove(hdaps->timeout); + } + + /* And free the string (if any) containing + the device name. */ + if (G_LIKELY(hdaps->device_name != NULL)) { + g_free(hdaps->device_name); + } + + /* ...and finally free the plugin structure. */ + panel_slice_free(HdapsPlugin, hdaps); +} + + + +static void hdaps_orientation_changed(XfcePanelPlugin *plugin, + GtkOrientation orientation, + HdapsPlugin *hdaps) { + + /* Change the plugin's orientation. Basically magic to me. */ + xfce_hvbox_set_orientation(XFCE_HVBOX(hdaps->hvbox), orientation); +} + + + +static gboolean hdaps_size_changed(XfcePanelPlugin *plugin, + gint size, + HdapsPlugin *hdaps) { + + GtkOrientation orientation; + + /* Get the current orientation of the plugin. */ + orientation = xfce_panel_plugin_get_orientation(plugin); + + /* We want to make the widget "bigger" in the direction + of its orientation. Or is it the other way around? */ + if (orientation == GTK_ORIENTATION_HORIZONTAL) { + gtk_widget_set_size_request(GTK_WIDGET(plugin), -1, size); + } + else { + gtk_widget_set_size_request(GTK_WIDGET(plugin), size, -1); + } + + /* We handled the change, so we're supposed to return TRUE. */ + return TRUE; +} + + + +static gboolean hdaps_update_status(HdapsPlugin *hdaps) { + /* This checks the status of HDAPS and updates the + widget accordingly. */ + + /* This just gets the status. */ + int status = parse_int_from_file(hdaps->sysfs_file); + + if (status != hdaps->previous_status) { + /* And we only update the icon if we need to. */ + hdaps_set_icon(hdaps, status); + hdaps->previous_status = status; + } + + return TRUE; +} + + + +void hdaps_reset_timeout(HdapsPlugin *hdaps) { + /* Remove, and then re-set the timeout function. Useful + for changing the poll frequency. */ + if (hdaps->timeout) { + g_source_remove(hdaps->timeout); + } + + hdaps->timeout = g_timeout_add(hdaps->poll_frequency, (GSourceFunc)hdaps_update_status, hdaps); +} + + + +static void hdaps_construct(XfcePanelPlugin *plugin) { + HdapsPlugin *hdaps; + + /* Set the "translation domain". I don't know what that does. */ + xfce_textdomain(GETTEXT_PACKAGE, PACKAGE_LOCALE_DIR, "UTF-8"); + + /* First, create the plugin. */ + hdaps = hdaps_new(plugin); + + /* Add the plugin's eventbox to the panel. */ + gtk_container_add(GTK_CONTAINER(plugin), hdaps->eventbox); + + /* This configures the right-click menu to appear + on the plugin's eventbox. */ + xfce_panel_plugin_add_action_widget(plugin, hdaps->eventbox); + + /* Connect the common event handlers. */ + g_signal_connect(G_OBJECT(plugin), "free-data", + G_CALLBACK(hdaps_free), hdaps); + + g_signal_connect (G_OBJECT(plugin), "save", + G_CALLBACK(hdaps_save), hdaps); + + g_signal_connect (G_OBJECT(plugin), "size-changed", + G_CALLBACK(hdaps_size_changed), hdaps); + + g_signal_connect (G_OBJECT(plugin), "orientation-changed", + G_CALLBACK(hdaps_orientation_changed), hdaps); + + /* Show the "configure" right-click menu item, and + connect its event handler. */ + xfce_panel_plugin_menu_show_configure(plugin); + g_signal_connect(G_OBJECT(plugin), "configure-plugin", + G_CALLBACK(hdaps_configure), hdaps); + + /* Show the "about" right-click menu item, and + connect its event handler. */ + xfce_panel_plugin_menu_show_about(plugin); + g_signal_connect(G_OBJECT(plugin), "about", + G_CALLBACK(hdaps_about), hdaps); + + /* Set the timeout for the function which checks the + HDAPS status. */ + hdaps_reset_timeout(hdaps); + + return; +} diff --git a/panel-plugin/xfce4-hdaps.desktop.in.in b/panel-plugin/xfce4-hdaps.desktop.in.in new file mode 100644 index 0000000..d65e5d9 --- /dev/null +++ b/panel-plugin/xfce4-hdaps.desktop.in.in @@ -0,0 +1,8 @@ +[Xfce Panel] +Type=X-XFCE-PanelPlugin +Encoding=UTF-8 +_Name=HDAPS Plugin +_Comment=HDAPS plugin for the Xfce panel +Icon=xfce4-hdaps +X-XFCE-Exec=@libexecdir@/xfce4/panel-plugins/xfce4-hdaps +X-XFCE-Unique=false diff --git a/panel-plugin/xfce4-hdaps.h b/panel-plugin/xfce4-hdaps.h new file mode 100644 index 0000000..7de1d5e --- /dev/null +++ b/panel-plugin/xfce4-hdaps.h @@ -0,0 +1,47 @@ +#ifndef __XFCE4_HDAPS_H__ +#define __XFCE4_HDAPS_H__ + +#include +#include +#include +#include "hdaps.h" + +G_BEGIN_DECLS + +typedef struct { + XfcePanelPlugin *plugin; + + /* Panel widgets */ + GtkWidget *eventbox; + GtkWidget *hvbox; + GtkWidget *icon; + + /* A pointer to the timeout function. + That is, a pointer to the function that gets + executed every poll_frequency milliseconds. */ + gint timeout; + + /* Keep track of the previous status so we don't update the + icon every poll_frequency for no reason. */ + int previous_status; + + /* Settings */ + gchar *device_name; + gint poll_frequency; + + /* Pseudo-setting, updated whenever device_name is. */ + char sysfs_file[FILENAME_MAX]; + + /* Configuration dialog widgets */ + GtkWidget *sb_poll_frequency; /* Spinners on all our rides, yo. */ + GtkWidget *cb_device_name; /* The "Device name" combo box. */ + + +} HdapsPlugin; + +void hdaps_save(XfcePanelPlugin *plugin, + HdapsPlugin *hdaps); + +G_END_DECLS + +#endif diff --git a/po/LINGUAS b/po/LINGUAS new file mode 100644 index 0000000..1756fb5 --- /dev/null +++ b/po/LINGUAS @@ -0,0 +1,2 @@ +# set of available languages (in alphabetic order) + diff --git a/po/POTFILES b/po/POTFILES new file mode 100644 index 0000000..b381f77 --- /dev/null +++ b/po/POTFILES @@ -0,0 +1,4 @@ + ../panel-plugin/hdaps.c \ + ../panel-plugin/xfce4-hdaps.c \ + ../panel-plugin/xfce4-hdaps-dialogs.c \ + ../panel-plugin/xfce4-hdaps.desktop.in.in diff --git a/po/POTFILES.in b/po/POTFILES.in new file mode 100644 index 0000000..7ff2ccc --- /dev/null +++ b/po/POTFILES.in @@ -0,0 +1,4 @@ +panel-plugin/hdaps.c +panel-plugin/xfce4-hdaps.c +panel-plugin/xfce4-hdaps-dialogs.c +panel-plugin/xfce4-hdaps.desktop.in.in