On Monday, May 12, 2014 5:27:21 AM UTC-7, Jason Grout wrote:
>
> Right. I think you're pointing out a problem with the example interact
> William posted, which I agree is not very polished.
I haven't looked at William's version, only your SageCell translation. I
imagine they would suffer from
On 5/9/14, 16:41, Nils Bruin wrote:
On Friday, May 9, 2014 1:05:23 PM UTC-7, Jason Grout wrote:
Right---the interact always is recreating that control, which defaults
to the first entry. With a selector, our thinking was that if the item
was already selected, then it didn't need to
On Friday, May 9, 2014 1:05:23 PM UTC-7, Jason Grout wrote:
> Right---the interact always is recreating that control, which defaults
> to the first entry. With a selector, our thinking was that if the item
> was already selected, then it didn't need to be selected again.
But I can see where i
On 5/9/14, 11:14, Nils Bruin wrote:
Hi Jason,
Thank you very much for all the work on SageCell. It's an unbelievably
useful tool to make little demonstrations.
On Friday, May 9, 2014 6:11:24 AM UTC-7, Jason Grout wrote:
4. When you click on a selector button that is already selected, the
Hi Jason,
Thank you very much for all the work on SageCell. It's an unbelievably
useful tool to make little demonstrations.
On Friday, May 9, 2014 6:11:24 AM UTC-7, Jason Grout wrote:
>
> 4. When you click on a selector button that is already selected, the
> cell server ignores the click (since
On 5/8/14, 11:01, William Stein wrote:
@interact
def foo(functions=[sin(x)], f=sin(x)):
show(plot(foo.functions))
del foo.functions
foo.functions = [f(x=x), f(x=x^2), f(x=x^3)]
Here's a corresponding one working in the cell server:
http://sagecell.sagemath.org/?q=ribyjg
@inter