I figured it was about time for a status update on this.

The concept is that HTCWizardWeb would maintain a central repository of registry tweaks for the HTCWizard and then users could select several and download a CAB file which would automatically import those settings into their registry.

• a basic webpage (it's ugly) which can insert XML into a database based on registry tweak information. (Read: you give basic registry info and it makes XML and puts it in a DB.)
• a php page that dynamically creates installable CAB files given the proper XML input.
• the beginnings of an admin page for approvals.

Whats left:

• add created_by_user to form that inserts XML into unapproved status.
• finish the approval page
  • include created_by_user in display of unapproved tweaks
  • include a test link to test tweaks individually without approving them.
  • finish the database updates to allow approval to work.
  • finish the database updates to allow delete to work.
• create user tweak_group admin page
• create tweak to tweak_group assignment page.
• create tweak_group download page.
• Make the whole thing pretty
• Wrap the thing in a Drupal module to get access to it's userids and integrate it into the site.

I feel like i'm missing some stuff from this TODO list, but I'll add to it later when i get a better idea of what's left.

The important thing is the hard work is done. It MAKES the XML puts it in a cab file, allows you to download it, AND can store XML in the DB. Now it's just a few database inserts, updates, deletes, and selects left. (plus the "make it pretty" part and the "make a Drupal module" part.)

The general idea was:

1. registry edits are irritating to perform manually
2. cab files are easy to install
3. cab files can be placed in the Extended ROM for restoration on Hard Reset
4. I shouldn't have to install LOTS of cab files to install multiple registry tweaks
5. We shouldn't have to store the cab files on the server for any long period of time - i.e. they should be dynamically created

The point was then raised that it would be nice to be able to track which ones you had installed already from the site.

We added the idea of user level groupings (so you could have more than one different sets of registry tweaks you could easily apply.)

This idea started in a blog post Stanley made here.

clafarge recommended that tweaks be verified before being available to the public. (He also suggested a better design for the tweak groups database structure.)

Rudy pointed me in the right direction for the dynamic building of the XML that goes in the CAB file.

CAB creation done by the PERL version of LCAB.

If i missed anybody please let me know.