pipemania Wiki & Documentation Rss Feed

Updated Wiki: Home

ilkerde — Fri, 02 Oct 2009 19:03:22 GMT

Project Description
Pipemania is a classic single-player Puzzle Game. The primary purpose of this implementation Pipemania is to demonstrate various application design concepts, such as component-driven Architecture with usage of Dependency Injection (Microkernel) strategies and complete separation of application logic and presentation user interface through commanding.

This project not only concentrates in game development rather than in demonstrating some application designs and patterns. As a result, the game itself is not as much in focus on this project as the code behind it. The initial idea was to show some strategies for separation of logic and user interfaces - just for personal usage and upon interest of some friends of mine. However, as I started building the game, it somehow grew to a little "portfolio" of specific application design concepts. It soon reached some critical mass, and evolvement from "sample code" to "real application" happened to some extent.

I then decided to put all that stuff in here. Maybe someone's out there interested in

realizing "dependecy injection" (using service locator pattern) by means of .NET only or
how separation of logic and user interface works with a commanding infrastructure and
many other application design techniques.

Beside providing the source code, I do want to provide some comments and explanations why and how some specific concepts used in Pipemania code work. As of today, I do not have english materials to provide. Nevertheless, for the german speaking people I've set up a small project website explaining the game development as well as the core concepts used.

You're welcome to checkout http://www.gmbsg.com/projects/pipemania/.

UPDATED WIKI: Home

gmice — Thu, 23 Aug 2007 06:48:33 GMT

realizing "dependecy injection" by means of .NET only or
how separation of logic and user interface works with a commanding infrastructure and
many other application design techniques.

UPDATED WIKI: Home

gmice — Sun, 19 Aug 2007 23:19:09 GMT

realizing "dependecy injection" by means of .NET only or
how separation of logic and user interface works with a commanding infrastructure and
many other application design techniques.

Beside providing the source code, I do want to provide some comments and explanations why and how some specific concepts used in Pipemania code work. As of today, I do not have english materials to provide. Nevertheless, for the german speaking people I've set up a small project website explaining the game development as well as the core concepts used. Be sure to checkout http://www.gmbsg.com/projects/pipemania/.

UPDATED WIKI: Home

gmice — Sun, 19 Aug 2007 23:16:20 GMT

Project Description
Pipemania is a classic single-player Puzzle Game. The primary purpose of this implementation Pipemania is to demonstrate various application design concepts, such as component-driven Architecture with usage of Dependency Injection (Microkernel) strategies and complete separation of application logic and presentation user interface through commanding.

<div>

</div>

This project not only concentrates in game development rather than in demonstrating some application designs and patterns. As a result, the game itself is not as much in focus on this project as the code behind it. The initial idea was to show some strategies for separation of logic and user interfaces - just for personal usage and upon interest of some friends of mine. However, as I started building the game, it somehow grew to a little "portfolio" of specific application design concepts. It soon reached some critical mass, and evolvement from "sample code" to "real application" happened to some extent.

I then decided to put all that stuff in here. Maybe someone's out there interested in

realizing "dependecy injection" by means of .NET only or
how separation of logic and user interface works with a commanding infrastructure and
many other application design techniques.

Beside providing the source code, I do want to provide some comments and explanations why and how some specific concepts used in Pipemania code work. As of today, I do not have english materials to provide. Nevertheless, for the german speaking people I've set up a small project website explaining the game development as well as the core concepts used. Be sure to checkout http://www.gmbsg.com/projects/pipemania/.

UPDATED WIKI: Home

gmice — Sun, 19 Aug 2007 23:15:42 GMT

Project Description
Pipemania is a classic single-player Puzzle Game. The primary purpose of this implementation Pipemania is to demonstrate various application design concepts, such as component-driven Architecture with usage of Dependency Injection (Microkernel) strategies and complete separation of application logic and presentation user interface through commanding.

||This project not only concentrates in game development rather than in demonstrating some application designs and patterns. As a result, the game itself is not as much in focus on this project as the code behind it. The initial idea was to show some strategies for separation of logic and user interfaces - just for personal usage and upon interest of some friends of mine. However, as I started building the game, it somehow grew to a little "portfolio" of specific application design concepts. It soon reached some critical mass, and evolvement from "sample code" to "real application" happened to some extent.

I then decided to put all that stuff in here. Maybe someone's out there interested in

realizing "dependecy injection" by means of .NET only or
how separation of logic and user interface works with a commanding infrastructure and
many other application design techniques.

Beside providing the source code, I do want to provide some comments and explanations why and how some specific concepts used in Pipemania code work. As of today, I do not have english materials to provide. Nevertheless, for the german speaking people I've set up a small project website explaining the game development as well as the core concepts used. Be sure to checkout http://www.gmbsg.com/projects/pipemania/.

