Quote from: ChuckTrukk at Jan 23, 2009, 03:23 PM
From: http://modxcms.com/forums/index.php/topic,32354.msg196885.html#msg196885
Not sure how that link pertains...
- This seems more difficult to me to make a new ’module’. How has modExt made ’modules’ better/faster for you?
Instant usability benefits, automatic validation, drag/drop + grid abilities, automatic styling to current manager style, ability to create fully-functional pages with web2.0 capabilities in less than 30 minutes.
- To work within the current manager context, is it pretty much a requirement to use modExt to work correctly?
No. You could technically do whatever you want. MODx will automatically include the css/js headers including Ext/MODExt if you have the ’haslayout’ field set to true on the modAction object you create. If you turn it off, it will output a blank page with only the controller’s content inside. So you could have your own header files that use jQuery or whatever. You’d lose the MODx navigation and other things, but you get the idea.
- Does this mean if I want to make a module (or convert something to a module), I need to drop jquery (for instance) and my current setup? (example might be a gallery module/snippet)
No.
You could, for instance, set ’haslayout’ to false in your modAction, copy the header.tpl from manager/templates/default/header.tpl, and change the Ext adapter to use Ext’s jQuery adapter - allowing you to use both. I haven’t tested this, but it should work.
