Simple syntax of gallery code. Code of the gallery contains only some text. As a consequence, future changes to a gallery are very straightforward and quick. All is required to do some changes is just text editor. Internet browser doesn't have to receive each gallery picture one by one, only gallery text. It speeds up the process of content adjustment.

Placing gallery with pictures is just placing of certain set of characters with specified order and meaning (syntax), limited with braces: {...}. Engine which processes www site (Joomla!) will take care to interpret such a text string in a way that for User it will be visible as picture gallery.

Optionally any text description could be added to any picture. A comment is displayed to User if one will move mouse cursor over a miniature or, after click in any photo miniature, at the bottom of the photo. Comments aren't placed in separate file or in file header. They are present in body of article content. Thanks to that it's possible to edit them easily with ordinary text editor.

Google search engine indexes picture file names as well as picture comments.

Either picture file names, either text strings (comments) are indexed by Google search engine. It means that after gallery is ready, file names and comments might be searched with use of Google.

Full control of the Author over size and order of the photos in gallery.

Author of gallery has full control over size and order of photos. Size of the photos depends only on Author preferences. Change of the photo order in the gallery is as simple as text edition. It could be done as copy paste combination in text editor.

Many photo galleries works as follows: in code there are storied only information about photo location, and its original size. Just on time when User starts to browse photos, the gallery engine alters size of photos, keeping resized versions temporarily in cache memory of server. When user stops browsing the temporary copies are removed. Operation of photo resizing takes time and a lot of server resources like memory and processor time. From User point of view a time needed to resize photos is added to a time required to get photos from its origin. Everything is fine if Author's web page is visited by small number of Users and each User browse another gallery. Lets consider situation when there significant amount of Users. Then it might be a case that server won't be able to quickly and efficiently process all the photos and what's more User will have to wait much longer for the final effect: resized photo.

YASIG just reads photos already prepared to be viewed. There is no overhead due to photo processing. What's more server is able to serve many Users concurrently. So it could be said that YASIG pays off at its best in case of big, popular galleries...

YASIG just displays previously prepared photos. Resized, shrinked photos of the time are much smaller then original photos. As a consequence Author can save some server side disk volume. For example typical photo in size of 2816 x 2112 pixels takes about 2.4 MB in volume. The same photo resized down to 640 x 480 pixels takes only 81.6 kB and resized down to 200 x 150 pixels takes only 18.5 kB. So it could be clearly seen we are able to spare about 2.3 MB of disk volume per each photo.

Many photo galleries works as follows: in code there are storied only information about photo location, and its original size. Just on time when User starts to browse photos, the gallery engine alters size of photos, keeping resized versions temporarily in cache memory of server. When user stops browsing the temporary copies are removed. Operation of photo resizing takes time and a lot of server resources like memory and processor time. From User point of view a time needed to resize photos is added to a time required to get photos from its origin. Everything is fine if Author's web page is visited by small number of Users and each User browse another gallery. Lets consider situation when there significant amount of Users. Then it might be a case that server won't be able to quickly and efficiently process all the photos and what's more User will have to wait much longer for the final effect: resized photo.

YASIG just reads photos already prepared to be viewed. There is no overhead due to photo processing. What's more server is able to serve many Users concurrently. So it could be said that YASIG pays off at its best in case of big, popular galleries...

To browse sequentially gallery photos one can simply use a mouse by clicking. All what has to be done is click to the left or right half of a photo of currently displayed photo. Then additional buttons are temporarly overlayed for a time being when mouse cursor is placed over a photo area:

• next photo button is displayed if right half of a photo is clicked,
• previous photo button is displayed if left half of a photo is clicked.

To browse sequentially gallery photos one can simply use a keyboard (shortcuts):

• next photo is displayed if 'right cursor' (->) is pressed down,
• previous photo is displayed if 'left cursor' (<-) is pressed down,
• to exit gallery just press 'Esc' key.

In address field of your web browser put address of your web site finished with "administrator" section, for example:
http://www_address_of_your_web_site.extension/administrator

After a while your screen should look like neighbouring picture.

In the field "Filter" put the string "yasig" and push the "Search" button.

After a while one should see a table similar to the one presented at neighbouring picture with 4 installed extensions:

• com_yasiguncle,
• pkg_yasiguncle,
• plg_yasig,
• plg_yasiguncle.

These are all extensions belonging to yasig solution.

Author has chosen an article, where YASIG photo gallery will be placed, opened this article, put the cursor in article text content in the place where YASIG gallery call will be placed.

