Skip to content
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

Improving documentation for Julia as MIT 18.337 Class Project #4717

Closed
velicanu opened this issue Nov 3, 2013 · 6 comments
Closed

Improving documentation for Julia as MIT 18.337 Class Project #4717

velicanu opened this issue Nov 3, 2013 · 6 comments
Labels
docs This change adds or pertains to documentation

Comments

@velicanu
Copy link

velicanu commented Nov 3, 2013

Dear Julia community,

As my final project for a class I am taking, I would like to propose and implement an improved documentation for Julia. See this link for my proposal: https://www.dropbox.com/s/qxrztntmyqflsfe/DragosVelicanu_ProjectProposal_Fall2013_18337.pdf

Cheers,
Dragos

@jiahao
Copy link
Member

jiahao commented Nov 3, 2013

There are several relevant issues which you will want to consult: #762, #1619, #2567, JuliaLang/LinearAlgebra.jl#10, #3988, #4226, #4227, #4579.

@Keno
Copy link
Member

Keno commented Nov 3, 2013

I should also point out that the readline-based REPL is on its way out. That's good news though since it means you'll be able to share code between the new REPL and the IJulia kernel.

@ivarne
Copy link
Member

ivarne commented Nov 3, 2013

Proposal 3 is actually implemented in the most recent readline-REPL as of #4361, but as @loladiro points out, the REPL functionality will change a lot when 0.2 gets released and the developers starts using and improving the new julia based replacement.

You also link to the 0.1.0 version of the documentation, and julia has improved a lot since that release was made.

@timholy
Copy link
Member

timholy commented Nov 3, 2013

This sounds really great. One thing to keep in mind is that many functions accept "untyped" arguments (for good reasons). In such cases some examples of legitimate input and the resulting output would still be helpful, but you won't be able to give an exhaustive list.

@StefanKarpinski
Copy link
Member

I'm increasingly convinced that we should use IJulia for documentation, as proposed in #4579, except without the round trip translation stuff I proposed there – just .ipynb files as checked-in documentation. The master version of IPython uses names instead of UUIDs as URLs for notebooks, which allows linking between notebooks. It wouldn't be too tough to create TOC functionality and convert the manual and stdlib docs into a set of notebooks.

Both IJulia and the new REPL should use the same completion infrastructure to do things like tab completion. Currently IJulia seems to have the lead on this functionality but they should be brought into sync. If we could make our REPL tab menu behavior as slick as zsh's, I would be a very happy man.

@JeffBezanson
Copy link
Member

This is a fine discussion, but not actually an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs This change adds or pertains to documentation
Projects
None yet
Development

No branches or pull requests

7 participants