mabshoff wrote:
>
>
> On Jan 8, 3:22 pm, Jason Grout <jason-s...@creativetrax.com> wrote:
>> mabshoff wrote:
>>
>>> I think that the editor is just as important as the @interact in the
>>> notebook. So if we could find some more people to test the patches we
>>> can get them into the next release. As long as they don't break any
>>> existing functionality I would think that even if the editor support
>>> is slightly broken on some platforms it should still go in. The patch
>>> has been around for a while and resolving this would make life easier
>>> for everyone.
>> Can someone official make a list of requirements on this ticket to get
>> into Sage (i.e., a list of platforms people need to try it on, so many
>> people per platform, whatever). I would, but I'm afraid it'd be a bit
>> biased :).
>
> Well, my personal POV:
>
> (a) testing with IE 6, IE 7 Windows
> (b) testing with FF 2.0.x, 3.x on Windows, OSX and Linux
> (c) testing with Safari on 10.4 and 10.5
> (d) testing with Opera 9.5 on Windows, OSX, Linux
> (e) Chrome on Windows
>
> Obviously this is rather harsh, so if we covered all five major
> browsers somehow this would be enough for me assuming the patches
> themselves get a positive review and everything is working *after* we
> delete the javascript from the ext repo since there is potentially a
> reference to some code in there.
Here are the things that still need to be done to get this in (I believe
I've covered everything). If anyone can do part or all of this, that
would be great!
* testing with IE 6 on Windows
* testing with FF 2.0.x on Windows, OSX and Linux
* testing with Safari on 10.4
* testing with Opera 9.5 on OSX, Linux
* review of the patches themselves
* review of mabshoff's changes to the spkgs
* trivial one-line patch to fix the "ghostly text" issue (just make
the placeholder string the empty string in cell.py (search for
"placeholder" in cell.py).
* (maybe can wait for another patch): figure out what is going on
with divs with the same id. My guess is that it is an issue with setting
the innerHTMl of an object, rather than replacing the object itself.
When the page is "Edit"ed and then reloaded, the duplicate nested IDs go
away. This points to the javascript code that inserts text cells as the
problem.
> In the end having your assurance that you will available to fix
> some of the inevitable issues would also be assuring.
You have my assurance.
Jason
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
