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

2009-08-27	Remove 'ENGINE=InnoDB' specification from tables that we create. Use	Bharat Mediratta
	the system's default table specification. Fixes ticket #597.
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	clean up whitespace errors introduced in last commit	Bharat Mediratta

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-20	Avoid complex inserts in available_tasks() to make admin/maintenance	Bharat Mediratta
	run faster. This fixes ticket #235. Incidentally, refactor exif and search to use the same patterns overall so that if you understand one, you understand the other and they generally use the same strings for localization.
2009-05-13	Gee it's May already. Update copyright to 2009.	Bharat Mediratta

2009-05-11	Refactor the exif module to denormalize the stored data. This way we	Bharat Mediratta
	have a single exif_record for each item instead of 1 per key. It's about 5x faster to scan photos this way.
2009-05-05	Detect input encodings from EXIF/IPTC data and convert to utf-8 as	Bharat Mediratta
	appropriate. This allows us to switch the exif value column back to varchar and improves the way that we deal with non-utf8 data in our embedded EXIF/IPTC data.
2009-04-27	Update value size to 1536 chars because I had an image which went over 1024 ↵	Bharat Mediratta
	chars
2009-04-25	Drop the item_id key; we don't need this level of strictness in most	Bharat Mediratta
	cases and it slows down inserts.
2009-04-25	Change the value column to varbinary so that we can handle the occasional ↵	Bharat Mediratta
	binary data embedded in places like the EXIF caption field
2009-04-25	Add a key on item_id so that our query to find missing exif records is efficient	Bharat Mediratta

2009-04-05	Optimization: add all exif/iptc keys in a single insert, instead of	Bharat Mediratta
	many separate queries. In the process, rip out the summary column, we weren't using it. Clean up the test, and drop the exif_records database on uninstall.
2009-03-13	Make the exif_key value size 1k	Bharat Mediratta

2009-02-28	Change the pattern to identify tables that need prefix substitution to	Tim Almdal
	mirror the drupal pattern of using braces {}.
2009-02-27	This implements table prefix for all the queries in core, user, exif,	Tim Almdal
	tag, search, comment and notification modules (Ticket #68)
2009-02-15	Tweak EXIF extraction code to be more robust.	Bharat Mediratta
	* Create Exif_Record_Model to track whether we've scanned the EXIF data for this photo or not. This allows us to track photos that don't have EXIF data (and won't have any Exif_Keys) * Blow away old Exif_Keys when extracting, else we hit unique index constraints. * exif::_get_stats() -- before it was running the task forever
2009-02-10	Exif data is now collected when an image is added.	Tim Almdal

2009-02-07	The start of the exif module. so I can merger the exifer library	Tim Almdal