| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
Kaare)
|
|
of item. All other references use photo for non album and non dynamic pages.
|
|
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
|
|
helper, so that we can use it else where (i.e. the new organize module)
Signed-off-by: Tim Almdal <tnalmdal@shaw.ca>
|
|
#gProgress" and if it finds it assumes that it is a progress dialog and removes the title. This pathc changes the name of the div containing the progress bar to gServerAddProgress and avoids the issue.
Signed-off-by: Tim Almdal <tnalmdal@shaw.ca>
|
|
#gProgress" and if it finds it assumes that it is a progress dialog and removes the title. This pathc changes the name of the div containing the progress bar to gServerAddProgress and avoids the issue.
|
|
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.
|
|
helper, so that we can use it else where (i.e. the new organize module)
|
|
do a single select after a drop operation. I think its related to needing to destroy the existing selectable before creating the new one. The error I get is "this._selection[i].data("selectabe-item") is undefined."
|
|
showing. As well fixed a problem where selectable single clink no longer
worked when the album was reloaded.
|
|
drag selected images and drop them on the micro thumb grid in a different position or onto a branch in the gallery tree. No ajax call is made, it just writes the generated url and post data to the console, so it only works in ff right now.
|
|
|
|
to get the draggable autoscrolling working, so this is a poor replacemment.
|
|
visual feedback of the drop position between thumbnails, so this commit provides a checkpoint for trying various options
|
|
and album covers in the context menu.
Notes:
- This requires context_menu() to have a CSS selector that refers to the
<img> that we're operating on, otherwise we don't know how to find the
thumbnail, etc.
- Create Menu_Element_Ajax_Link which has an ajax_handler attribute
that contains a snippet of JS that we're going to run when the ajax
call returns.
- Add $.gallery_replace_image in gallery.common.js
- Add lib/gallery.ajax.js which can be used to ajaxify any link, and have
ui.init.js in the themes call that on all .gAjaxLink elements.
|
|
|
|
- Update digibug_event::context_menu() to take the actual item
- Change gallery::context_menu() to not require the page_type as an argument
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Gallery 3!" dialog, but not immediately open the "change your
password" dialog.
|
|
|
|
Conflicts:
modules/gallery/js/quick.js
|
|
identifies situations where its restricted by open_basedir.
We now track more informatoin about the toolkit including the version
and any errors we encountered while doing the detection so that we can
provide more info downstream. This makes graphics::detect_toolkits()
a little heavier, but that's ok because it should not be called very
often.
In the process, refactor the controller and view hierarchy so that
it's a little more straightforward in the code.
Fixes ticket #616.
|
|
supersized based on ly last commit.
|
|
Completes the conversion from using 1 to true for the immediate paramter to gallery_dialog
|
|
|
|
|
|
|
|
click events, but just show the dialog. Also remove the destroy method and put all the cleanup into the dialog close handler
|
|
affected. Practically speaking this means that we'll reindex items
when tags are added or removed from them.
API change:
Remove item_related_updated_batch event.
Rationale:
While this is an efficient event, it requires module developers to
support two event APIs for staying up to date and increases the
likelihood that they'll forget one and have data corruption. Force
them all through the slower but more reliable pipe, for now. We
can always try to improve efficiency by using the batch_start and
batch_stop events.
|
|
|
|
labels in the menu.
|
|
|
|
reason (probably a timing thing) the height of the contents was not being set correctly in FF. So we just hard code an estimate of the size of the Draw handle, and message areas.
|
|
Conflicts:
themes/default/js/ui.init.js
|
|
and have some basic namespacing:
showMessage --> gallery_show_message
vAlign --> gallery_valign
showLoading --> gallery_show_loading
Convert gallery.show_full_size.js to be a jQuery function and give it a namespace:
show_full_size --> gallery_show_full_size
|
|
gallery_dialog respectively
Signed-off-by: Bharat Mediratta <bharat@menalto.com>
|
|
Signed-off-by: Bharat Mediratta <bharat@menalto.com>
|
