On Monday, December 3, 2012 10:45:50 PM UTC+1, William wrote:
If anybody reading this has any experience with how to dramatically
improve reference documentation of a big open source software project,
please share.
Likely, there is nobody in the world. My take on this would be to
On Monday, December 10, 2012 9:02:17 PM UTC+1, Harald Schilly wrote:
I could also envision some meta-tutorials, that explain what could be done
for a certain problem...
... after having some thoughts about this, I remembered this: The R
program is rather small, but all the features are
Yes, it was kind of frustrating. Basically, David advertised it a
lot, but at the end of the day, basically few people were available to
come to a Sage Days on improving the documentation, even with all
expenses paid...
I don't know if my situation is typical but for me usually the time
Something like the information provided at
http://www.sagemath.org/doc/thematic_tutorials/tutorial-objects-and-classes.html#sage-specifics-about-classes
would be nice to have for an mathematical object in general. A good
start would be the blog post at sagemath.blogspot.com from William,
On Dec 4, 2012 2:56 AM, Martin Albrecht martinralbre...@googlemail.com
wrote:
Yes, it was kind of frustrating. Basically, David advertised it a
lot, but at the end of the day, basically few people were available to
come to a Sage Days on improving the documentation, even with all
On 4 December 2012 13:44, William Stein wst...@gmail.com wrote:
Does anybody want to organize another doc days (maybe to happen in July
2013?)?
Note that there's a planned Sage Days in Leiden at the end of that
month:
On Sunday, December 2, 2012 8:52:00 PM UTC-5, John H Palmieri wrote:
See
http://sage.math.washington.edu/home/palmieri/misc/6495-jsmath/html/en/reference/index.htmlfor
what the reference manual might look like if
http://trac.sagemath.org/sage_trac/ticket/6495 is every merged into Sage.
On Sun, Dec 2, 2012 at 11:59 PM, charles Bouillaguet
charles.bouillag...@gmail.com wrote:
I still think that MAGMA's handbook is easier to browse than SAGE's
reference manual (both are supposed to exhaustively describe all the
functions in the system). One reason for that is probably that in
,
On Mon, Dec 3, 2012 at 1:16 PM, David Roe roed.m...@gmail.com wrote:
On Sun, Dec 2, 2012 at 11:59 PM, charles Bouillaguet
charles.bouillag...@gmail.com wrote:
I still think that MAGMA's handbook is easier to browse than SAGE's
reference manual (both are supposed to exhaustively describe
On 12/03/2012 04:45 PM, William Stein wrote:
Yes, it was kind of frustrating. Basically, David advertised it a
lot, but at the end of the day, basically few people were available to
come to a Sage Days on improving the documentation, even with all
expenses paid...
If anybody reading this
Hi,
Actually, I think I agree with the request of WM Chung. I found myself
longing for a high-level overview of SAGE development. I think it
could be pretty simple, but that it could explain how some things are
organized. For instance :
*) what is the category framework? what purpose does it
Your starting point should be the developer guide
(http://www.sagemath.org/doc/developer), not the reference manual. The
latter is really for reference. I think the developer manual has a
reasonable explanation of the coercion model. A similar treatment of the
category framework is sorely
On Sunday, December 2, 2012 9:43:49 AM UTC-8, Charles Bouillaguet wrote:
And now, for something completely different.
I think that the reference manual is very useful, but its linear
structure (a loong list of items where it is not obvious where to
find what you are looking for) is
Hey everyone,
Two things on that note, I looked over the conventions page and noticed
some discrepancies, which is now ticket
http://trac.sagemath.org/sage_trac/ticket/13791 and I'd appreciate review.
Second, Andrea, there are many bugs which are not mathematical problems,
but errors in
2012/12/3 John H Palmieri jhpalmier...@gmail.com:
See
http://sage.math.washington.edu/home/palmieri/misc/6495-jsmath/html/en/reference/index.html
for what the reference manual might look like if
http://trac.sagemath.org/sage_trac/ticket/6495 is every merged into Sage. Do
you like that any
Hi,
I am new to Sage and I am interested to participate in the development work
of Sage. I would like to understand the codes of Sage.
I would like to know if there is any high level architectural design
document on Sage. I can find fragments of information related to this, e.g.
- Sage use
16 matches
Mail list logo
