First we need someone who has time to review the markup and partices used to document OO stuff in the manual, and then come up with *one true way*, which will be acceptable for the future.
Does anyone have time for this? Unfortunately, I don't.
I think it's important that we get this hashed out sooner than later. The more OO documentation we add without a concrete *one true way*, the more re-doing we'll have to do (which is exponential in the translations).
And whats wrong in the current OO docs? We must know that first. I think the current docs perform just fine..
Currently documented OO extensions: MySQLi, SOAP, tidy, PDO OO needed to be documented: sqlite, ...?
Have you done a deep review of what tags and constructs these docs use? We cannot tell if there is anything wrong, or if those differ, if there is noone to review. DOM is another oo extension BTW, swf also has some oo stuff, if I remember corerctly.
Goba
