-
Notifications
You must be signed in to change notification settings - Fork 5
Add utility functions and documentation #10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
…ontext. Added Utilities.jl to the list of files that are included in CGP.jl
|
This fixes #8. |
|
Actually, I was thinking about this last night and I may go ahead and change to using reStructuredText and Sphinx (http://sphinx-doc.org/rest.html) to generate the documentation. This is what Julia itself uses. It has the added advantage of being able to use Read The Docs for documentation hosting, which automatically updates itself from GitHub. The Julia documentation is an example of how this turns out. Another example is the documentation for a library I wrote for parsing VTK files in Python: https://vtkxml-builder.readthedocs.org/en/latest/. |
|
Either is OK with me. I see that both have support for images. On Alden On Mon, Mar 23, 2015, at 09:16, George Lesica wrote:
|
|
I went ahead and cherry-picked the utilities commits and moved them into master, so now this branch is just all about documentation. |
|
Good. I can send where I am on documentation tomorrow. I am going to send a separate message about neutrality and Alden On Sat, May 2, 2015, at 13:44, George Lesica wrote:
Links: |
Create utilities file for internal functions and start in on the documentation. Utilities functions should live in their own module.