SocialCalc: Difference between revisions

From OLPC
Jump to navigation Jump to search
(stub)
 
No edit summary
Line 1: Line 1:
A [[Javascript]]-based spreadsheet being developed as a Sugar [[activity]] by Dan Bricklin and Luke Closs for the XO, with help from many others.
A [[Javascript]]-based spreadsheet being developed as a Sugar [[activity]] by Dan Bricklin and Luke Closs for the XO, with help from many others. See also [[pyxpcom]] notes.


== Recent updates ==
== Recent updates ==
Line 30: Line 30:
challenge for tonight.
challenge for tonight.
</pre>
</pre>

[[category:activities]]

Revision as of 19:27, 23 February 2008

A Javascript-based spreadsheet being developed as a Sugar activity by Dan Bricklin and Luke Closs for the XO, with help from many others. See also pyxpcom notes.

Recent updates

From a post by Luke to sugar on 2/22:

Background:
Socialcalc is a HTML/JS based spreadsheet engine that Dan has
developed.  He asked me to help him with sugar packaging, and
integration with the journal and other XO specific features.  The
python/javascript integration necessary for this project may also be
generally useful for other projects.  I'm developing with this in mind.

Summary of tonight's progress:
I learned how to change the gecko security settings to allow a local
HTML file access to XPCOM.  This means that I can now easily pass
messages between python and javascript.

Next Steps
With this spike done, I next need to spike to learn how saving and
restoring data to/from the journal works, and then I can integrate
this with pyxpcom to save and load data from the journal into
javascript.  With this in place, we should be almost ready to write
the save/load feature for Socialcalc.

Details of tonight's progress:
ActiveState Komodo developer Todd Whiteman (pyxpcom expert) suggested
I look into the nsIObserver xpcom interface as a way of passing
messages back and forth between python and javascript.  So this was my
challenge for tonight.