gallery3.git - A clone of the Gallery3 code for testing and development.

Age	Commit message (Collapse)	Author
2013-01-31	Drop the requirement to have the install() function set the module	Bharat Mediratta
	version. It's redundant. Fixes #1985.
2013-01-21	Update copyright to 2013. Fixes #1953.	Bharat Mediratta

2012-02-27	Update copyright to 2012. #1822	Bharat Mediratta

2011-01-21	Update copyright to 2011.	Bharat Mediratta

2010-03-03	Update the copyright to 2010. It's only 3 months into the year :-)	Bharat Mediratta

2010-01-22	Change the check_environment method in the module helper and the module ↵	Tim Almdal
	installers to can_activate to reflect that it is doing more than just checking the environment.
2010-01-21	Convert the slideshow module to use the new check environment and ↵	Tim Almdal
	pre_deactivate api methods.
2009-12-27	Allow users to upscale images in the slideshow by making the maxScale	Bharat Mediratta
	parameter configurable in Admin > Settings > Advanced. You specify the scaling factor. Normally, images fill the stage; 0 -> never scale up; any other positive number S --> scale up to S times the original size of the photo (but never bigger than the stage)
2009-09-05	Change the module installer so that you don't need to provide your own	Bharat Mediratta
	install() function if all you're going to do is to set the version of the module from module.info into the database. This means that for some simple modules, you don't need an install.php file at all.
2009-06-23	Refactor the install/upgrade code to be more flexible.	Bharat Mediratta
	Add xxx_installer::upgrade($version) method so that upgrade stanzas are separate from install stanzas. In the old code, to do an upgrade meant that you had to re-evolve everything from the initial install because we'd step through each version's changes. But what we really want is for the initial install to start off in the perfect initial state, and the upgrades to do the work behind the scenes. So now the install() function gets things set up properly the first time, and the upgrade() function does any work to catch you up to the latest code. See gallery_installer.php for a good example.
2009-05-26	Restructure the module lifecycle.	Bharat Mediratta
	Install: <module>_installer::install() is called, any necessary tables are created. Activate: <module>_installer::activate() is called. Module controllers are routable, helpers are accessible, etc. The module is in use. Deactivate: <module>_installer::deactivate() is called. Module code is not accessible or routable. Module is not in use, but its tables are still around. Uninstall: <module>_installer::uninstall() is called. Module is completely removed from the database. Admin > Modules will install and activate modules, but will only deactivate (will NOT uninstall modules).
2009-05-13	Gee it's May already. Update copyright to 2009.	Bharat Mediratta

2009-05-12	Use the module_change event to figure out if the rss module is	Bharat Mediratta
	inactive. If it is, we need to alert the admin user.
2009-01-14	Make sure that helper functions are all static. Add new	Bharat Mediratta
	File_Structure_Test to make sure we don't regress. According to the PHP docs, the "public" keyword is implied on static functions, so remove it. Also, require private static functions to start with an _. http://php.net/manual/en/language.oop5.visibility.php
2008-11-27	Centralize logging around installing/uninstalling modules.	Bharat Mediratta

2008-11-21	Revert module block approach	Tim Almdal

2008-11-20	A look at away to allow modules to define html head contents (links and js) ↵	Tim Almdal
	and also allow modules to contribute blocks to the layout.
2008-11-18	The start of the slideshow module. Mostly framework stuff, no real ↵	Tim Almdal
	implementation yet