[hugin-ptx] Python pto parser

[kfj]

Hi all!

I've come to a point with my Python pto parser project where I have a
functioning scanner which can handle all pto syntax I'm aware of and
presents the scan as an object containing the pto file's content in a
structured form to be analyzed and modified.

The scan is syntactic so far, and it deliberately recognizes a
superset of pto to be quite future-proof. It does not check if the
scan makes sense semantically. Semantics aren't necessary, though, for
a lot of operations on the pto data, so I want to keep the scanner
accessible as a separate entity anyway.

I would like to publish the code for peer review. I don't know how to
go on about publishing. Is there a designated space in the hugin
dataverse to upload stuff like this? Maybe one of the developers could
give me advice? I'd rather have the project hatch in the community
than going ahead and putting it on PyPI already. The code is plain
Python, licensed GPL.

with regards
Kay

-- 
You received this message because you are subscribed to the Google Groups 
Hugin and other free panoramic software group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: [hugin-ptx] Python pto parser

[Yuval Levy]

Hallo Kay,

On November 22, 2010 08:39:41 am kfj wrote:
 I would like to publish the code for peer review. I don't know how to
 go on about publishing. Is there a designated space in the hugin
 dataverse to upload stuff like this?

Thanks for intending to share.  The earlier the better.

I will open an extra Mercurial repositories in Hugin for scripts and other 
contributions.  It can always be merged into the main repo later on if it 
makes sense.

You will need to tell me your SF user ID so that I can grant you write access 
to the Hugin project.

If you don't have yet an SF user ID, open first a Launchpad account (and 
document it please).  Then you can use OpenID to log on and create an account 
on SF.  Theoretically it should be simpler than creating a new account from 
scratch.  I'm interested in a documented experience.

Opening a repo is a matter of a minute or two, so I'll wait until you 
communicate your SF ID here.

Welcome to the team!
Yuv




 Maybe one of the developers could
 give me advice? I'd rather have the project hatch in the community
 than going ahead and putting it on PyPI already. The code is plain
 Python, licensed GPL.
 
 with regards
 Kay


signature.asc
Description: This is a digitally signed message part.