First of all I should mention that Intramaps.Roam is a really cool piece of software.
I tested it for a tree inventory I set up for Oslo.
I started my work with a QGIS desktop project were I defined the relevant forms and form elements and added some python logic for validation and an auto completer for tree species names (n=270). QGIS Desktop forms were needed anyway, because the tree DB will also be used at the office.
Then I tried Intramaps.Roam and had to re-define all my form settings (which was quite some work). It would make the transition from QGIS to Roam much easier and increase the interoperability between QGIS and Roam, if Roam was able to import form definitions (as far as supported) from QGIS project files (or .qml)...
Meaning: widget types, ranges, true / false values for check boxes and so on.
Alias names are being read already, so it seems you are on that way!?
The funny thing is I did that when I first started Roam but it was easier to make my own widgets and config because it was faster to develop that way. Having it auto read and do a best fit would be pretty handy.
First of all I should mention that Intramaps.Roam is a really cool piece of software. I tested it for a tree inventory I set up for Oslo.
I started my work with a QGIS desktop project were I defined the relevant forms and form elements and added some python logic for validation and an auto completer for tree species names (n=270). QGIS Desktop forms were needed anyway, because the tree DB will also be used at the office. Then I tried Intramaps.Roam and had to re-define all my form settings (which was quite some work). It would make the transition from QGIS to Roam much easier and increase the interoperability between QGIS and Roam, if Roam was able to import form definitions (as far as supported) from QGIS project files (or .qml)... Meaning: widget types, ranges, true / false values for check boxes and so on.
Alias names are being read already, so it seems you are on that way!?