hey was it was a try to find any functions to add to the modx cms.
and there is obviouls a very big one that makes me sad about modx.
I and I suppose any other developer would love to hape a better template management.
You suppose WAY wrong. Front end devs LOVE ModX (which actually created a bit of a ruckus back about a year or so ago when the backend and the docs weren't quite ready for all of us who jumped in with both feet!) I've templated for a bunch of different dynamic programs-- WordPress, PHPld, Esyndicat, Drupal, TextPattern, CubeCart, Zencart, Joomla, Joomla/Virtuemart, etc. . . . and ModX is pretty much the easiest to template of all of them, with no frontend code decisions forced on us from backend, no stupid overrides, nor any of the other idiocies other dynamic programs force on us. It's also the most flexible, allowing me to easily template different areas of the site differently, hell-- different areas of each DOCUMENT differently if I wish, and allows me to create a completely tableless and accessible site with most any of the bells and whistles I might want. It also gives me three different ways to structure content additions (chunks, templates, snippets) which, in various combinations, allow me to make this pup jump through multiple hoops. Better template management compared to what? Hands down, ModX gives me the most flexibility in making the frontend look exactly the way I wish it to, compared to any other dynamic program I've templated.
I suspect you might not truly understand how ModX templating really works if you're making a statement like that.