Add in true/false for click sortable using sortable option, matching this to the way it is handled in node.views.inc. Also move 'allow_empty' option to field definition and add it to all elements to make it available to Views everywhere it might be used.

A couple more fixes needed to get the new filter operator working correctly. We don't need to mess with the form element here, and the form element must return an array instead of a value, so just remove that part.

The many_to_one operator looks like it makes more sense to use as the default filter for fields with allowed values lists.

Add allowed values to the in_operator_content handler to automatically populate the options list with the results of either hook_allowed_values() or content_allowed_values().

Re-organize the Vews field handlers into a basic one that just adds the fields and formatters and a more complex one that adds in the group multiple values handling. Field modules can extend either one, depending on their needs.

Also add in a basic sort handler that just adds field info to the regular sort handler.

#63240 Add field permissions with new content_permissions module and related fix to views handling to implement permissions in Views, patch by moshe weitzman. thx moshe!!

Add smarter handling for arguments and sorts based on column type and sortable settings, and get rid of outdated Views 1 code that is no longer being used.

Change the field group to be the field name, instead of 'Field', so we will see 'Text: field_my_field' instead of 'Field: field_my_field' as labels for fields, filters, etc.

Re-name fields to use Views 1 naming like field_text_value instead of field_text to make updates easier, and alter content.views_convert.inc to match.

Add default filters for all fields, and update fields to switch from string or numeric filters to 'in' operators if there are lists of allowed values.

Add helper function to return Views table name to make it easier to change the tablename in the future, like if we find a way to avoid the need to alias each field as its own table.

'group multiple values' views handler messes the query in various ways,
and is not needed to begin with : the nids we retrieve are selected by the
main views query, which already goes through a db_rewrite_sql.

The $this->nid_field got renamed in Views when the relationships patch hit, need to rename it here, too.

load field data in one query per field (instead of one per field and per node previoulsy).
More optimisations could possibly be made there (fetch from cache ?)
Suggested by Adrian and Earl.

#233364 Changing the Views field name is going to break other things. Change this back to field name and handle the discrepency with the hook in content.views_convert.inc instead.

#233364 Make sure field names used in Views 2 map to field names used in Views 1 so we can more easily import Views 1 views into Views 2. With this change the import code in that issue will correctly pick up CCK fields and import them automatically. We still need to implement hook_views_convert() to update options and values, and there may still be other things that need to be adapted.

- default Empty / Not empty filter for all fields
  (still triggers a few warnings when used as exposed filters)
- very early beginnings of 'relationships' for nodereferences.
  Doesn't do anything yet.

Thanks Earl.

hide 'multiple values' settings for non-multiple fields

follow last refactoring in Views

- going back and forth on where to initialize CCK data in handlers. construct() should be fine.
- we need a 'field_alias' if we want to display several fields
- cleanup some todos

Views integration : sync with Views 2 HEAD changes, and fix stuff now that Views actually lets us save and test views :-)
'Fields' are working (still very young).
No Filters / args / sorts yet.

Time to think about the way field modules can tweak views exposed data...

That's probably as close as we can get without Views actually working :-)

No Views for D6 yet, so simply porting over.