josemaria.alkala
7th May 2010, 17:30
Good afternoon,
Last week I started a repository of filters. It can be found here:
http://bitbucket.org/josemaria.alkala/avisynth_filters/src
There is a small wiki associated to it:
http://bitbucket.org/josemaria.alkala/avisynth_filters/wiki/Home
I am using Mercurial (quite easy to use). A software repository seem well suited to manage avisynth filters/scripts. When compared to other alternatives:
- Many people can contribute to it, so the workload does not have to fall over one person (better than a web page, easier than a wiki).
- From the user perspective, you can download the latest .zip version, knowing that you are downloading the latest version.
- If you install Mercurial, you can update only those filters which are new or modified, just by executing: "hg pull" in your directory.
The structure of the repository is:
- The main directory with .dll, .vdf, .avs, .avsi. E.g.: myfilter.dll
- ./doc/myfilter_v1.0: documentation associated to the "myfilter.dll".
- ./src/myfilter_v1.0: source code (when available).
- ./licenses/: some licenses in general format or per filter basis.
- licenses.org: within this file I keep track of the version uploaded, the author, the web page, the license applicable, files affected by the license.
You can see that I avoid upload many filters at the same time to give more visibility of the version uploaded and to keep a fine track of the license applicable.
The reason why I am posting this here is because maybe some of you may wish to post directly your filters in the repository. I'd be glad if anyone desire to join to this effort.
Regards,
José María
Last week I started a repository of filters. It can be found here:
http://bitbucket.org/josemaria.alkala/avisynth_filters/src
There is a small wiki associated to it:
http://bitbucket.org/josemaria.alkala/avisynth_filters/wiki/Home
I am using Mercurial (quite easy to use). A software repository seem well suited to manage avisynth filters/scripts. When compared to other alternatives:
- Many people can contribute to it, so the workload does not have to fall over one person (better than a web page, easier than a wiki).
- From the user perspective, you can download the latest .zip version, knowing that you are downloading the latest version.
- If you install Mercurial, you can update only those filters which are new or modified, just by executing: "hg pull" in your directory.
The structure of the repository is:
- The main directory with .dll, .vdf, .avs, .avsi. E.g.: myfilter.dll
- ./doc/myfilter_v1.0: documentation associated to the "myfilter.dll".
- ./src/myfilter_v1.0: source code (when available).
- ./licenses/: some licenses in general format or per filter basis.
- licenses.org: within this file I keep track of the version uploaded, the author, the web page, the license applicable, files affected by the license.
You can see that I avoid upload many filters at the same time to give more visibility of the version uploaded and to keep a fine track of the license applicable.
The reason why I am posting this here is because maybe some of you may wish to post directly your filters in the repository. I'd be glad if anyone desire to join to this effort.
Regards,
José María