hoist1999 / sappho Goto Github PK

we need a page that lists the twenty most recent photos (a thumbnail view).

currently, we require that users manage to resize and upload their images
themselves.

we could offer some simple scripts that resize and/or upload images.

we need to be able to edit an image's information.

exactly what it says--

we currently store some text regarding each set. this should be displayed
on the set page, along with the thumbnails.

use an s3 call to make imported images public in the php script.

it would be nice if there were a feature to import a number of images with
a default, common set for them all. this could be achieved by including a
link to 'import images into set' link on the set page (much like there is
an 'import images' link on the images page)

i.e. when $s3_path = '' (and the a/b directories are
http://xxx.s3.amazonaws.com/a etc), sappho does not successfully
acknowledge the existence of image/thumbnail pairs; however, when the a/b
directories are within some other directory, they are recognized.

currently, the software assumes that http auth has been implemented to
restrict access to the management backend.

i feel that moving to a cookie-based auth system would offer many benefits.
mostly, i am looking forward to httpd-agnostic software and the secure flag
for cookies.

once photo sorting within a set is finished, we need this link to the next
image in set to work.

REQUIRED: http://code.google.com/p/sappho/issues/detail?id=1

the individual photo page needs a link back to the set (thumbnail view).

maybe we also want links to the collections?

currently, we require the user to resize the images into three versions.

we could, however, simply have the user upload the high-res version, and
have an ec2 instance resize the photo into the necessary versions.

ref:
http://developer.amazonwebservices.com/connect/entry.jspa?externalID=1602&catego
ryID=175

when viewing a set, the parent collection is emphasized but not linked.
this would be useful to be linked as well.

yeah.

it would be nice if there were a README file which included a more detailed
description of the installation and configuration process.

similarly, more documentation regarding the logical structure of image sets
and collections within the application.

I am not a developer/coder - simply a guy trying to offload massive amounts of 
data (photos and videos) on to the "cloud" via Amazon S3 and then view all 
those files with a picture viewer that will generate thumbnails.  Think of it 
like Picasa, but everything is housed at Amazon S3.

Does sappho do that?  Can I buy it?

Sorry for my naivete.

AGT

there is a dashed border that runs down the right side of each page. it
does not span the entire height of the visible area. fix it so that it does.

there should be links throughout the site to the about page.

there is a constant defined in several files in the /manage/ directory that
has a hardcoded:

{{{
define('SAPPHO_HTTPS', true)
}}}

statement near the top of the file. this can cause severe lag times on
installations of sappho which don't reside in https directories.

`ORDER BY date_imported DESC`

will not allow drag & drop on /manage/set_sort.php.

os x 10.4.11 / safari 3.1.2

convert from iso-8859-1 to utf-8.

we must have a thumbnail ("c") and a web-viewable ("b") version of every
image. but it's not necessary to have a high-resolution ("a") version of
every image.

so let's make the import script detect if a high-res version exists, set a
field in `photo_image` accordingly, and omit the link to the high-res
version on image.php accordingly.

we need to be able to manually change the sorting of images within a set.

when images are imported (and inserted into `photo_image`), we need to
specify an integer for the `sort` field.

we need to be able to specify a license (e.g., creative commons, none).

we should show this license on every page that displays an image.

at first, we will just have a site-wide license.  perhaps later we will
allow a different license for each image.

exactly what it says--

i believe that the user interface (front-end) could be better organized.

first-time visitors may have difficulty understanding how the photo album
is organized, and as a result, may not browse the album as intended.

the ui should be more clear with respect to organization.

we should not use id numbers in the urls. instead, we should use some
string that is specified in the database via a unique field (and altered in
the backend).

we need an rss feed for new photos.

the import script does not check to make sure that all three versions of
the photo exist. it should do this, so that dead images won't go live.