List view
- Overdue by 11 year(s)•Due by July 6, 2014•1/1 issues closed
- Overdue by 11 year(s)•Due by June 22, 2014•3/3 issues closed
Creation of the API Extensions that will provide user-friendly abstraction, data validation, and utility functions
Overdue by 11 year(s)•Due by July 20, 2014Prove that every ConfigFile derivative and Manager is working properly by implementing an easy way to interact in SEConfigTool2 (or a new name) for each derivative. This milestone is intended to Create a higher level core to handle every possible problems about Core usage. - Make sure all interfaces and managers created are easy to use and respect a common pattern. They sould handle problems related to interact with one or multiple Core definition. - Every class of SEModAPI must be tested completely somewhere in SEConfigTool2. - Make sure the way to interact with all interfaces and managers is simple and optimally presented into through SEConfigTool2. We don't want to have an interface for every class, we want to have an interface for every concept in the gam: - Items :which include components, handitems, consumables like ammo, etc. - Blocks : which include components, subtypeDefinition, variants, model, etc. - Etc, etc.
Overdue by 11 year(s)•Due by August 10, 2014Create UML documentation as artifacts for the API and make sure code is commented. - Generate an UML Class Diagram of SEModAPI project. - Comment properly classes and code that is not respecting documentation standard in [All-In-One Code Framework Coding Standards](http://1code.codeplex.com/wikipage?title=All-In-One%20Code%20Framework%20Coding%20Standards&referringTitle=Documentation) entire section 2.11 and 2.12
Overdue by 11 year(s)•Due by July 13, 2014Code optimizations, simplification and tests. - Every classe and interface must respect [C# standard](http://msdn.microsoft.com/en-us/library/ff926074.aspx) but use less as possible LINQ expressions as they tend to be slower than well coded for or foreach loops. Code should also respect [Microsoft All-In-One Coding Standards](http://1code.codeplex.com/wikipage?title=All-In-One%20Code%20Framework%20Coding%20Standards&referringTitle=Documentation) and [Brad Adams Internal Coding Guide](http://blogs.msdn.com/b/brada/archive/2005/01/26/361363.aspx) - Make sure every objects are coherents to their name and concept, if they do something that is not matching their name, rename them or extract thoses functions into other objects. Multiple simple objects that do what their name says is easier to maintain. - Remove code duplicates by adding functions, class hierarchy or design patterns. - Enable all warnings and treat them as errors. - Create unit tests for every class in SEModAPI.
Overdue by 11 year(s)•Due by July 6, 2014•4/6 issues closedSupport all configuration files into classes easily managable. Every classes should be able to serialize and deserialize themselves without giving much trouble and should have a common structure and exception management. This is the core of the API, so we should only give a simple and clear way to interact with the game.
Overdue by 11 year(s)•Due by June 29, 2014•16/21 issues closed