Hi,
On Jan 10, 11:13 am, "Luiz Felipe Martins"
wrote:
> Hi. The software you mention may remain nameless, but it is pretty
> obvious what it is.
Yeah, I was aiming more for obnoxious than subtle. :-)
> There was a serious screw up when they tried to
> redo their whole interface in Java, as I w
On Sat, 10 Jan 2009 at 08:27PM -0800, William Stein wrote:
[snip]
> That situation was just very frustrating for me, not because I
> couldn't get Magma (I got it for free as a developer), but that so
> many other students and colleagues couldn't get it.
Exactly! The value of any of these pieces of
William Stein wrote:
> One problem I personally had wasn't the same sort of forced transition
> from CAS X to CAS Y like you had, but that the sole "CAS" I could use
> was Magma, since it was literally the only program out there capable
> of doing pretty much any of the interesting computational m
On Sat, Jan 10, 2009 at 8:06 PM, Dan Drake wrote:
> On Sat, 10 Jan 2009 at 12:13PM -0500, Luiz Felipe Martins wrote:
>> Believe me, going to Sage has been (and will continue to be) a major
>> time investment. Faculty coming to Sage will weigh their disillusion
>> with other software against the i
On Sat, 10 Jan 2009 at 12:13PM -0500, Luiz Felipe Martins wrote:
> Believe me, going to Sage has been (and will continue to be) a major
> time investment. Faculty coming to Sage will weigh their disillusion
> with other software against the investment needed to change. I
> actually pondered about i
On Sat, Jan 10, 2009 at 8:53 AM, john_perry_usm wrote:
>
> One of the reasons I switched to Sage was that a handful of years ago
> the previous CAS I used (who shall remain nameless) introduced a
> worksheet interface that grossly slowed down the system. Rather than
> improve the efficiency, subs
Hi. The software you mention may remain nameless, but it is pretty
obvious what it is. There was a serious screw up when they tried to
redo their whole interface in Java, as I was told by a representative.
There are two main reasons I switched to sage, besides frustration
with other software:
1)
One of the reasons I switched to Sage was that a handful of years ago
the previous CAS I used (who shall remain nameless) introduced a
worksheet interface that grossly slowed down the system. Rather than
improve the efficiency, subsequent releases made things worse by
adding an extremely slow synt
William Stein wrote:
> On Fri, Jan 9, 2009 at 2:30 AM, Martin Albrecht
> wrote:
>>> Sure. I think that what you want is still orthogonal to the TinyMCE
>>> effort, but having another edit widget in the tree "just" for
>>> highlighting ought to be well thought out and the burden of
>>> maintenance
On Jan 9, 2009, at 8:25 AM, William Stein wrote:
> On Fri, Jan 9, 2009 at 2:30 AM, Martin Albrecht
> wrote:
>>
>>> Sure. I think that what you want is still orthogonal to the TinyMCE
>>> effort, but having another edit widget in the tree "just" for
>>> highlighting ought to be well thought out a
I admit it wouldn't be for everyone. Initially I tried loading it in
using a GreaseMonkey script but discovered that was too late in the
DOM tree. What would be nice is if one could add plug-ins. Perhaps
they could be loaded using xml files much like Google allows. These
initially could be to pers
On Fri, Jan 9, 2009 at 2:30 AM, Martin Albrecht
wrote:
>
>> Sure. I think that what you want is still orthogonal to the TinyMCE
>> effort, but having another edit widget in the tree "just" for
>> highlighting ought to be well thought out and the burden of
>> maintenance must be taken into account
bsdz wrote:
> Hi,
>
> I dabbled a little with the vmware version of Sage and was able to
> install EditArea, a javascript syntax highlighting library (http://
> www.cdolivet.net/index.php?page=editArea). It is quite useful when
> editing Python and can be turned on or off. It also allows callback
> Sure. I think that what you want is still orthogonal to the TinyMCE
> effort, but having another edit widget in the tree "just" for
> highlighting ought to be well thought out and the burden of
> maintenance must be taken into account, i.e. if somehow TinyMCE could
> be extended to do Python and
On Jan 8, 2:34 pm, bsdz wrote:
> I must admit I did consider TinyMCE amongst many others but I liked
> EditArea since it could syntax highlight python code. Other
> highlighters either didn't allow editing or didn't have built in
> python lexers. I notice the other thread has recently become mo
I must admit I did consider TinyMCE amongst many others but I liked
EditArea since it could syntax highlight python code. Other
highlighters either didn't allow editing or didn't have built in
python lexers. I notice the other thread has recently become more
active so I may follow that.
Thanks fo
On Jan 6, 1:33 am, bsdz wrote:
> Hi,
Hi Blair,
> I dabbled a little with the vmware version of Sage and was able to
> install EditArea, a javascript syntax highlighting library
> (http://www.cdolivet.net/index.php?page=editArea). It is quite useful when
> editing Python and can be turned on
17 matches
Mail list logo
