This file describes some issues that should be implemented in future and how it should be implemented. 
Note: it should be implemented exactly how it described below, because another parts of system can rely on it.

1) QDateField.
QDateField metadata should contain the following fields:
	a) Time zone in integer format (GTM shift). This field should be taken from the customer properties located on server.
	b) Date format pattern. This pattern should be accepted on both, server and client sides. On server side it should be accepted by 
		java.text.SimpleDateFormat. On the client side should be implemented simple date formatter, that will accept it.
QDateField data should contain java.util.Date object. This object should represent the time value for the Time zone, presented in metadata.

2) QListBox.
QListBox component can have 2 states witch is determined by attribute "use-cache" in "efield" element in entity description xml file. 
	a) If "use-cache" attribute is "true" QListBox component should contain elements that was loaded in metadata, it happens at ones 
		in session, when client loads metadata. 
	b) If "use-cache" attribute is "false" QListBox component should fire special event "GetMoreDataEvent" (will be implemented 
		in near future) and wait for a list of available items to be shown in list. That action should be called each time, when
		customer tries to drop down the list of items.

3) Enhancement for QForm component.
QFormController external interface should be extended with "FieldData[] getUpdatedFieldsOnly()". It should returns fields array, that should
contain only fields, that was externally changed by actor (can be both, system or user) since form was turn to "New" or "Update" states. If a
form is not in "New" or "Update" states it should return empty array (not null).

4) Reports are stored in another way. (save/load report in Adhoc Report Frame)
Queplix 3.0 stores reports like serialized array of ReportElement instead of xml representation of class Reqs (Queplix 2.6).