| Age | Commit message (Collapse) | Author |
|---|
|
Kohana makes this type of transition fairly straightforward in that
all controllers/helpers/etc are still located in the cascading
filesystem without any extra effort, except that I've temporarily
added a hack to force modules/gallery into the module path.
Rename what's left of "core" to be "application" so that it conforms
more closely to the Kohana standard (basically, just
application/config/config.php which is the minimal thing that you need
in the application directory)
There's still considerable work left to be done here.
|
|
|
|
|
|
when adding photos/movies/albums
|
|
collapse multiple spaces, drop the extension. Fixes ticket #237
|
|
error if we can't find one-- just assume its a photo).
|
|
views were being manually set. Also removed it from the Admin_View.
|
|
|
|
uploader. This is modeled on
http://codex.gallery2.org/Gallery3:Upload_UX but is not yet complete.
Notes:
* Changed #gProgressBar to .gProgressBar to support multiple progress
bars on the same page
* Added a bunch of CSS to the "needs a home" section in
themes/default/css/screen.css
|
|
Fixes ticket #120.
|
|
swf file for now
|
|
batch::start() before starting a series of events, and batch::stop()
when you're done.
In batch mode, the notification module will store up pending
notifications. When the batch job is complete, it'll send a single
digested email to each user for all of her notifications.
Updated the scaffold and local_import to use this. Haven't modified
SimpleUploader yet.
|
|
Starting a batch call batch::operation(name, item). In the case of
adding photos name = add and item is the parent of the new items.
When the operation is finished the batch::end_operation(name) is
called.
operation and end_operation events are called. Handlers
(i.e. item_created) can call batch::in_progress(name) to determine if
a batch is being processed.
|
|
start_batch and end_batch add and remove the batch id from the
session. Modules wishing to do batch processing, just need to fire
the start_batch and end_batch events. Other modules that need to be
aware of batches (i.e. notifications) just check the session for "batch_id".
|
|
events: start_add_batch and end_add_batch. The parameter is a batch
id which is generated on the first add request. The protocol is call
the add_photo as many times as required and then call finish when
done.
Also renamed the add method in local_import to add_photo so it is
consistent with simple_uploader
|
|
them using the h264streaming plugin. Everything else is a fairly
minor change.
|
|
|
|
extract a thumbnail out of it and if you click through we show it
using flowplayer.
|
|
|
|
This fixes the uploader on FF/Linux (and probably other platforms).
|
|
|
|
filenames.
|
|
This requires a little trickery to proxy the session id and user agent
through the ActionScript code so that we can assume the same session
in the uploader. It's also using its own path to add photos since
we'll want to have a slightly different protocol for dealing with
responses (as opposed to JSON or HTML).
A work in progress for sure, but it's already better than what we had before.?\024
|
