汉语 翻译 英语 小弟急得很!请高手帮忙啊！一定追加高分！！
请高手帮忙把下面的翻译成英语“运行“game.dsw”文件，完成链接和所有添加过程。直接运行出现相应的窗口根据相应的提示点击窗口“ControlPanel”的四个方向键，...
请高手帮忙把下面的翻译成英语
“
运行“game.dsw”文件，完成链接和所有添加过程。直接运行出现相应的窗口根据相应的提示点击窗口“Control Panel”的四个方向键，观察机器人的移动，做出相应的下一步动作。
1. 发现一个问题，把各个子程序写出来不是难事，困难的是完成项目的控制的文件，把所有的子程序连接在一起。
2. 第二个问题是写出程序不是什么大问题，问题的关键是完成链接，使程序能够正确运行，即改正所有写程序是出现的错误。
3. 第三个不是什么问题，但对写程序有一定影响，就是刚开始不能急着写程序，关键是把握程序的整体架构，考虑怎么样才能是程序更为简单化、实用化。以及更为美观，这里的美观不仅仅是程序做出来的界面好看，更为重要的是写的程序源代码要简洁明了，让别人更容易看懂，（一个最简单的也是最常见的就是头文件定义时要吧所有定义的对象对其，这或许在目前我们写的小程序短代码中不能充分体现出其价值所在，但将来不管是在代码的重用（就是简单的对其复制）还是代码进行改错，都更为直观的让人接受。）因为我们写代码不仅仅是给自己看的，是拿给老板看的，或者你以后不从事这个项目的开发，转手交给别人继续的话，那么让别人更容易看懂也是很重要的。这个时候我们不需要去考验别人的所谓“C++基本技术”，没那必要啊，能做干嘛不简简单单地做好呢？这点纯属个人意见，不一定符合大众需求。
4. 第四点就更加没那么重要的，也是朋友教我的，但确实有课借鉴之处：就是如果可能的话，最好把有关C++的插件安上，安装的主要目的当然是编程序是更为方便，可以给你很多提示；就算你现在用不着，安装这些插件还能给你更好的视觉效果，有些插件会使你的各种不同的对象定义颜色不一样，如果有必要需要寻找一些对象是更容易找到，有事一些简单的语法错误安装的插件都会给你用不同的颜色标注出来的，修改的时候也很方便。
关于写报告方面：
1. 确实是太讨厌那个类图表示了，反正太麻烦了。不过确实看上去比框图和程序模块表示好理解多了，也好看多了。
2. 个人认为还可以再加一个板块,就是在最后加一个“错误报告以及错误总结还有是怎么样解决的”，这样或许下一次会尽量避免同样的错误（尤其是一些基本错误）。
我还想说说一些个人学习C++的心里话：如果再让我选择一次，我不会选软件工程，这样简单的设计都会造成如此烦恼，真的进入更高领域会是一种怎样的场面，当然我不否认可能别的行业更困难，只是我没有去深究而已，但这并不表示我会放弃，我想我会坚持的。这只是牢骚话，或许将来我们进入更高领域会产生更大的兴趣异或更高的成就感，对将来还是有信心的。说这段话不是为了发牢骚，而是为了引入我的下面观点。
我的观点就是：爱一门专业就必须做到不管怎样都深究下去，你可以不喜欢，但你必须对你的专业深究下去。
这就是这次程序设计的一点点感受。
”
小弟痛哭流涕！倍加感谢！
追加高分！！！ 展开
“
运行“game.dsw”文件，完成链接和所有添加过程。直接运行出现相应的窗口根据相应的提示点击窗口“Control Panel”的四个方向键，观察机器人的移动，做出相应的下一步动作。
1. 发现一个问题，把各个子程序写出来不是难事，困难的是完成项目的控制的文件，把所有的子程序连接在一起。
2. 第二个问题是写出程序不是什么大问题，问题的关键是完成链接，使程序能够正确运行，即改正所有写程序是出现的错误。
3. 第三个不是什么问题，但对写程序有一定影响，就是刚开始不能急着写程序，关键是把握程序的整体架构，考虑怎么样才能是程序更为简单化、实用化。以及更为美观，这里的美观不仅仅是程序做出来的界面好看，更为重要的是写的程序源代码要简洁明了，让别人更容易看懂，（一个最简单的也是最常见的就是头文件定义时要吧所有定义的对象对其，这或许在目前我们写的小程序短代码中不能充分体现出其价值所在，但将来不管是在代码的重用（就是简单的对其复制）还是代码进行改错，都更为直观的让人接受。）因为我们写代码不仅仅是给自己看的，是拿给老板看的，或者你以后不从事这个项目的开发，转手交给别人继续的话，那么让别人更容易看懂也是很重要的。这个时候我们不需要去考验别人的所谓“C++基本技术”，没那必要啊，能做干嘛不简简单单地做好呢？这点纯属个人意见，不一定符合大众需求。
4. 第四点就更加没那么重要的，也是朋友教我的，但确实有课借鉴之处：就是如果可能的话，最好把有关C++的插件安上，安装的主要目的当然是编程序是更为方便，可以给你很多提示；就算你现在用不着，安装这些插件还能给你更好的视觉效果，有些插件会使你的各种不同的对象定义颜色不一样，如果有必要需要寻找一些对象是更容易找到，有事一些简单的语法错误安装的插件都会给你用不同的颜色标注出来的，修改的时候也很方便。
关于写报告方面：
1. 确实是太讨厌那个类图表示了，反正太麻烦了。不过确实看上去比框图和程序模块表示好理解多了，也好看多了。
2. 个人认为还可以再加一个板块,就是在最后加一个“错误报告以及错误总结还有是怎么样解决的”，这样或许下一次会尽量避免同样的错误（尤其是一些基本错误）。
我还想说说一些个人学习C++的心里话：如果再让我选择一次，我不会选软件工程，这样简单的设计都会造成如此烦恼，真的进入更高领域会是一种怎样的场面，当然我不否认可能别的行业更困难，只是我没有去深究而已，但这并不表示我会放弃，我想我会坚持的。这只是牢骚话，或许将来我们进入更高领域会产生更大的兴趣异或更高的成就感，对将来还是有信心的。说这段话不是为了发牢骚，而是为了引入我的下面观点。
我的观点就是：爱一门专业就必须做到不管怎样都深究下去，你可以不喜欢，但你必须对你的专业深究下去。
这就是这次程序设计的一点点感受。
”
小弟痛哭流涕！倍加感谢！
追加高分！！！ 展开
2个回答
展开全部
呵呵 这个就是：
Circulate a "game.dsw" document, complete a chain to connect with all add process.The direct movement appears homologous window way to click four direction keys of the window way"Control Panel" according to the hint for correspond, observe the ambulation of robot and do a next move action for correspond.
1. Discover a problem, writing out each statures procedure isn't a difficult matter, difficult is the document of control which completes item, link all sub- procedures together.
2. The second problem is to write a procedure is not what great problem, the key of problem completes a chain to connect and make procedure can correct movement, then correct all write procedure is the mistake for appear.
3. The third is not what problem, but contain certain influence towards writing procedure, be just start can't nasty write procedure, the key is the whole structure which holds procedure, consideration how be a procedure to more in brief turn, practical turn.And more beautiful, beauty here not only only is that the interface that the procedure does out is good-looking, more important is the procedure source code for write to want simple and direct clear, let other people more easily see understand, (1 most in brief is also the most familiar be a document definition want all definitions of object as to it's, this probably in currently we write of small procedure short code can't well the body appear it to be worth place, but future ignore is in the code of heavy use(be simple of as to it's make duplicate) still the code carry on correct mistake, all more for keep a let of view a person to accept.)Because we write code not only only give oneself see, take to see to the boss, perhaps you hereafter don't be engaged in the development of this item, turn to hand over to the words that the other people continue, so let other people more easily see understand also very important.We don't need to so-called"C++ basic technique" of test the other people this time, have no that necessity, can make why not does Chien in brief and singlely work well?This purely belongs to personal opinion and meet the public's need not necessarily.
4. The fourth didn't be so important more of, is also what friend teaches me, but really have the place that the lesson draw lessons from:Be if possible words, had better chase concerning the C++of plug-in Anne up, install of main purpose certainly is weave procedure is more convenient, can give you a lot of hints;Calculate your now needless, install these plug-ins can also give you the better visual effect, some plug-ins will make you of various different object definition the color be different, if necessary look for some objects is to more easily find out, occupy some simple phrasing mistakes install of the plug-ins all will give you mark with the different color of, modification of the time be also very convenient.
Concerning write a report:
1. Really disliked that type chart to show too much, anyway and too bothered.However really had a liking for to meant good comprehension to have another than frame diagram and procedure mold piece, all right saw many.
2. Personal think to can also add one more tectonic plate, be finally add a "the mistake report and the mistake tally up to still have to how solve of", so probably will as far as possible avoid a same mistake next time.(BE particularly some basic mistake)
I still mean to say to say some personal study Cs++of in the mind words:If again let me choose once, I will not choose software engineering, so simple designs all will result in thus vex, really getting into higher realm will be a kind of how of condition, certainly I don't deny the probably another profession is more difficult, just I have no go to probe just, but this doesn't mean that I will give up, I think that I will insist.This is just grievance words, probably in the future our getting into higher realm will produce greater interest different or higher sense of achievement and still have confidence to the future.Say these words aren't for the sake of the complainant, is but is for leading to go into my underneath standpoint.
My standpoint is:Love a profession have to attain aught and all the bottom of the probe to go to, you can not like, but you have to to you of professional probe the bottom go to.
This is a little of this program design to feel.
Circulate a "game.dsw" document, complete a chain to connect with all add process.The direct movement appears homologous window way to click four direction keys of the window way"Control Panel" according to the hint for correspond, observe the ambulation of robot and do a next move action for correspond.
1. Discover a problem, writing out each statures procedure isn't a difficult matter, difficult is the document of control which completes item, link all sub- procedures together.
2. The second problem is to write a procedure is not what great problem, the key of problem completes a chain to connect and make procedure can correct movement, then correct all write procedure is the mistake for appear.
3. The third is not what problem, but contain certain influence towards writing procedure, be just start can't nasty write procedure, the key is the whole structure which holds procedure, consideration how be a procedure to more in brief turn, practical turn.And more beautiful, beauty here not only only is that the interface that the procedure does out is good-looking, more important is the procedure source code for write to want simple and direct clear, let other people more easily see understand, (1 most in brief is also the most familiar be a document definition want all definitions of object as to it's, this probably in currently we write of small procedure short code can't well the body appear it to be worth place, but future ignore is in the code of heavy use(be simple of as to it's make duplicate) still the code carry on correct mistake, all more for keep a let of view a person to accept.)Because we write code not only only give oneself see, take to see to the boss, perhaps you hereafter don't be engaged in the development of this item, turn to hand over to the words that the other people continue, so let other people more easily see understand also very important.We don't need to so-called"C++ basic technique" of test the other people this time, have no that necessity, can make why not does Chien in brief and singlely work well?This purely belongs to personal opinion and meet the public's need not necessarily.
4. The fourth didn't be so important more of, is also what friend teaches me, but really have the place that the lesson draw lessons from:Be if possible words, had better chase concerning the C++of plug-in Anne up, install of main purpose certainly is weave procedure is more convenient, can give you a lot of hints;Calculate your now needless, install these plug-ins can also give you the better visual effect, some plug-ins will make you of various different object definition the color be different, if necessary look for some objects is to more easily find out, occupy some simple phrasing mistakes install of the plug-ins all will give you mark with the different color of, modification of the time be also very convenient.
Concerning write a report:
1. Really disliked that type chart to show too much, anyway and too bothered.However really had a liking for to meant good comprehension to have another than frame diagram and procedure mold piece, all right saw many.
2. Personal think to can also add one more tectonic plate, be finally add a "the mistake report and the mistake tally up to still have to how solve of", so probably will as far as possible avoid a same mistake next time.(BE particularly some basic mistake)
I still mean to say to say some personal study Cs++of in the mind words:If again let me choose once, I will not choose software engineering, so simple designs all will result in thus vex, really getting into higher realm will be a kind of how of condition, certainly I don't deny the probably another profession is more difficult, just I have no go to probe just, but this doesn't mean that I will give up, I think that I will insist.This is just grievance words, probably in the future our getting into higher realm will produce greater interest different or higher sense of achievement and still have confidence to the future.Say these words aren't for the sake of the complainant, is but is for leading to go into my underneath standpoint.
My standpoint is:Love a profession have to attain aught and all the bottom of the probe to go to, you can not like, but you have to to you of professional probe the bottom go to.
This is a little of this program design to feel.
本回答由提问者推荐
已赞过
已踩过<
评论
收起
你对这个回答的评价是？
展开全部
"Operation "game.dsw" document, completed all the links, and add process. Direct operations in the corresponding window in accordance with the corresponding prompt window click "Control Panel" of the four key to observe the robot's movement, the next step of action accordingly.
1. Discovered a problem, the various routines written is not difficult, difficult is the complete control of the project document, all the routines connected together.
2. The second problem is not a process to write any major problems, the key link is completed, so that the correct procedures can run, that is correct procedure is to write all the mistakes.
3. The third is not a problem, but to write a certain impact on the process, that is not the beginning of a hurry to write procedures, the key lies in grasping the overall framework procedure, consider how kind can be more simplified procedures, practical use. And more beautiful, here is not just the appearance of the interface procedures done good-looking, more important is to write the source code to be concise, to let others more easily understand, (the simplest and most common is The first document to define it all the definition of its target, perhaps in the current process we wrote a small short code does not adequately reflect their value lies, but whether in the future reuse of code (that is simple to copy) or Gaicuo code, is more intuitive acceptable.) Because we are not just writing code to see for himself, is the show to see the boss, or you do not engage in this project after the development, transfer it to others to continue , Then let others more easily understand is also very important. This time we do not need others to test the so-called "C + + basic technology" that did not need to, ah, do not simply doing to do it » This is purely personal opinion, not necessarily in line with public demand.
4. The fourth point is even less important, but also a friend taught me, but indeed of the draw lessons: that is, if possible, to the best of the C + + plug-in the placement, installation is of course the main purpose of procedures for Is more convenient and can give you a lot of tips, even if you do not need to install these plug-ins can give you a better visual effects, some plug-in will make you the object of the definition of various colors not the same, if there is Need to find some objects are more easily found, emergency simple grammatical mistakes installing the plug-in will give you a different color marking out the revised time also very convenient.
On the written reports:
1. Is really too disgusted that the plans that category, since too much trouble. But really looks than the diagram and procedures module that good understanding more and more attractive.
2. Personally think it could be coupled with a plate, is in the final and a "wrong and wrong report concluded there is how to solve the kind", so perhaps the next will try to avoid the same mistakes (especially some of the basic error).
I would also like to talk about some personal learning C + + the truth: If I choose once again, I will not elected software engineering, such a simple design that will cause trouble, really into the higher areas will be a scene of what, of course, I do not deny that other industries may be more difficult, but I did not go to the Shenjiu it does not mean that I will give up, I think I will adhere to. This is only to complain, perhaps the future we will have access to higher areas of greater interest in a different sense of achievement or higher in the future there is still confident. To say that this passage is not complaining about, but to introduce my point of view below.
My view is: love to be a professional in any case have to go Shenjiu, you may not like, but you must continue your professional Shenjiu.
This is the process of designing a little bit of experience.
1. Discovered a problem, the various routines written is not difficult, difficult is the complete control of the project document, all the routines connected together.
2. The second problem is not a process to write any major problems, the key link is completed, so that the correct procedures can run, that is correct procedure is to write all the mistakes.
3. The third is not a problem, but to write a certain impact on the process, that is not the beginning of a hurry to write procedures, the key lies in grasping the overall framework procedure, consider how kind can be more simplified procedures, practical use. And more beautiful, here is not just the appearance of the interface procedures done good-looking, more important is to write the source code to be concise, to let others more easily understand, (the simplest and most common is The first document to define it all the definition of its target, perhaps in the current process we wrote a small short code does not adequately reflect their value lies, but whether in the future reuse of code (that is simple to copy) or Gaicuo code, is more intuitive acceptable.) Because we are not just writing code to see for himself, is the show to see the boss, or you do not engage in this project after the development, transfer it to others to continue , Then let others more easily understand is also very important. This time we do not need others to test the so-called "C + + basic technology" that did not need to, ah, do not simply doing to do it » This is purely personal opinion, not necessarily in line with public demand.
4. The fourth point is even less important, but also a friend taught me, but indeed of the draw lessons: that is, if possible, to the best of the C + + plug-in the placement, installation is of course the main purpose of procedures for Is more convenient and can give you a lot of tips, even if you do not need to install these plug-ins can give you a better visual effects, some plug-in will make you the object of the definition of various colors not the same, if there is Need to find some objects are more easily found, emergency simple grammatical mistakes installing the plug-in will give you a different color marking out the revised time also very convenient.
On the written reports:
1. Is really too disgusted that the plans that category, since too much trouble. But really looks than the diagram and procedures module that good understanding more and more attractive.
2. Personally think it could be coupled with a plate, is in the final and a "wrong and wrong report concluded there is how to solve the kind", so perhaps the next will try to avoid the same mistakes (especially some of the basic error).
I would also like to talk about some personal learning C + + the truth: If I choose once again, I will not elected software engineering, such a simple design that will cause trouble, really into the higher areas will be a scene of what, of course, I do not deny that other industries may be more difficult, but I did not go to the Shenjiu it does not mean that I will give up, I think I will adhere to. This is only to complain, perhaps the future we will have access to higher areas of greater interest in a different sense of achievement or higher in the future there is still confident. To say that this passage is not complaining about, but to introduce my point of view below.
My view is: love to be a professional in any case have to go Shenjiu, you may not like, but you must continue your professional Shenjiu.
This is the process of designing a little bit of experience.
已赞过
已踩过<
评论
收起
你对这个回答的评价是？
推荐律师服务：
若未解决您的问题，请您详细描述您的问题，通过百度律临进行免费专业咨询
