-
Thanks; it looks good enough to me. Are there other atoms that need to be added? I'd like to have a bigger picture before starting work on the MOVI atom changes (sounds like a lot of work around the parameter handling and xml building/parsing)
2009-12-03 04:42:56 UTC in AtomicParsley
-
I can't access that file (gives me a broken tarball). Please create an issue with the docs pasted into it on bitbucket; it will shortcut things a great deal for me (as that's all I'm going to do about it in the meantime anyway):
[you can create an issue by clicking here](http://bitbucket.org/wez/atomicparsley/issues/new/)
http://bitbucket.org/wez/atomicparsley/issues/new/.
2009-12-03 03:23:26 UTC in AtomicParsley
-
I merged the stack/buffer fixes from the snapstream sources, but omitted their proprietary extensions.
My preference for receiving patches, suggestions and bug reports is via
[the bitbucket issue tracker](http://bitbucket.org/wez/atomicparsley/issues/new/)
Patches will ideally be supplied as a diff against the repo (you need python + mercurial for this), as this is easiest for me to deal...
2009-11-29 09:48:22 UTC in AtomicParsley
-
Sorry, I was not monitoring this thread (checking the box now!).
I'm just about to push the HD, account name and debug-spam changes up to bitbucket, and I'll take a look at the snapstream sources.
2009-11-29 08:54:27 UTC in AtomicParsley
-
I forked the code onto bitbucket and took a stab at 64-bit file support; it seems to work ok for me for the file I was testing it on today, and I'd appreciate feedback from others:
http://bitbucket.org/wez/atomicparsley.
2009-11-25 08:58:33 UTC in AtomicParsley
