Add Anonymous+Navigation

 

  • View
  • Changes
  • Options
  • Related
  • Edit
  • Download | Support | Changelogs

     

    Documentation:

    General Information

    Introduction | Overview | Features | Goals and Scope | FAQ Installation | Running an ACE Server | Tracking Problems

     

    Community Information

    About Us (contact) | Compatible Mods | Contribute | Guides | Missions | Servers | Videos

     

    Developer Information

    API | Classlists | Compatibility | Modification | Resources

     

  • View
  • Changes
  • Options
  • Related
  • Edit
  • News   

    Ongoing development 

       ACE 1.13 RC5 [2011-12-09]

    Stable

       ACE 1.13 for OA [2011-12-23]

     

    Or deprecated:

       ACE 1.3 for ArmA 2 [2010-07-05]

    Dev blogs

    1 to 20 of 35Next-page 1 to 20 of 35Next-page

     

    Wheeled by Wagn v. 1.7.1
  • View
  • Changes
  • Options
  • Related
  • Edit
  •  

     

     

    Why Wagn?+blog

     

    Some months ago we switched from MediaWiki to Wagn.

    As with any new technology it needs time to adapt to, even for us managing the documentation.

    Therefore the setup might be a little wonky here or there.

    Since that time, our wagn has undergone various improvements, changes like the Improved pathfinding in ACE2 features,

    improved Download page or improved navigation menu (on the right >>) etc.

     

    As always with a new/different system, there will be those who will not like it, can't or don't want to get used to it, etc.

    This is simply a fact of life, one can never please all, those who try will have very busy days :)

     

    Still there are probably many areas that can still be improved.

    Constructive critics are always welcome and we continuously try to improve both the documentation itself,

    as well as formatting / wagn setup. Also feel free to Contribute.

     

    Motivations

    Some might wonder.. Why Wagn? What is Wagn anyway? What's wrong with a PDF, or good old MediaWiki?

    Well first off, nothing is wrong with either. Both are fine, and people can prefer either of course.

     

    However, we feel the wagn system is more modern (in terms of technology) and flexible, and more fun to edit / work on,

    quicker and easier to tag/link/search, awesome inclusion features (we like to only write things once, like other wagneers), with a very powerful (yet almost nostalgic) card's system.

    The hows, whys etc, behind Wagn, are pretty much handled over at the Official Wagn site, anyone with (serious) concerns about the system should have a read.

     

    What is important to note is that the switch to Wagn is a motivator for working on the documentation, 

    which I think is more important than (some)user-comfort in general (if there's no motivation to write documentation, there's little use in having a user-comfort system).

     

    Overlooked Features

    A much overlooked feature (it's hidden well) is the Related tab:

    If you hover over a card's title, you get extra options, including changes history, etc, but also the Related tab. This one is basically the backbone of the card system and can get you to related information really quick.

     

    Another overlooked feature is the two options to show a card:

    You can collapse and uncollapse a card by clicking on the card's title, or the icon left of it.

    However, you can also visit the card as a full page, by clicking on the icon right of it. (appears when hovering).

     

    And of course as everywhere, the Search Bar up top is often missed.

    Then a tiny other one, the italic text next to card titles show the type of the card, you can also click it for an overview of all cards of that type.

     

    Future

    Since Wagn is Ruby on Rails based (my favorite) and easy to interact with (API), i'm hoping to hook up other systems like the Config Browser with dynamic Classlists etc.

    So information can be pulled and pushed both ways, further improving the information flow and provide different views to our information for different requirements.

    However, non of this has left the design phase just yet.

     

     

    Add +discuss