Create named fields for all attributes #7

Open
opened 2015-10-07 10:27:33 -05:00 by mattbk · 1 comment
mattbk commented 2015-10-07 10:27:33 -05:00 (Migrated from github.com)

This is the kicker for making this module much more useful. How to create a Views field for each attribute?

Can multiple handlers be added in the same handler file? If so, it could be possible to loop through the attributes array in uc_views_attribute.views.inc to create the view handler names, then loop through the attributes array in uc_views_attribute_handler_WHATEVER.inc to create the actual handlers. If all the handlers can be the same format (text, numeric, etc.) this could work.

There are two big ifs to look into above.

This is the kicker for making this module much more useful. How to create a Views field for each attribute? Can multiple handlers be added in the same handler file? **If so**, it could be possible to loop through the attributes array in `uc_views_attribute.views.inc` to create the view handler names, then loop through the attributes array in `uc_views_attribute_handler_WHATEVER.inc` to create the actual handlers. **If** all the handlers can be the same format (text, numeric, etc.) this could work. There are two big **if**s to look into above.
mattbk commented 2015-10-07 18:32:14 -05:00 (Migrated from github.com)

Maybe if the data were deserialized in uc_views_attribute.views.inc they could use a generic handler?

Maybe if the data were deserialized in `uc_views_attribute.views.inc` they could use a generic handler?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: matt/uc_views_attribute_fork#7
No description provided.