EllisLab text mark
Advanced Search
1 of 2
1
   
Explaining the CI source code
Posted: 06 November 2012 04:51 PM   [ Ignore ]
Avatar
Joined: 2012-05-22
12 posts

Hello everybody,

I’m looking for help writing a series of posts that explain the CI source code. Here’s a sample:

http://samehramzylabib.wordpress.com/2012/11/04/uri-php-ci-explained/

I don’t know how many people learn frameworks by reading their source code. But, if you think there’s enough interest (and you have the skills) I would appreciate the help.

All comments are welcomed!

 
Posted: 06 November 2012 05:12 PM   [ Ignore ]   [ # 1 ]   [ Rating: 0 ]
Joined: 2011-02-23
882 posts

Sounds like a good idea. I personally learned a lot from reading through the CI source code.
If you put your posts in markdown language and have them in a GitHub repo I could imagine writing some posts as well. Plus contribution and collaboration is much easier with GitHub.

 Signature 

ignited Community Framework (WiP)  |  Read the User’s Guide. It won’t bite.

STOP! Before posting your questions, remember the WWW Golden rule:
What did you try? What did you get? What did you expect to get?

CI example .htaccess

 
Posted: 06 November 2012 05:25 PM   [ Ignore ]   [ # 2 ]   [ Rating: 0 ]
Avatar
Joined: 2012-05-22
12 posts

I don’t know Git and GitHub?

Usually I edit a WP post in the WP web interface .. use the WP upload button .. view the page .. edit some more .. [Go To step 1 again].

What would my new workflow be?

Is it worth learning Git and GitHub to do this?

 
Posted: 06 November 2012 06:09 PM   [ Ignore ]   [ # 3 ]   [ Rating: 0 ]
Joined: 2011-02-23
882 posts

No, it would not be worth your time learning git to write a blog. However, version control is pretty fancy and can come in handy in many different things - not only in developing software.

Your new workflow would not change that much from your current, except that you would not be editing in a WP web interface but in your favorite text editor - or e.g. Mou for having markdown syntax rendering enabled. After you created a page you would add it to version control and push the changes to the GitHub server (if using a gh-pages branch the page would also be rendered automatically) and you can either create/edit another topic or keep editing that page.

The best advantage I see in Git is decentralized version control i.e. you don’t even need a working internet connection to use git - you can have a local git repository with all its benefits and a smaller footprint than SVN.

But as I said: Just for writing theses posts it wouldn’t be worth your time.

 Signature 

ignited Community Framework (WiP)  |  Read the User’s Guide. It won’t bite.

STOP! Before posting your questions, remember the WWW Golden rule:
What did you try? What did you get? What did you expect to get?

CI example .htaccess

 
Posted: 06 November 2012 08:35 PM   [ Ignore ]   [ # 4 ]   [ Rating: 0 ]
Avatar
Joined: 2012-05-22
12 posts

Okay Phil. I like your idea. As a matter of fact I’m in the process of writing a blog post (My New Collaborative Blogging Workflow) about how I’ll implement your idea.

The post is being done my old way so if you keep checking back on it you’ll be getting newer stuff each time.

 
Posted: 06 November 2012 09:31 PM   [ Ignore ]   [ # 5 ]   [ Rating: 0 ]
Avatar
Joined: 2009-05-17
1415 posts

Rather than a detailed explanation of how CI works, I’d rather see a detailed flowchart type illustration. The problem with the detailed explanation would be that it could be almost as hard to follow as the code itself. This is what I was thinking when I looked at your example.

 Signature 

Brian
Brian’s Web Design - Temecula
Community Auth - CodeIgniter Authentication Application

 
Posted: 06 November 2012 11:12 PM   [ Ignore ]   [ # 6 ]   [ Rating: 0 ]
Joined: 2011-02-23
882 posts

You’re right @skunkbad, a flowchart of the actual CI business logic would be very helpful, too, and would also give more insight on how CI works.

 Signature 

ignited Community Framework (WiP)  |  Read the User’s Guide. It won’t bite.

STOP! Before posting your questions, remember the WWW Golden rule:
What did you try? What did you get? What did you expect to get?

CI example .htaccess

 
Posted: 07 November 2012 12:46 AM   [ Ignore ]   [ # 7 ]   [ Rating: 0 ]
Avatar
Joined: 2012-05-22
12 posts

Yes, some day I’ll make a flowchart but first I need to really understand all the source code.

 
Posted: 07 November 2012 12:53 AM   [ Ignore ]   [ # 8 ]   [ Rating: 0 ]
Avatar
Joined: 2012-05-22
12 posts

I think having an explanation of the source is important because when I’m in the middle of a CI project I may need to look at the framework source. I’ll know where to look but I won’t have the time to figure out exactly what it does. In that case I find it better if the CI source has been already figured out.

 
Posted: 07 November 2012 06:22 AM   [ Ignore ]   [ # 9 ]   [ Rating: 0 ]
Avatar
Joined: 2012-01-09
117 posts

Hey, just wanted to drop in a suggestion.

CodeIgniter 3.0 is not far from its release and its codebase is WAY more different than the 2.1.x versions, so it might be better if you don’t waste your time writing on a soon to be obsolete version. Checkout the GitHub repo at https://github.com/EllisLab/CodeIgniter

 
Posted: 07 November 2012 12:57 PM   [ Ignore ]   [ # 10 ]   [ Rating: 0 ]
Avatar
Joined: 2012-05-22
12 posts

Thanks @narfbg. That’s a very good point. I’ll do CI 3.0. BTW I think I’ll be doing it on GitHub instead of WordPress. I’ll let you all know once I get the ball rolling.

Currently I’m still working on:

My New Collaborative Blogging Workflow

 
Posted: 07 November 2012 08:40 PM   [ Ignore ]   [ # 11 ]   [ Rating: 0 ]
Avatar
Joined: 2012-05-22
12 posts

I’ve never used a version control system. Can someone look at my blog post and tell me something helpful or guide me?

 
Posted: 08 November 2012 01:00 AM   [ Ignore ]   [ # 12 ]   [ Rating: 0 ]
Avatar
Joined: 2011-04-13
256 posts
Narf - 07 November 2012 06:22 AM

Hey, just wanted to drop in a suggestion.

CodeIgniter 3.0 is not far from its release and its codebase is WAY more different than the 2.1.x versions, so it might be better if you don’t waste your time writing on a soon to be obsolete version. Checkout the GitHub repo at https://github.com/EllisLab/CodeIgniter

Any guesstimations on a ballpark release date? IE: a specific month in mind?

 Signature 

Expert Web Development Backed by LIFETIME Guarantee
CI-Foundation v1
InfinityTracker - Project Management

 
Posted: 11 November 2012 12:02 PM   [ Ignore ]   [ # 13 ]   [ Rating: 0 ]
Avatar
Joined: 2012-05-22
12 posts

Hey Everyone,

I’ve started the repository:

Sameh-R-Labib / CodeIgniter-3-Source-Explained


I’m not ready to contribute yet; However, you’ll find instructions in README.md.

 
Posted: 24 November 2012 10:14 AM   [ Ignore ]   [ # 14 ]   [ Rating: 0 ]
Avatar
Joined: 2012-05-22
12 posts

I’ve made improvements to the GitHub repository for this project.

I’m inviting you to look at them.

Project link

 
Posted: 24 November 2012 11:13 AM   [ Ignore ]   [ # 15 ]   [ Rating: 0 ]
Avatar
Joined: 2011-08-08
524 posts

@narf

That’s a nice news, what are the new features of CI-3.0 ?
Can you list them all.

 Signature 

Stick with it, practice it and have fun with it.

 
1 of 2
1