search

UIKit0 / freemedforms

Automatically exported from code.google.com/p/freemedforms
Other
0 stars 0 forks source link

FormItem mechanism #321

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
This is not optimal, we should think about something to replace this 
representation.

Whatever, when deleting m_FormWidget in the FormItemPrivate -> segfault. Why ?

Original issue reported on code.google.com by eric.mae...@gmail.com on 7 May 2013 at 3:16

GoogleCodeExporter commented 9 years ago 
I never really could wrap my brains around this stuff.
But before we redesign the process within the formitem etc., we could think 
about QtQuick forms, now we have Qt5 ready.

It would be a possibility to use QML as description language for the forms.
benefit:
* no xml etc parsing, just qml
* included JavaScript for inter-form-calculations (etc. weight, length ->BMI) - 
the current QtScript is buggy, intransparent, in another file (needs sync etc)
* form creation with QtCreator, maybe with designer, if needed
* FMF qml components could be written in C++ and completely configureable
* easy migrating of forms to a mobile device. Ubuntu Touch, Meego, Android, 
Blackberry10, iDevices.

This is a mid-term aim, but I think before putting much work into FormItem 
stuff, a redesign would be an option.

Original comment by christian.a.reiter@gmail.com on 7 May 2013 at 5:00