Quote from: rthrash at Dec 11, 2008, 06:46 AM
I think your assumptions are right Bob. And later we can take it one step further by making a handy little property set import/export button. It could generate or load an XML (or other format) config file that can be used to share settings more easily without having to go through the trials of building a full blown package.
That would great. It would allow developers to provide multiple configurations as appropriately named property set files in a package.
It might be really cool to save them in this format (or something similar):
$properties = array(
array(
'name'=>'errorsTo',
'desc'=>'Error reports will be emailed to this address if the appropriate options are set.',
'type'=>'textfield',
'options'=>'',
'value'=>'[email protected]'
),
array(
'name'=>'spformTpl',
'desc'=>'SPForm Template chunk name',
'type'=>'textfield',
'options'=>'',
'value'=>'spformTpl'
),
array(
'name'=>'spformprocTpl',
'desc'=>'SPFormproc Template chunk name',
'type'=>'textfield',
'options'=>'',
'value'=>'spformprocTpl'
)
}
It makes them nicely human-readable/editable and the properties could be set with something like:
require_once($props_file]);
$c->setProperties($properties, true);
