| Age | Commit message (Collapse) | Author |
|---|
|
so that the test passes.
|
|
the controller initiates a request to a top level page (eg:
album.html.php) which is then free to include whatever other page
chunks it wants with calls like <?= $theme->display('header.html') ?>
Variables like $item and $children are in the global space for all
views.
theme.php helper is now Theme.php library which lets us store the name
of the theme inside the variable itself. This means that the theme
does not have to know its own name because you can use $theme->url()
for all urls to stuff inside the theme itself, which makes it possible
to cline a theme without changing a single line.
Still using the mock album UI.
|
|
stack. The test passed, but the actual code failed. Fixed now.
|
|
returns a url local to the theme that you're in. For example, if
you're in themes/foo/views/page_header.html.php and you call
theme::url("images/foo.png") then it'll create a url to:
themes/foo/images/foo.png
|
|
|
|
* core_installer::install now creates the root album and the albums/thumbnails
directories under VARPATH.
* Add a test for core_installer
|
|
different from ORM_MPTT which we used in gx
|
|
* 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
|
