Please follow the approach of Open Event Orga/API server and develop the app in a way that separates frontend and backend and connects both through APIs. The advantage is that it makes development easier and more versatile. Also frontend devs don't need to deal with backend functionality.

• Heroku reaps free dynos after 30 minutes of inactivity
• A request made to an inactive dyno takes 10 seconds, and this can be confusing to users who may think that the frontend app has frozen.
• A message/countdown timer can be shown when the app is opened indicating that the backend is waking up

• send script ID to API server for execution.
• Open modal and display result/error.

• the --proxy option during development redirects all AJAX calls to a specified URL, but the build command does not have such an option.
• There exist adapters to set the host parameter for JSONadapter, RESTAdapter etc, but these do not affect jquery.post, getJSON etc.
• a workaround is necessary for setting the base URL for all AJAX calls in the final build

• the stacking variable defaults to 'xy' which takes [xdata,ydata] and makes [[x1,y1],[x2,y2]... ]
• Extrapolate this for capture2 method
• Extrapolate this for capture4 method

• add jqplot plugins: cursor, highlighter, pointLabels

Semantic UI can help us to move faster with this app. The URL is here: http://semantic-ui.com

• Include modal for 'confirm delete'
• Auto-refresh the page after a script is deleted

• Include on User-Home
• Automatically fetch code via API when user clicks on the edit button for any of the saved scripts
• Include ace-js code editor
• Include an update button

• Current filename title is set to unique
• Since the database is shared across multiple users, a filename is invalid if someone else has already used it.
• this is a bug, and the filename should not be unique. rather, a a combination of the username and filename should be set to unique if needed.

• Use models to render the list instead of jquery.tml
• Use a controller to fetch the scriptlist via the API

• Submit user credentials
• Act according to the response by either showing the error message, or redirecting to the home page
• ember server must be launched with the --proxy option in order to let it access the API server . e.g. ember s --proxy http://127.0.0.1:8000 for accessing the python-flask app.

• Use a jquery based online code editor for basic syntax highlighting

The BSD licensed Ace code editor seems like a good choice, and has excellent reference code in the kitchen sink

This will enable users to take a quick look at the source code while viewing the output

All clients web, Android etc. should be able to access remote experiment features. Please outline experiments and describe what APIs/features are required.

When the user clicks on the edit button against any of his/her scripts, an AJAX call will be made to the server along with the unique ID of that script.
The server should search the database for this script, and respond accordingly so that the frontend can popup the code editor with the relevant contents.

• ember-cli-showdown can be used for client-side rendering of markdown.

@viveksb007 @asitava1998 @CloudyPadmal In the last PR , I embedded ace.js text editor on a page that allowed users to write their own Python code.

Now the question is how to store these.
Should they go into a database along with the Primary key user-email and a unique id for searchability,
or
Should they be stored as text files in a directory.

Which begs the larger question ... if users are allowed to upload experiment results/screenshots as the app evolves, where is such data typically stored?

• Plots once created can be updated via async json calls

• Will be required for array manipulations and other mathematical functions
• First use will be to convert separat xdata and ydata to xy pairs.

Automatic deployments to Heroku will enable everyone to test the system easily.

• deploy the flask backend
• deploy the EmberJS based frontend

• Enable callbacks via AJAX
• Support styling via bootstrap classes

• Return filenames and contents of all files stored in pslab-remote/app/scripts

These files will represent common applications and serve as examples for remote users. They will be read-only

Not sure if this can be achieved at this point, or if a separate repository will be needed for the webapp.

• Deploy API server via Heroku
• Deploy frontend via Surge

• ember install ember-bootstrap
• this does not use bootstrap.js , but instead uses better integrated ember components.
• Replace modals to delete and edit code

• Store function calls in a dictionary. This will be used for #34 in order to execute functions via a string.

The name virtual lab is already use by another project. The question here is anyways, if virtual lab would be the correct name. The goal of the project is to enable citizen scientists and students access to lab equipment that is not "virtual" but actually physically exists. This lab equipment is stationed remotely from the user. Therefore "remote lab" or something similar is probably a more correct naming.

return a comprehensive list of functions, their arguments and their docstrings

• {'status':true/false,
  'doc_list':[
  • { args:list of arguments, name:name of the function , doc_string : inline documentation if any },
  • {function 2},
  • {function 3},
    ....
    ]

}

• These docstrings will be passed over to the webapp's user-home page via its model, and will eventually be used for autocompletion, inline help tooltips etc

The webapp only has an option to logout as of now.

• handler will execute remotely submitted code in a sandbox
• stdout will be redirected to formatted html
• results will be displayed in the webapp

• At present, the return value of the codeEvaluator only includes any data printed to the console.
• It is not flexible enough to deal with other forms of output such as plots, or OOP constructs
• Converting the output of the codeEvaluator into a JSON object with each row/section representing the output at various points of the execution process can simplify creation of a more flexible output
• For example, If a plot is to be inserted, the relevant row can specify the HTML as well as the relevant JS snippet that must be injected in order to set it up.

• installation of dependencies
• running and testing locally
• links to blog posts

Please add all relevant services.

• add a toUnique method which accepts an ID string, checks if it exists, and then returns a new one

• The ability to write and submit scripts has already been implemented

• Now we need to show the list of submitted scripts on the user's homepage

• Further down the line(separate issue), the user should be able to view, edit, delete or execute these scripts.

how to reproduce the bug

import numpy as np
x=np.linspace(0,2*np.pi,30)
plt = plot(x, np.sin(x))
plt2 = plot(x, np.sin(x))

right way

import numpy as np
x=np.linspace(0,2*np.pi,30)
plt = plot(x, np.sin(x))
plt2 = plot(x, np.sin(x),name = 'newplotid')

default name is myPlot . However, the toUnique method is not being invoked , and hence the same name is used for all plots.

add *.pyc files in gitignore and remove them from repo.

Other FOSSASIA projects use Flask with Postgres. Please consider doing the same.

• return results via JSON {'status':true/false , 'data':object}

• Add a text input and a button on the user's home page to submit function strings
• Add a modal to show the results of the submitted function.

• install and use ember-ace
• create template for code submission
• Create controller to submit data to the backend

• Use jqplot
• add methods addPlot and setData

• At present, buttons when clicked can get numeric/string responses from an API and update a label
• Now they should be able to fetch arrays and update plot objects