update

.gitignore

@@ -0,0 +1,3 @@
+LiaScriptImageDescriber/liascript-devserver-win.exe
+LiaScriptImageDescriber/highlightJS/test2.html
+

LiaScriptImageDescriber/ImageDescriber.js

@@ -159,7 +159,7 @@ function buttonPressFunction() {
         //what happens when the button is pressed and picture is selected
         ImgUrlLink = document.getElementById("LinkTextBox").value;
         console.log(ImgUrlLink);
-        LastSentTaskString = taskSelection.picture;
+        LastSentTaskString = taskSelection.graph;
         LastSentTaskString += "![]("+ ImgUrlLink + ")"
         LastSentTaskString += userTasks.picture;
         sendLia(LastSentTaskString);

LiaScriptImageDescriber/userTasks.js

@@ -61,23 +61,75 @@ Here are some examples:\n
 `
 
 userTasks.code = `
-Task - DEMO CODE DESCRIPTION TB1  
+
+Prep-work:
 ================
-        
-To capture the attention of your readers, you should start with a good introduction phrase(s).\n
-Here are some examples you may use:
 
-* If you look at this picture, you will see...
-* In the picture you can see...   
-* The picture shows... 
+Code descriptions are a bit more unorthodox than normal image descriptions.
+So, what do we have to look for in a code description?
+
+First of all, we have to figure out the context of this code...
+
+Here are some examples which may help you to do just that: \n
+
+* Looking at the code(snipped) as a whole, you can see that...
+* This code(snipped) has been written in...
+* This code(snipped) is a [...] which returns a...
             
 <textarea id="graphTextArea1" oninput="TBonChange(this)">Please enter text here!</textArea> \n
 
-Task - DEMO CODE DESCRIPTION TB2  
+What is this code all about? 
 ==============
 
-DESCRIPTION OF ANOTHER TASK...
+Describe what you think it is used for, or where you have found it...
+
+Some helpful examples:
+
+* The [...] uses this [...] for...
+* One might need this in...
+* When you are [...] you might need a function like this to...
 
 <textarea id="graphTextArea2" oninput="TBonChange(this)">Please enter text here!</textArea>  \n
 
+Detailed analysis:
+==============
+
+Analyse the code now thoroughly. What can you see, what is written where, is there something interesting?
+This might be achievable by looking at it line by line and will probably be the largest text(s) you'll need to write.
+
+Here are some examples which might help you get started from the top:
+
+* In the code provided the following imports are made...
+* We make use of the [...] libraries...
+
+<textarea id="graphTextArea3" oninput="TBonChange(this)">Please enter text here!</textArea>  \n
+
+Continue with the line-by-line check to focus on individual functions and lines. 
+Make note of things like efficiency, variable names or even comments, here are some phrases which might help: 
+
+* In the [...] line you can see that it is a call to a...
+* In Line [...] you can see, that variable [...] is defined with...
+* In the next line, the previously defined [...] is used for...
+
+<textarea id="graphTextArea4" oninput="TBonChange(this)">Please enter text here!</textArea>  \n
+
+Become the compiler:
+==============
+
+Code is never perfect... have you spotted a mistake? Would this code run at all, or would the compiler just throw a warning or maybe even error?
+Be critical and insightful, do you have improvements? Write about it and remember 'Be the compiler'.
+
+Here are some examples which might help:
+
+* In Line [...], the pointer to the variable [...] is used instead of the...
+* The line has not been completed and there is a [...] missing at the end.
+* The [...] of the function [...] is undefined.
+
+<textarea id="graphTextArea5" oninput="TBonChange(this)">Please enter text here!</textArea>  \n
+
+
+`
+
+userTasks.graph = `
+Hier könnte ihre werbung stehen... und so (WORK IN PROGRSS! guck weck! >:D)
 `