[sage-devel] Re: backwards compatibility of sage 4.1.2 format
I've made the following experiment: * uncompress a sws file from sage 4.1.2 * rename worksheet.html into worksheet.txt * compress it again * open with sage 4.1 It basically worked. Of course the new pickle file is not used, but the core of the page remains. The output may be lost but we can evaluate all cells. Any thoughts? --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: help with notebook i18n
On Wed, 21 Oct 2009 at 04:46PM +0900, Dan Drake wrote: I was inspired by the Korean translation of the notebook to try and get internationalization (i18n) support into the notebook. I got a good start on figuring out what to do, but I'm a bit stuck and I need some help. I have some stuff working, but right now, utf-8 strings in the notebook don't work and I'm not sure what's wrong. If you'd like to work on this, you can download the tarball at http://sagenb.kaist.ac.kr/~drake/sagenb-with-gettext.tar.bz2 and use it to replace $SAGE_ROOT/local/lib/python/site-packages/sagenb. You'll need 4.2.alpha0 or 4.1.2 with Jinja2 installed. Then run the notebook and try things until something breaks. The above tarball is just a rough draft, really just messing around to see how to get stuff working, so my modifications are a bit random and messy. William asked me to post a bit more about what goes wrong. If you grab the above tarball and drop it into the site-packages directory, you should be able to run the notebook as usual. You'll notice some new bits on the front notebook page -- those are translated strings that are getting correctly pulled in via gettext. Log into the notebook as usual, and you'll see the sign out string is also translated. The problem occurs when you try to print non-ascii text in a worksheet. If you open a worksheet and execute a cell like print 'Français' the server either gets stuck in an infinite loop, or just won't render the page. The traceback looks something like this: File /scratch/drake/sage-4.2.alpha0-x86_64-Linux/local/lib/python2.6/site-packages/sagenb/notebook/twist.py, line 1469, in render self.worksheet.sage() File /scratch/drake/sage-4.2.alpha0-x86_64-Linux/local/lib/python2.6/site-packages/sagenb/notebook/worksheet.py, line 2933, in sage self.initialize_sage() File /scratch/drake/sage-4.2.alpha0-x86_64-Linux/local/lib/python2.6/site-packages/sagenb/notebook/worksheet.py, line 2911, in initialize_sage self._enqueue_auto_cells() File /scratch/drake/sage-4.2.alpha0-x86_64-Linux/local/lib/python2.6/site-packages/sagenb/notebook/worksheet.py, line 3337, in _enqueue_auto_cells for c in self.cell_list(): File /scratch/drake/sage-4.2.alpha0-x86_64-Linux/local/lib/python2.6/site-packages/sagenb/notebook/worksheet.py, line 2651, in cell_list self.set_body(open(worksheet_html).read()) File /scratch/drake/sage-4.2.alpha0-x86_64-Linux/local/lib/python2.6/site-packages/sagenb/notebook/worksheet.py, line 2137, in set_body self.edit_save(body) File /scratch/drake/sage-4.2.alpha0-x86_64-Linux/local/lib/python2.6/site-packages/sagenb/notebook/worksheet.py, line 2279, in edit_save C.set_output_text(output, '') File /scratch/drake/sage-4.2.alpha0-x86_64-Linux/local/lib/python2.6/site-packages/sagenb/notebook/cell.py, line 1348, in set_output_text self.__out = unicode(output) exceptions.UnicodeDecodeError: 'ascii' codec can't decode byte 0xed in position 1: ordinal not in range(128) I've messed around in cell.py, trying to get all the strings to be Unicode objects, but haven't met with any success. In the regular notebook, I get no trouble with things like print 'Français', so something about the gettext'ed code is wonky, but I'm not sure what. If you want to work on this, the Sage tree in /scratch/drake/sage-4.2.alpha0-x86_64-Linux on sage.math has my changes in it. Thanks for any help, Dan -- --- Dan Drake - http://mathsci.kaist.ac.kr/~drake --- signature.asc Description: Digital signature
[sage-devel] Re: backwards compatibility of sage 4.1.2 format
On Wed, Oct 21, 2009 at 12:52 AM, Pablo Angulo pablo.ang...@uam.es wrote: I've made the following experiment: * uncompress a sws file from sage 4.1.2 * rename worksheet.html into worksheet.txt * compress it again * open with sage 4.1 It basically worked. Of course the new pickle file is not used, but the core of the page remains. The output may be lost but we can evaluate all cells. Any thoughts? The above makes sense. It sounds like I should change the sws format in the soon to be released sage-4.2 so that it is backwards compatible. I'll likely do that right now. -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Category review: what's the category of a category?
Hi! In Sage 4.1, the category of a category was changed from Objects() to Sets(). I.e. we used to have: sage: Groups().category() Category of objects And now we have: sage: Groups().category() Category of sets Was there any rationale for this? The former sounds more natural to me, in particular because the objects of Sets() are exactly the parents. If you agree with reverting this, please put a positive review on the otherwise trivial ticket #7259. Thanks in advance! Nicolas Sorry Mike: I had forgotten to mention this patch in CategoriesRoadMap. -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: backwards compatibility of sage 4.1.2 format
On Wed, Oct 21, 2009 at 1:10 AM, William Stein wst...@gmail.com wrote: On Wed, Oct 21, 2009 at 12:52 AM, Pablo Angulo pablo.ang...@uam.es wrote: I've made the following experiment: * uncompress a sws file from sage 4.1.2 * rename worksheet.html into worksheet.txt * compress it again * open with sage 4.1 It basically worked. Of course the new pickle file is not used, but the core of the page remains. The output may be lost but we can evaluate all cells. Any thoughts? The above makes sense. It sounds like I should change the sws format in the soon to be released sage-4.2 so that it is backwards compatible. I'll likely do that right now. Yes, this worked easily. There is now a patch posted here: http://trac.sagemath.org/sage_trac/ticket/7261 -- William --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: backwards compatibility of sage 4.1.2 format
The page title is also a bit different: The old sage 4.1 format started with: -- page title system:sage h1content... -- while the new one takes the title from somewhere else and starts directly with content. Then when a sage 4.1.2 worksheet.html is renamed into worksheet.txt and opened in sage=4.1.1, the first line becomes the title and disappears from the content. How would the new format in sage 4.2 be? Which would be the compatibility diagram? Do you think the following is possible?: sage =4.1.1: reads 4.2 but not 4.1.2 sage 4.1.2: reads =4.1.1 and 4.2 sage 4.2: reads =4.1.1 and 4.1.2 We're performing an installation right now for 40 computers and that information would be very interesting. Thanks! --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: backwards compatibility of sage 4.1.2 format
Oh, I see in your patch you've taken care of the title. --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: sage-4.1.2 and sage-4.2
On Oct 20, 10:30 pm, Georg S. Weber georgswe...@googlemail.com wrote: @Harald, Minh, William: Could you upload Marshall's binary to the usual download place? yes, i'll do it. Next time please email me directly ... so that i don't miss it ;) H --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: backwards compatibility of sage 4.1.2 format
On Wed, Oct 21, 2009 at 2:30 AM, Pablo Angulo pablo.ang...@uam.es wrote: Oh, I see in your patch you've taken care of the title. If you want to very easily try this new code (and everything else we've done improving the new notebook in the last few days), just do this: sage -i http://wstein.org/home/wstein/patches/sagenb/sagenb-0.3.5.spkg If that causes problems, you can switch back with sage f sagenb-0.3.spkg -- William --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
Re: [sage-combinat-devel] Re: [sage-devel] Re: [Cython] LiE in Cython
Dear Dan, Marc, David, Steve, Mike, ... On Tue, Oct 20, 2009 at 09:53:01AM -0700, Daniel Bump wrote: By the way: what's the status of this spkg? Is there some documentation somewhere of what can be done with it from Sage? (I just tried lie-2.2.2.p3 but it does not seem compile on my 32bits i686 ubuntu box). William Stein has stated that LiE would not be made a standard package because it is no longer supported. See: http://groups.google.com/group/sage-devel/msg/613cc5aa78c89f3d?hl=en My belief is that this is the right decision and that the functionality in LiE should be redone natively in sage. It can do quite a few things and people have found it very useful. Dan: Thanks for sharing your view on this! Marc: what is your opinion? By the way: we are organizing Sage days 20 at CIRM at the end of February with combinatorics as main theme. We will update the web page soon: http://www.lirmm.fr/arith/wiki/MathInfo2010/SageDays. But unofficially, I can already tell that root systems and friends are one of the main themes. In particular, we will host at least one Chevie developer (M. Geck) and with some chances A. Mathas and C. Hohlweg will join as well. Marc: would you be willing to join and offer us insight on how best to integrate / reuse / port / reimplement or otherwise recycle the features in LiE, and coordinate with the LiE community? David: you would be most welcome as well! One important thing LiE can do is to compute Kazhdan-Lusztig polynomials. However it is slow and can't get much past around B3. Coxeter3 is a better program for this. KL polynomials are quite important and it should be a priority to get them in Sage. When I needed them I wrote my own routines, but only for type A. Before KL Polynomials can be implemented Bruhat order must be implemented in Sage. The root system patch does not do this. Currently Bruhat order is in Sage but only for Type A. I think a good way to give a fast recusive definition would be to use Proposition 1.1 in Stembridge, A Short Derivation of the Möbius Function for the Bruhat Order, Journal of Algebraic Combinatorics 25, (2007). Thanks to Steve, the Bruhat poset for all (finite) types has been in the Sage-Combinat queue since May or June. With root_systems-bruhat_order-nt.patch and preferably weyl_group_optimizations-nt.patch, you can do things like: sage: W = WeylGroup([D, 4]) sage: B = W.bruhat_poset() sage: u = B[0] sage: v = B[50] sage: B.mobius_function(u,v) -1 Everything is based on the following recursive implementation of lower covers for Bruhat order, which also works for infinite groups, and uses the same approach as Stembridge's implementation (so I assume as in his paper): @cached_in_parent_method def bruhat_lower_covers(self): desc = self.first_descent() if desc is not None: ww = self.apply_simple_reflection(desc) return [u.apply_simple_reflection(desc) for u in ww.bruhat_lower_covers() if not u.has_descent(desc)] + [ww] else: return [] (by the way: Steve: could you add a ref to Stembridge's paper in the doc, and use `descent` rather than `desc`?) And with #7004 (also in the queue) + graphviz + the dot2tex spkg, you can further do: sage: G = B.hasse_diagram() sage: G.set_latex_options(format=dot2tex) sage: view(G, tightpage = True, pdflatex=True) There are still lots of rough corners, so this won't be integrated instantly into Sage. It also badly needs further optimizations in CombinatorialFreeModules, Weyl groups, ... Kazhdan-Lusztig polynomials can be computed quickly if one is willing to cache a large number of results. If one just caches everything computed, the main limitation is the size of the Weyl group. Coxeter3 takes a more intelligent approach by deciding carefully what to cache. Using Coxeter3 sounds definitely like the way to go for KL. Thanks Mike for your work on that! Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[marc.van-leeu...@math.univ-poitiers.fr: Re: [sage-combinat-devel] Re: [sage-devel] Re: [Cython] LiE in Cython]
Please find below a first answer from Marc van Leeuwen who is travelling abroad and can't yet post to the mailing lists. - Forwarded message from Marc van Leeuwen marc.van-leeu...@math.univ-poitiers.fr - Quoting Daniel Bump b...@match.stanford.edu: William Stein has stated that LiE would not be made a standard package because it is no longer supported. See: http://groups.google.com/group/sage-devel/msg/613cc5aa78c89f3d?hl=en Just for the record I should like to correct that to say it is no longer being developed, but it is still supported. You can address any bug reports to me, and I will correct them. That this hasn't happened for more than a decade doesn't imply that LiE is no longer working, rather to the contrary (and it even computes quite a bit faster than it used to;-). Anyone know when was the last change to the core TeX program? My belief is that this is the right decision and that the functionality in LiE should be redone natively in sage. I can agree with that, if you can find someone to do it. I presume it is quite a it of work, but it may help that the mathematically relevant part is well separated from the rest, and almost completely done in Literate Programming. It can do quite a few things and people have found it very useful. One important thing LiE can so is to compute Kazhdan-Lusztig polynomials. However it is slow and can't get much past around B3. Here I agree; in fact doing Kazhdan-Lusztig polynomials does not blend well with the design of LiE where almost no information retained between computations. I was in fact against including these half-hearted procedures in LiE, but they were done anyway. Coxeter3 is a better program for this. KL polynomials are quite important and it should be a priority to get them in Sage. When I needed them I wrote my own routines, but only for type A. Before KL Polynomials can be implemented Bruhat order must be implemented in Sage. The root system patch does not do this. Currently Bruhat order is in Sage but only for Type A. I think a good way to give a fast recusive definition would be to use Proposition 1.1 in Stembridge, A Short Derivation of the Möbius Function for the Bruhat Order, Journal of Algebraic Combinatorics 25, (2007). Coxeter does KL Polynomials using the Bruhat order, and this is important for doing things like infinite Coxeter groups. Computing this order is not absolutely essential though; one can set up the recursion without knowing the Bruhat order beforehand, and find out what it is as result of the computation, with as main drawback that one is sometimes adding zeroes that could have been predicted if the Bruhat order had been known. Atlas works this way for computing the more general KLV polynomials, which is more or less inevitable because there is not really a clear Bruhat order around in its setting (an order can be defined, but it does not precisely predict the support of the KLV polynomials). Kazhdan-Lusztig polynomials can be computed quickly if one is willing to cache a large number of results. If one just caches everything computed, the main limitation is the size of the Weyl group. Coxeter3 takes a more intelligent approach by deciding carefully what to cache. My understanding is that apart from polynomials that are immediate copies of other ones, it is more or less imperative to cache everything computed or else computation time increases exponentially. Coxeter3 however is more intelligent in not insisting (like atlas does) that every KL polynomial be computed if any one of them needed, which makes doing infinite groups possible. -- Marc van Leeuwen Dear Dan, Marc, David, Steve, Mike, ... On Tue, Oct 20, 2009 at 09:53:01AM -0700, Daniel Bump wrote: By the way: what's the status of this spkg? Is there some documentation somewhere of what can be done with it from Sage? (I just tried lie-2.2.2.p3 but it does not seem compile on my 32bits i686 ubuntu box). William Stein has stated that LiE would not be made a standard package because it is no longer supported. See: http://groups.google.com/group/sage-devel/msg/613cc5aa78c89f3d?hl=en My belief is that this is the right decision and that the functionality in LiE should be redone natively in sage. It can do quite a few things and people have found it very useful. Dan: Thanks for sharing your view on this! Marc: what is your opinion? By the way: we are organizing Sage days 20 at CIRM at the end of February with combinatorics as main theme. We will update the web page soon: http://www.lirmm.fr/arith/wiki/MathInfo2010/SageDays. But unofficially, I can already tell that root systems and friends are one of the main themes. In particular, we will host at least one Chevie developer (M. Geck) and with some chances A. Mathas and C. Hohlweg will join as well. Marc: would you be willing to join and offer us insight on how best to integrate / reuse / port / reimplement or
[sage-devel] Integration / migration of LiE in Sage
- Forwarded message from Marc van Leeuwen marc.van-leeu...@math.univ-poitiers.fr - Quoting Daniel Bump b...@match.stanford.edu: William Stein has stated that LiE would not be made a standard package because it is no longer supported. See: http://groups.google.com/group/sage-devel/msg/613cc5aa78c89f3d?hl=en Just for the record I should like to correct that to say it is no longer being developed, but it is still supported. You can address any bug reports to me, and I will correct them. That this hasn't happened for more than a decade doesn't imply that LiE is no longer working, rather to the contrary (and it even computes quite a bit faster than it used to;-). Anyone know when was the last change to the core TeX program? Great. I was very much hoping for such an answer :-) My belief is that this is the right decision and that the functionality in LiE should be redone natively in sage. I can agree with that, if you can find someone to do it. I presume it is quite a it of work, but it may help that the mathematically relevant part is well separated from the rest, and almost completely done in Literate Programming. Ok. There is no real rush, but it sounds like we should all meet at some point to discuss the best integration-migration roadmap; on the feature side, the adaptation of Chapter 4 of the LiE manual to Sage is a great basis for this road map. Then, we could start with a documented interface between LiE and Sage. Later, if there is a clear roadmap to be followed, one can plan that the Sage developers involved in the root system stuff will progressively integrate/port the material on a need-driven basis. David: would you by any chance be interested in taking over the maintenance of the LiE package for Sage, and integrate there your Cython interface? As far as I can tell, the current minimal version was created a while ago by William and Michael. It should not be that much work, especially with Marc's support in case of technical issue with LiE. Feel free to ask for more details about Sage packages, but you can start with: - http://www.sagemath.org/doc/developer/producing_spkgs.html - http://sagemath.org/packages/optional/lie-2.2.2.p3.spkg Best regards, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: backwards compatibility of sage 4.1.2 format
I have to agree on that. A double point upgrade should mainly be bug fixes, I think. It would have made more sense to make this 4.2. -Marshall On Oct 20, 11:25 am, Nick Alexander ncalexan...@gmail.com wrote: I am not passionate about this issue, but: why was such a large made from 4.1.1 - 4.1.2? Not even a point upgrade (4.1 - 4.2), but a double point upgrade destroys backwards compatibility? I question this decision. Nick --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: sage-4.1.2 and sage-4.2
Just a datapoint that might provide useful feedback for those who are trying to make binary installs a smooth experience: I tried to install 4.1.2 on a Fedora 10 (i686) laptop. I tried both the Fedora 9 and the Fedora 11 image. With either I got errors: ImportError: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by lib.so) doing a sage -f ... for the package that provides lib.so solved that problem, but then the next C++ library would play up. I ended up getting stranded on: local/lib/python2.6/site-packages/sage/combinat/partitions.so for which I was not readily able to determine which spkg to install. It may just be that F9/F10/F11 is a particularly active time of libstdc ++ development. However, it gave me the impression that binary distributions of sage are very fragile. It's good that there is always the source fall-back option, but the prospect of having my laptop churn for 2 hours to produce an upgrade actually put me off upgrading for now. If this is a more common problem, how difficult is it to have a list of c++ spkgs so that libstd++ problems can be solved by recompiling those? Or are there so many that you might as well do a source install? --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] target=_blank when opening worksheet
In case anyone is interested, here is a quick patch to get rid of that
annoying behavior of the notebook that creates a new Active Worksheets
tab every time I close a worksheet.
Warning: William said that this behaviour is intended to avoid
massive corruption but it is not clear to me how opening worksheets
in new tabs would prevent that. In any case I always click Discard
quit instead of the browser back button.
sage subshell$ hg diff
diff -r 5bf36a37cd0c sage/server/notebook/templates/worksheet_listing.html
--- a/sage/server/notebook/templates/worksheet_listing.html Wed Oct 14
14:43:41 2009 -0700
+++ b/sage/server/notebook/templates/worksheet_listing.html Wed Oct 21
12:43:55 2009 -0400
@@ -151,7 +151,7 @@
/td
td class=worksheet_link
- a title={{ worksheet.name() | escape }} id=name/{{ name }}
class=worksheetname target=_blank href=/home/{{ name }}
+ a title={{ worksheet.name() | escape }} id=name/{{ name }}
class=worksheetname target=_self href=/home/{{ name }}
{% if worksheet.compute_process_has_been_started() %}(running) {% endif
%}
{{ worksheet.truncated_name(35) | escape}}
/a
/home/wspage/sage-4.1.2
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: target=_blank when opening worksheet
On Wed, Oct 21, 2009 at 9:55 AM, Bill Page bill.p...@newsynthesis.org wrote:
In case anyone is interested, here is a quick patch to get rid of that
annoying behavior of the notebook that creates a new Active Worksheets
tab every time I close a worksheet.
Warning: William said that this behaviour is intended to avoid
massive corruption but it is not clear to me how opening worksheets
in new tabs would prevent that. In any case I always click Discard
quit instead of the browser back button.
Even better -- if you try
http://sage.math.washington.edu/home/wstein/patches/sagenb/sagenb-0.3.5.spkg
then you'll get the newest testing version of the notebook, which (1)
doesn't have the opens in a new window behavior, and (2) has automatic
synchronization! I.e., if you use the back button, or open a
worksheet in two tabs, etc., then changing it in one, changes it in
the other.Try it out.
And Bill, thanks -- welcome to being a notebook developer!!
William
sage subshell$ hg diff
diff -r 5bf36a37cd0c sage/server/notebook/templates/worksheet_listing.html
--- a/sage/server/notebook/templates/worksheet_listing.html Wed Oct 14
14:43:41 2009 -0700
+++ b/sage/server/notebook/templates/worksheet_listing.html Wed Oct 21
12:43:55 2009 -0400
@@ -151,7 +151,7 @@
/td
td class=worksheet_link
- a title={{ worksheet.name() | escape }} id=name/{{ name }}
class=worksheetname target=_blank href=/home/{{ name }}
+ a title={{ worksheet.name() | escape }} id=name/{{ name }}
class=worksheetname target=_self href=/home/{{ name }}
{% if worksheet.compute_process_has_been_started() %}(running) {%
endif %}
{{ worksheet.truncated_name(35) | escape}}
/a
/home/wspage/sage-4.1.2
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: sage-4.1.2 and sage-4.2
On Wed, Oct 21, 2009 at 8:38 AM, Nils Bruin nbr...@sfu.ca wrote: Just a datapoint that might provide useful feedback for those who are trying to make binary installs a smooth experience: I tried to install 4.1.2 on a Fedora 10 (i686) laptop. I tried both the Fedora 9 and the Fedora 11 image. With either I got errors: ImportError: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by lib.so) doing a sage -f ... for the package that provides lib.so solved that problem, but then the next C++ library would play up. I ended up getting stranded on: local/lib/python2.6/site-packages/sage/combinat/partitions.so for which I was not readily able to determine which spkg to install. It may just be that F9/F10/F11 is a particularly active time of libstdc ++ development. However, it gave me the impression that binary distributions of sage are very fragile. It's good that there is always the source fall-back option, but the prospect of having my laptop churn for 2 hours to produce an upgrade actually put me off upgrading for now. If this is a more common problem, how difficult is it to have a list of c++ spkgs so that libstd++ problems can be solved by recompiling those? Or are there so many that you might as well do a source install? Would you be willing to test taking a fresh install of the fedora 11 binary and dropping libstdc++ from Fedora 11 (etc.) into your local/bin/? For a very long time, with Sage we *distributed* a bunch of libstdc++ files with the binary. Maybe a combination of that with some instructions like you mention bight be the best option. Linux is a such an exciting challenge when it comes to making binaries. -- William --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: sage-4.1.2 and sage-4.2
On Wed, Oct 21, 2009 at 10:08 AM, William Stein wst...@gmail.com wrote: On Wed, Oct 21, 2009 at 8:38 AM, Nils Bruin nbr...@sfu.ca wrote: Just a datapoint that might provide useful feedback for those who are trying to make binary installs a smooth experience: I tried to install 4.1.2 on a Fedora 10 (i686) laptop. I tried both the Fedora 9 and the Fedora 11 image. With either I got errors: ImportError: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by lib.so) doing a sage -f ... for the package that provides lib.so solved that problem, but then the next C++ library would play up. I ended up getting stranded on: local/lib/python2.6/site-packages/sage/combinat/partitions.so for which I was not readily able to determine which spkg to install. It may just be that F9/F10/F11 is a particularly active time of libstdc ++ development. However, it gave me the impression that binary distributions of sage are very fragile. It's good that there is always the source fall-back option, but the prospect of having my laptop churn for 2 hours to produce an upgrade actually put me off upgrading for now. If this is a more common problem, how difficult is it to have a list of c++ spkgs so that libstd++ problems can be solved by recompiling those? Or are there so many that you might as well do a source install? Would you be willing to test taking a fresh install of the fedora 11 binary and dropping libstdc++ from Fedora 11 (etc.) into your local/bin/? For a very long time, with Sage we *distributed* a bunch of libstdc++ files with the binary. Maybe a combination of that with some instructions like you mention bight be the best option. Linux is a such an exciting challenge when it comes to making binaries. Check out the VirtualBox binary download page for Linux: http://www.virtualbox.org/wiki/Linux_Downloads There are 39 distinct binaries listed there: * Ubuntu 9.10 (Karmic Koala) i386 | AMD64 * Ubuntu 9.04 (Jaunty Jackalope) i386 | AMD64 * Ubuntu 8.10 (Intrepid Ibex) i386 | AMD64 * Ubuntu 8.04 LTS (Hardy Heron) i386 | AMD64 * Debian 5.0 (Lenny) i386 | AMD64 * Debian 4.0 (Etch) i386 | AMD64 * openSUSE 11.1 i386 | AMD64 * openSUSE 11.0 i386 | AMD64 * openSUSE 10.3 i386 | AMD64 * SUSE Linux Enterprise Server 10 (SLES10) i386 | AMD64 * Fedora 12 (Constantine) i386 | AMD64 * Fedora 11 (Leonidas) i386 | AMD64 * Fedora 9 (Sulphur) / 10 (Cambridge) i386 | AMD64 * Fedora 8 (Werewolf) i386 | AMD64 * Mandriva 2009.1 i386 | AMD64 * Mandriva 2008.0 i386 * Red Hat Enterprise Linux 5 (RHEL5) / CentOS 5 i386 | AMD64 * Red Hat Enterprise Linux 4 (RHEL4) / CentOS 4 i386 * Turbolinux 11 i386 | AMD64 * PCLinuxOS 2007 i386 * All distributions i386 | AMD64 Opera is similar. If these guys don't have a better solution, then probably this is simply the sort of thing that is *demanded* by distributing nontrivial binary software for Linux. I am not opposed to trying to target making binaries for far more system, if we get organized and work together. It's just a matter of making VirtualBox machines that have g++, make, m4, gcc, installed into them. I like them to also have a /tmp that has at least 32GB free disk space on it. I think we could support building 30-40 binaries on our current rather powerful hardware resources. The main issue is the workload of creating all these VirtualBox virtual machines. I don't want to do it all myself! William --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] including @interact examples in documentation
(Yet again) I tried to pull up an @interact from the wiki and it didn't work because it had not been updated to keep up with the changes to syntax in Sage. Are there any objections to making a file of the @interact examples so that it is easy to spot when they need to be updated through normal doctesting? Thanks, Jason --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: target=_blank when opening worksheet
William, On Wed, Oct 21, 2009 at 1:04 PM, you wrote: Even better -- if you try http://sage.math.washington.edu/home/wstein/patches/sagenb/sagenb-0.3.5.spkg then you'll get the newest testing version of the notebook, which (1) doesn't have the opens in a new window behavior, and (2) has automatic synchronization! I.e., if you use the back button, or open a worksheet in two tabs, etc., then changing it in one, changes it in the other. Cool. Try it out. Since the notebook is now an spkg is $ wget http://sage.math.washington.edu/home/wstein/patches/sagenb/sagenb-0.3.5.spkg $ ./sage -f sagenb-0.3.5.spkg sufficient? And Bill, thanks -- welcome to being a notebook developer!! Well I have to admit the I am becoming kind of dependent on it - necessity being my mother and all ... ;-) Thank you. Regards, Bill Page. --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: including @interact examples in documentation
On Oct 21, 2:54 pm, Jason Grout jason-s...@creativetrax.com wrote: (Yet again) I tried to pull up an @interact from the wiki and it didn't work because it had not been updated to keep up with the changes to syntax in Sage. Are there any objections to making a file of the @interact examples so that it is easy to spot when they need to be updated through normal doctesting? What a great idea. Tons of interacts are broken (not really, but have annoying error messages) because of the deprecation of function- call syntax... It could have a role similar to wester.py in sage/ calculus/, but for interact. Thanks for volunteering! - kcrisman --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: including @interact examples in documentation
On Wed, Oct 21, 2009 at 11:54 AM, Jason Grout jason-s...@creativetrax.com wrote: (Yet again) I tried to pull up an @interact from the wiki and it didn't work because it had not been updated to keep up with the changes to syntax in Sage. Are there any objections to making a file of the @interact examples so that it is easy to spot when they need to be updated through normal doctesting? How would it work? What would you put in the file. I think it would be much better to make a while directory in the main Sage tree of examples, along with an organized namespace, e.g., something like sage: interacts.tab sage: interacts.calculus.tab sage: interacts.calculus.derivative() up pops the interact Regarding doctesting, that may require some extension to how interact works? I.e., some special function like sage: interacts.calculus.derivative.test() that would do something clever. I've always planned to do something like the above since when I first wrote interact, but I never found the time. William Thanks, Jason -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] notebook() changes the working directory
This has been true in Sage for a long time, and I've always found it mildly annoying: $ cd /some/random/directory $ sage -- | Sage Version 4.2.alpha0, Release Date: 2009-10-16 | | Type notebook() for the GUI, and license() for information.| -- sage: pwd '/some/random/directory' sage: notebook() let the notebook start up, then hit ctrl-c sage: pwd '/Users/palmieri/.sage' How hard would it be to change this? John --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: notebook() changes the working directory
On Wed, Oct 21, 2009 at 12:28 PM, John H Palmieri jhpalmier...@gmail.com wrote: This has been true in Sage for a long time, and I've always found it mildly annoying: $ cd /some/random/directory $ sage -- | Sage Version 4.2.alpha0, Release Date: 2009-10-16 | | Type notebook() for the GUI, and license() for information. | -- sage: pwd '/some/random/directory' sage: notebook() let the notebook start up, then hit ctrl-c sage: pwd '/Users/palmieri/.sage' How hard would it be to change this? Trivial. I didn't even know about this bug. Thanks for pointing it out!! William --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Category review: what's the category of a category?
What about the category of categories (with functors as morphisms)? --David --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: sage-4.1.2 and sage-4.2
On Oct 21, 10:08 am, William Stein wst...@gmail.com wrote: Would you be willing to test taking a fresh install of the fedora 11 binary and dropping libstdc++ from Fedora 11 (etc.) into your local/bin/? $sage_root/local/lib I presume. Sure. Can I get the appropriate libstdc++ from somewhere? Is there an i686 F11 VM accessible from sage.math? I guess one should not recompile any components on a sage install with an overridden system library. --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: sage-4.1.2 and sage-4.2
On Wed, Oct 21, 2009 at 3:07 PM, Nils Bruin nbr...@sfu.ca wrote: On Oct 21, 10:08 am, William Stein wst...@gmail.com wrote: Would you be willing to test taking a fresh install of the fedora 11 binary and dropping libstdc++ from Fedora 11 (etc.) into your local/bin/? $sage_root/local/lib I presume. Yes. Sure. Can I get the appropriate libstdc++ from somewhere? Is there an i686 F11 VM accessible from sage.math? I guess one should not recompile any components on a sage install with an overridden system library. I've posted it here: http://sage.math.washington.edu/home/wstein/tmp/fedora11/ William --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: including @interact examples in documentation
William Stein wrote: On Wed, Oct 21, 2009 at 11:54 AM, Jason Grout jason-s...@creativetrax.com wrote: (Yet again) I tried to pull up an @interact from the wiki and it didn't work because it had not been updated to keep up with the changes to syntax in Sage. Are there any objections to making a file of the @interact examples so that it is easy to spot when they need to be updated through normal doctesting? How would it work? What would you put in the file. I think it would be much better to make a while directory in the main Sage tree of examples, along with an organized namespace, e.g., something like sage: interacts.tab sage: interacts.calculus.tab sage: interacts.calculus.derivative() up pops the interact Regarding doctesting, that may require some extension to how interact works? I.e., some special function like sage: interacts.calculus.derivative.test() that would do something clever. Nice idea! As things are right now, if I define an interact function interacts.calculus.vector_motion_2d then someone could call it up by: interact(interacts.calculus.vector_motion_2d) (except that it would also then return the function object, which is kind of ugly at the end of the output) I agree that having a function which tests interacts would be nice. Things could be automated a bit by having an interact control having a random_value method which generates a random value for the control. Then the interact_test function would just construct the appropriate interact control for each argument of a function, ask for a random value, and then pass those random values into the function. I'm not sure exactly what your suggestion for a place for code was, but reading your answer above and replacing while with whole, I agree that a new directory is called for. Shall we call it interacts, or a more general name like examples? Thanks, Jason --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Jmol in 4.1.2
On Wed, Oct 21, 2009 at 8:54 AM, kcrisman kcris...@gmail.com wrote:
Dear sage-devel,
I'm having trouble with jmol from the command line in 4.1.2 and
4.2.alpha0. E.g.,
sage: var('A,B,C')
(A, B, C)
sage: implicit_plot3d(sin(A)*cos(B)+sin(B)*cos(C)+sin(C)*cos(A),
(A,-2*pi,2*pi),(B,-2*pi,2*pi),(C,-2*pi,2*pi))
does nothing. Adding .show() also fails, and quicker. On
alpha.sagenb.org I don't have the same problems (though sometimes I
get the featureless black box), so I think it may be a command-line
issue. Any ideas? I do NOT get this in 4.1.1. I am on a MacIntel
running OSX 10.5.
I've replicated this: http://trac.sagemath.org/sage_trac/ticket/7263
Basically all jmol 3d plotting at the command line is totally broken
right now on all platforms. Not good.
William
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: target=_blank when opening worksheet
On Wed, Oct 21, 2009 at 12:00 PM, Bill Page bill.p...@newsynthesis.org wrote: William, On Wed, Oct 21, 2009 at 1:04 PM, you wrote: Even better -- if you try http://sage.math.washington.edu/home/wstein/patches/sagenb/sagenb-0.3.5.spkg then you'll get the newest testing version of the notebook, which (1) doesn't have the opens in a new window behavior, and (2) has automatic synchronization! I.e., if you use the back button, or open a worksheet in two tabs, etc., then changing it in one, changes it in the other. Cool. Try it out. Since the notebook is now an spkg is $ wget http://sage.math.washington.edu/home/wstein/patches/sagenb/sagenb-0.3.5.spkg $ ./sage -f sagenb-0.3.5.spkg sufficient? Yes. But pleae keep in mind this is an unstable testing release. I think the auto-resynchronize code needs more testing and isn't good enough yet. I may have to disable it for the next sagenb release. It's a really nice idea, but it's very tricky to make work perfectly in all cases. And Bill, thanks -- welcome to being a notebook developer!! Well I have to admit the I am becoming kind of dependent on it - necessity being my mother and all ... ;-) Thank you. Regards, Bill Page. -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: sage-4.1.2 and sage-4.2
I dropped the file into $sageroot/local/lib, made the symbolic link ln -s libstdc++.so.6.0.12 libstdc++.so.6 and ran sage in my by now weird hybrid binary install with a few spkgs compiled from source and, surprisingly, NO ERRORS! So apparently, the locally compiled files run quite happily with the newly provided libstdc++, but not the other way around. Incidentally, fedora 10 has libstdc++.so.6.0.10. I don't understand why the fedora 9 binary didn't work. The libstdc++ for that can't have been more recent than the standard one for F10, right? --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: sage-4.1.2 and sage-4.2
On Wed, Oct 21, 2009 at 7:48 PM, Nils Bruin nbr...@sfu.ca wrote: I dropped the file into $sageroot/local/lib, made the symbolic link ln -s libstdc++.so.6.0.12 libstdc++.so.6 and ran sage in my by now weird hybrid binary install with a few spkgs compiled from source and, surprisingly, NO ERRORS! So apparently, the locally compiled files run quite happily with the newly provided libstdc++, but not the other way around. Incidentally, fedora 10 has libstdc++.so.6.0.10. Did you run make test? I'm curious if everything works. William I don't understand why the fedora 9 binary didn't work. The libstdc++ for that can't have been more recent than the standard one for F10, right? -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: including @interact examples in documentation
On Oct 21, 2009, at 3:13 PM, Jason Grout wrote: William Stein wrote: On Wed, Oct 21, 2009 at 11:54 AM, Jason Grout jason-s...@creativetrax.com wrote: (Yet again) I tried to pull up an @interact from the wiki and it didn't work because it had not been updated to keep up with the changes to syntax in Sage. Are there any objections to making a file of the @interact examples so that it is easy to spot when they need to be updated through normal doctesting? How would it work? What would you put in the file. I think it would be much better to make a while directory in the main Sage tree of examples, along with an organized namespace, e.g., something like sage: interacts.tab sage: interacts.calculus.tab sage: interacts.calculus.derivative() up pops the interact Regarding doctesting, that may require some extension to how interact works? I.e., some special function like sage: interacts.calculus.derivative.test() that would do something clever. That would be cool. Nice idea! As things are right now, if I define an interact function interacts.calculus.vector_motion_2d then someone could call it up by: interact(interacts.calculus.vector_motion_2d) I'd prefer interacts.calculus.vector_motion_2d() to interact(interacts.calculus.vector_motion_2d) - Robert --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: including @interact examples in documentation
Robert Bradshaw wrote: On Oct 21, 2009, at 3:13 PM, Jason Grout wrote: William Stein wrote: On Wed, Oct 21, 2009 at 11:54 AM, Jason Grout jason-s...@creativetrax.com wrote: (Yet again) I tried to pull up an @interact from the wiki and it didn't work because it had not been updated to keep up with the changes to syntax in Sage. Are there any objections to making a file of the @interact examples so that it is easy to spot when they need to be updated through normal doctesting? How would it work? What would you put in the file. I think it would be much better to make a while directory in the main Sage tree of examples, along with an organized namespace, e.g., something like sage: interacts.tab sage: interacts.calculus.tab sage: interacts.calculus.derivative() up pops the interact Regarding doctesting, that may require some extension to how interact works? I.e., some special function like sage: interacts.calculus.derivative.test() that would do something clever. That would be cool. Nice idea! As things are right now, if I define an interact function interacts.calculus.vector_motion_2d then someone could call it up by: interact(interacts.calculus.vector_motion_2d) I'd prefer interacts.calculus.vector_motion_2d() to interact(interacts.calculus.vector_motion_2d) Two comments: (1) as it is now, interacts.calculus.vector_motion_2d(a=1,b=2) would produce usable output with those parameter values (no sliders, but the function would work), so the function is a nice function as well as an interact. (2) interact() does all of its work when it wraps the function, so the interact system would need some tinkering to make your option work, while interact(interacts.calculus.vector_motion_2d) works now. To take care of option 2, it seems like we could either redo some of the interact functionality, or we could define a library_interact decorator that embeds the interact functionality into the function call, rather than the function definition. However, (1) makes me lean towards what I proposed. Does that change your mind? Thanks, Jason -- Jason Grout --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] webMathematica 3 -- mathematica's take on web-based manipulate
Hi, Mathematica released their web-based *manipulate* implementation: http://wolfram.com/products/webmathematica/ There are a few dozen examples. They are now ahead in that they allow for something like our web-based interacts, but without any login required. However, I think our 3d plots are a lot nicer, and the speed of their web-based interacts seems as bad or worse than Sage's (to me, from at home). William -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
