Windows 8 game development tutorial-opening part

Http://www.cnblogs.com/crazylights/archive/2011/09/26/2190723.html

I am going to start writing a Win8 game development tutorial. Now let's sort out the ideas here.

There are a lot of problems that need to be explained in the beginning. First, try to write them down one by one.

 

1. What is the basis for reading this tutorial?

2. What kind of demo can this tutorial bring about? What kind of game can be developed after the end?

3. What knowledge is covered in this tutorial, And what languages and tools are used for development?

 

Question 1: the first is the encoding capability. This is not a copy.ProgramC # is the main development language. You must have a certain understanding of C. Second, some hands-on capabilities, sometimes requires a certain degree of C ++ development, will provide detailedCodeIf you skip the Code, at least you should be able to compile and use them. Third, the spirit of exploration focuses on Win8 game development. knowledge beyond the topic must have more suitable materials for understanding and learning.

 

Question 2: This tutorial will not bring about a perfect game, but it will certainly show you all aspects required to develop a Win8 Metro game. It brings a series of examples of 2D 3D drawing, music sound effects, multi-touch, resource, thread management, and demonstration projects that put multiple examples together, select a simple game method to illustrate how to put these examples into a game. Technically, you can develop any game, but it's just a little short. Your continuous efforts.

 

Question 3:

This tutorial will cover someAlgorithm, Data structure, graphics.

Development tools include DirectX, winrt, XAML, XML, and winmd.

The development language tools involve C #, C ++,

Environment requirements: Windows 8, vs2011 for windows8

Other tools:

Graphics and model processing tools: Simply put, they are 2D and 3D art tools. Without an accident, these tools must be used by programmers. Art specifications should be provided by programmers who use relevant resources, of course, you must first be familiar with it. There is no unnecessary trouble. Although I have basically used some big-name art tools, Considering copyright issues, free tools are used in the tutorials. You can use the big-name tools to do the same job.

Version Management Tools: Even if you only write some exercises on the local machine, you are strongly required to use version management tools (such as SVN) to save each step of your operations, it takes a few hours to learn a version management tool. Stick to it.

Text comparison tool: extends version management and checks the differences between the two versions. It is a very practical method. If you do not know what is wrong with the change, check the previous version.

Work record tools: Text, email, blog, whatever you like, record your progress, review frequently, stick to the plan, and stick to the plan. Otherwise, it is almost impossible to complete a job that takes more than 10 days. 30 jobs your brain will twist him into a twist, but the record is only half a page on the paper, and it is easy to organize. You only need to focus on today's things today, don't let the brain break down on this matter. We have more things to think about.

 

Well, there are a lot of tools. I won't tell you how to use the tool in the tutorial. I will try my best to tell you which tools to use in the tutorial, however, the habit of using tools depends on you.

 

Let's start with the focus

Why do we need a Windows 8 game development tutorial?

The main interface used by Windows 8 is Metro, and the traditional interface is desktop, which is only supported by Win8 desktop edition and serves as a compatibility and transition to the old operating system. The development of Metro UI programs started with Windows Phone 7, which is quite different from the Development of Windows desktop programs in the past. In addition, it is quite different from Windows Phone 7, and there is even a saying that Windows Phone 8 will be upgraded to a page similar to Windows 8.

The winmd Interface format is introduced. The addition of C ++, the disadvantage of DOTNET performance, and the functions not provided in winrt and DOTNET ramework can be easily supplemented. As a new interface, winmd does not have enough information. This tutorial will also serve as winmd materials.

What is new?

Metro UI:The concept of window is abandoned. The basic UI format is organized by control, and is organized by XAML, developed from WPF-> Silverlight-> Metro UI.

Winmd:The new interface technology, such as the mixed race between COM and DOTNET, can directly call the winmd interface using C ++, DOTNET, and Js. Currently, both C ++ and DOTNET can be used to produce winmd interface class libraries. DOTNET can produce cross-platform winmd interface class libraries. c ++ needs to be compiled for different platforms.

Windows kits:Non-Brand new. A large part comes from Windows SDK WIN32API, C ++ header file, Lib, and winrt. This time, we provide lib (x86 x64 arm) on three platforms ), not all Win32 APIs are included. Metro UI can only use Windows kit. Do not try to use traditional Win32 APIs.

