whoever's willing to writing code in PHP, which I'd consider programming
, should get himself familiar with how an API reference is written and what the stuff means. The pages at api.joomla.org contain typical information and are just fancy looking compared to the plain-vanilla layout of most other references, incl. the PHP manual. It's neither top-notch nor does ist suck. It's just a reference like many others.
It isn't that
hard to learn reading it, and you can safe yourself a lot of time and headaches if you know "how to read a function definition
". That's basic knowledge in order to write any
That chapter from the PHP manual and the Joomla! Framework naming schema I mentioned in my previous post should help you and others to walk your way through the J! API Reference. For the remaining issues: post in the forums :-)
This topic started as the result of some people using code examples from a book that was published when J! 1.5.0 was not yet released.
The codebase of the Framework was complete, yet it wasn't stable
. Unfortunately the two classes in the "filter" package have been renamed twice after
that book was released. That's sad, but it happend. It's not like everyone now has to rewrite thousands of lines of code due to this; just flip two words. If you were a programmer -- which according to your last post I assume you're not -- you'd know that this kind of "refactoring" happens all the time. Now
both classes fit well into the system and you don't have to remember yet-another
exception in the file and class naming schema (which is not as strict as it could have been.)
I absolutely agree that many extensions written for 1.0.x (or Mambo) do not work seamlessly within 1.5.x, but the legacy layer does a pretty good job. Many "old" extensions suddenly stop working because their "programmers" did not use the interfaces 1.0.x had to offer, it's API, and wrote their own stuff -- bypassing the system. Given the code quality and code design
of some such extensions, their "creators" aren't developers either.
So who's to blame? Maybe its Mambo and J! 1.0 for not providing the tools that forced 3PDs to finally come up with their own "solutions"?
Sure, the 1.0-API wasn't very sophisticated and the reason for 1.5 to be written in the first place. Backwards compatibility is a curse.
In summary, Joomla! 1.0 provided less functionality
than 1.5. It's just the many, many Mambo and J! 1.0 compliant extensions that added to it. Get yourself well written
extensions, and you have the same "functionality" in 1.5.
People who "just use" the CMS application won't necessarly notice, but web designers an developers do, and they have much more and much better tools to use.
It's just 6 months since 1.5 was released. Allow 3PDs to catch up and get familiar with the new environment. It's an easy task to refactor an old extensions using the new Framework, but it takes time.
You can have programs written fast, well, and cheap, but you only get to pick 2 ...
"I love deadlines. I like the whooshing sound they make as they fly by." Douglas Adams