well thanks to davereids wonderful entity_view_mode we don't need to predeclare so many different view modes, actually I will rather have non at all, and ccreate them as needed with the module, if anyone disagree there is still and entity_info_alter, right?

WARNING: None of this changes have been tested. All the code from eck.module has been refactored in accordance with drupal terminology

small change in eck__entity_create, I need to stop using those stupid $entity and $type objects, they are not very intuitive, so I started here, hopefully I will be able to clean up everything else soon enough.

Fixed argument on delete, now that our stuff in under structure in the admin section, and also fixed a little bug when list (overview) tables are empty

Adding a little bit more functionality to the administration section of entities, now the entity overview is a tableselect form, and the submit function from that form calls a hook so other modules can do whatever they like with the selected rows

Stefan Kudwien authored Jul 23, 2011 and MaOva AsSicI committed Jul 23, 2011

Adding some features support for entities and bundles, also now eck has the capability of creating a different class for every entity type for further customization, tested and debugged by Merco

separated some other stuff. So now we have a funtion that will return all of the ids given an entity type and a bundle, and another function that will return all the entities given the same two parameters. Also I turned the entity overview table into an tableselect element in a form, currently eck does not do nothing when a row is selected, but it has an alter hook on submit so you can see the data from the form state do whatever you want and redirect to wherever you want

separated some parts of the entity_add functionality, to make it easier for other modules to reuse the eck code

added a drupal_alter hook to the overview function to be able to modify the rows of the table of entities

Added a state field, it should be use for functionality similar to the status field in nodes. There is an update implemented for this change.

**NOTE** From now on I will start using drupal terminology on the comments so the community can better understand what I am doing, the code has not been refactored to use those definitions, but this will come soon also --- Reactivated the delete functionality for entities

Small change: commented out all dpm statements, so it would not give us trouble if it devel is not enabled

Added the types (bundles) feature, now any entity can have multiple types, I took all of the delete code from the UI as it has not been tested after all the changes, but everything else seem to be working correctly

Included some descriptions and the fields as required in the entity creation form, and added a validation function that checks to make sure that the entity name is in the right format.

Fixed a problem with the entity db table creations, a nonexistant property of an object was being called

Added a few menu rebuilds when entities are created and deleted, but that still did not fix the problem of all the field managing tabs showing up when a new entity is created

Most code now follow drupal standars, database tables for factory entities now have the prefix efactory_, and permissions are working like they are supposed to