Ability to compose a project linked to the datas of another project.

Ability to create the component configuration page, the same than for a regular view.
Ability to create a data structure for the configuration the same way than building regular table.

Add the component version to the name of the zip file.

Builder repository for keeping your reusable and sharable images and icons.
Once achieved, you will be able to customize better your creations.
Cpanel Icons, Icomoon in the pages titles, ...

Organize better the bricks and custom the positions.
Ability to clone a layout
Ability to instance faster the fields with one click.

Ability to insert and keep you own regular expressions, and share them with the community.

Ability to import the language strings from your translated component before to generate it again. Your translations will appear in the generated component and will be completed with the eventual new strings.

Offer the ability to import a component and recreate the structure from the SQL file, the dataset, views and layouts.

Ability to reorder the tables to change the default order of the menus.

Ability to create a JSON Form inside a form.
Including a JSON field inside a JSON field will let you the ability to create JSON trees of datas.

Autocompletion helper in the builder to edit faster your creations.

Ability to edit the same project between a team of users.

Ability to export / Print the database diagram.

Ability to take snapshots of dataset and to reload it in the sandbox afterwards.

Ability to group tables between themselves for a better user experience.
The tables can be organized in categories depending their utility.
It would not affect the resulting source code. Only for editing.

Ability to create views in a calendar shape. Using the date/time fields from the table.

Ability to create a "Static Content" brick in the builder and be able to edit customizable zones, whatever can be translatable texts, Joomla articles, modules position, ajax layouts from anywhere from your component. etc...

Ability to render any layout from any view, using the "layouts" and JLayout CLass.
This would give the opportunity to build dashboards or to load any data anywhere, including in AJAX mode.

Ability to hide a field (and label) when its value is null in the fly view.

Ability to leave a PHP comment for every brick (in the builder)
It would write PHP comments for the developer inside every file relative of this brick.
For views / XML / templates, this can be a very nice feature for searching the parts of codes for customization.

Ability to disable scrollbars in modals for instance.

Ability to define a default size for the thumbs,
Or to define predefined sizes in the component configuration.

Ability to define a linear (or tree), step navigation.
This would allow to go back in navigation.

Option to send a notification mail after creating an item.

Multi languages contents. Adding some fields to create the versioning of items by language.

Wizard for implementing a Map.
List of the features :

• Google Maps & OpenStreets, maybe others.
• Ability to drag and store the position value.
• Geocoding and save automatically the positions
• Batch Geocoding

Simply add the wizard to guide the user to create the correct names : publish_up, publish_down
Joomla! does it alone, but this wizard could instance the required fields.

Simple wizard to implement the SEO meta tags of an item directly in the meta keywords of your page.

Ability to transform a table in a recursive tree of datas.

Ability to keep items with their relations in the session. The shopping cart is NOT a complete shop, only the session stack.

Ability to define more than one field in the source

Read the user IP and keep in a IP field.
This feature can also read the full SERVER request containing the agent, the referral.. and much more.

Ability to free an authored and protected item, to the public.
This option would be directly available from the author user.

Ability to make multiple components working together :

• Ability to link Foreign-Keys and any relations with third components.
• Can interact others components even if not build with cook.
• More connectivity with Joomla! native components.
• Ability to split your big projects in parts

Ability to generate modules based on your component MVC

A simple way to return back to the previous page, or to define the next page is to define the return parameter in the URL. It needs to be encoded 64. Lot of Joomla components works that way.

Introduce the triggers in the component, in a maximum of possible places

• Controller
• Model
• View
• Helpers
• Fields
• ...

Generate scaffoldings of plugins related to your component.

Improve the ajax capacities in order to edit in place and replace the modal box way. Avoiding the iframe, doing it all in the same JS document. Modal box has sometimes problems in case of file upload, rich text, and checkout task in case of 'cancel' hit.
For all those reason, this feature promise you a full JS tiny framework, or a rich framework such as

• Angular
• Ember
• Backbone

Introduce an option to avoid JDom from your components and use the Joomla native JHtml classes.
It would reduce the capacities of your component, but the component would be standalone.

Ability to extend the ACL for a specific item.

Ability to restrict the access of the pages using the ACL.

Ability to execute a task over a bunch of items.

Ability to choose the default ordering for a combo list.
Automatically on the 'ordering' column when the ordering wizard is used.

Paypal integration

Ability to create menus and tree of menus integrated to the component. Would be usefull for the back-end.
About the front-end, the custom menu could be automatically installed in the native joomla! menu manager. (ie : such as Kunena does)

