Thread

@Lab Technician
Thanks. I won’t bother you again on this topic (at least for 6 months or so).

My First Module Contribution: a simple module that can autoload views - Pages! It is useful to help migrate a old-school, page-based website to a CI/HMVC site.

To use, create a new module directory called “pages” and put these files into pages/controllers and pages/views:

SNIP, SNIP, SNIP - I moved this post into the Wiki.

Pages - HMVC Module for Modular Extensions - Helps migrate Static page-based sites to CI

Feedback?

Good work sophistry, I will be trying this out. Thanks.

I’ve coded up another module: PhotoBox - a simple photo gallery.

PhotoBox Module for HMVC - Modular Extensions

Hey, I’ve integrated it into my Tarichi for next release. It’s nice, for extended module (I called extra). So, installation just place in one folder. Fiuuh…. This thing help me so much

Excellent work sophistry, It’s good to see people enjoy using Modular Extensions as much as I do.

A photo gallery module is something I can use for sure, Thanks man. 😉

can i use both this ME and Matchbox at the same time?

I want to use Matchbox just like Component on Joomla, but i need ME too. And I want to use ME like Module on Joomla.. Can I?

can i use both this ME and Matchbox at the same time?

ME does everything Matchbox does, and then some, you don’t really need both.

so, cain i use ME for 2 different function?? one for modulation like Joomla Components, and one for modulation like Joomla Modules??

I never bothered with Joomla, so I don’t know the functionality.

ME allows you to use Modules as an organizational structure like Matchbox and it also provides HMVC features not found in Matchbox or CI

mmm…..

yes, but what i want is 2 different of modules function, one function is work like component that accessible via url like gallery, guest book, etc and one work like module that cannot be acceesible via url like menu, sidebar, login form, etc. And i want to organize them into different folder.

sorry if my english make you confuse.

@Adods… yes, ME can do what you describe:

1) URL access to complete, self-contained modules where all resources exist in their own, single directory.

2) access small bits of each of the modules from within other modules - so in your example, you want a menu, sidebar, login form and each of these can be in their own directory or in a combined directory.

basically, ME makes CI more flexible. it lets you group related resources together in directories and access them from outside. currently, CI is designed in a way that controllers cannot “talk to” other controllers so you have to be clever in OOP and code architecture if you want to combine pre-existing resources. but, with ME in place you can build a module and then “expose” functionality through the controller like it is a library or an API. so, controllers can be http-facing or internal.

cheers.

BTW, your english is good, and your concepts about programming are better! 😉

wow.. that’s great.. but can put module like menu or login form separately from normal modules folder, like i put normal modules on ‘Modules’ dir and menu module on ‘Blocks’ dir??? And is there any example for this new ME? because all example i found using older version.

This may be an idea for a new feature, add a source directory to the module loader.

All URL based calls are directed to APPPATH.‘modules/’ while internal module calls can specify a module base directory.

Any thoughts?

OTTOMH… that sounds like extra complexity for not much gain.

why not just put the “Blocks” in a module directory called Blocks? You can have multiple controllers that do each of the jobs required.

What would be gained by allowing the developer to load resources from a directory outside of the modules? Am I missing something?