Hi Admin,
just a thought to extend the function of the TODO setting in config

The idea would be to have an area to store notes of things that need to be done outside the Cook environment

For now i have simply..,
- created an extra Text+ (rich text) field called "todo"
- created a form brick called todo in each layout (where needed)
- Placed the todo field into the todo brick
- Downloaded component
- dropped the todo brick code <?php echo $this->loadTemplate('todo'); ?> into each layout under the scissors and dotted line

Just thought this would help us to...
- "remember" what needs to be done outside of Cook if we have not visited that component project for a while
- assist clients to communicate any additional changes needed to builders in the design / pre-production phase
- If this data was transferable from the sandbox to your download it would be an asset as well (JMO)

- maybe there could be a field type called dev_cook_todo and if that field was present in layout it would be displayed would be displayed for that layout below the scissors and dotted line

Just a thought...

+1

Great Idea!!!

Not really as you say because you are associating the text in a table field, so it creates an extra field in DB wich is not clean.
It could eventually be better in the 'params (or attribs)' field, in JSON.

But this is definitivly not a solution because you set it at the item level, so if you change item, the TODO have changed contents.

I think if the TODO is relative to a work on the page, layout or table, it must be done another way.

TEXTS IN THE PAGE
One of the future devs is the integration of html/strings anywhere in the component. (Translatable and editables in place)

Try to create a table for that, storing any types of strings for anywhere in component. Give their a position name, and other params if you want (Published, ACL, etc...)

Then, write a helper function that is rendering the texts to output them where you want.

Use-them for TODO instruction in the production team, or use them as your please.
You will then be able to easily change the texts strings of your component.

Thanks Admin,
I did see before posting that my current method was not ideal but really just needed a quick solution to communicate required changes pre-production

i did think of including a simple file that would be read and edited as required

i like your alternate table idea for larger development environments

Anyhow thanks for your input