Changes between Version 3 and Version 4 of Roadmap

Timestamp:

01/31/10 14:42:01 (10 years ago)

Author:

ibboard

Comment:

Further changes to prevent trademark litigation

Roadmap

@@ -14 +14 @@
 == The next step ==
 
-Once v0.1 is released there are still some features that would be needed before the application is totally feature complete. The next set of goals are then:
+Once v0.1 is released there are still some features that would be needed before the application is totally feature complete. The next set of goals would then include:
 
  * Finish development on [milestone:"WarFoundry 0.2"] to extend the core towards a complete feature set
@@ -22 +22 @@
 == Version One ==
 
-Version one will be the first version that is feature-complete for an army building application, including army validation and other useful features. Exactly what remains in it and how many versions there will be between v0.2 and v1.0 depends on what people feel is missing and how the project progresses.
+Version one will be the first version that is feature-complete for an army creator, including army validation and other useful features. Exactly what remains in it and how many versions there will be between v0.2 and v1.0 depends on what people feel is missing and how the project progresses.
 
 That's not to say that all versions before 1.0 won't be useful, just that there may be some features (like checking you have enough Troops in your Warhammer 40,000 army) that might not be in versions before 1.0.
@@ -30 +30 @@
 There are a number of other ideas floating around that will be supported as and when we get time/get extra developers and if people show an interest in them. The "would like" list of planned features with no ETA currently includes:
 
- * Army Builder support (see [http://forums.hiveworldterra.co.uk/viewtopic.php?f=40&t=1257 this thread] for discussion on the topic)
+ * ArmyBuilder support so that WarFoundry can load Army Builder data files (see [http://forums.hiveworldterra.co.uk/viewtopic.php?f=40&t=1257 this thread] for discussion on the topic)
  * A Mac OS X/Carbon interface so that we can support the other main desktop OS
- * A QT interface for people who use KDE (although first we need someone to make the QT to Mono bindings)
+ * A QT interface for people who use KDE
  * A web-based interface (we should be able to use the API for mod_mono/ASPX pages and an online version of the tool)
  * Support for [http://www.thedigitalfoundry.com/forge/ The Forge] data files (may be a no-go as it doesn't seem to have been updated in ages)
  * Support for Games Workshop's own [http://ial.games-workshop.com/ Interactive Army List] files (again, may be a no-go as GW doesn't seem to have updated it in years)
 
-For now, though, the focus will be on Windows and Linux (GTK) and WarFoundry files with Rollcall support through a plugin.
+For now, though, the focus will be on Windows and Linux (GTK) and native WarFoundry files with Rollcall support through a plugin.