| Age | Commit message (Collapse) | Author |
|---|
|
|
|
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.
|
|
$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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
implementation yet
|
|
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
|
|
|
|
* Remove user registration link and popup from the theme; this
shouldn't be done in a popup. Use ajaxform to simplify the way
that we load the login popup.
* Create form.html.php, this is a template for Forge based forms.
* Move user validation rules into User_Model and let forms
populate the rules into their forms as useful.
* Undo r18688's changes regarding the REST code. We should never
accept a null resource, this breaks the REST abstraction.
* Change login and user controllers to use Forge which lets us delete
login.html.php and user.html.php since those now are generated by
the theme-owned form template
|
|
|
|
login link in the header wil open up a login box like the mockup
|
|
Removed .first class, it's not needed, at least not now. Moved all top-level layout containers to page.html.php so that if themers want to replace YUI grids with something else, like Blueprint, they only really need to edit page.html.php.
|
|
|
|
|
|
|
|
these rather than CDN versions, for now. Renamed default theme's style sheet to screen.css, recommend that CSS files be named for the primary media they support. Removed unused YUI JS component calls from the default theme.
|
|
|
|
Now we have an overall page layout (page.html.php) which has a $content
variable, and that $content will be one of several possible secondary
views. Currently, it is either photo.html.php or album.html.php.
header, footer, breadcrumb, sidebar, anything common to all pages is
in page.html.php.
|
|
so that the test passes.
|
|
|
|
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.
|
