Difference between revisions of "UserDoc2.0"
(→Syntax) |
(→Syntax) |
||
Line 69: | Line 69: | ||
z time zone (Text) Pacific Standard Time | z time zone (Text) Pacific Standard Time | ||
' escape for text (Delimiter) | ' escape for text (Delimiter) | ||
− | ' | + | ' single quote (Literal) ' |
Revision as of 13:51, 12 October 2008
Contents
Browser
OpenFlyers (OF) is designed to work with Firefox 2 or 3 (FF) and Internet Explorer 7 (IE).
Flight
Flight form
Checking process
After you have filled flight form, OpenFlyers checks following things:
- There is no uncompatibility between flight types
- There is no uncompatibility between a flight type and aircraft type
- Required flight types according to the aircraft type have been correctly set
- Required flight type in case of a second pilot on board have been correctly set
Additionnaly, if the club administrator has activated the option, OpenFlyers checks that the pilot has got:
- right qualifications according to the aicraft type
- right qualifications according to the flight types
Validation
For flight and account, an entry (flight entry or account entry) may have two states:
- not validated
- validated
When an entry is validated, it is no more longer possible to modify it
So, it's important to check accuracy of the entry before validating it
If after validation, an error is detected, for flight you can't do anything, for account, you can add an entry to counterbalance the mistake.
Validation process
Flight
When a flight is entered, it is not validated. There is two alternatives configuration to validate a flight:
- automatic validation: a flight is automatically validated when a new flight (which begin after the previous one) on the same aircraft is entered
- manual validation: a mechanical (for example) check manually the flights according to the aircraft log book and validate flights with a formular.
Account
- Account entries which are consequence of a flight are validated as soon as the corresponding flight is validated
- Transfer are always validated
- Other entries (payments) are manually checked to be validated
Display
A not validated entry is displayed in italic characters.
Modification
A non validated entry may be modified
Account
listing
Warning: flights with no debit are not displayed in the account listing
Display personalization
Users may personalize their display in the menu "Data/Display and personal data"
Date and time format
Date and time format have to set in the "Date format pattern" field and in the "Time format pattern" field of the "Display options" form.
Syntax
To specify the format use a pattern string. In this pattern, all ASCII letters are reserved as pattern letters, which are defined as the following:
Symbol Meaning Presentation Example ------ ------- ------------ ------- G era designator (Text) AD y year (Number) 1996 M month in year (Text & Number) July & 07 d day in month (Number) 10 h hour in am/pm (1~12) (Number) 12 H hour in day (0~23) (Number) 0 m minute in hour (Number) 30 s second in minute (Number) 55 S millisecond (Number) 978 E day in week (Text) Tuesday D day in year (Number) 189 F day of week in month (Number) 2 (2nd Wed in July) w week in year (Number) 27 W week in month (Number) 2 a am/pm marker (Text) PM k hour in day (1~24) (Number) 24 K hour in am/pm (0~11) (Number) 0 z time zone (Text) Pacific Standard Time ' escape for text (Delimiter) ' single quote (Literal) '
The count of pattern letters determine the format.
(Text): 4 or more pattern letters--use full form, < 4--use short or abbreviated form if one exists.
(Number): the minimum number of digits. Shorter numbers are zero-padded to this amount. Year is handled specially; that is, if the count of 'y' is 2, the Year will be truncated to 2 digits.
(Text & Number): 3 or over, use text, otherwise use number.
Any characters in the pattern that are not in the ranges of ['a'..'z'] and ['A'..'Z'] will be treated as quoted text. For instance, characters like ':', '.', ' ', '#' and '@' will appear in the resulting time text even they are not embraced within single quotes.
A pattern containing any invalid pattern letter will result in a thrown exception during formatting or parsing.
Examples Using the US Locale:
Format Pattern Result -------------- ------- "yyyy.MM.dd G 'at' hh:mm:ss z" ->> 1996.07.10 AD at 15:08:56 PDT "EEE, MMM d, yy" ->> Wed, July 10, '96 "h:mm a" ->> 12:08 PM "hh 'oclock' a, zzzz" ->> 12 o'clock PM, Pacific Daylight Time "K:mm a, z" ->> 0:00 PM, PST "yyyyy.MMMMM.dd GGG hh:mm aaa" ->> 1996.July.10 AD 12:08 PM