[WPF program ents tour] class digoal under system. Windows. Program ents

[WPF program ents tour] class digoal under system. Windows. Program ents
Zhou yinhui

For work and personal interest, start to learn about the "document" (flowdocument, XPS...) in WPF ...).

there are two ways to learn new things:
first, let's take a rough look and then "learn with questions ", for example, if you need to encounter a problem, you can start to flip through the document, Google, solve the problem, and learn new things.
in another way, you can build a solid foundation of the basic knowledge before solving the problem, and then face the problem with confidence.
This has its own advantages and disadvantages. The former avoids the problem of "too many things to learn", but it is inevitable that some "Headaches, headaches, and pains" are solved ", in addition, it will become more blind when looking for answers. Maybe the class library has a corresponding method or can be done with a slight work, but I never think of it. In fact, to put it bluntly, in addition to some special industries, inspiration is more likely to come from solid foundations, rich experiences, rather than smart brains. After a while, I finally realized: Oh, no system learning. Therefore, I am more inclined to follow one of the following learning methods, thanks to the learning habits of the student age: before finishing my homework, I will spend an hour reviewing what the teacher said carefully, in this way, you can get the job done more easily, rather than by the job. Don't worry that the learning volume is too large, because the knowledge is segmented. For example, there are a lot of WPF things. You can't work after learning all of WPF, but at least before you get a button, you should understand all the attributes, methods, and events of the button, instead of checking the usage of the method only when a method is used. If so, it's hard for you to understand what a button can do.

We often say "development drives (driven) learning ". As a "driver", we have two ways of action:
First, it is a negative method (more common). learning and learning only (checking and checking only) What needs to be used in development will end after the problem is fixed. A simple example: You are responsible for displaying a WPF window, so you read the information and know that you should call the show () method, so you learned the show () method. But what about the showdialog () method? Maybe you will check it next time when you need to use the showdialog () method to solve the development problem. Without such a development problem, you will never know it, can you write "familiar with WPF" or "2 years of WPF development experience" in your resume? When interviewing some friends, we often encounter this embarrassing situation:
Me: I see XXX technology mentioned in your resume. Can we just talk about it?
Friend: I used this technology for a company project, and I have been using it for more than two years.
Me: Can you talk about YYY?
Friend: Oh, sorry, I seem to have heard of it, but we use less...
The second is to take the initiative to learn and use this item in projects. It reminds you that such a thing exists in the world (maybe you have never heard of it before ), in addition, this can solve a certain type of problem in reality. This is another best opportunity to combine personal growth and team output. This is the best way to apply what you have learned. Maybe you will think of more. When talking about this, you can imagine what it is like to take the initiative to learn.

So much nonsense, so it is not surprising to draw a class diagram before learning the document in WPF (because there are many classes involved, the class diagram is relatively large, and the whole graph can beArticleObtained in the attachment, as shown in the following figure :)

Download the entire class diagram: http://files.cnblogs.com/zhouyinhui/DocumentsNamespace.zip (this class diagram is edited with visual paradigm for UML 6.4 Professional Edition, where you can download the trial: http://www.visual-paradigm.com/product/vpuml)

In addition, the following textelement content model from the msdn document is also of reference value: