On Jan 8, 7:41 pm, "David Joyner" wrote:
> Hi:
Hi David,
> I just posted more pics
> tohttp://sage.math.washington.edu/home/wdj/sagedays/ams2009/images.html
>
> I think Sage gained a lot of publicity this year both by being at
> the booth but also having an MAA panel discussion and an AMS se
Hi:
I just posted more pics to
http://sage.math.washington.edu/home/wdj/sagedays/ams2009/images.html
I think Sage gained a lot of publicity this year both by being at
the booth but also having an MAA panel discussion and an AMS session.
The panel discussion was good to be able to meet others in
On Jan 8, 2:34 pm, bsdz wrote:
> I must admit I did consider TinyMCE amongst many others but I liked
> EditArea since it could syntax highlight python code. Other
> highlighters either didn't allow editing or didn't have built in
> python lexers. I notice the other thread has recently become mo
On Jan 8, 3:22 pm, Jason Grout wrote:
> mabshoff wrote:
>
> > I think that the editor is just as important as the @interact in the
> > notebook. So if we could find some more people to test the patches we
> > can get them into the next release. As long as they don't break any
> > existing funct
mabshoff wrote:
>
> I think that the editor is just as important as the @interact in the
> notebook. So if we could find some more people to test the patches we
> can get them into the next release. As long as they don't break any
> existing functionality I would think that even if the editor su
On Jan 8, 2:33 pm, "William Stein" wrote:
> Hi,
Hi,
> One of the virtual machines I use for building Sage has 512MB RAM and
> is running Linux CentOS 64-bit.
> In trying to build Sage it gets to linbox:
>
> g++ -DHAVE_CONFIG_H -I. -I../.. -I../.. -I. -I../../linbox -g
> -I/home/wstein/build/
That's ok, not to worry. Actually I just want people to keep in mind
it is something unfinished. Perhaps in retrospect I should have waited
one day to post it.
On Thu, Jan 8, 2009 at 5:26 PM, mabshoff wrote:
>
>
>
> On Jan 8, 2:21 pm, "Luiz Felipe Martins"
> wrote:
>> Oh well...
>
> Yeah, I kin
I must admit I did consider TinyMCE amongst many others but I liked
EditArea since it could syntax highlight python code. Other
highlighters either didn't allow editing or didn't have built in
python lexers. I notice the other thread has recently become more
active so I may follow that.
Thanks fo
Hi,
One of the virtual machines I use for building Sage has 512MB RAM and
is running Linux CentOS 64-bit.
In trying to build Sage it gets to linbox:
g++ -DHAVE_CONFIG_H -I. -I../.. -I../.. -I. -I../../linbox -g
-I/home/wstein/build/centos64/build/sage-3.2.3/local/include/linbox
-I/home/wstein/b
On Jan 8, 2:21 pm, "Luiz Felipe Martins"
wrote:
> Oh well...
Yeah, I kind of wandered about this myself and we could in theory
delete that particular message from sage-devel. But since this list is
archived elsewhere there is no point to do this and I would greatly
prefer not to change/delete
Oh well...
On Thu, Jan 8, 2009 at 5:16 PM, Martin Albrecht
wrote:
>
>> Please do not distribute this, since it is work in progress.
>
> You just sent the worksheet to a public mailinglist with 752 members.
>
> Furthermore, your attachment is available for download here:
>
> http://groups.google.
> Please do not distribute this, since it is work in progress.
You just sent the worksheet to a public mailinglist with 752 members.
Furthermore, your attachment is available for download here:
http://groups.google.com/group/sage-devel/browse_thread/thread/a4ba0ed228e220c5
i.e. your work is a
On Jan 8, 12:29 pm, Martin Albrecht
wrote:
Hi Martin,
> > Sure, but the fact that moinmoin just works without the need for any
> > configuration of a sql database is a killer feature since it might not
> > be a problem for some people on this list to set up mysql and so on
> > properly, but m
On Jan 8, 12:42 pm, "Conrad Meyer" wrote:
> 2009/1/8 mabshoff :
Hi,
> Ah, I meant the wiki on the site, not the wiki shipped with Sage. I
> wasn't aware Sage shipped a wiki -- if it does, MoinMoin certainly
> makes sense for that.
Yes, I agree that this is a special case. Even though now I t
2009/1/8 mabshoff :
> On Jan 8, 10:16 am, "Conrad Meyer" wrote:
>> I didn't have a specific
>> replacement in mind, though over at Fedora we recently transitioned
>> from MoinMoin to Mediawiki specifically because MoinMoin was becoming
>> too slow. If you can get MoinMoin to use a database it mig
> Sure, but the fact that moinmoin just works without the need for any
> configuration of a sql database is a killer feature since it might not
> be a problem for some people on this list to set up mysql and so on
> properly, but many, many Sage users will not even know what a sql db
> is and not
On Jan 6, 1:33 am, bsdz wrote:
> Hi,
Hi Blair,
> I dabbled a little with the vmware version of Sage and was able to
> install EditArea, a javascript syntax highlighting library
> (http://www.cdolivet.net/index.php?page=editArea). It is quite useful when
> editing Python and can be turned on
On Jan 7, 7:05 pm, "David Joyner" wrote:
> On Wed, Jan 7, 2009 at 6:59 PM, Jason Grout
> wrote:
>
> > Hi everyone,
>
> > There was another request on sage-edu for a nice way to edit text cells
> > in the notebook. Patches which enable a very nice in-place wysiwyg
Hi David,
> Just to emphas
On Jan 8, 10:16 am, "Conrad Meyer" wrote:
> 2009/1/8 mabshoff :
Hi Conrad,
> Perhaps it's time to upgrade to something that scales better than moinmoin?
>
> > Well, this is not a scalability issue, but a bug. And there is more at
> > play here than scalability, i.e. mediawiki is way more wo
On Jan 8, 10:45 am, adrian wrote:
Hi Adrian,
> Is this only for solaris/x86?
Yes, that binary is 32 bit only, but requires SSE2. The 64 bit version
should be coming soon, i.e. around Sage 3.4 since it requires touching
a lot of spkg build scripts and I plan to do some more cleanups on the
wa
Is this only for solaris/x86?
Is there a version working for solaris/sparc?
Thanks.
-Adrian.
On Jan 8, 4:10 am, mabshoff wrote:
>
>
> > A same session - up until now this would just hang before twisted even
> > started up. I will post a binary for 32 bit SSE2 Solaris 10 binary
> > soon - so ke
2009/1/8 mabshoff :
>
>
>
> On Jan 8, 9:43 am, "Conrad Meyer" wrote:
>
>
>
> Hi,
>
>> Perhaps it's time to upgrade to something that scales better than moinmoin?
>
> Well, this is not a scalability issue, but a bug. And there is more at
> play here than scalability, i.e. mediawiki is way more wo
On Jan 8, 8:13 am, "William Stein" wrote:
> On Thu, Jan 8, 2009 at 1:21 AM, mabshoff wrote:
>
> > Hi,
>
> > the Sage wiki is down for now again since it has been acting up again
> > by consuming up to 23 GB RAM, i.e. pushing itself up to 16 GB into
> > swap. I am not sure what happens, but onc
On Jan 8, 9:43 am, "Conrad Meyer" wrote:
Hi,
> Perhaps it's time to upgrade to something that scales better than moinmoin?
Well, this is not a scalability issue, but a bug. And there is more at
play here than scalability, i.e. mediawiki is way more work to set up
and keep up to date securi
2009/1/8 mabshoff :
>
> Hi,
>
> the Sage wiki is down for now again since it has been acting up again
> by consuming up to 23 GB RAM, i.e. pushing itself up to 16 GB into
> swap. I am not sure what happens, but once it happens all the sudden
> it consumes about 0.1% of the available RAM *per* seco
On Thu, Jan 8, 2009 at 1:21 AM, mabshoff wrote:
>
> Hi,
>
> the Sage wiki is down for now again since it has been acting up again
> by consuming up to 23 GB RAM, i.e. pushing itself up to 16 GB into
> swap. I am not sure what happens, but once it happens all the sudden
> it consumes about 0.1% of
> A same session - up until now this would just hang before twisted even
> started up. I will post a binary for 32 bit SSE2 Solaris 10 binary
> soon - so keep an eye on the main Solaris porting page at
>
> http://wiki.sagemath.org/solaris
The wiki is flaky at the moment, it is up, but I might
Hi,
the Sage wiki is down for now again since it has been acting up again
by consuming up to 23 GB RAM, i.e. pushing itself up to 16 GB into
swap. I am not sure what happens, but once it happens all the sudden
it consumes about 0.1% of the available RAM *per* second. I have
pinged #moinmoin and h
Hi,
I finally fixed the main usability bug in Sage on Solaris, i.e that
the notebook was completely busted. It turned out to be an issue
libgcrypt, but all details are at
http://wiki.sagemath.org/solaris/sage-3.2.3
A same session - up until now this would just hang before twisted even
started
29 matches
Mail list logo
