I don't understand: which is the difference between this codenode and our new notebook? Did we manage to get two brand new (but different) notebooks at the precisely same moment? This would be good in some sense, but also bad, if you know what I mean for avoiding waste of efforts
Regards Maurizio On 17 Ott, 00:04, Dorian Raymer <deldo...@gmail.com> wrote: > Hello everyone, > We have merged a big development effort into the master > repository<http://github.com/codenode/codenode> > ! > > This represents a milestone in the ongoing effort to bring the whole design > to a new stable point. The Frontend was re-implemented using Django earlier > this year, and we now have completely re-done the Backend! > > High level features: > - Engine plug-ins > An engine is the computation process behind the notebook (Before today, > Codenode only supported the regular Python engine). > Engine types can be added without modifying library code! > - Sage Engine > Template engine type for using Sage in codenode! > - Admin management of Backends > A frontend can be associated with any number of backend servers, running > anywhere on the network. Each of those backend servers can support any > number of engine types. > - Development version of servers > Improved work flow; development of running code. Raw support for reloading > of modules with out restarting the process. > > Updated documentation <http://codenode.org/docs/>. These still need work, so > please make as many comments and ask as many questions as you have. This > will aid improving the quality of the documentation greatly. > > Updated live public notebook <http://live.codenode.org>, with two engine > types: Python and Sage!!! This backend server is also much more powerful > than what we had running on app engine. This makes the live site an actually > useful service, so please use it for day to day python/sage things as much > as you like. > > Making it easy to develop codenode is an important design feature we are > striving to fulfill. The major pieces of the system are becoming > sufficiently modularized such that working on a specific component does not > require deep knowledge of the entire system. We hope this will allow people > with specific specializations to have a fun time developing features either > independently, or with some counterpart collaborator who might have a > complementary expertise. > > As a project, codenode is finding a balance between providing a solid base > design for long term viability/extendability, and writing useful features > that people care about and need NOW! With this milestone, the focus of our > efforts will noticeably shift back to fulling feature requests, fixing bugs, > and sharing/proposing our own feature ideas. > > A few quick mentions of features: > General plotting capability for plain Python that is compatible with Sage. > Sage version of notebook style and key bindings. > Collaborative running notebooks, portable notebook formats, etc. > Uploading code and data for use in a notebook. > Engines for other languages. > > Looking forward to feedback! > > Thanks, > Dorian and Alex --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
