lifeograph-1.0.1/AUTHORS0000644000000000000000000000004412273216102013021 0ustar 00000000000000Ahmet Öztürk [aoz_2@yahoo.com] lifeograph-1.0.1/CMakeLists.txt0000644000000000000000000001676112273216102014526 0ustar 00000000000000# Copyright (C) 2013 Ahmet Öztürk (aoz_2@yahoo.com) # # This file is part of Lifeograph. # # Lifeograph 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. # # Lifeograph 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 Lifeograph. If not, see . cmake_minimum_required( VERSION 2.6 ) project( Lifeograph ) include( ${PROJECT_SOURCE_DIR}/cmake/definitions.cmake ) add_definitions( -Wall -DHAVE_CONFIG_H ) # DEBUG BUILD if( ${CMAKE_BUILD_TYPE} MATCHES Debug ) set( DEBUG_BUILD 1 ) else() set( DEBUG_BUILD 0 ) endif() # PACKAGES find_package( PkgConfig REQUIRED ) find_program( INTLTOOL "intltool-merge" ) if( ${INTLTOOL} MATCHES "INTLTOOL-NOTFOUND" ) message( "Program needed for building Lifeograph not found: intltool" ) return() endif() find_library( GCRYPT gcrypt ) if( ${GCRYPT} MATCHES "GCRYPT-NOTFOUND" ) message( "Dev module needed for building Lifeograph not found: gcrypt" ) return() endif() pkg_check_modules( GTKMM REQUIRED gtkmm-3.0>=3.4 ) if( NOT GTKMM_FOUND ) message( "Dev module needed for building Lifeograph not found: gtkmm-3.0 (>=3.4)" ) return() endif() pkg_check_modules( ENCHANT REQUIRED enchant ) if( NOT ENCHANT_FOUND ) message( "Dev module needed for building Lifeograph not found: enchant" ) return() endif() # CONFIGURATION HEADER FILE configure_file( ${PROJECT_SOURCE_DIR}/config.h.in ${LOCAL_INCL_DIR}/config.h ) # add path of config.h include_directories( ${LOCAL_INCL_DIR} ) include_directories( ${GTKMM_INCLUDE_DIRS} ${ENCHANT_INCLUDE_DIRS} ) #link_directories( ${GTKMM_LIBRARY_DIRS} ${ENCHANT_LIBRARY_DIRS} ) set( CMAKE_RUNTIME_OUTPUT_DIRECTORY ${BIN_DIR} ) # TRANSLATION FILE OPTIONS INVOKED MANUALLY WHEN REQUIRED add_custom_command( OUTPUT ${pot_file} COMMAND intltool-update -p -g ${PACKAGE_NAME} DEPENDS ${SOURCE_FILES} WORKING_DIRECTORY ${po_dir} ) add_custom_target( update-translations COMMAND ${CMAKE_COMMAND} -P ${PROJECT_SOURCE_DIR}/cmake/msgmerge.cmake DEPENDS ${pot_file} WORKING_DIRECTORY ${PROJECT_SOURCE_DIR} ) # TRANSLATION FILE OPTIONS DURING BUILD # based on Remmina code at https://github.com/FreeRDP/Remmina/blob/master/cmake/GETTEXT.cmake set( GETTEXT_MSGFMT_EXECUTABLE msgfmt ) set( mo_files ) if( NOT EXISTS ${MO_DIR} ) file( MAKE_DIRECTORY ${MO_DIR} ) endif() file( GLOB po_files ${po_dir}/*.po ) foreach( po_file ${po_files} ) get_filename_component( lang ${po_file} NAME_WE ) set( mo_file ${MO_DIR}/${lang}.mo ) add_custom_command( OUTPUT ${mo_file} COMMAND ${GETTEXT_MSGFMT_EXECUTABLE} -o ${mo_file} ${po_file} DEPENDS ${po_file} ) install( FILES ${mo_file} DESTINATION share/locale/${lang}/LC_MESSAGES RENAME ${PACKAGE_NAME}.mo ) set( mo_files ${mo_files} ${mo_file} ) endforeach() add_custom_command( OUTPUT ${desktop_file} COMMAND intltool-merge -d -u -q po ${desktop_file_in} ${desktop_file} DEPENDS ${desktop_file_in} ) add_custom_target( format-translations ALL DEPENDS ${mo_files} ${desktop_file} ) # TARGETS add_executable( ${PACKAGE_NAME} ${SOURCE_FILES} ) target_link_libraries( ${PACKAGE_NAME} ${GTKMM_LIBRARIES} ${ENCHANT_LIBRARIES} ${GCRYPT} ) # CUSTOM TARGETS if( ${CMAKE_BUILD_TYPE} MATCHES Debug ) # BACKUP add_custom_target( BACKUP ALL COMMAND ${CMAKE_COMMAND} -P ${PROJECT_SOURCE_DIR}/cmake/backup.cmake DEPENDS ${BIN_DIR}/${PACKAGE_NAME} WORKING_DIRECTORY ${PROJECT_SOURCE_DIR} ) # rev_no.h and build_time.h add_custom_target( TARGET_STAMP_HEADERS COMMAND ${CMAKE_COMMAND} -P ${PROJECT_SOURCE_DIR}/cmake/rev_no.cmake WORKING_DIRECTORY ${PROJECT_SOURCE_DIR} ) add_dependencies( ${PACKAGE_NAME} TARGET_STAMP_HEADERS ) endif() # INSTALL install( TARGETS ${PACKAGE_NAME} DESTINATION bin ) install( FILES lifeograph.appdata.xml DESTINATION share/appdata ) install( FILES icons/lifeograph-48.png DESTINATION share/pixmaps RENAME lifeograph.png ) install( FILES icons/lifeograph-256.png DESTINATION share/icons/hicolor/256x256/apps RENAME lifeograph.png ) install( FILES icons/lifeograph-128.png DESTINATION share/icons/hicolor/128x128/apps RENAME lifeograph.png ) install( FILES icons/lifeograph-64.png DESTINATION share/icons/hicolor/64x64/apps RENAME lifeograph.png ) install( FILES icons/lifeograph-48.png DESTINATION share/icons/hicolor/48x48/apps RENAME lifeograph.png ) install( FILES icons/lifeograph-32.png DESTINATION share/icons/hicolor/32x32/apps RENAME lifeograph.png ) install( FILES icons/lifeograph-24.png DESTINATION share/icons/hicolor/24x24/apps RENAME lifeograph.png ) install( FILES icons/lifeograph-22.png DESTINATION share/icons/hicolor/22x22/apps RENAME lifeograph.png ) install( FILES icons/lifeograph-16.png DESTINATION share/icons/hicolor/16x16/apps RENAME lifeograph.png ) install( FILES icons/scalable/lifeograph.svg DESTINATION share/icons/hicolor/scalable/apps ) #install( FILES ${desktop_file} DESTINATION share/applications ) install( FILES icons/category_tags-16.png DESTINATION share/${PACKAGE_NAME}/icons ) install( FILES icons/category_tags-32.png DESTINATION share/${PACKAGE_NAME}/icons ) install( FILES icons/chapter-16.png DESTINATION share/${PACKAGE_NAME}/icons ) install( FILES icons/chapter-32.png DESTINATION share/${PACKAGE_NAME}/icons ) install( FILES icons/diary-16.png DESTINATION share/${PACKAGE_NAME}/icons ) install( FILES icons/diary-32.png DESTINATION share/${PACKAGE_NAME}/icons ) install( FILES icons/entry-16.png DESTINATION share/${PACKAGE_NAME}/icons ) install( FILES icons/entry-32.png DESTINATION share/${PACKAGE_NAME}/icons ) install( FILES icons/favorite-16.png DESTINATION share/${PACKAGE_NAME}/icons ) install( FILES icons/favorite-32.png DESTINATION share/${PACKAGE_NAME}/icons ) install( FILES icons/filter-16.png DESTINATION share/${PACKAGE_NAME}/icons ) install( FILES icons/filter_remove-16.png DESTINATION share/${PACKAGE_NAME}/icons ) install( FILES icons/filter_symbolic-32.png DESTINATION share/${PACKAGE_NAME}/icons ) install( FILES icons/gear-32.png DESTINATION share/${PACKAGE_NAME}/icons ) install( FILES icons/month-16.png DESTINATION share/${PACKAGE_NAME}/icons ) install( FILES icons/month-32.png DESTINATION share/${PACKAGE_NAME}/icons ) install( FILES icons/tag-16.png DESTINATION share/${PACKAGE_NAME}/icons ) install( FILES icons/tag-32.png DESTINATION share/${PACKAGE_NAME}/icons ) install( FILES ui/lifeograph.ui DESTINATION share/${PACKAGE_NAME}/ui ) install( DIRECTORY diaries/ DESTINATION share/${PACKAGE_NAME}/diaries ) # xdg: mime info install( CODE "execute_process( COMMAND ${CMAKE_COMMAND} -P ${PROJECT_SOURCE_DIR}/cmake/xdg.cmake WORKING_DIRECTORY ${PROJECT_SOURCE_DIR} )" ) # UNINSTALL add_custom_target( uninstall COMMAND ${CMAKE_COMMAND} -DDESTDIR=${CMAKE_INSTALL_PREFIX} -P ${PROJECT_SOURCE_DIR}/cmake/uninstall.cmake WORKING_DIRECTORY ${PROJECT_SOURCE_DIR} ) lifeograph-1.0.1/COPYING0000644000000000000000000010451312273216102013012 0ustar 00000000000000 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 . lifeograph-1.0.1/NEWS0000644000000000000000000002736012273216102012462 0ustar 000000000000001.0.1 - 2014/02/01 * Bug fixes * Small updates to the user manual 1.0.0 - 2013/12/08 * Brand new main icon * Moved from Waf to Cmake for the build system * Implemented the ability to add password to diaries directly in the file dialog while creating them * Migrated to Gtk::Application and added app menu * Improved user interface for creating new entries and chapters * Simplified the look of the diary view * Implemented moving tags to categories by dragging and dropping * Implemented moving chapters to different dates by dragging and dropping onto entries * Implemented changing topic order by dragging and dropping * Implemented tagging and theming entries by dropping tags and themes onto the items in the entry list * Added the option to dismiss the associated entries when dismissing tags and chapters * Added the option to dismiss the associated tags when dismissing tag categories * Added a chart to the tag category view * Improved visibility and sensitivity states of chapter, theme and diary view widgets in read-only mode * Disabled spell-checking in read-only mode * Never show markup chars in read-only mode * For increased security, Lifeograph now asks for password before exporting encrypted diaries * Added support for using multiple configuration files via setting LIFEOGRAPH_CONFIG_FILE variable in the environment * Translation updates * Updated, and extended the user manual * Install Lifeograph diary file Icons to the system * Many bug fixes ================================================================================ 0.11.1 - 2013/02/06 * Updated the look of the diary toolbar * Slightly extended the user manual * Fixed several bugs * Updated translations 0.11.0 - 2012/12/22 * Added trash can functionality to dismiss entries in two steps for increased safety * Replaced the icon view for entry tags with a new custom widget * Printing improved greatly. Main improvements are: * Images in entries are printed as images now * Smarter placement of chapters and entries on pages e.g. chapters always start on a new page now * A new option to justify text * New diary version which brings following new features: * Ability to save spell-checking language for diary as well as for individual entries * Trashed entries which may be restored if needed * Updated the GUI to have a more Gnome3-ish look * Added support for adding diary files to login view by drag & drop from a file browser * Added the ability to move current paragraph up and down with ALT+Up and ALT+Down * Implemented preserving maximized window state * Updated and slightly extended the user manual * Huge code reorganizations and cleanups * Many bug fixes * Added Ukrainian translation and updated existing translations ================================================================================ 0.10.0 - 2012/10/21 * Added support for displaying image thumbnails in text editor for links to image files * Added support for relative paths in links * Greatly improved manual with the images and several new chapters, though still not complete * Added the ability to sort the entries by last change time * Added the ability to (un)indent multiple lines at once * Started to recognize dash as separator for dates such as YYYY-MM-DD * Many small UI improvements such as: * Simplified tags & themes panel * More informing password dialog * More careful handling of diary file permissions * Added "--read-only" switch for opening files as read-only from commandline * Added Read button to the diary file chooser dialog * Added the ability to sort diary files by last read time in the login view * Dropped GtkSpell dependency and started to use Enchant directly * Many bug fixes ================================================================================ 0.9.0 - 2012/07/08 * Lifeograph upgraded to Gtk+ 3 * Improved login screen with an unlimited list of diaries * More compact interface thanks to removal of redundant widgets * Association of Lifeograph diaries with Lifeograph. So, diaries can now be opened by double-clicking in a file explorer. * Addition of extension ".diary" to names of new diaries automatically * Added a read-only mode for preventing a diary from being edited accidentally * Support for multi-line selections when inserting bullets and check-boxes * Added the ability to edit the date of an entry just like editing a tag's name * Added an example diary file to the Lifeograph package which is installed to the system * Added first version of Lifeograph Manual to the Lifeograph package which is installed to the system * Fixed a couple of really old problems * Updated translations ================================================================================ 0.8.2 - 2012/05/10 * Fixed numerous bugs * Cleaned up source code * Updated translations 0.8.1 - 2012/03/05 * Fixed/improved markup character handling * Fixed numerous bugs * Updated Czech translation 0.8.0 - 2012/02/13 * Improved and fixed entry text parser * Visually improved some of the icons * Fixed compilation problems on relatively older systems * Fixed numerous bugs * Updated existing translations ================================================================================ 0.7.5 - 2012/01/28 * Added printing support * Added the ability to add comments to text which can be hidden when not needed * Added the ability to mark paragraphs for being ignored by the parser to be able to use markup chars such as *, =, or _ freely * Implemented filtering enties by date range * Added the ability to hide (filter out) individual entries * Added a monthly chart to the diary view * Skip login screen when an unencrypted diary file is passed in commandline * Added a preview widget to the theme view * Added theme importing from other diaries * Removed background picture feature * Implemented exporting diaries partially * Made minor improvements in the GUI * Fixed numerous bugs * Updated existing translations * Re-added a plain makefile as an alternative way of building Lifeograph for the ones who do not like waf * And many more... 0.7.4 - 2011/11/21 * Added time-independent chapters (topics) and entries for adding notes that are not related to a particular date * Added drag and drop support to the entry list * Implemented changing entry date by drag and drop to another entry or chapter * Added unique numeric IDs to almost every item in the diary * Added a new type of link target: deid:##### which refers to the target item by its ID to never lose the track * Added a new link syntax which shows a descriptive text instead of its target when cursor is not in it * Added an option to diaries that allows users to configure the item that is shown at startup * Made markup characters hidden as long as cursor does not touch them * Enabled formatting toolbar, removed formatting right-click menu * Added timestamp insertion (ALT+T) to entry text editor * Added back autocompletion to the tag editor * Removed chapter dialog; all of its functions are available on the main window now * Every diary must have at least one chapter category now * Made some UI refinements * Fixed numerous bugs * Updated existing translations * And many more... 0.7.3 - 2011/07/30 * Added tag categorization for easier management of tags * Added the ability to store multiple themes within a diary file * Implemented support for different themes per entries * Added basic indentation support to the lists * Implemented automatic insertion of bullets and check boxes * Lifeograph now stores creation and last change date of entries and displays them as a tooltip * When browsing back, it is now possible to cycle through last 5 items shown rather than 2 * Added filtering entries by being favorite and by tags * Fixed sorting entries by size * Redesigned editing user interface: * Added a separate list for tags * Added the ability to tag entries by drag and drop * Added the ability to change themes of entries by drag and drop * Changed main window title bar text to show name of current diary instead of current entry's title * Lifeograph now remembers folders' state of being expanded or collapsed in both entry and tag lists * Added a new toolbar for text formatting (partially functional now) * Implemented importing entries and tags from other diary files * Improved diary file structure to be more consistent and partially more human readable. So, files saved with this version are incompatible with previous releases. * Empty entries are no longer purged at logging out if they have tags * Removed grouping entries by month * Renamed "Chapter Sets" to "Chapter Categories" * Removed most of the right click menus as their functionality is provided by toolbars in various views now * Today button now also creates a new entry when current entry is in today * Many code structure improvements and clean-up * Fixed numerous bugs * Added Dutch, Romanian, and Serbian translations and updated existing translations * And many more... 0.7.2 - 2010/12/12 * Added support for three different types of lists to the editor: * A basic bulleted list system, * a basic numbered list system, * and a very handy check list sytem. * Added the ability to give links to the other entries of a day from within an entry of the same day * Implemented saving daily backup files when compiled in debug mode * Changed default state of markup chars to visible * Added translator credits to the about box * New translations: Arabic, Basque, Galician, and German * Updated existing translations * Numerous bug fixes and improvements 0.7.1 - 2010/10/31 * Added an option to hide wiki markup characters in the entry editor * Added charts to the month and tag views that show graphs of number of entries and usage of tags over time * Implemented a lock mechanism to prevent opening a diary file multiple times * Added back replace and replace all functionality * Added Brazilian Portuguese and Hungarian translations and updated existing translations * Added a chapter icon and improved the month icon * Improved infrastructure at some more points * Numerous bug fixes and improvements 0.7.0 - 2010/09/05 * Switched the build system of choice to "Waf" * Switched to a plain text file based settings storage system, thus * Removed the dependency to Gconfmm * Improved the infrastructure substantially to ease further development of the program * Added a preferences dialog that enables changing auto-logout and background picture settings in the gui * Added the ability to sort entries by size * Added summary views for the open diary and selected month, tag, or chapter that show some information about them as well as providing some editing facilities * Added a text formatting submenu to the textview right-click menu * Added a month icon * Tweaked main window layout to use less vertical space * Added Italian and Polish translations and updated existing translations * [Regression] Temporarily disabled replace and replace all functionality lifeograph-1.0.1/README0000644000000000000000000000140212273216102012630 0ustar 00000000000000Description ----------- Lifeograph is a diary program to take personal notes on life. It has all essential functionality expected in a diary program and strives to have a clean and streamlined user interface. Requirements ------------ For compilation, Lifeograph requires development versions of the following packages to be installed on the system: * gtkmm-3.0 (v3.4 or newer), * enchant, and * gcrypt. In addition, intltool is needed for internationalization and cmake is needed for building. Building & Installation ----------------------- To configure, build, and install, use the following commands in the root directory of Lifeograph: cmake -i . make make install 'make install' may require super user privileges depending on the install prefix. lifeograph-1.0.1/cmake/0000755000000000000000000000000012273216102013033 5ustar 00000000000000lifeograph-1.0.1/config.h.in0000644000000000000000000000044212273216102013776 0ustar 00000000000000#ifndef LIFEOGRAPH_CONFIG_H #define LIFEOGRAPH_CONFIG_H #define PACKAGE "@PACKAGE_NAME@" #define LOCALEDIR "@LOCALEDIR@" #define PIXMAPDIR "@PIXMAPDIR@" #define ICONDIR "@ICONDIR@" #define UIDIR "@UIDIR@" #define DIARYDIR "@DIARYDIR@" #define LIFEOGRAPH_DEBUG_BUILD @DEBUG_BUILD@ #endif lifeograph-1.0.1/diaries/0000755000000000000000000000000012273216102013373 5ustar 00000000000000lifeograph-1.0.1/icons/0000755000000000000000000000000012273216102013066 5ustar 00000000000000lifeograph-1.0.1/lifeograph.10000644000000000000000000000217212273216102014157 0ustar 00000000000000.TH LIFEOGRAPH 1 "02 Sep 2012" .SH NAME \fBlifeograph\fP \- private digital diary .SH SYNOPSIS .B lifeograph\fP\ [\-\-force-welcome] [\-\-open, \-o \fIDIARY\fP]\ [\-\-read-only] .SH DESCRIPTION .B Lifeograph is a digital diary with strong emphasis on privacy. It has a minimalistic and modern gui, designed usability in mind. .SH OPTIONS .TP \fB\-\-open, \-o \fIDIARY\fR Sets the diary file to be opened. If the diary is encrypted, Lifeograph will start with a password prompt. .TP \fB\-\-read\-only, \-r\fR Open the command\-line supplied file in read\-only mode if there is one. .TP \fB\-\-ignore\-locks\fR Enables opening locked diary files. Beware that if a diary file is locked it is probably being edited by another instance of .B Lifeograph or the last session with it did not finish correctly. In either case the lock file may contain unsaved changes. .TP \fB\-\-force\-welcome\fR Forces program to show the welcome screen. Normally welcome screen is only shown on the first run of .B Lifeograph. .SH BUGS If you find a bug, please report it at http://launchpad.net/lifeograph. .SH AUTHORS Ahmet Öztürk (aoz_2 at yahoo dot com) lifeograph-1.0.1/lifeograph.appdata.xml0000644000000000000000000000345712273216102016237 0ustar 00000000000000 lifeograph.desktop CC0 Lifeograph A diary program

