So far that looks like a real improvement! I end up making my own
bookmarks for useful but hard to find wiki pages, although I think in
some cases I tried to edit the front page to put them there. Like
http://wiki.sagemath.org/combinat/HelpOnTheDoc
and
http://wiki.sagemath.org/DanDrake/JustEn
On Sep 28, 2:53 pm, Pat LeSmithe wrote:
> On Sun, Sep 27, 2009 at 11:16 AM, Pat LeSmithe wrote:
> > * Re-organize the Sage wiki front page? For example:
>
> There's a very early version at
>
> http://wiki.sagemath.org/NewFrontPage
What a massive improvement in organization this would be! T
On Sun, Sep 27, 2009 at 11:16 AM, Pat LeSmithe wrote:
> * Re-organize the Sage wiki front page? For example:
There's a very early version at
http://wiki.sagemath.org/NewFrontPage
Feel free to make suggestions and changes to this page or to any of
http://wiki.sagemath.org/SageSupportCenter
h
On Sat, Sep 26, 2009 at 7:14 PM, Minh Nguyen wrote:
>
> Hi,
>
> On Sun, Sep 27, 2009 at 11:16 AM, Pat LeSmithe wrote:
>
>
>
>> On related notes, should we
>>
>> * Re-organize the Sage wiki front page? For example:
>>
>> + Make it easier for a newcomer, developer or user, to find what they
>
Hi,
On Sun, Sep 27, 2009 at 11:16 AM, Pat LeSmithe wrote:
> On related notes, should we
>
> * Re-organize the Sage wiki front page? For example:
>
> + Make it easier for a newcomer, developer or user, to find what they
> want.
Yes. Any volunteers?
> + Put more recent and/or useful pa
Kwankyu wrote:
> I think that if Sage has a component as a part of it, we should at
> least tell the user how to use the component. Currently the user is
> told to ask Google about it. Here I mean those components intended for
> end users. .
How about at least including links to [sufficiently] o
On Sep 26, 2:55 pm, William Stein wrote:
> On Sat, Sep 26, 2009 at 3:59 AM, Nick Alexander wrote:
> > And at this point, which sage component doesn't have its documentation
> > on the web -- latest version, everything maintained upstream?
>
> Many important Sage users don't have web access all
Hi,
I think that if Sage has a component as a part of it, we should at
least tell the user how to use the component. Currently the user is
told to ask Google about it. Here I mean those components intended for
end users. .
Kwankyu
--~--~-~--~~~---~--~~
To post to
On Sat, Sep 26, 2009 at 3:59 AM, Nick Alexander wrote:
> And at this point, which sage component doesn't have its documentation
> on the web -- latest version, everything maintained upstream?
Many important Sage users don't have web access all the time.
-- William
--~--~-~--~~
On 26-Sep-09, at 12:35 AM, Robert Bradshaw wrote:
>
> On Sep 25, 2009, at 8:31 PM, Kwankyu wrote:
>
>>> It is totally feasible. It hasn't happened only because nobody has
>>> done it. I think the only good reasonable longterm way to do this
>>> would be to modify the spkg-install for each and
On Sep 26, 2009, at 3:59 AM, Nick Alexander wrote:
> On 26-Sep-09, at 12:35 AM, Robert Bradshaw wrote:
>
>>
>> On Sep 25, 2009, at 8:31 PM, Kwankyu wrote:
>>
It is totally feasible. It hasn't happened only because nobody has
done it. I think the only good reasonable longterm way to d
On Sep 25, 2009, at 8:31 PM, Kwankyu wrote:
>> It is totally feasible. It hasn't happened only because nobody has
>> done it. I think the only good reasonable longterm way to do this
>> would be to modify the spkg-install for each and every package so
>> that
>> it installs documentation for
>
> And at this point, which sage component doesn't have its documentation
> on the web -- latest version, everything maintained upstream?
>
eclib, for a start
John
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To u
>
> It is totally feasible. It hasn't happened only because nobody has
> done it. I think the only good reasonable longterm way to do this
> would be to modify the spkg-install for each and every package so that
> it installs documentation for that package into
> $SAGE_LOCAL/doc/pkgname. This
On Fri, Sep 25, 2009 at 6:45 PM, Kwankyu wrote:
>
> Hi,
>
> I thought of this idea. How about including the manuals (and/or
> tutorials and/or references) of all (perhaps not all but almost all)
> the (enduser) components of Sage into Sage? Or maintain a repository
> site of all the manuals such
15 matches
Mail list logo
