Frame Averager for MM 2.0

.gitignore

@@ -1,9 +1,10 @@
-/FrameAverager.1.4.18/build/
-/FrameAverager.1.4.16/build/
-/FrameAverager/build/
-.gitignore
-/FrameAverager/nbproject/private/
-/FrameAverager.1.4.16/nbproject/private/
-/FrameAverager.1.4.18/nbproject/private/
-/BitDepthDowngrader/nbproject/private/
-/BitDepthDowngrader/build/
+/FrameAverager.1.4.18/build/
+/FrameAverager.1.4.16/build/
+/FrameAverager/build/
+.gitignore
+/FrameAverager/nbproject/private/
+/FrameAverager.1.4.16/nbproject/private/
+/FrameAverager.1.4.18/nbproject/private/
+/BitDepthDowngrader/nbproject/private/
+/BitDepthDowngrader/build/
+FrameAverager.2.0/build/

FrameAverager.2.0/MANIFEST.MF

@@ -0,0 +1,9 @@
+Manifest-Version: 1.0
+Ant-Version: Apache Ant 1.9.7
+Created-By: 1.8.0_101-b13 (Oracle Corporation)
+Signature-Title: FrameAverager
+Signature-Vendor: Marine Biological Laboratory (Rudolf Oldenbourg)
+Application-Plugin: Micro-Manager
+Built-By: Nick
+Built-Date: 08-19-2018
+

FrameAverager.2.0/build.xml

@@ -0,0 +1,101 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- You may freely edit this file. See commented blocks below for -->
+<!-- some examples of how to customize the build. -->
+<!-- (If you delete it and reopen the project it will be recreated.) -->
+<!-- By default, only the Clean and Build commands use this build script. -->
+<!-- Commands such as Run, Debug, and Test only use this build script if -->
+<!-- the Compile on Save feature is turned off for the project. -->
+<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
+<!-- in the project's Project Properties dialog box.-->
+<project name="FrameAverager" default="default" basedir=".">
+    <description>Builds, tests, and runs the project FrameAverager</description>
+    <import file="nbproject/build-impl.xml"/>
+    <!--
+
+    There exist several targets which are by default empty and which can be 
+    used for execution of your tasks. These targets are usually executed 
+    before and after some main targets. They are: 
+
+      -pre-init:                 called before initialization of project properties
+      -post-init:                called after initialization of project properties
+      -pre-compile:              called before javac compilation
+      -post-compile:             called after javac compilation
+      -pre-compile-single:       called before javac compilation of single file
+      -post-compile-single:      called after javac compilation of single file
+      -pre-compile-test:         called before javac compilation of JUnit tests
+      -post-compile-test:        called after javac compilation of JUnit tests
+      -pre-compile-test-single:  called before javac compilation of single JUnit test
+      -post-compile-test-single: called after javac compilation of single JUunit test
+      -pre-jar:                  called before JAR building
+      -post-jar:                 called after JAR building
+      -post-clean:               called after cleaning build products
+
+    (Targets beginning with '-' are not intended to be called on their own.)
+
+    Example of inserting an obfuscator after compilation could look like this:
+
+        <target name="-post-compile">
+            <obfuscate>
+                <fileset dir="${build.classes.dir}"/>
+            </obfuscate>
+        </target>
+
+    For list of available properties check the imported 
+    nbproject/build-impl.xml file. 
+
+
+    Another way to customize the build is by overriding existing main targets.
+    The targets of interest are: 
+
+      -init-macrodef-javac:     defines macro for javac compilation
+      -init-macrodef-junit:     defines macro for junit execution
+      -init-macrodef-debug:     defines macro for class debugging
+      -init-macrodef-java:      defines macro for class execution
+      -do-jar-with-manifest:    JAR building (if you are using a manifest)
+      -do-jar-without-manifest: JAR building (if you are not using a manifest)
+      run:                      execution of project 
+      -javadoc-build:           Javadoc generation
+      test-report:              JUnit report generation
+
+    An example of overriding the target for project execution could look like this:
+
+        <target name="run" depends="imgavgMmgr-impl.jar">
+            <exec dir="bin" executable="launcher.exe">
+                <arg file="${dist.jar}"/>
+            </exec>
+        </target>
+
+    Notice that the overridden target depends on the jar target and not only on 
+    the compile target as the regular run target does. Again, for a list of available 
+    properties which you can use, check the target you are overriding in the
+    nbproject/build-impl.xml file. 
+
+    -->
+    <tstamp>
+    <format property="TODAY" pattern="MM-dd-yyyy" />
+    </tstamp>
+
+    <!--
+    <loadfile property="Version_Major" srcfile="..\..\PolScopeAPI\PsPluginsAppApi\src\edu\mbl\cdp\ps\Version_Major.txt"/>
+    <loadfile property="Version_Minor" srcfile="..\..\PolScopeAPI\PsPluginsAppApi\src\edu\mbl\cdp\ps\Version_Minor.txt"/>
+    <loadfile property="Version_Type" srcfile="..\..\PolScopeAPI\PsPluginsAppApi\src\edu\mbl\cdp\ps\Version_Type.txt"/>
+    -->
+
+    <manifest file="MANIFEST.MF">
+    <attribute name="Signature-Title" value="FrameAverager"/>
+    <attribute name="Signature-Vendor" value="Marine Biological Laboratory (Rudolf Oldenbourg)"/>
+    <attribute name="Application-Plugin" value="Micro-Manager"/>
+    <attribute name="Built-By" value="${user.name}"/>
+    <!--<attribute name="Built-Version" value="${Version_Major}.${Version_Minor}${Version_Type}"/>-->
+    <attribute name="Built-Date" value="${TODAY}"/>
+    </manifest>
+
+<target name="-post-jar">  
+  <property name="MMPlugin_dist1" value="dist/FrameAverager.jar"/>
+  <property name="MMPlugin_dir1" value="${work.dir}/mmplugins/FrameAverager.jar"/>
+  <copy tofile="${MMPlugin_dir1}">
+  <fileset file="${MMPlugin_dist1}"/>
+  </copy>
+</target> 
+
+</project>

FrameAverager.2.0/doc/ReadMe.txt

@@ -0,0 +1,7 @@
+FrameAverager Plugin for MicroManager
+by Amitabh Verma & Grant Harris
+Marine Biological Laboratory, 2012
+
+
+Please refer to:
+http://www.openpolscope.org/pages/MMPlugin_Frame_Averager.htm