Gnusto development moved to GitHub

[Dannii]

I will now be doing my work on the Gnusto engine at GitHub:
http://github.com/curiousdannii/gnusto/

Feel free to register and start up branches etc. I'm still just
getting started with git but it doesn't seem too complicated.

And I guess if you change it here in Parchment I'll update it at
Github with your changes too... but I'd prefer for it to all happen on
Github now.

Now, what am I planning to do with it in the future?
- Consider making parts of the engine more generic to have
compatibility with Quixe (https://github.com/erkyrath/quixe/)
- Hopefully make Gnusto independant of any libraries
- Stop it polluting the window namespace
- Add a unit test suite (planning to write a new inform assembler
first though)
- Lots more optimisations
- Lots more fun!

[Atul Varma]

Very cool!

Github seems really sweet.  I'm only familiar with HG at the moment, though, so I need to learn git's ins and outs.

- Atul

[Dannii]

Hey Atul,

I'm thinking of adding more docs... would you still recommend code-
illuminated for JS? What would you recommend for python?

On Mar 29, 4:01 am, Atul Varma <var...@gmail.com> wrote:
> Very cool!
>
> Github seems really sweet. I'm only familiar with HG at the moment, though,
> so I need to learn git's ins and outs.
>
> - Atul
>

[Atul Varma]

Cool!  Yeah, I like code illuminated, but I am partial to it of course :)  For Python I guess I like Sphinx (http://sphinx.pocoo.org/), though it also wouldn't be hard to modify code-illuminated to work with Python code too--though it wouldn't be able to easily snoop into docstrings and use all the cool introspective capabilities of Python to auto-generate docs.

- Atul