Milestones

My main idea was to start with relatively small and easy milestones working toward the initial release: breaking up large complicated pieces of work into smaller, workable chunks I might actually be able to accomplish.

  • Learn some rudimentary VBScript specifically related to the Document Object Model of Internet Explorer (completed)
    • Create form text fields, the values of which are tied to pushing a button (event) (completed)
    • Dynamically add rows and cells to a table containing the values of the next fields from the form (completed)
  • Establish “working directory” while editing records prior to windows install and the location of all the applications during the Windows install
    • perhaps build in a further customization for installing from a network location or running a script to copy over a folder hierarchy from a network location
  • Find way of tracking different categories of applications
    • like utilities, internet, runtimes/codecs, windows updates, media, reg entries etc.
    • add a way of adding custom categories, perhaps tracking them separately in a text file or separate XML file(?)
  • Add an edit button to the end of each table row as an “edit” feature for changing the values
    • Upon clicking edit the read-only values of the table row will switch to a text fields with the same value entered. When done editing a Save button will switch the text field back to a read-only table cell with the new value
    • Edit button will switch captions to “save” while the record is editable. Upon clicking save the button will say Edit again
    • May very well find a different way of modifying existing records
  • Add check box to the end of each row to indicate this item will be installed or passed over during XML parsing/execution
    • this will be an attribute for each item record in the XML file (install=0 or install=1)
  • XML
    • come up with a standard XML markup for each application
    • Saving contents of table to an XML file, use a default file name (applist.xml or something)
    • function for loading a different XML in particular with a standard open file dialog box
    • if applist.xml is found in the “current directory” with the HTA then load this by default
    • functionality for saving current application list as a different XML name
    • add a “run currently loaded XML” type button to execute the listed applications that are flagged for install
    • add “profile” field to the XML to save a set of applications to install as a specific name
  • Different ways of adding records to XML database list
    • manually entering each one-by-one
    • scanning existing folder hierarchy adding each one
    • perhaps a text file in each application folder that specifies the the name of the installer along with the desired silent install command line options

Really long term goals…

  • Establish large database of application names along with associated silent install parameters
    • check several different sources online for working silent install options
    • Perhaps sample *.ins and *.mst files
    • perhaps a “get this file” type feature, apt-get style, for auto-downloading applications
    • a way of customizing auto-downloading of different applications
    • Store application names and associated install parameters in local XML file,  synchronize this with online version
  • Add update feature for application that synchronizes local copy with “official” copy hosted at web site
  • Make interface highly “skinnable” and other-wise customizable

 

No Comments »

Leave a Reply