Design Logic Help Requested

Hey @cartalot...I just read what I believe to be "the thread on this board about the autocomplete file" that you mentioned above. I saw that you contributed a autocomplete config file that was working for you. I've copied it over to see if it's something that might be helpful for me, but I thought I'd ask if you had made any significant changes/improvements to the file since posting it. Do you think your solution has any specific pitfalls I should watch for? Or have you found any other sources that you think work better?

the only drag is that you have to put in your model names like in the example. otherwise its really awesome.

Also, in response to your final paragraph (which I seem to have missed earlier)...I know that CI documentation talks about moving the Application folder, but is there much about making a multiple application folder structure? Either in CI Docs or elsewhere that you know of? Of course, I can google this and that might answer my prematurely asked question, but if you have any input, I'd certainly take it in.

Some people get in this mode where they think the application folder has to be named 'application', and the system folder has to be named 'system'. This is even implied in the docs for upgrading. The main index.php file is where the file path for the application and system folders are. So you can go in that file, and change those settings. Then you can name your system folder something relevant like "system306" and your application folder "alphajuly2016" .

Then by creating a folder - with the main index.php file inside of it - that version of the application is directly available. So like a folder called 'alpha' - you set which system and application folder its using - then example.com/alpha will pull up that version. example.com/beta can pull up the beta version. and you can link between the two of them.

So then for example - if you have a bunch of public website functionality. And an admin area with completely different functionality. There is no reason they need to be sharing the same application folder - and there are many reasons why they should not be. Similar if you are building something - when you have something stable you can split it off. And then when you are working in your alpha folder and you do something to a route file that kills the application - you have not affected your beta version because its in a completely separate application folder.

I strongly support you dumping whatever 'addition' to codeigniter and learning how to use the framework as it is. There are few to none really great codeigniter tutorials out there because they are created in a hurry by people trying to teach one point. Developing a maintainable complex application is completely different. As soon as you add some 'custom' library etc to 'make things easier' you have added another layer of complexity (and confusion). Don't worry about being 'dry' or saving a line of code - make things as readable as possible. Again the most helpful lessons i've gotten have been from Robert Martin Clean Code lectures.