Winrt:Windows APIs packaged with the winmd interface in the object-oriented form basically replace most of the DOTNET framework or the DOTNET framework with the winmd interface. Now C # develops Metro UI applications, and most calls are winrt. For C ++ and JS application development, you also need to call winrt.

By comparing the data with ease, we can see that most of the functions of the DOTNET framework are reduced, and winrt makes up the slimming part, all the windows namespaces called during development are winmd interfaces, which are winrt.

C ++ CX:C ++ and winmd communication extensions, typical Syntax "^" Ref new XXX"

 

It seems terrible. There are a lot of new things. In fact, you don't have to worry about what winmd winrt is. They are all APIs, and they are all organized in namespaces when called, as a class library, the extension is winmd. Actually, there is no difference between the DOTNET class library and the winmd class library in terms of encoding. The Lib in winrt is also a standard C ++ class library. There is no difference between the Linked Library and C ++.

 

What old ones are available?

C ++ development knowledge remains unchanged and remains unchanged. The only difference is that it provides three platforms with more lib than arm.

C # And DOTNET development knowledge has not changed, and the DOTNET framework still works, but some of them are replaced by winrt. In addition, the alternative part does not affect your development. At most, the namespace is different. Please try again.

DirectX knowledge. Currently, no drawing API is provided in winrt. The drawing API is deleted in DOTNET framework, and xNa has not logged on to Win8. Therefore, using C ++ to call dx to develop the graphic part has become an inevitable choice for developing Windows 8 games.

From the introduction of the winmd interface, hybrid programming becomes easier. c ++ and DirectX accumulate a large number of games and engines. We can boldly predict that xna4 may be the last version, xna5 may appear in the form of winmd interface and return to the MDX mode. As the winmd interface version of DX, xNa is no longer the only solution on the platform according to this development trend, he will face numerous competitions, including this tutorial pai_^.

We can also boldly predict that winmd will definitely log on to Windows Phone and Xbox in such a gorgeous form. Then, DOTNET's xNa will gradually become optional, and then there will be no more, xna5 may be converted into DX winmd packaging.

 

If you find anything wrong, ask for positive criticism.

Coming soon, introduce Metro UI with code next week

Http://www.cnblogs.com/crazylights/archive/2011/09/26/2190723.html

I am going to start writing a Win8 game development tutorial. Now let's sort out the ideas here.

There are a lot of problems that need to be explained in the beginning. First, try to write them down one by one.

 

1. What is the basis for reading this tutorial?

2. What kind of demo can this tutorial bring about? What kind of game can be developed after the end?

3. What knowledge is covered in this tutorial, And what languages and tools are used for development?

 

Question 1: The first is coding capability. This is not a program teaching material. The encoding basics are not described. If C # is selected as the main development language, you must have a certain understanding of C. Second, some hands-on capabilities, sometimes requires a certain degree of C ++ development, will provide detailed code, if you skip the Code, at least you should be able to compile them, use them. Third, the spirit of exploration focuses on Win8 game development. knowledge beyond the topic must have more suitable materials for understanding and learning.

 

Question 2: This tutorial will not bring about a perfect game, but it will certainly show you all aspects required to develop a Win8 Metro game. It brings a series of examples of 2D 3D drawing, music sound effects, multi-touch, resource, thread management, and demonstration projects that put multiple examples together, select a simple game method to illustrate how to put these examples into a game. Technically, you can develop any game, but it's just a little short. Your continuous efforts.

 

Question 3:

This tutorial covers certain algorithms, data structures, and graphics.

Development tools include DirectX, winrt, XAML, XML, and winmd.

The development language tools involve C #, C ++,

Environment requirements: Windows 8, vs2011 for windows8

Other tools:

Graphics and model processing tools: Simply put, they are 2D and 3D art tools. Without an accident, these tools must be used by programmers. Art specifications should be provided by programmers who use relevant resources, of course, you must first be familiar with it. There is no unnecessary trouble. Although I have basically used some big-name art tools, Considering copyright issues, free tools are used in the tutorials. You can use the big-name tools to do the same job.

Version Management Tools: Even if you only write some exercises on the local machine, you are strongly required to use version management tools (such as SVN) to save each step of your operations, it takes a few hours to learn a version management tool. Stick to it.

