![]() The update mostly consists of refactoring existing code and replacing deprecated API calls. In addition to the Journler code itself, I am also updating local frameworks on which the application is dependent as well as incorporating newer versions of other 3rd party code and frameworks. The 2.6 compatibility update is a significant undertaking. As I make improvements to the code I will push them to github so that this repository should reflect changes to the latest binaries. Compiling this project will produce an application identical to the current version of the publicly available 2.6b update. This is the complete Xcode project for the Journler application, including source code, interface files and application resources, and it is the same code I am currently developing for the 2.6 Mac OS compatibility update. The issue is that I combined this code into a framework, whereas I should have just grabbed the source files from the repository as I required them. In fact I will likely continue to maintain separate repositories for re-usable code. The issue is not so much that the code is kept separate. I no longer believe this was necessary, and a portion of the open sourcing effort includes the decomposition of these frameworks into their constituent parts and the re-incorporation of that code back into the main Journler project. Initially I thought it wise to collect generic code used in Journler into these two separate frameworks to improve their re-usability. The Utilities and Interface frameworks are forthcoming. SproutedAVI handled's audio-visual input and is already available at github. Journler relies on a three additional frameworks from Sprouted. KBWordCountingTextStorage by Keith Blount.The Pantomime framework by Ludovic Marcotte.More cool windows and candy by Chad Weider.Cool windows and other visual candy by Matt Gemmell.iMediaBrowser by Greg Hulands and the crew / Karelia.The LAME Framework and Quicktime Component by Lynn Pye.The LAME encoder by the lame group at.If you find unaccredited code or improperly used licenses, please let me know. License does not supersede any licenses imposed by the included 3rd party code. Journler uses the following open source software, many of whose sourceįiles are contained within the Journler code base. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES LOSS OF USE, DATA, OR PROFITS OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. Neither the name of the author nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |