I Like this tool. But im really confused. I want to create a standard Status field. Published/Unpublished etc.

I add the published field using the wizard (Which one assumes creates the correct type of field with a standard name...) and then in the form i want to create a dropdown like every other joomla component has for the status....

But all i get is a radio button. Am I missing something with the builder - or is it just unfinshed or what?

And before any one asks - NO - I havnt done the "tutorials" - I cannot follow them at all, they make no sense to me what so ever.

Is there ANY decent documentation or tutorials on line that explain how Cook works other than the basics of table and layout creation. Like - What it can and Cant do - What the features actually do - Like should i use Jquery or Moo tools? Should my DB automatisms be Model or Table ....

With 2.5, you can now use the 'State' filter.

But for the moment, you can only see what it wil look like, because your changes in beta 2.5 will not be kept.

About the documentation, this is the next step. For the moment, the forum is the knowledge base.
Wich tutorial makes no senses ? N-M tutorial or the videos ?

You should use JQuery. MooTools will not be used anymore. With Cook 2.5, MooTools is deprecated.

DB Automatisms :
There isn't a standard here. Those functions are for handling aliasing, creation/modification date, etc...
After saving/updating an item.

- In model : you have more freedom to customize, but also written twice (front / back)
- In table : more security because it is always called, even if you call your table from outside of model with JTable. More close to de data treatments. Written only in one place.

I have a preference for 'Table'

Thousands of apologizes for still not having documentation. I had to deal with priorities because Cook has been released with already a lot of features and it took a long to stabilize and find the standards.
Without a stable standard, the documentations will have been very confused with a lot of updates and changes in the source code.

Now with Cook 2.5, I hope the name of the functions and classes will stay forever in this way, because It looks like Joomla have almost accomplished this too.