Lifeograph is a diary program to take personal notes on life. It has all essential functionality expected in a diary program and strives to have a clean and streamlined user interface.

Lifeograph:

  • supports encrypted (with real encryption) and unencrypted diaries
  • automatically logs out when not used for some time (to protect your diary when you forget to log out doing some other thing) (optional)
  • automatically formats entry titles and subheadings (we owe thanks to tomboy for the idea)
  • wiki-like rich text formatting (*bold*, _italic_, =strikeout=, etc…)
  • basic searching/filtering and replacing text
  • themes in text editor
  • favorite entries
  • entry tagging
  • spell checking
  • links between entries
  • links in URI form (http://, file://, mailto://, etc…)
  • automatic backups
  • printing individual entries or whole diaries
  • basic statistical charts
  • image thumbnails in entries
 http://lifeograph.wdfiles.com/local--files/screenshots/lifeograph-1.0.0-edit.png http://lifeograph.wikidot.com/start aoz_2@yahoo.com lifeograph-1.0.1/lifeograph.desktop.in0000644000000000000000000000041312273216102016071 0ustar 00000000000000[Desktop Entry] Version=1.0 Encoding=UTF-8 Name=Lifeograph _GenericName=Diary _Comment=Keep a private journal of your life Type=Application Terminal=false Exec=lifeograph %F Icon=lifeograph Categories=Utility MimeType=application/x-lifeographdiary StartupNotify=true lifeograph-1.0.1/lifeograph.mime0000644000000000000000000000015112273216102014741 0ustar 00000000000000application/x-lifeographdiary; lifeograph '%s'; description="Lifeograph diary"; test=test -n "$DISPLAY" lifeograph-1.0.1/lifeograph.xml0000644000000000000000000000065112273216102014617 0ustar 00000000000000 Lifeograph diary Lifeograph günlüğü lifeograph-1.0.1/po/0000755000000000000000000000000012273216102012371 5ustar 00000000000000lifeograph-1.0.1/src/0000755000000000000000000000000012273216102012542 5ustar 00000000000000lifeograph-1.0.1/ui/0000755000000000000000000000000012273216102012370 5ustar 00000000000000lifeograph-1.0.1/cmake/backup.cmake0000644000000000000000000000275412273216102015312 0ustar 00000000000000# Copyright (C) 2013 Ahmet Öztürk (aoz_2@yahoo.com) # # This file is part of Lifeograph. # # Lifeograph 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. # # Lifeograph 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 Lifeograph. If not, see . include( ${CMAKE_SOURCE_DIR}/cmake/definitions.cmake ) execute_process( COMMAND stat -c %Y "${BIN_DIR}/${PACKAGE_NAME}" OUTPUT_VARIABLE MODIFIED_SRC ) set( CP_REQUIRED YES ) file( GLOB bin_files ${BIN_DIR}/lifeograph.* ) foreach( bin_file ${bin_files} ) execute_process( COMMAND stat -c %Y ${bin_file} OUTPUT_VARIABLE MODIFIED_TGT ) if( MODIFIED_TGT EQUAL MODIFIED_SRC ) set( CP_REQUIRED NO ) break() endif() endforeach() if( CP_REQUIRED ) execute_process( COMMAND date +%Y-%m-%d--%H-%M-%S OUTPUT_VARIABLE DATE_SUFFIX ) string( REGEX REPLACE \n "" DATE_SUFFIX "${DATE_SUFFIX}" ) execute_process( COMMAND cp -p "${BIN_DIR}/${PACKAGE_NAME}" "${BIN_DIR}/${PACKAGE_NAME}.${DATE_SUFFIX}" ) endif() lifeograph-1.0.1/cmake/definitions.cmake0000644000000000000000000000411312273216102016347 0ustar 00000000000000# Copyright (C) 2013 Ahmet Öztürk (aoz_2@yahoo.com) # # This file is part of Lifeograph. # # Lifeograph 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. # # Lifeograph 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 Lifeograph. If not, see . set( PACKAGE_NAME lifeograph ) set( Lifeograph_VERSION_MAJOR 1 ) set( Lifeograph_VERSION_MINOR 0 ) set( BUILD_DIR ${CMAKE_SOURCE_DIR}/build ) set( BIN_DIR ${CMAKE_SOURCE_DIR}/build/bin ) set( MO_DIR ${CMAKE_SOURCE_DIR}/build/mo ) set( LOCAL_INCL_DIR ${CMAKE_SOURCE_DIR}/build/include ) # config.h DEFINITIONS set( LOCALEDIR "${CMAKE_INSTALL_PREFIX}/share/locale" ) set( PIXMAPDIR "${CMAKE_INSTALL_PREFIX}/share/pixmaps" ) set( ICONDIR "${CMAKE_INSTALL_PREFIX}/share/${PACKAGE_NAME}/icons" ) set( UIDIR "${CMAKE_INSTALL_PREFIX}/share/${PACKAGE_NAME}/ui" ) set( DIARYDIR "${CMAKE_INSTALL_PREFIX}/share/${PACKAGE_NAME}/diaries" ) set( po_dir ${CMAKE_SOURCE_DIR}/po ) set( pot_file ${po_dir}/${PACKAGE_NAME}.pot ) set( desktop_file_in ${CMAKE_SOURCE_DIR}/${PACKAGE_NAME}.desktop.in ) set( desktop_file ${CMAKE_SOURCE_DIR}/build/${PACKAGE_NAME}.desktop ) set( SOURCE_FILES src/app_window.cpp src/dialog_export.cpp src/dialog_password.cpp src/dialog_preferences.cpp src/diary.cpp src/diarydata.cpp src/entry.cpp src/entry_parser.cpp src/helpers.cpp src/lifeograph.cpp src/main.cpp src/panel_diary.cpp src/panel_extra.cpp src/panel_main.cpp src/printing.cpp src/settings.cpp src/undo.cpp src/view_entry.cpp src/view_login.cpp src/views.cpp src/widget_chart.cpp src/widget_entrylist.cpp src/widget_tag_list.cpp src/widget_textview.cpp ) lifeograph-1.0.1/cmake/msgmerge.cmake0000644000000000000000000000214212273216102015642 0ustar 00000000000000# Copyright (C) 2013 Ahmet Öztürk (aoz_2@yahoo.com) # # This file is part of Lifeograph. # # Lifeograph 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. # # Lifeograph 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 Lifeograph. If not, see . include( ${CMAKE_SOURCE_DIR}/cmake/definitions.cmake ) file( GLOB po_files ${po_dir}/*.po ) foreach( po_file ${po_files} ) execute_process( COMMAND msgmerge -U ${po_file} ${pot_file} WORKING_DIRECTORY ${po_dir} ) endforeach() execute_process( COMMAND intltool-update -r -g ${PACKAGE_NAME} WORKING_DIRECTORY ${po_dir} ) lifeograph-1.0.1/cmake/rev_no.cmake0000644000000000000000000000306512273216102015331 0ustar 00000000000000# Copyright (C) 2013 Ahmet Öztürk (aoz_2@yahoo.com) # # This file is part of Lifeograph. # # Lifeograph 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. # # Lifeograph 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 Lifeograph. If not, see . include( ${CMAKE_SOURCE_DIR}/cmake/definitions.cmake ) if( EXISTS ${CMAKE_SOURCE_DIR}/.bzr ) if( EXISTS ${LOCAL_INCL_DIR}/rev_no.h ) file( READ ${LOCAL_INCL_DIR}/rev_no.h rev_no_content ) endif() execute_process( COMMAND bzr revno OUTPUT_VARIABLE REVISION_NO ) string( REGEX REPLACE \n "" REVISION_NO "${REVISION_NO}" ) #message( "Building revision ${REVISION_NO}" ) if( NOT ( ${rev_no_content} MATCHES "#define REVISION_NO \" r${REVISION_NO}\"" ) ) file( WRITE ${LOCAL_INCL_DIR}/rev_no.h "#define REVISION_NO \" r${REVISION_NO}\"" ) endif() endif() # BUILD TIME STAMP execute_process( COMMAND date +%Y-%m-%d--%H-%M-%S OUTPUT_VARIABLE BUILD_TIMESTAMP ) string( REGEX REPLACE \n "" BUILD_TIMESTAMP "${BUILD_TIMESTAMP}" ) file( WRITE ${LOCAL_INCL_DIR}/build_time.h "#define BUILD_TIMESTAMP \" ${BUILD_TIMESTAMP}\"" ) lifeograph-1.0.1/cmake/uninstall.cmake0000644000000000000000000000730012273216102016046 0ustar 00000000000000# Copyright (C) 2013 Ahmet Öztürk (aoz_2@yahoo.com) # # This file is part of Lifeograph. # # Lifeograph 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. # # Lifeograph 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 Lifeograph. If not, see . include( ${CMAKE_SOURCE_DIR}/cmake/definitions.cmake ) # UNINSTALL FILE FUNCTION function( UNINSTALL arg1 ) message( STATUS "Uninstalling file \"${arg1}\"") if( EXISTS "${arg1}" ) execute_process( COMMAND ${CMAKE_COMMAND} -E remove "${arg1}" OUTPUT_VARIABLE rm_out RESULT_VARIABLE rm_retval ) if( NOT ${rm_retval} EQUAL 0 ) message( FATAL_ERROR "Problem when removing \"${arg1}\"" ) endif( NOT ${rm_retval} EQUAL 0 ) else( EXISTS "${arg1}" ) message( STATUS "File \"${arg1}\" does not exist." ) endif( EXISTS "${arg1}" ) endfunction( UNINSTALL ) # UNINSTALL DIR FUNCTION function( UNINSTALL_DIR arg1 ) message( STATUS "Uninstalling directory \"${arg1}\"") if( EXISTS "${arg1}") execute_process( COMMAND ${CMAKE_COMMAND} -E remove_directory "${arg1}" OUTPUT_VARIABLE rm_out RESULT_VARIABLE rm_retval ) if( NOT ${rm_retval} EQUAL 0 ) message( FATAL_ERROR "Problem when removing \"${arg1}\"") endif( NOT ${rm_retval} EQUAL 0 ) else( EXISTS "${arg1}" ) message( STATUS "Folder \"${arg1}\" does not exist." ) endif( EXISTS "${arg1}" ) endfunction( UNINSTALL_DIR ) # FILES UNINSTALL( "${DESTDIR}/bin/${PACKAGE_NAME}" ) UNINSTALL( "${DESTDIR}/share/appdata/lifeograph.appdata.xml" ) UNINSTALL( "${DESTDIR}/share/pixmaps/lifeograph.png" ) UNINSTALL( "${DESTDIR}/share/icons/hicolor/48x48/apps/lifeograph.png" ) UNINSTALL( "${DESTDIR}/share/icons/hicolor/32x32/apps/lifeograph.png" ) UNINSTALL( "${DESTDIR}/share/icons/hicolor/24x24/apps/lifeograph.png" ) UNINSTALL( "${DESTDIR}/share/icons/hicolor/22x22/apps/lifeograph.png" ) UNINSTALL( "${DESTDIR}/share/icons/hicolor/16x16/apps/lifeograph.png" ) UNINSTALL( "${DESTDIR}/share/icons/hicolor/scalable/apps/lifeograph.svg" ) UNINSTALL_DIR( "${DESTDIR}/share/${PACKAGE_NAME}" ) # TRANSLATIONS file( GLOB po_files ${po_dir}/*.po ) foreach( po_file ${po_files} ) get_filename_component( lang ${po_file} NAME_WE ) UNINSTALL( "${DESTDIR}/share/locale/${lang}/LC_MESSAGES/${PACKAGE_NAME}.mo" ) endforeach() # XDG find_program( XDG-MIME_EXE xdg-mime ) find_program( XDG-DESKTOP-MENU_EXE xdg-desktop-menu ) find_program( XDG-ICON_RES_EXE xdg-icon-resource ) execute_process( COMMAND ${XDG-MIME_EXE} uninstall ${CMAKE_SOURCE_DIR}/lifeograph.xml ) execute_process( COMMAND ${XDG-ICON_RES_EXE} uninstall --context mimetypes --size 16 application-x-lifeographdiary ) execute_process( COMMAND ${XDG-ICON_RES_EXE} uninstall --context mimetypes --size 32 application-x-lifeographdiary ) execute_process( COMMAND ${XDG-ICON_RES_EXE} uninstall --context mimetypes --size 48 application-x-lifeographdiary ) execute_process( COMMAND ${XDG-ICON_RES_EXE} uninstall --context mimetypes --size 64 application-x-lifeographdiary ) execute_process( COMMAND ${XDG-ICON_RES_EXE} uninstall --context mimetypes --size 128 application-x-lifeographdiary ) execute_process( COMMAND ${XDG-DESKTOP-MENU_EXE} uninstall ${desktop_file} ) lifeograph-1.0.1/cmake/xdg.cmake0000644000000000000000000000406112273216102014620 0ustar 00000000000000# Copyright (C) 2013 Ahmet Öztürk (aoz_2@yahoo.com) # # This file is part of Lifeograph. # # Lifeograph 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. # # Lifeograph 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 Lifeograph. If not, see . include( ${CMAKE_SOURCE_DIR}/cmake/definitions.cmake ) find_program( XDG-MIME_EXE xdg-mime ) find_program( XDG-DESKTOP-MENU_EXE xdg-desktop-menu ) find_program( XDG-ICON_RES_EXE xdg-icon-resource ) execute_process( COMMAND ${XDG-MIME_EXE} install --novendor ${CMAKE_SOURCE_DIR}/lifeograph.xml ) execute_process( COMMAND ${XDG-ICON_RES_EXE} install --context mimetypes --size 16 ${CMAKE_SOURCE_DIR}/icons/diary-16.png application-x-lifeographdiary ) execute_process( COMMAND ${XDG-ICON_RES_EXE} install --context mimetypes --size 32 ${CMAKE_SOURCE_DIR}/icons/diary-32.png application-x-lifeographdiary ) execute_process( COMMAND ${XDG-ICON_RES_EXE} install --context mimetypes --size 48 ${CMAKE_SOURCE_DIR}/icons/diary-48.png application-x-lifeographdiary ) execute_process( COMMAND ${XDG-ICON_RES_EXE} install --context mimetypes --size 64 ${CMAKE_SOURCE_DIR}/icons/diary-64.png application-x-lifeographdiary ) execute_process( COMMAND ${XDG-ICON_RES_EXE} install --context mimetypes --size 128 ${CMAKE_SOURCE_DIR}/icons/diary-128.png application-x-lifeographdiary ) execute_process( COMMAND ${XDG-DESKTOP-MENU_EXE} install --novendor ${desktop_file} ) execute_process( COMMAND ${XDG-MIME_EXE} default ${desktop_file} application/x-lifeographdiary ) lifeograph-1.0.1/diaries/Lifeograph Manual0000644000000000000000000006561212273216102016606 0ustar 00000000000000LIFEOGRAPHDB V 110 E no O -d l en_US S 10009 L 10009 ID10016 t stub ID10018 oe2147485696 Advanced ID10011 oe2147484672 Intermediate ID10010 oe2147483648 Basics ID10002 CcDefault ID10032 E 2147485702 Dr1383064691 Dh1391266386 P Diary File Version Support P P Current diary file version is 110. P P Below is a list showing which diary file versions can be opened and saved by a particular Lifeograph version. P P Lifeograph version 0.11.0 - 1.0.1 P • *Opens:* 56-110 P • *Saves:* 110 P P 0.7.4 - 0.10.0 P • *Opens:* 56-74 P • *Saves:* 74 P P 0.7.3 P • *Opens:* 56,73 P • *Saves:* 73 P P 0.7.1, 0.7.2 P • *Opens:* 56 P • *Saves:* 56 P P 0.7.0 P • *Opens:* 51-56 P • *Saves:* 56 P P 0.5.6 - 0.6.4 P • *Opens:* 37-56 P • *Saves:* 56 ID10034 E 2147485701 Dr1391259680 Dh1391261226 P Configuration File P P The default path for the Lifeograph configuration file is *XDG_CONFIG_HOME/lifeograph/lifeo.conf* where *XDG_CONFIG_HOME* is equal to *~/.config* on most systems. P P Lifeograph can be forced to use another configuration file than the default by setting the *LIFEOGRAPH_CONFIG_FILE* system variable. P P e.g. if started with the following commandline Lifeograph will use the alternative config file specified (if the config file does not exist, it will be created): P P $ LIFEOGRAPH_CONFIG_FILE=/home/user/.lifeo.conf2 lifeograph ID10029 E 2147485700 Dr1359488053 Dh1359489009 T stub P Encryption P P Lifeograph uses via for encrypted diaries. P P This is real encryption. So, there is no known way of recovering the data in an encrypted diary when its password is lost -except for trial and error. ID10017 E 2147485699 Dr1337552255 Dh1354357524 P Hidden Options P P Diary file extension P To override the default value (.diary) add a line to lifeo.conf starting with E. P e.g. to change to .lifeograph (Please note that any custom extension should begin with a dot): P P E .lifeograph P P and to disable automatic appendage of an extension use just a dot: P P E . ID10020 E 2147485698 Dr1341263079 Dh1349123917 P Command-line Options P P SYNOPSIS P lifeograph [--force-welcome] [--open, -o _DIARY_] [--read-only] P P OPTIONS P *--open*, *-o* _DIARY_ P Sets the diary file to be opened. If the diary is encrypted, Lifeograph will start with a password prompt. P P *--read-only*, *-r* P Open the command-line supplied file in read-only mode if there is one. P P *--ignore-locks* P Enables opening locked diary files. Beware that if a diary file is locked it is probably being edited by another instance of Lifeograph or the last session with it did not finish correctly. In either case the lock file may contain unsaved changes. P P *--force-welcome* P Forces program to show the welcome screen. Normally welcome screen is only shown on the first run of Lifeograph. ID10023 E 2147485697 Dr1341266304 Dh1391260730 P Backup Files P P Lifeograph saves two backup files. Both are saved in the same directory as the diary file. Their names are *.~LOCK~* and *.~previousversion~*. P The first one is saved twice a minute during an editing session and contains all unsaved changes up to that time. It is, however, deleted after logging out successfully. P The second one is saved at log-out and is simply a backup of the diary before the last editing session. P P Recovery after crashes P *.~LOCK~* is useful to recover unsaved changes after crashes. When, due to a crash or any other reason, a Lifeograph session ends improperly the .~LOCK~ file will not be removed. In that case, Lifeograph will refuse to open the original diary again complaining that it is locked. P If the presence of the lock is due to quitting improperly (rather than the file's being open in another instance of Lifeograph) you can rename the lock file and open it with Lifeograph to recover the unsaved changes. If you are sure that you don't want to restore the changes you can simply delete the lock file and open the original diary. P P *.~previousversion~* can be used to revert changes made in the last editing session. ID10033 E 2147484683 Dr1390645490 Dh1390647359 P Graphs P P Lifeograph provides simple statistical graphics to visualize the distribution of entries to months for all entries in a diary or for entries associated with a single tag or any tag in a tag category. These can be found at the bottom of tag, tag category and diary views. P P To be able to create a visual, entries related to a graph need to spread over two or more months or *INSUFFICIENT DATA* message will be displayed. P P Scrolling P If there are many months between the earliest and latest entry related to a particular graph, the graph widget may not have enough horizontal space to display the whole graph line at once. Then, it will add a scrollbar to the bottom with the complete graph line on it. This can be used to navigate along the time frame associated with the graph like a regular scrollbar. P It is also possible to scroll using the mouse wheel. P ID10031 E 2147484682 Dr1377870243 Dh1386428715 P Read-Only Mode P P Lifeograph opens diaries in Read-only mode when P • the user does not have write permissions on the diary file, P • the file is a system diary, such as Lifeograph Manual, or P • the user choses so, usually for preventing accidental changes on the diary. P P Differences between Read and Edit modes P In read-only mode, P • editing functionality elements are hidden, resulting in a much simple user interface, P • links are activated without pressing Ctrl and selected with pressing it, P • markup characters are always hidden, P • spell checking is always disabled. P P P P P P ID10026 E 2147484681 Dr1349541098 Dh1391259606 P Settings P P rel://images/settings.gif P P Logging out when idle P Lifeograph can save the current diary and log out when a configurable time has passed without any user interaction. This only happens when the opened diary is encrypted. P P Formatting toolbar P Formatting toolbar (which is the one with bold, italic, etc... buttons) can be hidden to reclaim some more screen real estate. Note that, all the functionality in the toolbar is also accessible via . ID10019 E 2147484680 Dr1349123755 Dh1391259636 P Printing P P Lifeograph specific options P Lifeograph specific options can be found on the *Lifeograph* tab of the print dialog: P P rel://images/printing.gif P P What to print? P It is possible to print the current entry, filtered entries (if there is an active filter) or the entire diary. P P Text options P The default font for the print out is configurable here. Optionally it is also possible to print each entry in its theme's font. P The last option is for justifying the text on the page. Normally text is left aligned. ID10028 E 2147484679 Dr1354958522 Dh1386428595 T stub P Importing P P It is possible to merge diaries by importing entries, tags, and themes from another diary. P P Import dialog can be opened from the gear menu of the . P P It is also possible to add a certain tag to all imported entries in order to be able to differentiate them after they are merged with other entries in the target diary. ID10025 E 2147484678 Dr1341429541 Dh1377869660 P Exporting (Saving a Copy of) the Diary P P It is possible to save a complete or partial copy of the current diary as either another diary file or as a plain text file. P P Export dialog can be opened from the gear menu of the . P P Lifeograph will ask for the password before exporting an encrypted diary. P P Exporting to plain text file P Plain text files can be used as a future-proof back-up format or for sharing diaries with other people who do not use Lifeograph. P P Exporting to a Lifeograph diary file P This can be used for saving a copy of the current diary either as a whole or partially as per the active entry filters. Encryption is optional and a different password can be selected than that of the original file. P P Exporting to PDF P Although Lifeograph does not support exporting to PDF directly, printing to file facility can be used for that very purpose. ID10027 E 2147484677 Dr1354449009 Dh1354450412 T stub P Spell Checking P P Lifeograph supports spell-checking utilizing _Enchant_ library. P P To enable spell checking go to and select a language from the *Spell Checking* combo box. P P If needed, spell checking preference set for the diary can be overridden for any particular entry. To do this, open the entry and right-click in the text editor. Select the desired option from the *Spell Checking* sub-menu. P Diary Default option removes the override from the entry. ID10015 E 2147484676 Dr1330897444 Dh1386424035 P Lists in Entries P P If you indent the line, either by Alt-I or , you can create different kinds of lists depending on the first character(s) you type: P P Bulleted lists by typing '*'. P Enumerated lists by typing a number followed by '.', ')', or '-'. P Checklists by typing '[]'. P P It is also possible to convert the current line (or multiple lines at once when text selection covers multiple lines) to bullet or check list items by using the dedicated buttons in the Entry formatting toolbar. P P Bulleted lists P P • Item 1 P • Item 2 P P Checklists P Lifeograph has basic checklist support. Each checklist item may have one of the three possible states: P P ☐ not finished P ☑ finished P ☒ canceled P P State of an item can be changed by clicking on the check box of it. Highlight and strike-through styles are applied automatically for finished and canceled items, respectively. P P Numbered lists P Lifeograph has very basic support for numbered lists in that it automatically inserts the next number to the beginning of a new line if previous line is a valid numbered list line i.e. starts with a sequence where separator is " *)* " " *-* " or " *.* " . P P 1- item 1 P 2- item 2 P 3- item 3 P ID10022 E 2147484675 Dr1341265720 Dh1386423865 P Text Formatting P P Heading (Entry title) P First paragraph of an entry (i. e. any text before the first line break) is considered the title rendered in heading style. Other formats (such as highlight) cannot be used within entry titles nor are comments. Color of heading is defined by associated theme. P P Subheading P Paragraphs starting with a single space (" ") are styled as subheading. Other formats and comments can be used normally in subheadings however using bold will make no difference as subheading style is already bold. Color of subheading comes from associated theme. P P Markup chars P Lifeograph has a text formatting system reminiscent of wiki software i.e. certain characters are used to denote different text styles. These are called _markup characters_. P P *bold*: asterisk * P P _italic_: underscore _ P P =strike-through=: equal sign = P P #Highlight#: hash # P P Important points about markup chars P • Markup characters are normally hidden. They are only shown when input cursor is placed adjacent to their location. P • Markup characters should be inserted at the beginning and end of the part of the text you want to apply formatting P • Opening markup characters must came after a *separator* but mustn't be followed by one. (Separator is a character to separate words such as space or tab.) P • Closing markup characters mustn't come after a separator P • Highlight color is defined by entry theme. ID10014 E 2147484674 Dr1330895860 Dh1354956776 T stub P Filtering and Replacing P P Entries can be filtered by P • having a tag, P • coming before or after a particular date, P • containing some text, and P • being favorite. P P These filters can be combined to achieve a finer result. P Additionally any single entry can be hidden/filtered out to further tweak the list of displayed entries according to any purpose. P P Use cases of filtering P Hiding some entries by means of filters has two main uses: finding things looked for without browsing too much and limiting effects of some operations (such as exporting and ) to a subset of entries in the diary. P P A third use related to filtering by text is replacing certain text blocks with something else. ID10012 E 2147484673 Dr1329596926 Dh1377870967 P Links P P Links can be given to many types of objects, such as dates, web sites, email addresses, and diary elements. P P Links can be followed by holding Ctrl key when clicking on them. This behavior is reversed in . P P Basically there are two types of links: automatic and manual. P P Automatic links P Certain expressions are recognized and automatically converted into links such as P • urls starting with P • http:// P • https:// P • ftp:// P • file:// P • e-mail addresses with @ sign P • dates in YYYY.MM.DD format (Note that besides dots, slashes and dashes can also be used as separators in dates) P P e.g.: P http://launchpad.net/lifeograph P e-mail@address.com P 2012.12.01, 2012/12/01, 2012-12-01 P P Relative links P For file links, rather than providing a full path, it is also possible to enter link paths relative to the location of the diary. Such links are formed by using a special prefix: P rel:// P P e.g.: P rel://example.diary P P Manual links P Besides special tokens, any type of text can be converted into a link by using a special syntax: P P P P where target is any type of link that is recognized by automatic link mechanism explained above or id of an entry. Please note that target and label are separated by a single *tab* character. P P e.g.: P <2012.03.31 his birth day> P . <2012.03.31 his birth day> P P P . P P Second example above shows the usage of an entry ID as a target. Every entry in a diary has a unique ID that never changes. However, users are not supposed to know entry IDs. The normal way of creating such links is dropping entries from list into the entry text. ID10008 E 2147483659 Dr1315862697 Dh1360177056 P Keyboard Shortcuts P P General P • *Log out:* Ctrl + Escape P • *Focus filtering control:* Ctrl + F P P Text Editing P • *Undo:* Ctrl + Z P • *Redo:* Ctrl + Shift + Z P P • *Bold:* #Ctrl + B# P • *Highlight:* #Ctrl + H# P • *Italic:* #Ctrl + I# P • *Strike-through:* #Ctrl + S# P P • *Toggle visibility of comments:* #Alt + C# P • *Indent:* #Alt + I# P • *Unindent:* #Alt + U# P • *Insert empty line above:* #Alt + L# P • *Erase empty line above:* #Alt + Shift + L# P • *Move current paragraph up:* #Alt + Up# P • *Move current paragraph down:* #Alt + Down# P P • *Insert current date and time:* #Alt + T# P P • *Focus tag widget:* #Ctrl + T# P P #Highlighted# shortcuts can only be used when focus is on entry text. P P Navigation P • *Go to the previous entry in the list:* Ctrl + Page Down P • *Go to the next entry in the list:* Ctrl + Page Up P • *Go to the previous entry in browsing history:* Alt + Left P • *Go to today:* Ctrl + D P • *Jump to current entry in the list:* Ctrl + J ID10006 E 2147483658 Dr1315863045 Dh1386422735 T stub P Themes P P Font and colors used in entries can be customized via so called themes. Multiple themes can be saved in a diary file and each can be assigned to different entries. P P System theme: [ - 0 - ] P Every diary has a system theme which inherits its features mostly from operating system theme and cannot be edited by the user. P P Default theme P The default theme in a diary is used in entries where a specific theme is not set. This theme is displayed with a check-mark icon in the theme list. P P Working with themes P New themes are created by duplicating existing ones. A theme is assigned to the current entry by dropping it from the theme list onto the entry text. ID10013 E 2147483657 Dr1330895758 Dh1386422451 T stub P Topics P P Topics are like chapters but they are not time based thus they are used to group time independent entries. P P To create a topic, click the *New* button in the and select _Topic_ from the drop down list. P P It is possible to drop entries to topics to move them from chapters to topics or between different topics. ID10007 E 2147483656 Dr1315862841 Dh1386422303 P Chapters P P Chapter system is a means of organizing entries according to phases in our lives. This will make it a lot more convenient to manage a diary with hundreds of entries. P P Creating chapters P • Select the day the Chapter will begin in the calendar P • From the *New* button in the main tool bar select *Chapter* P P Chapter categories P More than one set of chapters can be created within a diary file for grouping entries according to different schemes or different aspects of life. These chapter sets are called chapter categories. P P e.g. one can create a chapter set called _Jobs_ with chapters for companies she has worked for and another one called _Places_ that contains chapters for cities she has lived in. P P Working with chapter categories P Chapter categories are managed in : P P rel://images/chapter_ctg.gif P P To create a new chapter category, click the down arrow beside the category rename and select *Create New...* from the menu. P P To dismiss a category, select one from the list and click the dismiss button. P P To rename a category, select one from the list. Type a new (unused by any other category) name. The dismiss button will turn into a apply button with a check mark icon. Click on it to apply the new name. ID10005 E 2147483655 Dr1315863054 Dh1386420946 T stub P Tags P P Tags are user defined attributes in a diary that entires can be associated with. There is no limit for the number tags a diary can hold. P P Tags can be added to the current entry by dropping them onto the entry text or by typing their name into the *Tag name* field which is opened by clicking *Add Tag* in the entry's tag list or by using the shortcut Ctrl + T. Entering only part of the tag name is sufficient as Lifeograph will suggest tags containing the entered text portion for auto-completion. P P The entries other than the current one can be tagged by dropping the tag onto the entry items in the entry list. P P Creating tags P Tags are crated by typing a unique tag name in the *Tag name* field below the entry view and clicking the *Create Tag* button that will show up when the entered text is not a name used before. Newly created tag will also be associated with the current entry. P P Tag categories P Tags can optionally be grouped into so called categories to help users manage the tag list when the number of the tags grows too big. P P To add a tag to an existing or new category: P • Click the tag in the tag list to open its view. P • From *Category* combo-box select *Create New...* ID10003 E 2147483654 Dr1315863316 Dh1386420753 P Entries P P Entries constitute the most essential part of a diary. P P Entries can be time based or time independent. Time based entries are for recording notes related to a certain date like events happened on that day. They are normally sorted by date. Up to 1024 entries can be added to a particular date. P P Time independent entries are for general notes, or any other idea not associated with a date. Time independent entries are grouped into ordinal chapters usually called _topics_. P P Creating entries P Entries are created by using the _New_ button in the main toolbar. The type of the new entry will depend on the current entry or whether a day is selected on the calendar. P P Time based entries can also be created by double clicking a day in the calendar. P Time independent entries can also be added to topics by using the dedicated button in the topic view. P P It is also possible to create a new entry on the current date by using *Today* button. P P Entry list P Entries in the list are sorted by date by default. Order is from latest to earliest. P It is also possible to have entries sorted P • by size, i.e. number of characters in them (from longest to shortest) P • and by last save time (from newest to oldest). P P Text formatting P First paragraph of an entry is formatted as heading. P P Paragraphs starting with a single space character (" ") are formatted as subheading. P P Any text between P • two asterisks ("*") are formatted as bold; P e.g. Look at the *emphasized part* of the text! P • two underscores ("_") are formatted as italic; P e.g. Why do you _lean_ forward? P • two equals signs ("=") are formatted as strike-through. P e.g. =canceled out= P P Refer to for a complete guide of text formatting. P P Comments P There is a special markup type to denote comments in a text. Marking up comments this way has the benefit of toggling their visibility when needed. e.g. before taking a print out. P P [[this is a comment]] P P Disabling markups in a paragraph P Paragraphs starting with a dot (.) followed by a tab are ignored by the markup system: P P . *no bold* _no italic_ [[no comment]] P P Links P It is possible to create links to other entries, dates, files, web sites, etc... in an entry. See for more info. P P Images P Links to image files are automatically replaced by the thumbnail of the target image under following conditions: P • link should be start with file:// or rel:// P • it should be placed in a dedicated paragraph i.e. there should be no other character in the paragraph other than link text, including space characters. P P Please note that image files are not saved within diary files. Although they appear as images inside the entries, they are still just links to external files. P ID10021 E 2147483653 Dr1349518893 Dh1359487998 T stub P Diary Elements P P Diary elements are data blocks that holds different data types in a diary. P Types of diary elements are P • Entry, P • Tag, P • Tag Category, P • Chapter, P • Chapter Category, P • Topic, P • and Theme. P P Graphical interface P Diary elements listed in left and right panels have its own _view_ for editing and management. (central panel) displays the view of the currently selected element. ID10004 E 2147483652 Dr1315863197 Dh1375515766 P Diaries P P Lifeograph supports working with multiple diary files. It remembers previously opened diaries and offers a list of them at the startup for easy access. P P Creating a new diary P Click *Create a New Diary...* button on the top of the diary list. P P Saving P Diaries are saved automatically on log out. Previous version of the diary is also kept as a backup file. For more information about backups see . P Empty entries are ignored when saving. P P Diary view P Diary view is opened by clicking the topmost item in the . P It allows the user P • to add encryption to the diary P • to change the password if the diary is already encrypted P • to set spell checking language, P • exporting and importing P and some more. P P Encryption P There are two types of diaries: plain and encrypted. P To encrypt a diary, all that is needed to be done is adding a password to it. P Lifeograph offers to add a password in the file dialog while creating a new diary. It is also possible to encrypt a plain diary afterwards via the *Encrypt..* item in the gear menu of the diary view. P Encryption, once added, cannot be removed from a diary file. However, an unencrypted copy can be created via . P P Extension of diary files P Default extension for diaries is *.diary* which will be appended automatically to the end of the name. This behavior, though, can be overridden via a