Delicious Bookmark on Delicious

Changeset 99

Show
Ignore:
Timestamp:
10/30/07 07:48:28 (5 years ago)
Author:
uncle_fungus
Message:

Updated polish translation to 2.3.1pre1, updated buildenv to 2.3.1

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • trunk/ChangeLog

    r95 r99  
    11FahMon: The Folding@home client monitoring program 
    22 
    3 v2.3.1 
     3v2.3.1 (30/10/07) 
    44 
    55    General 
    …… 
    3030      controlled by the old "Display ETA as" option which has been renamed to 
    3131      "Display dates as" 
    32     * Added menu item to cycle through ETA display display styles as requested. 
     32    * Added menu item to cycle through ETA display styles as requested. 
    3333    * Updated about dialog to use new website 
    3434    * HTTP requests from FahMon now send a User-Agent string (i.e. FahMon/2.3.1) 
    …… 
    3737    * Added Brazilian Portuguese translation 
    3838    * Added Spanish translation 
     39    * New application icon, including Vista-required dimensions 
    3940 
    4041v2.3.0 (10/09/07) 

  • trunk/FahMon.nsi

    r94 r99  
    139139 
    140140SectionEnd 
    141 Section /o "Polish" secLangpl 
    142  
    143   SetOutPath "$INSTDIR\lang\pl" 
    144   File "lang\pl\pl.po" 
    145   File "lang\pl\fahmon.mo" 
     141Section /o "Polish" secLangplPL 
     142 
     143  SetOutPath "$INSTDIR\lang\pl_PL" 
     144  File "lang\pl_PL\pl_PL.po" 
     145  File "lang\pl_PL\fahmon.mo" 
    146146 
    147147SectionEnd 
    …… 
    193193  LangString DESC_SecLangnlNL ${LANG_ENGLISH} "Install Dutch translation" 
    194194  LangString DESC_SecLangfrFR ${LANG_ENGLISH} "Install French translation" 
    195   LangString DESC_SecLangpl ${LANG_ENGLISH} "Install Polish translation" 
     195  LangString DESC_SecLangplPL ${LANG_ENGLISH} "Install Polish translation" 
    196196  LangString DESC_SecLangptBR ${LANG_ENGLISH} "Install Portuguese (Brazil) translation" 
    197197  LangString DESC_SecLangptPT ${LANG_ENGLISH} "Install Portuguese (Portugal) translation" 
    …… 
    208208    !insertmacro MUI_DESCRIPTION_TEXT ${SecLangnlNL} $(DESC_SecLangnlNL) 
    209209    !insertmacro MUI_DESCRIPTION_TEXT ${SecLangfrFR} $(DESC_SecLangfrFR) 
    210     !insertmacro MUI_DESCRIPTION_TEXT ${SecLangpl} $(DESC_SecLangpl) 
     210    !insertmacro MUI_DESCRIPTION_TEXT ${SecLangplPL} $(DESC_SecLangplPL) 
    211211    !insertmacro MUI_DESCRIPTION_TEXT ${SecLangptBR} $(DESC_SecLangptBR) 
    212212    !insertmacro MUI_DESCRIPTION_TEXT ${SecLangptPT} $(DESC_SecLangptPT) 

  • trunk/NEWS

    r38 r99  
    66 
    77Please send FahMon bug reports to the.uncle.fungus@gmail.com. 
     8 
     9Version 2.3.1 
     10 
     11* The most obvious new change to version 2.3.1 is the new "WebApp" module. This 
     12  enables you to export the monitoring information provided by FahMon to a web- 
     13  page, or to a file for viewing over a secure shell. 
     14* Drag and drop capability has been added to the client-list too, so you just 
     15  drag and drop your FAH folder onto the list, and the add client dialog appears 
     16  with the location field already filled in. This works for multiple clients 
     17  too, you just get presented with multiple dialogs in succession. 
     18* An update notification system has been added, which although very basic, will 
     19  alert you that a new version of FahMon has been released. You can either check 
     20  manually from the menu item, or allow FahMon to check every time it starts. 
    821 
    922Version 2.3.0 

  • trunk/README

    r45 r99  
    1717The following instructions do NOT apply to the precompiled Windows binaries. 
    1818 
    19 BUILD 
    20 ===== 
     19Compiling FahMon for Windows 
     20============================ 
     21Please see README.win32.txt 
     22 
     23Compiling, Installing and Running FahMon for Linux 
     24================================================== 
    2125For the build requirements of FahMon please see the REQUIRES file. 
    22 For the generic building and installation instructions please see the INSTALL 
    23 file. 
    2426 
    25 Building for Linux 
    26 ================== 
    27 FahMon uses the standard ./configure; make method for software building. Under 
     27FahMon uses the familiar ./configure; make method for software building. Under 
    2828normal circumstances these are the only commands you will need to run. Configure 
    2929will detect and setup the necessary software and files, and make will compile 
    3030the software for you. 
    3131 
    32 Building for MS Windows 
    33 ==================== 
    34 Building for MS Windows is not fully supported as the build environment can be 
    35 quite difficult to set up. However, the generic instructions are as follows: 
    36 * Compile the Unicode Release of wxWidgets, making sure that you compile all the 
    37 libraries statically (i.e. in the "runtime library" configuration, set it to be 
    38 "Multi Threaded (/MT)"). 
    39 * Open the FahMon solution file and configure the additional include directories 
    40 to point to the wxwidgets folders, and edit the linker files to use the correct 
    41 versions of the libraries. 
    42 * Make sure that all the source files are actually being loaded by the solution 
    43 file (the given solution file may expect the files to be in a different 
    44 location) 
    45 * Compile FahMon 
     32Full installation instructions: 
    4633 
    47 INSTALLING AND RUNNING 
    48 ====================== 
    49 Under Linux, you can simply run "make install" (either as root or with sudo) 
    50 which will install all the necessary files to their correct locations. To run 
    51 FahMon, either run "fahmon" from a shell (it will work from anywhere in the 
    52 system, no more need for shell scripts), or launch it from your Desktop 
     34 cd <fahmon source folder> 
     35 ./configure 
     36 make 
     37 sudo make install 
     38 
     39Depending on your Linux distribution, you may not have (or use) sudo. In which 
     40case you need to login as root with `su`, run `make install`, then `exit` 
     41To run FahMon, either run "fahmon" from a shell (it will work from anywhere in 
     42the system, no more need for shell scripts), or launch it from your Desktop 
    5343Environment's Applications menu (if supported). You can add a shortcut item 
    5444manually if your DE is not supported. 
    55  
    56 In MS Windows, make a new folder and copy 'images', 'lang' and fahmon.exe into 
    57 it. The 
    58 images and lang folders MUST be in the same folder as fahmon.exe. After that you 
    59 can move 
    60 the folder to anywhere on your system and launch it directly or create your own 
    61 shortcut to it. 
    6245 
    6346TRANSLATIONS 
    …… 
    6851Editing existing translations 
    6952============================= 
    70 To edit existing translations, you can open the relevant .po file in your gettext catalog editor (see REQUIRES) and start modifying the strings. On Linux, these can be found in the po directory of the installation source, on MS Windows, these can be found in the lang folder. Once you are happy with the translations you have edited, you need to install them. 
     53To edit existing translations, you can open the relevant .po file in your 
     54gettext catalog editor (see REQUIRES) and start modifying the strings. On Linux, 
     55these can be found in the po directory of the installation source, on MS 
     56Windows, these can be found in the lang folder. Once you are happy with the 
     57translations you have edited, you need to install them. 
    7158 
    72 To install an edited translation on Linux, simply run "make update-gmo" then "make install" (as root or sudo). This will compile the translation to a binary file and install it into the relevant location. 
     59To install an edited translation on Linux, simply run "make update-gmo" then 
     60"make install" (as root or sudo). This will compile the translation to a binary 
     61file and install it into the relevant location. 
    7362 
    74 To install the edited transltaion on MS Windows, you need to get you gettext catalog editor to save a .mo file (poEdit wil do this). Save the file as fahmon.mo into the relevant folder under the "lang" folder. 
     63To install the edited transltaion on MS Windows, you need to get you gettext 
     64catalog editor to save a .mo file (poEdit wil do this). Save the file as 
     65fahmon.mo into the relevant folder under the "lang" folder. 
    7566 
    7667Restart FahMon and your new translations should appear. 
    …… 
    8071Make sure you have read the REQUIRES file. 
    8172 
    82 Make sure you know the language code for your new translation (combine the two letter language code from ISO 639-1 with the two letter country code from ISO 3166. See the existing translations for examples). 
     73Make sure you know the language code for your new translation (combine the two 
     74letter language code from ISO 639-1 with the two letter country code from ISO 
     753166. See the existing translations for examples). 
    8376 
    84 On Linux, copy fahmon.pot in the po folder, to 'your_translation_name'.po and start editing. After saving your translation, open up configure.ac in the source root directory, and navigate down to "ALL_LINGUAS" and add your new translation to the list. 
    85 Run ./reconf; ./configure; make update-gmo; make install to add your new translation. (This should not force a recompile of fahmon itself, unless you passed different options to configure). 
     77On Linux, copy fahmon.pot in the po folder, to 'your_translation_name'.po and 
     78start editing. After saving your translation, open up configure.ac in the source 
     79root directory, and navigate down to "ALL_LINGUAS" and add your new translation 
     80to the list. 
     81Run ./reconf; ./configure; make update-gmo; make install to add your new 
     82translation. (This should not force a recompile of fahmon itself, unless you 
     83passed different options to configure). 
    8684 
    87 On Windows, make a folder under 'lang' with the name of your translation and copy fahmon.pot into it. Rename this to a .po file and start editing it. Once finished, save the .mo file as fahmon.mo and restart FahMon. 
     85On Windows, make a folder under 'lang' with the name of your translation and 
     86copy fahmon.pot into it. Rename this to a .po file and start editing it. Once 
     87finished, save the .mo file as fahmon.mo and restart FahMon. 
    8888 
    89 Once you've created translations, please email the mo files to translations@fahinfo.org 
     89Once you've created translations, please email the mo files to 
     90translations@fahinfo.org 

  • trunk/README.in

    r36 r99  
    1717The following instructions do NOT apply to the precompiled Windows binaries. 
    1818 
    19 BUILD 
    20 ===== 
     19Compiling FahMon for Windows 
     20============================ 
     21Please see README.win32.txt 
     22 
     23Compiling, Installing and Running FahMon for Linux 
     24================================================== 
    2125For the build requirements of FahMon please see the REQUIRES file. 
    22 For the generic building and installation instructions please see the INSTALL 
    23 file. 
    2426 
    25 Building for Linux 
    26 ================== 
    27 FahMon uses the standard ./configure; make method for software building. Under 
     27FahMon uses the familiar ./configure; make method for software building. Under 
    2828normal circumstances these are the only commands you will need to run. Configure 
    2929will detect and setup the necessary software and files, and make will compile 
    3030the software for you. 
    3131 
    32 Building for MS Windows 
    33 ==================== 
    34 Building for MS Windows is not fully supported as the build environment can be 
    35 quite difficult to set up. However, the generic instructions are as follows: 
    36 * Compile the Unicode Release of wxWidgets, making sure that you compile all the 
    37 libraries statically (i.e. in the "runtime library" configuration, set it to be 
    38 "Multi Threaded (/MT)"). 
    39 * Open the FahMon solution file and configure the additional include directories 
    40 to point to the wxwidgets folders, and edit the linker files to use the correct 
    41 versions of the libraries. 
    42 * Make sure that all the source files are actually being loaded by the solution 
    43 file (the given solution file may expect the files to be in a different 
    44 location) 
    45 * Compile FahMon 
     32Full installation instructions: 
    4633 
    47 INSTALLING AND RUNNING 
    48 ====================== 
    49 Under Linux, you can simply run "make install" (either as root or with sudo) 
    50 which will install all the necessary files to their correct locations. To run 
    51 FahMon, either run "fahmon" from a shell (it will work from anywhere in the 
    52 system, no more need for shell scripts), or launch it from your Desktop 
     34 cd <fahmon source folder> 
     35 ./configure 
     36 make 
     37 sudo make install 
     38 
     39Depending on your Linux distribution, you may not have (or use) sudo. In which 
     40case you need to login as root with `su`, run `make install`, then `exit` 
     41To run FahMon, either run "fahmon" from a shell (it will work from anywhere in 
     42the system, no more need for shell scripts), or launch it from your Desktop 
    5343Environment's Applications menu (if supported). You can add a shortcut item 
    5444manually if your DE is not supported. 
    55  
    56 In MS Windows, make a new folder and copy 'images', 'lang' and fahmon.exe into 
    57 it. The 
    58 images and lang folders MUST be in the same folder as fahmon.exe. After that you 
    59 can move 
    60 the folder to anywhere on your system and launch it directly or create your own 
    61 shortcut to it. 
    6245 
    6346TRANSLATIONS 
    …… 
    6851Editing existing translations 
    6952============================= 
    70 To edit existing translations, you can open the relevant .po file in your gettext catalog editor (see REQUIRES) and start modifying the strings. On Linux, these can be found in the po directory of the installation source, on MS Windows, these can be found in the lang folder. Once you are happy with the translations you have edited, you need to install them. 
     53To edit existing translations, you can open the relevant .po file in your 
     54gettext catalog editor (see REQUIRES) and start modifying the strings. On Linux, 
     55these can be found in the po directory of the installation source, on MS 
     56Windows, these can be found in the lang folder. Once you are happy with the 
     57translations you have edited, you need to install them. 
    7158 
    72 To install an edited translation on Linux, simply run "make update-gmo" then "make install" (as root or sudo). This will compile the translation to a binary file and install it into the relevant location. 
     59To install an edited translation on Linux, simply run "make update-gmo" then 
     60"make install" (as root or sudo). This will compile the translation to a binary 
     61file and install it into the relevant location. 
    7362 
    74 To install the edited transltaion on MS Windows, you need to get you gettext catalog editor to save a .mo file (poEdit wil do this). Save the file as fahmon.mo into the relevant folder under the "lang" folder. 
     63To install the edited transltaion on MS Windows, you need to get you gettext 
     64catalog editor to save a .mo file (poEdit wil do this). Save the file as 
     65fahmon.mo into the relevant folder under the "lang" folder. 
    7566 
    7667Restart FahMon and your new translations should appear. 
    …… 
    8071Make sure you have read the REQUIRES file. 
    8172 
    82 Make sure you know the language code for your new translation (combine the two letter language code from ISO 639-1 with the two letter country code from ISO 3166. See the existing translations for examples). 
     73Make sure you know the language code for your new translation (combine the two 
     74letter language code from ISO 639-1 with the two letter country code from ISO 
     753166. See the existing translations for examples). 
    8376 
    84 On Linux, copy fahmon.pot in the po folder, to 'your_translation_name'.po and start editing. After saving your translation, open up configure.ac in the source root directory, and navigate down to "ALL_LINGUAS" and add your new translation to the list. 
    85 Run ./reconf; ./configure; make update-gmo; make install to add your new translation. (This should not force a recompile of fahmon itself, unless you passed different options to configure). 
     77On Linux, copy fahmon.pot in the po folder, to 'your_translation_name'.po and 
     78start editing. After saving your translation, open up configure.ac in the source 
     79root directory, and navigate down to "ALL_LINGUAS" and add your new translation 
     80to the list. 
     81Run ./reconf; ./configure; make update-gmo; make install to add your new 
     82translation. (This should not force a recompile of fahmon itself, unless you 
     83passed different options to configure). 
    8684 
    87 On Windows, make a folder under 'lang' with the name of your translation and copy fahmon.pot into it. Rename this to a .po file and start editing it. Once finished, save the .mo file as fahmon.mo and restart FahMon. 
     85On Windows, make a folder under 'lang' with the name of your translation and 
     86copy fahmon.pot into it. Rename this to a .po file and start editing it. Once 
     87finished, save the .mo file as fahmon.mo and restart FahMon. 
    8888 
    89 Once you've created translations, please email the mo files to translations@fahinfo.org 
     89Once you've created translations, please email the mo files to 
     90translations@fahinfo.org 

  • trunk/configure

    r94 r99  
    11#! /bin/sh 
    22# Guess values for system-dependent variables and create Makefiles. 
    3 # Generated by GNU Autoconf 2.61 for FahMon 2.3.1pre. 
     3# Generated by GNU Autoconf 2.61 for FahMon 2.3.1. 
    44# 
    55# Report bugs to <Andrew Schofield the.uncle.fungus@gmail.com>. 
    …… 
    575575PACKAGE_NAME='FahMon' 
    576576PACKAGE_TARNAME='FahMon' 
    577 PACKAGE_VERSION='2.3.1pre' 
    578 PACKAGE_STRING='FahMon 2.3.1pre' 
     577PACKAGE_VERSION='2.3.1' 
     578PACKAGE_STRING='FahMon 2.3.1' 
    579579PACKAGE_BUGREPORT='Andrew Schofield the.uncle.fungus@gmail.com' 
    580580 
    …… 
    12101210  # This message is too long to be a string in the A/UX 3.1 sh. 
    12111211  cat <<_ACEOF 
    1212 \`configure' configures FahMon 2.3.1pre to adapt to many kinds of systems. 
     1212\`configure' configures FahMon 2.3.1 to adapt to many kinds of systems. 
    12131213 
    12141214Usage: $0 [OPTION]... [VAR=VALUE]... 
    …… 
    12801280if test -n "$ac_init_help"; then 
    12811281  case $ac_init_help in 
    1282      short | recursive ) echo "Configuration of FahMon 2.3.1pre:";; 
     1282     short | recursive ) echo "Configuration of FahMon 2.3.1:";; 
    12831283   esac 
    12841284  cat <<\_ACEOF 
    …… 
    13811381if $ac_init_version; then 
    13821382  cat <<\_ACEOF 
    1383 FahMon configure 2.3.1pre 
     1383FahMon configure 2.3.1 
    13841384generated by GNU Autoconf 2.61 
    13851385 
    …… 
    13951395running configure, to aid debugging if configure makes a mistake. 
    13961396 
    1397 It was created by FahMon $as_me 2.3.1pre, which was 
     1397It was created by FahMon $as_me 2.3.1, which was 
    13981398generated by GNU Autoconf 2.61.  Invocation command line was 
    13991399 
    …… 
    21612161# Define the identity of the package. 
    21622162 PACKAGE='FahMon' 
    2163  VERSION='2.3.1pre' 
     2163 VERSION='2.3.1' 
    21642164 
    21652165 
    …… 
    33873387LIBS="$LIBS $WX_LIBS" 
    33883388 
    3389 ALL_LINGUAS="en_GB fr_FR pt_PT ru_RU pl sv_SE cs_CZ nl_NL pt_BR es_ES" 
     3389ALL_LINGUAS="en_GB fr_FR pt_PT ru_RU pl_PL sv_SE cs_CZ nl_NL pt_BR es_ES" 
    33903390 
    33913391 
    …… 
    65876587# values after options handling. 
    65886588ac_log=" 
    6589 This file was extended by FahMon $as_me 2.3.1pre, which was 
     6589This file was extended by FahMon $as_me 2.3.1, which was 
    65906590generated by GNU Autoconf 2.61.  Invocation command line was 
    65916591 
    …… 
    66406640cat >>$CONFIG_STATUS <<_ACEOF 
    66416641ac_cs_version="\\ 
    6642 FahMon config.status 2.3.1pre 
     6642FahMon config.status 2.3.1 
    66436643configured by $0, generated by GNU Autoconf 2.61, 
    66446644  with options \\"`echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`\\" 

  • trunk/configure.ac

    r94 r99  
    1010m4_include(m4/wxwin.m4) 
    1111AC_INIT([FahMon], 
    12         [2.3.1pre], 
     12        [2.3.1], 
    1313        [Andrew Schofield the.uncle.fungus@gmail.com], 
    1414        [FahMon]) 
    …… 
    4646LIBS="$LIBS $WX_LIBS" 
    4747 
    48 ALL_LINGUAS="en_GB fr_FR pt_PT ru_RU pl sv_SE cs_CZ nl_NL pt_BR es_ES" 
     48ALL_LINGUAS="en_GB fr_FR pt_PT ru_RU pl_PL sv_SE cs_CZ nl_NL pt_BR es_ES" 
    4949 
    5050AM_GNU_GETTEXT([external])