Hello again, Yes, I noticed how SageCell uses a different branch of Sage. That would be a nice problem to solve for all future versions and developers of SageCell. I guess the best way to go about this would be to carefully find out the exact differences between the two branches being used and figuring out a solution for each difference. I'd love to help with the Javascript parts, let me know what exactly I'll be looking at in that situation and how I should begin.
In the meanwhile, I've applied to be added to the sage-cell development forum to keep myself updated about relevant changes in the system. Please approve the request if you think this would be helpful. I'll send an update over the weekend summarizing some actions and plans. Thanks a lot, On Thursday, February 12, 2015 at 3:19:18 AM UTC+5:30, Andrey Novoseltsev wrote: > > Hi Gurshabad, > > Contributions to SageCell are certainly welcome! In particular it would be > nice to make it "more standalone" in the sense of not needing any patches > to Sage (which will greatly simplify upgrading to new Sage versions since > there will be no need to resolve merge conflicts and fix resulting bugs) > and cleaner interaction with other dependencies, chiefly IPython. I am > trying to improve the situation gradually, but would not mind help, > especially with the JavaScript parts. Another angle is robustness under > load spikes and nice tests for it. > > Best, > Andrey > -- You received this message because you are subscribed to the Google Groups "sage-gsoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-gsoc. For more options, visit https://groups.google.com/d/optout.
