| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
scaffolding, then browse around your Gallery3 to see where you can add
visible elements via modules.
|
|
|
|
|
|
li to comment thread ul. Added fadeIn for user login.
|
|
|
|
|
|
here. In place commenting works again.
|
|
|
|
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.
|
|
the header_bottom() insertion point.
|
|
using absolute positioning (slideshow link). CSS comment org and comment updates.
|
|
the generic item info into the info module.
|
|
$theme->block_type() so that the themer has a consistent interface.
Also added a bunch more callbacks and normalized the names so that the
module author has plenty of options for where stuff gets put on the
page. Especially renamed album/photo/sidebar to be album_blocks()
photo_blocks() and sidebar_blocks() to make it clear that those are
going to be larger content sections and not just basic insertion
points.
Used __call() to collapse all functions in the theme, which
incidentally makes it trivially easy to add a new insertion point.
|
|
user login form. Added gHide, gShowBlock, gShowInline, gClose classes to handle show and hide functions. Half-baked idea which will need refinement.
|
|
fields as we currently do w/ the search form, a label should be included to maintain accessibility. Set label display to none if it shouldn't be displayed.
|
|
|
|
|
|
|
|
|
|
|
|
Removed unused CSS. CSS format updates. Applied jQuery tab styles to gSiteMenu. Removed gBlockHeader, all we need is a good old h3 element for a heading.
|
|
|
|
prototype. Dropped YUI Base CSS in favor of defining our own base styles in screen.css, headings will and other items may not look right until I do. Need to figure out how jQuery ThemeRoller CSS should be integrated, if at all.
|
|
and also allow modules to contribute blocks to the layout.
|
|
|
|
|
|
slideshow link and button text. The slideshow link will only show up if the slideshow module is installed.
|
|
|
|
|
|
|
|
in order to follow the convention that controllers that refer to a collection of resources have plural names.
* Added a bug workaround to routes.php
|
|
implementation yet
|
|
|
|
try to display a comment if it is not installed
|
|
refer to collections should now have plural names and there should be only one controller per resource. Updated existing classes that implement REST_Controller. The routing now works like this:
GET /controller -> controller::_index()
POST /controller -> controller::_create()
GET /controller/id -> controller::_show()
PUT /controller/id -> controller::_update()
DELETE /controller/id -> controller::_delete()
GET /form/edit/controller/resource_id -> controller::_form()
GET /form/add/controller/data -> controller::_form()
|
|
ajaxify_comment_form() as needed. Otherwise the 2nd post attempt won't be ajax
|
|
gTags to gTag in the CSS.
|
|
1) Changed the way that we get forms. Now, if you want to get a form
for a REST resource you prefix /form to the resource id. So:
/form/photo/1 : returns a form for editing photo id 1
/form/comments/1 : returns a form for adding a comment to photo id 1
/form/comment/1 : returns a form for editing comment id 1
2) Changed the comment module to have two controllers:
comment: deals with a single comment resource
comments: deal with collections of comments attached to an item
Related stuff:
- Moved the comments js into the theme
- Reworked Comment_Helper for clarity
- Moved form generation code down into Comment_Helper
- Cleaned up routes (eliminating new comment ones added in recent rev)
- Added form() function to all REST controllers
- Changed comment module to use a block instead of an arbitrary helper call from the theme
- Comment controller only returns HTML currently, but returns a 201 Created status
code when a new comment is added, which the Ajax code can catch and act upon.
- Got rid of a lot of extra views in comment module
|
|
This disambiguates forms from blocks (for example in the comment
module we were calling both the form and block gComments).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Hardcode the item has_one owner relationship again
* Overload User_Model::__get to handle missing owners gracefully
* Fix Item_Controller to take the owner_id from the session or
from the parent album when adding new albums and photos.
|
|
user; and the views don't break if user module is not installed
|
|
|
