18 lines
1.8 KiB
Plaintext
18 lines
1.8 KiB
Plaintext
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fcharset0 Arial;}{\f1\fnil\fcharset2 Symbol;}}
|
||
{\colortbl ;\red0\green0\blue0;}
|
||
\viewkind4\uc1\pard\fi-1800\li1800\tx1800\cf1\b\f0\fs20 From:\b0\tab Weiru Cai\par
|
||
\b Sent:\b0\tab Monday, January 10, 2000 4:52 PM\par
|
||
\b To:\b0\tab Alex Armanasu\par
|
||
\b Subject:\b0\tab Meeting notes for 12/22/1999\par
|
||
\pard\cf0 Attendee:\tab John, Delo, Weiru\par
|
||
\par
|
||
\pard{\pntext\f1\'B7\tab}{\*\pn\pnlvlblt\pnf1\pnindent0{\pntxtb\'B7}}\fi-380\li380 XML files are easy to transport, which is why it's chosen for manifests.\par
|
||
{\pntext\f1\'B7\tab}But XML files are text files which are slow to process, so they got compiled into a binary file format before they get processed.\par
|
||
{\pntext\f1\'B7\tab}Two more features to support:\par
|
||
\pard{\pntext\f1\'B7\tab}{\*\pn\pnlvlblt\pnf1\pnindent0{\pntxtb\'B7}}\fi-380\li760 Identify lists in registry. We can identify some or all the candidates using heuristic search methods, and ask the user to validate them.\par
|
||
{\pntext\f1\'B7\tab}Identify paths. Also we can identify some or all the candidates, and ask the user to validate them.\par
|
||
\pard{\pntext\f1\'B7\tab}{\*\pn\pnlvlblt\pnf1\pnindent0{\pntxtb\'B7}}\fi-380\li380 We should specify handler for each group of settings (inf files, registry settings, etc.) in the manifest we generate. We can get this information from some "guessing" and from the user. Currently handlers already exist for inf files, files, and registry settings. I can use them also to generate manifest (iterate through the registry, extracting information from the inf file, etc.)\par
|
||
{\pntext\f1\'B7\tab}Existing handlers don't tell me the type of the data. I have to figure out the data type for each setting and keep that information in the manifest.\par
|
||
\pard\fi-1800\li1800\tx1800\cf1\par
|
||
}
|
||
|