|
このページはEtoJ逐語翻訳フィルタによって翻訳生成されました。 |
This "tutorial" is mostly in the sourcecode that is 供給(する)d with it.
It was created 25 Jan 2019... and 反映するs many years of teaching programming, and of learning to 現在の 構成要素 on the web. And it is simple enough that it doesn't get into the 絡まるs that, 長,率いる hanging with shame, I have to 収容する/認める 存在する in some of my 解放する/自由な, oh by the way, offerings.
Fetch the .zip とじ込み/提出する, 負担 it into your Lazarus IDE, and dig around in it, reading the rems.
I hope that you will find your way around 比較して easily, and, while 調査/捜査するing the code, find useful tricks. More on what is there in a moment. First "the beef"...
I have 地位,任命するd a zip とじ込み/提出する with the sourcecode, and a 収集するd .exe... large 列s of that can be ignored, just used, if your main 利益/興味 is playing with encrypting/ decrypting text.
The code can be used on two levels... even three!
The "third" way is to use it, as it is 供給(する)d, to encrypt text. A 収集するd .exe とじ込み/提出する is 含むd, to make this 平易な for you. (And to let you "play" a bit with the "finished" app, to see what it's features are before you delve into the code.)
The as-供給(する)d encryption might give a ten year old 15 minutes pause... 2 minutes, if he/she had a eureka moment.
But! The first way to use the code is to ignore almost everything in it, and 単に 改訂する the sEncrypt and sDecrypt 機能(する)/行事s, which you will find at the 底(に届く) of the code. 支援する up the code as 供給(する)d before you tinker with it! Start slowly. Try something simple. (Walk before you run.)
The remaining way to use the code is as a boilerplate, or at least guide, for doing 確かな general things in your own work.
Inside the code, you will see an example of using an ini とじ込み/提出する to "remember" the dimensions and position of the app's window between uses.
Look at how the constants sPrgmName and sVers are used. I comment that practice to you in all Lazarus work, for keeping 跡をつける of what you are doing, and what 見解/翻訳/版 each of your 事業/計画(する)s (and each copy of each!) is in.
You'll see how to 負担 .txt とじ込み/提出するs to TMemo 反対するs, and to save the contents of 覚え書きs to text とじ込み/提出するs.
Look at how the "unnecessary" constants kPlain and kEncry helped make the code in LoadMemo(bWhich:byte); and SaveMemo(bWhich:byte); easier to follow. (And, oh by the way, 公式文書,認める how what might have taken four 手続きs was 減ずるd to only two 手続きs by making the 手続き more 一般に useful.
There's code to learn from that shows you how to work through the contents of a 覚え書き character by character.
Code that turns characters into numbers, and numbers into characters.
実験(する) on Tuesday!
Feedback... or just a "that was useful"... always welcome. Maybe this could be a starting point for an assignment to a class doing Lazarus programming? What ideas did students come up with?
Search across all my 場所/位置s with the Google search...
|
|
Page WILL BE 実験(する)d for 同意/服従 with INDUSTRY (not MS-only) 基準s, using the 解放する/自由な, 公然と accessible validator at validator.w3.org. Mostly passes. There were two "unknown せいにするs" in Google+ button code. Sigh.
....... P a g e . . . E n d s .....