Project Template

[m-kuhn]

Things that need to be present in a project template:

• Relations
  • [x] Requires layer ids which are normally generated and not predictible (maybe assign static values in the template definition)
• Edit widgets
  • [x] Types
  • [x] Configuration
  • [x] Value relation widget configuration needs to be language aware
  • [x] Relation reference configuration depends on relations
• [x] Form layout
  • [x] Drag and drop tree
• [x] Field aliases (Translation)
• [x] Layer names (Translation)
• [x] Symbology
• [x] Labelling (Translated)
  • [ ] Multiple styles for a layer
• [x] Legend tree
  • [ ] Including layer set
  • [ ] Preserve layer order

Things to consider:

• It could be good to separate style from widgets

[m-kuhn]

I have done some quick tests.

• Exporting a layer file that can be loaded again (Independent from the project)
• Exporting the layer style file (containing style and edit widget definitions, aliases, still unified)
• Relations that reference the current layer

The good thing is, the XML can easily be altered as shown e.g. for the layer id which is updated to something easier usable.

https://gist.github.com/m-kuhn/5bed84dbfec7c84d6a07

[sjib]

What would need to be edited and kept up to date to maintain a German and French project version with the basic forms translated?

[m-kuhn]

Every change to the project would need to be manually added in two different projects. Translation would need to be done once (forms, layer names, aliases etc) but every addition functionality, style etc. would need to be done on different projects.

[sjib]

Any progress on this? Do we have the specifications we talked about in the last meeting

[m-kuhn]

80%

[sjib]

Discuss in Technical group meeting if this is still an issue - connect with new project file. May be the new plugin "Trackable QGIS Project" could also help on this