Papert Logo encapsulated in a TiddlyWiki which can be sent as an email attachment?

[Gene Sullivan]

Given that TiddyWiki's ARE an HTML file crammed full of *all* the JavaScript code which is used within the HTML file it seems that Papert Logo could be encapsulated in a single HTML or XML file just like a TiddlyWiki. 

http://en.wikipedia.org/wiki/TiddlyWiki

Any thoughts on this?

Cheers!
  Gene

[jlaerkedal]

Interesting idea.

I am no javascript wizard, but I cannot see why this should not be
feasible, provided that the email system allows loads of javascript,
and that the html code is interpreted by a capable browser. But what
would be the advantage compared to sending the link to
logo.twentygototen ?

Best regards
Jens

[Gene Sullivan]

2009/5/14 jlaerkedal <j...@itu.dk>

Interesting idea.

I am no javascript wizard, but I cannot see why this should not be
feasible, provided that the email system allows loads of javascript,
and that the html code is interpreted by a capable browser.

 

But what would be the advantage compared to sending the link to
logo.twentygototen ?

All the variations in which off-line mode could or would be used.
Papert Logo could be run from USB flash drive, CD, DVD, or a file
located anywhere on the hard drive of a given system.
One could conceivably bundle a given assortment of Logo programs
within the same TiddlyWiki as this implementation of Logo under which they
run.  Thus future modifications to the Logo REPL available on-line
would not break such logo programs bundled with the Logo REPL
upon which they would depend.  The bundling of the Logo REPL with an assortment of programs which depend upon it would ensure compatibility, standalone operation via a browser, and removal of hassles possibly encountered due to spotty, slow, or no web connectivity.

There are undoubtedly other reasons that could be dreamed up which
have escaped me at present.  Perhaps Logo could be used as an extension language for JavaScript to augment the creation of TiddlyWiki content as well.

Cheers!
  Gene

[jlaerkedal]

Hi Gene

I see your point. I am just thinking, that out of the 3 mailsystems I
use on a regular basis, only one MIGHT be able to display content
based on included javascript. One system would stript it off
alltogether, while my job e-mail would convert it to plain ASCII text.
Whereas an URL would pass through all. And in an offline situation,
you would probably not be able to retrieve your mail anyway.

Best regards
Jens

[Gene Sullivan]

On Sun, May 17, 2009 at 4:04 PM, jlaerkedal <j...@itu.dk> wrote:

Hi Gene

I see your point. I am just thinking, that out of the 3 mail systems I

use on a regular basis, only one MIGHT be able to display content
based on included javascript.

Huh?
I had imagined the TiddlyWiki file being sent as an attachment.
Did you imagine the contents of the file being inserted in the body?
If one DID want to do such then one could wrap the contents within `pre' tags

<pre>
  {
   html, xml, or/and javaScript code goes here
  .
  .
  .
 }
</pre>
 

One system would strip it off
altogether, while my job e-mail would convert it to plain ASCII text.

 

Whereas an URL would pass through all.

As would an attached file.
 

And in an offline situation,
you would probably not be able to retrieve your mail anyway.

Here is a scenario,
 Scenario I:
  A tax-funded functionary at an institution tasked with `educating'  citizens too young to vote -- EG a `teacher' in a public school -- has computers in his or her `classroom', which are connected to the web, but a draconian policy is in place which prevents accessing all but pre-approved URLs.  (S)He, being a member of the ruling class, can receive emails with attachments.  A `concerned citizen' CAN send her or him a tiddlyWiki which (s)he can open, access, evaluate and scrutinize to his or her heart's content.  Then, if (s)he so desires, (s)he can copy the stand-alone file to one-or-more of the computers in his or her classroom ... thus circumventing the web-access policy which would otherwise prevent his or her charges from accessing http://logo.twentygototen.org/ , for example.

Scenario II:
   Phase one of a Logo-REPL-embedded-in-a-TiddlyWiki project has completed resulting in
anyone having access to a computer running a major browser being able to run Logo programs compliant with this dialect of Logo.  Some enterprising software developer makes note that the vector graphics produced by `fd' and `bk' can be generated via a web browser via SVG {ref: http://en.wikipedia.org/wiki/Scalable_Vector_Graphics} and decides to create SVG drawing routines via JavaScript which will be implemented as Tiddlers embedded in any given TiddlyWiki file .... which, once again, can be distributed and disseminated near and far around the web as email attachments ... which can be copied onto floppies, CDs, DVDs, USB flash drives, etc. .... which can then be sneaker-netted to computers either not having web access or having constraints imposed which disallow direct access to twentyGotoTen.

Scenario III:
  Given the option of creating Tiddlers with JavaScript or Logo, users of this LogoTiddlyWiki form factor start creating Tidders in Logo which CAN not only use embedded Logo code but can, if their computer has web access, reference Logo code residing at Scenario II:

Scenario IV:
  ______________________________

Scneario V:
  ______________________________

^----- An open invitation to brainstorm!

Cheers!
  Gene

Best regards
Jens