For this part, no code it purpose.
First when you make an application, a game or any software, you cut it in some distinct parts. This parts can be define by a visual approach. For us first game we will make a Tic Tac Toe game. And now we search to fitted plugins.
But, what is a plugin ? What can it bring to me ? Who killed Laura Palmer with a plugin ?
There are two goods reasons that can help you to view our game with plugins :
Some advantages are in favor of plugin with LowRA (MVC and IOC concept) :
You can now make a remark, like a Major Briggs Junior : divide for reign.
Like a normal application we identify each functionalities. We need :
Now let’s look how does it work :
It’s wonderful. It will work. So easy, yeah ! Not exactly, it’s missing an important part. We have already thought about what we need. But we never think about : how it agglomerates, which of this part is the main ?
Around Laura Palmer world a lady can tell you : “speak to my log !”
In LowRA world we prefer use Inversion Of Control conception. It consists to create an XML that defines how will work my application, my game, my plugins.
For this, we need to make an assembler which can read the famous XML : applicationContext.xml for instantiate all plugins.
For now, we just know how to think with lowra in plugins. Next time, we’ll make our first plugin, promised ;)
For any suggestion, remarks : mickael.foucaux@gmail.com
For any correction, make better english : create an account and click [edit] button
For another think about LowRA call Francis Bourre.