5
One thing about the Alpha 1 release.
The extensions should reside in their own directory and not the module directory. It can be a little confusing especially to new users if an item is a module or extension. This should be a simple thing to fix.
Also since Extensions are really parts of the core that were moved to external code and some modules rely on this code we should establish a "standard" api definition for the base extensions. So if a "replacement" extension is written it will produce the same results to anything that uses it as the original extension. Doesn't mean the extensions can't do MORE but the bare minimum should be set as a standard and approved by someone. For now the core developers but down the road someone who is a module support person.
As an example, the ratings system... I may at some point be writing my own system that will extend the current rating system but I will need to support the main code that the ratings extension does now. The great thing about it being in an extension is now I can create an extension replacement and it is NOT a core hack so it should work across releases of the core. Similar to providing a module...
I haven't looked at the code related to extensions yet. Is support for specific extensions hard coded in or are they flexible like a normal module?
Attending College working towards Bachelors in Software Engineering and Network Security.
