It is in main.js file. Can we have a call so that I will be able to explain
properly?



On Thu, Jul 28, 2022, 3:22 PM Pamidighantam, Sudhakar V <
spami...@illinois.edu> wrote:

> Where should I check for this path?
>
>
>
> Thanks,
>
> Sudhakar.
>
>
>
> *From: *Aishwarya Sinhasane <aishwaryasinhas...@gmail.com>
> *Date: *Thursday, July 28, 2022 at 3:20 PM
> *To: *dev@airavata.apache.org <dev@airavata.apache.org>
> *Subject: *Re: Regarding Airavata Seagrid Rich Client
>
> Hello Sudhakar
>
>
>
> It is working for me. This error is mainly because of path difference in
> OS. Can you please try giving path as per your OS requirements. I will make
> it dynamic today n will push the code again.
>
>
>
> Thanks & Regards
>
> Aishwarya Sinhasane
>
>
>
> On Thu, Jul 28, 2022, 1:01 PM Aishwarya Sinhasane <
> aishwaryasinhas...@gmail.com> wrote:
>
> Yes sure Sudhakar. I will try to fix it.
>
>
>
> Thank you
>
> Aishwarya Sinhasane
>
>
>
> On Thu, Jul 28, 2022, 12:57 PM Pamidighantam, Sudhakar V <
> spami...@illinois.edu> wrote:
>
> Aishwarya:
>
>
>
> I am getting this error message when I try to load the JSMol Editor. Can
> this be addressed.
>
>
>
> Thanks,
>
> Sudhakar.
>
>
>
> npm start
>
>
>
> > electron-quick-start@1.0.0 start
>
> > electron .
>
>
>
> (node:10220) electron: Failed to load URL:
> file:///Users/spamidig/Library/Applications/airavata-sandbox/gsoc2022/seagrid-rich-client/C:/Users/aishw/gsoc/seagrid-client-electron/airavata-sandbox/gsoc2022/seagrid-rich-client/ui/samplemol.html
> with error: ERR_FILE_NOT_FOUND
>
> (Use `Electron --trace-warnings ...` to show where the warning was created)
>
>
>
>
>
>
>
>
>
> *From: *Aishwarya Sinhasane <aishwaryasinhas...@gmail.com>
> *Date: *Thursday, July 21, 2022 at 3:49 AM
> *To: *dev@airavata.apache.org <dev@airavata.apache.org>
> *Subject: *Re: Regarding Airavata Seagrid Rich Client
>
> Hello Sudhakar,
>
>
>
> Yes I have committed the code and below is my repository and recent PR:
>
>
>
>
> https://github.com/aishwaryasinhasane/airavata-sandbox/tree/master/gsoc2022/seagrid-rich-client
> <https://urldefense.com/v3/__https:/github.com/aishwaryasinhasane/airavata-sandbox/tree/master/gsoc2022/seagrid-rich-client__;!!DZ3fjg!6dk7oQM3gRRFhxM9R-pq4Iv-7z1mJw4SdTXjpXj9PiV_umuOFJ4O64F2xveJrVIQq2V7iraP5cNASt2nzaRqQQhMc0W_sg$>
>
> https://github.com/apache/airavata-sandbox/pull/83
> <https://urldefense.com/v3/__https:/github.com/apache/airavata-sandbox/pull/83__;!!DZ3fjg!6dk7oQM3gRRFhxM9R-pq4Iv-7z1mJw4SdTXjpXj9PiV_umuOFJ4O64F2xveJrVIQq2V7iraP5cNASt2nzaRqQQiwC0o-Pg$>
>
>
>
> Thanks and Regards
>
> Aishwarya Sinhasane
>
>
>
>
>
> On Wed, 20 Jul 2022 at 15:33, Pamidighantam, Sudhakar V <
> spami...@illinois.edu> wrote:
>
> Aishwarya:
>
>
>
> Has a code been committed about this to git yet? Could you please point to
> the repo.
>
>
>
> Thanks,
>
> Sudhakar.
>
>
>
> *From: *Aishwarya Sinhasane <aishwaryasinhas...@gmail.com>
> *Date: *Tuesday, June 21, 2022 at 9:21 PM
> *To: *dev@airavata.apache.org <dev@airavata.apache.org>
> *Subject: *Regarding Airavata Seagrid Rich Client
>
> Hello Everyone,
>
>
>
> I tried to make a login module in electronJS which is working properly for
> login with credentials as well as CILogon.
>
>
>
> The electronJS application loads the django airavata portal so we can
> access all the modules that are already present in the django portal.
>
>
>
> I discussed with sudhakar about including other modules such as
> Application Editors and Molecule Editors in application. We came to the
> conclusion that to include these modules in the main menu of the
> application. Users can access these before login and can create molecules
> and applications using editors and once it's ready to create an experiment
> the user needs to login to the system. Also users can login and can access
> editors.
>
>
>
> Currently, I am developing the frontend for the molecule editor nanocad.
> Also I am trying to understand the logic of the molecule editor developed
> in JavaFX.
>
>
>
> If anyone has other suggestions please let me know.
>
>
>
> Screenshots are attached below for your reference.
>
>

Reply via email to