Page 実験（する）d for 同意／服従 with INDUSTRY (not MS-only) 基準s, using the 解放する／自由な, 公然と accessible validator at validator.w3.org|
このページはEtoJ逐語翻訳フィルタによって翻訳生成されました。 |
This page is one of several trying to help you get the most out of the splendid Open Office. They are 連合した with a larger 始める，決める concentrating on ooBase.
Remember that Open Office, 含むing ooBase, is 解放する／自由な! But don't let that fool you. And it's not new. Big organizations, 政府 and 非軍事の, are 可決する・採択するing it as their 基準 office 控訴... and saving million$, and still Getting The 職業 Done.
There's more about ooBase in the main 索引 to this 構成要素.
This page is "browser friendly". Make your browser window as wide as you want it. The text will flow nicely for you. It is easier to read in a 狭くする window. With most browsers, 圧力（をかける）ing 加える, minus or 無 while the 支配（する）／統制する 重要な (ctrl) is held 負かす／撃墜する will change the texts size. (大きくする, 減ずる, 回復する to default, それぞれ.) (This is more fully explained, and there's another tip, at my 力／強力にする Browsing page.)
Page contents © TK Boyd, Sheepdog ソフトウェア ®, 2/06-6/09.
What you are reading arose when I decided that an essay I was trying to 令状 was getting out of 手渡す. From that essay arose this and three others!
In this page, I will 始める，決める out the underlying 概念s you need for Open Office 大型の programming. Once you are （疑いを）晴らす about them, the next two pages to read are....
When you've mastered that, you will be ready for what started all of this....
"But I don't want to 輸出（する） CSV!", I hear you cry. Read the essay anyway. It will give you the 道具s to do lots and lots of fun things, 経由で 大型のs, with ooBase databases. It will also give you the 道具s to use ooWriter to create "programs", aka "使用／適用s". Maybe not the next chart 破産した／（警察が）手入れするing-ビデオ game... but almost anything I wrote in computer classes at university in the 70's could be written as a 大型の 力／強力にするd ooWriter 文書.
By the way, for those too timid to ask: CSV is a way of 蓄える／店ing "stuff" in a とじ込み／提出する. Guess what... I've written essays about that, too... but you don't need to understand CSV to follow all of the Good Stuff in these tutorials about 大型のs. CSV, for our needs, is just a way of "令状ing" something on a レコード.
Lastly, there are some 捨てるs left over after editing 過程 in the に引き続いて 文書....
If you want to 強固にする／合併する／制圧する your learning after reading the other essays, it might be helpful. It does 現在の a whole new 大型の example, too: a checkbox which changes its label.
To make your Open Office 使用／適用s do all of the things you could make them do, you need to understand.....
...and you need to learn to 適用する the general 原則s of the above within the Open Office 環境.
There! I said it "all" in just three lines! Be afraid, be very afraid: ーするために become an 見習い工 in the 事柄s I've just so succinctly 輪郭（を描く）d is not a simple 仕事. But it can be done! If you are in a hurry, skip over the next section...
Remember learning to ride a bike? If you don't know how, it seems impossible. Try, try, and try again and suddenly you flip into the "I can do this. I will always be able to do it. Why couldn't I yesterday?" 明言する／公表する.
Computer programming seems to be a 類似の learning 仕事. その上に, as students approach the 打開 point, they seem to become more and more dispirited, dejected. It is like running into the surf.... except that in learning programming, at a 確かな point a sudden 打開 occurs.... if you 港／避難所't give up when you got the "this is impossible" feeling.
=====
So much for the good news. There's also a bit of bad news: Not everyone has the 根底となる aptitude for programming.
In school, やめる rightly, even those pupils with no knack for mathematics are 要求するd to struggle with it for やめる some time. Some pupils do 井戸／弁護士席, many will always be weak in mathematical topics.
But we all need some mathematical fluency, hence the flogging of 近づく-dead horses. Sorry. I meant "激励", didn't I?
Not everyone needs to have programming 技術s. So if "your friend", has struggled and struggled, be 用意が出来ている to consider that maybe "he" just doesn't have the knack.
Society today would like us to believe that we are all created equal. While I would vigorously defend the 原則 that children with two left feet on the ends of two stubby 脚s should have an equal chance to have fun (if they think it is fun) playing (at) サッカー, I think we need to stop kidding ourselves, and deceiving the kids: There are those の中で us who aren't 削減（する） out for sports. And we are different from one another in our mental 能力s, too. Pretending さもなければ is foolish. There's a 指名する for 存在 out of touch with reality.
So! Now that we've dealt with those 問題／発行するs, 支援する to work....
I've been doing OOP for about 15 years now... and I still don't understand it, really. But I can get things done! (For proof of that （人命などを）奪う，主張する, see my freeware and shareware website... Please!)
To do OOP, you need to have some idea of....
You also need to master one of the features of 反対するs: they 存在する in 階層制度s. And lastly, you also need to distinguish classes of 反対するs and instances of 反対するs. (The last one isn't too hard!)
So! Let's dig into those topics....
When you are trying to see something in the forest at night, with no flashlight, you will have better results if you look just to one 味方する of the item which 利益／興味s you. (This is 予定 to the anatomy of the 支援する of your 注目する，もくろむ.) It takes a little practice, but once you have the trick of perceiving something that is 相殺する from where you are looking, the trick 作品 井戸／弁護士席. But look 直接／まっすぐに at the item of 利益／興味, and it may disappear again.
The 正確な meaning of "反対する" is a bit like this. Try not to "over-think" the question of "what is an 反対する". Be a little relaxed. Use the 軍隊. Don't "look at" it too hard.
An 反対する is.... an "反対する"! A thing. An （独立の）存在.
Forget programming for a moment. Just think about using any computer program you are familiar with as a mere 使用者. Let's, for instance, take your web browser.
The browser itself is an 反対する. The mouse pointer is an 反対する. The に引き続いて are all 反対するs....
So much for some 公正に／かなり obvious 反対するs. There are other 反対するs which are more abstract. Your printer is an 反対する, not only in the physical sense but also in the abstract sense of someplace to which you can send stuff. Your disk 運動 and other 貯蔵 装置s are 反対するs. The keyboard and your sound system are 反対するs.
Get the idea? Those examples will 十分である for the moment.
--- OBJECT HEIRACHIES
Part of the 推論する／理由 programmers turned to 反対する Oriented Programming (OOP) so enthusiastically was that OOP brings programming closer to the real world. Programming will always 伴う／関わる 存在 comfortable with intangible elements, but the OOP 視野 helps programmers visualize what they are 取引，協定ing with.
In OOP, 反対するs are hierarchical, just as they are in the real world.
What does that mean?
Forget about computers for a moment; think about a dog. A dog is an 反対する. That "反対する" is made up of other 反対するs: 長，率いる, 脚, tail, etc. Each of those are made up of 反対するs... for instance, the hind 脚 has femur, tib/fib, and paw. The paw has toes and claws.
If you were "making a dog" (creating a program) you could "build" it a bit at a time. You PLAN (design the program) the 全体にわたる 反対する, the dog, first ("最高の，を越す 負かす／撃墜する"), but then you ASSEMBLE (develop, "底（に届く） up") it by starting with the sub-sub-sub 議会s, and working "上向きs"... so:
You 計画（する）: It will have 長，率いる, 団体／死体, 脚s, tail. Then you go "負かす／撃墜する" a step, e.g. to 計画（する） the 脚: It will have femur, tib/fib, and paw. Then you go "負かす／撃墜する" a step, e.g. to 計画（する） the paw. You will go 負かす／撃墜する 類似の paths, some of them 支店ing, from each of the other main parts.
Then you 組み立てる／集結する, 底（に届く） up....
You make claws, and the other parts of paws. You 組み立てる／集結する those parts into paws. You make the femur 部隊s, the tib/fib 部隊s. Now you can 組み立てる／集結する the 脚s. You put the 長，率いる, the trunk together in a 類似の "底（に届く） up" way. And, finally, you can 組み立てる／集結する the four 脚 部隊s with the trunk 部隊, and the 長，率いる 部隊... (Oh yes: and a waggy tail, of course)... and you have a "dog"!
The beauty of this approach is that it makes it 平易な to concentrate on one bit at a time, get that "権利", in 孤立／分離, and thus you are able to manage something which, 全体にわたる, can be やめる 抱擁する. Divide and 征服する／打ち勝つ.
You can probably come up with your own examples of everyday 反対するs which can be broken 負かす／撃墜する into 構成要素 反対するs, which themselves can be broken 負かす／撃墜する again, etc.
Now let's get 支援する to computer programming.
The "反対するs" an OOP programmer 作品 with... and you will become familiar with them along the way of doing programming examples... are 類似の. As I said: It is 平易な to "over think" this one. Just 説得する yourself of the fact that 反対するs ARE. (Like love, 現実に, IS.)
--- OBJECTS: CLASSES AND INSTANCES
Don't worry too much about the next few paragraphs. Read them, but until you reach the "所有物／資産／財産s" 長，率いるing, just keep going....
Go 支援する to the dog analogy again. We all know what a dog is. The "general idea" of a dog isn't hard. We also know 明確な／細部 dogs... Fido, 位置／汚点／見つけ出す, Bella.
In computer programming, we speak of 反対する classes. This is "class" in the sense of "部類", or "type", NOT in the sense of "instructional 集会 of pupils."
There is a "class" called "dog". Also a "cat" class. These 反対するs are both in the "vertebrate" class, by the way, to take us 支援する to the 問題／発行する of 反対する 階層制度s for the moment. See how simple it is?
いつかs we want to speak of a particular dog, e.g. my good friend Fido. Fido is an 反対する... and he is an instance of the "dog" class. (And every "dog" 反対する is also an instance of the "vertebrate" class.)
In your programming, in working with 大型のs, you will have "薄暗い" 声明s at the start of each 大型の. ("薄暗い" from "dimension". You are telling the computer to 始める，決める some space aside. Nothing to do with "not 有望な", however 圧倒するd you may be feeling at the moment!)
A "薄暗い" 声明 will 準備する the way for working with an instance of a class of 反対する. We might have....
薄暗い AFriend as Dog
... to make an analogy. In some hypothetical language, that would 始める，決める up a variable called "AFriend" into which I could put an instances of a dog-type 反対する, e.g. Fido.
It will soon seem "natural" to you to think both of classes of 反対するs and of instances of 反対するs. Don't worry over-much about the distinction... but try to notice when your thinking of an instance of something, and when you are thinking about a class.
Whew... that's most of the hard stuff done. 所有物／資産／財産s and methods are いっそう少なく arcane.
反対するs have "所有物／資産／財産s". いつかs a 所有物／資産／財産 can be 始める，決める when you are high up in the 反対する 階層制度. The color of my favorite Labrador is 黒人／ボイコット. I can say that this instance of the "dog" 反対する is "黒人／ボイコット", and I am done. The 脚, paw and toe 反対するs "相続する" their color 所有物／資産／財産s from the higher level 反対する. In another 産む／飼育する of dog, the colors of the different parts might be different, in which 事例／患者 I can over-ride the 相続するd default for the color 所有物／資産／財産 of one of the subordinate 部隊s, and, for instance, "create" a dog with a white 長，率いる but a 黒人／ボイコット tail.
Besides 反対するs and their 所有物／資産／財産s, what's left to the story of OOP is methods. Methods are things that 反対するs can do. To stretch the analogy a bit, a "dog" 反対する has a "jump" method, a "run" method, a "sleep" method. The dog's throat 反対する has a "bark" method.
In my hypothetical language, you could 令状 the に引き続いて to create a dog, and get him to make a welcoming bark...
薄暗い oAnimal as 反対する
薄暗い oPartToUse as 反対する
oAnimal="Fido"
oPartToUse=oAnimal.getByName("Throat")
oPartToUse.Bark="Welcome"
oPartToUse.doBark
The 薄暗い 声明s create the variables to 持つ／拘留する the things we want to を取り引きする, 言及する to.
We put WHICH dog we want to use in oAnimal with oAnimal="Fido". We are 説 "Fill the oAnimal variable with that instance of the class "dog" which is called Fido.
The next line starts "oPartToUse=", which tells the computer that we're going to 明示する something to go in that variable. "getByName" is a "method" of all "dog" 反対するs, and 許すs us to "get" one of the dog's parts. After "oPartToUse=oAnimal.getByName("Throat")", we can 言及する to Fido's throat 簡単に by referring to oPartToUse, which is "持つ／拘留するing" Fido's throat.
You might guess that "oPartToUse.Bark" 暗示するs that "Bark" is a method of oPartToUse, but it isn't. It is a 所有物／資産／財産 of the 反対する. This is another place where you can over-think things. Just step 支援する, "use the 軍隊".... it "makes sense".... 結局. We're setting the type of bark that Fido's throat will 放出する as a result of the next line.
"doBark" is a method. When the program or 大型の gets to "oPartToUse.doBark", the doBark method is called, and we get the bark.
It will become intuitive to you, if you bang your 長，率いる against the 塀で囲む long enough.
To recap a 詳細（に述べる）: oPartToUse.Bark 言及するs to a 所有物／資産／財産, oPartToUse.doBark invokes a method. This "ambiguity" isn't as hard to live with as you might think.
Take a break! You have got through the worst of it! At least your first pass through the worst of it. The topics above are things that you will revisit again and again, consciously and sub-consciously. You were taught about 株ing as a toddler... but you're always 深くするing your understanding of the 概念. So too with the ideas of 反対するs, 所有物／資産／財産s, methods, 階層制度s, 相続物件.... even if they aren't as important.
Just one little thing before your break...
While the....
oPartToUse.Bark="Welcome" oPartToUse.doBark
... notation looks a little strange until you get used to it, it is 現実に やめる elegant. You いつかs find several elements strung together, too, so you might find something like....
oDocument=ThisDocument oDocument.Footer.Text.Font.Size=12
That is a made up example, but is plausible, assuming that the system can put a 文書 in an 反対する-type variable, and that the 反対する has a 所有物／資産／財産 called "Footer", which has a subordinate 所有物／資産／財産 called "Text" which has a subordinate 所有物／資産／財産 called "Font" which has a subordinate 所有物／資産／財産 called "Size"... which can be 始める，決める to 12! As I said, the example is hypothetical, but a line just like that could easily work in some 環境.
Whether you use Windows, Linux, or a Mac, you are operating within an "event driven 環境".
Windows and Linux are both event driven operating systems. Good news: This "events" thing is easier than the OOP stuff you've already struggled through.
When you have a 文書 on the 審査する, the computer isn't just waiting for you to 圧力（をかける） the next 重要な on the keyboard, as it might have been in The Good Old Days".
For instance, you may not only have the 文書 open, your email program may also be running. You may have the email program 始める，決める up to check your mailbox from time to time, and to 通知する you of new mail. Your computer's time-of-day clock is certainly ticking away. And the computer (more 特に, the operating system) is "watching" both the keyboard and the mouse to see if you are 圧力（をかける）ing 重要なs or moving or clicking the mouse.
Everything hinges on "events". 圧力（をかける）ing a 重要な gives rise to an event. Moving the mouse 生成するs at least one event, かもしれない several.
The operating system (OS) is continually watching for events. When it sees one, it checks the 明言する／公表する of sundry 関連した 所有物／資産／財産s, and invokes an event handler to 答える／応じる to the event. It also takes care of deciding which of the programs running in the computer should "see" the event happened.
There are 得点する／非難する／２０s of events which you can forget about. We'll come to them 簡潔に in a moment. But if you produce a 大型の, you will probably make it be the event handler for something. In the next essay in this series we will see how to attach a little 大型の that puts "Hello World" on the 審査する to the event handler for what should be done if the mouse button was clicked when the mouse pointer was over the button we put on our page. (See what I meant a moment ago when I said the OS "checks the 明言する／公表する of 関連した 所有物／資産／財産s"? The OS checked to see where the mouse was when it was clicked, and only invokes the "Hello World" code when the mouse is over the 権利 button. The 場所 of the mouse pointer is a 所有物／資産／財産 of the mouse 反対する.)
What about those events we can forget about? They are in two 部類s....
** Events like the one that watches the "tick tock" 深い within the OS and changes the time of day 陳列する，発揮するd on the 審査する once a minute
** Events which, for now, we are happy to have the OS を取り引きする in the "ordinary" way. We may 結局 tell the operating system to let the event handler in our program 答える／応じる to the event, but for now "the ordinary" is 十分な.
井戸／弁護士席.... I wish I could say I've "told you everything". I can't. My piano teacher tried to "tell me everything" when he said "You play the piano by 圧力（をかける）ing 負かす／撃墜する the 重要なs with your fingers". While that may be "everything", just knowing it doesn't mean you have the 技術s, or know enough of the 詳細（に述べる）s behind "everything". But it is important to know the 全体にわたる 形態／調整 of what you are trying to do.
You've had an introduction to the 必須の elements of making your computer do what you want it to. To make 進歩, keep the big ideas in mind....
Revisit this essay from time to time. You might be surprised at how something means more when you re-read it in a few weeks time, after 伸び（る）ing more experience with programming. Programming is an art, a （手先の）技術, not a science. Successful programmers bring more to their work than a mere しっかり掴む of the language's vocabulary and syntax. The artist's competence grows through practice.
The next thing for you to read, which ironically was the third thing I wrote in this creative burst, is the little tutorial about putting a button on an ooWriter 文書, and making the 文書 put a message on the 審査する when you click the button. Bach's B minor 集まり, it isn't, but it will 演習 the 技術s you need, and help you become familiar with 確かな basic terminology. If you are "an 専門家", it will take you 5 minutes... but will still be 価値（がある） doing, to put us on "the same page". Beginners will get even more from the 演習.
When you've done the "Hello World Button" tutorial, it will be time to 取り組む the "輸出（する） CSV With A 大型の" tutorial. To repeat what I said earlier: even if you don't want to 輸出（する） data as CSV, if you want to use 大型のs with ooBase, this is a tutorial you really shouldn't skip.
A little aside, as I am feeling sorry for myself and want a shoulder to cry on: All I 手配中の，お尋ね者 to do when this creative burst 掴むd me was to 令状 the "輸出（する）..." tutorial. It 証明するd to be a much larger 請け負うing than I 心配するd. I wrote something 抱擁する and unsatisfactory, which led to a big re-令状, resulting in what you are reading now, then the much re-written "輸出（する）..." tutorial, and finally (in the sequence of 創造) the "Button..." tutorial that helps you get from "beginner" work to the 中間の level topics in the "輸出（する）..." tutorial.) (Oh yes.... and the "Misc Thoughts" essay with "the left-overs".)(And すぐに thereafter three more essays arose when I had a relapse of creative fever.)
Thank you for reading. I hope you'll 圧力（をかける） on to the next two parts. Not "fun", but they will reward you in the long run.
The documentation can be 極端に 失望させるing. I am still unable to navigate it easily. Also, searches for things which I know are 現在の, e.g. "ConvertFromURL", fail to find the excellent 関連した pages.
You can try using something like...
場所／位置:wiki.services.openoffice.org ConvertFromURL
... as a Goggle search string. It turned up the 権利 page... along with 8 other 攻撃する，衝突するs.
* Guide to ooBasic.... the language of Open Office 大型のs...
The OpenOffice.org page where the ooBasic guide starts. The 欠陥d search engine remains a problem. You may find that digging in the "Runtime library" section turns up Good Stuff, depending on what you are looking for. (A lot of what I 手配中の，お尋ね者 was there.)
* Guide to OO API.... the "things" Open Office is built from, e.g. getByName. They (I'm pretty sure) underlie all of Open Office. How you get to them, 直接／まっすぐに, with ooBasic I'm not so sure about.
The "things" 含む what I would call 反対するs, methods and 所有物／資産／財産s. The nice people at Open Office use the 称する，呼ぶ／期間／用語 "service" for some things I think of... やめる かもしれない ignorantly... as 反対するs. Not everything I call an 反対する is a service. Some of the things I call methods they call 機能（する）／行事s. We both use "所有物／資産／財産" the same way... I think! The API guide also tells you about other useful things. If you want to become a 技術d OpenOffice programmer, it would probably be very wise to 試みる／企てる to master "What is a thingie", where "thingie" can equal...
Don't be 圧倒するd by that 名簿（に載せる）／表（にあげる）. It really isn't as bad as it seems.
The Guide is at this OpenOffice.org page
* Creating, saving, 負担ing 文書s... Although the に引き続いて is "just" a discussion within oooForum.org, it 会社にする／組み込むs a commendable tutorial which takes you through the basics. An excellent introduction.
oooForum.org essay on basic 文書 操作／手術s.
I dislike 'fancy' websites with more 関心 for a flashy 外見 than for good content. For a pretty picture, I can go to an art gallery. Of course, an attractive 場所／位置 WITH content deserves 賞賛する... as long as that pretty 直面する doesn't cost download time. In any 事例／患者....
I am trying to 現在の this 構成要素 in a 判型 which makes it 平易な for you to USE it. There are two 面s to that: The way it is 分裂（する） up, and the way it is 地位，任命するd. See the main 索引 to this 構成要素 for more （警察などへの）密告，告訴（状） about the way it is 分裂（する） up, and the way it is 地位，任命するd.
PLEASE >>> Click here to visit editor's Sheepdog ソフトウェア (tm) freeware, shareware pages <<< PLEASE
If you liked this ooBase tutorial, see the main 索引 for （警察などへの）密告，告訴（状） other help from the same author.
Editor's email 演説（する）／住所. Suggestions welcomed! - - - Want a 場所／位置 hosted, or email? I like 1&1's services.
Page 実験（する）d for 同意／服従 with INDUSTRY (not MS-only) 基準s, using the 解放する／自由な, 公然と accessible validator at validator.w3.org
. . . . . P a g e . . . E n d s . . . . .