Arianne Project Meeting 2010/Talks: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
imported>Kymara No edit summary |
imported>Kymara rearrange order to match what happened, add summary and reviews. |
||
| Line 2: | Line 2: | ||
== Talks == |
== Talks == |
||
We will add here the slides from each talk and a link to a video, when these have been prepared for display on the net. Please check back if you are interested! |
|||
| ⚫ | |||
In this section suggestions and ideas about talks are collected. Those are just first ideas that may be adjusted. This includes the speaker, so if you are interested in giving a talk on a subject, just add your name. And if you want to listen to a talk on a subject just suggest it. |
|||
| ⚫ | |||
The target group is split into Developers, Contributors and Players/Users. This may change based on feedback of who is going to join us. |
|||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
=== Concepts of Marauroa and how to use it === |
=== Concepts of Marauroa and how to use it === |
||
| Line 14: | Line 18: | ||
; Abstract : In this talk I will present the basic ideas of the Marauroa engine (Actions, Perceptions, Messages, Events, Objects and Classes) and explain how to use them for your own games and programs. I will start with a very short introduction to UML class diagrams as they are a handy tool to describe object oriented structures. |
; Abstract : In this talk I will present the basic ideas of the Marauroa engine (Actions, Perceptions, Messages, Events, Objects and Classes) and explain how to use them for your own games and programs. I will start with a very short introduction to UML class diagrams as they are a handy tool to describe object oriented structures. |
||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | ; Abstract : There is a number of very interesting and complicated things on the feature wish list for Marauroa. As you are probably aware of, KISS (Keep it simple, stupid) is one of the main principal of Marauroa. This of course does not mean that we cannot do complicated things. But it means that complicated things have to be well thought of and be broken into small parts. In this talk |
||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
; Language : English |
; Language : English |
||
; Target group : All |
; Target group : All |
||
| ⚫ | ; Abstract : Can anyone name all Stendhal NPCs and describe something interesting about what each does? Without preparation? (honestly... the speaker has no time to prepare...) If anyone can, the Amazing Stendhal Dictionary can! Marvel as she attempts to draw a map of the island and its dungeons, and take each region in turn, describing some history, each NPC's features, and some funny* anecdotes. |
||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
; Language : English |
; Language : English |
||
; Target group : All |
; Target group : All |
||
| ⚫ | |||
| ⚫ | ; Abstract : Can anyone name all Stendhal NPCs and describe something interesting about what each does? Without preparation? (honestly... the speaker has no time to prepare...) If anyone can, the Amazing Stendhal Dictionary can! Marvel as she attempts to draw a map of the island and its dungeons, and take each region in turn, describing some history, each NPC's features, and some funny* anecdotes. |
||
| ⚫ | |||
===JUnit testing - how and why? === |
===JUnit testing - how and why? === |
||
| Line 56: | Line 42: | ||
; Abstract : It is well known that no application is bug free, so we need to find those errors to fix them. The earlier we find an error the less effort will be necessary to correct it. With tests that can be run repeatable you earn a lot safety for proceeding development. The tests can ensure that once working parts are not broken by changes of the ongoing the development. A freely available framework supporting such automated testing is JUnit. In this session we will tell why unit testing is a good idea and how we can use JUnit to test your code. |
; Abstract : It is well known that no application is bug free, so we need to find those errors to fix them. The earlier we find an error the less effort will be necessary to correct it. With tests that can be run repeatable you earn a lot safety for proceeding development. The tests can ensure that once working parts are not broken by changes of the ongoing the development. A freely available framework supporting such automated testing is JUnit. In this session we will tell why unit testing is a good idea and how we can use JUnit to test your code. |
||
; Review : Markus gave a talk on JUnit testing, and managed to make it sound not only vital to the code quality and stability of the project, but even fun too. He demonstrated how continuous integration (our hudson bot) and JUnit testing can work together to notify developers early of any problems. At the end of the talk at least one developer was heard to mutter ''Hm, I should add a test for that method I wrote last week.'' |
|||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | ; Abstract : There is a number of very interesting and complicated things on the feature wish list for Marauroa. As you are probably aware of, KISS (Keep it simple, stupid) is one of the main principal of Marauroa. This of course does not mean that we cannot do complicated things. But it means that complicated things have to be well thought of and be broken into small parts. In this talk we will present ideas on how to archive the following "feature" and ask for you feedback and suggestion on the issues: |
||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
; Review : Hendrik and Markus together gave a talk on Marauroa's future. This covered both plans achievable in the short term and some more ambitious ideas. It was a talk aimed at developers and there were often questions and comments from the audience, which was really nice. Some of the topics, like asychronous database access and https multiplexing, seemed like they are both very useful and achieveable in the short term. Other plans like the meta model for storing objects and their attributes, values, and relationships, in the database, are really good plans |
|||
and will need quite a lot of work to be introduced. |
|||
| ⚫ | |||
| ⚫ | |||
; Speaker : |
|||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
===More Ideas=== |
===More Ideas for another time=== |
||
* Using Tiled to create Stendhal maps |
* Using Tiled to create Stendhal maps |
||
* Using Eclipse to develop Arianne projects |
* Using Eclipse to develop Arianne projects |
||
| Line 80: | Line 83: | ||
Note: Use View | Heading/Footer... to add the title of your presentation into the middle section of the footer |
Note: Use View | Heading/Footer... to add the title of your presentation into the middle section of the footer |
||