Hello to all developers in the house, my team and I are about to start working on a web project using the the codeigniter framework.
The team comprises of 3 back-end developers and 2 front-end guys. We are going to be using github for the collaboration(and version control). Now, my question is:

Do the front-end developers also have to install codeigniter locally?
if they don't have to, how then do they get access to the php variables that will be supplied by the backend developers?

Somebody please help ASAP, your contribution is highly appreciated.

omoelu1:
Hello to all developers in the house, my team and I are about to start working on a web project using the the codeigniter framework.
The team comprises of 3 back-end developers and 2 front-end guys. We are going to be using github for the collaboration(and version control). Now, my question is:

Do the front-end developers also have to install codeigniter locally?
if they don't have to, how then do they get access to the php variables that will be supplied by the backend developers?

Somebody please help ASAP, your contribution is highly appreciated.

Of course they have to, they will be in charge of the View part of your CodeIgniter (MVC) project. They write the view while the backend guys deal with the model and the controller.

I dont think they need to install any CI, all they need to do is do wjat they do best and mail it to you guys for integration in your system.
Please, dont make life unbearable for this guy.

talk2hb1:
I dont think they need to install any CI, all they need to do is do wjat they do best and mail it to you guys for integration in your system.
Please, dont make life unbearable for this guy.

But the team is using GIT (he talks about version control) , why will you switch to email when your team already has a standard tool? What the FE guys need to do is write and structure the interfaces, the BE folks will integrate the little bit they need to do. It's that simple.

Urine:

But the team is using GIT (he talks about version control) , why will you switch to email when your team already has a standard tool? What the FE guys need to do is write and structure the interfaces, the BE folks will integrate the little bit they need to do. It's that simple.

That means the UI guys will have to learn git command, and CI procedure, which is bad for production.

It is called Model View Controller design pattern.

The FE developers can work on the site without Codeigniter. It is not necessary and it is unimportant.

What FE Developers does is to work with client side scripting and markup languages. They don't need to have an understanding of how the application will work.

After they must have finished developing the interface, the BE Developers integrate and modify it to work with the Controller.

It is unnecessary for FE to have any technical knowledge. Theirs is to build the interface. Yours is to integrate it into the system.

Adesege:
It is called Model View Controller design pattern.

The FE developers can work on the site without Codeigniter. It is not necessary and it is unimportant.

What FE Developers does is to work with client side scripting and markup languages. They don't need to have an understanding of how the application will work.

After they must have finished developing the interface, the BE Developers integrate and modify it to work with the Controller.

It is unnecessary for FE to have any technical knowledge. Theirs is to build the interface. Yours is to integrate it into the system.

GOD bless yu bro

Adesege:
It is called Model View Controller design pattern.

The FE developers can work on the site without Codeigniter. It is not necessary and it is unimportant.

What FE Developers does is to work with client side scripting and markup languages. They don't need to have an understanding of how the application will work.

After they must have finished developing the interface, the BE Developers integrate and modify it to work with the Controller.

It is unnecessary for FE to have any technical knowledge. Theirs is to build the interface. Yours is to integrate it into the system.

Sir does it mean the front end guys don't need d Form Helper?

Urine:


Of course they have to, they will be in charge of the View part of your CodeIgniter (MVC) project. They write the view while the backend guys deal with the model and the controller.

thanks so much. your contribution is so much appreciated.

malawi101:



Sir does it mean the front end guys don't need d Form Helper?

No dey dont need to have an understanding of how codeigniter works.

Once they've designed the interface, the BE developers will be the one to put all that.

Take for instance a blog list page. The FE developers will create an interface for the blog list. After which the BE developers will edit it and put a loop where necessary.

There are lot of stuffs you can add to codeigniter to make it intuitive to use.

HMVC is one of them. It allows you to create independent modules of a MVC. That is, you can have a login module and make it usuable in other applications you will build. The module will have its own model,view, and controller.

Also, you can add theming to your application just like wordpress. Codeigniter allows that.

Another great one is a templating system. Smarty is a great one. and talking of caching web pages, it allows that.

While smarty may not be of essence to you, just think of having all your views in one folder. That is theming.

Also think of having independent modules for your MVC.

God bless

omoelu1:
Hello to all developers in the house, my team and I are about to start working on a web project using the the codeigniter framework.
The team comprises of 3 back-end developers and 2 front-end guys. We are going to be using github for the collaboration(and version control). Now, my question is:

Do the front-end developers also have to install codeigniter locally?
if they don't have to, how then do they get access to the php variables that will be supplied by the backend developers?

Somebody please help ASAP, your contribution is highly appreciated.

All the previous comments have a point but ultimately it depends on how your team works, most people on my team are full stack so we all work on CI. The major challenge for you here is if the FE guys work out of CI the BE guys will still do a bit of FE coding, if you are cool with that then you should be fine.

For example the way you will design a header and footer section with your normal HTML/CSS is not the way you will design it in CI. In CI you will write it once and call it whenever you need it on an interface. So like I said earlier, it's a matter of preference.

Adesege:


No dey dont need to have an understanding of how codeigniter works.

Once they've designed the interface, the BE developers will be the one to put all that.

Take for instance a blog list page. The FE developers will create an interface for the blog list. After which the BE developers will edit it and put a loop where necessary.

There are lot of stuffs you can add to codeigniter to make it intuitive to use.

HMVC is one of them. It allows you to create independent modules of a MVC. That is, you can have a login module and make it usuable in other applications you will build. The module will have its own model,view, and controller.

Also, you can add theming to your application just like wordpress. Codeigniter allows that.

Another great one is a templating system. Smarty is a great one. and talking of caching web pages, it allows that.

While smarty may not be of essence to you, just think of having all your views in one folder. That is theming.

Also think of having independent modules for your MVC.

God bless

Tanx dats informative

Adesege:


No dey dont need to have an understanding of how codeigniter works.

Once they've designed the interface, the BE developers will be the one to put all that.

Take for instance a blog list page. The FE developers will create an interface for the blog list. After which the BE developers will edit it and put a loop where necessary.

There are lot of stuffs you can add to codeigniter to make it intuitive to use.

HMVC is one of them. It allows you to create independent modules of a MVC. That is, you can have a login module and make it usuable in other applications you will build. The module will have its own model,view, and controller.

Also, you can add theming to your application just like wordpress. Codeigniter allows that.

Another great one is a templating system. Smarty is a great one. and talking of caching web pages, it allows that.

While smarty may not be of essence to you, just think of having all your views in one folder. That is theming.

Also think of having independent modules for your MVC.

God bless

Thanks so much.

efreaky:


All the previous comments have a point but ultimately it depends on how your team works, most people on my team are full stack so we all work on CI. The major challenge for you here is if the FE guys work out of CI the BE guys will still do a bit of FE coding, if you are cool with that then you should be fine.

For example the way you will design a header and footer section with your normal HTML/CSS is not the way you will design it in CI. In CI you will write it once and call it whenever you need it on an interface. So like I said earlier, it's a matter of preference.

You have really helped a brother.