| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
|
|
Track a set of rules in Graphics_Rule_Model which specify how we turn
original images into thumbnails and resizes. There's one set of rules
that applies to every image in the Gallery.
Track the state of thumbs and resizes with a "dirty" bit. The new
graphics helper manages the rules and can rebuild the thumbs and
resizes for any images that are considered "dirty".
Introduce the concept of an "album cover" which is an item that an
album points to. We'll use that item as the source for the album's
thumbnail/resize.
Conflated with this change (sorry!) I also changed the Var table to
use module_name instead of module_id. This may be marginally less
efficient, but it's much easier to follow in the database.
|
|
|
|
store information, but is not enough to warrant a table of its own
|
|
* item model (contains basic item info, similar to the gx version)
* module model (has info about each module and which version of it is installed)
* added a very basic unit test to verify that we can create an instance of item
* Updated our test controller to require a unit_test db config and
call core::install if it hasn't been done already.
New pattern:
* core/helpers/core_installer.php creates core_installer helper.
When we install a new module you call xxx_installer::install(),
and when you want it to go away, you do xxx_installer::uninstall()
Create
|
