On 12/15/2014 02:15 PM, Justin Luth wrote:
Debugging: How can you tell what your extension is doing? Nothing
warns you if you have a spelling mistake, invalid XML. There is zero
feedback anywhere - either you have it all right, or nothing happens.
The tragedy there is that the code reading
On 12/15/2014 03:48 PM, Justin Luth wrote:
-comparing before/after XML snapshots is not easy because XML keys can
move around a lot. xmldiff can't handle big files. (It was tedious
trying to isolate the settings I needed.)
IIRC, at least the order of items in registrymodifications.xcu
On 12/11/2014 08:26 PM, Justin Luth wrote:
By far, the best way to manage default settings is to write a
configuration extension. However, that is a HUGE, daunting step for
your average sysadmin to take. Documentation is sparse, debugging
ability is non-existent, and intimate knowledge of XML
On 2014-12-15 12:37 PM, Stephan Bergmann wrote:
An alternative would be to make it easier for the target audience to achieve
their goals with extensions. That could
include better documentation and examples. What were the problems you
encountered when trying it (what was your
co-workers
When my co-worker wrote the extension on Feb 4, he said: I think it
now meets the standards for writing an extension. But it was a long
hard path to get there: like stabbing in the dark. After much pain
and scant documentation, and a lot of trial and error (MOSTLY error) I
think it is working.
On 15/12/14 14:18, Noel Grandin wrote:
Perhaps we need an official, bundled (but off by default) extension
that performs this job?
An example extension won't be enough. However, a config builder tool
could do the job.
1.) Identifying the setting change difficulties:
-does a setting change
I am working on Bug 69609 - allowing /presets/registrymodification.xcu
to be incorporated into a new user profile. This would be a really easy
way for a system administrator to deliver a customized default
configuration to his users. A proposed patch has been added to the bug
report.
