FotoWeb 6.0 User Guide - Customization - FotoWare

More documents

Recommendations

Info

Customizing FotoWeb 3.0 4 Tips and tricks 4.1 Evaluating multiple conditions Combining and evaluating multiple conditions using standard approach requires nesting of condition evaluations. Depending on the number of conditions to combine and the number of times the evaluations are to be repeated, the templates can end up being rather complex and messy that further can be hard to maintain and debug. It can, therefore, be a good idea to create some own conditions that represent a combination of standard conditions. For example, if you want to categorize a user’s access level to the archive and later use this information in a couple of places, then you can do as follows: Example 47: Evaluating multiple conditions. In this example we have created two conditions ‘accessLevel1’ and ‘accessLevel2’ and set their initial values to false. Then we perform the real evaluation and reset these conditions’ values accordingly. Once done, we do not need to repeat the deeply nested evaluation any more and can use the values of ‘accessLevel1’ and ‘accessLevel2’ for further evaluations. 4.2 Special archive You can allow different archives to be displayed differently. A trivial approach to this would be to look for an archive identifier and split the grid using if-else evaluations to display archive contents differently. This approach requires designing a complex grid page that evaluates archive identifier in multiple places and repeats major parts of the code with different parameters. Maintenance of such pages is also difficult and full of risks. A better approach to achieve the same results more elegantly would be to design two or more different grid pages. This way each grid page will be rather small in size and contain clearer standard FotoWeb and Html code. Simple pages are also easy to maintain and debug. In case of unknown or hard-to-find errors it is then no harder to just rename a page to one that is working until further than being stuck with a large messy page that won’t display anything correct. The trick here is to create a dynamic system, as rest of FotoWeb, so that the archive lists generated on top of the grid pages ‘know’ which grid page to use for different archives. Hard coding these archive lists will require manual updating every time an archive on the system is added, deleted or updated. A dynamic solution can be achieved by using a newly introduced ‘CompareNumbers’ tag in FotoWeb. With this tag, we can continue generating the archive list dynamically while watching for the archive ids and create grid links for different archives. For example: 40 / 47
Example 48: Special archive with special grid page. Customizing FotoWeb 3.0 In this example, we compare the archive ids reported by the ‘ListArchives’ tag with the id of the archive that is ‘5001’. If the id of the archive being enumerated is 5001, then we create a link with ‘SpecialGrid.fwx’ while all other archives are linked with ‘Grid.fwx’. 4.3 Image marking In some environments it is important for the clients to know if an image has already been used earlier or, even better, when it was lat used. Since FotoWeb has re-implemented the IPTC history event writing, it has become an easy task to perform. The destinations can be set to write IPTC history events on source images when they are processed through workflow. These events can later be read back in the grid page to mark images. This way the client can get visual information on images that have been used and even how long ago were they last used. There are no limitations on how such a solution can be implemented. One way is to utilize JavaScript along with FotoWeb commands. For example: FotoWare 41 / 47
Page 1 and 2: Customizing FotoWeb 6.0 Copyright (
Page 3 and 4: 1 Introduction Customizing FotoWeb
Page 5 and 6: 2.2 Scripting in FotoWeb Customizin
Page 7 and 8: 2.3.1 Empty tags Customizing FotoWe
Page 9 and 10: Customizing FotoWeb 3.0 Since the v
Page 11 and 12: Example 19: Removing custom variabl
Page 13 and 14: 2.3.6.3 Existence of conditions Cus
Page 15 and 16: 2.5 Include files Customizing FotoW
Page 17 and 18: 2.6.3 Avoid illegal peers Customizi
Page 19 and 20: 2.7.1.1 Script (template) selection
Page 21 and 22: 2.7.2 Validating the templates Cust
Page 23 and 24: 2.7.2.2 Manually edit templates Cus
Page 25 and 26: 3.2 Adding the first tag Now that w
Page 27 and 28: Next, we will evaluate a condition
Page 29 and 30: 3.3 Adding ‘ImageList’ tag Cust
Page 31 and 32: Customizing FotoWeb 3.0 Next we wil
Page 33 and 34: 3.4 Displaying images Customizing F
Page 35 and 36: Customizing FotoWeb 3.0 Next, we wa
Page 37 and 38: Customizing FotoWeb 3.0 Note that w
Page 39: Screenshot 23: Improving page navig
Page 43 and 44: 4.5 Displaying navigation informati
Page 45 and 46: 5.1.3 Examples We start by looking
Page 47: Customizing FotoWeb 3.0 Example 20:

FotoWeb 6.0 User Guide - Customization - FotoWare

Create successful ePaper yourself

Delete template?

Save as template?