Age | Commit message (Collapse) | Author |
|
|
|
Implement a real breadcrumb.
|
|
Currently only the album view works, albums have no thumbnails, and
there's only 1 image in use.
Improved Item_Model to have the following API methods
file_path() -- returns the path to the source image or album dir
thumbnail_path(), thumbnail_url() -- returns path/url to the thumbnail
resize_path(), resize_url() -- returns path/url to the resize
All tests updated.
|
|
|
|
|
|
|
|
|
|
screen and you can install and uninstall it. Which creates the tables, defines 2 groups (adminstrator, registered) and one user (admin).
|
|
|
|
sidebar.html.php file loops over $theme->blocks() which in turn calls
carousel::block() which uses the Block object to create a standard
block UI. Hooray!
|
|
uninstalled modules.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Simplify the installer-detection code.
|
|
|
|
|
|
whether they need to be installed or uninstalled.
|
|
Replace theme HTML with *almost* the latest stuff from the
mockups. (it doesn't include r18467 yet).
Our theme format is now modelled after WordPress / Habari's style
where you have one entry point per type (eg: album.php) which can
load up whatever parts it needs (eg: $theme->display("header"))
Created album and photo helpers which have create() functions
that form the base of our new API, along with tests for them.
Created our own version of the ORM_MPTT since the existing
versions were too buggy and unsupported to depend upon. Only has
a minimal implementation so far, and the tests are not yet
committed.
Added path(), thumbnail_path() and resize_path() to Item_Model
Extended the scaffolding to allow you to add lots of
photos/albums into your hierarchy.
Deleted modules/mptt -- we're not going to use this anymore.
|
|
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.
|
|
route
and add a link to it from the welcome page.
|
|
all (except in some very minor ways). It's unclear if this is the
best final structure. Right now the album controller knows a
considerable amount about the layout of the page, which may not be the
best way to do things.
|
|
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
|
|
|
|
|
|
|
|
|
|
and create methods to install/uninstall modules.
|
|
different from ORM_MPTT which we used in gx
|
|
mess up the real database.
|
|
* 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
|
|
|
|
occasionally
end in tags like <?= this ?>
|
|
|
|
it walks you through creating the database also.
|
|
|
|
directory set up correctly and a database config file in place.
|
|
disable logging if the log dir is not writable.
|