Text comparison tool: extends version management and checks the differences between the two versions. It is a very practical method. If you do not know what is wrong with the change, check the previous version.

Work record tools: Text, email, blog, whatever you like, record your progress, review frequently, stick to the plan, and stick to the plan. Otherwise, it is almost impossible to complete a job that takes more than 10 days. 30 jobs your brain will twist him into a twist, but the record is only half a page on the paper, and it is easy to organize. You only need to focus on today's things today, don't let the brain break down on this matter. We have more things to think about.

 

Well, there are a lot of tools. I won't tell you how to use the tool in the tutorial. I will try my best to tell you which tools to use in the tutorial, however, the habit of using tools depends on you.

 

Let's start with the focus

Why do we need a Windows 8 game development tutorial?

The main interface used by Windows 8 is Metro, and the traditional interface is desktop, which is only supported by Win8 desktop edition and serves as a compatibility and transition to the old operating system. The development of Metro UI programs started with Windows Phone 7, which is quite different from the Development of Windows desktop programs in the past. In addition, it is quite different from Windows Phone 7, and there is even a saying that Windows Phone 8 will be upgraded to a page similar to Windows 8.

The winmd Interface format is introduced. The addition of C ++, the disadvantage of DOTNET performance, and the functions not provided in winrt and DOTNET ramework can be easily supplemented. As a new interface, winmd does not have enough information. This tutorial will also serve as winmd materials.

What is new?

Metro UI:The concept of window is abandoned. The basic UI format is organized by control, and is organized by XAML, developed from WPF-> Silverlight-> Metro UI.

Winmd:The new interface technology, such as the mixed race between COM and DOTNET, can directly call the winmd interface using C ++, DOTNET, and Js. Currently, both C ++ and DOTNET can be used to produce winmd interface class libraries. DOTNET can produce cross-platform winmd interface class libraries. c ++ needs to be compiled for different platforms.

Windows kits:Non-Brand new. A large part comes from Windows SDK WIN32API, C ++ header file, Lib, and winrt. This time, we provide lib (x86 x64 arm) on three platforms ), not all Win32 APIs are included. Metro UI can only use Windows kit. Do not try to use traditional Win32 APIs.

Winrt:Windows APIs packaged with the winmd interface in the object-oriented form basically replace most of the DOTNET framework or the DOTNET framework with the winmd interface. Now C # develops Metro UI applications, and most calls are winrt. For C ++ and JS application development, you also need to call winrt.

By comparing the data with ease, we can see that most of the functions of the DOTNET framework are reduced, and winrt makes up the slimming part, all the windows namespaces called during development are winmd interfaces, which are winrt.

C ++ CX:C ++ and winmd communication extensions, typical Syntax "^" Ref new XXX"

 

It seems terrible. There are a lot of new things. In fact, you don't have to worry about what winmd winrt is. They are all APIs, and they are all organized in namespaces when called, as a class library, the extension is winmd. Actually, there is no difference between the DOTNET class library and the winmd class library in terms of encoding. The Lib in winrt is also a standard C ++ class library. There is no difference between the Linked Library and C ++.

 

What old ones are available?

C ++ development knowledge remains unchanged and remains unchanged. The only difference is that it provides three platforms with more lib than arm.

C # And DOTNET development knowledge has not changed, and the DOTNET framework still works, but some of them are replaced by winrt. In addition, the alternative part does not affect your development. At most, the namespace is different. Please try again.

DirectX knowledge. Currently, no drawing API is provided in winrt. The drawing API is deleted in DOTNET framework, and xNa has not logged on to Win8. Therefore, using C ++ to call dx to develop the graphic part has become an inevitable choice for developing Windows 8 games.

From the introduction of the winmd interface, hybrid programming becomes easier. c ++ and DirectX accumulate a large number of games and engines. We can boldly predict that xna4 may be the last version, xna5 may appear in the form of winmd interface and return to the MDX mode. As the winmd interface version of DX, xNa is no longer the only solution on the platform according to this development trend, he will face numerous competitions, including this tutorial pai_^.

We can also boldly predict that winmd will definitely log on to Windows Phone and Xbox in such a gorgeous form. Then, DOTNET's xNa will gradually become optional, and then there will be no more, xna5 may be converted into DX winmd packaging.

 

If you find anything wrong, ask for positive criticism.

Coming soon, introduce Metro UI with code next week