Some content cannot be annotated

The branch adds list_string and entity_reference. Entity reference allows taxonomy terms.

I would also like to see this functionality. Thoughts on a timeline for completion and release?

Thanks all.

Also adds:
boolean
changed
created
datetime

I have allowed some more fields based on a project that I'm currently working on.

Hope this helps!

Chances are I'll have more to add as this project grows.

Hi @jmester13,

I think email, telephone, and address are good additions. How are you using tablefield? I am not saying no to tablefield. I am having trouble picturing the use case for tablefield.

@bluegeek9

We are using table field for something like a score card when a user is creating a piece of content. Probably more of and edge use case for most folks, but the project I'm working in has the need. It is a simple table, 5 rows, 5 columns which some rate 1-4 type of questions.

Thanks!

@jmester13,

I am thinking it would be better if we provide a setting for which field types are valid. We would need to update the settings form.

Maybe, use Tableselect. Each row of the table is another field type used by moderated content. There is a checkbox for each row.

This makes is easy for site builders to decide which field types are allowed.

@bluegeek9

Settings form sounds nice and makes sense to me. I wonder if we could 'detect' which modules are installed and which fields are therefore available for that settings page? Trying to think as dynamic as possible. So for example, if Table Field isn't installed the option isn't there or is at least disabled on our settings page.

I like the idea of getting granular with the table and allowing comments per table row, that makes a lot of sense to me.