On Friday, 28 December 2012 06:34:27 UTC+1, Techinfocomp wrote:
>
> Hello,
>
> I Feel that Cake 1.3 documentation is much understandable and easier then
> Cake 2.0 documentation, I don't know why CakePHP Did that ?
>
> Eg:
>
> AuthComponent in 2.0
> ---
m the api then the book.
On Dec 28, 2012 8:00 AM, "Techinfocomp" wrote:
> Hello,
>
> I Feel that Cake 1.3 documentation is much understandable and easier then
> Cake 2.0 documentation, I don't know why CakePHP Did that ?
>
> Eg:
>
> AuthComponent in 2.0
Hello,
I Feel that Cake 1.3 documentation is much understandable and easier then
Cake 2.0 documentation, I don't know why CakePHP Did that ?
Eg:
AuthComponent in 2.0
-
http://book.cakephp.org/2.0/en/core-libraries/components/authentication.html
Am I right to assume that was there all along Mark? If so, sorry :)
I am yet to make the switch to Cake 2.0 so not spent much time in the 2.0
book. I only got involved in this thread as seeing various threads
discussing the new documentation where the answer has been for them to
contribute so
Tada!
http://book.cakephp.org/2.0/en/contributing/documentation.html
-Mark
On Dec 8, 4:14 pm, aries wrote:
> Got it. What I'm hungering for is an easier way to submit changes and/
> or supplementation. A sticky guide as you suggest would help.
>
> I hasten to add that I think the documentation
Got it. What I'm hungering for is an easier way to submit changes and/
or supplementation. A sticky guide as you suggest would help.
I hasten to add that I think the documentation is very well written. I
usually find what I'm looking for, even if it takes some time to find
it.
Best,
-Brian
On De
The argument is simple, it is wrong to add a comment if it is
to supplement missing or correct existing documentation. You should edit
the documentation then the problem is resolved for all others who read it
thereafter.
I think this is a brilliant advancement for the new book, but maybe we
c
Oh, and after having it locally, make changes to it and push to your fork
in github. The rest is just doing a pull request to us. Please let me know
if you need help with anything.
--
Our newest site for the community: CakePHP Video Tutorials
http://tv.cakephp.org
Check out the new CakePHP Qu
Got to repository in github, browse the file you need to change, click edit
and that's it.
If you need to do changes to the layout, I would suggest to download the
source, and follow the instructions to get it running.
--
Our newest site for the community: CakePHP Video Tutorials
http://tv.ca
AD,
Thanks for the link to the source. I get what you're saying about
comments vs document edits, and though I might disagree (haven't read
through all the arguments), I have no desire to fire up an old debate,
especially if the matter is for all intents and purposes closed. What
is the best metho
it would also be nice if one could jump from 1.3 => 2.0 for the same
thing
often times the google results are still on 1.3
but then I have to "research" in the ajax box what I have been looking
for before because there
is no direct link
On 7 Dez., 18:19, mark_story wrote:
> I've toyed with addin
I've toyed with adding an on-page TOC for the sub-sections not in the
master TOC, but haven't had the time to add it in. It shouldn't be
hard to do on longer pages with lots of subsections. Its probably
mostly a matter of updating the CSS and adding the toctree directives
where necessary.
-Mark
On Dec 6, 11:34 pm, aries wrote:
> Hi,
>
> I'm not sure if this is the right place to post my comments, but I'm
> unable to find a more appropriate venue. Feel free to redirect me.
>
> Unlike previous versions, the 2.0 documentation lacks heading links
> within the TOC. It used to be that when v
Hi,
I'm not sure if this is the right place to post my comments, but I'm
unable to find a more appropriate venue. Feel free to redirect me.
Unlike previous versions, the 2.0 documentation lacks heading links
within the TOC. It used to be that when viewing a particular topic you
could access subto
14 matches
Mail list logo
