| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
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.
|
|
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
|
|
|
|
supersized based on ly last commit.
|
|
|
|
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.
|
|
Organize_Controller:
* Remove unnecessary constants
* Rename index() to dialog()
* Simplify _get_micro_thumb_grid
organize.js:
* Move sizing code in here from organize_dialog.html.php
organize_dialog.html.php:
* Move CSS and JS links in here so that we only load them when we need them.
* Move sizing code into organize.js
organize_thumb_grid.html.php:
* Move pagination logic in here, since it's view centric
* Collapse the css class determination code and inline it
|
|
caps) and more explicit about what it's doing.
* use toggleClass() to simplify the +/- css management.
|
|
|
|
|
|
processing
|
|
micro thumb grid, by setting all the parent elements to 100% in the
css and then subtract the height of the button bar
|
|
mechanism. Create a new"""
This reverts commit 7b1cca168cb9b29fcccdcdce9e32efb190e4575e.
Basically remove it and Bharat and I will fight it out in SF for a resolution :-)
|
|
the events to populate the button bar.
|
|
|
|
|
|
|
|
|
|
plus/minus""
This reverts commit e37526f94df74a52a9cf36f0a5a5e641958ebbb3.
|
|
doesn't really do""
This reverts commit 397468c47b8fc3fefeb54ff19a73980ed1dd8c20.
|
|
Create a new""
This reverts commit 9f396178cedc96abb282e72ff0e843e255c8225a.
|
|
This reverts commit 1f014aae6c16bbda62d8f5937180f11ccb0eb1b1.
|
|
really do"
This reverts commit a25f08d433d504a53763feb358a1aa7f5f798de6.
|
|
This reverts commit 869c3de9612a598dae0ce400991bdbe173a2decc.
|
|
icons. Branches with no albums, will not have an icon.
|
|
anything, but get the dialog up, populate the album tree and intelligently
populate the micro thumb grid.
Still to do:
1) get the microthumbs laided out ptoperly
2) expand and collapse functionality in the album tree
3) use the album tree to change the content of the micro thumb grid
4) Actually add some functionality
At the moment, it supports a callback "" to allow modules to add icons
to the organize drawer label. The close button is added outside of this
framework as it will always be last.
|
|
|
|
This is the first step towards having a simple, lightweight and
unified API for module interaction.
|
|
javascript lib (gallery.reload.js) which defines the functions
gallery_reload() and gallery_location(new_location). They just
do a window.location.reload() and window.location = new_location.
This change breaks the assumption that all themes will handle page reloads
the same and allows the theme to customize the page refresh.
|
|
theme. Because the theme comes first, this means that themes can
override any module resources, at the cost that we no longer have
namespacing for JS and CSS files.
The only file getting used outside of this model is
themes/default/screen.css which is used in the admin theme. I fixed
that by copying screen.css into admin_default and renaming its
screen.css to admin_screen.css. I also copied over all the images
that it was referencing.
Fixes tickets #48 and #539.
Theme API changes:
- theme_script(), theme_url() and theme_css() are no longer needed
- script(), url() and css() now refer to the first matching asset in
the module load path, where gallery3/lib is at the end of the path
|
|
|
|
This fixes ticket #546
Signed-off-by: Bharat Mediratta <bharat@menalto.com>
|
|
related events from within the model handling code. The only
exception to this currently is item_created which is challenging
because we have to save the item using ORM_MPTT::add_to_parent()
before the object itself is fully set up. When we get that down to
one call to save() we can publish that event from within the model
also.
|
|
1) The item_updated event no longer takes the old and new items.
Instead we overload ORM to track the original data and make
that available via the item. This will allow us to move event
publishing down into the API methods which in turn will give us
more stability since we won't require each controller to remember
to do it.
2) ORM class now tracks the original values. It doesn't track
the original relationships (no need for that, yet)
3) Added new events:
item_deleted
group_deleted
user_deleted
|
|
|
|
This reverts commit 31ffb82382d76390f1206944329dde86c687349c.
|
|
test to make sure that we continue to do so.
This makes sure that we don't have problems with 5.3 which treats the
literal "on" as a boolean.
|
