約 2,387,361 件
https://w.atwiki.jp/eurail/pages/15.html
ここはRailway の Top です。
https://w.atwiki.jp/ohden/pages/286.html
RubyOnRails install ◆環境 Ubuntu 10.04 Ruby 1.8.7 RubyGems 1.3.7 ◆install ※注：現時点で以下のコマンドを打つとrails3.0.1が入るみたいです。2系を入れたい人は下の方まで読み進めて実行して下さい。 sudo gem install rails --include-dependencies INFO `gem install -y` is now default and will be removedINFO use --ignore-dependencies to install only the gems you listSuccessfully installed activesupport-3.0.1Successfully installed builder-2.1.2Successfully installed i18n-0.4.2Successfully installed activemodel-3.0.1Successfully installed rack-1.2.1Successfully installed rack-test-0.5.6Successfully installed rack-mount-0.6.13Successfully installed tzinfo-0.3.23Successfully installed abstract-1.0.0Successfully installed erubis-2.6.6Successfully installed actionpack-3.0.1Successfully installed arel-1.0.1Successfully installed activerecord-3.0.1Successfully installed activeresource-3.0.1Successfully installed mime-types-1.16Successfully installed polyglot-0.3.1Successfully installed treetop-1.4.8Successfully installed mail-2.2.9Successfully installed actionmailer-3.0.1Successfully installed rake-0.8.7Successfully installed thor-0.14.3Successfully installed railties-3.0.1Successfully installed bundler-1.0.3Successfully installed rails-3.0.124 gems installedInstalling ri documentation for activesupport-3.0.1...Installing ri documentation for builder-2.1.2...ERROR While generating documentation for builder-2.1.2... MESSAGE Unhandled special Special type=17, text=" !-- HI -- "... RDOC args --ri --op /usr/lib/ruby/gems/1.8/doc/builder-2.1.2/ri --title Builder -- Easy XML Building --main README --line-numbers --quiet lib CHANGES Rakefile README doc/releases/builder-1.2.4.rdoc doc/releases/builder-2.0.0.rdoc doc/releases/builder-2.1.1.rdoc --title builder-2.1.2 Documentation(continuing with the rest of the installation)Installing ri documentation for i18n-0.4.2...Installing ri documentation for activemodel-3.0.1...Installing ri documentation for rack-1.2.1...Installing ri documentation for rack-test-0.5.6...Installing ri documentation for rack-mount-0.6.13...Installing ri documentation for tzinfo-0.3.23...Installing ri documentation for abstract-1.0.0...Installing ri documentation for erubis-2.6.6...Installing ri documentation for actionpack-3.0.1...Installing ri documentation for arel-1.0.1...Installing ri documentation for activerecord-3.0.1...Installing ri documentation for activeresource-3.0.1...Installing ri documentation for mime-types-1.16...Installing ri documentation for polyglot-0.3.1...Installing ri documentation for treetop-1.4.8...Installing ri documentation for mail-2.2.9...Installing ri documentation for actionmailer-3.0.1...Installing ri documentation for rake-0.8.7...Installing ri documentation for thor-0.14.3...Installing ri documentation for railties-3.0.1...Installing ri documentation for bundler-1.0.3...Installing ri documentation for rails-3.0.1...File not found lib 順調に入ってると思ったら...止まった。(;´д｀) Error自体はドキュメントの入れ損ねっぽぃが... log見てると...なんかRails3の文字が... rails -v Rails 3.0.1 Σ(´Д｀;) Rails3が入りやがった...もうgemで取ってくると3が入るのね...orz 今回は2系を入れたいので、仕方がないのでやり直し。(´・ω・｀) って sudo gem uninstall rails したら...依存関係含めてuninstallしてくれる訳じゃないんだね...。・゜・(ノД｀)・゜・。 今回はまっ更な状態から入れたけぇえぇんじゃが... ある程度環境がある状態から入れとったらどんなことになったか分かりませんね... なんか良い方法あるんかな? gem list sudo gem uninstall abstract actionmailer actionpack …以下listで出た物全部の羅列 とりあえず、gem入れたトコまで戻しました。(ノ∀｀) で、今度はVer指定して実行。コレで2系の最新版が入るハズ。 sudo gem install rails --version " 3.0.0" --include-dependencies もしかして、rails入れる時に『gem1.3.6以上じゃねぇとダメ!!』とか言われとったのって...Rails3のせいなんじゃろうか...(;´д｀) 最初からVer指定しとったらあっさり入ったんじゃろうか...orz ⇒ その通りでした。apt-getでgem1.3.5が入った状態で上記コマンド実行することでrails2.3.10が無事入りました。 ただ、apt-getで入れたgemだと色々おかしな事が多くて結局手動で入れ直しましたけど... INFO `gem install -y` is now default and will be removedINFO use --ignore-dependencies to install only the gems you listSuccessfully installed rake-0.8.7Successfully installed activesupport-2.3.10Successfully installed activerecord-2.3.10Successfully installed rack-1.1.0Successfully installed actionpack-2.3.10Successfully installed actionmailer-2.3.10Successfully installed activeresource-2.3.10Successfully installed rails-2.3.108 gems installedInstalling ri documentation for rake-0.8.7...Installing ri documentation for activesupport-2.3.10...Installing ri documentation for activerecord-2.3.10...Installing ri documentation for rack-1.1.0...Installing ri documentation for actionpack-2.3.10...Installing ri documentation for actionmailer-2.3.10...Installing ri documentation for activeresource-2.3.10...Installing ri documentation for rails-2.3.10...Installing RDoc documentation for rake-0.8.7...Installing RDoc documentation for activesupport-2.3.10...Installing RDoc documentation for activerecord-2.3.10...Installing RDoc documentation for rack-1.1.0...Installing RDoc documentation for actionpack-2.3.10...Installing RDoc documentation for actionmailer-2.3.10...Installing RDoc documentation for activeresource-2.3.10...Installing RDoc documentation for rails-2.3.10... 今度はドキュメント含めて問題無く入ったみたいですね。(*＾ω＾) あとは、railsとDB接続のためにsqlite3-rubyってのが要るらしい。 sudo gem install sqlite3-ruby Building native extensions. This could take a while...Successfully installed sqlite3-ruby-1.3.21 gem installedInstalling ri documentation for sqlite3-ruby-1.3.2...No definition for libversionEnclosing class/module 'mSqlite3' for class Statement not knownInstalling RDoc documentation for sqlite3-ruby-1.3.2...No definition for libversionEnclosing class/module 'mSqlite3' for class Statement not known もし、sqlite3-rubyのinstallで失敗したら、 sudo apt-get install ruby-dev か sudo apt-get install ruby-full を実行後、再度gem installをやってみると上手く行くかもしれません。 で、これでRailsが動く環境になった。 rails -v Rails 2.3.10 が、何かやっとる内に失敗するパターンがあった... rails -v The program 'rails' is currently not installed. You can install it by typing sudo apt-get install rails って...『/var/lib/gems/1.8/bin』見てみたらちゃんとrails入っとるみたいなんじゃが... カレントdir移動して cd /var/lib/gems/1.8/bin ./rails -v Rails 2.3.10 間違いなく入ってるのに、シンボリックリンクだけ作られて無いって話!?謎だ...シンボリックリンクだけ作りゃえぇんかな？つか、こんな事RubyGems入れよる時にもあったな... Ruby関係じゃとコレ普通なんかな？ cd /usr/bin sudo ln -s /var/lib/gems/1.8/bin/rails rails で rails -v Rails 2.3.10 う～ん...表示されたが...えぇんじゃろうか？ 更新日： 2017年04月14日 (金) 09時04分17秒 名前 コメント すべてのコメントを見る
https://w.atwiki.jp/i2p3/pages/16.html
SusiMailとは I2PではI2Pネットワーク内でのみ送受信可能なメールサービス(SusiMail)が備わっています。簡単な登録を済ませてアカウントを作成するだけでI2Pさえ使えればいつでもどこでも使えます。 アカウント作成 http //127.0.0.1 7657/susimail/susimailにアクセスします。画面下部の【アカウント作成】をクリックします。表示されるまで10秒ほどお待ちください。 画面下部に次のようなフィールドがあります。 desired accountname @mail.i2p アカウント名を決めます。hogehogeと入力すればhogehoge@mail.i2pというメールアドレスを持つことになります。 既に使われているものは使えません。半角英数字のみ使用可能です。 desired password アカウントにログインするためのパスワードを入力します。半角英数字と_-#+~.;, の記号が使えます。 repeat password 確認のためもう一度同じパスワードを入力してください。 Your nick/handle メールアカウントの所有者のハンドルネームです。わざわざ実名で入力すると意味が無いので、こだわりがなければアカウント名と同じものを入力するといいでしょう。 Do you want to appear in the public addressbook? (Yes/No) チェックをつけるとメールアドレスとハンドルネームが公開されます。望まない場合はチェックをつけないでおきましょう。 【Proceed】をクリックしてアカウント作成は完了です。 アカウントログイン アカウントを作成したらメールの送受信が可能です。http //127.0.0.1 7657/susimail/susimailにアクセスして登録したとおりにアカウント名とパスワードを入力し、【ログイン】をクリックします。 非常にシンプルな画面かつ日本語表示されているので特にこれ以上の解説はしません。 注意 テスト用でアカウントを作る場合、テスト終了後はアカウントを削除してください。 通常のインターネットメール宛てに送信しないでください。匿名性が損なわれたり、メールが届かない可能性があります。 メールの多人数一斉送信、広告、誹謗中傷、スパム用途で使用しないでください。 SusiMailは発信者の匿名性を守りますが、内容は秘匿されません。メッセージが誰かに読まれて困る内容である場合はGPG等を使って終端間暗号化を行ってください。 受信したメールは放ったらかしにせず、できるだけ削除してください。 好ましくない利用をしていると管理者に判断された場合はアカウントが凍結される場合があります。
https://w.atwiki.jp/simai/pages/1003.html
What is simai's Notation? Location of Note Numbers Chart Definition and Ending Definition of BPM Length of NotesHow to Define the BPM How to Define the Length Divider TAP HOLD SLIDE (Basics Shapes) SLIDE (Multiple Chaining)Multiple SLIDE Chaining SLIDE TOUCH, TOUCH HOLD, Firework EffectTOUCH TOUCH HOLD Firework Effect EACH EX Notes Other NotationsChange Normal TAP to Star-shaped TAP Change Star-shaped TAP to Normal TAP Notations of Pseudo-TAP HOLD and Pseudo-TOUCH TOUCH HOLD Pseudo EACH SLIDE without Star-shaped TAP ※BREAK's notation is summarized in the description of TAP, HOLD, and SLIDE. What is simai's Notation? simai's notation was created by Celeca in 2013 for denoting the various types of notes appeared in maimai in plain text. By using combinations of half-width alphanumeric characters according to the rules explained below, any maimai charts can be accurately denoted using only plain text theoretically. This notation was first used in simai, a chart simulator for maimai which was first released on February 5, 2013, by Celeca. Since then, various simulators inspired by maimai have been created by volunteers, and the simai's notation has often been used as their chart notation. While Celeca will be closing simai to the public on February 5, 2023, there are still a certain number of users who use simai's notation, which is why Celeca decided to create this page. Although some simulators may have extended/further developed simai's notation in their implementation, only the notation rules officially defined as "simai's notation" are listed here. For those who want to create a simulator supporting simai's notation, it is recommended to make the simulator able to handle the notation rules on this page. Also, if you make such a simulator, Celeca would appreciate it if you could inform Celeca, who has the rights to the simai's notation. Although it is not necessary to inform, Celeca would be glad to hear from you. Location of Note Numbers First, please look at the image below. ⑧① ⑦ ② ⑥ ③ ⑤④ This shows the numbered location of maimai's buttons and sensor areas. They are numbered 1 to 8 in clockwise order. For sensor areas, each numbered location is further divided into 4 alphabet-numbered sensor areas as explained later. These numbers are used to represent notes' position, so be sure to remember this. Chart Definition and Ending A chart in simai's notation is composed by a series of commas and note notations. Every comma occupies a certain length of time. For example, when a comma has a length of 1 second and there are 10 commas in the chart, the chart will have a total length of (10 × 1s =) 10 seconds. In this case, 【1,1,1,1,1,1,1,1,1,1,1,1,1,】 represents a chart with 10 TAP notes at BUTTON-1, in the density of 1 note per second. Once the chart definition has begun, the chart can be defined using commas and note notations. However, for dealing with songs beginning with a fade-in section, a large number of commas would be needed. To save the efforts, there is a parameter which determines how many seconds should pass since the music begins playing when the chart begins at the first comma of the chart. In simai, this is determined by the parameter "first". Since the timing of the beginning of the chart should be determined precisely and accurately, a number with decimal places such as 1.234 seconds is usually used. If "first" is 1.234 seconds, then the same 【1,1,1,1,1,1,1,1,1,1,1,】 chart will have 10 TAP notes at BUTTON-1 at 1.234, 2.234, 3.234, ..., and 10.234 seconds, respectively, after the music begins playing. Just as a real sheet music has an ending notation, an ending should be defined in simai's notation, otherwise the music may continue playing endlessly. ※In simai, when the chart definition is longer than the length of the MP3, the chart still ends when the MP3 is played to the end The end of a chart is denoted by an "E". If "first" is 1.234 seconds and the chart definition is 【1,1,1,1,1,1,1,1,1,1,1,1,1,E】, the chart progresses until 10.234 seconds, as described above, and since the last comma also has a length of 1 second, the chart ends at 11.234 seconds. A chart definition in simai's notation is a long string with a large number of commas and note notations and then an "E" at the end. Line breaks, spaces, and tabs can be inserted in the middle of this string for better readability. These characters are ignored when the chart definition is being parsed. Definition of BPM Length of Notes In the previous examples, a comma has the length of 1 second. Although the following example has a BPM which make the calculation difficult on purpose, the length of a 16th note at 174 BPM is 0.08620689655 seconds. If such length is assigned to every comma, notes with the length of a 16th note at BPM 174 can be placed correctly. However, it would be troublesome to calculate this manually every time. The per-comma length can be changed by adjusting the BPM and/or the length divider by using the following notations. How to Define the BPM (120) Input the BPM value and enclose it in a pair of round brackets. Since the BPM value should be accurate, a number with decimal places can be used. How to Define the Length Divider {2} Input the dividing value and enclose it in a pair of curly brackets. E.g., "{4}" specifies the per-comma length to be a quarter note, "{8}" to be an 8th note, and "{1}" to be the whole note. A number with decimal places can be used but should be avoided because it may cause confusions. The BPM must be defined before the length divider. Because the length of notes cannot be calculated unless the BPM value is defined, when these two parameters are defined together, the length divider should come after the BPM. E.g., 【(120){2}】 specifies the per-comma length to be a half note at 120 BPM (exactly 1 second). If the BPM value is B and the length divider is T, the per-comma length can be calculated using the following formula Per-comma length = 240 / B / T (seconds). Depending on the music, there might be cases where charting to a special sound effect or so with unknown BPM is attempted or matching the vocals precisely is desired. In these cases, 【{#0.35}】, for example, can be used, and the per-comma length after this will become 0.35 seconds. When this notation is used, the per-comma length is already determined, so there is no need to specify the length divider. These two parameters can be defined anywhere when necessary. TAP From here on, note notations which can be added before a comma will be explained. TAP is the most basic note type in maimai. TAP's notation is very simple and is denoted by a button number followed by a comma. TAP that occurs at BUTTON-1 ... 【1,】 TAP that occurs at BUTTON-5 ... 【5,】 To change a TAP into a BREAK TAP, add a "b" before the comma, e.g., 【1b,】, 【5b,】. HOLD To place a HOLD, in addition to the button number, how long the button should be held down should also be specified. For example, for a hold to be held down for the length of a half note at 174 BPM, its held-down length would be 0.68965517241...... seconds. However, as with the BPM example above, this is also troublesome to calculate manually every time. If the current BPM is 174, then 【(174)】 has already been placed before. What is missing is the length divider, 【one half note】. The held-down length is written as 【[2 1]】 in simai's notation. The number before the colon denotes the length divider (half note), and the number after colon denotes the multiplier of the length divider (1×). Hence the total held-down length of such HOLD note is (1 × half note =) one half note. This way of denoting the length parameter is used in both HOLD and SLIDE. In the actual notation, a button number is specified, an "h" is specified after the button number to make it clear that the note is a HOLD, and then the held-down length is be specified after both of them. HOLD that occurs at BUTTON-5 with the held-down length of one half note ... 【5h[2 1],】 This is the basic notation. However, there might be cases where it is more convenient to specify the held-down length to be an exact number of seconds. HOLD that occurs at BUTTON-4 with a held-down length of 5.678 seconds ... 【4h[#5.678],】 HOLD that occurs at BUTTON-4 with a held-down length of one half note at 150 BPM ... 【4h[150#2 1],】 To change a HOLD into a BREAK HOLD, add a "b" after the "h" like 【5hb[2 1],】. It does not matter whether the "h" and the "b" are swapped, as in 【5bh[2 1],】. SLIDE (Basics Shapes) To place a SLIDE, many parameters should be specified, such as the starting and ending button numbers, how they are to be connected with the arrow track, and how long the tracing star is to move. Although SLIDE has gone through remarkable development in the history of maimai, and many features have been implemented to it, this section only describes the basic notation and the shapes of SLIDE. The format of SLIDE's basic notation is a combination of 【starting point, shape of track, ending point, and tracing length】. BUTTON-1 to BUTTON-4, straight shape, tracing length of 3 8th notes ... 【1-4[8 3],】 The 【[8 3]】 part at the end of the notation is specified using the same concept as the held-down length described for HOLD. For SLIDE, there is a waiting time after the approaching star-shaped TAP reaches the judgment line and before the tracing star actually begins to move. Specifically, it is one beat at the current BPM. The tracing length of the SLIDE and the waiting time for the tracing star to start moving can be directly specified in seconds as follows Status ... BUTTON-1 to BUTTON-4, straight shape, 120 BPM Waiting time is one beat at 160 BPM, tracing length is three 8th notes at 160 BPM ... 【1-4[160#8 3],】 Waiting time is one beat at 160 BPM, tracing length is 2 seconds ... 【1-4[160#2],】 Waiting time is 3 seconds, tracing length is 1.5 seconds ... 【1-4[3##1.5],】 Waiting time is 3 seconds, tracing length is three 8th notes at current BPM ... 【1-4[3##8 3],】 Waiting time is 3 seconds, tracing length is three 8th notes at 160 BPM ... 【1-4[3##160#8 3],】 The arrow track of a SLIDE has many possible shapes. "-" ... Straight shape Connects the start to the end in a straight line. " ", " ", "^" ... Arc shape Connects the start to the end along the circled judgment line. If the direction of travel is to the right, use " ". If left, use " ". If the distance is shorter than half the circle, "^" can be used and thinking of the direction is thus not needed. "v" ... v-shape Connects the start to the end through the screen center as the turning point in two straight lines. "p", "q" ... p-shape, q-shape Connects the start to the end while curving around the screen center. "s", "z" ... Thunderbolt shape Connects the start to the end with three short lines in the shape of a thunderbolt symbol (⚡). "pp", "qq" ... Grand p-shape, Grand q-shape Connects the start to the end while curving along an imaginary circle which is tangent to both the screen center and the circled judgment line. "V" ... Grand v-shape Connects the start to the end through a middle turning point in two straight lines. The line connecting the start to the middle turning point is always a short straight line. "w" ... Fan shape Connects the start to three ends in an expanding track in a shape similar to a folding hand fan. Three tracing stars going to each end are spawn for this SLIDE shape. For the "V" SLIDEs, the middle turning point is specified by an extra button number in addition to the button numbers of the starting and ending points. Starting point is BUTTON-1, turning point is BUTTON-3, ending point is BUTTON-5 ... 【1V35】 Every SLIDE has a constant tracing speed from the start to the end. To change the track of a SLIDE into a BREAK SLIDE, add a "b" after the "]" like 【1-4[8 3]b,】. The allowed positions of the ending point relative to the starting point are restricted by the shape of the SLIDE. The following table lists the possible combinations of starting and ending points of each SLIDE shape where the arrow track of the SLIDE can be drawn normally. SLIDE (Multiple Chaining) Multiple SLIDE Multiple SLIDE refers to a SLIDE note with two or more arrow tracks stating from a single star-shaped TAP. Each SLIDE arrow track is specified with its own set of parameters, since every set of parameters may be different for each SLIDE arrow track, except that the starting point is the same. The tracing speed can be different for each SLIDE arrow track, but these SLIDE arrow tracks are treated as EACH because their tracing stars begin to move at the same time. BUTTON-1 to BUTTON-4, straight shape, tracing length of 3 4th notes, plus BUTTON-1 to BUTTON-6, arc shape, tracing length of 5 8th notes ... 【1-4[4 3]*-6[8 5],】 After the starting button number at the beginning of the note notation, there is no need to repeat that button number. An "*" can be added after the second SLIDE arrow track to specify the third arrow track and so on. Chaining SLIDE Chaining SLIDE is a SLIDE note which composes of multiple SLIDE arrow tracks with their starting and ending points joined together and is treated as a single SLIDE arrow track. For example, the 【1V75】 arrow track is internally two SLIDE arrow tracks (【1-7】 and 【7-5】) combined into one. However, the combination is not limited to the grand V-shapes but can be any shape and two or more SLIDE arrow tracks joined together. No matter how long the chaining SLIDE is, the tracing speed is calculated from the tracing length to be a constant from the start to the end of tracing. BUTTON-1 to BUTTON-4 with straight shape, BUTTON-4 to BUTTON-7 with q-shape, BUTTON-7 to BUTTON-2 with straight shape, tracing length of two whole notes ... 【1-4q7-2[1 2],】 Specify a series of button numbers and SLIDE shapes and then specify the tracing length at the end. In the case of this SLIDE, the tracing star continues tracing at a constant speed from BUTTON-1 until it reaches BUTTON-2. However, there might be cases where different tracing lengths are desired for some of the SLIDE arrow tracks. In such cases, the tracing length for each SLIDE arrow track can be specified like 【1-4[2 1]q7[2 1]-2[1 1],】. However, be sure to specify the tracing speed for all individual SLIDE arrow tracks. Otherwise, an error may occur. To change it to BREAK SLIDE, add a "b" after the "]", which the same as for regular SLIDE. It is not possible to make only a section of chaining SLIDE into BREAK SLIDE. A chaining SLIDE note can only be either a normal SLIDE or a complete BREAK SLIDE. Therefore, even when different tracing speeds can be specified for some of the SLIDE arrow tracks, the "b" can be added only after the last "]". TOUCH, TOUCH HOLD, Firework Effect TOUCH In maimai DX series, there are 34 sensor areas on the screen which the player can touch. All of these can handle contact events, and SLIDEs require the contact events to be made in a specific order. Since maimai DX, there have been new types of notes that require directly touching the sensor. They are TOUCH and TOUCH HOLD. The sensor areas are also divided into five major groups Group A, located adjacent to the buttons; Group B, located between Group A and the center of screen; Group C, which is in charge of the center; Group D, which fills the space between the areas of Group A; and Group E, located slightly inward from Group D and adjacent to Group B. Group C is in the center and has 2 sensor areas, while each of the other groups has 8 sensor areas which are numbered in clockwise order. The following diagram shows the approximate location and positioning of the sensors. To place a TOUCH, the sensor number of the desired location is denoted in the same way as TAP. TOUCH that occurs at SENSOR-B1 ... 【B1,】 TOUCH that occurs at SENSOR-D4 ... 【D4,】 The sensor in the center is divided into two areas, C1 and C2. However, no TOUCHes appear separately for each of them, instead a TOUCH appears in the middle of the areas. Therefore, a TOUCH that occurs in the center can be denoted as 【C,】 without numbering. Denoting this as either 【C1,】 or 【C2,】 causes no errors and is treated the same as 【C,】. TOUCH HOLD TOUCH HOLD is a note that requires the sensor to be pressed and held. It is counted as "HOLD" in the play result. The awarded score is also the same as HOLD. This notation is a direct combination of TOUCH and HOLD. Just simply replace the button number of a HOLD with a sensor number. TOUCH HOLD that occurs at SENSOR-C with held-down length of 3 4th notes ... 【Ch[4 3],】 While TOUCH has appeared in all 34 sensor areas since DX FESTiVAL, TOUCH HOLD has only appeared on the C sensor since DX classic, at least until DX UNiVERSE PLUS. However, in simai's notation, TOUCH HOLD can appear anywhere if the sensor number is specified to be not C. Firework Effect Firework effect refers to the rainbow-colored radial effect that appears as if fireworks are spreading from a certain location when a specific TOUCH is touched. Since there was no official name for this effect at the time DX classic was launched, 3simai used the name "firework effect" for convenience. To enable firework effect, add an "f" after the sensor number. TOUCH that occurs at SENSOR-B7 with firework effect ... 【B7f,】 TOUCH HOLD that occurs at SENSOR-C with held-down length of two whole notes with firework effect ... 【Chf[1 2],】 In the case of TOUCH HOLD, when "h" for HOLD and "f" for FIREWORK effect are specified together, either "hf" or "fh" is fine. EACH If two or more notes occur at exactly the same time, they are treated as an EACH (BOTH). In the case of SLIDEs, even if their tracing length are different, they are still considered to be an EACH if their tracing stars begin to move at the same time. The notes treated as part of an EACH change their color to yellow, except for BREAK notes. An EACH is denoted by placing each composing note and separating each of them with a "/". TAP at BUTTON-1 and HOLD at BUTTON-8 with held-down length of one half note ... 【1/8h[2 1],】 Their order does not matter, so the notation 【8h[2 1]/1,】 works fine. However, for SLIDEs, for example, in 【1-4[8 1]/2-6[8 1],】, 【1-4[8 1]】 will be displayed as if it occurred before 【2-6[8 1]】. In other words, the SLIDE defined earlier will be displayed as if it occurred earlier. Three or more elements are also treated as an EACH and can be denoted as note A / note B / note C ... Only EACHes composing of only non-BREAK TAPs can be denoted like 【12】 without the "/". The "/" between each note cannot be omitted even if there is only a single non-TAP or BREAK note within the EACH. EX Notes TAP, HOLD, and BREAK can be specified as EX notes. EX notes are judged to be CRITICAL PERFECT if they are hit within the timing window of GOOD or better. Simulators that support only the autoplay mode always hit notes within the timing window of CRITICAL PERFECT regardless of the notes' EX setting. However, Celeca have defined the notation because demands are expected for the needs of reproducing official charts and/or charting for simulators that react to player's input. To change a note into an EX note, add an "x" in the similar manner for changing the notes into BREAKs. EX-TAP at BUTTON-1 ... 【1x,】 EX-HOLD at BUTTON-3 ... 【3hx[α β],】 EX-BREAK at BUTTON-5 ... 【5bx,】 EX-BREAK HOLD at BUTTON-7 ... 【7bxh[α β],】 When two or more of "x", "h", and "b" characters are specified together, they can be specified in any order. Other Notations The notations listed below allow charters to create special charts more easily, such as the UTAGE charts appeared in MURASAKi version. Change Normal TAP to Star-shaped TAP A BUTTON-1 TAP is denoted as 【1,】. But if a "$" is appended and denoted as 【1$,】, it changes into a star-shaped TAP that would appear if a SLIDE were placed. This can be used in conjunction with a BREAK TAP or an EX-TAP. When two or more of "$", "b", and "x" characters are specified together, they can be specified in any order. Also, if two "$" are stacked to form "$$", the star-shaped TAP rotates. Currently, the rotation speed of the star-shaped TAP is a pre-defined constant. Change Star-shaped TAP to Normal TAP When a SLIDE is described as 【1-5[8 1],】, the BUTTON-1 TAP automatically changes into a star-shaped TAP, but if a "@" is appended to the star-shaped TAP as in 【1@-5[8 1],】, this star-shaped TAP changes back into a normal TAP. The SLIDE is processed as usual, so the SLIDE arrow track appears to start from the normal TAP. This can be used in conjunction with a BREAK TAP or an EX-TAP too. When two or more of "@", "b", and "x" characters are specified together, they can be specified in any order. Notations of Pseudo-TAP HOLD and Pseudo-TOUCH TOUCH HOLD Assuming there is a HOLD denoted by 【3h[1 1],】, if its held-down length is shortened to the limit, the required held-down length becomes instant, and the visual length of the HOLD shrinks as well, giving it the appearance of a hexagonal TAP. Although such a HOLD can be denoted like 【3h[1000 1],】, it can be easily denoted by removing the held-down length notation like 【3h,】. The same notation can be used for TOUCH HOLD. For example, a TOUCH HOLD denoted as 【Ch,】 gives a judgment instantly when hit. This can be used to denote a pseudo TAP or pseudo TOUCH. Note that this notation is treated internally as if 【[1280 1]】 were specified. It is because the held-down length of such notes is implied to be set to the length of a 1280th note in the official fan book sold by SEGA. Pseudo EACH When denoting two TAPs that are almost but not exactly simultaneous, the notes in the nearby section would needed be very fine-tuned in this way {96} 1,2,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, {8} ~~~~~~ In the above example, the 96th note length divider was used for the timing gap, and specifying the notes to be closer to each other would be even harder. When strictly reproducing an official chart, this made it infeasible, and when creating a fan-made chart, this could be troublesome. In this case, 【1`2,】 can be used. It makes the BUTTON-2 TAP placed only slightly later than the BUTTON-1 TAP but still almost simultaneous. The BUTTON-2 TAP is processed internally as a TAP that is 1 millisecond later than the BUTTON-1 TAP. Since they are not exactly simultaneous to become a part of an EACH, the two TAPs do not turn yellow and do not count as an EACH on the play result. For example, in 【1`2`3/4,】, a BUTTON-2 TAP is placed 1 millisecond after the BUTTON-1 TAP, and an EACH composing of a BUTTON-3 TAP and a BUTTON-4 TAP is placed another 1 millisecond after the BUTTON-2 TAP. Note that, the "`" symbol can be entered by holding down Shift and pressing the "@" key right to the "P" key on a JIS layout keyboard and also by directly pressing the "`" key left to the "1" key on a US or UK layout keyboard. SLIDE without Star-shaped TAP When a SLIDE is placed, a star-shaped TAP normally always appears and approaches to the SLIDE's starting point, but this approaching star-shaped TAP can be eliminated. Assume that there is a SLIDE denoted by 【1-5[2 1],】. The tracing star fades in before starting to move ... 【1?-5[2 1],】 The tracing star does not fade in and suddenly appears when it begins to move ... 【1!-5[2 1],】 In both cases, the SLIDE arrow track fades in and the approaching star-shaped TAP does not appear. For creating a chart that letters, symbols, etc. are drawn using SLIDEs, it is recommended to use "?" to make it clear where to start tracing. For creating a chart with single-stroke SLIDEs, using "!" is recommended to avoid displaying extra stars on the screen. [pseudoEach] backtick (`) is located to the left of "1" on a US/UK layout keyboard. Its Alt code is 96. Alternatively you can copy and paste... -- cubruce1103 (2023-02-13 02 35 50) 名前 コメント
https://w.atwiki.jp/psmovie/pages/409.html
nihilsiesta nihilsiesta 主催：rpzn 編集：rpzn 公開日：2017/01/31 出演者 chama タロイモ kabu ace〆 hash AiMo GO_ONRONE Miyana Jujorous KRH モナチョ
https://w.atwiki.jp/kobuchi/pages/42.html
30000系通勤型電車 実車について 1996年(平成8年)より製造が開始された通勤型電車で、伊勢崎線系統の輸送力増強用として投入された。 当時計画されていた営団地下鉄(現・東京メトロ)半蔵門線への直通運用に対応できる仕様となっており、2002年(平成14年)より、直通対応機器を設置、 2003年より計画通りに営団半蔵門線ならびに東急田園都市線への直通運用に充当された。 車体は10030系を基本とした軽量構造のオールステンレス車体であるが、 扉間の側窓は2連のユニット窓とされ、さらに側扉の高さも1850mmに拡大されている。制御方式はIGBT素子を使用したVVVFインバータ制御である。 半蔵門線直通運用車ではあったが、同時に東武線内での運用も考慮して4両+6両の分割編成であった。 そのため直通時には先頭車の運転台同士の連結部分だけ定員が減少、その結果混雑に拍車をかける格好になってしまい、 直通先である東急田園都市線・地下鉄半蔵門線の利用者からは敬遠され、2006年より一部の編成を残して50050系と 交代する形で直通運用を譲り、再び地上用となった。 その後、東上線のATC化に伴う車輌改修の効率化を目的に一部編成は東上線へと転属しているが、その際に中間に封じ込められる先頭車はライトケースをカバーで覆い、 運転台の使用を取りやめている。 イラスト作成に当たって 地下鉄乗り入れ用にと鳴り物入りで登場したものの、いろんな事情があって乗り入れ先の乗客から嫌われまくった挙句、 地下鉄直通運用を外されてしまったなんともかわいそうな電車、というイメージが定着してしまった30000系ですが、 6+4の分割編成にしたことで、地上用としては使いやすい車両になっています。10000系列との分割・併合もこなせますし。 こいつらの格好いいところといえば、やはり前面の貫通幌を収納式にした点ですしょうね。 連結しないときは幌を貫通扉の周りにある溝に収納してしまって目立たなくする。 国鉄のキハ82などにも見られた構造ですが、なかなかいいデザイン処理だなと感服したものです。
https://w.atwiki.jp/maimuzo/pages/30.html
使い分けや逆引きは逆引きプラグイン参照 良さそうだったので調べてみたリストです。 annotate_models(テーブル構造をモデルにコメントとして挿入) acts_as_versioned(モデルのバージョニング。過去のデータの内容に戻せる) acts_as_paranoid(削除フラグ対応。いわゆる理論削除) acts_as_breadcrumbsプラグイン(Modelからパンクズリストを作る) active_formプラグイン(ARモデル以外の場合にもバリデーションを使える) SafeERBプラグイン(HTMLエスケープし忘れたときに警告を出す) acts_as_commentableプラグイン(モデルにコメント付けが可能になる) acts_as_ordered_treeプラグイン(acts_as_treeにpositionでの表示順指定) acts_as_favoriteプラグイン(お気に入りのモデル) MinusMORプラグイン(RJSの拡張?というか、RJSからRuby構文を取ったもの。とても書きやすい) default_orderプラグイン(デフォルトのorderを指定) 以下は良さそうだけど、まだ調査してないモノのリストです。 ちょっと便利だから入れと系(詳しくは調べてない。必要ならこの名称でググってみてください) Exception Notifier(nilなどで例外が発生したらメールで通知) acts_as_searchable(HyperEstraierで全文検索) acts_as_searchable_with_similarity(全文検索+類似検索) composite_primary_keys(ARで複合キーを扱う) ActiveCrypto(カラムの暗号化を透過的に扱う) riff(同じモデルのインスタンス間の差を取る) enforce_column_limits(最大文字数バリデーションを自動で行う) Spatial Adapter(PostGISを扱えるようになる。位置情報やるなら必須) settings(アプリケーション全体で使うような設定値を扱える) rails_pdf(railsからPDFを生成) upload_progress(アップロード時のプログレスバーを表示) ar_fixtures(テスト用のDBのデータを、実在のDBのデータから生成する) history(セッションにアクセス履歴(URL)を保存しておく) output_compression(Railsからの応答をgzip圧縮する) acts_as_threaded(BBSのスレッドのようなのモデルを1回で取得する) acts_as_network(snsのようなユーザ間の連携をモデリングできる) acts_as_most_popular(特定カラムを出現頻度が高い順にn個取ってくる) CAPTCHA(書き込み時に画像の内容を入力させるロボットはじきを付ける) acts_as_voteable(投票機能) validates_email_format_of(RFC 2822準拠のメアドバリデータ) mail-queue(ARをメールキューに見立ててcronなどからキックする) Token Generator(MD5を使ってトークンを作る機能をmixinする) acts_as_countable(使われた数(ページビューなど)をカウントする) Acts as Feeder(RSSを生成する) mimetype-fu(ファイルのバイナリを読んでMIME Typeを検出する???) LiveValidation(ブラウザ上でリアルタイムバリデーションを行う) enum_fu(ARに疑似enum機能を追加する) acts_as_list(並べ替えやソート機能) acts_as_habtm_list(並べ替えやソート機能を関連先によって制御) acts_as_tree(スレッド式BBSのようなツリー構造のモデルをサポート) Lipsiadmin(ExtJS2.0を使ったscaffold?) acts_as_sluggable(/articles/show/76-the-valueのようにurl_forで生成するURLを人間に読みやすい物に変える。てかアクセス解析時には必須だよね)
https://w.atwiki.jp/tojo/pages/12.html
□過去スレッド一覧 111-120 Part116 http //toki.2ch.net/test/read.cgi/rail/1300325498/ Part115 http //toki.2ch.net/test/read.cgi/rail/1300267018/ Part114 http //toki.2ch.net/test/read.cgi/rail/1300194519/ Part113 http //toki.2ch.net/test/read.cgi/rail/1300070248/ Part112 http //toki.2ch.net/test/read.cgi/rail/1299859512/ Part111 http //toki.2ch.net/test/read.cgi/rail/1298441757/ 101-110 Part110 http //toki.2ch.net/test/read.cgi/rail/1296697805/ Part109 http //toki.2ch.net/test/read.cgi/rail/1295871827/ Part108 http //toki.2ch.net/test/read.cgi/rail/1292335380/ Part107 http //toki.2ch.net/test/read.cgi/rail/1289279924/ Part106 http //toki.2ch.net/test/read.cgi/rail/1286937152/ Part105 http //toki.2ch.net/test/read.cgi/rail/1284292039/ Part104 http //toki.2ch.net/test/read.cgi/rail/1279206066/ Part103 http //anchorage.2ch.net/test/read.cgi/rail/1276092346/ Part102 http //anchorage.2ch.net/test/read.cgi/rail/1272251182/ Part101 http //anchorage.2ch.net/test/read.cgi/rail/1270456058/ 91-100 Part100 http //anchorage.2ch.net/test/read.cgi/rail/1267873424/ Part99 http //anchorage.2ch.net/test/read.cgi/rail/1265778912/ Part98 http //anchorage.2ch.net/test/read.cgi/rail/1261815663/ Part97 http //anchorage.2ch.net/test/read.cgi/rail/1260019788/ Part96 http //anchorage.2ch.net/test/read.cgi/rail/1258037756/ Part95 http //anchorage.2ch.net/test/read.cgi/rail/1256312263/ Part94 http //anchorage.2ch.net/test/read.cgi/rail/1255685202/ Part93 http //anchorage.2ch.net/test/read.cgi/rail/1255010884/ Part92 http //anchorage.2ch.net/test/read.cgi/rail/1253702929/ Part91 http //anchorage.2ch.net/test/read.cgi/rail/1251522816/ 81-90 Part90 http //anchorage.2ch.net/test/read.cgi/rail/1249185892/ Part89 http //anchorage.2ch.net/test/read.cgi/rail/1246341525/ Part88 http //anchorage.2ch.net/test/read.cgi/rail/1244354548/ Part87 http //anchorage.2ch.net/test/read.cgi/rail/1242397592/ Part86 http //anchorage.2ch.net/test/read.cgi/rail/1240704877/ Part85 http //anchorage.2ch.net/test/read.cgi/rail/1238953151/ Part84 http //anchorage.2ch.net/test/read.cgi/rail/1236946261/ Part83 http //anchorage.2ch.net/test/read.cgi/rail/1235518266/ Part82 http //anchorage.2ch.net/test/read.cgi/rail/1234590370/ Part81 http //anchorage.2ch.net/test/read.cgi/rail/1233741637/ 71-80 Part80 http //anchorage.2ch.net/test/read.cgi/rail/1232715996/ Part79 http //anchorage.2ch.net/test/read.cgi/rail/1231717635/ Part78 http //anchorage.2ch.net/test/read.cgi/rail/1230306640/ Part77 http //anchorage.2ch.net/test/read.cgi/rail/1229138524/ Part75 http //anchorage.2ch.net/test/read.cgi/rail/1226231978/(※実質Part76) Part75 http //anchorage.2ch.net/test/read.cgi/rail/1226231799/ Part74 http //anchorage.2ch.net/test/read.cgi/rail/1224763625/ Part73 http //anchorage.2ch.net/test/read.cgi/rail/1223127662/ Part72 http //gimpo.2ch.net/test/read.cgi/rail/1220749378/ Part71 http //hobby11.2ch.net/test/read.cgi/rail/1218723837/ 61-70 Part70 http //hobby11.2ch.net/test/read.cgi/rail/1216638674/ Part69 http //hobby11.2ch.net/test/read.cgi/rail/1215094732/ Part68 http //hobby11.2ch.net/test/read.cgi/rail/1214095064/ Part67 http //hobby11.2ch.net/test/read.cgi/rail/1213616437/ Part66 http //hobby11.2ch.net/test/read.cgi/rail/1213366150/ Part65 http //hobby11.2ch.net/test/read.cgi/rail/1212809998/ Part64 http //hobby11.2ch.net/test/read.cgi/rail/1211445986/ Part63 http //hobby11.2ch.net/test/read.cgi/rail/1211447925/ Part62 http //hobby11.2ch.net/test/read.cgi/rail/1210352018/ Part61 http //hobby11.2ch.net/test/read.cgi/rail/1208646003/ 51-60 Part60 http //hobby11.2ch.net/test/read.cgi/rail/1206862519/ Part59 http //hobby10.2ch.net/test/read.cgi/rail/1205825003/ Part57 http //hobby10.2ch.net/test/read.cgi/rail/1203304590/(※実質Part58) Part56 http //hobby10.2ch.net/test/read.cgi/rail/1198373736/(※実質Part57) Part56 http //hobby10.2ch.net/test/read.cgi/rail/1198401156/ Part55 http //hobby10.2ch.net/test/read.cgi/rail/1196475713/ Part54 http //hobby10.2ch.net/test/read.cgi/rail/1195651458/ Part53 http //hobby10.2ch.net/test/read.cgi/rail/1194085121/ Part52 http //hobby10.2ch.net/test/read.cgi/rail/1191422751/ Part51 http //hobby9.2ch.net/test/read.cgi/rail/1188775562/ 41-50 Part50 http //hobby9.2ch.net/test/read.cgi/rail/1185382362/ Part49 http //hobby9.2ch.net/test/read.cgi/rail/1182836769/ Part48 http //hobby9.2ch.net/test/read.cgi/rail/1180133905/ Part47 http //hobby9.2ch.net/test/read.cgi/rail/1178138918/ Part46 http //hobby9.2ch.net/test/read.cgi/rail/1175182428/ Part45 http //hobby9.2ch.net/test/read.cgi/rail/1172596845/ Part44 http //hobby9.2ch.net/test/read.cgi/rail/1170764769/ Part43 http //hobby9.2ch.net/test/read.cgi/rail/1168177580/ Part42 http //hobby9.2ch.net/test/read.cgi/rail/1166444824/ Part41 http //hobby7.2ch.net/test/read.cgi/rail/1164168587/ 31-40 Part40 http //hobby7.2ch.net/test/read.cgi/rail/1160894016/ Part39 http //hobby7.2ch.net/test/read.cgi/rail/1158372496/ Part38 http //hobby7.2ch.net/test/read.cgi/rail/1155816221/ Part37 http //hobby7.2ch.net/test/read.cgi/rail/1153540240/ Part36 http //hobby7.2ch.net/test/read.cgi/rail/1151682653/ Part35 http //hobby7.2ch.net/test/read.cgi/rail/1149172689/ Part34 http //hobby7.2ch.net/test/read.cgi/rail/1146991887/ Part33 http //hobby7.2ch.net/test/read.cgi/rail/1144596023/ Part31 http //hobby7.2ch.net/test/read.cgi/rail/1140620477/(※実質Part32) Part30 http //hobby7.2ch.net/test/read.cgi/rail/1140616499/(※実質Part31) 21-30 Part30 http //hobby7.2ch.net/test/read.cgi/rail/1137771259/ Part29 http //hobby7.2ch.net/test/read.cgi/rail/1135004014/ Part28 http //hobby7.2ch.net/test/read.cgi/rail/1132146524/ Part27 http //hobby7.2ch.net/test/read.cgi/rail/1129992295/ Part26 http //hobby7.2ch.net/test/read.cgi/rail/1127365419/ Part25 http //hobby7.2ch.net/test/read.cgi/rail/1124191430/ Part24 http //hobby7.2ch.net/test/read.cgi/rail/1121268132/ Part23 http //hobby7.2ch.net/test/read.cgi/rail/1117978962/ Part22 http //hobby7.2ch.net/test/read.cgi/rail/1114524314/ Part20 http //hobby7.2ch.net/test/read.cgi/rail/1110289004/(※実質Part21) 11-20 Part20 http //hobby7.2ch.net/test/read.cgi/rail/1105566716/ Part19 http //hobby7.2ch.net/test/read.cgi/rail/1102342618/ Part18 http //hobby6.2ch.net/test/read.cgi/rail/1099117568/ Part17 http //hobby6.2ch.net/test/read.cgi/rail/1094643426/ Part16 http //hobby6.2ch.net/test/read.cgi/rail/1090546736/ Part15 http //hobby6.2ch.net/test/read.cgi/rail/1086946386/ Part13 http //hobby6.2ch.net/test/read.cgi/rail/1078804087/(※実質Part14-2、複々線進行) Part13 http //hobby6.2ch.net/test/read.cgi/rail/1078784517/(※実質Part14、複々線進行) Part13 http //hobby3.2ch.net/test/read.cgi/rail/1075219704/ Part12 http //hobby3.2ch.net/test/read.cgi/rail/1071522345/ Part11 http //hobby3.2ch.net/test/read.cgi/rail/1068223017/ 1-10 Part10 http //hobby3.2ch.net/test/read.cgi/rail/1065177350/ Part9 http //hobby3.2ch.net/test/read.cgi/rail/1061334560/ Part8 http //hobby3.2ch.net/test/read.cgi/rail/1056533333/ Part7 http //hobby3.2ch.net/test/read.cgi/rail/1053495294/(※鯖飛びのため立て直し) Part6 http //hobby.2ch.net/test/read.cgi/rail/1047795742/ Part5 http //hobby.2ch.net/test/read.cgi/rail/1043110874/ Part4 http //hobby.2ch.net/test/read.cgi/rail/1038621189/ Part3 http //cocoa.2ch.net/test/read.cgi/rail/1034465669/ Part2 http //cocoa.2ch.net/test/read.cgi/rail/1030503622/ Part1 http //cocoa.2ch.net/test/read.cgi/rail/1019056206/ □過去スレ(train) 池袋から・・・ 東武東上線 2 http //curry.2ch.net/train/kako/1013/10134/1013485223.html 1 http //curry.2ch.net/train/kako/1008/10082/1008295294.html (東武)東上線スレッド 7 http //piza2.2ch.net/train/kako/1007/10077/1007724701.html 6 http //piza2.2ch.net/train/kako/1006/10065/1006516488.html 5 http //piza2.2ch.net/train/kako/1000/10003/1000390462.html 4 http //piza2.2ch.net/train/kako/996/996104393.html 3 http //piza.2ch.net/train/kako/995/995459331.html 2 http //piza.2ch.net/train/kako/988/988558771.html 1 http //piza.2ch.net/train/kako/981/981387263.html
https://w.atwiki.jp/ksmn/pages/130.html
鼎泰豊 東武池袋店 googlemap コメント東部百貨店13Fレストランフロアの台北料理。台湾に行った友人が本店に行ったらしく、そこが非常に美味しかったらしい。池袋に支店があるので行ってみることに。点心がメインのお店で、これは非常にレベルが高い。小籠包は薄皮の中にたっぷりと熱々のスープが封じ込まれている。さすがは世界10大レストランの支店といったところか。本店とは使ってる食材が違ったりするらしいが、詳しいことはわからない。日本では手に入らない食材という噂。評価A。（ymmt）
https://w.atwiki.jp/simai/pages/15.html
simaiとは simaiができること simaiができないこと 制作環境 動作環境 simaiとは simaiはCelecaが制作した、SEGAが開発しているフィジカル パフォーマンス系 音楽ゲーム"maimai"のシミュレータです。 譜面エディタは必要なく、MP3とメモ帳があれば譜面を作ることができます。 様々なプレーヤーがいわゆる「譜面確認動画」をアップロードされていますが、 HOLDを放置して始点がMISS扱いになった時点でそのHOLDが消えてしまったり、 SLIDEを放置し続けて表示される手のマークが邪魔になってしまったり、 SLIDEが大量に出現すると矢印が重なって見にくかったり……と、 ちょっと確認するには問題があります。 そこで、それらを解消し、ついでに得点が分かるようにしてしまおう！ということで制作しました。 simaiができること SLIDEを☆が流れる速度にぴったり沿って捌いてくれる SLIDEの手のマークが現れない HOLDをきっちり保ち続けてくれる 各リングの数・総ノーツ数・APスコア・現時点でのランク・完全理論値スコアを自動算出してくれる(ついでにEACHの数も) 再生中でもスピード(リング・タッチ)を変更することができる simaiができないこと 遊べない 制作環境 ParaFla! Version 1.39http //parafla.coaworks.jp/ Flash作成ソフトです。したがってsimai本体はswfファイルとなっております。 動作環境 Windows XP以降ならば動作すると思います。Macはよく分かりませんがよほど古くなければ多分動きます。 simaiはFlashソフトのため、拡張子が".swf"になっています。 そのため、SWFファイルを再生できるプレーヤーを用意する必要があります。 これに関しては、こちらの内容が参考になるかと思われます。 どこの事を言っているのか全く分かりません。あのサイトの何をDLすればいいんですか?? -- 名無しさん (2015-02-28 20 00 12) よろしくでーす -- らいか (2015-04-25 22 53 51) リンクが切れていてダウンロードができません -- MEGANE (2018-12-14 11 39 29) 名前 コメント