Archives of the Frogans technology mailing lists

Archives Top > Frogans-awards mailing list > May 2016  by date | by thread > Message posted

<Previous message by date] [Next message by date>
<Previous message by thread] [Next message by thread>

From <contact@...>
Sent Sat, 28 May 2016 11:50:43 UTC
Subject [Frogans technology - Frogans-awards] Frogans Tip for Day -10
Date Sat, 28 May 2016 11:50:45 UTC

In the spirit of the Frogans Awards, I'm going to submit, here and on
[1], a Frogans authoring tip each day through
June 6th, the day before the submission deadline.

So, with just ten days left before you submit your Fro-creation...

Frogans Tip for Day -10

Use a naming scheme for "fileid"s, "resid"s and "layerid"s

The production-chain nature of FSDL requires that you create a lot of
identifiers in your FSDL document. And each identifier in a document
must be different from all of the others.

For example, say you're going to use an image file called "icon.png."
For showing that image on a Frogans slide you're going to write a
<file> element, a <resimage> element and a <layer> element - and each
element will require a unique identifier. Here's a simple scheme easily
managing your identifiers:

- fileid='icons_f'
- resid='icons_r'
- layerid='icons_l'

By always using the character string "icons," it is easier to trace
your layer back to your resource or file, and vice-versa. By using an
underscore (_) you can double-click and copy the identifier and paste
it into an other element? By using a single letter at the end of the
identifier ('f' for fileid, 'r' for resid, etc.), it's easy to
appropriately rename your identifier for each element.


Check back here tomorrow for the Frogans Tip for Day -9!


Frogans-awards mailing list -
To Un/Subscribe:

<Previous message by date] [Next message by date>
<Previous message by thread] [Next message by thread>

Message thread:
  • [Frogans technology - Frogans-awards] Frogans Tip for Day -10, contact, [28-May-2016 11:50 UTC] <=

To subscribe to the Frogans technology mailing lists:

In these archives, strings in the format 'Anon_<number>' represent personal data that has been anonymized by request, in compliance with the OP3FT Privacy Policy