[sage-devel] Re: Mac application licensing question
Can you tell me where the license to fluid is located? I downloaded from http://fluidapp.com/ the zip file. There is a subdirectory for licenses but the fluid license isn't in it only the (BSD-like) licenses for the components. BTW, it appears to be Leopard only and the website says is similar to Mozilla's prism, http://en.wikipedia.org/wiki/Mozilla_Prism, which is open source and cross platform. Have you tried creating something similar with prism? On Fri, Mar 7, 2008 at 2:04 AM, Ivan Andrus <[EMAIL PROTECTED]> wrote: > > > > The following might be acceptable. > > > > (1) The user downloads a Fluid app. > > > > (2) The user downloads a separate sage-2.10.2.dmg (say). > > > > (3) When Fluid app runs it asks for the location of the sage dmg, > > extracts it > > "into itself", and uses that. > > > > Then the combination of Fluid with Sage only happens after the user > > installs > > the programs, so it doesn't violate the GPL in letter. Also > > sage-2.10.2.dmg > > also works by itself, and decoupling Fluid and sage-*dmg will make > > it so > > people can easily upgrade sage without you having to make a new sage > > +fluid > > application. Is this possible? > > That would be possible (isn't anything) but would be much different > than now, since it would require some sort of user interface to be > written to do that. I think at that point I may as well start from > scratch with a brand new application. That's probably the best thing > anyway, but I'm not sure that I am up to it at the moment. I can't > even seem to find time to get this working. > > > > > Could you post a version somewhere so I can try it out? > > > I have also uploaded > > http://wiki.sagemath.org/SageMacApplication?action=AttachFile&do=get&target=Sage-fluid.zip > which does not include a copy of sage. It does contain a script that > I use to combine the sage fluid-app and the sage distribution. All > you have to do is put a sage directory (as off of a .dmg from > sagemath.org) in the same folder and run make-sage-app.sh. This is > not how I would like to distribute it ideally, but on the other hand, > it may be better than what we have right now. > > I don't think the fact that I include the "source code" for the Fluid- > derived app (i.e. the fact that I typed http://localhost:8000/ into a > dialog) will satisfy RMS's raging zombies of freedom. I do have a > completely packaged version and would like to distribute it, but think > that it's probably not legal to do so. I would really rather not get > in any trouble. > If anyone wants > > I am also looking into adding a browser to Platypus. I think that may > be a superior solution, but it will undoubtedly be more work. > > On a slightly different note, does it count as distributing it if I > only give it to a friend? In other words does distributing mean > giving it to anyone, or just making it public? Surely, it must mean > the latter? > > -Ivan Andrus > > > > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: symbolic logic code
Wow, I had no idea that was even a possibility:) Thanks for pointing that out to me. -Chris Gorecki --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Mac application licensing question
> Can you tell me where the license to fluid is located? I downloaded > from http://fluidapp.com/ the zip file. There is a subdirectory for > licenses but the fluid license isn't in it only the (BSD-like) licenses for > the components. Actually the README.txt is probably as close as you will get. I don't know where the license is. There may not even be one. For some reason that never bothered me until now. :-( > BTW, it appears to be Leopard only and the website says is similar to > Mozilla's prism, http://en.wikipedia.org/wiki/Mozilla_Prism, > which is open source and cross platform. Have you tried creating something > similar with prism? Yes, it is Leopard only. I couldn't get Prism to work at all, but maybe I should try again. I would rather (for selfish reasons) have a Webkit browser than Gecko-based one. Of course, I can always use whatever I want at home... The further I get into this the less I think Fluid is going to work. That is slightly saddening since I think it's a rather nice application. I'll keep looking for other alternatives though. -Ivan -- MacMail - the Webmail service especially for Mac users worldwide http://www.macmail.com --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Doc Days
On Thu, Mar 6, 2008 at 11:59 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > > > On Mar 7, 8:53 am, Timothy Clemans <[EMAIL PROTECTED]> wrote: > > Does one just add a bunch of documentation and make a patch and submit > > it? Or does one make a bunch of Trac tickets and make a ton of > > patches? > > > > The idea is to add doctests. One would add doctests to one file or > directory of files and then open a ticket with a patch attached. We > don't need loads of open tickets about missing doctests since someone > has written them. "-coverage" let's you find out instantly where the > problem areas are. Also, like all new patches in Sage, the new docstrings will be refereed, and will have to satisfy the referee. Fortunately, refereeing helps a lot in this regards. So you add doctests to a file or files, make a patch, post it to trac, and put [with patch; needs review] at the beginning of the ticket title. -- William --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] sage-3.0
Hi Sage-Devel: The main goals for Sage-3.0 are: * DOCTESTS: Raise the doctest coverage of the Sage library to 50%. * INTERACT: Interactive versions of functions in the notebook; kind of like Mathematica's Manipulate command. * R: a pexpect R interface * TIMING/BENCHMARK: Making it so doctesting Sage also saves complete timing and profiling information. Start using and publishing the results of this. * PORTING: OSX 10.5 64 bit , FreeBSD, PPC 64 bit build support out of the box. Experimental 32 bit Solaris 10 build support The target date is April 5, 2008. -- William -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.0
Hi On Fri, Mar 07, 2008 at 08:29:33AM -0800, William Stein wrote: > Hi Sage-Devel: > The main goals for Sage-3.0 are: > The target date is April 5, 2008. Awesome, great work, good luck, and thanks to all the devs! Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Demo of mlab module in enthoughts mayavi-2.1.0 for sage-2.10.3
See some screenshots: http://picasaweb.google.com/j.spies88/ScreenshotsMlabMayavi210 For those in the *experimental vein* (linux only): See: http://sage.math.washington.edu/home/jsp/SPKGS/mayavi_2.1.0/ > Install or build sage-2.10.3 or one of the release candidates. > > Put all this files in $SAGE_ROOT/spkg/standard > > type ./sage -i mayavi-2.1.0.20080306 > > and wait (a long time). > > Now start with ./sage -wthread > > Note that vtk-5.0.4 is gl2ps enabled. So you can save images to eps, ps and > pdf formats. > > > Or install all packages one by one starting with cmake, vtk, wxPython, > setuptools, etc. Have fun. Jaap --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] slides for my first sage talk
Here are slides from my first Sage talk. I told the audience why I am excited about Sage. http://www.lacim.uqam.ca/~saliola/maths/talks/slides/SageTalk1.pdf I made the slides with beamer using the sagetex latex package. Here is the tex file for the slides. http://www.lacim.uqam.ca/~saliola/maths/talks/slides/SageTalk1.tex Franco -- --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] updating programming guide
There has been talk of things that need to be updated in the programming guide. Here is a short list (also on trac at http://trac.sagemath.org/sage_trac/ticket/2422 ). Is there anything else? You might add your comments to the trac ticket. The programming guide should be updated: 1. Instructions about working with trac (posting a patch, the "[with patch, needs review]", the review process, etc.) 2. Expectations for patches (doctests and documentation, clean code, can be slow as an initial version, but if it's a naive way to do things when it could be faster, it should probably be mentioned, references for algorithms if it is an algorithm from a paper, etc.) 3. Instructions on creating patches instead of bundles, maybe a short introduction to queues. 4. Say that you really should go ask people to review your patch and then follow up and make sure the patch doesn't fall through the cracks. 5. Instructions for running the doctests to check for failures. 6. Expectations and instructions for creating spkgs Also, we probably ought to reorganize the guide so that it's very, very easy for a person to pick it up and start doing at least small fixes. Maybe put the short mercurial tutorial in the very front with a small documentation-fixing example or an example of adding a simple function. Jason --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: slides for my first sage talk
Nice. I really liked the LaTeX examples. John On 07/03/2008, Franco Saliola <[EMAIL PROTECTED]> wrote: > > Here are slides from my first Sage talk. I told the audience why I am > excited about Sage. > > http://www.lacim.uqam.ca/~saliola/maths/talks/slides/SageTalk1.pdf > > I made the slides with beamer using the sagetex latex package. Here is > the tex file for the slides. > > http://www.lacim.uqam.ca/~saliola/maths/talks/slides/SageTalk1.tex > > Franco > > > -- > > > > -- John Cremona --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] gcd() for fields
In reviewing #2340, which adds some nice documentation for rings/ring.pyx -- done by cswiercz -- I came across for the first time the feature that gcd(a,b) works for rational a,b, returning a perfectly sensible answer. sage: gcd(1/2,1/3) 1/6 Are there any other fields for which someone has implemented a gcd function? Although this is a nice function and I cann that it has its uses, I am not so happy with its name I could just as easily make a case for gcd(a,b)=1 for all rationals a,b (except (gcd(0,0)=0). -- John Cremona --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: slides for my first sage talk
On Mar 7, 2008, at 09:10 , Franco Saliola wrote:
>
> Here are slides from my first Sage talk. I told the audience why I am
> excited about Sage.
>
> http://www.lacim.uqam.ca/~saliola/maths/talks/slides/SageTalk1.pdf
>
> I made the slides with beamer using the sagetex latex package. Here is
> the tex file for the slides.
>
> http://www.lacim.uqam.ca/~saliola/maths/talks/slides/SageTalk1.tex
I thought I'd try sagetex for some notes I'm writing up. I keep
running into this problem (with sagetex.sty from 2.10.1):
Overfull \hbox (12.28172pt too wide) in paragraph at lines 10--10
[]\OT1/cmtt/m/n/9
---[]
) [28] (./SageTalk1.vrb
) [29 ] (./SageTalk1.vrb
! Bad space factor (0).
[EMAIL PROTECTED]
l.20 \end{sagesilent}
Any clues? I replaced Franco's graphics with my own; I'm not sure
what effect this might have...
Thanks!
Justin
--
Justin C. Walker, Curmudgeon at Large
Institute for the Absorption of Federal Funds
---
If it weren't for carbon-14, I wouldn't date at all.
---
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Multipolynomials: jacob() should be gradient()?
This is at http://sagetrac.org/sage_trac/ticket/2425 awaiting review. Jason John Cremona wrote: > +1. For calculus, gradient is the good term. For a Jacobian > function I would expect the input to be a list/sequence of functions > and the output a matrix. > > John > > On 29/02/2008, didier deshommes <[EMAIL PROTECTED]> wrote: > >> On Fri, Feb 29, 2008 at 1:58 PM, Jason Bandlow <[EMAIL PROTECTED]> wrote: >> > >> > Hi, >> > >> > Currently, if f is a multi-polynomial, the call f.jacob() returns the >> > list of partial derivatives of f with respect to the ring generators: >> > >> > sage: R. = PolynomialRing(QQ) >> > sage: f = x^4 + y^3 + z^2 + x*y*z >> > sage: f.jacob() >> > [4*x^3 + y*z, 3*y^2 + x*z, x*y + 2*z] >> > >> > >> > I'd like to change the name to gradient. Another possibility is changing >> > the name to 'jacobian', but I think it's likely that more people (eg >> > calculus students) will recognize the term 'gradient' and not 'jacobian' >> > than vice-versa. And who talks about the Jacobian of a single function >> > anyway? :) >> >> >> +1 for the "gradient" name change. >> >> >> didier >> >> >> > >> >> > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] linear algebra in Cython
I would like to implement some Bayesian routines using Cython. I have looked at some of the Cython examples but they don't really provide enough information for a newbie like me. As a starting point i'd like to implement bootstrapping of OLS parameter standard errors. That would give me an idea of how to implement (1) linear algebra in Cython, i assume by calling routines from Numpy in some way, (2) random number generators for sampling, and (3) running loops. I anyone has any (simple) examples of how to do something like this in Cython i'd love to see them. Also, if there are better ways to do this than through Cython i'd luv to hear your suggestions. Thanks, Vincent --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
