Yes! This discussion thread is about Documentation.
The Current Documentation is "good". On a scale of 1 to 10, it is a 5.
I say this for a number of reasons.
1. It contains deprecated items that are not noted as such.
2. Alternative / Preferred methods to deprecated items are not
provided.
3. It provides items without specific examples which can be used and
tested by users.
4. It does not provide specific methods to solve specific fundamental
web application problems.
My goal of this thread was to present a problem an a web application
builder(user) brings to the Documentation.
The application builder brings a general question to the
Documentation.
For Example:1) How do I add a select option driven by a database
table to my View(form)?
2) How do I eliminate a label on a form eliment?
3) How do I change the label on a select
option?
Are the direct and explicit answers to these types of questions beyond
the scope of this Documentation?
The application builder has followed the cakePHP instructions to build
their application in accordance with cakePHP methodology and
practice.
The Methods, Controllers and Views were built with cake.php Bake and
tested with scaffold.
This was accomplished in short order!
Thanks cakePHP!
Some of the boring repetitive work is out of the way.
Now the CUSTOMIZATION work begins.
How do I add a select option driven by a database table to my
View(form)?
The developer finds a solution in the Documentation use
generateList().
The developer applies generateList() to the application.
Many trials and failures follow.
Finally, the developer finds that generateList() is deprecated.
The notes in the Documentation regarding the deprecation of the
generateList() are missing?
Time Wasted!
There are no notes on an alternative method!
More frustration.
More time.
More research.
CakePHP gurus provide the following:
1) Use "find" and "Set::combine". Those components are in the
documentation.
or
2) Download X,Y or Z web application and decontruct.
Deconstruction!
Yes!
More research.
More time.
CakePHP users will try components 2,3, 4 or more times before an error
isn't kicked out because there is a lack of specific examples.
Did the guru say "find", "find(''list"), find("all"), "findAll()",
"generateList(), etc. etc. etc. which one? They are all in the
Documentation.
How many times does a user have to test "find", "find(''list"),
find("all"), "findAll()", "generateList(), etc. etc. etc. before they
find that the solution to this fundamental form requirement, "a select
option" based upon a database doesn't produce the desired results.
Why?
That component requires the use of another component.
Remember? Set::combine?
More time.
More research.
More testing.
Do you remember the web developers original question which brought
them to the Documentation?
How is a select option based upon a database table added to a
View(form)?
How much time does a user spend to find the component(s) needed to
answer this basic web application question?
How much time does a user spend to find out how, when and where to use
those components with what dependencies (Model, Controller and View)
are required?
More research!
More testing!
Is providing, in the documentation, the answer to this type of
question beyond the scope of the Documentation?
I don't think that it is.
Therefore, I rate the Documentation a 5.
The Documentation at this time is more of a compendium, repository,
alphabetical list of all of the neat things (components) that CakePHP
developers have built.
Cool.
Some of the components in the Documentation are deprecated. Some are
not. Some deprecated items are noted as such and provide alternatives.
Some aren't and don't. Some components have examples on how to they
are to be used. Some don't.
What ever time a user saves by using cakePHP framework will be spent
and then some on research and testing?
That is until the developer has built their own repository of
solutions to common requirements such as how to add a selection option
to a View(form).
Why?
While the components to a solution are in the documentation, the
solution is not and watch out for deprecation!
The need is clear.
Wayne
On Jun 24, 11:15 am, Wayne Madison <[EMAIL PROTECTED]>
wrote:
> Hello,
>
> I want to create cakePHP(1.2.0.xxxx) Forms to "View", "Add", "Edit",
> "Delete" a "User".
>
> Constraints: 1 (No "Scaffold")
> 2 (No Deprecated "generateList()")
>
> I want the "Add" and "Edit" form to contain:
>
> 1) A select option box for "title" based upon the values in the
> "titles" table showing field values for "Title" saving "title_id" to
> the "users" table.
> 2) An input box for first_name
> 3) An input box for last_name
>
> I want the "User" "View" form to show:
>
> 1) The "title" selected not the "title_id"
> 2) The "first_name" value
> 3) The "last_name" value
>
> Table One: "Users"
>
> user_id integer primary key auto number
> title_id integer,
> first_name varchar(40)
> last_name varchar(40)
>
> Table One: Data Example:
> user_id titile_id first_name last_name
> 1 1 bill smith
> 2 2 jane murphy
> 3 3 elizabeth baker
>
> Table Two: "Titles"
> title_id: integer primary key autonumber
> title: varchar(40)
>
> Table Two: Data Example:
> title_id title
> 1 Mr.
> 2 Ms.
> 3 Mrs.
>
> Thanks
>
> Wayne
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