Ability to create views / layouts not based on datas or model. Would include toolbar and controller.

Ability to connect and authenticate with another web 2.0 account.

Improve the redirector engine.

• Uses a XML file to configure it, or something equally flexible.
• Integrate common pages : 'home', 'contact', 'etc'...
• Keep historical in session to go back in real previous page, with a long stack or unlimited.

Ability to read / write native user profiles informations.

Ability to change the DB engine choosing between : MyISAM / InnoDB

Adding the basic requirements for your applications to be supported insinde the "JMS multisites" environement

Ability to export a list, a filtered list or the results of a search (CSV, JSON)

Ability from the builder to snapshot the database structure.
This feature would be able to detect the changes between two databases structures and automatically create the version step SQL script including : CREATE, DELETE, ALTER TABLE, RENAME ...

Ability to connect your component to an external databse

Ability to build tables based on third component's tables, such as #__users.
The created tables in the component would act such as table extension.

Propose some datasets ready to use.

• Civil informations (M., Mrs, ...)
• Geographic database
• ...

Ability to override (DROP) the existing database on the component update.

Option to disable the database installation of the component at install.
Asked from developers who simply want the files upgraded.

Ability to change the field name of the primary key. (Actually always 'id')
Only the F.O.F. version can support that at the moment.

Ability to filter on N:m / N:1 relations.

Ability to edit multiple different models in the same form.

Ability to manage sub forms.

Ability to display the fields in line or in a different HTML structure.

Ability to instance a static text in a row of a form instead of a regular control.
It would contains some explanations about the fields below. It could be placed anywhere.
It could also be introduced a "separator" field following the same concept.

In some case, if a FK refers to a table containing 1:1 link, the form would be able to show the information of any field of any extension of this table. Very often with the #__users table.
Example : One of your forms instance a Foreign Key to an account. This account link with #__users table in 1:1.
Then in your form you could show the 'username' property of the users table.
Only for this exception (1:1), Cook should not limit the FK combo to the first root level only.

Improve the "link to FK" feature. (Grid and Fly)
Ability to compose an url from the database item.

Option to customize the datetime picker and use bootstrap UI component: bootstrap-datetimepicker

Captcha field.

Integrate the native Joomla! Tags field.

Improve the jQueryFormvalidator implementation, or change validator engine.

Foreign Key Modal Picker

Ability to link your component to a Joomla article, and to pickup the article with a modal picker in the forms.

Ability to use the native Joomla categories as regular Foreign Key

Ability to autogenerate a value in the form.

• For integer : Incremental, random
• For string : Random, from user data, from Third component ...

Stores Images / Files as binary into BLOB Type

Ability to show a file icon as display for representing the mime-type (based from file extension)

Avoiding the given date format and use the date time formats from the language files.

The values states of the filters are stored separately based on the context of the page. That way the filters do not apply for others calls (internal, ajax, combos). But those contexts are actually based on the layout name. Different layout, different filters states.
This feature request is the ability to share the same filters states between layouts of the same view.

Review the HTML layout for the filters.
Use or not the searchtools layouts given by Joomla ?
My opinion is 'searchtools' is very complex and difficult to custom. Some Cook filters goes beyond the simple combo (ajax, ranges, dates, multiple searches possibles ...)
Creating our own filters layout file can be an option proposed in the builder. Because the native Joomla layout can be ugly / unconsistant for the filters Cook propose.

Ability to create custom filters in the builder.

Ability to add an item inside a combo box list for adding a Foreign Key item directly from a child form.
This features has to be pure Ajax.

Ability to show the layout alone (&tmpl=component) for printing.
Ability to send the page layout through email.

Ability to copy an item, with the propagation of the Foreign Keys.

Add dividers in the toolbars

Ability to rename the copied item with a suffix (ie : Item Copy 1)

Integrate other payement gateways and methods :

• CB card
• Skrill
• Bitcoin
• Money transfert

Ability to custom your company informations and reprint all your past bills.

Ability to custom the control panel icons.

Ability to reuse the item row informations to rename the file once uploaded.

Functionality to define a default image to use in a preview of a missing or empty image.

Store the files in the media folder, instead of the 'files' component's folder by default.

Ability to upload and manage video files. Including a video player.

Ability to fork the language files.

Configuration button to disable the forks of your component for testing.
It would ignore the fork directory without needing to rename both folders.
It would ignore the templates overrides, and so on.

ability to change the Joomla template of the destination hyperlink.

Ability to use images thumbs inside radio buttons

Improve the ordering functionality for mobiles

Fix the problem with IE. To be confirmed.