Re: [PHP-DOC] oop5 status

2004-07-18 Thread Curt Zirzow
* Thus wrote Gabor Hojtsy:
> >
> >  Right now we have the title's of stuff that vary a lot. Some are 
> >  prefixed with 'Object' other's have the word 'Keyword' appended.
> >  I'm thinking we should get rid of those pre and post words and
> >  just do stuff like:
> >Constants
> >Abstraction
> >...
> >
> >  The only two I don't see that fit that naming scheme are final 
> >  and static, they don't make sense to me without some sort of text
> >  around them.
> 
> It is nice to have helper words when the meaning of something is not 
> clear. Like you would not remove 'methods' from after 'magic' :) or you 
> would not remove 'objects' after 'comparing', since the 'comparing' word 
> alone would not provide much clue on what is going on.

I might have been a little unclear on this. right now the current
items are:

  Static
  Object Constants
  Object Abstraction
  Object Interfaces
  Overloading
  Object Iteration
  Magic Methods
  Final Keyword
  Object cloning
  Comparing objects
  Reflection

Would be better as:
  Static
  Constants
  Abstraction
  Interfaces
  Overloading
  Iteration
  Magic Methods
  Final Keyword
  Cloning
  Comparing objects
  Reflection

I might just being too picky here, I'm perfectly  fine with the
current names we have.

> 
> >What to do with the built in classes and implementations:
> >
> >  Like implementing Iterator (and all that SPL stuff if applicable)
> >  extending the Exception class etc.
> 
> I don't understand the question. Built in classes should be at the 
> relevant appendix. Iterators and Exceptions should have their own parts 
> otherwise: iterators under the OOP 5 part where they are currently, 
> exceptions on the language reference level as a new section.

Sorry, i was kind of thinking outloud here. I'm not entirely sure
what I was asking either, but your explantation clears things up.


Thanks.

Curt
-- 
First, let me assure you that this is not one of those shady pyramid schemes
you've been hearing about.  No, sir.  Our model is the trapezoid!


Re: [PHP-DOC] oop5 status

2004-07-17 Thread Gabor Hojtsy
We need a nice intro. I've been avoiding it cause I'm not really sure what
should go there, any thoughts on what should be said there? Any thing will be
better than my 'Intro to oop 5' :)  Perhaps one of the things on the first
page is the basic concept on how to create a class and extending a class.
Current sections that need content, limited to sections defined:
  - Object Constants
  - Object Interfaces 
  - Overloading
  - Object Iteration
  - Magic Methods
  - Final keyword

The only section that isn't listed in the current structure is Exceptions.
If, however, the oop5 documentation is going to be more on the idea that
they have no clue about php4 oop then we need:
  - class  creation
  - extending classes
One way to aproach this is to have a 'Intro to OOP with PHP', which will
define the basics that are common between the both 4 and 5. Like class 
creation and extending a class. On second thought this might not be a good
idea since member and method declartion are completely different.  
We need separate PHP 4 and PHP 5 intro sections, since they will be very 
much different. We do have this for PHP 4 IMHO, it just needs to be 
taken as an example for PHP 5. Well, the cart example might be changed 
for something more exciting :))

Consistancy issues:
  Right now we have the title's of stuff that vary a lot. Some are 
  prefixed with 'Object' other's have the word 'Keyword' appended.
  I'm thinking we should get rid of those pre and post words and
  just do stuff like:
Constants
Abstraction
...

  The only two I don't see that fit that naming scheme are final 
  and static, they don't make sense to me without some sort of text
  around them.
It is nice to have helper words when the meaning of something is not 
clear. Like you would not remove 'methods' from after 'magic' :) or you 
would not remove 'objects' after 'comparing', since the 'comparing' word 
alone would not provide much clue on what is going on.

What to do with the built in classes and implementations:
  Like implementing Iterator (and all that SPL stuff if applicable)
  extending the Exception class etc.
I don't understand the question. Built in classes should be at the 
relevant appendix. Iterators and Exceptions should have their own parts 
otherwise: iterators under the OOP 5 part where they are currently, 
exceptions on the language reference level as a new section.

The Title's for PHP4 vs PHP5:
  Although very low priority right now, on my browser the left navigation
  line breaks in between the words and looks horrible. This might be more
  of an issue of how the left nav vertical alignment is displayed.
Low priority, yes...
Goba


[PHP-DOC] oop5 status

2004-07-16 Thread Curt Zirzow

We need a nice intro. I've been avoiding it cause I'm not really sure what
should go there, any thoughts on what should be said there? Any thing will be
better than my 'Intro to oop 5' :)  Perhaps one of the things on the first
page is the basic concept on how to create a class and extending a class.


Current sections that need content, limited to sections defined:

  - Object Constants
  - Object Interfaces 
  - Overloading
  - Object Iteration
  - Magic Methods
  - Final keyword


The only section that isn't listed in the current structure is Exceptions.
If, however, the oop5 documentation is going to be more on the idea that
they have no clue about php4 oop then we need:
  - class  creation
  - extending classes

One way to aproach this is to have a 'Intro to OOP with PHP', which will
define the basics that are common between the both 4 and 5. Like class 
creation and extending a class. On second thought this might not be a good
idea since member and method declartion are completely different.  


Consistancy issues:

  Right now we have the title's of stuff that vary a lot. Some are 
  prefixed with 'Object' other's have the word 'Keyword' appended.
  I'm thinking we should get rid of those pre and post words and
  just do stuff like:
Constants
Abstraction
...

  The only two I don't see that fit that naming scheme are final 
  and static, they don't make sense to me without some sort of text
  around them.


What to do with the built in classes and implementations:

  Like implementing Iterator (and all that SPL stuff if applicable)
  extending the Exception class etc.

  
The Title's for PHP4 vs PHP5:
  Although very low priority right now, on my browser the left navigation
  line breaks in between the words and looks horrible. This might be more
  of an issue of how the left nav vertical alignment is displayed.


Well this was a little more complicated than I expected :) I hope I was 
clear enough.


Curt
-- 
First, let me assure you that this is not one of those shady pyramid schemes
you've been hearing about.  No, sir.  Our model is the trapezoid!