On 4/1/11 1:18 PM, Jonathan wrote:
Dan,
I'm glad you like most of what has been done. If you manage to get
anything to fail please report that as well.
As to the speed, there's not a lot we can do. That is limited by how
fast information is passed from the server and how fast your computer
is
On Apr 1, 4:35 pm, Jonathan wrote:
> On Apr 1, 1:49 pm, kcrisman wrote:
>
> > > with all the applets replaced by static images, but this requires
> > > changes to the plot3d functions. I was worrying about the interface
> > > first.
>
> > Can you expand on this? Do you mean that any given pag
On Apr 1, 1:49 pm, kcrisman wrote:
> > with all the applets replaced by static images, but this requires
> > changes to the plot3d functions. I was worrying about the interface
> > first.
>
> Can you expand on this? Do you mean that any given page would have a
> static image, and it would onl
> One thought is to make it clearer what is happening. Would a pop-up
> progress window indicating which applet is loading help with the way
> it feels? Long term, I will probably make it so that old pages load
Yes. But that can be added after this. Let's make sure your valuable
improvements
Dan,
I'm glad you like most of what has been done. If you manage to get
anything to fail please report that as well.
As to the speed, there's not a lot we can do. That is limited by how
fast information is passed from the server and how fast your computer
is. Jmol is doing quite a bit of compu
So I just made a fresh build of sage and the patching went smoothly.
Not sure what was causing the problem. So far, everything works
great! I also noticed that it did seem to take a long time for the
applets to load, and somehow it seems that the image resolution is not
as good as it was before I
On Thu, 31 Mar 2011 at 06:08AM -0700, Jonathan wrote:
> If you want to see what is coming down the pike in the next few
> weeks, take a look at the published samples on my test server:
> http:///141.233.197.45:. I could really use some comments on how
> it works.
I'm using Firefox 4.0 on Ubu
Thanks guys. I was definitely using hg_sagenb.apply() and not
hg_sagenb.commit(), so I am not sure why it was asking me to commit.
The only difference from what you say Jonathan was that I was applying
the patches from a local directory and not an http:, so I doubt that
makes a difference. I will
On 03/31/11 05:32 PM, jtyard wrote:
Hi Jonathan,
Thanks for your reply. I tried last night to figure out how to patch
my notebook, and I ended up giving up after several hours. I also
couldn't find any documentation for hg_sagenb.apply. After updating
jmol to 1.1.5, I tried to follow the dire
Your description sounds like you are doing a hg_sagenb.commit(), not a
hg_sagenb.apply("http://.patch"). If you just copy
the link to the listed patches as shown above they should work.
That's what I do.
Jonathan
P.S. Great name!
On Mar 31, 11:32 am, jtyard wrote:
> Hi Jonathan,
>
> Thank
Hi Jonathan,
Thanks for your reply. I tried last night to figure out how to patch
my notebook, and I ended up giving up after several hours. I also
couldn't find any documentation for hg_sagenb.apply. After updating
jmol to 1.1.5, I tried to follow the directions at
http://www.sagemath.org/doc
Jon,
We are sorting this out. Ticket #9238 is the one you want.
The .spkg you used is out-of-date. All the fixes are not in, but if
you follow the patching instructions on #9238 you should get something
that will work cleanly on MacOS + Chrome. FF has been inconsistent,
so we are having troubl
12 matches
Mail list logo
