The main advantage of the definitive guide is that all information about
symfony are available in one place. The right side tag cloud also help a lot
to go to the correct part of the documentation.
I still look at it to get references about cache, slot and other stuffs.
Some information are only a
The book is now available in the SVN repository, ready for anyone to
contribute.
More information are available on the symfony docs mailing-list:
http://groups.google.com/group/symfony-docs/browse_thread/thread/66c6eb6c91ee6726
Fabien
--
Fabien Potencier
Sensio CEO - symfony lead developer
se
As it stands right now symfony has W more documentation than
any comparable framework out there. I think you are suffering from a
case of being spoilt too much by what symfony provides so that
anything "removed" is a big deal.
I started this discussion not as a complaint but as a query/sug
On 1/29/10 10:19 AM, Skyblaze wrote:
I don't want to spam or to offende anyone i just want to see the
reality. Ok it is an open source project and bla blablabut the
real fact is that this defenitive guide little update (with also two
important chapters left out from the update) and imho a no
On 1/29/10 10:19 AM, Skyblaze wrote:
I don't want to spam or to offende anyone i just want to see the
reality. Ok it is an open source project and bla blablabut the
real fact is that this defenitive guide little update (with also two
important chapters left out from the update) and imho a not
On 1/25/10 6:00 PM, Javier Garcia wrote:
Hi,
Thanks Fabien for your words.
I think every software should have its official manual updated even if
NOBODY is reading it.
lol
I think 1600 open tickets are too much tickets.
Many/most of these tickets are for plugins not maintained by the cor
Hi,
Thanks Fabien for your words.
I think every software should have its official manual updated even if
NOBODY is reading it.
I think 1600 open tickets are too much tickets.
I think maybe 1.3 and 1.4 could wait some?.
Javi
On 01/25/2010 04:52 PM, Fabien Potencier wrote:
On 1/25/10 4:45 PM
On 1/25/10 4:45 PM, Skyblaze wrote:
So i don't understand if you (Fabien) will release/publish the updated
defenitive guide this week even if chapters 8 and 10 are not yet
updated? Or You will publish it only when these two chapters are also
updated by the community?
I will commit the updated
About i have told a little bit earlier, i already have started to try
select some tickets that needs to be checked or are a little bit
simple.
Unfortunately, even i would want to help (which i did in the past), i
cannot due to a thight shedule and a second job.
I will try however to select some ti
On 1/25/10 4:18 PM, Alexandru-Emil Lupu wrote:
If Fabien wants and allows me, i could try to restart the
"1Day1Ticket" project, but for that i would need some users that are
willing to help.
I think that there is no need for a 1Day1Ticket initiative to start
helping. Asking people to fix 1 ti
Hi all,
I am totally agree with Fabien, but i would like to add some
completion on what Fabien said.
Is true.. i still feel that something has not been said. Even that is
a lot of documentation available, and there is one nice tutorial
(Jobeet) which is available for sf 1.3 and 1.4, the people stil
Hi Fabien,
Thank you for the complete and descriptive response; we really do
appreciate it. Just to give my take on why the Definitive Guide is so
good. Its for one of the reasons that you mentioned, that its easier
to find a description of the various aspects as the Practical guide
looks at symfo
Hi all,
I'm listening... but I needed some time to think about the topic a bit
more before answering. Here are my thoughts.
But before I start "ranting" about the definitive guide, remember that
all the work done on symfony is benevolent. It's true for my work, but
also for the work of the m
Yes,
i agree completely.
Javi
On 01/25/2010 11:29 AM, Gareth McCumskey wrote:
I understand, as well, that this is an open source project and that
the community should pitch in to things like the documentation in
order to update it but you see I am caught in a bit of a catch 22
situation. Th
I understand, as well, that this is an open source project and that
the community should pitch in to things like the documentation in
order to update it but you see I am caught in a bit of a catch 22
situation. The book needs to be updated with all the latest changes,
yet I need the book to know w
15 matches
Mail list logo
