summaryrefslogtreecommitdiff
path: root/modules/gallery/helpers/module.php
AgeCommit message (Collapse)Author
2009-09-29Remove the @todo and optimize the gallery_event call for 3 and 4 ↵Tim Almdal
arguments... context menu events have 4 arguments.
2009-09-29* Remove the @todo in module event and always try to call ↵Tim Almdal
gallery_event::$function first * Refactor gallery.php to move site_menu, admin_menu, and context_menu to gallery_event.php * Change Theme_View and Admin_view to call module::event("site_menu|admin_menu|context_menu"...)
2009-09-05Change the module installer so that you don't need to provide your ownBharat 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-08-03Combine the quick menu and the thumb menu into a single menu calledBharat Mediratta
the "context" menu. This new context menu is generated using the typical event processing system, like our other menus. The specialized quick CSS and JS is now gone, replaced by our generic menu handling code. It's all rolled together currently using the thumb_menu UI for easy packaging. All the CSS and JS is updated. NOTE: the non-dialog links (rotate, album_cover) have a broken UI because they return JSON which the quick.js code handled specially, but we don't handle properly now. I need to fix this.
2009-06-30Fix i18n issue - accidentally called t() on translated messages. Please ↵Andy Staudacher
truncate incoming_translations after this update to get rid of bad messages in your DB.
2009-06-29Partial fix for ticket 471 - i18n of module names in upgrader.Andy Staudacher
2009-06-23Refactor 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-06-09Fix a bug in set_version() where we were always forcing the value to 1. Oops!Bharat Mediratta
2009-06-09Cache the available module list in module::$available.Bharat Mediratta
2009-06-09Use a reference in available() to avoid crappy looking dereferencing.Bharat Mediratta
2009-05-28Restore calls to module::load_modules() after ↵Bharat Mediratta
install/activate/deactivate/uninstall events.
2009-05-28Load the gallery module in load_modules(), but put it at the end ofBharat Mediratta
the module list (to match its location in the cascading filesystem)
2009-05-28Force modules/gallery to be at the end of the module load path, soBharat Mediratta
that all other modules can override the core code.
2009-05-27Fix up another place where we were incorrectly referencing the gallery module.Bharat Mediratta
2009-05-27Update all references to the core application to now point to theBharat Mediratta
gallery module. This type of mass update is prone to some small bugs.
2009-05-27Restructure things so that the application is now just another module.Bharat Mediratta
Kohana makes this type of transition fairly straightforward in that all controllers/helpers/etc are still located in the cascading filesystem without any extra effort, except that I've temporarily added a hack to force modules/gallery into the module path. Rename what's left of "core" to be "application" so that it conforms more closely to the Kohana standard (basically, just application/config/config.php which is the minimal thing that you need in the application directory) There's still considerable work left to be done here.