| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
communicate. Almost all controllers now use JSON to speak to the
theme when we're dealing with form processing. This means tht we only
send the form back and forth, but we use a JSON protocol to tell the
browser success/error status as well as the location of any newly
created resources, or where the browser should redirect the user.
Lots of small changes:
1) Admin -> Edit Profile is gone. Instead I fixed the "Modify Profile" link
in the top right corner to be a modal dialog
2) We use json_encode everywhere. No more Atom/XML for now. We can bring those
back later, though. For now there's a lot of code duplication but that'll be
easy to clean up.
3) REST_Controller is no longer abstract. All methods its subclasses should create
throw exceptions, which means that subclasses don't have to implement stubs for
those methods.
4) New pattern: helper method get_add_form calls take an Item_Model,
not an id since we have to load the Item_Model in the controller
anyway to check permissions.
5) User/Groups REST resources are separate from User/Group in the site
admin. They do different things, we should avoid confusing overlap.
|
|
1) Deleted in-place-editing. We'll be replacing this with a real edit
system that groups settings together and is more coherent.
2) Tweaked the way that dialog boxes work to get the ajax stuff working
again. It's imperfect and does not work properly for uploading images.
This is going to get redone also, but this is a good resting point.
3) Created edit forms for albums and photos. Moved _update and _create out
of Items_Controller and into the individual subclasses.
4) Created access::required which is a shorthand for:
if (!access::can(...)) {
access::forbidden();
}
5) Added validation rules to Items_Model
6) Converted login to use the regular modal dialog approach in the theme.
|
|
1) If the create request is Ajax, then return a 201 Created response code
2) If we receive back a 201 response, then switch to the new page.
3) Display a status message when we do an upload.
|
|
|
|
|
|
module install/uninstall work and tie it into the messaging system.
|
|
consistency
with the callbacks in the xxx_block helpers. So in the theme we have:
admin.html.php:
$theme->admin_page_bottom()
then in the helpers:
core_block.php:
function admin_page_bottom() { }
|
|
|
|
the various modules. In the process, rename xxx_menu::site_navigation() to just
xxx_menu::site(). And add xxx_menu::admin().
The menus are the same as before, but I changed the HTML to be
consistent with the way that we do it in the regular site, and this
broke the superfish styles. I don't know how to fix this.. help me
Chad!
|
|
context of dialog display (don't show legends, fieldset border, or submit button).
Let's make sure that all forms generated are complete and well formed and then use JS and CSS to control their display and behavior in different contexts.
|
|
Applied to modal dialogs.
|
|
Item_Model and simplifies
file_proxy. It also means we can stop munging file names in the var/resizes hierarchy.
In the process, rename "thumbnail" to "thumb" everywhere in honor of
Chad (well, ok because it's shorter)..
|
|
labels' value. Labels should always be used with visible inputs. Use this to style and control short form input display and behavior.
|
|
|
|
|
|
submission so the form doesn't close. There might be a better way, but i couldn't think of it.
|
|
|
|
|
|
|
|
and earlier. Fixed bg images in album/item view buttons, IE 6/7 don't appear to handle background-position: center center :(
|
|
|
|
|
|
|
|
|
|
|
|
need to be passed into the javascript
|
|
errors don't display on first failed attempt, will fix later. Moved jquery js, images, css out to respective folders.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
search to header_top. Reduced borders. Started album grid improvements. Minor white space improvements. Still need to handle text/photo alignment in album grid, improve placement of search.
|
|
|
|
updates and added Gallery Info block for admin dashboard prototype.
|
|
form and form child elements.
|
|
site menu
|
|
and we can reuse it for a different popup
|
|
clashing with the superfish styling.
|
|
1) separate the classes that are generated by the Menu class from what is used for the rendering. The classes that are generated are gMenu, gMenuElement, and gMenuDialog for the Menu, Menu_Element and MenuDialog classes respectively.
2) Changed the ui.init.js to add the appropriate rendering classes to the above classes. All gMenu elements have the sf-menu class added. All elements of class gMenuDialog have the gDialogLink class added.
3) Use Superfish for the menus so they now float properly.
|
|
|
|
|
|
complete with icons for message types ( .gSuccess, .gError, .gWarning, .gInfo, .gHelp).
|
|
(1.6rc2) copied from the the corresponding vendor branch.
Move into the application/lib directory and remove from the theme.
Remove the ui.jquery javascript from the rearrange module and use the common library.
|
|
|
