<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Beta</title><link>https://sourceforge.net/p/audiobackup/wiki/Beta/</link><description>Recent changes to Beta</description><atom:link href="https://sourceforge.net/p/audiobackup/wiki/Beta/feed" rel="self"/><language>en</language><lastBuildDate>Wed, 31 Aug 2011 13:12:23 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/audiobackup/wiki/Beta/feed" rel="self" type="application/rss+xml"/><item><title>WikiPage Beta modified by Andrew Hamlin</title><link>https://sourceforge.net/p/audiobackup/wiki/Beta/</link><description>&lt;pre&gt;--- v4 
+++ v5 
@@ -6,18 +6,24 @@
 1. Create XML configuration in AppData folder
 +  Store database in Documents folder (or customized location)
 +  Add Module Manifest file
-
++  Install to __Program Files (x86)__ directory
+
 Configuration will include:
 
 * [Service factory] type
     * Location of database file
 * Root location of audio files (single directory or multiple?)
 
 Module Manifest will include:
 
 * Required assembly references
 * Helper functions (exported)
 * [Beta API changes] to PS API
+
+Install to Program Files directory:
+
+* In order to simplify deployment and provide a GUI application, I am going to install the module to its own program files directory
+* A shortcut will load the module into its own PowerShell command prompt
 
 I do not plan to include help documentation. The PS syntax auto-generated by PowerShell v2 is sufficient for users familiar with PowerShell and I am not targeting others yet. Also, I need to take a look at generating the help documentation files.
 
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew Hamlin</dc:creator><pubDate>Wed, 31 Aug 2011 13:12:23 -0000</pubDate><guid>https://sourceforge.net1d456a11fdc827ad529e51145065165c336292a2</guid></item><item><title>WikiPage Beta modified by Andrew Hamlin</title><link>https://sourceforge.net/p/audiobackup/wiki/Beta/</link><description>&lt;pre&gt;--- v3 
+++ v4 
@@ -2,19 +2,23 @@
 ==============
 
 Changes:
- 1. Create XML configuration in AppData folder
- +  Store database in Documents folder (or customized location)
- +  Add Module Manifest file
-
+
+1. Create XML configuration in AppData folder
++  Store database in Documents folder (or customized location)
++  Add Module Manifest file
+
 Configuration will include:
- * location of database file
- * root location of audio files (single directory or multiple?)
+
+* [Service factory] type
+    * Location of database file
+* Root location of audio files (single directory or multiple?)
 
 Module Manifest will include:
- * required assembly references
- * helper functions (exported)
- * [Beta API changes] to PS API
+
+* Required assembly references
+* Helper functions (exported)
+* [Beta API changes] to PS API
 
 I do not plan to include help documentation. The PS syntax auto-generated by PowerShell v2 is sufficient for users familiar with PowerShell and I am not targeting others yet. Also, I need to take a look at generating the help documentation files.
 
-I do not plan to reimplement the underlying Cmdlet code that is in place. Currently, the alpha commands are implemented to directly call into the SQLite database. I don't see a reason to change that today. After the items above are into a Beta release then refactoring will be put on the roadmap. I need to decide some basic architectural things depending on how much effort I want to put into this balanced by how much fun I am having building it.
+I have decided to tackle adding a bit more abstraction to the underlying code than previously considered. Including the configuration of a type of [Service factory] gives me the ability to move in the future from a local database to a cloud-based service and does not significantly change the amount of work involved. The result will be something much more flexible, opening this up to more than just a Windows PowerShell client. I think that would be cool. Hey, I would like to run this on my [Ubuntu](http://www.ubuntu.com/ "Get Ubuntu") machine was well.
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew Hamlin</dc:creator><pubDate>Tue, 16 Aug 2011 13:25:11 -0000</pubDate><guid>https://sourceforge.netd8ddbaaf8358a45f6bdb134cc7526a121ee59043</guid></item><item><title>WikiPage Beta modified by Andrew Hamlin</title><link>https://sourceforge.net/p/audiobackup/wiki/Beta/</link><description>&lt;pre&gt;--- v2 
+++ v3 
@@ -13,7 +13,7 @@
 Module Manifest will include:
  * required assembly references
  * helper functions (exported)
- * [Changes] to PS API
+ * [Beta API changes] to PS API
 
 I do not plan to include help documentation. The PS syntax auto-generated by PowerShell v2 is sufficient for users familiar with PowerShell and I am not targeting others yet. Also, I need to take a look at generating the help documentation files.
 
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew Hamlin</dc:creator><pubDate>Tue, 16 Aug 2011 01:08:18 -0000</pubDate><guid>https://sourceforge.netf5863b27f26ca54f27f1bfd1a16c925e7457d7f4</guid></item><item><title>WikiPage Beta modified by Andrew Hamlin</title><link>https://sourceforge.net/p/audiobackup/wiki/Beta/</link><description>&lt;pre&gt;--- v1 
+++ v2 
@@ -13,6 +13,7 @@
 Module Manifest will include:
  * required assembly references
  * helper functions (exported)
+ * [Changes] to PS API
 
 I do not plan to include help documentation. The PS syntax auto-generated by PowerShell v2 is sufficient for users familiar with PowerShell and I am not targeting others yet. Also, I need to take a look at generating the help documentation files.
 
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew Hamlin</dc:creator><pubDate>Mon, 15 Aug 2011 19:55:12 -0000</pubDate><guid>https://sourceforge.neta9fe5d5d8554a687f9e8e41f077053f75fa705e8</guid></item><item><title>WikiPage Beta modified by Andrew Hamlin</title><link>https://sourceforge.net/p/audiobackup/wiki/Beta/</link><description>Beta Planning
==============

Changes:
 1. Create XML configuration in AppData folder
 +  Store database in Documents folder (or customized location)
 +  Add Module Manifest file

Configuration will include:
 * location of database file
 * root location of audio files (single directory or multiple?)

Module Manifest will include:
 * required assembly references
 * helper functions (exported)

I do not plan to include help documentation. The PS syntax auto-generated by PowerShell v2 is sufficient for users familiar with PowerShell and I am not targeting others yet. Also, I need to take a look at generating the help documentation files.

I do not plan to reimplement the underlying Cmdlet code that is in place. Currently, the alpha commands are implemented to directly call into the SQLite database. I don't see a reason to change that today. After the items above are into a Beta release then refactoring will be put on the roadmap. I need to decide some basic architectural things depending on how much effort I want to put into this balanced by how much fun I am having building it.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew Hamlin</dc:creator><pubDate>Sun, 07 Aug 2011 17:01:20 -0000</pubDate><guid>https://sourceforge.net28a9f3f1e3e4f07632fc594cf97bdad5ec8cca0f</guid></item></channel></rss>