its working fine with CI2 also i have checked that for CI2 you have to put MY_Loader file from libraries to core folder, and for model you have to extend with CI_Model its working really fine

good job mate, will be integrating the changes at some point today.

umefarooq - 29 October 2010 09:08 PM

its working fine with CI2 also i have checked that for CI2 you have to put MY_Loader file from libraries to core folder, and for model you have to extend with CI_Model its working really fine

Thanks. I’ll try it

In HMVC I can create 2 or more modules folders, as example: one in application directory and one in applicataion/third_party directory. Can your widget do the same thing? It would be nice if this feature applied in your widget. Thanks

I’ve put MY_Loader file from libraries to core folder, and changed “extends Model” to “extends CI_Model” but it still doesn’t work with my CI2.0. It still returns a blank page. i think the problem in library “widgets.php”. Can you re-upload your code for me? Thank you very much!

first sorry for late reply, now in CI2.0 widget.php has become library now you have to load widget.php also for CI2.0 either use in autoload or where you want to load use $this->load->library(‘widgets’) will work.

That’s great! Thanks @umefarooq. I did it. It worked in my CI2.0. Thanks for your support!

Now widgets work with Modular separation(HMVC) you have to create widgets folder in module, so every module will have different widget, with version you can access module model and views just in normal way. if you are using CI2 just put files as it is. if you are using CI1.7 just copy widgets and widget functions from MY_Loader class and put in Moulder MY_Loader class file can be download from my first Post

I think it would be better to code it to use just a widgets directory.

This way they could be used anywhere.

InsiteFX

you can access widgets from widget main directory along with modular