lucion
September 16th, 2005, 08:35
Why have 6 different installation pages when, from the user/site admin's point of view, all Mambo files are the same; a ZIP file that you upload to Mambo?
For this thread, I'm going to coin
Mambo files: ZIP files, that can be uploaded to Mambo to install modules, components, mambots, site templates, admin templates, or language packs.
Mambo addons: The modules, components, mambots, site templates, admin templates, or language packs.
All Mambo files contain an XML file that defines if the ZIP file is in fact a Mambo file or not, and what type of Mambo file it is - ie. a module, component, mambot, template, or language pack.
When I download Mambo files, I download anything I want to try out to see if it's useful for me or not. I don't pay attention to whether it's a bot, com, or a mod. In fact I don't know what the diference is between them, and I don't particularly care either.
When it comes to installing the oh-so-precious and useful Mambo addons, I have to go round each installation page trying to find which one will allow me to install it!!
Solution
This could easily be solved by using one - yes, just ONE - installation page. The only hardcode change, would be that the Mambo addon installation bot, com, or mod (or whatever it is), would check the XML file to see what type of Mambo addon the Mambo file is. This of course would happen after the file is uploaded, and the XML file confirmed that the upload is a Mambo file, but before the Mambo addon is sent to be decompressed, and the files are loaded into the db.
Afterthought
Infact, why not even rename the file extension on the Mambo Files to *.mam !? Then the stupid users wouldn't ever get Mambo files mixed up and confused - like I do!!
For this thread, I'm going to coin
Mambo files: ZIP files, that can be uploaded to Mambo to install modules, components, mambots, site templates, admin templates, or language packs.
Mambo addons: The modules, components, mambots, site templates, admin templates, or language packs.
All Mambo files contain an XML file that defines if the ZIP file is in fact a Mambo file or not, and what type of Mambo file it is - ie. a module, component, mambot, template, or language pack.
When I download Mambo files, I download anything I want to try out to see if it's useful for me or not. I don't pay attention to whether it's a bot, com, or a mod. In fact I don't know what the diference is between them, and I don't particularly care either.
When it comes to installing the oh-so-precious and useful Mambo addons, I have to go round each installation page trying to find which one will allow me to install it!!
Solution
This could easily be solved by using one - yes, just ONE - installation page. The only hardcode change, would be that the Mambo addon installation bot, com, or mod (or whatever it is), would check the XML file to see what type of Mambo addon the Mambo file is. This of course would happen after the file is uploaded, and the XML file confirmed that the upload is a Mambo file, but before the Mambo addon is sent to be decompressed, and the files are loaded into the db.
Afterthought
Infact, why not even rename the file extension on the Mambo Files to *.mam !? Then the stupid users wouldn't ever get Mambo files mixed up and confused - like I do!!