Donate
Muzikman wrote on Monday 16th of July 2012:Just an idea. I've been reading over the documentation for Fuel very thoroughly. I've caught many grammatical errors. Would you like me to grab this branch from GIT and make some changes?
Not necessarily instantiate, a DiC is basically a container for name -> object mappings, so instead of calling a class directly, you access it through the DiC. This allows you to swap classes in the DiC without touching your code, which is especially very handy when you want to test classes in isolation, you can replace dependencies by stub classes with a known behaviour.Muzikman wrote on Monday 16th of July 2012:I've read about DI but not in great depth. Is it a technique to instantiate all of the object dependencies needed for a particular situation?
Harro Verton wrote on Monday 16th of July 2012:Not necessarily instantiate, a DiC is basically a container for name -> object mappings, so instead of calling a class directly, you access it through the DiC. This allows you to swap classes in the DiC without touching your code, which is especially very handy when you want to test classes in isolation, you can replace dependencies by stub classes with a known behaviour.Muzikman wrote on Monday 16th of July 2012:I've read about DI but not in great depth. Is it a technique to instantiate all of the object dependencies needed for a particular situation?
Harro Verton wrote on Monday 16th of July 2012:Muzikman wrote on Monday 16th of July 2012:Just an idea. I've been reading over the documentation for Fuel very thoroughly. I've caught many grammatical errors. Would you like me to grab this branch from GIT and make some changes?
Most of us are non-native speakers, so it's inevitable. We'd hoped for more community contributions, but these haven't materialized sofar. So if you're willing to do this, yes, please. It's simplest to fork the repo on github, change whatever needed (make sure you're on 1.3/develop), commit, and and send a pull request.
Harro Verton wrote on Tuesday 17th of July 2012:Difficult question. I'd say (but that is personal opinion) that FuelPHP is not targeting the absolute beginner, but developers with some knowledge of PHP and OOP concepts and design patterns should be able to use it without problems. And any suggestion that will improve the documentation is welcome. Modifications are a bit cumbersome at the moment, as that would involve forking the repo, making changes in HTML files, and sending pull requests. We're working very hard at a new website (called the Fuel Depot project) that will include the documentation, which can be edited online using markdown. We hope to finish at least the docs part soon, after which I'm going to port the current 1.3/develop docs from HTML to markdown. Once that is done, it will be a lot easier for the community to improve the documentation. The new site will also have sections for snippets (that can be tagged so they can be referenced from the docs as examples), tutorials and screencasts. Especially the area for more elaborate examples needs work, as the current docs focus more on API documentation, which makes it sometimes difficult to see the use case. We are still looking for a "Docs Master", someone that will keep tabs on the quality of the docs, make sure missing pieces are documented, someone that hits the developers with a stick if they commit new code without proper documentation.
It looks like you're new here. If you want to get involved, click one of these buttons!
