working onrefactoring datum states to remove them from the datum, so that only states which are on are in the datum
Revert "working onrefactoring datum states to remove them from the datum, so that only states which are on are in the datum"

This reverts commit f701d516d7dc5228d2c98ee68891eec7423bd50e.
prototyping a new datum that is more flexible
Revert "prototyping a new datum that is more flexible"

This reverts commit acb68f616ab2a93aad6fd12d64ce994d0a91b4ac.
made eport as cxv work properly with all fields and a header, fixed bug in latex (two + in a row) for #808
fixes #808 for now until we have a aserver side which can extract all data, convert into xml and simplified json as the user wishes... for now they can at least see that export is straightforward and very flexible
removing the minified files from the repo
adding a view for all usermasks in a corpus
fixes #823 now the morpheme visualizaiton shows beginning #_ and end _# of the word. which is a lot closer to a wiggly finite state machine.
small tweeks in corpus (added tags and validation states and removed changepouch from all models except app and activity. for #756
working on getting rid of conflict notices and simply overwriting a userpublic thats in the databse with the updated one in the user's preferences.
app is loading in a chrome extension, using backbone couchdb adapter not pouch, for #756 next step is to test the rest of the functionality, new users, new corpus, new objects etc, then decide if we want to include pouch for the beta testers, or have them use the app only online.
logging in is working for #756
creating new corpus in existing user works and search works for #756
for #756 creating new users is working in chrome app and in couch app. ready for testing upgrade of existing users...
fixes #830 in the chrome store and online, the chrome store is unfortunately waiting for issue #827 and #828 which have to do with the fact we cant whitelist iriscouch anymore for CORS using a permission. we are waiting for some guidance from the chrome extensions developers list... this issue also fixes #829 and fixes #801 with a new update page that backups the user's corpora in their pouches so they can use it in the online app. it also fixes #769 we have changed the public user so that hte one in the authentication and the one in the userPrivate are the same, thereby ensuring that the userpublic can be saved into a user's corpus, and the userpublic stored in the users preferences is used to overwrite old ones in teh corpus
dont ask lingllama to back up their prefs
making a cuter spinner for corpus creation. on the snowleopard machine it sometimes takes 2 tries to get the corpus to save in the new database, so depending on the users connection this is very tricky. now it loops until it succeeds in saving.
Merge pull request #831 from cesine/master

Release for 1.40 chrome app and online app