Automated reference builder about heroprotocoljs HOT 4 OPEN

Should the reference stay in this project and in what form: files, wiki or both? Or make a dedicated project?

Would be nice to team up with people working in other languages if possible.

from heroprotocoljs.

Because Javascript is interpreted, I'm not opposed to make node-gyp modules (using c) for these, especially the mpq functions. Most of the time wasted in extracting the data is there.

from heroprotocoljs.

Current work visible on the feature-automation branch.

It's a work in progress, currently porting from a local clone of the heroprotocol repository, but I want for the script to do it's own clone/pull.

The porting script reads the Python lines and transforms them into Javascript object representation of the data structure and events, thus paving the way for the automatically generated reference.

from heroprotocoljs.

Considering the feature-automation branch, a conundrum has occurred. Should the porting script and the distributables be in the same repo?

The following two questions are not mutually exclusive:

• Should the porting script be in this repo or a heroprotocoljs-build repo?
• Should the distributables be in a repo at all, or just always built (e.g. in a dist/ folder to copy into higher-level application; or, automatic github uploader to personal repo; or, automatic npm uploader to personal namespace)

Two cases:

• Is this repo trying to maintain as close a port as possible? If so, perhaps the -build repo automatically generates this repo.
• Someone wants to create a fork of this project to change the template, a fork of the -build repo would let them do so. Example: I have a minimally-working fork using storm-replay rather than mpyqjs. If there was a -build repo, I could use it's script to grab the Blizzard/heroprotocol repo and update the templates.

Food for thought...

from heroprotocoljs.