| Age | Commit message (Collapse) | Author |
|
a call to Organize with the appropriate album open. I have not yet
figured out how to get the SWF code to highlight the active image, but
that's coming. Partial fix for #1204.
|
|
|
|
back to the same canonical domain that we came from. Else Flash makes
crossdomain.xml requests, fails, and falls over.
Fixes ticket #1298.
|
|
by the following rules:
1) An initial dialog or panel load can take either HTML or JSON, but
the mime type must accurately reflect its payload.
2) dialog form submits can handle a pure HTML response, but the mime
type must also be correct. This properly resolves the problem
where the reauth code gets a JSON response first from the reauth
code, and then an HTML response when you reauth and continue on to
a given form -- try it out with Admin > Settings > Advanced.
3) All JSON replies must set the mime type correctly. The json::reply
convenience function does this for us.
4) By default, any HTML content sent back in the JSON response should be
in the "html" field, no longer the "form" field.
The combination of these allows us to stop doing boilerplate code like
this in our controllers:
// Print our view, JSON encoded
json::reply(array("form" => (string) $view));
instead, controllers can just return HTML, eg:
// Print our view
print $view;
That's much more intuitive for developers.
|
|
method to set the content type header and encode the response as a json object
|
|
|
|
|
|
dialog. Convert all the controllers
that create the data to go into a dialog to return the html as part of a json object.
|
|
returns just the access key string for the active user. That's how we
use the API, so keep it simple.
|
|
dialogWidth and dialogHeight and adjsut the internal controls when added to
the stage.
2) Cleanup the controller code
|
|
|
|
of appearance in the template. Also remove the @todo's
|
|
every time the SWF file changes.
|
|
removed and replaced with the restUri, which contains the relative uri for the rest controller. The controller parameter is now the relative uri for the organize controller. The protocol parameter was added. In addition, there is not default size for the organize flex object. It attempts to fit within the gallery3 dialog box.
|
|
|
|
contains a json encoded string. Also address the problem that IE returns the color values differently that Firefox and Chrome
|
|
add a progress bar for longer running tasks
|
|
Rearrange is moving items within the same album, move is moving to a different album.
|
|
dialog.
|
|
|
|
|
|
|
|
is now done in the browser.
|
|
ticket #939.
|
|
in the album tree. Fixes ticket #959.
|
|
|
|
|
|
1) Controller::$input is gone -- use Input::instance() now
2) Handle new 'database.<default>.connection.params' parameter
3) Handle new 'cache.<default>.prefix' parameter
|
|
|
|
|
|
API a little clearer. Write a test for it, too.
|
|
|
|
variables were reversed
|
|
1) check that target and source are not the same.
2) check that the source is not already a child of the target (use to be a
descendant) Fixes #741.
|
|
out of the move for now.
|
|
whenever we expand a tree.
|
|
it right away while still allowing incremental tree loading.
|
|
up to the album that you're viewing, and if you move a photo to a
different album it'll reload the entire album tree.
|
|
|
|
slow down simple operations. We may run into problems with more
complex operations, but let's only add tasks into the mix when it's
clear that we need them.
|
|
* Clean up naming conventions for variables in the controller
so that we specifically refer to albums with $album_id, etc.
* Move complexity for drawing tree out of the controller and into
the view.
* Simplify task definitions to get rid of extraneous text
* Change __PLACEHOLDERS__ to clearly define which is the album
and which is the item that we're moving before/after
* Remove as many CSS ids as we can from the tree view to keep
things simple
|
|
change the sort order on the fly.
|
|
|
|
|
|
|
|
1) If images are dragged from the content pane and dropped on a branch in the
tree that the user only has view priviledges, then the drop is cancelled
and the images are reverted.
2) The user cannot click on a branch, to which they only have view priviledges,
the content pane does not change to the new album
|
|
direct sql update. This bypasses the gallery3 event mechanism. Fire a album_rearrange event when the rearrangement is complete
|
|
batch::start() method so notifications are queued
|
|
bypassing ORM and generating the sql directly.
|
|
the debug statements in until we can solve this issue.
|