CodeIgniter Forums
Build My Own Addin - Printable Version

+- CodeIgniter Forums (https://forum.codeigniter.com)
+-- Forum: External Resources (https://forum.codeigniter.com/forumdisplay.php?fid=7)
+--- Forum: Addins (https://forum.codeigniter.com/forumdisplay.php?fid=13)
+--- Thread: Build My Own Addin (/showthread.php?tid=66916)



Build My Own Addin - jamierc80 - 12-18-2016

Hi Everyone,

I was just wondering if people could point me in the direction of a good article/tutorial for creating an addin for CI 3?

Many thanks

Jamie


RE: Build My Own Addin - enlivenapp - 12-18-2016

That all depends on what you want to make.


RE: Build My Own Addin - jamierc80 - 12-18-2016

(12-18-2016, 08:42 AM)enlivenapp Wrote: That all depends on what you want to make.

A couple of ideas for standard functionality I always build in

1, User Authentication based on Roles
2, Front end includes - JS, CSS etc


RE: Build My Own Addin - enlivenapp - 12-20-2016

It sounds like what you're looking for has already been made individually.

You could package your favorite Auth system and Template Engine/Asset manager...

It'll still depend if you want to create an HMVC module, a helper, or something else. My advice is to figure out more specifically what you want and search google for ideas on that particular subject.


RE: Build My Own Addin - jamierc80 - 12-20-2016

Ok thanks, I've have been googling a bit more and thinks it's more of a library/helper that I need for bootstrap elements.


RE: Build My Own Addin - enlivenapp - 12-21-2016

(12-20-2016, 11:23 AM)jamierc80 Wrote: Ok thanks, I've have been googling a bit more and thinks it's more of a library/helper that I need for bootstrap elements.

often what I do is create a config file for the frontend framework.  So, for bootstrap, I create bootstrap.php and put it in applications/config/bootstrap.php

Then add it to the /application/config/autoload.php file.

In the bootstrap.php file, I have all the possible bootstrap changes.

PHP Code:
<?php
//  application/config/bootstrap.php
// make sure it's autoloaded in /application/config/autoload.php

$config["full_tag_open"] = '<ul class="pagination">';
$config["full_tag_close"] = '</ul>';    
$config["first_link"] = "&laquo;";
$config["first_tag_open"] = "<li>";
$config["first_tag_close"] = "</li>";
$config["last_link"] = "&raquo;";
$config["last_tag_open"] = "<li>";
$config["last_tag_close"] = "</li>";
$config['next_link'] = '&gt;';
$config['next_tag_open'] = '<li>';
$config['next_tag_close'] = '<li>';
$config['prev_link'] = '&lt;';
$config['prev_tag_open'] = '<li>';
$config['prev_tag_close'] = '<li>';
$config['cur_tag_open'] = '<li class="active"><a href="#">';
$config['cur_tag_close'] = '</a></li>';
$config['num_tag_open'] = '<li>';
$config['num_tag_close'] = '</li>'

Once you've added all the easy stuff like this, then you could build your library to cover the things the bootstrap config file doesn't cover.