On Tue, 22 Jan 2008, Nick Alexander wrote:
>
>
> On 22-Jan-08, at 9:08 AM, [EMAIL PROTECTED] wrote:
>
>>
>>>> I think this could be an exciting way to get all the java applet
>>>> makers out there interested in sage, although I don't completely
>>>> understand the architecture of what this is supposed to do.
>>>
>>> Wouldn't a Java applet imply that the functionality it provides
>>> could only be
>>> accessed via Sage's web interface?
>>>
>>> I would like to establish some (roughly) like this: If a
>>> computation cannot be
>>> expressed from the command line (in pure Python) then it cannot be
>>> a standard
>>> part of Sage. E.g. if you cannot compute $sin(x)$ for some $x$
>>> from the
>>> command line but you can do it by clicking some Java buttons, then
>>> this
>>> functionality would not be considered a part of (standard) Sage.
>>>
>>> Would that make sense?
>>> Martin
>>
>> No, that makes no sense at all.
>
> One reason to do this is because automated testing graphical
> interfaces (including, but not limited to, the notebook) tends to be
> nigh on impossible. If it can't be done from the command line, it's
> pretty hard to test; if it's not tested, I'd like it to not be widely
> accepted.
>
> Nick
>
The interface itself might be tricky -- however, the communication protocol
isn't hard to test, whatever computations go on behind the scenes aren't hard
to test, and Java has some *great* unit-testing capabilities, so that side
isn't hard to test either. In short, there is very little that we wouldn't be
able to test in an automated way.
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
