| Age | Commit message (Collapse) | Author |
|---|
|
|
|
This reverts commit 940edac81c854227d1a25f482cb38c96b6937bb2.
Revert "Add window resizing support. Just can't seem to get loading icon to show up"
This reverts commit afd85945d7028cefd703c3f6bbebdf92f8e0477a.
Revert "Resolve issues with show the wrong album when slideshow is invoked from a photo page. In addition, implement the slideshow based on tags."
This reverts commit 152caf5195e3bbcdb353707fed5683ed07927f47.
Revert "Initial commit of a basic slideshow"
This reverts commit 5943761df282bfdfe68453de5c1682030006cd11.
|
|
showing a photo. Fixes #631
|
|
one. Duh!
Fixes #642.
|
|
|
|
|
|
|
|
Thanks to katpatuka for providing the fix.
|
|
|
|
photo page. In addition, implement the slideshow based on tags.
|
|
|
|
http://gallery.menalto.com/node/90306
Thanks rWatcher
Signed-off-by: Tim Almdal <tnalmdal@shaw.ca>
|
|
http://gallery.menalto.com/node/90306
Thanks rWatcher
|
|
of item. All other references use photo for non album and non dynamic pages.
Signed-off-by: Tim Almdal <tnalmdal@shaw.ca>
|
|
|
|
|
|
|
|
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.
|
