User:Tancre/2/hackpact/Clippy: Difference between revisions

From XPUB & Lens-Based wiki
< User:Tancre‎ | 2‎ | hackpact
 
(32 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Clippy (Clippit) =
= Clippy (Clippit) =
== Historical Background ==
=== Microsoft Office ===
=== Office Assistant ===
=== Clippy ===
https://www.youtube.com/watch?v=8bhjNvSSuLM
https://www.youtube.com/watch?v=8bhjNvSSuLM


== Existing Projects ==
== ClippyJS ==
 
=== ClippyJS ===
Most famous project online with Clippy. It allows adding an Assistant to your web page.<br>
Most famous project online with Clippy. It allows adding an Assistant to your web page.<br>
* https://www.smore.com/clippy-js<br>
* https://www.smore.com/clippy-js<br>
* https://github.com/smore-inc/clippy.js
* https://github.com/smore-inc/clippy.js
=== Clippy prank ===
Project for windows. Every 60 seconds Clippy appears on your desktop to basically bother you with stupid phrases. No animations only text.
* http://rjlpranks.com/pranks/clippy/
=== Clippy on iOS and macOS ===
* iOS > https://github.com/hbang/WritingALetter
* macOS > https://github.com/Clipy/Clipy
=== ClippyVS ===
Clippy on Visual Studio.
https://github.com/tanathos/ClippyVS


== Unpacking the software ==
== Unpacking the software ==
Line 43: Line 22:
=== Methodology ===
=== Methodology ===
* Overview of the repository + available data  
* Overview of the repository + available data  
* Pass through readable files (txt, md, ...)
* Read files (txt, md, ...) + description
* Pass through other folders + guess the usage of the files
* Check other folders + guess the usage of the files
* Built a website with Clippy + description of the interactions
* Built a website with Clippy + description of the workflow & interactions
* Analysis of the main code + description  
* Analysis of the main code + description  
* Edit the code
* Edit the code
Line 53: Line 32:
=== Overview ===
=== Overview ===
For a general overview, I used the command ''tree -h'' to recursively list the directory and the size of each file. <br>
For a general overview, I used the command ''tree -h'' to recursively list the directory and the size of each file. <br>
Sublime text provide an interactive overview of the folder you are working on. <br>
[[File:clippy_overview.PNG | 600px]]
[[File:clippy_overview.PNG | 600px]]
[[File:Overview_sublime.PNG | 183px]]
----
The command ''tree'' can print an XML file with the argument '-X' and a JSON file with the argument '-Y', this would allow generating a data visualization of the directory. Probably I can use it with D3.js. >> [[User:Tancre/2/hackpact/Git_Stalker | Git Stalker]] <br>


* The command ''tree'' can print an XML file with the argument '-X' and a JSON file with the argument '-Y', this would allow generating a data visualization of the directory. Probably I can use it with D3.js. >> [[User:Tancre/2/hackpact/Git_Stalker | Git Stalker]]  
It could be something like this: <br>
* The overview through listing the files in the directory can be also achieved non-recursively with ''ls'' or recursively by using the option ''ls -R'' (''ls -hlR'' to get more details on the files)
[[File:workflow-01.png | 300px]]
[[File:wworkflow-02.png | 300px]]
[[File:wworkflow-03.png | 300px]]
 
The overview through listing the files in the directory can be also achieved non-recursively with ''ls'' or recursively by using the option ''ls -R'' (''ls -hlR'' to get more details on the files)
----


=== Files ===
=== Files ===
Line 65: Line 55:
* [build] > contains clippy files (css, js, js.min), I guess to build Clippy and its actions and give him an initial position in the webpage.   
* [build] > contains clippy files (css, js, js.min), I guess to build Clippy and its actions and give him an initial position in the webpage.   
* [agents] > contains other agents, but there is again a folder for Clippy, this time with a png (probably the sprite animation), audio files (why in JS?), and a JS called agent (probably the object agent)
* [agents] > contains other agents, but there is again a folder for Clippy, this time with a png (probably the sprite animation), audio files (why in JS?), and a JS called agent (probably the object agent)
* [src] > it seems the main folder, and there are again both clippy.css and agent.js
* [src] > it seems the main folder with different actions (load, queue, animator..), and there are again both clippy.css and agent.js
** [images] > 2 png files (I cant understand for what)
** [images] > 2 png files (I cant understand for what)


----
----
I'm a bit confused about how does this works. <br>
In particular, I'm not sure if working on a piece of software that works on the web is a good idea. I don't know if I would be able to understand how it works as a whole, because of the networks involved in it.
If working with Processing and Arduino was making me conscious of their being dependents on the desktop and other layers of software, this clippy.js involves a knowledge of the browser, as a piece of software, and all the computer networks. <br>
----
=== Initial workflow ===
Using the code from the Git is less intuitive than I thought. <br>
Three files are required in the .html + the initial script to run Clippy:
* clippy.css (in <head>)
* clippy.min.js
* jquery.1.7.min.js
* <code> clippy.load('Clippy', function(agent){ agent.show(); }); </code>
HTMl (meta & script) > CSS / JQUERY / CLIPPY.JS
[[File:workflow-04.png | 200px]]
>The first two files are in the folder ''built'', (I will use ''clippy.js'' instead of the .min.js) but I have to download jquery.
I,n fact when I open the .html, in the console says '$ is not defined'.
CLIPPY.JS ($) > JQUERY > CLIPPY.JS
[[File:workflow-05.png | 200px]]
> When I run the page, it doesn't work. The console reveals that a script is searching for ''agent.js'' and ''sound-mp3.js'' but the path is wrong.
I check in ''clippy.js'' and the function clippy.load(...) have in the first line a ''var path'' equal to a url. Probably if I run the file from a server it works because it can access the website and its content. (I try with ''python simpleHTTPserver'' and it works). Anyway I prefer to work outside of the server so I change the path to my ''Agent'' folder which contains the required files.
HTML (script inline) > clippy.load(...) > CLIPPY.JS > PATH 
[[File: workflow-06.png | 300px]]
When the path is correct, all a series of connections between the code in the files start, and Clippy appears on the screen.
[[File: workflow-07.png | 700px]]
----
I noticed that to describe software, right now there are 3 layers working together (more if you count the access to another server): folders/files/code. Actually, this methodology I'm following is pushing me toward the code. The workflow can be represented from the point of view of the folders but once all the links are activated (working paths through files), it becomes really a matter of code. <br>
Instinctively I've used forms to describe folders and files as circles and rectangles(or dots when too small the space), eventually, code as lines. <br> 
Which is the distinction between these 3 elements? In the end, it is just code. That can be resumed in a single file containing all Clippy. I'm wondering how it could be this single file: CSS, Jquery and js all inline, images and sounds (?). <br>
Indeed the last layer (code) contains all a series of further layers (objects, functions, variables ..) that I will analyze later. To understand better the code, each part (class, function ..) can be isolated in separate files. <br>
I'm starting to play with languages (html / css / js) and language models (OOP). There are also libraries (jquery), sound file. I feel like I could get stuck in trying to understand how the code works on its high-level and how to represent this process. I should also start to reveal the other levels..but how? (maybe unpacking the images and sound?)<br>
There are more things involved as I go on, concepts that are unclear, processes that are too fast. 
----
=== Experiments with the code ===
[http://145.137.124.160:8000/hackpact_clippy/website/using_the_code/ run clippy] <br>
[http://145.137.124.160:8000/hackpact_clippy/website/editing_the_code/clippy_world.html clippy's world]
'''Next...''' <br>
>> Learn to use the debug in firefox to pass through the steps of the code <br>
>> How can I convert the js in object code and machine code?

Latest revision as of 13:33, 14 October 2019

Clippy (Clippit)

https://www.youtube.com/watch?v=8bhjNvSSuLM

ClippyJS

Most famous project online with Clippy. It allows adding an Assistant to your web page.

Unpacking the software

Where to start?

> I wanted to work on the original code but I couldn't find it. Microsoft never published it.

> I tried to work on Clippy prank, which is based on Windows, but after using 7zip to extract the .exe I got stuck. The extracted files have strange extensions (ADATA, ASPAK, IDATA ...) or no extension at all. When I tried to open them I noticed the code is encoded and I've no idea how to work with it. (I searched a bit and it seems like I should get some .msi file from the .exe).

> The only accessible project I can work on is ClippyJS. It is the most famous project available online and can be interesting to play with it and make a website.
Furthermore, it is stored on Github allowing me to work on both sides of my hackpact #1
(How did they make it if the original code is not available?)

 git clone https://github.com/smore-inc/clippy.js

Methodology

  • Overview of the repository + available data
  • Read files (txt, md, ...) + description
  • Check other folders + guess the usage of the files
  • Built a website with Clippy + description of the workflow & interactions
  • Analysis of the main code + description
  • Edit the code

At each step, I will try to write down some thoughts that eventually could lead me to a new phase of the hackpact.

Overview

For a general overview, I used the command tree -h to recursively list the directory and the size of each file.
Sublime text provide an interactive overview of the folder you are working on.
Clippy overview.PNG Overview sublime.PNG



The command tree can print an XML file with the argument '-X' and a JSON file with the argument '-Y', this would allow generating a data visualization of the directory. Probably I can use it with D3.js. >> Git Stalker

It could be something like this:
Workflow-01.png Wworkflow-02.png Wworkflow-03.png

The overview through listing the files in the directory can be also achieved non-recursively with ls or recursively by using the option ls -R (ls -hlR to get more details on the files)


Files

  • README.md > description + usage + greetings
  • MIT-LICENSE > free license + restrictions + property of Microsoft


  • [build] > contains clippy files (css, js, js.min), I guess to build Clippy and its actions and give him an initial position in the webpage.
  • [agents] > contains other agents, but there is again a folder for Clippy, this time with a png (probably the sprite animation), audio files (why in JS?), and a JS called agent (probably the object agent)
  • [src] > it seems the main folder with different actions (load, queue, animator..), and there are again both clippy.css and agent.js
    • [images] > 2 png files (I cant understand for what)



I'm a bit confused about how does this works.
In particular, I'm not sure if working on a piece of software that works on the web is a good idea. I don't know if I would be able to understand how it works as a whole, because of the networks involved in it. If working with Processing and Arduino was making me conscious of their being dependents on the desktop and other layers of software, this clippy.js involves a knowledge of the browser, as a piece of software, and all the computer networks.


Initial workflow

Using the code from the Git is less intuitive than I thought.
Three files are required in the .html + the initial script to run Clippy:

  • clippy.css (in <head>)
  • clippy.min.js
  • jquery.1.7.min.js
  • clippy.load('Clippy', function(agent){ agent.show(); });

HTMl (meta & script) > CSS / JQUERY / CLIPPY.JS

Workflow-04.png

>The first two files are in the folder built, (I will use clippy.js instead of the .min.js) but I have to download jquery. I,n fact when I open the .html, in the console says '$ is not defined'.

CLIPPY.JS ($) > JQUERY > CLIPPY.JS

Workflow-05.png

> When I run the page, it doesn't work. The console reveals that a script is searching for agent.js and sound-mp3.js but the path is wrong. I check in clippy.js and the function clippy.load(...) have in the first line a var path equal to a url. Probably if I run the file from a server it works because it can access the website and its content. (I try with python simpleHTTPserver and it works). Anyway I prefer to work outside of the server so I change the path to my Agent folder which contains the required files.

HTML (script inline) > clippy.load(...) > CLIPPY.JS > PATH

Workflow-06.png

When the path is correct, all a series of connections between the code in the files start, and Clippy appears on the screen.

Workflow-07.png


I noticed that to describe software, right now there are 3 layers working together (more if you count the access to another server): folders/files/code. Actually, this methodology I'm following is pushing me toward the code. The workflow can be represented from the point of view of the folders but once all the links are activated (working paths through files), it becomes really a matter of code.

Instinctively I've used forms to describe folders and files as circles and rectangles(or dots when too small the space), eventually, code as lines.

Which is the distinction between these 3 elements? In the end, it is just code. That can be resumed in a single file containing all Clippy. I'm wondering how it could be this single file: CSS, Jquery and js all inline, images and sounds (?).

Indeed the last layer (code) contains all a series of further layers (objects, functions, variables ..) that I will analyze later. To understand better the code, each part (class, function ..) can be isolated in separate files.

I'm starting to play with languages (html / css / js) and language models (OOP). There are also libraries (jquery), sound file. I feel like I could get stuck in trying to understand how the code works on its high-level and how to represent this process. I should also start to reveal the other levels..but how? (maybe unpacking the images and sound?)

There are more things involved as I go on, concepts that are unclear, processes that are too fast.


Experiments with the code

run clippy
clippy's world

Next...
>> Learn to use the debug in firefox to pass through the steps of the code
>> How can I convert the js in object code and machine code?