UPDATED WIKI: Home

gmice — Sun, 19 Aug 2007 23:15:08 GMT

This project not only concentrates in game development rather than in demonstrating some application designs and patterns. As a result, the game itself is not as much in focus on this project as the code behind it. The initial idea was to show some strategies for separation of logic and user interfaces - just for personal usage and upon interest of some friends of mine. However, as I started building the game, it somehow grew to a little "portfolio" of specific application design concepts. It soon reached some critical mass, and evolvement from "sample code" to "real application" happened to some extent.

I then decided to put all that stuff in here. Maybe someone's out there interested in

realizing "dependecy injection" by means of .NET only or
how separation of logic and user interface works with a commanding infrastructure and
many other application design techniques.

Beside providing the source code, I do want to provide some comments and explanations why and how some specific concepts used in Pipemania code work. As of today, I do not have english materials to provide. Nevertheless, for the german speaking people I've set up a small project website explaining the game development as well as the core concepts used. Be sure to checkout http://www.gmbsg.com/projects/pipemania/.

UPDATED WIKI: Home

gmice — Sun, 19 Aug 2007 23:13:26 GMT

Project Description
Pipemania is a classic single-player Puzzle Game. The primary purpose of this implementation Pipemania is to demonstrate various application design concepts, such as component-driven Architecture with usage of Dependency Injection (Microkernel) strategies and complete separation of application logic and presentation user interface through commanding.

Cannot resolve link: [image:pipemania_v1_sneak_preview_screen_xs.png|right]
This project not only concentrates in game development rather than in demonstrating some application designs and patterns. As a result, the game itself is not as much in focus on this project as the code behind it. The initial idea was to show some strategies for separation of logic and user interfaces - just for personal usage and upon interest of some friends of mine. However, as I started building the game, it somehow grew to a little "portfolio" of specific application design concepts. It soon reached some critical mass, and evolvement from "sample code" to "real application" happened to some extent.

I then decided to put all that stuff in here. Maybe someone's out there interested in

realizing "dependecy injection" by means of .NET only or
how separation of logic and user interface works with a commanding infrastructure and
many other application design techniques.

Beside providing the source code, I do want to provide some comments and explanations why and how some specific concepts used in Pipemania code work. As of today, I do not have english materials to provide. Nevertheless, for the german speaking people I've set up a small project website explaining the game development as well as the core concepts used. Be sure to checkout http://www.gmbsg.com/projects/pipemania/.

UPDATED WIKI: Home

gmice — Sun, 19 Aug 2007 23:13:11 GMT

realizing "dependecy injection" by means of .NET only or
how separation of logic and user interface works with a commanding infrastructure and
many other application design techniques.

Beside providing the source code, I do want to provide some comments and explanations why and how some specific concepts used in Pipemania code work. As of today, I do not have english materials to provide. Nevertheless, for the german speaking people I've set up a small project website explaining the game development as well as the core concepts used. Be sure to checkout http://www.gmbsg.com/projects/pipemania/.

UPDATED WIKI: Home

gmice — Sun, 19 Aug 2007 23:12:18 GMT

Project Description
Pipemania is a classic single-player Puzzle Game. The primary purpose of this implementation Pipemania is to demonstrate various application design concepts, such as component-driven Architecture with usage of Dependency Injection (Microkernel) strategies and complete separation of application logic and presentation user interface through commanding.

Cannot resolve link: [image:Pipemania_screenshot_xs.png]
This project not only concentrates in game development rather than in demonstrating some application designs and patterns. As a result, the game itself is not as much in focus on this project as the code behind it. The initial idea was to show some strategies for separation of logic and user interfaces - just for personal usage and upon interest of some friends of mine. However, as I started building the game, it somehow grew to a little "portfolio" of specific application design concepts. It soon reached some critical mass, and evolvement from "sample code" to "real application" happened to some extent.

I then decided to put all that stuff in here. Maybe someone's out there interested in

realizing "dependecy injection" by means of .NET only or
how separation of logic and user interface works with a commanding infrastructure and
many other application design techniques.

Beside providing the source code, I do want to provide some comments and explanations why and how some specific concepts used in Pipemania code work. As of today, I do not have english materials to provide. Nevertheless, for the german speaking people I've set up a small project website explaining the game development as well as the core concepts used. Be sure to checkout http://www.gmbsg.com/projects/pipemania/.

UPDATED WIKI: Home

gmice — Sun, 19 Aug 2007 23:10:33 GMT

Project Description
Pipemania is a classic single-player Puzzle Game. The primary purpose of this implementation Pipemania is to demonstrate various application design concepts, such as component-driven Architecture with usage of Dependency Injection (Microkernel) strategies and complete separation of application logic and presentation user interface through commanding.

