On Mon, Oct 19, 2009 at 3:45 PM, Dorian Raymer <deldo...@gmail.com> wrote: > Hi Stan, > I looked in to the solve problem and I get the same error. > > Solve does work when I log into the server and use Sage from the command > line, and it works from the codenode notebook on my local linux install, so > I am slightly baffled. > > Does William or another sage person have any idea what would cause the > 'Unable to start maxima' error? I'm thinking it might be some kind of > environment problem that a sage expert would have better intuition on. > > For plotting, this has been the number one first thing people try, and I'm > currently working on getting plots to show up in the notebook. Most of the > code supporting this already exists, it has just been a matter of > updating/adapting it to work with the new backend/frontend, so it won't be > long. Yeah, plotting and data management are incredibly important to actual real-person-usability. I'm very excited about the fact that our architecture is now feeling very solid and we can (finally) shift our main focus to usability.
We already have most of the plotting code in place, and I have a branch going with some good data management functionality, so these features should come along pretty quickly. -Alex > > -Dorian > > > On Mon, Oct 19, 2009 at 4:39 AM, Stan Schymanski <schym...@gmail.com> wrote: >> >> Hi Dorian, >> >> I got all excited but the live public notebook in sage mode does not >> seem to work for me. >> >> plot(x^3 - 3*x^2 + 2*x -3, (x,-3,3)) >> >> produces an empty field for me, and >> >> solve(0 == x^3 - a*x^2 + b*x -3, x) >> >> results in a traceback: >> >> Traceback (most recent call last): >> [snip] >> TypeError: Unable to start maxima >> >> Is there a problem with the sage installation? >> >> Cheers, >> Stan >> >> Dorian Raymer 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 >> > >> > >> > > >> >> >> > > > > > -- Alex Clemesha clemesha.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