Just under the editor window there is visible 'yasiguncle' button. If the button is clicked, the wizard will come out. With assistance of the wizard all next tasks are made.

When 'yasiguncle' button is clicked, screen will be covered with neighbouring window. This is mentioned wizard. Author of a gallery should now configure it by changing at least some of the options. First of all one should indicate input folder, so the folder where pictures were uploaded. Later the output folder should be specified, so the folder where processed files will be placed. (Author may change also all other options, which are explained in details in the following section of this guide, Configuration of yasigunucle plugin).

Author may change options 'Input folder' and 'Output folder' in two ways. The first way is clicking in second text row below the text 'Input folder' and 'Output folder'. In consequence small window with list of server folders will be opened. In this way, with use of mouse, one can specify existing folders. The second way is placing input and output folders manually. For this purpose the first text input fields are prepared, just below the text 'Input folder' and 'Output folder'.

At neighbouring screen gallery Author already changed required options. If the visible link Show options is clicked, one may change all other options.

When all the options follow requirements of gallery Author, one should click button 'Go to next step!' to proceed.

On the screen small turning circle will be displayed. It shows time of picture processing. In a moment syntax of YASIG gallery will be displayed together with button 'Insert yasig-output into article'. Click this button with mouse.

When the mentioned button is clicked, in article content correct YASIG gallery body will be placed. All one have to do now is saving the article.

In the field "Filter" put the string "yasig" and push the "Search" button.

After a while one should see a table similar to the one presented at neighbouring picture with 4 installed extensions:

• com_yasiguncle,
• pkg_yasiguncle,
• plg_yasig,
• plg_yasiguncle.

These are all extensions belonging to yasig solution.

Mark a square to the right from "pkg_yasiguncle" string with a tick.

Push the button "Uninstall" (top-right corner of the screen). After a while one should see the following messages:"Unistalling package was successful" and "There are no extensions installed matching your query". (The latter message is caused by string "yasig" still present inside of "Filter" field.

After a while one will see list of all installed plugins.

In the field "Filter" put the string "yasig" and click the neighbouring to the right button "Search". After a while  one will see on the screen all installed plugins which fit to criteria of filtering.

Click in the name string "plg_yasig".

Next screen displays all configuration options available for this plugin. Screen is divided into several areas:

• Basic Options
• Details

When YES option is set, when last photo in the gallery is displayed and pressing 'Next' button, there will be displayed the first photo of the gallery.

When User clicks on whatever miniature in a gallery, background of the web site is obscured (opaqued) and in the front photo is displayed in so called normal size. The parameter 'overload of opacity' determines a level of background opacity.

Color of picture background. The available options from the drop-down list: black, red, pink, yellow, green, cyaneous, blue, white.

When miniatures are displayed at a web page, it's a size (in pixels) of a margin between top edge of a miniature and a content above.

When miniatures are displayed at a web page, it's a size (in pixels) of a margin between right edge of a miniature and a content along side.

When miniatures are displayed at a web page, it's a size (in pixels) of a margin between bottom edge of a miniature and a following content.

When miniatures are displayed at a web page, it's a size (in pixels) of a margin between right edge of a miniature and a content along side.

Text string displayed in the area of a button used to display the next picture in a gallery.

Text string displayed in the area of a button used to display the previous picture in a gallery.

Text string displayed in the area of a button used to close a gallery.

Text string displayed in the area just under the picture in normal size.

Text string displayed in the area just under the picture in normal size.

Enables to switch off JQuery library. This option is handful if web site already uses some extension which is based on JQuery. Thanks to this option one might avoid of multiple loading into memory of different versions of JQuery library, what pays off with shorter time of web processing and less amount of errors.

Under each photo from within gallery there might be displayed additional text string. It might be for example short info about shortcuts handful for navigation between pictures of gallery.

When User click in any miniature there will start well known and beloved Lightbox script. Currently viewed page will be obscured with semitransparent background and in the front there will be displayed picture in normal size.

If then User will move mouse cursor over normal size picture there are displayed additional control buttons. For example if User move cursor over the right part of a picture there will be displayed string 'Next' suggesting that if User clicks then next gallery picture will be displayed.

Another set of gallery attributes are marked in red: just below main picture body there is displayed example comment; at top right a control button used to display next gallery photo.

There are marked in red: at bottom left an informational string saying about number of currently displayed picture in gallery sequence, at bottom right the control button used to close gallery normal size view, at top right another control button used to display previous gallery picture.

Option 'Additional information' lets to display any additional string which will be repeated for all pictures within gallery. It can be for example a sentence explaining how to navigate within gallery pictures.

AccessPathToNormalSizePhotoFile/picture1_normal.jpg |
AccessPathToMiniatureSizePhotoFile/picture1_miniature.jpg |
Example comment dedicated to picture1 ||

AccessPathToNormalSizePhotoFile/picture2_normal.jpg |
AccessPathToMiniatureSizePhotoFile/picture2_miniature.jpg |
Example comment dedicated to picture2 ||

...

AccessPathToNormalSizePhotoFile/picturen_normal.jpg |
AccessPathToMiniatureSizePhotoFile/picturen_miniature.jpg |
Example comment dedicated to picturen ||

}

