The function decomposition--android the time-sharing graph and the K-line graph thoughts

<span id="Label3"></p><p><p>Recently work extremely busy, has not updated the blog for a long time, the total feeling if you do not take the time to summarize things, minutes will be lazy state to hit. At the same time, I hope that students will remember that if you have decided to adhere to certain correct things, such as the end of a chapter of the word, read a book or run out how many kilometers and so on, you have to stick to it, do not easily defeated by their laziness and slack ...</p></p><p><p>Today is about how to solve some of the big bang-like problems, I think of all the problems encountered in the past, can be divided into a trivial small problem. So I think of the management of the "split" in the content, <span style="line-height: 1.5;">is any complex things can be split into a simple one can be done by anyone to the Point. </span></p></p><p><p>The background of these problems is that because of the current development of a securities software, so it is unavoidable to draw the relevant candlestick chart and time-sharing Charts. And this arduous task fell on my hand. As a programmer, under normal circumstances, all do not know to ask Google. I'm not the exception to ask ... There are a lot of drawing candlestick charts and all kinds of graphic demo and GitHub above the relevant source Code. It was very exciting at First. For the simple function realization, in Google really want to take what to take! But when you have the UI draft, it's a matter of another story ...</p></p><p><p>You will find that unless you have a really good luck, just meet a demo with your UI requirements, and then communicate with the product, the basic is Finished. On the contrary, most of the cases, especially those such as drawing, are completely useless. so, either you find a demo source code, and then slowly study, a little feel or want to modify it yourself, or you are directly on the battlefield, starting from scratch slowly carved. There is a time problem, have to pay attention to: in the end which can be faster development completed?!</p></p><p><p>If you find that reading the demo source directly and then modifying it faster, you should naturally choose the former, because it is more important than anything to quickly complete the established development tasks. And what I'm going to say is, when you find out that the source code is really hard to melt into what you want, maybe you can think through the latter--and slowly decompose this seemingly huge task.</p></p><p><p>It's like drawing a candlestick chart, it's all torn down! You find that the whole candlestick chart is made up of straight lines, curves, and rectangles, so your problem becomes you can draw straight lines, curves, rectangles? When you think about it, You're already full of confidence because you'll know how to draw straight curves and rectangles through android, just by searching. And if you can still not solve, then continue to split, you will find that the rectangle is actually composed of straight lines, so the problem is reduced to become, draw straight lines and curves of the problem!</p></p><p><p>I don't know about you, how do you feel when you see this process of thinking? But for me, this really gives me a lot of confidence, the solution to a problem, from the beginning to the point of evolution to a step-by-step state! perhaps, you see this article, is looking for a K line chart or time-sharing map of the source code, I can also give you these source code, but in fact, you still do not understand, because you are in essence, want a completely conform to your UI design image, and this no matter how you wish, so really suggest you think about this problem , and then draw them yourself, and you'll experience the freedom to do it, whether it's after speed optimization or a variety of customized operations.</p></p><p><p>The function decomposition--android the time-sharing graph and the K-line graph thoughts</p></p></span>