Changeset 7933 for main/waeup.kofa/trunk/src/waeup/kofa/utils
- Timestamp:
- 21 Mar 2012, 13:42:00 (13 years ago)
- Location:
- main/waeup.kofa/trunk/src/waeup/kofa/utils
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
main/waeup.kofa/trunk/src/waeup/kofa/utils/batching.py
r7907 r7933 44 44 45 45 # Name used in pages and forms... 46 name = u'Non-registered base importer'46 name = u'Non-registered base processor' 47 47 48 48 # Internal name... 49 util_name = 'base importer'49 util_name = 'baseprocessor' 50 50 51 51 # Items for this processor need an interface with zope.schema fields. -
main/waeup.kofa/trunk/src/waeup/kofa/utils/batching.txt
r7811 r7933 10 10 mass-remove, or mass-update data. 11 11 12 So you can feed CSV files to importers orprocessors, that are part of12 So you can feed CSV files to processors, that are part of 13 13 the batch-processing mechanism. 14 14 15 Importers/Processors16 ---------- ----------15 Processors 16 ---------- 17 17 18 18 Each CSV file processor -
main/waeup.kofa/trunk/src/waeup/kofa/utils/helpers.py
r7819 r7933 152 152 153 153 In :mod:`waeup.kofa` we use factories extensively for 154 batching. While processing a batch some importerlooks up a154 batching. While processing a batch some processors looks up a 155 155 factory to create real-world instances that then get filled with 156 156 data from imported CSV files. … … 192 192 True 193 193 194 After grokking we (and importers) can create objects without194 After grokking we (and processors) can create objects without 195 195 knowing about the location of the real class definition, just by 196 196 the factory name:
Note: See TracChangeset for help on using the changeset viewer.