codename: codenames


power to the packs - more data in cards, more code in modules


If you've been following Wagn, you know how excited we are about Wagn 2.0:  how it will complete our transition from a nifty app to a powerful platform...  how it will be easy to discover, use, and extend...


Well, we're getting closer!  I should say up front: 1.9 will not be the last release before 2.0.  We're planning 1.10 and 1.11 releases, as outlined on our roadmap.


That said,Wagn 1.9 takes some big steps.


One key step is that we've considerably increased the number of cards that can be renamed without creating problems by giving them an additional "codename" identifier to be used when referenced in the code.   This is important for Wagn because we give so much power to Wagneers, who are essentially coding by manipulating card content.  Our new, more robust approach allows for powerful relationships between code and content, so that we can continue to give Wagneers more and more new capacities.


1.9 is also slimmer.  By moving data into cards, we've gone from having seven core data tables to having just four.  (We'll be down to three in 1.10).  This has considerably simplified our codebase without sacrificing any functionality.


Perhaps most importantly, it gets us much closer to the 2.0 apis (both REST and pack) that we think will make Wagn the platform of the future.


See the Release card for tickets and update details.






migrate away all old global permissions links?

  --Ethan McCutchen.....2012-10-01 16:33:44 +0000

(not migrating those yet. for now they go to a deprecation notice)

  --Ethan McCutchen.....2012-10-09 21:38:42 +0000