約 2,211,334 件
https://w.atwiki.jp/ce00582/pages/5888.html
html head meta charset="utf-8"/ title 思い出のメロディー /title script src="jquery.js" /script script src="getdata.js" /script script src="view.js" /script /head body onload="getdata()" p label for="number" 回 /label select id="number" name="number" option value="21" 21 /option option value="22" 22 /option option value="23" selected 23 /option option value="24" 24 /option option value="25" 25 /option option value="26" 26 /option option value="27" 27 /option /select /p input type="button" value="選択" onClick="table()" / p id="memo" 準備中 /p /body /html var a=new Array(); var b=new Array(); var c=new Array(); var number; function getdata() { var query = "SELECT a,b,c FROM " + 1gzTysB4plB46XOHOWOZHK5uQ431BDbKRRyK9BAc ; var encodedQuery = encodeURIComponent(query); var url = [ https //www.googleapis.com/fusiontables/v1/query ]; url.push( ?sql= + encodedQuery); url.push( key=AIzaSyAH0WCAXRIdHdbI-6bnMSN4kVDDZZmGyqY ); url.push( callback=? ); sx=0; $.ajax({ url url.join( ), dataType jsonp , success function (data) { var rows = data[ rows ]; for (var i in rows) { sx=sx+1; a[sx]= rows[i][0]; b[sx]= rows[i][1]; c[sx]= rows[i][2]; } number=sx; view(); } }); } function view(){ $("#memo").html("準備完了"); } function table(){ var str; var s; var y1=$("#number").val(); str=" table "; for(s=1;s number+1;s++){ if(a[s]==y1){ str=str+" tr "; str=str+" td "; str=str+a[s]; str=str+" /td "; str=str+" td "; str=str+b[s]; str=str+" /td "; str=str+" td "; str=str+c[s]; str=str+" /td "; str=str+" /tr "; } } str=str+" /table "; $("#memo").html(str); }
https://w.atwiki.jp/wiki7_benjamin/pages/30.html
EVENT BROKER OPTIONS # Controls what (if any) data gets sent to the event broker. # Values 0 = Broker nothing # -1 = Broker everything # other = See documentation event_broker_options=-1 EVENT BROKER MODULE(S) # This directive is used to specify an event broker module that should # by loaded by Nagios at startup. Use multiple directives if you want # to load more than one module. Arguments that should be passed to # the module at startup are seperated from the module path by a space. # # Example # # nebmodule= modulepath [moduleargs] #broker_module =/somewhere/module1.o #broker_module =/somewhere/module2.o arg1 arg2=3 debug=0 LOG ROTATION METHOD # This is the log rotation method that Nagios should use to rotate # the main log file. Values are as follows.. #n= None - don t rotate the log #h= Hourly rotation (top of the hour) #d= Daily rotation (midnight every day) #w= Weekly rotation (midnight on Saturday evening) #m= Monthly rotation (midnight last day of month) log_rotation_method=d LOG ARCHIVE PATH # This is the directory where archived (rotated) log files should be # placed (assuming you ve chosen to do log rotation). log_archive_path=/usr/local/nagios/var/archives LOGGING OPTIONS # If you want messages logged to the syslog facility, as well as the # NetAlarm log file set this option to 1. If not, set it to 0. use_syslog=1 NOTIFICATION LOGGING OPTION # If you don t want notifications to be logged, set this value to 0. # If notifications should be logged, set the value to 1. log_notifications=1 SERVICE RETRY LOGGING OPTION # If you don t want service check retries to be logged, set this value # to 0. If retries should be logged, set the value to 1. log_service_retries=1 HOST RETRY LOGGING OPTION # If you don t want host check retries to be logged, set this value to # 0. If retries should be logged, set the value to 1. log_host_retries=1 EVENT HANDLER LOGGING OPTION # If you don t want host and service event handlers to be logged, set # this value to 0. If event handlers should be logged, set the value # to 1. log_event_handlers=1 INITIAL STATES LOGGING OPTION # If you want Nagios to log all initial host and service states to # the main log file (the first time the service or host is checked) # you can enable this option by setting this value to 1. If you # are not using an external application that does long term state # statistics reporting, you do not need to enable this option. In # this case, set the value to 0. log_initial_states=0 EXTERNAL COMMANDS LOGGING OPTION # If you don t want Nagios to log external commands, set this value # to 0. If external commands should be logged, set this value to 1. # Note This option does not include logging of passive service # checks - see the option below for controlling whether or not # passive checks are logged. log_external_commands=1 PASSIVE CHECKS LOGGING OPTION # If you don t want Nagios to log passive host and service checks, set # this value to 0. If passive service checks should be logged, set # this value to 1. log_passive_checks=1 GLOBAL HOST AND SERVICE EVENT HANDLERS # These options allow you to specify a host and service event handler # command that is to be run for every host or service state change. # The global event handler is executed immediately prior to the event # handler that you have optionally specified in each host or # service definition. The command argument is the short name of a # command definition that you define in your host configuration file. # Read the HTML docs for more information. #global_host_event_handler =somecommand #global_service_event_handler =somecommand SERVICE INTER-CHECK DELAY METHOD # This is the method that Nagios should use when initially # "spreading out" service checks when it starts monitoring. The # default is to use smart delay calculation, which will try to # space all service checks out evenly to minimize CPU load. # Using the dumb setting will cause all checks to be scheduled # at the same time (with no delay between them)! This is not a # good thing for production, but is useful when testing the # parallelization functionality. #n= None - don t use any delay between checks #d= Use a "dumb" delay of 1 second between checks #s= Use "smart" inter-check delay calculation # x.xx = Use an inter-check delay of x.xx seconds service_inter_check_delay_method=s MAXIMUM SERVICE CHECK SPREAD # This variable determines the timeframe (in minutes) from the # program start time that an initial check of all services should # be completed. Default is 30 minutes. max_service_check_spread=30 SERVICE CHECK INTERLEAVE FACTOR # This variable determines how service checks are interleaved. # Interleaving the service checks allows for a more even # distribution of service checks and reduced load on remote # hosts. Setting this value to 1 is equivalent to how versions # of Nagios previous to 0.0.5 did service checks. Set this # value to s (smart) for automatic calculation of the interleave # factor unless you have a specific reason to change it. # s = Use "smart" interleave factor calculation # x = Use an interleave factor of x, where x is a # number greater than or equal to 1. service_interleave_factor=s HOST INTER-CHECK DELAY METHOD # This is the method that Nagios should use when initially # "spreading out" host checks when it starts monitoring. The # default is to use smart delay calculation, which will try to # space all host checks out evenly to minimize CPU load. # Using the dumb setting will cause all checks to be scheduled # at the same time (with no delay between them)! #n= None - don t use any delay between checks #d= Use a "dumb" delay of 1 second between checks #s= Use "smart" inter-check delay calculation # x.xx = Use an inter-check delay of x.xx seconds host_inter_check_delay_method=s MAXIMUM HOST CHECK SPREAD # This variable determines the timeframe (in minutes) from the # program start time that an initial check of all hosts should # be completed. Default is 30 minutes. max_host_check_spread=30 MAXIMUM CONCURRENT SERVICE CHECKS # This option allows you to specify the maximum number of # service checks that can be run in parallel at any given time. # Specifying a value of 1 for this variable essentially prevents # any service checks from being parallelized. A value of 0 # will not restrict the number of concurrent checks that are # being executed. max_concurrent_checks=0 SERVICE CHECK REAPER FREQUENCY # This is the frequency (in seconds!) that Nagios will process # the results of services that have been checked. service_reaper_frequency=10 AUTO-RESCHEDULING OPTION # This option determines whether or not Nagios will attempt to # automatically reschedule active host and service checks to # "smooth" them out over time. This can help balance the load on # the monitoring server. # WARNING THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY auto_reschedule_checks=0 AUTO-RESCHEDULING INTERVAL # This option determines how often (in seconds) Nagios will # attempt to automatically reschedule checks. This option only # has an effect if the auto_reschedule_checks option is enabled. # Default is 30 seconds. # WARNING THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY auto_rescheduling_interval=30 AUTO-RESCHEDULING WINDOW # This option determines the "window" of time (in seconds) that # Nagios will look at when automatically rescheduling checks. # Only host and service checks that occur in the next X seconds # (determined by this variable) will be rescheduled. This option # only has an effect if the auto_reschedule_checks option is # enabled. Default is 180 seconds (3 minutes). # WARNING THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY auto_rescheduling_window=180 SLEEP TIME # This is the number of seconds to sleep between checking for system # events and service checks that need to be run. sleep_time=0.25 TIMEOUT VALUES # These options control how much time Nagios will allow various # types of commands to execute before killing them off. Options # are available for controlling maximum time allotted for # service checks, host checks, event handlers, notifications, the # ocsp command, and performance data commands. All values are in # seconds. service_check_timeout=60 host_check_timeout=30 event_handler_timeout=30 notification_timeout=30 ocsp_timeout=5 perfdata_timeout=5 RETAIN STATE INFORMATION # This setting determines whether or not Nagios will save state # information for services and hosts before it shuts down. Upon # startup Nagios will reload all saved service and host state # information before starting to monitor. This is useful for # maintaining long-term data on state statistics, etc, but will # slow Nagios down a bit when it (re)starts. Since its only # a one-time penalty, I think its well worth the additional # startup delay. retain_state_information=1 STATE RETENTION FILE # This is the file that Nagios should use to store host and # service state information before it shuts down. The state # information in this file is also read immediately prior to # starting to monitor the network when Nagios is restarted. # This file is used only if the preserve_state_information # variable is set to 1. state_retention_file=/usr/local/nagios/var/retention.dat RETENTION DATA UPDATE INTERVAL # This setting determines how often (in minutes) that Nagios # will automatically save retention data during normal operation. # If you set this value to 0, Nagios will not save retention # data at regular interval, but it will still save retention # data before shutting down or restarting. If you have disabled # state retention, this option has no effect. retention_update_interval=60 USE RETAINED PROGRAM STATE # This setting determines whether or not Nagios will set # program status variables based on the values saved in the # retention file. If you want to use retained program status # information, set this value to 1. If not, set this value # to 0. use_retained_program_state=1 USE RETAINED SCHEDULING INFO # This setting determines whether or not Nagios will retain # the scheduling info (next check time) for hosts and services # based on the values saved in the retention file. If you # If you want to use retained scheduling info, set this # value to 1. If not, set this value to 0. use_retained_scheduling_info=0 INTERVAL LENGTH # This is the seconds per unit interval as used in the # host/contact/service configuration files. Setting this to 60 means # that each interval is one minute long (60 seconds). Other settings # have not been tested much, so your mileage is likely to vary... interval_length=60 AGGRESSIVE HOST CHECKING OPTION # If you don t want to turn on aggressive host checking features, set # this value to 0 (the default). Otherwise set this value to 1 to # enable the aggressive check option. Read the docs for more info # on what aggressive host check is or check out the source code in # base/checks.c use_aggressive_host_checking=0 SERVICE CHECK EXECUTION OPTION # This determines whether or not Nagios will actively execute # service checks when it initially starts. If this option is # disabled, checks are not actively made, but Nagios can still # receive and process passive check results that come in. Unless # you re implementing redundant hosts or have a special need for # disabling the execution of service checks, leave this enabled! # Values 1 = enable checks, 0 = disable checks execute_service_checks=1 PASSIVE SERVICE CHECK ACCEPTANCE OPTION # This determines whether or not Nagios will accept passive # service checks results when it initially (re)starts. # Values 1 = accept passive checks, 0 = reject passive checks accept_passive_service_checks=1 HOST CHECK EXECUTION OPTION # This determines whether or not Nagios will actively execute # host checks when it initially starts. If this option is # disabled, checks are not actively made, but Nagios can still # receive and process passive check results that come in. Unless # you re implementing redundant hosts or have a special need for # disabling the execution of host checks, leave this enabled! # Values 1 = enable checks, 0 = disable checks execute_host_checks=1 PASSIVE HOST CHECK ACCEPTANCE OPTION # This determines whether or not Nagios will accept passive # host checks results when it initially (re)starts. # Values 1 = accept passive checks, 0 = reject passive checks accept_passive_host_checks=1 NOTIFICATIONS OPTION # This determines whether or not Nagios will sent out any host or # service notifications when it is initially (re)started. # Values 1 = enable notifications, 0 = disable notifications enable_notifications=1 EVENT HANDLER USE OPTION # This determines whether or not Nagios will run any host or # service event handlers when it is initially (re)started. Unless # you re implementing redundant hosts, leave this option enabled. # Values 1 = enable event handlers, 0 = disable event handlers enable_event_handlers=1 PROCESS PERFORMANCE DATA OPTION # This determines whether or not Nagios will process performance # data returned from service and host checks. If this option is # enabled, host performance data will be processed using the # host_perfdata_command (defined below) and service performance # data will be processed using the service_perfdata_command (also # defined below). Read the HTML docs for more information on # performance data. # Values 1 = process performance data, 0 = do not process performance data process_performance_data=0 HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS # These commands are run after every host and service check is # performed. These commands are executed only if the # enable_performance_data option (above) is set to 1. The command # argument is the short name of a command definition that you # define in your host configuration file. Read the HTML docs for # more information on performance data. #host_perfdata_command =process-host-perfdata #service_perfdata_command =process-service-perfdata HOST AND SERVICE PERFORMANCE DATA FILES # These files are used to store host and service performance data. # Performance data is only written to these files if the # enable_performance_data option (above) is set to 1. #host_perfdata_file =/tmp/host-perfdata #service_perfdata_file =/tmp/service-perfdata HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES # These options determine what data is written (and how) to the # performance data files. The templates may contain macros, special # characters (\t for tab, \r for carriage return, \n for newline) # and plain text. A newline is automatically added after each write # to the performance data file. Some examples of what you can do are # shown below. #host_perfdata_file_template =[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$ #service_perfdata_file_template =[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$ HOST AND SERVICE PERFORMANCE DATA FILE MODES # This option determines whether or not the host and service # performance data files are opened in write ("w") or append ("a") # mode. Unless you are the files are named pipes, you will probably # want to use the default mode of append ("a"). #host_perfdata_file_mode =a #service_perfdata_file_mode =a HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL # These options determine how often (in seconds) the host and service # performance data files are processed using the commands defined # below. A value of 0 indicates the files should not be periodically # processed. #host_perfdata_file_processing_interval =0 #service_perfdata_file_processing_interval =0 HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS # These commands are used to periodically process the host and # service performance data files. The interval at which the # processing occurs is determined by the options above. #host_perfdata_file_processing_command =process-host-perfdata-file #service_perfdata_file_processing_command =process-service-perfdata-file OBSESS OVER SERVICE CHECKS OPTION # This determines whether or not Nagios will obsess over service # checks and run the ocsp_command defined below. Unless you re # planning on implementing distributed monitoring, do not enable # this option. Read the HTML docs for more information on # implementing distributed monitoring. # Values 1 = obsess over services, 0 = do not obsess (default) obsess_over_services=0 OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND # This is the command that is run for every service check that is # processed by Nagios. This command is executed only if the # obsess_over_service option (above) is set to 1. The command # argument is the short name of a command definition that you # define in your host configuration file. Read the HTML docs for # more information on implementing distributed monitoring. #ocsp_command =somecommand ORPHANED SERVICE CHECK OPTION # This determines whether or not Nagios will periodically # check for orphaned services. Since service checks are not # rescheduled until the results of their previous execution # instance are processed, there exists a possibility that some # checks may never get rescheduled. This seems to be a rare # problem and should not happen under normal circumstances. # If you have problems with service checks never getting # rescheduled, you might want to try enabling this option. # Values 1 = enable checks, 0 = disable checks check_for_orphaned_services=0 SERVICE FRESHNESS CHECK OPTION # This option determines whether or not Nagios will periodically # check the "freshness" of service results. Enabling this option # is useful for ensuring passive checks are received in a timely # manner. # Values 1 = enabled freshness checking, 0 = disable freshness checking check_service_freshness=1 SERVICE FRESHNESS CHECK INTERVAL # This setting determines how often (in seconds) Nagios will # check the "freshness" of service check results. If you have # disabled service freshness checking, this option has no effect. service_freshness_check_interval=60 HOST FRESHNESS CHECK OPTION # This option determines whether or not Nagios will periodically # check the "freshness" of host results. Enabling this option # is useful for ensuring passive checks are received in a timely # manner. # Values 1 = enabled freshness checking, 0 = disable freshness checking check_host_freshness=0 HOST FRESHNESS CHECK INTERVAL # This setting determines how often (in seconds) Nagios will # check the "freshness" of host check results. If you have # disabled host freshness checking, this option has no effect. host_freshness_check_interval=60 AGGREGATED STATUS UPDATES # This option determines whether or not Nagios will # aggregate updates of host, service, and program status # data. Normally, status data is updated immediately when # a change occurs. This can result in high CPU loads if # you are monitoring a lot of services. If you want Nagios # to only refresh status data every few seconds, disable # this option. # Values 1 = enable aggregate updates, 0 = disable aggregate updates aggregate_status_updates=1 AGGREGATED STATUS UPDATE INTERVAL # Combined with the aggregate_status_updates option, # this option determines the frequency (in seconds!) that # Nagios will periodically dump program, host, and # service status data. If you are not using aggregated # status data updates, this option has no effect. status_update_interval=15 FLAP DETECTION OPTION # This option determines whether or not Nagios will try # and detect hosts and services that are "flapping". # Flapping occurs when a host or service changes between # states too frequently. When Nagios detects that a # host or service is flapping, it will temporarily supress # notifications for that host/service until it stops # flapping. Flap detection is very experimental, so read # the HTML documentation before enabling this feature! # Values 1 = enable flap detection # 0 = disable flap detection (default) enable_flap_detection=0 FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES # Read the HTML documentation on flap detection for # an explanation of what this option does. This option # has no effect if flap detection is disabled. low_service_flap_threshold=5.0 high_service_flap_threshold=20.0 low_host_flap_threshold=5.0 high_host_flap_threshold=20.0 DATE FORMAT OPTION # This option determines how short dates are displayed. Valid options # include #us(MM-DD-YYYY HH MM SS) #euro (DD-MM-YYYY HH MM SS) #iso8601(YYYY-MM-DD HH MM SS) #strict-iso8601(YYYY-MM-DDTHH MM SS) # date_format=us P1.PL FILE LOCATION # This value determines where the p1.pl perl script (used by the # embedded Perl interpreter) is located. If you didn t compile # Nagios with embedded Perl support, this option has no effect. p1_file=/usr/local/nagios/bin/p1.pl ILLEGAL OBJECT NAME CHARACTERS # This option allows you to specify illegal characters that cannot # be used in host names, service descriptions, or names of other # object types. illegal_object_name_chars=`~!$%^ *| " ?,()= ILLEGAL MACRO OUTPUT CHARACTERS # This option allows you to specify illegal characters that are # stripped from macros before being used in notifications, event # handlers, etc. This DOES NOT affect macros used in service or # host check commands. # The following macros are stripped of the characters you specify #$HOSTOUTPUT$ #$HOSTPERFDATA$ #$HOSTACKAUTHOR$ #$HOSTACKCOMMENT$ #$SERVICEOUTPUT$ #$SERVICEPERFDATA$ #$SERVICEACKAUTHOR$ #$SERVICEACKCOMMENT$ illegal_macro_output_chars=`~$ | " REGULAR EXPRESSION MATCHING # This option controls whether or not regular expression matching # takes place in the object config files. Regular expression # matching is used to match host, hostgroup, service, and service # group names/descriptions in some fields of various object types. # Values 1 = enable regexp matching, 0 = disable regexp matching use_regexp_matching=0 "TRUE" REGULAR EXPRESSION MATCHING # This option controls whether or not "true" regular expression # matching takes place in the object config files. This option # only has an effect if regular expression matching is enabled # (see above). If this option is DISABLED, regular expression # matching only occurs if a string contains wildcard characters # (* and ?). If the option is ENABLED, regexp matching occurs # all the time (which can be annoying). # Values 1 = enable true matching, 0 = disable true matching use_true_regexp_matching=0 ADMINISTRATOR EMAIL ADDRESS # The email address of the administrator of *this* machine (the one # doing the monitoring). Nagios never uses this value itself, but # you can access this value by using the $ADMINEMAIL$ macro in your # notification commands. admin_email=nagios ADMINISTRATOR PAGER NUMBER/ADDRESS # The pager number/address for the administrator of *this* machine. # Nagios never uses this value itself, but you can access this # value by using the $ADMINPAGER$ macro in your notification # commands. admin_pager=pagenagios DAEMON CORE DUMP OPTION # This option determines whether or not Nagios is allowed to create # a core dump when it runs as a daemon. Note that it is generally # considered bad form to allow this, but it may be useful for # debugging purposes. # Values 1 - Allow core dumps # 0 - Do not allow core dumps (default) daemon_dumps_core=0 # EOF (End of file)
https://w.atwiki.jp/pianocompetition/pages/16.html
2008年開催主要なコンクール一覧 2008年3月 20080309-0327 第12回ルービンシュタイン国際ピアノコンクール(イスラエル)[25000米ドル]★配信あり 公式HP http //www.arims.org.il/comp-rules.php 20080330-0413 第8回リスト国際ピアノコンクール(NL)[20000ユーロ]★配信あり 公式HP http //www.liszt.nl/english/competition 2008年4月 20080414-0427 第4回ソウル国際音楽コンクール(韓国) [50000米ドル]★配信あり 公式HP http //www.seoulcompetition.com/competition/piano_schedule_eng.html 2008年5月 20080508-0520 第54回マリア・カナルス・バルセロナ国際音楽演奏コンクール(スペイン)[10000ユーロ]★配信あり 公式HP http //www.mariacanals.org/eng/13_premis.asp 20080519-0529 モントリオール国際音楽コンクール(カナダ)[30000米ドル]★音声配信あり 公式HP http //www.concoursmontreal.ca/permanent/en/inscription/piano2008.asp 2008年6月 20080615-0629 リヒテル国際ピアノコンクール(ロシア)(30000米ドル)★配信あり 公式HP http //www.richtercompetition.com/2008/ 20080616-0621 ホセ・イトゥルビ国際音楽コンクール at UCLA (米国) [50000米ドル] 公式HP http //www.joseiturbifoundation.org/ 2008年7月 20080704-0711 e-Competition ジュニア部門(米国)[8000米ドル]★配信あり 公式HP http //www.piano-e-competition.com/ecompetition/dates_junior.asp 20080716-0802 第9回シドニー国際ピアノコンクール(豪)[25000米ドル]★配信あり 公式HP http //www.sipca.com.au/ 20080725-0807 第16回サンタンデール国際ピアノコンクール(スペイン)[30000ユーロ]★配信あり 公式HP http //www.fundacionalbeniz.com/ 2008年8月 200808 PTNAコンペティション 特級(日本)☆(100万円) 2008年9月 20080915-0927 第16回ホセ・イトルビ国際ピアノコンクール(スペイン)[18000ユーロ]★配信あり 公式HP http //www.pianoiturbi.com/ 2008年10月 20081017-1029 第63回ジュネーブ国際音楽コンクール(スイス)[20000CHF] 公式HP http //www.concoursgeneve.ch/index.php?option=com_content task=view id=66 Itemid=212 ★は配信有りのコンクール(配信形態の詳細は各頁参照) ☆は過去の実績等から配信が期待されるコンクール カッコ内は優勝賞金額
https://w.atwiki.jp/s603rd/pages/111.html
Mobipocket Reader １．概要 eBookリーダ（PDFは読めない） 栞機能やリンク機能があり読書に向いている。 訂正機能もある。 ２．設定 設定画面は４つ。 基本設定、表示文字設定、表示色設定、表示設定がある。 ２．１ 基本設定 基本設定では起動時の設定が出来る。 At startup,open [Library|Last book] ： 起動時にライブラリを表示するか、最後に読んでいたブックを開くか Dictionary [Auto] ： Auto以外の選択肢が無い。辞書ファイルを自動認識するかどうかかな？ ２．２ 表示文字設定 フォント設定が出来る。 下線設定はここではないのではと、分類に疑問を感じる。 Font size ： 表示文字サイズ Font familty ： フォントの選択（SBMのN82標準ではHeisei kaku Gothic S60のみ選択可能っぽい） Underline links [On|Off] ： リンクが設定されている文字列に下線を付けるかどうか ２．３ 表示色設定 画面表示の色設定が出来る。 Text color ： 通常文字色 Background color ： 背景色 Highlight color ： 選択文字色 Modify color ： 訂正文字色 Hyperlink color ： リンク文字色 ２．４ 画面設定 上記以外の表示設定が出来る。 Margins ： 余白 Line spacing ： 行間 Orientation ： 縦横表示 Full justification ： 行末を画面右端に揃えるかどうか Fullscreen ： 全画面 Show the progress bar ： 進捗状況バー ３．使用方法 eBookリーダとして紹介しているが辞書しか入っていない。 辞書画面を使用して説明をする。 ３．１ 起動画面 起動時の設定を最後に読んでいたLast Bookにしていれば、その場所が初期状態で開く。 Libraryにしておくとライブラリリスト画面が表示される。 ３．１．１ Libraryリスト画面 LibraryにはeBooks、eNews、eDocs、Cドライブ、Eドライブのタブがある。 それぞれのカテゴリのeBookが表示される。 eNewsは、デスクトップ版のMobipocket Readerで購読しているRSSと同期すると読める。 ３．２ Library画面での操作 ３．２．２ 開く OptionのOpenを選択するか、センターキーでBookを開く事が出来る。 閉じる前に読んでいた場所から開く事が出来る。 ３．２．３ 詳細表示 OptionのBook detailでBookの詳細を確認出来る。 ３．２．４ 削除 OptionのDeleteでBookの削除が出来る。 ３．２．５ 本屋 OptionのeBookstoreから、Mobipocketが運営しているオンラインBook Storeに行ける。 ３．２．６ 送信 OptionのSendからBookの送信が出来る。 ファイル送信になるのでSMSは選択できない。 ３．３ 閲覧中の操作 ３．３．１ 辞書検索 辞書タイプのBookの場合は、検索画面への移動リンクが表示される。 Look Upを選択すると、検索画面になる。 検索文字列を入力するとインクリメンタルサーチが出来る。 リストから目的に言葉を選択すると詳細画面が表示される。 ３．３．２ 栞 OptionのAdd bookmarkを選択すると栞が設定できる。 栞設定している場所でOptionのRemove bookmarkで栞を削除する事も出来る。 設定している栞の一覧はOptionのAnnotationsで確認、ジャンプが出来る。 ３．３．３ マーキング OptionのSelection modeからHighlightを選択するとマーキングできる。 マーキング一覧の確認やジャンプは栞と同じ操作で可能だ。 ３．３．４ メモ OptionのSelection modeからAdd noteを選択するとメモが設定できる。 メモ一覧の確認やジャンプは栞と同じ操作で可能だ。 ３．３．５ 訂正 OptionのSelection modeからModifyを選択すると訂正ができる。 但し、Book本文は訂正ラインが入るだけで、訂正されている文字列に カーソルを合わせる事で訂正内容を確認出来る。 EditやDeleteで訂正を修正、削除する事も出来る。 ３．３．６ リンク OptionのSelection modeからAdd linkを選択するとリンクを設定できる。 移動先で文字列を選択しろとメッセージが表示されるので、リンク先へ移動して選択する。 OptionのSekection modeからSet link targetを選択すればリンクが生成される。 ３．３．７ 栞、マーク、メモ、リンクの一覧 OptionのAnnotationsで栞、マーク、メモ、リンクの一覧が確認できる。 All以外に個別のタブでも確認可能だ。 OptionのOpenまたはセンターキーでジャンプできる。 Deleteで削除する事も出来る。 ３．３．８ 辞書の作り方 辞書の作り方は705NKのwikiに出ているのでここでは触れない。 昔Zaurusで使っていた日⇔比辞書の元ネタがcsv形式で残っていたので辞書に変換してみた。 日→比 比→日 自作辞書なので意味も短いが、何とか役には立っている。 ４．公式サイト MOBIPOCKET ５．入手方法 公式サイトからダウンロード出来る。 ６．最新バージョン 2009.11.18時点 5.03.(576) ７．インストール情報 ７．１ メインプログラム Name ： Mobipocket Reader Supplier ： MOBIPOCKET.COM App size ： 2MB ７．２ 個別ライブラリ 特になし ７．３ Supplier共通ライブラリ 特になし ７．４ S60共通ライブラリ 特になし ８．価格 フリーソフト ９．個人所見 以前はRSSリーダとして使用していたが、PCから更新する必要があったので使わなくなった。 Bookリーダとして使っている訳でもない。 辞書としてのみ使用している。便利だが辞書のみで使うにはアプリのサイズが大きいのが気になる。 操作は軽快で、機能も豊富だ。日本語のeBookがあれば読むかもしれない。
https://w.atwiki.jp/nkym_memo/pages/207.html
tmuxinator インストール(Ubuntu12.04) gem install tmuxinator 下記を環境変数を.zshrcや.zshenvなどに追加 export EDITOR= vim export SHELL= zsh プロジェクト作成 mux new dev * 設定ファイル # ~/.tmuxinator/dev.yml name dev root ~/ # Optional tmux socket # socket_name foo # Runs before everything. Use it to start daemons etc. # pre sudo /etc/rc.d/mysqld start # Runs in each window and pane before window/pane specific commands. Useful for setting up interpreter versions. # pre_window rbenv shell 2.0.0-p247 pre_window touch test # Pass command line options to tmux. Useful for specifying a different tmux.conf. # tmux_options -f ~/.tmux.mac.conf # Change the command to call tmux. This can be used by derivatives/wrappers like byobu. # tmux_command byobu windows - dev layout tiled panes - - cd Documents 起動 mux dev gemが古い場合 sudo gem install rubygems-update sudo gem update_rubygems tmux 設定ファイル .tmux.conf # ctrl-t でコマンドモード set-option -g prefix C-x unbind C-b # 日本語環境なら今のところ必須。 set-window-option -g utf8 on #マウス操作対応 set-option -g mouse-select-pane on set-option -g mouse-select-window on set-option -g mouse-resize-pane on set-option -g mode-mouse on set-option -g mouse-utf8 on # 設定ファイルリロード bind C-r source-file ~/.tmux.conf # ウィンドウの移動 # Prefix(ここではCtrl+t)を連続入力することでウィンドウを移動させます。 bind -n M-t select-pane -t + # ウィンドウを強制的に終了 # Prefix k でウィンドウを強制終了できるようにします。 bind k confirm-before -p "kill-window #W? (y/n)" kill-window #ステータスバーの外観の設定 set -g status-interval 5 set -g status-left-length 16 set -g status-right-length 50 set -g status-fg cyan set -g status-bg black set -g status-left-length 60 set -g status-left '#[fg=white,bg=black]#H#[fg=white] #[fg=white][#S#[fg=white[#[default]' set -g status-right '#[fg=black,bg=cyan,bold] [%Y-%m-%d(%a) %H %M]#[default]' set -g message-attr bold set -g message-fg white set -g message-bg red set -g pane-active-border-fg cyan set -g pane-active-border-bg black setw -g window-status-current-fg blue set-window-option -g mode-bg white set-window-option -g mode-fg black set-window-option -g window-status-fg white set-window-option -g window-status-bg black #set-window-option -g window-status-current-attr underline set-window-option -g window-status-current-bg black set-window-option -g window-status-current-fg green # window-status-current setw -g window-status-current-fg black setw -g window-status-current-bg cyan setw -g window-status-current-attr bold#,underscore # ウィンドウを(ペインに)分割 # ＜Prefix＞＜v＞、＜Prefix＞＜h＞と入力するだけで分割できるようにします。 bind v split-window -v bind h split-window -h # ペインのアクティブなウインドウの外観の設定 set -g pane-active-border-fg black set -g pane-active-border-bg cyan # ペインの移動 # Shift + 上下左右でペインを移動できるようにする。(＜Prefix＞不要) # 行頭に"bind -n"をつけるとPrefixが不要になる。 bind -n S-left select-pane -L bind -n S-down select-pane -D bind -n S-up select-pane -U bind -n S-right select-pane -R # コピー関連の設定 # Prefix y でコピーし、 Prefix p で貼付けをできるように設定。 bind y copy-mode bind p paste-buffer # window間でのヒストリーの共有 #function share_history { # history -a # history -c # history -r #} #PROMPT_COMMAND='share_history' #shopt -u histappend #export HISTSIZE=9999 # ペイン分割をemacsライクに bind 0 kill-pane bind 1 break-pane bind 2 split-window -v bind 3 split-window -h # キーストロークのディレイを減らす set -sg escape-time 1
https://w.atwiki.jp/eirgvginfo/pages/122.html
Liberation メインギルド 無 Liberation リベリオン サブ系列ギルド Artifact アーティファクト Nidhoggr ニットヘッグ 無 Battle Jam バトルジャム 無 - God of War - ゴッドオブウォー ボス狩りをメインにする、現時点におけるEir最強ギルドの1つ。 圧倒的な装備を誇るメンバーが揃っており、その攻撃力は間違いなくNo.1。 味方以外は常に完全排除の方針を貫いている。 Eirの全神器のおよそ半数を保有しており、金ゴキをはじめとしてボスカード・ボス装備も多数保有するため、全く想定外の攻撃で翻弄されることがよく起こる。 1人で小規模同盟を壊滅させるほどの力を持つメンバーが複数人存在する。 ゴスリンの普及率も異常で、ほぼ全員が保有していると考えても良いかもしれない。 個々のメンバーが突出して個性が強いため、構成人数が少なすぎるのが欠点。 また、ボスを巡る争いなどから、他ギルドとの折り合いが悪すぎることがほとんどである。 それ故同盟を組むことが非常に難しく、GvG参加者が数名しかいなかったために組織的に活動することが困難な時期もあった。その当時、ゲリラ活動的に各砦に現れては暴れるため、天災のように思われていたこともあったようだ。 数あるギルドの中でも「規格外」と認識されるギルドの1つ。 【ギルドマスター】Nehalem 職？ 性別？ Artifact Dordona Clown ♂ Nidhoggr StrayCat Chaser ♂ Battle Jam金ゴキ・ゴスリン Kratos Chaser ♀ - God of War -金ゴキ・ゴスリン 【Lord Knight】Maria=Firsece ♀Wメギン・金ゴキ・ゴスリン †リコリス† ♀Wメギン・金ゴキ・ゴスリン Amaranth ♀Wメギン・金ゴキ・ゴスリン はーさん ♂ゴスリン Love-Beat ♀ゴスリン 【Paladin】Apocaｌypse ♀ゴスリン Border of Life ♀ゴスリン 【Assassin Cross】Era step ♂ゴスリン 【Chaser】EL CONDOR PASA ♂ゴスリン 【Creater】どどりあさん ♀ミョル・金ゴキ・ゴスリン 【High Wizard】ice cat ♀ ice=cream ♀ NattiLand ♀ 【Proffesor】Hellfire ♂ゴスリン 【Champion】弓塚 さつき ♀ゴスリン Fiora ♀ゴスリン
https://w.atwiki.jp/lexicon/pages/57.html
http //coliss.com/articles/build-websites/operation/javascript/jquery-plugin-darktooltip.html http //rubentd.com/darktooltip-examples/ http //rubentd.com/js/darktooltip-examples.js http //rubentd.com/css/darktooltip-examples.css Example 1 Example 2 default html wow such content very html Options Option Values Default opacity(不透明度) 0 – 1 0.9 content(ツールチップのメッセージ) Tooltip message empty size(ツールチップのサイズ) small, medium, large medium gravity(ツールチップの表示方向) south, west, north, east south theme(ツールチップのテーマ) dark, light dark trigger(ツールチップを表示するトリガー) hover, click hover animation(ツールチップを表示するアニメーション) none, flipIn, fadeIn none confirm(confirm機能の有無) true, false false yes(yesのラベル) Label for ‘Yes’ option ‘Yes’ no(noのラベル) Label for ‘No’ option ‘No’ finalMessage(最後に表示するメッセージ) A message that appears at the end of the action for the confirm ” finalMessageDuration(最後に表示するメッセージの間隔) Duration of the final message in ms 1000 onYes(yes時の動作) Function that is triggered when clicking ‘Yes’ on confirm empty onNo(no時の動作) Function that is triggered when clicking ‘No’ on confirm empty
https://w.atwiki.jp/searchcustom/pages/19.html
カテゴリ選択部分（複数select化） カテゴリ選択部分（複数select化） かなり無理矢理 ps_user.cgi 56行目 push(@sitecat,$text) if $key eq sitecat ; この行の上に↓追加 for($i=0;$i $maxcat;$i++){ my $name = "sitecat".$i;if($text){push(@sitecat,$text) if $key eq $name;} } ps_user.cgi 292行目（sub change1） foreach(@y2){$z1{$_}=1;}foreach (sort {$a cmp $b;} keys %category){$category.=" option value=\"$_\"".($z1{$_}?" selected" "")." ". linkmake($_,1)."\n";}$category=" select name=\"sitecat\" size=10".(($maxcat-1)?" multiple" "")." $category /select \n"; ↓と差し替え ##カテゴリ複数行for($i=0;$i $maxcat;$i++){$category.=" select name=\"sitecat".$i."\" size=1 option value=\"\" ---- /option \n";foreach (sort {$a cmp $b;} keys %category){if($_ eq $y2[$i]){$category.=" option value=\"$_\" selected ". linkmake($_,1)." /option \n";}else{$category.=" option value=\"$_\" ". linkmake($_,1)." /option \n";}}$category.=" /select br \n";}##カテゴリ複数行ここまで ps_user.cgi 732行目（sub reg1） 赤字を追加 my ($category,$bannerinput,$categoryput); ps_user.cgi 737行目（sub reg1） foreach (sort {$a cmp $b;} keys %category){$category.=" option value=\"$_\" ". linkmake($_,1)."\n";}$category=" select name=\"sitecat\" size=10".(($maxcat-1)?"multiple" "")." $category /select \n"; ↓と差し替え ##ここからforeach (sort {$a cmp $b;} keys %category){$categoryput.=" option value=\"$_\" ". linkmake($_,1)." /option \n";}for($i=0;$i $maxcat;$i++){$category.=" select name=\"sitecat".$i."\" size=1 option value=\"\" ---- /option \n";$category.=$categoryput;$category.=" /select br \n";}##ここまで ▲
https://w.atwiki.jp/valokaku/pages/21.html
*ATTACKER **A - link_anchor(,anchor_only=true){} - link_anchor(,anchor_only=true){} **B - link_anchor(,anchor_only=true){} - link_anchor(,anchor_only=true){} *DEFENDER **A - link_anchor(,anchor_only=true){} - link_anchor(,anchor_only=true){} **B - link_anchor(,anchor_only=true){} - link_anchor(,anchor_only=true){} ---- - sizex(7){ aname(,option=nolink){}} sizex(5){} sizex(5){} ---- - sizex(7){ aname(,option=nolink){}} sizex(5){} sizex(5){} ---- - sizex(7){ aname(,option=nolink){}} sizex(5){} sizex(5){} ---- - sizex(7){ aname(,option=nolink){}} sizex(5){} sizex(5){} ---- - sizex(7){ aname(,option=nolink){}} sizex(5){} sizex(5){} ---- - sizex(7){ aname(,option=nolink){}} sizex(5){} sizex(5){} ----
https://w.atwiki.jp/vocaloidchly/pages/2426.html
作詞：謝謝P 作曲：謝謝P 編曲：謝謝P 歌：巡音ルカ 翻譯：yanao＋Mac OS X 鍵盤快速鍵 Space Shortcut Key Part3 （Space Shortcut Key… Macintosh Love…） Learn about common Mac OS X keyboard shortcuts. A keyboard shortcut is a way to invoke a function in Mac OS X by pressing a combination of keys on your keyboard. 瞭解常用的 Mac OS X 鍵盤快速鍵。鍵盤快速鍵讓您按鍵盤上的按鍵組合，就能叫出·Mac·OS·X·的功能。 shift + command + A ・・・開啟「應用程式」檔案夾 shift + command + D ・・・開啟桌面檔案夾 shift + command + U ・・・開啟「工具程式」檔案夾 shift + command + N ・・・新增檔案夾 control + command + I ・・・取得摘要簡介 option + command + 拖移 ・・・製作拖移項目的替身 command + C ・・・複製 command + V ・・・貼上 command + X ・・・剪下 command + A ・・・全選 command + D ・・・複製 command + E ・・・在所選範圍內進行尋找 command + I ・・・簡介 command + W ・・・關閉視窗 option + command + N ・・・新增智慧型檔案夾 option + command + T ・・・在 [Finder] 視窗中隱藏工具列 / 顯示工具列 option + command + A ・・・取消選取所有項目 option + command + Y ・・・幻燈片秀（Mac OS X 10.5 或以上版本） option + command + I ・・・顯示檢閱器 shift + command + F ・・・尋找 Spotlight 檔案名稱符合項目 command + 1 ・・・以圖像顯示 command + 2 ・・・依列表顯示 command + 3 ・・・依欄位顯示 command + 4 ・・・依 Cover Flow 顯示 command + 拖移 ・・・把拖移的項目移動到其他卷宗/位置 option + 拖移 ・・・拷貝拖移的項目 command + M ・・・最小化視窗 command + L ・・・製作所選項目的替身 command + H ・・・隱藏視窗 command + J ・・・打開顯示方式選項 shift + command + delete ・・・清空垃圾桶 option + shift + command + esc ・・・強制結束Finder shift + command + T ・・・加到喜好項目 option + shift + command + Q ・・・立即登出 option + command + 電源鈕 ・・・強制結束 command + Z ・・・還原/重作 command + Y ・・・快速預覽 command + O ・・・開啟選取項目 command + delete ・・・丟到垃圾桶 command + K ・・・連接伺服器 command + N ・・・新增Finder視窗 command + R ・・・顯示替身的原項目 command + tab ・・・切換應用程式 command + T ・・・加到側邊欄裡 command + [ ・・・返回 command + ] ・・・往前 老早就…把滑鼠…丟掉了