| Age | Commit message (Collapse) | Author |
|
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
|
|
|
|
Make the continue= param a GET only parameter so that it's not part of
the form.
|
|
* 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
|
|
|
|
generate the post data
|
|
|
|
|
|
|
|
|
|
|
|
or list items with gError. Don't highlight submit, reset inputs.
|
|
|
|
|
|
and sidebar.
|
|
.gInline for forms like login, search, tags. Updated comment, login, search, and tagging forms. All form styles live in screen.css now. Still a lot to do, but this is a good foundation.
|
|
html for the login form is retrieve via an ajax call when the user clicks on login. Can't login with a valid id yet, but you certainly get error messages when things are wrong :-)
|
|
|
|
|
|
|
|
|
|
login link in the header wil open up a login box like the mockup
|
|
|
|
|
|
logged in) and changed the header to use the helper class
|
|
index.php/index.php/ for some environments)
|
|
variable; change the header so it links to the user controllers; and add the user controllers which don't do anything.
|
|
|
|
|
|
|
|
|
|
|
|
do anything else. Just got tire of my changes being clobbered :-)
|
|
need to avoid using absolute and relative positioning for our primary layout containers (i.e. gHeader, gFooter, etc.).
|
|
view :)
|
|
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.
|
|
background. Don't precede decimal values with 0 (.8em instead of 0.8em). Convert colors to short form, use lower case hex alpha values (easier to read), convert keyword colors to hex values. Quoted url paths. Fixed the order of border attributes (width style color). Don't clear floated elements around #gContent.
|
|
|