| Age | Commit message (Collapse) | Author |
|---|
|
the "context" menu.
This new context menu is generated using the typical event processing
system, like our other menus. The specialized quick CSS and JS is now
gone, replaced by our generic menu handling code. It's all rolled
together currently using the thumb_menu UI for easy packaging. All
the CSS and JS is updated.
NOTE: the non-dialog links (rotate, album_cover) have a broken UI
because they return JSON which the quick.js code handled specially,
but we don't handle properly now. I need to fix this.
|
|
|
|
|
|
|
|
1) Stop changing the menu classes in JS, instead allow us to specify
it in the Menu class itself and then set it to be gThumbMenu in Theme_View
2) Move the gThumbMenu init code to the bottom of the $(document).ready() block;
something in there was interfering with it.
|
|
gPhotoMenu for use on both album and photo pages, eventually.
|
|
|
|
|
|
absolute within them. Moved css from quick.js to quick.css.
|
|
|
|
toggle, and forms to external files.
|
|
jQuery UI button, they stand well on their own. Thx to Ben Dunkle!
|
|
single quotes in JS.
|
|
success green brighter.
|
|
|
|
unstyled list appear which causes the page layout to flicker.
|
|
|
|
|
|
button is clicked. Used jQuery UI Effect to .highlight() to bring attention to newly added comments. Also added a named anchor to our block library to allow direct linking/scrolling to those blocks on the page.
|
|
content now clears the menu. Added IE-specific stylesheet to admin theme.
|
|
|
|
|
|
|
|
user/group buttons and search form on search results page.
|
|
AJAX)
removed unnecessary {element: dialogLinks[i]} from dialog and panelLink handling. now uses event.currentTarget
|
|
|
|
|
|
|
|
|
|
link added. Also need add the slideshow link to the menu.
|
|
|
|
|
|
|
|
|
|
Comment updates.
|
|
gAddTagForm). This maintains styles when forms are are reloaded into the DOM. Haven't figured out how to fire shortFormInit() when a form is reloaded into the DOM, as gAddTagForm is :(
|
|
container. Brought back borders. Use a neutral bg color for albums. Link item titles, not just thumbnails.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
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.
|
