I have started work on something that might prove to make things much simpler. It is in a very early stage of development, so I'm not very comfortable with going public with it yet, but the discussions in this thread are making me think that it could be very useful, and it is probably of interest to many of us, and more than any others, to ACs and ERCs.
I was setting out to make an experimental list. Well, I don't know if you're like this, but I found it very painful, lots of layout issue and I'm not an expert with any stuff like Acrobat or Word or whatever.
However, I am an expert in web development (or at least a scattering of techniques useful on the web), and I am the kind of lazy guy who would rather develop a software from the ground than fight with the layout options of MSword.
So the idea is to make a web based application, that could store complete lists for EA, from units and weapon statlines to lists with all their options, point costs, etc.
then, from there, the goal is to be able, dependent on a system of permission per user and per user groups, to :
- export data in a format that would be understandable by the application itself, and human-readable enough that someone web-competent could develop his own stuff based on the data.
- import data in the same format.
- display, on a web type interface (i.e. : web pages) :
* unit listings in a way akin to what the current lists are doing, with full stats, background/lore/fluff text and possibly image galleries
* lists with core, support, allied choices and upgrade, i.e.: Lists as usable as those published
* quick reference sheets
- generate and export the same "view" (unit datasheets, army lists, quick reference sheets) in a paper friendly way (web based probably at first, PDF as a probable future feature)
- Allow people with sufficient permission (i.e.:ACs ) to modify and add data to official lists, so that updated lists are available instantly
- Allow people with sufficient permission (i.e. : hand-registered taccommers) to create their own lists, as variants, house lists, experimental stuff, etc.
There are LOTS of stuff that could be plugged on such a structure, from army-builder style sub-applications to statistic extraction from lists to whatever.
Now, where am I with all that ? Well, the basic data structure is defined (like, I have my MySQL structure ready), and that's all for now. This structure can do everything I found in marine, guards, eldar, ork lists, from alternate weapon loadouts (marine dreadnought) to weapon with alternate statline themselves (earthshaker cannon), it can manage unit upgrades or free upgrades (+1DC as an upgrade), core/support/restricted allies discriminations and that kind of things, detailed structural transport options, etc.
The system can cope from the start with some stuff that are not used anywhere but could be interesting (for example, making you buy "detachment packages", for example paying n points and getting a marine company, that is 4 detachments : 2 tacs, one Assault and one dev).
I think I still have to do some slight modifications to allow things like weapons as an upgrade in a structured way (that should be almost instantaneous however), and of course re-read to all lists to make sure that I can manage all that is currently existing.
This is an important but small part in term of the total amount of work involved.
From there I have to (in a rough order) :
- define the structured data format I want to use in the application (only just started, relatively straightforward, JSON will be the obvious choice for me)
- develop SQL procedures and various middleware to :
* produce the aforementioned data structures from the database
* be able to insert/update the correct stuff in the DB, taking the aforementioned structure.
Nota : this stage is likely to be the most technical and the most time consuming; this also imply that if I get this done, motivation and time won't be nearly as hard to get to do the rest. import/export functionality are almost free at this stage, since the structured JSON will be the export format.
- develop the SQL structures and associated code to implement the user & permission system (relatively straightforward, but tedious and meticulous task if we don't want this to have gaping security breach; luckily, a good friend of mine is a security expert: that might help); after this stage, the stuff can basically go public (it still wont be usable for most interesting applications)
- develop a basic display interface. Basic means ugly.
- develop a basic input interface. Basic still means ugly.
- refine such display to make it nice to look at, and alternate layout for printing and use on paper. (fun stuff for me)
- expand from there (link to galleries, quick references extractions, celebrating with champagne, etc).
Keep in mind that this is all a LOT of work; also keep in mind that while motivation is strong at this point, I have a consuming RL job (I'm an IT engineer if you didn't guess), a wife, a son, like to do long roller-skating sessions, have started rock climbing recently, have armies to paint, and am an avid reader. So, stuff might move very fast or stall, and I would be a liar if I made any promises, or even give you an ETA on all this.
What I can commit to do is keep you all informed on my progress, and answer any questions you might have on all this. I'll start a thread about this as soon as I have the time and a name for the project. I'm open to suggestions of course.
Oh, and by the way, if you don't realise all the usefulness of such an applications, it implies things like instant army compendium compilation, indeed a living army rulebook with no compilation work involved, clearly labelled status of lists (be they netEA official, FERC official, EUK official, experimental, fanlists... indeed as many status as one might want).
Right now I HAVE to go take a plunge into the Mediterranean sea with my family, so I probably won't answer any questions instantly
, but I'll be back soon.
