Hi there,
I am (or was) working on a similar framework myself and found out pods the other day. Im testing it and have to say that I really enjoy it. I loved that the plugin actually create the tables for each pod – this is what I was looking for.
The possibility of having relationships with WordPress elements and with other Pods are also beautiful… Really.. Congrats for the great work.
Ill you give now my feedback, bringing some ideas I have been working on my CRUD plugin. The thing is I think a plugin like that shoud leave the possibility to developers to change things. The interface is great, but its important to have the possibility to do things that were not planned and are not available in the UI.
What Im working on is totally developer driven, there is no UI, but simple php class you can invoke and create you CRUD passing a model. And the nice thing is that you can extend the php classes and modify the methods to you specific needs. This, added to lots of hooks in the core code, lets you extend and modify the default behavior very easily and with great power.
Why Im telling this? Because I was thinking on improvements to Pods (the porpouse of this topic) and I will list them here… Chances are that I can put my effort on that if you guys think its a good idea.
1. Hooks – Have hooks on the pods code so I can modify it to my needs in a per Pod basis.
2. datatype File – Handle the file upload with wordPress’ media_handle_upload() and, when its an image, have the option to choose wich size you want to display when building your template.
3. sortable – marking a Pod as sortable creates an extra column (item_order) wich is the default field that will be used to order the results. While browsing the content of the Pod, allow you to order items draggin them with jQuery.sortable
4. datatype color – with a color picker
5. Browsing – possibility to choose what fields will be displayed on the list (when the pod has its own menu on the admin); Make the table look more like the rest of WordPress admin area.
