Module Guide?

Archives Yii 1.0.x Discussions
1

I plan on making a few modules for yii that use Mootools.

I have a few basic questions to make sure that I am following the standard.

Module Directory Structure: (?)

extensions

  -> VsPortfolio

    -> css

    -> js

    -  VsPortfolio.class.php

then VsPortfolio.class.php will extend widget and publish all of my modules assets and do all of the display magic.

If I want to use the mootools library and I have to include it for each of the widgets I create, it almost makes sense to include mootools once before i load the new modules… But the documentation specifically says to avoid that?

Thanks in advance…

2

I guess you are creating a set of widgets in this extension. If so, why don't you create a base class and include mootools there?

BTW, do not name your class file like Xyz.class.php because it would prevent users from using Yii::import() or path aliases.

3

I could do it that way, but if another developer down the line creates some widget that also uses mootools and he is already importing my module then he will have problems. But, it looks like I could check for this case by using CClientScript.isScriptFileRegistered(…)

Thanks for the tip on the blah.class.php, I see that now.