Changeset 2191
- Timestamp:
- 2006-03-15 20:49:15 (3 years ago)
- Files:
-
- AnnodexFirefoxExtension/trunk/Docs/DevDoc_MediaEngine.html (modified) (7 diffs)
- AnnodexFirefoxExtension/trunk/Docs/DevDoc_XULCore.html (modified) (4 diffs)
- AnnodexFirefoxExtension/trunk/Docs/Release_Notes.html (modified) (1 diff)
- AnnodexFirefoxExtension/trunk/Installer/WinSetup.bat (modified) (1 diff)
- AnnodexFirefoxExtension/trunk/LICENSE.txt (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
AnnodexFirefoxExtension/trunk/Docs/DevDoc_MediaEngine.html
r2188 r2191 44 44 </tr> 45 45 <tr> 46 <td width="100%"> 47 <a href="#2.2_ME_Code_Structure_&_Functionality">2.2 Media Engine Code 48 Structure & Functionality</a></td> 46 <td width="100%"> <a href="#2.2_ME_Directory_Structure">2.2 Media Engine 47 Directory Structure</a></td> 49 48 </tr> 50 49 </table> … … 115 114 116 115 <p>The chrome and media engine are packaged as separate .XPIs. While the chrome 117 is the same on all platforms, a different video plug in is required for each116 is the same on all platforms, a different video plug-in is required for each 118 117 operating system and CPU architecture. The two main components to AFE are as 119 118 follows:</p> … … 128 127 display. The chrome is platform-independent, and it registers itself with 129 128 Mozilla as the handler for application/x-annodex, and it embeds the video 130 plug in. The AFE Chrome also handles the parsing of CMML metadata and clip129 plug-in. The AFE Chrome also handles the parsing of CMML metadata and clip 131 130 information implementing JavaScript's XML to RDF parser functions.<br> 132 131 </li> 133 132 <li><b>Media Engine</b><br> 134 The media engine is a Mozilla plug in used to do the playback and rendering of135 the audio or video. Currently, we use the VLC Mozilla plug in as the media133 The media engine is a Mozilla plug-in used to do the playback and rendering of 134 the audio or video. Currently, we use the VLC Mozilla plug-in as the media 136 135 engine on all platforms, though this may change in the future. The video 137 plug in is native code specific for each of the supported platforms on Windows,136 plug-in is native code specific for each of the supported platforms on Windows, 138 137 Linux (x86 and PowerPC) and MacOS. Each media engine registers with Mozilla as 139 an application/x-annodex-player plug in; e.g. the VLC media engine is138 an application/x-annodex-player plug-in; e.g. the VLC media engine is 140 139 registered as application/x-annodex-vlc-viewer-plugin.</li> 141 140 </ol> … … 145 144 146 145 147 <p>A "media engine" is a Mozilla plug in which is responsible for the actual146 <p>A "media engine" is a Mozilla plug-in which is responsible for the actual 148 147 playback of the video or audio file. Currently, VLC is used on all three 149 148 supported platforms (Windows, Linux, Mac OS X) as the media engine. You will 150 need to compile a customised VLC Mozilla plug in to get the Firefox extension to149 need to compile a customised VLC Mozilla plug-in to get the Firefox extension to 151 150 work correctly. Without a media engine, you can download and view the CMML 152 151 content in the Table of Contents list for the video (as this is handled by the … … 164 163 </li> 165 164 <li>The Gecko (Mozilla) SDK, which includes some header files and utility 166 programs required for the building the VLC Mozilla plug in. The Gecko SDK is165 programs required for the building the VLC Mozilla plug-in. The Gecko SDK is 167 166 common to all the media engines, which contain Mozilla header files and 168 167 tools that the plug-ins will require to compile correctly:<br> … … 195 194 <br> 196 195 See the toplevel README.txt file (the one in the main AnnodexFirefoxExtension/ 197 directory) for more information, including how to package the built plug in196 directory) for more information, including how to package the built plug-in 198 197 into an XPI.<br> 199 198 <br> … … 209 208 provide prebuilt Gecko SDK binaries for those platforms for you.</p> 210 209 <ul> 211 <li>For Windows, the Gecko SDK is expected to be in a gecko-sdk-win32/ 212 directory. To get the prebuilt Win32 binaries, svn checkout the following 213 path:<br><br>http://svn.annodex.net/AnnodexFirefoxExtension/Extras/gecko-sdk-1.4-win32/<br> 214 <br>to gecko-sdk-win32/. For convenience, you can also use the 215 checkout-gecko-sdk-win32.bat batch to do this if you have the command-line 216 Subversion MSI (not TortoiseSVN) installed.<br> </li> 217 <li>For Mac OS X, use the following Subversion URL instead:<br><br>http://svn.annodex.net/AnnodexFirefoxExtension/Extras/gecko-sdk-1.7-macosx/<br> 218 <br>and check it out to ../gecko-sdk-macosx/. For convenience, you can use 219 the checkout-gecko-sdk-macosx.sh shell script to do this.</li> 210 <li><b>For Windows:</b><br> 211 The Gecko SDK is expected to be in a <font face="Courier New">gecko-sdk-win32/</font> 212 directory. To get the prebuilt Win32 binaries, SubVersion checkout the following 213 path below to <font face="Courier New">gecko-sdk-win32/</font>. For convenience, you can also use the 214 <font face="Courier New">checkout-gecko-sdk-win32.bat</font> batch to do this if you have the command-line 215 Subversion MSI (not TortoiseSVN Explorer Shell) installed:<br><br> 216 <a href="http://svn.annodex.net/AnnodexFirefoxExtension/Extras/gecko-sdk-1.4-win32/">http://svn.annodex.net/AnnodexFirefoxExtension/Extras/gecko-sdk-1.4-win32/</a><br> 217 </li> 218 <li>For Mac OS X:<br> 219 use the following Subversion URL instead and check it out to 220 <font face="Courier New">../gecko-sdk-macosx/</font>.<br><br> 221 <a href="http://svn.annodex.net/AnnodexFirefoxExtension/Extras/gecko-sdk-1.7-macosx/">http://svn.annodex.net/AnnodexFirefoxExtension/Extras/gecko-sdk-1.7-macosx/</a><br> 222 <br> 223 For convenience, you can use the checkout-gecko-sdk-macosx.sh shell script 224 to do this, as the script contains the following commands below:<br> 225 <br> 226 <font face="Courier New">cd MediaEngine/VLC<br>./Patch<br>cd build<br>./Build<br>cd ..<br>./PrepareInstall.sh</font></li> 220 227 </ul> 221 <blockquote>222 <p>cd MediaEngine/VLC<br>./Patch<br>cd build<br>./Build<br>cd ..<br>./PrepareInstall.sh</p>223 </blockquote>224 228 <p>These steps will patch and build the VLC media engine, and put the needed 225 files into bin-macosx, bin-win32, bin-linux-i386, or bin-linux-ppc, depending on 226 the host machine. (Note to propellerheads: cross-compiling is not currently 227 possible. Feel free to submit a patch to enable this functionality if you like!) 228 The Installer/Make{Linux,MacOSX,Windows}VLCPluginXPI.sh scripts will take the 229 files from MediaEngine/VLC/bin-etc and package them into an .XPI, which is 229 files into <font face="Courier New">/bin-macosx</font>, <font face="Courier New"> 230 /bin-win32</font>, <font face="Courier New">/bin-linux-i386</font>, or 231 <font face="Courier New">/bin-linux-ppc</font>, depending on the host machine. 232 The Installer/Make (For Linux, MacOS X and Windows platforms) 233 <font face="Courier New">VLCPluginXPI.sh</font> scripts will take the 234 files from <font face="Courier New">/MediaEngine/VLC/bin-etc</font> and package them into an .XPI, which is 230 235 placed into the Installer directory. After making the XPIs using the scripts in 231 the Installer directory, run Firefox and open the Installer/installtest.html 232 file to test out whether your XPIs work.</p> 236 the Installer directory, run Firefox and open the <font face="Courier New">/Installer/installtest.html</font> 237 file to test out whether the XPI's are detected correctly by Mozilla as Annodex 238 extensions.<br> 239 <br> 240 <b>Note:</b> Cross-compiling is not currently possible. This functionality is 241 considered desirable, but not essential during the beta development of the 242 Annodex Firefox Plug-in.</p> 233 243 <h4><a name="2.1.2_Compiling_VLC_on_Linux">2.1.2 Compiling VLC on Linux</a></h4> 234 <p>There are a few extra complications trying to compile the VLC Mozilla plug in244 <p>There are a few extra complications trying to compile the VLC Mozilla plug-in 235 245 on Linux:</p> 236 246 <ol> 237 247 <li>As mentioned above, ensure that you only have static libraries of 238 lib {ogg,theora,vorbis,speex}available, otherwise the end-user will require239 them to be installed. <br>240 For package maintainers, it 's fine (and much more sensible)to simply link248 lib (ogg, theora, vorbis, speex) available, otherwise the end-user will require 249 them to be installed. 250 For package maintainers, it is fine to simply link 241 251 against your distribution's packages rather than statically compiling them 242 252 in.<br> 243 253 </li> 244 <li>You may need to adjust the mozilla-configscript so that the Mozilla245 plugin doesn't unnecessarily link against lib{plds4,plc4,nspr4,xpcom}. These246 are Mozilla libraries that the VLC Mozilla plug in doesn't need to link to at254 <li>You may need to adjust the<font face="Courier New"> mozilla-config</font> script so that the Mozilla 255 plug-in doesn't unnecessarily link against lib (plds4, plc4, nspr4, xpcom). These 256 are Mozilla libraries that the VLC Mozilla plug-in doesn't need to link to at 247 257 all, and causes problems because almost all end-users won't have those 248 258 libraries installed in the locations you have them installed in.<br> 249 259 <br> 250 For example, on Debian GNU/Linux, Mozilla Firefox uses libplds4.so located 251 at /usr/lib/mozilla-firefox/, but the mozilla-dev package installs a 252 separate libplds4.so to /usr/lib/. When the VLC Mozilla plugin is compiled, 253 it will link against the library found at /usr/lib/ -- meaning that 254 end-users who don't have themozilla-dev package installed (i.e. most of 255 them) will not be able to load the plugin on their system properly, due to 260 <b>For example: </b>on Debian GNU/Linux, Mozilla Firefox uses libplds4.so 261 that is located 262 at <font face="Courier New">/usr/lib/mozilla-firefox/</font>, but the mozilla-dev package installs a 263 separate libplds4.so to <font face="Courier New">/usr/lib/</font>. When the VLC Mozilla 264 plug-in is compiled, 265 it will link against the library found at <font face="Courier New">/usr/lib/</font>. 266 This means that 267 end-users who don't have themozilla-dev package installed (this is not a 268 default package on most systems) will not be able to load the plug-in on their system properly, due to 256 269 the dynamic linker throwing an error.<br> 257 270 <br> 258 Package maintainers can choose of two options here: the better one is 259 probably to somehow patch the vlc-config or mozilla-config scripts so that "vlc-config 271 Package maintainers can choose of two options here<ul> 272 <li>The better one option is 273 to probably somehow patch the vlc-config or mozilla-config scripts so that "vlc-config 260 274 --libs mozilla" doesn't produce the -l flags to link against those 261 libraries. Otherwise, you can simply depend on whatever Mozilla development 275 libraries.</li> 276 <li>Otherwise, you can simply depend on whatever Mozilla development 262 277 package is in your distribution (mozilla-dev) to ensure that those libraries 263 278 are installed.<br> 264 279 </li> 280 </ul> 281 </li> 265 282 <li>Be aware that if you are building an XPI intended to work across 266 283 different distributions, you will want to statically link in libstdc++ (the 267 C++ runtime library) into the Mozilla plugin, since different distributions 268 use different major versions of libstdc++. For example, Ubuntu Warty uses 269 libstdc++5, Fedora Core 3 uses libstdc++6, while Ubuntu Hoary uses libstdc++5 284 C++ runtime library) into the Mozilla plug-in, since different distributions 285 use different major versions of libstdc++. Package maintainers don't have to 286 worry about this problem, since they can link against the standard libstdc++ 287 required by their distribution.<br> 288 <br> 289 <b>For example:</b> Ubuntu 4.10 (Warty) uses libstdc++5, Fedora Core 3 uses libstdc++6, while Ubuntu 290 5.04 (Hoary) uses libstdc++5 270 291 and libstdc++6. This is taken care of in the Annodex patches to VLC; if you 271 look at the VLC_Annodex.diff file, you'll notice that mozilla/Makefile.am 272 has been modified so there's some magic there to force libstdc++ to be 273 linked in statically. As far as I know, this is safe to do, and the method 274 in the diff file is the best known way of doing it that I'm aware of. (You 275 would think that "-Wl,-Bstatic -lstdc++ -Wl,-Bdynamic" would work, but it 276 doesn't.) If you are an expert on all this, please let me know if this is 277 the Right Way of doing things.<br><br>Package maintainers don't have to 278 worry about this problem, since they can link against the standard libstdc++ 279 required by their distribution.<br> </li> 280 <li>There is also the problem of multiple video and audio output drivers for 281 Linux. By default, the Mozilla plugin will use only OSS for audio output and 292 look at the <font face="Courier New">VLC_Annodex.diff</font> file, you'll notice that mozilla/Makefile.am 293 has been modified to force libstdc++ to be linked in statically. While this is safe to do, the method 294 in the diff file is the best known way of doing it from current development 295 efforts. Attempts to do this command "<font face="Courier New">-Wl,-Bstatic -lstdc++ -Wl,-Bdynamic</font>" does 296 not work at the moment. Any experts in this field who could give advice to 297 these issues are welcome to contact the Annodex Development Team.<br> 298 <br> 299 <b>Pending Issues:</b> There is the problem of multiple video and audio output drivers for 300 Linux. By default, the Mozilla plug-in will use only OSS for audio output and 282 301 will try Xvideo then X11 (in that order) for video output. If you wish to 283 support other types of audio or video plugins (such as jack, esd), you will 284 need to modify some #defined constants near the start of mozilla/vlcshell.cpp 285 file. Good luck :).</li> 302 support other types of audio or video plug-ins (such as jack, esd), you will 303 need to modify some <font face="Courier New">#defined</font> constants near the start of 304 <font face="Courier New">mozilla/vlcshell.cpp</font> file, which is beyond 305 the scope of current developments.</li> 286 306 </ol> 287 <h3><a name="2.2_ME_Code_Structure_&_Functionality">2.2 Media Engine Code 288 Structure & Functionality</a></h3> 289 <p>Insert Table...</p> 307 <h3><a name="2.2_ME_Directory_Structure">2.2 Media Engine Directory Structure</a></h3> 308 <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="100%" id="AutoNumber2"> 309 <tr> 310 <td width="20%"><b>Directory</b></td> 311 <td width="80%"><b>Contents</b></td> 312 </tr> 313 <tr> 314 <td width="20%">/trunk/Core</td> 315 <td width="80%">Core XPI Files: Refer to XUL Core development documentation 316 for further information.</td> 317 </tr> 318 <tr> 319 <td width="20%">/trunk/Docs</td> 320 <td width="80%">Documentation directory, in which this document and release 321 notes reside.</td> 322 </tr> 323 <tr> 324 <td width="20%">/trunk/Installer</td> 325 <td width="80%">Linux Shell Scripts for compilation of files into a XPI 326 Firefox Plug-in Installer; and Windows Installer Batch file. Refer to section 327 1.0 for details.</td> 328 </tr> 329 <tr> 330 <td width="20%">/trunk/MediaEngines</td> 331 <td width="80%">Contents of VLC Media Engine plug-in for Mozilla Firefox 332 Browser.</td> 333 </tr> 334 <tr> 335 <td width="20%">/trunk/MediaEngines/GeckoSDK/gecko-sdk-1.4-win32</td> 336 <td width="80%">Pre-compiled Gecko SDK for Windows 32-bit systems. Refer to 337 section 2.1.1 for information.</td> 338 </tr> 339 <tr> 340 <td width="20%">/trunk/MediaEngines/GeckoSDK/gecko-sdk-1.7-macosx</td> 341 <td width="80%">Pre-compiled Gecko SDK for MacOS X systems. Refer to section 342 2.1.1 for information.</td> 343 </tr> 344 <tr> 345 <td width="20%">/trunk/MediaEngines/VLC/bin-linux-i386</td> 346 <td width="80%">Pre-compiled Linux plug-in of VLC Media Engine for Annodex 347 media playback. (Intel x86 CPU architecture-based systems)</td> 348 </tr> 349 <tr> 350 <td width="20%">/trunk/MediaEngines/VLC/bin-linux-ppc</td> 351 <td width="80%">Pre-compiled Linux plug-in of VLC Media Engine for Annodex 352 media playback. (IBM PowerPC architecture-based systems)</td> 353 </tr> 354 <tr> 355 <td width="20%">/trunk/MediaEngines/VLC/bin-macosx</td> 356 <td width="80%">Pre-compiled Mac OS version X and above plug-in of VLC Media 357 Engine for Annodex media playback.</td> 358 </tr> 359 <tr> 360 <td width="20%">/trunk/MediaEnginesVLC/bin-win32</td> 361 <td width="80%">Pre-compiled Windows 32-bit plug-in of VLC Media Engine for 362 Annodex media playback.</td> 363 </tr> 364 <tr> 365 <td width="20%">/trunk/MediaEngines/VLC/builc</td> 366 <td width="80%">Cygwin Configuration files for setting up environmental 367 paths for VLC media engine's supported platforms.</td> 368 </tr> 369 <tr> 370 <td width="20%">/trunk/MediaEngines/VLC/src</td> 371 <td width="80%">Source code of VLC Media Engine. Refer to section 2.1 and 372 2.2 for information.</td> 373 </tr> 374 </table> 290 375 291 376 </body> AnnodexFirefoxExtension/trunk/Docs/DevDoc_XULCore.html
r2188 r2191 40 40 </tr> 41 41 <tr> 42 <td width="100%"><a href="#2.1_Building_the_Chrome_XPI">2.1 Building the Chrome XPI</a></td> 42 <td width="100%"> <a href="#2.1_Building_the_Chrome_XPI">2.1 Building the Chrome XPI</a></td> 43 </tr> 44 <tr> 45 <td width="100%"> 46 <a href="#2.2_XUL_Code_Directory_Structure">2.2 XUL Core Directory Structure</a></td> 43 47 </tr> 44 48 </table> … … 206 210 207 211 <p>The chrome and media engine are packaged as separate .XPIs. While the chrome 208 is the same on all platforms, a different video plug in is required for each212 is the same on all platforms, a different video plug-in is required for each 209 213 operating system and CPU architecture. The two main components to AFE are as 210 214 follows:</p> … … 218 222 display. The chrome is platform-independent, and it registers itself with 219 223 Mozilla as the handler for application/x-annodex, and it embeds the video 220 plug in. The AFE Chrome also handles the parsing of CMML metadata and clip224 plug-ins. The AFE Chrome also handles the parsing of CMML metadata and clip 221 225 information implementing JavaScript's XML to RDF parser functions.<br> 222 226 </li> 223 227 <li><b>Media Engine: </b>Refer to the Media Engine documentation for further 224 228 details.<br> 225 The media engine is a Mozilla plug in used to do the playback and rendering of226 the audio or video. Currently, we use the VLC Mozilla plug in as the media229 The media engine is a Mozilla plug-in used to do the playback and rendering of 230 the audio or video. Currently, we use the VLC Mozilla plug-in as the media 227 231 engine on all platforms, though this may change in the future. The video 228 plug in is native code specific for each of the supported platforms on Windows,232 plug-in is native code specific for each of the supported platforms on Windows, 229 233 Linux (x86 and PowerPC) and MacOS. Each media engine registers with Mozilla as 230 an application/x-annodex-player plug in; e.g. the VLC media engine is234 an application/x-annodex-player plug-in; e.g. the VLC media engine is 231 235 registered as application/x-annodex-vlc-viewer-plugin. </li> 232 236 </ol> … … 243 247 This is because all the XUL and the Javascript code is loaded into memory 244 248 upon startup. The use of existing Javascript debuggers for Mozilla Firefox 245 as a plug in will identify the ANXLoader.js files, but it may not be able to249 as a plug-in will identify the ANXLoader.js files, but it may not be able to 246 250 trace the internal Javascript code.</li> 247 251 </ol> 248 252 249 <h3><a name="2.2_XUL_Code_Structure_&_Functionality">2.2 250 XUL_Code_Structure_&_Functionality</a></h3> 251 <p>Insert Table...</p> 253 <h3><a name="2.2_XUL_Code_Directory_Structure">2.2 254 XUL Core Directory Structure</a></h3> 255 <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="100%" id="AutoNumber2"> 256 <tr> 257 <td width="20%"><b>Directory</b></td> 258 <td width="80%"><b>Contents</b></td> 259 </tr> 260 <tr> 261 <td width="20%">/trunk/Core</td> 262 <td width="80%">Core XPI Files: Refer to XUL Core development documentation 263 for further information.</td> 264 </tr> 265 <tr> 266 <td width="20%">/trunk/Core/chrome/afeview</td> 267 <td width="80%">The Core XUL Annodex Firefox Viewer files. Refer to section 268 2.0 for further details.</td> 269 </tr> 270 <tr> 271 <td width="20%">/trunk/Core/chrome/afeview/content</td> 272 <td width="80%">Contains the Core XPI interface (afeview.xul) and Javascript 273 code (afeview.js). This is elaborated in section 1.1.</td> 274 </tr> 275 <tr> 276 <td width="20%">/trunk/Core/chrome/afeview/locale</td> 277 <td width="80%">Contains the stub directory which will hold the 278 internationalisation of the plug-in interface.</td> 279 </tr> 280 <tr> 281 <td width="20%">/trunk/Core/chrome/afeview/skin</td> 282 <td width="80%">Contains the graphical elements of the Core XPI and CSS 283 Stylesheet.</td> 284 </tr> 285 <tr> 286 <td width="20%">/trunk/Core/components</td> 287 <td width="80%">Contains the ANXLoader Mozilla component (ANXLoader.js). 288 This is elaborated in section 1.2.</td> 289 </tr> 290 <tr> 291 <td width="20%">/trunk/Core/testcode</td> 292 <td width="80%">Contains stub code methods to test XML to RDF parser 293 embedded in the Core XPI.</td> 294 </tr> 295 <tr> 296 <td width="20%">/trunk/Docs</td> 297 <td width="80%">Documentation directory, in which this document and release 298 notes reside.</td> 299 </tr> 300 <tr> 301 <td width="20%">/trunk/Installer</td> 302 <td width="80%">Linux Shell Scripts for compilation of files into a XPI 303 Firefox Plug-ins Installer; and Windows Installer Batch file. Refer to section 304 1.0 for details.</td> 305 </tr> 306 <tr> 307 <td width="20%">/trunk/MediaEngines</td> 308 <td width="80%">Contents of VLC Media Engine plug-in for Mozilla Firefox 309 Browser: Refer to Media Engine development documentation for further 310 information</td> 311 </tr> 312 </table> 252 313 253 314 </body> AnnodexFirefoxExtension/trunk/Docs/Release_Notes.html
r2188 r2191 9 9 10 10 <h1>Annodex Firefox Extension Viewer (AFE): Release Notes</h1> 11 12 13 <p>For further information about the development notes and documentation, refer 14 to relevant document on the Media Engine and XUL Core in the /Docs directory.</p> 11 15 12 16 AnnodexFirefoxExtension/trunk/Installer/WinSetup.bat
r2190 r2191 41 41 @ echo ====================================================== 42 42 @ echo. 43 @ xcopy /e /i /y ..\Core\chrome\afeview "%ProgramFiles%\Mozilla Firefox\chrome\afeview"44 @ copy /y "..\Core\components\ANXLoader.js" "%ProgramFiles%\Mozilla Firefox\components\ANXLoader.js"45 @ copy /y "..\Core\components\VlcIntf.xpt" "%ProgramFiles%\Mozilla Firefox\components\VlcIntf.xpt"43 @ xcopy /e /i /y ..\Core\chrome\afeview "%ProgramFiles%\Mozilla Firefox\chrome\afeview" 44 @ copy /y "..\Core\components\ANXLoader.js" "%ProgramFiles%\Mozilla Firefox\components\ANXLoader.js" 45 @ copy /y "..\Core\components\VlcIntf.xpt" "%ProgramFiles%\Mozilla Firefox\components\VlcIntf.xpt" 46 46 @ copy /y "..\MediaEngines\VLC\bin-win32\npanxvlc.dll" "%ProgramFiles%\Mozilla Firefox\plugins\npanxvlc.dll" 47 47 @ echo. AnnodexFirefoxExtension/trunk/LICENSE.txt
r957 r2191 24 24 Conrad Parker <Conrad.Parker@csiro.au> 25 25 Silvia Pfeiffer <Silvia.Pfeiffer@csiro.au> 26 Chris Chiu <Chris.Chiu@csiro.au> 26 27 27 28 Alternatively, the contents of this file may be used under the terms of