| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Theme.php.
|
|
so that we don't ship XML down to Chrome.
|
|
|
|
core_block:head method to insert the title into the head section. If the config value is false, the default Browse Photos::$item->title is used. A string value with a trailing '-' will append the config value to $item-title. Otherwise, the page title is set with the supplied value.
|
|
lower case:
http://docs.kohanaphp.com/general/helpers
Remove block_helper file as the abstract class os no longer required.
|
|
excercises it.
|
|
|
|
|
|
and also allow modules to contribute blocks to the layout.
|
|
|
|
|
|
* HTTP header setting in comment module now going through REST helper API.
* Fixed items controller test.
* Fixed user installer test.
* Fixed _create() handling in the REST controller.
* Fixed routing for edit and add forms.
* Added some tests for the REST controller.
* Set svn:eol-style to LF on a bunch of files.
* Added preamble to MY_Forge.php.
|
|
|
|
full URLs with a clean API, and isolate the cruddy party where we have
to hardcode the server protocol into a single file.
|
|
|
|
1) We now use __call() in REST_Controller to handle any requests to a controller
that were not already handled. In the case of RESTful controllers, this should
be the only entry point (although they're free to break the model and add other
ones.. nothing stops them).
This means that we can remove all the catch-all routes in
routes.php which greatly simplifies it.
2) Move request_method() and output_format() out of REST_Controller and into the REST
helper in core/helpers/rest.php
3) Experiment with letting the various subclasses check the output_format and deal with
it themselves. This simplifies the API, but it might be a bad idea in that it might
push too much work to the individual controllers. It's a balancing act, time will tell,
I'm willing to change it back later.
|
|
|
|
|
|
try to display a comment if it is not installed
|
|
XML to the comment controllers as a proof of concept. It's not fully
baked; we should examine ways to create helpers to make this process
easier.
|
|
|
|
and deletes modules into it.
|
|
Adjust/simplify photo::create
Add image uploading to the scaffolding
|
|
|
|
relationship to bind the two. To do this, I overrode __get in
Item_Model so that $item->owner returns the appropriate User_Model.
|
|
|
|
|
|
sometimes i would get the message "There was an SQL error: Table 'gallery3_unittest.modules' doesn't exist - ...." and sometimes I would get the message "Table modules does not exist in your database." In both cases the error code was 44.
|
|
Fix a bug in the scaffolding where we weren't saving the album after
adding its thumbnail (so its dimensions weren't getting set).
|
|
properly in the theme.
* Move thumbnail and resize generation down into the model for
consistency.
* Add a sample thumbnail for albums
* Fix a bug in the ORM to clear the cache when we reload an object.
* Add Kohana docs to the scaffold.
|
|
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.
|
|
|
|
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.
|
|
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
|
