Hi,
Thanks for your honest reply, though you do it again.. make reference to Morph being "seriously flawed" without knowing the whole truth.
So, from my particular and personal perspective Morph today is a seriously flawed Joomla extension - I understand that you have chosen to go down that road for good reasons of your own and I recongise that it may perform marvellously well in other contexts.
and
&tmpl=component - Morph breaks that too.
Morph does not break it, it just disables it for security precautions, this was a user requested feature because many people don't want it enabled if they dont use it. Users can set Morph in a mode where it is hard for hackers to see it is Joomla as all traces of it can be removed.
The idea is to give users as many options as possible to control all aspects of their website. We have tried to include options that cover a broad spectrum of common tasks Joomla developers/ website builders do most often. Much of our options are from user feedback over a 6 months beta period and our users love the flexibility.
Saying its flawed because a feature you would need as a developer is turned off... especially a feature 90% of other users wont even use or need or even consider. So why not turn it off? The defaults in Morph are set to the most commonly used setting, and in this case, it is disabled because most users wont need it. Me thinks you are looking through "developer covered glasses"
You can see Morph's debug and performance options here. These cover a wide variety of options and choices for users.
![](http://www.prothemer.com/assets/staff/andrew/perf.png)
![](http://www.prothemer.com/assets/staff/andrew/debug.png)
In my opinion - which you may well disagree with - a robust Joomla template should not disable core Joomla functionality at all and certainly ot without a clear and comprehensible warning to all users that it may well break otehr extensions. The MooTools library is core Joomla functionality. I understand it is entirely possible to set JQuery into no-conflict mode so that it will co-exist with MooTools.
Yes, I disagree... you are assuming all extensions use mootools... but they dont. In fact, many many use jquery and I did say that we can check if a component is loading and needs mootools. We can include this for Chronoforms, so users in future will not need to enable it, it will do so automatically.. we just need to add it once and that's it. I also said jquery is in no conflict mode so it wont conflict, but that's not why we disable mootools, its about the performance.
The point is... why load a 65kb file when its not always needed? 65kb... that's a lot when you look at really optimizing everything and more so when its not used... just sitting there. Many of our users keep it disabled as they don't need it, but many do, the key is they have the option to do so... ie the flexibility without having to dig in any code.
Our entire JS with everything together is only 23kb for ALL Morph's features. So I ask, why on earth would we push that to up by another 65kb unless its required.. and to say it is.. is again assuming that every Joomla website uses components that rely on mootools.
We do have on our roadmap to include an equivalent mootools option for all our features, so the user can essentially choose between jquery and mootools with Morph.
ChronoForms too has some faults and bugs - Max, the developer, is aware of most of those. It is a complex extension capable of helping Joomla jump through some advanced hoops that ae not always easy with other extensions.
Yes, I agree, it is a great component and I have used it before (not in a while) and if the bugs I had last time I used it are fixed, I will certainly be using it again in the future.