Cannot resolve link: [image:http://www.gmbsg.com/projects/images/2/24/Pipemania_screenshot_xs.png]
This project not only concentrates in game development rather than in demonstrating some application designs and patterns. As a result, the game itself is not as much in focus on this project as the code behind it. The initial idea was to show some strategies for separation of logic and user interfaces - just for personal usage and upon interest of some friends of mine. However, as I started building the game, it somehow grew to a little "portfolio" of specific application design concepts. It soon reached some critical mass, and evolvement from "sample code" to "real application" happened to some extent.

I then decided to put all that stuff in here. Maybe someone's out there interested in

realizing "dependecy injection" by means of .NET only or
how separation of logic and user interface works with a commanding infrastructure and
many other application design techniques.

Beside providing the source code, I do want to provide some comments and explanations why and how some specific concepts used in Pipemania code work. As of today, I do not have english materials to provide. Nevertheless, for the german speaking people I've set up a small project website explaining the game development as well as the core concepts used. Be sure to checkout http://www.gmbsg.com/projects/pipemania/.

UPDATED WIKI: Home

gmice — Sun, 19 Aug 2007 23:09:55 GMT

Project Description
Pipemania is a classic single-player Puzzle Game. The primary purpose of this implementation Pipemania is to demonstrate various application design concepts, such as component-driven Architecture with usage of Dependency Injection (Microkernel) strategies and complete separation of application logic and presentation user interface through commanding.

Cannot resolve link: [image:http://www.gmbsg.com/projects/images/5/5d/Pipemania_screenshot_xs.png]
This project not only concentrates in game development rather than in demonstrating some application designs and patterns. As a result, the game itself is not as much in focus on this project as the code behind it. The initial idea was to show some strategies for separation of logic and user interfaces - just for personal usage and upon interest of some friends of mine. However, as I started building the game, it somehow grew to a little "portfolio" of specific application design concepts. It soon reached some critical mass, and evolvement from "sample code" to "real application" happened to some extent.

I then decided to put all that stuff in here. Maybe someone's out there interested in

realizing "dependecy injection" by means of .NET only or
how separation of logic and user interface works with a commanding infrastructure and
many other application design techniques.

Beside providing the source code, I do want to provide some comments and explanations why and how some specific concepts used in Pipemania code work. As of today, I do not have english materials to provide. Nevertheless, for the german speaking people I've set up a small project website explaining the game development as well as the core concepts used. Be sure to checkout http://www.gmbsg.com/projects/pipemania/.

UPDATED WIKI: Home

gmice — Sun, 19 Aug 2007 23:08:31 GMT

realizing "dependecy injection" by means of .NET only or
how separation of logic and user interface works with a commanding infrastructure and
many other application design techniques.

Beside providing the source code, I do want to provide some comments and explanations why and how some specific concepts used in Pipemania code work. As of today, I do not have english materials to provide. Nevertheless, for the german speaking people I've set up a small project website explaining the game development as well as the core concepts used. Be sure to checkout http://www.gmbsg.com/projects/pipemania/.

UPDATED WIKI: Home

gmice — Sun, 19 Aug 2007 23:07:29 GMT

About Pipemania Project

realizing "dependecy injection" by means of .NET only or
how separation of logic and user interface works with a commanding infrastructure and
many other application design techniques.

Beside providing the source code, I do want to provide some comments and explanations why and how some specific concepts used in Pipemania code work. As of today, I do not have english materials to provide. Nevertheless, for the german speaking people I've set up a small project website explaining the game development as well as the core concepts used. Be sure to checkout http://www.gmbsg.com/projects/pipemania/.

UPDATED WIKI: Home

gmice — Sun, 19 Aug 2007 23:01:29 GMT

Project Description
Pipemania is a classic single-player Puzzle Game. The primary purpose of this implementation Pipemania is to demonstrate various application design concepts, such as component-driven Architecture with usage of Dependency Injection (Microkernel) strategies and complete separation of application logic and presentation user interface through commanding.

!!About Pipemania Project

This project not only concentrates in game development rather than in demonstrating some application designs and patterns. As a result, the game itself is not as much in focus on this project as the code behind it. The initial idea was to show some strategies for separation of logic and user interfaces - just for personal usage and upon interest of some freinds of mine. However, as I started building the game, it somehow grew to a little "portfolio" of specific application design concepts. It soon reached some critical mass, and evolvement from "sample code" to "real application" happened to some extent.

I then decided to put all that stuff in here. Maybe someone's out there interested in

realizing "dependecy injection" by means of .NET only or
how separation of logic and user interface works with a commanding infrastructure and
many other application design techniques.

UPDATED WIKI: Home

gmice — Sun, 19 Aug 2007 21:44:49 GMT