Skip to content
Two letters better than MetaX
Objective-C Swift C Shell Rich Text Format AppleScript Other
Branch: develop
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/workflows Try and fix github site action Mar 9, 2020
App Support TV app and missing iTunes Mar 17, 2020
Externals Remove Growl Plugin Jan 2, 2020
Extras Moved stuff to extras directory Apr 3, 2014
Framework Support TV app and missing iTunes Mar 17, 2020
MetaZ.xcodeproj Revert "Don't let Carthage copy the Sparkle.framework (breaks XCode 11)" Mar 22, 2020
Plugins Support TV app and missing iTunes Mar 17, 2020
Release First crack at automatic releases Sep 10, 2017
Scripts Fix issues that prevent build when path contains space Mar 16, 2020
.gitignore xcschemes were stored in user data location. Now they are in the shar… Dec 25, 2019
.gitmodules Add GTM as submodule Sep 9, 2017
.travis.yml Move Travis CI to Xcode 11.3 to update git for Carthage fixes. Mar 14, 2020
Cartfile Update Sparkle Mar 14, 2020
Cartfile.resolved Update Sparkle Mar 14, 2020
Credits.html Switched to MGViewAnimation Aug 23, 2011
Document.scpt Finished the rough first version of applescript support Nov 1, 2012
Gemfile Try different way of setting release notes Sep 22, 2017
Gemfile.lock Change Gemfile.lock to support ruby 2.0.0 Sep 24, 2017
License.txt Update copyright Sep 12, 2017
README.markdown Update build instructions Mar 17, 2020
Selection.scpt Finished the rough first version of applescript support Nov 1, 2012
Tags.scpt Finished the rough first version of applescript support Nov 1, 2012
bisect.sh Added a small bisect script Dec 4, 2012
compile-applescripts.sh Support TV app and missing iTunes Mar 17, 2020
init.sh Added init script to simplify build from fresh checkout Oct 8, 2013
sparkle_private.pem.enc Make new encryption key Jun 19, 2019
sparkle_public.pem Added Sparkle sign script Sep 4, 2009
version.plist Initial import of MetaZ Sep 4, 2009

README.markdown

Introduction Build Status

MetaZ is an mp4 meta-data editor for OS X.
It started its life when another great meta-data editor MetaX stopped getting updated, some of the web-services it used changed in ways that broke functionality and it had some really anoying (to us at least) little missing things like no proper window resizing. This lead to us starting MetaZ as a reimplementation of MetaX with a few ideas of our own sprinkled in there.

Bugs / Feature request

For bugs and feature requests you can use our issue tracker at github

Extras

We have created some extra resources and small plugins that were deemed to small or silly to be included with the main program.

The classic moo from MetaX is finally available via a small MetaZ plugin you can download from here. To install it simply unpack the zip file and drop the unpacked script onto the MetaZ dock icon.

If you use Script Debugger from Late Night Software you are in luck because we have created a Script Debugger template for MetaZ plugins which illustrate the different types of events plugins can respond to. To get the template click here

Helping out

Building

To build the project you need to have Xcode and Carthage installed.

Before you can build the project with Xcode you first need to download the needed submodules:

git submodule update --init

And then bootstrap the dependencies managed by Carthage:

cathage bootstrap

After those two steps you should be able to compile the project with Xcode normally.

Contribution steps

We follow GitHub flow, as a workflow. Basically:

  • Create a feature branch in your fork
  • Make your change with documentation as appropriate
  • Please run and test a release build before submitting a pull request!
  • Submit a pull request from your branch
  • Someone with commit access will review the code and merge it. This applies even if you also have commit access.

Becoming a committer

Going forward we will follow rubinius' lead and once you have one pull request accepted into MetaZ, we will add you to a team that has push+pull access. Basically you will get a big green merge button on other people's pull requests, and you will be able to commit those pull requests to the griff/metaz master branch.

This also means that you could push your commits directly to griff/metaz without going through a pull request. We ask that you not do this, however, so that any code on master has been reviewed. This does not apply to branches other than master; if there is long-term collaboration happening, create a feature branch and feel free to push directly to that (but have commits reviewed before merging that branch into master).

We reserve the right to take away this permission, but in general we trust you to give it to you.

You can’t perform that action at this time.