hugin-devs team mailing list archive

[Yuv <789444@xxxxxxxxxxxxxxxxxx>]

** Changed in: hugin
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/789444

Title:
  2011.2+: scripts repository

Status in Hugin - Panorama Tools GUI:
  Fix Released

Bug description:
  The introduction of HSI/HPI will hopefully catalyze a whole echo-
  system of hundreds of scripts.  A few will be shipped and installed by
  default with Hugin;  the rest need a home.

  Scripts shipped with Hugin will be deemed either core functionality,
  or examples to jump-start the user on hacking scripts.

  All other scripts need to be stored in a central, open, accessible
  repository.

  As the body of scripting grows, there will be hopefully many
  contributors to that repository with hundreds of plugins to choose
  from.

  The code will be stored in a mercurial repository (to be created).
  Every version of every script ever committed will be accessible with a
  schema like:

  http://hugin.hg.sourceforge.net/hgweb/hugin/plugins/raw-
  file/32055f79a8aa/woa.py

  where:
  * http://hugin.hg.sourceforge.net/hgweb/hugin/plugins is the hard-coded base for the repository
  * /raw-file/ is the function of the repository that gives the script as-is, so that on the other end Hugin can save it in the pre-defined script folder and make it accessible to the user
  * 32055f79a8aa is the specific revision of the plugin
  * /woa.py is the unique name identifying the plugin

  For every revision of the script, we will need to record and make
  accessible / searchable the following information:

  * against which API of Hugin it is compatible.  This is currently a significant issue because accidental incompatible modification of the wrapped header is a very possible scenario.  See bug 789442
  * against which O/S (version) it is known to work, and against which one it is known not to work
  * external dependencies - Python scripts can and will call on functionality of third party tools such as dcraw or ImageMagick.

  Moreover the entries should be taggable and users shall have an
  opportunity to rate the scripts / plugins.

  This calls for a web page with a database that maps all of this
  information against the schema described at the beginning of this
  post.  Access to this web page can be integrated in Hugin, and maybe
  even the fetching and storing of the plugins.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/789444/+subscriptions