|Version 5 (modified by 13 years ago) ( diff ),|
Update: This may not be necessary for GIS
,52 has a rewritten approach to Layers where
'gis_layer_%s' % type are SQLTables (inheriting from a base set) which we can use
- this seems to give us most (all?) of the benefits below.
However I think that PERSON won't be solvable in the same way :/
The GIS module may benefit from writing a LAYER class.
Layer Types would extend this base class.
Each Layer Type would be a single Table & hence could use the standard RESTlike controller.
This should ease maintenance compared to the current process.
Have the Map Service Catalogue have a tab per Type(*).
Each has its own self-processing SQLFORM (generated by T2)
(This would make it like S2, which works well)
This gives us better control of the display order for Layers & better modularity of Layer-processing JS code (1 file per layer type).
- Alternatives could be collapsible sections (like appadmin) or submenus on left-hand navigation.
Objects contain both data and functionality together.
A Class in essence defines a new data type.
=> The Class is not the Controller alone, but the Resource (including Controller)
=> Each Resource type should extend a base Resource (which extends...?)
Currently our resources are defined in the model & hence of type gluon.sql.SQLTable (inc SQLFields)
NB A similar solution probably applies for 'PERSON' as well.