Webtags (preserving history): Difference between revisions

Webtags (preserving history) (view source)

Revision as of 09:24, 22 March 2020

672 bytes added , 09:24, 22 March 2020

m

→‎Differences between Cumulus 1 and Cumulus MX (Cumulus 3):

Sfws

5,838

edits

@@ Line 77: / Line 77: @@
 == Differences between Cumulus 1 and Cumulus MX (Cumulus 3): ==
-*Cumulus MX uses the .NET date and time format characters that are not exactly the same as the Delphi ones that Cumulus 1 uses.  For Cumulus MX see [http://msdn.microsoft.com/en-us/library/8kb3ddd4(v=vs.110).aspx this Microsoft site] for format selectors. The differences come about because Delphi is case-insensitive, and .Net is case sensitive, so .Net can use upper and lower case for different items, where Delphi has to use different letters.
+All web tag_names are identical in both flavours, but not all web tags are available in both. All input parameters are the same (see [[#Recent_History|Recent History]]), but output parameters do vary between Cumulus 1 and MX.
-*#For example, in Delphi, "nn" means "minutes" for Cumulus 1, but "minutes" is "mm" for .Net in Cumulus MX.
+=== Output (format modifier) parameters for decimal places ===
-*# e.g. the hour in 24-hour format, is "hh" (although 'HH' would be treated same) in Delphi (Cumulus 1) and in .Net it must be "HH" (Cumulus MX).
+"dp=" is used for both Cumulus 1 and MX.
-*You might be put off by references for .Net (Cumulus MX) to single/standard characters and custom modifiers:
+=== Output (format modifier) parameters for times and dates ===
+*Cumulus MX (when running on Windows) uses the '''.NET''' date and time format characters that are not exactly the same as the '''Delphi''' ones that Cumulus 1 uses.  For Cumulus MX see [http://msdn.microsoft.com/en-us/library/8kb3ddd4(v=vs.110).aspx this Microsoft site] for format selectors. The differences come about because Delphi is case-insensitive, and .Net is case sensitive, so .Net can use upper and lower case for different items, where Delphi has to use different letters. If Cumulus MX is running on Linux or Mac OS X, then it uses '''Mono''' for date and time formatting, but the same case sensitive rules apply as for .NET.
+*#For example,[[File:badge v1.png]] in Delphi, "nn" means "minutes" for Cumulus 1, [[File:Badge vMx.png]]but "minutes" is "mm" for .Net in Cumulus MX.
+*# e.g. the hour in 24-hour format, is "HH" (although in Delphi (Cumulus 1)'hh' would be treated same) but in .NET it must be "HH" (Cumulus MX).
+*[[File:Badge vMx.png]]You might be put off by references within .NET (Cumulus MX) to single/standard characters and custom modifiers, the following 3 examples may add clarity:
 *#For example ''<#MonthTempHD format="d">'' is a single character format modifier, therefore the 'd' acts as a standard modifier, and causes a date of 22 July 2014 for the highest temperature in the month to be returned in the standard short date format e.g. '22/07/2014' (exact contents for any one date vary by locale).
 *#Similarly ''<#MonthTempHD format="M">'' is a single character format modifier and therefore the 'M' acts as a standard modifier and causes the date for the highest temperature in the month to be returned in the standard day and month format e.g. '22 July' (exact contents for any one date vary by locale).
@@ Line 87: / Line 93: @@
 For official full details see [https://cumulus.hosiene.co.uk/viewtopic.php?f=27&t=12908 Cumulus MX forum], the following table is revised for simplicity. (I've abridged the table here and included '%' where necessary to avoid single character versus custom complications).
-=== List of allowed output parameter format modifiers ===
+=== List of allowed modifiers ===
 Note for Cumulus 1 - where lower (or upper, for easier comparison with MX) case shown, because Delphi is case insensitive, upper (or lower) case (in some cases, indicated by use of italics in brackets) could be used instead (exceptions: a/p, ampm, am/pm, Am/Pm, AM/PM, A/P, AMPM etc display as input)
 {| class="wikitable" border="1"