CodeIgniter's got a slew of modules (http://codeigniter.com/wiki/Special:Titles/), but all I can find for Kohana (CI's fork) is http://dev.kohanaframework.org/projects/. Is the assumption that CI modules work in Kohana (or at least can be massaged to without too much effort), or is it just that Kohana's got fewer modules?
Kohana is no longer simply a "CodeIgniter fork" and has not been for a while so sadly the code cannot be simply copied and pasted across.
Also, CodeIgniter does not have modules, just MVC components, libraries and helpers so I'm not sure what you would be copying from CodeIgniter. :-)
Many of Kohana's modules are on GitHub in the following 424 repositories.
This repository (kohana-universe) tracks over 111 modules for you.
The best part about Kohana is that most 3rd party classes and modules can be used within Kohana either with no effort at all or with a simple reorganization of the class structure.
The latest version, 3.0, is very flexible and has very few restrictions on what if allows you to do.
Here's a good place to start: http://kohanaframework.org/guide/using.autoloading
Related
I have used backbone boilerplate on the past
https://github.com/backbone-boilerplate/backbone-boilerplate
I want to use marionette on my next project and I have found this
https://github.com/BoilerplateMVC/Marionette-Require-Boilerplate
My question is if it's a good idea to go with the marionette boilerplate or start form scratch.
As an aside, I'd like to suggest you give Yeoman a shot for scaffolding your first Marionette app. Yeoman works via what are called "generators", and provide much more than the the above Boilerplate MVC can offer you (Chai and Sinon for testing, Bower for client-side package management, etc...). Plus, Addy Osmani, who runs backbone-boilerplates is one of the heads of the project. Check out generator-marionette here.
I haven't used BoilerPlate, but glancing through it, it certainly seems like a valid approach to writing Marionette apps. If you're just getting started it will certainly help you see how the various pieces are supposed to be used. One gripe I've got is the folder structure. I prefer to break my applications down into modules, and then add models, collections, views, etc under each module. But this will certainly get you up and running quick, and there's nothing stopping you from customizing it to suit your needs.
I agree with others here: it is a useless limitation to imitate a folder structure that follows the 'old mvc model for server-side code'. You will remain more flexible further down the road if you think of your application strictly as completely self-containing modules, i.e. they contain their own controller/router/views/collections/templates etc. You can have a separate folder structure for shared code that is not a module, although anything can be made a module :)
Regarding boilerplate code and generators: i think in the beginning you should actually NOT do it, because you won't understand what you're doing. But that's just my personal opinion.
I am trying to learn how to make a site with PyroCMS. I know it is similar to CodeIgniter, but I have not worked on either in the past. I was wondering if anyone could tell me the differences, as most sites talking about PyroCMS will inevitably mention CodeIgniter as an explanation for anything potentially confusing about PyroCMS, but as they are tutorials about Pyro, they will not explain how to program in CodeIgniter. What is frustrating about this is they will not go into many core differences between the two, either, so it's not as easy as looking up a CodeIgniter tutorial and changing a few things.
I was wondering if anyone could tell me the main differences to watch out for that would be relevant for these tutorials. For example, the folder structure seems to be similar, but CodeIgniter has an Applications folder, while Pyro probably has another folder that does the same thing, but the Pyro tutorials don't say what that similar folder is.
PyroCMS is a CMS build on CodeIgniter. PyroCMS is used by individuals, small & medium-sized businesses, and large organizations worldwide to easily create & build a variety of websites & web-enabled applications.
CodeIgniter is an Application Development Framework - a toolkit - for people who build web sites using PHP. Its goal is to enable you to develop projects much faster than you could if you were writing code from scratch, by providing a rich set of libraries for commonly needed tasks, as well as a simple interface and logical structure to access these libraries. CodeIgniter lets you creatively focus on your project by minimizing the amount of code needed for a given task.
UPDATE:
One good overview for PyroCMS you can read here
PyroCMS is built using modular MVC, which means (in short) that each part of the system is its own micro-instance of MVC. This allows the system to be more flexible and cleanly organized than other CMS platforms. PyroCMS describes itself as a simple, flexible, community driven content management system.” And because PyroCMS is powered by CodeIgniter (at least for a bit longer, while the team migrates over to a Laravel backend), it is easy to learn, understand, and own.
CodeIgniter (CI) is one of popular php framework,it is very help full whenever we need to build large websites using php.It has so many libraries,helpers and plugins.But, CodeIgniter is not everything. We will not find 'engine generator' that can build page self. Several frameworks have features like that. For example, they can create web page (that to do basic Create, Read, Update, and Delete operation) automatically. CodeIgniter doesn't do this.
But codeigniter is very useful to decrease our code maximally without loosing functionalists.
I've use symfony and now using codeigniter is there any folder structure
that can be used in scalable applications similar to symfony.
I want to make an application that will be divided in sub-apps and the sub-apps
will have their own modules.
Thanks.
What you are describing is called HMVC (Hierarchical Model View Controller). This means that an application is split up into modules (or as you described them, rather accurately, "sub-apps"). Sadly CodeIgniter does not support HMVC unmodified, however there is a drop-in extension for CodeIgniter which allows you to use a HMVC architecture. [Thanks Wesley]
Alternatively you can use a fork of CodeIgniter which is specifically designed for HMVC called Kohana Framework. The project was originally a fork but has now changed massively and is barely recognisable from the original CI project.
As far as modules go, the go-to solution for CI is the HMVC package:
https://bitbucket.org/wiredesignz/codeigniter-modular-extensions-hmvc/wiki/Home
This is a "drop-in" solution; very easy to install, has been around for quite a long time, and is actively maintained.
Since Codeigniter tries to stay lightweight, you'll find that a lot of important things you need, like Auth or ORMs, are not built in, and you have to use third party code.
A lot of solutions hosted here: http://getsparks.org/packages/browse/latest
And the wiki: http://codeigniter.com/wiki/
I'm building several sites that need similar "modules." For example, the sites may have the exact same login system, forum, etc.
Is there a way I could build these modules once and just "drop" them in these various sites? Some of the challenges I see:
Keeping the code consistent in the various sites. Any changes made to a module should propagate to all of the sites using that module. I guess I need a way to upgrade?
Database: these functionality need to work as part of a bigger application. Maybe the module needs to define relationships with other tables in its respective site.
I'm sure there are more problems. I think I should be looking at this: https://bitbucket.org/wiredesignz/codeigniter-modular-extensions-hmvc/wiki/Home, but I don't have any experience with it.
So, I'm looking for solutions, suggestions, or more problems to this idea.
You can create and use third party packages by adding them to the third party folder (which is new for CI 2). There is not much about it in the docs, but i found this.
http://codeigniter.com/user_guide/libraries/loader.html
You can autoload the third party packages in the autoload file. Packages can have their own controllers, models, views etc.
Interestingly, Phil Sturgeon wrote a bit (http://philsturgeon.co.uk/blog/2010/04/codeigniter-packages-modules) about packages not being modules (in the strict sense of the term), but you could probably use third party packages for what you need.
I would write them as libraries and use Git submodules to manage each module. Phil Sturgeon actually just wrote a great post about doing this in CodeIgniter.
If you're not using version control, I can't see an easy way to sync across all of your applications. Yes, HMVC will let you break apart your application into actual modules, but it won't help in syncing those modules across your applications.
Here is my question about 'Database communication in modular software'
that you may find useful.
I'm little bit familiar with Drupal, and as a modular application, I think it can be taken as good example of how relationships between modules should be defined.
Here is one good post about art-of-separation-of-concerns
I would like to hear if you have run into some concrete challenges, solutions and references concerning modular design in CI.
On my first try, I've only included system/application/models, system/application/controllers, system/application/helpers, and system/application/libraries. I chose those folders because I think those folders contain the code that you want to be properly documented for future reference. What other folders do you think should be included?
To be thorough in terms of your own code. I would recommend the following folders and where necessary have annotated:
system/application/controllers
system/application/helpers
system/application/hooks - Don't miss this out! Any time that you change/extend the CI core, you should definitely document it
system/application/models
system/application/libraries
system/application/language - This may come in useful when implementing localisation
system/plugins - As you're including libraries, it would make sense to include any external plug-ins being used as well
I think you got it covered. The rest is probably documented in CodeIgniter's documentation already.
If you add any plugin/library/whatever that requires to be outside of these folders, make sure you add them later as well.