How to use "TraversalSpec" in VISDK?
Althought "Programming Guide" has spent some words on it, I still feel a little confused.
Below link gives a good example. Noted
"Leveraging the VI3 SDK with .NET, part two"
http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1277591,00.html
http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1277590,00.html
" Certificates and the VMware Infrastructure 3 SDK"
http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1277589,00.html
2007年12月25日星期二
2007年12月24日星期一
Merry X'mas and Lonely X'mas
唉，Christmas Eve前一天分手，注定这个是个lonely的X'mas
公司的人一到下班时间早就闪光了，也就剩下我们这些孤家寡人的在这边坚守阵地。
不过，今天关于那个VI API的SDK一个demo总算搞定了，明天继续，把那些第一阶段的feature给搞定，嗯，就这样吧！
公司的人一到下班时间早就闪光了，也就剩下我们这些孤家寡人的在这边坚守阵地。
不过，今天关于那个VI API的SDK一个demo总算搞定了，明天继续，把那些第一阶段的feature给搞定，嗯，就这样吧！
2007年12月2日星期日
生日快乐！
今天是老妈的生日，老爸有点喝多了，在电话里东一句西一句的，我也一句句的回应着。说着说着，心情变的好差。
从小到大，在外人眼中我都是个听话的孩子，而且也看得出来，爸妈也一直都为这点感到很欣慰。可是人长大了，一直到今天，自己为他们做的事情太少了。
我是个好儿子吗？我不禁开始反复问自己这个问题。
我也希望能做一个人让他们骄傲的儿子，可是事实上，我连一些最基本的东西都没做到，平时不能陪在他们身边，更不用提到去照顾他们。而且还一直要他们为我操心，工作怎么样了，感情怎么样了。我心里很清楚，他们只是期望我能有个好的将来，我将来能幸福，都不为自己考虑什么。
写到这里，觉得自己特失败。
在将来的日子里，我一定要更加的努力的工作，学习！
不为别的，
只是为了他们，
一定要让他们都幸福！
从小到大，在外人眼中我都是个听话的孩子，而且也看得出来，爸妈也一直都为这点感到很欣慰。可是人长大了，一直到今天，自己为他们做的事情太少了。
我是个好儿子吗？我不禁开始反复问自己这个问题。
我也希望能做一个人让他们骄傲的儿子，可是事实上，我连一些最基本的东西都没做到，平时不能陪在他们身边，更不用提到去照顾他们。而且还一直要他们为我操心，工作怎么样了，感情怎么样了。我心里很清楚，他们只是期望我能有个好的将来，我将来能幸福，都不为自己考虑什么。
写到这里，觉得自己特失败。
在将来的日子里，我一定要更加的努力的工作，学习！
不为别的，
只是为了他们，
一定要让他们都幸福！
2007年4月2日星期一
Two Days UML Training
Last weekend, I've attend a UML training and learned something. List some key points here.
About UML diagram
To be honest, I don't learn as much as I expected from this training. The main cause is I'm not familiar with Object-oriented design, although I've read some books in this area. How to abstract classes from the business domain? How to create use case and how to make these class interact with each other... All of these needs time of practice.
So what's the follow-up action?
1. Try to think the project I've worked on in an O-O way and embody these thoughts with UML diragrams.
2. When playing with open-source project, always ask self several questions.
About UML diagram
- All the diagram could just reflect some aspect of the whole system from a specified angle, which the owner wants to express.
- It's just a tool to present your understanding about the system under design. obviously, diagram is easier way to get the whole picture. what's more, the process of drawing could help you to organize thoughts.
- The thoughts beneath the diagram is essential, which you can deduce using method of OOA/OOD. Design pattern is great experience pioneers have summarized up and stands time of testing. Consider these pattern when practising.
To be honest, I don't learn as much as I expected from this training. The main cause is I'm not familiar with Object-oriented design, although I've read some books in this area. How to abstract classes from the business domain? How to create use case and how to make these class interact with each other... All of these needs time of practice.
So what's the follow-up action?
1. Try to think the project I've worked on in an O-O way and embody these thoughts with UML diragrams.
2. When playing with open-source project, always ask self several questions.
- How is the problem domain split up, which is represented with various classes.
- Does it take some kind of design pattern?
- Is it possible to address the problem in another different or better way?
订阅：
博文 (Atom)