I was thinking on how to "divide" options in a long dropdown TV, and I remember there’s a tag that does this job, "optgroup".
Before starting to hack the MODx core I thought to simply write dividing labels in uppercase, for example, and to tell to the client to "ignore the uppercased options, they’re just to divide group of options".
But I prefer to fix things one time for all so I can, eventually, be able to do things as I wanted next time I need to.
So, a thought start running around in my mind...
why I can’t, if I know how to create a form element, use a chunk?
By simply inserting the (x)html in the chunk I can create every kind of field, size them, add every kind of description (very useful), and why not use snippets (this means portable @SELECTs, @EVALs in the repository, Template Varible forum) instead of @bindings (well, some binding can be time saving).
Another use can be simply adding instructions for the content editor (I mean the person), separate TVs pack (eg. with a <hr />), list data (eg. Your last 10 post).
This can greatly improve the power of TVs which, by the way, it’s a key-feature of MODx for me. Can enhance the manager , as I told you.
What you think?
