-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A placeholder localhost URL in place for the Server buttons #59
Comments
hi @pradeeban I would like to contribute in this project and be part of your GSOC projects this year can u please guide me |
Hi and welcome, @parteekcoder. Please go through the README and previous discussions, also in https://github.com/NISYSLAB/Emory-BMI-GSoC/. |
Yeah can u please assign me some work so that I can understand better |
Please feel free to attempt the open bugs. |
But there are not many issues ,may be u can suggest some improvements if want |
@pradeeban is this issue still open to solve |
as there is already an PR for this issue |
@pradeeban this issue can be closed after reviewing. |
Thanks, @Rahuljagwani, for your contributions. Closing this issue now. |
concore editor is developed as a front-end for concore. However, currently, there is no seamless integration between the concore-editor and concore deployment. Currently, these server buttons (Build, Debug, Run, Clear, Stop, Destroy) do not do anything when clicked. Adding a sample URL from a localhost execution of concore FRI will provide a first step towards the integration with concore backend.
To identify and understand the concore APIs, please check the test.py provided as part of concore FRI. Concore FRI (File Receiver Interface) functions as a python interface to expose concore methods as REST APIs.
To test this locally and implement it, one must perform the below steps:
Following the above steps, once the concore FRI runs, implement a similar strategy (similar to how test.py functions as a client for FRI) with concore editor in Javascript (React or a similar framework).
The text was updated successfully, but these errors were encountered: