Thread

i think thread title is clear ?,
so what do you need and you didn’t find it in codeigniter ,
some of us will request libraries and plugins, and the others who leak the ideas will create it,

speaking about myself , i need a twitter and RSS reader writer , i have found a good one for twitter but still can’t find a good one for RSS…

I think I would lose some respect for CodeIgniter if it had a twitter library.

well, some extra libraries repository will be a good idea , don’t you think so?

@Blaze Boy: If you’re still looking for an RSS library check out Ellio Haughin’s port of SimplePie as a CI library http://www.haughin.com/code/simplepie/.

@skunkbad: Hear, hear!  😜

I think it would be ok for some third party to create a twitter library for CI, but I too would feel a sense of disappointment if it were included in the official releases.

@eoinmcg thanks,
but do you think guys that we need a repository like the jquery plugins repository,
@jdfwarrior yeah i can see that codeigniter with twitter library is disrespectable for the official release, but another release of codeigniter with more libraries is a good idea,
we can say that the normal is the minimum and with extra libraries is the full release

Personally, I like the way codeigniter is bloat free. The core libraries are great and well documented and I can easily drop in other libraries on a per project basis,either from the wiki or the multitude of PHP classes out on the interweb.

I guess the whole CodeIgniter philosophy is to keep it light and tight! As the homepage says

CodeIgniter is right for you if…

  * You want a framework with a small footprint.
  * You are not interested in large-scale monolithic libraries like PEAR.

Nothing to stop you starting a community driven repository of 3rd party libraries, though!

Nothing to stop you starting a community driven repository of 3rd party libraries, though!

@Blazy Boy Sounds like a new CodeIgniter project for you 😊

I agree with the 3rd party bloat is an issue. Only thing I would like to see in CL is standard database migration support.

I agree with the previous speakers (mostly).

Twitter is very hip right now, but might as well be forgotten tomorrow.
Codeigniters classes is great and works very well.

Maybe I miss support for modularity built-in sometimes.
But it’s not a big deal - just drop three files in the library-folder och voila! 😊

In CodeIgniter 2.0 they are going to enforce a requirement by default that all views contain less than 140 printable characters.

Now, we are talking!!! If CI is the first to fully realize the world revolves around Twitter than it will leave all other frameworks in the dust!!

@jdfwarrior hehe, i have to build a personal website first then think about another project
@Spicer well, twitter is really having a huge progress now, i think CI would be really good with 2 major parallel release(full, mini)
@Johan André what modularity library do you use? and do you have a link to explain the the pros and cons of modularity ?

In CodeIgniter 2.0 they are going to enforce a requirement by default that all views contain less than 140 printable characters.

Your killin’ me! I got a good laugh out of that comment.

@Johan André what modularity library do you use? and do you have a link to explain the the pros and cons of modularity ?

I don’t use it all the time, but when I do I use Modular Extensions.

Pros:
Each part of the application has it’s own structure (libs, helpers, configs etc).
Everything gets really tidy when you group certain functionality into a module.

Cons:
Hmm… maybe that to use models from a different module than the one you are executing you need to use $this->module_model->load(‘module’, ‘model’). This breaks the CI syntax and the controllers need som changes before used in a non-ME project.

The application I develop right now is VERY big (around 60 controllers so far, including the backend) and uses standard CI (no modules).