[Stormproject] pilot version

[Kuznetsov Alexey]

Skipped content of type multipart/alternative-------------- next part --------------
оПЕДКЮЦЮЕРЯЪ ЯКЕДСЧЫХИ ТНПЛЮР ГЮОХЯЕИ config-file:


<..>
	
	#comment for int
	INT_CONFIG_ENTRY_NAME 1000
	
	#comment for double
	DOUBLE_CONFIG_ENTRY_NAME 1.2 
	
	#comment for bool
	BOOL_CONFIG_ENTRY_NAME true\false
	
	
	#comment for Select, no '\n' in select config entry
	SELECT_CONFIG_ENTRY "String value with isolated \"`s "
	
	# Comments for string
	# No line breaks '\n' in string config entry!
	STRING_CONFIG_ENTRY "String value with isolated \"`s "
	
	#comment for LIST_CONFIG_ENTRY 
	LIST_CONFIG_ENTRY {"S1","S2","S3"}
	
	#alternative for LIST_CONFIG_ENTRY 
	LIST_CONFIG_ENTRY2 {
		"S1",
		"S2",
		"S3"
	}
	#be careful with separators: ' ', '\n', '\t'	
	
</..> <-???

оПЕДКЮЦЮЕРЯЪ ЯКЕДСЧЫХИ ТНПЛЮР ГЮОХЯЕИ description-file:

----------------------------------------------------------------- begin
# original comment, this comment will be stored in Server`s 
# DB automatically with entry type and config entry name
# [,] brackets means that default value is not required so, default
# value may be absent in real description file
# 
INT INT_CONFIG_ENTRY_NAME [1000]

# comment 
DOUBLE DOUBLE_CONFIG_ENTRY_NAME [1.2]

#Comment: Hello, "World" - value, but it is not required in description
STRING STRING_CONFIG_ENTRY_NAME ["Hello, \"World\""]

# Select config entry must have variants list as list of strings without '\n'`s
# Default value is not required, but in this example "ONE" - selected by default
SELECT SELECT_CONFIG_ENTRY_NAME ["\"ONE\""] {
 "\"ONE\"", 
 "\"TWO\"" 
}

# list of strings description: may have or may not have following initial list 
LIST LIST_CONFIG_ENTRY_NAME [{

    "\"ONE\"",
    "Hello, world"

}]
end -------------------------------------------------------------------