add the ability to create terms to Fieldmanager_Datasource_Post; prevent saving the same post twice via a revision.
Added hide_empty=false to get_term to allow for new terms to appear in draft state
Ensure that attachment ids are stored as absolute integers
Fixing bug with latest WP nightly build where null term IDs are returning the first term
Merge pull request #36 from mboynes/media-id-storage

Ensure that attachment ids are stored as absolute integers
Merge pull request #37 from mboynes/fixing-datasource-term-null-bug

Fixing bug with latest WP nightly build where null term IDs are returning the first term
Fixing a data saving bug in the submenu context

When the menu slug was overridden, the data would not save because FM was checking to see if the current page slug == the fieldmanager name. Props to ostowe for reporting the bug
Adding custom preview size to media fields
Assorted media enhancements

* adding ability to customize buttons and titles
* converting media popup to use custom media popup (as opposed to editor popup)
* adding i18n
* making images clickable (links to edit the media)
grid fix
Merge pull request #39 from mboynes/fixing-submenu-saving

Fixing a data saving bug in the submenu context
Merge pull request #40 from mboynes/media-updates

Media updates
adding apigen template to git.
* Updating README
* Adding proper license
* Regenerate documentation
* Fix broken unit tests
* Improve code coverage of Fieldmanager_Field to 80%
prevent inclusion of dialog html when already included, fixes fullscreen and link dialog bugs
Merge pull request #42 from nschoenholtz/link_dialog_bugfix

Fix for the link dialog and fullscreen editor bugs
Fixing a bug where datasources set to not use ajax weren't working
Making the autocomplete selector more specific, as a wrapping div also gets the same class
Resolving issue with non-ajax datasource items, which were not loaded properly for autocomplete elements
Restricting "Add element" to the immediate fm-wrapper scope

This resolves a bug whereby two groups, named differently, with identically-named children, will have a conflict when blocks 2->n's "Add element" button is clicked. The second (or beyond) add element button adds an element in the correct place, based off the first wrapper's prototype.