After a while one will see list of all installed plugins.

In the field "Filter" put the string "yasig" and click the neighbouring to the right button "Search". After a while  one will see on the screen all installed plugins which fit to criteria of filtering.

Click in the name string "plg_yasiguncle".

Next screen displays all configuration options available for this plugin. Screen is divided into several areas:

• Details
• Basic Options

Let's assume that input gallery folder consists of 5 pictures. If this option is set to 'yes' in article content will be inserted 5 separate YASIG galleries, one for each photo from input folder. Each photo will be inserted into table, (1 row, 2 columns in size), into left column. Width of a left columnt will be adjusted to size of a thumb image.

This option is helpful if Author is willing to prepare a guide, where aside of a picture is placed explanation text.

{yasig
...
}

Surrounding text.Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text.

Surrounding text.Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text. Surrounding text.

c. The third option depends on change of an order of plugin loading. With use of administrative configuration panel it is possible to change order of loading a code of plugins. On the left side of the screen one cand see example print screen where was changed the order of 'slimbox' and 'YASIG' plugins.

a. Check if toggle of the parameter 'Load JQuery' helps (configuration of YASIG extension: administration panel menu: Extensions -> Plug-in Manager -> plg_yasig).

c. The third option depends on change of an order of plugin loading. With use of administrative configuration panel it is possible to change order of loading a code of plugins. On the left side of the screen one cand see example print screen where was changed the order of 'slimbox' and 'YASIG' plugins.

Damian Damaszke

Nickname: woroo

Poject role: software developer.

Main code developer, author of 'yasig' plugin and .php script used for processing of pictures.

26 years old. Education background: master engineer in informatics. On everyday life works as software developer, speciality in web applications and user interfaces, mainly .NET. His main professional achievement is, among others, designing of graphical user interface for SID system (informatics system for train irregularities detection devices).

Pastime: adoration of beautiful women, puzzles in any form.

Maciej Szczepański

Nickname: kroovechkaja

Poject role: software developer.

Creator (or more truly 'converter' ) of the YASIG uncle code (editor-xtd button and component). Age group 83, education background master engineer in informatics. On everyday life works as software developer specialized in .NET and C++. His main professional achievements are projects related to railways:  diagnostics of rolling stock irregularities, exclusively commercial.

Pastime: ASG (Air Soft Gun), breeding of exotic reptiles.

Sławomir Rapeła

Poject role: tester.

He joined YASIG project spontaneously and works as software anti-bug squad .

30 years old. Education background: master engineer in informatics of management. On everyday life manages his own business. His main professional achievements, among others, contribution in project eUrząd (Polish: eOffice), System Elektronicznego Monitorowania Pracy (Polish: System of Electronically Aided Work Survaillance), project manager for ITD (Polish: Inspectorate of Road Transport), System Wspierający Centralną Ewidencję Naruszeń (Polish: Supporting System For Central Records of Infringements).

Pastime: books, travels.

Karol Lewoniewski

Nickname: karas

Poject role: software developer.

Age group 1985. Master of science degree, informatics and applied physics, speciality: applied informatics. On every day life he works for one of the biggest Tricity informatics oriented companies supporting banks. One of his main achievements till now is participation in project of software aided ship design for CTO in Gdańsk city.

Pastime: journeys.

Maciej Słojewski

Nickname: mslonik

Project role: project manager.

Originator of the YASIG project.

Age group 1976. More about my professional background here.

More about my private inspirations here.

Sylwia Ławrów

Poject role: software developer.

She joined the project in February 2012. Student of Informatics at Fauctly of Electronics, Telecommunication and Informatics. After hours worsk as freelancer designer of web pages.

Pastime: cinema, bicycle riding.

Karol Domagała

Nickname: kazuar

Poject role: software developer.

He has modified .js script useful for display of pictures when user clicks at any (part of YASIG plugin) and developed ajax code showing progress of pictures processed when pictures are shrinked.

Pastime: overhauling of old cars, participation in open source projects.