ԭYarpengallery
룺Ƕʻ
汾0.1
űPHP
ԣEnCs
ݿ⣺ֱ
PHP5.0+php-imagick module 2.0+
С105Ktar.gz
2009.1.20


Yarpen Galleryһ򵥡ֲʧǿPHPԴȳݿ⣬֧jpgpdfmp3wmaoggļҲԸҪӡҷΪǶʻȣYarpenӦߵ֣Galleryܶ˳Ϊᡢͼ⣬̫ɰͣǻ󡣹GalleryվǳڼûУаȨʶһ棬ͼƬۣ˭ԸءһЩGalleryıܹשӭλĲ֧֡
Ե
ԴGalleryٸԿYarpen Galleryԭǣ
1.鷳
2.ʱݣϴ򵥣ʹã
3.ɱػ㸸ĸ
4.ʾʧ棻
5.ʳƷƬůɫʾ
6.ϣԼݱ¼ҲôѡYarpen Gallery
װ
1.ؽѹļ
2.༭config.phpļ
3.config.phpTHUMB_DIR, DISPLAY_DIRĿ¼ȷϿд
4.ý塢ͼƬļBASE_DIRĿ¼Ҳconfig.phpãҲĬϣ
5.index.php, inc/style.cssǲļҪ޸ģ
6.ʻҳindex.phpԶͼ
7.ϲǾߺƿơƣ
Aiving.com

ʾhttp://www.aiving.com/gc/yarpengallery
http://www.aiving.com/space.php?do=mtag&tagid=88
أhttp://www.aiving.com/gc/yarpengallery/yarpengallery.rar


YARPEN GALLERY

Author: Petr Vanek <petr@yarpen.cz>
License: MIT (http://www.opensource.org/licenses/mit-license.php)

Files in inc/thickbox directory are taken from thickbock project: http://www.opensource.org/licenses/mit-license.php
Icons in inc directory are taken from Oxygen icon theme: http://www.oxygen-icons.org/


I hear you asking: "yet another web gallery?"

Well, this is the gallery that fit *my* needs. It's up to give it a chance. See _About_ section for more info and philosophical thoughts about joys and sorrows of web galleries.

Yarpen-gallery can handle images, music files (mp3, ogg, wma...), videos, and all other binary files as I require to handle it -- with [http://jquery.com/demo/thickbox/ thickbox] popups for images and with simpla access via links in the case of binary files.

== Installation ==

  # Download and unpack the tarball into requested directory.
  # Edit config.php file to fit your needs.
  # create _THUMB_DIR_, _DISPLAY_DIR_ (specified in config.php) and make it writable for webserver
  # copy your media/directories/files into _BASE_DIR_ (specified in config.php)
  # customize webpage layout (index.php, inc/style.css)
  # visit galleries with webbrowser to create thumbnails and displays
  # enjoy it and buy me a beer

=== Use this gallery in existing web ===

  * just take index.php as an example. It can be inserted wherever - in all PHP codes.

== About ==

There are hundreds of web galleries available. Why I decide to write one more? The answer is simple:
  * I am lazy.
  * I want to have a *reusable piece of software featuring backup facility* of family photo collection.
  * I (read: my pretty wife) need *the simplest files upload* as is possible - just upload via ftp, sftp, scp, webdav, or whatever your server supports.
  * It should be *fully localized* with *minimal amount of text to translate* for our older parents.
  * It should display *pictures of doggies* without any distortion.
  * Images of food and beer should be displayed in *shiny warm tones*.

All these points are fulfilled with this *cool* yarpen-gallery

== System Description ==

The gallery is based only on filesystem (no additional database is needed). Yarpen-gallery is inspired by [http://www.davilin.com/tbg/ Thickbox Gallery (TBG)], the most usable gallery I've ever found, but it takes much more simplified functionality set (no additional files handling, commenting, etc.).
 
Yarpen-gallery is much more faster than TBG (and Gallery2, Coppermine and whatever I tried) for large collections.

=== Background ===

It takes files from so-called _archive_ directory and transforms it into _display_ and _thumbnails_ files. Files in the _archive_ archive are left untouched (archive/backup feature).

Let's describe a small example.

This is the base structure of directories before first upload:

{{{
/albums/
/thumbnails/
/display/
}}}

Then you connect with your ftp client to upload some files:

{{{
/albums/
  - foo
    - photo.jpg
    - video.mpg
    - document.pdf
/thumbnails/
/display/
}}}

Now, when you visit the gallery with browser some important things happen:

{{{
/albums/
  - foo
    - photo.jpg
    - video.mpg
    - document.pdf
/thumbnails/
  - foo
    - photo.jpg.jpg
    - video.mpg.jpg
    - document.pdf.jpg
/display/
  - foo
    - photo.jpg.jpg
    - video.mpg.jpg
    - document.pdf.jpg
}}}

Files in _thumbnails_ and _display_ directories are created on the fly (of course you can use a shell/python/whatever scripts to create it yourself or from cron.


== Technical Informations ==

*Requirements:*

  * PHP 5.0 or later
  * php-imagick module 2.0 or greater (prefered)
  * php-gd module
  * two directories writable by webserver

*Miscellaneous notes for code crawlers:*
  * It should use exif, more ajax, whatever). No it doesn't. Or patch it yourself and send it to me.
  * It's writen with functions. I don't use classes as I don't need to.
  * There is no additional template system used. You know, PHP is templating system itself.
  * It mixes html and logic together. Who cares?
  * And many more - just because I don't like web coding.